yashsingh1/xdaforums huggingface dataset:
[HTC One S] light_n_roses:
is that true that the new update for the one S which is rolling those days is blocking this exploit??
[HTC One S] Deluxestar:
I had the OTA Update with the new Radio and had no problems to S-OFF my phone for me it worked
[HTC One S] dhigby:
Wow, this rumor is hard to squash. Read the post above yours for instructions.

Sent from my One S
[HTC One S] Sneakyghost:
According to the rumor i heard, the Exploit itself is not and will not be closed by HTC but the Partition 4, which holds the CID, has been flagged read-only or something like that. It cannot be written to anymore. So, if you guys have superCID, you can do the S-OFF, still, even after the OTA.

If you don't have SuperCID, do not do the OTA, change to SuperCID first.

Also, i was just thinking, the Brick Downgrade thread created by AbsolutelyGrim (changed his name now to mirGantrophy i think) contained instructions to write the Partition 4 in QDL mode. So, if all else fails i think we can still use Ubuntu and brick the device by killing partition 4 and then restore an edited version with SuperCID with that method.

Not sure that works but maybe someone wants to try? xD i won't because i lost already one Phone due to that guide and i won't risk another. I am not that rich.
[HTC One S] cicciocant:
If you get a OTA with supercid you will have a brick.
[HTC One S] Sneakyghost:
Correct only for the latest JellyBean OTA, and even there, at least one person i know got that particular OTA on SCID and the brick didn't happen.

Also, apparently if i read the above comments right, someone claims to have S-OFF'ed after the OTA without a problem. If that is not some bullcrap, the rumor might just be a rumor after all.

Plus, i just realized that mirGantrophy's guide to brick downgrade uses P4 to get into QDL Mode and since P4 cannot be overwritten anymore (apparently) that method is useless too. Maybe mirGanthrophy knows another way to get down to QDL mode.
[HTC One S] ryanshew:
I'm starting to think the issue is that people are overlooking the write protection initially after the JB update.

Has anyone not able to super cid tried a custom kernel with the write protection removed?

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] beaups:
It's not kernel write protection.
[HTC One S] mickey-r:
first sorry for my poor english ...

ok, this is my personal experience

