Database Info

Update to 4.0.4 unsuccessful?

The update to 4.0.4 for the ATT HTC One X has arrived! Unfortunately, everytime I update, everything looks good until it restarts to begin the installation of the update procedure. It gets about a 3rd done before it stops, then shows a red triangle for about a minute and restarts back. Saying that the "update was unsuccessful". What am I doing wrong? I am rooted on 1.85. The bootloader is "relocked". Any suggestions would be great.

niceppl said:
which ruu are u trying to flash...
there isnt a ruu for 2.20 yet...
the patched ruu isnt an ruu....
the signature on it is not correct
the only way u can flash is with s-off
you can get 2.20
by ruu 1.85 then dl and copy the ota .zip someone else extracted put on sdcard
and flash it with stock recovery.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
this

niceppl said:
this
Click to expand...
Click to collapse
Thanks, but I found out the stock recovery in my recently relocked phone was gone. I flashed the RUU the way I was supposed to (1.85) and It turns out, the bootloader became "tampered" again. I have no idea how that happened. But it's all good now. Currently finishing up installing all my apps the old fashioned way since I lost root (eh, didn't need it anyway)

See my posts in the PSA thread in General. I'm rooted on 1.85 but never unlocked. My update failed exactly the same way as yours. Still no luck.
Sent from my HTC One X using XDA Premium HD. In between FCs.

Same here. Must be a root issue.
Sent from my HTC One X using Tapatalk 2

FWIW there's a 2.20 RUU on HTC.com now

If you deleted any system apps then the OTA will fail. You'll need to reinstall them or RUU back to stock before you try to update.

akvtiger said:
Same here. Must be a root issue.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
It is a root issue, rooting my phone changed the filmware version to include "R2" at the end. Not a big thing, but enough to completely f*ck up my phone when it was time to update. No more rooting for me til I gain the courage again... And root is found for 4.0.4.
Sent from my HTC One X using xda app-developers app

_MetalHead_ said:
If you deleted any system apps then the OTA will fail. You'll need to reinstall them or RUU back to stock before you try to update.
Click to expand...
Click to collapse
That must've been another problem. I tried to push google now to my phone, then i found out it sucked and took it off. I thought i put the other file back on, but i guess something went wrong.
gunnyman said:
FWIW there's a 2.20 RUU on HTC.com now
Click to expand...
Click to collapse
I didn't know that. I was looking all over for it yesterday. Thank you.
Sent from my HTC One X using xda app-developers app

Bought my One X with a ROM and rooted, how to get back to stock?

I'm not sure how to get back to stock as I purchased my phone off craigslist and it has CM10 on it with a custom recovery (TWRP or something I believe). I would like to get back to completely stock as if I purchased the phone brand new from AT&T. I searched through the forums and found stock RUU's but I'm not sure which one to use or how to flash it.
I would appreciate any help at all. Thank you.

Give it time and your question will be answer in here
Sent from my HTC One X using xda premium
---------- Post added at 07:46 PM ---------- Previous post was at 07:41 PM ----------
Also this need to be posted in the question section to be answer.
Sent from my HTC One X using xda premium

Check your hboot version ...if 1.14 relock bootloader then run the 2.20 ruu...if your on 1.09 or 1.11 I guess if you wanna go back to stock and have no desire of rooting then just relock and run the 2.20 ruu

Not really sure why you would want to be back at bone stock seeing as the warranty is gone with no chance to reverse it. Even if you get the boot loader relocked it states Relocked on the bootloader screen. Just flash a stock rom... and keep super user so you can remove all AT&T's bloat. The phones memory is already small as it is, no reason to waste it on crap apps.

Mrkrackie said:
Not really sure why you would want to be back at bone stock seeing as the warranty is gone with no chance to reverse it. Even if you get the boot loader relocked it states Relocked on the bootloader screen. Just flash a stock rom... and keep super user so you can remove all AT&T's bloat. The phones memory is already small as it is, no reason to waste it on crap apps.
Click to expand...
Click to collapse
Selling it, buying nexus 4

