Question about S-off - One (M7) Q&A, Help & Troubleshooting

I did S-off with revone when it initially came out. I have since flashed many firmware and I am currently running on the 3.18 base with the hboot that comes with it. My phone still says S-off and I can still flash custom firmware. I was wondering if the S-off is still kept through flashing newer hboots. I believe it is because custom firmwares still work but a little insight about this. Thanks.

Your phone will be always in S-OFF...
But if you want, you can port it in s-on

chuckado said:
I did S-off with revone when it initially came out. I have since flashed many firmware and I am currently running on the 3.18 base with the hboot that comes with it. My phone still says S-off and I can still flash custom firmware. I was wondering if the S-off is still kept through flashing newer hboots. I believe it is because custom firmwares still work but a little insight about this. Thanks.
Click to expand...
Click to collapse
As a practical matter, it is impossible to "lose" s-off. You either have to manually reset the flag in fastboot, or overwrite the partition where the flag lives with an img from an s-on phone.
It's theoretically possible for HTC or a carrier to push out an OTA that resets s-off, but they would never do this because of the bricks that would result.

Related

[Q] going to stock fail... need 2.24.401.1 nandroid

I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!
+1
Are you s off?? Downgrade your hboot to 1.44 and then flash the ruu for your device....
Sent from my HTC One using xda premium
No unfortunately im s-on... Funny how being a good boy and being s-on HTC rewards me with no option to go back to stock...
Sent from my HTC One using xda app-developers app
LOL............ I am in same postion . want to go back to stock for updates but cant !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app
ipmanwck said:
You cant s-off on hboot 154 yet. Unless I am mistaken.
Like op says we need a nandroid of firmware think that's only way until ruu is releasee ; (
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
2 things:
1) I'll quote what I said, I never said S-Off was available .. "Obviously you'll need S-Off for Hboot 1.54 if/when it happens"
2) What I said above for going to stock is a way of doing it, a Nandroid is not the only way.
AllAboutTheCore said:
http://forum.xda-developers.com/showthread.php?t=2224752 ... Flash ROM, install stock recovery, relock bootloader, done. The official firmware will be about soon no doubt so you will be able to fastboot it and have the newest base, stock and all before HTC release it in whatever region.
Obviously you'll need S-Off for Hboot 1.54 if/when it happens in order to remove the tampered flag and change relocked back to locked but what I mentioned above is the closest you'll get without being able to run an RUU.
Click to expand...
Click to collapse
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app
ossman said:
I actually did this and Im running it right now without problems...
But Im not sure id be getting OTAs as the bootloader main ver still says 2.24.401.1 and not 2.24.401.8. I dont think Mike made a 2.24.401.1 available.
Its a bit disappointing. Im fine with having my bootloader tampered and relocked and s-on as long as I got stock running like it should be. i dont understand why HTC gives you the option to unlock ur bootloader to play around with custom firmware but not allow you to go back to stock. im guessing the RUU is on the way but I have my doubts... Just like s-off.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Nah, the stock firmware for 2.24.401.8 is not available yet, only a customised one which would require S-Off anyway. The method I mentioned is the only way at the moment to get as close to stock as possible without being able to go S-Off and flash an older RUU. When Mike gets hold of the stock firmware to post, I'm sure he will ... I can't see any 2.24 RUU's being available seeing that HTC are pushing for a 4.3 release by the end of September, so I'd wait anyways, unless you need to return your device for warranty purposes of course.
As for you getting OTA updates ... I haven't installed the .8 ROM but it shouldn't affect it as the base you are on is still an older base than what you'd be trying to update to but I'm not 100% on that as I haven't flashed it as my device is away for repair lol. I would imagine that the 2.24.401.8 firmware would be about soon enough and then you would be able to revert to stock with the newest base but obviously as you said yourself, without S-Off you wouldn't be able to wipe any trace of you flashing and modding.
I think HTC only allow you to unlock your bootloader because they can void so many warranties that way and bill for repairs lol ... Maybe I'm being cynical but I do agree that they could provide a stock RUU for people to return to stock, without all the hassle of S-Off or waiting months before any suitable RUU is available but sometimes you have to just suck it up and live with what we have lol
ossman said:
I got myself in a bit of a dead zone here.
I have my HTC one. Its HTC__001 WWE Europe. It OTA upgraded to 2.24.401.1.
When I saw that you can convert to a GPE I really wanted to check it out specially after users reported success in getting OTA updates. But I quickly realized I needed S-Off and thats not available yet.
I decided to at least take it to a test drive with ARHD GPE 3.0. I downloaded the latest RUU for my device (1.28.401.7) thinking I would need that to get back to stock. I went and unlocked the bootloader at HTC dev. Flashed CWM recovery and flashed ARHD GPE 3.0. Played around with it for a bit and now when I needed to go back to stock.
RUU.exe file got stuck at updating signature then returned 155 unknown. I realized maybe its attempting to downgrade the bootloader so i looked around for a 2.24.401.1 RUU but its not available yet.
I looked at Nandroid backups and found 1.28.401.7 HTC__001 but its UK unbranded. When I restored this version it loaded up but my touch screen didnt work at all. I flashed back ARHD to get touch capability back.
So my question is... Any chance anyone can nandroid backup the stock 2.24.401.1 i need? How can I go to stock now? Am I stuck with custom roms untill atleast s-off or HTC decides 2.24.401.1 RUU should be made available?
Thanks!
Click to expand...
Click to collapse
i got an nandroid backup for you fully stock unrooted : https://mega.co.nz/#!AUZGkKwC!EAfhUXYAgjpAR42jGzG_mhzWJjwcs1j7R_tm_HPMDAo

