fastboot and adb not working with sudo fastboot and adb not working with sudo android android

fastboot and adb not working with sudo


Instead of forcing permissions via sudo each time you need to run fastboot, you can permanently fix the issue:

  1. use lsusb to identify your device USB VendorID
  2. configure udev to set proper permissions when your device is plugged in
  3. profit!

As a bonus - it will be fixed for adb too.

For example, in my case (for 'Megafon SP-A20i') :

$ fastboot devicesno permissions  fastboot$ sudo fastboot devices[sudo] password for kaa: MedfieldA9055F28    fastboot$ 

Let's fix:

First, we need to identify the device:

a) look for usb bus number (hack: I know the device is Intel-based one)

$ fastboot -l devicesno permissions         fastboot usb:1-1.2$ lsusb |grep 001 |grep -i intelBus 001 Device 044: ID 8087:09ef Intel Corp. Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub$ 

b) look for other Intel devices:

$ lsusb |grep 8087Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching HubBus 001 Device 044: ID 8087:09ef Intel Corp. Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub$ 

Hubs are not smartphones definetely, so - USB vendorID we need is "8087".

Second, configure udev (you must replace "idVendor" value with yours) :

$ sudo sh -c "echo '# Megafon SP-A20i' >> /etc/udev/rules.d/51-android.rules"$ sudo sh -c "echo 'SUBSYSTEM==\"usb\", ATTR{idVendor}==\"8087\", MODE=\"0666\", GROUP=\"plugdev\"' >> /etc/udev/rules.d/51-android.rules"$ sudo service udev restartudev stop/waitingudev  start/running, process 1821$ 

Third, re-plug your device to allow udev to perform it's magic.

Final check:

$ fastboot -l devicesMedfieldA9055F28       fastboot usb:1-1.2$ adb devicesList of devices attached $ fastboot rebootrebooting...finished. total time: 0.253s$ sleep 90$ adb devicesList of devices attached MedfieldA9055F28    device$ 

Voila!


You can use

sudo $(which fastboot) devices