Database Info

[Q] Model ID incorrect! Update Fail!

My HTC Inspire fell in water. I Immediately took battery out. After reading few user groups, I kept my phone in the rice bag for a day.
• Well, it is stuck on HBOOT Screen.
• I cannot use my volume up or down buttons.
• I can use Power button and it goes through checks to find PD98IMG.zip file.
• I downloaded it and copied on the micro SD card.
• Now it goes through blue progress bar and then through yellow progress bar on the top right.
• After this it gets stuck with this message: "Model ID incorrect! Update Fail! Press <POWER> to reboot."
• I am stuck in this cycle. It keeps doing the same thing every time.
I am not trying to root the phone. I read somewhere about Gold Card but that won't work for me because when I connect Inspire to PC, it does not show me a micro SD drive. It seems it is now getting connected as a mounted disk.
Any suggestion from anybody?

Only thing I would suggest is to download attn1's stock rom that's rooted and save the ruu to the root of SD card. But if I was u,maybe get another SD card to flash the ruu. Rename the ruu to PD98IMG.zip and make sure the md5 is correct,to ensure a good download. Flash into hboot and see if it recognizes and flash away. That's what I would do
Sent from my Desire HD using XDA App

Ok... I'll try that tonight. Thanks.

No problem let me know how it goes
Sent from my Desire HD using XDA App

Which pd98img are you using? If you are s-on then only a signed HTC zip will work, like the original stock unrooted ROM.
Sent from my HTC Inspire 4G using XDA Premium App

True u never did state weather u was rooted or not
Sent from my Desire HD using XDA App

I have not rooted. I'll try to find original stock unrooted ROM.
Thanks.

Not sure if I am trying with the correct programs.
I tried RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_2 6.06.04.06_M_release_166557_signed.exe
But no success as the phone is not getting connected to the pc. I get error 170 - USB connection error.
I see S-ON on the HBOOT screen. It has "HBOOT USB PLUG" but still can't see from my computer.
Any pointer to signed HTC ROM?

appybase said:
Not sure if I am trying with the correct programs.
I tried RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_2 6.06.04.06_M_release_166557_signed.exe
But no success as the phone is not getting connected to the pc. I get error 170 - USB connection error.
I see S-ON on the HBOOT screen. It has "HBOOT USB PLUG" but still can't see from my computer.
Any pointer to signed HTC ROM?
Click to expand...
Click to collapse
Yup, download it here

appybase said:
Not sure if I am trying with the correct programs.
I tried RUU_Ace_Cingular_US_1.80.502.3_Radio_12.39.60.19_2 6.06.04.06_M_release_166557_signed.exe
But no success as the phone is not getting connected to the pc. I get error 170 - USB connection error.
I see S-ON on the HBOOT screen. It has "HBOOT USB PLUG" but still can't see from my computer.
Any pointer to signed HTC ROM?
Click to expand...
Click to collapse
id10terrordfw said:
Yup, download it here
Click to expand...
Click to collapse
Note: with S-ON, you'll need a gold card to install that zip.

Gene Poole said:
Note: with S-ON, you'll need a gold card to install that zip.
Click to expand...
Click to collapse
True, I forgot about that. I have been S-Off since release day, lol.

So with S-ON, I need gold card... but my phone is not detected when I connect to computer. So that means I cannot make a gold card. Correct?
Any other way I can make it S-OFF?
Or Any way I can have phone connect to computer? HBOOT screen does get a message HBOOT USB Plus but that's all. It does not get mounted as a disk to the computer.

appybase said:
So with S-ON, I need gold card... but my phone is not detected when I connect to computer. So that means I cannot make a gold card. Correct?
Any other way I can make it S-OFF?
Or Any way I can have phone connect to computer? HBOOT screen does get a message HBOOT USB Plus but that's all. It does not get mounted as a disk to the computer.
Click to expand...
Click to collapse
Do you have another Android? A gold card can be made with any device that supports reading the SD Serial number.
It sounds like you probably have gunk or still have moisture in your vol-down button contacts. Do you have any of that computer dust-off spray? Try blowing the area around the VOL switch good. Maybe try to clean it with some 90% isopropanol and then blowing it down good.

