Database Info

[HELP] I bricked my DS!!

Hello,
This morning I was in the market ( My Apps) and i chose Update all option. Loads of apps started to download, and after few minutes my phone froze. So i removed the battery and since then I', stuck in the bootloader menu:
AlphaRev
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.14_M
eMMC-boot
Mar 10 2011, 14:58:38
I can't do factory reset or access recovery. At some point I have successfully ran RUU, problem is I'm on UK O2 but being complete idiot I installed 3's ROM. Even the 3's ROM don't boot up. I can't run RUU anymore, because every time RUU is trying to reboot into boot loader it get stuck.
So,
I got phone from O2 that has a 3 logo (its stuck on it),
I have S-OFF phone so it probably voided the warranty.
Can anyone think of any solution please?
Thanks in advance for your help guys.
If you need more info please let me know.
Marcin

There are at least 5 similar topics, one is mine (same thing happened to me). Use search.

Does adb works yor you ?

yeap I have also created a topic on this.
I had to send mine back to HTC to fix.
What I would like to know is, if you send it back to HTC, would they notice the s-off and charge you money?

What ROMs were you all on? I got a similar problem on stock ROM after XTC Clip S-OFF, but a battery pull fixed it. I guess this only happens with S-OFF stock ROMs, so switch to avoid this.

No, adb doesn't see my phone....

mpolak83 said:
No, adb doesn't see my phone....
Click to expand...
Click to collapse
Remember with adb you need to be in Fastboot not Hboot! Very important. Cab you get into Fastboot?

InfernalByte said:
Remember with adb you need to be in Fastboot not Hboot! Very important. Cab you get into Fastboot?
Click to expand...
Click to collapse
When I run Adb devices it doesn't list my phone...so it doesn't work i suppose....
If I send my phone to HTC for repair will they accept it or will charge me because of S-OFF??

I just need my phone to be in the state so I can send it to HTC...I need to at least get rid off 3 logo and S-OFF...

mpolak83 said:
I just need my phone to be in the state so I can send it to HTC...I need to at least get rid off 3 logo and S-OFF...
Click to expand...
Click to collapse
Try flashing the eng hboot by PB88IMG method, and then try and run the correct RUU. That's my best idea.

InfernalByte said:
Try flashing the eng hboot by PB88IMG method, and then try and run the correct RUU. That's my best idea.
Click to expand...
Click to collapse
I have tried that, but I got the error that I can't roll back to older version of hboot.

I have just booked my phone for repair.. I'm gonna act stupid. I'll tell them that my friend installed something on my phone etc. Probably won't work... I will let you know what they said.
HTC gave me some terms and conditions to read and one of the says:
2.3 NonWarranty chargeable Repair Service
a) Repair of a Device that is
In-Warranty but which needs to be repaired including the following or similar
reasons shall be classified as a NonWarranty chargeable Repair Service:
1) Accidental damage. Accidental damage to the Device, such as dropping it
on the ground or in water. 2) Broken Liquid Crystal Display (hereinafter
known as “LCD”). 3) Damaged Sync or Charger Connector. 4) Damage
caused by liquid entering the Device, or other misuse due to the failure of the
Customer to follow the instructions properly. 5) Failure of the Customer to
upgrade the software according to the procedures outlined under the
warranty terms card of the Device. 6) Downloading illegal software onto the
Device. 7) Where the fault is caused by downloading illegal software onto the Device
or other accidental damage, the Customer shall be required to pay for spare
parts, labour, diagnosis and software refurbishment along with shipping and
handling charges.
Is S-OFF classified as illegal software?

Everything except RUU is illegal software...

Bubaaak said:
Everything except RUU is illegal software...
Click to expand...
Click to collapse
So I'm busted?

It's 50:50
Sent from my HTC Desire S using Tapatalk

Bubaaak said:
Everything except RUU is illegal software...
Click to expand...
Click to collapse
Wrong.
Its not illegal but you have probably invalidated your warranty. The thing is HTC have to bother to check your phone for custom software and a lot of the time they do.

Quick update.
I have sent my phone to HTC for repair under warranty yesterday. I have checked the status today, and it says "We are repairing your phone" So it looks like HTC don't check if the phone was rooted or have S-OFF

I've done the same i tried to flash a ruu image that was the wrong one i followed a thread on how to get s-on again just so i knew i could. I got s-on but now my phone is stuck on bootloader and is not recognised by the pc Please let me know how you get on and if you get charged as i will be doing the same i think.

