Hi all,
I am having one issue with my AT&T HTC One X. I had my HOX rooted with CM10 installed. I unrooted it flashed at&t rom through RUU. After that (without reading enough about it) I updated my phone to JB update and got bricked. I sent out my phone to mobiletechvideos and they did an awesome job in JTAGing my phone and its running fine now with official At&t ROM ( and all its bloat) and its running on JB 4.1.1.
Now as my phone is still under warranty I wanna try taking it to the at&t device support center and get it replaced (I know its void already but I still wanna try it) The question is that I still have Superuser installed in there and I dont see any options in it to uninstall it. I also download root checker app which says that I still have root. I went into bootloader and it says LOCKED hboot 2.14. Now how can I turn it to complete stock (out of the box) without SU and root so that i can TRY to get it replaced under the warranty. Thanks!!
Isn't SU simply an application that's installed?
Not sure what they check for at the service center (probably varies depending on the person), but unrooting (possible?), locking the bootloader, and making sure that 'TAMPERED' doesn't show when booting into the bootloader is probably a good idea. Pretty sure that once they see 'TAMPERED', they'll say your warranty is hosed, and you're stuck with your current device.
Just my thoughts. I would search XDA for threads that have similar experiences and see what they have to say before attempting that, of course.
You can use ES file explorer or Root explorer to delete super user.
Sent from my HTC One X using xda premium
so did you request for them to put jellybean back on it? i just sent my phone in but i requested for s-off while they are fixing it. i wonder if they are goin to put jellybean on mine and whether or not ill still be able to root afterwards
jrlatta said:
so did you request for them to put jellybean back on it? i just sent my phone in but i requested for s-off while they are fixing it. i wonder if they are goin to put jellybean on mine and whether or not ill still be able to root afterwards
Click to expand...
Click to collapse
Yes I asked them to update ROM to 4.1.1 and thats what they did.
My phone is on JB 4.1.1 with software version 3.18
I just rebooted to bootloader and saw that its locked but its S-OFF, can I install a custom ROM? Attached is the screen shot from the bootloader
uzair_rock said:
My phone is on JB 4.1.1 with software version 3.18
I just rebooted to bootloader and saw that its locked but its S-OFF, can I install a custom ROM? Attached is the screen shot from the bootloader
Click to expand...
Click to collapse
If i an reading this correctly, you have s off and supe cid. You need to unlock the boot loader but i dont know if that is possible. It is just werid they kept it locked, but it is s off. I am sure htc will see that
Sent from my Carbon-ize Evita using xda-developers app
I believe there is a way to trick htc dev If it will allow you to change cid. I have seen where people would change it to a rogers cid and use dev to unlock since there are no restrictions like at&t has. But I would research this carefully before any attemp is made to do it. Forget where I read it. But it might be worth looking into.
Sent from my HTC One X using xda premium
Venomtester said:
I believe there is a way to trick htc dev If it will allow you to change cid. I have seen where people would change it to a rogers cid and use dev to unlock since there are no restrictions like at&t has. But I would research this carefully before any attemp is made to do it. Forget where I read it. But it might be worth looking into.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Oh wow, that seems sweet. Since Rogers uses the "evita" code name. I wonder if it would also work for Telstra as well. Gonna google see. If that is the case you (or where ever you read it from) just solve a handful of mysteries for us AT&T folks.
EDIT: It's by our very own redpoint73. Amazing what a quick google can do http://forum.xda-developers.com/showthread.php?t=1671237
By now I have realized that I have root, SUID and S-OFF. But the question is how do I get my boot loader unlocked?? I need that unlocked to flash custom ROMs and radios....help needed guys.
Thanks
uzair_rock said:
By now I have realized that I have root, SUID and S-OFF. But the question is how do I get my boot loader unlocked?? I need that unlocked to flash custom ROMs and radios....help needed guys.
Thanks
Click to expand...
Click to collapse
thats what i said, i was trying to understand how you have s-off, but the bootloader is locked (not re-locked)
do you have the unlock_code.bin that you first used?
uzair_rock said:
By now I have realized that I have root, SUID and S-OFF. But the question is how do I get my boot loader unlocked?? I need that unlocked to flash custom ROMs and radios....help needed guys.
Click to expand...
Click to collapse
Just to to HTCDev.com and follow the bootloader unlock process. Since you have SuperCID, it will work.
uzair_rock said:
By now I have realized that I have root, SUID and S-OFF. But the question is how do I get my boot loader unlocked?? I need that unlocked to flash custom ROMs and radios....help needed guys.
Thanks
Click to expand...
Click to collapse
Fastboot oem writecid 22222222
Then unlock with htcdev
If that Fastboot command doesn't work, (not sure the the bootloader needs to be unlocked for it to work) then hex edit your Cid. And then unlock with htcdev
Sent from my HTC One X using xda app-developers app
---------- Post added at 02:38 PM ---------- Previous post was at 02:37 PM ----------
redpoint73 said:
Just to to HTCDev.com and follow the bootloader unlock process. Since you have SuperCID, it will work.
Click to expand...
Click to collapse
I thought it didn't accept 1s anymore?
Sent from my HTC One X using xda app-developers app
Herc08 said:
thats what i said, i was trying to understand how you have s-off, but the bootloader is locked (not re-locked)
do you have the unlock_code.bin that you first used?
Click to expand...
Click to collapse
No idea bro! I bricked my phone, then sent it to get JTAGed, I asked them to update my phone to 4.1.1 and this is what I got.
exad said:
I thought it didn't accept 1s anymore?
Click to expand...
Click to collapse
Folks have been reporting still being able to use 11111111 (even after it was reported that HTC was blocking it), while others have had to change to 22222222. There doesn't seem to be any rhyme or reason. But you're right, if 11111111 doesn't work for the OP, they should try 22222222.
So I successfully unlocked my boot loader. So now I have root, S-OFF and unlocked bootloader. The question is now I want to flash a custom ROM i.e. ViperXL. Do I need to flash boot.img first like it is with 1.14 hboot?
Not if you are s-off.
Sent from my HTC One X using xda premium
---------- Post added at 08:20 PM ---------- Previous post was at 08:17 PM ----------
What recovery are you using?
Sent from my HTC One X using xda premium
Venomtester said:
Not if you are s-off.
Sent from my HTC One X using xda premium
---------- Post added at 08:20 PM ---------- Previous post was at 08:17 PM ----------
What recovery are you using?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
But I am on the 3.18 firmware with JB 4.1.1. I just need to flash the ROM in TWRP?
uzair_rock said:
But I am on the 3.18 firmware with JB 4.1.1. I just need to flash the ROM in TWRP?
Click to expand...
Click to collapse
Since you are s-off, you can just flash in twrp as normal. You can fastboot the boot.img if you want, but it isnt necessary. So if you want to download the zip straight from your phone, you can...no pc needed. S-off is almost like a super phone...
Yes. S-Off makes its possible to flash roms without flashing boot image separately. Just flash the zip from twrp.
Sent from my HTC One X using xda premium
Related
Hi there. Got a message on my phone to install new JB Update, BUT, my one S is rooted, hboot 1.16 ,TWRP Recovery, Rom stock 4.0.4.
I probably need to relock bootloader and flash stock recovery. I tried to find some nooby guide about that but no joy and after seeing that a few people bricked their phone I want to be sure Im doing everything correctly. So.
1. Do I need to flash stock recovery first?
2. If so then maybe relock bootloader. How?
3. Run Update. How?
Thanks for answer.
And merry Xmas.
:thumbup:
Sent from my HTC One S using xda app-developers app
You need to unroot and relock bootloader. After you do this you download and install the update and then you re-unlock bootloader and re-root you want
Sent from my HTC One S using xda app-developers app
You can just flash the stock recovery. And change CID to HTC__001.
Sent from my HTC One S using Tapatalk 2
tominozh said:
Hi there. Got a message on my phone to install new JB Update, BUT, my one S is rooted, hboot 1.16 ,TWRP Recovery, Rom stock 4.0.4.
I probably need to relock bootloader and flash stock recovery. I tried to find some nooby guide about that but no joy and after seeing that a few people bricked their phone I want to be sure Im doing everything correctly. So.
1. Do I need to flash stock recovery first?
2. If so then maybe relock bootloader. How?
3. Run Update. How?
Thanks for answer.
And merry Xmas.
:thumbup:
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Are you in the USA ??
---------- Post added at 07:48 PM ---------- Previous post was at 07:46 PM ----------
How do you do that?
You can just flash the stock recovery. And change CID to HTC__001.
I am useing t mobile with 2.31.401 .If i will change super cid to HTC__001 will be save to install ota sense4+ update?
i don't think he is or else i would have gotten the same message of JB
regarding your phone, i would suggest relocking and unrooting, else it may crash...
i have the same question, im new with my htc one s and i got it already rooted and it runs on a viperoneS so i dont have any idea on how the 1st owner did it and i dont know anything about modding this phone. i try to look at one s forums on how to go back to stock but no luck.
info of my phone( the things i know on my phone)
unluck bootloader
rooted with supersu
clockworkmod (inside this program i saw 3 recoveries in the backup/recovery menu, oneS ics stock, oneS ics rooted, viperoneS)
my one s runs viperoneS 1.2.1
now i want to get back to stock rom because i want to update to official jellybean.
i hope someone can teach me or lead me on how to do it.
OR
should i just wait for viperoneS to update to JB?
Thanks in advance peeps
What's this talk of people bricking during the ota with supercid? I was under the impression that taking an ota while unlocked is a bad idea
absolutelygrim said:
What's this talk of people bricking during the ota with supercid? I was under the impression that taking an ota while unlocked is a bad idea
Click to expand...
Click to collapse
It's usually not a very good idea to install an OTA whilst unlocked, there's a small chance it will mess up (higher than if it were locked). But what doubles that chance is if you have SuperCID, the new JB OTA messes up at least 60% of phones with SuperCID. I don't know why, since SuperCID is supported in the android-info.txt.
It might be because when you're SuperCID'd, does it say that in HBOOT? If a new HBOOT like 2.15 needs to overwrite the previous one, it might cause problems. That's just a guess though, and doesn't explain why it went smoothly for other people.
Sent from my HTC One S using Tapatalk 2
yfcpunishment said:
i have the same question, im new with my htc one s and i got it already rooted and it runs on a viperoneS so i dont have any idea on how the 1st owner did it and i dont know anything about modding this phone. i try to look at one s forums on how to go back to stock but no luck.
info of my phone( the things i know on my phone)
unluck bootloader
rooted with supersu
clockworkmod (inside this program i saw 3 recoveries in the backup/recovery menu, oneS ics stock, oneS ics rooted, viperoneS)
my one s runs viperoneS 1.2.1
now i want to get back to stock rom because i want to update to official jellybean.
i hope someone can teach me or lead me on how to do it.
OR
should i just wait for viperoneS to update to JB?
Thanks in advance peeps
Click to expand...
Click to collapse
anybody please?
yfcpunishment said:
anybody please?
Click to expand...
Click to collapse
I updated OTA on a virgin device. I now want to revert back to ICS. So if anyone has a way of permanently rooting a JB device on S4, please bell me.
Is there a way we can erase entire system OS, like a rooted device can using TWRP? If so after erasing system OS we can use older RUU? Afterwards then unlock bootloader and root, mission accomplished root successful. But does anyone know if you can do the erase system OS through the Command Prompt on platform-tools. If so how!? We might not be able to root 3.18 AT&T One X because AT&T are jerks but once we find a way to downgrade problem solved, maby that's the loop hole into the software I just don't know how to do it.
Wrong section
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
And the answer is no ..
a box of kittens said:
Wrong section
---------- Post added at 10:30 PM ---------- Previous post was at 10:29 PM ----------
And the answer is no ..
Click to expand...
Click to collapse
Oops sorry about that. Can a moderator move it? Also your positive it cant be done?
Techinstein said:
Oops sorry about that. Can a moderator move it? Also your positive it cant be done?
Click to expand...
Click to collapse
no this is not going to work. You need root to be able to do anything like this, and this is not a way to root.
Erasing the OS wont make a difference, RUU contains everything including my grandmothers panties, not just a OS.
XsMagical said:
Erasing the OS wont make a difference, RUU contains everything including my grandmothers panties, not just a OS.
Click to expand...
Click to collapse
In that case can't you I or someone brick the one x on purpose. Then use the RUU? Then root and unlock and then mission accomplished?
Techinstein said:
In that case can't you I or someone brick the one x on purpose. Then use the RUU? Then root and unlock and then mission accomplished?
Click to expand...
Click to collapse
Nope BC without perm root you can only ruu to the version you were previously on.
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Nope BC without perm root you can only ruu to the version you were previously on.
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I used to be on ICS 1.14 then upgraded , but i tried factory reset and nothing happened. Well ruu 2.20 work to downgrade for me? Or other people with the same problem as me at least?
So you want to root your phone or downgrade from 3.18? Do you want to use CM rom or what?
jun10rocks said:
So you want to root your phone or downgrade from 3.18? Do you want to use CM rom or what?
Click to expand...
Click to collapse
I want to downgrade back. Then root. If you know how thanks! As said above I hade ICS before JB then it updat
ed to 2.14 and 3.18 firmware.
Techinstein said:
I want to downgrade back. Then root. If you know how thanks! As said above I hade ICS before JB then it updat
ed to 2.14 and 3.18 firmware.
Click to expand...
Click to collapse
You can't downgrade from 3.18 but some roms are based on older versions. What's wrong with 3.18?
jun10rocks said:
You can't downgrade from 3.18 but some roms are based on older versions. What's wrong with 3.18?
Click to expand...
Click to collapse
if you previously had s-off before the ota then you can unlock/root/and flash i downgraded to ics 2.20 after jb update no issues
Idea but I'm no hacker so I could be very very wrong.......
Techinstein said:
Is there a way we can erase entire system OS, like a rooted device can using TWRP? If so after erasing system OS we can use older RUU? Afterwards then unlock bootloader and root, mission accomplished root successful. But does anyone know if you can do the erase system OS through the Command Prompt on platform-tools. If so how!? We might not be able to root 3.18 AT&T One X because AT&T are jerks but once we find a way to downgrade problem solved, maby that's the loop hole into the software I just don't know how to do it.
Click to expand...
Click to collapse
As far as I know the only reason you can't use lower ruus is because of the hboot.(could be wrong)
Also i think you can unlock bootloader with root and maybe get twrp (might be wrong)
So use this to downgrade to 1.09 http://forum.xda-developers.com/showthread.php?t=1982442 (not sure it will work for your hboot)
then use the hboot 1.09's respective ruu.. I think 1.85.
root 1.85 then wham rooted.
But this is just a guess made by a guy who doesn't do these things. I'm honestly more of a hardware guy than software.
But the only to find out is for a guy who knows about software to tell me I'm an idiot or for you to try it one an actual xl.
Unless you're s-off you CAN NOT ruu down.... Only up my brother... OP hasn't been 100% clear if he's s-off or not....
If he has a telus or rogers phone he can unlock the bootloader without root. ATT models HAVE to have root access, if not htcdev will let you know your device isn't supported.
If you were unlocked BEFORE taking the update, should you be able to still have held on to the original unlock token you might be able to fastboot it again and unlock, fastboot twrp, flash rom or SU..... Although I can almost guarantee I'm wrong lol
If you were rooted, unlocked, and took the ota you should have bricked. So is there a chance you had s-off?
Sent from my One X using Tapatalk 2
oops forgot one thing
boss1019 said:
As far as I know the only reason you can't use lower ruus is because of the hboot.(could be wrong)
Also i think you can unlock bootloader with root and maybe get twrp (might be wrong)
So use this to downgrade to 1.09 http://forum.xda-developers.com/showthread.php?t=1982442 (not sure it will work for your hboot)
then use the hboot 1.09's respective ruu.. I think 1.85.
root 1.85 then wham rooted.
But this is just a guess made by a guy who doesn't do these things. I'm honestly more of a hardware guy than software.
But the only to find out is for a guy who knows about software to tell me I'm an idiot or for you to try it one an actual xl.
Click to expand...
Click to collapse
oops i forgot makesure you have a linux installation everything you need to have is in the thread
does he want to downgrade to root? because 3.18 is rootable
jun10rocks said:
does he want to downgrade to root? because 3.18 is rootable
Click to expand...
Click to collapse
As of right now 3.18 is not rootable
Sent from my HTC One X using xda app-developers app
Megadoug13 said:
As of right now 3.18 is not rootable
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I updated to the 3.18 update and rooted the phone or was there a newer update because I got the update about 2 weeks ago.
InflatedTitan said:
Unless you're s-off you CAN NOT ruu down.... Only up my brother... OP hasn't been 100% clear if he's s-off or not....
If he has a telus or rogers phone he can unlock the bootloader without root. ATT models HAVE to have root access, if not htcdev will let you know your device isn't supported.
If you were unlocked BEFORE taking the update, should you be able to still have held on to the original unlock token you might be able to fastboot it again and unlock, fastboot twrp, flash rom or SU..... Although I can almost guarantee I'm wrong lol
If you were rooted, unlocked, and took the ota you should have bricked. So is there a chance you had s-off?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
S-Off is the only reason i did not brick when running the 3.18 RUU on my current device also why not just hook up an otg cable with a pj83img.zip and flash a radio with a modified mainver in the android-info.txt? thats how i have meen modifying the mainver in almost every htc device since the Touch Diamond
The reason you can't wipe the whole phone is that important portions of the firmware are write-protected without s-off.
If you were s-off before, you haven't lost root, you just need to push your custom recovery back on and then flash a rooted rom.
okay so this time around i made sure my htc one x was S-Off and i didnt do anything wrong. i installed a rom that themes sense 5 and what not... anyways the install failed and when i went to go boot up it didnt go further than the htc splash screen... i can get to bootloader but i cannot load recovery, it opens and then 3 seconds later it closes and then im back at splash screen... any ideas on how to fix?
Redownload twrp, check md5
fastboot flash recovery recoveryfilename.img
Fastboot erase cache
Fastboot reboot-bootloader
select recovery
If that doesnt work, since youre s-off, just ruu.
Sent from my Sony Tablet S using xda app-developers app
exad said:
Redownload twrp, check md5
fastboot flash recovery recoveryfilename.img
Fastboot erase cache
Fastboot reboot-bootloader
select recovery
If that doesnt work, since youre s-off, just ruu.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
thank you Exad. im just going to run ruu. but since im ruu i should be fine?
exad said:
Redownload twrp, check md5
fastboot flash recovery recoveryfilename.img
Fastboot erase cache
Fastboot reboot-bootloader
select recovery
If that doesnt work, since youre s-off, just ruu.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
THANK YOU MAN i did what you said. now i just gotta flash my back up. i really wish i coudl delete this post now :/
Yeah Ive RUUed at least ten times with my bootloader unlocked and cid as 11111111
Sent from my Sony Tablet S using xda app-developers app
As long as you aren't taking an ota supercid won't hurt you
Sent from my Nexus 4
Megadoug13 said:
THANK YOU MAN i did what you said. now i just gotta flash my back up. i really wish i coudl delete this post now :/
Click to expand...
Click to collapse
**** happens. I embarrass myself on here all the time. Glad its working again.
Sent from my Sony Tablet S using xda app-developers app
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
mirGantrophy said:
As long as you aren't taking an ota supercid won't hurt you
Sent from my Nexus 4
Click to expand...
Click to collapse
It bricked my telus phone when I ruud with supercid. No ota.
Sent from my Sony Tablet S using xda app-developers app
exad said:
**** happens. I embarrass myself on here all the time. Glad its working again.
Sent from my Sony Tablet S using xda app-developers app
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
It bricked my telus phone when I ruud with supercid. No ota.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
I'm glad my phone is working too, am I looking forward to sense 5 roma coming out soon. I really want blinkfeed lol
Sent from my HTC One X using xda app-developers app
exad said:
**** happens. I embarrass myself on here all the time. Glad its working again.
Sent from my Sony Tablet S using xda app-developers app
---------- Post added at 08:36 PM ---------- Previous post was at 08:35 PM ----------
It bricked my telus phone when I ruud with supercid. No ota.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
I've done it many times :\
Sent from my Nexus 4
Megadoug13 said:
I'm glad my phone is working too, am I looking forward to sense 5 roma coming out soon. I really want blinkfeed lol
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sense 5 is already out. Look in the "getting port to boot" thread.
Sent from Xparent Red using my Venomized Evita
mirGantrophy said:
As long as you aren't taking an ota supercid won't hurt you
Click to expand...
Click to collapse
Its been well documented here (happened to more than a few folks):
3.18 RUU + SuperCID + S-On = brick
redpoint73 said:
Its been well documented here (happened to more than a few folks):
3.18 RUU + SuperCID + S-On = brick
Click to expand...
Click to collapse
Doesn't seem to be limited to 3.18 RUU as the RUU I used was for an older software ver. since telus never released a 3.17 ruu.
exad said:
Doesn't seem to be limited to 3.18 RUU as the RUU I used was for an older software ver. since telus never released a 3.17 ruu.
Click to expand...
Click to collapse
Yeah, I saw you commented on the Telus RUU in a previous reply earlier on this thread. I hadn't heard of RUUs for other carrier (aside from 3.18 from AT&T) bricking due to SuperCID and S-on, so I was just commenting on what I knew.
redpoint73 said:
Its been well documented here (happened to more than a few folks):
3.18 RUU + SuperCID + S-On = brick
Click to expand...
Click to collapse
I have only done an ruu with supercid and s-on with 1.44, 1.73, 1.85 and 2.20, I guess at&t put in some extra security measures. I never bricked on those. But my phone did catch on fire fwiw
Sent from my Nexus 4
mirGantrophy said:
I have only done an ruu with supercid and s-on with 1.44, 1.73, 1.85 and 2.20, I guess at&t put in some extra security measures. I never bricked on those. But my phone did catch on fire fwiw
Click to expand...
Click to collapse
Yup, on older firmwares it was fine to RUU with SuperCID and S-on. But not so on 3.18. Nobody here really knows why 3.18 bricks the phone under these conditions, but it does.
redpoint73 said:
Yup, on older firmwares it was fine to RUU with SuperCID and S-on. But not so on 3.18. Nobody here really knows why 3.18 bricks the phone under these conditions, but it does.
Click to expand...
Click to collapse
I have a feeling it has to do with the write protection that gets implemented.
any jellybean update for evita with supercid + s-on will brick
exad said:
Redownload twrp, check md5
fastboot flash recovery recoveryfilename.img
Fastboot erase cache
Fastboot reboot-bootloader
select recovery
If that doesnt work, since youre s-off, just ruu.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
Wow I did the same thing thank you.
redpoint73 said:
Its been well documented here (happened to more than a few folks):
3.18 RUU + SuperCID + S-On = brick
Click to expand...
Click to collapse
That being said.... I believe I was the first to experience it lol
Sent from my HTC One XL using xda app-developers app
i've stuck with cwm since release since i havent had any of the same twrp woes. even with twrp 2.3.3.1 i still had problems with getting into recovery from bootloader, which is a pain when you are bootlooping. usually if you manually get into bootloader without the phone plugged into pc then once in bootloader you plug your phone into pc you have a better chance of getting it to load on the first try, same goes for getting unlock token to take.
I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.
seth50k said:
I want to be able to flash the latest CM10.1 for my AT&T HTC One X. Details about the phone-
Unlocked with HTCDev. Hboot 1.14.0002. Have latest TWRP flashed. Says TAMPERED, UNLOCKED, and S-ON.
I tried a RUU to update the Hboot, but that didn't work.
How can I update the firmware so I can run latest ROMs like CM10.1? I've looked at similar questions, but the answers were for the International Version of the HTC One X.
Any help or suggestions are appreciated.
Click to expand...
Click to collapse
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium
31ken31 said:
S-off
Run 3.18 ruu (no need to relock with s-off)
Relash recovery
Flash cm10
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?
seth50k said:
Ok, so here's the 2nd question. Somehow I managed to wipe whatever ROM I had on here (CleanROM I think), so it doesn't boot to anything. I've tried flashing CleanROM 6 and 3.20.401.1 Odexed, both error out in TWRP.
I'm assuming I've managed to softbrick it?
Click to expand...
Click to collapse
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?
RollTribe said:
Not sure 3.20.401.1 is but what did you do? You didn't do factory reset from bootloader did you?
Click to expand...
Click to collapse
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.
seth50k said:
I might have. What I was trying to do is clean out the phone to sell it, then get it updated, etc. I know in TWRP I ran probably every type of wipe, and I may have run Factory reset from the bootloader. It was a while ago and I set it aside, and now i've come back to it trying to get this phone sorted out.
Click to expand...
Click to collapse
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.
RollTribe said:
If you did, then you're not gonna be able to so anything with ROMs. Run an ruu, reunlock, and report back.
Click to expand...
Click to collapse
I've tried running RUU, it gets about halfway and fails. Do I need to flash the stock recovery and relock first, then run a RUU?
U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium
If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app
breezedragon said:
U need to relock the bootloader
Use command prompt
"Fastboot oem lock" from fastboot then run the ruu.... I recommend getting s-off as well is very easy and fast and it will save u a lot of troubles in the future plus u will not have to lock the bootloader to flash an ruu
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.
seth50k said:
Yeah, but you need a ROM working to even do the s-off process. So getting a ROM loaded is my main priority at this point. I can get into Bootloader/Fastboot, and I can still get to TWRP. Flashing a ROM from TWRP isn't working, and neither is running the latest RUU from fastboot. I get ERROR 159 when I try to run the latest RUU. So do I need to fastboot oemlock, then try again?
Perhaps running the RUU that was previously on it would work? 2.20, is what firmware was on it last.
Click to expand...
Click to collapse
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
exad said:
If you ruu with s-on and supercid you brick.
Be careful with your advice breeze. You'll cause him a brick.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Unlock, flash a sense rooted rom, soff and then ruu up to 3.18
Sent from my One X using xda app-developers app
RollTribe said:
Yeah, you have to run the same/later ruu if you're not S-Off. And you'll have to relock and you can flash stock recovery to be safe (but I think it flashes for you).
---------- Post added at 02:12 PM ---------- Previous post was at 02:11 PM ----------
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?
seth50k said:
I'm able to run the 2.20 RUU so far after relocking, it's about 3/4 of the way done. After this i'll try the latest RUU, then go from there to re-unlock, then S-OFF, THEN reflash TWRP?
Click to expand...
Click to collapse
Yup, you can swap the last two if you want
RollTribe said:
Yup, you can swap the last two if you want
Click to expand...
Click to collapse
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yep, looks like it's bricked. http://forum.xda-developers.com/showthread.php?t=2181929
seth50k said:
Well shoot...got so close. 2.20 RUU worked, then I did the latest RUU, which completed fine, but now the phone won't turn on, and won't even show a red LED charging indicator. WTF...
Click to expand...
Click to collapse
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.
RollTribe said:
Yeah, you have to s-off before running latest ruu. Damn sorry if I was unclear man.
Click to expand...
Click to collapse
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.
Sorry about your phone. It's Jtagg or new phone.
---------- Post added at 02:34 PM ---------- Previous post was at 02:34 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
I think it might be under warranty still, might try that route. Thanks for the help.
Click to expand...
Click to collapse
They state on their site that after unlocking the bootloader, RUU/OTA could brick you.
If you plan to try warranty with HTC, do not mention that you unlocked. They will charge you 200 straight up no matter what you say.
RollTribe said:
That's not necessarily true, I've ruu'ed with s-on and SuperCID and was fine. It is risky, though.
Click to expand...
Click to collapse
But was it the 3.18? It applies specifically for the AT&T 3.18 (and for some 3.17 JB RUUs on other carriers, and reported by some folks on this forum).
If you were able to run the 3.18 RUU successfully with SuperCID and S-on, I believe this is the first I've heard of it.
---------- Post added at 12:37 PM ---------- Previous post was at 12:33 PM ----------
seth50k said:
It's alright, just a little surprised given the fact that HTC allows you to unlock and such, but their own RUU bricks the phone if in such a state.
Click to expand...
Click to collapse
SuperCID as implemented on the AT&T One X is a mod/hack, and therefore not explicitly "allowed" by HTC. They can't really be held responsible for the effects of it.
SuperCID shouldn't be "expected" to brick under these conditions (worked fine with pre-JB RUUs), and nobody here has really been able to explain exactly why the phone bricks from SuperCID. But unfortunately, it does.
AT&T HOX from Android 4.2.1, with 3.18 firmware. Attempting to get to CM 10.1
Rooted and flashed TWRP via http://forum.xda-developers.com/showpost.php?p=41830252&postcount=201
Moved on to Facepalm S-off http://forum.xda-developers.com/showthread.php?t=2155071, was getting error 99.
Used the Viper solution from ChongoDroid on page 17 http://forum.xda-developers.com/showpost.php?p=38186473&postcount=163 using viper from http://forum.xda-developers.com/showthread.php?t=2087443
Install Viper from TWRP, Viper install stops at 0.00%, will not progress. Hard restart via power button battery remove sim, attempted s-off again. At some point I ended up getting the correct error 92. Success! Run 'fastboot oem boot', get list of errors, wait for boot into Android. Boot stops at white HTC splash screen, android will not boot.
Panic, hard restart back into bootloader, and this is where things go hazy (it was 5 in the morning by now). At this point I'm sure I put in some commands I should not have via adb (don't remember which ones), and did a factory reset via hboot. Recovery now brings me back into the bootloader. Bootloader shows *** TAMPERED ***, ***RELOCKED *** and *** Security Warning ***. I'm still S-ON with hboot 2.14.0000.
When in fastboot, my phone will not list via 'adb devices'. FAQ Q16 (http://forum.xda-developers.com/showthread.php?t=2136172) says if I did a factory reset in hboot, my SD mem is wiped and i need to format it from device manager. Device Manager shows my phone as Android USB Devices > My HTC and options are Update Driver Software..., Disable, and Uninstall. Updating drivers gives me a drivers up to date notice. No option to format the SD
Word is that if it turns on, it isn't bricked, but if I can't get my adb to recognize my phone, what is there that I can do to fix it? I'm on 64 bit Windows 7.
alright, first off, you flashed a ROM for the international quad core One X and you're lucky not to have bricked your phone. Secondly, what you're gonna need to do is run the 3.18 ruu and restore your phone to factory settings with that. That's the only way to recover from factory reset in bootloader. Before you do, you need to be S-Off. Which you are, correct?
Edit: re-reading this, it appears you're not s-off. I'm gonna need to call in some help here because 3.18 ruu with SuperCID will brick you, but I don't think you can use a lower RUU since you're s-on. Anyone know what to do? If you are s-off and I just misread your post, then go ahead and run the ruu.
If it turns on, there's always a way to fix it!
Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app
Correct, I am still s-off, and 'adb devices' gives an empty list, and does not list my phone. I cannot send commands to my phone via adb commands.
You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app
exad said:
Adb requires an os to work, since you can't boot to your os, no Adb
That being said, in bootloader, you should be able to access your phone with fastboot. Boot to bootloader/fastboot with your phone plugged in to your pc.
Do: fastboot devices and confirm that fastboot commands reach your phone, then we will move on to the next step.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
exad said:
You just said in your first post you're still s-on......
These details are extremely important so please be sure of what you've typed prior to posting.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.
Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app
Korad said:
Yes, sorry. I realized my mistake as soon as I posted, but since I'm a new member I can only edit or reply every 5 minutes.
Yes, I am S-ON. S-ON, not S-OFF.
And aha, yes. 'fastboot devices' does list my phone.
Click to expand...
Click to collapse
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium
exad said:
Good good. So first you'll want to unlock your bootloader again since it's relocked. Just flash the unlock_code.bin or whatever it's called again that you previously used.
Sometimes if you're relocked it does the unlock process like it's going to unlock but then leaves you relocked. If this happens press and hold power to simulate a battery pull and try again. It should work eventually. Might take several tries.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***
Korad said:
Okay, flashed Unlock_code.bin on first try, now showing *** UNLOCKED ***
Click to expand...
Click to collapse
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And... Here: http://forum.xda-developers.com/forumdisplay.php?f=1726
Sent from my HTC One X using xda app-developers app
exad said:
Do as ken posted above though twrp 2.6 is supposedly stable and fine too.
Roms from here are safe to flash: http://forum.xda-developers.com/forumdisplay.php?f=1541
And...:
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Have you flashed 2.6 yet? I've heard it works as well but was waiting for more input
Sent from my HTC One XL using xda premium
Not yet, going to when I get home. Jacobas92 said hes been using it though and I trust him.
Sent from my HTC One X using xda app-developers app
Well I'll take ur word for it. Gonna download and flash now and test the hell out of all options.
Sent from my HTC One XL using xda premium
31ken31 said:
I'm assuming you have supercid already?
I would reflash twrp.. nothing higher that 2.3.3.1
Then load a sense Rom from this forum through twrp. Just to get a running os on the phone. Then you can s-off and run 3.18 ruu
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
I believe you need to be on a rooted ROM to get s-off.
Korad said:
So I'm waiting on ViperXL to download (going very slowly), but if I'm looking to get to CM 10.1, and have root with TWRP, do I need to flash a ROM with TWRP first or can I do the Facepalm S-Off and move straight to CM 10.1 without flashing a middle-man ROM?
Click to expand...
Click to collapse
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium
31ken31 said:
Viper xl will work fine that's what I used to s-off. Not with the new cm10.1 kernel you have to ruu up to 3.18 before you install it.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
hes already on 3.18
If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?
Korad said:
If I'm using ViperXL as my ROM during S-Off, will I want to use ChongoDroid's extra steps when installing ViperXL or should I only need to do those if the Facepalm S-Off steps don't work by themselves?
Click to expand...
Click to collapse
You should be able to S-OFF with viperxl without any problems just by flashing viperxl and following the S-OFF thread right after.
So ViperXL finally finished downloading, and I've sent the command to push the .zip to /sdcard in prep to install it with TWRP, but it's been stuck there for 15+ minutes. Should I be worried? Should I restart?