Database Info

Cant flash RUU

Hi Guys, since monday im the owner of a htc one s. I unlocked the booloader and flashed the team win recovery. Then I flashed the TrickDroid Custom Rom, because I thought i would have a nice battery life like it was told in the title. But the fact is that my One S looses extremly much battery in standby-mode and i dont know why. So i would flash a RUU. But I couldnt do this. Like in some Threads i flashed the Stock-Recovery and the I relocked the bootloader. Now I tried to start my phone to flash the RUU but i coulndt, the One S wasnt booting. Then I tried to flash the Recovery over the Bootloader and ive got the failure-code 171 (ruu cant find a fastboot device -> usb). But i realy want to go back to stock. Can you help me?
iZodiac

never done an ruu, so can't help much there other than what is already posted
assuming you are up on your adb/fastboot stuff, try reinstalling the htc drivers. then open command window, cd to fastboot.exe folder, usually in something like tools or platform-tools and at command prompt type fastboot devices and see if phone is recognized.

And thats the Point, if I install Android SDK my CMD Console says me, that I cant open this and then my cmd isnt available anymore on my pc. i tried this 2 times and every time I needed to restore my pc to a earlier time..

not sure
can you reinstall htc sync or try new usb or different pc port
you need the fastboot.exe and adb.exe and 2 windll files in your tools folder. If they are missing--might be issue
did you check and see on phone if usb debugging is checked under Settings/Development and fastboot is unchecked under Settings/Power
oh, if you haven't and get to a point you can, get a nandroid. i know you can't bu sdcard to pc--but, first chance you get, do it

Thanks first for your Support, 2nd
Can you give me a link of the (if available) latest RUU-Nandroid? Would be great if you'll find something

[Q] HTC Inspire Red Traingle Exclamation Won't reset

Hello,
I was reading a thread on someone who had the exact same issue, but no solution was ever posted.
Here's the thread http://forum.xda-developers.com/showthread.php?t=1458066
Background - this is a friends HTC Inspire, no rooting or anything was attempted, factory untouched phone bought new from AT&T.
Turns on, eventually goes to a 2 green arrows in a circle around a phone and then to a red triangle with red exclamation point over a black phone. I can hold the volume up and power to reset or wipe cache, neither does anything. Comes back to the same screen. says:
E:Can't open /cache/recovery/command
-- Wiping data...
Formatting /data...
E:Can't open /data/cwpkg.zip
E:Can't open /data/cw.prop
E:Can't open /cache/cwpkg.zip
E:Can't open /cache/cw.prop
Formatting /cache...
Data wipe complete
Doing a boot holding volume down and power shows this info:
ACE PVT SHIP S-ON RL
HBOOT-0.85.0024
MICROP-0438
RADIO-26.10.04.03_M
eMMC-boot
Apr 12 2011,00:55:45
HBOOT
I tried formatting the sd card and using recovery and stock rom to load, nothing worked, as if not recognized. The sd card had data on it(which was accessible), which I transfered to the computer before formatting.
Any ideas? I have never used an android device but I've been reading through this forum and others for hours now... phone is outside of warranty now too, so that's no longer an option. Thanks in advance.
Devin

It failed during the update to the current rom version or was reset/lost power during update. Use a pc to download the most recent ruu update for the inspire from HTC. Then download and install htc sync on pc. Place phone into fastboot mode with sd card inserted and then plug into pc. Run ruu from pc. Data will be lost but phone will be usable.

Gizmoe said:
It failed during the update to the current rom version or was reset/lost power during update. Use a pc to download the most recent ruu update for the inspire from HTC. Then download and install htc sync on pc. Place phone into fastboot mode with sd card inserted and then plug into pc. Run ruu from pc. Data will be lost but phone will be usable.
Click to expand...
Click to collapse
Dude you rock! That did it, thanks so much!
Devin

HTC Inspire needs RUU
Gizmoe said:
It failed during the update to the current rom version or was reset/lost power during update. Use a pc to download the most recent ruu update for the inspire from HTC. Then download and install htc sync on pc. Place phone into fastboot mode with sd card inserted and then plug into pc. Run ruu from pc. Data will be lost but phone will be usable.
Click to expand...
Click to collapse
So Gizmoe, I am in the same boat as original poster. I downloaded the correct ruu from HTC , but PC won't recognize phone. Point of clarification
When you say "place phone into fast boot mode" does that mean just connect to PC at that point or do I shut phone down and then connect. I've been going bonkers since ATT pushed software update and bricked the phone.
Thanks for any advice.
Terry

