Short story: can't get identifier token, stuck on "waiting for device".
Hi everyone I have scanned around and feel confident I have a unique or difficult situation trying to root my HTC One. I have the phone drivers installed, the latest 4.1.0.001 msi to be precise, and the phone responds more or less to the computer when it's in Android. So the issue is with fastboot state, for which I tried the normal HTC drivers, then other drivers I was able to find for Fastboot around XDA, and finally the Universal Naked Driver which supports HTC One for ADB. I am able to use the command adb reboot-fastboot and then I return a blank list from the command adb devices or fastboot devices. I have PDA net on the phone, and have it set to "connect automatically". There is a sign that something is awry when I plug the phone up to the PC and PDAnet immediately returns "can't connect, HTC Sync Error = -1". I went into windows and allowed unsigned drivers for ADB, and uninstalled other drivers, deleted files, and rebooted each time I switched drivers in attempt to get a response from the phone in Fastboot.
usb debugging is enabled. In fastboot, the Universal Naked driver returns the following error:
Port_#0004.Hub_#0003
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Btw Universal Naked Driver seems to be the MOST functional returning a lot of info about the device, and the second driver I dl'ed was apparently for HTC One X and didn't work at all.
Shortcuts I have taken: yeah I didn't install the entire android SDK I just got the package off XDA and also tried Hasoon's solution. I didn't install the entire large HTC Sync app either, but I don't think either of these are required.
Basically on my ATT htc one, I will never get this thing unlocked if it is REFUSING to recognize the device while it's in Fastboot, halting the process by making a bootloader unlock impossible.
Plz help and I won't return it for an S4!! I don't wanna. A beer to he who saves me the trip back to ATT store.
zWiLLX said:
Short story: can't get identifier token, stuck on "waiting for device".
Hi everyone I have scanned around and feel confident I have a unique or difficult situation trying to root my HTC One. I have the phone drivers installed, the latest 4.1.0.001 msi to be precise, and the phone responds more or less to the computer when it's in Android. So the issue is with fastboot state, for which I tried the normal HTC drivers, then other drivers I was able to find for Fastboot around XDA, and finally the Universal Naked Driver which supports HTC One for ADB. I am able to use the command adb reboot-fastboot and then I return a blank list from the command adb devices or fastboot devices. I have PDA net on the phone, and have it set to "connect automatically". There is a sign that something is awry when I plug the phone up to the PC and PDAnet immediately returns "can't connect, HTC Sync Error = -1". I went into windows and allowed unsigned drivers for ADB, and uninstalled other drivers, deleted files, and rebooted each time I switched drivers in attempt to get a response from the phone in Fastboot.
usb debugging is enabled. In fastboot, the Universal Naked driver returns the following error:
Port_#0004.Hub_#0003
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Btw Universal Naked Driver seems to be the MOST functional returning a lot of info about the device, and the second driver I dl'ed was apparently for HTC One X and didn't work at all.
Shortcuts I have taken: yeah I didn't install the entire android SDK I just got the package off XDA and also tried Hasoon's solution. I didn't install the entire large HTC Sync app either, but I don't think either of these are required.
Basically on my ATT htc one, I will never get this thing unlocked if it is REFUSING to recognize the device while it's in Fastboot, halting the process by making a bootloader unlock impossible.
Plz help and I won't return it for an S4!! I don't wanna. A beer to he who saves me the trip back to ATT store.
Click to expand...
Click to collapse
i would say you havent installed the drivers. best thing to download to get your HTC one to recognize in any mode is the HTC sync manager. i know its kinda annoying but the phone will get recongized in every mode and the initial plug in just requires a few minutes to detect, download, and install the drivers.
syaoran68 said:
i would say you havent installed the drivers.
Click to expand...
Click to collapse
I did try the "stripped" HTC One drivers found here on XDA.. I mean http://forum.xda-developers.com/showthread.php?t=2217396 seems pretty straightforward!
But yes at this point in the game why not give the full bloatware a try, thx
are you using the all in one toolkit? i have also found that installing the htc sync software helped alot of people with driver problems
Is your phone actually in fastboot mode?
Gave it a shot; my win 8 laptop still has no ability to recognize the phone in device manager with HTC BMP, Sync Manager, or HTC Driver Installer.. which are the the 3 related programs I've installed.
The HTC driver recognizes the device (while in Fastboot) as My HTC, while the Universal Naked Driver calls it something different I believe, but neither are working to allow adb or fastboot to list the device, and both drivers have the same error as to why the device can't start: "a request for the USB BOS descriptor failed"
BenPope said:
Is your phone actually in fastboot mode?
Click to expand...
Click to collapse
Hey Ben Pope thanks for asking, yes it's in the white screen saying ***LOCKED*** in pink at the top. And yes I get into fastboot by adb reboot-bootloader most of the time because it's easier than the button pressing (which I've done also).
One weird thing I did notice is that "FASTBOOT" is shown with a red background when the device goes into the mode, however if I use the volume up/dn buttons and navigate, the text changes to "FASTBOOT USB", and persists that way until it's re-booted. Don't know if that matters, but at least if it's totally abnormal, there could be something funky going on in the firmware.
Thanks.
skinsfanbdh said:
are you using the all in one toolkit? i have also found that installing the htc sync software helped alot of people with driver problems
Click to expand...
Click to collapse
I tried Hasoon's toolkit but because it calls fastboot oem getidentifiertoken or whatever it is, the result is "waiting for device" which stops the process in its tracks even while the phone is in the white screen, where it got from responding to the prior command the toolkit sent which I believe is adb reboot-bootloader.
Currently I installed the 48mb "stripped" sync software from the link a few posts prior; do you think I should go with the non-stripped version?
zWiLLX said:
Gave it a shot; my win 8 laptop still has no ability to recognize the phone in device manager with HTC BMP, Sync Manager, or HTC Driver Installer.. which are the the 3 related programs I've installed.
The HTC driver recognizes the device (while in Fastboot) as My HTC, while the Universal Naked Driver calls it something different I believe, but neither are working to allow adb or fastboot to list the device, and both drivers have the same error as to why the device can't start: "a request for the USB BOS descriptor failed"
Click to expand...
Click to collapse
there is a thread around for people who are having issues with windows 8. the soulution for you problem is probably in that thread
---------- Post added at 11:01 AM ---------- Previous post was at 10:59 AM ----------
zWiLLX said:
Hey Ben Pope thanks for asking, yes it's in the white screen saying ***LOCKED*** in pink at the top. And yes I get into fastboot by adb reboot-bootloader most of the time because it's easier than the button pressing (which I've done also).
One weird thing I did notice is that "FASTBOOT" is shown with a red background when the device goes into the mode, however if I use the volume up/dn buttons and navigate, the text changes to "FASTBOOT USB", and persists that way until it's re-booted. Don't know if that matters, but at least if it's totally abnormal, there could be something funky going on in the firmware.
Thanks.
Click to expand...
Click to collapse
to use fastboot commands it needs to say fastboot usb
---------- Post added at 11:03 AM ---------- Previous post was at 11:01 AM ----------
zWiLLX said:
I tried Hasoon's toolkit but because it calls fastboot oem getidentifiertoken or whatever it is, the result is "waiting for device" which stops the process in its tracks even while the phone is in the white screen, where it got from responding to the prior command the toolkit sent which I believe is adb reboot-bootloader.
Currently I installed the 48mb "stripped" sync software from the link a few posts prior; do you think I should go with the non-stripped version?
Click to expand...
Click to collapse
when it says waiting for device you have to close that cmd screen and if your phone says fastboot usb it will start but you have to manually close the first window
hey SkinsFan, I tried the thread here and downloaded the ADB drivers to replace my Android 1.0 device. Other than those new drivers, I had done a lot of those steps. However, the PC says "The third party INF does not contain digital signature information", and rejects the ADB drivers linked from there, despite already allowing unsigned drivers in Windows settings.
Actually now I can't re-install the "naked driver" and matters are worse because the PC is now saying a hash file is missing for them, despite being installed an hour ago. So I guess I'll restart and try again, possibly unistalling HTC Sync since it was the new addition.
as far as closing the cmd window, this isn't doing anything to make the device recognized by the PC and it isn't therefore showing in adb devices or fastboot devices.
Still working on it thanks!
zWiLLX said:
hey SkinsFan, I tried the thread here and downloaded the ADB drivers to replace my Android 1.0 device. Other than those new drivers, I had done a lot of those steps. However, the PC says "The third party INF does not contain digital signature information", and rejects the ADB drivers linked from there, despite already allowing unsigned drivers in Windows settings.
Actually now I can't re-install the "naked driver" and matters are worse because the PC is now saying a hash file is missing for them, despite being installed an hour ago. So I guess I'll restart and try again, possibly unistalling HTC Sync since it was the new addition.
as far as closing the cmd window, this isn't doing anything to make the device recognized by the PC and it isn't therefore showing in adb devices or fastboot devices.
Still working on it thanks!
Click to expand...
Click to collapse
when your phone is in bootloader does it say fastboot usb at the top?
i think the links for drivers are for samsung devices he said its copied from his other thread. you need to get drivers from somewhere else
As I said, after "adb reboot-bootloader", left untouched, it says "FASTBOOT", but when I use a volume key to navigate just one click, it changes its tune to "FASTBOOT USB". I don't know whats going on with that ...
The samsung drivers are there but I believe Android ADB interface drivers can be universal , not sure, but now can't get back my Naked driver! working on that now
zWiLLX said:
As I said, after "adb reboot-bootloader", left untouched, it says "FASTBOOT", but when I use a volume key to navigate just one click, it changes its tune to "FASTBOOT USB". I don't know whats going on with that ...
The samsung drivers are there but I believe Android ADB interface drivers can be universal , not sure, but now can't get back my Naked driver! working on that now
Click to expand...
Click to collapse
Hey, I know your issue I can help on TeamViewer? Don't worry, I won't harm your PC
try pressing the power button while in bootloader. does it switch between hboot and fastboot usb?
MacHackz said:
Hey, I know your issue I can help on TeamViewer? Don't worry, I won't harm your PC
Click to expand...
Click to collapse
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
zWiLLX said:
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
Click to expand...
Click to collapse
yea it has to be plugged it to the computer first
zWiLLX said:
I am open to that! Could you give a preview on what you're thinking? Have teamviewer running. I will warn you I've lost ability to install the Universal Naked Driver via a "missing hash file" despite having it installed hours ago.
@skinsfanbdh yes. But again, it starts off intially (before a volume keypress) as "fastboot" not "fastboot USB", then changes.
Click to expand...
Click to collapse
Hey, I replied to your email PM me your TeamViewer info
MacHackz said:
Hey, I replied to your email PM me your TeamViewer info
Click to expand...
Click to collapse
Hey guys, Im experiencing similar problems. How exactly did you guys solve it?
Thanks
MacHackz said:
Hey, I replied to your email PM me your TeamViewer info
Click to expand...
Click to collapse
Hey, I´m experiencing the same problem here. Could you help me too?
Kenchinito said:
Hey, I´m experiencing the same problem here. Could you help me too?
Click to expand...
Click to collapse
Sorry for the very slow reply. Unfortunately, we won't know why HTC didn't play nicely with my Lenovo/Win8 laptop. However, I was quick to try a different older netbook I had lying around. At first, nothing happened, and I got used to the Sense UI enough to tolerate it.
But, I couldn't wifi tether and a few other unacceptable details, so I tried again last week with the same netbook that didn't seem to work the first time, and voila! Flawless. Maybe a reboot of that kicked it into gear, but both ADB and Fastboot were recognizing the HTC as a specific device, as opposed to the lenovo which found a ghost device with no name.
I am guessing too many android devices were installed and in the registry as USB devices, disorienting the PC, even though they were uninstalled, perhaps their drivers lingered as shared drivers. In theory I had S3 S4, HTC, possibly S2 and Motorola drivers all present.
The key is, keep the drivers on a folder on your phone with adb fastboot etc, and try a couple diff laptops. You'll know it worked when the device is recognized via "devices" with its unique number in both adb and fastboot.
Now running Revolution HD Google Play after trying CM 10.2 and Revolution HD Sense. CM did not work very smoothly with a lot of force crashes (navigation and music) and I can strongly recommend RevolutionHD google play edition.
Beware though, the first wipe takes out all the contacts and pictures etc, unfortunately, because I thought they would be spared.
So, pretty much the title. I'm pretty noobish when it comes to phones, and think i messed it up. I'm currently with Rogers, and what i did i unlocked it, and put the Google Play edition onto my phone, because i personally did not like the Blink Feed. So me being awful with phones, after the update came out for the Google Play 4.4 KitKat, I decided to update the firmware... Not realizing that it would mess my phone up... I have no rom to go back too, which would of probably saved this whole problem... Also another huge problem, my Phone does not want to be found by my computer... I would of just easily fixed it by flashing another rom, but i can't because it doesn't want to be recognized. Basically my phone right now boots up half way to the Google Logo, and then goes to a blue/green screen and stays there till i decide to turn it off.. I can get into bootloader, but that's as far much as i can do... Any help would be awesome, because i'm lost as far as it goes and decided to come here to post about it... Considering this is the best website for phones and whatnot... Thanks ahead of time guys!!
BUMP!
You have to fix your driver issues.. without it can't help. Try a different computer, usb port, usb cable, different htc driver package, anything to get your device detected when running
adb devices
or
fastboot devices (in bootloader/fastboot mode)
SaHiLzZ said:
You have to fix your driver issues.. without it can't help. Try a different computer, usb port, usb cable, different htc driver package, anything to get your device detected when running
adb devices
or
fastboot devices (in bootloader/fastboot mode)
Click to expand...
Click to collapse
The thing is, the only time it can recognize it is when it is in fastboot, it says it's connected but it on the phone but doesn't connect to the computer :/
Interesting... what about changing your HTC drivers. There are a few links floating around. Do you have Windows 7 or 8/8.1?
SaHiLzZ said:
Interesting... what about changing your HTC drivers. There are a few links floating around. Do you have Windows 7 or 8/8.1?
Click to expand...
Click to collapse
Sorry for super late reply, fell asleep. Also Windows 7, tried installing different drivers to no avail
Can't help if the phone refuses to respond to fastboot devices in bootloader mode.. or adb devices in custom recovery..
SaHiLzZ said:
Can't help if the phone refuses to respond to fastboot devices in bootloader mode.. or adb devices in custom recovery..
Click to expand...
Click to collapse
Says it's connected, [FastBoot USB] Also says it's connected via Device Manager, http://gyazo.com/f9dfe5d0ab3f184f3b085d776e765d2c But, does not appear in my computer. http://gyazo.com/b23dc0defe0d657a7a4aab8abcc2866e Wish i could get a picture of my phone as well, but you know
So I need help XDA fams. I am currently trying to update my N6 to 5.0.1. The issue i'm having is that my pc wont connect to my N6 while in bootloader. When in bootloader the usb seems to work fine, im assuming, since im getting "transfer mode: usb connected" on the very bottom of the phone screen. But when i adb and check to see if its connected, under "list of devices attached", nothing shows up.
When the N6 is booted up normally it works perfectly fine. I'm able to adb into my phone and it shows up under "list of devices attached".
Ive read around and know windows 8.1 and usb 3.0 drivers might be an issue. So I tried both usb google drivers and the universal naked drivers. I've uninstalled and reinstalled a crap load of times and nothing.
This thing is pissing me off. CAN ANYONE HELP OUT!
Adb is for Android. When you are in the boot loader, you use fastboot.
Try "fastboot devices"
El Daddy said:
Adb is for Android. When you are in the boot loader, you use fastboot.
Try "fastboot devices"
Click to expand...
Click to collapse
Wow lol. I feel stupid. Thanks man. Didnt know that.
But im still having an issue with it being recognized. I go into recovery mode and select the "apply update from adb". When trying to sideload the zip file i keep getting "error: device not found".
Any ideas?
jrforlife said:
Wow lol. I feel stupid. Thanks man. Didnt know that.
But im still having an issue with it being recognized. I go into recovery mode and select the "apply update from adb". When trying to sideload the zip file i keep getting "error: device not found".
Any ideas?
Click to expand...
Click to collapse
Check your device manager in Windows. Make sure it says "ADB Composite Interface" or something similar. If not, you'll have to install the drivers again.
Also, make sure you have the latest ADB package from the SDK.
I’m a noob when it comes to android adb but I'm an IT guy so what the hell I want 5.1.
I am following some directions on line on how to side load the OTA update seems easy, just a few commands and it should work. Here is what I'm doing and where I'm getting stuck any help?
Loaded Android SDK
Enabled Dev options, USB Debugging and OEM Unlock.
adb Devices - shows my device
adb reboot bootloader – restarts into the bootloader.
Select Recover Mode
Hold Power button, then press once the Volume Up button. To get Recovery Mode
This is where I get stuck, I'm reading I need to send the command “adb sideload <filename of update.zip>” but at this point ADB no longer sees my nexus 6? Nothing happens when I run this command and nothing is reported when I run ADB Devices?
Now I'm thinking drivers but I loaded the drivers? Can someone point me in the right direction?
I'm trying on a Windows 8 PC
Also when I'm looking at the device manager everything shows up fine until i enter the recover. At this point nothing shows up in device manager and when i resead the USB cable nothing happens no sound like im disconnecting something and reconnecting it, not device manager refresh, weird.
update! got it working.
So it turns out the device manager dose not show anything until you get into adb sideload options then the wrong driver is loaded and i had to manual pick Android adb driver. once i did this i was able to side load the ota update and now on 5.1.
You're plugged into the computer, correct? When you go into sideload mode, unplug the phone and plug it back it. It'll install an additional driver on the PC so that it can "see" the device in adb sideload mode. It took me longer than I'd care to admit to figure that **** out.
EDIT: Just reread your post and saw the last couple lines. You're still in the adb sideload mode on the phone, correct? So that it will trigger that driver installation. I'm on Win7 though, so there could be some Win8 stuff going on that I can't help with.
tom1226 said:
You're plugged into the computer, correct? When you go into sideload mode, unplug the phone and plug it back it. It'll install an additional driver on the PC so that it can "see" the device in adb sideload mode. It took me longer than I'd care to admit to figure that **** out.
EDIT: Just reread your post and saw the last couple lines. You're still in the adb sideload mode on the phone, correct? So that it will trigger that driver installation. I'm on Win7 though, so there could be some Win8 stuff going on that I can't help with.
Click to expand...
Click to collapse
Thanks you are right you have to be in the adb sideload options for the phone to show up in device manager and at this point it was not seeing the right driver, once i picked android adb driver i was able to update Thanks!
Awesome, glad it worked out for you!
Hello ,
I encountered a very weird problem with the usb port.
I have turned on USB-debugging but my phone doesn't show the connection dialog that indicates the state of phone connection.
I experienced this on a windows-10 machine and on an Ubuntu driven machine.
Cables are ok, drivers are ok. I tried to connect an old moto g 1st edition and the rsa dialog showed up and then I could choose if I wanted to recharge the battery or make an another type of connection.
Adb bridge also worked fine with my old phone, so I am sure the computers and the cables are fine.
So I gave an last try to my XT1805. Did a reboot into fastboot mode by using the start and volume down buttons, and to my big surprise the fastboot commands worked fine.
Well after that booted back in normal mode, backed up everything a did a factory reset.
Unfortunately that didn't solve the problem, adb doesn't work but fastboot is ok.
Hope somebody con give me some hints to solve the problem.
Forgot to state that the phone is on Oreo updated by OTA to the most recent version.
Regards
jm_sanders said:
Hello ,
I encountered a very weird problem with the usb port.
I have turned on USB-debugging but my phone doesn't show the connection dialog that indicates the state of phone connection.
I experienced this on a windows-10 machine and on an Ubuntu driven machine.
Cables are ok, drivers are ok. I tried to connect an old moto g 1st edition and the rsa dialog showed up and then I could choose if I wanted to recharge the battery or make an another type of connection.
Adb bridge also worked fine with my old phone, so I am sure the computers and the cables are fine.
So I gave an last try to my XT1805. Did a reboot into fastboot mode by using the start and volume down buttons, and to my big surprise the fastboot commands worked fine.
Well after that booted back in normal mode, backed up everything a did a factory reset.
Unfortunately that didn't solve the problem, adb doesn't work but fastboot is ok.
Hope somebody con give me some hints to solve the problem.
Forgot to state that the phone is on Oreo updated by OTA to the most recent version.
Regards
Click to expand...
Click to collapse
You need to use adb device, in order to use the command while the device is on.
For bootloader:- fastboot (command)
For power on device:- adb (command)
riyan65 said:
You need to use adb device, in order to use the command while the device is on.
For bootloader:- fastboot (command)
For power on device:- adb (command)
Click to expand...
Click to collapse
Forgot to state that 'adb devices' does not show any device connected.
As I said it's not a problem on the computer side as other Android phones are accessed correctly in ' adb shell'.
Regards
jm_sanders said:
Forgot to state that 'adb devices' does not show any device connected.
As I said it's not a problem on the computer side as other Android phones are accessed correctly in ' adb shell'.
Regards
Click to expand...
Click to collapse
To get adb device, you need to enable adb debugging and enable for your pc on phone
riyan65 said:
To get adb device, you need to enable adb debugging and enable for your pc on phone
Click to expand...
Click to collapse
Of course enabled as stated in my first post.
Regards