Geek Answers Handbook

Adb no permissions error suddenly

I have been working on the Snapdragon Dragonboard for several days. I was able to configure it and even push some applications on it and run them. Of course, the adb shell commands and adb devices gave me some meaningful results. But today I can’t detect the device, adb shell gives me enough permissions error and adb devices give me

????????? no devices

The instructions that I followed at the beginning of working with this board told me to include the line: 0x05c6; 0x0956 0x05c6; 0x0956 in adb_usb.ini in the ~/.android .

However, today I saw better documentation that asked me to include the line SUBSYSTEM=="usb",SYSFS{idVendor}=="05c6",MODE="0666"
I replaced SYSFS with ATTR coz. I read somewhere that the latest udev requires ATTR instead of SYSFS

I carry out:

 chmod a+r 51-android.rules sudo stop udev sudo start udev android update adb adb kill-server adb start-server adb devices

and I get the same result! No permissions yet. What is going wrong? Btw, lsusb gives me a Qualcomm record. When usb is disabled, the lsusb command does not give me a Qualcomm entry. How to change behavior in one night?

+4
source share
2 answers

Instead:

adb kill-server

adb start-server

I tried:

sudo adb kill-server

sudo adb start-server

somehow it works. I do not know why.

+6
source

It looks like your udev rule is broken, and at some point you started the adb daemon as the root user. This is pretty easy to do by accident, since running adb with any command will start the daemon if it is not already running. Using the root user to manually start the daemon is great for solving the problem, but tools like Eclipse that automatically start the service will still try as an unprivileged user (which will cause the problem). The correct fix is ​​to follow the official steps in Configuring USB Access .

+2
source

More articles:


All Articles