Database Info

Stock Rom Odex

Hi
Does anybody know where i can find One S (S4) odex stock roms for tmobile. Basically i can't get ota updates and i think my problem is that my current stock rom is deodex.

none of the develops in the One S community wants to make it.. dont know why....
the closest u get is the nandroid in the dev section.. thats what im running now...

Why not run a RUU from the Shipped ROMs thread in development section

I'd like it too actually. I tried flashing stock recovery and relocking my bootloader, but out still said tampered and still couldn't flash an ruu... I'm hoping getting all stock could help with that.

There are no RUU's for tmobile uk sadly, so i need to super cid my phone to get the international version. Also i dont know how to super cid

I found another version of the RUU for TMOUS so I'll try that in the near future and see what happens.
Because the cramp just won't go away!

Does anybody have a stock nandroid for tmobile UK?
Sent from my HTC One S using xda app-developers app

If you read the posts it says there isn't one. Just to verify I looked and I didn't see one either.
Also, after going into fastboot and flashing stock recovery I did
Code:
fastboot OEM lock
My phone rebooted I did it again and flashed the latest RUU for my phone which was TMOUS 1.84 or something like that.
That seemed to work. Now running android 4.0.4.
_______________________________________
Because the cramp just won't go away!

mylegiscramped said:
If you read the posts it says there isn't one. Just to verify I looked and I didn't see one either.
Also, after going into fastboot and flashing stock recovery I did
Code:
fastboot OEM lock
My phone rebooted I did it again and flashed the latest RUU for my phone which was TMOUS 1.84 or something like that.
That seemed to work. Now running android 4.0.4.
_______________________________________
Because the cramp just won't go away!
Click to expand...
Click to collapse
I'm just curious are you from UK or USA. I supercid my phone yesterday and tried flashing three different ruu's but none of them worked. But then again my bootloader is unlocked so I'm not sure whether locking it will help.
Sent from my HTC One S using xda app-developers app

I'm from us, but please don't hate me i didn't decide to be birthed here
I'm assuming your a tmobile UK user due to your post. I'm not really familiar as to what to do with your situation as I've never dealt with UK RUU Issues. I would assume you probably can't use any of the RUUs from anywhere else. You would think T-Mobile would have an international one out. I would probably not risk damaging your device using other carriers unless someone tells you it works. I don't see why trying a tmous RUU would harm you though. There are two versions of it out a 1.54 and 1.84 I believe. I don't know what effect itll have on your phone though so don't blame me if it bricks if you try.

Ive got a huge problem I supercid my phone last night and after that I couldn't call or text anyone as well as recieve. I even unsupercid my phone and back to the original HTC__001 cid. So can anyone give me a solution. Btw I relocked my bootloader and ran the European RUU and it worked
Sent from my HTC One S using xda app-developers app

Maybe try to run the RUU again? Or a factory reset.
_______________________________________
Because the cramp just won't go away!

No no this happened due to me trying to super cid. I just did the ruu right now. I think I need to flash a radio but not sure how to
Sent from my HTC One S using xda app-developers app

That's possible I suppose. Here is how.
After flashing your device properly, start it up and let everything run a few minutes so the ROM can get settled in, I assume you've done that already.
Next you download the radio image you need, I'm not sure which it is I don't know what your running.
Then reboot to fast boot.
Enter
Code:
fastboot flash radio radio.IMG
Then reboot your phone with
Code:
fastboot reboot
Or you can do it through a menu on the device.
Then you should have your radio set.
Someone please correct if anything is wrong.
_______________________________________
Because the cramp just won't go away!

My hboot version is 1.14.002
Radio-1.06s.50.02.27_2
I'm not sure which radio to flash, so could you please tell me?
P:S I'm on the S4 processor
Sent from my HTC One S using xda app-developers app

I'm not sure which radio you need. This is what I have.
HBOOT-1.14.004
RADIO-1.08ts.50.02.16
I googled quick, but haven't been able to find anything as of yet. Maybe check the wiki?

