Database Info

[Q] Differences between hboots 1.06, 1.09, 1.13, and 1.14?

So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.

byliu88 said:
So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.
Click to expand...
Click to collapse
1.06, flash the new radio seperately once your on 1.06.

usaff22 said:
1.06, flash the new radio seperately once your on 1.06.
Click to expand...
Click to collapse
Thanks for the info, which radio is that though?

<here you go mate, http://d-h.st/XBu it was posted on this forum by torx, i think , it's a flashebel zip. with aroma installer so just folow the instructions

alexskin said:
<here you go mate, http://d-h.st/XBu it was posted on this forum by torx, i think , it's a flashebel zip. with aroma installer so just folow the instructions
Click to expand...
Click to collapse
Alright I'll try it out. thanks!

byliu88 said:
So I successfully downgraded from hboot 1.14 to 1.06, and used the TMOUS 1.53 RUU to restore it, but now I am curious as to what the major differences and incompatibilities each hboot has. Since I was on 1.14 I understand that that one had more restrictions and broke wi-fi on some roms. Which hboot would be "best" for 3rd arty roms and overall usage? I'm asking this partly because even with hboot 1.06 wi-fi was still too buggy for use on CM10.
Click to expand...
Click to collapse
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.

HD Case said:
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.
Click to expand...
Click to collapse
He probably used the instructions in the development section:
http://forum.xda-developers.com/showthread.php?t=1990043

Kamilr97 said:
He probably used the instructions in the development section:
http://forum.xda-developers.com/showthread.php?t=1990043
Click to expand...
Click to collapse
Thanks,
Yikes! Now I see why a lot of people don't even attempt this

I have also downgrade my hboot back to 1.06 and my wifi is also buggy i hope there is a solution for
Maybe i must go back to stock but i dont know if my wifi then is fix

fjjfrank said:
I have also downgrade my hboot back to 1.06 and my wifi is also buggy i hope there is a solution for
Maybe i must go back to stock but i dont know if my wifi then is fix
Click to expand...
Click to collapse
I downgraded from 1.14 to 1.06 too, installed 1.53 RUU and then experienced wifi issues on Trickdroid 8.
I had to flash "extra partitions" to make it work. Seems to be some partitions required for wifi to work on versions based on latest sense kernels.
I flashed extra partitions 2.35 and wifi did not work. Then I flashed 1.84 and wifi on Trickdroid 8 would connect, but from time to time (very frequently every 15 seconds on average) disconnect and reconnect, randomly (was annoying and killing my battery). I moved to trickdroid 7 TMOUS version and wifi works perfectly, never disconnects.
(My phone was from T-Mobile)
Here are the links, taken from this post: http://forum.xda-developers.com/showthread.php?t=1657831&page=271
2.35 Extra Partitions
https://www.dropbox.com/s/7gtuvbynr3...rtitions.zip?m
1.84 Extra Partitions
https://www.dropbox.com/s/mmjcqisgoo...rtitions.zip?m
NOTE: On CM rom I never had issues even without flashing extra partitions, and even when I was on hboot 1.14.
Hope this helps,
Regards,
Diego
---------- Post added at 07:57 PM ---------- Previous post was at 07:51 PM ----------
And regarding the topic from this post, hboot is like the BIOS of the phone. You gain nothing from upgrading it, only gain restrictions from 1.13 and above. So as far as I read it is better to stick to 1.06
Regarding the procedure to downgrade, for the one that asked, it can make you panic on the step when you upload hboot 1.06. For me, it failed 3 times, and I had to go to work after third time with a "bricked" phone -.-
But I came back, tried from my laptop instead of my PC, and worked on the first attemp!. Seemed to be my PC USB not working properly or not being fast enough/not having enough power, who knows.
It seems scary but is fairly straight through, the procedure is perfectly detailed. Did it from an Ubuntu 12.04 live image.
Regards,
Diego

HD Case said:
I wonder if you could please explain how you were able to downgrade. I heat tons of conflicting info on this.
Thanks in advance.
Click to expand...
Click to collapse
Yes, I used the guide Kamilr mentioned. It was fairly nerve wracking but if you carefully read all of the instructions and get an idea of what your doing it goes pretty smoothly. Same with sperad, flashing the hboot itself failed for me 3 times, but all you had to do was reboot and retry. But anyways regarding the wifi issue. flashing the new radio did not seem to alleviate anything, but I flashed viperOneS and wifi now works fine, so I plan to stay with it.
@fjjfrank Try relocking your bootloader, then running your RUU http://d-h.st/users/agentc13/?fld_id=2293#files (if you're on tmobile its 1.53, im not sure about the other networks), which'll bring you back to stock. Wi-Fi worked perfectly on stock when I tried that after downgrading to 1.06. If its good from there you can try what i did and unlock your bootloader again and flash viperOneS which worked for me.

