Database Info

Get back to stock sensation (T-Mobile) with s-on?

How would I go about doing this sso I can sell it? I'm currently on a 3.5 rom.

Same problem here (warranty exchange). I've done everything recommended here http://forum.xda-developers.com/showthread.php?t=1192300 but when I rune the .exe, I get an error [155] (incorrect ruu). I have searched everywhere for an up-to-date RUU, but have not had any luck.

You need to change your cid number to correspond with your carrier if you search the forums there is a list of them I presume you know how to go about this as you would have to have the super cid 11111111 or Eu HTC__001 to flash another Ruu other than your carriers
Sent from my HTC Sensation Z710e using XDA App

Change Cid number? Why would I have to do this? I've never messed with that before.

My apologies I presumed you had installed a unbranded firmware prior to rooting
Normally you have to change the cid to do this as the gold card method won't work
Sent from my HTC Sensation Z710e using XDA App

I followed a thread here to return to S-ON and then flashed the newest RUU from the post that lists all of the RUU's for the Sensation.

alright I've been reading and I'm still a little confused.
Basically, I have an s-off sensation with root and a rom. It's a T-Mobile sensation. I never debranded or anything like that.
What exactly do I need to do to return to stock as if I just bough it? I also noticed there are two TMOUS ruu files....which one do I use?

OK, lets begin
When you S-OFF'd the HBOOT changed to a newer one than your stock, TMOUS ROM. Because of this, you NEED Super CID to be able to go to a lower HBOOT. So that's why you need to change to it.
Once done, you can flash the stock 1.29.531.2 RUU. Once this has completed, you can change the CID back to the TMOUS one and then go back to S-ON and voila - one stock, ready to sell Sensation

Has any one got the Vodafone UK ROM please?
Cancel that. The download hasn't got that long left, so I'll just wait for it to finish.

EddyOS said:
OK, lets begin
When you S-OFF'd the HBOOT changed to a newer one than your stock, TMOUS ROM. Because of this, you NEED Super CID to be able to go to a lower HBOOT. So that's why you need to change to it.
Once done, you can flash the stock 1.29.531.2 RUU. Once this has completed, you can change the CID back to the TMOUS one and then go back to S-ON and voila - one stock, ready to sell Sensation
Click to expand...
Click to collapse
Thanks....so how exactly would I do this super CID thing? lol
So basically...do super cid thing, flash stock RUU, then super cid again? Sorry, I've never really done much other than flash roms, so I don't know what this cid stuff is.

You should've really learnt all this before jumping in as you should always know how to get out of something before you go ahead with it.
The guide you followed to S-OFF has the Super CID procedure:
http://forum.xda-developers.com/showthread.php?t=1192300
However, before changing it you need to make a note of your current one. To do so, you need to run the following fastboot command:
fastboot getvar cid
Once done, use the guide above to write the Super CID. This will allow you to flash the 1.29.531.2 RUU.
Then, using the same procedure as writing Super CID, write your old one back. Then follow the guide to get S-ON
Having said all that, you could just try flashing the 1.29.531.2 RUU and if it works then follow the guide to go back to S-ON - it may work

I have tried to change it to 111111... but the exe gives me the error nontheless. What do i change the CID TO?

akbisw said:
I have tried to change it to 111111... but the exe gives me the error nontheless. What do i change the CID TO?
Click to expand...
Click to collapse
I'm sure you've already figured it out since the thread hasn't been updated since a couple of months back, but here's the link to the thread with the answer if anyone gets here while searching for the right T-MOUS Stock CID for sensation:
http://forum.xda-developers.com/showthread.php?p=23046170

be careful
if u updated firmware to ics be careful before flashing an ruu this messed up my phone

Sorry for bumping an old topic, this topic was helpful with what I needed. I need to return my phone to stock for a replacement. I completed all the steps but what can I double check to make sure I did it correct. I have stock rom and s on. My CID still shows "11111111". I was trying to get the OTA update to ICS but it won't let me download it so it worries me that I still am not completely stock.

[Q] Which is the actual CID? - different response from different tools

