Database Info

Semi-Bricked HTC ONE X

SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85

you are lucky to have white screen

You posted in the wrong section...
This is for devsonly
Sent from my HTC One X using xda premium

xpurpleblob said:
SO I've basically tried everything here,
it all went wrong when I stupidly forgot that I was in the wrong section and was trying to flash a international rom...
anyways now the phone only goes up to the HTC white screen and is stuck there.
BAsically i did the fastboot clearing and erything.
I also locked my bootloader and then tried to write the ruu again.
However while im doing that about after 4% , it gives me the error code 171, saying that my phone ahs been disconnected. I installed the HTC sync and everything what am i doing wrong....thanks
im using the ruu 1.85
Click to expand...
Click to collapse
If you updated to 4.0.4 (2.20) before you killed your phone, then use the 2.20 RUU found on HTC's website. You can't be updated and use a downgraded RUU. If that doesn't work, and your bootloader is locked and everything, then idk what to say. Try taking it to ATT if you're stillin your 30 day period. If try even if you're not.
---------- Post added at 12:19 AM ---------- Previous post was at 12:17 AM ----------
And you are in the wrong section. This belongs in the Q&A.

vin255764 said:
you are lucky to have white screen
Click to expand...
Click to collapse
what does this mean...

xpurpleblob said:
what does this mean...
Click to expand...
Click to collapse
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?

HTC_Phone said:
It means your lucky your phone still turns on. A brick means the phone won't turn on at all, or anything. You're lucky to be seeing the white HTC Screen. You really are.
EDIT: Download the HTC Drivers again, and reinstall them. That might help the connectivity issues. Or, try using a different USB port on your computer. When you plug the phone in, do you hear a resounding "beep", meaning the computer has recognized the device being plugged in?
Click to expand...
Click to collapse
I believe so, maybe not I'm currently doing work right now so I will check later.
However, the computer seems to recognize my phone when I'm applying the RUU, it stops at about 7% then shows the ERRor message 171
Thanks for the help.

can anyone please help

Where can I get stock recovery, stock boot for the phone?

First to Relock your device, you will want to boot into your bootloader and select fastboot. After you've selected fastboot plug your device into your pc and open a command prompt. You'll want to type 'cd C:\Android' and then 'fastboot oem lock' and your phone will restart with a locked bootloader. Now you can upgrade to the RUU without any issues.
Now find your ruu here http://forum.xda-developers.com/show....php?t=1671237 under STOCK RUUs AND RELATED.
Once you've finished upgrading your ruu you will want to boot into your bootloader again, with your device unplugged, and select fastboot. THEN plug your device in and run your command prompt again on your PC. Again, cd to C:\Android and type in the following command to unlock your bootloader again: 'fastboot flash unlocktoken Unlock_code.bin'
Hope this helps ^____^

thanks for the reply, however ur link is broken.

And if possible can someone list all the programs I need for this task...
the Htc sync, android sdk,.. etc
and do i need the adt file??

Also i am getting a signature verify failure when im flashing a recovery.img....
also btw i have the nandroid backups. i cant access the recovery in the hot boot though

xpurpleblob said:
thanks for the reply, however ur link is broken.
Click to expand...
Click to collapse
He meant to link the Index thread for the RUUs: http://forum.xda-developers.com/showthread.php?t=1671237

I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/

subarudroid said:
I did the same. :silly: I've allways used CM recovery. couldn't get to flash. TWRP worked great!
If you have fastboot hopfully this works. May not get back to stock without RUU. However who cares.
Flashing custom ROMs is fun. :victory:
http://theunlockr.com/2012/06/05/how-to-install-twrp-2-1-recovery-on-att-and-rogers-htc-one-x/
Click to expand...
Click to collapse
I don't think I can use that because my bootloader is locked.

Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?

subarudroid said:
Did you try SUPERCID? How did you do all that without SUPERUSER# ?
correct me if I'm wrong but you should still be able to unlock the bootloader if you have fastboot?
Click to expand...
Click to collapse
i relocked my bootloader to run the RUU, however when I run it the eroor code 170 comes up

I tried 3 diff. RUU's none of them worked. I'm on AT&T.
You should be able to Unlock bootloader again though.
HTC devs would have email you the unlock_code.bin file
Maybe you deleted from desktop? IT might still be in your email?
IF your windows you can hit (Shift+rightclick) in folder run CMD.
fastboot erase cache
fastboot flash unlocktoken Unlock_code.bin make sure your fastboot files are in there also.
THis thread might also help. I take no credit. But I hope we can help you get your phone up and running to some degree.
http://forum.xda-developers.com/showthread.php?t=1671396
---------- Post added at 08:03 PM ---------- Previous post was at 07:37 PM ----------
I should also know note that I cannot take any responsibility for your phone being destroyed
Sent from my One X using xda app-developers app

