One, Solution 1.
1, use the following command to get the PID and vid of the machine.
Lsusb
you will see the following feedback:
Icon
Bus 002 Device 002:id 8087:8000 Intel Corp bus 002 device 001:id 1d6b:0002 Linux Foundation 2.0 root Hubbus 001 Device 002:id 8087:8008 Intel Corp Bus 001 device 001:id 1d6b:0002 Linux Foundation 2.0 root hubbus 004 Device 001:id 1d6b:00 The Linux Foundation 3.0 root Hubbus 003 device 004:id 413c:2107 Dell computer Corp. Bus 003 Device 003:id 046d:c077 Logi Tech, Inc. bus 003 device 023:id 0e8d:201d Lenovo Inc. bus 003 device 012:id 0424:2514 Standard Microsystems Corp. USB 2 .0 Hubbus 003 Device 001:id 1d6b:0002 Linux Foundation 2.0 root Hub
where our machine is Lenovo, then we can get our vid as well as the PID. respectively: 0e8d:201d.
2. In the. Android directory, create a new Adb_usb.ini file that writes the vid we just got in this file.
1,CD ~/.android/2,touch Adb_usb.ini3, the vid is written to Adb_usb.ini.
3, perform kill-server and start-server operations in Administrator mode.
1, sudo -s2,adb kill-server2,adb start-server. Or 1, sudo adb kill-server2, sudo adb start-server .
two, Solution 2.
Some devices cannot be managed by Ubuntu, and it is possible that the system does not have permissions to perform certain operations. Android authorities have given some solutions. You can do the following:
Add the following to the file:
1,sudo Vim/etc/udev/rules.d/50-android.rules
Devtype is a description of the equipment in our program 1 through LSUSB. The device description for MTK is: MediaTek Inc.
Usb_device, which is USB uid.uid, can refer to scenario 1.
Then proceed to the 3rd step in Scenario 1.
2,subsystem== "USB", env{devtype}== "Usb_device", mode= "0666". For example: subsystem== "USB", sysfs{"high Tech computer Corp."} = = "0bb4", mode= "0666"
Third, frequently asked questions:
1, there is a solution to the following phenomenon.
This phenomenon indicates that your machine has been identified, but Ubuntu needs permission.
List of devices attached???????????? No permissions
Please do the following:
1, sudo -s2,adb kill-server2,adb start-server. Or 1, sudo adb kill-server2, sudo adb start-server .
ADB cannot find device