ILCUL8R said:
So Gizmoe, I am in the same boat as original poster. I downloaded the correct ruu from HTC , but PC won't recognize phone. Point of clarification
When you say "place phone into fast boot mode" does that mean just connect to PC at that point or do I shut phone down and then connect. I've been going bonkers since ATT pushed software update and bricked the phone.
Thanks for any advice.
Terry
Click to expand...
Click to collapse
It means with phone powered off hold down volume up and press power. Continue to hold volume until you see the hboot screen. Then select fastboot ( vol + - to make choice power to select). Then plug into pc. You should see the words fastboot usb on phone.

Gizmoe said:
It means with phone powered off hold down volume up and press power. Continue to hold volume until you see the hboot screen. Then select fastboot ( vol + - to make choice power to select). Then plug into pc. You should see the words fastboot usb on phone.
Click to expand...
Click to collapse
Ok, we'll I got it into fast boot USB mode, plugged in USB to PC, ran exe ruu file (which takes forever btw) and then got connection error. Ruu application then exits. Must be something hosed up in the phone with drivers. Bummer
I just checked Windows devices and it is showing as a "Device failed enumeration" error. Trying to troubleshoot that but have my doubts right now. I did notice that when I connected it earlier today PC saw it as G drive for a split second and then it dropped.

ILCUL8R said:
Ok, we'll I got it into fast boot USB mode, plugged in USB to PC, ran exe ruu file (which takes forever btw) and then got connection error. Ruu application then exits. Must be something hosed up in the phone with drivers. Bummer
I just checked Windows devices and it is showing as a "Device failed enumeration" error. Trying to troubleshoot that but have my doubts right now. I did notice that when I connected it earlier today PC saw it as G drive for a split second and then it dropped.
Click to expand...
Click to collapse
Do you have HTC sync installed and running?

Hi Gizmoe. Well I have HTC Sync but I didn't think I needed to have that running. I just ran the ruu exe file, but got connection error. I just tried HTC Sync with phone in fastboot usb mode but HTC Sync can't see it. Version of HTC Sync is 3.3.63. The other thing I noticed is that if phone is off and plugged into PC it is recognized as a removable device with a G: drive letter in device manager, but doesn't show up in file explorer and running exe or HTC Sync still can't see it.
If it's connected when it's in fastboot usb mode then windows says "last device connected malfunctioned " and PC doesn't see it.
I'm in this catch 22. Tried to do recovery process to install a ruu off sdcard which errors out, and can't install ruu from pc since phone usb connection not recognized.

ILCUL8R said:
Hi Gizmoe. Well I have HTC Sync but I didn't think I needed to have that running. I just ran the ruu exe file, but got connection error. I just tried HTC Sync with phone in fastboot usb mode but HTC Sync can't see it. Version of HTC Sync is 3.3.63. The other thing I noticed is that if phone is off and plugged into PC it is recognized as a removable device with a G: drive letter in device manager, but doesn't show up in file explorer and running exe or HTC Sync still can't see it.
If it's connected when it's in fastboot usb mode then windows says "last device connected malfunctioned " and PC doesn't see it.
I'm in this catch 22. Tried to do recovery process to install a ruu off sdcard which errors out, and can't install ruu from pc since phone usb connection not recognized.
Click to expand...
Click to collapse
UPDATE: I decided to just try the recovery method again while the phone was plugged into USB cable just to charge it. Well it downloaded the latest HTC version of the ROM and it installed....YEAH, BUT phone thinks it's a Desire , not an Inspire and the IMEI MMEI etc. info is missing. No connectivity to mobile network. And I don't have keyboard function either. Sooo, I think I will try another ruu and see if that works starting from scratch. I guess I'm still missing some files or steps in this process. I used to be in the PC business and thought they could be convoluted, but cellphones take the cake.

