Database Info

S-OFF, LOCKED, Can't root

I've bought a phone which has S-OFF, ***LOCKED***, which I'm trying to root. I've seen many guides, read them but they are all from the point you have S-ON. I've tried manual ADB install of CWM but that fails, permission denied.
Any advice before I brick it ? The phone seems to be in a quasi state...not sure how I progress.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.401.8
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3963mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0

are you sure you are S-OFF? If so, you can try a pre-rooted rom.(Flash a recovery first)
http://forum.xda-developers.com/showthread.php?t=1183684

Have the same problem. It says ***Locked*** S-OFF. Don't know what to do. Before made RUU I have rooted my phone succesfully (one click root), but now can't do that in the same way. ;/

I wasn't sure if S-OFF was really off but everything I tried was failing. This was from a Win7 64 bit, I switch to Win7 32bit PC and SuperOneClick worked then!
I've got root, CWM recovery installed and all sorted so thank. Not sure why 64bit Windows 7 was causing a problem, nothing indicated it was but a 32 bit pc everything worked perfectly.

How you switch to windows 32bit?

Generally, when S-OFF, the only thing needed to be able to do just about anything - is to use a special PG88IMG.ZIP that includes latest reengineered bootloader and custom recovery.
I'm not sure if there is one in this forum, but it's easy to create.

Jack_R1 said:
Generally, when S-OFF, the only thing needed to be able to do just about anything - is to use a special PG88IMG.ZIP that includes latest reengineered bootloader and custom recovery.
I'm not sure if there is one in this forum, but it's easy to create.
Click to expand...
Click to collapse
Where could I get this? Or how it is called? Because I have no clue what I need to enter in google.

To begin with, search for PG88IMG.ZIP to understand, what it is and what it does.

You need to unlock the bootloader, the ***locked*** indicates its still locked. Use HTCDev or some other tool to unlock your bootloader. Not sure how S-off works for this phone, it might have just been re-locked, so try "fastboot oem unlock" i think is the command and it should unlock
Then you can flash a recovery image and then flash a zip file containing the su binary and app via recovery
Sent from my HTC One X using Tapatalk 2

Just flash a ROM from the INDEX
Do you have a custom recovery?
Swyped from my DesireS

stumpyz9 said:
You need to unlock the bootloader, the ***locked*** indicates its still locked. Use HTCDev or some other tool to unlock your bootloader. Not sure how S-off works for this phone, it might have just been re-locked, so try "fastboot oem unlock" i think is the command and it should unlock
Then you can flash a recovery image and then flash a zip file containing the su binary and app via recovery
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Please, do not give suggestions when you don't know how things work - see the bold part of your own post. You wouldn't want someone that doesn't know exactly how motor works to fix your car, would you?
If he has S-OFF, there is no need to unlock bootloader and void warranty. Moreover, having S-OFF is better and more powerful than having unlocked bootloader. All the info is in the stickies, and you should go read them too.

Jack_R1 said:
Please, do not give suggestions when you don't know how things work - see the bold part of your own post. You wouldn't want someone that doesn't know exactly how motor works to fix your car, would you?
If he has S-OFF, there is no need to unlock bootloader and void warranty. Moreover, having S-OFF is better and more powerful than having unlocked bootloader. All the info is in the stickies, and you should go read them too.
Click to expand...
Click to collapse
Dont talk to me like i dont know what im talking about. Ive rooted and messed with plenty of phones. I based my advice off of my experience. Just because i dont know all of the specifics of a particular device doesnt really matter, all of HTCs devices operate basically the same. So maybe you shouldnt be worried about me and more worried about helping this guy like everyone else is. Its not up to you to decide if he wants to take my advice or not, thats for him to decide.
Sent from my HTC One X using Tapatalk 2

