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.
Related
[Q] Stuck in "Starting Fastboot Protocol Support" when trying to flash stock images
When i punch in adb reboot bootloader i get starting fastboot protocol support, i used the rootmyxoom procedure which does unlock my bootloader.
im using this method:
http://forum.xda-developers.com/showthread.php?t=1075260
Please Email me with responses, [email protected]
philski421 said:
When i punch in adb reboot bootloader i get starting fastboot protocol support, i used the rootmyxoom procedure which does unlock my bootloader.
im using this method:
http://forum.xda-developers.com/showthread.php?t=1075260
Please Email me with responses, [email protected]
Click to expand...
Click to collapse
I don't understand, when you type in adb reboot bootloader you should get fastboot...whats the problem.
bwcorvus said:
I don't understand, when you type in adb reboot bootloader you should get fastboot...whats the problem.
Click to expand...
Click to collapse
thats where I have no clue what hell is going on, if I type in flash blah blah it says waiting for device
i have the same issue, I'm I reboot via adb and then my xoom reboots and says starting fasboot protocol support and just sits there. Any help or idea why?
answered my own question. This is because my device has not been unlocked yet.
I had to do the fastboot oem unlock found here.
http://forum.xda-developers.com/showthread.php?t=967065
Only thing I can suggest is to check to make sure you have your drivers installed and ready for fastboot. I think one of the commands you can throw at it is fastboot devices which should do the samething as adb devices but use for fastboot (but can't remember, been awhile since I've had to do anything with fastboot). If that is an acceptible command then you should see your device listed, if not then your computer isn't seeing the device which is why it's saying waiting for device.
You might also want to try throwing the fastboot oem unlock command again and see what happens (it's possible that you've never actually unlocked the xoom).
This is only a few suggestions I can give you for now as I'm not at home to try throwing some of those commands myself to confirm they're valid commands or not, sorry.
drivers are installed that's how I did the original unlock. and I'm sure I hit accept. I went through the whole process of losing everything when doing so. no dice on being able to flash . and the weird thing is this. when I type in adb reboot bootloader it reboots to the fast boot protocol screen but when I type in the info to flash the recovery I get the error of can't load
I'm having the same problem, I simply can't boot into FASTBOOT. I've got the latest USB drivers, I've updated ADB, but it just won't work. It just sits there telling me "Starting fastboot protocol support".
Very frustrating, nothing I do seems to fix it - I've even done a factory reset.
Edit: Now it won't even respond to "fastboot oem unlock", it just sits there saying "<waiting for device>" even though the device shows fine when I do "adb devices" and the device also shows in Windows. (Is this simply because the device is already unlocked)
Are you sure USB debugging is enabled?
Sent from my GT-I9000 using XDA Premium App
Yep, it is
Edit: By the way, if I do "fastboot devices" nothing is listed. If I do "adb devices" it lists the XOOM just fine.
Edit again: Just noticed that the OP also used the "rootmyxoom" process, which is exactly what I used and I'm having the same issues he's having... hmm.
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!
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 just got this phone, and was told to unlock the bootloader and flash custom recovery as the first step, so I'm following this guide: forums.oneplus.net/threads/full-guide-setting-drivers-up-unlocking-bootloader-flashing-recovery-roms-kernels-rooting.291274/
I've been following it to a T and everything was working well. Once I got up to #3 and type in cmd "fastboot reboot" and it boots back to normal mode (so I can disable Cyanogen Recovery), typing "adb reboot bootloader" in cmd returns "error: device not found." If I'm in fastboot mode and enter "fastboot oem device-info" it returns true for tampered and unlocked so I know I have the bootloader unlocked. If I'm in normal mode, the phone shows up in device manager under portable devices. If I uninstall it, it disappears from the list. Once I unplug it and plug it back in, it pops back up in the same place, saying device installed correctly. If I try to update the drivers, most of the options from the Manufacturer list (see in the gifs from the guide) are gone, including the google ones.
How do I move from here? should I just wipe the whole thing and try again? What's the best way to do that? If I use the the USBDeview thing and remove the A0001 driver, will that allow me to put the android ADB Interface on the phone (Basically starting over)?
Thanks friends. Really excited to get going on Android!
threemor said:
I just got this phone, and was told to unlock the bootloader and flash custom recovery as the first step, so I'm following this guide: forums.oneplus.net/threads/full-guide-setting-drivers-up-unlocking-bootloader-flashing-recovery-roms-kernels-rooting.291274/
I've been following it to a T and everything was working well. Once I got up to #3 and type in cmd "fastboot reboot" and it boots back to normal mode (so I can disable Cyanogen Recovery), typing "adb reboot bootloader" in cmd returns "error: device not found." If I'm in fastboot mode and enter "fastboot oem device-info" it returns true for tampered and unlocked so I know I have the bootloader unlocked. If I'm in normal mode, the phone shows up in device manager under portable devices. If I uninstall it, it disappears from the list. Once I unplug it and plug it back in, it pops back up in the same place, saying device installed correctly. If I try to update the drivers, most of the options from the Manufacturer list (see in the gifs from the guide) are gone, including the google ones.
How do I move from here? should I just wipe the whole thing and try again? What's the best way to do that? If I use the the USBDeview thing and remove the A0001 driver, will that allow me to put the android ADB Interface on the phone (Basically starting over)?
Thanks friends. Really excited to get going on Android!
Click to expand...
Click to collapse
You probably don't have ADB enabled on your OPO, but you don't even need it for this. "adb reboot bootloader" is just a handy way of rebooting to fastboot without shutting down and holding the up volume button while turning it on. Once you get into fastboot by doing that, continue on as the guide says! (i.e. "fastboot flash recovery xxxx.img")
Using Samsung Android 11 default ROM - nothing modified. I'm trying to boot custom recovery (twrp) temporarily from PC console.
What I did to set up adb and fastboot:
OEM unlocked, usb debugging active, not rooted.
I installed latest ADB and Fastboot. Also installed Samsung USB drivers. Samsung doesn't provide fastboot drivers, and I've read on some thread that AOSP drivers are used for that. So, I'm using Google's Bootloader Interface installed via Device Manager, because plenty of guides suggest that online.
Problem:
I can use adb when phone's on. But when it comes to fastboot, I can get into it by 'adb reboot bootloader' and, i can see the device is listed using 'fastboot devices', but i can't really do anything at all other than that command.
I tried 'fastboot oem device-info', 'fastboot boot twrp.img'. I don't get any error messages. When I execute a command, the command just stays there on the terminal like it is busy executing. Waiting for over 15 minutes and there's no change.
Ex: When I executed the boot command, the console output was stuck at 'Sending boot.img', without any progress.
Additional info:
I've got Ryzen CPU, and I applied some USB fix bat to change some registry entries. No change.
All my ports are USB 3 and I'm on Win 10, and I've seen threads where they say USB 2 is preferable.
TLDR: Seemingly nothing's wrong, except no fastboot command really seems to be executing other than the one to list connected devices.
AFAIK Samsung does not know a Fastboot mode, but there is the so-called Odin/Download mode besides the Recovery mode.