Alright I got it working. If anybody ever gets the same problem as me, disable your antivirus, take out your internet connection from the computer, run as administrator for the RUU, and close all programs except for the RUU.
I BELIEVE THE MOST IMPORTANT WAS TO OPEN A NEW ADMINISTRATOR ACCOUNT ON THE COMPUTER.
I don't know which of these factors are definite but follow these steps and hopefully you will solve your problem too.

Please help installing CleanROM 4.5....Stuck in Recovery....

I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!

reflash
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp

thesm4rt1 said:
Try flashing the boot.IMG from the the zipped ROM you were trying to flash to boot partition through the bootloader (cmd in windows: fastboot flash boot boot.img[enter] after you put The boot.img in the same folder as the adb & cd to that folder) and flash cwm for recovery, then you can reflash twrp
Click to expand...
Click to collapse
I will definitely be trying that. Will be back in a couple of hours and let you know how it went. Thank you!

bbonline said:
I had my phone rooted and unlocked and was also using CleanROM 4.1 before I decided today to change to CleanROM 4.5.
So, I downloaded the file and went to Recovery and flashed it (it did take very little time with flashing which I found rather strange.) When I rebooted, the phone was stuck at the HTC screen. I figured that I MIGHT have had CWM installed and I didn't know it (I can't be quite 100% sure of this as I thought I DID have TWRP since it was a touch recovery that I had.) Since I was able to boot back up to Fastboot, I said "Let me flash the TWRP recovery file and try again".....Well, I did that and according to the Command Prompt it was successful (showed sending, writing, finished etc....) Once finished, I rebooted back and all I see now is the TeamWin logo in Recovery and THAT'S IT. It won't give me any menu options. If I let it sit, it will reboot back to the HTC screen.
What are my options right now? Is there a specific file I can flash through Fastboot that will allow me to proceed?
I would appreciate the help and I'll be sure to come back and let you know how successful I was. :fingers-crossed:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.

Butters619 said:
In the future I suggest factory wipe even if going from CR to CR. Also, make sure to check the MD5 once you move the file on to your storage.
Click to expand...
Click to collapse
I did do the factory wipe.
By the way, I tried what I was told to do and nothing happened. It successfully flashes the boot image and recovery, but when it tries to boot into the recovery, it just freezes in the recovery with the word TEAMWIN and a blue background....No menu or options.... I did try several different ways by downloading and installing several versions of the CWM and TWRP, but no success. Any other suggestions? Will I be stuck with this piece of brick now? Please help.

bbonline said:
****BTW, I want to point out that my phone has had this strange message everytime it reboots (over the past few months since unlocked) stating: "This build is for development purposes only. Do not distribute outside of HTC without HTC's written permission....etc..." What does that mean? I don't like that message to appear everytime I reboot my phone. Thanks again!
Click to expand...
Click to collapse
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.

Butters619 said:
^That right there is normal by the way and will always be there.
Looks like it's time for you to relock your bootloader (don't worry you can unlock it again), download an RUU, and try again.
Click to expand...
Click to collapse
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!

bbonline said:
Ughh! Do you know if I will lose any documents/pictures that are in my USB storage? Which RUU do you think is the best in my case? Thanks!
Click to expand...
Click to collapse
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!

Butters619 said:
You will lose the contents of your SD card, which is why you should back that up before flashing. Since you were on CR 4.1, I would go with the 1.85 RUU. If you use 2.20, you will add an extra step or two in when it comes to flashing ROMs. But hey, your phone should work again!
Click to expand...
Click to collapse
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?

bbonline said:
I know, silly me. Usually I backup the data and everything goes well and when I don't, there goes my luck! I really appreciate the suggestion.
One quick question, if in the future I need to have the phone sent in for warranty, is this the same procedure I need to follow? Relock and flash an RUU? Will they not know it had been unlocked before?
Click to expand...
Click to collapse
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
Darn.... I just hope I don't have to deal with sending it for any repair. Gave you thanks!

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
But only if they reboot and look, which from what I've seen here, they never seem to do.

iElvis said:
But only if they reboot and look, which from what I've seen here, they never seem to do.
Click to expand...
Click to collapse
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.

Butters619 said:
Exact same procedure, but yes they will know. The giant RELOCKED gives it away lol.
Click to expand...
Click to collapse
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
Butters619 said:
I took my One X back to Best Buy to swap it out just before the return policy expired because my gf dropped it and put a small dent in the casing and I didn't even bother to relock or even RUU my device. I said I had a software issue and couldn't get the OTA. They turned it on and played with it and it had a custom boot animation and a ROM on it lol. They also couldn't get the OTA so they approved the return.
Click to expand...
Click to collapse
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on

trichrome1 said:
it doesn't say RELOCKED when you run an RUU. It gets rid of everything like Tampered and Unlocked and returns the phone to LOCKED. like it came
---------- Post added at 08:34 PM ---------- Previous post was at 08:31 PM ----------
hahaha, thank god for company cutbacks sometimes... it makes the employees not give a ****. and rightfully so too!!
the fact that companies cut back to make a few more billion dollars makes me sick anyways. but this is not the place for this conversation. carry-on
Click to expand...
Click to collapse
Nope once you unlocked it won't ever say locked again. Just re-locked