- buy EU unbranded one s some month ago come with 1.78 rom (i don't remember hboot, radio version)

- unlock and su it with One_S_All-In-One_Kit

- play some time with MIUI

- relock it and install RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe

- unlock and su it with One_S_All-In-One_Kit

- play some time with this rom without change anything

- relock it and install again RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe

- update with OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50.05.28_10.27.50.08L_release_301852xf01hejl416oev96.zip

- unlock and su it with One_S_All-In-One_Kit

- work on OTA in order to build a custom rom with aroma installer to make custom install without bloatware

- install my custom rom and use it one month

- install viper rom 2.1.0 last week for try it (i can't clean install 2.2.0 like some other users, freeze, battery blink ... but no matter back to 2.1.0)

- then i saw it was possible to s-off after install supercid and i do it without really know what i do but it work

now, my one s is unlocked, supercid applied, s-off, hboot 2.15.0000, radio 1.11.50.05.28
[HTC One S] ryanshew:
This had been confirmed?

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] popolon59:
Worked fine for me! Thanks
[HTC One S] f10a:
Sorry if this has been covered already but my hboot is 2.15 running the latest unkown tmo jb rom and I am trying to figure out how to supercid and s-off my phone without breaking it, or having to wipe anything.

any additional tips appreciated! thanks!
[HTC One S] mod_terrik:
I'm on the same hboot as you with the same ROM. When I try and update the cid from T-MOB010 to 11111111 and rewrite the partition, it doesn't stick on reboot. I think they made the partition that needs to be modified read only with the last update. We might have to wait for a workaround.
[HTC One S] PutterPlace:
Did a lot of research before attempting S-OFF for my HOS and noticed that the JB update isn't recommended if S-OFF is desired, but not yet applied. Because of that, I stayed on ICS for a bit, and now I've got SuperCID and S-OFF. Now I'm just letting my device charge before I install the UnKnown JB ROM. Thanks a ton for everyone who's worked on this!!
[HTC One S] Beppemi:
Worked really fine for me. Now my One s is perfect!! thanks so much :good::good:
[HTC One S] f10a:
Did you already have jb installed?
[HTC One S] joemanbui:
Hello everyone. Sorry if this has been asked before but if our phone model shows PJ04011000, is it still okay to use the OneS PJ4010000-OneS.zip on the front page?
[HTC One S] Beppemi:
yes man!
[HTC One S] nihS:
hi i have a question do i have to relock the bootloader before doing this? and do i have to downgrade my girls phone from JB to ICS to make this work? Cuz i can find the CWS001 or anything else in this mmlc... thing :/ there are just some dots "......." in line 210 and i really need s-off otherwise my gf's phone wont have wifi no more and i cant fix it with s-on.

pls help me thx in advance

Gesendet von meinem GT-I9001 mit Tapatalk 2
[HTC One S] touch of jobo:
No, you don't have to be bootloader locked. You must be rooted.

No, you don't have to be on ICS. In fact the poster right above you just did this on JB.

It's not

line

210, but

byte offset

0x210 (or in my case 0x214) so that is 528 (or in my case 532) bytes from the top.
[HTC One S] d3ckart:
worked fine , thanks
[HTC One S] vacsed:
Will S-Off prevent install any further official HTC OTAs or does this have no effect on updating the HTC firmware (no black-listing happening)?
[HTC One S] rustykwak:
No it wont affect OTA's!
[HTC One S] leezer3:
Being a tad more precise, it's highly unlikely to effect OTAs, but may be technically detectable if HTC decided to write the appropriate code.

I personally don't see this as likely, but still. On the flip side, if you know what S-OFF is and want it, if they do ever decide to block OTAs to these devices, then members of the community will write a flashable version in double time!

Technical waffle:

The facepalm team have found a way to exploit the bootloader, and from there to write the appropriate S-OFF flags. If doing it the official way writes another 'flag' somewhere else (Look at the tampered message for an example), and this exploit doesn't, then HTC could detect this in pure code.

Further, they will probably have a database of devices officially S-OFF on their servers, from which they are able to void your warranty and probably block OTA updates if they so-wish :)
[HTC One S] vacsed:
I am in sort of dilemma now because I would like to install the 401.9 update (which for now, will make changing the CID impossible) but also S-Off my device for whenever I decide to use a custom ROM and flashing different radios.

If I install now 401.9 with my normal CID, I cannot SCID anymore and hence not S-Off my device anymore. Installing the 401.9 with SCID doesn't work because the installer doesn't allow it.

A possible solution would be SCID my phone now with the 401.8 firmware, go S-Off, change back to a normal CID and install 401.9 and be stuck forever with a normal CID but still being S-Off... or does flashing 401.9 with a the included bootloader revert my device automatically back to S-On?

Also, would a normal CID pose any problem with a S-Off device like limiting a few of the S-Off advantages?
[HTC One S] touch of jobo:
No. Actually I recommend that after you get S-Off, you change your CID back in fastboot, either to original or to HTC__001.

(Taking OTA's on SuperCID has not always been safe.)
[HTC One S] f10a:
What would happen if you do not superCID and do only s-off, assuming you are TMOUS?
[HTC One S] vacsed:
Thanks. So the question remains if the secure flag gets reset after flashing the OTA since the update comes with a new bootloader (or atleast it gets rewritten)? My understanding is that the secure setting is stored in the bootloader partition or this wrong?
[HTC One S] beaups:
Question has been answered. Secure flag resides elsewhere and s-off persists.
[HTC One S] ryanshew:
You need super cid in order to s-off.

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] boc11:
All was fine to this step

What is the problem?
[HTC One S] wendellc:
Hi I went thru all the steps but after rebooting to the bootloader my daughters phone is still s-on. I watched a video and there is a mention of the soffbin file being a certain size.

Please advise what to do next
[HTC One S] cuiltheory:
for some reason, I can not get the supercid. I have the newest OTA. It is possible to have s=off withoutthe supercid?. I do have bootloader unlocked.
[HTC One S] ryanshew:
Nope, looks like you took the ota which rendered this method useless for you.

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] rustykwak:
We have been expecting this from the info someone gave out a while back but was not verified! Perhaps you should post the questions on the superCid thread with a bit more info as to= at what point did you get too when the process failed, also what Hboot version did the latest OTA leave you with? That question is more for my benefit ;)
[HTC One S] Sneakyghost:
Since we seemingly have no solid proof yet for the theory that the latest OTA disables the superCID method, it would be quite valuable if you could get back to this thread or the superCID thread with a detailed description where the process failed for you.

