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!

[Q] LG P500 stuck in fastboot - "waiting for device"

Hello.
Earlier today I wanted to try a new JB rom to replace ICS so I transfered it into SD card and tried to reboot into recovery.
Instead of getting to recovery, I got stuck in fastboot mode, so I'm assuming recovery has been damaged.
After a whole afternoon of researching this forum I tried for several times this tutorial in order to install a recovery and afterwards a ROM (http://forum.xda-developers.com/showthread.php?t=1088046) and similar ones in both Mac OS X and Windows 7 (tried both USB 2.0 and USB 3.0 so its not a problem from USB) and I didn't succeed at all.
When I am using Windows 7, when I use "fastboot erase recovery", I keep receiving this message "waiting device". If I write "fastboot devices", I don't get results.
When using Mac OS X, I can get via command line to the folder "platform-tools" where fastboot is located but if I write "fastboot erase recovery" or something, it says "command not found". I've read it could be because I have to set fastboot as an environmental variable, but I having trouble setting it (Mac OS Lion).
Thank you so much for reading. Please help me!!! Any clues would be really appreciated!
-----
UPDATE: I finally managed to communicate with the device.
I used the following commands from this tutorial http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode-2.html
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery
The problem is, now I'm stuck at LG Logo, can't access fastboot... Please help, I think it's even worse now.

boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566

grigtm said:
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
Click to expand...
Click to collapse
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...

techdani said:
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
Click to expand...
Click to collapse
ok, read here http://forum.xda-developers.com/showthread.php?t=1088046 do exactly what says in this thread

[Q] Wiped everything, can't get ADB to see my device anymore

Hi everyone, this is the first time i write here. I've been dealing with this problem for some hours now and it seems i can't get out of it alone.
Today i decided to wipe the N5 and install Lollipop. I downloaded the factory image, wiped everything from TWRP (i know it was unnecessary...), started to flash all the stuff from ADB...but i got some error. I tried again, and got the same error again. So i started to mess around...a guide told me to give adb the following commands:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
I think it was after this that ADB stopped recognizing my phone, and now i can't even get to the recovery. I tried uninstalling and reinstalling sdk and google usb drivers plenty of times, i even tried some alternative solutions like LGUnitedMobileDriver and Universal Naked Driver.
I can see that windows sees the device (which now only works in fastboot mode) from Device Manager, and that ADB is working (if i give the command "adb version" it responds correctly), but there's no way to make adb recognize the Nexus. If i just install the drivers, Device Manager shows it as "Android Bootloader Interface". A guide i found says to manually select "Android ADB Interface" or "Android Composite ADB Interface", and so i have done (i have to untick the "show compatible hardware" box in the installation process to see this options), but no luck.
Does anybody have any idea how to solve this? What may i have missed?

You need fastboot commands to flash images in recovery. ADB will only recognize the device when you have android running
Try "fastboot devices" command without quotes. It should detect your phone and return a serial number. If so, flash the images (see the sticky on how to return to stock and follow the method 2)

Adb and fastboot are two different things. ASB works in android or recovery but is not used for flashing. Fastboot works in bootloader.
I wrote an "adb and fastboot" thread. Use it uninstall your Google drivers and install naked.

Omg, it was that simple! Thank you guys, you were so fast :good:

If you downloaded the factory image, it seems like you just need to flash that with fastboot.
1). Reboot into the boot loader by holding down volume when powering on.
2). Type fastboot devices to make sure your phone is recognized.
3). Untar the image and execute the flash-all.bat script. This will completely factory reset your phone, including stock recovery. Note this will also delete your internal storage files.
If you don't like this approach, you can also flash the recovery partition with fastboot flash recovery recovery.img, where recovery.img is the TWRP image you downloaded. Once you boot into recovery you can restore a nandroid or whatever from there. Good luck.
Sent from my Nexus 5 using Tapatalk

Device isn't detected by computer after fastboot boot image

I was trying to follow the advice here: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 but I must have missed a step, and now I can't even fastboot anything.
Previous Status:
I could run
Code:
adb devices
and
Code:
fastboot devices
fine. My computer was able to detect my OPO. When I
Code:
fastboot oem device-info
it says my phone is tampered with, and unlockedied.
What I did:
I rebooted my phone to fastboot mode by turning it off, then holding volume down + power button. It went into a menu, in which I selected reboot into fastboot mode.
Once in fastboot mode, and connected to my computer,
Code:
fastboot devices
shows my device. Then I ran
Code:
fastboot boot twrp-3.0.2-0-bacon.img
(the img was downloaded from https://dl.twrp.me/bacon/) which at this point I assumed was a mistake. My terminal said it was successful, but then running
Code:
fastboot devices
shows nothing.
Current Status:
Even in fastboot mode, my device is not detected. Booting up normally is successful, and I can access my files and apps. When booted up normally, running
Code:
adb devices
detects nothing. In fact, MTP and other USB connections has no affect on the OPO. The OPO would indicate that it is charging, but not indicating that it is actually connected to a computer.
My Conclusion:
Running
Code:
fastboot boot twrp-3.0.2-0-bacon.img
messed up my device in which it wouldn't communicate with my computer anymore. I don't know how to fix that though. In fact, I don't even know if that was the case, and I don't know how to fix this at all. Any help would be appreciate.

joeyism said:
I was trying to follow the advice here: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 but I must have missed a step, and now I can't even fastboot anything.
Previous Status:
I could run
Code:
adb devices
and
Code:
fastboot devices
fine. My computer was able to detect my OPO. When I
Code:
fastboot oem device-info
it says my phone is tampered with, and unlockedied.
What I did:
I rebooted my phone to fastboot mode by turning it off, then holding volume down + power button. It went into a menu, in which I selected reboot into fastboot mode.
Once in fastboot mode, and connected to my computer,
Code:
fastboot devices
shows my device. Then I ran
Code:
fastboot boot twrp-3.0.2-0-bacon.img
(the img was downloaded from https://dl.twrp.me/bacon/) which at this point I assumed was a mistake. My terminal said it was successful, but then running
Code:
fastboot devices
shows nothing.
Current Status:
Even in fastboot mode, my device is not detected. Booting up normally is successful, and I can access my files and apps. When booted up normally, running
Code:
adb devices
detects nothing. In fact, MTP and other USB connections has no affect on the OPO. The OPO would indicate that it is charging, but not indicating that it is actually connected to a computer.
My Conclusion:
Running
Code:
fastboot boot twrp-3.0.2-0-bacon.img
messed up my device in which it wouldn't communicate with my computer anymore. I don't know how to fix that though. In fact, I don't even know if that was the case, and I don't know how to fix this at all. Any help would be appreciate.
Click to expand...
Click to collapse
Why were you booting TWRP? Were you trying to flash it? Normally its
fastboot flash recovery twrp-3.0.2-0-bacon.img
Sent from my A0001 using Tapatalk

Renosh said:
Why were you booting TWRP? Were you trying to flash it? Normally its
fastboot flash recovery twrp-3.0.2-0-bacon.img
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yea I was trying to flash it, but I read from http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 that another trick is to do
Code:
fastboot boot <path/name of the recovery twrp img>
So I thought I'd try it. But now my computer can't even detect my phone :/ Would there be a reason why my phone no longer communicates with my computer?

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!