gunnyman said:
Nope once you unlocked it won't ever say locked again. Just re-locked
Click to expand...
Click to collapse
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.

trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
You should probably double check that. Anybody with an AT&T One X had to have SuperCID to unlock their bootloader so that wouldn't matter. I have unlocked two AT&T One Xs and run the 1.85 RUU on both (one of them a couple times) and I have run the 2.20 RUU on one. every time it says RELOCKED.

Mine did this to when going to 4.5.
I did the following to get back into Recovery.
Use fastboot to flash the boot.img from the cleanrom 4.5 zip.
"fastboot flash boot boot.img"
I then flashed the recovery (TWRP 2.2.1.4 at the moment) again to the phone.
next I erased Cache.
"fastboot erase cache"
I then used the phone itself to reboot the bootloader and went into recovery. It took about 10 minutes but recovery finally booted.
At this point I had no access to anything on the SD card. so I selected mount and mounted the sd card as disk drive to access it through my PC. I was forced to format the drive at this point and loaded a fresh copy of the ROM onto the drive for flashing.

You probably just got a wrong recovery. The recovery on twrp website didn't work for me. The one I downloaded from the development section works fine.
Sent from my One X using xda app-developers app

trichrome1 said:
not true, mine said LOCKED after running the att 1.85 RUU.. I had SUPERcid though if that makes any difference.
Click to expand...
Click to collapse
Screenshots PLS

PLEASE HELP!!! My HTC One X is completely messed up and i would like some help**

Hello everybody i am posting because my One X is messed up. I bought the phone from radio shack and i love it. When i first bought it i rooted it and then downloaded fun root apps like titanium backup, and set cpu. I heard about custom roms and i wanted to try one. So i followed the instructions given on the website. Im sorry i dont remember what website it was that i downloaded it from. So i downloaded Clockworkmod from play store and installed it on my phone. Then copied the rom to my sd card. I tried to flash is but nothing would happen. So i tried to boot into recovery mode and i woould get a legal actions page, then my bootloader would say ***tampered*** ***locked*** ***security warning***. So then i tried to unlock my boot loader via htc dev and i got the error 160 mid not allowed. So i wanted to unroot and restore so i deleted supersu and the su files from my phone and i used root checker to check if unrooted. it said *not properly rooted*. But my phone can still view and download root apps.
Then i tried to restore my phone to stock, but when i pressed factory reset i would get the same legal actions page and my boot loader would say *tampered* *locked* *security warning*. And my att software update doesnt work. when i press on it it says htc dm has stopped and after that it does nothing when i press the button. And many apps close unsuspectingly. I would like to completely revert my phone to stock so i can start over again. thank you.
I have the HTC One X dual core usa version
i bought it at radio shack
It is on AT&T

Sounds like you might have tried to install a rom for the international version. Be thankful it didn't work.
You can't unlock via htcdev without changing your CID because AT&T is blocking it.
The version of CWM in the Play Store (ROM Manager?) is not supported for this phone and will not work.
To restore to stock, you need to flash the RUU for your current version. Check your software version in Settings.

This may come across as rude but you are obviously aware of XDAs existence since you are posting here, why on earth would you do anything to your phone without FIRST checking XDA to make sure it's kosher? I see way too many threads like this and it boggles my mind.
You guys don't want to come to XDA for help with your ROMs and mods, but as soon as you screw something up you come running to us for assistance.
Sent from my HTC One X using xda premium

ewokiscool said:
Hello everybody i am posting because my One X is messed up. I bought the phone from radio shack and i love it. When i first bought it i rooted it and then downloaded fun root apps like titanium backup, and set cpu. I heard about custom roms and i wanted to try one. So i followed the instructions given on the website. Im sorry i dont remember what website it was that i downloaded it from. So i downloaded Clockworkmod from play store and installed it on my phone. Then copied the rom to my sd card. I tried to flash is but nothing would happen. So i tried to boot into recovery mode and i woould get a legal actions page, then my bootloader would say ***tampered*** ***locked*** ***security warning***. So then i tried to unlock my boot loader via htc dev and i got the error 160 mid not allowed. So i wanted to unroot and restore so i deleted supersu and the su files from my phone and i used root checker to check if unrooted. it said *not properly rooted*. But my phone can still view and download root apps.
Then i tried to restore my phone to stock, but when i pressed factory reset i would get the same legal actions page and my boot loader would say *tampered* *locked* *security warning*. And my att software update doesnt work. when i press on it it says htc dm has stopped and after that it does nothing when i press the button. And many apps close unsuspectingly. I would like to completely revert my phone to stock so i can start over again. thank you.
I have the HTC One X dual core usa version
i bought it at radio shack
It is on AT&T
Click to expand...
Click to collapse
First, you need to do A LOT more reading before you try to unlock your bootloader and flash ROMs. You missed a ton of steps and it is pretty clear you didn't do your homework. I am not trying to be rude, but trying to save you from ruining your phone.
Check what firmware you have. I assume 1.85 if you have root, but please check. If you want to be able to re-root your phone do not use the 2.20 RUU! Go download the RUU . Follow the instructions and run the RUU to return your phone to stock.
http://forum.xda-developers.com/showthread.php?t=1670238 (1.85 RUU)
You can then start the process over with rooting and unlocking. You must have SuperCID before you can unlock your bootloader. Use TWRP and not CWR because it is not supported on the AT&T One X. You must NEVER try installing a ROM meant for the international version. (Stay in this section of the forum!) Once you root and unlock, you will not be able to download OTAs from HTC.
http://forum.xda-developers.com/showthread.php?t=1671237 (AT&T One X Resources. Pretty much every thing you need)

