yashsingh1/xdaforums huggingface dataset:
[HTC One S] havikx:
hey guys...i'm almost done but ran into a snag in litterally the last line. when i went to su -c "/data/local/tmp/soffbin3" i get a syntax error. i'm adb on a macbook if that helps. i'm not sure what i did wrong and i did try to reboot to see if it took and i'm still s-on. i was about to chmod command and it went thru...just get a syntax error when -c.

i'm kinda lost to be honest...i can adb and fastboot a little but i'm not sure what a syntax error is.

edit: i redownloaded the soffbin3 file and it worked. but i'm still s-on. hboot 1.06. s4. tmobile. running cm10.
[HTC One S] renn9420:
I didn't either. But I locked my boot loader with original unlock_code.bin then unlocked it with the new token after I supercid, no screen popped up, but said unlock successful then did rest of steps and s-off'd

Phone HTC G1 - G2 - One S *Rooted*

ROM: Dark Jelly One S

---------- Post added at 09:19 PM ---------- Previous post was at 09:14 PM ----------

I relocked my bootloader with my original unlock_code.bin then used my new unlock token after I super cid to unlock bootloader. Need to mention that neither showed the screen. Just got message saying unlock successful

Phone HTC G1 - G2 - One S *Rooted*

ROM: Dark Jelly One S
[HTC One S] alphaeagle777:
Any advice before i take my phone to tmo tomorrow, is relock
[HTC One S] havikx:
did we fix the 99 errors problem with this? i tried to flash viper2 rom but it still gave me the 99 errors.
[HTC One S] sponkemonke:
Confirmed Working!

One S T-Mobile with AOKP 4.2.2.

Quick question, if I choose to flash a stock RUU, will I need to revert back to TMOB010 as my CID? I remember the Sense JB update bricked SuperCID devices.
[HTC One S] Drashna:
I had that issue too (the 99 error). Rebooting the machine... and letting the phone sit most of the day, and when I came back to it later, it worked 100% fine.
[HTC One S] vido4eva:
thank you

thank you sir for the info and to the other guys involved with the whole process. im now s-off and i did all of this while still on venom:laugh:
[HTC One S] Snotmann:
I got the 99er problem too.

Have changed the CID to 11111111 and tried it again and it works fine for me. Even with stoneold htc drivers and so on.

I was on Trickdroid, and be on it further without problems ... i dont think that the rom have something to do with the bootloader ... :confused:

Question for me is: What can i do now with my S-OFF device :cowboy:
[HTC One S] havikx:
ok... i've really tried everything to do this. i'm stuck with a "segmentation error". i went thru the process of relocking my bootloader and reunlocking it just to make sure i tried everything. i still get a segmentation error. i flashed multiple roms to get rid of the 99error problem.

i'm 1.06 hboot. superCID. unlocked. and i'm stuck.
[HTC One S] Darknites:
Try it on Viper2 rom.

Is it me but are people locking the bootloader for no reason?
[HTC One S] havikx:
i was on viper. i was get 99error problem. flashed around. fixed that. then segmentation error which is a su binary error apparently. stock jb binarys fix that. now s-off.
[HTC One S] fusk:
Is the s-off permanent?
[HTC One S] wanxu:
Thanks! working like a charm!
[HTC One S] Jewcifer:
As long as you don't run any RUU's, but even if you do you can reapply the s-off method easily.
[HTC One S] cbgti:
It dosen't work for me... :crying:

I'have a HTC One S (S4).

My HBoot is 1.140002.

I'm SuperCID: 11111111

My Rom is the ViperOneS v1.2.1

I'm Rooted.

I tryed it 3 times but with no result... I'm still S-ON.

It was the same thing after reboot my computer and HTC...

This is my Log (of the 2nd Fail) if someone can help me... ;)
[HTC One S] beyored:
i would remove your serial number from log......
[HTC One S] Snotmann:
The problem is further above "FAILED (remote: 99 unknown fail)"

With that error you can discontinue the process ...

