ADB usage and problem solving on Ubuntu

ADB usage and problem solving on Ubuntu

The ADB package is extracted from the decompression version of Eclipse (ADB can be used independently from Eclipse or SDK and can be copied directly)

and made a Soft link under/sbin/(Employee PC has been done), $sudo ln–s/home/it/sdk/platform-tools/adb/sbin/, can execute which command to view: $ which adb

ADB version: 1.0.31 (Android 4.4.2 requires ADB version 1.0.29 above if ADB version is lower can be replaced)

After the ADB executes the kill, then start will generate the. Android directory (sudo before command execution)

$ sudo adb kill-server

$ sudo adb start-server

$ sudo ls/root/.android/(Adbkey and Adbkey.pub)

and then in /root/android/New Adb_usb.ini file, the file is written on the phone USB ID (can be viewed through LSUSB, such as: 0x1773)

If an employee Ubuntu cannot connect to the phone first to see if the file (Adb_usb.ini) exists, or if the file contents (0x1773) are correct

Execute again adb kill and ADB start (don't forget to add sudo)

To see if your phone is connected to your computer properly: $ adb Devices

Under normal circumstances, the following content will appear

Listof devices attached

19761202 Device (This information is not fixed, as long as there is information on the line)

If it appears

Listof devices attached

???????? No permissions

Please perform the following command to resolve:

$sudo adb kill-server

$sudo adb start-server

If the device doesn't show up,

Listof devices attached

please click on phone settings -Application-Development-USB debug (if checked please remove tick after check)

Then hit the following command:

$sudo adb kill-server

$sudo adb start-server

Login Phone Command:

$ADB Shell

under normal circumstances, it will enter Root Mode

#

This article from "Linux" blog, declined reprint!

ADB usage and problem solving on Ubuntu