stumpyz9 said:
Dont talk to me like i dont know what im talking about. Ive rooted and messed with plenty of phones. I based my advice off of my experience. Just because i dont know all of the specifics of a particular device doesnt really matter, all of HTCs devices operate basically the same. So maybe you shouldnt be worried about me and more worried about helping this guy like everyone else is. Its not up to you to decide if he wants to take my advice or not, thats for him to decide.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You basically wrote that you don't know what you're talking about, and by suggesting to unlock bootloader on S-OFF phone you made it obvious beyond any doubt. Indeed, all of HTC devices operate the same, all of HTC devices have bootloader security, all of them more or less since eMMC introduction block write access to /system in bootloader, all of them can be unblocked by turning S-OFF or unlocking the bootloader.
Unlocking the bootloader voids the warranty and prevents /boot from being flashed from recovery, subjecting the user to constant kernel flashing through FASTBOOT for any ROM he wants to flash, while S-OFF allows full and undisturbed recovery functionality. Thus, bootloader unlock is inferior solution that should be avoided if possible, and suggesting it for a phone that already has S-OFF is BAD/not smart/pick whatever negative adjective you want.
Of course, all that is written in stickies, as I said, but I guess that you can't be bothered reading before writing, and when suggested to do so, prefer going all defensive. Yes, you don't know what you're talking about. I'm glad you rooted zillion devices, if you think it makes you know everything - read the info above again.
I already did my part to help the guy, and I don't have enough time for people that want everything laid out for them. If he's willing to use some Google and read - he'll get to his solution using my pointer, or somebody will point him to the relevant guide (and there is one in INDEX thread, AFAIK). The old debate of giving someone a fish vs teaching him fishing. I picked my side a long time ago.

Guys, don't be angry at each other
Thank you, you both helped me a lot. Big thanks )
Rooted my phone. If it's interesting I can tell how

NX3 said:
I've bought a phone which has S-OFF, ***LOCKED***, which I'm trying to root. I've seen many guides, read them but they are all from the point you have S-ON. I've tried manual ADB install of CWM but that fails, permission denied.
Any advice before I brick it ? The phone seems to be in a quasi state...not sure how I progress.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.401.8
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3963mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Lucky!
Looks like you're S-OFF'd and have SuperCID, which means you should be able to install any rom you like.
If I'm guessing correctly you have ENG hboot 2.00?
Just ignore the ***Locked***, as you're S-OFF'd you should do anything. How did you try to flash cwm?
Fastboot flash recovery?

(bootloader) version-bootloader: 2.00.0002
(bootloader) cidnum: 11111111
(bootloader) security: off
Click to expand...
Click to collapse
It looks like a xtcclip s-off so you've got a permanent s-off regardless which hboot you use.

Hi guys, i have the same problem. I'm *****Locked***** but s-off, so i made this: http://forum.xda-developers.com/showthread.php?t=1525100 but as i'm s-offed i don't need the 2nd pass (i think).. so in 3rd pass when i make this, the cmd tells me that im not allowed to install the recovery. What's wrong?

Read the answer in your original thread

[Q] HTC One X (Evita) 3.18 RUU for S-ON

I have had this great phone for around 3-4 months now. In the second week of owning it, I already unlocked the bootloader and rooted my phone. It is not S-OFF, because I'm under the impression that you need to buy extra hardware.
What I want to know is if there is any way that I can flash 3.18 RUU on my AT&T branded (but I use T-Mobile) evita? If there is, can you provide me with a link?
Again, I'm already rooted and I'm bootloader unlocked. Thanks

You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita

Thanks, mate. I appreciate the fast answer. Naturally, I hate being left behind; and seeing that most of the new ROMs require S-Off for the 3.4 kernel, I decided it was time to upgrade. I'll give it a try, as I'm currently trying to flash a ROM because I mistakenly flashed one of ^. Now, it's stuck on the the HTC splash screen, and I guess it's just the first boot scenario. However, it has taken a curious amount of time.

Yeah it's pretty much gonna be essential from now on anyway so you might as well get it outta the way.
What ROM did you try to flash? Also, what firmware/hboot are you currently on?
Sent from my Evita

I tried flashing CarbonROM. It gave me that (Status 7) error so I figured it was the 3.4 kernel giving me problems. After that, I tried flashing a previous version of CarbonROM, and it'd just stay stuck in the splashscreen (This is the ROM that I was discussing in my previous post). Now I tried to flash RageXL, and it's bootlooping. So I'm figuring that I should just go to a stock ROM and get this procedure done, and THEN flash a custom ROM. #BadLuckw3r3w0lv33

Ok. Yep it's the fact that you haven't yet upgraded via the RUU that these ROMs won't boot. Try flashing something like MagioRom or ViperXL just to get the s-off procedure done.
Sent from my Evita

Hmph. I'm pretty sure I've downloaded the latest Google and HTC USB drivers. Still, when I enter "adb reboot bootloader", this pops up:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
I have enabled USB debugging on my HOXL. Perhaps, it's the HTC Sync Manager? I have no clue beyond that point. I even tried restarting my phone AND computer.
EDIT: Nevermind, I just manually rebooted to the bootloader and continued from there. I am now S-Off

