Related
Yes, I have searched... ALL OVER!
I have the new 1.6 sdk installed. I'm running the Cyanogen 4.1.999 ROM Donut/1.6. I have adb working. But, I can NOT get fastboot to recognize my device.
I have tried the following:
I have uninstalled the mass storage device - problem here is that Windows automatically installs the drivers again and I CAN'T stop it!
I have gone into the device manager/mass storage device and instructed it to update the drivers using the new 1.6 sdk. The message I received was that I was using the most up to date drivers.
I have found additional tips to solve this problem if I was running Linux. But, I can't find anything I haven't tried for Windows 64-bit....
You even title your question Q and don't post in the Q&A section?
Sorry, I didn't realize I was still in the Android Dev section when I started the thread. I was in a hurry.
If a Moderator will please move this to the Q&A section!
you are running fastboot from the SPL arent you...if not you need to boot up with (Cam+Power)
you need the engineering spl, hardspl, or haykuro spl for fastboot. you also need to make sure fastboot is active on the phone (make sure it says fastboot on it in the bootloader. if not, press the back button)
Yes, sir done all of the above. ADB works great. Boot into spl - shows Fastboot USB. I just get "waiting for device" in the command window. This should be a windows setting, driver install process, or something that either I am missing, doing wrong, or that I don't have installed. But, I have attempted everything I can find on the net. I worked at it for about three hours the other night. The wife was pissed b/c I was on the computer for so long.
Well is fastboot devices showing up under device manager?
it is most likely a driver error. note that if you have haykuro's spl, he has different drivers for it. you will need to get them from his google code page
ok I'm trying to get the PSGroove so what is fastboot? An app? Please explain
shaneaus said:
Yes, I have searched... ALL OVER!
I have the new 1.6 sdk installed. I'm running the Cyanogen 4.1.999 ROM Donut/1.6. I have adb working. But, I can NOT get fastboot to recognize my device.
I have tried the following:
I have uninstalled the mass storage device - problem here is that Windows automatically installs the drivers again and I CAN'T stop it!
I have gone into the device manager/mass storage device and instructed it to update the drivers using the new 1.6 sdk. The message I received was that I was using the most up to date drivers.
I have found additional tips to solve this problem if I was running Linux. But, I can't find anything I haven't tried for Windows 64-bit....
Click to expand...
Click to collapse
If you cannot get the sdk usb drivers to work for you when your entering into fastboot, try installing htc sync. It has additional drivers that may work. I have attached a driver pack that i use.
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.
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
When you boot in fastboot and connect your phone to pc does it shows fastboot usb if yes then it is recognised if no then you will have to download the drivers if HTC and install them
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes fastboot usb is shown and all fastboot commands work, its just that adb doesnt work when its in bootloader or recovery.
I did some more digging around and found that when the phone is connected while in recovery, the computer recognizes it as a "HTC MTP device"..and thats it. I cant upgrade the drivers of the said device or essentially do anything with it.
What am i missing?
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would start with these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
TygerByte said:
ADB should only work under Recovery. I found that with the last HTC driver it didn't install for when you are under Bootloader, Recovery, or Fastboot. I forgot what version actually worked the best but it might have been the 3 series drivers. Anyway while under Recovery you'll have to force the HTC drivers to install thru your Device Manager. It will not automagically detect them. I would startpage these drivers and try them out.
HTCDriver_4.2.0.001.exe
Universal_Naked_Driver_0.72.zip
HTCDriver3.0.0.007.exe
Click to expand...
Click to collapse
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Bhavpreet said:
Thanks for the reply, ive tried the first two drivers, work fine when the phone is booted, but no avail in recovery. The laptop shows the device connected as "My HTC" while in recovery, but im unable to use adb commands as adb doesnt connect to it. Ill try the third 3 series driver and post an update in a few.
UPDATE: wont install, im running windows 8 and it says this driver is not compatible with this operating system.
Click to expand...
Click to collapse
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
EddyOS said:
Does it say its offline? What do you actually see when using adb. As for the driver in Windows 8, you have to disable driver signature checking to use them. There is a thread in the Nexus 4 forum on how to do this, which is here:
http://forum.xda-developers.com/showpost.php?p=33463359&postcount=109
Click to expand...
Click to collapse
installed the 3 series driver, still the same problem. Heres some photos (which i should have attached originally) of whats happening.
The pictures are while the phone is normally booted, and then when the phone is in recovery.
Edit: Uninstalled all of the HTC drivers and devices inside the device manager, and only installed the Universal Naked Driver, the phone now shows up with a different name in device manager, but STILL does not work while in recovery.
Another pictures attached of how device manager looks with just the Universal Driver while in recovery.
anyone?
i have the same problem as u.. I tried both my missus Windowss PC now.. It used to detect it before. Now it suddenly doesn´t anymore. On my mac, same deal. Nothing detected.
Been googling around and i have found threads but they all end unsolved. ADB returns ADB devices blank. Kill-server or adb remount does nothing. in Fastboot USB its totally a ghost.
found any fixes?
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Me too...
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
bretula said:
Did anyone ever resolve this? I'm facing it now, having tried multiple recoveries. Previously was able to use adb fine. (I'm on a mac.)
Click to expand...
Click to collapse
In case this helps someone else: The reason I lost adb was that I'd installed the drivers on my mac for EasyTether. There's a note about this on the EasyTether FAQ page. When I disabled the EasyTether driver, I was able to use adb again.
TygerByte said:
I'm clueless too. I can only think to try other recoveries. Philz CWM comes to mind. I also uploaded the latest google usb drivers for you incase you want to try that out too. Google v7 USB drivers I think they are called. You'll probably have to force install them since they won't detect. Included the adb and fastboot from the SDK too. Last thing I can probably suggest is to try different USB port. Oh and TWRP too since it has the terminal built in it you could try starting up ADB from there.
Click to expand...
Click to collapse
have you tied all-in-one-tool-kit ???
Not sure if this will help, but I had an issue like this with my asus tab - adb worked fine in android os but not in twrp recovery, device manager showing it as other device.
While in recovery with device connected to pc I followed this how-to from the device manager part on and got adb working in recovery.
ADB not connecting
Bhavpreet said:
I have a nandroid backup.
Its too big to keep on the phone at all times
Therefore its been placed on my computer
And in the case i need it (boot-loop), how can i transfer the backup while in CWM?
ADB seems to be the simplest way, but adb cannot find my device when it is in the bootloader or in custom recovery.
Am i missing something? Or is there another way to solve this issue.
If anyone could help, id be very grateful.
Click to expand...
Click to collapse
Re Install HTC drivers manually, windows sees HTC until you boot into recovery mode and try to use ADB, It worked for me.
HTC One(M7) not recognized by adb
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
TonyDEV said:
Condition:
HTC One(M7) - rooted; s-ON; GPE ROM 4.3.1
Recovery - CWM
I have a similar problem with my HTC One(M7). I'm working mainly on a mac (OSX Maverick), but I have also tried using a PC (Windows 8). I accidentally wiped the data on the phone while in recovery, and now I have a phone that only boots to the bootloader and recovery. Since backups usually take a lot of memory, I kept all of mine on my computer. The simple fix I've been trying to do is sideload the ROM to the phone through adb, however adb does not find the device. I repeatedly get the "device not found". However the device is recognized in fastboot, and i always get the "fastboot USB" when it is connected. So I am unable to flash the ROM I need to the phone because it is unable to communicate with either computer. On the PC I made sure to have had the proper drivers, I downloaded HTC SYNC, and have tried updating them manually. However I always get the "error Code 43". The PC also does not recognize the device, so again I am unable to communicate with the device. Can I plz get any help, I have tried reading multiple forums, but have had no luck trying any solution. I would really appreciate any advise; Im desperate to fix the phone.
Click to expand...
Click to collapse
Take a look at this FAQ post and see if this doesn't help solve your problems. I would also recommend updating your CWM recovery to the latest.
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb... I can't install the naked drivers it just says that the file is incompatible
blu422 said:
having a similar problem. My system and everything is wiped all I have is TWRP 2.6.0.1 and I'm trying to end with cyanogenmod. theres no sdcard slot so my only option is an adb push through recovery. Adb doesnt recognize it, it just doesn't return anything in the list of devices when i type adb devices. in devmgmt it lists my phone as a disk drive... I have tried to update the drivers to the universal naked ones, but then windows says that it already found and installed the best driver software I have the T-Mobile variant but I thought I'd post here since this problem is more than likely not carrier specific and I didn't wanna add another thread. I can do fastboot just fine when in fastboot usb mode, but in recovery no adb...
Click to expand...
Click to collapse
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
thanks! did what you said i installed the drivers and the installation crashed the first time, then the second time it game me the option to remove or repair and i repaired and it worked thank you!!!
---------- Post added at 02:55 PM ---------- Previous post was at 02:37 PM ----------
clsA said:
your TWRP is very outdated update to 2.6.3.3
http://techerrata.com/browse/twrp2/m7
Install this driver then plug your phone in and enter TWRP
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
If device manager does not see your phone as My HTC under ADB Interface it's installed wrong.
Click to expand...
Click to collapse
so i have adb... but now it wont let me flash cyanogenmod... error executing updater binary in zip.... just fails.... help? updated to twrp 2.7.1.1. that fixed the problem
Hey guys I unlocked my boot loader and rooted once then I un-rooted and re-locked the boot-loader and now I am trying to do it again but I am having a problem. When I have my phone connected in debugging mode it shows up fine, I can use the code "adb devices" and it shows up but then when I load into the boot loader and go into fastboot and connect my phone to my computer Windows 8 says that it can not recognize the device this is on USB 2.0 it also says "device failed enumeration". On USB 3.0 I get a message that says "The device cannot start code 10". I have un-installed and then re-installed the sync manager and mulitple drivers to no avail. Please help.
Help
Anyone?
I had this before. It's a glitch I think but after keep trying I finally got it to work and really I don't know how to fix it.
What's your hboot version? Battery full? Try a different computer? Have a linux live cd?
Sent from my HTC One using xda app-developers app
Tw1tchy said:
I had this before. It's a glitch I think but after keep trying I finally got it to work and really I don't know how to fix it.
What's your hboot version? Battery full? Try a different computer? Have a linux live cd?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yea I've tried two different computers I did have luck with one but I got as far as "fastboot flash unlocktoken Unlock_code.bin" and get an error that says that it cannot load the "Unlock_code.bin". My hboot version is 1.44. My battery has been full all day due to the fact that its been connected to a computer all day http://forum.xda-developers.com/images/smilies/tongue.gif
arenglish said:
Yea I've tried two different computers I did have luck with one but I got as far as "fastboot flash unlocktoken Unlock_code.bin" and get an error that says that it cannot load the "Unlock_code.bin". My hboot version is 1.44. My battery has been full all day due to the fact that its been connected to a computer all day http://forum.xda-developers.com/images/smilies/tongue.gif
Click to expand...
Click to collapse
Well lets kinda rule things out. It shouldn't be your computer hardware or fastboot files because you tried this on multiple computers. Now what drivers are you using on each computer? Did you tried other micro usb cords? What shape is your micro usb slot on your device (looking at mine right now its kinda dirty)?
Complete those and it should tell you if its a connection problem or not. Otherwise we can partially assume its the software on your phone.
Tw1tchy said:
Well lets kinda rule things out. It shouldn't be your computer hardware or fastboot files because you tried this on multiple computers. Now what drivers are you using on each computer? Did you tried other micro usb cords? What shape is your micro usb slot on your device (looking at mine right now its kinda dirty)?
Complete those and it should tell you if its a connection problem or not. Otherwise we can partially assume its the software on your phone.
Click to expand...
Click to collapse
I have been using drivers that didn't seem to work(some that I got off some thread here) but those didn't work so I uninstalled those and then uninstalled and then re-installed HTC Sync. I have used three different cables and my micro usb slot seems to be in fine condition it doesn't seem to be that dirty.
What happens when you try
fastboot erase cache
Does the command work or fail?
Sent from my HTC One using xda app-developers app
Tw1tchy said:
What happens when you try
fastboot erase cache
Does the command work or fail?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I would assume this would not work as the op states that his device is not recognised in fastboot.
bobsie41 said:
I would assume this would not work as the op states that his device is not recognised in fastboot.
Click to expand...
Click to collapse
Incorrect, OP has got as far as loading the unlock code but fails at fastboot.
Sent from my HTC One using xda app-developers app
Ok so with one laptop when I have my phone in debugging mode and are in the sense OS the phone is detected using the code "adb devices" but when I go to the bootloader and put the phone in fastboot mode it is unrecognized. On my other laptop it is recognized in fastboot using the code "fastboot devices". I have not used the clear cache yet I will try it later.
Sent from my HTC One using xda app-developers app
arenglish said:
Ok so with one laptop when I have my phone in debugging mode and are in the sense OS the phone is detected using the code "adb devices" but when I go to the bootloader and put the phone in fastboot mode it is unrecognized. On my other laptop it is recognized in fastboot using the code "fastboot devices". I have not used the clear cache yet I will try it later.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I'm in the exact same place as you on the first computer, as soon as I boot my phone into fastboot my computer no longer recognizes it and I've tried at least 5 different drivers and the HTC sync thing to help with the driver, what is wrong??
Sent from my HTC One using Xparent Cyan Tapatalk 2
Tw1tchy said:
What happens when you try
fastboot erase cache
Does the command work or fail?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
When I try that command all that happens is it says "waiting for device" and stays like that.
arenglish said:
When I try that command all that happens is it says "waiting for device" and stays like that.
Click to expand...
Click to collapse
Have you updated your firmware? If so, make sure your sdk is the latest version.
Use usb 2.0, usb 3.0 is known to cause problems.
Un-install htc sync but not the drivers.
Before attempting commands, eject htc sync drive from My PC.
Let me know how you get on.
bobsie41 said:
Have you updated your firmware? If so, make sure your sdk is the latest version.
Use usb 2.0, usb 3.0 is known to cause problems.
Un-install htc sync but not the drivers.
Before attempting commands, eject htc sync drive from My PC.
Let me know how you get on.
Click to expand...
Click to collapse
Ok, my firmware is 1.26.502.12 which I believe is the latest for AT&T, I've switched from USB 3.0 to 2.0 still not working in fastboot. I re-installed the SDK yesterday so I don't think there should be an update. I have un-installed HTC sync but not HTC Driver Installer and still after doing all of this the device shows up when it is in the OS but not in fastboot. Also when I reboot my device USB debugging keeps disabling itself.
Any updates to this? I'm running Windows 8, have the HTC drivers / Sync installed.. The phone connects fine while in Windows. But is unrecognized when the phone is in bootloader. This is driving me nuts. I do not have access to another PC. I'm sure someone has this working.
Edit: usb 3.0 ports working after following the plugable.com method for windows 8 usb 3 host controller fix.
born_fisherman said:
Any updates to this? I'm running Windows 8, have the HTC drivers / Sync installed.. The phone connects fine while in Windows. But is unrecognized when the phone is in bootloader. This is driving me nuts. I do not have access to another PC. I'm sure someone has this working.
Edit: usb 3.0 ports working after following the plugable.com method for windows 8 usb 3 host controller fix.
Click to expand...
Click to collapse
Thanks... tried that method worked like a charm.
Okay, I'm not sure exactly what happened, but long story short:
I flashed a rom and instead of getting a new rom on my phone, the phone rebooted into fastboot. I tried to enter recovery... no dice. Somhow my recovery uninstalled itself. So now I'm stuck with a phone with no rom installed, and no recovery installed. Frustration.
First step would be to reinstall recovery right? But when attempting to use fastboot flash command, i get stuck at <waiting for device>. I have the htc phone driver installed, and it's recognizing the phone is plugged into the pc in device manager. The phone screen even says FASTBOOT USB. I have no idea why it's not flashing. The recovery i'm trying to flash is twrp, the latest sprint build. It's the same one I had before it somehow uninstalled itself.
Please help out guys?
Thanks.
What phone?
Sent from my SM-P600 using Tapatalk
Details
Sorry for not making this clear earlier: the phone is the HTC One, Sprint. Just the regular one.
I'm really in a bind in here. Right now I have no recovery or rom to work with, and the only rom on my phone is the one that caused all this mess. I'm going to have to sideload a rom, but right now I need to get twrp on there. For some reason, it still won't get on, i'm still stuck at <waiting for device>. The phone is coming up on device manager as "My htc", so it's definitely plugged into the computer correctly. I have no idea what's going on.
Smells like bad usb drivers.
What does this command say:
fastboot devices
The result should be your device id. It not, your usb drivers are not working.
If it does work, I would RUU back to stock. Look at the faq page for links.
tdhite said:
Smells like bad usb drivers.
What does this command say:
fastboot devices
The result should be your device id. It not, your usb drivers are not working.
If it does work, I would RUU back to stock. Look at the faq page for links.
Click to expand...
Click to collapse
The command doesn't return anything. I guess this means my drivers aren't working. This doesn't make any sense though (pun intended): the phone is being recognized in device manager under "Android USB Devices" as "My HTC" via HTC's drivers that come with htc sync. I already downloaded htc sync and uninstalled it, keeping the driver files. This is really wierd stuff, any idea on how to get the drivers working? I'm sure if I could just get a recovery on there, resolving the issue wouldn't be too difficult via adb. Thanks.
Sounds like you are running Win 8.1.
Your phone won't be recognized if your hboot is 1.44
BD619 said:
Sounds like you are running Win 8.1.
Your phone won't be recognized if your hboot is 1.44
Click to expand...
Click to collapse
I am running 8.1, but my hboot is 1.55.
There it's a specific question in this in the faq page, particularly 8.1 and usb. Did you look at that?
See this: http://forum.xda-developers.com/showthread.php?p=49038239
EXDetonator said:
I am running 8.1, but my hboot is 1.55.
Click to expand...
Click to collapse
Did you install HTC sync? You need it for the proper drivers
Fixed! ...halfway
Alright guys, I flashed a recovery.
I actually started off with HTC's drivers, but they were causing the issue.
Thankfully the information the thread tdhite posted had a link to a working driver.
Thanks everyone! Now I need to sideload a rom.