Butters619 said:
First, you need to do A LOT more reading before you try to unlock your bootloader and flash ROMs. You missed a ton of steps and it is pretty clear you didn't do your homework. I am not trying to be rude, but trying to save you from ruining your phone.
Check what firmware you have. I assume 1.85 if you have root, but please check. If you want to be able to re-root your phone do not use the 2.20 RUU! Go download the RUU . Follow the instructions and run the RUU to return your phone to stock.
http://forum.xda-developers.com/showthread.php?t=1670238 (1.85 RUU)
You can then start the process over with rooting and unlocking. You must have SuperCID before you can unlock your bootloader. Use TWRP and not CWR because it is not supported on the AT&T One X. You must NEVER try installing a ROM meant for the international version. (Stay in this section of the forum!) Once you root and unlock, you will not be able to download OTAs from HTC.
Click to expand...
Click to collapse
thankyou so much!! that was such a stupid mistake. The indian people making the videos i was watching for instructions should have been a dead giveaway that it was for the international version!! again thank you so much. so where can i download RUU and instructions. and if you can what would be the best way to root and unlock bootloader for my version of the phone?

ewokiscool said:
thankyou so much!! that was such a stupid mistake. The indian people making the videos i was watching for instructions should have been a dead giveaway that it was for the international version!! again thank you so much. so where can i download RUU and instructions. and if you can what would be the best way to root and unlock bootloader for my version of the phone?
Click to expand...
Click to collapse
I edited my reply and included two links. First is to the 1.85 RUU. Make sure you don't have 2.20 by going to Settings -> About -> Software Information and look at Software Number. As long as you don't have 2.20, download that RUU, plug your phone in, and run it. IT WILL ERASE EVERYTHING! so make sure to back up the contents of your SD card first.
The second link is to the AT&T One X resource Roll-up. Everything you need to root/unlock/rom will be in there.
The steps are in this order:
1. Root using the 1.85 root
2. Get SuperCID
3. Go to HTCDev.com to get unlock token, flash unlock token, unlock bootloader
4. Flash recovery (TWRP)
5. Flash ROM
Make sure you read ALL of the instructions first!! And I would recommend CleanROM once you get that far.
Disclaimer: I am not responsible if you mess up your phone.

ewokiscool said:
thankyou so much!! that was such a stupid mistake. The indian people making the videos i was watching for instructions should have been a dead giveaway that it was for the international version!! again thank you so much. so where can i download RUU and instructions. and if you can what would be the best way to root and unlock bootloader for my version of the phone?
Click to expand...
Click to collapse
Butters619 said:
Check what firmware you have. I assume 1.85 if you have root, but please check. If you want to be able to re-root your phone do not use the 2.20 RUU! Go download the RUU . Follow the instructions and run the RUU to return your phone to stock.
http://forum.xda-developers.com/showthread.php?t=1670238 (1.85 RUU)
You can then start the process over with rooting and unlocking. You must have SuperCID before you can unlock your bootloader. Use TWRP and not CWR because it is not supported on the AT&T One X. You must NEVER try installing a ROM meant for the international version. (Stay in this section of the forum!) Once you root and unlock, you will not be able to download OTAs from HTC.
http://forum.xda-developers.com/showthread.php?t=1671237 (AT&T One X Resources. Pretty much every thing you need)
Click to expand...
Click to collapse
dude.
edit: Whoops! Didn't realize the edit had come afterwards. That was some odd timing.
But seriously, poke around the forums. Things are labeled pretty well around here.

ewokiscool said:
thankyou so much!! that was such a stupid mistake. The indian people making the videos i was watching for instructions should have been a dead giveaway that it was for the international version!! again thank you so much. so where can i download RUU and instructions. and if you can what would be the best way to root and unlock bootloader for my version of the phone?
Click to expand...
Click to collapse
Please read and make sure you know what you are doing before you do! I can not stress this enough.
Rooting/unlocking is very easy and take no time at all, but please read.
---------- Post added at 11:23 AM ---------- Previous post was at 11:21 AM ----------
Protogon said:
dude.
edit: Whoops! Didn't realize the edit had come afterwards. That was some odd timing.
But seriously, poke around the forums. Things are labeled pretty well around here.
Click to expand...
Click to collapse
I am just trying to guide him in the right direction. It is up to him to make sure to read everything and know what he is doing to his phone.

