Hello,
I got a strange problem: my phone does not accept adb or fastboot commands sent from my pc anymore. The screen says FASTBOOT when connected in fastboot mode to the pc, but the USB appears only after I move the cursor up or down (push the volume button up or down).
The command line on windows states "Waiting for device...". The driver seems broken. In Device Manager (Windows) it says "Other devices -- Android Phone" with an exclamatin mark. A driver update fails.
I am running CM alpha 12 on a HTC One S (S4). The phone was not connected to my pc while on stock. The Android SDK is installed on the pc and up to date.
The phone is running fine besides the lack of usb access in any way. Charging works fine.
Any suggestions appreciated.
Burkhard
I had the same issue too. I wantet to push a recovery and my pc could not find my device. I reinstalled htc sync and then found the drivers in c:/programs/htc/sync drivers
Sent from my HTC VLE_U using xda premium
SOLVED
I'm delighted it worked. Thank you. I should have tried this before, but I did not think of installing HTC sync. Will keep that in mind.
hello
i have got a seriuos problem,i just booted my phone to fastboot to flash a boot.but when i rebooted to bootloader fastboot usb just dissapears.when i used cmd using adb it says waiting for the device....
anyone please help me from this problem:cryinglease.....................
my device is htc one v,
this problem occurs when am using cm10,and i want to use my stock rom again.
please help me to solve this problem:crying:
udhayababu said:
hello
i have got a seriuos problem,i just booted my phone to fastboot to flash a boot.but when i rebooted to bootloader fastboot usb just dissapears.when i used cmd using adb it says waiting for the device....
anyone please help me from this problem:cryinglease.....................
my device is htc one v,
this problem occurs when am using cm10,and i want to use my stock rom again.
please help me to solve this problem:crying:
Click to expand...
Click to collapse
You have the HTC One V? These forums are for the One S. They are more likely to give better advice
Please need help....!!!!
I accidentally formatted my internal storage , cache , data, system and everything.
I cannot able to mount the USB and not even fastboot as it is saying waiting for device. My bootloader is the only thing thats working, not even my philz recovery is of no use . adb is not recognizing my phone . please help
Please let me know about any solution for the problem
Has your problem solved ir not...???
herzbert said:
Hello,
I got a strange problem: my phone does not accept adb or fastboot commands sent from my pc anymore. The screen says FASTBOOT when connected in fastboot mode to the pc, but the USB appears only after I move the cursor up or down (push the volume button up or down).
The command line on windows states "Waiting for device...". The driver seems broken. In Device Manager (Windows) it says "Other devices -- Android Phone" with an exclamatin mark. A driver update fails.
I am running CM alpha 12 on a HTC One S (S4). The phone was not connected to my pc while on stock. The Android SDK is installed on the pc and up to date.
The phone is running fine besides the lack of usb access in any way. Charging works fine.
Any suggestions appreciated.
Burkhard
Click to expand...
Click to collapse
Hay dear has your problem solved.??
If solved then how.by which method pleas tell me because i am facing the same problem. Thanks in advance
I don't know how he solved but this guide on xda worked for me!
http://forum.xda-developers.com/showthread.php?t=2858337
[GUIDE] Fix Fastboot on Windows 8.1 [Latest fix as of 8/25/14]
Sent from my One S using XDA Free mobile app
faisal459459 said:
Hay dear has your problem solved.??
If solved then how.by which method pleas tell me because i am facing the same problem. Thanks in advance
Click to expand...
Click to collapse
Hello Faisal,
I (re-)installed HTC sync software (as I said in post #3). That is all of the story.
Hope this solves your problem too.
I relocked my bootloader and tried running a RUU but it keeps telling me that my phone is not connected. I'm using parallels for mac, I installed the drivers and I notice that when i connect the phone it doesn't say "fastboot usb" but when i push volume down is changes yet it still is unable to detect the phone. I installed the htc drivers but when I connect the phone is shows i dont have the drivers for " HTC Remote NDIS based device"
Could this be because im using parallels instead of a full windows pc?
please help, this is my very first android device and im scared I already ruined it
Yeah parallels is touchy. It works in VMware. Make sure in vm settings the usb device for the phone is set to always available to windows. If it is set to ask then it can lose connection.
Ok, Ill give a try.
I still have another problem. When I try to install the htc drivers, I get an error saying device not found. How am I able to install the drivers now?
I found the best way to get the driver installed is to install HTC sync
Thanks for the replies gunnyman, I have one last problem and hopefully theres a fix. I have a low battery and unable to flash the RUU. Is there a fix?
Is there battery actually low? Just shut down the phone and charge it up.
When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?
Jaykelso said:
When I plug in the phone, it boot up on its own into fastboot and it says "fastboot ac". Is it charging?
Click to expand...
Click to collapse
Sorry. No idea. Sounds like it.
Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.
chriscerv90 said:
Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2066805
Hope this helps.
AT&T HTC OneX
Android 1.1.1
ViperXL
Venomtester said:
http://forum.xda-developers.com/showthread.php?t=2066805
Hope this helps.
AT&T HTC OneX
Android 1.1.1
ViperXL
Click to expand...
Click to collapse
Thanks for the reply. That linked me to all the threads I went through by searching myself. I was just taking a stab to see if anyone had a new solution. Weird that this just started for me. VERY FRUSTRATING.
Windows XP makes life easier
chriscerv90 said:
Thanks for the reply. That linked me to all the threads I went through by searching myself. I was just taking a stab to see if anyone had a new solution. Weird that this just started for me. VERY FRUSTRATING.
Click to expand...
Click to collapse
Did you try searching resolutions at Microsoft?
http://technet.microsoft.com/en-us/library/cc725873(v=WS.10).aspx
AT&T HTC OneX
Android 4.1.1
ViperXL
Venomtester said:
Did you try searching resolutions at Microsoft?
http://technet.microsoft.com/en-us/library/cc725873(v=WS.10).aspx
AT&T HTC OneX
Android 4.1.1
ViperXL
Click to expand...
Click to collapse
Thanks for the tip lol
I tried similar steps.
I did a fresh install of windows too. I know I am a little obsessive. Still can't get the dang thing to be recognized in fastboot.
chriscerv90 said:
Thanks for the tip lol
I tried similar steps.
I did a fresh install of windows too. I know I am a little obsessive. Still can't get the dang thing to be recognized in fastboot.
Click to expand...
Click to collapse
I know this may sound silly at this point but did you try moving it to a different usb port? I have seen that work before.
AT&T HTC OneX
Android 4.1.1
ViperXL
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
I had to use a different Micro-USB cable to get it work. Try that.
Yeah I actually have tried all those steps. Thanks for the replies guy. I check out that application.
I'm starting to think something is wrong with my HOX
Sent from my HTC One X using xda app-developers app
DvineLord said:
try using this application if you think your device drivers are dirty but installed correctly for usb devices
USBDeview just uninstall whatever devices you want reinitialized especially since they can change even with rom changes so it is good to clear some old ones out by sorting them based on Last Plug/Unplug Date.
Click to expand...
Click to collapse
This FREAKING WORKED!!!!!!!!!! HAHAHA Thanks man ... I've only had 2 hours of sleep trying to fix this stupid problem... I owe you one man. :highfive:
glad you got it fixed, check out his other apps they are life savers and they work how "real" windows apps should work.
I have the same problem
chriscerv90 said:
This FREAKING WORKED!!!!!!!!!! HAHAHA Thanks man ... I've only had 2 hours of sleep trying to fix this stupid problem... I owe you one man. :highfive:
Click to expand...
Click to collapse
I have the the same problem my computer does not recognise the device ( htc one x endeavour) and in fastboot mode it does not work.
pls help
how you solved this ??
abhilashlinge said:
I have the the same problem my computer does not recognise the device ( htc one x endeavour) and in fastboot mode it does not work.
pls help
how you solved this ??
Click to expand...
Click to collapse
If your on Windows 8 problems will occur but there are methods you need to look into. Windows 7 is your ally.
First Uninstalled the drivers for the device using the program in the previous post. Second, make sure your cable is working correctly. Third, make sure you have the correct drivers for you phone on the computer - - HTC Sync causes problems sometimes. Fourth, plug in the phone in while it's on and let the drivers install correctly. Fifth, place the phone in fastboot and let drivers install. Should work.
Remember sometimes you need to restart your computer and try different USB ports. Some users have said 3.0 ports cause problems.
Good luck.
Sent from my SM-N900A using XDA Premium 4 mobile app
chriscerv90 said:
Ok guys, sorry to start another thread on this but I have been going through thread after thread and searching endlessly for a solution and nothing has worked for me.
I was getting ready to do the S-Off procedures and my device is recognized by computer to transfer files, and adb recognizes the device as well, I was able to get the device ID. Reboot into bootloader and fastboot just hangs there and no fastboot usb. try to enter fastboot command and it just hangs at "waiting for device"
I started going crazy and uninstalled drivers. Installed HTC Sync, (never needed it before). Now when I plug in USB while in Fastboot computer recognizes device but says it is not working properly.
Under device manager > Android USB Devices > (Yellow triangle) My HTC > Device Status ( This device cannot start Code 10), (A request for the USB BOS descriptor failed). Driver version 2.0.7.14. I try to update the driver manually and it says "It appears the right driver is already installed." Tried disabling enabling. Unistalling, plugging back in. Nothing seems to work.
Running Viper 3.2.3
Windows 8 (didnt have the problem before using fastboot)
Sorry for long post. Thanks in advance.
Click to expand...
Click to collapse
I ws installing a Ruu zip but process got failed and hboot version changed to 1.54.000 . my device is in now relocked status and bootloader is not reconised by hp envy. adb still showing my device my i lost fastboot mode completely. Any solution there???
I already tried several drivers method. Error is something HTCAND4 in driver events log.
What did u do?
Hello guys,
So I have an unlocked, unroot AT&T HTC One X, running stock rom JB 4.1.2 & Sense 4. The other day I was just using it when all of a sudden the phone froze & stop responding. I pressed and held the power button, trying to reset it. Ever since then, it had been stuck in a boot loop ("HTC -quietly brilliant" appeared, then reboot). I did not have any recovery like TWRP installed or anything similar. When I tried to enter HBoot, this is what I get"
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
and a bunch of options as usual. I tried everything from factory reset, clear storage, to recovery, but nothing works. I tried fastboot then install the RUU, but when I plug the phone in the USB port, it is not recognized by my pc. When I opened cmd and type "fastboot device", it says <waiting for device> and nothing happened.I have already installed HTC Sync Manager and the driver, but the problem is still there. Can anyone please help me? I'm a total noob and don't know what to do now. I just want to wipe everything clean and return it to stock.
Any help would be greatly appreciated. Thanks!
dxbach12 said:
Hello guys,
So I have an unlocked, unroot AT&T HTC One X, running stock rom JB 4.1.2 & Sense 4. The other day I was just using it when all of a sudden the phone froze & stop responding. I pressed and held the power button, trying to reset it. Ever since then, it had been stuck in a boot loop ("HTC -quietly brilliant" appeared, then reboot). I did not have any recovery like TWRP installed or anything similar. When I tried to enter HBoot, this is what I get"
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Nov 26 2012,18:37:14:-1
and a bunch of options as usual. I tried everything from factory reset, clear storage, to recovery, but nothing works. I tried fastboot then install the RUU, but when I plug the phone in the USB port, it is not recognized by my pc. When I opened cmd and type "fastboot device", it says <waiting for device> and nothing happened.I have already installed HTC Sync Manager and the driver, but the problem is still there. Can anyone please help me? I'm a total noob and don't know what to do now. I just want to wipe everything clean and return it to stock.
Any help would be greatly appreciated. Thanks!
Click to expand...
Click to collapse
Are you sure the device is unlocked? It says locked in your bootloader screen. Did you perform a factory reset from the bootloader? That causes the sd card to become corrupt on modified devices, so if you've done that you've created another problem for yourself. Whatever you do, absolutely do not run an RUU, you'll brick your phone. S-on + SuperCID + jb RUU = brick, that's assuming your phone is modified like you say, but it isn't worth the risk. What happens when you enter recovery? And did you have fastboot working previously or have you installed it since this happened?
Sent from my Evita
timmaaa said:
Are you sure the device is unlocked? It says locked in your bootloader screen. Did you perform a factory reset from the bootloader? That causes the sd card to become corrupt on modified devices, so if you've done that you've created another problem for yourself. Whatever you do, absolutely do not run an RUU, you'll brick your phone. S-on + SuperCID + jb RUU = brick, that's assuming your phone is modified like you say, but it isn't worth the risk. What happens when you enter recovery? And did you have fastboot working previously or have you installed it since this happened?
Sent from my Evita
Click to expand...
Click to collapse
My bad, I mean the device is sim-unlocked (I used it with t-mobile). I did try the factory reset from the bootloader, and it seems like I do have a corrupt sd card, just like you suggested. When I enter recovery, the phone reboot, and stuck in boot loop again. I also agree that install the RUU with s-on is a recipe for a bricked phone. I never had fastboot working before, I just tried it for the sake of installing the RUU.
Do you think that the phone's microusb port is broken?
Ok, so an RUU is possibly safe for you, if the phone has never been modified in the past. The only way to be sure of this is to check the CID but to do that you need a working fastboot connection. The command is this:
Code:
fastboot oem readcid
If it comes back as CWS__001 you're safe to run an RUU, but if it comes back as 11111111 (or anything else) it isn't safe.
When you connect the phone to your PC while the phone is in bootloader mode what does it say on the screen of the phone? It should either say fastboot usb or fastboot ac. If it says fastboot usb your usb port is fine, if it says fastboot ac there could be a problem with the data pins on the port.
Sent from my Evita
timmaaa said:
Ok, so an RUU is possibly safe for you, if the phone has never been modified in the past. The only way to be sure of this is to check the CID but to do that you need a working fastboot connection. The command is this:
Code:
fastboot oem readcid
If it comes back as CWS__001 you're safe to run an RUU, but if it comes back as 11111111 (or anything else) it isn't safe.
When you connect the phone to your PC while the phone is in bootloader mode what does it say on the screen of the phone? It should either say fastboot usb or fastboot ac. If it says fastboot usb your usb port is fine, if it says fastboot ac there could be a problem with the data pins on the port.
Sent from my Evita
Click to expand...
Click to collapse
Yeah, I tried to look up my CID too, but the pc doesnt recognize the phone. When I connect the phone to the pc and I enter the fastboot menu, there're 4 options: bootloader, reboot, reboot bootloader, and power down. It says fastboot usb when I move down to the 3 bottom options.
Still, when I typed in "fastboot oem readcid" in cmd, it stills says < waiting for device >. Could I be setting up the fastboot wrong?
dxbach12 said:
Yeah, I tried to look up my CID too, but the pc doesnt recognize the phone. When I connect the phone to the pc and I enter the fastboot menu, there're 4 options: bootloader, reboot, reboot bootloader, and power down. It says fastboot usb when I move down to the 3 bottom options.
Still, when I typed in "fastboot oem readcid" in cmd, it stills says < waiting for device >. Could I be setting up the fastboot wrong?
Click to expand...
Click to collapse
You can try "fastboot devices" to see if its connecting, beyond that you can check device manager to check if your PC can actually see the device, but perhaps hasn't installed it properly.
For fastboot to work properly you need fastboot installed (obviously), you need the proper drivers installed, you need to be using a usb 2.0 port, and you need to be using the original HTC cable (or one that's known to have good data transmission properties). Do you meet all those requirements? If you have drivers installed how did you install them? The fact that fastboot usb shows up on your screen suggests that the port on your phone is ok. What os are you running on your PC?
Sent from my Evita
timmaaa said:
For fastboot to work properly you need fastboot installed (obviously), you need the proper drivers installed, you need to be using a usb 2.0 port, and you need to be using the original HTC cable (or one that's known to have good data transmission properties). Do you meet all those requirements? If you have drivers installed how did you install them? The fact that fastboot usb shows up on your screen suggests that the port on your phone is ok. What os are you running on your PC?
Sent from my Evita
Click to expand...
Click to collapse
This may be where the problem lies. I don't have an OEM HTC data cable. I've been using a 3rd party one, and before the boot loop problem, the cable works fine. I tried both USB 2.0 port and 3.0 port, but neither works. The pc runs Windows 8.1. I install the driver using "HTC Driver Installer.msi" from another thread on XDA. Still, in device manager, the phone is shown as "Unknown USB Device (Device Failed Enumeration)". I tried to update the driver using local files with no luck.
Ok, your problem is Windows 8.1, there are no compatible fastboot drivers. You need to downgrade to Windows 8 or lower and you should be fine.
Sent from my Evita
timmaaa said:
Ok, your problem is Windows 8.1, there are no compatible fastboot drivers. You need to downgrade to Windows 8 or lower and you should be fine.
Sent from my Evita
Click to expand...
Click to collapse
Sorry for the delayed response, I have been away on business.
So I tries the fastboot on my wife's win 7 pc and it works, finally. When I ran fastboot oem readcid, it returns CWS_001. It looks like I can install the RUU after all.
What guide would you recommend me following? I tried to google one but there're just too many.
Thanks in advance!
All you need to do is connect your phone in fastboot mode and run the RUU exe in Windows. Make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off. All you need to do is follow the prompts.
Sent from my Evita
timmaaa said:
All you need to do is connect your phone in fastboot mode and run the RUU exe in Windows. Make sure HTC Sync Manager is uninstalled, make sure no other programs are running, and make sure screen saver/hibernation is turned off. All you need to do is follow the prompts.
Sent from my Evita
Click to expand...
Click to collapse
I put the phone in fastboot, ran the RUU, and after a few prompts, clicked "Update", I reached the screen where it says "Waiting for bootloaders" with a status bar. Then after a while (seems like the bootloader fails?), Error [171]: USB Connection Error screen pops up. I gues this is because I can't boot the phone up and select USB debugging as the connection mode. What can I do now? Is it possible to fix the bootloader or put the phone is USB debugging mode?
Thanks!
dxbach12 said:
I put the phone in fastboot, ran the RUU, and after a few prompts, clicked "Update", I reached the screen where it says "Waiting for bootloaders" with a status bar. Then after a while (seems like the bootloader fails?), Error [171]: USB Connection Error screen pops up. I gues this is because I can't boot the phone up and select USB debugging as the connection mode. What can I do now? Is it possible to fix the bootloader or put the phone is USB debugging mode?
Thanks!
Click to expand...
Click to collapse
It has nothing to do with the usb debugging option, I've run RUUs with no OS on my phone before, they do not require that. The problem is your usb connection, this can be sure to multiple things. Are you using a usb 2.0 port? Are you using an original HTC cable or a cable that's known to work with adb/fastboot? You're not still using the PC with Windows 8.1 on it are you?
Sent from my Evita
timmaaa said:
It has nothing to do with the usb debugging option, I've run RUUs with no OS on my phone before, they do not require that. The problem is your usb connection, this can be sure to multiple things. Are you using a usb 2.0 port? Are you using an original HTC cable or a cable that's known to work with adb/fastboot? You're not still using the PC with Windows 8.1 on it are you?
Sent from my Evita
Click to expand...
Click to collapse
Let me tried borrowing someone else's cable. I was using a LG G2 one, so that could be a usb 3.0 cable.
You didn't answer my question, what OS are you using on the PC now?
Sent from my Evita
timmaaa said:
You didn't answer my question, what OS are you using on the PC now?
Sent from my Evita
Click to expand...
Click to collapse
Sorry. It's Windows 7 Professional SP1.
Ok, check the cable and check the port too.
Sent from my Evita
timmaaa said:
Ok, check the cable and check the port too.
Sent from my Evita
Click to expand...
Click to collapse
Ok, so far I have tried connecting the phone to the usb 2.0 port of the win 7 sp1 laptop using:
- 3rd party usb 2.0 cable
- OEM LG G2 cable (probably usb 3.0)
- OEM Kindle usb 2.0 cable
None have works so far. Every time, error [171] pops up.
Could it be a problem with the battery? The RUU recommends charging the phone at least to 30%. When I plug a charger in the phone, the boot loop continues, so I don't think my phone is charging.
dxbach12 said:
Ok, so far I have tried connecting the phone to the usb 2.0 port of the win 7 sp1 laptop using:
- 3rd party usb 2.0 cable
- OEM LG G2 cable (probably usb 3.0)
- OEM Kindle usb 2.0 cable
None have works so far. Every time, error [171] pops up.
Could it be a problem with the battery? The RUU recommends charging the phone at least to 30%. When I plug a charger in the phone, the boot loop continues, so I don't think my phone is charging.
Click to expand...
Click to collapse
So the phone bootloops even when in the bootloader?
Sent from my Evita
timmaaa said:
So the phone bootloops even when in the bootloader?
Sent from my Evita
Click to expand...
Click to collapse
No, that doesnt happen. When it's not in HBOOT, that happens. I'm charging it while putting in HBOOT right now.