Could you still write to p4? Did it reset the CID after a reboot? Did it not accept the modified p4 at all? What errors did you get and at what stage?

I'd be very happy to know that and certainly some others too.

Also, you could try to run the 3.16 RUU as that has the same hboot like the OTA. If that brings back the ability to obtain superCID that would be awesome.

Mobile Post
[HTC One S] rustykwak:
Delete sorry!
[HTC One S] cougzzz:
Thank you for s-off. Extremely easy process. :)
[HTC One S] invasion2:
S-Off'd last night, super easy. Thanks for your work guys. And for the guy who made the video! :)
[HTC One S] f10a:
So just to confirm.. I went from rooted with ics to the unknown jb rom. I never had installed an ota rom from tmous unless that is the same thing as the unknown rom.

Is it really impossible to super cid and s-off using this rom on hboot 2.15. I've read mixed results and want to attempt it if it does indeed work and won't brick my phone.
[HTC One S] Sneakyghost:
There's a yet unverified rumor that the latest OTA by the name of 401.9 locks partition 4 (mmcblk0p4) for writing, hence no superCID and hence no s-off.

The normal RUU that brings you hboot 2.15 does not do this. You can still s-off.

I'm currently very much waiting for people to confirm that the super CID does not work anymore after the OTA. I'm sure other people also wait for clarification.

In this sense I'd like to encourage people again to report back with a detailed description of their process if they encounter a fail on either CID or s-off. Well, if that happens on the OTA that is.

Mobile Post
[HTC One S] nashwing:
Phone has only been RUU'd with the latest TMOB JB RUU

Bootloader 2.15

Appears to write to p4:

dd if=/sdcard/mmcblk0p4mod of=/dev/block/mmcblk0p4
2+0 records in
2+0 records out
1024 bytes (1.0KB) copied, 0.049321 seconds, 20.3KB/s

but rebooting to bootloader and looking at CID shows T-MOB010 still

C:\Android\platform-tools>fastboot oem readcid
...
(bootloader) cid: T-MOB010
OKAY [ 0.016s]
finished. total time: 0.016s

Hopefully this is more descriptive...
[HTC One S] tylerjholmgren:
Same Here!

I believe this is the write protection introduced by htc for the jb update.(Done quote me)

Its just something I've heard from hours of research after bricking my phone. Also htc decided

it would be a good idea to not let you unlock if you have supercid from my understanding. HTC is a joke

now in my opinion. They care more about keeping you locked into their system with their bloatware then

they do about their customers happiness. I have loved my past htc phones for their durability and usability

but now after the experiences I've had with the one s I think HTC finally put the last nail in the coffin. There is

a reason its been hard for them to get parts its because they are a second tier manufacturer now and why is

that... BECAUSE they can't make their customers happy and they lose sales and lose money and continue

to get lower on the totem pole.

**That was my 2 cents I'm not frustrated with anybody in this forum or any of the dev's I love you guys your great...

but HTC come on now!
[HTC One S] beaups:
You need to downgrade firmware.
[HTC One S] Sneakyghost:
Thank you, it totally is. However, I'm unsure this applies to WWE devices and I'm not even sure this isn't an individual phone problem. I have followed your story over at Tecardo's riff thread and I pretty much got the impression that something is seriously wrong with your phone.

Why? Simply because other people were able to superCID on RUU 3.16.

Plus, yours wouldn't be the first of a series of stories regarding various unexplainable partition locks.

I much rather think that the Ville suffers from incredibly bugged NAND controller firmware (on chip, not flashed with ruu, contains e.g translation layers that enable the chip to be seen as block devices rather than flash devices). This bad NAND as one could call it has caused numerous random crap stories all over XDA and I'm my eyes that's the only possible explanation for the very random behavior of the different Ville samples.

I'm not an electronics guy by trade so this is an uneducated guess, but it does make a lot of sense to me.

I'm happily taking corrections if anyone knows better.