Butters619 said:
I am just trying to guide him in the right direction. It is up to him to make sure to read everything and know what he is doing to his phone.
Click to expand...
Click to collapse
It certainly is, but it says something when he asks for this information despite having a large and detailed resource roll-up stickied in the Development forum.

Butters619 said:
I edited my reply and included two links. First is to the 1.85 RUU. Make sure you don't have 2.20 by going to Settings -> About -> Software Information and look at Software Number. As long as you don't have 2.20, download that RUU, plug your phone in, and run it. IT WILL ERASE EVERYTHING! so make sure to back up the contents of your SD card first.
The second link is to the AT&T One X resource Roll-up. Everything you need to root/unlock/rom will be in there.
The steps are in this order:
1. Root using the 1.85 root
2. Get SuperCID
3. Go to HTCDev.com to get unlock token, flash unlock token, unlock bootloader
4. Flash recovery (TWRP)
5. Flash ROM
Make sure you read ALL of the instructions first!! And I would recommend CleanROM once you get that far.
Disclaimer: I am not responsible if you mess up your phone.
Click to expand...
Click to collapse
before i do anything i want to know if it will work because my software number is: 1.73.502.1

Protogon said:
It certainly is, but it says something when he asks for this information despite having a large and detailed resource roll-up stickied in the Development forum.
Click to expand...
Click to collapse
Yeah he followed a YouTube video and then went straight to Q&A when things went wrong and clearly never stopped by the dev threads once. Perhaps I was being too nice by giving links. Hopefully he shakes that habit quickly.

The second link is to the AT&T One X resource Roll-up. Everything you need to root/unlock/rom will be in there.
The steps are in this order:
1. Root using the 1.85 root
2. Get SuperCID
3. Go to HTCDev.com to get unlock token, flash unlock token, unlock bootloader
4. Flash recovery (TWRP)
5. Flash ROM
Revise - 4.a Make nandroid backup
:beer::beer:
Sent from my SPH-L710 using xda premium

18th.abn said:
The second link is to the AT&T One X resource Roll-up. Everything you need to root/unlock/rom will be in there.
The steps are in this order:
1. Root using the 1.85 root
2. Get SuperCID
3. Go to HTCDev.com to get unlock token, flash unlock token, unlock bootloader
4. Flash recovery (TWRP)
5. Flash ROM
Revise - 4.a Make nandroid backup
:beer::beer:
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Good point! I just automatically do that every time I flash a rom so I always forget to include that as an additional step. But that will save a lot of time if anything goes wrong.
---------- Post added at 12:03 PM ---------- Previous post was at 11:53 AM ----------
ewokiscool said:
before i do anything i want to know if it will work because my software number is: 1.73.502.1
Click to expand...
Click to collapse
Although the answer is already in this thread, if I were you, I would take this time to use the search and find out what an RUU is and what it does. You are going to use them many times in the future so might as well know.

This is really starting to become an epidemic
Sent from my One X using xda app-developers app

InflatedTitan said:
This is really starting to become an epidemic
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
You should see all the skyrocket users coming to the i777 forums saying they bricked and have no idea why... Probably by flashing a rom for the wrong phone....

Butters619 said:
First, you need to do A LOT more reading before you try to unlock your bootloader and flash ROMs. You missed a ton of steps and it is pretty clear you didn't do your homework. I am not trying to be rude, but trying to save you from ruining your phone.
Check what firmware you have. I assume 1.85 if you have root, but please check. If you want to be able to re-root your phone do not use the 2.20 RUU! Go download the RUU . Follow the instructions and run the RUU to return your phone to stock.
http://forum.xda-developers.com/showthread.php?t=1670238 (1.85 RUU)
You can then start the process over with rooting and unlocking. You must have SuperCID before you can unlock your bootloader. Use TWRP and not CWR because it is not supported on the AT&T One X. You must NEVER try installing a ROM meant for the international version. (Stay in this section of the forum!) Once you root and unlock, you will not be able to download OTAs from HTC.
http://forum.xda-developers.com/showthread.php?t=1671237 (AT&T One X Resources. Pretty much every thing you need)
Click to expand...
Click to collapse
thankyou so much i got the RUU and ran it. it worked llike a charm. now for rooting i tried the one click rooot a bunch and did not work, then i tried your link and it did not work. i tried to install the super cid but every website says u must be rooted before doing so

