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.
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
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 !
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 just gave my KF HD 7" to my friend and he wanted me to set it back up as a KF since i had Cyanogen Mod cm-12.1-20160126-NIGHTLY installed on it but haven't used it in a while (read 1-2 years). He was messing around with it before i could get to it and thought hitting Restore to Factory settings would fix it. The device is now stuck on a flashing teamwin logo screen and wont go any further no matter what i've tried. My computer wont recognize the kindle to let me in from cmd so i've reached the limits of my modding knowledge. Could someone please point me in the right direction so i can fix this for him.
If you're running Windows, you should install the Kindle drivers from this post. Also run the nifty 15 second ADB installer found here on XDA, and answer Yes to the "install ADB & fastboot" and "install ADB system wide" questions, and no to the "install device drivers" question. Reboot when the installations are completed, then power off the kindle completely, type fastboot -i 0x1949 getvar product into a command prompt/terminal on your PC, and plug in the kindle (preferably with a fastboot cable/adapter if you have one) when you see <waiting for device>. If you get a string beginning with "tate", then fastboot is working properly. At that point, you should reflash TWRP and the freedom-boot and 2nd bootloader images as directed in Hashcode's thread. (download the files in Step 2, then follow steps 5 and 6 to flash TWRP and the other files.)
Or once you get fastboot working you could use the SRT tool to flash it back to stock with root.
install the Kindle drivers from this post.
Downloaded but installation fails every time with no given reason so i tried a universal adb driver to no avail.
run the nifty 15 second ADB installer found here
Did this with no problems.
I started the fastboot in cmd and it says "waiting for device" but when i plug the kindle in after turning it off completely (i think, best i can do is hold power button till screen turns off and stops flashing teamwin) yet still cant seem to find it. Any suggestions?
TheN3wguy said:
install the Kindle drivers from this post.
Downloaded but installation fails every time with no given reason so i tried a universal adb driver to no avail.
run the nifty 15 second ADB installer found here
Did this with no problems.
I started the fastboot in cmd and it says "waiting for device" but when i plug the kindle in after turning it off completely (i think, best i can do is hold power button till screen turns off and stops flashing teamwin) yet still cant seem to find it. Any suggestions?
Click to expand...
Click to collapse
Are you running Windows 8, 8.1, or 10?
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Are you running Windows 8, 8.1, or 10?
Click to expand...
Click to collapse
Oh god sorry i thought i had said im running windows 10
TheN3wguy said:
Oh god sorry i thought i had said im running windows 10
Click to expand...
Click to collapse
No worries. All you need to do to get the fastboot drivers to install is to follow these instructions to temporarily disable driver signature enforcement. Once you've done that, install the drivers and reboot. After that, fastboot should recognize the kindle.
Above steps worked and KF is now working correctly thanks!
monster1612 said:
If you're running Windows, you should install the Kindle drivers from this post. Also run the nifty 15 second ADB installer found here on XDA, and answer Yes to the "install ADB & fastboot" and "install ADB system wide" questions, and no to the "install device drivers" question. Reboot when the installations are completed, then power off the kindle completely, type fastboot -i 0x1949 getvar product into a command prompt/terminal on your PC, and plug in the kindle (preferably with a fastboot cable/adapter if you have one) when you see <waiting for device>. If you get a string beginning with "tate", then fastboot is working properly. At that point, you should reflash TWRP and the freedom-boot and 2nd bootloader images as directed in Hashcode's thread. (download the files in Step 2, then follow steps 5 and 6 to flash TWRP and the other files.)
Click to expand...
Click to collapse
it doesn't say my device when i connected it helppp
but i can get fastboot working by adb reboot bootloader but i don't know what to do after
AndroidLove231 said:
it doesn't say my device when i connected it helppp
but i can get fastboot working by adb reboot bootloader but i don't know what to do after
Click to expand...
Click to collapse
Once you're in fastboot mode (rebooting into the bootloader from Android, for example), does fastboot -i 0x1949 devices show that the Kindle's connected?
Hi guyz i wanted to root my phone for enabling camera2api. İ did it on Android 9 and worked perfectly. But i disabled it for updating to Android 10. Now im trying to boot patched boot for installing magisk. Everything is okay untill i type adb reboot bootloader for entering fastboot mode and boot img file. When it enters to fastboot mode i type fastboot devices for checking phone but nothing happening and when i type fastboot boot patched_boot.img it says waiting for device and nothing happening. Also when it restarts, usb debugging automatically turning off. İm turning it on checking phone with abd everything is okay but when it restarts from fastboot usb debugging turns off. Any help? İdk if its bug or im doing something wrong
Maharram said:
Hi guyz i wanted to root my phone for enabling camera2api. İ did it on Android 9 and worked perfectly. But i disabled it for updating to Android 10. Now im trying to boot patched boot for installing magisk. Everything is okay untill i type adb reboot bootloader for entering fastboot mode and boot img file. When it enters to fastboot mode i type fastboot devices for checking phone but nothing happening and when i type fastboot boot patched_boot.img it says waiting for device and nothing happening. Also when it restarts, usb debugging automatically turning off. İm turning it on checking phone with abd everything is okay but when it restarts from fastboot usb debugging turns off. Any help? İdk if its bug or im doing something wrong
Click to expand...
Click to collapse
AFAIK, your first point of reference is the fastboot issue. As long as device isn't recognized in fastboot mode, you won't be able to proceed. Drivers ? USB debugging on and authorized with the PC ? Command prompt being used with elevated rights ?
Regarding Cam2Api, I used a Magisk Module since I use Magisk.
Tianhe said:
AFAIK, your first point of reference is the fastboot issue. As long as device isn't recognized in fastboot mode, you won't be able to proceed. Drivers ? USB debugging on and authorized with the PC ? Command prompt being used with elevated rights ?
Regarding Cam2Api, I used a Magisk Module since I use Magisk.
Click to expand...
Click to collapse
Yep i used magisk module too. Yeah usb debugging on and authorized with pc but not recognized on fastboot mode ( adb mode works )
Maharram said:
Yep i used magisk module too. Yeah usb debugging on and authorized with pc but not recognized on fastboot mode ( adb mode works )
Click to expand...
Click to collapse
I know this might sound silly but are you using the latest platform tools version ?
Tianhe said:
I know this might sound silly but are you using the latest platform tools version ?
Click to expand...
Click to collapse
Yeah. Everytime i used 1.4.3 but this time specially downloaded latest version of adb and platform tools (from What is Adb post on xda)
Maharram said:
Yeah. Everytime i used 1.4.3 but this time specially downloaded latest version of adb and platform tools (from What is Adb post on xda)
Click to expand...
Click to collapse
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7. Also try downloading the Platform Tools from developer.android.com (adb is already available in the folder)
Tianhe said:
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7
Click to expand...
Click to collapse
Yeah im using win 10 redstone (latest version)
But also i did it on win 10 with Android 9
Tianhe said:
The only thing I can think of right now is Windows version. I have faced issues on Windows 10 but not in Windows 7. Also try downloading the Platform Tools from developer.android.com (adb is already available in the folder)
Click to expand...
Click to collapse
Going to try this. Thanks a lot <3
Maharram said:
Going to try this. Thanks a lot <3
Click to expand...
Click to collapse
Hope you get the desired result. I am also on Win 10 latest update and I had faced issues initially. I have also added a registry hack so that everytime I open CMD with shift+right click it opens with administrator privileges.