:thumbup:
Sent from my Evita

Btw.... If I helped you, please press the thanks button.
Sent from my Evita

Help me please
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....

hirias said:
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
Click to expand...
Click to collapse
If you are already s-off, just install custom recovery, then flash a rooted ROM or SU to get root.
Sent from my HTC One XL using xda app-developers app

Will this RUU work if I have a locked bootloader and s-on?

Chudawg62 said:
Will this RUU work if I have a locked bootloader and s-on?
Click to expand...
Click to collapse
As I said earlier in the thread, SuperCID + s-on + jb RUU = brick.
Sent from my Evita

guys can you please help me here?
my phone is
*** LOCKED ***
EVITA PVT SHIP S_OFF RL
CID-11111111
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Junn 11 2012,14:36:28
i dont understand thiss phone that well so can you please tell me if its safe to install the stock jellybean RUU on my phone?

Yes you're s-off so you can run the RUU with minimal risk.
Sent from my Evita

3.17 or 3.18?
Hi,
First off, thanks everyone - this forum has provided me a wealth of information.
I'm wondering if I can run non-sense based roms (ex. Cyanogenmod 10.2 or 11) without downgrading the touchpanel firmware. Here are my phone specs:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT27XXXXXXXX
(bootloader) imei: 359691XXXXXXXXX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4050mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Currently running ViperXL Android 4.2.2, stock kernel. Had to upgrade to HBOOT 2.15 to get rid of the random reboots and signal drop.
Before I upgraded HBOOT from 2.14 to 2.15 I was pretty sure I was on 3.17. I'm not even sure how to check this again? Would the upgrade to hboot 2.15 put me on 3.18? Sorry for the n0ob questions, help would be appreciated.

Current aosp ROMs no longer require you to down the ts firmware, they haven't since about June. You're a bit confused about the terminology, you didn't just upgrade to the 2.15 hboot, you upgraded to the 2.15 firmware, so you're currently on the 2.15 firmware. The hboot is only one component of the firmware as a whole.
Long story short, yes you can flash non-sense ROMs.
Sent from my Evita.

timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
can i run this RUU if i'm on CM10.2 ? and it says it will delete ALL from my phone, do i need to flash a rom and gapps right after i did that or will it still boot on CM10.2 ?

The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.

timmaaa said:
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
Click to expand...
Click to collapse
it doesn't work, i'm getting the usb connection error (170) but the cmd adb devices works just fine and the rumrunner s-off procedure went fine too...maybe i'm missing something ?

[Q] HTC One S having issue with CM10.1

Hi all!
Im in a big pickle here and I cant get myself out at the moment.
First hand.. The info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.17.31501S.10_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3917mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
Now i've been running cyanogenmod 10 stable since I started rooting etc...
And it's been amazing, but now since there has been a release candidate for 10.1, I was looking into updating it.
I ran into an issue where my boot-loader was not accepted , therefor i would run into an error on Clockwork mod stopping me from flashing 10.1
The bad thing was that I erased my previous installation without backing up the stock and CM10.
So now i'm left with no system. Though I can get into Fastboot and ADB via recovery.I
For some reason if I try to flash CM10 (The rom and the boot file) the cyanogenmod logo will continue spinning.
I tried to fiddle around with my RUU afterwards because I currently have S-On. But i later learned that i need superCID.
^(Which i learned that you need your phone on to alter it to the 8 "1"s) Which i cant do because i have no system.
I might have already altered some files guessing that my boot-loader is named "dirty-d92cc658" and im afraid that I messed up something internally.
So anyways. Im here with my Ville S4 plugged in on fastboot not knowing what to do.
Any Help would be amazing , thank you

Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid

c19932 said:
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
Click to expand...
Click to collapse
Do I need to have superCID to flash RUU's ?

Mozziliac said:
Do I need to have superCID to flash RUU's ?
Click to expand...
Click to collapse
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930

tivofool said:
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
Click to expand...
Click to collapse
How can I superCID my phone if I cant boot into the rom?