ewokiscool said:
thankyou so much i got the RUU and ran it. it worked llike a charm. now for rooting i tried the one click rooot a bunch and did not work, then i tried your link and it did not work. i tried to install the super cid but every website says u must be rooted before doing so
Click to expand...
Click to collapse
Did you make sure to use the 1.85 RUU?
---------- Post added at 01:36 PM ---------- Previous post was at 01:27 PM ----------
ewokiscool said:
thankyou so much i got the RUU and ran it. it worked llike a charm. now for rooting i tried the one click rooot a bunch and did not work, then i tried your link and it did not work. i tried to install the super cid but every website says u must be rooted before doing so
Click to expand...
Click to collapse
As long as you flashed 1.85 then the root script will work. You may have to manually set the day ahead and try again a few times. Read the thread. Search the thread. Your answers are probably in there.
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
ewokiscool said:
thankyou so much i got the RUU and ran it. it worked llike a charm. now for rooting i tried the one click rooot a bunch and did not work, then i tried your link and it did not work. i tried to install the super cid but every website says u must be rooted before doing so
Click to expand...
Click to collapse
As long as you flashed 1.85 then the root script will work. You may have to manually set the day ahead and try again a few times. Read the thread. Search the thread. Your answers are probably in there.

Butters619 said:
Did you make sure to use the 1.85 RUU?
---------- Post added at 01:36 PM ---------- Previous post was at 01:27 PM ----------
As long as you flashed 1.85 then the root script will work. You may have to manually set the day ahead and try again a few times. Read the thread. Search the thread. Your answers are probably in there.
---------- Post added at 01:37 PM ---------- Previous post was at 01:36 PM ----------
As long as you flashed 1.85 then the root script will work. You may have to manually set the day ahead and try again a few times. Read the thread. Search the thread. Your answers are probably in there.
Click to expand...
Click to collapse
yes i looked at the whole thread and i am !))% sure i downloaded 1.85 i tried your link and looked at the whole thread and bumped the date ahead and rebooted a bunch of times and it didn't work. my error was when i would press att software update, nothing would happen. it would not check for updates or reboot. i tried two other root options like one click root. and another way from the link you sent me. does not work.

ewokiscool said:
yes i looked at the whole thread and i am !))% sure i downloaded 1.85 i tried your link and looked at the whole thread and bumped the date ahead and rebooted a bunch of times and it didn't work. my error was when i would press att software update, nothing would happen. it would not check for updates or reboot. i tried two other root options like one click root. and another way from the link you sent me. does not work.
Click to expand...
Click to collapse
So you run the one click method, it tells you to try to run the AT&T software update, and your phone does nothing? That is what is happening?

Butters619 said:
So you run the one click method, it tells you to try to run the AT&T software update, and your phone does nothing? That is what is happening?
Click to expand...
Click to collapse
yes when i press check for updates nothing happens. im not sure if this is the reason but after the RUU was done and my phone was put back to stock, a popup for att software update came up and it downloaded and i had the update. i went to about then software info the software number is 1.85 so i am very confused.

[Q] Changed CID back cannot unlock now

I changed my CID back to CID__001 from superCID and re-locked phone. Now when I go back to unlock with unlock_code.bin it does not work.
So I regenerate a token identifier....
C:\Users\M\HOX>fastboot oem get_identifier_token
< waiting for device >
... INFO
INFO< Please cut following message >
INFO<<<< Identifier Token Start >>>>
INFO639E7B248BDCAB6CBEA0577A98CD11AD
INFO0B20640D8180AB31F0B0DC2DDC62EB6A
INFO2524B5D27105D40678D5CC2C0E492220
INFO6A98F11162989E19E5F326B78E38D72E
INFO31E8D7A04B433C18C204D007D4B58689
INFO693ABAC1650EB10FC962312231F9E548
INFOF8D103A3EE4DD17F2D807751D006C739
INFO6254FA142E08F7DDBDF777300D8C8BE5
INFO4A6BA0CE58FFAAF25646B8B8A21CF068
INFO50F67F9A30A6DD984D50E497AF32485D
INFOFF19DBAB976D7F81CDC9E8320BD25E9D
INFOA56BB0B240AB81E35CD9742922C28320
INFOC02CF3A74B8589948155024DA23D31EC
INFO7620755FE9B5CA879B4968E79E239B39
INFOBFC9203AD5ED5373F568492B61B20700
INFO0C5B33DEA9E101B475EAF0E3CD4076F7
INFO<<<<< Identifier Token End >>>>>
OKAY [ 0.063s]
finished. total time: 0.063s
C:\Users\M\HOX>
On HTC site I get error code 160 mid not allowed when I try to generate a a new .bin

My Token identifier prior to the change was
<<<< Identifier Token Start >>>>
1A5036DDFCC755FA08619C55D40C47D0
A6FB8A57A0F9482C9174A6FA83921F0A
8D639270F2DCA79AD36FFB093D79F319
B9A66170322959FC5A93C12CB3500DF5
C6D42B624710F209FF4A4B70F5EAA9F3
B1947CFA26A96C7969F2788CAA631583
1C643ED6FEA902F1349AC5219AB8648C
C405010F564F16D1F63E3EA5DE089BE6
02D0CC3CBBFDDBBC74B8844144333E0E
BB70889A1F45259AE20ADCE88E7A201A
CF4BEB1A6F44E3162C63959FB800CF99
1E081824821F45DD2BEC4420A29A8F06
F4271D50F0F124EF324F5E41A34CE420
10572E09220654655A467B7AE1EAFB51
1D52CB57BA7154FB9CAC9F782494AF35
D76D2762018B42BEA736906581D9D1BE
<<<<< Identifier Token End >>>>>

