Database Info

S-OFFing Relocked Sensation Xe

Hi all, I had to re-install a stock rom from an HTC RUU. Prior to that I was HTC unlocked, HBOOT 1.27, firmware 3.33, rooted, custom ROMs.
Right now the bootloader is re-locked, HBOOT 1.29, european stock 3.33.401.106 with 11.76A.3504.00U_11.24A.3504.31_M radio.
The objective is to re-gain S-OFF and go trough all the way to custom ROM again.
I was thinking to execute fastboot oem writesecureflag 3
To my understanding this should clear off the relocked flag.
At this point to go to htcdev and proceed with that like I did already once.
Probably the above is too simple to work, but the whole JuopunutBear timing thing is a bit an issue having tried already in ther past.
Any help/feedback is greatly appreciated.

DiscreteTask said:
Hi all, I had to re-install a stock rom from an HTC RUU. Prior to that I was HTC unlocked, HBOOT 1.27, firmware 3.33, rooted, custom ROMs.
Right now the bootloader is re-locked, HBOOT 1.29, european stock 3.33.401.106 with 11.76A.3504.00U_11.24A.3504.31_M radio.
The objective is to re-gain S-OFF and go trough all the way to custom ROM again.
I was thinking to execute fastboot oem writesecureflag 3
To my understanding this should clear off the relocked flag.
At this point to go to htcdev and proceed with that like I did already once.
Probably the above is too simple to work, but the whole JuopunutBear timing thing is a bit an issue having tried already in ther past.
Any help/feedback is greatly appreciated.
Click to expand...
Click to collapse
fastboot oem writesecureflag 3 returns bootloader to S-ON, it wont help you.
The only way to S-OFF 1.2x.xxxx HBOOT versions is JuopunutBear S-OFF. Oh and did you know you dont have to be S-OFF to flash ROMs, search for the Flashing ROMs with S-ON guide and follow it.

Jonny, thank you for your input. To be honest I did not know that it was possible flashing with S-OFF, I will look into this.
From you answer I understand that JuopunutBear S-OFF can be used the same also in the case the device was already S-OFF and relocked.
Thanks again.
Jonny said:
fastboot oem writesecureflag 3 returns bootloader to S-ON, it wont help you.
The only way to S-OFF 1.2x.xxxx HBOOT versions is JuopunutBear S-OFF. Oh and did you know you dont have to be S-OFF to flash ROMs, search for the Flashing ROMs with S-ON guide and follow it.
Click to expand...
Click to collapse

DiscreteTask said:
Jonny, thank you for your input. To be honest I did not know that it was possible flashing with S-OFF, I will look into this.
From you answer I understand that JuopunutBear S-OFF can be used the same also in the case the device was already S-OFF and relocked.
Thanks again.
Click to expand...
Click to collapse
you have hboot version 1.29.0000 yes? This means that the easier revolutionary method wont work on your phone (revolutionary is GingerBread only), so the only possible way to S-OFF on your phone is with the JuopunutBear method.
To get rid of the relocked text on the bootloader you need to flash the JuopunutBear hboot (which you can only do after S-OFF) then run an RUU. This will make the text say "LOCKED" again

[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

RUU after S-OFF

Is it possible to do a JB RUU after i just superCID and S-OFF? Because i wanna go back to stock.

Yes,but don't use the OTA RUU or you will brick your phone

yooouuri said:
Is it possible to do a JB RUU after i just superCID and S-OFF? Because i wanna go back to stock.
Click to expand...
Click to collapse
You can use any ruu while s-OFF, just simply plug phone to computer and run ruu. No need to relock bootloader.
For the supercid, it is recommended to change it back to original with fastboot command.
Fastboot oem write cid xxxxxxxx.
There has been a few bricks takin Jb ota while still supercid.
Sent from my HTC One S

tominozh said:
You can use any ruu while s-OFF, just simply plug phone to computer and run ruu. No need to relock bootloader.
For the supercid, it is recommended to change it back to original with fastboot command.
Fastboot oem write cid xxxxxxxx.
There has been a few bricks takin Jb ota while still supercid.
Sent from my HTC One S
Click to expand...
Click to collapse
Uwe303 said:
Yes,but don't use the OTA RUU or you will brick your phone
Click to expand...
Click to collapse
Thanks for your fast response, how do i know my original CID?
Im going to flash
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
So do i need to change my CID?

yooouuri said:
Thanks for your fast response, how do i know my original CID?
Im going to flash
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4.exe
So do i need to change my CID?
Click to expand...
Click to collapse
Just change it to
Fastboot oem writecid HTC__001
Sent from my HTC One S

tominozh said:
Just change it to
Fastboot oem writecid HTC__001
Sent from my HTC One S
Click to expand...
Click to collapse
Thanks
Edit;
If i change my CID to HTC__001 and i run the RUU, i cant change my language to dutch.
@tominozh
Edit;
Changed to HTC__E11, lets run the RUU again and hope!
CIDs list: http://forum.xda-developers.com/showthread.php?t=2139447

tominozh said:
Just change it to
Fastboot oem writecid HTC__001
Sent from my HTC One S
Click to expand...
Click to collapse
Its not mandatory to change your SuperCID back to stock just to install a RUU (with OTA RUU you get problems, but not with normal ones).
yooouuri said:
Thanks
Edit;
If i change my CID to HTC__001 and i run the RUU, i cant change my language to dutch.
@tominozh
Edit;
Changed to HTC__E11, lets run the RUU again and hope!
CIDs list: http://forum.xda-developers.com/showthread.php?t=2139447
Click to expand...
Click to collapse
Where you cant change the language?

HTC A9 s-off. after flashing RUU.exe software still modified and bootloader unlocked

HTC A9 s-off. after flashing RUU.exe software still modified and bootloader unlocked. WHY?????

UAALEX said:
HTC A9 s-off. after flashing RUU.exe software still modified and bootloader unlocked. WHY?????
Click to expand...
Click to collapse
RUU doesn't regain s-on and it doesn't relock bootloader. To relock bootloader you should be running a command in fastboot that's similar to
Code:
fastboot oem relock

EVOuser94 said:
RUU doesn't regain s-on and it doesn't relock bootloader. To relock bootloader you should be running a command in fastboot that's similar to
Code:
fastboot oem relock
Click to expand...
Click to collapse
but RUU.exe must set software to official, or not?

UAALEX said:
but RUU.exe must set software to official, or not?
Click to expand...
Click to collapse
To ruu you need to relock bootloader only if you are s-on, if you're s-off you don't need to worry about that.
Ruu also might not set it to official, because you would have a modified boot.img, though correct me if I'm wrong.