Mobile Post
[HTC One S] bombina:
How can we downgrade firmware when we have no SuperCID and are S-ON. The OTA basically bricked my phone and through a lot of trial and error, like Nashwing, I was able to finally get a working phone at the loss of SuperCID/S-ON. I can almost say that this whole brick issue happened as soon as I flashed the firmware.zip from the 1.7.1A TMOUS JB Rom thread. Right now my phone is working, but the reception/signal is messed up. Random dropouts, and data is very unstable/dies often. What a mess! Never thought an update could screw up a phone so much. Unfortunately, I don't have much knowledge to troubleshoot much, I will leave that to the very intelligent experts in this thread who may have a solution in the future for the increasing number of users facing this problem.
[HTC One S] nashwing:
I totally agree. There is something else behind the scenes here causing the issues.

*** Just for note, my new phone I received yesterday has the 3.16 JB already installed (shipped to me this way). I cannot superCID that either. Same results.

---------- Post added at 11:41 AM ---------- Previous post was at 11:39 AM ----------

Let me ask this however, is there any real good reason for S-OFF on the HOS? We don't have an engr hboot, so I don't see a good reason to S-OFF other than the ability to downgrade the hboot.

I wonder if the old method of downgrading the hboot might work, and allow SCID...

http://xdaforums.com/showthread.php?t=1990043

I'm not willing to mess this new one up now. It works. :)
[HTC One S] ryanshew:
I wouldn't attempt the old downgrade method. I've only heard of bricks since hboot 2.15 with that method.

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black-Blue_Sense_Theme | Bulletproof_1.3
[HTC One S] Sneakyghost:
Not sure either. It killed my phone too, not instantly, but the hboot I wrote while in qhusb mode wasn't solid, some corruption must have occurred while writing it. There was graphical corruption in that boatloader and it died two weeks later. Before that, reboots got harder, wouldn't wake up more and more often.

I'm rather sure that method is a total emergency procedure and shouldn't be used if not really really necessary (like getting the phone out of an already existing brick situation).

Mobile Post
[HTC One S] wendellc:
I was able to get super cid. But can't get the s- off to work.
[HTC One S] cuiltheory:
I can write to p4. I did verify with Android commander, root explorer , but after reboot - all was gone. I did some searching and found out that /dev partition is RAM disk. Any change written to that partition are gone after reboot. Need to find a way to write to p4 and then go to flash the file from fastboot without rebooting.

---------- Post added at 10:16 AM ---------- Previous post was at 10:14 AM ----------

How did you got the supercid?. Are you on 2.15?
[HTC One S] kirkcody:
Hi, will the new s-off method for the HTC One help us JB update T-mo users at all :crying::confused:
[HTC One S] donb123:
Just so you'll know, I didn't SuperCID and I am still S-ON and I too installed Unknown's ROM and didn't brrick my device nor did flashing the firmware harm my phone in any way.
[HTC One S] wendellc:
HBoot is 1.14
[HTC One S] cuiltheory:
Well, with 2.15, we can not do the supercid - that is given. Need to find some other way to get the s=off. If I flash the PJ without the supercid, will I brick the phone?. I did try the revone from htc one but did not worked for me.
[HTC One S] bombina:
If you never SuperCID/S-OFF, then you won't run into the problem I or anyone else that had it. The bricks/bootloops happen when you are specifically S-OFF (not the SuperCID, I think), so that's why you never had any problem. After a lot of re-flashing, etc...the phone is currently working, but the data is very unstable/doesn't work most of the time, and the signal dies spradically too. I tried to rectify the issue by flashing the Temporary Installer (because flashing a new radio with 2.15 is not possible in any other way). It didn't solve the issues I was facing, so I think my last line of solution would be to contact T-Mobile and get a new phone sent.
[HTC One S] ATSPerson:
Apologies in advance might be tl;dr for some.

I think I am in the same boat as many here but in a different way. I was S-Off from very early on and happily flashing roms ever since. But last night I foolishly ran the WWE 3.16 RUU. (Most definitely not a TMous RUU), assuming that I'd keep S-Off.

But after running the RUU and rebooting: nothing. I could get to the bootloader but Sense wouldn't fire up. It said "Storage Being Prepared" (or similar) I flashed and reflashed with the same result. so I unlocked the bootloader, rooted and reinstalled TWRP so I could run my Nandroid. Same thing happened. So after dome intensive reading, I realised I had to S-on. After resetting the secure-flags I ran the RUU again and everything was fine. Sense fired up as it should.

So I rooted, installed twrp and S-Offed again. Sense stopped working as I did before. I ran my Nandroid again with the same result - no joy.

