Related
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?
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!!
Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
ianthomas said:
Could somebody please help with a few brief answers in case I mess something up? I'm new to HTC/S-OFF concept.
I bought a used sprint htc one that I wish to return completely to stock in fear previous owner messed something up, and to start from scratch (SU can't install busybox).
The phone has been unlocked, and rooted, no S-OFF, Hboot 1.56 OTA updated to 4.06.651.9 stock. (don't need to edit hboot, or show "locked" again through S-OFF, just normal "relocked", and stock everything else. I know I need to relock bootloader, and stock recovery anyways)
Is an official RUU for 4.06.651.9 (slash .4) the only way to return to stock completely? I don't want/need S-OFF (currently available through Firewire for Sprint on 1.56) unless necessary.
Can I S-OFF, and then S-ON afterwards?
What is the difference between an official RUU vs pushing this stock firmware (4.06.651.9) or .4 through fastboot? Do I need to S-OFF and go to an earlier firmware, and THEN, go to the newest like some people suggest because of the radio?
What has the radio to do with going back to an earlier firmware, and then upgrading?
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Devilish_Angel said:
... oh man so many questions and believe me this is the best way to go by it
long story short you can just factory reset your device and it will be like stock out of the box.
Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910
you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us
if you get s-off 1st then no need to lock your bootloader. RUU runs irrespective of bootloader status if device is s-off.
and yes you can s-on after s-off.
hope this helps ...
Click to expand...
Click to collapse
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
fastboot oem writesecureflag 3
Click to expand...
Click to collapse
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
ianthomas said:
I really appreciate your help . I'm still a little stuck though. When you say:
"long story short you can just factory reset your device and it will be like stock out of the box."
If by that you mean to Factory Reset through the privacy options of any Android phone, then this is a big NO-NO for me from previous expirience with many other non HTC phones that would soft brick if I did that on a rooted phone. Maybe it works on HTC's, but it seems too easy to be true So I would rather not risk it, and go the RUU way if possible,
"Now though you dont need it but here is the link to RUU if you really wanna do it but it wont make a difference if you are not experiencing any hiccups. but for this RUU to run you need to relock your botloader via fastboot.
http://forum.xda-developers.com/showthread.php?t=2658910"
I was going to try that RUU, even though it's for 4.06.651.4, and I have 4.06.651.9. I was going to assume it works on all 4.0's firmwares on S-ON, and that I need S-OFF to go back to earlier firmwares? The info out there is very vague on this, but since I'm S-ON, I will risk it, since it seems the most I would get out of that in S-ON maybe a softbrick.
"you are in a good position to gain s-off as you are already unlocked so go get it. folow rumrunner.us"
The rumrunner threads seem to say it doesn't work on Hboot 1.56. So far I only read a few threads with people saying only Firewire works on Hboot 1.56, but again, others say it doesn't, and the info it's very vague. I will try S-OFF if I have to though
"and yes you can s-on after s-off."
This one does seem dangerous. The only credible info I found on it was from a popular dev in these threads saying NOT to be quoted about using this command because he wasn't sure either:
So the info was vague/unclear again, so I will take a leap of faith with S-OFF if I have to, and report back anything else I find
Click to expand...
Click to collapse
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
S-OFF - do it!
Devilish_Angel said:
... well you are the 1st one to experience problems after factory reset . usually it happens other way round. i cant remember how many times i have rooted how many phones of how many makes and never ever have i encountered any problems after resets. factory resets are done to rectify any harm done to the device OS by the user, apps, kernels, mods or something else. it brings the phone back to original stock out of the box state.
by the experiences i have with the phones you just need to reset it and if you are really adamant to RUU, you can.
as for the s-off is concerned, there is no harm trying rumrunner or firewater. they do no harm even if they fail. a lot of people including me have gained s-off with hboot 1.56. if rumrunner doesnt work for you try fire water and if that too fails, flash ARHD 41 and then try rumrunner ...
Click to expand...
Click to collapse
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
... well buddy you quoted the wrong guy . never mind. this is exactly what i was telling him to get s-off to make things easier. appreciate your help though ...
ianthomas said:
Is there a way to "freeze" the OTA software upgrade like it's possible on other non HTC devices?
Sorry to bother guys, I have read many threads, but I'm not so clear on these questions
Click to expand...
Click to collapse
It's my understanding that the OTA only works on bone stock phones.
slyest12 said:
It's my understanding that the OTA only works on bone stock phones.
Click to expand...
Click to collapse
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Little story to tell:
A day or two ago I got a notification of an ota*.9* to be exact, I tried installing it knowing it wouldn't cause I was rooted. I like to flash back to my stock Rom and update the apps and stuff so I get get the stock feel back without losing much from my daily driver Roms.
Anyways, there is a thread in the forums about installing this update, I tried it and wiped my phone minus the stock Rom, everything was gone even backups. The thread suggested to me to download this app sort of like flashify to flash stock recovery. After flashing stock recovery, well I had or think I had stock recovery cause I had to reinstall twrp, that's when I found out I wiped the heck out of my phone.
I had to start from scratch without a stock Rom cause what ever I did, my stock Rom was borked somehow, everything was gone, I couldn't "repair" missing stuff* like the weather/widget couldn't stick on the home screen. I had to make a sense six Rom my "stock" Rom while gathering more info on RUU and being s-off.
What I thought was this, I'd have to relock boot loader to do a RUU, which I didn't want to do, cause I am thinking I will lose root and have to htcdev again. But I'm s-off'd and now knowing that I won't need to relock bootloader, I have a question.
How do I EXACTLY go about RUU with s-off if I don't have to "oem lock"?
I s-off'd mainly to change boot splash and use a modded hboot to show its "not" rooted, I knew I don't have to htcdev again while s-off, but I was hoping to not come to that point, then this ota thing happened.
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Lol, nice hijack buddy, but it just so happens I have the same question
I got frustrated about a continuous brick while on S-ON, so I decided to S-OFF on my Hboot 1.56, and turns out, only Firewater was able to give me S-OFF. The process was very simple!!!
http://firewater-soff.com/
But even with S-OFF, I still soft brick or get into a bootloader bootloop while trying to install any non stock ROMS:
[Q] Bootloader Bootlopp soft brick on Viper 5.8.0 and other ROMS
I stopped trying more crazy things... I learned no to use TWRP 2.7 in my case, and use older versions, or PhilzTouch, but I still can't figure out how to either OTA update to .9, or install the Viper ROM correctly.
My guess is the same as yours... I shouldn't push a Stock odex ROM through fastboot, or ADB sideload through recovery. Having S-OFF means being able to use the RUU tool WITHIN a stock ROM itself, BUT BEFORE doing so, maybe it's best to flash a stock recovery, or this firmware file:
[Guide][How-to] Run 4.06.651.4 RUU on any windows without any problem..!!
That I guess it's the same found here (MD5 match "Full Firmware from RUU (fastboot flashable)"):
[RUU][Firmware]Sprint HTC One | 4.06.651.4 | Encrypted | Decrypted | Stock Rooted ROM
Anyways, before trying to do any of that, I will try to simply run the RUU from within the stock ROM, and hope the RUU flashes a firmware that contains a stock recovery as well (and maybe more?), so that maybe that's all I need to install the .9 OTA properly through the stock ROM, and after that, try and get the Viper ROM installed properly.
Will report back whatever I can find.
More useful posts:
[Tutorial][Rescue]Sprint HTC One users that flash GSM roms on their CDMA devices.
[ROM] Bad Boyz Sprint ONE ROMz | 4.4.2 | KitKat | Deodexed | myHUB | Updated 2/23/14
[HOW TO] ADB Sideload/Push if you Wipe Internal Storage And have no ROM to Flash
[Tutorial][Resource][Root]Unlock-Recovery-SuperSU for HTC One(M7)-Sprint-m7wls The all in one folder put togheter by BD619 in this post is pretty handy.
EDIT: Actually I will report back in my other question too, since this thread was supposed to be about RUU, and S-OFF, which I resolved through Firewater under Hboot 1.56.
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
v1ral said:
Sorry for the hijack mang!!
Good info here though.
I tried flashing the stock Rom that's on post #2 on the ruu thread but I still get the ota nagging, and data is slow for some reason, that Rom is really wonky for me.
At the moment I'm using a sense 6 Rom and viper Rom 5.8, and data with those are well enough to say I can browse normally on 3g.
Anyways so what is being said is that we would have to just run the ruu though desktop and it should have stock bootloader so we can take the .9 ota. And then after its done we can just flash any custom recovery after that?
Is there really no way to just bypass the its, like how we can bypass hfa?
Click to expand...
Click to collapse
... There is a way to bypass hfa if you don't know yet ...
Devilish_Angel said:
... There is a way to bypass hfa if you don't know yet ...
Click to expand...
Click to collapse
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
v1ral said:
I only know about deleting or modifying the "xxxOmad.apks" in the /system/app/ areas. Is there another way?
Click to expand...
Click to collapse
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
slyest12 said:
Take it from me, one who has replaced his One 3 times- twice being directly my fault, get S-OFF. If I could go back in time and slap younger me in the face, I would. Instead, I will tell you this- get S-OFF. It doesn't take a ton of work, and you will never find a reason to regret it. Plus, RootLinux has an HBOOT flasher in the Development forums if you really want everything to LOOK stock. Once you're S-OFF, you don't have to relock the bootloader to flash an RUU, another perk.
Click to expand...
Click to collapse
I forgot to thank you for your advise, which I took, and I don't regret There is a tiny little fine print about this though: " you don't have to relock the bootloader to flash an RUU"... That is not mentioned in the guides I read, and I will try to clarify in my noob post.
v1ral said:
Edited for clarity or the lack there of.
Or bone stock rooted Roms, however you have to flash stock recovery first if s-on, how about with s-off?
Sorry for a long post and prolly going way off topic, but s-off and RUUs or having to flash stock recovery in order to install an ota is confusing to me.
1. Can I RUU without relocking bootloader with s-off?
2. Can I install an ota update without flashing stock recovery with s-off?
3. Last thing, what are the steps to update my stock Rom, while being s-off?
Click to expand...
Click to collapse
It is confusing for me too, but one of my theories was right, and I felt like a dunce once I figured it out, and I think you figured it out too...
Anyways, the HTC one will be for my brother, so I had limited access to it, and finally did more tests on it to figure things out.
I will try and answer your questions to my best of knowledge, but please keep in mind this is a noob/guinea pig point of view that is still asking questions, and I may be wrong on some things, so bear with me, but this has worked for me:
===========================================================================
Being on a Sprint HTC ONE with Hboot 1.56, originally on stock 4.06.651.4 , and S-OFF thanks to Firewater (other methods failed for me). I would recommend getting S-OFF now (to whoever else this may help).
OK v1ral, as far as I know, the ability to flash the 4.06.651.4 RUU WITHOUT having to relock the bootloader is from WITHIN the stock ROM itself, NOT from fastboot or anywhere else.
TIP: When unlocking the bootloader, simply save the .BIN file HTCDEV sends you, and save the command used to unlock for quick unlocking and relocking, just in case.
However you have to flash stock recovery first if s-on, how about with s-off?
You don't have to flash a stock recovery, because the RUU itself does that for you, regardless of S-ON or S-OFF. The only condition is having to relock the bootloader if S-ON BEFORE running the 4.06.651.4 RUU from WITHIN the stock ROM you're in, but obviously that is not necessary if S-OFF.
Can I RUU without relocking bootloader with s-off?
As far as I know, yes. that is the perk of having S-OFF.
Can I install an ota update without flashing stock recovery with s-off?
As far as I know (please correct me), the RUU itself flashes a stock recovery anyways, or at least that's one of the messages it gives while working. Keep reading for the info on how to install the OTA properly in my case.
Last thing, what are the steps to update my stock Rom, while being s-off?
OK, here we go, there is a very important, and easy missing detail nobody mentions in the guides I read, and the reason I was soft bricking with any rom.
How to OTA update from 4.06.651.4 to 4.06.651.9 properly, regardless of being S-ON, or S-OFF, and avoid bootloader bootloop for noobs
First off, If you're already in trouble, and can't install a stock rom, in a bootloop, or don't know how to adb sideload a rom into your device, etc... PM me to try and help you out of it, and start off in a stock room. That may take more time.
Moving on, assuming you're already in a stock rom, or any 'working' rom for that matter, meet these requierements first:
Make sure you never installed HTC Sync before, EVER. Have proper drivers installed, and a correct ADB online connection to your phone is important. I'm just assuming you didn't lazy out, and know how to research the drivers in here already. I just need you to run the command
ADB devices
Click to expand...
Click to collapse
and get a correct online connection between your phone, and PC. Another thing is not to use usb 3.0, or the frontal usb inputs on your PC, and use the back inputs just in case...
And even MORE important tip, is to never... EVER... use cheap low quality or damaged usb cables. I learned this the hard way hard bricking 2 phones in my old LG LGNPST days (LGNPST is another type of flashing tool for LG devices).
Having a damaged usb cable may be really dangerous, specially if your'e S-OFF
Having an al in one folder with the tools to work is pretty convenient, and user BD619 gathered one in his thread
He may not always have the latest version of the TWRP or CWM/PhilzTouch recoveries in it, but you can easily get them in this forum obviously.
TIP: TWRP is the recommended recovery on this device, version 2.7.0.3 didn't work for me, but the new 2.7.0.4 seems better for me, but I still can't mount an OTG drive to it, so you may have to learn how to push/adb sideload ROMs or files into it like this.
OK, from WITHIN your stock ROM, run this 4.06.651.4 RUU first (you only need to relock bootloader prior to running it if you're S-ON):
http://forum.xda-developers.com/showthread.php?t=2658910
It doesn't matter if you're already on firmware 4.06.651.4, run it anyways (it will flash a stock recovery, and more), reboot, and
THEN relock your bootloader, regardless of being S-ON or S-OFF
That was the little detail I was missing, and should've figured out before...
After relocking the bootloader, reboot back in, and THEN, and only then, you can download and install the 4.06.651.9 update from within the Software Update option.
After updating properly to 4.06.651.9, it is then that you can unlock the bootloader back again, flash TWRP, and root with it, or get ROMS already rooted without hiccups.
Finally, if I'm wrong on any of the small details in this, please correct me, but it was what worked for me at least.
Devilish_Angel said:
... here you go. download the attached zip file. flash the rom, boot the rom until you see hfa then restart device in recovery and flash the below file. when its done restart the device normally and guess what ???? no hfa ...
Click to expand...
Click to collapse
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
v1ral said:
Lol, what I meant to put is ota not about hfa.. I have stopped hfa on all the new flashed roms I get by renaming/deleting some files in the system/app.
Does that link work for all roms?
Click to expand...
Click to collapse
... It should. Moreover it is far more easy to flash a simple zip than mounting the file system, finding files and then deleting some and renaming some ? ...
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.
I have an AT&T variant m7 running 4.1.2 and I'm gonna be unlocking, flashing tarp, and rooting. I am looking to install the newest viperone Rom and am wondering if I can do this s-on or not, I've read some stuff that says I have to flash boot.img after and some that says before, and others that say I don't need that step at all! I just wanna get this straightened out so I don't screw up. Any help would be appreciated and if there are any other suggestions I'd be happy to hear them
Thank you.
dirtrider129 said:
I have an AT&T variant m7 running 4.1.2 and I'm gonna be unlocking, flashing tarp, and rooting. I am looking to install the newest viperone Rom and am wondering if I can do this s-on or not, I've read some stuff that says I have to flash boot.img after and some that says before, and others that say I don't need that step at all! I just wanna get this straightened out so I don't screw up. Any help would be appreciated and if there are any other suggestions I'd be happy to hear them
Thank you.
Click to expand...
Click to collapse
Get S-off try revone and rumrunner or firewater (don't skip this step)
after your s-off flash the 3.xx.502.x RUU
now flash TWRP 2.6.3.3 and then the ViperOne rom
clsA said:
Get S-off try revone and rumrunner or firewater (don't skip this step)
after your s-off flash the 3.xx.502.x RUU
now flash TWRP 2.6.3.3 and then the ViperOne rom
Click to expand...
Click to collapse
So after I unlock bootloader, flash twrp, and root, once I get s-off, do I need to re-flash the stock recovery before flashing RUU, then flash twrp again then flash viper? Also why the RUU, I just want to understand what I'm doing and why. Thank you so much for your help, I'm definitely a noob and am really interested in this world.
dirtrider129 said:
So after I unlock bootloader, flash twrp, and root, once I get s-off, do I need to re-flash the stock recovery before flashing RUU, then flash twrp again then flash viper? Also why the RUU, I just want to understand what I'm doing and why. Thank you so much for your help, I'm definitely a noob and am really interested in this world.
Click to expand...
Click to collapse
skip the stock recovery step .. after your s-off you can flash the RUU even unlocked... your flashing the RUU to get your hboot / touch screen drivers and radio more up to date.
clsA said:
skip the stock recovery step .. after your s-off you can flash the RUU even unlocked... your flashing the RUU to get your hboot / touch screen drivers and radio more up to date.
Click to expand...
Click to collapse
Oh ok, now I understand. Thanks
clsA said:
skip the stock recovery step .. after your s-off you can flash the RUU even unlocked... your flashing the RUU to get your hboot / touch screen drivers and radio more up to date.
Click to expand...
Click to collapse
Once I flash the RUU zip, will I lose root also?
dirtrider129 said:
Once I flash the RUU zip, will I lose root also?
Click to expand...
Click to collapse
of course you'll have to re-flash recovery and root again
revone failing
clsA said:
of course you'll have to re-flash recovery and root again
Click to expand...
Click to collapse
Ok so I after having a bunch of issues with htcdev site I finally unlocked my bootloader using the kingo program, then I flashed twrp 2633 and rooted although I forgot to erase cache after flashing twrp. At first it didn't boot in recovery, just booted up normally but it worked the second time, after rooting root checker said I didn't have proper root but after rebooting again it says it is rooted. Superuser said I need to update binaries wasn't sure how but I read somewhere to install superSU from playstore. Anyways that's not really my issue, just thought I'd let u know it was goin. When I try running revone, after I run ./revone.bin -P I'm getting revone fail error -6. Coundnt find a strait answer so thought I'd check here. Thanks all and let me know if u need any other info
Dirtrider129
dirtrider129 said:
Ok so I after having a bunch of issues with htcdev site I finally unlocked my bootloader using the kingo program, then I flashed twrp 2633 and rooted although I forgot to erase cache after flashing twrp. At first it didn't boot in recovery, just booted up normally but it worked the second time, after rooting root checker said I didn't have proper root but after rebooting again it says it is rooted. Superuser said I need to update binaries wasn't sure how but I read somewhere to install superSU from playstore. Anyways that's not really my issue, just thought I'd let u know it was goin. When I try running revone, after I run ./revone.bin -P I'm getting revone fail error -6. Coundnt find a strait answer so thought I'd check here. Thanks all and let me know if u need any other info
Dirtrider129
Click to expand...
Click to collapse
I'm not sure why you want to S-off. You have now unlocked, changed recovery, and rooted. You can simply download viper one rom and flash it from recovery. You dont need to flash any boot.img for m7. I hope that helps. If you still want to S-off use rumrunner. revone is not supported for bootloader that comes with 4.1.2. Do note that you cannot s-on again once you s-off the device.
coolshritz said:
I'm not sure why you want to S-off. You have now unlocked, changed recovery, and rooted. You can simply download viper one rom and flash it from recovery. You dont need to flash any boot.img for m7. I hope that helps. If you still want to S-off use rumrunner. revone is not supported for bootloader that comes with 4.1.2. Do note that you cannot s-on again once you s-off the device.
Click to expand...
Click to collapse
I was getting s-off because I was told to get s-off so I could flash the 3.17 ruu to update my hboot/ touchscreen drivers and radio before flashing viper, which I figured so viper would run smoother. I'm a noob just getting into modding. I have a AT&T HTC one running on crickets new gsm network and since I can't get OTAs I first wanted to just get up to 4.4 and sense 6 but then I figured I'd just go custom Rom.
dirtrider129 said:
I was getting s-off because I was told to get s-off so I could flash the 3.17 ruu to update my hboot/ touchscreen drivers and radio before flashing viper, which I figured so viper would run smoother. I'm a noob just getting into modding. I have a AT&T HTC one running on crickets new gsm network and since I can't get OTAs I first wanted to just get up to 4.4 and sense 6 but then I figured I'd just go custom Rom.
Click to expand...
Click to collapse
It is not mandatory to S-Off to flash a rom. Your rom will anyway work in a good way.
clsA said:
skip the stock recovery step .. after your s-off you can flash the RUU even unlocked... your flashing the RUU to get your hboot / touch screen drivers and radio more up to date.
Click to expand...
Click to collapse
Well after failing with revone, rumrunner, and firewater I went ahead and flashed viper, and everything was fine. I can't help be bugged by the fact that you told me to get s-off and flash that ruu to get the updated radio and touchscreen drivers, I read that I need a 4.2 Rom to get revone to work so I am gonna give it another try. I tried running firewater with ARHD and it said that it had an anti-firewater patch. So I am just curious as to what the importance of having the updated hboot, radio, and touchscreen drivers. I just feel like I should still get it done since u told me not to skip that step, not to mention later on down the line when I get more familiar with all of this dev and modding stuff I might want to do other things that require a-off. Thanks for all your help and info . Before I continue with it I made a backup of viper with the setting and themes I've set up, after I get s-off and flash the ruu, should I 're-flash the Rom or can I restore my backup with out changing any of the updated software, I didn't think the Rom would have anything to do with it but I just wanna make sure. Thanks
dirtrider129 said:
Well after failing with revone, rumrunner, and firewater I went ahead and flashed viper, and everything was fine. I can't help be bugged by the fact that you told me to get s-off and flash that ruu to get the updated radio and touchscreen drivers, I read that I need a 4.2 Rom to get revone to work so I am gonna give it another try. I tried running firewater with ARHD and it said that it had an anti-firewater patch. So I am just curious as to what the importance of having the updated hboot, radio, and touchscreen drivers. I just feel like I should still get it done since u told me not to skip that step, not to mention later on down the line when I get more familiar with all of this dev and modding stuff I might want to do other things that require a-off. Thanks for all your help and info . Before I continue with it I made a backup of viper with the setting and themes I've set up, after I get s-off and flash the ruu, should I 're-flash the Rom or can I restore my backup with out changing any of the updated software, I didn't think the Rom would have anything to do with it but I just wanna make sure. Thanks
Click to expand...
Click to collapse
you can restore your backup with the new firmware
for firewater you needed ARHD + ElementalX kernel
it mark just fine with the ViperOne rom also
Revone only works on hboot 1.44 and android 4.1.2 and/or 4.2.2
clsA said:
you can restore your backup with the new firmware
for firewater you needed ARHD + ElementalX kernel
it mark just fine with the ViperOne rom also
Revone only works on hboot 1.44 and android 4.1.2 and/or 4.2.2
Click to expand...
Click to collapse
Do you think firewater will work with viper+Elemental X kernel? If I used the same guide as with ARHD. I tried to s-off with revone by flashing a 4.2.2 viper Rom but I lost all signal and service, so I restored my backup. Also I was wondering since I'm running the 3.17 ruu to update radio and stuff , should I use the 4.18 ruu since its newer? Thanks again for all the help.
UPDATE: Well ran firewater since coudnt get revone to work , took all of like 45 seconds and it said device is s-off. Couldn't believe it after all the trouble I've had.Awesome!