InfernalByte said:
Wrong.
Its not illegal but you have probably invalidated your warranty. The thing is HTC have to bother to check your phone for custom software and a lot of the time they do.
Click to expand...
Click to collapse
Aren't custom Sense ROMs illegal ?
Coz Sense is HTC Proprietary framework.

goatimus said:
I've done the same i tried to flash a ruu image that was the wrong one i followed a thread on how to get s-on again just so i knew i could. I got s-on but now my phone is stuck on bootloader and is not recognised by the pc Please let me know how you get on and if you get charged as i will be doing the same i think.
Click to expand...
Click to collapse
You have to go to fastboot
Sent from my HTC Desire S using Tapatalk

how to S-ON HTC wildfire after revolutionary!

HI everyone. i have started this thread as i didnt know what to do when i first had to send my wildfire back for repairs. first download the attatched zip. unzip to desktop and make sure u have got the drivers for your bootloader interface already installed. to do this you will need just two things. the zip you have just downloaded and the HBOOT which i included inside the ziped file. once extracted run the java file named S-ON.jar and plug your phone in and turn on fastboot. once connected make sure you click on check connection. once you have done that you should see your serial number appear. okay your ready to go. look for the first tab and click on it. then click on HBOOT/SPL. locate the HBOOT file you inzipped with the S-ON tool and then click it. once done just click on flash HBOOT/SPL. once done you will see it says FLASH HBOOT/SPL/SUCCESS. thanks for takuing time to look at my GUIDE and i hope it helps you. just remember one thing only flash the new HBOOT after you have installed the RUU which is android 2.1 update 1 so you can root again.

thanks for posting this, gonna try it now since I have to send my wildfire in for repair..

no problem if you have any trouble let me know and ill help you gain s-on

Hmm well it didn't work, so just sent it in as it was. I replaced the custom recovery and the custom rom with stock from an RUU, I hope thats enough.
To gain S-ON I also tried the suggestions from a few other posts, I guess the problem is that I didn't gain S-OFF by software but by using an XTC-Clip. The fastboot command to flash the hboot always returned something like remotly denied or simular

kaefert said:
Hmm well it didn't work, so just sent it in as it was. I replaced the custom recovery and the custom rom with stock from an RUU, I hope thats enough.
To gain S-ON I also tried the suggestions from a few other posts, I guess the problem is that I didn't gain S-OFF by software but by using an XTC-Clip. The fastboot command to flash the hboot always returned something like remotly denied or simular
Click to expand...
Click to collapse
this will not work with xtc clip i have 1 other way tho. please try this.
go into you start menu click RUN the type cmd in the dialog box. when you have the cmd up type C:\fastboot>fastboot oem mb 9C068490 1 30 then it will say okay. then open the s-on tool then try to flash the HBOOT. let me know if you have anymore problems. but this way shud work for you
they will not accept it as they just have to go into the HBOOT menu and they will be able to see it is s-off. and they will send it back as it is and wont carrie out any sort of repairs on it as you have hacked the phone and comprimised the security software

hmm, well we will see. I will post as soon as I get an response. That command "fastboot oem mb 9C068490 1 30" always threw an error and somewhere I read that maximum 3 parameters are allowed

kaefert said:
hmm, well we will see. I will post as soon as I get an response. That command "fastboot oem mb 9C068490 1 30" always threw an error and somewhere I read that maximum 3 parameters are allowed
Click to expand...
Click to collapse
okay no worries. if they wont repair it. then get back to me and ill cook somthing up and get you back to s-on. this is the trouble when gaining s-off with a xtc clip. its a pain to get back to s-on again lol but good luck anyways

Thanks for the moral support, I hope they will repair it...
Well back then I had no chance, my Wildfire was delivered to me with hboot 1.01.001 back in the time where there was no software S-OFF method for 1.01.001 and up, so I found myself a shop that had an XTC-Clip and invested 10€ on him

Okey! So they repaired it although it had S-OFF done by XTC-Clip. Got it back yesterday, and the phone earpeace is working again

kaefert said:
Okey! So they repaired it although it had S-OFF done by XTC-Clip. Got it back yesterday, and the phone earpeace is working again
Click to expand...
Click to collapse
Great news for you mate im glad they sorted it out for you. and your very lucky as they sent mine back twice for being s-off lol.

lol, where are you from? and where did they send your device? Im from austria and they sent my device to slovakia and they gave me a slovenian report of what they did so I had to use google translate to understand it

[Q] Returning a Desire S to S-ON

Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.

