Related
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.
Hey guys!
In advance I'm sorry for asking something that has probably been asked many times before, but I'm unable to find the right answer.
Okay let's start at the beginning. My HTC one with an unlocked bootloader on stock started to display a very irritating bug in that sometimes the screen would not rotate and was stuck in landscape mode. Nothing would help nor rebooting, nor calibrating the sensor. Only booting into the bootloader would somehow help.
Until it did not.
I tried a factory reset, which did not help and then tried just wiping Dalvik and Cache, which did not help too.
Then I tried wiping Data and System, which I now know was very stupid.
The current problem is that I can't figure out how to send a new ROM to my HTC one using adb, when typing adb devices the device does not show up.
My computer does see the device, listed under Android USB devices ad My HTC. I think Fastboot too, recognized the device, because I am able to get the Identifier token.
I have installed the drivers and installed HTC Sync manager. I have restarted my Pc multiple times and changed the USB port the device is connected to.
I too, tried mounting the USB, but either I'm doing it wrong, or it does not work.
Hope one of you can help me! I've been at this all day long...
Adb commands only work when you're booted in the rom or recovery. Fastboot uses fastboot commands. Do you have a custom recovery? If so, you can adb sideload a rom. If not, you can fastboot flash a custom recovery assuming your bootloader is unlocked. You may have mentioned it in your post I just can't remember. Good luck!
Sent from my HTC One using xda app-developers app
Thanks for the help!
Yes, I unlocked my bootloader and have twrp installed.
I think I have narrowed down the problem: that my device is not recognized by the computer in twrp.
When in fastboot, My computer does recognize the device, listed as an HTC one, so the drivers are not the problem.
When booting into recovery, me computer only recognizes the phone for about 3 seconds, when it dissapears.
I have been able to see the device in Adb (using Adb devices).
What could I do? Adb sideload does not work because the computer does not recognize the device.
Hi,
You're on Windows? If yes which version?
Windows 7, but if needed I do have access to a win 8 PC as well.
All x64 by the way.
Ok, maybe take a look here if you use USB 3.0?: [FIX]Fastboot problems on Windows 8 x64 with USB 3.0? Solution inside.
It might work on Windows 7 too, there is a link for the drivers for x64.
Maybe using a toolkit to use ADB/fastboot? Take a look here:
[TOOL]HTC One (M7) All-In-One Toolkit V3.1
[TOOL]HTC One (M7) AIO Toolkit | v1.4
Okay, from now on I'll only use USB 2.0.
I tried these two toolkits, but they suffer the same problem as me in that in order for adb sideload to work the device has to be recognized for longer than 3s after booting into recovery.
I just bought a female-female USB adapter, hopefully installing a rom from a usb stick will work
Ofcourse help would still be greatly appreciated as i will have to wait for over a week till the USB adapter arrives.
I know there's a few threads already about this issue and believe me i looked at them all..i didn't find an answer yet.
It all started a few weeks ago(on my Mac with Mavericks) when i was trying to transfer music,I was using htc sync manager as i did many times before without problems,
then decided to use Android file transfer..Didn't work...so i uninstalled both and re-installed htc sync manager and that didn't work as well.
So i went to windows (8.1) installed countless times the latest HTC drivers,SDK (adb and fastboot) not showing up, keeps saying waiting for device.
Same thing with windows Vista(lol i know) and win 7 ultimate and another mac as well and nothing...even tried 4 different cables.
of course USB Debugging is enabled and tried different roms doing a clean install with same results.
If it is hardawre failure i would just return the device to stock and get it fixed, but i can't because I'm S-ON Rooted( to return to stock i need S-off) I can't get S-off if Fastboot and adb don't see my device.
M7_ul pvt ship S-on
hboot 1.54.0000
radio- 4A.17.3250.14
os-2.24.980.2
Jul.9-2013
I don't usually post because i like to resolve the problems on my own, but this time I'm stuck any help is greatly appreciated.
digitallsin said:
I know there's a few threads already about this issue and believe me i looked at them all..i didn't find an answer yet.
It all started a few weeks ago(on my Mac with Mavericks) when i was trying to transfer music,I was using htc sync manager as i did many times before without problems,
then decided to use Android file transfer..Didn't work...so i uninstalled both and re-installed htc sync manager and that didn't work as well.
So i went to windows (8.1) installed countless times the latest HTC drivers,SDK (adb and fastboot) not showing up, keeps saying waiting for device.
Same thing with windows Vista(lol i know) and win 7 ultimate and another mac as well and nothing...even tried 4 different cables.
of course USB Debugging is enabled and tried different roms doing a clean install with same results.
If it is hardawre failure i would just return the device to stock and get it fixed, but i can't because I'm S-ON Rooted( to return to stock i need S-off) I can't get S-off if Fastboot and adb don't see my device.
M7_ul pvt ship S-on
hboot 1.54.0000
radio- 4A.17.3250.14
os-2.24.980.2
Jul.9-2013
I don't usually post because i like to resolve the problems on my own, but this time I'm stuck any help is greatly appreciated.
Click to expand...
Click to collapse
can you post a screen shot of android devices in device manager on the windows PC.
also were these all different computers ? and none see your phone at all ?
you do realize adb devices only works when the phone is in recovery or booted to android and fastboot devices only works when in the bootloader with fastboot usb showing
Thanks for the reply
Nothing comes up in device manager in any of the computers,
Also I was able to run the command "adb devices" in Mac or Windows and it would show a number... Not anymore.
Now just says waiting for device....
And fastboot doesn't work ither in"hboot' or bootloader
digitallsin said:
Thanks for the reply
Nothing comes up in device manager in any of the computers,
Also I was able to run the command "adb devices" in Mac or Windows and it would show a number... Not anymore.
Now just says waiting for device....
And fastboot doesn't work ither in"hboot' or bootloader
Click to expand...
Click to collapse
Have you tried a different micro usb cable? I have like 5 different cables running around my house and only one allows my phone to be recognized by adb through my pc. Try that.
telegraph0000 said:
Have you tried a different micro usb cable? I have like 5 different cables running around my house and only one allows my phone to be recognized by adb through my pc. Try that.
Click to expand...
Click to collapse
well so far i have tried 6-7 cables of different type from friends and of mine, but only one is the original cable from HTC, and none of them work...i can charge, but that's about it. ( and that stupid message i get when i plug it in the computer...Slow charge,The connected charger will take longer to charge...blah blah blah)
i can only think of a corrupted file of some sort, but that wouldn't make sense because i did a clean install many times. Unless new roms (kikat) require USB 3? uhmm i doubt it.
I'll just keep trying different cables
Any suggestions are welcome.
digitallsin said:
well so far i have tried 6-7 cables of different type from friends and of mine, but only one is the original cable from HTC, and none of them work...i can charge, but that's about it. ( and that stupid message i get when i plug it in the computer...Slow charge,The connected charger will take longer to charge...blah blah blah)
i can only think of a corrupted file of some sort, but that wouldn't make sense because i did a clean install many times. Unless new roms (kikat) require USB 3? uhmm i doubt it.
I'll just keep trying different cables
Any suggestions are welcome.
Click to expand...
Click to collapse
sounds more like a hardware problem with the usb port on your phone, try cleaning it (maybe using a compressed air can or similar) to get any debris out.
nkk71 said:
sounds more like a hardware problem with the usb port on your phone, try cleaning it (maybe using a compressed air can or similar) to get any debris out.
Click to expand...
Click to collapse
lol funny you should say that because that's exactly what i did tonight but still not working...but i was reading somewhere else that it could be a corrupted HBOOT, but i have no idea how to change that..
I'll keep you updated just in case some other people have the same issue
digitallsin said:
lol funny you should say that because that's exactly what i did tonight but still not working...but i was reading somewhere else that it could be a corrupted HBOOT, but i have no idea how to change that..
I'll keep you updated just in case some other people have the same issue
Click to expand...
Click to collapse
if hboot was corrupted, you would have a brick on your hands; and since you're S-On, no way you can corrupt it.
hboot 1.44/1.54 don't play nice with Windows 8.1, but Windows 7 and Mac shouldn't have any issues.
If you really want to try another way, just make yourself an Ubuntu 12.04 (32bit) Live USB, boot from that, install adb & fastboot (you can check my guide in the FAQ section on how to do that)
then try
sudo fastboot devices in bootloader
adb devices in custom recovery
adb devices in booted up ROM (with USB debugging enabled)
nkk71 said:
if hboot was corrupted, you would have a brick on your hands; and since you're S-On, no way you can corrupt it.
hboot 1.44/1.54 don't play nice with Windows 8.1, but Windows 7 and Mac shouldn't have any issues.
If you really want to try another way, just make yourself an Ubuntu 12.04 (32bit) Live USB, boot from that, install adb & fastboot (you can check my guide in the FAQ section on how to do that)
then try
sudo fastboot devices in bootloader
adb devices in custom recovery
adb devices in booted up ROM (with USB debugging enabled)
Click to expand...
Click to collapse
Ok I'll try that tomorrow. Thanks for the help
nkk71 said:
if hboot was corrupted, you would have a brick on your hands; and since you're S-On, no way you can corrupt it.
hboot 1.44/1.54 don't play nice with Windows 8.1, but Windows 7 and Mac shouldn't have any issues.
If you really want to try another way, just make yourself an Ubuntu 12.04 (32bit) Live USB, boot from that, install adb & fastboot (you can check my guide in the FAQ section on how to do that)
then try
sudo fastboot devices in bootloader
adb devices in custom recovery
adb devices in booted up ROM (with USB debugging enabled)
Click to expand...
Click to collapse
Unfortunately i get nothing....but i must say..only once on my phone it said USB Connected tap to change settings, if clicked on it gave me the option of choosing a tethering choice (bluetooth,wifi,....) with no errors, i thought it was fixed.Then i run the commands and nothing:crying:
btw I'm liking Ubuntu...now i got 3 operating systems at boot:good:
If you got anymore ideas please, I'm all ears:fingers-crossed:
1.sudo fastboot devices in bootloader <=== i get nothing back
2.adb devices in custom recovery
[email protected]:~/android-sdk-linux/platform-tools$ sudo ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[email protected]:~/android-sdk-linux/platform-tools$
3.adb devices in booted up ROM (with USB debugging enabled)[/QUOTE]
[email protected]:~/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached
[email protected]:~/android-sdk-linux/platform-tools$
digitallsin said:
Unfortunately i get nothing....but i must say..only once on my phone it said USB Connected tap to change settings, if clicked on it gave me the option of choosing a tethering choice (bluetooth,wifi,....) with no errors, i thought it was fixed.Then i run the commands and nothing:crying:
btw I'm liking Ubuntu...now i got 3 operating systems at boot:good:
If you got anymore ideas please, I'm all ears:fingers-crossed:
1.sudo fastboot devices in bootloader <=== i get nothing back
2.adb devices in custom recovery
[email protected]:~/android-sdk-linux/platform-tools$ sudo ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
[email protected]:~/android-sdk-linux/platform-tools$
3.adb devices in booted up ROM (with USB debugging enabled)
Click to expand...
Click to collapse
[email protected]:~/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached
[email protected]:~/android-sdk-linux/platform-tools$[/QUOTE]
sounds like a hardware issue: phone usb port and/or pc usb port and/or cable
nkk71 said:
[email protected]:~/android-sdk-linux/platform-tools$ ./adb devices
List of devices attached
[email protected]:~/android-sdk-linux/platform-tools$
Click to expand...
Click to collapse
sounds like a hardware issue: phone usb port and/or pc usb port and/or cable[/QUOTE]
Im having the same problem i got the computer to see the phone because i went under device manager and updated the driver manually but i still cant get adb to see my device
getmoneygreen said:
Im having the same problem i got the computer to see the phone because i went under device manager and updated the driver manually but i still cant get adb to see my device
Click to expand...
Click to collapse
is it showing up as My HTC? like in FAQ #2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
also adb will only work in custom recovery
or a booted ROM with USB Debugging enabled
EDIT: and these drivers here seem to be working for a lot of people: http://forum.xda-developers.com/showthread.php?t=2588979
Same problem
digitallsin said:
I know there's a few threads already about this issue and believe me i looked at them all..i didn't find an answer yet.
It all started a few weeks ago(on my Mac with Mavericks) when i was trying to transfer music,I was using htc sync manager as i did many times before without problems,
then decided to use Android file transfer..Didn't work...so i uninstalled both and re-installed htc sync manager and that didn't work as well.
So i went to windows (8.1) installed countless times the latest HTC drivers,SDK (adb and fastboot) not showing up, keeps saying waiting for device.
Same thing with windows Vista(lol i know) and win 7 ultimate and another mac as well and nothing...even tried 4 different cables.
of course USB Debugging is enabled and tried different roms doing a clean install with same results.
If it is hardawre failure i would just return the device to stock and get it fixed, but i can't because I'm S-ON Rooted( to return to stock i need S-off) I can't get S-off if Fastboot and adb don't see my device.
M7_ul pvt ship S-on
hboot 1.54.0000
radio- 4A.17.3250.14
os-2.24.980.2
Jul.9-2013
I don't usually post because i like to resolve the problems on my own, but this time I'm stuck any help is greatly appreciated.
Click to expand...
Click to collapse
Did you ever get Fastboot working to display your device? I tried 3 different OSs, 3 different cables and every possible driver out there. I can push files back and forth when connect to pc in normal operating mode. I can do an "adb reboot bootloader" command and it will reboot to bootloader, My device manager shows the phone without yellow exclamation mark, but when I issue "adb devices" it successfully starts server but doesn't list device????? Losing my mind. I need to update my radio and firmware desperately.
daddygene said:
Did you ever get Fastboot working to display your device? I tried 3 different OSs, 3 different cables and every possible driver out there. I can push files back and forth when connect to pc in normal operating mode. I can do an "adb reboot bootloader" command and it will reboot to bootloader, My device manager shows the phone without yellow exclamation mark, but when I issue "adb devices" it successfully starts server but doesn't list device????? Losing my mind. I need to update my radio and firmware desperately.
Click to expand...
Click to collapse
Mine was hardware problems I ended up taking it back to Optus (Australia) and they gave me a refurbished one which had the exact same problem...sent it in again and got another one back, looks to be ok now but I'm very disappointed with HTC so I gave it to my wife and got myself the Galaxy s5 and didn't look back. sorry I can't be of any help
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
pannic514 said:
I've been trying to solve this for a while now and cant seem to get it to work.
I have adb and fastboot installed on the computer.
When I run the cmd window, I can get a recognition from adb when I'm in recovery mode, but as soon as I run <adb reboot bootloader> the phone goes into bootloader, disconnects temporarily from the computer and reconnects.
When I go into devices on the computer I can see that the computer see's it. It recognizes it as my HTC although it shouldn't right?
When I come back to my cmd window I try to run fastboot commands with no success. <fastboot devices> gives me a blank line and its ready for the next command.
I looked around and saw that a lot of people dint have the right cables, drivers for the phone or dint restart they're computer.
I have done it all. I re-downloaded the drivers I think 10 times in vane.
Any help would be appreciated thx
OS on phone is no longer there I lost it. dont know how.
OS on computer is windows 10 64 bit
Click to expand...
Click to collapse
Try it on Windows 7 or update your drivers.
http://androidxda.com/download-htc-usb-drivers
http://www.andromods.com/fix-troubleshoot/issue-fastboot-waiting-for-device-windows-81-fixed.html
Fastboot and adb don't work on Windows 10 yet. That's why I didn't upgrade from Windows 7 ?
Hello, I just wanted to unlock LG V40 official way/pie OS on it.
But I was for quite a long time stuck on that my Windows 10 were not able
to recognize the LG V40 in fastboot mode - so I was unable to perform fastboot commands...
Which drivers for fastboot do you use? After a long time I was able to find this thread https://forum.xda-developers.com/t/guide-v20-fastboot-access-in-windows.3491439/
but this seems absurd to me, that one need to look to LG V20 thread to find working fastboot drivers for LG from some mysterious package that miraculously works.
I am really glad that this works, but how to find/from where to get working fastboot drivers for my own and not to be dependent on
somebody, who creates some driver package, that maybe will not work after some time?
I used to normally get to the fastboot of my LG G7 so I was totally confused when I found out, that my old driver folder which I used to unlock the bootloader of LG G7 suddenly does not work... what happened? Did Windows 10 stop being compatible with fastboot drivers from LG?
Is it some legacy google fastboot drivers that work?
Or is it some general Qualcomm fastboot driver I need to look for?
Thanks to anyone willing to share knowledge about this.
I can't really help much, although I've gotten adb / fastboot to work on win 8.1 and 10.
The really unusual thing I found was that under windows, even after you've gotten the device to work with adb, you STILL have to find the device in device mgr, when connected with fastboot, and the SELECT the same driver AGAIN to work with fastboot.
I hate windows. I only have it for things like qfil. Linux is so much easier. Anyway, sorry for the rant. But, in my case, to get fastboot to work, find the indicator with the android ! mark and then assign the same adb driver for it.
I didn't have to use any specific one off package, it worked with (it was either lg or google adb usb driver - I'm not booted in windows to look at the mo).
cheers
AsItLies said:
I can't really help much, although I've gotten adb / fastboot to work on win 8.1 and 10.
The really unusual thing I found was that under windows, even after you've gotten the device to work with adb, you STILL have to find the device in device mgr, when connected with fastboot, and the SELECT the same driver AGAIN to work with fastboot.
I hate windows. I only have it for things like qfil. Linux is so much easier. Anyway, sorry for the rant. But, in my case, to get fastboot to work, find the indicator with the android ! mark and then assign the same adb driver for it.
I didn't have to use any specific one off package, it worked with (it was either lg or google adb usb driver - I'm not booted in windows to look at the mo).
cheers
Click to expand...
Click to collapse
Thank you for your reply. I didn't know that the same driver for ADB works for fastboot... I implicitly assumed that driver for fastboot must be different.
The "Android" device in device manager was what was driving me crazy. So thank you for this information, I will probably test
if this works on my other PC.