Are you sure you have SuperCID ? New HTC Drivers on pc ? and so on and so on ...
[HTC One S] beyored:
it wouldnt work with viper 1.2.1 when i tried it......then i changed it to viper 2..0 and it worked flawlessly....hope this helps....
[HTC One S] fusk:
By "ruu" you mean roms in general?

By "any" you mean any rom at all or some goes and some doesn't ?

As i understand it, it's for stock roms only, however the s-off allows you to flash custome hboot.
[HTC One S] scotty1223:
correct. flash any ruu you want,radio s off is permanent

see above ;)

nothing wrong with flashing ruus now.

---------- Post added at 12:42 PM ---------- Previous post was at 12:40 PM ----------

add another successful s-off from viper 2.0.0 ( http://xdaforums.com/showthread.php?t=2105863 )

i tried everything but stand on my head yesterday,and after reading several statements like above,flashed it this morning,and voila- worked fine. :cool:
[HTC One S] cbgti:
I'm SuperCID, yes...

When I go into fastboot and I type "fastboot getvar cid" in the command prompt, I have this CID in return "11111111".
[HTC One S] beyored:
yeah thats super cid....
[HTC One S] sander151187:
Can you change your CID back to original after your device is S-OFF? Had some trouble with CID 1111111 before, so I would like to change it back to HTC_001
[HTC One S] beyored:
yeah im sure u can.....
[HTC One S] Phantom Pt. II:
When I do get the supercid and use this method to get s-off, is there any wipes happening during it all? Do I need to set up and restore all my settings and apps, or will all be the same afterwards?

Sent using herpdiderp
[HTC One S] KACE321:
hmmm, with S-OFF maybe developers could possibly get the Sense Image Chip to work on ASOP ROMs?, making this phone complete :)
[HTC One S] flex420:
this would be awesome, but i doubt s-off has anything to do with this.
[HTC One S] fusk:
I thought everything worked.
[HTC One S] rootrider:
Did that yesterday, no wipes happened. Everything was there.
[HTC One S] frickinjerms:
so this 99 unknown fail has to be my issue also buuut i goofed differently than all these others..

my initial flash of the pj zip was successful with the 92 flush img thing but i typo'd fastboot reboot oem and so it took a good 7 seconds to get the command right (whoops!) and my screen like "reset" itself in this time...

but i got it finally and once the phone booted into android i figured i had to try again so i smiply rebooted into the bootloader, did the rebootRUU, then the flash zip... and alas the status 99..

i didn't think anything of it so i did the adb push soffbin3 / chmod / su -c | and no errors there but also no s-off

and since then i continuously get a "status 99: unknown fail" error after several reboots then flashing that zip again, i am officially stumped..

should i relock and run an ruu or maybe restore my nandroid of cm10 or reflash the rom cuz it seems as if it would've worked if i didn't initially screw up and reboot early? im gonna try the rom reflash while i await a response :P

running blackout sense 1.5 (as a "dummy" rom) / duh im supercid / hboot 1.06.0000 (yesss im unlocked and rooted)

rom reflash was a no go

by the way, fastboot oem lock doesn't relock my bootloader anymore...
[HTC One S] scotty1223:
Sure,with s off its easy. Just use the following fastboot command:

Fastboot oem writecid xxxxxxxx

Fastboot reboot-bootloader
[HTC One S] odl:
I did both (supercid and s-off) today on PACman 4.1.2 ROM and it was messed up after reboot with s-off (some settings stayed, some were wiped - launcher, superSU). restoring nandroid backup fixed everything. so.. just create backup before starting ;)
[HTC One S] Orical:
I have to admit I thought this was going to be one of those very few devices that S-Off wasn't going to be blessed with but I'm glad to say I'm wrong in the assumption.

Great work guys you definitely deserve the bounty for figuring this one out.

Thanks.
[HTC One S] blackwing182:
What are you talking about?
[HTC One S] flex420:
now, that we have S-OFF, will it be possible to have dual boot on the device, like the HD2 lives forever? :D
[HTC One S] Darknites:
Ya I would love to see that.
[HTC One S] alphaeagle777:
getting a replacement phone, tomorrow

