Database Info

[Q] RUU after S-OFF?

Hi everyone.
I've been having very bad problems with by battery life lately (I mean BAD) across nearly virtually all ROMs and configurations... so I'm thinking it's time to RUU and see if it solves the problem before sending my phone off.
Currently, I'm bootloader unlocked, SuperCID, S-OFF, rooted, custom recovery, etc.
I've done an RUU before, before I got S-OFF, and I know that if you have an unlocked bootloader you have to 're-lock' it before running the RUU.
Since I'm S-OFF, are there any other prerequisites to RUUing?
Can I simply re-lock my bootloader, RUU, then unlock my bootloader, root, and I'll be good?
And will I remain S-OFF throughout the RUU? Will my S-OFF mess anything up?

Hydromea said:
Hi everyone.
I've been having very bad problems with by battery life lately (I mean BAD) across nearly virtually all ROMs and configurations... so I'm thinking it's time to RUU and see if it solves the problem before sending my phone off.
Currently, I'm bootloader unlocked, SuperCID, S-OFF, rooted, custom recovery, etc.
I've done an RUU before, before I got S-OFF, and I know that if you have an unlocked bootloader you have to 're-lock' it before running the RUU.
Since I'm S-OFF, are there any other prerequisites to RUUing?
Can I simply re-lock my bootloader, RUU, then unlock my bootloader, root, and I'll be good?
And will I remain S-OFF throughout the RUU? Will my S-OFF mess anything up?
Click to expand...
Click to collapse
From what i understand, you don't even need to relock your bootloader, while S-OFF, but I did it anyway when I RUU'd.
RUUing will not mess with S-OFF or anything.
After RUUing, I also Took the latest OTA from Telus (I'm with Telus, you may not be) And I noticed ROMs using a 3.17 base run much smoother and with less bugs. I did not, however, notice much difference in battery life with AOSP roms.
Hope this helps ya

exad said:
From what i understand, you don't even need to relock your bootloader, while S-OFF, but I did it anyway when I RUU'd.
RUUing will not mess with S-OFF or anything.
After RUUing, I also Took the latest OTA from Telus (I'm with Telus, you may not be) And I noticed ROM using a 3.17 base run much smoother and with less bugs. I did not, however, notice much difference in battery life with AOSP roms.
Hope this helps ya
Click to expand...
Click to collapse
OK, so you mean that after RUUing, you took the OTA, and Sense 3.17 ROMs ran smoother and better than before you took the OTA?
I'm thinking about using the 3.18 RUU. Since I'm S-OFF, am I safe to use any RUU I want since I can revert easily?
As in, I can safely use the 3.18 RUU (which is currently regarded unrootable), and if it turns out to be bad I can just go back to an older RUU?
Basically, will using the 3.18 OTA/RUU mess anything up if I'm S-OFF?

Hydromea said:
OK, so you mean that after RUUing, you took the OTA, and Sense 3.17 ROMs ran smoother and better than before you took the OTA?
I'm thinking about using the 3.18 RUU. Since I'm S-OFF, am I safe to use any RUU I want since I can revert easily?
As in, I can safely use the 3.18 RUU (which is currently regarded unrootable), and if it turns out to be bad I can just go back to an older RUU?
Basically, will using the 3.18 OTA/RUU mess anything up if I'm S-OFF?
Click to expand...
Click to collapse
Yes, I did find Viper and clean rom both ran much better than they did previously.
I'm sorry, I don't know about the 3.18 OTA... Hopefully someone else here can shed more light?
Theoretically, Since you're S-OFF, you should be able to update just fine. I haven't seen anyone actually do it yet though. I would test if I could.

I didn't relock I just ruu'd and after the process was done I just pushed twrp to my phone in fastboot and flashed viper. Only took a few mins top
Sent from my Elemental Venomized S-off HTC One XL

If I decide to update to a complete 3.18 base, is it better to use a 3.18 RUU or OTA? And if I use the OTA, how exactly do I 'flash' it (it's a ZIP file). Do I just put it on the top level of my internal storage, and boot into recovery, and select 'update' or whatever?

Hydromea said:
If I decide to update to a complete 3.18 base, is it better to use a 3.18 RUU or OTA? And if I use the OTA, how exactly do I 'flash' it (it's a ZIP file). Do I just put it on the top level of my internal storage, and boot into recovery, and select 'update' or whatever?
Click to expand...
Click to collapse
I used the ruu for 3.18 and haven't regretted it yet. My battery life has gotten much better.
Sent from my Elemental Venomized S-off HTC One XL

OTA just downloads through the phone. IE: Go to settings about phone, check for updates and it updates. You don't have to do anything else, it prompts you and updates for you.
If there was already a 3.18 RUU that would be the fastest way. Telus is slow with releasing RUU's so I had to use ICS myself. Neither way should give you trouble.

Here's to hoping my phone doesn't brick. Running the RUU as we speak (bootloader unlocked, s-off, super-cid)...

Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X

ECEXCURSION said:
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
Click to expand...
Click to collapse
Did you use the 3.18 RUU?

ECEXCURSION said:
Well it worked. Twrp 2.2.2.0 doesn't though. Ugh, 2.3x is so ugly.
Sent from my HTC One X
Click to expand...
Click to collapse
If you're hellbent on TWRP 2.2.2.0, downgrade the touchscreen firmware.

Hydromea said:
Did you use the 3.18 RUU?
Click to expand...
Click to collapse
Yeah I did. Maybe I'll look into downgrading the touchscreen firmware.
Sent from my HTC One X

If I'm S-OFF and use the 3.18 RUU, in order to use AOSP-based 4.2.2 ROMs, will I have to downgrade my touchscreen firmware?

Hydromea said:
If I'm S-OFF and use the 3.18 RUU, in order to use AOSP-based 4.2.2 ROMs, will I have to downgrade my touchscreen firmware?
Click to expand...
Click to collapse
yes you will here is how
http://forum.xda-developers.com/showthread.php?t=2159863

If I use the 3.18 RUU, how will I obtain root afterwards?
I'm already S-OFF and bootloader unlocked BTW.
And since I'm S-OFF, can I easily revert back to an older RUU without any extra steps?

Hydromea said:
If I use the 3.18 RUU, how will I obtain root afterwards?
I'm already S-OFF and bootloader unlocked BTW.
And since I'm S-OFF, can I easily revert back to an older RUU without any extra steps?
Click to expand...
Click to collapse
after ruu just fastboot flash a recovery transfer a rooted rom to your phone and flash in recovery
and with s-off you can run any ruu dont even need to relock bootloader

jerrycoffman45 said:
after ruu just fastboot flash a recovery transfer a rooted rom to your phone and flash in recovery
and with s-off you can run any ruu dont even need to relock bootloader
Click to expand...
Click to collapse
What he said lol
Sent from my Elemental Venomized S-off HTC One XL

this is all great info i would like to thank all of you
does this go for the rogers model as well?

babarnard said:
this is all great info i would like to thank all of you
does this go for the rogers model as well?
Click to expand...
Click to collapse
Yes.
Just an update. I successfully ruu'd to 3.18, downgraded hboot to 1.09, downgraded the touchscreen firmware, installed twrp 2.2.2.0 and all is well.
I'm sort of back where I started but maybe something good has come of it.
Sent from my HTC One X

Root 3.18 idea

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.

[Q] Can't update firmware, Unlocked/Tampered S-ON

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.

[Q] HTC One XL Evita trouble restoring to stock HELP

Hello,
So I have a HTC One XL Telstra (Australia) evita phone. I purchased it already rooted and I want to take it back to stock. I managed to RELOCK my phone back and now it only boots into the bootloader.
I have found the following RUU RUU_Evita_UL_Telstra_WWE_1.89.841.9_Radio_0.18c.32 .09.01_10.93a.32.20L_release_266699_signed but when I try to load it onto my phone I get an error that my bootloader is too new for this file. For the last two days I have been searching for a newer RUU but come up with nothing. Also CID hasnt been changed.
Now I am stuck, I am quite switched on with all OS but this is a first for me with Android. The following are the details in my bootloader:
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
Any help would be greatly appreciated. Also I don't have any backups.
Cheers!

You can't RUU backwards while you're s-on, that's your problem. Unlock your bootloader again, flash a custom rooted ROM, get s-off, then you can run any Evita RUU you want to.
Sent from my Evita

timmaaa said:
You can't RUU backwards while you're s-on, that's your problem. Unlock your bootloader again, flash a custom rooted ROM, get s-off, then you can run any Evita RUU you want to.
Sent from my Evita
Click to expand...
Click to collapse
Now this is where the fun starts, I thought of that but when I got to unlock it in htcdev the identification token is invaild for some unknown reason even though the CID hasnt been changed.
The idea is to just get it back to all stock.

Do you still have the original unlock token?
Sent from my Evita

Scratch that I just got a valid token but the whole purpose was to keep the bootloader locked with the stock OTA

Unlock. Twrp. Jb Rom. S-off. Ruu to older. Relock. Take stock otas.
Sent from my VENOMized HoxL

I know what your purpose is, and the instructions I detailed will get you there. Now that you've unlocked, flash TWRP, flash rooted ROM, get s-off, run the RUU you want to run, relock bootloader, take OTA's. It's the only way to do it after the mistake you made.
Sent from my Evita

timmaaa said:
I know what your purpose is, and the instructions I detailed will get you there. Now that you've unlocked, flash TWRP, flash rooted ROM, get s-off, run the RUU you want to run, relock bootloader, take OTA's. It's the only way to do it after the mistake you made.
Sent from my Evita
Click to expand...
Click to collapse
Half way there, up to s-off. Do you know of any tutorials specifcally related to the one xl? Btw thanks for all the help.

There are two s-off methods for our phone, Facepalm and Rumrunner. Facepalm won't work for you because it requires SuperCID, so Rumrunner is the one you want. Just go to that website and it explains everything. I haven't personally used it because I got s-off ages ago but it looks like a piece of cake.
Sent from my Evita
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
You're welcome by the way, happy to help.
Sent from my Evita

timmaaa said:
There are two s-off methods for our phone, Facepalm and Rumrunner. Facepalm won't work for you because it requires SuperCID, so Rumrunner is the one you want. Just go to that website and it explains everything. I haven't personally used it because I got s-off ages ago but it looks like a piece of cake.
Sent from my Evita
---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------
You're welcome by the way, happy to help.
Sent from my Evita
Click to expand...
Click to collapse
Rumrunner is definitely the way to go if you want to S-off your phone its so easy! Do you know of any RUU later than 1.89 Telstra? Most links I have a broken.

I believe the 1.89 RUU is the latest one, you can double check at androidRUU though.
Sent from my Evita

timmaaa said:
I believe the 1.89 RUU is the latest one, you can double check at androidRUU though.
Sent from my Evita
Click to expand...
Click to collapse
Yeh it is the latest one. I followed your instructions and now Im back to stock firmware which can receive OTA. Thank you so much for your help!

[Q]~[HELP] SuperCID, Unlocked, Rooted, and S-OFF, how to restore to stock AT&T ROM?

[Q]~[HELP] SuperCID, Unlocked, Rooted, and S-OFF, how to restore to stock AT&T ROM?
Hi, geeks,
For my AT&T HTC One X, I have followed you guys all the way to here now: with SuperCID, Bootloader Unlocked (via HTC Dev), Rooted of course, and S-OFF (with touchscreen firmware down-graded).
Now I want to go back to AT&T stock ROM to use the ISIS wallet. Could you please tell me how? I am worried that my phone get bricked!
Thank you so much!

You can just flash a stock at&t ROM which you'll find in our Android Development section. Or you can run the 3.18 RUU. This will also flash stock recovery, hboot, radio, and other firmware modules. The ROM is probably the better and easier option.
Sent from my Evita

Thank you, timmaaa. Do I need to lock the bootloader and so on? I saw it somewhere but can't find the link now.
timmaaa said:
You can just flash a stock at&t ROM which you'll find in our Android Development section. Or you can run the 3.18 RUU. This will also flash stock recovery, hboot, radio, and other firmware modules. The ROM is probably the better and easier option.
Sent from my Evita
Click to expand...
Click to collapse

To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita

timmaaa said:
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
Click to expand...
Click to collapse
I'm doing the same thing, but to attempt to trade in my phone. I assume that after running the RUU I should relock the bootloader. I want to get rid of the red text.
*EDIT* nevermind. didn't realize that the RUU clears out the *TAMPERED* flag and gets rid of the red text. should be all good now.

One more question, timmaaa: after flashing RUU, the recovery partition will be replaced with the stock recovery, and the S-OFF and boot loader will be kept as it is (based on what I learned from other posts of you). What if I need to flash CM again? I am confused because not many people are doing what I am. Thanks!
timmaaa said:
To run the RUU? No, because you're s-off you don't need to do any of that, just run the RUU through Windows.
Sent from my Evita
Click to expand...
Click to collapse

Yes, the RUU will install the stock recovery. Your phone will still be s-off and will still have an unlocked bootloader. All you need to do is install TWRP recovery again and then you can flash any ROM you like. Full instructions on how to install a recovery can be found in my How-To Guide For Beginners thread, link in my signature.
Sent from my Evita

Hi, timmaaa, I got a RUU error 155 when flashing RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial.exe.
Seems I need to re-lock the bootloader, which I am reluctant to do. Do I miss anything?
timmaaa said:
Yes, the RUU will install the stock recovery. Your phone will still be s-off and will still have an unlocked bootloader. All you need to do is install TWRP recovery again and then you can flash any ROM you like. Full instructions on how to install a recovery can be found in my How-To Guide For Beginners thread, link in my signature.
Sent from my Evita
Click to expand...
Click to collapse

You don't need to relock if you're s-off. Are you using a 2.0 or 3.0 usb port? Are you using a HTC cable? Are you in fastboot mode? Have you uninstalled HTC Sync Manager?
Sent from my Evita

Hi, timmaaa, I am using USB2.0 on windows XP, with a regular cable, not in fastboot mode, and haven't uninstalled HTC Sync Manager.
I will try flash in fastboot mode again.
timmaaa said:
You don't need to relock if you're s-off. Are you using a 2.0 or 3.0 usb port? Are you using a HTC cable? Are you in fastboot mode? Have you uninstalled HTC Sync Manager?
Sent from my Evita
Click to expand...
Click to collapse

aaronDroid80 said:
I'm doing the same thing, but to attempt to trade in my phone. I assume that after running the RUU I should relock the bootloader. I want to get rid of the red text.
*EDIT* nevermind. didn't realize that the RUU clears out the *TAMPERED* flag and gets rid of the red text. should be all good now.
Click to expand...
Click to collapse
You need to make sure the person you are trading with understands the phone is s-off and bootloader unlocked, and what that means.
---------- Post added at 01:57 PM ---------- Previous post was at 01:54 PM ----------
BBS678 said:
One more question, timmaaa: after flashing RUU, the recovery partition will be replaced with the stock recovery, and the S-OFF and boot loader will be kept as it is (based on what I learned from other posts of you). What if I need to flash CM again? I am confused because not many people are doing what I am. Thanks!
Click to expand...
Click to collapse
If you think you might still want to flash custom ROMs, you need to ask yourself why you want to return to stock in the first place.
Going back to stock if you are s-off, custom recovery, etc. is a step backward, not forward. Aside from getting on the correct hboot, firmware, etc. (or selling/trading your phone like the guy above), there is no benefit to going through all the hassle to running the RUU to get back to stock. Just flash a stock rooted ROM as timmaaa originally mentioned.
EDIT: Missed the part in the OP where it mentioned ISIS. See my response below (#13).

An update (for the forum): In fastboot mode, I have flashed Stock RUU successfully, without locking boot loader. After this, even in stock ROM, ISIS still doesn't work. I think it's caused by the SuperCID and S-OFF.
Timmaaa, do you know how I can SAFELY get SuperCID and S-OFF fixed? Thank you!
BBS678 said:
Hi, timmaaa, I am using USB2.0 on windows XP, with a regular cable, not in fastboot mode, and haven't uninstalled HTC Sync Manager.
I will try flash in fastboot mode again.
Click to expand...
Click to collapse

BBS678 said:
An update (for the forum): In fastboot mode, I have flashed Stock RUU successfully, without locking boot loader. After this, even in stock ROM, ISIS still doesn't work. I think it's caused by the SuperCID and S-OFF.
Timmaaa, do you know how I can SAFELY get SuperCID and S-OFF fixed? Thank you!
Click to expand...
Click to collapse
Reading around, root seems to be the only mod that interferes with ISIS. Its unlikely that s-off would interfere with ISIS. SuperCID? Its possible. Changing from SuperCID is very easy with fastboot. Just search for the command.
Also, be aware that you need a ISIS compatible SIM ("secure element SIM") available from your carrier.
http://www.att.com/shop/apps/isis-mobile-wallet.html#fbid=xHuv6S8moS4

Could be. HTC One X is not available on att.com now, so your link can't explain at this moment.
From here, https://www.paywithisis.com/get-started.html, it says AT&T HTC One X is compatible.
In addition, I do have a ISIS compatible SIM card from AT&T. The reason I suspect it is due to CID is that it is “heard" from this forum that ISIS doesn't work if you put an AT&T SIM card in the T-mobile version of GN3 (unlocked).
redpoint73 said:
Reading around, root seems to be the only mod that interferes with ISIS. Its unlikely that s-off would interfere with ISIS. SuperCID? I suppose its possible, but my gut says no. Especially in light of the following:
I'm thinking it more the issue that the AT&T One X is not a "ISIS ready phone": http://www.att.com/shop/apps/isis-mobile-wallet.html#fbid=xHuv6S8moS4
Also, be aware that you need a ISIS compatible SIM ("secure element SIM") available from your carrier.
Click to expand...
Click to collapse

BBS678 said:
Could be. HTC One X is not available on att.com now, so your link can't explain at this moment.
From here, https://www.paywithisis.com/get-started.html, it says AT&T HTC One X is compatible.
Click to expand...
Click to collapse
Yes, I later realized that One X is not available at all anymore from AT&T (and that it is supposed to be ISIS ready), and revised my above response accordingly.
BBS678 said:
In addition, I do have a ISIS compatible SIM card from AT&T. The reason I suspect it is due to CID is that it is “heard" from this forum that ISIS doesn't work if you put an AT&T SIM card in the T-mobile version of GN3 (unlocked).
Click to expand...
Click to collapse
It could also be that they are looking at the phone model number. So SuperCID is a possibility, but not certain.
Its easy to change from SuperCID with a simple fastboot command. Just search this forum for the proper syntax.
---------- Post added at 02:43 PM ---------- Previous post was at 02:32 PM ----------
Here is the command to change from CID:
fastboot oem writecid CWS__001
(note that CWS__001 has two underscores)

Thank you! I learned from this forum that changing S-OFF to S-ON is very risky, and currently S-OFF relies on a SuperCID, so I think it's also risky to change the CID back. Have you ever tried? I need more opinions on this before I take the risk.

BBS678 said:
Thank you! I learned from this forum that changing S-OFF to S-ON is very risky, and currently S-OFF relies on a SuperCID, so I think it's also risky to change the CID back. Have you ever tried? I need more opinions on this before I take the risk.
Click to expand...
Click to collapse
I honestly doubt s-off is blocking ISIS. S-off is exclusively an HTC invention, and I doubt ISIS would care about such a thing. I would recommend to leave s-off alone.
I wouldn't say its "risky" to change CID. As long as you still have s-off, I don't see any reason to still have SuperCID. But even so, you can still use the correct exploit to change back to SuperCID.

Hi, timmaaa, could you please shed some lights on this (change back to stock CID) please? Thanks!

here is my other post about ISIS: http://forum.xda-developers.com/showthread.php?p=49822333
redpoint73 said:
I honestly doubt s-off is blocking ISIS. S-off is exclusively an HTC invention, and I doubt ISIS would care about such a thing. I would recommend to leave s-off alone.
I wouldn't say its "risky" to change CID. As long as you still have s-off, I don't see any reason to still have SuperCID. But even so, you can still use the correct exploit to change back to SuperCID.
Click to expand...
Click to collapse

Everything that @redpoint73 has said is correct. There's pretty much no risk involved in changing your CID back to stock, having s-off does not rely on SuperCID. You can try changing your CID using the command that redpoint gave before.
There's pretty much no risk involved with going from s-off to s-on either. I don't know where you read that but I believe you're misunderstanding the information. Personally I wouldn't go back to s-on though because I don't believe that is affecting your ability to run ISIS. Plus getting s-off again can be tricky sometimes.
Sent from my Evita