byliu88 said:
Yes, I used the guide Kamilr mentioned. It was fairly nerve wracking but if you carefully read all of the instructions and get an idea of what your doing it goes pretty smoothly. Same with sperad, flashing the hboot itself failed for me 3 times, but all you had to do was reboot and retry. But anyways regarding the wifi issue. flashing the new radio did not seem to alleviate anything, but I flashed viperOneS and wifi now works fine, so I plan to stay with it.
@fjjfrank Try relocking your bootloader, then running your RUU http://d-h.st/users/agentc13/?fld_id=2293#files (if you're on tmobile its 1.53, im not sure about the other networks), which'll bring you back to stock. Wi-Fi worked perfectly on stock when I tried that after downgrading to 1.06. If its good from there you can try what i did and unlock your bootloader again and flash viperOneS which worked for me.
Click to expand...
Click to collapse
oke thanks
i am from the netherlands and i have got a unbranded one s
witch hboot can i install without updating my bootloader

Can't flash Radio

I am on stock T-Mobile rom:
Android version 4.0.4
HTC Sense version 4.1
Software number 2.35.531.7 710RD
HTC SDK API level 4.23
HTC Extension version HTCExtension_403_1_GA_20
Kernel version [email protected]#1
Baseband version 1.08ts.50.02.16_10.08e.50.04L
Build number 2.35.531.7 CL96068 release-keys
Browser verion WebKit/534.30
I want to flash a new radio since the version I have the signal keeps dropping and I cannot flash any radio. I am rooted, I go to TWRP and successfully flash a different radio but when I check the settings again it still say 1.08ts. I even tried an older RUU but it keeps failing. I do not want to flash another countries RUU since I'm afraid it will brick it.
Is there away to change just the radio?

There is a universal radio flasher in the dev section.
Sent from my HTC One S using xda app-developers app

bstylz911 said:
There is a universal radio flasher
Click to expand...
Click to collapse
..but you have to be on a low hboot (1.06 or 1.09) or s-off for that. On sense ROMs anyway.

so that means I would have to wait until a newer RUU comes out?

princeferoz said:
so that means I would have to wait until a newer RUU comes out?
Click to expand...
Click to collapse
I would S-Off the device and then flash the radio installer.
That way you can quickly and easily try a bunch of different radios.

what rom are you on
when you say ck settings, are you talking about Phone/Settings/About Phone
i would have to re-read the OPs on the cm and sense radio installer, but thought with them you could be on a higher hboot, since radio is put into system partition and bypasses htc restrictions. may be wrong--
i did some reading but no time to read all. you need to read them for yourself. talking about the cm and sense radio installer threads
my understanding is with cm rom and cm radio installer you can flash radio if above .09 hboot. it puts radio in system
with sense it puts it to phone. but there was a temporary installer that put it into system and could be used with higher hboots.
don't know if that installer is still available for dl from tecardo
some reading and a nandroid advised as i have no time to read both threads

princeferoz said:
so that means I would have to wait until a newer RUU comes out?
Click to expand...
Click to collapse
Just s off. Its not as hard as it looks.
I'm on hboot 1.14 and s offed. Glad I did
Sent from my HTC One S using xda app-developers app

Thanks for all your help. I was able to get S-Off and flashed a new radio but the radio still keeps fluctuating.

princeferoz said:
Thanks for all your help. I was able to get S-Off and flashed a new radio but the radio still keeps fluctuating.
Click to expand...
Click to collapse
am pretty sure you flashed the radio properly the first time but fail to check radio version on fastboot since it doesn't show correct radio on settings>"about phone" (known bug)

the radio flashed properly and it shows the correct radio in settings but the signal still fluctuates.

confused, can I get some clarification on this?

ultimate goal is to run the latest 4.2.2 rom from Magio without the reboots and data loss. So from what I understand I need to update the fw. Therfore I need S-Off and Super CID. Can I use the X-Factor Exploit to get Super CID while on 1.09 or do I need to get to 2.2. If so, how do I get to 2.2? I'm sure I have more questions but that's my first hurdle. Any assistance is appreciated and kudos will be given. Thanks

What's the status of the phone? Have you done anything to it or did you just get it and also what firmware are you on?
Sent from my HTC One XL using XDA Premium 4 mobile app

If that's under build number is 5.08.111 and I'm currently running magio rom 4.0.2.

No, he's asking for your bootloader details, can you post them please? Also, is your phone an at&t model?
Sent from my Evita

Yes it's at&t. I don't see something that says firmware but here is the info it does give me.
Evita PDT Ship S-On RL
Hboot 1.09
Radio 0.24p.32.09.06
Opendsp v34.1.0.45.1219
I thought that the fw version was usually found in the software version in settings>about but mine just says magio 4.0.2