schnidex said:
Hi all
I would like to know if it is possible to return a Desire S to S-ON if it were made it S-OFF, rooted and then upgraded from a network-specific ROM to a higher generic HTC ROM.
I've seen various threads about this, but can't find any specific steps for a relative newbie.
The revolutionary.io method would be used to go S-OFF.
Any input very much appreciated.
Click to expand...
Click to collapse
Go to shippedroms and download the RUU for your phone. Although why you'd want to return to stock is beyond me?

You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.

schnidex said:
You're saying that just running a branded RUU will return it to S-ON? Are you sure about that?
It's because I'd need the phone sent back under warranty, which S-OFF invalidates.
Click to expand...
Click to collapse
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?

olyloh6696 said:
+1 sending my phne back on Monday. I read the guide, but I still don't get it. It's too confusing. What's adb shell etc?
Click to expand...
Click to collapse
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
kartkk said:
do a nandroid backup & also set up your adb beforehand
setting up adb saved me from possibly bricking my device a few times
try this guide
Click to expand...
Click to collapse

ben_pyett said:
ADB is Android Debug Bridge. It's installed on your PC and enables you to control the phone over USB (if you have USB debugging on) and HTC drivers installed on PC.
adb shell - is simply when you run a shell through a command prompt on a PC so that you're able to directly type commands into the phone from the PC.
You should be able to see the adb drivers as a link within my signature, download and install these as a quick workaround which should enable you to run adb shell or you could follow the full correct method of installing the full Android SDK and JDK see below:
Click to expand...
Click to collapse
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Sent from my HTC Desire S using XDA Premium App

olyloh6696 said:
Thanks Ben! Makes sense! But to s-on again, can I just flash the h-boot., but then how do I use RUU to get back to stock? Will u need to wipe data first etc?
Click to expand...
Click to collapse
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.

ben_pyett said:
I'm afraid that I don't know about S-ON after S-OFF with AlphaRevx as I used XTC clip to get S-OFF myself, which is one way process.
So as I've never gone through the process myself I can't really confirm its success or failure.
But, I assume that you're following this GUIDE which involves running an RUU as the final step.
I wouldn't bother wiping data first as I imagine that the RUU process will do that as part of its operation. If not and it works you can always run a factory reset afterwards.
Click to expand...
Click to collapse
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?

olyloh6696 said:
cheers ben. will this also remove cutom recoveries from the phone (cwm) ?
so it would be truly stock then?
Click to expand...
Click to collapse
If the ruu runs successfully to competition I believe that it will return the device do that it's identical to stock
Swyped from HTC Desire S using XDA Premium

After many, many hours of trying to figure out what the hell half the terminology about Android actually means and wondering whether or not I would brick my phone..
..I'm now back to S-ON. It's been a pretty horrible experience all in all. Yes, it's easy when you know how but knowing how has been through trial and fortunately not much error.
From being on 6.98.1002, I used the Jorgen method in Ben's link above to get to 0.98.0000. I should note that when my phone was first supplied, I was on 0.98.0002 and very worried that the earlier software wouldn't work - but I tried it anyway, and it did. However, I was still S-OFF.
I then re-installed my stock network ROM using the RUU. This kept me on 0.98.0000 but put the phone to S-ON. I flashed the branded ROM that the phone was shipped with thinking that this would take me to 0.98.0002 but to my surprise it didn't. Otherwise though, the phone is now stock condition again.
So I then tried to update OTA to the problematic software which caused me all this grief in the first place - and it appears my network have withdrawn it. And rightly so, pending a fix.

