Related
[Q] USB BOS descriptor failed, "waiting for device", "Device cannot start. (Code 10)"
Hello
The situation:
I'm trying to relock the bootloader and flash RUU, so that I can get rid of the tampered flag and start over.
I'm trying to use Hasoon2000's Toolkit to do this, but I'll try any method that sounds reasonable.
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
EXTRA INFO:
I didn't use Hasoon's toolkit to unlock the bootloader, I actually used the platform-tools from the SKD bundle thru the terminal on a mac pc. Then I flashed CWM onto the One S using "./fastboot flash recovery recovery_thefilename.zip". Then I reloaded bootloader, selected Recovery, then my phone's screen went black, turned back on, and I saw the Red Triangle with the Exclamation mark. According to a "How to" blog, which I didn't read until after the fact, I was supposed to hold down the power button and volume button at that point in time, but I didn't. I had no idea what was going on. I pressed the power button and my phone restarted, and now every time I reboot to recovery mode, it just restarts the phone and says "This build is for development purposes only. Any redistribution will result in legal action." or something like that.
OK THAT'S ALL.
I appreciate any help!
jire
The text in red is normal if you have a custom recovery.
Just get the device in fastboot USB mode.
Check with command: fastboot devices
To see if it is connected. I should return you sn number.
(Since you manually unlocked, this should be easy for u.)
Then manually flash a correct recovery (or use the toolkit with the custom option). Reboot in recovery. Flash ROM.
Verstuurd van mijn One S met Tapatalk
Can you try to execute fastboot oem lock command on Windows OS which have hTC drivers installed? I guess that you using Linux OS now... Just install Windows in VM and hTC drivers, adb and fastboot you can download on htcdev.com or from android bundle package... I'm pretty sure that you have problem with your drivers...
Sent from quietly brilliant HTC One S
USB 3.0 might be the issue
Hey guys, thanks for trying to help me out here, I appreciate it a bunch!
Before I go any further. I think I've learned what the problem is. Well, first of all, if you didn't catch it, I've been working thru this on both win and apple computers.
Hasoon's toolkit is only available for windows. Therefore, if I said/say I did something with his toolkit, that means I was using my win computer, which is actually a Surface Pro, which has USB 3.0 === THE PROBLEM
According to this: http://forum.xda-developers.com/showthread.php?p=29286429
Unfortunately, I haven't been able to test this hypothesis, yet, because I first need to find a win pc with USB 2.0. [Fact: I couldn't get androidfiletransfer.app to recognize my htc one S on my mac. Coincidence?]
real187: When you say to install a "correct" recovery, are you implying I currently have an incorrect recovery on my phone?
mikronac: I have virtually no experience with command prompt. I just got my Surface Pro last week :laugh: and I'm geeking out...So, what I'm saying is I don't know how to do "fastboot oem lock command" ... The htc drivers are installed, up-to-date and operating without a hitch.
It can't be problematic your usb 3.0.
Please deinstall your phone drivers and install them again...
If you know how to navigate to platform tools folder in Windows Explorer, only what you need to do is to hold shift key on keyboard and right click on mouse and select option open command prompt here. Than you type :
Adb devices
Response should be serial number of phone
Adb reboot bootloader (uab debugging must be enabled)
When it reboot in fastboot, type in cmd:
Fastboot oem lock
Sent from quietly brilliant HTC One S
I can confirm: It is USB 3.0
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
maatriks said:
Hi, today I faced similar problem while trying to put my Sony Xperia S into fastboot. Only after finding this topic and switching from USB3.0 port to USB 2.0 did I manage to boot into fastboot. I have not tested, if I can boot into fastboot now, that the driver has been correctly installed via USB 2.0, but to avoid any troubles I suggest everyone to stick with USB2.0 for now.
I found this topic as I had the exact same error in Device Manager as OP in this topic.
Click to expand...
Click to collapse
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
No USB 2.0
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
dsuresh89 said:
Hi,
I don't have USB 2.0 in my laptop.
Could you please help me how to proceed with USB 3.0?
Thanks in advance
Click to expand...
Click to collapse
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
dsuresh89 said:
Problem solved with USB 3.0.
uninstall your 3.0 USB xtensible host controller driver provided by microsoft and install driver from INTEL.
Enjoy...
Click to expand...
Click to collapse
hey
there is no driver for 3.0 USB xtensible host controller for windows 8
and I already have a usb 2 but I have the same problem
I think that it came from windows 8
Thanks in advance
Unable to fastboot in Windows 8.1
Aciong.Aksaya said:
Thanks for this bro I tried usb 2.0 and it worked. I searched many tuturial how to access fastboot in my Win8 but no luck many thanks for this.
Click to expand...
Click to collapse
Hey Bro,
I am facing the same issue. Unfortunately I don't have a USB 2.0 port in my computer. Im struggling to flash the boot file.
Please help
jire0006 said:
Hello
When I connect the HTC One S to the PC (running Windows 8) and select 'Mount as disk drive', the PC recognizes the device, and I can explore it. Using Hasoon's toolkit I select "Relock Bootloader" and click "Do Command". A first command prompt pops up, then my phone goes into fastboot, then I close the first prompt, then a second prompt follows and says "waiting for device".
I enter the Device Manager -> "Android USB Devices" -> "My HTC", -> Right click -> "Properties". In the Device Status field it says:
"This device cannot start. (Code 10) A request for the USB BOS descriptor failed."
jire
Click to expand...
Click to collapse
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
To apply the workaround for a specific device, add a REG_DWORD value named SkipBOSDescriptorQuery that has a value of 1 to the following registry subkey:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\usbflags\vvvvpppprrrr
(where vvvv is the device's Vendor ID, pppp is the device's Product ID, and rrrr is the device's Revision number. You can get the VID/PID/REV numbers from the device manager's details tab. This number is encoded in the HardwareIDs of the device)
1. Click Start, click Run, type regedit in the Open box, and then click OK .
2. Locate and then click the following subkey in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\UsbFlags
3. On the Edit menu, point to New, and then click Key.
4.Type the name of the new key in the following form:
vvvvpppprrrr
where
vvvv is a 4-digit hexadecimal number that identifies the vendor (idDevice from the USB Deviceescriptor),
pppp is a 4-digit hexadecimal number that identifies the product (idVendor from the USB Device Descriptor)
rrrr is a 4-digit binary-coded decimal number that contains the revision number of the device
(bcdDevice from the USB Device Descriptor).
5. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
6. Type SkipBOSDescriptorQuery for the name of the DWORD Value, and then press ENTER.
7. Right-click SkipBOSDescriptorQuery, and then click Modify.
8. In the Value data box, type 1 , and then click OK.
9. Exit Registry Editor.
10. Unplug and re-plug the device for the workaround to take effect.
Click to expand...
Click to collapse
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
windows 8 have a issue with ville fastboot... please make you sure you have a fix
zoodles said:
I know it has been a long time but I just encountered the same problem with fastboot, an HTC One S and Windows 8.1. These steps from Microsoft (a registry edit workaround) enabled my computer to recognize the device and got fastboot seeing it too:
http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
I'll paste the workaround here in case Microsoft take the page down:
On mine that meant editing a registry key called 0BB40FF00100 that already existed.
Click to expand...
Click to collapse
THANK YOU SO MUCH. Fixed for me on HTC Magic
..
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows.
---------- Post added at 10:41 PM ---------- Previous post was at 10:17 PM ----------
Problem is caused by Windows 8 and Windows 10. Just no compatibility for old hardware.. I'm disappointed from Microsoft Windows. Btw, I tried all methods in forums and in YouTube too (updating USB Root Hub drivers). Nothing helps, just "Failed device enumeration". Windows 10.. I will go back to Win7, fortunately I don't have license for 10.. Pray about these who has...
Bruh, this worked like magic on my HTC One X+ !!!
Using Windows 10 Enterprise Build 17134 by the way
Thanks a lot!
Thank you very much bro. HTC One V good working.
I have read many guides about setting up and using ADB, I am using an older computer with windows xp sp3. I just got my first nexus device which is a nexus 5, in device manager the phone shows up as " samsung android phone" and then "google nexus adb interface". I have tried uninstalling and then reinstalling the drivers using many different ones found on xda. I have the android sdk installed and adb seems to be working, at least when I type in "adb version" the version number comes up, but when I type "adb devices" nothing comes up as attached devices. This is really frustrating me, as I have have been trying to get this working for days now.i have already uninstalled every other android related driver using USBDeview. If anyone could please help me with this I would greatly appreciate it. I'm almost to the point go giving up! Could the problem be because I rooted the phone before getting all this setup? I ask this because when I try to update the driver in device manager it always shows driver type as clockwork mod no matter what driver I try to use
Did you enable ADB via Dev Options on the phone?
theesotericone said:
Did you enable ADB via Dev Options on the phone?
Click to expand...
Click to collapse
Do you mean USB debugging, yes I have that enabled
Go to device manager select your phone (samsung device or whatever it's showing!!) and right click and select "Update Driver Software".
On the next screen, select "Browse my computer for driver software" and set the path to : C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver"
I have used C:\Program Files (x86) because that's the place in which I have installed the SDK. Put a tick mark on "Include subfolders" and then hit Next...
Your device drivers will be installed again and adb will be working!
PS: Please make sure you have the latest android sdk and usb_driver downloaded from SDK manager!!
Hi,
I have a rooted Xperia Z5 and I would like to update my firmware to 32.2.A.0.305.
I used to do firmware updates many times before using flashtool on my windows 7 machine.
Recently I switched to windows 10 and now need to reinstall the fastboot driver.
I downloaded the driver from sonymobile webstie:
http://developer.sonymobile.com/downloads/drivers/fastboot-driver/
Unzipped the file, and got a directory with the "android_winusb.inf" file.
Booted the phone in "bootloader" mode via the TWRP recovery (LED on phone is blue).
The regular method of power down, volume up+connect to USB did not work. The LED was blue for a second and then turned off.
When in "bootloader/fastboot" mode, opened the windows "device manager" and found the problematic S1 device.
Right click on it, update driver, browse my computer, pointed to the directory where the ".inf" file is located.
Windows "makes sounds" as if it is installing the driver, but then gives an error:
"Windows found a driver software for your device but encountered an error while attempting to install it"
"Android ADB interface"
"The system cannot find the flie specified"
I have no idea what the problem is.
A few posts suggested that this might be a driver-signing problem with windows 10.
They suggested removing the "driver-signing" option and try. Did not work.
I also tried this with a virtual machine Windows 7 that I have installed, and got the same error, so I'm not sure it is a windows version problem.
I read in one place that this is an error with the location of the file and that it should be located under the "C:\Windows\WinSxS" directory.
Tried that as well, and no luck.
Does someone have any idea what the problem is?
Alernatively, if someone can explain or point me to a post of how to use fastboot and flashtool with linux,
that can also help.
Thank you.
Avi
driver signature verification
1. Goto START (windows icon);
2. Keep pressing SHIFT, klick POWER and RESTART
(shift is pressed all the time along);
3. Choose Troubleshoot > Advanced options > Startup Settings and click the Restart button.
When your computer restarts you'll see a list of options.
4. Press F7 on your keyboard to select Disable driver signature enforcement.
Your computer will now restart and you’ll be able to install unsigned drivers.
This is firt to do, but didnt quite get it if you tried this allready. Greetings
Have the same problem. Disabled driver signature enforcement. Did not help
Are you sure it's disabled? Some pc's don't have the option to disable the driver signature enforcement. If that's the case you need to enter the bios settings and look for the tk keys and delete them, then restart your pc and you can install the fastboot driver.
Hope this helps
Had the same issue on my new setup.
This solved all my problems: https://forum.xda-developers.com/xperia-z/help/help-findiing-installin-s1boot-fastboot-t2218143
dim4x4 said:
Have the same problem. Disabled driver signature enforcement. Did not help
Click to expand...
Click to collapse
Disable driver signature enforcment then install flashtool drivers and select your phone drivers and fastboot drivers, it will ask you are you sure to install press yes and then in folder x10flasher you have fastboot and open cmd in that folder and just use fastboot. Cheers
L33Tgod said:
Disable driver signature enforcment then install flashtool drivers and select your phone drivers and fastboot drivers, it will ask you are you sure to install press yes and then in folder x10flasher you have fastboot and open cmd in that folder and just use fastboot. Cheers
Click to expand...
Click to collapse
Nice and cool - but we still dont have a Sony Xperia Z5 Driver from it in the List
enter ‘’adb devices‘’，cmd list the devices list，display devices number.everything is normal.
after i reboot to fastboot and link to my computer,i enter 'fastboot devices'.there is no response in cmd.
i have install drive.i dont know where the question is.please give me some advices.
thanks
hahaha1659 said:
enter ‘’adb devices‘’，cmd list the devices list，display devices number.everything is normal.
after i reboot to fastboot and link to my computer,i enter 'fastboot devices'.there is no response in cmd.
i have install drive.i dont know where the question is.please give me some advices.
thanks
Click to expand...
Click to collapse
When your device is connected while in fastboot mode, does it show the device listed in Windows device manager? It should show a driver for "android bootloader interface". If it doesn't show that then your drivers aren't installed/associated correctly. To do this, boot into fastboot and connect to PC, then go to device manager, find the device on the list, right click on the device, then select "update driver", then select "browse my computer for driver software", then select "let me pick from a list of available drivers on my computer", if you have the correct drivers installed on your PC, you should see a list of drivers, you're looking for the one that says "android bootloader interface", that is the driver you need to select.
Sent from my LGL84VL using Tapatalk
Droidriven said:
When your device is connected while in fastboot mode, does it show the device listed in Windows device manager? It should show a driver for "android bootloader interface". If it doesn't show that then your drivers aren't installed/associated correctly. To do this, boot into fastboot and connect to PC, then go to device manager, find the device on the list, right click on the device, then select "update driver", then select "browse my computer for driver software", then select "let me pick from a list of available drivers on my computer", if you have the correct drivers installed on your PC, you should see a list of drivers, you're looking for the one that says "android bootloader interface", that is the driver you need to select.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
thank you very much,at first.
i do the steps you told me.but i cant find the item named 'andriod bootloader interface'in the list of drivers.there are three items in the list of drivers.
one is named'samsung mobile usb cdc composite device',the other two are named 'usb serial device'.
so what i should do in the next.
thank you again.
hahaha1659 said:
thank you very much,at first.
i do the steps you told me.but i cant find the item named 'andriod bootloader interface'in the list of drivers.there are three items in the list of drivers.
one is named'samsung mobile usb cdc composite device',the other two are named 'usb serial device'.
so what i should do in the next.
thank you again.
Click to expand...
Click to collapse
Ahh..
That explains it, you're trying to use fastboot on a Samsung device, Samsung does not use fastboot, adb can be used on Samsung but fastboot can not. Samsung uses download mode instead of fastboot mode and Odin instead of fastboot, download mode does not use the "bootloader interface" driver like fastboot does, it uses a USB comm driver. The "cdc" and "serial USB" drivers that you see in device manager are the drivers to access the device's storage.
Next time, do some searching to understand your device. If you had done any kind of reasonable searching and reading about your device, you would know that Samsung devices don't use fastboot and are not fastboot compatible at all, and they probably never will be.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Ahh..
That explains it, you're trying to use fastboot on a Samsung device, Samsung does not use fastboot, adb can be used on Samsung but fastboot can not. Samsung uses download mode instead of fastboot mode and Odin instead of fastboot, download mode does not use the "bootloader interface" driver like fastboot does, it uses a USB comm driver. The "cdc" and "serial USB" drivers that you see in device manager are the drivers to access the device's storage.
Next time, do some searching to understand your device. If you had done any kind of reasonable searching and reading about your device, you would know that Samsung devices don't use fastboot and are not fastboot compatible at all, and they probably never will be.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
thank you
i know the common method the samsung devices use,via odin in download mode.i just follow the Installation instructions published by lineageos organization.there is the url wiki.lineageos.org/devices/hlte/install
they gave a reason why use heimdall instead of odin. and i have finished those steps in my another device.so i think those steps dont have problem.
i guess the problem i am facing is i havent installed the deriver correctly like you said.
hahaha1659 said:
thank you
i know the common method the samsung devices use,via odin in download mode.i just follow the Installation instructions published by lineageos organization.there is the url wiki.lineageos.org/devices/hlte/install
they gave a reason why use heimdall instead of odin. and i have finished those steps in my another device.so i think those steps dont have problem.
i guess the problem i am facing is i havent installed the deriver correctly like you said.
Click to expand...
Click to collapse
Odin is much easier, the lineage website discusses using Hiemdall because they are developers, developers primarily use Linux instead of Windows, they just prefer Linux over Windows because Linux is best for the kind of work they do. Linux is a more powerful operating system but, in my experience, setting things up on a Linux system always involves chasing issue after issue to get it set up correctly, you find an issue, fix the issue, then you find another issue to solve only to find another when you fix that issue. It always involves having to install packages and updating packages, even having to install or update "this" package so that you can install or upgrade "that" package in order to get some other package installed, and so on and so on. If you aren't a software developer, forget about using Linux.
When it comes to android devices, the only advantage that Linux has over Windows is when building ROMs and other android development. Other than that, Windows can do anything you need to do on an android device. I've used Linux systems and Windows systems, Windows
Use a Windows PC, it's MUCH, MUCH easier. All you need is:
1) A Windows PC
2) Odin
3) The "USB drivers for Samsung phones.exe" file
4) Your stock firmware file or your custom recovery file in .tar.md5 file format.
5) A USB cord
6) USB debugging enabled in developer options.
7) Charge your device to at least 70%
When you have all of those things, you can flash your device and have it up and running within an hour.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Odin is much easier, the lineage website discusses using Hiemdall because they are developers, developers primarily use Linux instead of Windows, they just prefer Linux over Windows because Linux is best for the kind of work they do. Linux is a more powerful operating system but, in my experience, setting things up on a Linux system always involves chasing issue after issue to get it set up correctly, you find an issue, fix the issue, then you find another issue to solve only to find another when you fix that issue. It always involves having to install packages and updating packages, even having to install or update "this" package so that you can install or upgrade "that" package in order to get some other package installed, and so on and so on. If you aren't a software developer, forget about using Linux.
When it comes to android devices, the only advantage that Linux has over Windows is when building ROMs and other android development. Other than that, Windows can do anything you need to do on an android device. I've used Linux systems and Windows systems, Windows
Use a Windows PC, it's MUCH, MUCH easier. All you need is:
1) A Windows PC
2) Odin
3) The "USB drivers for Samsung phones.exe" file
4) Your stock firmware file or your custom recovery file in .tar.md5 file format.
5) A USB cord
6) USB debugging enabled in developer options.
7) Charge your device to at least 70%
When you have all of those things, you can flash your device and have it up and running within an hour.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you very much.I have done as you said.The procedure is so easy. hahaha
the only question is whether the website 'odindownload.com' is right or not.i am not sure the software from there is safe.i cant find formal website.
you are so patient.i am very pleased to talk with you.
hahaha1659 said:
Thank you very much.I have done as you said.The procedure is so easy. hahaha
the only question is whether the website 'odindownload.com' is right or not.i am not sure the software from there is safe.i cant find formal website.
you are so patient.i am very pleased to talk with you.
Click to expand...
Click to collapse
It was created by a member of this forum, you should be able to find a safe version here somewhere.
Sent from my LGL84VL using Tapatalk
Win10, in fastboot mode the device cannot be found, but it can be found in adb. I installed drivers from Sony's website. In fastboot mode the device manager shows under 'other', in adb it is normal and shows 'Sony sa0116 ADB interface driver'. As far as I know the driver is the same for adb and fastboot...my Pixel is recognised with no problem, only this Sony...anyone knows how to get it recognised in fastboot mode?
Sorted the driver issue... didn't install it properly...
Go to Windows device manager look for one called x-boot or android (your xperia) and open the driver details.
Klick update driver and next choose look for software on computer. Next window gives you the option to pick one of common devices. Install the sony driver for adb interface.
Could give a zip of it if needed.
After the manual driver update it should recognize your phone immediately - if you have checked the "fastboot devices" prompt before just repeat that (no reboot or reconnection necessary)
Win 10 seems to have problems. I downgraded to win 7 all sorted.
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
funkoot said:
I'm having the same issue with my Xperia X compact. Windows 10 says it's installed best driver for my device but in device manager theres a warning next to the driver and device is not recognised under ADB devices. I remember it being simple the last time I did it under windows 7. Is there an alternative method for flashing Twrp recovery other than ABD?
Thanks
Dave
Click to expand...
Click to collapse
unfortunatly, adb is the only way to install twrp.
the drivers (i attached) [from Sony by the way] need to be installed.
You need to install this driver/ file : android_winusb.inf
then boot your phone to fastboot (volume + [up] only) or with adb (adb reboot fastboot) and windows should detect "a new device" which (normaly) is called "android" with exclamation mark.
Tap "update driver"
Search on PC
select from list
ADB interface
Samsung Android ADB Interface is the driver you need to select for windows to detect the phone
And then theoretically it should work.
If that doesn't work, look if a USB port (either PC/Phone/Cable) is broken/damaged etc.