Database Info

[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] Re root after OTA JB Update?

okay so ive already bricked 1 device because of the ota update my question is can i root/re-unlock the boot loader with out bricking this device? also ive been reading that htcdev now blocks supercid 111111 so if going to try getting another unlocktoken will i need to fastboot write cid 222222? also if my device is S-Off then why is it when i try to write in fastboot it returns the error Failed(Remote Not Allowed)... where in my evo 3d allows writing and it also is S-Off and Relocked
Current Specs:
Android 4.1.1
Software build:3.18.502.6 710RD
HBOOT INFO
*** RELOCKED***
EVITA PVT SHIP S-OFF RL
CID- 11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06

S-off on our device does not let you write certain things with a locked bootloader. Why? I'm not really sure.
You can't brick unlocking the bootloader unless you're crazy stupid and doing things wrong.
Do you not have the original unlock token from when you unlocked last time?
If not, does your current rom have root? If so you should be able to hex edit your Cid.
If not you're sol until 3.18 root comes out.
Sent from my HTC One X using xda app-developers app

exad said:
S-off on our device does not let you write certain things with a locked bootloader. Why? I'm not really sure.
You can't brick unlocking the bootloader unless you're crazy stupid and doing things wrong.
Do you not have the original unlock token from when you unlocked last time?
If not, does your current rom have root? If so you should be able to hex edit your Cid.
If not you're sol until 3.18 root comes out.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I actually have 5 different tokend for 5 different one x devices and i dont want to flash wrong token

FragmentedLogik said:
I actually have 5 different tokend for 5 different one x devices and i dont want to flash wrong token
Click to expand...
Click to collapse
Why not? what will happen?

exad said:
Why not? what will happen?
Click to expand...
Click to collapse
just hesitant on flashing it seeing how the recent OTA update hard bricked one of my Devices and i cant find a place to purchase a RIFF box, so im kinda trying to avoid hard bricking my 2nd device today

http://www.ort-jtag.com/ you can order them for 150.00 usd plus shipping.
Sent from my One X using xda premium

You'll have to wait until 3.18 root is achieved then unfortunately as you cannot change your CID in your phone's current state.
For future reference, don't bother relocking the bootloader after achieving s-off on this phone. It's pointless and creates issues like this.

exad said:
You'll have to wait until 3.18 root is achieved then unfortunately as you cannot change your CID in your phone's current state.
For future reference, don't bother relocking the bootloader after achieving s-off on this phone. It's pointless and creates issues like this.
Click to expand...
Click to collapse
okay but to verify i am s-off if i flash the unlock token what are the chances of a brick? mainly asking because i am wanting to do the 3 button remap mod and the new elemental kernel as well and only reason i relocked the bootloader and ran the JB ruu is because my basebands all except for lte kept losing signal at random

Can he not write a different cid since he's s off?

a box of kittens said:
Can he not write a different cid since he's s off?
Click to expand...
Click to collapse
Apparently not. Which doesn't surprise me as there are many things I could not do with s-off and a locked bootloader. This seems to be a quirk of the one xl

Can't he fastboot oem writecid if he's already supercid tho
Sent from my VENOMized HoxL

area51avenger said:
Can't he fastboot oem writecid if he's already supercid tho
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
Read the OP. He says it errors when trying to write a new cid.
Sent from my HTC One X using xda premium

With the evita, s-off + super cid is not enough, you require an unlocked bootloader aswell.

