I have done this on Windows 10/11 with the 8 Pro, 8T, and 9 Pro personally.Other members have had success with the OP5T, OP6T, OP7P, OP7T, OP8 and even a OP1 for @mawil1013 and somehow a Xiaomi Mi 9T lol
Spoiler: Backstory
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
To fix the issue, we are going to disable driver signing enforcement in Windows and then install the Unsigned OnePlus drivers.
Install the OnePlus drivers that are included with your phone.
They should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer.
I'm sure you can find the installation package somewhere online, but I don't have a good download source so I am not going to give out random links.
This will create a directory containing the USB driver. This will most likely be
C:\Program Files (x86)\OnePlus USB Drivers
In that folder there is a driver, but both when installed using the installer incuded with my phone, and a downloaded version, I ran into...
The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.
To get around this we are going to disabled signed drivers on windows.
Select the “Start” button.
Type “startup”.
Select “Change advanced startup settings“.
Select “Restart now” under the “Advanced startup” area.
Once presented with the Advanced options select...
“Troubleshoot“ --> “Advanced Options“ --> “Startup Options“ --> “Restart“
After that, a menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver until you reboot, meaning we can install our unsigned OnePlus driver.
Pop open Device Manager
You can press windows + x to bring up a menu, then you can press m or select device manager for quick access
Boot your device into fastboot mode.
This should cause it to show up in device manager as "Andriod", with a yellow triangle
In device manager right click the "android" device
Then press the following options
Update driver --> Browse my computer --> Let me pick --> Have Disk
Navigate to the folder from earlier: C:\Program Files (x86)\OnePlus USB Drivers
Select OnePlus_android_winusb.inf and click okay
After that, OnePlus Android Bootloader interface should be selected. Go ahead and install it.
Congrats! Your device should start showing up in fast boot mode.
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
Make sure when you allow adb debugging in developer mode that you authorize the phone when using adb devices, otherwise you will not see fastboot when you try to use.
Thank you, that would have driven me crazy. It is crazy that it is 2020 and driver manufactures still don't sign their drivers some times.
There is no CD Drive show up....
find on internet a oneplus usb driver and installed....
then got this message trying to get the [oem get_unlock_code]
Code:
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Thanks OP.
finally works...
Okay, I just figured out my mistake, but I'll leave it in case someone else stumbles across the same thing. The fix: choose your language, then choose "reboot to fastboot" and confirm that you're sure. You'll get to a screen with "Fastboot mode" in red near the top. Once there, run the get code command.
Click to expand...
Click to collapse
REFERENCE: reference link
Thanks a lot @Mbektic. This seems so much harder than it needs to be and I wouldn't have been able to unlock my bootloader without your guide. Thanks again!
Wow I didn't even realize that I had helped people until now! I am so glad I could help you guys @bigd4ve @jefffeely and @Pain-N-Panic
Mbektic said:
Hey Guys,
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
So for me, the issue was resolved by doing the following below.
1) install the OnePlus drivers that are included with your phone.
--- they should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer
2) This will create a directory like this... C:\Program Files (x86)\OnePlus USB Drivers, containing the USB driver
3) In that folder there is a driver "" but both when installed from my phone, and a downloaded version, i ran into The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.. So next we are going to disabled signed drivers on windows.
-----Select the “Start” button.
-----Type “startup”.
-----Select “Change advanced startup settings“.
-----Select “Restart now” under the “Advanced startup” area.
-----Select “Troubleshoot“.
-----Select “Advanced Options“.
-----Select “Startup Options“.
-----Select “Restart“.
-----A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver you like in Windows 10 until you reboot.
4) Boot your device into fastboot mode. This should cause it to show up in device manager as Andriod, with a yellow triangle
5) In device manager(press windows + x to bring up a menu, then you can press m or select device manager for quick access) right click the android device
-----Update driver
-----Browse my computer
-----Let me pick
-----Have Disk
-----Navigate to C:\Program Files (x86)\OnePlus USB Drivers
-----Select OnePlus_android_winusb.inf and click okay
-----OnePlus Android Bootloader interface should be selected, and go ahead and install it.
After that your device should start showing up in fast boot mode.
I'm not sure if for some reason my driver version just was lacking a hash, or if it is a common issue, but hopefully i'll save someone a couple of minutes.
Click to expand...
Click to collapse
Yes, I also had to disable device driver signing, then the phone showed up in the bootloader.. You can just open an admin command prompt, type "bcdedit /set testsigning on", REBOOT, then install the proper driver. This seems to be a problem with OOS11.
The easiest method for any newbie is to install , iobit driver booster , free.
Driver Booster 10 Free: Official Free Driver Updater Tool for Windows 2023
The best free driver updater for Windows 11/10. Fully detect and update all your old drivers for graphics, USB, audio, display, network, printer, mouse, keyboard and scanner. Free check driver updates now.
www.iobit.com
Then update the android driver. The fastboot would be working fine after that.
dogmatism said:
The easiest method for any newbie is to install , iobit driver booster , free.
Driver Booster 10 Free: Official Free Driver Updater Tool for Windows 2023
The best free driver updater for Windows 11/10. Fully detect and update all your old drivers for graphics, USB, audio, display, network, printer, mouse, keyboard and scanner. Free check driver updates now.
www.iobit.com
Then update the android driver. The fastboot would be working fine after that.
Click to expand...
Click to collapse
I just cant thank as much as I have to! I couldnt find solution for months, I was using magisk module on old phone to use fastboot and it sucked. Now updated driver and works like charm. Thank you so much!
Thanks for making this thread. I couldn't believe I were having so many issues on my desktop, when I had managed to get everything right when I first got the phone(8PRO) on my laptop. I had adb & fastboot installed, then plugging in Kona w/ usb debug off allowed me to install the adb driver and then for fastboot(while in fastboot, using window's "device manager" I selected the Google usb driver I had downloaded, and finally for edl mode driver just in case (msm), I installed the qualcomm driver while in edl mode( whew). Anyway thanks,
I cannot believe I did not see this thread earlier...
Just finished solving the same problem after going nuts for a couple of hours.
It is most definitely just getting the PC to install the OnePlus drivers AND disabling the driver signing.
What a pain.
Mbektic said:
Hey Guys,
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
So for me, the issue was resolved by doing the following below.
1) install the OnePlus drivers that are included with your phone.
--- they should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer
2) This will create a directory like this... C:\Program Files (x86)\OnePlus USB Drivers, containing the USB driver
3) In that folder there is a driver "" but both when installed from my phone, and a downloaded version, i ran into The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.. So next we are going to disabled signed drivers on windows.
-----Select the “Start” button.
-----Type “startup”.
-----Select “Change advanced startup settings“.
-----Select “Restart now” under the “Advanced startup” area.
-----Select “Troubleshoot“.
-----Select “Advanced Options“.
-----Select “Startup Options“.
-----Select “Restart“.
-----A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver you like in Windows 10 until you reboot.
4) Boot your device into fastboot mode. This should cause it to show up in device manager as Andriod, with a yellow triangle
5) In device manager(press windows + x to bring up a menu, then you can press m or select device manager for quick access) right click the android device
-----Update driver
-----Browse my computer
-----Let me pick
-----Have Disk
-----Navigate to C:\Program Files (x86)\OnePlus USB Drivers
-----Select OnePlus_android_winusb.inf and click okay
-----OnePlus Android Bootloader interface should be selected, and go ahead and install it.
After that your device should start showing up in fast boot mode.
I'm not sure if for some reason my driver version just was lacking a hash, or if it is a common issue, but hopefully i'll save someone a couple of minutes.
Click to expand...
Click to collapse
you've saved my sanity on oneplus5T after upgrading to Android Q 10. Thank you
I also struggled with this issue but found another solution. Once my phone was plugged in (can't remember if it was system or fastboot) I went to Windows Update and browsed the optional updates. One of the optional updates was a driver for android recovery. Installed it and it worked.
bynarie said:
Yes, I also had to disable device driver signing, then the phone showed up in the bootloader.. You can just open an admin command prompt, type "bcdedit /set testsigning on", REBOOT, then install the proper driver. This seems to be a problem with OOS11.
Click to expand...
Click to collapse
Between the OP and this post, I was finally able to get the drivers to work on my 8T (Sim Free- Carrier Unlocked) new phone from Oneplus. I spent several hours trying to determine what the issues were and then found this thread. I am successfully unlocked from the bootloader. Thank you both.
behel1t said:
I also struggled with this issue but found another solution. Once my phone was plugged in (can't remember if it was system or fastboot) I went to Windows Update and browsed the optional updates. One of the optional updates was a driver for android recovery. Installed it and it worked.
Click to expand...
Click to collapse
THANK YOU! This worked 100% for me, super easy too. Went to Windows Update, View Optional Updates, saw the Android External Device update, device showed in fastboot after installing.
THANK YOU SO MUCH!!!!! You're a legend, it works on my OnePlus 5T as well.
Mbektic said:
Hey Guys,
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
So for me, the issue was resolved by doing the following below.
1) install the OnePlus drivers that are included with your phone.
--- they should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer
2) This will create a directory like this... C:\Program Files (x86)\OnePlus USB Drivers, containing the USB driver
3) In that folder there is a driver "" but both when installed from my phone, and a downloaded version, i ran into The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.. So next we are going to disabled signed drivers on windows.
-----Select the “Start” button.
-----Type “startup”.
-----Select “Change advanced startup settings“.
-----Select “Restart now” under the “Advanced startup” area.
-----Select “Troubleshoot“.
-----Select “Advanced Options“.
-----Select “Startup Options“.
-----Select “Restart“.
-----A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver you like in Windows 10 until you reboot.
4) Boot your device into fastboot mode. This should cause it to show up in device manager as Andriod, with a yellow triangle
5) In device manager(press windows + x to bring up a menu, then you can press m or select device manager for quick access) right click the android device
-----Update driver
-----Browse my computer
-----Let me pick
-----Have Disk
-----Navigate to C:\Program Files (x86)\OnePlus USB Drivers
-----Select OnePlus_android_winusb.inf and click okay
-----OnePlus Android Bootloader interface should be selected, and go ahead and install it.
After that your device should start showing up in fast boot mode.
I'm not sure if for some reason my driver version just was lacking a hash, or if it is a common issue, but hopefully i'll save someone a couple of minutes.
Click to expand...
Click to collapse
ohhh my man, you really saved my time. thanks a lot. appreciates ur help.
I recovered my account just so I could post a reply on this thread. THANK YOU MBEKTIC, you saved my skin!
I was puzzled for 3/4 hours wondering what to do. Thank you
Mbektic said:
Hey Guys,
After fighting this for about an hour, and trying everything I could think of, this was the only way I could get my T-Mobile 8T to show up while in fastboot mode.
I tried the below, and probably more...
Ensuring I had the latest fastboot version
Manually installing the bootloader driver from googles SDK
Several restarts
Just installing OnePlus' driver that come on the phone per-installed
So for me, the issue was resolved by doing the following below.
1) install the OnePlus drivers that are included with your phone.
--- they should show up as CD Drive: OnePlus Drivers when you just connect your phone to your computer
2) This will create a directory like this... C:\Program Files (x86)\OnePlus USB Drivers, containing the USB driver
3) In that folder there is a driver "" but both when installed from my phone, and a downloaded version, i ran into The hash for the file is not present in the specified catalog file. The file is likely corrupt or the victim of tampering.. So next we are going to disabled signed drivers on windows.
-----Select the “Start” button.
-----Type “startup”.
-----Select “Change advanced startup settings“.
-----Select “Restart now” under the “Advanced startup” area.
-----Select “Troubleshoot“.
-----Select “Advanced Options“.
-----Select “Startup Options“.
-----Select “Restart“.
-----A menu will appear where you can press “7” on your keyboard to choose “Disable driver signing enforcement“.
Now Device Driver Signing should be disabled, allowing you to install any driver you like in Windows 10 until you reboot.
4) Boot your device into fastboot mode. This should cause it to show up in device manager as Andriod, with a yellow triangle
5) In device manager(press windows + x to bring up a menu, then you can press m or select device manager for quick access) right click the android device
-----Update driver
-----Browse my computer
-----Let me pick
-----Have Disk
-----Navigate to C:\Program Files (x86)\OnePlus USB Drivers
-----Select OnePlus_android_winusb.inf and click okay
-----OnePlus Android Bootloader interface should be selected, and go ahead and install it.
After that your device should start showing up in fast boot mode.
I'm not sure if for some reason my driver version just was lacking a hash, or if it is a common issue, but hopefully i'll save someone a couple of minutes.
Click to expand...
Click to collapse
Thanks for this - I know its a little after the fact but 6+ months later this post has gotten me out of a fastboot hole with a oneplus 9. Now fully rooted only for this. Thanks again.
Related
Since I bought the Lenovo IdeaPad S2110AF from NY, I was searching for how to root the device and I found this thread http://forum.xda-developers.com/showthread.php?t=1896899.
But I was unable to get the ADB interface on Windows 7 x64 laptop and I found the same problem is there for most of the users. Finally last night, I could fix this issue and root my tablet. How I did it:
Download the "S2110-Root.zip" file through the above URL. and extract it to a folder.
1. Enable USB debugging under Settings-> Developer options.
2. Connect tab to computer using the provided data cable.
3. The driver for OTP will be installed in Windows. But the ADB interface may not be installed automatically.
4. Go to Device Manager (Right click My Computer and Properties, the click Device Manager).
5. You can see Other Devices-> Android
6. Right click on that and click Update driver software.
7. Click "browse my computer for driver software"
8. Click "Let me pick from a list of device drivers on my computer" rather than browsing and selecting the driver folder.
9. Click Next and then click "Have Disk" .
10. Then choose the drivers folder and the inf file (in extracted files) - \S2110-Root\Drivers\android_winusb.inf
11. Then select the ADB interface and click OK.
12. Ignore any warning message (like not signed)
That is it. Now you got an ADB interface. You will see as Samsung device on the device manager, never mind it.
Now you got the ADB interface and follow instruction to root through the URL.
Note: I am not sure is this a right place, but I just wanted to post this, it may help someone
I had some problems getting root to work.
I found out to use root with adb the display must be on and unlocked.
I started to work on recovery.img, finally I extracted it and took a look on it. Seems not too hard to get it modified and after do some play with custom roms.
Are you getting errors like "device not found" or "device offline" while trying to run ADB commands? Here's a quick way to troubleshoot your problem on Windows.
Steps
1. Ensure USB Debugging is enabled in Developer Options.
2. Verify current Google USB Driver is installed and that Device Manager is using that driver.
3. Update to latest version of ADB.
1. Ensure USB Debugging is enabled in Developer Options.
Enable Developer Options by going to Settings -> About Phone and tapping on "Build Number" multiple repeated times. You will be greeted with "You are a developer."
Now, under Settings -> Developer Options, ensure you check the box for "USB debugging."
2. Verify current Google USB Driver is installed and Device Manager is using that driver.
You may skip this step if Device Manager lists your phone as "Android Phone -> Android Composite ADB Interface." If it does not, this is likely your root cause.
Go to the Google USB Driver page and download the latest driver directly from Google. Extract the zip file to a folder you know and will remember in the future.
Open up Device Manger in Windows with your Nexus 5 connected. Whatever your Nexus 5 is currently detected as, right click on it and select Properties. Then, in the Driver tab, hit "Uninstall." If available, select "Delete the driver software for this device." and hit "OK." It will remove the old drivers.
Restart your computer.
After restarting, reconnect your Nexus 5. It should be recognized as an unknown device in the Device Manager. (If it isn't, try the previous driver deletion steps again.)
Right click on the unknown Nexus 5 device, choose Properties, and in the Driver tab again select "Update driver." Browse your computer manually by putting in the path to the new Google USB Drivers you unzipped to a folder of your choice in the beginning of this step. Choose next and your drivers should install! You'll know everything completed successfully when you see the phone listed under "Android Phone -> Android Composite ADB Interface" in Device Manager.
This is the most finicky process, so don't be afraid to reboot your computer a time or two and repeat these steps if they don't work on the first try.
3. Update to latest version of ADB.
This is a crucial step. The new version of ADB is required to work with the "USB debugging authorizations" setting.
Perhaps you know how to update ADB, in which case, just do it. However, here's a detailed manual approach to download JUST the adb suite from the SDK:
Go to the Google Android SDK website and choose "Use An Existing IDE" and click the "Download the SDK Tools for Windows." This will allow you to download only an 80 MB file rather than the whole 400 MB suite.
Install the SDK tools exe to a folder of your choosing.
Run SDK Manager and uncheck everything except for "Android SDK Platform-tools." This is the ADB and Fastboot bundle. Install that.
Navigate to your SDK Path as indicated at the top of your Android SDK Manager window. You will now see a freshly downloaded platform-tools folder containing ADB.exe, Fastboot.exe, and a host of other files. That folder is now your updated, portable ADB tools folder. You can move it anywhere you like as long as you run ADB from a command prompt window set to that directory.
After you've followed these procedures, running "ADB Devices" should trigger a prompt on your device to accept the RSA fingerprint of your computer. Accept it, and now all should be working as intended!
Questions? Ask below!
Thanks to:MaxRabbit
Other solutions
Windows 8 Diagnosis
Originally Posted by Yorus
The following worked for me, since all of the suggestions mentioned here didn't work for me:
If you use a Windows 8.1 enterprise N or KN edition, install the Microsoft Media Feature Pack :
http://support.microsoft.com/kb/2929699/en
Sounds too simple to be true but work instantly for me.
Hope it works you some of the people here looking for a solution
Click to expand...
Click to collapse
I tried a hell lot to install ASUS Zenphone adb drivers on my PC( on Windows 7, 8 and 10).
I got the same error everywhere. Error 10. Driver not installed properly.
I searched the Internet for hours without success.
I hope XDA community has some answers.
i got the same problem as you , my zenfone 5 detected as unknown device , i solved with adjusting usb when plug in to laptop like slowly inserting the usb to laptop port and keep adjusting untill its detected. weird dont know why its happen like that , all other phones that i've connect to my laptop detected with easy except for that zenfone 5.
Did you already download from Asus Official Website ? @ceomaverick
Try use this one.
Step:
1. Download and Extract the file from .ZIP
Link: http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE500CL/ASUS_Android_USB_drivers_for_Windows_20150212.zip
2. Go to Device Manager, right click ' Asus Android ADB Interface '.
3. Update Driver Software, then choose ' Browse from My Computer for Driver Software'
4. Select Folder where you extract the .Zip file, check 'Include Subfolder' then klik 'Next'
5. Wait while system searching and installing the driver.
6. Finsih
Hope it will help you.
Thanks
OK, some progress here.
Find the Asus 8.0.0.2 drivers or the 8.0.0.3 ones.
Do the Add Legacy Hardware thing for the ADB Composite Interface -- it will install as "Code 10" not started.
Highlight that device and select update device...ask it to search windows online for the update.
In Win7 this will take a long time, in Win10 it will take just a second BUT be nicely hidden. Click View Optional Updates and then click Driver Updates and then select the ADB Composite interface.
In Win7 it completes quickly w/o reboot. In Win10 you have to reboot.
But with that, the ADB Composite Interface will function.
Now do the Add Legacy hardware thing for the Bootloader -- again, installs as Code 10
Put your phone into fastboot
Select the Bootloader device and do the update-from-windows thing.
Win7 does it directly, Win10 you have to navigate through the Update wizard as before
Now the fastboot interface is presented as working...
I tried to flash my google glass EE2 via my laptop which is currently running windows 10. I have done the following steps:
1. Update the Google USB Driver from android studio sdk manager
2. Download the new image file and unzip it
3. Open windows powershell from inside unzip image folder.
4. Run adb devices (Show my google glass in list)
5. Then adb reboot-bootloader
6. Then turn off the device with physical button and restart with camera and power button until “Press volume key to select, and press the power key to accept.” screen shows up.
7. Then run fastboot devices (Here I stuck, No list of devices, no message nothing happens)
Note:- I updated the driver as well via these steps but still end with no success
1. Connect your Android device to your computer's USB port.
2. From Windows Explorer, open Computer Management.
3. In the Computer Management left pane, select Device Manager.
4. In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see.
5. Right-click the name of the device you connected, and then select Update Driver Software.
6. In the Hardware Update wizard, select Browse my computer for driver software and click Next.
7. Click Let me pick from a list of available drivers on my computer
8. Click Next with Show all devices selected.
9. Click Have disk.
10. Click Browse and then locate the USB driver folder. For example, the Google USB Driver is located in android_sdk\extras\google\usb_driver\.
11. Select android_winsub.inf file and click Open.
12. Click Next to install the driver with Android ADB Interface selected.
13. Confirm the Update Driver Warning dialog.
14. Driver installed
Yeah...
It's funny enough that you created this thread because I am having the exact same issue right now too.
I tried on my laptop running Windows 10 and then on my desktop running Ubuntu. Absolutely zero luck with this. Please let me know if you can figure out a solution. With Powershell I was able to see adb devices but other than that fastboot seems broken to me on Glass.
Hard reset maybe? While on hold power button for 15 seconds, then release. wait a few seconds after that and then hold power button for a few seconds to turn back on.
Also you might try Installing the rooted bootloader.
And take a look at these 2 pages: https://support.google.com/glass/answer/9649198?hl=en
https://dl.google.com/android/repository/platform-tools_r30.0.1-windows.zip
I appreciate your response!
On Windows 10, fastboot devices just seemingly doesn't work at all and doesn't populate the glass hardware at all for me.
OscarDelphi said:
I appreciate your response!
On Windows 10, fastboot devices just seemingly doesn't work at all and doesn't populate the glass hardware at all for me.
Click to expand...
Click to collapse
I see others have had problems on Windows 10 using fastboot. Seems to be related to having a correct driver for your device. If you can't find one (check your device manager to see if it is recognizing Glass properly) you might have to find a Windows 7 computer to do this on.
droidzer1 said:
I see others have had problems on Windows 10 using fastboot. Seems to be related to having a correct driver for your device. If you can't find one (check your device manager to see if it is recognizing Glass properly) you might have to find a Windows 7 computer to do this on.
Click to expand...
Click to collapse
I even tried on Ubuntu with no luck just for curiosity's sake.
Device manager is showing me Unknown USB Device is attached.
OscarDelphi said:
I even tried on Ubuntu with no luck just for curiosity's sake.
Device manager is showing me Unknown USB Device is attached.
Click to expand...
Click to collapse
It makes me so happy to be able to follow up this post with how I found a solution. I am going to give a story first because this was beyond frustrating. The solution for me was to forget finding a solution in Windows 10 and just use an installation of Ubuntu. Holy crap this made the steps a lot easier.
However, even using the Terminal in Ubuntu it hung up twice while flashing system.img and I thought Glass was dead. Fortunately, fastboot was just being finicky and refusing to work. The solution to that was to have the command already ran and then reboot back into fastboot because this allowed the system to almost instantaneously realize the device was in fastboot and it immediately the flashed the files.
I hope this might point some light if anyone else ever comes across the issue!
Install Ubuntu
The easy way to do it, is install Ubuntu and install adb and fasstboot from terminal with comand "apt-get install 'your Tool...'"
yubarajoli77 said:
I tried to flash my google glass EE2 via my laptop which is currently running windows 10. I have done the following steps:
1. Update the Google USB Driver from android studio sdk manager
2. Download the new image file and unzip it
3. Open windows powershell from inside unzip image folder.
4. Run adb devices (Show my google glass in list)
5. Then adb reboot-bootloader
6. Then turn off the device with physical button and restart with camera and power button until “Press volume key to select, and press the power key to accept.” screen shows up.
7. Then run fastboot devices (Here I stuck, No list of devices, no message nothing happens)
Note:- I updated the driver as well via these steps but still end with no success
1. Connect your Android device to your computer's USB port.
2. From Windows Explorer, open Computer Management.
3. In the Computer Management left pane, select Device Manager.
4. In the Device Manager right pane, locate and expand Portable Devices or Other Devices, depending on which one you see.
5. Right-click the name of the device you connected, and then select Update Driver Software.
6. In the Hardware Update wizard, select Browse my computer for driver software and click Next.
7. Click Let me pick from a list of available drivers on my computer
8. Click Next with Show all devices selected.
9. Click Have disk.
10. Click Browse and then locate the USB driver folder. For example, the Google USB Driver is located in android_sdk\extras\google\usb_driver\.
11. Select android_winsub.inf file and click Open.
12. Click Next to install the driver with Android ADB Interface selected.
13. Confirm the Update Driver Warning dialog.
14. Driver installed
Click to expand...
Click to collapse
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
Hey thx for the reply....if you mean the oneplus drivers, then yes they are installed on pc and adb works(command prompt and all that).
i uninstalled the old ones and rebooted...downloaded that file and installed....trying now
L!V3_4_XC3SS said:
Hmmm... You do have the regular drivers for the device installed as well, correct?
(ADB) works? Try this - (Let me know if you need 32 bit installer) No need to disable driver signing enforcement.
10.99 MB file on MEGA
mega.nz
64bit - If it needs a password it's GADGETSDOCTOR
If you're getting into the use of Qualcomm engineering tools check out the fine work of KL Joachim Schepke and the #u100 Crew to make QXDM5g and the accompanying Tools available, search QXDM5 , also includes driver autoinstaller.
Uninstall the old ones and reboot first, go actually delete the directory, Qcomm doesn't uninstall very cleanly.
Let me know how it goes,
-L4X$
Click to expand...
Click to collapse
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"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)"
msi laptop running windows 10 latest update
JayTheKid said:
I have tried this and no luck, this is preventing me from using msm to convert my 8t and possibly unbrick if needed. No matter how I install these drivers this is what I get after reboot
"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)"
msi laptop running windows 10 latest update
Click to expand...
Click to collapse
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
fosgate24360 said:
i was able to get device manager to show the device(kb2005) and update/install the driver for that....however, it does not show another kb2005 device, just shows 2 'unknown device'. when i try the update/install driver for the 'unknowns', i get the windows has encountered an error message
with only the one driver installed(shows qualcomm android modem 9018 in device manager under modems tab), i still cant get qpst tools to work without both drivers. in qpst, it shows the correct driver installed as active phones and shows under ports tab....and theres no port to add with add new port
Click to expand...
Click to collapse
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
L!V3_4_XC3SS said:
Sorry I was traveling for a little bit - did you get this handled? Sounds to me like you need to make sure that your USB & or wireless debugging is active and not just charging, you can change it on your notifications to transfer files or something like that
Click to expand...
Click to collapse
no problem....i was able to get it working thank you. i ended up switching over to android12 evolutionx rom. i had to do that same mod with carrier files and the phone does now pick up 5g signal and 5g icon in stat bar
fosgate24360 said:
Trying to get these drivers installed on windows 10 machine but no matter which driver i choose it always pops up "windows encountered an error while installing driver". im trying to get into qpst file explorer to see the policy_man folder for the carrier policy. im on havoc rom 11 and there is no engineer mode(*#801, *#800) or log kit since im not factory rom. ive tried disable driver signature verify under advanced restart on the pc....no luck same error. ive tried disable secure boot in bios on pc....same error.
ive tried these steps......
1. adb reboot ftm
2. Install (in your smartphone) USB Gadget Tool (https://f-droid.org/es/packages/net.tjado.usbgadget/) and check this modes: ( cser.dun.O , diag.diag, diag.diag.mdm , ffs.adb , gsi.dpl , gsi.rmnet , qdss.qdss , qdss.qdss.mdm )
3. adb shell su setprop sys.usb.config diag,diag_mdm,adb
4. Disconnect and connect your phone usb cable.
5. Go to Control Panel – Device Manager. You will see some unknown device. You should look at the so-called "Oneplus 8T", ignore the others.
Right click on the first "Oneplus 8T" –> Update Driver –> Browse my computer drivers -> Let me pick form a list of available drivers -> Click on I Have Disk -> Show all devices, browse then go to the Qualcomm Drivers that you download earlier. Then do the same to the other "Oneplus 8T". Choose 9018 for both unknown "Oneplus 8T"..
6. Add both ports in QPST Configuration. Only one of them is the one you are going to use. By clicking on EFS Explorer you will know which one it is by seeing X55 Driver in the description.
7. Change carrier_policy and carrier_policy.xml_Subscription01 files
8. adb reboot
stuck on step 5
Click to expand...
Click to collapse
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
Have you tried disabling Driver Signing Enforcement when booting into Windows and then installing the driver?
Xryphon said:
What did you do specifically to get this working? I'm having trouble on Step 5 as well and I can't detect a device.
Click to expand...
Click to collapse
#3 command should start like this:
adb shell
su
setprop....
Also disable Driver Signing Enforcement, as you'll have to install driver every time you want to use QPST, with it enabled.