djlobes said:
Yes it's at&t. I don't see something that says firmware but here is the info it does give me.
Evita PDT Ship S-On RL
Hboot 1.09
Radio 0.24p.32.09.06
Opendsp v34.1.0.45.1219
Hope that helps. Thanks
Click to expand...
Click to collapse
Did u flashed newer radio?....coz I use old radio + 1.09 hboot work fine for me ...no signal drop and no wifi issue.....with stock kernel from Magio ROM btw I used 1.89 radio ....0.18
Swyped from T3DRO1CS RedHoXence

It's standard procedure to give as much information as possible when asking a question here, that includes bootloader details. The info you gave wasn't the firmware by the way, that's just ROM information, when someone is asking for firmware version they're asking for bootloader details.
Anyway, you basically have two options:
You can leave your firmware as it is and flash the Beastmode kernel which should stop your signal loss and reboot problems. You're s-on but luckily you're on hboot 1.09 so you'll have no problems flashing kernels in recovery (anyone with s-on and hboot greater than 1.09 needs to flash the boot.img via fastboot for ROMs and kernels).
The other option is to get s-off and upgrade your firmware to the 2.15 version.
My suggestion would be to flash the Beastmode kernel first, if that doesn't work then move on to upgrading your firmware.
The fact that your phone is an at&t model almost certainly means you have SuperCID. If you want to check though you can give the following fastboot command:
Code:
fastboot oem readcid
If it comes back as 11111111 you have SuperCID, if it comes back as CWS__001 you don't.
Sent from my Evita

Thanks to both of you. I just flashed beastmode 3.5 and 1.85 radio. I'll see if that helps.

djlobes said:
Thanks to both of you. I just flashed beastmode 3.5 and 1.85 radio. I'll see if that helps.
Click to expand...
Click to collapse
I used old radio with stock kernel that came with the ROM.......different phone different place make it different.....u can try flashing beastmode kernel like timmaaa said if doesn't work
Swyped from T3DRO1CS RedHoXence

The radio alone probably won't fix signal drops. There are some lucky people that it works for though.
Sent from my Evita

djlobes said:
Can I use the X-Factor Exploit to get Super CID while on 1.09 or do I need to get to 2.2. If so, how do I get to 2.2?
Click to expand...
Click to collapse
I think you are confusing build numbers and hboot versions. For the AT&T version:
Build 1.73 and 1.85 = hboot 1.09
Build 2.20 = hboot 1.14
Build 3.18 = hboot 2.14
I believe the facepalm s-off should work with any hboot. Really getting SuperCID is the main hurdle (seems to be most problematic). S-off is very easy after that.
---------- Post added at 02:28 PM ---------- Previous post was at 02:24 PM ----------
ted77usa said:
Did u flashed newer radio?....coz I use old radio + 1.09 hboot work fine for me ...no signal drop and no wifi issue.....with stock kernel from Magio ROM btw I used 1.89 radio
Click to expand...
Click to collapse
Did you ever have signal drops? I don't think everyone necessarily had signal drops with Sense 5. And if you did, I wouldn't think flashing an older radio would fix it (as timmaaa suggests).

redpoint73 said:
I think you are confusing build numbers and hboot versions. For the AT&T version:
Build 1.73 and 1.85 = hboot 1.09
Build 2.20 = hboot 1.14
Build 3.18 = hboot 2.14
I believe the facepalm s-off should work with any hboot. Really getting SuperCID is the main hurdle (seems to be most problematic). S-off is very easy after that.
---------- Post added at 02:28 PM ---------- Previous post was at 02:24 PM ----------
Did you ever have signal drops? I don't think everyone necessarily had signal drops with Sense 5. And if you did, I wouldn't think flashing an older radio would fix it (as timmaaa suggests).
Click to expand...
Click to collapse
I still used 1.89 radio+1.09 hboot....work fine same as before.....plus now i'm using beastmode v2 and is ok too .... I think radio work better with build release.....for example ATT 1.85/1.82 radio with 1.85/1.82 build ....1.89 telstra radio with telstra build 1.89 or maybe sense 5 good with 5.08 radio with 5.08 Germany build( I will try this later on ) to match radio+ril on build version
Swyped From BlueICESense_HoXatt

