Database Info

Fastboot Commands Don't Work

I am trying to unroot and re-lock my xoom and everytime I try to use a fastboot command all I get at the command promt is "waiting for device". I have installed the moto drivers and adb is working fine, just no fastboot. Please help... Thanks in advance!

did you reboot your xoom into bootloader mode? (adb reboot bootloader)

does it show any devices when you type
adb devices

Yes,
adb devices returns the attached device with the serial number.
adb reboot bootloader reboots the device and it say starting fastboot protocol at the top. then when I try to use fastboot flash boot boot.img or any other fastboot command all it does is say waiting for device and that's it..

usb debugging is on? should be if you see the device with adb devices
try to flash another cwm - like rogue version
if you do that - same error?
./adb reboot bootloader
./fastboot flash recovery recoveryroguecwm.img (change real filename )

well, usb-debugging has no effect whatsoever on fastboot.
personally, I suspect a problem outside of the xoom. Have you installed the current motorola drivers using driverhelper? If not, please do so. Please make sure any firewall or anti-virus-software on your computer is disabled or uninstalled.
If you have the possibility, you should try fastboot with another computer.
btw: I'd try if fastboot works with the command fastboot devices. This should return a list of connected and detected devices.

Thanks! For some odd reason my driver needed to be re=installed. After I did that a restarted my computer everything works as it hasin the past!

Cannot install USB drivers on Windows 10, device not displayed with fastboot devices

When I try to install the USB Drivers It fails with an error message.
ADB devices works, but fastboot devices doesnt.
I'm on Windows 10.

Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).

redpoint73 said:
Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).
Click to expand...
Click to collapse
Yes, I'm trying fastboot from the bootloader screen.
On windows 8.1 it works, I can install the needed drivers, on windows 10 I cannot. Doesn't work. I wonder why adb works but fastboot doesn't.

I had this exact issue up until today, and this what I did to get fastboot on my shield tablet:
1. Uninstall all adb usb drivers just to make sure you start from a clean slate.
2. Then go to Nvidia (https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB) and download their Nvidia shield tablet drivers.
3. While plugged into the computer (have the tablet set to transfer files or mtp) go to the Bootloader menu on your shield tablet and then on your computer go to device manager and update the drivers. For me the device showed up as Fastboot, right click and select update drivers from the folder that you unzipped your nvidia shield tablet drivers to. When I did this I actually got an 'This device cannot start. (Code 10)' error message but I think this is okay because when I looked at the device manager again a new listing had appeared near the top called Android Composite Device.
4. Now go through the exact same process to install the drivers that you did for the 'fastboot' device but now for the 'Android Composite Device', you should also still get the 'This device cannot start. (Code 10)'. After you've done all that reboot the Shield Tablet.
5. Once the tablet has rebooted go to command prompt with Administrator Privledges and type ADB devices and your device should show up, then type adb reboot bootloader and the tablet will reboot into the bootloader menu. I this point I did not select fastboot protocol and I'm not sure if this made a difference, but in any case in the command prompt type Fastboot devices and at least for me this finally worked.
I hope this helps.

Thank you Captain_FSU! :good:
I had the same problem. My Shield K1 was showing up on adb devices but not at fastboot devices. I was unable to update the driver. In Win 10 Device Manager my Shield was showing up at Portable Devices and it was impossible to install the driver there. So finally I am able to unlock bootloader and install TWRP.

Fastboot not working

UPDATE: Problem Solved.
It was the driver problem finally. Tried a whole lot of drivers whole day, but no one worked. Then I found a driver by name clockworkMod, tried that on my device, it worked like a charm.?
I'm trying to unlock my Realme 5 pro bootloader by in depth test.
I'm no expert in all this, but I've turned on Usb debugging & OEM Unlocking.
When powered on, Adb commands work properly, but not fastboot commands,
and when in bootloader, neither adb commands nor fastboot commands work.
I tried 'adb devices' and 'fastboot devices'
command when phone on and in bootloader mode
Tried going in bootloader by in depth app and also by adb reboot bootloader, both worked fine, but after that nothing worked.

So now ur bootloader unlock or not. I think in your laptop adb drivers are not installed.

Obviously not, because device was not detected.
I've tried installing the adb drivers, but it also didn't worked.

Installing GrapheneOS onto Google Pixel 3 - Fastboot Unlock <waiting for device>

