Fastboot says waiting for any device: why the phone is not detected and how to fix it
Waiting for any device means fastboot is running but sees no phone in Fastboot mode. The phone may show a Fastboot screen. The cause is almost always on the PC side: driver, cable, port or an outdated fastboot.
Quick diagnosis
- Is the phone really in Fastboot? On Xiaomi a bunny, on others the word FASTBOOT.
- Open Device Manager and connect the phone.
- Android with a yellow mark means no driver.
- Android Bootloader Interface means the driver is there and the issue is fastboot or the port.
- No change means the cable or USB port.
Install Android Bootloader Interface
- Download the Google USB Driver or the maker driver.
- In Device Manager, right-click Android, Update driver, Browse, Let me pick.
- Choose Android Device then Android Bootloader Interface.
- Confirm and reconnect.
fastboot devices should then print the serial.
Outdated fastboot
Old fastboot builds from third-party archives may not work with new phones. Download the latest platform-tools from Android and run fastboot from that folder. Remove old adb/fastboot copies from PATH so the wrong file does not run.
USB 3.0 and ports
On some platforms, especially AMD Ryzen and newer Intel chipsets, Fastboot on USB 3.x is unstable: the phone appears and disappears. A rear USB 2.0 port, a USB 2.0 hub or another PC helps. Front-panel ports and long extensions are a common cause.
Symptom table
| Symptom | Cause | Fix |
|---|---|---|
| waiting for any device | no driver or wrong fastboot | Bootloader Interface driver, fresh platform-tools |
| Device flickers in Device Manager | cable or USB 3.x | another cable, USB 2.0 |
| FAILED (remote: ...) | link works, command unsupported | check the command for that firmware |
| Phone leaves Fastboot at once | key or firmware | re-enter, do not hold the keys |
Fastboot and service tools
Many tools use Fastboot to read device info and the codename. On Xiaomi, Fastboot can reveal the version and chip before EDL or BROM work. If Fastboot is not detected, the tool will not see the phone either. First make fastboot devices print the serial.
If the phone will not enter Fastboot
If holding the keys boots the system or recovery instead, power off fully, wait 10 seconds and hold the combination until it powers on. On Xiaomi you can use adb reboot bootloader if debugging is on. On a locked phone with no system access only the keys remain.
Fastboot and an unlocked bootloader
Fastboot works on a locked bootloader too, but many write commands are rejected. FAILED (remote: Flashing is not allowed in Lock State) means the link works and the bootloader is closed; that is not a driver problem.
Brand notes
| Brand | Enter Fastboot | Note |
|---|---|---|
| Xiaomi / Redmi / POCO | power + volume down | bunny screen |
| Motorola | power + volume down | bootloader menu |
| Google Pixel | power + volume down | Google USB driver |
| Samsung | no Fastboot | uses Download Mode |
Real-world example
A Redmi Note 13 on a Ryzen laptop kept showing waiting for any device even with the driver installed. On an Intel PC it was detected at once. The fix on the first laptop was a USB 2.0 hub between the phone and the port.
Glossary
- Fastboot — the Android bootloader mode for flashing partitions.
- platform-tools — the official adb and fastboot package.
- Android Bootloader Interface — the Windows driver for Fastboot.
Which tool fits
Once Fastboot is detected, work continues in a service tool: UnlockTool rental or Android Multi Tool rental.
Bottom line
Waiting for any device is almost always the driver, an old fastboot or the port. Install Android Bootloader Interface, use fresh platform-tools and a USB 2.0 port, and the phone will be detected.
Does debugging need to be on?
No, USB debugging is for ADB inside the system, not for Fastboot. In Fastboot the phone is identified by the Bootloader Interface driver regardless of the debugging setting. Antivirus rarely blocks fastboot.exe, but if it does, add the platform-tools folder to the exclusions.
Future tip
Keep one current platform-tools folder and a verified driver on the work PC. Then waiting for any device will only ever mean a cable or mode problem, not a PC setup problem.
FAQ
Why does adb see it but fastboot does not?
They are different modes with different drivers. In Fastboot the phone is Android Bootloader Interface; without that driver the command waits forever.
Where do I get platform-tools?
From the official Android developer page.
Does USB 3.0 help?
Fastboot can be unstable on USB 3.x; try USB 2.0 or a USB 2.0 hub.
What is FAILED remote unknown command?
The phone answered: the link works but the command is not supported on that firmware.
Why did a Windows update break it?
The update may have replaced the driver with a plain Android one; reinstall Android Bootloader Interface by hand.
Can I use Fastboot on a Mac?
Yes, platform-tools exist for macOS with no driver, but many service tools are Windows-only.