Hi,
If I check in fastboot I get CID 11111111 which I set myself during the setup of a custom ROM.
If I check with CID Getter application I get HTC__E11 my original CID.
Which one should I trust?
Also, anybody know if having a super CID would void the warranty? have to return my phone for repair so cleaning it up. All is different now is the CID.
Thanks a lot for your help!

saf_ro said:
Hi,
If I check in fastboot I get CID 11111111 which I set myself during the setup of a custom ROM.
If I check with CID Getter application I get HTC__E11 my original CID.
Which one should I trust?
Also, anybody know if having a super CID would void the warranty? have to return my phone for repair so cleaning it up. All is different now is the CID.
Thanks a lot for your help!
Click to expand...
Click to collapse
I would trust the one that you get it fastboot as the one you get from CID getter is the one that is in the build.prop of your ROM.
S-OFFing would void your warranty. You need S-OFF to set SuperCID so there. Connect the dots

thanks!
Guess that's a typo and you meant S-OFF voids the warranty. You are right, if I can connect the dots they can do it as well would they check the CID
Need to find a way to change the CID back. Does not allow me to S-off now with revolutionary coz I think I use a too recent RUU (saw some related threads). Will try with an older RUU version.
Cheers,

saf_ro said:
thanks!
Guess that's a typo and you meant S-OFF voids the warranty. You are right, if I can connect the dots they can do it as well would they check the CID
Need to find a way to change the CID back. Does not allow me to S-off now with revolutionary coz I think I use a too recent RUU (saw some related threads). Will try with an older RUU version.
Cheers,
Click to expand...
Click to collapse
YES! I meant S-OFF. That was embarrassing
I think you can just write CID just like how you SuperCID'd but writing proper CID instead of 11111111. I haven't done it myself so I can't help you there.
Just go to viper's thread here. He has instructions for S-ONing
http://forum.xda-developers.com/showthread.php?t=1192300

saf_ro said:
thanks!
Guess that's a typo and you meant S-OFF voids the warranty. You are right, if I can connect the dots they can do it as well would they check the CID
Need to find a way to change the CID back. Does not allow me to S-off now with revolutionary coz I think I use a too recent RUU (saw some related threads). Will try with an older RUU version.
Cheers,
Click to expand...
Click to collapse
I think what you are searching for is
fastboot oem writecid ............ (Your cid)
Be sure to flash a proper ruu first, or you might end up bricking your device turning s on
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk

dgenx210 said:
YES! I meant S-OFF. That was embarrassing
I think you can just write CID just like how you SuperCID'd but writing proper CID instead of 11111111. I haven't done it myself so I can't help you there.
Just go to viper's thread here. He has instructions for S-ONing
http://forum.xda-developers.com/showthread.php?t=1192300
Click to expand...
Click to collapse
yep, already got it working.
I guess in my case the writecid was not working because I was back to S-ON and no root anymore
So, I flashed again the 1.50.401.1 ROM WITHOUT accepting the update, S-off, root, change the CID, flash the 1.50.401.1 again, change back to S-ON with the writesecureflag 3. Device can go now to repair.
Thanks for the help, great forum and info sources!

Will at&t ruu 2.20.502.7 will work on supercid 1111111 at&t hox to get back to stock?

Will at&t ruu 2.20.502.7 will work on supercid 1111111 at&t hox to get back to stock?
I am having at&t htc one x bootloader with :
**** tampered ****
**** unlocked ****
evita pvt shp s-on rl
hboot-1.09.0000
radio-0.19as.32.09.09_l
opendsp-v28.1.0.32.0504
emmc-boot
apr 2 2012,21:08:24
installed twrp 2.2.0 recovery and stock rooted rom 2.23707.2 asia generic.
Now the problem is, i am facing the mobile signal(not wifi) dropping issues and i have to revert back to at&t stock rom, i have downloaded the official at&t ruu 2.20.502.2.....exe,
but i am concerned with the doubt that will the ruu will work 100% on supercid 111111 without any problem after relocking the bootloder or do i have to revert back the stock at&t cid, and if yes then what is the procedure to revert back the stock at&t cid???????

If you ever want to unlock the bootloader again leave the cid alone. BTW you can just flash the radio from the new ota if you want. There's a thread in development section with radios

