Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Android fastboot waiting for devices

I am trying to load a customized kernel on my NVIDIA test git. I typed fastboot boot myImage after which which I get:

<Waiting for device>  

I think this is a problem with a driver on fastboot mode on my device. But I don't know how to install the driver on linux.

Do you guys know how to install the driver?

like image 305
codereviewanskquestions Avatar asked Oct 03 '11 23:10

codereviewanskquestions


People also ask

How do I fix fastboot mode waiting for device?

From a completely fresh win 10 installation I just plugged in my phone, install the OnePlus drivers, then activated USB debugging, allowed all drivers to be installed. Added necessary ADB and fastboot files in a folder to C: and then typed ADB devices via powershell in that folder, got prompted to accept the device.

Why my device is not showing in fastboot devices?

The very first reason is a faulty USB cable or port. If either of these things is damaged, Fastboot will not work on your system. To access the Fastboot mode, you need to choose “Charge only” upon connecting your Android smartphone with a PC using a USB cable.

How do I know if my device is connected to fastboot?

Boot your phone into Android, then connect it to your desktop computer with a USB cable. On your computer, launch the Command Prompt and change the directory to point to the platform-tools folder. Type adb devices and hit Enter. You should now see a list of attached devices, with a serial number.

What is adb wait for device?

Device Basics wait-for-device can be specified after adb to ensure that the command will run once the device is connected. -s can be used to send the commands to a specific device when multiple are connected.


2 Answers

The short version of the page linked by D Shu (and without the horrible popover ads) is that this "waiting for device" problem happens when the USB device node is not accessible to your current user. The USB id is different in fastboot mode, so you can easily have permission to it in adb but not in fastboot.

To fix it (on Ubuntu; other systems may be slightly different):

Run lsusb -v | less and find the relevant section which will look something like this:

Bus 001 Device 027: ID 18d1:4e30 Google Inc.  Couldn't open device, some information will be missing Device Descriptor: ...   idVendor           0x18d1 Google Inc. 

Now do

sudo vi /etc/udev/rules.d/11-android.rules 

it's ok if that file does not yet exist; create it with a line like this, inserting your own username and vendor id:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="18d1", MODE="0640", OWNER="mbp" 

then

sudo service udev restart 

then verify the device node permissions have changed:

ls -Rl /dev/bus/usb 

The even shorter cheesy version is to just run fastboot as root. But then you need to run every command that talks to the device as root, which tends to cause other complications. Simpler just to fix the permissions in the long run.

like image 54
poolie Avatar answered Sep 21 '22 00:09

poolie


Just use sudo, fast boot needs Root Permission

like image 33
Saleh Abdulaziz Avatar answered Sep 19 '22 00:09

Saleh Abdulaziz