Some situations and solutions of ADB's non-recognition device (mobile phone)

1. Execute ADB root hint adb:unable to connect for Root:no devices/emulators found; execute ADB devices, no device under list

= = "is often a data cable or USB jack problem, change the root data cable or a different USB port to try

2. Execute ADB devices list under "592b925b no permissions (verify Udev rules)"; Perform the ADB root prompt "adb:unable to connect for root:insufficient permissions for device:verify udev rules."

= = "No permission is required because it is necessary to increase the Verdorid and ProductID of the device in/etc/udev/rules.d/70-android.rules." This is not the case with all new devices, and occasionally there are devices that need to be manually added

Add the following method:

(1) In the case of plug-in device and plug-in device, execute LSUSB separately to find the corresponding item of the device. Xxxx:yyyy are VendorID and ProductID, respectively.

(2) Add Item in/etc/udev/rules.d/70-android.rules file: subsystem== "USB", attrs{idvendor}== "xxxx", attrs{idproduct}== "yyyy" , mode= "0666" note the replacement of XXXX and YYYY, save the file

(3) sudo chmod a+rx/etc/udev/rules.d/70-android.rules Add file permissions, can be viewed first, all have RX permissions, you can no longer perform the addition

(4) Sudo/etc/init.d/udev restart

(5) sudo./adb kill-server

OK, can be viewed through ADB devices, the device should be able to recognize the

Some situations and solutions of ADB's non-recognition device (mobile phone)