Please for the love of god help me. I've tried everything.
I have a developer edition. I have the newest drivers, the newest phone updates. Everything. It is recognized by ADB when I'm on the home screen, but when I am in fastboot mode itself it will not recognize the device. I can't unlock the BL because of this. It's VERY frustrating and I'm about 12 hours from selling this device and buying an HTC M8.
I have Windows 7 64 bit. I'm on the newest moto drivers, the newest FW for the X. I've uninstalled and re-installed and restarted my machine countless times. With no luck. With the drivers installed I booted the phone into fastboot mode, pulled up a command prompt where ADB was installed, ran adb devices and nothing. Over and over again. Please help me. I really want to keep this phone.
Navigate to where fastboot.exe is installed, and run "fastboot devices".
And make sure phone is in bootloader mode.
Does it list serial number?
I ran into the same issue last night, I just got a moto x DE for my wife, and a new laptop since last March when I unlocked my moto x DE. "adb devices" returned nothing, and I had a fresh install of the SDK and the moto drivers. Both old and new laptop on Win 7 64-bit. I googled trying to find a solution, but didn't find anything that worked. Grabbed my old laptop, hooked up to it, and it worked fine.
One suggestion I saw and didn't try was to remove/reload the moto drivers. Since I got it working and got her phone unlocked with my old laptop, I didn't pursue further.
Nitemare15 said:
....With the drivers installed I booted the phone into fastboot mode, pulled up a command prompt where ADB was installed, ran adb devices and nothing. Over and over again. Please help me. I really want to keep this phone.
Click to expand...
Click to collapse
Adb devices wont work when the phone is in Booloader/fastboot mode.
Make sure you have the latest Moto drivers from here -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Follow this -> http://mark.cdmaforums.com/ADB.htm To install The Android SDK, PlatformTools, and mFastboot, and add platform tools to the Path.
once that is done.. type fasboot devices and see if you get anything. If no, look at Device Manager and make sure there are no ! or such in there.
This is what worked for me. Posting here for posterity and potential helpfulness.
yghrv said:
I hit the issue earlier and fixed it with the steps. hope will help you too.
1. connect your phone with computer
2. go to C:\Program Files\Common Files\Motorola Shared\Mobile Drivers\
3. run Motorola Driver Installer.exe, choose clean and Reinstall.
Click to expand...
Click to collapse
31337z3r0 said:
This is what worked for me. Posting here for posterity and potential helpfulness.
Click to expand...
Click to collapse
Even that wouldn't help him if he was trying to use adb while in the bootloader.
KidJoe said:
Adb devices wont work when the phone is in Booloader/fastboot mode.
Make sure you have the latest Moto drivers from here -> https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Follow this -> http://mark.cdmaforums.com/ADB.htm To install The Android SDK, PlatformTools, and mFastboot, and add platform tools to the Path.
once that is done.. type fasboot devices and see if you get anything. If no, look at Device Manager and make sure there are no ! or such in there.
Click to expand...
Click to collapse
Thanks for clarifying. I only end up dealing with rooting something once a year or so and always forget the "ins-outs-and-what-have-yous". Once I was reminded of fastboot vs. adb all was well!
31337z3r0 said:
This is what worked for me. Posting here for posterity and potential helpfulness.
Click to expand...
Click to collapse
Thank you very much, that did the trick for me !
Related
Having a strange problem with my HTC One (m7) where adb works fine and can even reboot to bootloader, but fastboot doesn't see the device.
My HTC One is S-Off and rooted and unlocked. Running Android Revolution HD 31.5 (JB 4.3) and my current recovery is TWRP.
The computer is running Windows 8.1 x64.
I've got the latest Android SDK installed, and can run both adb and fastboot from command prompt with no problem.
I've got the latest HTC Sync manager installed so the drivers should be there as well.
adb works fine, I can issue "adb devices" and it shows my device and serial number and I can do all other things with adb as well (so no issue with USB cable or port either).
I can boot to bootloader with "adb reboot bootoader" and when I'm there it shows "Fastboot USB" so that looks ok as well.
But fastboot doesn't see the device. "fastboot devices" returns nothing.
I've tried searching the forums and googling and everything, but can't find anything. I'm at my wits' end. Any help greatly appreciated.
aryonoco said:
The computer is running Windows 8.1 x64.
Click to expand...
Click to collapse
That is the problem mate
google: fastboot windows 8.1 and you will find your answer im sure.
alray said:
That is the problem mate
google: fastboot windows 8.1 and you will find your answer im sure.
Click to expand...
Click to collapse
You were indeed correct, and I was obviously googling for the wrong thing. I just didn't think the 8.1 update would have broken that...
Anyway, for the record, this guide helped me fix it by replacing Microsoft's USB drivers with Intel's. http://www.droid-now.com/2013/10/fix-working-fastboot-drivers-windows-8-1-x64/
Oh, and thanks to Microsoft for wasting hours of my time with your buggy driver Times like this I really miss my Linux box.
fastboot not returning anything
deleted
I spent a good part of the day reading through all the steps to get my new device (just arrived, 4.4) rooted. I've had several rooted devices before, but always used tools to do it.
Never used adb before, but managed to get the SDK installed and have been playing around with it. That's as far as I got, however.
On my mac, using terminal, I can get adb to see my device (type ./adb devices and it lists it as connected).
When I go through this guide
http://forum.xda-developers.com/showthread.php?t=2446515
to do any fastboot commands, I always get "waiting for device." Previously I got some kind of pipe error. Yes, usb debugging is on.
I think I'm pretty close to getting flashed down to 4.2.2, just can't get the adb to work.
tl;dr - adb gives me "waiting for device" forever. any ideas how to fix?
Thanks very much!
motoxuser said:
I spent a good part of the day reading through all the steps to get my new device (just arrived, 4.4) rooted. I've had several rooted devices before, but always used tools to do it.
Never used adb before, but managed to get the SDK installed and have been playing around with it. That's as far as I got, however.
On my mac, using terminal, I can get adb to see my device (type ./adb devices and it lists it as connected).
When I go through this guide
http://forum.xda-developers.com/showthread.php?t=2446515
to do any fastboot commands, I always get "waiting for device." Previously I got some kind of pipe error. Yes, usb debugging is on.
I think I'm pretty close to getting flashed down to 4.2.2, just can't get the adb to work.
tl;dr - adb gives me "waiting for device" forever. any ideas how to fix?
Thanks very much!
Click to expand...
Click to collapse
if your phone is turned on when it is connected to the computer then you can't run fastboot commands. you can only run adb commands. If your phone is in "fastboot mode" / bootloader screen, then you can run fastboot commands but not adb commands. Not sure this is your issue but based on your info it is my best guess at where you are having problems.
jayboyyyy said:
if your phone is turned on when it is connected to the computer then you can't run fastboot commands. you can only run adb commands. If your phone is in "fastboot mode" / bootloader screen, then you can run fastboot commands but not adb commands. Not sure this is your issue but based on your info it is my best guess at where you are having problems.
Click to expand...
Click to collapse
that sounds about right! thanks!
how do I get the phone into fastboot mode/bootloader screen? or better yet, when i'm doing this whole process, in what mode should the phone be and how do I get it there?
motoxuser said:
that sounds about right! thanks!
how do I get the phone into fastboot mode/bootloader screen? or better yet, when i'm doing this whole process, in what mode should the phone be and how do I get it there?
Click to expand...
Click to collapse
adb reboot bootloader in terminal
you can you my tool kits to help you.
http://forum.xda-developers.com/showthread.php?t=2591875
mjphillips1981 said:
adb reboot bootloader in terminal
you can you my tool kits to help you.
http://forum.xda-developers.com/showthread.php?t=2591875
Click to expand...
Click to collapse
great! I'll do that - actually, I just sent you a PM - i'm trying to work my way through the mac tool now and got stuck. appreciate it!
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
DragonRyderX said:
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
Click to expand...
Click to collapse
Any way you could try it on a Windows 7 machine?
Where did you get your fastboot files? If mofo detects it then your fastboot files are jacked up
Go here: http://dl.google.com/android/android-sdk_r24.3.3-windows.zip
Once you extract it, run SDK Manager, Select to install Android SDK Tools, Platform-Tools.
Once that's done, go to \android-sdk-windows\platform-tools. Hold shift, right click and Open Command Prompt. Then fastboot will work
O
Here's an easy way to install Fastboot/ADB.
Once that is installed you'll have to change your commands to fit the file path of the fastboot files.
For example:
Code:
fastboot flash logo C:\Users\OP\Desktop\logo.bin
[/COLOR]
savagebunny said:
Where did you get your fastboot files? If mofo detects it then your fastboot files are jacked up
Go here: http://dl.google.com/android/android-sdk_r24.3.3-windows.zip
Once you extract it, run SDK Manager, Select to install Android SDK Tools, Platform-Tools.
Once that's done, go to \android-sdk-windows\platform-tools. Hold shift, right click and Open Command Prompt. Then fastboot will work
O
Click to expand...
Click to collapse
DragonRyderX said:
I am not new to flashing phones, but I cannot figure this out. I can run Mofo and Mofoverify, but I cannot run a fastboot commands like "fastboot flash logo logo.bin". All I get is waiting for device. " Adb devices" and "fastboot devices" both return an empty list in there respective modes. Now I have tried several similar but not the same fixes from many Google and XDA searches. I have tried all sort of driver solutions, USB cables, toggleing of settings in my phone and such. I have used Mofo without issue and still can, but fastboot won't let me flash the setup files for Lollipop and I want me some sweetness! I have a newer Windows 8.1 machine and the XT1254. Lastly, this is my first Q&A thread post, so please be gentle. Thank you ahead of time, because this is XDA, and it can solve anything!
Click to expand...
Click to collapse
This minimal version of fastboot is a lot smaller and worked for me.
I have used minimal Adb/fastboot. I don't know if it helps, but when in Android, even after revoking USB debugging authorizations, I never get asked on my phone to re-authorize my pc. As for a Windows 7 machine, I could downgrade my laptop, but I wanted that to be a last resort.
@savage- sorry for posting this on ComputerFreaks thread, but it was his image I am trying to install and figured someone doing the same as me may have had same issue, but I'm sorry.
DragonRyderX said:
I have used minimal Adb/fastboot. I don't know if it helps, but when in Android, even after revoking USB debugging authorizations, I never get asked on my phone to re-authorize my pc. As for a Windows 7 machine, I could downgrade my laptop, but I wanted that to be a last resort.
@savage- sorry for posting this on ComputerFreaks thread, but it was his image I am trying to install and figured someone doing the same as me may have had same issue, but I'm sorry.
Click to expand...
Click to collapse
A windows 7 machine is unnecessary. I used windows 8.1 pro x64 to perform the whole upgrade process without a hitch. If mofo functions correctly, that means the fastboot drivers are installed correctly. If you start up minimal adb/fastboot, plug in your phone while it's in fastboot mode and type "fastboot devices," what do you get?
EDIT: Duh. You already said that it says returns nothing. Well in that case there has to be some sort of problem with the USB connection or the minimal adb/fastboot installation. Maybe try running the minimal adb/fastboot shortcut as administrator. I don't remember having to do that on mine, but who knows?
St33ve- see OP, nothing listed for adb or fastboot devices commands in their respective modes.
Have you tried a different USB cable?
Yonnor said:
Have you tried a different USB cable?
Click to expand...
Click to collapse
Yes, about 7 different ones. 4 that I am sure have worked before, and no physical damage to them.
You said Mofo is able to see your device though, so that's kind of throwing me through a loop. You could try a fresh install of the Minimal ADB, and double check your drivers?
That's a sign of drivers not being installed!
Try opening up device manager n see if the driver is not installed.... If u see a device with an exclamatory mark n "quark" somewhere in it... The drivers aren't installed...
When the phone is in fastboot mode, the phone is listed as quark fastboot, but no exclamation mark. I reflashed computerfreaks image (KK) without an issue, but still isn't recognized in fastboot or Adb. I really want to flash me some Lollipop! I have crack flashed with every phone I own. I'm going thru withdrawals here LOL.
i am having the exact same issues. I've reinstalled drivers, switched usb cords and have had no success.
I'm not certain what actual fixed mine because I tried so many things but I got mine to recognize my phone. I think what did it was revoking the USB debugging authorizations and deleting the adb files on my computer under username/.Android. Then reauthorizing my phone. That and I believe I may have had duplicate drivers interfering with each other. Hope this helps
Hallelujah, I have lollipop!!!
I do not know exactly what the issue was but after factory resetting windows 8.1, and manually loading each driver for adb and fastboot, it works (again). I wish there was a Thank All Button. THANKS ALL!!!
I have used adb and fastboot for a long time, and this is the first time I've had a problem. I updated to the August security update on the first with no problem, and my computer updated to Windows 10 Anniversary 64 bit on the second. I can do "adb reboot bootloader" and it works, but any fastboot command, even "fastboot devices" does nothing.
Windows Device Manager shows an exclamation mark for "Fastboot Shamu S". I have looked for hidden devices and uninstalled the driver. I tried to update the driver but Windows can't find one.
The adb and fastboot drivers I have been using are from December of last year, so I installed these: http://www.teamandroid.com/2016/06/15/install-fastboot-adb-google-usb-drivers-windows/ but still can't get fastboot working.
Has anyone run into this and can suggest a solution?
Same configuration here - Windows 10 Anniversary 64 bit ,shamu, old fastboot files and drivers from Google. Everything is fine.
Try to download official drivers.
JimSmith94 said:
.... and my computer updated to Windows 10 Anniversary 64 bit on the second. I can do "adb reboot bootloader" and it works, but any fastboot command, even "fastboot devices" does nothing.
Has anyone run into this and can suggest a solution?
Click to expand...
Click to collapse
The W10 anniversary update doesn't accept drivers that aren't certified by Microsoft.
When there are no certified fastboot drivers you may thank Microsoft.
If it's a driver issue, uninstall then follow this http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Then reinstall after disabling the driver signature verification
bultras said:
Same configuration here - Windows 10 Anniversary 64 bit ,shamu, old fastboot files and drivers from Google. Everything is fine.
Try to download official drivers.
Click to expand...
Click to collapse
Thanks to all! Installing the driver from "latest_usb_driver_windows.zip" in your link did the trick!
Works fine for me.
Sent from my DROID Turbo 2
JimSmith94 said:
I have used adb and fastboot for a long time, and this is the first time I've had a problem. I updated to the August security update on the first with no problem, and my computer updated to Windows 10 Anniversary 64 bit on the second. I can do "adb reboot bootloader" and it works, but any fastboot command, even "fastboot devices" does nothing.
Windows Device Manager shows an exclamation mark for "Fastboot Shamu S". I have looked for hidden devices and uninstalled the driver. I tried to update the driver but Windows can't find one.
The adb and fastboot drivers I have been using are from December of last year, so I installed these: http://www.teamandroid.com/2016/06/15/install-fastboot-adb-google-usb-drivers-windows/ but still can't get fastboot working.
Has anyone run into this and can suggest a solution?
Click to expand...
Click to collapse
Not sure if exact to your issue but I'm using a moto g play (2021) and windows 10. Now as long as I don't boot android into recovery mode, the phone is available within file explorer as well as command line. Once I boot into recovery adb commands useless. Unseen. I've reinstalled every driver... It just won't let me fastboot
Lightnin'BoWatt said:
Not sure if exact to your issue but I'm using a moto g play (2021) and windows 10. Now as long as I don't boot android into recovery mode, the phone is available within file explorer as well as command line. Once I boot into recovery adb commands useless. Unseen. I've reinstalled every driver... It just won't let me fastboot
Click to expand...
Click to collapse
Now, this thread is for the Nexus 6 phone. If your problem is specific to the Moto G Play, it is unlikely that anyone here is able to answer.
But generally, fastboot works when the phone is in bootloader mode, not in recovery. However, not all phones have a fastboot-compatible bootloader.
If you have installed an advanced recovery like TWRP, you should be able to use adb. But probably not with the default recovery.
So I have literally tried every single method I have come across and I have seen a few people having the same issue i have.. adb devices see's my phone adb reboot bootloader works and puts me into fastboot mode, how ever thats where everything stops working.. this is a fresh install of windows, fresh driver installs and everything is up to date adb/fastboot wise..
as soon as i type fastboot oem unlock it says waiting for any device and stops never finding the phone..
any help solving this issue would be great.. and the one click method wont work on my phone either
I was dying on this last night but finally figured it out. ADB worked fine, but Fastboot said "waiting for device". I would suggest downloading USBDview if you don't already have it.
Boot your phone into Fastboot and connect to computer.
Check USBDeview for driver that doesn't have a green light next to it.
Open Device Manager and find that device
Right click and update driver and Let me Pick from list
Look for Fastboot and install it
Two seconds later, your bootloader will be unlocked.
brg7562 said:
I was dying on this last night but finally figured it out. ADB worked fine, but Fastboot said "waiting for device". I would suggest downloading USBDview if you don't already have it.
Boot your phone into Fastboot and connect to computer.
Check USBDeview for driver that doesn't have a green light next to it.
Open Device Manager and find that device
Right click and update driver and Let me Pick from list
Look for Fastboot and install it
Two seconds later, your bootloader will be unlocked.
Click to expand...
Click to collapse
When you say "Look for Fastboot" where is this driver that I can choose?