How to fix fastboot devices not detected (waiting for any device) 2023

preview_player
Показать описание

Drop a comment below if you have questions or reach out to us on the following platforms:

Video Transcript

0:00:10.240,0:00:16.520
There are times that even if you've installed your ADB fastboot drivers you

0:00:16.520,0:00:20.300
still don't get detection when you run fastboot commands or even adb commands

0:00:20.300,0:00:31.760
I'm going to give you an example. In this
case I'm going to run an ADB command I'm

0:00:31.760,0:00:42.380
going to launch ADB. I'll do this by copying the address on my ADB folder and then cd ... so

0:00:42.380,0:00:46.489
now I'm in the adb directory so I'm going to run this ADB command:

0:00:46.489,0:00:50.090
adb devices . Don't forget your phone has to be connected to

0:00:50.090,0:00:55.100
the PC via USB cord and USB debugging enabled on the phone for it to

0:00:55.100,0:01:01.700
have a detection. Now I have ADB detection so I'm going to boot this phone into

0:01:01.700,0:01:08.289
fastboot and run a fastboot command so adb reboot bootloader

0:01:10.329,0:01:17.770
This is going to boot my phone into fastboot so on the screen you will

0:01:17.770,0:01:22.479
notice the blank screen and fastboot mode written somewhere on the

0:01:22.479,0:01:28.390
screen so I'm going to run a fastboot command right now fastboot devices to

0:01:28.390,0:01:35.229
check if I have detection. As you can see, I have no detection. Now, when you

0:01:35.229,0:01:40.329
encounter this kind of issue you have two options or two things to try. First off,

0:01:40.329,0:01:44.979
you need to download the latest fastboot binaries. We have that at our forum so

0:01:44.979,0:01:49.420
visit the Hovatek Forum, download the latest fastboot binaries and then retry running the

0:01:49.420,0:01:53.200
command. If you still don't get a detection then you need to update the phone's

0:01:53.200,0:01:58.149
fastboot drivers. Now, to do that, you (still with the phone in fastboot mode and

0:01:58.149,0:02:08.019
connected to the PC) launch device manager and then you look out for what

0:02:08.019,0:02:14.410
the phone gets detected as. You'll find something like this under other devices Android

0:02:14.410,0:02:19.389
this is what mine looks like. To confirm that, I'm going to disconnect the phone that

0:02:19.389,0:02:26.260
should disappear. You can see it disappears. I'm going to reconnect the phone still

0:02:26.260,0:02:29.400
in fastboot

0:02:34.310,0:02:38.390
Now this is what you're going to be updating all right? You need to have

0:02:38.390,0:02:43.550
downloaded the updated Google USB drivers. We also have a link to that at our

0:02:43.550,0:02:48.530
forum so check it out. This is what it looks like; the updated

0:02:48.530,0:02:53.150
Google USB drivers. You are going to be manually updating your drivers to this

0:02:53.150,0:02:58.819
so now you right-click this Android entry, select Update driver, Browse my

0:02:58.819,0:03:08.209
computer for driver software, Let me pick from a list, Next, Have disk, click on

0:03:08.209,0:03:13.670
Browse. You navigate to the location of the USB drivers and select the

0:03:13.670,0:03:20.569
Android_USB.inf file. Select Open, OK then you highlight Android

0:03:20.569,0:03:29.269
bootloader interface, Next, Click on Yes anyway. Don't forget that if you are

0:03:29.269,0:03:34.550
using a Windows 8 and above PC, you need to have disabled driver signature verification so

0:03:34.550,0:03:38.900
Windows has successfully updated your drivers. You can click on close. Now, you're going to re-run

0:03:38.900,0:03:47.650
the fastboot command fastboot devices
and I have a detection --------------------------
Hire Or Consult Us

Join Our Training
Рекомендации по теме
Комментарии
Автор

You saved my life!
It was the first time that the drivers didin't work automatically and I was stuck in bootloader, I was afraid the problem was more serious...
Thanks for share this method!

AndreaMunnia
Автор

3 hours I'm looking for a solution!!! thanks man

Witchness
Автор

I thought it was clickbait but it turned out to be working thanks guy for everything

gin
Автор

it said it doesnt contain a compatble driver software

sxndypz
Автор

cant find my device in other devices while in fastboot mode

umeshpatil
Автор

Bro just keep it up it worked for my redmi 5a

rehanahmed
Автор

Thats my exact problem, there is no detection whatsoever when my phone is in fastboot mode, not even an unrecognized device, the second I leave adb and boot my fastboot my device completely disappears from the device manager screen, please help.

ttaytrevor
Автор

what kinda accent is it? any african country is my guess. I like it.
You are a hero man, no one else mentioned this.

skullteria
Автор

Thank you for the video, that helped a lot!

vladisslave.
Автор

My adb detects my phone in normal mode, but when I boot into recovery mode it doesn't show my device. I have installed the drivers, etc. What else can I try?

avk
Автор

thank you so much bro you solved my problem

debrajbiswas
Автор

Achtung. If nothing works for you and you have a device with two USB ports (Type-C perhaps) - try plugging in the cable in the side port, not the bottom one.

tomar-bz
Автор

I received an error message when following your step.

"The folder you specified doesn't contain a comptabile software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems."

Please help. ( Using Razer phone 2, android 9)

justicevsunfair
Автор

after I enter the command adb reboot bootloader the phone shutdown and message pop up saying "the serial is not match" so I can't enter the fastboot mode
how to resolve it?
TIA

whtsername
Автор

Oh, thanks a lot brother. My device was not shown after executing 'fastboot devices' command in fastboot mode. Your this tutorial fixed it for me

yapsejaiteh
Автор

I did everything you told but nothing worked on my Oneplus Nord 2... what should I do ?

shubhamsrivastava
Автор

Hello
When I select android in device and manager and do the steps u said and install the adb bootloader then still the name of device is android and now it has a question mark on it

thetron
Автор

what if my phone doesn't detected as "Android" on other devices? the device manager detected it as "ADB composite interface"

reliqua
Автор

my phone not detected by device manager in fastboot mode
but detected normally when boot into system
any solution?

nextgodlevel
Автор

My device doesn't show up in device manager after being booted into fastboot mode so I can't update the driver

zizi