Im having issues using fastboot on my vista x64 machine, it cant seem to find my G1. Im currently using the signed x64 adb driver. Has anyone gotten fastboot to work on x64? Thanks in advance for any responses.
Just to provide a bit more info, iv confirmed that my g1 is in fastboot mode via the engineering SPL. when attempting to flash images to it, fastboot cant seem to find the g1 in fastboot mode.
Works fine for me (Vista 64 + signed drivers + fastboot)...
Are you sure it's in fastboot mode? The screen actually says fastboot?
Also make sure fastboot is using AdbWinApi.dll from the 1.1 SDK and not the 1.0 SDK.
Hmm, i must be doing something wrong.. Im able to use adb normally with the x64 driver , just no fastboot. Can you send me a link to the driver you are using? Thanks.
Never mind, i think i got it, i was using an older 1.0 r2 sdk, ill try the new one. Thanks, your answer fixed my problem.
I am having the same problem. I'm using the 64 bit drivers and can use adb just fine.
When I boot the phone up I hold the camera and power, says "serial0", i insert the phone usb, push the back button so that it displays "fastloader" it then makes a "USB chime" in windows and my device manager flickers for a second.
The I run "fastboot flash system system.img' with admin privs and all i get is <waiting for device>...
Please help!!
Are you using the 1.1r1 android sdk?
http://developer.android.com/sdk/1.1_r1/index.html
I've installed a ROM and need to flash boot.img but in "cmd" ı cannot do this. I'm using Windows 8 and I got "waiting for device" error. I ran cmd as administrator and wrote "fastboot -i 0xfce flash boot boot.img" but they did not work too. How can I flash the boot.img ? Thanks for your helps.
Anyone know that ?
welocan said:
Anyone know that ?
Click to expand...
Click to collapse
Windows 8 has issues with HTC Drivers. For example I have 2 Windows 8 machines - one with clean install, the other - an upgrade from Windows 7.
The upgraded one, which has perfectly working drivers on Win7 now connects the device fine. But I spent hours on the other one (clean install) trying different drivers without sucess. It just refuses to detect the device.
So you can install older version of Windows or Ubuntu as dual-boot alongside your Win8 or use another computer.
And do not add the "-i 0xfce" to the command, it is not necessary. fastboot flash boot boot.img will do fine
Hey there
(info: Windows 7, LG optimus 4X HD, 4.0.3 ICS, debugging mode is ON)
So i've installed the SDK, ADB & fastboot + drivers
to try to unlock my bootloader.
First i followed this guide:
http://forum.xda-developers.com/showthread.php?t=2224020
When I type this command in the prompt: adb reboot oem-unlock
My device is just rebooting as normal.
But when i try to do fastboot commands it tells me
Waiting for device.....
So fastboot isn't seeing my phone
Does anyone have an idea what's going on?
Ryan.
ryantju said:
Hey there
(info: Windows 7, LG optimus 4X HD, 4.0.3 ICS, debugging mode is ON)
So i've installed the SDK, ADB & fastboot + drivers
to try to unlock my bootloader.
First i followed this guide:
http://forum.xda-developers.com/showthread.php?t=2224020
When I type this command in the prompt: adb reboot oem-unlock
My device is just rebooting as normal.
But when i try to do fastboot commands it tells me
Waiting for device.....
So fastboot isn't seeing my phone
Does anyone have an idea what's going on?
Ryan.
Click to expand...
Click to collapse
your phone must be booted in bootloader mode to use fastboot commands unlike adb commands that are used when booted in the OS
Currently in the process of unlocking bootloader via following the steps provided in this forum. I'm having trouble with my computer recognizing my device when I boot into bootloader. When the phone is on, it is recognized as "OnePlus", but in Bootloader the computer says "Android" and "Drivers unavailable" I've tried manually assigning them with no luck. Any help would be appreciated
Still no luck on unlocking boot loader. I've installed and reinstalled drivers from OnePlus and Adb and fastboot, tried installing the Android SDK. No luck. I cannot get "fastboot devices" command to show anything in a command prompt
are you writing the command "fasboot devices" on the same directory where you have installed your adb?
Chinaroad said:
are you writing the command "fasboot devices" on the same directory where you have installed your adb?
Click to expand...
Click to collapse
I have tried it on a few different directories. I installed the adb via the exe on the tutorial. I'm not sure which directory that would be
If you already installed adb go to c:/adb in the folder hold shift and click the right mouse button, there should be an option that says open command prompt here or open powershell prompt here, click it. You should see a command prompt, boot into fastboot and connect your phone to your computer and now type "fastboot devices". If it doesn't detect it, it might mean that you haven't enabled USB debugging. And remember to turn on oem unlocking in your phone
I finally figured out my issue. I had to go into the windows device properties, attempt to manually install the drivers while the phone was in bootloader. It would then throw an error about the android bootloader interface and asked if i wanted to search for an update, windows actually found an update to that particular part of the driver. Installed it and that fixed it.
Glad you fixed it
TheBananaz said:
I finally figured out my issue. I had to go into the windows device properties, attempt to manually install the drivers while the phone was in bootloader. It would then throw an error about the android bootloader interface and asked if i wanted to search for an update, windows actually found an update to that particular part of the driver. Installed it and that fixed it.
Click to expand...
Click to collapse
Could you kindly share which specific OnePlus device you were able to unlock the bootloader, e.g. Unlocked OnePlus 6, International Version, etc?
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both.
Oneplus 7 pro is running 10.3.0GM21AA
>fastboot devices
>adb devices
List of devices attached
966c8016 device
Trying to use fastboot to flash patched magisk img and install magisk.
Do you enter in fastboot in phone?
Sent from my GM1910 using Tapatalk
Yes tried from bootloader as well
fustyler said:
Yes tried from bootloader as well
Click to expand...
Click to collapse
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
redpoint73 said:
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
Click to expand...
Click to collapse
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
fustyler said:
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
Click to expand...
Click to collapse
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
redpoint73 said:
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
Click to expand...
Click to collapse
Have tried different cables and different machines both pc and mac
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
mnemesis said:
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
Click to expand...
Click to collapse
I ran adb reboot bootloader from pc to boot phone into fastboot.
In the bootloader it states device state is unlocked
However fastboot devices ran from pc still shows no device.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thanks this fixed it.
Issue fixed by billyt1's comment above. case closed.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Giri Prasad said:
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Click to expand...
Click to collapse
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
I have a similar problem. I tried to disable the signature. Installed a new Redmi Note 7 driver. The phone is recognized as an Android phone in the device manager. In Orangefox recovery it is recognized with ADB command. In fastboot it is not recognized. In Orangefox I can't format data. So my ROM is not booting up. So I want to flash fastboot ROM with Fastboot but in Fastboot device is not even recognized.
t
puyow18 said:
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
Click to expand...
Click to collapse
Sorry on the late reply. Pretty sure you can only do fastboot boot boot(recovery).img or\and boot_a or boot_b. Wont let you fastboot flash boot.img.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thank you so much!
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Thank you Thank you Thank you Thank you Thank you Thank you...I have been fooling with this all day
Hi, I already solved this issue (but this only works for xiaomi phone (Redmi Note 7 to be specified), for other brands I think need to download your devices flasher/driver tool)
For Xiaomi user only
1. Download Mi Unlock Tool (https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/) (Version 4.5.813.51)
2. Extract the files anywhere you like
3. Run MiUsbDriver.exe to install the driver
4. Try fastboot devices command
I hope this helps you guys. The Mi Unlock Tool also useful to unlock device locked bootloader.
For other devices maybe can follow this tutorial
Fixed: Fastboot not detecting your Android device
Fix the Fastboot not detecting your device. If your device is not detected by the Fastboot then these tricks will really help you.
www.qasimtricks.com