lonegunman0 said:
My hboot version is 1.14.002
Radio-1.06s.50.02.27_2
I'm not sure which radio to flash, so could you please tell me?
P:S I'm on the S4 processor
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Your not flashing any radio with that HBOOT.
HTC One S

Flash radio
fmedrano1977 said:
Your not flashing any radio with that HBOOT.
HTC One S
Click to expand...
Click to collapse
Are you saying there aren't any radios that i can flash? I'm actually considering sending this back to htc to see if they can fix it but im not sure if they will

lonegunman0 said:
Are you saying there aren't any radios that i can flash? I'm actually considering sending this back to htc to see if they can fix it but im not sure if they will
Click to expand...
Click to collapse
He is saying you CAN'T flash radios, new, old, it doesn't matter. Your hboot does not support it. You are SOL.

Can't Get Back To Unrooted Stock No Matter What I Try

Last week I went back to stock to familiarize myself with the process (which unfortunately brought my HBoot to 1.14). I also decided to try out TWRP when I rooted again. But before I could finish up I hit a button in TWRP that didn't need any confirmation. I don't remember which button because it did what it did quicker than I could notice. After that I couldn't even flash a ROM because I couldn't mount the sd card and whatever happened erased everything on my phone but I ended up figuring that out.Now I'm on ViperOneS but I can't unroot. I can't flash either of the RUU (Error 155) that are for T-Mobile US I even changed my CID to 11111111 but no dice(and yes I did flash the stock recovery and boot before relocking). The only thing I can do to get close to unrooted stock is flash the nandroid of a rooted stock ROM. Now I haven't mentioned every method I've tried, so before I start getting bashed for not searching, I want to mention that I've been at this for about 4 days and I have tried EVERYTHING that I've found on XDA and other forums but nothings worked. Is it my HBoot that prevents from doing anything? Should get another One S? Or should I just be thankful that I have a functioning phone?
Sorry for the long winded post but I wanted to make sure I put in as much detail as possible.

antny said:
Last week I went back to stock to familiarize myself with the process (which unfortunately brought my HBoot to 1.14). I also decided to try out TWRP when I rooted again. But before I could finish up I hit a button in TWRP that didn't need any confirmation. I don't remember which button because it did what it did quicker than I could notice. After that I couldn't even flash a ROM because I couldn't mount the sd card and whatever happened erased everything on my phone but I ended up figuring that out.Now I'm on ViperOneS but I can't unroot. I can't flash either of the RUU (Error 155) that are for T-Mobile US I even changed my CID to 11111111 but no dice(and yes I did flash the stock recovery and boot before relocking). The only thing I can do to get close to unrooted stock is flash the nandroid of a rooted stock ROM. Now I haven't mentioned every method I've tried, so before I start getting bashed for not searching, I want to mention that I've been at this for about 4 days and I have tried EVERYTHING that I've found on XDA and other forums but nothings worked. Is it my HBoot that prevents from doing anything? Should get another One S? Or should I just be thankful that I have a functioning phone?
Sorry for the long winded post but I wanted to make sure I put in as much detail as possible.
Click to expand...
Click to collapse
It's most likely your hboot that prevents the RUU's from working. You can only use a RUU that contain a hboot of 1.14 or higher.
Since your signature says HBoot: 1.14 & Radio: 1.08ts.50.02.16_10.08e.50.04L. I assume you updated via the T-mobile US OTA, is that correct?
What's interesting is that other hboots in the 1.14 family are listed as 1.14.0002 but the T-mobile OTA the hboot is labeled 1.14.0004. I haven't seen anyone state if this is will prevent "downgrading" to 1.14.002 and don't feel like finding out myself.
What RUU are you trying?

dc211 said:
It's most likely your hboot that prevents the RUU's from working. You can only use a RUU that contain a hboot of 1.14 or higher.
Since your signature says HBoot: 1.14 & Radio: 1.08ts.50.02.16_10.08e.50.04L. I assume you updated via the T-mobile US OTA, is that correct?
What's interesting is that other hboots in the 1.14 family are listed as 1.14.0002 but the T-mobile OTA the hboot is labeled 1.14.0004. I haven't seen anyone state if this is will prevent "downgrading" to 1.14.002 and don't feel like finding out myself.
What RUU are you trying?
Click to expand...
Click to collapse
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium

