Develop Bugs

adb fastboot driver problem

Hi,
i tryed to get the Desire working with adb and everything works fine. I downloaded HTC Sync, installed only the drivers, and the adb interface worked with the Desire. But if i reboot in bootloader and use fastbootinterface it doesn't work.
fastboot devices get no result.
I downloaded unrevoke modified drivers, i also tryed to uninstall HTC driver and install only the modifed drivers. I also tryed to use this drivers:
http://forum.xda-developers.com/showthread.php?t=1161769
but always the same problem:
The device manager shows adb Intreface and there the HTC bootloader, but with and yellow !. properties of the Device shows me following error:
original Error log said:
Das Gerät kann nicht gestartet werden. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
Translation in my own words: said:
The devices can not be startet (Code10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
And i installed the drivers correctly. So with settings, reboot and tha with deactivate the driver signature.
I hope you can help me

You should uninstall everything and start from the beginning. HTC sync clearly messed something up.
First, try to reinstall hboot drivers.

allready tryed but i get the same error.

google "the devices can not be started (code 10)"
happened to me before, its a windows problem. u have to delete something , cant remember what tho.

i uninstalled every thing desire also the not shown devices in devices manager. than i connected the desire in fastboot with pc and the pc gets the driver from alone. But with the error.
Thanks for the tip with the delete something. but the only results i find are something about reinstall the driver, update the driver, uninstall the driver, ask the support of the device -.-
Do you know maybe a link word what i need to delete? is it a file, an old driver,...??

http://www.google.com/url?sa=t&sour...9oGABg&usg=AFQjCNH1CYaPX1ZheHJ-vYr2Y3GDNFFvWw
try here, the thing that worked for me was deleting somthing in the registry.

thank you very much i'll try it

Just found the time to read the link.
One question? I looked for the Device Class GUID for USB. But there is no lowerfilter and upperfilter. What class is the desire?

I got a similar problem on my workstation, I got an Android Phone in device manager and nothing else, I'm not able to connect and mount desires SD Card. Windows 7 x64, on my laptop (same os) everthing works fine. My PC recognizes desire only with drivers from Android SDK software.

i think your problem is a bit diferent. Do you have a custom ROM installed?
If you did and it is an android 4.x ROM there are many Problems with USB mount. Try an app to mount the SD Card.
Back to my problem. I readed all of the site from up to down and than i deletet the Keys. After Reboot 2 times i got the bluescreen -.- after that the autorepair startet it selfs. the first couldn't repiar the system, and the second couldn't either. So i needed to reinstll windows
The good thing with this is There is difently no HTC on the PC anymore. So in what order i need to install which drivers to get the Desire in Fastboot connected?

A the moment I'm using CronMode 2.1 (previous CM 2.0, SpazeDog ICS, BravoBCM). On previous roms (all ICS based on CM9) got same problem. Laptop - ASUS S6F, Windows 7 Pro x64 - phone recognized, usb mount working fine. Desktop - Gigabyte P55-UD3, Windows 7 Pro x64 - just got Android Phone in device manager and that's all.
What app do you mean?

Try Usb mass storage toggle form the market.

Not working... Also my PC doesn't mount SD as usb storage in recovery (4ext).

nonline said:
Not working... Also my PC doesn't mount SD as usb storage in recovery (4ext).
Click to expand...
Click to collapse
You may have a usb brick. Try the "usb unbrick" option in recovery

abaaaabbbb63 said:
You may have a usb brick. Try the "usb unbrick" option in recovery
Click to expand...
Click to collapse
So why other PC/Laptopts recognize my phone proper?

nonline said:
So why other PC/Laptopts proper recognize my phone?
Click to expand...
Click to collapse
Ok then... reinstall your OS on the PC. If your tried everything, it's the last solution I can think of.

You can first try to reinstall the Driver.
Back to my problem in what order do i need to install the drivers for fastboot?

I can't reinstal OS. It's my workstation... I work on it. I tried with a lot of drivers (even from SDK), same effect "Android Phone" or ADB Interface device.

nonline said:
I can't reinstal OS. It's my workstation... I work on it. I tried with a lot of drivers (even from SDK), same effect "Android Phone" or ADB Interface device.
Click to expand...
Click to collapse
Some firms disable this ability and also SD card reading for security purposes. That can be only reason i can think of.
Sent from my HTC Desire

I'm also a sysadmin of this machine, so you can belive me, just a build-in firewall and security essentials as antivirus protection software.
My wife's Desire S shows the same problem. I think it is a driver issue. Can someone recommend a single "htc desire driver" for Windows 7 64bit?

[Q] Desire - device failed enumeration fastboot/hboot mode

OK everybody I think I already know what is going to come from this but I'm putting it out there anyway to see if anybody else in this world has experienced anything like this and managed to resolve it. I'm assuming it's the boot-loader that is at fault here but maybe, hopefully I am wrong.
So a friend of mine has rooted and installed Cyanogenmod 7.1 stable on his HTC Desire (bravo - gsm) using the revolutionary method. It has been working fine except he had many issues getting any ADB drivers to install and work. I've resolved this issue using Koush's drivers. Good old Koush. File transfers work fine too so the USB itself is obviously fine.
The problem I am facing is that he couldn't and now I cannot for the life of me get HBOOT/Fastboot drivers to install. I've tried using Windows and Linux for this task. I'm assuming that all was well before considering the fact he rooted his device!
Now, please don't shout at me but maybe there is a fancy HTC mode like the Samsung download mode that can be used? It's been a while since using HTC and couldn't recall if there was or even if it would be on these early devices.
So....
In Linux I've done all of the 51android.rules stuff and it works with my Galaxy Nexus and Nexus One. I can also see the device in 'sudo lsusb'.
In Windows.... well.... it's Windows, what more can I say!
The device shows up in device manager as Unknown USB Device (Device failed Enumeration). Now I know that basically means that my device is technically buggered, over current, generally failed to connect etc. I've tried different cables, ports and computers!
So here is the boot-loader information:
Revolutionary (In the pink bar at the top)
S-OFF
HBOOT-6.93.1002
RADIO-5.11.05.27
Whether in Fastboot or HBOOT, when I plug the device in it flashes between Fastboot and Fastboot USB/HBOOT and HBOOT USB PLUG
after a few seconds it goes back to the USB unplugged state on the phone and Windows pops up USB devices not recognized and I get the device show up in device manager as mentioned above.
If I try to install any HTC or custom/universal Fastboot drivers thy all fail as does HTC sync.
I've tried suggestions in this post too - http://forum.xda-developers.com/showthread.php?t=2124360
I think that is everything I can provide. Let me know if you need anything else! Like I say, I think it's the boot-loader itself but would loved to be proved wrong!
Thanks in advanced everyone!
DeeToTheVee

Does connecting your phone as a storage device work?

Yes both storage mode and ADB work fine. ADB was a pain to get working though. Only the universal drivers from Koush worked on windows.
Sent from my GT-P1000 using xda app-developers app

[Q] Help
I have some problem ,
Still no work :/ My os Windows 8.1 x64 ,
Mobile ... , usb device not recognized. So sad i cant downgrade my hboot and still no work Fastboot…
I try disconnect all devices and try all usb port on my computer no work . . .device failed enumeration.
Htc sync cant find my phone. But storage is work fine. Any idea ? Solution ? please

Kasp3rsky said:
I have some problem ,
Still no work :/ My os Windows 8.1 x64 ,
Mobile ... , usb device not recognized. So sad i cant downgrade my hboot and still no work Fastboot…
I try disconnect all devices and try all usb port on my computer no work . . .device failed enumeration.
Htc sync cant find my phone. But storage is work fine. Any idea ? Solution ? please
Click to expand...
Click to collapse
Windows 8 has some problems with installing drivers. I used friends Windows 8 to root her phone and got the same message. With my Windows 7 it worked fine

thanks Yes , windows 8 is su*k but i have Windows 8 and8.1 --11 months but some things is worst (drivers now) i actually finished Bricked and Downgrade my phone (hboot) on Windows 7x64 everything is OK adb and fastboot working on
But i want do this thing on my deskop PC with Win8 Do you think it will ever be possible haha Mic*osoft =D
:good:

Theres a thread in desire general somewhere by @k3lcior and he had same problems with windows 8 but he found the solution (drivers etc) have a search for it or look at his profile then threads started by him. The solution is here somewhere

Try this: http://forum.xda-developers.com/dro...er-fix-windows-8-1-update-2-fastboot-t2831385

[Q] Fastboot windows 8.1 AMD HELP PLZ!!!

Hello. I've been searching for hours for solution. I have HTC desire HD and I had CM11 on it. Then I wanted to upgrade it to newer version. I did almost everything, but then I saw, that my PC recognize my HTC in fastboot as My HTC. There is also error code: 10. I tried almost everything (updating drivers, chipset, USB drivers...) but nothing worked. I don't know what to. Plz help

Did you try something like?:
http://forums.team-nocturnal.com/ind...in-windows-81/
or
http://forum.xda-developers.com/show....php?t=2596698

Yes, I tried both, but none worked. :c

What do you get when you tipe adb devices or fastboot devices?
Some times your phone first have to be recognized by htc sync.
I had problem with one DHD even with WIN7 x86. Adb and fastboot didn't recognize device until i first connect it to htc sync and after that i was able to use adb and fasboot.
Good luck

No fastboot devices but can use adb devices.

Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks

I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

ELoTRIX said:
I have the same problem ADB works but Fastboot not.... I have all drivers correct installed..
Rom: OOS 3.2.7
PC: Windows 10
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
Yeah me too, same ROM and PC OS. Very strange

CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10

But phone starts ok in OOS system?
If, yes, download TWRP 3.0.2.1 original & TWRP 3.0.2.1-19 modified. Put them in phone sd card. Download FLashify from Play store and flash recovery .img. Then go recovery to test if it works.
One of those will work.

inflames19 said:
Got the same problem too, after unlocking the bootloader the fastboot devices cannot find anything
Tested several drivers and even another laptop :/
Rom: OOS 3.2.7
PC: Windows 10
Click to expand...
Click to collapse
CallumL701 said:
Yeah me too, same ROM and PC OS. Very strange
Click to expand...
Click to collapse
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....

Thanks for the different solutions, I'll try it for myself.
But I'm still wondering why the unlock worked because there it used fastboot too

1
me too its says : Witting for devices !!!
Rom: OOS 3.2.7
PC: Windows 10

CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.

1
rpsgrayfox said:
Had the same issue, here's what fixed it for me:
(On Windows 10)
1 - Plug your device while on and install the OP3 drivers that appear as a removable disk, I reinstalled them also, so no harm in doing that again.
2 - Run admin command prompt from wherever you have your adb and fastboot
3 - get your device into fastboot/bootloader mode "adb reboot bootloader"
4 - press windows key + X and go to device manager, look for the Android device with exclamation mark
5 - right click on Android Device > update driver software > browse my computer... > let me pick... > look for Android and then select Android Fastboot Interface if memory serves me right.
And that's it. Fastboot should be recognized now. That's what worked for me when windows recognized adb but not fastboot, hope it helps out.
Remember to hit the thanks button if I helped you out.
Click to expand...
Click to collapse
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem

Since there are a lot of people complaining I think the problem is bigger than we think :/ My OP3 nor OPO are seen

CallumL701 said:
Hey, I am having trouble pushing TWRP onto my op3 via fastboot. I managed to unlock my bootloader successfully but after that, I know cannot flash TWRP. When I type in "adb devices" It returns a string, however "fastboot devices" does nothing. I've uninstalled and re-installed oneplus usb, fastboot and adb drivers countless time and even reset my PC twice. Any ideas? This is really frustrating as I was on TWRP fine before I had to RMA my op3 where they put it back to stock. Any ideas? Thanks
Click to expand...
Click to collapse
Sir Mohd said:
I've done everything U said but when it on the Bootloader it says waiting for device
Thank you to try solve the problem
Click to expand...
Click to collapse
I'm sorry to hear it didn't work, I'd try to reinstall adb and fastboot then using Minimal Adb and Fastboot found in this thread http://forum.xda-developers.com/showthread.php?t=2317790

ELoTRIX said:
I've solved that problem by installing Windows 7 on a Virtual Machine the phone Was recognized and has installed the drivers by itself. And fastboot was working
I don't know why fastboot is not working on Windows 10....
Click to expand...
Click to collapse
Please tell us how you did That ,
Ty.

Sir Mohd said:
Please tell us how you did That ,
Ty.
Click to expand...
Click to collapse
I have just installed on my Windows 10, a Virtual Machine (VMware) with Windows 7 installed all driver oneplus 3 and adb+fastboot and it works

I have the same issue. Got my OP3 yesterday and have been trying in vain to get my Windows 10 install to recognise the phone in fastboot mode, but to no avail. I am unable to unlock my bootloader.

I think the problem is with Windows 10. My laptop did an update yesterday, I think that's the problem.

Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help

It appears to be an issue with Windows 10 drivers. I have used an ancient install of Xubuntu on an older EeePC in order to unlock the bootloader and flash TWRP and SuperSU. I've still had no luck getting fastboot to be recognised on Windows 10, though on Xubuntu, it is recognised instantly with no issues.

inflames19 said:
Got some news for you:
I was so frustrated that I decided to install Windows 7 over my Windows 10 and have a try.
Well what should I say: everything worked on the first try, without any problems with the original driver which comes with the op3 when you plugin the phone.
Hope I could help
Click to expand...
Click to collapse
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u

Sir Mohd said:
I'v Windows 7 Can you explain how ? and what the required files ?
Thank u
Click to expand...
Click to collapse
I'm not at my pc atm but I'll try my best:
If you plugin your op3 there will be a cd mounted with the setup for the driver.
I just installed this driver with the setup.exe (on a complete new instance of Windows 7).
After the installer was finished, I opened cmd.exe and could use adb and fastboot.

OP3 Not Found By Fastboot (Win 10)

So I'm running windows 10 on my pc and my op3 is easily found by windows. When I enter fastboot mode on my op3, the command "fastboot devices" doesn't show my op3. I used that 15 sec adb & fastboot installer.

MrHaPpY66 said:
So I'm running windows 10 on my pc and my op3 is easily found by windows. When I enter fastboot mode on my op3, the command "fastboot devices" doesn't show my op3. I used that 15 sec adb & fastboot installer.
Click to expand...
Click to collapse
Have you enabled oem unlocking from developer options?

I'm having the same problem. After going back to Oxygen OS (now 3.5.4) from MIUI 8 fastboot just doesn't work anymore. ABD works just fine (tried on Minimal ABD and Fastboot on Windows and ABD installed over Android Studio on Ubuntu. Fastboot did recognize the phone on Ubuntu but flashing TWRP resolved in a bootloop (tried the old and the new recovery image).
All drivers are installed on both Windows and Ubuntu (I even removed all drivers on Windows and added them again) and just to make sure everything gets installed I disabled driver signature verification on Windows, but as I said - still no luck.
Edit: Of course USB Debugging and OEM Unlocking is enabled (my bootloader is also unlocked since I already had tried out multiple roms)

Had the same Problem, Win10 is the Problem + the old OP Drivers + the new Update to Win10 etc.
Nothing worked, tryed everything. Created a Thread last week here also...
After that i created a new Partition and installed Win7 on it. All works fine, only thing is while Boot ur System u have to pick ur OS or it waits 30sec to boot up but thats ok.
Now i have Win10 for everything and i reboot to win7 for Fastboot/OP3
http://forum.xda-developers.com/oneplus-3/help/connect-to-phone-adb-fastboot-t3485079
Didnt tryed the last Tip.

KornY10 said:
Win10 is the Problem
Click to expand...
Click to collapse
Can't solve your problem, but OP3 fastboot does work in Windows 10. I did have to disable driver signature verification to install the driver in the first place, and you'll have to leave it off for the driver to stay functional, but it definitely works on Win 10.

I dont tryed ur Way, so yes after disable Driver sign. it works like u Said but i did not Test it.

i had the same problem to find the correct adb driver spent many hours but it didnt work so after that last i try to update windows 10 and find adb driver there after updating window its work like charm so all u have to do is just connect ur phone with data transfer mode on and search the window automatic updates .

Same here

It's driving me crazy. I've updated from a rooted stock OS (incl TWRP) via full OTA directly to 3.2.7, which removed TWRP and root.
I now cannot enter a Fastboot mode which detects the USB connection. Thus I can't flash TWRP again and can't root my phone, making lots of apps unusable.
I've tried every suggestion on every thread but nothing works...
Sent from my ONEPLUS A3003 using Tapatalk

Also got kedacom on my device manager after automatic driver update but my phone still isn't recognised in adb devices, does everyone else's serial number show up?

You guys still have the problem?
Sent from my Xiaomi Mi 5 using XDA Labs

Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work

SgtIcetea said:
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
Click to expand...
Click to collapse
Good that you found the solution..
Sent from my Xiaomi Mi 5 using XDA Labs

Well I didn't really solve the problem on win 10 so i just decided to use Ubuntu instead. Worked well

SgtIcetea said:
Managed to solve it: Disable driver signature verification (follow howtogeek guide) then reinstall Drivers from Oneplus. Go to device manager chose the Kedacom Device and select the correct Oneplus Driver instead then reboot PC and Phone and now it should work
Click to expand...
Click to collapse
I tried that too, but didn't work. What driver did you select in Device manager?

superiscch said:
I tried that too, but didn't work. What driver did you select in Device manager?
Click to expand...
Click to collapse
Rebooted both devices, OP3 was in fastboot. Then there was a Driver called Oneplus Bootloader Interface (or something similar)

SgtIcetea said:
Rebooted both devices, OP3 was in fastboot. Then there was a Driver called Oneplus Bootloader Interface (or something similar)
Click to expand...
Click to collapse
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good ?

superiscch said:
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good
Click to expand...
Click to collapse
Yeah that one. After disabling the driver signature verification you have to re install it, when it's not disabled windows just doesn't install it although it says it does. After I disabled it Windows actually showed a completely new window during installation to install the driver properly

superiscch said:
The driver that shows up as a spare drive when you connect the phone? Tried that too, no good. Going to boot Ubuntu later today, hope that works. I just need twrp, then I'm good
Click to expand...
Click to collapse
Man, had to just do it through my Ubuntu VM. Tried Win 10 Win 7, all gave me troubles.
Started Ubuntu, setup ADB and unlocked in a breeze

i have same problem