The HTCDev.com site won't work with the AT&T CID, that's why it was changed in the first place.
I don't know why you changed the CID, what you hope to gain from it, and I don't recommend it. I don't see how its going to help your situation at all, really it just makes things harder for you (as you see you can't unlock the bootloader now).
I would also kindly suggest you back off from trying any new things, without at least coming on here and asking first if its a good idea. From your other thread, its apparent you are new to this phone, and are doing some things that are not necessarily the best way forward.

redpoint73 said:
The HTCDev.com site won't work with the AT&T CID, that's why it was changed in the first place.
I don't know why you changed the CID, what you hope to gain from it, and I don't recommend it. I don't see how its going to help your situation at all, really it just makes things harder for you (as you see you can't unlock the bootloader now).
I would also kindly suggest you back off from trying any new things, without at least coming on here and asking first if its a good idea. From your other thread, its apparent you are new to this phone, and are doing some things that are not necessarily the best way forward.
Click to expand...
Click to collapse
This phone is crap, from the confusing naming convention , bootloader lock, S-ON and the most fascinating that I just realized last night NO ADB IN BOOTLOADER OR STOCK RECOVERY. Way too complicated to work with.
So I am stuck now because I cannot RUU or get into past bootloader to change the recovery back to TWRP.

ADB works fine in bootloader. Looks like pilot error.
Complaining isn't going to help your case, might hurt it (discourage those of use who have been trying to help you).

Palmetto_X said:
This phone is crap, from the confusing naming convention , bootloader lock, S-ON and the most fascinating that I just realized last night NO ADB IN BOOTLOADER OR STOCK RECOVERY. Way too complicated to work with.
So I am stuck now because I cannot RUU or get into past bootloader to change the recovery back to TWRP.
Click to expand...
Click to collapse
I'm new to the onex myself, so I would like to know why you relocked it after all that work to get it unlocked? Just got mine unlocked with a custom Rom installed, and I don't know why you'd undo that.
Sent from my HTC One XL using Tapatalk 2

sizemore2000 said:
I'm new to the onex myself, so I would like to know why you relocked it after all that work to get it unlocked? Just got mine unlocked with a custom Rom installed, and I don't know why you'd undo that.
Click to expand...
Click to collapse
OP stated in another thread he bought his bootloader unlocked too.
But yes, I agree, there was not point in him relocking it. He wanted to return to stock. I suggested he flash a stock rooted ROM, but he either didn't listen, or was already too far down the relocking path (removed TWRP).

redpoint73 said:
ADB works fine in bootloader. Looks like pilot error.
Complaining isn't going to help your case, might hurt it (discourage those of use who have been trying to help you).
Click to expand...
Click to collapse
Tell me about ADB in bootloader? What do you mean pilot error?
thanks for hanging with me

I think you should PILOT the closest vehicle over the phone to end this misery for everyone

954wrecker said:
I think you should PILOT the closest vehicle over the phone to end this misery for everyone
Click to expand...
Click to collapse
Aren't you supposed to be in school?

Palmetto_X said:
Tell me about ADB in bootloader? What do you mean pilot error?
thanks for hanging with me
Click to expand...
Click to collapse
ADB should work fine in bootloader. Are you getting any error message, or no response when you try to use adb?
Does the phone show up if you type:
adb devices
If not, try to re-install HTC Sync.
---------- Post added at 12:05 PM ---------- Previous post was at 11:37 AM ----------
How did you end up with no TWRP? Did the RUU run partially, and return the phone to stock recovery? Or did you do something else to go to stock recovery?

redpoint73 said:
ADB should work fine in bootloader. Are you getting any error message, or no response when you try to use adb?
Does the phone show up if you type:
adb devices
If not, try to re-install HTC Sync.
---------- Post added at 12:05 PM ---------- Previous post was at 11:37 AM ----------
How did you end up with no TWRP? Did the RUU run partially, and return the phone to stock recovery? Or did you do something else to go to stock recovery?
Click to expand...
Click to collapse
Nothing shows up in adb devices.....I even ran adb logcat and went through all the menus on the phone seeing if it would catch
I will try to re install sync
In attempting to fix the RUU problem I have I would flash stock recovery, stock boot.img, relock, try to RUU......my last genius move was rename cid , stock recovery, boot.img, relock...........now I am dead in the water

Palmetto_X said:
Nothing shows up in adb devices.....I even ran adb logcat and went through all the menus on the phone seeing if it would catch
I will try to re install sync
Click to expand...
Click to collapse
This is the entire cause of your RUU troubles. Your computer is simply not talking to the phone.
Re-install HTC Sync, and try a different USB ports. Problems with the PC not seeing the phone are almost always due to one of these 2 things. Last resort is to use a different PC (if possible).
If adb doesn't see the phone, the RUU won't run either. Get the PC to see the phone, and the RUU will run.
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Wait, you said you relocked. So you must have had an adb/fastboot connection at some point.
Something is royally screwed here. It really seems to me that you are doing things to the phone, that you shouldn't. Seriously, don't do anything more to the phone, unless we tell you to. NOTHING.
How did you flash stock recovery?
What is the state of the phone now?
Flashing boot.img was not a good idea. Stock boot.img + CM10 will result in the phone not booting (wrong kernel), assume that is the state you are now in?

