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
Related
A friend of mine asked if I could help him fix his phone. He is a noob and so am I but I have rooted several phones and flashed many ROMS on all sorts of phones with no issues. So I would a least say I am pretty tech savvy. Here is the dilemma- If I hold volume down and power I get a white screen with some options such as hboot, fastboot, recovery, factory reset, simlock & image crc. It also says S-On....which I believe is the problem. He says that he though he downgraded to 2.2 before rooting but couldn't be sure but says he was originally on 2.3.4. I can boot into recovery CWM, mount usb/SD and load roms but no matter what ROM I load it will never get passed the HTC screen. Can someone tell me or at least point me in the right direction as to how I can achieve S-Off? Also I must note that he made no backups prior to his rooting attempt (Ughhhh!). Is there an easy way to get S-Off when the phone seems to be unlocked, rooted & CMW installed? Thanks a bunch my fellow XDA Einsteins.
I didn't think you can have a recovery without s-off for the shift... You could run an RUU and use one of the root guides we have if someone with more experience can't cone up with an idea. Of he did downgrade to 2.2 he should of used the shiftrr.exe to root
Sent from my EVO using Tapatalk 2
YoungCorruptionV2.0 said:
I didn't think you can have a recovery without s-off for the shift... You could run an RUU and use one of the root guides we have if someone with more experience can't cone up with an idea. Of he did downgrade to 2.2 he should of used the shiftrr.exe to root
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
You can with an unlocked boot loader.
VICODAN said:
You can with an unlocked boot loader.
Click to expand...
Click to collapse
Oh really? I didn't know that
Sent from my EVO using Tapatalk 2
YoungCorruptionV2.0 said:
Oh really? I didn't know that
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/wiki/Fastboot
It's in my root thread.
VICODAN said:
http://wiki.cyanogenmod.com/wiki/Fastboot
It's in my root thread.
Click to expand...
Click to collapse
Ah good to know. I never read your thread no offense since I rooted on 2.2
Sent from my EVO using Tapatalk 2
YoungCorruptionV2.0 said:
Ah good to know. I never read your thread no offense since I rooted on 2.2
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
No worries, no need. Not offended.
Sounds like something got screwed up during the RUU process of downgrading. I've run into a similar issue when running the ROM Update Utility and it put me back to s-on but It kept my custom recovery. Same thing, no matter what I flashed I couldn't get it to boot. Your best bet is probably going to be run the the RUU. It will depend on which version of bootloader is on the device to which RUU will work. I can't remember the specific number but I believe the 2.2 bootloader is something like 93xxx something or another. If that's the case then you should be able to run the old RUU, putting your back on 2.2 and continue rooting. If your bootloader version is higher (98xxx or something) you'll have to run the newest RUU in order for it to work.
I may be completely wrong here but when all else fails... RUU!
Sent from my ELTE using Tapatalk 2
crump84 said:
Sounds like something got screwed up during the RUU process of downgrading. I've run into a similar issue when running the ROM Update Utility and it put me back to s-on but It kept my custom recovery. Same thing, no matter what I flashed I couldn't get it to boot. Your best bet is probably going to be run the the RUU. It will depend on which version of bootloader is on the device to which RUU will work. I can't remember the specific number but I believe the 2.2 bootloader is something like 93xxx something or another. If that's the case then you should be able to run the old RUU, putting your back on 2.2 and continue rooting. If your bootloader version is higher (98xxx or something) you'll have to run the newest RUU in order for it to work.
I may be completely wrong here but when all else fails... RUU!
Sent from my ELTE using Tapatalk 2
Click to expand...
Click to collapse
Yes, you know when I water damaged my phone I (stupidly) was trying to RUU it while trying to fix it and the RUU failed and I got to a point where RUU was telling me that a newer version is installed.
Well the way I fixed it was by running RUU 2.3.4. All worked good after that.
Please refer to my post about how to flash misc.img in recovery since you can't get past the htc screen and this will allow you to get downgraded. If I can the post it's around here somewhere and I'll post a link to it.
Edit: here it is
http://forum.xda-developers.com/showpost.php?p=27695411&postcount=254
Sent from my PG06100 using xda premium
sparksco said:
Please refer to my post about how to flash misc.img in recovery since you can't get past the htc screen and this will allow you to get downgraded. If I can the post it's around here somewhere and I'll post a link to it.
Edit: here it is
http://forum.xda-developers.com/showpost.php?p=27695411&postcount=254
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
I found the post it's on Vicodan's thread
I hope I don't get flamed for this but I couldn't find this anywhere...
I accidentally ran the ota while trying to reroot my HOX after a crash. Now I'm stuck on the new hboot. I see people talking about flashing boot.img through fastboot. I'm wondering how to flash radios now that I'm on this more locked down bootloader.
I have my unlock tokens and can still unlock the boot through fastboot. I'm running CR 4.5.
Any help would be appreciated.
Sent from my HTC One X using xda app-developers app
Nevermind
gunnyman said:
I'm not sure anyone has tried to flash a radio yet. Best advice I can give is to unlock the bootloader push twrp recovery and try to flash one.
Click to expand...
Click to collapse
That may brick his device. I wouldn't try that.
Sent from my One X using xda app-developers app
Good point. The radio location might have moved. Scratch my previous suggestion
I tried flashing TN and it hung in aroma on flashing boot. That ended up screwing a bunch of things up. I'm ok with my setup except my WiFi connection is iffy. I can live with it, but wanted to try a few radios to see if I could solve it that way.
Sent from my HTC One X using xda app-developers app
I had my TB running Zeus Skyraider. I was having some minor issues but nothing that really scared me. I decided to restore it/unroot it in case I had to bring it in. I used the app thunderbolt restore. Now it won't boot past the white "HTC" screen and it only says HTC, no "Quietly brilliant". I can get to the bootloader but it automatically tries to install a update and won't let me do anything other than reboot. I'm really scared I bricked my phone. Any help would be greatly appreciated.
I should probably also mention that it did boot up once and everything looked fine, and then I tried to install a verizon OTA update. That is when it started really having problems.
You might yet clearing your cache.
Sent from my ADR6400L using xda app-developers app
But I can't even get to recovery. The bootloader won't let me.
After the bootloader checks IMG150 or whatever it asks if I want to start update. Whatever I say it just leads to the plain HTC screen again. It also says "***LOCKED***" at the top of the screen. Is my phone completely locked?
The bootloader is locked. Perhaps flash an RUU to return to stock rather than an ota.
Sent from my ADR6400L using xda premium
Ok, I am pretty bad at this stuff. Can someone point me to an appropriate RUU. I don't know what I should use. Does the radio I had before restoring matter or anything like that? I just want to know exactly what I am doing before I do it.
Okay, Zeus is gingerbread, so if you were running that, then you are best served flashing one of the gingerbread RUU files. You most certainly do NOT want to flash a froyo version.
Development Stickies have them. Read up on how to flash it.
http://forum.xda-developers.com/showthread.php?t=1310014
Sent from my ADR6400L using xda premium
http://forum.xda-developers.com/showthread.php?t=1225752
So is this one I can use? It's the Verizon stock gingerbread RUU.
Remove sd
Sent from my ADR6400L using xda app-developers app
Actually bootloader says my radio is 1.xxxxxx
I don't know how to flash an RUU as an executable file, cannot say about the link you show.
Skyraider Zeus ran fine on the phone? The gingerbread version?
Sent from my ADR6400L using xda premium
Yeah, it ran very nicely. I used thunderbolt restore and it worked it booted up fine. Then I tried to install the newest Verizon update and it won't even boot up now.
Flash a gingerbread RUU
Sent from my ADR6400L using xda premium
In Hboot it says I have radio 1.48.00.0906w_1
That's not a GB radio is it?
jcbsides said:
In Hboot it says I have radio 1.48.00.0906w_1
That's not a GB radio is it?
Click to expand...
Click to collapse
Yes.
Remove the SD and then try to factory reset from the bootloader.
If it doesn't work remove the PG05IMG.zip off of the SD and then rename this https://dl.dropbox.com/u/61129367/Stock-ROM.zip to PG05IMG.zip and put it on the SD and then boot to the bootloader and run it. Then remove the file from the card and try to boot.
So nothing ITT seemed like it helped because the phone was not booting up all the way, but this morning it was on and everything was working so, I think it is at least in a state where I can take it to a verizon store and see what they can do about it. Thanks for all of the advise everyone.
Delete
Oops wrong thread.
Sent from my ADR6400L using Tapatalk 2
jcbsides said:
Yeah, it ran very nicely. I used thunderbolt restore and it worked it booted up fine. Then I tried to install the newest Verizon update and it won't even boot up now.
Click to expand...
Click to collapse
So Thunderbolt restore successfully got you to an old stock rom that ran fine?
I am running android version 4.0.3, HTC sense version 4.0, software number 1.73.502.1, HTC SDK API level 4.11
I've been attempting to flash TWRP using Hasoon200's HTC one X all-in-one kit but could never figure it out. I get stuck at the unlock bootloader step (step 6).
I am now attempting to reset my factory data by going to storage and clicking on factory data reset. The phone will reboot as normally but then will load into the Fastboot USB/Bootloader screen (the one that says *** TAMPERED *** *** LOCKED *** etc)
This is where I am running into trouble. How do I reset my factory data from here?
Save your data then flash ruu to return to stock , you will find root methods and ruu in this link, its a good link to save as it has a lot of hoxl toys
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One X using xda premium
You're using the wrong root method. You're on 1.73 and trying to root with a 2.20 one-click.
You need this one: http://forum.xda-developers.com/showthread.php?t=1644167
iElvis said:
You're using the wrong root method. You're on 1.73 and trying to root with a 2.20 one-click.
You need this one: http://forum.xda-developers.com/showthread.php?t=1644167
Click to expand...
Click to collapse
oh wow, i wonder if that makes his phone ancient...havent seen a device below 1.85 before
Herc08 said:
oh wow, i wonder if that makes his phone ancient...havent seen a device below 1.85 before
Click to expand...
Click to collapse
All phones sold at release were 1.73, and were so for maybe a couple months before 1.85 deployed. And there can always be old stock laying around. Pretty sure someone posted on here that they bought one (new, in-store) recently that came with 1.73.
redpoint73 said:
All phones sold at release were 1.73, and were so for maybe a couple months before 1.85 deployed. And there can always be old stock laying around. Pretty sure someone posted on here that they bought one (new, in-store) recently that came with 1.73.
Click to expand...
Click to collapse
Thanks for the info. I guess it is kind of like trying to find a ps3 60gb
Sent from my One X using xda app-developers app
So, I've been trying to use this method to root by AT&T HTC One X
http://forum.xda-developers.com/showthread.php?t=1644167
Attached is the software information of my phone...
I run the .bat file and everything works and my phone reboots three times but then I try to load SuperSU but it says su binary code not installed which leads me to believe that the phone isn't rooted?
Any advice on how to get it to work?
Cheers,
What Hboot version do you have? Go into boot loader by turning the phone off, hold the volume down button and press the power button. Let us know what it says?
Sent from my One X using xda premium
subarudroid said:
what hboot version do you have? Go into boot loader by turning the phone off, hold the volume down button and press the power button. Let us know what it says?
Sent from my one x using xda premium
Click to expand...
Click to collapse
hboot-2.14.000
Did you buy that phone second hand? Is the bootloader locked? Unlocked? Relocked? Does it say s-on? Or S-off?
Sent from my One X using xda app-developers app
No, I bought it new. Its locked and s-on
akaeavaian said:
No, I bought it new. Its locked and s-on
Click to expand...
Click to collapse
Well that's odd since you're software says 1.73 but your hboot is of 3.18.
Sent from my One X using xda app-developers app
nah hboot is 2.14
Post a photo of your bootloader screen, because what you're describing is virtually impossible.
The only way you could be on hboot 2.14 and 1.73 software is if you got a refurb that was previously on 2.20 or earlier, was rooted, unlocked, s-off, had the 3.18 ruu run, then the 1.73 stock rom installed, then relocked and s-on, and no one at AT&T bothered to clean up the mess.
iElvis said:
Post a photo of your bootloader screen, because what you're describing is virtually impossible.
The only way you could be on hboot 2.14 and 1.73 software is if you got a refurb that was previously on 2.20 or earlier, was rooted, unlocked, s-off, had the 3.18 ruu run, then the 1.73 stock rom installed, then relocked and s-on, and no one at AT&T bothered to clean up the mess.
Click to expand...
Click to collapse
Lmao that's sounds exactly like what would happen.
Sent from my One X using xda premium
That sounds complicated
but here you go...
Looks like youre going to have to wait. no exploit for att on that version. Pisses me off that Rogers can still unlock and s-off. I want to say horrible things about att. Can we turn this into a AT&T bashing thread now?
Sent from my One X using xda premium
subarudroid said:
Looks like youre going to have to wait. no exploit for att on that version. Pisses me off that Rogers can still unlock and s-off. I want to say horrible things about att. Can we turn this into a AT&T bashing thread now?
Sent from my One X using xda premium
Click to expand...
Click to collapse
can telestra too? telus can aswell.
Again another reason to bash AT&T
Sent from my One X using xda premium
akaeavaian said:
That sounds complicated
but here you go...
Click to expand...
Click to collapse
I'm sorry, even seeing it, I don't believe it. I just don't see how this could be possible.
In any case, the 1.73 root method might work, but with that hboot, you can't change cid, and thus can't unlock or flash a custom recovery, which means you can't get permanent root. You're stuck where you are, wherever that is.
They don't send ota's for the hboot right? I was on 2.20 few and 1.14 hboot. And got it refurb back in December
Sent from my Carbon-ize Evita using xda-developers app
Ota does affect the hboot... Yes. But there's not an Ota that changes just the hboot. This must have been previously rooted. Most likely this phone was at some point unlocked and rooted, the person who returned it most likely updated to 3.18 after bootloader unlock/soff, had issues, Relocked and s-on, ruu to 1.73, returned to HTC where HTC fixed and repackaged without updating the software.
*edit* sorry that makes no sense.. Ruu would have downgraded the hboot too.. Just woke up -_-
We may never know what happened to thus phone lol.
Sent from my One X using xda app-developers app
exad said:
Ota does affect the hboot... Yes. But there's not an Ota that changes just the hboot. This must have been previously rooted. Most likely this phone was at some point unlocked and rooted, the person who returned it most likely updated to 3.18 after bootloader unlock/soff, had issues, Relocked and s-on, ruu to 1.73, returned to HTC where HTC fixed and repackaged without updating the software.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Aha! So it couldn't have been new. Unless he had warranty. something isn't right.
Sent from my Carbon-ize Evita using xda-developers app
Yup, he's got an ICS Rom with a locked 2.14 hboot. Now that's f'd up.
exad said:
We may never know what happened to thus phone lol.
Click to expand...
Click to collapse
I think it's possible to get that configuration:
-phone was originally on ICS
-root, unlock, and s-off
-apply 3.17 or 3.18 ruu to get 2.14 hboot. This would also remove the TAMPERED flag
-flash rooted stock 1.73 rom
-edit p3 or flash scotty's zips to relock and restore LOCKED text
-remove root
-restore s-on
-return phone to AT&T
I just don't see why anyone would do it or how it would survive the refurb process.
soo...err....is there anything I can do? I got it through Costco though...if that changes anything...