Hi guys,
Looking for a genuis here...I've spent the last few days trying to work this puzzle out:
Installing GrapheneOS onto Pixel 3 phone using Windows 10, using command line tools only. Android Studio is not installed on the PC.
Here's what I've done so far...downloaded:
The Pixel image - GrapheneOS stable channel for Pixel 3
ADB & fastboot
First we downloaded fastboot (ADB, Android SDK platform-tools for Windows): https://developer.android.com/studio/releases/platform-tools - had an issue with the fastboot flashing unlock command...it doesnt unlock the device, instead says <waiting for any device>
Then we deleted the SDK platform tool and installed Minimal ADB & Fastboot and the same darn issue happened - the fastboot flashing unlock command doesnt unlock the device... command prompt says <waiting for any device>
The device is carrier unlocked, OEM unlocking enabled, USB debugging enabled, File transfer (MTP) mode on.
The following commands work with the SDK platform-tools & minimal ADB & Fastboot: adb devices, adb reboot bootloader
The block is the command: fastboot flashing unlock as we keep getting <waiting for device>.
Tried to fix this myself, here's what has been tried so far (not necessarily in this order):
Checked Fastboot version... fastboot --version works for both downloads so it's recognising it! Wahoo.
Used command prompt & powershell - when it gets to the fastboot flashing unlock command the response is always <waiting for device>
Checked the PATH (in control panel / advanced setting) and made sure environmental variable goes to the right folder
Downloaded Google USB Driver - nothing changed, we already had up-to-date drivers
Tried to change the fastboot script, click to open the fastboot file, when I click "open" the command prompt pops up, red error message flashes then the command prompt window closes in the blink of an eye. I then turned off Windows secuirty setting for app, same thing still happens.
Tried all USB ports with USB-C cable - same error <waiting for device>
Tried all USB ports with anotehr USB-C cable - same error <waiting for device>
Please help!

The ‘waiting for device’ is generated by Fastboot on PC when it can’t detect your device / can't communicate with phone's bootloader.
If the matching "Android USB Driver" got installed on PC, if latest Fastboot driver got installed on PC, too, and if you have rebooted PC afterwards at least once, then Fastboot should work if USB-cable that came with phone is used.
Hint: Try a different USB port on PC.

jwoegerbauer said:
The ‘waiting for device’ is generated by Fastboot on PC when it can’t detect your device / can't communicate with phone's bootloader.
If the matching "Android USB Driver" got installed on PC, if latest Fastboot driver got installed on PC, too, and if you have rebooted PC afterwards at least once, then Fastboot should work if USB-cable that came with phone is used.
Hint: Try a different USB port on PC.
Click to expand...
Click to collapse
Thansk so much for your reply! I have a few questions though...
I think it can communicate with the device as "adb reboot bootloader" turn the phone off and puts it into fastboot mode?
What is a macthing Android USB Driver? In Device Manager the pixel 3 appears under "portable devices" so I assume that means we have a driver for the device?
Thanks again!

Redsquirrel77 said:
Thansk so much for your reply! I have a few questions though...
I think it can communicate with the device as "adb reboot bootloader" turn the phone off and puts it into fastboot mode?
What is a macthing Android USB Driver? In Device Manager the pixel 3 appears under "portable devices" so I assume that means we have a driver for the device?
Thanks again!
Click to expand...
Click to collapse
Whether phone got booted into fastboot / bootloader mode via command
Code:
adb reboot bootloader
or not can only get verified by command
Code:
fastboot devices
Your Google Pixel device is based on Qualcomm SDM845 Snapdragon 845 chipset, hence the "Android USB Driver" I mentioned must match this chipset.
Download Qualcomm HS-USB QDLoader 9008 Driver (2022)
Want to connect your Qualcomm powered phone to computer? Here you can download Qualcomm HS-USB QDLoader 9008 Driver with installation guide.
www.ytechb.com

jwoegerbauer said:
Whether phone got booted into fastboot / bootloader mode via command
Code:
adb reboot bootloader
or not can only get verified by command
Code:
fastboot devices
Your Google Pixel device is based on Qualcomm SDM845 Snapdragon 845 chipset, hence the "Android USB Driver" I mentioned must match this chipset.
Download Qualcomm HS-USB QDLoader 9008 Driver (2022)
Want to connect your Qualcomm powered phone to computer? Here you can download Qualcomm HS-USB QDLoader 9008 Driver with installation guide.
www.ytechb.com
Click to expand...
Click to collapse
Thanks so much, I think we are getting closer to success!
Qualcomm USB driver downloaded and successfully installed.
Update since the Qualcomm USB driver download:
adb reboot bootloader command works - phone goes into fastboot mode
fastboot devices - no response (new command line)
fastboot - -version shows version and installation
fastboot flashing unlock response is still <waiting for any device>
Used command adb shell getprop ro.boot.cid and response is 00000000
Response should be 11111111 if it's a Google phone...is this my issue? Or does it help explain why fastboot isn't working?

Fastboot operates on device's bootloader only if unlocking bootloader isn't denied. Makes sense,, doesn't it?
Me and all my friends always test this by running
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported" <- on some devices: adb shell "getprop sys.oem_unlock_allowed"
If returned value is 1 - or true, then it's supported otherwise it's not.