ted77usa said:
I still used 1.89 radio+1.09 hboot....work fine same as before.....plus now i'm using beastmode v2 and is ok too .... I think radio work better with build release.....for example ATT 1.85/1.82 radio with 1.85/1.82 build ....1.89 telstra radio with telstra build 1.89 or maybe sense 5 good with 5.08 radio with 5.08 Germany build( I will try this later on ) to match radio+ril on build version
Click to expand...
Click to collapse
You seem to be contradicting yourself, so I'm not quite sure what you are trying to say.
The 1.31 baseband that came with 5.08 will work best for most people, since the signal drop issue seems to be caused by older radios being incompatible with the Sense 5 power save feature. And yes, using the radio and RIL that is intended for the ROM is often (but not always) the best option. Although some people have complained about power reception with the 1.31 radio, and better reception by flashing an older radio (as always, the "best" radio is very location specific, and no single radio works best for everyone).
Its still not clear from what you are saying whether you actually suffered the signal drop issue, or not. But it seems like you are saying you never had the issue to begin with. Not everyone suffers the signal drop issue. If you didn't suffer the issue on the older radio, then it may simply not apply to you (location or reception dependent, is my guess). And flashing Beastmode wouldn't make a difference either.
If you didn't have the issue to begin with, flashing a new radio or kernel isn't going to make a difference. If you are not sick in the first place, taking medicine (even the wrong one) isn't going to make a difference. You will still not feel sick.

redpoint73 said:
You seem to be contradicting yourself, so I'm not quite sure what you are trying to say.
The 1.31 baseband that came with 5.08 will work best for most people, since the signal drop issue seems to be caused by older radios being incompatible with the Sense 5 power save feature. And yes, using the radio and RIL that is intended for the ROM is often (but not always) the best option. Although some people have complained about power reception with the 1.31 radio, and better reception by flashing an older radio (as always, the "best" radio is very location specific, and no single radio works best for everyone).
Its still not clear from what you are saying whether you actually suffered the signal drop issue, or not. But it seems like you are saying you never had the issue to begin with. Not everyone suffers the signal drop issue. If you didn't suffer the issue on the older radio, then it may simply not apply to you (location or reception dependent, is my guess). And flashing Beastmode wouldn't make a difference either.
If you didn't have the issue to begin with, flashing a new radio or kernel isn't going to make a difference. If you are not sick in the first place, taking medicine (even the wrong one) isn't going to make a difference. You will still not feel sick.
Click to expand...
Click to collapse
Well, what I'm trying to say is that I don't have issue with signal and wifi on sense 5 Rom.... since I'm still using older radio ......I thought might help other to understand to try using older radio if they have issues.....but like u said it depend on their location it self......and they just need to try it them self.....
Swyped From BlueICESense_JBE

..... Do you play ingress?
Sent from my One X using Tapatalk 4

Beastmode Kernel Bootloop?

Hi guys,
I've looked everywhere and I cant find how to solve this problem. I have a One XL running ViperXL 4.20 with S-on and hboot 1.14. I have been trying to install the Beastmode Kernel 3.5 reloaded but when I do I get a bootloop. Ive tried installing the 2.0 version first and I still get a bootloop. I really need this kernel to solve my cell signal drops and random reboots. Can anyone help?

If you can't get Beastmode to work, why don't you get s-off and update to the 2.15 firmware. S-off is a good thing to have anyway.
Sent from my Evita

man im totally out of date...ill try those things and beastmode again perhaps?

lilballer151 said:
man im totally out of date...ill try those things and beastmode again perhaps?
Click to expand...
Click to collapse
If i may even i had that problem with Beastmode.. ( i so wanted it )I was on 2.15 and S-OFF i had to bother Timma and Redpoint many a times with all of my quetions... I tried Twice.. still had no success....
so i would suggest you give Elemental X 8.3.2 a try..
it does have almost all the features of Beastmode 3.5... and like Beastmode it does come with Aroma installer and so u can configure your setting during installation...
P.S this kernel does give a good battery and my benchmarks were good ( i am on vanilla):good:

Elemental kernel won't solve the signal drops and reboots on its own though, only in conjunction with the firmware update.
Sent from my Evita

thanks for the info, so is there a certain way I can stop the celldrop and reboots to happen? its really getting on my nerves

See my post above.
Sent from my Evita

Sorry to keep asking but how do I go about updating my hboot?

Go to Turge's stock Sense 5 ROM thread in the development section, the download and instructions are in the first post.
Sent from my Evita

Same problem
timmaaa said:
Go to Turge's stock Sense 5 ROM thread in the development section, the download and instructions are in the first post.
Sent from my Evita
Click to expand...
Click to collapse
Ive been having same problem on my onex evita , Im on hboot 1.14 with s - on ive tried the facepalm method to s-off but its not working therefore theres no way i can upgrade my firmware. The random reboots and signal drops are quite frustrating. I even tried to revert back to my previous viper xl version 3.XX through the backup i made but unfortunately after the restore the device would boot for 5 seconds and then reboot itself leaving me no option but get back to 4.2.0 with signal drops and couple of reboots . Beastmode would take the device into bootloops pls help me resolve this situation.

All you need to do is work out why s-off isn't working. There's no reason for it to not work, you just need to troubleshoot it.
When you restored your previous backup did you flash the boot.img via fastboot?
Sent from my Evita

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