brian85 said:
Selling it, buying nexus 4
Click to expand...
Click to collapse
Ah I gotcha, well seeing how you can't ever return to true stock (the day you first got it) I'd just flash a stock ROM and call it a day. Trying to relock the boot loader is a waste of time. Since it will make no difference.
Sent from my One X using xda app-developers app

Mrkrackie said:
Ah I gotcha, well seeing how you can't ever return to true stock (the day you first got it) I'd just flash a stock ROM and call it a day. Trying to relock the boot loader is a waste of time. Since it will make no difference.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Sure you can. Just change the cid hex in mmcblk0p4
Only difference is bootloader will say relocked and not locked
Sent from my One X using xda app-developers app

i wouldnt change cid back. id just ruu then give the guy your selling it to the unlock token incase the buyer wants to mod it. save the person some time. if you want to just run the 1.85 ruu you can still get it from htc http://dl3.htc.com/application/htc_onex_att_RUU_1.85.520.3_US.exe

absolutelygrim said:
Sure you can. Just change the cid hex in mmcblk0p4
Only difference is bootloader will say relocked and not locked
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Which is still not true stock. You cannot get the boot loader back to factory locked. The warranty is gone and cannot be recovered so these steps that are being taken are useless and make extra hurdles for the buyer if they plan to root. I'd recommend just selling it with a stock ROM on it with the boot loader left unlocked.
Sent from my HTC One XL using xda app-developers app

Songlambr37 said:
Who else in the world still use the manly Dell Venue?
who can help us upgrade it to 4.0?
Click to expand...
Click to collapse
Nice Grammar, wrong section all together.
http://forum.xda-developers.com/forumdisplay.php?f=1013

Is stock recovery required before flashing a RUU?

no, all you need to do is get into bootloader and "fastboot oem lock" then flash ruu.

mbh87 said:
Is stock recovery required before flashing a RUU?
Click to expand...
Click to collapse
i suppose you have twrp recovery right?
if you have, then just flash device with cleanrom. or stock.
i personally prefer cleanrom, cause its deoxed.

cleanrom is odexed

"Tampered" on HTC one x?

Hey guys. New on the forum and unfortunately a noob. I saw recently 2.20 was open to be rooted for this phone. The instructions are hard enough to follow, let alone on a macbook pro. I got as far as getting the token from htcdev.com. couldn't get any further. I decided to give up as the topic is still fresh and there isn't much Mac love regarding the new root method. So now since I got that far I am still on the stock ROM but now my phone has the "tampered" logo on the boot loader screen. Is there a way I can rid this of the phone? I don't care about rooting or unlock anymore. Just want to get rid of it because the phone is still new and I still want the warranty. Thanks a bunch guys for the help.
Sent from my Nexus 7 using xda app-developers app

RUU.

Even running a RUU it'll still say tampered I think.. the whole hboot thing isn't reversible till s-off..
For example, if you unlock your bootloader, and take any measure what so ever your hboot will even say re-locked
Sent from my One X using Tapatalk 2

InflatedTitan said:
Even running a RUU it'll still say tampered I think.. the whole hboot thing isn't reversible till s-off..
For example, if you unlock your bootloader, and take any measure what so ever your hboot will even say re-locked
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Tampered will go away after an ruu. It will always say relocked until s-off
Sent from my One X using xda app-developers app

[Q] HTC One X AT&T out of options

Hello, I recently received an AT&T One X and the very first thing I did with it was try to root it and all that fun stuff. After a long adventure I couldn't get the HBOOT to upgrade so I had changed the CID to HTC__001 from cws_001 (I couldn't find this CID anywhere, but I swear that's what it said) and then the bootloader was re-locked. There is no OS, there is no recovery, I've tried 10 RUU's from Asia WWE to the UK RUU's and than all the AT&T ones I can find.
Most fastboot commands come back with a "Too many Links" error which I assume is from the bootloader being locked, and I cant change the bootloader's status because the bin file I got is for the supercid.
Please help me, I am usually quite proficient with this type of stuff but I really buried myself in a hole.

Why were you trying to upgrade your hboot..? Anyways.. What hboot do you have now? Is your Cid still htc__001?
Sent from my HTC One X using xda app-developers app