ILCUL8R said:
UPDATE: I decided to just try the recovery method again while the phone was plugged into USB cable just to charge it. Well it downloaded the latest HTC version of the ROM and it installed....YEAH, BUT phone thinks it's a Desire , not an Inspire and the IMEI MMEI etc. info is missing. No connectivity to mobile network. And I don't have keyboard function either. Sooo, I think I will try another ruu and see if that works starting from scratch. I guess I'm still missing some files or steps in this process. I used to be in the PC business and thought they could be convoluted, but cellphones take the cake.
Click to expand...
Click to collapse
Yes they do. Just an fyi the desire and inspire are exactly the same device and HTC left the inspire name out of the build prop. It will say it's a desire HD, so that's normal. The rest isn't though. Yeah I would try the ruu again. Just make sure HTC sync is installed and running. You can run it from the phones os too.

Gizmoe said:
Yes they do. Just an fyi the desire and inspire are exactly the same device and HTC left the inspire name out of the build prop. It will say it's a desire HD, so that's normal. The rest isn't though. Yeah I would try the ruu again. Just make sure HTC sync is installed and running. You can run it from the phones os too.
Click to expand...
Click to collapse
Gizmoe, thought I'd give you the latest update: I was able to finally get the PC (Win8) to recognize the phone by installing HTC Sync 3.3.63, installing Win7 64bit drivers.
Then I downloaded RUU_Ace_Sense30_S_Cingular_US_3.20.502.63_Radio_12.69c.60.29U_26.09.13.17_M_release_335423_signed from HTC site. This is an exec file.
Got phone into USB debugging mode, fastboot off , charge only, and ran the above RUU. Seemed to be working as it asked if I wanted to update etc. and warned about losing data. Said ok and RUU exec then popped up status window saying "Waiting for bootloader......................"
This ran for a few minutes and then Windows popped up message saying last USB device connected failed. Then RUU exec finally popped up and said Connection Error 171. No choice but to exit program. This has happened twice. Very annoying. Took forever to get PC to recognize phone and now I'm still stuck with a brick thanks to ATT.
Any thoughts ?

ILCUL8R said:
Gizmoe, thought I'd give you the latest update: I was able to finally get the PC (Win8) to recognize the phone by installing HTC Sync 3.3.63, installing Win7 64bit drivers.
Then I downloaded RUU_Ace_Sense30_S_Cingular_US_3.20.502.63_Radio_12.69c.60.29U_26.09.13.17_M_release_335423_signed from HTC site. This is an exec file.
Got phone into USB debugging mode, fastboot off , charge only, and ran the above RUU. Seemed to be working as it asked if I wanted to update etc. and warned about losing data. Said ok and RUU exec then popped up status window saying "Waiting for bootloader......................"
This ran for a few minutes and then Windows popped up message saying last USB device connected failed. Then RUU exec finally popped up and said Connection Error 171. No choice but to exit program. This has happened twice. Very annoying. Took forever to get PC to recognize phone and now I'm still stuck with a brick thanks to ATT.
Any thoughts ?
Click to expand...
Click to collapse
Ahh yes windows 8 is a ***** with android devices and fastboot drivers. I would recommend trying it on a machine with windows 7. Also are you s off. If so you can try PD98IMG.

Gizmoe said:
Ahh yes windows 8 is a ***** with android devices and fastboot drivers. I would recommend trying it on a machine with windows 7. Also are you s off. If so you can try PD98IMG.
Click to expand...
Click to collapse
Yes, apparently there are a lot of issues with Win8 and android. I can try it on a machine with 7 or even XP. Unfortunately I'm S-ON so no go on PD98IMG. I'll let you know what happens when I try it on the other Windows machines.
Thanks

ILCUL8R said:
Yes, apparently there are a lot of issues with Win8 and android. I can try it on a machine with 7 or even XP. Unfortunately I'm S-ON so no go on PD98IMG. I'll let you know what happens when I try it on the other Windows machines.
Thanks
Click to expand...
Click to collapse
UPDATE:
SUCCESS !! :good: Well it only took a boatload of patience and a 7 yr. old laptop running XP to get the phone re-imaged. Process was sloooow (about 30 minutes) but all drivers loaded and the stock ROM from HTC installed fine. Phone is now back to operational. Turns out I didn't lose contacts since they were apparently backed up in Google account. (YEAH) Now I just have to manually install 4 more small security patches from HTC. Their website isn't too clear as to how to do this but I'll muddle thru it.
Thanks Gizmoe for your help and suggestions. You are right I would definitely recommend that anyone trying to root, recover or re-image from scratch an Android from a PC to avoid Win8 at this time and stick with Win7 or XP.