schnidex said:
Ben, I've seen elsewhere you've said:
"If you load the latest RUU you may end up updating the HBOOT so that it can't be downgraded."
..in which case, Houston, we may have a problem. The latest HTC non-branded ROM (1.47...) gives you HBOOT 6.98.1002.
Click to expand...
Click to collapse
You're right, I'm afriad that this is an area where I'm no expert, But HBOOT = 6.98.1002. = Alpharevx = so you've not upgraded it simply failed to downgrade (which is slightly better- I think )
I notice that there are a couple of guides, allow I've obviously not tried either of them both are in the [GUIDE] A Complete Tutorial for the Beginners and Others sticky
The second guide looks quite complex and not for beginners...
Although I've just spotted a note within the second guide which says says
Note 2: RUU 1.46 or greater can not be downgraded as yet, since gingerbreak does not work on these RUUs.
So Opps....a full nights sleep may shed some more light on this.....and hopefully so sound advice from someone who has already performed this task.
Good luck. (I'll back online in the morning) - but, only really able to answer easier questions and not unfortunately not provide you with a solution.....but I'll do what I can!

Alternate way to restore your phone to S-ON and stock
If your attempts are unsuccessful, there's another potential way to go S-ON.
http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2
Maarten

To be or not to be...bricked?

Hey guys,
some days ago I tried to get rid of my branded Sensation ROM, hboot 1.27, so I tried the bear method and everything was fine (did root/flash rom several time before, but with 1.17) until...until the wire trick was successful...then there was a driver issue due to my stupidity not to check the adb drivers before flashing...
result -> bricked device! No bootloader anymore, no power, no status LEDs...nothing...I prepared myself and my PC/Phone to unbrick the device. Launched linux and tried to figure out the device node so to be able to proceed with unbrick, no success. Linux didn't show anything. Frustration...now I tried to give it a last last-ditch attempt.........and I couldn't believe it: LED came alive, linux message "new high speed usb device, Product: Android Phone", [sdb] Attached scsi removable disk", phone is booting and I can see something like Android but the screen is black...apart of the top part, where I can see the correct time, battery power (charging!), some status messages.
I'm able to enter recovery and this is where I stopped and need advice: What happend? Is the device bricked? Should I proceed with "unbrick" ? I was close to "The phone is water under the bridge", now I want to avoid any further stupid mistake...I guess the phone is still S-On (***locked*** in recovery) so I think its not that easy to simply flash a new rom?
Thanks to anyone in advance for advice!

It sounds to me you will need to re flash your firmware. Go to the IRC channel and sign in. The people there can walk you through thing.

T-Macgnolia said:
It sounds to me you will need to re flash your firmware. Go to the IRC channel and sign in. The people there can walk you through thing.
Click to expand...
Click to collapse
Thanks I will do that tomorrow, I think it's better to wait until the battery is fully charged (it's close to zero since my s-off attempt some days ago...).
Best regards

hellbot77 said:
Thanks I will do that tomorrow, I think it's better to wait until the battery is fully charged (it's close to zero since my s-off attempt some days ago...).
Best regards
Click to expand...
Click to collapse
After doing some reading today it seems like you need to remove temp root from your device to solve your problem. But still go to the IRC channel as XDA Recognized Contributor ganeshp will be there. It was one of his post that I got this info from, he is on of the most knowledgeable people about using Juopunutbear S-off.

hellbot77 said:
Thanks I will do that tomorrow, I think it's better to wait until the battery is fully charged (it's close to zero since my s-off attempt some days ago...).
Best regards
Click to expand...
Click to collapse
No.. No flashing Firmware... First you need to remove temproot first.. As T-Mac said
Go to my soff guide (link in signature)
And get the soff tool (ignore if you already have it)
Then connect the device with the black screen to pc.. Then run the
remove_temp_root file.. That will remove the temp root.. Then you can boot normal
Sent from my pyramid.. Through blazing fast sonic waves

ganeshp said:
No.. No flashing Firmware... First you need to remove temproot first.. As T-Mac said
Go to my soff guide (link in signature)
And get the soff tool (ignore if you already have it)
Then connect the device with the black screen to pc.. Then run the
remove_temp_root file.. That will remove the temp root.. Then you can boot normal
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Wohooo, Phone is online again
Thanks Thanks Thanks!

[S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA

http://www.youtube.com/watch?v=zNswkPGYtLc
note: updated 2/20 @ 9:20 EST, better ICS compatibility.
Welcome to Facepalm S-Off for the HTC One S (S4 only).
Credits and terms:
Exploit by beaups. Full guide, testing, and concept by jcase and beaups. Thanks to dsb9938 and dr_drache for support and testing. Thanks also to all of the regulars at teamandirc.
Both beaups and jcase will collect the applicable active bounties. Further donations are greatly appreciated and can be sent to:
beaups - [email protected] - http://forum.xda-developers.com/donatetome.php?u=711482
jcase - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2376614
dsb9938 - [email protected] - http://forum.xda-developers.com/donatetome.php?u=2963256
dr_drache - [email protected] - https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=6LRSY8MT8P3A6
You can also come by irc for support or just to say thanks: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
While this process shouldn’t be too risky, bricks can happen. None of us will be accountable. If you are worried, don’t do it.
This is a pretty simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
HTC One S superCID: http://forum.xda-developers.com/showthread.php?t=1671643
Once you have confirmed you have SuperCID, get started (read it through first so you understand it all):
Special note for One S users - flashing the OTA firmware (which you are initiating, but not actually doing here) likes to BRICK superCID phones for some reason. Follow these instructions EXACTLY. After the error 92 in step 5, whatever you do, do NOT run the fastboot flash command again. Make sure you procede on to step 6.
Let's get started:
1.) Download patcher and unzip it in your working directory:
soffbin3.zip http://d-h.st/WrZ Mirror http://goo.im/devs/dsb9938/soff/soffbin3.zip
2.) Download zip that matches your model id and move it in your working directory (do not unzip it!):
OneS PJ4010000-OneS.zip http://d-h.st/sE6 Mirror http://goo.im/devs/dsb9938/soff/PJ4010000-OneS.zip
3.)
Code:
adb reboot bootloader
(wait for bootloader)
4.)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
5.)
Code:
fastboot flash zip <appropriate zip filename from above>
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
6.) Immediately issue the following command:
Code:
fastboot oem boot
You may see some errors, just wait for the device to boot into Android (only now, you should be booted into Android with no eMMC write protection of any kind active).
7.) Issue the following 3 commands to update the security partition with S-off flags (one command at a time!):
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
(wait for a few seconds)
8.)
Code:
adb reboot bootloader
9.) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.

