Database Info

[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

[Q] Help With RUU or S-OFF, Stuck at ICS S-ON

So I flashed the ICS OTA to see if my signal improved, and it was the same so I wish to install ARHD ICS but cannot without S-OFF and S-OFF is just all round useful.
I'm still S-ON with 1.27 hboot, and have managed to install ARHD but still S-ON. Does anyone know a way to get back to GB stock or S-OFF 1.27. I have tried an RUU but it always fails, and using A PG85IMG.zip doesn't work (just stays on parsing or reboots a lot).
Any help would be GREATLY appreciated and will do all I can to help myself and you guys.
Thank you.

Bump, really need help. I can't flash anything from bootloader, not RUU.zip or firmware, it just reboots or says parsing for a long time. Really need to fix this.

You can't S-OFF 1.27 yet

EddyOS said:
You can't S-OFF 1.27 yet
Click to expand...
Click to collapse
I understand that, but is there no way to get the phone into a state where I can use an RUU to downgrade to gingerbread? Like, at all?

No, as you don't have S-OFF
Although I believe a guide is being written to 'brick' the phone on purpose so you can downgrade it but it's not ready yet (not my work)

EddyOS said:
No, as you don't have S-OFF
Although I believe a guide is being written to 'brick' the phone on purpose so you can downgrade it but it's not ready yet (not my work)
Click to expand...
Click to collapse
Alright thanks man I've seen your posts a lot so I trust you know your stuff a lot.
Guess I will stick with this for the time being, at least my phone works now.. kind of haha.

[Q] H-Boot 1.06, S-ON, no Super CID, please help update

First, let me apologize for probably posting something that's been answered. Unfortunately, the forum search is down right now and I've been working on this for hours and gotten no where. I've been away from updating my phone for a long time and need something more stable.
I'd like to upgrade to Maximus 10 ROM. I'm on H-Boot 1.06. Now I think I need a higher H-Boot and maybe Super CID, but I haven't had any luck with any of those. I tried using Moonshine and that stops working when it tries to ADB, for some reason that I haven't been able to figure out.
Basically, can someone give me a quick rundown of what/where I need to go to get my phone updated for Maximus? Many thanks!

shadow300z said:
First, let me apologize for probably posting something that's been answered. Unfortunately, the forum search is down right now and I've been working on this for hours and gotten no where. I've been away from updating my phone for a long time and need something more stable.
I'd like to upgrade to Maximus 10 ROM. I'm on H-Boot 1.06. Now I think I need a higher H-Boot and maybe Super CID, but I haven't had any luck with any of those. I tried using Moonshine and that stops working when it tries to ADB, for some reason that I haven't been able to figure out.
Basically, can someone give me a quick rundown of what/where I need to go to get my phone updated for Maximus? Many thanks!
Click to expand...
Click to collapse
Moonshine is definitely easy, when it works.
You should consider yourself lucky with that low of a HBoot.
You could use Facepalm S-off (most who have updated their phone to Jelly Bean and 2.15 hboot cannot use it.)
http://forum.xda-developers.com/showthread.php?t=2155135
After you s-off you could skip onto maximus if you wanted.

tivofool said:
Moonshine is definitely easy, when it works.
You should consider yourself lucky with that low of a HBoot.
You could use Facepalm S-off (most who have updated their phone to Jelly Bean and 2.15 hboot cannot use it.)
http://forum.xda-developers.com/showthread.php?t=2155135
After you s-off you could skip onto maximus if you wanted.
Click to expand...
Click to collapse
Thanks for your help. I've tried Facepalm S-off and it doesn't work (I'm guessing because I'm not SuperCID which I also can't get to work?) I keep getting error Remote: 99 unknown fail after pushing PJ4010000-OneS.zip even after wiping cache, powering down, etc. I've continued on with the rest of the steps and I'm still S-On.
I'm sure I'm missing something obvious.

shadow300z said:
Thanks for your help. I've tried Facepalm S-off and it doesn't work (I'm guessing because I'm not SuperCID which I also can't get to work?) I keep getting error Remote: 99 unknown fail after pushing PJ4010000-OneS.zip even after wiping cache, powering down, etc. I've continued on with the rest of the steps and I'm still S-On.
I'm sure I'm missing something obvious.
Click to expand...
Click to collapse
Your missing supercid
Sent from my HTC One S using Tapatalk 4

CleanROM 7 stuck at splash screen

Stuck...just displays the HTC logo on white screen.
I had cleanrom 5.0 final. TWRP, super SU, rooted, unlocked. Firmware 2.20.
I dropped in the new ROM, did a factory reset in TWRP, and installed new rom. I read that that would work with my current setup, but apparently not. I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
I flashed back to 5.0 with no issues, but I would really like to try to get the cleanrom 7 working if possible. Any ideas?

It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita

timmaaa said:
It sounds like you're s-on, if so you'd need to flash the boot.img via fastboot. Is this the first ROM you've flashed? Please post your bootloader details.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for your reply. You are correct, I am s-on. But I was able to re-load CleanROM 5. This is my second custom rom on this phone (the first being CleanROM 5). But this is only my third custom rom ever, so I am pretty much of a noober. :cyclops:

klaypigeon said:
I am unclear on the part where it says "Highly recommend latest Jellybean firmware and S-Off!" Not sure how to determine this or proceed. Things here seem to be getting increasingly more jargoned rather than step by step for those of us that do this once a year or so :/
Click to expand...
Click to collapse
The ROM threads are to inform you of the features and requirements of the ROM, not to be a step-by-step guide. There are plenty of step-by-step guides in various places, for those that care to read and look.
If you don't flash often, a good resource is my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
My Index will at least point you to the s-off process. I intend to add some info about the 2.15 firmware (as people keep constantly asking about it), but work has been chaotic, to say the least.
Another good thing to do, is read through the more recent pages of the ROM thread, or do a search on the thread.

Thanks, I am subscribed to your index, that's where I found the ROM and what I used during my first flash.
I did the process for unlocking the 2.20 firmware about a year ago as that is what my phone came with. I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
'CID Getter' says I have no CID, which I read means I have superCID.
Firmware : 2.20
SuperSU installed and functioning (I have root)
Current ROM: CleanROM 5 Final
S-ON
TWRP 2.3.1.0
So you think I need to do s-off as described here? http://forum.xda-developers.com/showthread.php?t=2155071
If I brick this phone I am using a clam-shell for a year until contract renewal :/

klaypigeon said:
I assume that would have given me superCID and s-off in order to install my old ROM (CleanROM 5).
Click to expand...
Click to collapse
You shouldn't be assuming anything. You just said the CID Getter says S-on. You can also confirm s-on or s-off by going into bootloader.
The main reason CleanROM7 will not boot, is that you forgot to extract boot.img from the ROM file, and flash it separately using fastboot. Some older versions of CleanROM didn't require this (boot.img was flashed in the AROMA installer), so that may be why you don't remember doing this.
S-off removed the requirement to flash boot.img separately (will flash in recovery automatically when you flash the ROM). It will also allow you to install hboot 2.15 and associated firmware, if you happen to suffer from signal drops or random reboots while on Sense 5 ROMs.

Further to that, CID Getter doesn't show your actual CID. The proper way to display your CID is by using the fastboot command "fastboot oem readcid". Like Redpoint said, you shouldn't be assuming anything.
Sent from my Evita

Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.

What did you flash?
Sent from my Evita

Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.

timmaaa said:
Further to that, CID Getter doesn't show your actual CID.
Click to expand...
Click to collapse
Ha, that's not a very useful app, then. What is it actually reading?
---------- Post added at 09:24 AM ---------- Previous post was at 09:21 AM ----------
klaypigeon said:
Well...its pretty much dead. I verified supercid and then I flashed the bootloader and now it is just in a slow bootloop. It shows the HTC developer splash screen and then shuts down then a few minutes later does it again and so on. Looks like I am clamshell bound.
Click to expand...
Click to collapse
Do you mean "locked the bootloader" instead of "flashed"?
If you locked the bootloader, this is what is supposed to happen. Locking the bootloader assumes you will be running RUU, and renders the phone unable to boot normally.
I know you got it back up and running. But for future reference, this phone is almost never bricked, as long as the screen comes on.
---------- Post added at 09:26 AM ---------- Previous post was at 09:24 AM ----------
klaypigeon said:
Muahahaaha, WORKING! Had to hold down volume through 5 reboot cycles and it finally picked up bootloader. set S-OFF. Tried CleanROM every which way and flashed boo.img as well, never could get it to make it past google boot animation. Installed ViperXL and boot.img without issue. Jelly Bean 4.2.2 sweetness! I lost hope there for about an hour, glad I didn't launch phone into the woods.
Click to expand...
Click to collapse
Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.

I'm not sure what CID Getter is actually reading, but when I used it it came up with the incorrect CID, can't remember exactly what it was now but it was definitely incorrect because I already had SuperCID.
Sent from my Evita

Flashing boot.img manually is not necessary with s-off, it should happan automatically when you flash a ROM. I suspect you may be having trouble with CleanROM due to a buggy or outdated TWRP version. What version of TWRP are you using?
It also seems that you are pretty unclear about some of the basic concepts around flashing ROMs on this phone. It would probably benefit you to read and learn a bit more before something bad actually happens due to negligence.
Click to expand...
Click to collapse
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out

klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do. As far as read and learning, I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
If you have s-off you don't need to flash the boot.img via fastboot, that's only required if you're s-on. It might be worthwhile updating your TWRP to the 2.6 version though.
What Redpoint was saying is that you need to have a firm understanding of what you're doing when it comes to modifying your phone. If you only do it once a year that's cool, but that probably means that once a year you need to brush up before making any changes to your device. Rushing in without the required knowledge is how bricks occur. This is only being suggested to help you, for your own good.
Sent from my Evita

klaypigeon said:
I am using 2.3.1 TWRP. In the viperXL thread they said I may have to flash the boot.img if I had hboot 1.14 which I do.
Click to expand...
Click to collapse
Only with hboot 1.14 or later and s-on. If s-off the protection which prevents boot.img from being written in recovery is bypassed.
I believe TWRP 2.3.1 was a pretty trustworthy version (although older). So not sure why CleanROM didn't flash. Might not be a bad idea to update to 2.6.0 (although the latest 2.6.4 seems to have some bugs).
klaypigeon said:
I do this once a year I am not a ROM junkie. Every time I do it I have to re-learn. I work in IT so it is a use it or lose it world in my brain - volumes of info in > volumes out
Click to expand...
Click to collapse
Yeah, I understand that you only do this on a seldom basis. And its a lot of esoteric knowledge to have to relearn (or take in, since things have likely changed since lasts time). However, that doesn't change the fact that not fully understanding all the concepts and steps can have dire consequences for your phone.

[Q] No OS installed HTC ONE X

I have the htc one x with Rogers, version 3.17.631.2... the RUU isn't available for this version.
***TAMPERED***
***UNLOCKED***
s-on
Currently I have no OS installed, I have been searching through forums on this website for about 6 hours last night with no solution. Can someone please help. Thanks
I also have the token ID saved on my computer.
What I tried was:
installing the stock rogers PJ83IMG.zip from here
but since my version is 3.17.631.2 it wouldn't let me downgrade to the 1.73.631.1 version
Any suggestions?

Why are you trying to ruu. In order to ruu downgrade you will need to be s-off.
Sent from my VENOMized HoxL

is there any way to be s-off with no OS installed?

1. How did you even delete the OS?
2. Do you have a custom recovery?
Sent from my HTC One XL using XDA Premium 4 mobile app

I was installing a custom rom, and erased the OS by accident in TRWP, and I can flash a custom recovery on my phone. What would i do after that though?

Also go to the cleanROM thread and use their boot.img to get things at least booting up
You don't need soff to flash img files via fastboot
Sent from my HTC One XL using XDA Premium 4 mobile app

alright im giving it a try atm!

Why not just flash a ROM? You already have a custom recovery on your phone, that's what TWRP is. Should you really be messing with your phone in the first place though? It doesn't seem like you have the faintest idea of what you're doing if you can't even recover from deleting your OS.
Sent from my Evita

I LOVE YOU GUYS!
its all fixed up

timmaaa said:
It doesn't seem like you have the faintest idea of what you're doing if you can't even recover from deleting your OS.
Click to expand...
Click to collapse
I tend to agree. There has also seems to be an increase of this occurrence in the last several months of "I wiped the OS accidentally and I don't know how to recover". Which is a bit troubling since the default wipe in TWRP is factory reset, Dalvik, and cache. The Wipe screen on TWRP explicitly states that this is all the is usually needed. If you wipe /system, you did so deliberately by going into the Advanced screen and picking it from there. Meaning the OP took extra steps to do something without knowing if it was necessary, and without knowing how to recover from it.
This also means the OP didn't create a nandroid backup in TWRP, which would have been a simple way to recover. This is basic, fundamental step that should be taken whenever modding a phone, but something n00bs seem to be "skipping" (or ignorant of) lately.
This type of behavior/mindset while modding does not bode well for the life of your phone.

actually the TWRP recovery i had on my phone was really outdated. i didnt have the advanced option. I simply had to pick from a list and i wiped it all without warning.
I've learned what i have done wrong, and thank you guys for it.
I currently have cleanROM flashed on my phone, but its really buggy.. it even turns off randomly and if i ever lose reception I will have to restart my phone to gain reception again. Not sure why this is happening? What do you guys suggest I do?

You need to search properly before posting. It's XDA rules. The reboots and signal loss problems have been discussed countless times in the Cleanrom thread. Read a few of the last pages and you're guaranteed to find the solution.
Sent from my Evita

ecakici said:
actually the TWRP recovery i had on my phone was really outdated. i didnt have the advanced option. I simply had to pick from a list and i wiped it all without warning.
Click to expand...
Click to collapse
That's a pretty lame excuse. My previous general notion still holds: You took deliberate steps to wipe the OS (/system) as that option is still not selected as default even on older versions of TWRP. And you were therefore wiping things willy-nilly without understanding what they were, whether they really needed to be wiped, or how to recover from them.
And you still should have made a nandroid (TWRP backup).
All in all, it implies a careless mindset while modding your phone (skipping steps and doing things without understanding).

I have searched the forum: [ROM][9/11] - CleanROM 7.0.P1 -★| Android 4.2.2! | Sense 5! | Lite! | Stable! |★-
and found that if i install hboot 2.15 on my phone it should stop rebooting and the reception would go back to normal right?
is there anything else I have to do.
please, if it isn't too much trouble link me to a guide that fixes these issue for the HTC One X (Rogers)
or just give me a few steps of how to fix these issue.
Thank you so much!
PS my battery life improved so much, i usually charged my phone twice a day, and I haven't charged my phone at since 7am today.

Yes. Flash the 2.15 firmware. It's in the first post of Turge's stock Sense 5 ROM thread in the development section.
Sent from my Evita

Step 1: SuperCID 11111111
Step 2: S-Off using beaups guide
Step 3: Flash the 2.15 firmware
Can someone link me to the best guide to follow for step 1?

You can do it two ways, here's the first:
Step 1: SuperCID with hex edit method.
Step 2: S-off with Facepalm S-off.
Step 3: Flash firmware.
Or the other way:
Step 1: S-off with Rumrunner S-off.
Step 2: SuperCID with fastboot command:
Code:
fastboot oem writecid 11111111
Step 3: Flash firmware.
I believe the second method is easier. The Rumrunner s-off process seems much easier, it doesn't require you to have SuperCID first to work. Once s-off is achieved you can easily change your CID by fastboot command as opposed to messing around with hex editing.
Sent from my Evita

thanks a lot guys!
i learned a lot through this forum!

HTC One X plus OS has been deleted accidentaly
ecakici said:
I LOVE YOU GUYS!
its all fixed up
Click to expand...
Click to collapse
Can u plz tell me how did u u fixed it

reachsoumendra said:
Can u plz tell me how did u u fixed it
Click to expand...
Click to collapse
What is your exact problem?
Sent from my Evita.