I didn't realize that another Android will work... I will definitely try that.
I appreciate everybody's help on this. I will try again tonight and update the thread.

I had to try couple of sd cards. Looks like I got the gold card ready. I have PB98img.zip on it. Now I get a different error:
Main Version is older!
Update Fail!
Press <POWER> to reboot.
Some where I read I should try with PB99IMG.zip. I'll try to find that and try once more.

appybase said:
I had to try couple of sd cards. Looks like I got the gold card ready. I have PB98img.zip on it. Now I get a different error:
Main Version is older!
Update Fail!
Press <POWER> to reboot.
Some where I read I should try with PB99IMG.zip. I'll try to find that and try once more.
Click to expand...
Click to collapse
No, that's a myth. It has to be PD98IMG.ZIP (I assume that's a typo) for the HBOOT to even load it. What version did you have on the phone before? What version are you trying to flash now? What is the ultimate goal here? Are you trying to get back to stock for an exchange?

I am attaching the screen image of my phone screen.
Not sure what version I had earlier... but over the weekend, AT&T did send an upgrade.
Thanks...

Did you try this already?
http://forum.xda-developers.com/showthread.php?t=1058042
Sent from my HTC Desire HD using XDA Premium App

Gene Poole said:
No, that's a myth. It has to be PD98IMG.ZIP (I assume that's a typo) for the HBOOT to even load it. What version did you have on the phone before? What version are you trying to flash now? What is the ultimate goal here? Are you trying to get back to stock for an exchange?
Click to expand...
Click to collapse
appybase said:
I am attaching the screen image of my phone screen.
Not sure what version I had earlier... but over the weekend, AT&T did send an upgrade.
Thanks...
Click to expand...
Click to collapse
That answered maybe one of my questions. Since you mentioned you had the update, I assume you've got the latest from HTC. Your picture confirms that you have the latest radio. Where did you get the PD98IMG you're trying to flash? What version is it?
I assume from the fact that it gives you that message, there is some valid firmware on the phone. Is the problem that you can't get past the HBOOT screen? I think maybe your VOL-DOWN key is stuck (or wet and making contact) preventing you from booting the main boot-img.
And last but not least, why are you trying to reflash a RUU? It appears that you have a valid flash or you wouldn't be getting the message from HBOOT. Is it because you're stuck on HBOOT?
What is your ultimate goal and what is actually happening that is preventing you from reaching that goal? I believe that it is just a stuck key.

I am not trying to root the phone. Once it fell in water I dried the phone (took battery and sim/sd cards out). Also put in the rice bag for couple of days.
I am stuck on HBOOT screen. I just want to get past it. Unfortunately I am not able to use the volume up/down buttons and may that's the problem.
I have also used air spray/hair drier but no luck yet. The volume up/down buttons just don't work.

[Q] my htc sensation will not boot

I have a Htc Sensation running on the Tmobile network
i decided to go with a different rom and tried to install the rom from COREDROID SENSATION XE & 4G v5.1.
after installing it was stock on the boot screen.
I tried to SCID and install PG58DOAG.
at this point my phone will not boot.
I can get into the the recovery mode after i select "recovery" it goes to a screen with a red triangle and an exclamation mark.
I the volume up and power and the try to install a update...but non has worked
can get one help??

download this file http://www.filefactory.com/file/c19...00U_10.14.9035.01_M_release_223976_signed.exe
and run it with your phone plugged in your pc, it should do a stock recovery on your phone.

I faced the same issue with another ROM.
The only way I found to reboot was to reinstall the firmware while connected via USB with the PC.
And after that, I reinstalled the ROM.

I couldnt even boot.

primekrieger said:
I couldnt even boot.
Click to expand...
Click to collapse
Okay, first off stop digging up multiple 1 and 2 year old threads to post about your problem.
Second, be MUCH more specific about what the issue is. What happened before it stopped booting? Was it dropped or something or was it working fine?
Is it rooted?
Is it S-Off?