Help me please!
ILCUL8R said:
Yes, apparently there are a lot of issues with Win8 and android. I can try it on a machine with 7 or even XP. Unfortunately I'm S-ON so no go on PD98IMG. I'll let you know what happens when I try it on the other Windows machines.
Thanks
Click to expand...
Click to collapse
Please help me, i'm having the same problem and i'm trying to apply this solution but i can't understand what do you mean with "go on PD98IMG" please please tell me what does that means and how to do it please!
---------- Post added at 07:26 AM ---------- Previous post was at 07:21 AM ----------
Gizmoe said:
Ahh yes windows 8 is a ***** with android devices and fastboot drivers. I would recommend trying it on a machine with windows 7. Also are you s off. If so you can try PD98IMG.
Click to expand...
Click to collapse
Gizmoe, please can you tell me what do you mean with "try PD98IMG" i guess that it's a way to get the inspire 4g/DHD s-off but i can't find how to apply it. please help me

rokr_64 said:
Please help me, i'm having the same problem and i'm trying to apply this solution but i can't understand what do you mean with "go on PD98IMG" please please tell me what does that means and how to do it please!
---------- Post added at 07:26 AM ---------- Previous post was at 07:21 AM ----------
Gizmoe, please can you tell me what do you mean with "try PD98IMG" i guess that it's a way to get the inspire 4g/DHD s-off but i can't find how to apply it. please help me
Click to expand...
Click to collapse
A PD98IMG is a way to install various things but requires an s off device. It is not a method to acheive s off. What exactly is the problem you are having? Are you not able to boot your device? If you are still stock, run the current RUU from HTC through fastboot as explained in previous posts in this thread.

HTC bootloader problem
Gizmoe, I am joining this group, I have the same problem, followed all steps. my problem is that RUU during the process sends msg to phone to reboot and start Bootloader my phone reboots and stays with white screen / green HTC logo (freezes?) RUU after waiting for Bootloader returns error 171 connection problem. My guess is that bootloader is not starting and RUU times out and thinks that it is connection problem.
Uninstalled sync and reinstalled latest version, deleted and re downloaded latest RUU. System recognizes phone ( device manager shows HTC). Any suggestions? Thanks.

raydilba said:
Gizmoe, I am joining this group, I have the same problem, followed all steps. my problem is that RUU during the process sends msg to phone to reboot and start Bootloader my phone reboots and stays with white screen / green HTC logo (freezes?) RUU after waiting for Bootloader returns error 171 connection problem. My guess is that bootloader is not starting and RUU times out and thinks that it is connection problem.
Uninstalled sync and reinstalled latest version, deleted and re downloaded latest RUU. System recognizes phone ( device manager shows HTC). Any suggestions? Thanks.
Click to expand...
Click to collapse
What Windows version are you on?

Gizmoe said:
What Windows version are you on?
Click to expand...
Click to collapse
Windows 7 Pro.

raydilba said:
Windows 7 Pro.
Click to expand...
Click to collapse
Yeah there seems to be a communication issue. Try putting phone into fastboot. Make sure phone reads fastboot usb. Then run RUU. There may be programs in pc as well blocking it. See if you can send fadtboot commands if the aforementioned method doesn't work. If that's how you already tried running it then run it from booted phone.

Phone wont connect

Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.