exad said:
Why were you trying to upgrade your hboot..? Anyways.. What hboot do you have now? Is your Cid still htc__001?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Isn't that cid for the international version?
Sent from my HTC One X using xda app-developers app

Re
My HBOOT is 1.14.0002. I tried to upgrade it for all the newer roms and such but thats when I managed to screw everything up. Yes, it is still HTC__001 and that is the international. I've tried several WWE RUU's and all refuse to work giving me various errors..

Yeah no ruu will work because you have an international cid with an at&t phone.
You'll need to htcdev over again and pray it works.
Sent from my HTC One X using xda app-developers app

I already unlocked the bootloader, It just wont let me do anything anymore... All fastboot commands are giving me either unknown errors or too many link errors.
I just dont understand why I cant change the CID anymore! The bootloader is unlocked so i should just be able to use fastboot..

koolgshizman said:
I already unlocked the bootloader, It just wont let me do anything anymore... All fastboot commands are giving me either unknown errors or too many link errors.
I just dont understand why I cant change the CID anymore! The bootloader is unlocked so i should just be able to use fastboot..
Click to expand...
Click to collapse
You can only change the cid once with fastboot oem writecid unless you are s-off
As for fastboot not working. Are you able to flash recovery?
Sent from my HTC One X using xda app-developers app

I managed to put on twrp but I didn't make a nandroids

koolgshizman said:
I managed to put on twrp but I didn't make a nandroids
Click to expand...
Click to collapse
Flash a stock-based ICS rom and then S-OFF, then you can change your cid, or whattever you need to do

Doesn't necessarily need to be ics but yeah you get the idea. After s-off then you can ruu to update your hboot and anything else that gets updates. Bear in mind that on aosp ROMs the touchscreen won't work after you upgrade until you downgrade the touchscreen firmware.
Sent from my HTC One X using xda app-developers app

Don't you still need supercid to s-off? Or is that no longer a requirement?

Never tried with am international or cid from another carrier.. Maybe it'll work? If not he can always hex edit his cid.
Sent from my HTC One X using xda app-developers app

Thank you for the replies, the link to the Hex editing of the CID saved me. I knew that's where the CID was located but I didn't know you could dd it out of the system. By the way, I was having hard times trying to flash CM9 on there and it didn't work, neither did viper roms so I was greatly discouraged. By the way, I have no earthly clue on how to S-OFF the One X so I will probably try to look harder for that. I'm probably going to either RUU to where I was, I believe 2.2 or put on.. some rom that sounds good. Any favorites? Y'all say I can flash ICS to it if I just flash the boot.img first right? I thought that the partition sizes would cause a conflict.. Oh well, I'll give it a try

koolgshizman said:
Thank you for the replies, the link to the Hex editing of the CID saved me. I knew that's where the CID was located but I didn't know you could dd it out of the system. By the way, I was having hard times trying to flash CM9 on there and it didn't work, neither did viper roms so I was greatly discouraged. By the way, I have no earthly clue on how to S-OFF the One X so I will probably try to look harder for that. I'm probably going to either RUU to where I was, I believe 2.2 or put on.. some rom that sounds good. Any favorites? Y'all say I can flash ICS to it if I just flash the boot.img first right? I thought that the partition sizes would cause a conflict.. Oh well, I'll give it a try
Click to expand...
Click to collapse
You should be able to flash any rom so long as you fastboot flash the boot.img ics or jb.

A million thanks, well, I thanked you once, that should suffice. I'm almost set now, for a second I thought the phone would be a goner.

If you can get to bootloader your phone can be saved. Good luck, have fun.
Sent from my HTC One X using xda app-developers app

Yes, CM10.1 is now running, I'm just waiting for my gapps.. thanks again

[Q] CID # for AT&T U.S.

I currently have S-ON with SuperCID, and I'm trying to get S-OFF with stock AT&T CID. I've heard that it's a fairly simple process to change the CID ("fastboot oem writecid HTC_001"), but HTC_001 is for the unbranded international version, and I'm having a hard time finding the code for the AT&T version, which I suppose I failed to write down before overwriting with SuperCID. Hope someone can help? Also, should I be s-ON or S-OFF to write the CID?