on the other note wile waiting for tmo support to answer i over hear that there is an update coming soon for my phone (one s)
[HTC One S] bithunter_99:
thx @devs. you are the best!
[HTC One S] nickmv:
Thanks!
[HTC One S] d@rklink:
I was finally able to get S-Off!!!

After seeing someone else was successful by reinstalling a custom ROM and then trying the same steps, I did the same. Installed Viper OneS 2.0 and this worked like a charm. Thanks so much devs!
[HTC One S] hasoon2000:
To people who got S-off. What was your One S model number and what ROM did you use?
[HTC One S] bithunter_99:
i'm using cm10.1

hboot 2.15
[HTC One S] rootrider:
HT23F (Taiwan, 2012, March, 15th)

Used a nandroid of 3.16 JB OTA update which I rooted to get as close as possible to the original. Any other rom incl. Viper did not work or only partially.

Bootloader was downgraded to 1.06 already before.
[HTC One S] d@rklink:
I had the same issue. Relocking the phone doesnt work after superCID (at least that's what I'm assuming as I had no issues relocking the bootloader prior to superCID). As for the "error 99", rather than rebooting the device, try shutting down completely and then trying again. Each time I got the error 99 message I had to shut down in order to get the error 92 message. Definitely keep trying. I had to be persistent and it was getting annoying, but I finally got S-Off this morning.
[HTC One S] blackwing182:
My original T Mobile ModelID PJ40110

fcc id : NM8PJ40110

IC:4115B-PJ40110

My Hboot,Cid

And this is the zip in the op

OneS PJ4010000-OneS.zip

Is not even for PJ40110 and it worked fine. Fotos are the proff

And i used cm10.1 to make the s-off
[HTC One S] el7145:
I installed Viper Rom as other have suggested after i received a "segmentation fault error"...i dont get this anymore on step 8, but i do get another error...

when i got to enter in the commands on step 8, i get a "device not found" bc my phone reboots automatically

EDIT: ok so i finally figured it out...the above problem, i simply wasnt waiting long enough for it too boot (ya im kinda slow)...after going through the process again i was getting a "remote: 99 unknown fail" error when flashing the zip. So I rebooted into recovery, and wiped cache, and dalvik (that probably didnt do anything), ran through the steps again and achieved s-off

I had been on tmobile running trickdroid ICS, i updated to viper 2.0

i have 1.14.0004 hboot and my modelid=PJ4011000
[HTC One S] Jewcifer:
RUU stands for Rom Update Utility. They're the official HTC/Carrier ROMs that bring your device to an updated stock state.

ROMs are completely different. As long as you're in recovery mode, you can flash anything you want to flash.

As for custom HBOOT, there isn't one out for these phones...yet ;)
[HTC One S] blackwing182:
If god give us a enghboot i would be happy
[HTC One S] manikcs:
Welcome almost stock oneS :)

Sorry for bad quality.
[HTC One S] usrbrv8:
Flashed ViperOneS 2.0.0 fixed segmentation fault

I was getting the same segmentation fault and Error 99. I then flashed ViperOneS 2.0.0 and I then had the correct model number, the 92 error, and no segmentation fault issues. It does seem that the ROM you have installed can alter your device id. I had TrickDroid Tmobile US and my device id did not match the PJ4010000 from the instructions. But flashing ViperOneS corrected that and allowed me to complete the S-Off process.
[HTC One S] fusk:
Thanks for the ruu clarification, i just thought ruu was some slang for rom.

So in layman terms

ruu = stock htc brewed android

rom = custom rom

How would it be misleading when it's questions?

Your answer would be more misleading if it contained an error, it wouldn't really matter how wrong i am.