[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

Relock and RUU for o2 Germany One XL

I have a One XL with o2 Germany Branding (CID: O2___102)
HBOOT 2.14
S-ON
ROM installed: CM 10.1
I want to relock it and flash a Stock ROM. Reason is that I want to send it to warranty.
As far as I know the HBOOT of the ROM must not be older than 2.14 and I can't find an appropriate ROM.
1. fastboot oem lock
2. launch RUU (I tried some, but it did't work)
Do I have to flash a Stock Recovery after that?

Running an RUU returns the phone to being completely stock, including recovery. I hope your don't have SuperCID or you're gonna brick. Click the link in my signature, you'll find RUU threads there.
Sent from my Evita

timmaaa said:
Running an RUU returns the phone to being completely stock, including recovery. I hope your don't have SuperCID or you're gonna brick. Click the link in my signature, you'll find RUU threads there.
Sent from my Evita
Click to expand...
Click to collapse
And what if none of these RUUs work?
O2:
OTA_EVITA_UL_JB_45_S_O2_DE_3.17.207.1_0.23a.32.09. 29_10.128.32.34a_release_2990766qakrzbj4mpslnsy.zi p
OTA_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1-1.92.207.3_release_272963z2vl7cdycjk01nm4.zip

fly23 said:
And what if none of these RUUs work?
O2:
OTA_EVITA_UL_JB_45_S_O2_DE_3.17.207.1_0.23a.32.09. 29_10.128.32.34a_release_2990766qakrzbj4mpslnsy.zi p
OTA_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1-1.92.207.3_release_272963z2vl7cdycjk01nm4.zip
Click to expand...
Click to collapse
Those are ota updates... A ruu is an exe file that is run from Windows
Sent from my HTC One XL using xda app-developers app

The available o2 RUUs are too old
Sent from my One X using Tapatalk 4

So you run an older RUU and then take OTAs, you can't just flash OTA files, it won't work. You need to return the phone to being completely stock first though, s-on, original CID, locked bootloader, original recovery.
Sent from my Evita

I tried this file: RUU_EVITA_UL_ICS_40_S_O2_DE_2.29.207.1_Radio_0.19as.32.09.20_3_10.107.32.25L_release_272946_signed.exe, it didn't work (contentual: Error 170, USB Error)
The XL is S-ON (never was S-OFF), bootloader is relocked (fastboot oem lock), then I launched the RUU.exe.
What I read is, that I can't flash older ROMs (what ever that means). So, what can I do if the o2-RUUs are to old? Can I downgrade the HBOOT?
edit: Can I downgrade HBOOT with the JET (http://forum.xda-developers.com/showthread.php?t=1940512) and then ran a RUU?

Help with S-off, relock boot loader, and 3.18 ruu

Hello,
First thanks to any for all help I'm sure I'll receive. Im pretty sure of what I need to do but I'm a resident physician and can't afford to not have a phone by making a stupid mistake.
So I currently have supercid, am unlocked and rooted with boot loader 1.14. To update basically any roms or my current AOKP ROM I need 2.14. To get 2.14 I need to S-off, relock boot loader and run the 3.18 ruu, and reflash recovery.
Is this correct? The only other I'm confused of is relocking the bootloader, and them unlocking it again.
Thanks for any help.
Sent from my One X using XDA Premium 4 mobile app

You only need s-off to run the 3.18 RUU, locking the bootloader isn't necessary and only creates more work afterwards. So all you need to do is go here and get s-off, then you can download the RUU from here and run it. Your unlocked bootloader and s-off status will survive the RUU process but you will need to install TWRP recovery again afterwards.
Sent from my Evita

Thank man
Sent from my One X using XDA Premium 4 mobile app

No problems.
Sent from my Evita

timmaaa said:
You only need s-off to run the 3.18 RUU, locking the bootloader isn't necessary and only creates more work afterwards. So all you need to do is go here and get s-off, then you can download the RUU from here and run it. Your unlocked bootloader and s-off status will survive the RUU process but you will need to install TWRP recovery again afterwards.
Sent from my Evita
Click to expand...
Click to collapse
Will /SD survive the process as well? I have TWRP 2.6.00 on /SD at the root level and have been able to access it from the bootloader.
Thanks again, Timmaaa!

Your sd card shouldn't be wiped during the RUU process but you might want to make a backup just in case.
Sent from my Evita

how do I root again after RUU? do I just need to flash recovery image?

Just flash recovery and then a rooted ROM.
Sent from my Evita

thanks man. appreciate your help.

I've tried and have only been able to obtain unlocked boot loader and root no super cid or s-off ... I'm not sure what I'm missing ...
Sent from my HTC One X using Tapatalk[/QUOTE]
Sent from my HTC One X using Tapatalk

What are your bootloader details and which SuperCID method are you using?
Sent from my Evita

timmaaa said:
What are your bootloader details and which SuperCID method are you using?
Sent from my Evita
Click to expand...
Click to collapse
I finally was able to get it work I'm s-off know
Sent from my HTC One XL using Tapatalk

timmaaa said:
You only need s-off to run the 3.18 RUU, locking the bootloader isn't necessary and only creates more work afterwards. So all you need to do is go here and get s-off, then you can download the RUU from here and run it. Your unlocked bootloader and s-off status will survive the RUU process but you will need to install TWRP recovery again afterwards.
Sent from my Evita
Click to expand...
Click to collapse
This might be a dumb question but how do u run the 3.18 RUU? Do i plug my phone via usb and then run it? What do i do?

It's an exe file, so all you need to do is open it in Windows while your phone is connected in fastboot mode, then just follow the prompts. Make sure HTC Sync Manager is uninstalled, make sure no other programs are running, make sure screen saver/hibernation is turned off.
Sent from my Evita