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

[Q] PC won't recognise phone, but Moto Tool will

I need to restore to stock firmware to get Lollipop, but adb won't recognise my phone in cmd, thus I can't follow this guide: http://forum.xda-developers.com/showthread.php?t=2542219 . I installed the Motorola Drivers from here: http://forum.xda-developers.com/showthread.php?t=2550635 , and I have the Motorola Device Manager installed. MotoTool picks up my device and is able to boot it into fastboot and install CWM or TWRP, but when I try to flash stock recovery using MotoTool it either gives me a 'no command' screen or doesn't work at all. Anyone having the same problem/know how to fix this? I'm on the Moto G 2013 XT1032 British retail.
EDIT: I fixed it! I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/show...3#post54872143 then used Moto Tool to flash it, as that recognised my phone. I could then download the OTA as normal and installed it like a regular update. Enjoying Lollipop!

If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.

Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?

audit13 said:
If the phone is in fastboot mode, try using fastboot commands on your computer. At the command prompt, type fastboot devices to see of your phone's serial # appears.
Click to expand...
Click to collapse
SammyP6 said:
Do you have USB debugging enabled in settings?
Are you opening cmd in the directory where fastboot and adb were installed?
Are you sure you installed adb and fastboot correctly?
Click to expand...
Click to collapse
Yes to both of these, I was in fastboot and 'adb devices' came back with nothing even though I was in the directory where adb and fastboot were installed and the phone had USB debugging enabled. I fixed it a different way though, I replaced Moto Tool's stock recovery with the one that was included in here: http://forum.xda-developers.com/showthread.php?p=54872143#post54872143 then used Moto Tool to flash it as that recognised my phone. I could then download the OTA as normal and installed it like a regular update.

Adb commands won't work when the phone is in fastboot mode from what I have seen.

audit13 said:
Adb commands won't work when the phone is in fastboot mode from what I have seen.
Click to expand...
Click to collapse
They didn't work at all, no matter what mode I was in. All sorted now though.

Fithboy said:
They didn't work at all, no matter what mode I was in. All sorted now though.
Click to expand...
Click to collapse
It's great you that got the issue sorted out.
Post your solution in case it may help other users down the road. Thanks.

Brick after try to unlock bootloader

I was following this tutorial
https://forum.xda-developers.com/showthread.php?t=3859565
And my phone ended like this, It seems to be something with the screen
https://imgur.com/a/qY2PGjn
The only different step I made was install usb drivers for windows manually
I still enter to fastboot and when I type fastboot devices in the adb command shell it appers
Please help

Can't unlock oem bootloader on Oneplus 6 (Fixed)

Hey guys, as stated in the title i am unable to unlock my bootloader. The adb devices works up to the point where i boot into fastboot or recovery then it stops working. If i use the command it just says "waiting for any device" I want to install TWRP and change to LineageOS but the bootloader is bottlenecking me hard... any tips would be much appreciated!

Run
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
If this doesn't fix your issue then on Windows PC install the "Android USB Driver" suitable for the phone provided by OEM / Carrier.

jwoegerbauer said:
Run
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot devices
If this doesn't fix your issue then on Windows PC install the "Android USB Driver" suitable for the phone provided by OEM / Carrier.
Click to expand...
Click to collapse
Thank you for your response, found the problem. It was the Qualcom drivers not being signed so after i put test mode on on PC it worked. Thanks for the advice!