I know custom hboot ain't available yet, but s-off allows it, that was the point, not the availability of custom hboots. ;)
[HTC One S] danirebollo:
i got PJ40110, and im trying with windows 8 x64 without success... :( you have PJ40110 and it works?
[HTC One S] blackwing182:
Look at the pics
[HTC One S] Arijum:
Hi,

is it possible to flash lower HBOOT with S-OFF? Thanks in advance
[HTC One S] blackwing182:
NO
[HTC One S] Jewcifer:
I dunno if will be getting that, but surely someone will patch us an extended HBOOT sometime in the near future :D

Hahaha, awkward, that text somehow got caught on my clipboard when copy/pasting, it wasn't directed towards you x.x I fixed my post.
[HTC One S] blackwing182:
[/COLOR]

I think thats no posible
[HTC One S] bstylz911:
if i am not wrong,

s-off means we can flash any rom without having to flash boot.img if we are on hboot 1.14 correct?

is that the only reason why we have s-off?
[HTC One S] jaedolla:
My One S is finally S-OFF! thanks for this great tuturial.
[HTC One S] slainbybeats:
Yay, finally! Thanks again to everybody who was involved, I'm veery happy :D S-OFF just rocks... :P
[HTC One S] ponchofiesta:
Is it possible to revert to S-ON?
[HTC One S] ReichMann:
confirm succed:

hboot 2.15

ville s4

viperS 2.0.0

bravo,now finally we own our devices 100%.
[HTC One S] ram100987:
s-off achieved!

hboot 1.04

t-mo one s

aokp 4.2.2
[HTC One S] frickinjerms:
nailed it! i turned off my phone and went to sleep cuz i work all nite :P just woke up and all my commands were still in cmd so i powered up and plugged in and up arrowed found my most recent rebootRUU command and just hit arrow down / enter / arrow down / enter etc etc and got my 92 flush image again and completely error free in this go :D

now behold!

plus my cyanogenmod nandroid restored without a hitch :D i did notice that my cid now shows up in the bootloader now as before it didn't but hey more bragging rights :D
[HTC One S] alphaeagle777:
actualy on the processe to try to fix my phone from an internal error i manage to lower the hboot

BUT THERE is NO need to Lower the hboot
[HTC One S] blackwing182:
did you read man, he asked to flash a lower Hboot , not to flash a boot.img
[HTC One S] kingskidd268:
I had that same problem I had to flash viper. its a 4.1.1 rom i was on 4.2.1 now i am off.
[HTC One S] frickinjerms:
so my next question of morbid curiosity, if we dd our hboot, which is on mmcblk0p12 if im not mistaken, can't we open it up in hxd and change the unlock text and the red letters of death to whatever we want, save it, then dd it back into our devices wothout the fear of turning it into a paperweight now?
[HTC One S] real187:
nice, im s-off also.

on cm 10.1

hboot 2.15 eu device

quickly changed my cid back to its original with a simple fastboot command thanks to s-off
[HTC One S] Jewcifer:
fastboot oem writesecureflag 3

For future reference, only use with stock HBOOTs
[HTC One S] Behold_this:
Yes, but be very careful
[HTC One S] abracadabra11:
Worked like a charm - GREAT work.

CM v10.0

Hboot V1.09
[HTC One S] Darknites:
Didn't know there was a 1.04 Hboot.
[HTC One S] makomek:
My S-on with H-boot 1.06 is the same as S-off ,I never needed to flash kernel or anything so why all you guys in here act like you just won $5000 or you just got a iPad for your B-day after getting S-off.
[HTC One S] frickinjerms:
bahahahaha it worked :D

*** PAMPERED ***

S THE F**K OFF!!
[HTC One S] ipit:
haha yeah me too, that's why I never saw the need for it BUT I did it anywayz. Don't want to miss out on all the action.!!

Although one good thing I have noticed so far, when I perform an update via goomanager, it actually goes through, installs, wipes and reboots, whereas before it would simply take me to recovery where I had to do it manually. Not sure if it's a coincidence but it has been working since S-Off
[HTC One S] magicninja:
Here's a crazy question...what exactly is s-off?
[HTC One S] Darknites:
Full control of the phone.
[HTC One S] magicninja:
Hmm....I need more info is there anything on here where I can learn more

Sent from my HTC One S ViperOneS
[HTC One S] Darknites:
Big thread in General.
[HTC One S] magicninja:
Yeah....really didn't help much but thanks

Googled it....think I might have to wait till there's an easier way to get it
[HTC One S] Jewcifer:
Unlocking the bootloader lets you flash ROMs and recoveries, but that's it. S-off let's you do absolutely anything you want to it. Kernels, radios, full misc.img control, anything. You can also reset the Locked/Un-locked and *TAMPERED* status of the bootloader, even replace the bootloader entirely.

Next time, try searching beforehand, and don't get so disappointed when you don't get an answer to a simple question.

This is as easy as it gets. There's a reason it's called "Facepalm". I've S-OFF'd several droids and this by far has been the easiest. If these instructions are that difficult, S-OFF probably isn't for you.
[HTC One S] Darknites:
Ya that's about as much as I know lol and there is isn't going to be easier way then this.
[HTC One S] LibertyMonger:
S-OFF!

ABSOLUTELY AMAZING! WE GOT S-OFF! Thanks a bunch this is unbelievable I thought we thought it would never happened! I just successfully got S-OFF! Very easy to thanks a bunch this is exciting!
[HTC One S] Ashaman_Kupo:
I never have success with adb. I'm a zip kind of guy, lol.
[HTC One S] droidkevlar:
if you have fastboot on, disable it, reboot 2 times and try again. was reading on irc this might cause problems. i got the same error you did. you will get some error after doing it. i believe they mention it in the guide. also, if you are still having issues, go to the irc channel. they are very helpful...but i believe jcase and team might be sleeping but doesnt hurt to try and ping it in the channel. i would just put it on pastebin or direct link to ur post so they can see the output

EDIT: Looks like you missed step 7

7.) Immediately issue the following command:

