Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
TheeWolf said:
Hello,
I am trying to unlock my bootloader but I my computer (Windows 10) does not recognize fastboot.
When I connect to fastboot (holding volume up button + connecting my phone by USB when it's off, or using the adb reboot fastboot command), the computer does not recognize the phone. I then tried installing drivers (both from Google and Sony) by going into device manager but Windows just doesn't install the drivers.
I then saw this on Sony's website:
Fastboot driver - Sony Developer World
developer.sony.com
So I download the file and pasted it instead of the same file (android_winusb.inf) in the Google driver folder, and it somewhat worked, but Windows said something like unable to find drivers for ADB.
I also tried to install in Windows test mode but to no avail.
No matter what I tried, entering the command fastboot devices in fastboot mode does not give me any output (not even "waiting for device").
What am I doing wrong?
Thank you!
Click to expand...
Click to collapse
Hii. you go to device manager. find your phone in unknown device. Update the driver using i have a disk option. Then try again. it will work.
Disable windows 10 Driver signature and install Fastboot USB drivers again.
Related
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
download and install the sdks and nexus ine drivers manually.
thanks but no luck
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
astron46 said:
Downloaded drivers as you suggested but no luck. Also tried reinstalling sdk. Debugging is on, Java is installed, I'm out of ideas for the moment.
Click to expand...
Click to collapse
Del everything...restart your pc, and download the drivers and sdk..it'll take a few more mins.
When this happened to me, I restarted my PC and it worked.
astron46 said:
Been trying to root N1(FRG83) without unlocking bootloader. Downloaded android-sdk to c: drive and downloaded usb driver.
When I boot the N1 into fastboot mode and type fastboot from the cmd prompt on the computer it sees the phone and gives me the serial (HT****)
When I try the same thing from ADB (ADB devices) it doesn't recognize the phone. I just get a blank line and go back to the command prompt. I've tried this on 2 machines (1 Vista the other Windows 7) and get the same results.
The frustrating thing is that I actually had the phone recognized with the ADB devices command when I first set it up but got called away from the computer and never had a chance to run the rooting routine.
Anybody out there solved this problem?? All help appreciated.
Thanks.
Click to expand...
Click to collapse
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
If the phone is recognized by the computer via usb, but the adb does not see the phone connected, you just may need to simply delete and reinstall the latest USB driver that is offered.
There is actually an issue with Nexus One's where the adb composite interface doesn't work. It seems related to the issue with the broadcom driver and the mac address starting with 38.
See here - http://code.google.com/p/android/issues/detail?id=9437 - for more info.
I have now upgraded to frg83 and it works fine.
codesplice said:
If I recall correctly, adb won't work while the phone is in fastboot mode - and that fact that your fastboot commands work fine indicates that it shouldn't be a driver issue. Make sure you're running the adb commands when your phone is actually booted (at least to recovery).
Click to expand...
Click to collapse
This. If you're running ADB in fastboot, you'll get nowhere.
Ok, I get into Fastboot on my DELL S7 it just keeps on saying "Starting Fastboot USB download protocol" and other stuff in red text above, besides that I need to install the driver on my computer for Fastboot but Windows 7 says "Windows was unable to install your Fastboot" I guided windows to the driver folder in Fastboot+ADB which I got from the Clockwork Mod 5.0 RECOVERY Flash thread.
I really want to flash this clockwork mod http://forum.xda-developers.com/showthread.php?t=1334487
EDIT: Fastboot working, ok I have another problem I flashed the CWM 5.0 IMG file thru fastboot, but how to go into CW recovery? isn't it Power + Up Volume, but that takes me to the Dell update system.
EDIT 2 : I got everything working, used my brain instead of working blindly. Thanks anyways.
ikutoisahobo said:
Ok, I get into Fastboot on my DELL S7 it just keeps on saying "Starting Fastboot USB download protocol" and other stuff in red text above, besides that I need to install the driver on my computer for Fastboot but Windows 7 says "Windows was unable to install your Fastboot" I guided windows to the driver folder in Fastboot+ADB which I got from the Clockwork Mod 5.0 RECOVERY Flash thread.
I really want to flash this clockwork mod http://forum.xda-developers.com/showthread.php?t=1334487
EDIT: Fastboot working, ok I have another problem I flashed the CWM 5.0 IMG file thru fastboot, but how to go into CW recovery? isn't it Power + Up Volume, but that takes me to the Dell update system.
EDIT 2 : I got everything working, used my brain instead of working blindly. Thanks anyways.
Click to expand...
Click to collapse
Where did you find the driver during the fastboot screen? I'm having the same problem and any help would be definitely appreciated. What stock android did you have before installing CWR?
Ok, I had ADB drivers for a Motorola CLIQ and it worked, just select choose from list of installed drivers and selct Android Interface or ADB interface or whatever wityh ADB or android in it. Tyhen run cmd and ttpe fastboot.exe or fastboot
I see a few posts where folks cant get their computer to install the fastboot driver from the FASTBOOT+ADB.ZIP but then they say they got it working, but nobody has said how! I have XP sp3 and cant get the computer to install a fastboot driver. The ANDROID PHONE device is empty as well as the ANDROID USB DEVICE. I get adb interface when I plug in my Epic but I even tried uninstalling it and seeing if the steak would install but no go. Any suggestions?
PfcKirk said:
I see a few posts where folks cant get their computer to install the fastboot driver from the FASTBOOT+ADB.ZIP but then they say they got it working, but nobody has said how! I have XP sp3 and cant get the computer to install a fastboot driver. The ANDROID PHONE device is empty as well as the ANDROID USB DEVICE. I get adb interface when I plug in my Epic but I even tried uninstalling it and seeing if the steak would install but no go. Any suggestions?
Click to expand...
Click to collapse
Yeah, that's right.
This is how it is download ADB which is basically downloading the SDK.
And if you have an Android phone or something just install the drivers for it, usually downloads adb drivers for it too, or if that doesn't work try downloading MOTOROLA CLIQ USB or ADB drivers....as I had them installed when I plugged in the phone.
Put device in fastboot mode
Connect device
Open up Device Manager
Click on "Fastboot" or whatever it says
Click on "Update driver"
Click on "Browse my computer for driver"
Click on "Let me pick from a list of device drivers on my computer"
Click on "Have Disk"
Find your fastboot drivers
im on w10 and im having trouble using fastboot commands through cmd (in a folder with the files)
my device is not showing up when i type "fastboot devices" when i go into fastboot mode or flash mode
when i open cmd and type in "fastboot boot twrp.img" or "fastboot flash recovery twrp.img", it gets stuck saying "< waiting for device >"
but when i use flashtool, it recognizes that im in fastboot mode or flash mode
i have installed:
adb drivers
fastboot drivers
flashtool
platform tools
android sdk
google usb driver
i have tried uninstalling the drivers and reinstalling them through device manager
my device shows up as "S1Boot Fastboot"
my main objective is to get twrp in order to flash oreo carbon rom with magisk
Did you install the fastboot drivers through the file in the Flashtool folder, with the installation of unsigned drivers allowed in Windows (driver signature enforcement disabled)? Suppose that's often a problem.
I had the same problem as you, and I noticed that some [automatic] Windows update had apparently uninstalled those drivers. Installing them again did the trick for me. Good luck.
LaRazón said:
Did you install the fastboot drivers through the file in the Flashtool folder, with the installation of unsigned drivers allowed in Windows (driver signature enforcement disabled)? Suppose that's often a problem.
I had the same problem as you, and I noticed that some [automatic] Windows update had apparently uninstalled those drivers. Installing them again did the trick for me. Good luck.
Click to expand...
Click to collapse
sucha simple fix lol
thanks
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
davidw.roggenkamp said:
I'm about to convert my phone to the WW rom; but I am at an impasse. Any help would be greatly appreciated.
My phone is unlocked as verified by the security message and I can get into fastboot. I have developer mode and usb debugging enabled. When the phone is on, and also when in recovery; the phone will return the serial number with the adb command. When I reboot into fastboot, the phone is no longer detected. I have tried a USB A to C cable, USB C cable, and a combination of USB C, USB 2.0 and USB 3.0 ports on my computer. I have used both the side (blue) and bottom USB ports on the phone, but to no avail. Other odd confirmation is in the device manager my phone shows up as ROG Phone II, but under USB. I'm not sure if it is detected right; the screenshots I saw showed it detected as a device under another section in the device manager.
Click to expand...
Click to collapse
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
waiflih said:
I had the same issue last update. Something in a windows 10 update broke fastboot detection. Use another computer with an older version of win 10 or boot a linux distro.
Click to expand...
Click to collapse
I installed and used ADB into Linux Mint 20; but it ended with the same result.
davidw.roggenkamp said:
I installed and used ADB into Linux Mint 20; but it ended with the same result.
Click to expand...
Click to collapse
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
reg66 said:
Try installing this version of adb/drivers
https://androidfilehost.com/?fid=746010030569952951
Once installed, the adb folder in root of C contains a 'cmd here' file, makes launching a cmd even easier!
Click to expand...
Click to collapse
Tried this with the same result.
https://adbdriver.com/downloads/
Plug your phone on side port and reboot to fastboot then use this app to fix fastboot mode
If you already plugged the USB cable to the side port and still not able to use fastboot, it is probably a Windows problem. The Android fastboot exe is not properly signed so you need to disable Windows' driver signature check before installing the ADB/Fastboot drivers.
I cannot post link but search for "android fastboot driver disable driver signature enforcement". Disable the signature check then install the fastboot drivers.
Here is the quick run-down of the steps.
1. In command console and in Admin mode, run this command and then restart => bcdedit /set testsigning on
2. Install adb and fastboot stuff
3. After successful install, in command console and in Admin mode, run this command and then restart => bcdedit /set testsigning off
For ADB/Fastboot driver, i use the one by "fawazahmed0" here in XDA. The title of the thread is [Tool] Latest ADB Fastboot and USB Driver installer tool for Windows.
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
davidw.roggenkamp said:
Okay, I tried all of the above; fastboot is still not detected in ADB, but it is detected in Recovery and when the phone is at the home screen. I noticed the phone came up under "Samsung Smart Phone" or some such in the device manager. I uninstalled and reinstalled and now it shows up as ROGPhoneII. However, same result as before. I tried the install methods on a secondary Windows 7 machine, but with the same result.
Click to expand...
Click to collapse
Are you sure your using the side port ?
Created a new topic, disregard
Hi Friends,
I recently updated the Ultra to MIUI 13.03.
I enabled "Developer Options" and enabled "USB Debugging"
Recently Clean installed Windows 11.
Extracted Platform tools downloaded from Android Google website.
but when i typed "adb devices". The device wasn't detected.
then i saw in device manager driver wasn't installed, so downloaded the MiFlashTool and
tried to install drivers in that folder through Windows Device manager, It installed "Android ADB driver" But still my device isn't
listed in ADB Devices
Please help.
Have you tried a different cable? I'm not teaching you to suck eggs but some cables are just not up to it.
Can you see the red fastboot logo on the phone?
Or try a different phone to prove its not your set up.
Sathelp said:
Have you tried a different cable? I'm not teaching you to suck eggs but some cables are just not up to it.
Can you see the red fastboot logo on the phone?
Or try a different phone to prove its not your set up.
Click to expand...
Click to collapse
I'm able to detect device in "ADB Devices" when phone is booted into android OS, even the MiFlashTool also detects the device when phone in booted into OS.
But after i type ADB reboot bootloader, phone restarts into FASTBOOT, i can see RED "FASTBOOT" logo in phone screen but it doesn't get detected.
How come phone gets detected in ADB when Phone is booted into OS MIUI13 but not in FASTBOOT.
I'm on windows 11 .
I changed the cable also with a new Xiaomi cable purchased recently, still the same result.
You can never see a result to detect mi 11 ultra through ADB devices. Rest assured your device is already detected and ready to use. Even though can not see device address.
I had the same case. Make sure all the necessary drivers are installed.
At first mine was also not detected in fastboot. When I first ran MI Flash Tool, it automatically installed some drivers. And I also manually installed USB driver of MI 11 Ultra.
After that MI Flash detected my phone in fastboot.
A small suggestion from me: Use "Xiaomi ADB Fastboot Tools" for flashing. MI Flash was giving me, timeout error and my device got into fastboot loop. After flashing with "Xiaomi ADB Fastboot Tools" all went well.
hello, I also had this problem and to solve it I used the driver of Mi unlock which is at the level of the parameters and launch it in fastboot then connect it to the pc and the drivers must be installed
I had a similar problem with my Mi 10. Found via ADB but wouldn't show in fastboot. Tge way I solved it was to boot into TWRP recovery (assuming you have it) and then go to their reboot menu and choose fastboot from there. It will then put you into their version of fastboot and your computer should recognise the phone in fastboot mode.
I hope this helps
jaggub4u said:
Hi Friends,
I recently updated the Ultra to MIUI 13.03.
I enabled "Developer Options" and enabled "USB Debugging"
Recently Clean installed Windows 11.
Extracted Platform tools downloaded from Android Google website.
but when i typed "adb devices". The device wasn't detected.
then i saw in device manager driver wasn't installed, so downloaded the MiFlashTool and
tried to install drivers in that folder through Windows Device manager, It installed "Android ADB driver" But still my device isn't
listed in ADB Devices
Please help.
Click to expand...
Click to collapse
Adb and Fastboot is not the same thing!
If you're phone is detected in ADB, it means you have install the Adb Driver ( which more than probably is Google Driver or Xiaomi driver for ADB ).
In order for you phone to be in Fastboot do the following:
- Reboot to Fastboot and connect your phone to PC with original Xiaomi cable from the box
- Go to Device Manager > Other Devices > Android Device ( you will see a yellow sign, which means you don't have the Fastboot Driver )
- Download XiaomiMi11 Ultra Bootloader Driver.zip, unzip it
- Click on the Android Device with yellow sign > Update driver > Browse my computer for drivers > Select the Xiaomi Bootloader Folder
It will install the driver.
From here you're good to go!