Ubuntu using ADB to connect Android phone failed unknown solution
The ADB may not be able to recognize the device after it is connected to the G11 phone via a USB cable under Ubuntu. Follow the steps to resolve this issue.
1. Enter LSUSB below the terminal
[Email protected]:~$ Lsusb
Bus 001 Device 002:id 8087:8008 Intel Corp.
Bus 002 Device 002:id 8087:8000 Intel Corp.
Bus 003 Device 048:id 17ef:7435 Lenovo
Bus 003 Device 002:id 03f0:094a Hewlett-Packard
Bus 003 Device 003:id 03f0:034a Hewlett-Packard
Bus 001 Device 001:id 1d6b:0002 Linux Foundation 2.0 root Hub
Bus 002 Device 001:id 1d6b:0002 Linux Foundation 2.0 root Hub
Bus 003 Device 001:id 1d6b:0002 Linux Foundation 2.0 root Hub
Bus 004 Device 001:id 1d6b:0003 Linux Foundation 3.0 root Hub
You will find that the results are similar to the following records:
Bus 003 Device 048:id 17ef:7435 Lenovo
2. Enter [email protected]:~$ sudo gedit/etc/udev/rules.d/50-android.rules
Add the following text to the open file:
subsystem== "USB", attrs{idvendor}== "17ef", attrs{idproduct}== "7435", mode= "0666"
(Note: 17ef:7435 corresponding values Attrs{idvendor} and Attrs{idproduct})
3. Enter the following command in Terminal:
sudo chmod a+rx/etc/udev/rules.d/50-android.rules
Sudo/etc/init.d/udev restart (with hints and no need to worry about him)
4. Run in the tools directory of the Android SDK (this step is important, it must be sudo, otherwise no effect)
sudo./adb kill-server
sudo./adb start-server
sudo./ADB devices
Another type of:
The ADB may not be able to recognize the device after it is connected to the G11 phone via a USB cable under Ubuntu. Follow the steps to resolve this issue.
1. Enter LSUSB below the terminal
You will find that the results are similar to the following records:
Bus 001 Device 008:id 0bb4:0c02 high Tech computer Corp.
2. Enter sudo vim/etc/udev/rules.d/50-android.rules
Add the following text to the open file:
subsystem== "USB", sysfs{"high Tech computer Corp."} = = "0bb4", mode= "0666"
3. Enter the following command in Terminal:
sudo chmod a+rx/etc/udev/rules.d/50-android.rules
Sudo/etc/init.d/udev restart
4. Run in the tools directory of the Android SDK (this step is important, it must be sudo, otherwise no effect)
sudo./adb kill-server
sudo./ADB devices
You can then debug by executing commands such as the ADB shell.
If there is still no connection to the
VI ~/.android/adb_usb.ini
After adding the device ID mentioned above, try again:
0x0bb4
