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!
Related
I cant seem to ADB from the bootloader. It works fine when the Xoom is on but when i enter "adb reboot bootloader" it reboots in to boot loader and stops working.
I have the necessary drivers as its showing "Mot Single ADB Interface" under device manager.
When i enter adb devices its saying "list of devices attached" but there is no device under it.
When i enter "adb get-state" it comes back with "UNKNOWN"
Please help
When you say that it stops working, are you trying to enter other ADB commands or are you using fastboot? I've just tried all of the same commands as you have entered and I get the exact same results. It seems to me (and I'm by no means an expert in adb having just learnt the basics so far) that in bootloader the standard ADB commands do not work. Once in bootloader it seems that you need to use the fastboot commands to flash an img file.
Also, in bootloader mode the xoom is no longer recognised by the pc, just press vol up + popwer and it should reboot, or I guess you could also enter fastboot reboot to do the same thing.
Should I be able to find my adb device while my phone is only booting to HBOOT 0.93.0001?
Been stuck on this for days...and it's killing me!
PS. When I plug my phone in to
PC it says "Android ADB interface installed" "Ready to use"
But when I cmd the adb to find devices "adb devices" it shows blank
Use "fastboot" to connect to phone booted into HBOOT
When your phone is in HBOOT then it only accepts commands from the application "fastboot".
It also handles fastboot commands different depending if you are in Fastboot or Bootloader mode.
Search XDA for fastboot for your operating system.
A Windows system might recognize your phone as"adb device" as fastboot uses the same drivers as adb. However, your phone has another USB id and so the command adb will not find it.
Best regards,
Catherall
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
Hi,
I'm trying to boot a twrp image on my Motorola One Vision without flashing it or rooting the phone.
I've unlocked the boot loader and enabled developer options and set USB to debugging. When I connect the phone to the computer and use ./adb devices it is detected fine. When I disconnect, reboot and enable fastboot and when the menu is up connect it to the computer again it will not detect the phone. ./adb devices give no output and ./fastboot boot /PATH/TO/IMAGE.FILE just gives the output "waiting for device". I've tried from both my windows partition and Linux Debian with the same result. Cables are fine as I can use adb to pull files and such- It's basically in the fastboot menu that it doesn't seeem to respond.
The phone is running Android 10 Kane 4.14. I've tried twrp 3.4 but I don't think the image is the issue since it won't respond to commands in fastboot.
Does anyone have any suggestions for troubleshooting this? Any and all help is appreciated.
Kind regards
Magnus
Cardinal_Vice said:
Hi,
I'm trying to boot a twrp image on my Motorola One Vision without flashing it or rooting the phone.
I've unlocked the boot loader and enabled developer options and set USB to debugging. When I connect the phone to the computer and use ./adb devices it is detected fine. When I disconnect, reboot and enable fastboot and when the menu is up connect it to the computer again it will not detect the phone. ./adb devices give no output and ./fastboot boot /PATH/TO/IMAGE.FILE just gives the output "waiting for device". I've tried from both my windows partition and Linux Debian with the same result. Cables are fine as I can use adb to pull files and such- It's basically in the fastboot menu that it doesn't seeem to respond.
The phone is running Android 10 Kane 4.14. I've tried twrp 3.4 but I don't think the image is the issue since it won't respond to commands in fastboot.
Does anyone have any suggestions for troubleshooting this? Any and all help is appreciated.
Kind regards
Magnus
Click to expand...
Click to collapse
If ur phone is detected by adb don't disconnect and hit adb reboot bootloader, it worked for me than when ur in bootloader type:
fastboot flash vbmeta vbmeta_patch.img
fastboot erase userdata
fastboot erase cache (not necessary)
and boot to recovery
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!