antny said:
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I feel your pain. I updated with the OTA that moved us to hboot 1.13 before anyone said they changed the security :crying:.
The 1.84 and 1.53 RUU's wouldn't work for sure. 1.84 has the 1.13 hboot and 1.53 has the 1.09 hboot. Your only hope of using an RUU at this time is one of the Europe RUU's. The good news is that you already moved to supercid so you got that out of the way.
The ones that might work are the ones labeled "RUU_Ville_U_ICE_40_S_Europe_2.xxxxxx"
Here you can get the 2.21 RUU I can't recall if it's the 4.0.4 based one though. Not really sure where to get the other ones as file factory changed their download rules.
http://www.mediafire.com/?xlklqrlljb2zt#r9489rkr82wh2
You might need to click the "mainver error fix" on the on the All-in-one tool kit to get them to work since you would be downgrading the rom.
And if you do use that RUU from mediafire you can go here and click the thanks button for SneakyGhost for putting up the RUU for you to download.
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
Then go here and click the thanks button for Football since he's the only source of RUU's there is.
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
Good luck.

I've downgraded from 2.31 to 2.21, I know both have HBOOT 1.14 but not exactly sure if they have the exact identical numbers after the 1.14.
HTC One S
---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------
antny said:
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
2.21 RUU worked better for me than the T-Mobile stock Rom, it doesn't have w Wi-Fi calling do if that's a must for you only hope is to wait for the T-Mobile 2.35 RUU to be released.
HTC One S

dc211 said:
I feel your pain. I updated with the OTA that moved us to hboot 1.13 before anyone said they changed the security :crying:.
The 1.84 and 1.53 RUU's wouldn't work for sure. 1.84 has the 1.13 hboot and 1.53 has the 1.09 hboot. Your only hope of using an RUU at this time is one of the Europe RUU's. The good news is that you already moved to supercid so you got that out of the way.
The ones that might work are the ones labeled "RUU_Ville_U_ICE_40_S_Europe_2.xxxxxx"
Here you can get the 2.21 RUU I can't recall if it's the 4.0.4 based one though. Not really sure where to get the other ones as file factory changed their download rules.
http://www.mediafire.com/?xlklqrlljb2zt#r9489rkr82wh2
You might need to click the "mainver error fix" on the on the All-in-one tool kit to get them to work since you would be downgrading the rom.
And if you do use that RUU from mediafire you can go here and click the thanks button for SneakyGhost for putting up the RUU for you to download.
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
Then go here and click the thanks button for Football since he's the only source of RUU's there is.
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
Good luck.
Click to expand...
Click to collapse
I've thanked Football and gone to the link you provided but I don't get the whole Pt.1,2 and 3 thing. What am I supposed to do with that?
Edit: All good, just got it from the Dropbox link.... T-Mobile and Easy Tether don't mix.
fmedrano1977 said:
I've downgraded from 2.31 to 2.21, I know both have HBOOT 1.14 but not exactly sure if they have the exact identical numbers after the 1.14.
HTC One S
---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------
2.21 RUU worked better for me than the T-Mobile stock Rom, it doesn't have w Wi-Fi calling do if that's a must for you only hope is to wait for the T-Mobile 2.35 RUU to be released.
HTC One S
Click to expand...
Click to collapse
I don't really care about wifi calling, cool feature but I hardly use it. Is it 4.0.4 and Sense 4.1 though? It wouldnt stop me from using it if it wasn't but I'm just curious haha.

4.0.4 and Sense 4.0
HTC One S

fmedrano1977 said:
4.0.4 and Sense 4.0
HTC One S
Click to expand...
Click to collapse
Cool Cool Cool thanks

Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium

antny said:
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Glad it worked out for you.

antny said:
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
One last thing I did after installing that RUU was edit the build.prop to match some lines from the T-Mobile one:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=1
Make sure those match, these have given me the fastest DL speeds.
HTC One S