Hi,
I don't know if it will help but try this.
PROBLEM
I tried all manner of ADB drivers and fastboot drivers for the last 4 hours just so that I am able to oem unlock this OnePlus device.
I have all OnePlus drivers installed. I have the ADB drivers installed from here. With all these I was able to run adb commands on the phone when it was on including commanding the phone to enter into EDL mode, commanding the phone to reboot into bootloader (fastboot mode). However in once in Fastboot mode, I could not communicate with phone and all I got was "waiting for device".
SOLUTION THAT WORKED FOR ME
It could be a computer brand model. Turns out the problem was not Windows. The problem was not Oneplus. The problem was my Lenovo Thinkpad which apparently requires its own Lenovo USB drivers.
If at all you're on Lenovo machine and you're stuck on "waiting for device" in Fastboot mode despite trying everything, then try installing Lenovo USB Drivers. I would recommend installing the generic ADB drivers first from here. Then installing the Lenovo drivers that are specific to you machine from here. Mine is Thinkpad.
I really hope this helps if not you, then someone else just about to pull their hair out.

[Q] Adb devices command don't work while in fastboot and EDL mode

I have access to fastboot and EDL mode. Does this mean that I can also access the mode that will show the phone after the adb devices command?

If device gets booted into FASTBOOT or EDL mode then it can't additionally get accessed via ADB: this can only get achieved when device got booted into RECOVERY mode.
To clarify:
ADB ( short for Android Debug Bridge ) deals - as its name implies - with a device's Android OS.
FASTBOOT deals - as its name implies - with device's bootloader, if that isn't bricked.
EDL ( short for Emergency Download Mode ) - specific to devices with a Qualcomm Snapdragon chipset - deals with the device itself, is used if bootloader is bricked.

Thank you for your quick help. Is it possible to access adb during bootloop?
I entered something called recovery mode, but the computer doesn't recognize that any device has been connected - adb devices doesn't see anything either.
On one of the pages I read this information:
Spoiler
Ed Reynolds says:
December 2, 2018 at 4:31 am
Unfortunately, there really is no “recovery” per set, yet. There is a mode where one can factory reset the phone which can be reached using the hardware buttons. However, from there, you cannot do anything other than reboot to a simpler form of phone. There are no options to go into bootloader or Fastboot mode. ADB won’t get you there. Sometimes, using ADB, you can boot into a simple android recovery with no command! There you remain until hard booting back it back into full functionality. Developer is apparently working on it
Reply
Deepak Gupta says:
December 2, 2018 at 4:38 am
Hi Ed Reynolds,
Thanks for sharing your knowledge. We appreciate your efforts. Yes, stock recovery doesn’t offer many options. One has to install a custom recovery like TWRP to get over this problem and to maximize productivity.
Reply
Ed Reynolds says:
December 8, 2018 at 7:48 pm
That is correct. but, in order to install a custom recovery, one must be able to get into bootloader, in some way. Either through physical buttons or through the ADB tool. forget about using the physical buttons – they get you to the recovery that you mention, but cannot get you into Fastboot (bootloader) mode. If you use the ADB tools while in this particular recovery mode, and try to reboot into bootloader mode from there, it boots back into the system. So, using that route, you cannot ever get to a place where you can install TWRP or anything else, for that matter – including applying an unlocking code if one were available. Next, if you try to get into recovery mode using the ADB tools (not the physical buttons, you do arrive at a more “conventional” recovery — with the picture of the little Android symbol, etc. However, there are no commands to use to get into Fastboot or bootloader mode. I have had this problem before and sometimes, using the physical buttons, you can reveal commands at this stage. However, even here, no combination of physical buttons reveals any commands. Then, as a last ditch effort, you use the ADB tools to boot into bootloader mode, you return to the system! The result is, again, you cannot install any sort of custom recovery because there is no internal or external way to flash it. If you have overcome this problem, please share! It is very frustrating! Thanks. Ed
Does this mean that I will need to flash custom recovery to gain access via adb during bootloop?

Android's Recovery is nothing else than a minimalistic working Android OS, comparable to Windows Recovery Environment ( WinRE ), so it's accessible via ADB.
A Custom Recovery ( like TWRP ) isn't needed at all, because such a only is an UI version operable by touches.

So if Windows don't see device when is in recovery mode (but recognize correctly when is in fastboot mode), there is a problem with drivers?
I want to access to adb pull for backup. Device is rooted with unlocked bootloader and allowed USB debugging and no PIN password, but bootlooped after trying to restart after uninstalling YouTube app

OMG
when in Recovery mode then you've to connect device via USB-cable with computer and you can launch adb pull command on computer.

When I in recevery mode, computer not recognize it - adb commands not working, device manager don't see any device. When I on fastboot or EDL, computer recognize phone, commands working and device manager shows device on list

Then obviously USB Debugging didn't get enabled in Android's Developer Options.

Robert997 said:
When I in recevery mode, computer not recognize it - adb commands not working, device manager don't see any device. When I on fastboot or EDL, computer recognize phone, commands working and device manager shows device on list
Click to expand...
Click to collapse
As the other user said, USB Debugging is not enabled or proper drivers are not installed. The drivers for fastboot and adb are different. Search for correct drivers, disable driver signing in Windows and install the drivers.