[AT&T, Rogers HTC One X, Telstra One XL] cafe-con-leche:
So I have finally decided to root my AT&T HOX and want to flash custom rom, and I am running into a little bit of problem hoping someone could help me out. I have researched maybe a hundred pages/threads and I thought I was ready, until I run into problem and realized there are still many situations that I could get into.

So here is what I did:

- I was originally on ATT 2.20.

1. Download and followed the X-Factor root exploit instruction, changed CID successfully, got the unlock token and successfully unlocked bootloader. (At this point, I 'remember' seeing I had S-OFF without doing any additional step)

2. Flashed recovery with TWRP 2.6.3.0.

3. Flashed CleanROM. Everything went smooth. But after half day of using, it started random reboot.

4. So I did some release on the CleanROM thread, and seeing people mentioned flashing the firmware from Turge would fix the random reboot problem. So I downloaded the firmware and I 'think' here are the steps I have done:

- fastboot oem lock

- fastboot oem rebootRUU

- fastboot flash zip <Turge firmware>

5. Here comes the problem, while flashing zip, I first got error about "remote: not allowed", then I tried it again and got "remote: 12 signature verify fail". Then it's the same error from that time on.

6. So I gave up, thinking to backout of RUU mode and research for another solution, but I couldn't get back to normal system boot, it always boot to bootloader, and now I start to notice it says "Tampered" and "S-On".

7. So I flash my unlocktoken again, now I got back to my system (CleanROM). But it still shows S-ON and Tampered.

8. Wanting to get S-OFF and not Tampered, so I tried to run the ATT RUU of 2.20, it failed many times without much useful error, (mostly unknown error), somehow I was finally able to get it flashed after I issued a "fastboot oem lock". Now I am back on ATT's 2.20 rom with SuperCID and no more Tampering but "RELOCKED".

9. Run X-Factor root exploit again hopping to get S-OFF again, but no luck, instead, it's now "UNLOCKED" and "Tampered" again. but realized I still have supersu, so I am rooted, and my TWRP is still there.

10. Run "revone" script trying to get S-OFF, but I got error code 1. According to revone's guide, error code 1 means I am likely to never get S-OFF again on my phone.

I have also read that:

- Having SuperCID and S-ON would brick the phone when trying to do a upgrade RUU or OTA.

- If I have S-OFF and back to S-ON then I will never get S-OFF again.

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.14.0002

(bootloader) version-baseband: 0.19as.32.09.11_2

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.20.502.7

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) serialno: HT25XW301606

(bootloader) imei: 359691044520966

(bootloader) product: evita

(bootloader) platform: HBOOT-8960

(bootloader) modelid: PJ8310000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 4053mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 1a7fdca3

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

So my question is... is it true that my phone is just as-is and can never get S-OFF again? If I really cannot do S-OFF again, then I guess it's my own fault for not preparing enough, but just really wish i can still flash custom rom. So if there is still a way, i would like to give it a try.

Another question is, if I cannot do S-OFF again, how do I avoid running into the problem of a possible ATT OTA and brick my phone with the superCID, cuz seems like I cannot change the CID back without S-OFF.

If this issue was discussed before, I apologize, It's just too many information and scenario on the web and it's just not possible to read though all millions of pages.

Thanks.