Yes! Thank you. This seems to be what I'm looking for. You can see the question I posted recently about this similar issue. But I also don't understand the part 1, 2, and 3 thing. Help?

DoogleDood said:
Yes! Thank you. This seems to be what I'm looking for. You can see the question I posted recently about this similar issue. But I also don't understand the part 1, 2, and 3 thing. Help?
Click to expand...
Click to collapse
What are you trying to do?
HTC One S

Nevermind I got it! I wasn't sure if the 3 "parts" of the EU RUU needed to be combined or... what. But upon extracting I found the full file.

fmedrano1977 said:
One last thing I did after installing that RUU was edit the build.prop to match some lines from the T-Mobile one:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=1
Make sure those match, these have given me the fastest DL speeds.
HTC One S
Click to expand...
Click to collapse
Why thank you sir.

antny said:
Why thank you sir.
Click to expand...
Click to collapse
Please someone help me I just flashed axiom rom wifif won't work I tryd other roms too, wifi won't work how can I fix this ??
Do I need to flash a RUU I am new to this. I had th latest tmo update before I rooted the phone people says that's why wifi won't work in other thread.
Please help me fix this !!!

johnyguy said:
Please someone help me I just flashed axiom rom wifif won't work I tryd other roms too, wifi won't work how can I fix this ??
Do I need to flash a RUU I am new to this. I had th latest tmo update before I rooted the phone people says that's why wifi won't work in other thread.
Please help me fix this !!!
Click to expand...
Click to collapse
I'm honestly not to sure on how to fix this. I've searched it before I went back to stock (going back to stock is a definite fix) and couldn't find much on it. I'm sure something has developed from it by now though. Actually :: navigates to another tab:: http://forum.xda-developers.com/showthread.php?t=1900644 if it's compatible with your ROM, this kernel claims to have a fix for wifi and sound (I don't know what the sound issue is all about) but try that, it might work. But most importantly search, read, search and read some more, especially since you're new to this, I've rooted many phones and I still had problems with the One S. Good luck!

Found RUU 2.35 and finally got my phone back to stock. I posted info here:
http://forum.xda-developers.com/showthread.php?t=1941402

sylvestk said:
Found RUU 2.35 and finally got my phone back to stock. I posted info here:
http://forum.xda-developers.com/showthread.php?t=1941402
Click to expand...
Click to collapse
That release gives you the no data when screen is off issue.
HTC One S

Excuse me for sounding stupid but grey matter not working

I have been flashing for some time but excuse me if I sound stupid but the grey matter just don't work any more. I have RUU'd different RUU's from the 1.82 to 2.20 trying to get different customs to work and I can't figure out what base I am on. At the time I am using Clean Rom 6.1 R2 and things seem to work fine but just wondering. Some how I managed to go from HBOOT 2.14 I think down to HBOOT 1.09 without downgrading. I think I got it from some RUU. I have read that the HBOOT 1.09 is a golden thing on the phone but don't know why.
With this rom I have tried to flash the 3.18 radio and get a soft brick at the boot screen. I am pretty sure the last time I RUU'd I used the Cingular Us 1.82 and in the process it upgraded itself to the 1.83 . Now I have read that some roms with sense work better on the 3.18 RUU.. Will I loose the HBOOT 1.09 if I do this?
At the present
S-OFF
unlocked
CID 11111111
radio 0.24p..32.09.0501.......
I am just looking and trying different variations to find the best setup for my phone. Excuse me for sounding so stupid. The grey matter just is slush any more.

The 3.18 ruu will give you the 2.14 hboot but sense you are s-off which hboot you have is not that important people wanted the 1.09 hboot because you could flash radios and boot.img with it s-off allows you too do this no matter what hboot you have
Sent from my HTC One X using Tapatalk 2

Because you're s-off it doesn't matter what hboot you're on. Sense ROMs tend to run smoother/better with the latest update. So feel free to RUU up to 3.18. Don't relocked your bootloader, just ruu.
If you want to run AOSP ROMs after, though, you'll need to downgrade your touchscreen firmware.
Also for some people cm10 doesn't boot until they've upgraded for some odd reason.
Sent from my HTC One XL using xda app-developers app

