Related
UPDATE: Got it working on a windows 7 machine.
I've been trying to unlock my bootloader but have been having issues. I have done the following:
- Enabled Developer Options
- Enabled USB Debugging
- Enabled the OEM Unlock in the Developer Options
- Installed drivers via android SDK
I have adb and fastboot installed from the android SDK. Using that, I have been able to see my device with 'adb devices'. I have also been able to reboot it using 'adb reboot bootloader'. However, once the phone is in fastboot, it does not seem to be detected by my machine. I have tried 'fastboot devices' to no avail. Using 'fastboot oem unlock' just stalls at '< waiting for device >'. Am I missing something?
I have also tried:
- Using a different computer
- Using different USB ports
- Using different ADB / fastboot package (the minimal one).
Please assist! I'd really like to unlock my bootloader now for future flexibility.
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
crachel said:
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Click to expand...
Click to collapse
For some reason i thought that only applied to the 6p. Regardless, I just tried that command and it does the same ' <waiting for device >'.
amitte said:
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
Click to expand...
Click to collapse
Well, I did previously do that where I selected the drivers from the downloaded directory (from google's website). Looking in the device manager, while the device is booted up (not in the bootloader), I see two entries. One in Portable Devices as Nexus 5x, and one in Android Device as "Android Composite ADB Interface". I can't seem to get it to NOT be composite. That driver keeps reappearing even if i try to uninstall it.
yourbuddypal said:
For some reason i thought that only applied to the 6p. Regardless, I just tried that command and it does the same ' <waiting for device >'.
Well, I did previously do that where I selected the drivers from the downloaded directory (from google's website). Looking in the device manager, while the device is booted up (not in the bootloader), I see two entries. One in Portable Devices as Nexus 5x, and one in Android Device as "Android Composite ADB Interface". I can't seem to get it to NOT be composite. That driver keeps reappearing even if i try to uninstall it.
Click to expand...
Click to collapse
The Nexus 5x entry is the MTP interface I guess. The other one would be the ADB interface. For the other one: I had the same problem with a galaxy nexus once when i uses outdated drivers. When you update the dirver there is a checkbox called sth like show only compatible drivers try checking/unchecking that if redular adb interface doesnt show up. Anyhow, i uploaded you the most recent USB drivers just in case. www32.zippyshare(dot)com/v/hloEVk9l/file.html
Install the normal adb interface one while you are in the bootloader and try unlock afterwards with either "fastboot oem unlock" or the new "fastboot flashing unlock"
amitte said:
The Nexus 5x entry is the MTP interface I guess. The other one would be the ADB interface. For the other one: I had the same problem with a galaxy nexus once when i uses outdated drivers. When you update the dirver there is a checkbox called sth like show only compatible drivers try checking/unchecking that if redular adb interface doesnt show up. Anyhow, i uploaded you the most recent USB drivers just in case. www32.zippyshare(dot)com/v/hloEVk9l/file.html
Install the normal adb interface one while you are in the bootloader and try unlock afterwards with either "fastboot oem unlock" or the new "fastboot flashing unlock"
Click to expand...
Click to collapse
A few more updates.....
When the USB option is set to "Charging", the device does show up as "Google Nexus ADB Interface". When I select PTP, it shows up as the "Android Composite ADB Interface". I've tried uninstalling and reinstalling drivers and that didnt seem to help. When the device is in the bootloader, it shows up in the computer's device manager as "Android". Is that normal? I had windows search for a driver in the drivers folder you uploaded but it didnt find any compatible one.
Still not working
yourbuddypal said:
A few more updates.....
When the USB option is set to "Charging", the device does show up as "Google Nexus ADB Interface". When I select PTP, it shows up as the "Android Composite ADB Interface". I've tried uninstalling and reinstalling drivers and that didnt seem to help. When the device is in the bootloader, it shows up in the computer's device manager as "Android". Is that normal? I had windows search for a driver in the drivers folder you uploaded but it didnt find any compatible one.
Still not working
Click to expand...
Click to collapse
Yes this is normal. For the bootloader part, do not let windows search automaticly. Do as i described earlier exept use the driver i uploaded for you or search any other nexus usb driver install guide since the process did not change
Same applies to the installation when you are in the system already. Exept do not override any driver that is under portable devices since its the file transfer protocoll driver.
I succeeded! To be honest - I'm not entirely sure how / why it worked. What I did was install ADB and fastboot from Here on a windows 7 desktop. I was able to detect the device in ADB and reboot to the bootloader. The first time I tried to run fastboot oem unlock failed. The fastboot flashing unlock didnt work and didnt seem to be recognized. I was about to give up, but ran fastboot oem unlock again and that time it worked.
Not sure exactly what that was about, but success! Thanks!
yourbuddypal said:
I succeeded! To be honest - I'm not entirely sure how / why it worked. What I did was install ADB and fastboot from Here on a windows 7 desktop. I was able to detect the device in ADB and reboot to the bootloader. The first time I tried to run fastboot oem unlock failed. The fastboot flashing unlock didnt work and didnt seem to be recognized. I was about to give up, but ran fastboot oem unlock again and that time it worked.
Not sure exactly what that was about, but success! Thanks!
Click to expand...
Click to collapse
im having the same issue too. fastboot can't see the 5X phone. image attached. how did you resolve this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Solution on Linux
I had a similar problem earlier today on one of my linux boxes. Turns out, in order to use fastboot (successfully) under linux, you need to run fastboot with sudo rights.
If I had to guess, I'd guess this is because unlike adb, fastboot doesn't run as a server, so fastboot always needs to get elevated permissions to communicate with a device on a USB port.
Maybe it's possible that Windows wants Administrator rights for similar reasons?
duckxtales said:
im having the same issue too. fastboot can't see the 5X phone. image attached. how did you resolve this?
Click to expand...
Click to collapse
Sorry, I really don't have any more feedback to give you. It really did seem like voodoo when it worked. The only thing I can think to explain the "random" aspect is that perhaps it is related to the quality of cable used. I was using these (http://www.amazon.com/Orzly-Type-Cables-Assorted-Colours/dp/B013RMG5WY/ref=cm_rdp_product), which have now been taken down due to cable standards as described in the comments section for that product. I was thinking that maybe the different USB port on the desktop machine was somehow able to get sufficient voltage or something. Voodoo!
I am having the exact same issue with my 6P right now. However it shows when I do adb devices, just not fastboot devices. Weird...
I even uninstalled the Google USB driver and reinstalled it using Android Studio but Still did not work. Then I even went to Device Manager and uninstalled and deleted the driver. Then went manually to file path C:\Users\MyWindowsLoginName\AppData\Local\Android\sdk\extras\google\usb_driver and clicked next. It installed successfully, but displays as Android Composite ADB Interface. So I guess that is correct then?
Tried to just sideload the new 6.0.1 OTA update using adb since adb devices was recongizing it but still not found...
C:\Users\Matthew\AppData\Local\Android\sdk\platform-tools>adb sideload angler-MMB29M-from-MDB08L.zip
loading: 'angler-MMB29M-from-MDB08L.zip'
error: device '(null)' not found
EDIT: I got it after unplugging my phone, killing the adb.exe process in task manager, waiting until in bootloader before plugging phone in, then running fastboot devices shows the serial number now. I hope that helps others!
I am having this same issue of not being able to install the fastboot driver on Nexus 5X in W7. ADB driver installed no problem, but attaching the 5x in fastboot mode results in "android" device appearing in device manager with no driver installed and no way to install drivers. I have tried every solution suggested in this thread ... re-installing Android SDK, direct installing via device manager, different cables/ports, updating java, running fastboot w/ admin rights, and a few others. Any other suggestions?
I had the same trouble on my 64 bit Windows system. I believe it was HTC sync software that threw the monkey wrench. But I uninstalled that software together with all the adb fastboot drivers for my other devices, removed all adb fastboot versions, then installed the 64 bit version of the Minimal adb fastboot tool.
All good now
Garvinr said:
I am having this same issue of not being able to install the fastboot driver on Nexus 5X in W7. ADB driver installed no problem, but attaching the 5x in fastboot mode results in "android" device appearing in device manager with no driver installed and no way to install drivers. I have tried every solution suggested in this thread ... re-installing Android SDK, direct installing via device manager, different cables/ports, updating java, running fastboot w/ admin rights, and a few others. Any other suggestions?
Click to expand...
Click to collapse
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
wangxiangg said:
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
Click to expand...
Click to collapse
Thank you.
I follow this step. now I can use fastboot.
crachel said:
There do appear to be new fastboot commands. Not sure if "fastboot devices" should work or not, but "fastboot oem unlock" has been replaced with "fastboot flashing unlock"
Click to expand...
Click to collapse
Thanks man! Worked immediately after updating the drivers!
I too had this issue.
Manually installed drivers using this guide.
(pretty much the same instructions as wangxiangg, but with pics)
wangxiangg said:
I think I had the exact same issue. ADB works perfectly fine, but while the phone is in fastboot mode, it shows up in Windows Device Manager as "Android" without a driver. I had to manually "force" install the driver to fix this:
1. right click -> "Update Driver Software..."
2. "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. "Android Device"
5. Pick "Android Bootloader Interface Version: 11.0.0.0 [8/28/2014]" (you may get a warning for this from Windows, just OK it)
Click to expand...
Click to collapse
Man. That was it. Worked like a charm. Thank you.
To clarify, you do this while you are in Fastboot Mode and you right-click on "Android" in step 1.
You can go through the steps while you are in Fastboot Mode and with the cable still plugged in.
amitte said:
Try downloading and installing the latest USB drivers with the SDK manager if you have not yet.
Then go into the device manager (win+x -> device manager)
search for something named like android or simmilar (i dont own a n5x so i cant help you with that)
right click -> update driver software -> browse computer -> pick from list -> have a disk -> browse
now you should see an openfile dialog. driver is in: android-sdk\extras\google\usb_driver
hit open and select "android adb interface" (not composite)
Click to expand...
Click to collapse
Someone give this man a cookie!
it worked!!!!!!!!
Troubleshoot guide for updating the adb and fastboot drivers manually in a PC running any version of windows
First, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
Pre-requisites:
* PC running windows 7/8/10
* Internet connection (just 20MB)
* Working USB cable
Steps:
(1) Download the [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 from XDA
Link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) Install it with "Y" confirmation for all 3 options and reboot the PC
(3) Disable the internet connection of your pc
(4) Reboot your phone to fastboot mode and plug it to your PC's USB 2.0 port (important)
(5) Open device manager on PC and scan for hardware changes from the option if your device is not listed already
(6) If it shows 'Asus android device' -> "ASUS Android Bootloader Interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) Now scan for hardware changes (magnifying glass icon)
(8) It will show 'Android' with an ! symbol
(screenshot 3)
(9) Right click -> Update driver -> Browse my computer for driver software
(10) Choose "Let me pick from a list of available drivers on my computer"
(11) Choose "Android device" or "Asus android device" or similar option and confirm it with Yes or Next option
(screenshot 4)
(12) A warning will pop up, press 'Yes'
Done
(13) Go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Nice... Thanks for the guide... Many people needed it... Was about to make one myself...
Great. Many many thanks bro
kickyvivi said:
troubleshoot guide for updating the adb and fastboot drivers manually in a pc running any version of windows
first, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
pre-requisites:
* pc running windows 7/8/10
* internet connection (just 20mb)
* working usb cable
steps:
(1) download the [official][tool][windows] adb, fastboot and drivers - 15 seconds adb installer v1.4.3 from xda
link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) install it with "y" confirmation for all 3 options and reboot the pc
(3) disable the internet connection of your pc
(4) reboot your phone to fastboot mode and plug it to your pc's usb 2.0 port (important)
(5) open device manager on pc and scan for hardware changes from the option if your device is not listed already
(6) if it shows 'asus android device' -> "asus android bootloader interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) now scan for hardware changes (magnifying glass icon)
(8) it will show 'android' with an ! Symbol
(screenshot 3)
(9) right click -> update driver -> browse my computer for driver software
(10) choose "let me pick from a list of available drivers on my computer"
(11) choose "android device" or "asus android device" or similar option and confirm it with yes or next option
(screenshot 4)
(12) a warning will pop up, press 'yes'
done
(13) go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Click to expand...
Click to collapse
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Divyajeet90 said:
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Click to expand...
Click to collapse
I am having same problem... Did you find any solution for it?
kickyvivi said:
Troubleshoot guide for updating the adb and fastboot drivers manually in a PC running any version of windows
First, try updating your drivers through windows update automatically. If the drivers are installed and still fastboot commands are not working, then follow these steps:
Pre-requisites:
* PC running windows 7/8/10
* Internet connection (just 20MB)
* Working USB cable
Steps:
(1) Download the [OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3 from XDA
Link: https://forum.xda-developers.com/showthread.php?t=2588979
(2) Install it with "Y" confirmation for all 3 options and reboot the PC
(3) Disable the internet connection of your pc
(4) Reboot your phone to fastboot mode and plug it to your PC's USB 2.0 port (important)
(5) Open device manager on PC and scan for hardware changes from the option if your device is not listed already
(6) If it shows 'Asus android device' -> "ASUS Android Bootloader Interface', right click on it and uninstall device with the 'delete the driver software' option ticked.
(screenshot 1 & 2)
(7) Now scan for hardware changes (magnifying glass icon)
(8) It will show 'Android' with an ! symbol
(screenshot 3)
(9) Right click -> Update driver -> Browse my computer for driver software
(10) Choose "Let me pick from a list of available drivers on my computer"
(11) Choose "Android device" or "Asus android device" or similar option and confirm it with Yes or Next option
(screenshot 4)
(12) A warning will pop up, press 'Yes'
Done
(13) Go to adb folder -> shift+right-click and open cmd or powershell window -> type "fastboot devices" without the quotes and you will see your device listed.
Click to expand...
Click to collapse
Hello, I followed your mentioned steps but in my drivers its showing "Samsung Android Device" is that okay for my asus zenfone max pro m1 device? Or there is one portable device option, is that it?
Hi guys, specially opened an account because of this issue. I am unable to run the fastboot devices command even after following all the aforementioned steps. Phone screen turns black and a message appears on the top left stating "press any key to shutdown", while the fastboot devices command gives a "??????? fastboot" response on my PC. PLEASE HELP!
kickyvivi said:
(12) A warning will pop up, press 'Yes'
Done
Click to expand...
Click to collapse
After I completed all the steps, my phone showed on screen "press any key to shutdown" and even in device manager it shows android ADB interface as hidden. Help please. Rebooting again to fastboot mode doesn't help because it shows the same screen "press any key to shutdown" on reconnecting with PC.
May Asus x01bd can't in to the mode fastboot..how to solved it?
Kajin660 said:
May Asus x01bd can't in to the mode fastboot..how to solved it?
Click to expand...
Click to collapse
Well i learned this from somewhere but actually you need to turn off the secure boot in your PC from the BIOS. That's what helped me do it
D0CT0RFATE said:
Hi guys, specially opened an account because of this issue. I am unable to run the fastboot devices command even after following all the aforementioned steps. Phone screen turns black and a message appears on the top left stating "press any key to shutdown", while the fastboot devices command gives a "??????? fastboot" response on my PC. PLEASE HELP!
Click to expand...
Click to collapse
this same with me,, n i donk know how it is??
my phone asus x01bd
Nightmonkeyps said:
Well i learned this from somewhere but actually you need to turn off the secure boot in your PC from the BIOS. That's what helped me do it
Click to expand...
Click to collapse
can u explaining me?? sorry i dont understand what u mean??
Kajin660 said:
can u explaining me?? sorry i dont understand what u mean??
Click to expand...
Click to collapse
Well you know how there's a BIOS in your PC which contains the basic commands required to run a computer. There is a setting called secure boot inside your BIOS. You need to turn it off and then install fastboot tools. To open the BIOS, repeatedly press F10 or F8 on your computer while it is opening. This is how it worked for me atleast
Divyajeet90 said:
bro i have done everything you said, also i followed some youtube videos for help, also when i type "fastboot devices" it shows my device attached but when i try to execute something, my phone says "press any button to shutdown".....i want to flash my phone please help me........because somehow my phone got bricked after flashing latest havoc os 3.0 through twrp .
I follow xda for everything
looking forward for a quick response : - )
Click to expand...
Click to collapse
this happen to me,, and i have solved this,,
step:
1. U must flash ur Phone via qfil,(*)
,than u will lost ur IMEI and SN will Change to 111111,, but dont worry thats can be back again
2. next step is u must recover ur IMEI and SN back (in tele group u wil found the step) after that U just flash stock firmware modified (via TWRP/ORFOX)n then ur phne willl back normally
Note : (*) in firmware for flash via qfil replace the recovery.img with twrp/orfox (rename To "recovery.img") this will bring u a twrp/orfox recovery after flash via qvil
i hope this can help..
Good day everyone. I'm trying to get my bootloader unlocked to install TWRP, but I cannot seem to get the fastboot drivers to recognize my device when I'm in the fastboot bootloader. It works fine when the phone is booted normally, but once it goes to fastboot, it's no longer recognizable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried installing both the oneplus drivers, as well as the google usb_drivers
My phone is a OnePlus 7T on Andriod 10, any help would be appreciated.
raskulous said:
Good day everyone. I'm trying to get my bootloader unlocked to install TWRP, but I cannot seem to get the fastboot drivers to recognize my device when I'm in the fastboot bootloader. It works fine when the phone is booted normally, but once it goes to fastboot, it's no longer recognizable.
I've tried installing both the oneplus drivers, as well as the google usb_drivers
My phone is a OnePlus 7T on Andriod 10, any help would be appreciated.
Click to expand...
Click to collapse
I had a similar issue, yesterday. This was due to me being too excited to unlock my bootloader. I fixed the issue with the below:
https://adb.clockworkmod.com/
After you get your phone up and running, uninstall that ADB driver from Device Manager, then connect your phone to your PC and enable USB debugging. This will fix the MTP issue and install the proper ADB/Fastboot Drivers.
Soapy! said:
I had a similar issue, yesterday. This was due to me being too excited to unlock my bootloader. I fixed the issue with the below:
https://adb.clockworkmod.com/
After you get your phone up and running, uninstall that ADB driver from Device Manager, then connect your phone to your PC and enable USB debugging. This will fix the MTP issue and install the proper ADB/Fastboot Drivers.
Click to expand...
Click to collapse
I tried that out, no change.
I have OEM Unlocking enabled, USB debugging on, and the USB mode set to file transfer.
raskulous said:
I tried that out, no change.
I have OEM Unlocking enabled, USB debugging on, and the USB mode set to file transfer.
Click to expand...
Click to collapse
Try manually updating the driver with the Nexus 4 ADB driver (should say universal in the description).
Soapy! said:
Try manually updating the driver with the Nexus 4 ADB driver (should say universal in the description).
Click to expand...
Click to collapse
I tried that, along with the normal google drivers too, and it takes away the exclamation point in the device manager window, and changes it to a question mark.. but I still can't see the device with 'adb devices'
raskulous said:
I tried that, along with the normal google drivers too, and it takes away the exclamation point in the device manager window, and changes it to a question mark.. but I still can't see the device with 'adb devices'
Click to expand...
Click to collapse
When you check the driver properties do they match what's in the attached image?
Soapy! said:
When you check the driver properties do they match what's in the attached image?
Click to expand...
Click to collapse
No, this is what I get after installing the "Composite ADB" driver from google.
raskulous said:
No, this is what I get after installing the "Composite ADB" driver from google.
Click to expand...
Click to collapse
Have you tried to uninstall AND delete all android/android usb drivers, then reinstall oneplus drivers? https://drive.google.com/file/d/1mUz8Y3_WPce1v3IBLOcVi6unFGRztx_o/view?usp=sharing
[QUOTE = "bynarie, postagem: 83974147, membro: 5375894"]
Você tentou desinstalar E excluir todos os drivers USB do Android / Android e reinstalar os drivers oneplus? https://drive.google.com/file/d/1mUz8Y3_WPce1v3IBLOcVi6unFGRztx_o/view?usp=sharing
[/ CITAR]
Tank You
raskulous said:
No, this is what I get after installing the "Composite ADB" driver from google.
Click to expand...
Click to collapse
I had the same problem before, with fastboot not recognizing the device and only "waiting for device.." appear when I'm on bootloader mode on the phone. I got it working when I chose bootloader driver (Google USB drivers) on Windows Device manager (under the same screen like your screenshot). Put your phone on bootloader mode, open Device Manager (Windows), plug your phone and Android devices should appear. The Google drivers should come up (assuming you installed them) when you click on Update Driver, then choose bootloader. If successful, device should appear under fastboot devices command. Fastboot should then work.
for "fastboot waiting for devices" problem check solution here https://forum.xda-developers.com/t/...owing-up-in-fastboot-mode-windows-10.4194491/
Had the same issue, downloaded the Google USB driver, manually set the device driver to "Android Bootloader Interface" and it worked! Device shows up when running "fastboot devices" now.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
CheshireShorty said:
Had the same issue, downloaded the Google USB driver, manually set the device driver to "Android Bootloader Interface" and it worked! Device shows up when running "fastboot devices" now.
Click to expand...
Click to collapse
This worked for me also! It took me several minutes to understand what it meant to "set the device driver to 'Android Interface'," so let me detail that a little bit. This is what I did.
Put my phone into fastboot:
Code:
adb reboot bootloader
Loaded Windows 10 Device Manager and verified that my phone was listed under "Other Devices" with a yellow triangle next to it.
Downloaded and unzipped the most recent Google USB Driver, from @CheshireShorty's link.
Right-clicked my phone and chose Update Driver.
Clicked Browse my computer for drivers.
Clicked Let me pick from a list of available drivers on my computer
Clicked Have Disk...
Browsed to where I had unzipped the Google USB Driver, selected the file android_winusb.inf, and clicked Open.
Chose Android Bootloader Interface, as suggested by @CheshireShorty.
Verified that both fastboot was working:
Code:
fastboot devices
Rebooted the phone into normal mode:
Code:
fastboot reboot
Verified that adb was working:
Code:
adb devices
I hope that I remembered everything, but even if I didn't, maybe this will help somebody. And even though @CheshireShorty's post was over a year old, it sure helped me.
_sky.captain_ said:
This worked for me also! It took me several minutes to understand what it meant to "set the device driver to 'Android Interface'," so let me detail that a little bit. This is what I did.
Put my phone into fastboot:
Code:
adb reboot bootloader
Loaded Windows 10 Device Manager and verified that my phone was listed under "Other Devices" with a yellow triangle next to it.
Downloaded and unzipped the most recent Google USB Driver, from @CheshireShorty's link.
Right-clicked my phone and chose Update Driver.
Clicked Browse my computer for drivers.
Clicked Let me pick from a list of available drivers on my computer
Clicked Have Disk...
Browsed to where I had unzipped the Google USB Driver, selected the file android_winusb.inf, and clicked Open.
Chose Android Bootloader Interface, as suggested by @CheshireShorty.
Verified that both fastboot was working:
Code:
fastboot devices
Rebooted the phone into normal mode:
Code:
fastboot reboot
Verified that adb was working:
Code:
adb devices
I hope that I remembered everything, but even if I didn't, maybe this will help somebody. And even though @CheshireShorty's post was over a year old, it sure helped me.
Click to expand...
Click to collapse
Or just force a windows update (by clicking "Check for updates"), it will install the fastboot drivers for you when your phone is connected in fastboot mode.
Battled a bit with this one... Just to let others know. I had no change to get it work with Win11. Using Win10 everything worked fine. Luckily I had other PC with Win10 so I got everything working.
ej8989 said:
Or just force a windows update (by clicking "Check for updates"), it will install the fastboot drivers for you when your phone is connected in fastboot mode.
Click to expand...
Click to collapse
Thanks! I wasn't able to install the Google drivers manually with the device manager but this worked for me.
Just click on "View All optional updates" after checking for updates, expand driver updates and choose the Google - Android Bootloader Interface. I wasn't aware of that option in Windows update.
After failing to install LineageOS, I tried to escape a boot loop using @reaper000 's stock rom flash method. Flashing progress froze and I got stuck in fastboot. I powered it off and that was all she wrote. It's completely unresponsive. I've tried:
Hold power for 1 min
Hold power + vol up for 1 min
Hold power + vol down for 1 min
Hold power + vol up + vol down for 1 min
No cigar. It's a fancy glass brick
I've resorted to MsmDownloadTool from the Repository of MSM Unbrick Tools. I'm confident I downloaded the correct one (lemonadep_22_O.05_210324) and installed the correct Qualcomm drivers (I tried Qualcomm drivers from like 10 different sources). I followed the instructions like so:
Select "O2" in "Target" drop-down
Hold vol up + vol down
Plug in cable
Release buttons
Click "Start"
No response from msm. It says "Waiting for device" indefinitely. Device manager shows "Qualcomm HS-USB QDLoader 9008 (COM3)"
I have tried:
Installing Qualcomm drivers from 10 different sources
Installing OnePlus drivers
Using USB 2.0 and different ports
Holding volume buttons for much longer (30 seconds)
Running msm as admin
Deleting msmdownloadtool and opdownloadtool folders in AppData/roaming
Pressing "Start" before plugging in
Charging the phone
Please save me from my stupidity Thank you!
Um, those fastboot ROMs were made for the regular 9, not 9 Pro...
Even then, there's been a lot of op9 users who got stuck at the fastbootd part... What I've yet to hear back is whether those stuck users were indeed using Android SDK 31.0.3 (the latest as I write this) platform tools because I've personally gotten stuck at fastbootd with my new Pixel at Fastbootd and the ONLY way the device would then be recognized was to update the actual fastboot.exe on the PC to its most current version.
Anyways, you might want to try press volume up AND down while connecting USB cable to power to see if you get some response, and when you do, you need to get the device into EDL mode to use the MSM tool.
Although this thread is for the regular op9, it might prove helpful:
Global/US unbricking guide.
Global/US OnePlus 9 Unbricking Guide Tested and used on a LE2115 variant device. YOU SHOULDN'T USE THIS GUIDE UNLESS YOU ARE ABSOLUTELY SURE YOUR PHONE IS BRICKED. PLEASE TRY POWER COMBOS FIRST! THERE ARE NO GUARANTEES, AND THIS SHOULD BE A LAST...
forum.xda-developers.com
Good luck
I very much appreciate the quick reply! I must not have read that fastboot ROM forum correctly
Anyways, I have definitely been holding vol up + vol down when plugging in the device. After some more reading, I'm confident that I'm entering EDL mode based on the "Qualcomm HS-USB QDLoader 9008 (COM3)" name in Device Manager.
MsmDownloadTool is still stuck on "Waiting for device" no matter what sequence of steps I do.
The only clue is this little yellow triangle on the device in DM. Opening it shows this description of the issue:
"Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)"
I have tried drivers from many different sources and they all show this message.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Use this driver
1. Place the downloaded CAB file inside an empty folder, then extract its content (Explorer, 7-Zip, WinRAR)
2. Make sure the phone is connected with your computer's USB port in Qualcomm 9008 (EDL) mode.
3. From Windows Search, type in "Device Manager" (or equivalent in your computer's language) and open.
4. In Device Manager, locate your phone, which should appear under the "Other Devices" category.
5. Right-click the device you connected, and then select the first option, "Update Driver".
6. In the new "Update Drivers" window, click on "Browse my computer for drivers".
Method 1:
7. Click the "Browse" button, then locate the driver folder where you extracted the downloaded CAB file.
8. Click "Next" to start the driver updating process.
Method 2 (if Method 1 fails to install the drivers):
7. Click "Let me pick from a list of available drivers on my computer".
8. Click on "Have Disk" at the right, underneath the rectangle box list.
9. Click on Browse at the bottom right, then locate the driver folder where you extracted the downloaded CAB file.
10. Select the "qcser" file (or "qcser.inf" if you enabled file extensions in Explorer), then click "Open".
11. Click "OK", you should then see the driver appear in the rectangle box list.
12. Select the driver you see, then click "Next" to start the driver updating process.
Make sure you have it connected directly to your computer via USB port rather than via a USB Hub.
Try another cable
After this procedure if you getting same integrity problem;
For disabling signature verification you can give the following commands in Command Prompt (cmd) as admin a try:
bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe /set nointegritychecks on
bcdedit.exe -set TESTSIGNING ON
Reboot pc and try again
@aaron_ruiz You get no power at all? Not even fastboot? You clicked "others" when you first started MSM tool right? Any chance you can boot a linux thumb drive and try it there?
Me too expreienced similar issue with MSM tool. I got mine worked finally when I used a normal USB cable other than C to C... I dont know why is it so.... However that worked for me
falcont said:
https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Use this driver
1. Place the downloaded CAB file inside an empty folder, then extract its content (Explorer, 7-Zip, WinRAR)
2. Make sure the phone is connected with your computer's USB port in Qualcomm 9008 (EDL) mode.
3. From Windows Search, type in "Device Manager" (or equivalent in your computer's language) and open.
4. In Device Manager, locate your phone, which should appear under the "Other Devices" category.
5. Right-click the device you connected, and then select the first option, "Update Driver".
6. In the new "Update Drivers" window, click on "Browse my computer for drivers".
Method 1:
7. Click the "Browse" button, then locate the driver folder where you extracted the downloaded CAB file.
8. Click "Next" to start the driver updating process.
Method 2 (if Method 1 fails to install the drivers):
7. Click "Let me pick from a list of available drivers on my computer".
8. Click on "Have Disk" at the right, underneath the rectangle box list.
9. Click on Browse at the bottom right, then locate the driver folder where you extracted the downloaded CAB file.
10. Select the "qcser" file (or "qcser.inf" if you enabled file extensions in Explorer), then click "Open".
11. Click "OK", you should then see the driver appear in the rectangle box list.
12. Select the driver you see, then click "Next" to start the driver updating process.
Make sure you have it connected directly to your computer via USB port rather than via a USB Hub.
Try another cable
After this procedure if you getting same integrity problem;
For disabling signature verification you can give the following commands in Command Prompt (cmd) as admin a try:
bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe /set nointegritychecks on
bcdedit.exe -set TESTSIGNING ON
Reboot pc and try again
Click to expand...
Click to collapse
I second this. I had the same issue last time I soft-bricked, though I used a different method to temporarily disable signature verification via advanced reboot options and install the qualcomm driver. Either way should work.
How to Disable Windows Driver Signature Enforcement - android file box
This is a step-by-step guide on how to correctly disable driver signature enforcement in 64-bit version of Windows 7, Windows 8, and Windows 10. We will try to wrap up the whole...
androidfilebox.com
Zeus0fyork said:
@aaron_ruiz You get no power at all? Not even fastboot? You clicked "others" when you first started MSM tool right? Any chance you can boot a linux thumb drive and try it there?
Click to expand...
Click to collapse
No power at all. No fastboot. I'm confident I followed all the MSM instructions correctly and am using the correct build. A Linux USB boot is a great idea! Thanks for the reply!
falcont said:
https://onepluscommunityserver.com/list/Unbrick_Tools/Qualcomm drivers.7z
Use this driver
1. Place the downloaded CAB file inside an empty folder, then extract its content (Explorer, 7-Zip, WinRAR)
2. Make sure the phone is connected with your computer's USB port in Qualcomm 9008 (EDL) mode.
3. From Windows Search, type in "Device Manager" (or equivalent in your computer's language) and open.
4. In Device Manager, locate your phone, which should appear under the "Other Devices" category.
5. Right-click the device you connected, and then select the first option, "Update Driver".
6. In the new "Update Drivers" window, click on "Browse my computer for drivers".
Method 1:
7. Click the "Browse" button, then locate the driver folder where you extracted the downloaded CAB file.
8. Click "Next" to start the driver updating process.
Method 2 (if Method 1 fails to install the drivers):
7. Click "Let me pick from a list of available drivers on my computer".
8. Click on "Have Disk" at the right, underneath the rectangle box list.
9. Click on Browse at the bottom right, then locate the driver folder where you extracted the downloaded CAB file.
10. Select the "qcser" file (or "qcser.inf" if you enabled file extensions in Explorer), then click "Open".
11. Click "OK", you should then see the driver appear in the rectangle box list.
12. Select the driver you see, then click "Next" to start the driver updating process.
Make sure you have it connected directly to your computer via USB port rather than via a USB Hub.
Try another cable
After this procedure if you getting same integrity problem;
For disabling signature verification you can give the following commands in Command Prompt (cmd) as admin a try:
bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit.exe /set nointegritychecks on
bcdedit.exe -set TESTSIGNING ON
Reboot pc and try again
Click to expand...
Click to collapse
I installed these drivers and then tried running those commands in Command Prompt, but I was denied due to lack of permissions even when running CMD as Admin.
terlynn4 said:
I second this. I had the same issue last time I soft-bricked, though I used a different method to temporarily disable signature verification via advanced reboot options and install the qualcomm driver. Either way should work.
How to Disable Windows Driver Signature Enforcement - android file box
This is a step-by-step guide on how to correctly disable driver signature enforcement in 64-bit version of Windows 7, Windows 8, and Windows 10. We will try to wrap up the whole...
androidfilebox.com
Click to expand...
Click to collapse
I tried this method and it worked! The yellow triangle on the driver icon has disappeared and the device is now recognized by MSM. The steps to do so were:
1. Hold shift while clicking "Restart" in Windows power menu
2. Navigate to "Troubleshoot" > "Advanced" > "Startup Settings" and then selecting "Disable driver signature enforcement"
3. Restart
Anyone planning to use this method might need access to their Bitlocker recovery key to authenticate this change, which can be found on your Microsoft account online.
Not 1 minute after I passed this problem did I encounter the next... MsmDownloadTool repeatedly gets stuck at "Param preload" under Status of Communication and "Device not match image" under Status of Last Communication.
This is the only thread I could find discussing this. That user generated this error trying to run the MSM build for the global variant of their device without knowing that it had been converted from T-Mobile to Global by the previous owner. The solution in that scenario would be to run the T-Mobile build.
Neither of the T-Mobile MsmDownloadTool builds from the OnePlus Community Server worked. They both show the same error message. Any ideas?
Thank you again to everyone
Tried to run MSM tool as admin?
Tried motherboard usb 2.0 port?
Can you uninstall all qualcomm drivers that you installed before and install .cab driver again.
Or you can try with another pc that you don't install any qualcomm drivers.
I hope it works.
aaron_ruiz said:
No power at all. No fastboot. I'm confident I followed all the MSM instructions correctly and am using the correct build. A Linux USB boot is a great idea! Thanks for the reply!
I installed these drivers and then tried running those commands in Command Prompt, but I was denied due to lack of permissions even when running CMD as Admin.
I tried this method and it worked! The yellow triangle on the driver icon has disappeared and the device is now recognized by MSM. The steps to do so were:
1. Hold shift while clicking "Restart" in Windows power menu
2. Navigate to "Troubleshoot" > "Advanced" > "Startup Settings" and then selecting "Disable driver signature enforcement"
3. Restart
Anyone planning to use this method might need access to their Bitlocker recovery key to authenticate this change, which can be found on your Microsoft account online.
Not 1 minute after I passed this problem did I encounter the next... MsmDownloadTool repeatedly gets stuck at "Param preload" under Status of Communication and "Device not match image" under Status of Last Communication.
View attachment 5479579
This is the only thread I could find discussing this. That user generated this error trying to run the MSM build for the global variant of their device without knowing that it had been converted from T-Mobile to Global by the previous owner. The solution in that scenario would be to run the T-Mobile build.
Neither of the T-Mobile MsmDownloadTool builds from the OnePlus Community Server worked. They both show the same error message. Any ideas?
Thank you again to everyone
Click to expand...
Click to collapse
You ever figure it out I'm having same problem.
With Google Android SDK USB drivers (usb_driver_r13-windows.zip from 'Get the Google USB Driver') installed on a Windows PC, the platform-tools adb command can comunicate with the phone when it's in the Android system.
However, after booting into fastboot, the platform-tools fastboot command cannot communicate with the phone.
Does fastboot only work with the USB drivers installed by the miflash utility?
Or does it work with different drivers from Google or Qualcomm? If so, where to download them from?
There are countless sources claiming to be the Qualcomm drivers, but they are not authoritative.
Qualcomm puts all its downloads behind a login, but even after joining the Qualcomm developer network, I still couldn't find the drivers on there.
Gigajules said:
With Google Android SDK USB drivers (usb_driver_r13-windows.zip from 'Get the Google USB Driver') installed on a Windows PC, the platform-tools adb command can comunicate with the phone when it's in the Android system.
However, after booting into fastboot, the platform-tools fastboot command cannot communicate with the phone.
Does fastboot only work with the USB drivers installed by the miflash utility?
Or does it work with different drivers from Google or Qualcomm? If so, where to download them from?
There are countless sources claiming to be the Qualcomm drivers, but they are not authoritative.
Qualcomm puts all its downloads behind a login, but even after joining the Qualcomm developer network, I still couldn't find the drivers on there.
Click to expand...
Click to collapse
I always use the so-called Minimal ADB and Fastboot package (search by Google).
Starting from that it will further download additional drivers (when phone is connected in Android or in Fastboot mode - PC must be on Internet)
But you may have problems (preventing to recognize the phone in Fastboot) with your USB cable or USB port on the PC or even with some previously installed drivers - Windows wrongly recognize and try to use a previously installed driver instead and then it doesn't work in Fastboot
To clean up the previously installed USB drivers from the particular USB ports you may use USB Deview (google for, it's been couple of years ago when I had to use it last time)
Again, countless links to 'Minimal ADB and Fastboot package' downloads from untrustworthy sources such as dropbox, droidfilehost etc,
But anyway it was not necessary. Thank you for the suggestion to clean the device. I think the Google Android SDK USB drivers contains the bootloader driver, it just wasn't installed. The device manager just needed a nudge.
To recreate the issue...
Connect the phone to the PC via USB
In Windows, go to the Device Manager.
When the phone is in Android system, it is shown in the device tree as...
Android Device > Android Composite ADB Interface
...but when the phone is in fastboot, it is shown in the device tree as...
Other devices -> Android
...with an exclamation mark over the Android device to indicate it is not working.
To fix the problem...
In Device Manager, find...
Other devices -> Android
Right click Android, and select Properties.
In the General tab, click Change Settings. At the UAC prompt, log in with an Administrator account.
In the Driver tab, click Update Driver > Browse my computer > Let me pick from a list of available drivers on my computer > Android Device > Android Bootloader Interface > When 'Update Driver Warming' is displayed, click 'Yes'
Shows: Windows has successfully updated your drivers.
Driver properties now shows: Driver provider: Google, Inc
The phone shows in the device tree as:
Android Device > Android Bootloader Interface
Now Android platform tools fastboot commands work.
Gigajules said:
Again, countless links to 'Minimal ADB and Fastboot package' downloads from untrustworthy sources such as dropbox, droidfilehost etc,
But anyway it was not necessary. Thank you for the suggestion to clean the device. I think the Google Android SDK USB drivers contains the bootloader driver, it just wasn't installed. The device manager just needed a nudge.
To recreate the issue...
Connect the phone to the PC via USB
In Windows, go to the Device Manager.
When the phone is in Android system, it is shown in the device tree as...
Android Device > Android Composite ADB Interface
...but when the phone is in fastboot, it is shown in the device tree as...
Other devices -> Android
...with an exclamation mark over the Android device to indicate it is not working.
To fix the problem...
In Device Manager, find...
Other devices -> Android
Right click Android, and select Properties.
In the General tab, click Change Settings. At the UAC prompt, log in with an Administrator account.
In the Driver tab, click Update Driver > Browse my computer > Let me pick from a list of available drivers on my computer > Android Device > Android Bootloader Interface > When 'Update Driver Warming' is displayed, click 'Yes'
Shows: Windows has successfully updated your drivers.
Driver properties now shows: Driver provider: Google, Inc
The phone shows in the device tree as:
Android Device > Android Bootloader Interface
Now Android platform tools fastboot commands work.
Click to expand...
Click to collapse
Ofc that Google's SDK should contain drivers but I suggested Minimal.. since I always use them and it's the minimal/smallest package (as the name says, and self-contained) to download and install
Btw, there is a thread on XDA for Minimal..., that should be trustworthy I think
Anyway, it's important that it works now for you. And problem is usually with some mess on the PC with previous drivers
USB Deview is small, easy to use and powerfully tool for cleaning the old drivers that have been installed who knows when in the past
zgfg said:
Btw, there is a thread on XDA for Minimal..., that should be trustworthy I think
Click to expand...
Click to collapse
Thanks, found it here: https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
The latest version minimal_adb_fastboot_v1.4.3_setup.exe, is 1mb, dated is Feb 2018, hosted on androidfilehost.com.
I guess Google's platform-tools_r33.0.1-windows.zip supercedes it, it's a little bigger at 6mb, but it's portable, so doesn't require any Administrator access to install, and provenance it clear.