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!
Hello. Im trying to unlock bootloader on my wifes phone. All adb commands works. After I type adb reboot bootloader phone goes to fastboot mode and thats ok. But after I type fastboot devices nothing is happening. How can I fix it?
Gedablo666 said:
Hello. Im trying to unlock bootloader on my wifes phone. All adb commands works. After I type adb reboot bootloader phone goes to fastboot mode and thats ok. But after I type fastboot devices nothing is happening. How can I fix it?
Click to expand...
Click to collapse
it is a problem of s1 boot device driver . i even tried diabling driver signature on my win10 like every post suggested but no luck . i'm also trying to get over it
disable driver signature in win 10 and when windows boots go to device manager and update driver of s1 boot device from the files of given link
https://dl.xda-developers.com/4/0/0....zip?key=oeHhoI_uttjO0gP6y4vAiA&ts=1526629864
Hello, today I finally received my one plus 6. Been loving the device so far
I was on my way to Chuck a custom recovery and rom unlocked the bootloader no drama
I then hit a Plato of fastboot coming up with no command error as in fastboot isn't working in cmd I have researched heaps about it and I can not find a single thing. I tried to reinstall drivers and all that, and yes I'm running cmd in the fastboot files, only adb seems to be working but I can no longer use fastboot on my PC.
Has anyone come across this error, it seems to be that after installing the one plus drivers it stopped working correctly and fastboot commands no longer register in fastboot...
My phone is detected in fastboot mode so it's not the drivers. What could be causing this, is it the computer at fault?
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
cass89 said:
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
Click to expand...
Click to collapse
I had the same issue with my op9 unlocking bl.
ADB and Fastboot 29.0.2.zip | by evildog1 for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Use these and open your command window from this . Makes a shortcut on your desktop. I did and unlocking bl worked perfectly.
cass89 said:
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
Click to expand...
Click to collapse
Double post
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
cass89 said:
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
Click to expand...
Click to collapse
Make sure you enable oem unlocking in dev options first and reboot.Reboot to bootloader,issue command $fastboot flashing unlock..
cass89 said:
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
Click to expand...
Click to collapse
Are you a carrier variant or global unlocked 9/9pro?
OEM unlocking is enabled, reboot to bootloader, command 'fastboot devices' shows no devices
Still have unknown android device in device manager
It's a global unlocked 9
cass89 said:
OEM unlocking is enabled, reboot to bootloader, command 'fastboot devices' shows no devices
Still have unknown android device in device manager
It's a global unlocked 9
Click to expand...
Click to collapse
Did you create a shortcut to those adb driver's when you installed; on desktop. And open cmd window in that spot. ?
mattie_49 said:
Did you create a shortcut to those adb driver's when you installed; on desktop. And open cmd window in that spot. ?
Click to expand...
Click to collapse
I'm not sure what you mean by shortcut
I unzipped the file to my desktop, then tried installing driver through device manager, but no driver was found.. I then tried installing the driver with the "DPInst_x64.exe" file, but it says install failed with no other explanation
I tried just opening a command prompt in that folder, but with no driver installed, it still isn't recognized
Thanks for helping, I'm lost at this point lol
cass89 said:
I'm not sure what you mean by shortcut
I unzipped the file to my desktop, then tried installing driver through device manager, but no driver was found.. I then tried installing the driver with the "DPInst_x64.exe" file, but it says install failed with no other explanation
I tried just opening a command prompt in that folder, but with no driver installed, it still isn't recognized
Thanks for helping, I'm lost at this point lol
minimal_adb_fastboot_v1.4.3_setup.exe | by shimp208 for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Try one more thing. Install these and creat shortcut on desktop and try opening cmd in this. We gonna get you unlocked.
One last thing. You have also went into developer options and tic'ed "USB debugging on then ok on device when it asks if you wanna allow phone to communicate.
tried that, still nothing. usb debugging is on.
all I need is a working driver, everything else should be good..
one thing which i'm not sure if it's an issue, I'm using an old usb c to usb 2 cable, I'm not using the cable that came with the phone because my computer doesn't have usb c ports.. but adb and mass storage/file transfers work with no issue
Hate to say it, but it still COULD be your old USB cord even with file transfer and adb functionality preserved. I had a cord that did do file transfer but not adb. You should try another cord...
Here's another driver source to download:
Universal ADB Drivers
2 new cords, and also tried multiple driver downloads, but still nothing... i was really hoping to root this phone and it seemed so easy for everyone else, thats why i bought it.. but I guess I'm stuck with a locked bootloader...
I could try factory resetting windows or the phone, but would that even make a difference?
..rereading the root guide, at the beginning it says "if you're on global and want root, flash the eu boot.img" but I'm not sure if he means do that first or use that for the guide.. I'm assuming I need the bootloader unlocked in order to flash it first, but maybe not..
..also should I have just commented in the root guide post, instead of making a new post?..
I'm sure you've tried another usb port on your computer.
Last thing to try: another PC.
Shouldn't come to that, but that's where you look to be.
Got it!! Someone posted about the op6 not working either and the fix is turning off windows driver signature, not sure why but that worked for me..
Thanks, now on to root lol
I just had some serious fastboot driver issues when setting up my oneplus. Not sure if this helps but can you at least find the driver folder that was installed on your c:drive when you initially installed the drivers. Then check your device manager when your phone is in fastboot and update the device (usually under portable devices) through that path?
If you get a tampering /corrupt error when you do this you can disable driver signing in windows which is what worked for me thanks to this saint.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Edit: you solved it while I was responding....I had the same issue..congrats...I know the feeling!
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.