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?
Hey, I just flashed CM however I want to return completely to stock. The guides here seem to be with s-off, and my hboot is 1.54 or something so I can´t s-off apparently. What should I do? Thank you.
You can flash the stock rom, the stock recovery and after relock your bootloader.
But, if you need to send the phone to htc, they can say that your phone is cracked and they won't repair it
Alright one last question, where can I find the full stock rom and recovery for the international europe version? Can't seem to find it.. Thanks..
In this thread :good:
Ok, I originally was on the stock 4.3 rom that I received by OTA. I ran this for a while without root.
I finally rooted and flashed ARHD 31...therefore my rom was updated to the new sense 5.5, but my firmware was still based on 4.3 with sense 5.0
I didn't make a nandroid (dumb mistake)...I am looking to gain s-off so I can update my firmware.
I am wondering the safest way to do this...do I need to RUU back to 4.3, and if I do that, do I have to lock the bootloader back prior to RUUing? or after?
Also, is there a RUU posted for 4.3 att sense 5?
Any help would be appreciated...in the end all I am trying to accomplish is achieve s-off.
thanks
joho5 said:
Ok, I originally was on the stock 4.3 rom that I received by OTA. I ran this for a while without root.
I finally rooted and flashed ARHD 31...therefore my rom was updated to the new sense 5.5, but my firmware was still based on 4.3 with sense 5.0
I didn't make a nandroid (dumb mistake)...I am looking to gain s-off so I can update my firmware.
I am wondering the safest way to do this...do I need to RUU back to 4.3, and if I do that, do I have to lock the bootloader back prior to RUUing? or after?
Also, is there a RUU posted for 4.3 att sense 5?
Any help would be appreciated...in the end all I am trying to accomplish is achieve s-off.
thanks
Click to expand...
Click to collapse
You could use http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
or
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
You need to be locked/relocked before flashing the ruu.
Sorry if it is a noob question
I have a Rogers HTC One, 4.2.2 KitKat, S-On, HBoot 1.56, Software 4.19.631.9, Root, TWRP (unlocked at HTC Dev)
I don't have a Nanodroid Backup (Big error...)
I haven't been successful in getting S-OFF neither with Rumrunner nor firewater, I kind of disappointed, and maybe I'm taking the lazy way. I want to go back to stock so I can get future OTA updates. So... I don't care much about the Relock flag or anything, just the OTAs,
Can I just use a RUU and flash it right away? So get a fresh rom, unroot, and stock recovery? Or what can I do? I don't want to brick my device.
I see that in http://forum.xda-developers.com/showthread.php?t=2428276 there is the KitKat Rogers RUU, can I use this even if I'm S-ON?
Thanks for your help...
jorgepena9 said:
I see that in http://forum.xda-developers.com/showthread.php?t=2428276 there is the KitKat Rogers RUU, can I use this even if I'm S-ON?
Click to expand...
Click to collapse
With S-ON, you can flash a ruu if its the same version or higher than what you have on the device, so yes, you can use the 4.19.631.9 ruu. You must also have a locked/relocked bootloader to use a ruu with S-ON.
Hey,
i'm going to try some custom roms on my gf's One M7, unfortunately she updated her M7 to Lollipop so i can't make an S-ON (right?!) except sunshine, which is not free. Anyway, i think S-ON is problematic but still ok, but which rom can i flash with S-ON?
Only stock based? Or any aosp based, but not higher Android than 5.0 ? I would like to try SkyDragon (Sense 7) but not sure if i brick the phone
Same s-on but different problem can't return to stock
banangrg said:
Hey,
i'm going to try some custom rons on my gf's One M7, unfortunately she updated her M7 to Lollipop so i can't make an S-ON (right?!) except sunshine, which is not free. Anyway, i think S-ON is problematic but still ok, but which rom can i flash with S-ON?
Only stock based? Or any aosp based, but not higher Android than 5.0 ? I would like to try SkyDragon (Sense 7) but not sure if i brick the phone
Click to expand...
Click to collapse
If the phone is now running a lollipop firmware, you can flash any rom you'd like. S-On doesn't matter.
alray said:
If the phone is now running a lollipop firmware, you can flash any rom you'd like. S-On doesn't matter.
Click to expand...
Click to collapse
Even the Lollipop 5.1 (e.g. from M7 GPE) or 6.0 unofficial releases (if they are released/ported for M7)?
How about flashing cutom kernels (They will boot?) ?
Sorry, i'm really noob about possibilities with s-on (some time ago i had htc, but s-off'ed it)
banangrg said:
Even the Lollipop 5.1 (e.g. from M7 GPE) or 6.0 unofficial releases (if they are released/ported for M7)?
How about flashing cutom kernels (They will boot?) ?
Sorry, i'm really noob about possibilities with s-on (some time ago i had htc, but s-off'ed it)
Click to expand...
Click to collapse
System, boot(kernel), radio and recovery partitions are not secured so you don't need soff to flash a rom, kernel. Radio or recovery, you only need an unlocked bootloader.