YES
I love you man!
Goodbye bootloader restrictions, hello OTA's! <3
Edit: I made a Tutorial Video! If there's anything wrong that you guys want me to remove or anything, let me know. Once again, good work!

Worked. <33333 oodles of love!

Very simple....thank you guys so much!!!!!!!!

Wow....thank you guys
Sent from my HTC One S using Tapatalk 2

oh yea! thanks a million

Odp: [S-Off] Facepalm S-Off for HTC Devices One S, One XL, Droid DNA
w00t. Sensation work!
Its possible to edit Scid to any "official" and relock BL after s-off?

Problem resolved

i dont even have this phone and im happy for u guys!! s-off!!! good **it!!!!:good::victory::highfive:

I read earlier on http://chat.andirc.net:8080/?channels=facepalm that higher hboots were having issues. What hboot are you on?

Qs5 said:
I read earlier on http://chat.andirc.net:8080/?channels=facepalm that higher hboots were having issues. What hboot are you on?
Click to expand...
Click to collapse
1.14, so I guess that would do it. I'll downgrade and try again, thanks.
I just don't understand why I'm not getting the vital CID error anymore. I still have SuperCID...

Jewcifer said:
1.14, so I guess that would do it. I'll downgrade and try again, thanks.
I just don't understand why I'm not getting the vital CID error anymore. I still have SuperCID...
Click to expand...
Click to collapse
Hmm he did it. Weird. http://forum.xda-developers.com/showpost.php?p=38176024&postcount=776

Qs5 said:
Hmm he did it. Weird. http://forum.xda-developers.com/showpost.php?p=38176024&postcount=776
Click to expand...
Click to collapse
His HBOOT is actually higher than mine. Odd.

Jewcifer said:
His HBOOT is actually higher than mine. Odd.
Click to expand...
Click to collapse
You could always try redownloading the PJ4010000-OneS.zip, might be a bad download?

Qs5 said:
You could always try redownloading the PJ4010000-OneS.zip, might be a bad download?
Click to expand...
Click to collapse
Come to think of it, when I was downloading the soffbin3 package the download was behaving oddly and kept stalling. Could have been server problems? I'll try redownloading that.

Guy S3 device work or not? Please report.:victory:

Jewcifer said:
Come to think of it, when I was downloading the soffbin3 package the download was behaving oddly and kept stalling. Could have been server problems? I'll try redownloading that.
Click to expand...
Click to collapse
If all else fails try a new cable and or usb port. That seemed to help other people back in the day xD
http://forum.xda-developers.com/showpost.php?p=30845333&postcount=38

Beaups just advised me that some custom roms could have issues, failing S-Off which I had as well. He said better re-clock bootloader, revert to stock rom, unlock bootloader, root, super CID, then s-off

teerapong.g said:
Guy S3 device work or not? Please report.:victory:
Click to expand...
Click to collapse
Definitely do NOT attempt this on an S3 yet. I don't want to speak on behalf of the creators, but seeing as there's a difference between the S4 and the XL, there's got to be a difference between the S4 and the S3.
uvt_novice said:
Beaups just advised me that some custom roms could have issues, failing S-Off which I had as well. He said better re-clock bootloader, revert to stock rom, unlock bootloader, root, super CID, then s-off
Click to expand...
Click to collapse
This was my original plan, actually x) I'm on a CM10.1 base. I'm thinking it should work fine with a sense-based ROM though, I'll try that first.

Amazing job guys.
Confirmed S-OFF on HTC One S (S4) T-Mobile US HBOOT 1.14.0004.
Man...S-OFF....and 2.1.0 Viper??? It's like I'm holding a brick of gold in my hand, lol.
Sent from my One S using xda app-developers app