redpoint73 said:
This is the entire cause of your RUU troubles. Your computer is simply not talking to the phone.
Re-install HTC Sync, and try a different USB ports. Problems with the PC not seeing the phone are almost always due to one of these 2 things. Last resort is to use a different PC (if possible).
If adb doesn't see the phone, the RUU won't run either. Get the PC to see the phone, and the RUU will run.
---------- Post added at 01:31 PM ---------- Previous post was at 01:25 PM ----------
Wait, you said you relocked. So you must have had an adb/fastboot connection at some point.
Something is royally screwed here. It really seems to me that you are doing things to the phone, that you shouldn't. Seriously, don't do anything more to the phone, unless we tell you to. NOTHING.
How did you flash stock recovery?
What is the state of the phone now?
Flashing boot.img was not a good idea. Stock boot.img + CM10 will result in the phone not booting (wrong kernel), assume that is the state you are now in?
Click to expand...
Click to collapse
I just tried it on another PC and got RUU 2.2 to work. Thank you very much for your persistence.

Ouch. 2.20 RUU means you are now stuck with the 1.14 hboot. Fine if you want to stay stock, but a bit of a pain for flashing custom ROMs, as you now have to flash boot.img separately from fastboot. You also can't flash radios now.
1.73 or 1.85 would have been better. Did you try to run those RUUs on this other PC first?

He deserves hboot 1.14 after talking trash earlier. Hopefully he didn't even try the earlier ruu's
Sent from my HTC One XL

Well, he said he wanted to put it back to stock. If you never plan to root it, 1.14 isn't an issue.

iElvis said:
Well, he said he wanted to put it back to stock. If you never plan to root it, 1.14 isn't an issue.
Click to expand...
Click to collapse
He seems to know a decent amount of tricks (at least enough to be dangerous!). I'd be surprised if he never plans to root. But that's just a guess.

so... theres a way to permanently brick your CID to the point where it cant be changed/unlocked again? :/ now i'm REALLY going to read up on how to relock and get my phone back to the 2.20 RUU (came on that, no sense trying to get an earlier one) for selling it....

redpoint73 said:
He seems to know a decent amount of tricks (at least enough to be dangerous!). I'd be surprised if he never plans to root. But that's just a guess.
Click to expand...
Click to collapse
I'd like him to root his phone and brick it. Then he can come back here to whine about how crappy the phone is when he's the retard.

[Q] Help?? won't boot

So basically, I was running the stock HTC sense, and decided to root it to install CM10. I unlocked the bootloader via htcdev, and rooted it through a youtube tutorial.
Everything seemed to be going well, until the phone wouldn't boot, and would just power on to the quietly brilliant screen, and off.
I forgot to back up, the RUU exe won't start (it prompts an admin permission message and nothing happens after that), and I couldn't mount my sd in recovery. I can't sideload through CWM, and I relocked my bootloader.
I tried to find a way to just install cm10 through fastboot, but I need a system image, and I can't seem to find one.
I can't seem to find a way out of this.

What carrier version of the phone?

Why do people use youtube to brick their phones then come here after? Why didn't you just come here first?
Sent from my VENOMized HoxL

area51avenger said:
Why do people use youtube to brick their phones then come here after? Why didn't you just come here first?
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
It's the AT&T version.
And as for why I used a video tutorial, the ones here didn't seem to be working. The root itself worked just fine.
Since posting this thread, I've unlocked my boot loader again, which lets me get into Recovery again.

CWM doesn't mount USB on this phone. Its a known bug. Install TWRP using fastboot, and you should be able to mount USB.
From there, just flash the ROM again. You probably just forgot to extract the boot.img (on your computer) and flash using fastboot.
If you are on hboot 1.14 (rooted while on firmware 2.20), you will probably find this helpful: http://forum.xda-developers.com/showthread.php?t=1957193
---------- Post added at 09:46 AM ---------- Previous post was at 09:43 AM ----------
1ndistinct said:
And as for why I used a video tutorial, the ones here didn't seem to be working. The root itself worked just fine.
Click to expand...
Click to collapse
The methods here work fine, and are the original work. Any YouTube guides you find just steal their methods from here, anyway. Its not like the guy who made the video, discovered the methods for rooting and flashing ROMs.
Plus, its very dangerous to Google around or search YouTube for random tutorials. They are often for the quad core version of the One X, and can brick your phone.
Moral of the story, you won't find better guides and help than on here, and probably worse.

Lol prolly need to flash boot img if you ain't s off
Sent from my HTC One X using xda premium