InV15iblefrog said:
Hi guys
Desire S.
Unrooted, no custom recovery, basically everything default.
HBoot 2.00.0002
.
To root, i need the 0.98 version.
Using HTCdev.com, i tried to unlock, but at step 5, where i should type fastboot oem get_identifier_token, the phone doesnt come up at all, and cmd just continues to wait for device.
Before you ask, I HAVE (i hope) followed all steps.
This includes updating drivers manually, using htc sync (latest and older versions), swapping usb port and cable, reunzipping adb and fastboot material from other sources, and reading for a decent number of hours throughout xda and other external forums and guides.
But there is still no success.
Anyone help please? I don't just want fast, "get it working for me" type answers, but actually want to know why it refuses to greet me!
Cheers
BTW, i'm on a windows 8.1 laptop, and have updated the relevant drivers, still to no avail.
Click to expand...
Click to collapse
your phone must be in FASTBOOT bootloader mode..not in the HOME of your ROM..
if you don't wan to turn off your phone first and pressing volume down + power to go to bootloader..then you can using a adb command on cmd while your phone is still in the HOME of your ROM.. type "adb reboot bootloader" then select "FASTBOOT" now you can type "fastboot oem get_identifier_token"
don't forget to disabled Fast boot mode and enable USB Debuging first from the system settings and just connect your phone to pc as charge mode..
hope this help..

Sorry mate. Tried that before your post though.
However the person for whom I was doing this no longer needs it doing, and plans for a newer device, so I no longer have this device available. Thus, i thanked you, since it was a cue for me to mention that.
Cheers.

This model of HTC is died

[Q] AT&T HTC One X stuck in boot loop & usb connection not recognized by pc

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.

ADB doesn't see my HTC One X

My post that died.. please read also
http://forum.xda-developers.com/showthread.php?p=48646053#post48646053
Hello guys, long story short.. a little while ago I tried upgrading my ROM to 4.4.4 and found out that i have to turn S-off and install the RUU 3.18 i think it was. Upon doing this I came to find out that my phone isn't being listed when I type adb devices. I have debugging mode on and install the latest HTC drivers and uninstalled HTC sync, but yet it wont list my device.
I did some research and found out it could be the current rom I have installed causing it not being listed and that I may have to use another ROM to get windows to see my phone. But I dont think I can flash another rom because I cant get into TWRP now. I can get in bootloader but now recovery doesnt work and i cant get into TWRP anymore,I think I also have to update Hboot too.
My question is how do I go about getting my phone listed in adb and how can install twrp again.. Its been soo long since I did this I may need some help. If i can get ADB to list my phone I should be able to do the upgrading myself.
I'm taking a break atm as this is giving me a huge headache. I know Its not hard to flash if you have ADB working. Or TWRP but I dont have either of them. Can anyone shed some light for me please..
This is whats on my bootloader page
EVITA PVT SHIP S-ON RL
HBOOT- 1.09.0000
RADIO- 0.16a.32.09.06
OpenDSP-v25.1.0.32.0405
eMMC-boot
rootbox jb evita if that matters
Thx for reading.

Any help would be greatly appreciated.

So to make sure I understand your situation:
1. You CAN boot into your rom
2. You CANNOT boot into your Recovery (I'm assuming bootloop)
3. You CANNOT see your device in adb OR fastboot (please confirm)
So here's the best case scenario. You are NOT running Windows 8.1 and you can see your device in fastboot while in the bootloader. In this case, S-OFF again and flash recovery as usual. If your ARE running Win 8.1 .... well we'll cross that bridge when we get to it.
To debug your adb problem plug your phone into your computer. Does your phone respond in any way? Do you see the device show up on your computer for file transfer? If any of these things is true, rejoice! For there is hope! This is just for assurance, but you do have developer settings turned on and adb enabled right? Have you tried other usb ports? I forget if there is authentication in 4.2.2 but if there is, did you add you trust your computer? Try revoking all trusted computers and try again. Have you tried the newest version of ADB? Have you tried a different cord? If you have tried ALL of these, open up device manager. This can be done by simply typing into the search in start on both Win7/8. Now look at the top of the list. Do you see anything like ADB Interface or Android Device? If not, do you see any unrecognized devices or any device with an exclamation mark under Other Devices or Universal Serial Bus Controller? If any of these is true, right click the device and select properties. It'll be best to post a screen shot at this point. But if you're an intrepid risk seeker, go to the driver tab and hit uninstall. Next unplug your device, wait a few moments and plug it back in. You should see a driver installation progress. I've also attached the generic Google drivers that I know for sure works should you need it. Now try adb again and hopefully your device shows up:highfive:
If all is wrong with the world, and you do not see anything when you connect your phone, try on different computer with a different cord.