exad said:
Because you're s-off it doesn't matter what hboot you're on. Sense ROMs tend to run smoother/better with the latest update. So feel free to RUU up to 3.18. Don't relocked your bootloader, just ruu.
If you want to run AOSP ROMs after, though, you'll need to downgrade your touchscreen firmware.
Also for some people cm10 doesn't boot until they've upgraded for some odd reason.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I understand that being S-OFF one could do most anything and be safe but I didn't really know if loosing the HBOOT 1.09 had any consequents or not. Plus, didn't know if upgradeing to the 3.18 firmware would be that beneficial or not. At one point I was on the 2.20 and took the OTA ATT udgrade to see what it was about but didn't like the rom ,but I did downgrade the touch screen . There are features with all the customs but don't like any one in particular, wish there some way to combine certain features from each one into one to make one that I liked for my phone. So far the best I can come up with is Clean Rom 6.1R2 with BlueIceSense CR6 and cityID apk. plus the radio from 3.18.
Thanks for understanding loss of grey matter stupidity

[Q] HBoot - Unable to update.

After finally managing to work around Windows 8 and its BS, I rooted and unlocked the bootloader on my AT&T One X.
I'm now at the point of trying to update HBoot so that I can use the JB Roms. The phone is currently still running ICS. I followed the tutorial on YouTube from"onexroot" using JBWFlasher. My HBOOT versin is 1.14 currently, Originally my phone was S-ON with a CID of "11111111". I S-OFF'ed the phone and changed the CID to HTC__001 and all the way down the list because I keep getting the error "FAILED (remote: 41 model id check fail)". No matter which CID I give the phone or if I attempt to update for a device with S-ON or S-OFF.
Not really sure what else to try at this point as I've searched here and all over Google. I didn't want to bother you guys with it but I don't know where else to go.
Thanks for any help in advance.

Neorift said:
After finally managing to work around Windows 8 and its BS, I rooted and unlocked the bootloader on my AT&T One X.
I'm now at the point of trying to update HBoot so that I can use the JB Roms. The phone is currently still running ICS. I followed the tutorial on YouTube from"onexroot" using JBWFlasher. My HBOOT versin is 1.14 currently, Originally my phone was S-ON with a CID of "11111111". I S-OFF'ed the phone and changed the CID to HTC__001 and all the way down the list because I keep getting the error "FAILED (remote: 41 model id check fail)". No matter which CID I give the phone or if I attempt to update for a device with S-ON or S-OFF.
Not really sure what else to try at this point as I've searched here and all over Google. I didn't want to bother you guys with it but I don't know where else to go.
Thanks for any help in advance.
Click to expand...
Click to collapse
Unless I'm missing something, you don't need to update hboot to use JB ROMs. I never did and I've been using Sense and AOSP jellybean ROMs for the past 7 months or so.

RollTribe said:
Unless I'm missing something, you don't need to update hboot to use JB ROMs. I never did and I've been using Sense and AOSP jellybean ROMs for the past 7 months or so.
Click to expand...
Click to collapse
Really? Everything I read today mentioned the need to update hboot. My concern is being able to recover from it if it fails.

Yeah there's no need to update anything, just flash a jb rom from recovery. Once you have s-off hboot version kinda becomes moot
Sent from my HTC One X using xda premium

That model Id check fail is because your trying to flash a rom for the wrong phone.
Your lucky that's happening because usually it just bricks.
I should probably add that some people cannot boot newer JB Roms without updating hboot but that is not always the case and I still have no idea why it is so for some.

Yeah I should've asked... Do you have dual or quad core One X?

exad said:
That model Id check fail is because your trying to flash a rom for the wrong phone.
Your lucky that's happening because usually it just bricks.
I should probably add that some people cannot boot newer JB Roms without updating hboot but that is not always the case and I still have no idea why it is so for some.
Click to expand...
Click to collapse
I hadn't even gotten to the step to flash the ROM at that point. It was just for the hboot.
Anyway, got it sorted now. Thanks for the help everyone.

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