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!

Nexus 5 doesn't recognize computer while in fastboot

I'm trying to flash TWRP on a nexus 5. Bootloader is already unlocked. USB debugging is enabled. The command "adb reboot-bootloader" works when the device is on. While in fastboot it does not say USB is connected and doesn't show up on adb devices. (My laptop is currently running Elementary OS)

As soon as you're in bootloader mode you have to use 'fastboot flash recovery recovery.img' adb is used when the device is powered on and in debugging mode - but it's not the right command for flashing [emoji14]

experience7 said:
As soon as you're in bootloader mode you have to use 'fastboot flash recovery recovery.img' adb is used when the device is powered on and in debugging mode - but it's not the right command for flashing [emoji14]
Click to expand...
Click to collapse
Yeah I know HOW to flash a recovery I already tried that exact command. Thanks for the suggestion though. The problem is that it just doesn't know its there.
Sent from my HTC One using XDA Free mobile app

While in bootloader mode (not recovery!) connect your phone and try "fastboot devices". What does it show? Post a screenshot of your command prompt.

Sorry its my friend's phone so I don't have it with me. I will have to get back to you on that

1. USB Debugging ONLY applies to ADB while booted into Android, NOT the bootloader or recovery
2. ADB is only used within Android (with USB Debugging enabled) and recovery, NOT the bootloader
3. Fastboot is whats used while in the bootloader, not ADB (use fastboot devices, not adb devices)
4. Some people find you may need to use 'sudo' for fastboot commands

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.

download mode - device not seen in adb or fastboot

Hi
I did terrible mistake when updating to LineageOS 18.1. Just after flashing, it asked me if I want to switch TWRP 3.4 to LineageOS recovery, and I clicked yes... Now OS is not starting, phone is booting to LineageOS recovery instead. Error log is filled with
"failed to mount /cache: no such file or directory".
This recovery lacks of option to flash using img or zip, there is only "adb sideload" option. Problem is, that phone is not discoverable via adb anymore.
But putting LineageOS recovery away, fourtunately I can boot phone into download mode. It appears in device manager (I am using windows 10), but correct driver can not be found. In consequence, "adb devices" or "fastboot devices" shows nothing. Do you know, if there is an option to install windows 10 driver for u11 and flash TWRP again ?
I would appriciate any help

In case of anyone having similar issue as me, I was able to solve it using @Aldo101t link. Thanks!
Fastboot Not Recognizing My U11
Trying to unlock the bootloader on my HTC U11, but fastboot isn't recognizing the device (fastboot devices returns no serial number and fastboot oem get_identifier_token doesn't work) I have tried Minimal ADB and Fastboot, ADB and Fastboot...
forum.xda-developers.com

orestlenczyk said:
In case of anyone having similar issue as me, I was able to solve it using @Aldo101t link. Thanks!
Fastboot Not Recognizing My U11
Trying to unlock the bootloader on my HTC U11, but fastboot isn't recognizing the device (fastboot devices returns no serial number and fastboot oem get_identifier_token doesn't work) I have tried Minimal ADB and Fastboot, ADB and Fastboot...
forum.xda-developers.com
i am having the same issue, how did you flash twrp again? No matter what i do, I can't replace LOS recovery
Click to expand...
Click to collapse

Can't unlock bootloader Moto C XT1756

Hey! I need help, please. I'm trying to unlock bootloader of the Moto C XT1756, it has a MT6735. So, I tried in Windows and in Linux (linux with 2 pc). And the problem is next.
I installed ADB and Fastboot (I tried minimal, 15 seconds, platfoorm tools, all). So, ADB detects the device, I can use any adb command like the "adb reboot bootloader". It reboot in fastboot mode and if I use "fastboot devices" it is detected. But when i'm trying to use "fastboot oem get_unlock_data" it says me "failed, unknown command." It happen also with any oem command. I don't know how to proceed. If someone can help me, i'll be grateful. Thanks for read

Both ADB and Fastboot aren't equally implemented by manufacturers: the ADB & Fastboot what you have installed is correct for Google devices only.

Oh. So, I'll test your ADB-FASTBOOT installer, really thanks!

Hey! I don't understand, I need to use your ADB-FASTBOOT installer? I tried now and it doesn't work. The error is the same.

jwoegerbauer said:
Both ADB and Fastboot aren't equally implemented by manufacturers: the ADB & Fastboot what you have installed is correct for Google devices only.
Click to expand...
Click to collapse
Hey! I don't understand, I need to use your ADB-FASTBOOT installer? I tried now and it doesn't work. The error is the same.

I see you didn't get it.
Manufacturers implement ADB and/or Fastboot with version what corresponds to their ideas.
Hence in your case some ADB and/or Fastboot commands may work or not.

Oh. So, this phone can't be unlocked?

Use ADB / Fastboot as provided by Motorola - see attachment
Use Motorola's "Android USB Driver"

jwoegerbauer said:
Use ADB / Fastboot as provided by Motorola - see attachment
Use Motorola's "Android USB Driver"
Click to expand...
Click to collapse
I didn't get the second sentence. "Use Motorola's "Android USB Driver". Btw, I used "mfastboot.exe devices" and it recognizes my phone, then "mfastboot.exe oem get_unlock_data" and it keeps saying "failed: unknown command."

Update: I tried three different wires. Three different PC (Including Linux-PC) and the error is the same. I can't understand it. It have an option "Unlock OEM" in Developer Settings (so, I think that the manufacturer allows unlock) I can't do nothing.