Database Info

Help an idiot out

so i unlocked my device via HTCDev.com thinking since its htc device and all they said was i had to unlock bootloader to flash custon OS's i already knew about S-OFF but being the site didn't talk about it(why would it) i went and flash virtouous ROM and got stuck at the HTC screen. i wasnt thinking so i never backed up the stock HTC Rom!!
now i tried 2 of those RUU's in the shipped rom thread the tmous ones with 29 and 50 both saying wrong version.
my question here is there anyway to get at least one RUU to work or get s-off from HBOOT?
my reason of doing this after going back to completely stock is i cant wait any longer for HTC/Tmobile to get us ICS so i tried the custom way and failed lol

I am sure unless you super SID you will have to find ROMs specific for the country the phone came from.
Eg my phone was from Asia region and I could not flash Euro ROMs

ok from the Shipped rom thread in the dev section for the sensation i was trying to go back to stock to gain s-off but the tmous(USA) which is where i am from said wrong version.

futty said:
ok from the Shipped rom thread in the dev section for the sensation i was trying to go back to stock to gain s-off but the tmous(USA) which is where i am from said wrong version.
Click to expand...
Click to collapse
What h boot version do you have?
Sent from my HTC Sensation 4G with Beats Audio using xda premium

Hboot: 1.18.0000

Check your CID using fastboot getvar cid to see if these still match the ROM you were trying to flash.

says for cid is t-mob010
i guess out of the 2 stock ruu"s from the post doesnt match that?
edit: ok from what i learned in another post i opened up the rom.zip file and looked at android-info.txt both the cid and mid matched my phones from the RUU file "RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed" buuuuttttt it tried to update it but fails saying i need to correct version :\

futty said:
Hboot: 1.18.0000
Click to expand...
Click to collapse
Are you on t mous us?
Also you can s off and super cid and flash any ruu.
Sent from my HTC Sensation 4G with Beats Audio using xda premium

Yes i am. the 2 Ruu's i am using seem to have matching info to my phone when i went to get the rom.zip it uses to send to my phone and looked in the android-info.txt but tell me to get the correct RUU and try again. i got the from here:http://forum.xda-developers.com/showthread.php?t=1074559 under the tmous RUU one with 29 and the other 50.
so i am just stuck at the white screen with the word HTC. if i could get s-off and SuperCID through fastboot that would be awesome but googling it shows up that i cant s-off via fastboot ughhh

still no luck cant seem to flash anything without s-off or supercid
so looks like i am jumping the boat going to sprint this thursday and geting the iphone 4s...byebye android

If you can get into fastboot you should be able to flash RUU from there. Just download the RUU.exe and run it as administrator. Follow the prompts in the exe program while your phone is in fastboot mode.
Sent from my HTC Sensation 4G with Beats Audio using xda premium

futty said:
still no luck cant seem to flash anything without s-off or supercid
so looks like i am jumping the boat going to sprint this thursday and geting the iphone 4s...byebye android
Click to expand...
Click to collapse
Maybe iCrap is better for you. When you use Android phones and want to complete unlock them for flashing customroms aso you shoud realy learn to read before you do something. I hate it when people are not able to read about the stuff they want to do and when something goes wrong they blaim Android for it.
To get s-off, super CID and root on a HTC Android device is realy easy if you read the how-to threads and normaly takes about 15 minutes.
Have fun with your iCrap 4S and please don't try to jailbreak it before you read some stuff.
Sent from my Revolver powered ICS Asus Transformer TF101

first off let me say i have rooted and flashed roms on my sensation before just fine. i was unlocking via htcdev.com and figured their method didnt require s-off since it didnt say anything about it. it just talked about unlocking it to put customs os's on it. 2nd i always had a love hate thing for IOS since i had the 3G and ipod touch.
far as using the RUU'ss it tells me i need the correct Ruu version or something like that. maybe because i didnt run as admin but i have all that stuff turned off due to the theme i used for windows 7 required it off.