bikeracer4487 said:
I currently have S-ON with SuperCID, and I'm trying to get S-OFF with stock AT&T CID. I've heard that it's a fairly simple process to change the CID ("fastboot oem writecid HTC_001"), but HTC_001 is for the unbranded international version, and I'm having a hard time finding the code for the AT&T version, which I suppose I failed to write down before overwriting with SuperCID. Hope someone can help? Also, should I be s-ON or S-OFF to write the CID?
Click to expand...
Click to collapse
You can only S-OFF with super CID 11111111
After S-OFF you can write it back to the default of CWS__001 for AT&T, but there is no advantage to doing so. You can do whatever you like regardless of what your CID is after S-OFF. I set mine to R00T_001 after for example. (must be 8 characters)
Just noticed your other thread and see why you want the default CID. If you're selling it, make sure your cid is currently 11111111 then S-OFF then you can use that command to change the cid to default. If you're going to sell it, after S-OFF, I'd just format the SD card and run the 3.18 RUU and then power it off after so the person you sell it to will have a fresh start.

exad said:
After S-OFF you can write it back to the default of CWS__001 for AT&T, but there is no advantage to doing so.
Click to expand...
Click to collapse
From what I understand, CID can be changed once from SuperCID to something else, without s-off.
The OP wants to sell his phone, per this thread: http://forum.xda-developers.com/showthread.php?t=2251955
I suggested either changing from SuperCID, or achieving S-off, so the next owner doesn't unintentionally brick the phone by trying to install the 3.18 OTA or RUU (since he is currently SuperCID and S-on).
Not sure why he started this thread, I would have just answered the AT&T CID question in the other thread.

redpoint73 said:
From what I understand, CID can be changed once from SuperCID to something else, without s-off.
The OP wants to sell his phone, per this thread: http://forum.xda-developers.com/showthread.php?t=2251955
I suggested either changing from SuperCID, or achieving S-off, so the next owner doesn't unintentionally brick the phone by trying to install the 3.18 OTA or RUU (since he is currently SuperCID and S-on).
Not sure why he started this thread, I would have just answered the AT&T CID question in the other thread.
Click to expand...
Click to collapse
Sorry, the other thread was started because I couldn't turn my phone on, and was becoming unrelated to original post, thought it would be prudent to create a new thread. Really appreciate your help though.

Just a heads up, I bricked my first TELUS HOXL eventhough I had changed my CID back to the default prior to RUUing. May have been a fluke but yeah do with this info what you will.

UGGGHHH, this is getting frustrating...had to root the phone to get to S-OFF, so I used the X-FACTOR exploit, but when I tried to get S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) I got the first 2 adb command off but the second one said it couldn't find 'su' so I assumed to root hadn't worked. So I decided it would just be easiest to go back to CyanogenMod and start the whole process over. Only when I tried to unlock the bootloader again, I found that it wouldn't stick. It would SAY it was successful and reboot the phone, but when I would reboot to bootloader it would say "relocked". SO decided to run an RUU, only now the hboot was up to 2.14 from the S-OFF flashing, so I decided to run the 3.15 RUU instead of the 2.20, and that SEEMED to work fine, except that now I'm right back to where I was with not being able to turn the phone on, and I tried my previous trick of the Vol Down + Power...
EDIT: Aaaand, no LED when charging...

