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.
Related
So I am as excited as everyone else about s-off. Been waiting for awhile, but in the haste of everyone rooting their phone, I haven't been able to find a thread about restoring s-on in case of warranty work. Have I over looked something?
lots of views but no comments. This is from the IRC if interested
<splayer7> sorry if this has been asked, but what about resuming s-on for warranty work?
<hyuh> splayer7: no, not available
splayer7 said:
lots of views but no comments. This is from the IRC if interested
<splayer7> sorry if this has been asked, but what about resuming s-on for warranty work?
<hyuh> splayer7: no, not available
Click to expand...
Click to collapse
Exactly what has been said. There is no unrooting or S-On restoring at this time. I would just wait if you haven't already. HTC Released their source codes today. Its only a matter of time before an easier root is available with unroot, and S-on.
Was told that we could s-on by running the RUU. Here's a link to some I've found but haven't tested any of this. http://droidangel.blogspot.com/2011/06/htc-sensation-ruushipped-roms-packaged.html
kevinliu2336 said:
Was told that we could s-on by running the RUU. Here's a link to some I've found but haven't tested any of this. http://droidangel.blogspot.com/2011/06/htc-sensation-ruushipped-roms-packaged.html
Click to expand...
Click to collapse
do we have any confirmation on this working correctly
Tried it, resets your ROM but doesn't reset s-off
Guys.. There is about a 25% chance at best that HTC will actually check the boot loader status before providing warranty service. Even if you are unlucky and they do, if you make enough noise they might make an exception and let you off the hook. I think that as long as the issue that you are trying to resolve isn't a direct result of s-off or root, it should be fine.
splayer7 said:
So I am as excited as everyone else about s-off. Been waiting for awhile, but in the haste of everyone rooting their phone, I haven't been able to find a thread about restoring s-on in case of warranty work. Have I over looked something?
Click to expand...
Click to collapse
Flash an official RUU, and the device will be S-ON! TESTED!
lge73 said:
Flash an official RUU, and the device will be S-ON! TESTED!
Click to expand...
Click to collapse
Are you sure man? Somebody else above tested and found the opposite..
If the ruu is left untampered with, the boot image will be replaced with a stock one. Boot image is where your s-off lives. So in theory it should without a doubt work. You just have to make sure the boot image is in the ruu
smoochiezz24 said:
If the ruu is left untampered with, the boot image will be replaced with a stock one. Boot image is where your s-off lives. So in theory it should without a doubt work. You just have to make sure the boot image is in the ruu
Click to expand...
Click to collapse
I used the rom.zip file included in an untouched RUU, and I checked it includes HBOOT, also saw version change when I went into HBOOT.
It does NOT reset S-OFF back to S-ON.
I dont know if when you flash it reads S-OFF so keeps it, for users who genuinely had S-OFF?
I have personally tested this, and can confirm that using HTC's stock RUU does not return the phone to S-ON. However, it did remove the top area that says revolutionary, so now it appears as though I have a factory S-OFF device
Sent from my HTC Sensation 4G using XDA App
bummer.. I really hope there is a way to reverse s-off, just in case. but then again, I do have insurance so I guess I could say it was 'stolen' if I really need to get it replaced
prank1 said:
For those worrying about warranty issues..
You can try flashing the correct RUU for your phone.
IF that doesn't get rid of -revolutionary- s-off, then you can flash the ENG HBOOT (which gets rid of -revolutionary- but gives you ENG S-OFF) then you can flash the correct RUU for your region (which will definitely get rid of ENG S-OFF, and make you official stock HBOOT S-ON)
Click to expand...
Click to collapse
Try flashing ENG HBOOT, then the RUU afterwards.
I am going to try to get my phone back to S-ON now, just to test everything
EDIT
Hmm, very odd indeed, after flashing the RUU I have 'stock' Radio S-OFF (no -Revolutionary-) , I tried fastboot oem write secuflag 1 and fastboot oem writecid HTC__001 but I am still Radio S-OFF.
Just so people know, flashing full RUUs, even HBOOTs do NOT get rid of Radio S-OFF. Thats why it is favored by people, it can only be turned S-ON specifically by tools which may be released for the Sensation in the near future. I thought these tools only sent the commands that I tried to change the Radio security status. It would appear not.
However
There is no need to worry, Radio S-OFF probably won't void your warranty (if you sent it to a HTC repair center), as long as you have the correct CID and ROM installed you should be fine.
If I remember correctly, with the past Android phones, some people randomly got S-OFF (like sensation users did) out of the box. The HTC repair center didn't care. They don't like custom ROMs, custom HBOOTs, rooted ROMs, etc
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.
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.
i have read for hours and tried anything and everything pleas help
I have a att htc one x firmware 2.20 i unlocked bootloader and rooted with hansons tool kit then i went to flash rom in looking back i did incorrectly but bottom line now is i lost all data as far as stock configs and backups so i lost perm root and now i can flash roms but do not take just does recovery bootloop i can still boot into fast boot and enter twrp recovery and can mount ect but since i dont have perm root no roms will boot i caint get into phone to turn debugging on and my cid was cws__oo1 then i got su cid that was chanced when i tried to use toolkit for installing jelly bean and change the hboot its now set at htc__621 so i can not install custom rom becouse no perm root i cant get perm root couse i cant enable debugging i cant flash ruu becouse i get error 131 becouse my cid is not stock any longer i cant push or pull from adb shell becouse device not found i am a noob and yea i screwd up but i have learned alot about what not to do i hope someone canhelp me with a option i was thinking maby i could install ruu for cid__621 buti belive its tided to the endeavor not the evita....please help
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Who is telling noobs to change their CIDs to Endeavor? Is there some malicious youtube tutorial floating around? This is the second one today.
iElvis said:
Who is telling noobs to change their CIDs to Endeavor? Is there some malicious youtube tutorial floating around? This is the second one today.
Click to expand...
Click to collapse
no one the tool kit did it automaticaly to update hboot so i could install jelly bean nowi caintchange it back to flashstk ruu
rootmyhtc said:
no one the tool kit did it automaticaly to update hboot so i could install jelly bean nowi caintchange it back to flashstk ruu
Click to expand...
Click to collapse
What tool kit? There is no tool kit for installing JB on this phone, nor any need of one. You must have used something for the Tegra 3 International One X, which is why your phone is now screwed up. You can't use the '621 ruu because that's for a different phone.
Can you get into recovery? You might try and see if you can switch your CID back with Hanson's toolkit.
iElvis said:
What tool kit? There is no tool kit for installing JB on this phone, nor any need of one. You must have used something for the Tegra 3 International One X, which is why your phone is now screwed up. You can't use the '621 ruu because that's for a different phone.
Can you get into recovery? You might try and see if you can switch your CID back with Hanson's toolkit.
Click to expand...
Click to collapse
yes i can and i did try to push super user and per root but debugging is off so it does not see device thanx in advance for any help
Second person in 1 day trying to change their CID to that of the Tegra3 One X. Of course, that is the wrong device, and it can only end poorly. What gives???
http://forum.xda-developers.com/showthread.php?t=2100232
redpoint73 said:
Second person in 1 day trying to change their CID to that of the Tegra3 One X. Of course, that is the wrong device, and it can only end poorly. What gives???
Click to expand...
Click to collapse
No idea. I looked over in the endeavour forums, and even those tutorials said no, you can't change your CID to run a different RUU. It must be some noob hack floating around out on the web.
I don't understand why people are so obsessed with installing jelly bean that they throw all caution out the window. I don't really feel all that much difference between my N7 and my still-on-ICS evita.
iElvis said:
I don't understand why people are so obsessed with installing jelly bean that they throw all caution out the window.
Click to expand...
Click to collapse
Just as baffling is that these folks know enough or have researched enough to be able to change their CID, but not enough to know that they are installing a ROM for the wrong device (and changing to the CID for the wrong device).
redpoint73 said:
Just as baffling is that these folks know enough or have researched enough to be able to change their CID, but not enough to know that they are installing a ROM for the wrong device (and changing to the CID for the wrong device).
Click to expand...
Click to collapse
Unbelievable... Like I said in the other thread. That was 2 people in a row yesterday.... Where are these noobs getting there half a$$ info from... Lol
Sent from my HTC One XL using Tapatalk 2
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