I've never superCid, can't help you there.
Good news is you can get into bootloader still.
You could fastboot flash a boot.img and flash a rom in recovery.
Just need to mount usb storage in recovery to put the rom.zip on your phone.
Edit: reread that you tried that but rom didn't boot. Hopefully you waited 5-10 min for first load.
try wipedata/factory reset from CWM like 3 times then flashing?
Good luck to ya.
Edit 2: kind of wondering if you can run the Rogers RUU with that low of a bootloader (version-bootloader: 1.13.0000)
Maybe someone can chime in, because that would be nice not having to SuperCid.

Alright so I seemed to get it running on CM 10 by switching recoveries and flashing it's boot.
Then I was able to superCID the phone, which then lead my into S-off'ing it.
Then I was able to update the hboot firmware to 2.15
Cleared the cache and installed the new kernel and flashed cyanogenmod 10.1 rc
Everything went well after that. I did run into a laggy issue, which I then fixed by switching the CPU governor to ondemand instead of interactive.
Thanks for the post guys

[Q] Help with SuperCID/unlocked but unable to s-off

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.

1. All good, except that process doesn't give you s-off, that's an entirely different process.
2. All good.
3. All good.
4. Nowhere in the firmware instructions does it say you need to relock your bootloader so I'm not sure why you did that. You need to follow instructions exactly and not deviate from them. You actually need to have an unlocked bootloader, root, SuperCID, and s-off for the firmware to flash.
5. See above.
6. It says tampered because you still have root via Cleanrom, the tampered flag is normal. It says s-on because you never went through the s-off process.
7. All good.
8. The RUU wasn't needed at all.
9. Unlocked and tampered are completely normal for a phone with an unlocked bootloader and root.
10. That revone method isn't even for our phone (that's why it failed) so I don't know why you even tried that. Trying software/firmware/exploits for another device is a great way to brick your phone. Yes SuperCID + s-on + jb RUU = brick. If you get s-off and revert to s-on you can still get s-off again.
Conclusion:
You need to do a lot more research, it seems you're confused about what you're doing. It's very important to have a firm grasp on what you're doing when modifying your device because a lack of understanding leads to bricks, and leads to not being able to recover from situations you get yourself into. You never had s-off, but you absolutely can get s-off on your phone as long as you follow the right method, the Facepalm method (which is the only s-off method for this device).
Sent from my Evita

[Q] SIM Unlock Code Not Working

Hi, I got the SIM unlock code from my carrier for my HTC One S but it doesn't appear to work. It's also a lot shorter than the code I used on my Xperia Z1 (same carrier) but they say that it's supposed to be valid.
My HTC One S has the bootloader unlocked and CyanogenMod 10.2 installed on it. Could not having a locked bootloader and stock ROM be the reason the unlock code doesn't work?
Thanks!

polybius said:
Hi, I got the SIM unlock code from my carrier for my HTC One S but it doesn't appear to work. It's also a lot shorter than the code I used on my Xperia Z1 (same carrier) but they say that it's supposed to be valid.
My HTC One S has the bootloader unlocked and CyanogenMod 10.2 installed on it. Could not having a locked bootloader and stock ROM be the reason the unlock code doesn't work?
Thanks!
Click to expand...
Click to collapse
You probably need the non modified stock firmware installed.
BTW you can also unlock it for FREE

Well, I did get the code for free
Yeah, I've been trying to restore everything to stock to find out but I'm having problems with that also. Perhaps I'll try the link you posted to verify the code. Maybe it's slightly different. Thanks!

Well, the code is the same, guess it just won't unlock without being stock ROM or something and I can't get it back to stock

polybius said:
Well, the code is the same, guess it just won't unlock without being stock ROM or something and I can't get it back to stock
Click to expand...
Click to collapse
Why can't you get it back to stock?

Any of the guides I follow don't seem to work. I relock the bootloader but then I can't seem to apply the matching RUU for the phone. What looks like the matching one (hboot and radio) is a ZIP file (OTA_Ville_U_JB_45_S_TELUS_WWE_3.16.661.4_1.13.50.05.31_10.30.50.08L_release_307532nohrvy5j6i2o2i8i.zip) and I'm not sure how to apply it. The exe RUU versions don't work either because, I'm assuming, they don't match my hboot and radio. I feel like a pretty competent guy when it comes to rooting and imaging Android devices but this just isn't working for me Thanks for your help.