bikeracer4487 said:
UGGGHHH, this is getting frustrating...had to root the phone to get to S-OFF, so I used the X-FACTOR exploit, but when I tried to get S-OFF (http://forum.xda-developers.com/showthread.php?t=2155071) I got the first 2 adb command off but the second one said it couldn't find 'su' so I assumed to root hadn't worked. So I decided it would just be easiest to go back to CyanogenMod and start the whole process over. Only when I tried to unlock the bootloader again, I found that it wouldn't stick. It would SAY it was successful and reboot the phone, but when I would reboot to bootloader it would say "relocked". SO decided to run an RUU, only now the hboot was up to 2.14 from the S-OFF flashing, so I decided to run the 3.15 RUU instead of the 2.20, and that SEEMED to work fine, except that now I'm right back to where I was with not being able to turn the phone on, and I tried my previous trick of the Vol Down + Power...
EDIT: Aaaand, no LED when charging...
Click to expand...
Click to collapse
That's a brick. Do you have a linux boot disk? if not, create a linux boot disk or usb and then try the unbrick evita thread. If you can get past step 3, you should be able to unbrick. if not, Sorry to hear.

exad said:
That's a brick. Do you have a linux boot disk? if not, create a linux boot disk or usb and then try the unbrick evita thread. If you can get past step 3, you should be able to unbrick. if not, Sorry to hear.
Click to expand...
Click to collapse
Hm, not having much luck so far, but I AM seeing QHSUSB_DLOAD in the device manager...

bikeracer4487 said:
Hm, not having much luck so far, but I AM seeing QHSUSB_DLOAD in the device manager...
Click to expand...
Click to collapse
Yeah that bid brick I believe. Get live USB stick running Linux. All you need is small USB stick like 2 or 4 GB. Then download pen drive USB image creator. And run Linux from that. Then exad mentioned a thread to look into. I recommend an Ubuntu based distro. I use Linux mint
Sent from my Carbon-ize Evita using xda-developers app

There's a guide to making a bootable Linux usb in q&a if you need it.
Sent from my One X using xda app-developers app

exad said:
There's a guide to making a bootable Linux usb in q&a if you need it.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Yeah, booting from Linux isn't a problem, but as I said, I was trying to put it to stock so I could sell it...but then I discovered it was still under warranty (with just a week left), so instead of messing around in Linux I took it to an AT&T warranty center on my way home and they just straight up replaced with a new One X... Everything turned out better than expected

bikeracer4487 said:
Yeah, booting from Linux isn't a problem, but as I said, I was trying to put it to stock so I could sell it...but then I discovered it was still under warranty (with just a week left), so instead of messing around in Linux I took it to an AT&T warranty center on my way home and they just straight up replaced with a new One X... Everything turned out better than expected
Click to expand...
Click to collapse
Great!! But is it on the new unrootable software?

ImagioX1 said:
Great!! But is it on the new unrootable software?
Click to expand...
Click to collapse
Yup :-/ Software version 3.18, 2.14 hboot, S-ON, and CID of CWS__001... But since I won't be keeping this phone, it'll be someone else's problem...

bikeracer4487 said:
Yup :-/ Software version 3.18, 2.14 hboot, S-ON, and CID of CWS__001... But since I won't be keeping this phone, it'll be someone else's problem...
Click to expand...
Click to collapse
LoL!!
Sent from Xparent Red using my Venomized Evita

It is technically better to have a brand new in box phone for selling. That's awesome! Congrats! I wish Canadian carriers warranted phones like they do in the US. You only get manufacturer warranty here.
Sent from my One X using xda app-developers app

exad said:
It is technically better to have a brand new in box phone for selling. That's awesome! Congrats! I wish Canadian carriers warranted phones like they do in the US. You only get manufacturer warranty here.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
You could pay the 7 bucks a month for device protection then drive over it with a car when you brick it
Sent from my VENOMized HoxL

area51avenger said:
You could pay the 7 bucks a month for device protection then drive over it with a car when you brick it
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Or just keep it and say that you lost it. And of you are able to fix it, sell it and you still keep a new phone.
Sent from my Carbon-ize Evita using xda-developers app

Pft, that's an extra 252$ within my contract period. Forget that noise! I doubt I'll even have this phone in a year lol.
Sent from my One X using xda app-developers app
---------- Post added at 10:17 AM ---------- Previous post was at 10:06 AM ----------
Herc08 said:
Or just keep it and say that you lost it. And of you are able to fix it, sell it and you still keep a new phone.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
They don't warrant lost phones here.
Sent from my One X using xda app-developers app

exad said:
Pft, that's an extra 252$ within my contract period. Forget that noise! I doubt I'll even have this phone in a year lol.
Sent from my One X using xda app-developers app
---------- Post added at 10:17 AM ---------- Previous post was at 10:06 AM ----------
They don't warrant lost phones here.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Oh wow. Didn't know that
Sent from my Carbon-ize Evita using xda-developers app

exad said:
They don't warrant lost phones here.
Click to expand...
Click to collapse
They don't cover lost phones on warranty anywhere. He was talking about insurance, not a warranty.