If I were you I would Super CID your device. That is what I had to do. A great guide that I used was http://forum.xda-developers.com/showthread.php?t=1472298

i tried and i get this error
vreg_set: request is duplicated id 14
pyramid_init_sd, SD card power on ok
sdcc_init_memory_device done
[FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
[JAVACARD_ERR] SMART_IO.CRD cann't find
Click to expand...
Click to collapse
and my cid remains the same as t-mb010
how can i fix it? would love to get mt device back up and running

You can recover this. Firstly read this guide, regarding downgrading hboot and getting s-off.
http://forum.xda-developers.com/showthread.php?p=23222794
The problems are due to HTC.dev not unlocking all parts of the boot loader - you can't flash radio.img or boot.img so nothing is working.
Sent from my Pyramid-T

stringer7 said:
You can recover this. Firstly read this guide, regarding downgrading hboot and getting s-off.
http://forum.xda-developers.com/showthread.php?p=23222794
The problems are due to HTC.dev not unlocking all parts of the boot loader - you can't flash radio.img or boot.img so nothing is working.
Sent from my Pyramid-T
Click to expand...
Click to collapse
thanks for your help. i went to your link and i flashed a stock tmobile rom as suggested and before i could take out boot.img and send it over fastboot my sensation booted to the home screen. i went ahead and s-off'd and SuperCID. just need to create a backup before i screw up again.
again thanks for the help everyone.

[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.

Stuck on HTC screen, can't unlock bootloader, can't root from Fastboot

I got a bricked T-mobile Sensation today at the shop and after checking it out I thought it would be easy to fix but unfortunately its proving to be much more difficult than I expected. Here's what I'm working with:
Locked s-on
Hboot 1.18.0000
radio 10.14.9035.01_m
First, I tried all kinds of PG58 zips. None worked. I figure I need to be unlocked to do it. Did the HTC unlock and got to the warning screen and where it asks to choose yes or no. I can navigate to yes or no but when I choose yes it just freezes and doesn't do anything. I tried it 3 different times, same thing. I can't even choose factory reset in Hboot, it just freezes. I don't know what the eff is going on. I've been downloading RUUs but have yet to find the correct one. I don't know what firmware it has because it does not boot up.
I thought, well shoot, I have fastboot, maybe I could just s-off and root from fastboot, but I can't find any thread explaining how to do it.
Any help would be great.
Thanks!
Edit:
Found the correct RUU, 1.50.xxxx whatever. WHen I run the utility It says its rebooting into bootloader but stays in the same screen and doesn't do anything. I don't know if this helps, but when I go into the bootloader I cannot go back into hboot. It just, freezes.

Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1192300
And you need to be s-off to flash those pg58 zips, thats why they failed.

As you're on HBOOT 1.18.0000 use the revolutionary method to get S-OFF. http://revolutionary.io
The HTC unlock is a bit redundant as it doesn't give S-OFF which you need.
There are many guides here on XDA to help you. Such as:
http://forum.xda-developers.com/showthread.php?t=1192300
EDIT: Oops didn't notice that "Kazireh" has already posted the link.
You'll need the HTC drivers (download HTC Sync install it then delete HTC Sync leaving the drivers installed).
You should also get the ADB tools installed as at some stage they'll be useful.
As far as the RUU is concerned you need to make sure it's the right one for the current CID on the phone.

Kazireh said:
Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1192300
And you need to be s-off to flash those pg58 zips, thats why they failed.
Click to expand...
Click to collapse
gol_n_dal said:
As you're on HBOOT 1.18.0000 use the revolutionary method to get S-OFF. http://revolutionary.io
The HTC unlock is a bit redundant as it doesn't give S-OFF which you need.
There are many guides here on XDA to help you. Such as:
http://forum.xda-developers.com/showthread.php?t=1192300
EDIT: Oops didn't notice that "Kazireh" has already posted the link.
You'll need the HTC drivers (download HTC Sync install it then delete HTC Sync leaving the drivers installed).
You should also get the ADB tools installed as at some stage they'll be useful.
As far as the RUU is concerned you need to make sure it's the right one for the current CID on the phone.
Click to expand...
Click to collapse
Thanks for the help guys, but heres the deal:
I cannot s-off due to it not being able to boot.
I could try Junopbears s-off but I cannot unlock, as it just freezes when I try.
I found the correct ruu but again it freezes and does not boot into the bootloader.
My CID is T-mob010
I have all drivers installed, adb, fastboot, etc

If your on hboot 1.18 you have a gingerbread fw, look for that
Sent from my HTC Sensation 4G

its completely possible that the motherboard is failing. I see this in my shop all the time, though usually with the MyTouch 4G (faulty eMMC chip) but the sensation and a few other HTC's also see this. we havent come up with a solution between my two stores employees, so hopefully someone here can?

q said you did not understand, is how I explain more thoroughly I am new to the subject
and my device does not enter the system and when using the mode prop vo comand says device not found what to do? sensation with my ta hboot 1.27.0000 s-s on rl unloked help me

2strokenut said:
Thanks for the help guys, but heres the deal:
I cannot s-off due to it not being able to boot.
Click to expand...
Click to collapse
Can you get into "Fastboot USB" ?
I could try Junopbears s-off but I cannot unlock, as it just freezes when I try.
Click to expand...
Click to collapse
Junopbear is wrong as it's for 1.2x.xxxx HBOOT, try Revolutionary.
I found the correct ruu but again it freezes and does not boot into the bootloader.
My CID is T-mob010
Click to expand...
Click to collapse
Eek.
T-MOB010 == RUU x.xx.531.xxxxxxxxx according to my list.
I have all drivers installed, adb, fastboot, etc
Click to expand...
Click to collapse
Good.
There are a few "unbrick" guides, never tried to use them so can't help on that front.

nickL0V3 said:
its completely possible that the motherboard is failing. I see this in my shop all the time, though usually with the MyTouch 4G (faulty eMMC chip) but the sensation and a few other HTC's also see this. we havent come up with a solution between my two stores employees, so hopefully someone here can?
Click to expand...
Click to collapse
Yeah that's what I'm leaning toward right now, there is nothing else I can do. I have 4 or 5 Mytouchs on the shelf with bad eMMc chips so I guess this one is joining them.
gol_n_dal said:
Can you get into "Fastboot USB" ?
Junopbear is wrong as it's for 1.2x.xxxx HBOOT, try Revolutionary.
Eek.
T-MOB010 == RUU x.xx.531.xxxxxxxxx according to my list.
Good.
There are a few "unbrick" guides, never tried to use them so can't help on that front.
Click to expand...
Click to collapse
Yes the RUU was 1.50.531.xxxxxx
Yes, I can get into Fastboot usb, I can do fastboot commands, it just freezes when the RUU tries to do its thing.
Jbear would still work if the bootloader were locked, but I couldn't unlock the bootloader. Revolutionary will not work either because its run while the phone is on, which I can't do.
I think I've exhausted every option, it seems to all point to a failed eMMc chip, shame though, I really like these phones.
Thanks for the help fellas

GL
///////////////

[Q] Need unroot/re-locking help

I have an HTC One X with 3.18 firmware that is rooted, SuperCID, S-OFF and unlocked. I want to return it to stock, unroot and re-lock - basically I want to get it as close to stock as possible.
I made a backup of the stock ROM prior to flashing a custom ROM onto it, so I was able to restore that.
So here is how I assume I need to go about this:
unroot - not sure how to do this, I can't RUU 3.18 can I? I'm downloading the stock OTA right now just in case.
set the bootloader back to "locked" using this: http://forum.xda-developers.com/showthread.php?t=2168578
Is this correct? Do I need to undo the SuperCID? Is it possible to undo the S-OFF?

Why are you returning it to stock?
Sent from my Sony Tablet S using xda app-developers app

exad said:
Why are you returning it to stock?
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
It's a work phone. My bosses didn't care about me rooting it, but I will need to return it eventually to exchange it for another phone and it needs to be stock in case another employee gets it.

See the problem with that is, you've rendered it to a state whereby, if you relock and S-ON and the next person who uses it runs into an issue and wants to RUU or an update comes out, the phone will brick.
But yes, essentially, you're on the right track, RUU, to change CID back "fastboot oem writecid CWS__001" Then, I can't recall how to get Security flag back to S-ON but it is mentioned on this forum, I just don't have time to look for it, being at work.
Then you can relock
But just remember that if the next person RUUs or updates they will certainly brick. I would never root a company phone, for future reference.

exad said:
See the problem with that is, you've rendered it to a state whereby, if you relock and S-ON and the next person who uses it runs into an issue and wants to RUU or an update comes out, the phone will brick.
But yes, essentially, you're on the right track, RUU, to change CID back "fastboot oem writecid CWS__001" Then, I can't recall how to get Security flag back to S-ON but it is mentioned on this forum, I just don't have time to look for it, being at work.
Then you can relock
But just remember that if the next person RUUs or updates they will certainly brick. I would never root a company phone, for future reference.
Click to expand...
Click to collapse
Ah, gotcha. I didn't know that would happen when I unlocked and rooted - thought I had read everything I needed to about it prior to rooting, but I guess I missed that.
I guess I could just RUU, change the CID back, but leave it as S-OFF. That would keep it from getting bricked, right? The chances of it being an issue would be pretty slim I imagine.

Yes but then you also leave a big security hole open aswell.
Sent from my Sony Tablet S using xda app-developers app

exad said:
Yes but then you also leave a big security hole open aswell.
Sent from my Sony Tablet S using xda app-developers app
Click to expand...
Click to collapse
So there's really no way to return it back to stock? That's kind of a bummer...

So I'm currently returning my phone to stock.
In some steps for returning the phone to stock I've seen them tell you to lock the bootloader prior to flashing the RUU. This doesn't sound right to me but I wanted to check. Here are the steps I'll be taking:
1. Change CID back to stock - fastboot oem writecid CWS__001
2. flash RUU
3. Lock the bootloader - fastboot oem lock
4. Set it to s-on - fastboot oem writesecureflag 3
In some sets of instructions I've seen steps 2 and 3 switched around. I just want to make sure I get these in the right order.

kimboinatl said:
So I'm currently returning my phone to stock.
In some steps for returning the phone to stock I've seen them tell you to lock the bootloader prior to flashing the RUU. This doesn't sound right to me but I wanted to check. Here are the steps I'll be taking:
1. Change CID back to stock - fastboot oem writecid CWS__001
2. flash RUU
3. Lock the bootloader - fastboot oem lock
4. Set it to s-on - fastboot oem writesecureflag 3
In some sets of instructions I've seen steps 2 and 3 switched around. I just want to make sure I get these in the right order.
Click to expand...
Click to collapse
Sometimes the ruu fails if your bootloader is locked, but if it works, then you can lock it afterwards. It should work fine since you're s-off. Also, being s-off doesn't (shouldn't) void any warranties, so that step isn't necessarily required.

RollTribe said:
Sometimes the ruu fails if your bootloader is locked, but if it works, then you can lock it afterwards. It should work fine since you're s-off. Also, being s-off doesn't (shouldn't) void any warranties, so that step isn't necessarily required.
Click to expand...
Click to collapse
Excellent, so I can just RUU and then lock. I think I may just leave it as s-off - I'm leaving a security hole, but my main concern is just getting it back to stock without root.
Also just to confirm, the RUU will set recovery back to stock as well, right?
EDIT: Crap, just realized my tampered flag is still on. The RUU doesn't fix this, right? Guess I need to remove this first.

kimboinatl said:
Excellent, so I can just RUU and then lock. I think I may just leave it as s-off - I'm leaving a security hole, but my main concern is just getting it back to stock without root.
Also just to confirm, the RUU will set recovery back to stock as well, right?
Click to expand...
Click to collapse
Yessir. Everything should be back to stock except your CID (use the writeCID command), your bootloader (fastboot oem relock), and your s-off which you can leave as is.
Edit: it should remove the tampered flag. It did when I ruu'ed. Which ruu are you running?

RollTribe said:
Yessir. Everything should be back to stock except your CID (use the writeCID command), your bootloader (fastboot oem relock), and your s-off which you can leave as is.
Edit: it should remove the tampered flag. It did when I ruu'ed. Which ruu are you running?
Click to expand...
Click to collapse
I'm using the 3.18 RUU (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed.exe).
I found a thread that has instructions on changing RELOCKED to LOCKED here:
http://forum.xda-developers.com/showthread.php?t=2168578&highlight=lock+status+flag
Do I need to do this? My understanding is that it will forever say "RELOCKED" unless I actually set it back myself somehow, but would an RUU do this for me?

kimboinatl said:
I'm using the 3.18 RUU (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed.exe).
I found a thread that has instructions on changing RELOCKED to LOCKED here:
http://forum.xda-developers.com/showthread.php?t=2168578&highlight=lock+status+flag
Do I need to do this? My understanding is that it will forever say "RELOCKED" unless I actually set it back myself somehow, but would an RUU do this for me?
Click to expand...
Click to collapse
When I ruu'd it set it back to locked
Sent from my HTC One XL using xda premium

31ken31 said:
When I ruu'd it set it back to locked
Click to expand...
Click to collapse
Really? RUU shouldn't have an effect on the LOCKED flag.

31ken31 said:
When I ruu'd it set it back to locked
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Are you sure? If so, did you happen to have s-off when you did this?

Yes and supercid
Sent from my HTC One XL using xda premium

kimboinatl said:
Are you sure? If so, did you happen to have s-off when you did this?
Click to expand...
Click to collapse
If he didn't (have s-off) he would have bricked.
I am also curious about this. If the combo of S-off and RELOCKED and RUU results in LOCKED, than its the first I've heard of it.
Running the RUU and UNLOCKED, I can say first hand, the result is that it still says UNLOCKED.

I went ahead and used the method here to set it back to LOCKED:
http://forum.xda-developers.com/showthread.php?t=2168578&page=3
I set the CID back to original, relocked the bootloader, set it to LOCKED with the above method, and did the RUU. Everything is now back to stock except for the s-off. I seriously doubt they'll look for it or even care really.
31ken31, I probably would have just tried what you did if this wasn't a work phone, I just didn't want to risk it.
Thanks to everyone for the help!

kimboinatl said:
the CID back to original, relocked the bootloader, set it to LOCKED with the above method, and did the RUU. Everything is now back to stock except for the s-off. I seriously doubt they'll look for it or even care really.
Click to expand...
Click to collapse
Or have any idea what S-off even means, for that matter.
And a few folks have randomly received S-off devices from the factory. So you can conceivably just claim "It was like that when I got it", if they happen to ask about it.

redpoint73 said:
Or have any idea what S-off even means, for that matter.
And a few folks have randomly received S-off devices from the factory. So you can conceivably just claim "It was like that when I got it", if they happen to ask about it.
Click to expand...
Click to collapse
Yes on both counts
I could have also claimed that I got one with super CID, I think I've read that it happens sometimes, but it was easy enough to change back so hey, why not.
I'll really miss having root though. It makes things so much better.

Maximus HD with S-ON (Possible?)

I read that what the s-off does is basically buy you time so you dont have to flash the boot.img on your pc. The Maximus HD rom says you must have your s-off, but how about if I have my s-on, but flash the boot.img, will it be the same thing?
Thanks
Sent from my One S using xda app-developers app

elias.acab said:
I read that what the s-off does is basically buy you time so you dont have to flash the boot.img on your pc. The Maximus HD rom says you must have your s-off, but how about if I have my s-on, but flash the boot.img, will it be the same thing?
Thanks
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
No, the reason you need S-OFF for MaximusHD is because that ROM requires a leaked unsigned firmware, which you can only flash if you're S-OFF.

dr3amsINdigital said:
No, the reason you need S-OFF for MaximusHD is because that ROM requires a leaked unsigned firmware, which you can only flash if you're S-OFF.
Click to expand...
Click to collapse
Oh I see, thanks!
Sent from my One S using xda app-developers app

Hey, listen!
Please somebody help me. I have rooted and unlocked bootloader on my HTC One S. I want to install MaximusHD ROM on my phone, but I'm pretty sure I'm not S-off.
I have CM10.1 ROM installed on my phone.
Can somebody please tell me which guide should I follow so I can be S-off and install the desired ROM (MaximusHD)???
Also, with s-off the red letters disappear from splash screen? Thanks in advance. I really hope you can help me. I want sense 5 on my phone.
Sent from my One S using xda app-developers app

rolo143 said:
Hey, listen!
Please somebody help me. I have rooted and unlocked bootloader on my HTC One S. I want to install MaximusHD ROM on my phone, but I'm pretty sure I'm not S-off.
I have CM10.1 ROM installed on my phone.
Can somebody please tell me which guide should I follow so I can be S-off and install the desired ROM (MaximusHD)???
Also, with s-off the red letters disappear from splash screen? Thanks in advance. I really hope you can help me. I want sense 5 on my phone.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Moonshine S-OFF: http://forum.xda-developers.com/showthread.php?t=2325590
or
Facepalm S-OFF: http://forum.xda-developers.com/showthread.php?t=2155135

Absolutely right.
And how to remove the red warning text you can find here.
Keep in mind that once you're s-off and want to return to s-on (warranty, whatever...) you'll need to reflash any stock bootloader. Else you'll definitely brick your phone. Best thing is to run any RUU before you set s-on flag on your phone then. It'll automatically restore the stock bootloader that comes with it.

S-off to install Maximus then S-on for final step. It's Ok.
I must do S-on because I get boot loops. Flashed Temporary radio 1.13 because it restarted auto.

hongha_222 said:
S-off to install Maximus then S-on for final step. It's Ok.
I must do S-on because I get boot loops. Flashed Temporary radio 1.13 because it restarted auto.
Click to expand...
Click to collapse
So it's very unstable with s-off?
I mean if I'm going to have WiFi trouble and radio and bootloops I guess is better with s-on?
Sent from my One S using xda app-developers app

rolo143 said:
So it's very unstable with s-off?
I mean if I'm going to have WiFi trouble and radio and bootloops I guess is better with s-on?
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Your device must have s-off without s-off you WON'T BE ABLE TO RUN ROM.
Click to expand...
Click to collapse
Try S-off first. Do it right way.
Then if you can't do anything to get it running or get boot loops, you should try S-on.
I feel it's perfect after 2 day and nothing worry about that.. Flash Temporary-Radio-Installer-V4 if your phone auto restart.

hongha_222 said:
Try S-off first. Do it right way.
Then if you can't do anything to get it running or get boot loops, you should try S-on.
I feel it's perfect after 2 day and nothing worry about that.. Flash Temporary-Radio-Installer-V4 if your phone auto restart.
Click to expand...
Click to collapse
I highly suggest AGAINST going S-ON with Maximus.
If you S-ON, you cannot flash an RUU to lower your hboot back down to hboot 2.15. This means you will be unable to revert back to an older rom or to use the current CM roms.
S-ON while on HBOOT 2.16 is a dead-end and you're forcing yourself to be on either Maximus or another rom that is compatible with 2.16 like Magio. Until someone figures out how to S-OFF while on hboot 2.16, you're stuck with it.
If you're S-OFF, installed Maximus, and you're experiencing bootloop problems and radio problems. Please look into the rcdata partition fix that me and many other HTC One S users were experiencing. Don't S-ON until you give this a try.

tsphan said:
I highly suggest AGAINST going S-ON with Maximus.
If you S-ON, you cannot flash an RUU to lower your hboot back down to hboot 2.15. This means you will be unable to revert back to an older rom or to use the current CM roms.
S-ON while on HBOOT 2.16 is a dead-end and you're forcing yourself to be on either Maximus or another rom that is compatible with 2.16 like Magio. Until someone figures out how to S-OFF while on hboot 2.16, you're stuck with it.
If you're S-OFF, installed Maximus, and you're experiencing bootloop problems and radio problems. Please look into the rcdata partition fix that me and many other HTC One S users were experiencing. Don't S-ON until you give this a try.
Click to expand...
Click to collapse
you're right but I don't see any problem when I try the rcdata fix.
b) Type "mount" to see a list of mounts. I saw that the data block (p35) was being mounted again in /sdcard, which should be (p36). Checking /etc/fstab shows that the /sdcard was commented out!
I can do S-Off with hboot 2.16.

flashed with s-on
I am very new to Android, having been converted from iOS. I had extensive experience with jailbreaking and all that.. flashing Windows Mobile with my HTC TyTn as well.
After having my One for almost 3 months I decided to root it and explore other ROMs. Rooting wasn't an issue and I flashed MaxiumusHD 14 which was replaced within 2 weeks with version 20. Everything went well and I've got battery life that certainly exceeds, by a long shot, versus stock battery consumption rate. (Juice Defender and Profile Scheduler definitely help there too). Original stock ROM consumed a lot of power with the HTCCheckIn service. Noticed that here in Brazil I believe my battery life is worse than when I purchased the phone in Canada, I believe it's due to poor service coverage areas (weak data signals, in particular).
As I learn more, I realize that I don't believe that any of the steps I performed to root and install Clockwork involved making S-OFF active. My bootloader shows S-ON. ROM works fine and I didn't get any errors in flashing. How is that possible?
Am I missing something obvious here?
Should I do moonshine S-OFF and flash again?
I've frozen the updater using Titanium Backup (purchased that, it's great) so that I don't keep getting pestered to update to Maximus 21. I just flashed 20! (and I see no issues and nothing in the change log seems to be a huge selling point).
Thanks for the assistance with this newbie.
Matt

mattdbr said:
I am very new to Android, having been converted from iOS. I had extensive experience with jailbreaking and all that.. flashing Windows Mobile with my HTC TyTn as well.
After having my One for almost 3 months I decided to root it and explore other ROMs. Rooting wasn't an issue and I flashed MaxiumusHD 14 which was replaced within 2 weeks with version 20. Everything went well and I've got battery life that certainly exceeds, by a long shot, versus stock battery consumption rate. (Juice Defender and Profile Scheduler definitely help there too). Original stock ROM consumed a lot of power with the HTCCheckIn service. Noticed that here in Brazil I believe my battery life is worse than when I purchased the phone in Canada, I believe it's due to poor service coverage areas (weak data signals, in particular).
As I learn more, I realize that I don't believe that any of the steps I performed to root and install Clockwork involved making S-OFF active. My bootloader shows S-ON. ROM works fine and I didn't get any errors in flashing. How is that possible?
Am I missing something obvious here?
Should I do moonshine S-OFF and flash again?
I've frozen the updater using Titanium Backup (purchased that, it's great) so that I don't keep getting pestered to update to Maximus 21. I just flashed 20! (and I see no issues and nothing in the change log seems to be a huge selling point).
Thanks for the assistance with this newbie.
Matt
Click to expand...
Click to collapse
I would post this question again in the HTC One section, this is the HTC One S section. They would most likely be able to help you.

tivofool said:
I would post this question again in the HTC One section, this is the HTC One S section. They would most likely be able to help you.
Click to expand...
Click to collapse
Ok, will do. Sorry I didn't notice the S. Thanks