Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

adb devices => no permissions (user in plugdev group; are your udev rules wrong?) [duplicate]

I am getting following error log if I connect my android phone with Android Oreo OS to Linux PC

$ adb devices
List of devices attached
xxxxxxxx    no permissions (user in plugdev group; are your udev rules wrong?);
see [http://developer.android.com/tools/device.html]

I tried with the link provided by the error message but still getting same error.

like image 549
Abhishek Dwivedi Avatar asked Sep 25 '22 10:09

Abhishek Dwivedi


People also ask

How to add user to playdev group?

Add your user to playdev group as below, Know the USB Vendor Id and Product Id of your android device using lsusb command as, As seen above, For Our mobile idVendor is 2e04 and idProduct is c008, add this details to udev rule as, [ Replace idVendor and idProduct as per your device ]

Is there a default set of udev rules for Android devices?

This gives you a community-maintained default set of udev rules for all Android devices. I also had to restart ubuntu for the error to disappear. This is also in the Android Studio User Guide. See: developer.android.com/studio/run/device#setting-up

What to do if device is not detected by udev rule?

Now the device is good to be detected once udev rule is reloaded. So, let's do it: So, you are done. If it still doesn't work, unplug/replug the device. If it still doesn't work, restart your OS. This s/b the accepted answer.

How to find all USB devices in Ubuntu without permissions?

Ubuntu adb :no permissions (user in plugdev group; are your udev rules wrong?); Open source software supply chain lighting plan, waiting for you>>> He will list all the USB devices, you can find them. If you can’t find it, unplug your mobile phone and see if it’s missing


2 Answers

Check device vendor id and product id:

$ lsusb
Bus 001 Device 002: ID 8087:8000 Intel Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 078: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint Reader
Bus 002 Device 003: ID 8087:07dc Intel Corp. 
Bus 002 Device 002: ID 5986:0652 Acer, Inc 
Bus 002 Device 081: ID 22b8:2e81 Motorola PCS 
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Here my android device is Motorola PCS. So my vid=22b8 and pid=2e81.

Now create a udev rule:

$ sudo vi /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="2e81", MODE="0666", GROUP="plugdev"

Now the device is good to be detected once udev rule is reloaded. So, let's do it:

$ sudo udevadm control --reload-rules

After this, again check if your device is detected by adb:

$ adb devices
List of devices attached
ZF6222Q9D9  device

So, you are done.

If it still doesn't work, unplug/replug the device.

If it still doesn't work, restart your OS.

like image 379
Abhishek Dwivedi Avatar answered Oct 10 '22 08:10

Abhishek Dwivedi


I don't know the reason behind this issue. But a temporary fix would be to set the phone to File Transfer mode or MTP mode.

The problem with this fix is that you'll need to set the mode from charging mode to File transfer mode or MTP mode every time the cable is connected.

like image 194
Nabin Bhandari Avatar answered Oct 10 '22 07:10

Nabin Bhandari