fix adb devices no permission

Error:

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

Fix: 
1> sudo usermod -aG plugdev $LOGNAME (https://developer.android.com/studio/run/device)
2> lsusb
3> sudo vi /etc/udev/rules.d/51-android.rules
4> SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="2e81", MODE="0666", GROUP="plugdev" (idVendor, idProduct found at lsusb command)
5> sudo udevadm control --reload-rules
6> sudo adb kill-server
7> sudo adb start-server
( link: https://stackoverflow.com/questions/53887322/adb-devices-no-permissions-user-in-plugdev-group-are-your-udev-rules-wrong)

I always have this problem when my Pixel is in "Charging Only"/"No data transfer" mode. Setting it to "File transfer" (others may work as well) is the fix in this case.
(Just leaving this info here for the next time I end up here from Google 😉 )

Wonderful, solved my issue, thanks @dreua

Tips: In Oculus I had this error, the solution is just to unplug/plug the device (Oculus). Confirm the autorisation on my device and it worked.

I always have this problem when my Pixel is in "Charging Only"/"No data transfer" mode. Setting it to "File transfer" (others may work as well) is the fix in this case. (Just leaving this info here for the next time I end up here from Google wink )

Thanks this worked on my PixelExperience rom

I always have this problem when my Pixel is in "Charging Only"/"No data transfer" mode. Setting it to "File transfer" (others may work as well) is the fix in this case. (Just leaving this info here for the next time I end up here from Google wink )

ah this worked for me thank you very much

Heh I wouldn't have thought that my comment would turn out that helpful after going unnoticed for about a year. Anyway, I'm always happy to help, thanks for your kind responses ❤️

@martinericksonn Same here! Works well on PixelExperience ROM! Thanks @dreua!

I always have this problem when my Pixel is in "Charging Only"/"No data transfer" mode. Setting it to "File transfer" (others may work as well) is the fix in this case.

That really helped, thank you!

actually the issue persists. ADB has no errors anymore, fastboot still doesnt see a device...

@firefoxlover fastboot won't work when your device is booted normally to the system. You need to boot to the recovery of your phone (google it up for your model), connect it to your computer, and only then fastboot would work.

You most likely won't need this workaround in that case.

NOTE: AFAIK fastboot isn't available in all devices, e.g. some Samsung devices only support Samsung's own "Odin" tool.

@Skaldebane Yes I know, thats what I did. Its not Samsung, and it worked in the past, so I think it has to do something with udev rules.

I can do adb reboot bootloader thats the weird thing. But while in there no USB device is detected.

Thanks so much for sharing it

@firefoxlover That's weird. Depending on your OS you might need some extra drivers? You may find some solution online for your device model.

I always have this problem when my Pixel is in "Charging Only"/"No data transfer" mode. Setting it to "File transfer" (others may work as well) is the fix in this case. (Just leaving this info here for the next time I end up here from Google wink )

@dreua That really helped too, thank you!

Thanks bro it works!!

1. 5. 6. steps worked for me thanks.

First step helped 🤝

Much appreciated Sir, found it difficult to understand why the error occurred in the first place but this helped fix it anyway, immensely helpful...