Workaround 1:lsusb View the VendorID number, and then add (or modify) the 51-android.rules file under the/etc/udev/rules.d/directory.
Add a record:
subsystem== "USB", sysfs{idvendor}== "xxxx", mode= "0666" where xxxx is the value obtained by LSUSB view
The common situation is as follows, I have listed here:
# HTC
subsystem== "USB", sysfs{idvendor}== "0bb4", mode= "0666"
# Motorola
subsystem== "USB", sysfs{idvendor}== "22b8", mode= "0666"
# Acer 0502
subsystem== "USB", sysfs{idvendor}== "0502", mode= "0666"
# Dell 413c
subsystem== "USB", sysfs{idvendor}== "413c", mode= "0666"
# Huawei 12D1
subsystem== "USB", sysfs{idvendor}== "12d1", mode= "0666"
# LG 1004
subsystem== "USB", sysfs{idvendor}== "1004", mode= "0666"
# Nvidia 0955
subsystem== "USB", sysfs{idvendor}== "0955", mode= "0666"
# Samsung 04e8
subsystem== "USB", sysfs{idvendor}== "04e8", mode= "0666"
# sharp 04DD
subsystem== "USB", sysfs{idvendor}== "04DD", mode= "0666"
# Sony Ericsson OFCE
subsystem== "USB", sysfs{idvendor}== "0fce", mode= "0666"
# ZTE 19D2
subsystem== "USB", sysfs{idvendor}== "19d2", mode= "0666"
Workaround 2:
Write only one sentence in the 51-android.rules:
SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", MODE="0666"
Android adb shell fails to start: Insufficient permissions for device