[Q] rooting and return to stock without S-Off

Hi everyone,
I recently switched from my Galaxy Nexus to the HTC One. Coming from a nexus device, the general rooting procedure seems to be a bit more complicated on the one. After browsing the web for a few hours, a couple of things are still not completely clear and I would appreciate any help as I do not intend to break a recently bought 550€ device So thanks in advance.
Rooting, flashing roms and kernels, and installing a custom recovery works after unlocking the device with htcdev.com. I do not need S-Off for those things. Is this correct?
When it comes to returning the device to stock for let's say, a warranty-related issue, is this also possible with S-On? If this is the case, how would I do that as I mostly found guides to return to stock that require S-Off? I'm currently on hboot 1.54 so S-off is not an option right now.
Also, if I lock the bootloader again (which should work with fastboot oem lock I assume?) I read somewhere that it will say Relocked instead of Locked. Out of experience, would this be a problem if I need to send the device in?
Tl;dr: Rooting, flashing roms and kernels, installing a recovery is possible after unlocking the bootloader with htcdev.com. Can I also return the device to stock if I need to send it in with S-On or does that require S-Off?
Thank you.
Any help is appreciated.
All the rooting, etc. can be done with just an unlocked bootloader. It's the downgrading that required S-OFF
EddyOS said:
All the rooting, etc. can be done with just an unlocked bootloader. It's the downgrading that required S-OFF
Click to expand...
Click to collapse
That's quite pleasant news, thank you. Can I also return it to stock for warranty-related issues with S-on? And what do you mean with downgrading and why would I do that?
As there is no RUU available for anything over 1.29.401.16, being S-OFF gives the option of using an older RUU to get the phone back to 100% stock and then you can get the OTA updates to get to the latest version again. If you're S-ON you can only restore a nandroid backup (which I would say a million times to do before flashing a new ROM), restore the stock recovery and then relock the device
b0ld said:
That's quite pleasant news, thank you. Can I also return it to stock for warranty-related issues with S-on? And what do you mean with downgrading and why would I do that?
Click to expand...
Click to collapse
Well first thing you should do when you unlock your bootloader is do a nandroid backup of your stock rom. that way you can flash it back if you ever want to return to stock; so you won't need to look endlessly for an RUU or other backup, which may or may not exist.
However, once you do unlock and install custom recovery your bootloader will say:
*** UNLOCKED ***
*** TAMPERED ***
and if you re-lock your bootloader, it will only go back to *** RELOCKED ***, it will never go back to *** LOCKED *** (unless you're S-Off with revone)
I'm not sure about the TAMPERED, as there are some conflicting reports, some say TAMPERED will go away once you flash stock recovery, and others say it will not go away.
So for warranty issues it really depends on your country and/or repair center, some will "overlook" the unlocked/relocked status if it's a hardware defect and either repair or send you a new one, but then again there are some that will blame the fault on you, saying that unlocking and flashing custom roms was the cause of the malfunction.
We don't have warranty where I live so I can't really help there. You could post your carrier and country, and see what other people have experienced.
Thank you all, this has been really helpful. What happens in case I brick my device while having S-On? Would you say that S-off is really important or doesn't it really matter at all if I don't care for OTA updates? And can I obtain S-Off if I am already rooted and on a custom Rom if it should ever be available for hboot 1.54?
I'll post my information as you suggested.
Country: Austria
Carrier: 3, but I don't think that matters as I bought the device unlocked.
b0ld said:
Thank you all, this has been really helpful. What happens in case I brick my device while having S-On? Would you say that S-off is really important or doesn't it really matter at all if I don't care for OTA updates? And can I obtain S-Off if I am already rooted and on a custom Rom if it should ever be available for hboot 1.54?
I'll post my information as you suggested.
Country: Austria
Carrier: 3, but I don't think that matters as I bought the device unlocked.
Click to expand...
Click to collapse
With S-On you can do pretty much everything (custom ROMs, even Radios). The only thing you won't be able to flash is the firmware. You would either need to find a signed firmware for your CID and MID, or if an OTA comes in your country (which includes newer firmware), you would have to flash back to stock + stock recovery, relock your bootloader, accept the OTA then unlock again and restore whatever custom ROM you were using. (not that difficult)
Anyway, from what I've seen so far, most ROMs are not being dependent on any specific firmware version. Are you already on 2.24 firmware? I think that's the currently official version.
And with S-On, it's very hard to brick your device as you can't mess with the hboot which is the main reason for bricks.
Thanks for the quick reply. In this thread it is stated that after flashing s nandroid backup without s-off it might result in problems like the touchscreen not working. (1st post) http://forum.xda-developers.com/showthread.php?t=2358738
Is this always the case?
That is if you flash a 4.1.2-based nandroid when you have the 4.2.2 FW. If you flash your own one (which is why you should ALWAYS make a backup before doing anything else) you should have no issues
What if I flash a 4.3 custom rim and decide to flash my current 4.2.2 stock nandroid?
That'll be fine as you won't be on the 4.3 FW (as you can't flash FW when S-ON)
b0ld said:
What if I flash a 4.3 custom rim and decide to flash my current 4.2.2 stock nandroid?
Click to expand...
Click to collapse
Firmware version is not tied to ROM version, even if you run a 4.3 ROM, your firmware will still be 2.24 (from 4.2.2). And since you're S-On you can't flash any unsigned firmware. So no worries.
EDIT: EddyOS was faster
That's good news.
Why would I need a newer firmware then (probably noob question)? Would it also be possible to flash the official htc stock 4.3 rom with sense once it's released? And is it possible to get s-off once the bootloader is unlocked etc.?
If i understand correctly, even with s-on I can do pretty much anything, and if I should screw up something, flashing my nandroid backup will resolve it?
b0ld said:
That's good news.
Why would I need a newer firmware then (probably noob question)? Would it also be possible to flash the official htc stock 4.3 rom with sense once it's released? And is it possible to get s-off once the bootloader is unlocked etc.?
If i understand correctly, even with s-on I can do pretty much anything, and if I should screw up something, flashing my nandroid backup will resolve it?
Click to expand...
Click to collapse
1- Newer firmware can (should ) have improvements (performance, stability, battery) over previous ones, e.g. the firmware 2.24 showed significant improvement of the touch drivers, but after 2.24 firmware I haven't seen any noticeable remarks from other threads.
2- Once the official 4.3 stock OTA rolls out, you will be able to get it after you restore your phone to stock (ie stock rom from your backup + stock recovery + relocked)
3- You won't be able to get S-Off (even with unlocked bootloader) until a new exploit is found (if ever )
4- with s-on you can flash back your original backup, or any custom rom, kernel, radio. the only thing is your phone will show ***UNLOCKED***/***RELOCKED*** and ***TAMPERED*** in the bootloader.
Thanks again, very informative! One (hopefully) last question (for now), do I have to flash the boot.img seperately when flashing a new rom on the PC with s-on or can I jhst flash the .zip, just like on the nexus?
Boot.img flashes with the ROM as a Nexus does, only the One X needed to flash the boot.img manually after a ROM
b0ld said:
Thanks again, very informative! One (hopefully) last question (for now), do I have to flash the boot.img seperately when flashing a new rom on the PC with s-on or can I jhst flash the .zip, just like on the nexus?
Click to expand...
Click to collapse
boot.img usually comes in the zip of the ROM, no need to flash separately.
EDIT: EddyOS does it again :laugh:
So, long story short: The only thing that's different from the nexus is that the bootloader will say "relocked" or "tampered". I can still receive OTAs as soon as I flash the nandroid backup I made after flashing the custom recovery. I can still switch between 4.2 and 4.3 ROMs if I'd like to. I can basically do anything with S-On besides modifying system files (which I do not intend to). I could even receive the next firmware updates (the ones after the current 2.24) if I restore my nandroid, restore the original recovery image, and relock the bootloader. There are no "real" downsides for me if I stay S-On as I can return everything to stock anyway. Is this correct?
b0ld said:
So, long story short: The only thing that's different from the nexus is that the bootloader will say "relocked" or "tampered". I can still receive OTAs as soon as I flash the nandroid backup I made after flashing the custom recovery. I can still switch between 4.2 and 4.3 ROMs if I'd like to. I can basically do anything with S-On besides modifying system files (which I do not intend to). I could even receive the next firmware updates (the ones after the current 2.24) if I restore my nandroid, restore the original recovery image, and relock the bootloader. There are no "real" downsides for me if I stay S-On as I can return everything to stock anyway. Is this correct?
Click to expand...
Click to collapse
Yep sounds right :good:
If you had S-Off then you could remove the tampered and unlocked/relocked signs, and you could mess around (upgrade & downgrade) unsigned firmwares.
With S-On you have to stick with the official OTAs.
nkk71 said:
If you had S-Off then you could remove the tampered and unlocked/relocked signs, (...)
Click to expand...
Click to collapse
If there should ever be a method of getting S-Off with hboot 1.54, it makes no difference if I root it right now and install a custom rom, as I can relock and restore everything again. Right?

[Q] Just reverted to stock, safe to S-ON?

So my phone was S-OFF, superCID, custom firmware, running ARHD with TWRP recovery. I carried out the procedure to revert to 100% stock, I have a Rogers HTC One but a Rogers RUU doesn't exist, however I was able to get OTA updates after reverting to stock so I'm assuming the hboot, bootloader, recovery, stock ROM are all Rogers based.
However, when reverting to stock, I used an AT&T RUU to go down to 1.26 firmware and then Rogers OTA updates took me from 1.26 to 1.29 to finally 3.22 firmware. Everything at this point is stock and hopefully Rogers based, only modification that remains is S-OFF.
I need to S-ON for warranty purposes, I know how to S-ON, but I was wondering if it safe to S-ON considering I used a non-Rogers RUU to downgrade in the first place. I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
My bootloader is locked, no tampered flag, hboot 1.55, CID is no longer superCID but ROGER001 (specific to my carrier)
Your good
Ali812 said:
So my phone was S-OFF, superCID, custom firmware, running ARHD with TWRP recovery. I carried out the procedure to revert to 100% stock, I have a Rogers HTC One but a Rogers RUU doesn't exist, however I was able to get OTA updates after reverting to stock so I'm assuming the hboot, bootloader, recovery, stock ROM are all Rogers based.
However, when reverting to stock, I used an AT&T RUU to go down to 1.26 firmware and then Rogers OTA updates took me from 1.26 to 1.29 to finally 3.22 firmware. Everything at this point is stock and hopefully Rogers based, only modification that remains is S-OFF.
I need to S-ON for warranty purposes, I know how to S-ON, but I was wondering if it safe to S-ON considering I used a non-Rogers RUU to downgrade in the first place. I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
My bootloader is locked, no tampered flag, hboot 1.55, CID is no longer superCID but ROGER001 (specific to my carrier)
Click to expand...
Click to collapse
If you have changed your CID back to your carrier specific code you should be OK.
However, with the 4.4 update, there have been a few issues with the Bootloader not unlocking again, if you are sending your phone back under warranty for repair or replacement then your good to S-On, if you just want to set S-on for the hell of it (like me) I would hold fire for now.
Its will be your only remaining access to unlock the phone in one way or another.
Ali812 said:
I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
Click to expand...
Click to collapse
Like I said, no bricks involved, but read below too.
zeushacker said:
if you are sending your phone back under warranty for repair or replacement then your good to S-On
Click to expand...
Click to collapse
if he tries to go s-off to s-on on hboot 1.55, then there is a high probability, that after a few reboots "tamper detected - rebooting" -> and the TAMPERED sign is back.
I wrote the guide in a specific order 1, then 2, then 3, etc, because of that reason.
If the OP wants to give it a shot, he can go ahead, maybe the "tamper detected" won't happen; if it does, he will have to s-off using rumrunner, and start the procedure again.
s-on is not needed on waranty, there are always some devices shiped from factory with s-off. my advice is to keep s-off.

What Can I Do With S-ON?

Sorry for this n00b question, but I have never dealt with s-on before. I acquired s-off and was running custom roms no problem, Then, I had to send the phone in to HTC to fix the purple tint camera issue. So, I went full stock and made the mistake of putting it back s-on. Apparently, I can no longer s-off anymore (please correct me if I am wrong!)
So, now I am stuck with s-on and I have already htcdev unlocked my bootloader (in an attempt to s-off which I only later found out I can't do anymore).
How can I still run custom roms and gain root?
Also, if I do those things, will I still be able to go back and get OTA if I wanted to? Like, will I be able to go back to stock to run an OTA update for kitkat if it comes?
Thanks for the help!
SnapplerX said:
Sorry for this n00b question, but I have never dealt with s-on before. I acquired s-off and was running custom roms no problem, Then, I had to send the phone in to HTC to fix the purple tint camera issue. So, I went full stock and made the mistake of putting it back s-on. Apparently, I can no longer s-off anymore (please correct me if I am wrong!)
So, now I am stuck with s-on and I have already htcdev unlocked my bootloader (in an attempt to s-off which I only later found out I can't do anymore).
How can I still run custom roms and gain root?
Also, if I do those things, will I still be able to go back and get OTA if I wanted to? Like, will I be able to go back to stock to run an OTA update for kitkat if it comes?
Thanks for the help!
Click to expand...
Click to collapse
Hi, why can't you S-OFF? Is it due to your updated hboot?
It should be no problem getting S-OFF using rumrunner.
You can get root either by flashing a custom recovery like TWRP which helps you gain root.
Or flash a custom rom like Android Revolution which provides root access after flashing.
If you wan get OTA later on, I believe you have to create a nandroid backup using a custom recovery of your stock
or flash a RUU which requires S-OFF.
Check out the warning in this thread http://forum.xda-developers.com/showthread.php?t=2431515
Also, I confirmed I can't do it because I unlocked the bootloader but rumrunner keeps giving me an error something like "you need insecure bootloader or root su or fu"
That's why I think I can't s-off anymore.
So I'm just looking for steps to run a custom Rom and gain root access with s-on and also what are my limitations with s-on?
Lastly if I needed to, would I be able to get back stock enough to flash ota?
Please delete this post. Accidental double post.
DarkZacky said:
Hi, why can't you S-OFF? Is it due to your updated hboot?
It should be no problem getting S-OFF using rumrunner.
You can get root either by flashing a custom recovery like TWRP which helps you gain root.
Or flash a custom rom like Android Revolution which provides root access after flashing.
If you wan get OTA later on, I believe you have to create a nandroid backup using a custom recovery of your stock
or flash a RUU which requires S-OFF.
Click to expand...
Click to collapse
Nevermind, I just successfully gained S-OFF using rumrunner! I had to htcdev unlock the bootloader AND gain root access and I tried it and it took a while, but it worked!!
In case anyone else has this problem, I had s-off before then i went back s-on and fully stock to get a warranty fix for my camera. When I got it back, I tried to get s-off again by rumrunner, but I kept encountering an error that said "ERROR: looks like device is not rooted AND lacks an unsecure kernel. SU or FU!!"
I did have an unlocked bootloader, so I didn't know why I was getting that. I assumed that my device was no longer able to achieve s-off because according to a post (see post above this) it warned that going back s-on after s-off will result in an non-s-offable device and I didn't encounter this error when I did it the first time.
But, I thought I might as well root it and try again.
I flashed a custom recovery and flashed a superSU zip file to gain root access.
I tried rumrunner again and after a little while, it worked!!

[Q] Unroot Sprint HTC One from CM11

HTC One M7
SPRINT
S-ON
UNLOCKED
HBOOT 1.56
Radio 1.00.20.1108
OS 4.06.651.9
CM 11 20140504-SNAPSHOT
I need to restore my phone to a version of stock android (either an actual stock RUU or Android Revolution or whatever) so that I can get to the UICC option to turn off my SIM card (this setting is not available in CyanogenMod apparently).
Because I am on a newer firmware and because I am S-ON I do not seem to be able to install any of the (mostly older) RUUs I have found. Any suggestions? Is there an RUU for 4.06.651.9 that I am not seeing? Is there another way to roll back my OS to allow an older RUU to be installed? Another option altogether? A way to S-OFF while on CM?
Thanks for your help
pc010121 said:
HTC One M7
SPRINT
S-ON
UNLOCKED
HBOOT 1.56
Radio 1.00.20.1108
OS 4.06.651.9
CM 11 20140504-SNAPSHOT
I need to restore my phone to a version of stock android (either an actual stock RUU or Android Revolution or whatever) so that I can get to the UICC option to turn off my SIM card (this setting is not available in CyanogenMod apparently).
Because I am on a newer firmware and because I am S-ON I do not seem to be able to install any of the (mostly older) RUUs I have found. Any suggestions? Is there an RUU for 4.06.651.9 that I am not seeing? Is there another way to roll back my OS to allow an older RUU to be installed? Another option altogether? A way to S-OFF while on CM?
Thanks for your help
Click to expand...
Click to collapse
you can use this then take the OTA updates
http://www.htc1guru.com/dld/guru_reset_m7_sprint_3-04-651-2-zip/
Is this the 3.04.651.2 RUU? If so, I already have a copy, and when I attempt to run the ARUwizard I get Error 155. Most likely I am doing something wrong. I just assumed that since I am already on 4.06.651.9 that the problem was I couldn't install the older 3.04.651.2 version. Thoughts?
pc010121 said:
Is this the 3.04.651.2 RUU? If so, I already have a copy, and when I attempt to run the ARUwizard I get Error 155. Most likely I am doing something wrong. I just assumed that since I am already on 4.06.651.9 that the problem was I couldn't install the older 3.04.651.2 version. Thoughts?
Click to expand...
Click to collapse
This is exactly the same issue I'm experiencing. Well, now I'm even beyond this point... I am only able to boot the phone to the bootloader.
Edit: I am relocked as I am S-ON. I can't update firmware as the signature check fails. Flashing the 3.04.651.2 zip has a signature verify fail, as well.
Hope this helps
cheesesoda said:
This is exactly the same issue I'm experiencing. Well, now I'm even beyond this point... I am only able to boot the phone to the bootloader.
Click to expand...
Click to collapse
If you can still boot to bootloader your phone is fine. You should still have recovery (TWRP?) on your phone I assume. Regardless here are some steps that should help:
1. Figure out if you are S-ON (is found on the bootloader screen)
2. If you are S-ON, try Rumrunner to get S-OFF (just google it). This will allow you to install any RUU regardless of your firmware.
3. If Rumrunner doesn't work or you don't want to go to S-OFF then download the 4.06 RUU here http://forum.xda-developers.com/showthread.php?t=2658910
The problem is your firmware is ahead of the corresponding firmware of the 3.X release. As such you have to install from the newer RUU.
pc010121 said:
If you can still boot to bootloader your phone is fine. You should still have recovery (TWRP?) on your phone I assume. Regardless here are some steps that should help:
1. Figure out if you are S-ON (is found on the bootloader screen)
2. If you are S-ON, try Rumrunner to get S-OFF (just google it). This will allow you to install any RUU regardless of your firmware.
3. If Rumrunner doesn't work or you don't want to go to S-OFF then download the 4.06 RUU here http://forum.xda-developers.com/showthread.php?t=2658910
The problem is your firmware is ahead of the corresponding firmware of the 3.X release. As such you have to install from the newer RUU.
Click to expand...
Click to collapse
Actually, it seems that the phone is wiped; I can't boot my recovery. As a result, I can't really get S-OFF. I'll try the 4.06 RUU, but would it make a difference that it's .4 and not .9?
EDIT: I'm talking out of my ass right now. Long day, and this isn't helping. I am figuring it out; unlocked the bootloader, and now things seem to be functional. Well, except CM doesn't seem to want to boot any longer, but that shouldn't matter for long.
EDIT 2: How can I get S-OFF without enabling debugging? As of right now, CM is just in a boot loop.
Sim Unlock Sprint HTC One Max
I almost cannot believe how many different ROMs I've tried to flash after wiping out my original ROM.
Bootloader unlocked and rooted I managaged to relock the bootloader while trying to fastboot flash a stock ROM, which also failed.
Beleive it or not, I've have found a couple that will boot up with my Sprint HTC One Max . I was able to re-unlock the bootloader, flash a new rom and even recover user data I had backed up to my PC via adb backup.
All this for not, as I still cannot find a Sense ROM that will flash on my device and allow me to unnlock the Sim via Sim Unlock Helper.
Any help would be greatly appreciated!!!
TAMPERED
UNLOCKED
Sprint HTC One T6WL S-OFF
CID-SPCS_001
HBOOT-2.49.000
RADIO-1.48.50.0425
I recall reading somewhere that the Unlock Sim Helper should work on Sense 4.1.2 ROM. ????

Categories

Resources