gunnyman said:
If you ever want to unlock the bootloader again leave the cid alone. BTW you can just flash the radio from the new ota if you want. There's a thread in development section with radios
Click to expand...
Click to collapse
thanks for the help,appreciable. But i don't want to flash just the radio, coz i already did that, but it did not solve my problem. So the question still continues..Can i run Ruu with the current supercid 111111 or do i have to revert it back to stock???
SORRY FOR BAD ENGLISH. ITS NOT MY FAMILIAR LANGUAGE.

You don't have to change cid to flash the ruu just relock the bootloader

gunnyman said:
you don't have to change cid to flash the ruu just relock the bootloader
Click to expand...
Click to collapse
thanks for the help,

Are you already on 2.20? If not, why not run 1.85 RUU?

thedauntlessone said:
Are you already on 2.20? If not, why not run 1.85 RUU?
Click to expand...
Click to collapse
good question.

thedauntlessone said:
Are you already on 2.20? If not, why not run 1.85 RUU?
Click to expand...
Click to collapse
Doesn't look like the op is on 2.20, the hboot for 2.20 is 1.14.0002.

Absolutely Right, i am not on 2.20,
Sent from my HTC One XL using xda app-developers app

Sir this is not about 2.20 or 1.85, i just want to confirm is, if running a ruu on supercid 111111 will work 100% or do i have to revert to the region's cid of the ruu am using.
I dont want that ruu should get interupt by any reason nd i brick my phone coz i dont have any warranty or insurance on it.
SORRY 4 THE BAD ENGLISH, ITS NOT MY NATIVE LANGUAGE.
Sent from my AT&T HTC One X using xda app-developers app

hemsmaverick said:
Sir this is not about 2.20 or 1.85, i just want to confirm is, if running a ruu on supercid 111111 will work 100% or do i have to revert to the region's cid of the ruu am using.
I dont want that ruu should get interupt by any reason nd i brick my phone coz i dont have any warranty or insurance on it.
SORRY 4 THE BAD ENGLISH, ITS NOT MY NATIVE LANGUAGE.
Sent from my AT&T HTC One X using xda app-developers app
Click to expand...
Click to collapse
your question has been answered multiple times.
SuperCID will allow you to run the 2.20 RUU. The reason we're cautioning you is because once you do that, you will lose the ability to flash new radios at all and you'll have to flash a kernel in fast boot.
Also once you do this update to 2.20 you can't go backward to 1.85 even WITH SuperCID because the update includes a new HBOOT.

gunnyman said:
your question has been answered multiple times.
SuperCID will allow you to run the 2.20 RUU. The reason we're cautioning you is because once you do that, you will lose the ability to flash new radios at all and you'll have to flash a kernel in fast boot.
Also once you do this update to 2.20 you can't go backward to 1.85 even WITH SuperCID because the update includes a new HBOOT.
Click to expand...
Click to collapse
ok what will happen if i extract the rom.zip from the ruu and will extract and replace the hboot with earlier one and also the recovery with custom one and will rezip it and rename it as PJ83.img and will copy it to storage and run it in the current boot loader. will relock it before running the process.
Will this work and will i b able to flash the stock rom with same boot loader and custom recovery?
I AM AWARE INSTEAD OF DOING THIS I CAN JUST FLASH THE STOCK ROOTED 2.20 ROM FROM TWRP BUT I JUST WANT TO INCREASE MY TECHNICAL KNOWLEDGE AND WORK.

hemsmaverick said:
ok what will happen if i extract the rom.zip from the ruu and will extract and replace the hboot with earlier one and also the recovery with custom one and will rezip it and rename it as PJ83.img and will copy it to storage and run it in the current boot loader. will relock it before running the process.
Will this work and will i b able to flash the stock rom with same boot loader and custom recovery?
I AM AWARE INSTEAD OF DOING THIS I CAN JUST FLASH THE STOCK ROOTED 2.20 ROM FROM TWRP BUT I JUST WANT TO INCREASE MY TECHNICAL KNOWLEDGE AND WORK.
Click to expand...
Click to collapse
won't work because RUU's include a signature check and if you alter the files in any way, that signature check will fail.

