ADB stopping at <waiting for devices>

Question

I was trying to install some custom recovery and ROM on to my phone when I got to this situation.

(I have my windows update turned off)

ADB or fastboot shows

<waiting for devices>

I tried and saw few solutions. I'm writing a detailed solution to this. this was how I solved it. if you have more suggestions you can answer below.

Solution 1

the only reason for this is that your PC is not recognizing Phone.which is a driver problem.

You have to understand a few things before starting with the solution. you may know this too.

• when you are in your recovery adb gets into something like recovery mode(just framing some terms myself)

• in bootloader, it takes fastload mode.

each of this mode needs different drivers other than what the driver you use with adb when your phone is running on OS.

so what you have to do is.

if you are trying to get into recovery mode or fastload mode.

• open device manager(settings>devices>(more options)Device manager).

• now boot the phone into the required mode using manual or adb method.

• the device manager reloads and a new driver will be shown. either in Android or pointing device or others folder.

• select the driver and update online.(always preferred).

• if you don't find an online driver you have to select manual update here. select browse my computer. select let me pick. select browse.

at last, you have to select the usb-driver provided by the google. in sdk>extras>google>usb-driver

it will show the updatable driver.select and press next to install. press ok now it should work correctly.

Solution 2

Happened to MACOS Mojave 10.14.6 while trying to install twrp-3.3.1-2-enchilada.img.

Solved it by running:

adb reboot-bootloader

Then, when the phone boot into bootloader,

fastboot boot twrp-3.3.1-2-enchilada.img

worked like a charm

Solution 3

For me it was not turning on usb debugging.

(settings -> developer options(you should activate this if you don't see this option) -> usb debugging.)

Solution 4

Run following command to get your device into FastBoot mode (from adb-driver folder if using Windows System)

adb reboot-fastboot

Solution 5

I had to update Windows 10 to resolve this issue.

I believe the needed update was a driver update for Android Bootloader Interface from Google, Inc. Windows updated several things at once so I can't verify that is what specifically solved the problem for me.

View more solutions

Comments

[Dyno Cris]

Where to download the usb driver?

[Dyno Cris]

I can't to find the usb-driver folder

[Dyno Cris]

Oh, I solved! You can download usb-driver here developer.android.com/studio/run/win-usb

[Erick Adam]

what about if I am using a Samsung phone to deploy an app to my phone? I'm trying to use the WSL (Ubuntu) but it can't ever recognize my phone outright. It's present in my device manager, but I still get the "waiting for any device" message when I run the WSL shell in cmd.

[Reg Edit]

Have you enabled USB debugging in the phone settings?

[Erick Adam]

I did. No difference.

[Reg Edit]

So @ErickAdam did you follow the steps for Ubuntu? developer.android.com/studio/run/device says, "Ubuntu Linux: There are two things that need to be set up correctly: each user that wants to use adb needs to be in the plugdev group, and the system needs to have udev rules installed that cover the device." But actually if you are trying to use USB under WSL,. it may not supported; see here for info and a project aiming to make it possible devblogs.microsoft.com/commandline/…

[Erick Adam]

I actually figured it out. I was able to make the adb in Ubuntu WSL (/usr/bin/adb) equal to the adb in my Windows (/platform-tools/adb). I tried doing it before and had trouble, but finally figured it out, so now I can connect through USB.