Code:

fastboot oem boot
[HTC One S] Ashaman_Kupo:
or at least a video guide.
[HTC One S] renn9420:
Im on hboot 1.14.0004 and keep getting failed (remote: 99 unknown fail) and get passed this!
[HTC One S] Jewcifer:
No, I got that one in both times, maybe you just read over it. My phone wouldn't have booted if I had missed it and adb push would have failed.

I also just realized that I have no idea how to disable Fast Boot on Cyanogen. My Sense ROM only has about 5 minutes left though so I'll just wait a bit longer.

This is exactly what happened to me. Are you on an AOSP ROM? I'm flashing a sense one right now to see if that resolves the problem. If not, we'll probably have to perform a relock>RUU>unlock>root

Edit: Anyone plan on making a video tutorial? I don't mind using my own run to do it.
[HTC One S] DylanTheVillian:
easy as pie! s-off in 5 minutes :)
[HTC One S] LibertyMonger:
If you have android sdk setup with adb then all you have to do is hold shift+right click on the android folder where adb is installed and click on "open command window here" then if you can enter the command adb reboot bootloader (you can copy and paste it) if it reboots your phone into bootloader then you know you can run adb, if this helps you any. After testing your adb then everything else is a cake walk! Just make sure you unzip the files provided into the folder where adb is installed.
[HTC One S] hilokilo:
My phone gets stuck in HTC's "Quietly Brilliant" logo right at step 7. I did everything else but I can't continue because of this. Any tips?

Do I need to install SuperCID 2 just to get this working?

I'm running Viper Rom and unlocked the bootloader using jcase's method. Also, I'm on Cubed Kernel. Any help would be appreciated.
[HTC One S] blackfireshocker:
It figures...

This would surface now that I'm moving on to the Nexus 4 and just finished restoring mine to stock for selling...
[HTC One S] LibertyMonger:
I made a stupid mistake at first, luckily I didn't need it til the end but I missed the part where we extract soffbin3.zip into working folder. I got to antsy lol. Anyway do read over info first before rushing through like I did.
[HTC One S] droidkevlar:
I have hboot 1.14 and running CM10.1 and had no issues. I also had the same error as you. Are you running a custom kernel? I also rem them mention something about that. Good luck

---------- Post added at 10:13 PM ---------- Previous post was at 10:11 PM ----------

