My phone 2 boot to fastboot, can't found fastboot device in my computer. i try reinstall driver, change cable, reboot to fastboot mode. only found QDLoader 9008. my phone is not bricked but boot to fastboot mode, can't found fastboot device.
sorry for the my bad english...(translator)
I had the same issue. What I did was make a live boot disk with FWUL and boot into that. I believe there is an issue with fastboot and Windows 10 Update 2004.
hackthis02 said:
I had the same issue. What I did was make a live boot disk with and boot into that. I believe there is an issue with fastboot and Windows 10 Update 2004.
Click to expand...
Click to collapse
Can confirm it is an issue with Windows 10 v2004, I was driving myself insane with this issue and once I tried it on a computer with an older update everything worked perfectly.
try a different cable.
if you're on linux, run fastboot with sudo
Related
Hellow. I have some problem with connection of my One. Atm i wanna s-off my phone.But can't.
After connecting phone to usb2.0 port win8 recognise it well (checked by "adb devices -l"). But when i try to reboot into bootloader i've got "waiting for device" (fastboot reboot bootloader). Ok i'm switch off the phone and boot in bootloader (fastboot mode). Phisical connection is good (fastboot usb). Try to check connection by "adb devices -l" and i got no one device connected. But in same time i can easy flash recovery by "fastboot flash recovery recovery.img". Btw when i put phone in fastboot mode my win8 told me that connected device not recognised and can't work good, but when i start android win8 got my phone well. I've check it with two original htc usb cables and one not original.
Any ideas?
Thx!
When the phone is in fastboot mode, you use the fastboot command, adb won't work. When the phone is not in fastboot mode, you use the adb command, fastboot won't work.
BenPope said:
When the phone is in fastboot mode, you use the fastboot command, adb won't work. When the phone is not in fastboot mode, you use the adb command, fastboot won't work.
Click to expand...
Click to collapse
ah i understand. tnx for reply
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.
Ok..so here's the situation. I was going to install a new ROM ( my son got a new phone a iphone ) but any ways. As I was in TWRP i did everything we all normally do but the phone died mid flashing GAPPS. when i went to pulg the phone to the charger and restart the phone i see that it started to boot up the it jumped straight to FASTBOOT and it's stuck. I can toggle through fastboot but that is it. when i go to restart it will show the boot animation but then goes to fast boot. it wont go to TWRP nothing. I've combed XDA and found the multi tool but don't think that is working or i might be using it wrong. the computer doesn't recognize the phone. im trying to get this phone back up and going and give to my daughter . any help is greatly appreciated. thank you in advacne.
Here's what I'm talking about just in case someone asks
Try installing a stock factory image from fastboot.
runekock said:
Try installing a stock factory image from fastboot.
Click to expand...
Click to collapse
How...I can't get my computer to recognize the phone... When I plug it in it doesn't read it...I should have the drivers already installed...adb push right.... I'll search for the command to see if it finds the phone
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
runekock said:
adb never works in fastboot mode. You'll have to use the fastboot command.
On the PC, try
fastboot devices
to see whether the phone is available. If not, check your drivers - I believe that fastboot uses a different USB driver.
With fastboot, you can't install zip-files, only image files. So download the stock factory image, not the OTA.
Click to expand...
Click to collapse
Thanks for the heads up I'll definitely be trying this and I'll give you an update soon
I tried to roll back from 10 to 9 and ended up messing up my fastboot. I can use twrp and adb but in fastboot my computer does not see it at all. I've tried linux and windows.
Is there a fastboot image backup I can flash anywhere?
BlazingBullets said:
I tried to roll back from 10 to 9 and ended up messing up my fastboot. I can use twrp and adb but in fastboot my computer does not see it at all. I've tried linux and windows.
Is there a fastboot image backup I can flash anywhere?
Click to expand...
Click to collapse
Have you tired plugging into the side USB port and running "adb reboot bootloader" ?
Has anyone tried using adb fastboot on Samsung Galaxy Note 8 recently.
I have tried unsuccessfully to get the fastboot work using Windows and Macbook with the latest Samsung Samsung drivers for fastboot. Even installed the fastboot drivers from Android Development platform but still no luck beyond <waiting for device>.
I read on another forum that Samsung no longer allows fastboot to work with their devices. Is it correct?
Fastboot as I understand it is an extension of Android recovery.
If you have USB Debugging enabled on your device, you should be able to issue commands: adb reboot fastboot
Fastboot commands also work in bootloader.
@V0latyle
Thanks for your reply.
I have USB debugging enabled alongwith the unlocked bootloader, as my device is rooted.
Recently, I was trying to use adb fastboot to flash boot image file of my Samsung device. However, it kept displaying <waiting for device> .
I tried the same command from my MacBook using Android platform tools, but result was still the same.
All adb commands work very well on Windows and MacBook without any hiccups.
Prof_Shekhar said:
@V0latyle
Thanks for your reply.
I have USB debugging enabled alongwith the unlocked bootloader, as my device is rooted.
Recently, I was trying to use adb fastboot to flash boot image file of my Samsung device. However, it kept displaying <waiting for device> .
I tried the same command from my MacBook using Android platform tools, but result was still the same.
All adb commands work very well on Windows and MacBook without any hiccups.
Click to expand...
Click to collapse
The appropriate command to flash /boot would be:
Code:
fastboot flash boot <boot image>