I repeated the whole process a could of times doing things in a different order but always with the same result.

But going through the S-Off process was successful in each case. I could successfully change to SuperCid, push the modified file and run the soffbin. It just did something to corrupt the partitions or some such.

So now I am S-On. I've rooted and am running Droyds new Carbon Halo while is fine, but as you say, data is patchy.

I'd rather get back to S-Off but can live without it, but I'd rather the data was more consistent.

Any ideas?
[HTC One S] bombina:
You are in the same position that everyone that previously had S-OFF did after getting the phone back in working order -- unstable/not working data and unstable signals. The only way is to get it JTAGed or get a new phone sent through T-Mobile. Those are the only two choices left, unless someone pulls a miracle and revives this S-OFF method to be compatible for us.
[HTC One S] ryanshew:
Actually, in this case it could just be the ROM he is on, since it was a known issue with that one.

Maybe, maybe not, but I would confirm that before doing anything drastic.

HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4

Inverted Sense _4+_and_5_click me
[HTC One S] bombina:
I had the same problem on the RUU and also the 1.7.1 ROM as well. It it something more deeper than the ROM. Flashing Temporary Installer did nothing to fix the issue as well. He is free to flash any ROM he wishes, but the problem will remain, I wish that wasn't true ofcourse!
[HTC One S] ATSPerson:
But I originally S-Offed from the OTA that originally brought us (at least in Europe) JB on Christmas Eve. As far as I know there has been no other OTA, but then I've been on AOSP ROMs since anyway, so I could be wrong. If I ran an ICS RUU and forced the OTA update would I not get the phone back to the state it was in before I originally S-Offed?
[HTC One S] ATSPerson:
And the other difference is that I had no problem S-Offing again. I did it three times yesterday. I was able to SCid, and push the PJ4010000 & soffbin files.

I was S-Off but at the expense of a usable ROM...
[HTC One S] consuela:
JB firmware necessary?

used this method to get s-off a while ago and it worked like a charm, so thanks to everyone who brought us this method! (:

im currently running illiusions beta rom for the one s4 with twisteds gen2 vi kernel without any problems whatsoever.

was thinking about switching to droyds new carbon rom... his post mentioned we should use one of the JB RUU's to get the newest firmware so that we could run the newer 3.40 kernels... (currently 3.08 i think)

could anybody explain why or if its really a requirement? would really appreciate it ;)

p.s. - current hboot infos in attachment
[HTC One S] ATSPerson:
That was the reason for my current predicament - running the 3.16 RUU has rendered my HOS S-Offless with a dodgy radio.

Seek advice.

Probably not from Droyd as he is AFAIK not S-off - Intervigil might be a better option if you can corner him
[HTC One S] bombina:
This issue applies to the T-Mobile USA OTA, which broke the S-OFF/SuperCID. I am not sure if EU users are affected or not, so please take caution!
[HTC One S] ATSPerson:
Exactly my point, I think my case is different to others here
[HTC One S] bombina:
Yea, T-Mobile took forever to release the JB update for USA (extremely delayed), and then surprised us with this nonsense. Unbelievable.
[HTC One S] forgiven90:
I'm wanting to do this exact thing and just read that it's possible if we upgrade our hboot to 2.15 first. I'm curious which hboot you tried this with? I DON'T want to lose s-off!
[HTC One S] ATSPerson:
Was 2.15... but to be honest I didn't lose S-Off, I just lost the ability to run any ROM. If push came to shove I'd rather lose S-Off.

But it's all academic now. I have completely bricked the phone by trying to S-On with 1.06 hboot. It won't even start, don't even think Jtagging it will help. Ouch.
[HTC One S] usaff22:
JTAG with full reflash of the whole system and partitions should work... Don't know if we have the msm8960 hex and img files though

First you should try the unbricking thread from a long time ago... Whatever you do don't use the unlimited.io tool. That renders the unbricking method useless.
[HTC One S] ATSPerson:
First thing I did was PM Tecardo. He's looking into it now. Forgive me if I'm wrong, this is uncharted water for me, but I think Unlimited.io tool (I assume you mean the QHSUSB_DLOAD fix), is useless for me as I don't even get there. Just nothing. To say I'm not hopeful just about sums it up :( I need to dig out one of my old Nokias.