Skipjacks said:
Okay, first off stop digging up multiple 1 and 2 year old threads to post about your problem.
Second, be MUCH more specific about what the issue is. What happened before it stopped booting? Was it dropped or something or was it working fine?
Is it rooted?
Is it S-Off?
Click to expand...
Click to collapse
Sorry about that.
Here are the full details:
I have a Sensation XE, it was running ARHD 7.2, rooted, Bootloader Unlocked, S-OFF
I was playing subway surfers when all of a sudden the phone froze, no buttons nothing worked. After a while it itself restarted and got stuck on the white HTC boot screen. When it didnt progress for some minutes, I removed the battery, reinserted it and tried turning it on. But nothing, no signs of life were shown. Even on connecting the wall charger there was no charging LED.
Only thing is that windows can detect it as QHSUSB_DLOAD or something.
I checked out the Unbricking Sensation forum at: http://forum.xda-developers.com/show....php?t=1522351
but they say it works only for devices bricked while turning to S-ON, but as I mentioned mine is S-OFF. So, can I still use their method or is there some alternative?
Thanks

primekrieger said:
Sorry about that.
Here are the full details:
I have a Sensation XE, it was running ARHD 7.2, rooted, Bootloader Unlocked, S-OFF
I was playing subway surfers when all of a sudden the phone froze, no buttons nothing worked. After a while it itself restarted and got stuck on the white HTC boot screen. When it didnt progress for some minutes, I removed the battery, reinserted it and tried turning it on. But nothing, no signs of life were shown. Even on connecting the wall charger there was no charging LED.
Only thing is that windows can detect it as QHSUSB_DLOAD or something.
I checked out the Unbricking Sensation forum at: http://forum.xda-developers.com/show....php?t=1522351
but they say it works only for devices bricked while turning to S-ON, but as I mentioned mine is S-OFF. So, can I still use their method or is there some alternative?
Thanks
Click to expand...
Click to collapse
Can you get into recovery?
Sent from your phone. You should be careful where you leave that thing.

Skipjacks said:
Can you get into recovery?
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
No, I can't get to recovery. The phone doesn't start up at all. But windows detects something like QHSUSB_DLOAD when connecting through usb.

primekrieger said:
No, I can't get to recovery. The phone doesn't start up at all. But windows detects something like QHSUSB_DLOAD when connecting through usb.
Click to expand...
Click to collapse
Is the battery charging when you connect it to USB like that? If so I'd say to try an ruu to return it to completely stock. You will lose all user data on the internal memory when doing this. And it will return the phone to s-on and stock ROM. You will have to start over.
Do a search for ruu and you should find the thread that walks you through the process. Its really easy. You basically just run an .exe file from windows and it does everything else.
Sent from your phone. You should be careful where you leave that thing.

Skipjacks said:
Is the battery charging when you connect it to USB like that? If so I'd say to try an ruu to return it to completely stock. You will lose all user data on the internal memory when doing this. And it will return the phone to s-on and stock ROM. You will have to start over.
Do a search for ruu and you should find the thread that walks you through the process. Its really easy. You basically just run an .exe file from windows and it does everything else.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
No, the charging LED doesnt glow.
Phone is detected on USB connection after i remove the battery. And moreover windows doesnt detect it as a phone i think.
PS: Losing data, S-OFF, ROM is not a concern. I just want it working, bought it just 6 months ago :crying:

primekrieger said:
No, the charging LED doesnt glow.
Phone is detected on USB connection after i remove the battery. And moreover windows doesnt detect it as a phone i think.
PS: Losing data, S-OFF, ROM is not a concern. I just want it working, bought it just 6 months ago :crying:
Click to expand...
Click to collapse
Do you have access to another battery just to make sure your battery isn't fried? If there is physical damage to the battery it will neither charge nor will it power on.
Also, try doing the ruu thing anyway. Worst its going to do is not work.
Sent from your phone. You should be careful where you leave that thing.

Skipjacks said:
Do you have access to another battery just to make sure your battery isn't fried? If there is physical damage to the battery it will neither charge nor will it power on.
Also, try doing the ruu thing anyway. Worst its going to do is not work.
Sent from your phone. You should be careful where you leave that thing.
Click to expand...
Click to collapse
As you said I searched for RUU for my phone, but now the problem is I can't decide what RUU to download since the phone wont start and therefore I can't see software number or CID.