polybius said:
Any of the guides I follow don't seem to work. I relock the bootloader but then I can't seem to apply the matching RUU for the phone. What looks like the matching one (hboot and radio) is a ZIP file (OTA_Ville_U_JB_45_S_TELUS_WWE_3.16.661.4_1.13.50.05.31_10.30.50.08L_release_307532nohrvy5j6i2o2i8i.zip) and I'm not sure how to apply it. The exe RUU versions don't work either because, I'm assuming, they don't match my hboot and radio. I feel like a pretty competent guy when it comes to rooting and imaging Android devices but this just isn't working for me Thanks for your help.
Click to expand...
Click to collapse
May you type in commandline:
fastboot getvar all
and post all values except your imei here?

version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.13.50.05.31
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT26EW403840
imei: xxxxxxxxxxxxxxxxxx
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: TELUS001
battery-status: good
battery-voltage: 4146mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.068s

polybius said:
version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.13.50.05.31
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT26EW403840
imei: xxxxxxxxxxxxxxxxxx
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: TELUS001
battery-status: good
battery-voltage: 4146mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.068s
Click to expand...
Click to collapse
Flash Viper 2.2 as sense base stock rom.
Use rumrunner to gain S-OFF
Flash any RUU you like

Thanks! I'll give that a try. I read you need SuperCID for S-OFF, does rumrunner do that for you?

polybius said:
Thanks! I'll give that a try. I read you need SuperCID for S-OFF, does rumrunner do that for you?
Click to expand...
Click to collapse
Rumrunner will get you S-OFF. Then you can change the CID.

Perhaps you know, I'm getting this when I try to image that Viper ROM.
assert failed: getprop("ro.product.device") == "ville"
Click to expand...
Click to collapse

polybius said:
Perhaps you know, I'm getting this when I try to image that Viper ROM.
Click to expand...
Click to collapse
Try to first flash the included boot.img before flashing Viper 2.1.0
or try try Viper 3
You need any sense based rom to get S-OFF

Ok, so, I guess I missed the part of installing Viper where it says to have TWRP and not ClockworkMod recovery >_<
Got TWRP on there, was able to flash Viper 2.1 EASILY. And it unlocked like a charm. THANKS!! Didn't have to get S-OFF for the unlock. What ROM is the best for the One S in your humble opinion? Should I still get S-OFF?

polybius said:
Ok, so, I guess I missed the part of installing Viper where it says to have TWRP and not ClockworkMod recovery >_<
Got TWRP on there, was able to flash Viper 2.1 EASILY. And it unlocked like a charm. THANKS!! Didn't have to get S-OFF for the unlock. What ROM is the best for the One S in your humble opinion? Should I still get S-OFF?
Click to expand...
Click to collapse
S-OFF means you can flash any stock RUU e.g unbranded and flash any radio version e.g. 1.20 and the kernel (boot.img) get flashed with the rom via recovery and has not to be flashed by fastboot command.
I actually use Candy 5 v1.5.0 but I can't say what fits your needs best

Does Candy have decent battery life? What is your general experience with it? I really want to put Lollipop on this phone

Also, do you have a good tutorial to remove the red Dev warning on boot?

polybius said:
Also, do you have a good tutorial to remove the red Dev warning on boot?
Click to expand...
Click to collapse
Battery performance is very good for me with Candy 5. I use my phone mainy for messaging and making calls (Its a phone lol). I can't say how long last the battery when you play games or surf the web heavily. For me the battery easy lasts two days.
For getting rid of the red warning you can flash a modded HBoot which can be found HERE. Make sure you use the same version number that is actually installed on your phone but "modded"

LS.xD said:
Battery performance is very good for me with Candy 5. I use my phone mainy for messaging and making calls (Its a phone lol). I can't say how long last the battery when you play games or surf the web heavily. For me the battery easy lasts two days.
For getting rid of the red warning you can flash a modded HBoot which can be found HERE. Make sure you use the same version number that is actually installed on your phone but "modded"
Click to expand...
Click to collapse
Hmmm. I have 2.15 but I seem to be getting an error during the flash: FAILED (remote: 41 model id check fail)
Is that the variance in model that you mentioned earlier?

polybius said:
Hmmm. I have 2.15 but I seem to be getting an error during the flash: FAILED (remote: 41 model id check fail)
Is that the variance in model that you mentioned earlier?
Click to expand...
Click to collapse
Seems so And I don't know how to solve it for PJ4011000. May be you can ask or look in the thread if somebody has successfully done it for your model. You probably can edit the flashable file, but I you should NOT try it, if you not exactly know how.