You dont install SuperCID 2, you must have SuperCID. Steps on how to get SCID are on the first post for our phone. Takes 2mins to do. SCID should be 11111111 If you dont have that, that is your problem.
[HTC One S] hilokilo:
You dont install SuperCID 2, you must have SuperCID. Steps on how to get SCID are on the first post for our phone. Takes 2mins to do. SCID should be 11111111 If you dont have that, that is your problem.[/QUOTE]

Oh yeah, I already did that (22222222222). That explains how I have the Viper Rom installed on this. Any other tips? Thanks for the quick response by the way. (ugh, I broke the quote box)
[HTC One S] real187:
for testing just now flashed the 2.31 EU RUU. (was on hboot 2.15)

so my hboot changed back (normal behavior of a s-off device) to 1.14

props to the guys who made the s-off possible
[HTC One S] Jewcifer:
S-Off isn't just free reign over the boot.img. If you had read anything about it before making your post you'd know this.

Also, I don't know about you, but I'd be pretty let down if I got an iPad for my birthday. Apple sucks, that's why I'm here on XDA working with Androids.
[HTC One S] Darknites:
Its not the same but thanks for playing and I guess you forgot there is whole bunch of other Hboots that don't flash the boot.img in recovery.
[HTC One S] xxquicksh0txx:
I would rather get an ipad for my birthday than an android tablet. Why? You could sell it and buy 2 android tablets :p
[HTC One S] Jewcifer:
I have been bested in the game of logic. I tip my hat to you, sir.
[HTC One S] blackwing182:
then why are you here? just go away and leave this thread clean of nonsense stupid coments.
[HTC One S] sherry478:
How did you edit the hboot? (Which program did you use)
[HTC One S] CarstenDutch:
Made my DAY! lol
[HTC One S] frickinjerms:
to modify your hboot!

i used hxd hex editor and then did this to extract it and push it back:D

typed in these commands

adb shell
su
dd if=dev/block/mmcblk0p12 of=/sdcard/hboot.img
exit
exit

that will turn your hboot into an img file onto your internal storage

and then i moved into onto my computer and opened it up in hxd hex editor and searched for the strings then changed them around, making sure that it OVERWRITES the letters originally (don't hit delete EVER just start typing, the file size needs to be EXACTLY 1mb or 1,048,576 bytes) and also i wouldn't recommend going over the allotted space of letters.. then when i finished put the hboot img back onto my internal storage typed in these commands to get the modded hboot in place

adb shell
su
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p12
exit
exit
adb reboot bootloader

this is a very dangerous process soooo if it borks then i cant be held liable for the new brick

if you search around in the hboot file you can change the tampered / unlocked / htc disclaimer and possibly others i already got my disclaimer to go away by turning it into nothing but spaces :D
[HTC One S] forgiven90:
I was wondering about this zip difference, but decided to risk it. I also have a PJ40110 like blackwing.

S-off for me with :

Rom- Dark Jelly (build 10.1) (4.2.1)

Hboot- 1.1300
[HTC One S] leald:
I seem to only be able to get edge speeds for internet after doing this...has anyone else noticed something like this?
[HTC One S] magicninja:
Haha this thread is pretty ****ing funny....
[HTC One S] cat2115:
Hi how do I flash hboot and where can I download hboot? Any advantage by flashing a higher hboot since now is s-off? Thx
[HTC One S] topnomi:
I'm trying to get s-off and ran across an issue.

C:\Users\XXXXXX\Desktop\S-OFf>fastboot flash zip PJ4010000-OneS.zip
sending 'zip' (35551 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.019s

I'm hboot 1.06 (used downgrade)

originally a Cincinnati Bell phone, using on Tmobile. (front of phone says htc)

tried using official CM10.1 nightly

tried flashing viper 2.0.0, wouldn't boot (hangs on htc one screen for 20min+)

tried re-downloading viper, same issue

flashed CM10.0 stable and got the same error.

EDIT!!! I FIXED IT!!!

I was using a usb3 port on my computer. Don't use usb3 ports when fastbooting things. :)

I'm now S-OFF!!!!!