primekrieger said:
As you said I searched for RUU for my phone, but now the problem is I can't decide what RUU to download since the phone wont start and therefore I can't see software number or CID.
Click to expand...
Click to collapse
from bootloader connect the device in the pc via usb(it should say fastboot usb)
open a cmd in the folder where you have adb and fastboot files and do these commands
fastboot getvar version-main
fastboot getvar cid

rzr86 said:
from bootloader connect the device in the pc via usb(it should say fastboot usb)
open a cmd in the folder where you have adb and fastboot files and do these commands
fastboot getvar version-main
fastboot getvar cid
Click to expand...
Click to collapse
Hi there!
Even my device is facing similar sort of problems. Although the situation is not as bad as the op,but still the phone is still just a paperweight.
Now what I did- unlocked bootloader via HTC dev site( HBOOT Ver 1.27)
Decided to S-off by J.Bear method.
Everyhting went fine untill the phone restarted. Controlbear no longer recognised the device. It said check your drivers.
That was the time when everything messed up.
Now the phone would no longer boot ahead of the white HTC bootscreen. And sometimes it even powers on directly to recovery(even when i'm not pressing volume down).
And one more strange thing happening.."adb devices" command doesn't show any devices listed although i can check the firmware and cid version(via fastboot command). And the device is showing up in device manager(my HTC). But adb commands are not working.
Am i missing something?
Any help would be much appreciated.

walkermoon said:
Hi there!
Even my device is facing similar sort of problems. Although the situation is not as bad as the op,but still the phone is still just a paperweight.
Now what I did- unlocked bootloader via HTC dev site( HBOOT Ver 1.27)
Decided to S-off by J.Bear method.
Everyhting went fine untill the phone restarted. Controlbear no longer recognised the device. It said check your drivers.
That was the time when everything messed up.
Now the phone would no longer boot ahead of the white HTC bootscreen. And sometimes it even powers on directly to recovery(even when i'm not pressing volume down).
And one more strange thing happening.."adb devices" command doesn't show any devices listed although i can check the firmware and cid version(via fastboot command). And the device is showing up in device manager(my HTC). But adb commands are not working.
Am i missing something?
Any help would be much appreciated.
Click to expand...
Click to collapse
probably your hboot get locked after S-OFF.that's why adb commands don't work(i think)
check your bootloader details
if now you have S-OFF and locked hboot flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also patched hboot which is unlocked
follow the instructions to the letter(important)
and before flashing check md5 sums(important)

rzr86 said:
probably your hboot get locked after S-OFF.that's why adb commands don't work(i think)
check your bootloader details
if now you have S-OFF and locked hboot flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
it will give you also patched hboot which is unlocked
follow the instructions to the letter(important)
and before flashing check md5 sums(important)
Click to expand...
Click to collapse
Appreciate your concern.
But the thing is my device is still S On. The JBear method didn't finish. It messed up in between.
I'm attaching a pic. Give a look.

walkermoon said:
Appreciate your concern.
But the thing is my device is still S On. The JBear method didn't finish. It messed up in between.
I'm attaching a pic. Give a look.
Click to expand...
Click to collapse
hmm,
probably you need to use the temproot remove.bat file to remove temproot
check for troubleshooting in this thread
http://forum.xda-developers.com/showthread.php?t=1661631
also refer you issue there
ganeshp will help you further
or you can install 4ext recovery
enable smartflash from it and flash a custom rom

HTC One X in boot loop after unlocking

Hello there. I went through the unlock process just fine, but followed some reccomendation to install a new boot.img via Hasoon2000's tool in order to run Viper ROM (downloaded the boot.img from the Viper thread here). Well now my phone is in a boot loop that brings me to the HTC screen with red text saying This build is for..... When I power off it comes right back to that screen and I can't get it to get anywhere else.
Any thoughts? Thank you for any help.

mrwizard65 said:
Hello there. I went through the unlock process just fine, but followed some reccomendation to install a new boot.img via Hasoon2000's tool in order to run Viper ROM (downloaded the boot.img from the Viper thread here). Well now my phone is in a boot loop that brings me to the HTC screen with red text saying This build is for..... When I power off it comes right back to that screen and I can't get it to get anywhere else.
Any thoughts? Thank you for any help.
Click to expand...
Click to collapse
Does your computer recognize the phone being plugged in? If so, run adb reboot recovery. If that doesn't work, try re-running the kit to re-root it.

HTC_Phone said:
Does your computer recognize the phone being plugged in? If so, run adb reboot recovery. If that doesn't work, try re-running the kit to re-root it.
Click to expand...
Click to collapse
I don't believe the computer is recognizing it at all. I'm not hearing the normal "ding" I get when it reboots.

first turn the phone off by holding power button for a longer time, then turn it on by holding both power and volume down buttons for a couple of seconds to enter bootloader

Did you install the Rom? Or just the boot.img?
Sent from my VENOMized HoxL

Alright, so holding down the volume button did get me into the bootloader. I tried the recovery and was able to recover using TWRP, but when I reboot it brings me back to the same HTC screen. So again, now I am able to do things via the bootloader so hopefully there is a next step to fix this.
To answer your question, I did not get to install the ROM, only the boot.img
Thanks for everyones help so far.

So go to twrp and install the Rom
Sent from my VENOMized HoxL

area51avenger said:
So go to twrp and install the Rom
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Ok, went ahead and loaded up Viper 3.2.2 and it seemed to go fine. Rebooted and am at the same HTC logo screen with the "this build is for development....." It will keep rebooting into this screen several times and will hang.
I did get the tampered/unlocked notice on the bootloader before doing all this. Not sure if that makes a difference or not.
Thanks for any additional help.

Did the ROM install correctly? Flash the boot img in adb again.

pOLLYpOCKET said:
Did the ROM install correctly? Flash the boot img in adb again.
Click to expand...
Click to collapse
ROM did install correctly but was still bringing me to the HTC splash screen with developer warning.
As a last ditch effort I downloaded the correct RUU and ran it. Device now works properly, but when trying to go through the tool kit again I get to the bootloader in the end and it says "relocked" even though I submitted my token, got the proper .bin and unlocked.
Any thoughts? Everyone has been very helpful.

mrwizard65 said:
ROM did install correctly but was still bringing me to the HTC splash screen with developer warning.
As a last ditch effort I downloaded the correct RUU and ran it. Device now works properly, but when trying to go through the tool kit again I get to the bootloader in the end and it says "relocked" even though I submitted my token, got the proper .bin and unlocked.
Any thoughts? Everyone has been very helpful.
Click to expand...
Click to collapse
I thought you wouldn't be able to install RUU if your bootloader is unlocked. But anyway, try this thread instead http://forum.xda-developers.com/showthread.php?t=1732980

I'm glad to report that I was finally able to flash the 3.2.2 Viper ROM. I was having problems unlocking the phone again, but just did it via fastboot command line. Once that was done it was smooth sailing.
I do have a couple of issues with the Viper ROM, but all in all it's fine and I'll post those questions in the Viper thread.
Thanks again for everyones help!

mrwizard65 said:
ROM did install correctly but was still bringing me to the HTC splash screen with developer warning.
As a last ditch effort I downloaded the correct RUU and ran it. Device now works properly, but when trying to go through the tool kit again I get to the bootloader in the end and it says "relocked" even though I submitted my token, got the proper .bin and unlocked.
Any thoughts? Everyone has been very helpful.
Click to expand...
Click to collapse
Re-unlocking is a *****. Took me about 80 tries. Reboot phone, reboot pc, keep trying. Eventually it will work. You didn't need to run the ruu.. You may just want to keep the phone in stock state if this seems complex to you.
Sent from my One X using xda app-developers app

go into bootloader manually then plug phone to pc. works first time to unlock.

RUU Error 171 Stuck on waiting for boot loader

As the title says, RUU attempts booting my phone but it never comes back on. Even selecting restart boot loader in fastboot or a command it doesn't power itself back on. I have read through other forums and nothing has worked for me yet.
EDIT: I should probably clarify fastboot usb WORKS. Ruu must see my phone considering it detects the ROM version and turns the phone off in attempt to reboot. Anything that I do that requires a reboot doesn't work. I have tried unlocking the bootloader again, everything is fine until it comes to rebooting then I must turn the phone on myself and nothing changes...... IT DOESN'T REBOOT ITSELF therefore seemingly nothing wants to work. And the HTC boot screen is gone??
More background information: http://forum.xda-developers.com/showthread.php?p=39046436#post39046436

What we're your steps exactly? Did you relock your bootloader

a box of kittens said:
What we're your steps exactly? Did you relock your bootloader
Click to expand...
Click to collapse
Yes I did through fast boot with the oem lock command. I've tried installing RUU with a Windows 7 laptop (has HTC sync software) and Windows 8 desktop (basic drivers). Both failed, tried using Windows XP/Vista in compatibility modes and running as an admin with the same results.

Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.

iElvis said:
Error 171 is a connection error, meaning the RUU can't connect to/find your phone.
Try uninstalling HTC Sync, rebooting your pc, and installing it again. If you've got the Android SDK installed, be sure it's also fully updated.
Click to expand...
Click to collapse
No luck. And I believe it does see the phone in the beginning of the installation. It makes it reboot to the boot loader and that's where it loses the connection. The phone just isn't booting itself back up. I appreciate the reply, if you have anymore ideas please let me know.

Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?

iElvis said:
Could be something got corrupted. Try redownloading the ruu. Does adb see the phone?
Click to expand...
Click to collapse
Re-downloaded RUU and still no go. And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.

Does anybody else have some more ideas?

Okkoto said:
And adb doesn't see my phone, will it on the fastboot menu? I'm not to familiar with it.
Click to expand...
Click to collapse
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.

redpoint73 said:
No. If adb doesn't see it, fastboot won't either. Does the command "adb devices" (no quotes) show the device as connected?
It sounds like the connection might be working for a few things (like rebooting the phone, as you mentioned). But I still think a connection issue is the main problem.
Click to expand...
Click to collapse
Fastboot does see it but adb does not. And what I mean by rebooting the phone in my last post is RUU attempts rebooting it from the boot loader which does turn the phone off but it stays turned off. I've used other commands to reboot the phone from the fastboot screen and those too turn off the phone then again it doesn't come back on like a reboot should do.

I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.

Okkoto said:
I have about completely gave up and going back to using a regular feature phone. I have watched a video about a jtag repair service and was wondering about that or just selling the phone as bricked on ebay.
Click to expand...
Click to collapse
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.

DvineLord said:
don't sell it as bricked since it is obviously not bricked. you could get more money just saying you dont wtf your doing and gave up on it. but ill buy it as a bricked phone =) ill give you 50 bucks.
Click to expand...
Click to collapse
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.

i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.

Okkoto said:
Well if it's not bricked then I sure wish somebody would lead me to the right direction. I have tried 5 different PCs (which all show as connected through fastboot) and they all came with the same error. I've tried everything I could possibly think of and I haven't seen anyone else with quite the same problem I'm having.
I still have not completely gave up and have already decided against selling it as "bricked". The bootloader still comes up so there is at least some hope.
Click to expand...
Click to collapse
when you say it shows connected through fastboot what do you mean?
how are you getting the device into fastboot - through recovery??
oh, and what was on your device before you tried loading the RUU?

kkm68 said:
i just had the same problem. the solution was simple - i switch usb-port from front one to the backside one which is directly on motherboard.
Click to expand...
Click to collapse
Yes this + if you're on a usb3 port try usb2. Also make sure you're using the cable that came with the phone as I understand other cables may cause issues like this. Also, avoid using a hub or usb extension.

Solution to error 171
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!

diegoyabishh said:
I had the same problem and after many attempts I finally got it to work!
-Uninstall anything HTC related from your computer such as HTC Sync Manager and Drivers. Also delete any HTC folders from your program files.
-Make sure you leave the sdk and adb stuff that you downloaded.
-Connect your device via USB to your computer and let it recognize it. It will automatically install default drivers.
-A pop-up asking to install HTC Sync will appear, just ignore it.
-Make sure you set Fast Boot OFF on your phone, and Debugging ON.
-Leave your phone ON and run the RUU set up.
-Then follow the steps on the wizard and everything should work just fine!
Click to expand...
Click to collapse
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.

jondon156 said:
I have a similar problem with my HTC One. I am stuck in the bootloader and any action I take leads straight into a boot loop. If I try to reboot, reboot-bootloader, go into recovery (twrp), or factory reset it goes into a boot loop. Also I can't lock the bootloader and flashing my recovery doesn't help, even though it says its a success. I've tried three computers and deleted and reinstalled drivers but still the computers only find my phone in fastboot usb and can't find it using adb.
This solution above won't help me since I can't get my phone on for the life of me. I tried running RUU and All-in-One Toolkit but no luck. RUU fails finding the bootloader since my phone gets stuck in its boot loop. I am fresh out of ideas so any other ways to fix this issue would be greatly appreciated.
BTW I found my phone is this condition when I pulled it out of my pocket. I never installed custom ROMs on it. It is unlocked and rooted though running 4.2.2 (3.05.651.6) hoot 1.55. The only thing I can think of is that an OTA update got pushed to my phone and bricked it. That or for some strange reason something went wrong with phone from the rooting process after two weeks of it working perfectly.
Click to expand...
Click to collapse
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita

Heisenberg said:
Nobody here can help you as we don't have any experience with your device. You'd be much better off asking in the HTC One forum which you'll find here:
http://forum.xda-developers.com/htc-one
Sent from my Evita
Click to expand...
Click to collapse
hi all..
facing same problem with HTC Desire 816 n 4g... have anyone got any solution??
plz pass it..
thank you

[Q] HOX will not boot up or turn on or have LED response

Hey everyone. So everything was good for the last couple of days as I was on JellyBAM 6.6.0 evita. This morning after charging my phone I go to open it, view some websites etc. Phone reboots by itself, goes to lockscreen. I try unlocking my lockscreen everything good for about 10 seconds. Try to open facebook up, and boom phone goes black and will not turn on. I know for a fact that is 100% charged as when I woke up I checked the battery as I usually do to see if it charged or not.
I am pretty sure I am on Hboot 1.09 or less as I bought the phone close to the release date. Any thoughts because its weird how I cant turn even turn it on or have a LED light show up when it charges.
Thanks in advance
EDIT: Ok somehow my phone just turned on by itself and I took the opportunity to go into TWRP. Tried restoring but to a previous backup. Became stuck in boot screen. Went back into twrp tried to wipe the system and factory reset but somehow it says failed and that its not able to mount storage or anything. All of my data is gone now for some reason and it says no OS is installed. Do I have to RUU back again?

have you tried getting into bootloader by holding volume down and power? or a hard reset by holding power button for like 30 seconds
Sent from my HTC One X using xda premium

NerdFurgison said:
have you tried getting into bootloader by holding volume down and power? or a hard reset by holding power button for like 30 seconds
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah I forgot to mention I have tried getting into bootloader using the volume down + power process along with holding the power button. Nothing is working.

This phone has well-known power management issues. Sometimes the battery stats get corrupted and the phone thinks the battery is dead when it isn't. Unfortunately, this sometimes results in a brick.
Plug into your PC and see what pops up in Device Manager. If you get QHUSB_DLOAD, you've been bricked. However, this may be fixable since you're on 1.09.

Ok somehow my phone just turned on by itself and I took the opportunity to go into TWRP. Tried restoring but to a previous backup. Became stuck in boot screen. Went back into twrp tried to wipe the system and factory reset but somehow it says failed and that its not able to mount storage or anything. All of my data is gone now for some reason and it says no OS is installed. Do I have to RUU back again?
Additionally, under device manager it comes up as unknown. I am going to install the ADB drivers for Windows 8 and see if that does anything

Zobabe said:
Ok somehow my phone just turned on by itself and I took the opportunity to go into TWRP. Tried restoring but to a previous backup. Became stuck in boot screen. Went back into twrp tried to wipe the system and factory reset but somehow it says failed and that its not able to mount storage or anything. All of my data is gone now for some reason and it says no OS is installed. Do I have to RUU back again?
Additionally, under device manager it comes up as unknown. I am going to install the ADB drivers for Windows 8 and see if that does anything
Click to expand...
Click to collapse
Well, wiping /system and factory reset means the OS is erased. Could be the sdcard got corrupted. You'll need to reformat it.
Good news is you're not bricked; its just a matter of getting the software in order.

iElvis said:
Well, wiping /system and factory reset means the OS is erased. Could be the sdcard got corrupted. You'll need to reformat it.
Good news is you're not bricked; its just a matter of getting the software in order.
Click to expand...
Click to collapse
Ok so should I follow like this.
Download HTC drivers
Download 1.71 RUU
Done?
Because right now my computer does not recognize my phone. Installing the htc sync and the drivers hasnt made my computer (windows 8) to recognize my phone.

Zobabe said:
Ok so should I follow like this.
Download HTC drivers
Download 1.71 RUU
Done?
Because right now my computer does not recognize my phone. Installing the htc sync and the drivers hasnt made my computer (windows 8) to recognize my phone.
Click to expand...
Click to collapse
Did you try formatting in twrp? Ruu'ing might be overkill here. Can adb see the phone even if windows can't?

Zobabe said:
Ok so should I follow like this.
Download HTC drivers
Download 1.71 RUU
Done?
Because right now my computer does not recognize my phone. Installing the htc sync and the drivers hasnt made my computer (windows 8) to recognize my phone.
Click to expand...
Click to collapse
I had a similar problem last night with a "missing" SDcard in TWRP. Thankfully, I found a utility that you can run through fastboot that will restore the SDcard without ruu.
HOWEVER...that utility and website link that I found it on are on my computer at home...and I'm not at home
Although, I did find the utility through a google search.
Let me know if you find it. If not - I'll find the link when I get home.

iElvis said:
Did you try formatting in twrp? Ruu'ing might be overkill here. Can adb see the phone even if windows can't?
Click to expand...
Click to collapse
I am having trouble downloading ADB drivers atm. Trying to find an article that explains it. Kind of a noob at this type of stuff. As for formatting, I dont see an option in TWRP.

razorc03 said:
I had a similar problem last night with a "missing" SDcard in TWRP. Thankfully, I found a utility that you can run through fastboot that will restore the SDcard without ruu.
HOWEVER...that utility and website link that I found it on are on my computer at home...and I'm not at home
Although, I did find the utility through a google search.
Let me know if you find it. If not - I'll find the link when I get home.
Click to expand...
Click to collapse
If you could please link it to me, it would be greatly appreciated. Thanks

I dont know if this matters but I factory resetted from bootloader in the beginning after I was able to turn on my phone. Maybe everything got wiped because I did that?
Does anyone know how I can get windows to recognize my phone because I have looked at several guides on google and nothing is working for me.
Thanks

Zobabe said:
If you could please link it to me, it would be greatly appreciated. Thanks
Click to expand...
Click to collapse
Here is that link I was telling you about.
Follow the instructions in the cmd. There should be only two steps.
Good luck!
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL

razorc03 said:
Here is that link I was telling you about.
Follow the instructions in the cmd. There should be only two steps.
Good luck!
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL
Click to expand...
Click to collapse
in order to this though, my computer has to be able to recognize my htc one x. I cant even get it to recognize. any tips?

Zobabe said:
I dont know if this matters but I factory resetted from bootloader in the beginning after I was able to turn on my phone. Maybe everything got wiped because I did that?
Does anyone know how I can get windows to recognize my phone because I have looked at several guides on google and nothing is working for me.
Thanks
Click to expand...
Click to collapse
yea, factory reset in bootloader is bad. never do it again unless you are completely stock.

DvineLord said:
yea, factory reset in bootloader is bad. never do it again unless you are completely stock.
Click to expand...
Click to collapse
haha yeah I realized that once I did it and read it in the sticky in the android development section. Do you have any idea of how I could get windows 8 to recognize my htc one x?

windows 8 is the last thing in the world i would let touch my computer. windows xp for life.
i heard alot of people having issues with win8 and usb 3.0 ports.