All the instructions I can find for getting S-OFF on a HTC One S seem to be out-of-date. * [These instructions](https://forum.xda-developers.com/showthread.php?t=2155135) ask you to download soffbin3.zip but the link [takes you to website which thinks it's streaming you a video](http://d-h.st/WrZ) and the [mirror link is dead](http://goo.im/devs/dsb9938/soff/soffbin3.zip) * [Rumrunner is available](http://rumrunner.us/downloads-2/) but soju.exe frezzes on "please wait" * [firewater redirects to Sunshine](http://theroot.ninja/) which is a paid service. The Wayback Machine [has a copy of the executable](https://web.archive.org/web/20140519064907/http://firewater-soff.com/firewaterdownload-3) but when I copy the executable to my device and run it, it just... deletes itself. I'm out of ideas. How do I get S-OFF on my HTC One S in this day and age? (The only reason I want S-OFF is to install HBOOT 2.16.)

I have a HTC ONE M7 purchased from T-Mobile. I rooted it and have CyanogenMod installed in it. Recently, I switched to different carrier. Now, my phone rejects foreign sim card and asks for Network SIM card lock. The unlock code provided by T-Mobile doesn't work due to rooting the phone. I want to go back to T-Mobile Android stock ROM and try the unlock code. What's the process for it? Here are some details from bootloader screen: *** TAMPERED *** *** UNLOCKED *** M7_UL PVT SHIP S-ON RH HBOOT-1.61.0000 RADIO-4T.35.3218.16 OpenDSP-v35.120.274.0718 OS-7.18.531.2 eMMC-boot 2048MB Feb 11, 2015, 18:39:53.0 Apart from help in doing S-OFF, I would appreciate if someone points me to right link for going back to Stock ROM.

I want to try the CyanogenMod9 Alpha builds for the T-Mobile myTouch 4G Slide [MT4GS/Doubleshot] and all the instructions say I need S-OFF. The problem is that I have HBOOT 1.55 so software solutions like Revolutionary do not work and I am left with the JuopunutBear wire trick. I am not up for that so I will stay S-ON for now. Then, I found ROM Manager that claims to easily install custom ROMs easily, but I can not find if ROM Manager requires S-OFF for HTC devices. Does anyone know if I can install custom ROMs through ROM Manager with S-ON?

Ok guys i'm in a real problem! I cannot make or receive phone calls for one week... it all started when I got bored with the original OS of the HTC One M9, so I rooted the phone and installed CM13 following some tutorial on the internet (its the first time I root and install a custom rom in my life).. when I finished, I was verry happy until I discovered that I cannot make or receive calls, I searched for solutions, and I tried them (installing gapps, uninstalling capps, set phone app as default app...) but none of them worked. So I installed slim roms hoping that this can be the solution, but the same problem is stilling. I installed then android revolution HD and the problem disappeared, it was not solved, it disappeared because this rom didn't event boot. I reinstalled cyanogemod in order to use my phone for things in which it stills usable, and decided to return to the stock rom (the boring one). I found a good tutorial , in which he said that in order to successfully install it i have to: - Download the right ruu. - Change the cid and the mid. For the ruu file I found the zip file for the same version used in the tutorial (1.32.401.8). Now when I try to change the cid using this command: fastboot oem writecid HTC__001 It says: ... FAILED (remote: unknown command) finished. total time: 0.006s After googling it, the problem seems to be caused by 'S-ON', so I have to 'S-OFF' the phone. I downloaded sunshine and run it but the app shows an error saying: > SunShine encountered problems with your rom. Please flash a stock, or more near stock rom and try again I'm really confused. To install a stock rom i have to change cid. To change cid i have to S-OFF the phone. To S-OFF the phone i have to install a stock rom.

**Device:** AT&T HTC Holiday w/ Android 2.3 & no service **Goal:** To get Android 4.x (any derivative) working on said device. **Problem:** When I tried to install the PACMAN ROM (by loosely following the instructions provided at [Update HTC Raider/Velocity/Vivid/Holiday TO Android 4.4.4 KITKAT](http://www.crazyadvisors.com/update-htc-raider-velocity-vivid-holiday-to-4-4-4-kitkat/)) I got my phone stuck in a boot loop, meaning I can't S-OFF it using the tools provided at unlimited.io. (ControlBear is too impatient waiting for the phone to reboot because the phone is perpetually in a slow-to-start first-run state as it can't get past PACMAN's language selection screen before restarting itself, I'm assuming because the phone knows PACMAN isn't signed by HTC so it kills it) It doesn't help that ControlBear is closed source, meaning I can't modify it to suit my specific conditions. **The bright side:** I have the recovery "CWM-based Recovery (by @KDH4865) v5.0.2.7" installed on the phone, so I can flash any OS ROM I want, it's just not guaranteed to work. **Problem (cont'd):** I don't have a backup of anything. **The bright side (cont'd):** I imagine installing a ROM that is signed by HTC might work, such as that over-the-air update to ICS which was never received. Alternatively, I have heard chatter on the PACMAN forums about "flashing boot.img" as an alternative to S-OFF, and I have no idea what that means. All I know of are the OS partition, the user data partition, the bootloader (on a separate BIOS chip?), the recovery partition, and the GSM antenna which does that nasty S-ON security stuff. I am clearly missing a small chunk of information in my brain. Where might one go from my current situation in pursuit of one's goal? EDIT: It turns out HTC gives away what it calls "ROMs" in Windows executable format for its devices free of charge. Apparently it's some kind of "RUU" thing, which I guess is like Android open heart surgery. I'll try that and see how it works.

So I have an HTC Evo 4G LTE that I'm working on, and I upgraded Hboot to version 2.10. That probably wasn't quite as brilliant of an idea as I thought, being as now I can't seem to gain S-Off. I know how to get S-Off on Hboot version 2.09, but when I ran the RUU which included that, it gave me the error "ERROR : BOOTLOADER VERSION ERROR," so I figure it doesn't want to *downgrade* anything. Can I get back to Hboot 2.09, or gain S-Off some other way?

My HTC Desire is stuck in a boot loop: https://android.stackexchange.com/questions/52571/htc-desire-boot-loop I am trying to set S-Off so that I can use the Windows version of ADB and delete some apps/data off the phone memory. I don't want to wipe all the data off the phone memory and reset back to factory settings. I have tried using Revolutionary on two separate computers however, it just remains on the 'waiting for phone to connect' message. I have tried the phone in Fastbot mode and Recovery. I can't remember if the phone has USB debug enabled or not as I cannot boot into Android to check?

I came across [this forum post](http://forum.xda-developers.com/showthread.php?t=2221039) on rooting and getting S-OFF in HTC Desire HD. In step 6 it says > You should see the $ turn into a #. If this happens, congrats you have > root access. and continues the steps. The question I have is, does the rooting process finish there or do I have to follow the other steps as well to get the phone rooted?

I went through the tutorial found here and was able to unlock the bootloader, get s-off, get CWM installed, and superuser. Here are the questions I am having now. 1. Should I relock the bootloader after getting s-off? Will that prevent me from doing anything? 2. In that tutorial under the facepalm instructions, do I need to do step 7 if I already got s-off using facepalm? 3. How can I remove *** TAMPERED *** from the bootloader?

Let's say I want to run some app requiring root access on my HTC Droid DNA (2.06 stock firmware, 4.1 Android, NOT broken, meaning it's S-ON). My (somewhat naive) understanding of S-ON/S-OFF is that it write-protects the ROM, and thus makes writing anything into it impossible (such as whatever changes are needed to install root that persists from boot to boot). The question is, **is there a way to obtain *temporary* root without breaking S-ON**, such that it only persists till next boot? (with the understanding that any changes to filesystem made by the need-root application that would have been saved into protected parts of the filesystem would ALSO be lost after reboot). P.S. Please note that the question is about technical detail about rooting - asking me to clarify which app I need to run to help me do the same task without rooting is entirely off-topic.