gunnyman said:
won't work because ruu's include a signature check and if you alter the files in any way, that signature check will fail.
Click to expand...
Click to collapse
ok, well as per ur earlier suggestion, i have flash the radio incl ril files from at&t 1.85, asia 2.23, currently on a o2 2.29.
But signal dropping solution has not been resolved.
I have dropped the plan of running ruu and will install custom rom tn special edition 3.6
can u suggest me the best radio for better mobile signals? (i am from india -region asia)

[Q] HOX AT&T Update

Hello, I have my HTC One X of AT&T unlocked by code through AT&T. It´s Rooted and it´s Bootloader is unlocked and also has the CWM Recovery installed. Never flashed any ROM, it still have the Original ICS ROM, it´s S-ON. Can I update it manually or would I be bricking it?
I was going to follow this tuto http://www.titularesandroid.com/2013/03/actualiza-tu-htc-one-x-at-jelly-bean.html?showComment=1364530268627#c3645276792953205699 but it says that it shouldn´t have "SuperCID and S-on" I don´t have SuperCID because I legally unlocked it, my doubt is about S-on, should I be S-off? If I have to, how do you do it? Thank you.

philohtc said:
Hello, I have my HTC One X of AT&T unlocked by code through AT&T. It´s Rooted and it´s Bootloader is unlocked and also has the CWM Recovery installed. Never flashed any ROM, it still have the Original ICS ROM, it´s S-ON. Can I update it manually or would I be bricking it?
I was going to follow this tuto http://www.titularesandroid.com/2013/03/actualiza-tu-htc-one-x-at-jelly-bean.html?showComment=1364530268627#c3645276792953205699 but it says that it shouldn´t have "SuperCID and S-on" I don´t have SuperCID because I legally unlocked it, my doubt is about S-on, should I be S-off? If I have to, how do you do it? Thank you.
Click to expand...
Click to collapse
I would S-OFF. I can explain the steps I took but it may have been a bit overkill. I had a 1.09 hboot so I didn't want to take any risks. I'm on Telus which is only up to 3.17. I'm not sure how 3.18 would go as I understand AT&T has put a mechanism for checking with AT&T over the network. Nevertheless.
- I downloaded the RUU for my phone which was in my case a TELUS RUU 1.91.661.4 and then I extracted the rom from the RUU and the Hboot from the ROM and I flashed the stock Hboot.
- I Booted into the bootloader/fastboot and then I changed my CID back to default, in my case TELUS001. (I don't think you need to do this with S-OFF but it takes less than a minute to do)
- Rebooted back to bootloader/fastboot and ran the RUU
- When the RUU was done I was on ICS.
- Re-Unlocked my bootloader (I'm not on AT&T so no need for Super CID for me, was just to get S-OFF)
- Flashed TWRP
- Boot back to rom to get OTA
- After OTA was done, Booted to TWRP to root stock then nandroid backup for good measure, then flash whatever

philohtc said:
I don´t have SuperCID because I legally unlocked it,
Click to expand...
Click to collapse
SuperCID has nothing to do with SIM unlock. SIM unlock of course allows you to use the phone with another carrier's SIM. CID and SuperCID relate to the HTC firmware such as RUUs and OTAs (typically only allows you to install software intended for your carrier version).
If your phone is the AT&T version, and its bootloader unlocked it must be SuperCID. Period.
SuperCID + OTA = brick
SuperCID + RUU = brick
That is, unless you have S-off. So do the facepalm s-off if you want to RUU or OTA.
Another approach is just flash a stock rooted Jellybean ROM, or a custom ROM based on the AT&T update, such as CleanROM 6. These can be found in the Development forum section.

Get SuperCid,S-off, you are already unlocked but when you get those just ruu to the current OTA and wallah.

so philohtc are you now s-off with jb update?

Not yet, but I'm not 100% sure yet, still having doubts. Because I remember when unlocking the bootloader the CID was all in 1. So how do I put the original CID ? My steps would be the following (Please correct me if I am wrong): 1st- Facepalm S-off 2nd- SuperCID? 3rd- Update through HTC Software Device?. Please give me all the warnings so I don´t brick my phone, thank you!

Boot to bootloader/fastboot.
Do fastboot oem readcid
This will tell you your Cid
If it's 11111111 or 22222222 then proceed to S-OFF.
If not, proceed to SuperCID then S-OFF
Once your S-OFF, Run the RUU
If you want to be anal like I was, after s-off, before running the ruu, you can change your Cid back to an at&t Cid using fastboot oem writecid xxxxxxxx where the X's are the default Cid. I don't know it for at&t by heart.
Sent from my One X using xda app-developers app

exad said:
If you want to be anal like I was, after s-off, before running the ruu, you can change your Cid back to an at&t Cid using fastboot oem writecid xxxxxxxx where the X's are the default Cid. I don't know it for at&t by heart.
Click to expand...
Click to collapse
CWS__001

Appreciate that, thanks bud
Sent from my One X using xda app-developers app

[Q] RUU won't work

I have been trying to run a RUU to unroot the phone before I bring it in for a repair. I keep getting the 155 error and I searched through google for help on the error. I have read a few post about it but nothing works. I tried to run it through fastboot as well and that does not work. My phone information while in bootloader is Evita pvt ship s-on rl hboot 1.09.0000 radio .17.32.09.12 and I am running cleanrom v 6.5 as my rom. Since my rom and boot.img is based of 3.18 I tried to run the ruu on 3.18. Im not sure if its because it is an older verdion of bootloader while im running a rom that is based off the 3.18. So I also tried to flash a older rom and run the ruu for 1.73 but that didnt work either. Im stumped and very frustrated so please I need your help.

Could you post the download link for the RUU? Just wanna make sure you go the right one.
Sent from my HTC One XL using xda premium

Arrow44 said:
Could you post the download link for the RUU? Just wanna make sure you go the right one.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah for the 3.18 its http://bugsylawson.com/HTCFiles/Evi....24p.32.09.06_10.130.32.34_release_signed.exe
and for the 1.73 its http://www.ponack.net/designgears/b...73.502.2_2FE6772699D8596307CC997452BB8D25.exe
Also I read that in order to use the RUU correct I need to soff the phone, but then I cant upgrade the firmware to jellybean. Do you know if this is correct?

The phone will brick if you try to ruu or update to 3.18 while S-ON and superCID. Your CID right now, no doubt is 11111111. When the RUU runs it checks to see what your CID is, if it's not what it should be, it gives an error. If you change your CID back to CWS__001 you can run the 1.73 RUU but you can never update to 3.18 unless you S-OFF first or you'll brick.
to check your CID fastboot oem readcid.
You can change it once without S-OFF with fastboot oem writecid CWS__001 but you can't change it again with that command unless you're S-OFF

Arrow44 said:
Could you post the download link for the RUU? Just wanna make sure you go the right one.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
exad said:
The phone will brick if you try to ruu or update to 3.18 while S-ON and superCID. Your CID right now, no doubt is 11111111. When the RUU runs it checks to see what your CID is, if it's not what it should be, it gives an error. If you change your CID back to CWS__001 you can run the 1.73 RUU but you can never update to 3.18 unless you S-OFF first or you'll brick.
to check your CID fastboot oem readcid.
You can change it once without S-OFF with fastboot oem writecid CWS__001 but you can't change it again with that command unless you're S-OFF
Click to expand...
Click to collapse
Ok thanks. Im in the process of doing the S-OFF right now. What I want to do is get rid of the red text and make my phone look like the bootloader is locked and never tampered with. I remember doing this with my EVOLTE so it will look like the phone is S-ON and locked. After all that run the RUU for 2.20 so it can get repaired. Now after the repair I can root again and upgrade to the Jellybean firmware right?

cables2590 said:
Ok thanks. Im in the process of doing the S-OFF right now. What I want to do is get rid of the red text and make my phone look like the bootloader is locked and never tampered with. I remember doing this with my EVOLTE so it will look like the phone is S-ON and locked. After all that run the RUU for 2.20 so it can get repaired. Now after the repair I can root again and upgrade to the Jellybean firmware right?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2156368