What can be done with S-On (Hboot 1.54)? - One (M7) Q&A, Help & Troubleshooting

Firstly, apologies for asking possibly really dumb questions, but I haven't actually used an Android HTC device for a while, having gone to the darkside and used Windows Phone 8 (HTC 8X).
This HTC One is my first Android phone for a while, and obviously, I would like to root it and update to the latest Android 4.3 (with or without Sense 5.5 whatever it ships with) - and also hopefully get rid of that blasted BlinkFeed if possible.
I have HTCDev unlocked the bootloader, however the phone is still currently S-On.
What can I do now?
1: Can I flash custom recoveries with S-On?
2: If not, is it possible reflash older firmware (either via zip or via RUU - I am HTC__001 CID, and running 2.24.401.8 - again, not sure on what is the correct older version of this) which could lead to being able to S-Off on an older Hboot?
If neither is possible, then I guess I will just have to be patient and wait for the methods of S-Offing 1.54 to be released...
Anyway, hope you guys can help a newbie

taffypride said:
Firstly, apologies for asking possibly really dumb questions, but I haven't actually used an Android HTC device for a while, having gone to the darkside and used Windows Phone 8 (HTC 8X).
This HTC One is my first Android phone for a while, and obviously, I would like to root it and update to the latest Android 4.3 (with or without Sense 5.5 whatever it ships with) - and also hopefully get rid of that blasted BlinkFeed if possible.
I have HTCDev unlocked the bootloader, however the phone is still currently S-On.
What can I do now?
1: Can I flash custom recoveries with S-On?
2: If not, is it possible reflash older firmware (either via zip or via RUU - I am HTC__001 CID, and running 2.24.401.8 - again, not sure on what is the correct older version of this) which could lead to being able to S-Off on an older Hboot?
If neither is possible, then I guess I will just have to be patient and wait for the methods of S-Offing 1.54 to be released...
Anyway, hope you guys can help a newbie
Click to expand...
Click to collapse
You cannot get S-Off at the moment with hboot 1.54 (unless you use/know somebody that has a JavaCard).
AND THERE IS NO WAY TO DOWNGRADE. Nasty remark: C'mon guys, it's been said a few thousand times by now. (sorry couldnt help myself ).
Some say beaups will soon post a S-Off for 1.54, but can't confirm this. (http://forum.xda-developers.com/showthread.php?t=2474089)
Anyway, with bootloader unlocked, you can flash ROM, kernel, recovery, even radio, but not unsigned firmware. Take a look at ARHD 30.0 (amongst others) has Sense 5.5 and you can flash it with your current firmware. Do a full wipe install. If problems do arise it COULD be due to firmware, but nobody has really fully verified that. (as far as I know)
EDIT: remember to make a nandroid backup of your stock ROM!!

When you unlock your bootloader you are opening all the partitions necessary to flash custom kernels, recoveries and ROMs, so in answer to your first question, yes you can.
S-off is only necessary to flash radios, RUUs, etc. things that you won't need for a while (if ever) if you're only just flashing a custom ROM now.
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
When you unlock your bootloader you are opening all the partitions necessary to flash custom kernels, recoveries and ROMs, so in answer to your first question, yes you can.
S-off is only necessary to flash radios, RUUs, etc. things that you won't need for a while (if ever) if you're only just flashing a custom ROM now.

postfatal said:
When you unlock your bootloader you are opening all the partitions necessary to flash custom kernels, recoveries and ROMs, so in answer to your first question, yes you can.
S-off is only necessary to flash radios, RUUs, etc. things that you won't need for a while (if ever) if you're only just flashing a custom ROM now.
---------- Post added at 05:56 PM ---------- Previous post was at 05:55 PM ----------
When you unlock your bootloader you are opening all the partitions necessary to flash custom kernels, recoveries and ROMs, so in answer to your first question, yes you can.
S-off is only necessary to flash radios, RUUs, etc. things that you won't need for a while (if ever) if you're only just flashing a custom ROM now.
Click to expand...
Click to collapse
Radios can be flashed as well without S-Off, as far as I know.

Guys, I appreciate the fast response.
I understand the question about downgrading has probably been asked a million times.
Good news about still being able to flash custom recovery/rom etc.... will do that later, and then wait for the 1.54 s-off method
Again, much obliged for the help

nkk71 said:
Radios can be flashed as well without S-Off, as far as I know.
Click to expand...
Click to collapse
Official radios can, custom radios cannot.

postfatal said:
Official radios can, custom radios cannot.
Click to expand...
Click to collapse
You mean signed firmware right? Or am I missing something

Related

Should I go back to S-ON to OTA ICS a Bell Raider?

I know I have to relock bootloader, back to stock RUU, but what about Son Soff stuff? Thank you people!
Sent from my HTC PH39100 using xda premium.
I know I need to know as well I want the bell radios back .also if I want to keep them at a later the for a new from do I transfer over the system folder ?
---------- Post added at 05:32 PM ---------- Previous post was at 05:26 PM ----------
But s-off is only so you can flash stuff through recovery and not fast boot .and some devices came s-off from factory . What I'm iffy about as well is do I run the ruu from bell again that's gingerbread then do the ota ? Because h-boot I thought couldn't be downgraded ? I hope a dev sees this .I hate People having to put up with All the echoing in the phone calls
With stock Bell ics ota, it does not feedback anymore with phonecalls
Sent from my HTC Raider 4G LTE running ICS.
ideaLduK said:
With stock Bell ics ota, it does not feedback anymore with phonecalls
Sent from my HTC Raider 4G LTE running ICS.
Click to expand...
Click to collapse
So you did go back to S-ON before you OTA updated to ICS? (too much jargon )
Did you unlock the bootloader and flash a recovery after? Did you install the other kernel from the supertool and did you get root?
mohcho said:
So you did go back to S-ON before you OTA updated to ICS? (too much jargon )
Did you unlock the bootloader and flash a recovery after? Did you install the other kernel from the supertool and did you get root?
Click to expand...
Click to collapse
I havent S-ON prior to do this, it worked perfectly. I only relocked BL with fastboot oem lock then RUUed then OTAed. After that I reunlocked BL and, flashed twrp recovery and flashed my rom (already rooted )
Sent from my HTC Raider 4G LTE running ICS.
So it seems when you flashed a custom rom, it's the rom that gives you root access?
I'm on the stock OTA but can't get root. Should I flash another kernel?
I don't necessarily want to run a custom rom but want root.
mohcho said:
So it seems when you flashed a custom rom, it's the rom that gives you root access?
I'm on the stock OTA but can't get root. Should I flash another kernel?
I don't necessarily want to run a custom rom but want root.
Click to expand...
Click to collapse
If i was you and i wanted to get root, id do it manually instead of doing it via supertool. Look in the stickies of the dev subforum to get the procedure. Otherwise PM me maybe i can help you
Sent from my HTC Raider 4G LTE running ICS.
IF YOU ARE S-ON UNLOCKED: FLASH THE STOCK RECOVERY AND RELOCK THE BOOTLOADER, THEN RUN THE RUU IN FASTBOOT.
IF YOU ARE S-OFF: RUN THE RUU IN FASTBOOT.
Yes, caps is necessary. S-OFF is convenient in many ways.
Hunt3r.j2 said:
IF YOU ARE S-ON UNLOCKED: FLASH THE STOCK RECOVERY AND RELOCK THE BOOTLOADER, THEN RUN THE RUU IN FASTBOOT.
IF YOU ARE S-OFF: RUN THE RUU IN FASTBOOT.
Yes, caps is necessary. S-OFF is convenient in many ways.
Click to expand...
Click to collapse
Totally agree with that. Otherwise, your phone could be transformed into a BRICK.
*warning* noob content!
I used the Vivid_All-In-One_Kit_v1.2 to unlock, root, and install the clockwork recovery.
The OTA ICS update fails - it just goes into fastboot and that's it.
So I'm guessing I need to install the original recovery?
I tried finding that, but have been unsuccessful, any help provided is welcome.
Do I also need to apply the stock RUU? Where do I find that one?
On my old Legend HTC support actually supplied me with the stock RUU.....
you should be able to download it from htc just make sure you relock your bootloader if it is unlocked before running the ruu

[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?

[SOLVED] Some questions about S-OFF and RUU

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 ? ...

Cannot obtain s-off after accepting 1.54.651.8 software update

Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
might be your hardware, i am soff with 651.8
Sent from my 831C using XDA Free mobile app
koolcat7 said:
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
Click to expand...
Click to collapse
You could try it multiple times. Reboot the phone, computer, change USB ports, etc.. Who knows, maybe it'll work.
I know the M8 I got S-Off on took the 1.54.651.8 OTA before I even bothered to actually mess with it (unlock bootloader, root, and S-Off) and it was perfectly able to do all of those things.
koolcat7 said:
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
Click to expand...
Click to collapse
If Firewater says it won't work on your device, then you can't get S-OFF for the time being. There's nothing you can do about that.
Don't flash anything above 1.54.651.8 without being S-Off
koolcat7 said:
Im rooted but cannot get s-off using firewater. It gives that error saying im out of luck or something.... What can i do?
Click to expand...
Click to collapse
I'm running into the same problem and I need it badly.
If you do flash .13 without S-off you basically will have no way to flash the firmware and could be without audio from the stock music app.
Wow it's been a long night. This is a learning process for me. I've never come to a new phone so quickly so I'm getting used to the fact that development takes time and I need to be patient. I pretty much soft bricked my phone last night. Ended up deleting my system partition and had to pull some tricks to even get back into a bootable rom. I took one of the TWRP stock restores and reverted all the way back to 1.12.651.17. Then I fastboot flashed the stock recovery from 1.54.651.8 and took the OTA update so now I am completely back to stock....FEW...avoided a trip to the sprint store. I now understand that since I don't have S-OFF yet, I should flash any software versions over .8. In order to have a fully working .13, I'm sure the firmware is required as well (most likely the reason why my audio wasn't working for some of the ROMs). However, I'm still stuck with the issue in the picture below. I need to get S-OFF so I can flash the firmware 1.54.651.8, including the Hboot, Is it possible to flash an Hboot.img without being S-OFF?
#firewater is the IRC channel for the S-OFF by the way.
Also why is my radio and open dsp showing invalid-ver-info?
Anybody please help?
And something is really messed up because now my vibration won't work. No idea what is going on I just badly need s-off.
@mhuffer
So what is your current issue? It sounds like you have a working 1.54.651.8 setup, which, without S-OFF, is the most up-to-date. You might not be able to run the Harman Kardon ROM, as that may require the HK firmware, but besides that is everything working (outside of the invalid entries showing in HBOOT)?
Captain_Throwback said:
@mhuffer
So what is your current issue? It sounds like you have a working 1.54.651.8 setup, which, without S-OFF, is the most up-to-date. You might not be able to run the Harman Kardon ROM, as that may require the HK firmware, but besides that is everything working (outside of the invalid entries showing in HBOOT)?
Click to expand...
Click to collapse
Well it seems like my Hboot isn't recognizing my radios and somthing tells me the firmware is borked somehow because my vibration feedback isn't working. I am currently on 1.54.651.8, rooted, dev unlocked, fully stock. You can see from the picture my Hboot doesn't look right. My vibration was working fine yesterday but i cannot pin point when it stopped working. I'm guessing when I accidentally deleted the system partition through TWRP 2.7.0.7. I am currently running your version of TWRP (2.7.0.7). I'm also in the firewater IRC asking for help. I think my best bet would be to get s-off somehow and hboot the framework from 1.54.651.8 with unmodified hboot so I can get back to stock (if this is possible). At some point in all my confusion last night I did change my CID version to 11111111 and try to run the RUU for the HK version (.13) this might be where it all went wrong. I have my phone up and running and everything is working except for vibration and the Hboot looks out of whack.
mjhuffer said:
Well it seems like my Hboot isn't recognizing my radios and somthing tells me the firmware is borked somehow because my vibration feedback isn't working. I am currently on 1.54.651.8, rooted, dev unlocked, fully stock. You can see from the picture my Hboot doesn't look right. My vibration was working fine yesterday but i cannot pin point when it stopped working. I'm guessing when I accidentally deleted the system partition through TWRP 2.7.0.7. I am currently running your version of TWRP (2.7.0.7). I'm also in the firewater IRC asking for help. I think my best bet would be to get s-off somehow and hboot the framework from 1.54.651.8 with unmodified hboot so I can get back to stock (if this is possible). At some point in all my confusion last night I did change my CID version to 11111111 and try to run the RUU for the HK version (.13) this might be where it all went wrong. I have my phone up and running and everything is working except for vibration and the Hboot looks out of whack.
Click to expand...
Click to collapse
Well if you're not S-OFF, you couldn't have changed your CID. And if you ran the OTA to get where you are now, then you're firmware is already stock.
You can try flashing the stock firmware from the 1.54.651.8 OTA again and see if that normalizes your device.
Captain_Throwback said:
Well if you're not S-OFF, you couldn't have changed your CID. And if you ran the OTA to get where you are now, then you're firmware is already stock.
You can try flashing the stock firmware from the 1.54.651.8 OTA again and see if that normalizes your device.
Click to expand...
Click to collapse
How do I flash it without being S-off? Can I run it with S-On? I think I really just need a way to revert my Hboot to stock. I was hoping somebody had an RUU available that would just wipe everything and start from scratch.
---------- Post added at 12:56 PM ---------- Previous post was at 12:51 PM ----------
Captain_Throwback said:
Well if you're not S-OFF, you couldn't have changed your CID. And if you ran the OTA to get where you are now, then you're firmware is already stock.
You can try flashing the stock firmware from the 1.54.651.8 OTA again and see if that normalizes your device.
Click to expand...
Click to collapse
I need someway to revert my Hboot while being S-ON. I was hoping somebody that had some knowledge could make and RUU with the proper CID to revert EVERYTHING back to stock. I mean I want to start from the bottom up. I don't know if this is possible without HTC releasing anything.
mjhuffer said:
How do I flash it without being S-off? Can I run it with S-On? I think I really just need a way to revert my Hboot to stock. I was hoping somebody had an RUU available that would just wipe everything and start from scratch.
---------- Post added at 12:56 PM ---------- Previous post was at 12:51 PM ----------
I need someway to revert my Hboot while being S-ON. I was hoping somebody that had some knowledge could make and RUU with the proper CID to revert EVERYTHING back to stock. I mean I want to start from the bottom up. I don't know if this is possible without HTC releasing anything.
Click to expand...
Click to collapse
No one can make a RUU it has to be leaked from HTC.
Sent from my 831C using Tapatalk
Konfuzion said:
No one can make a RUU it has to be leaked from HTC.
Sent from my 831C using Tapatalk
Click to expand...
Click to collapse
I figured that, is there any way to create a flashable zip with signed everything except for the recovery so I can possibly push it through TWRP. You have to understand I want to try everything possibly before returning this phone to sprint. I have a feeling they will want to ship it off to HTC if the vibration doesn't work.
mjhuffer said:
I figured that, is there any way to create a flashable zip with signed everything except for the recovery so I can possibly push it through TWRP. You have to understand I want to try everything possibly before returning this phone to sprint. I have a feeling they will want to ship it off to HTC if the vibration doesn't work.
Click to expand...
Click to collapse
You don't need to be S-OFF to flash the signed firmware.zip through HBOOT, which is why I suggested it.
---------- Post added at 01:54 PM ---------- Previous post was at 01:40 PM ----------
https://www.dropbox.com/s/cm6m61o78r0poe6/firmware.zip
Relock Bootloader, then fastboot oem rebootRUU, then fastboot flash zip firmware.zip.
Then you can unlock again if you want and flash custom recovery. But you can at least see if the firmware zip gets everything working properly again.
skizzled said:
You could try it multiple times. Reboot the phone, computer, change USB ports, etc.. Who knows, maybe it'll work.
I know the M8 I got S-Off on took the 1.54.651.8 OTA before I even bothered to actually mess with it (unlock bootloader, root, and S-Off) and it was perfectly able to do all of those things.
Click to expand...
Click to collapse
I never got a message of "You are out of luck" on my failed attempts. But....
First phone took me like 3 tries. Windows 7 x64
Second phone took like 4 failed attempts Windows 8.1 x64 (same computer) (timing out with over 2 minutes of dots......) using the exact same version of firewater as previous phone.
I was not sure if it was a Windows 8 issue.
Then I tried downloading the latest firewater and it was different from what I downloaded a month ago and worked the first time.
I agree. Try multiple times. Try with phone on WIFI vs Mobile Data. SO that Data is available quickly after adb reboot.
Try rebooting computer and try even another computer another USB port. Some computers have internal "USB Hubs". Try front vs Back etc.
I was able to do it on Windows 8.1 x64. I install latest HTC Sync. Then uninstall everything but the drivers.
I also had flashed Bad Boys 1.1 (Unlocked with S-ON) to get my rooted OS instead of manually rooting it. Then Factory Reset it. Turned on WIFI then did S-OFF.
Most rooted ROMs remove a lot of baggage that might interfere with rooting.
I'm still running all stock firmware though except for Recovery.
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
koolcat7 said:
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
Click to expand...
Click to collapse
It doesn't matter how many times you try. It won't work. Read the message.
koolcat7 said:
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
Click to expand...
Click to collapse
Ouch, pretty blunt message.
You don't need S-OFF to get wifi tether. All you need is HTC Unlock and Root.
S-OFF mainly allows you to flash firmware. You can only flash complete and signed firmware without S-OFF.
And each time you do, you'll have to reflash recovery.
I believe you can install several ROMs with S-ON that support Wifi Tether.
I ran "Wifi Tether Router" from Google Play ($1.99) with S-ON (HTC Unlock/Root) before S-OFF was available.
koolcat7 said:
Thanks for all your replies. I keep trying, even with wifi on, and get this message every time (see attached picture). I really need s-off for wifi tether and so many more things. Please, someone must know a work-around?
Click to expand...
Click to collapse
The Captain is right. I got on the IRC this morning and talked to the firewater guys. They didn't really say why but they were at least a good amount of help. I can't say I blame them for not releasing any information on why. I just wish I knew about bootloader exploits.
Also, I'm on windows 7 pro 64-bit. I have a laptop with win 8 64-bit, but am afraid to try on that PC due to ALL its USB ports are 3.0 (and firewater says to avoid 3.0 ports).
Captain_Throwback said:
You don't need to be S-OFF to flash the signed firmware.zip through HBOOT, which is why I suggested it.
---------- Post added at 01:54 PM ---------- Previous post was at 01:40 PM ----------
https://www.dropbox.com/s/cm6m61o78r0poe6/firmware.zip
Relock Bootloader, then fastboot oem rebootRUU, then fastboot flash zip firmware.zip.
Then you can unlock again if you want and flash custom recovery. But you can at least see if the firmware zip gets everything working properly again.
Click to expand...
Click to collapse
Does this firmware.zip possibly have the hboot and boot.img included? If not could you please make me one with it. It worked but the Hboot still says Tampered Relocked and my Radio and Open DSP say Invalid_Ver_Info and I still don't have vibration.
mjhuffer said:
Does this firmware.zip possibly have the hboot and boot.img included?
Click to expand...
Click to collapse
Yes.

[Q] update issue

Hello all I am a noob getting into the game, I am trying to get my m7 to update with no luck. I have an AT&T branded One running on versio 1.26.502.15 . I have tried all the little tricks to get it to find them, but nadda. I have been reading into all the resets, RUUs, and OTAs and honestly I'm just more confused. From what I read about manually installing OTAs, I haven't been able to find the right one to upgrade my version. I just want to get up to date with Android and Sense. If anybody could just point me in the right direction I would be so thankful. If there's any other info needed I'll get it up here.
Locked
S_on
Hboot 1.44
Android v.1.26.502.15
Sense 5.0
dirtrider129 said:
Hello all I am a noob getting into the game, I am trying to get my m7 to update with no luck. I have an AT&T branded One running on versio 1.26.502.15 . I have tried all the little tricks to get it to find them, but nadda. I have been reading into all the resets, RUUs, and OTAs and honestly I'm just more confused. From what I read about manually installing OTAs, I haven't been able to find the right one to upgrade my version. I just want to get up to date with Android and Sense. If anybody could just point me in the right direction I would be so thankful. If there's any other info needed I'll get it up here.
Locked
S_on
Hboot 1.44
Android v.1.26.502.15
Sense 5.0
Click to expand...
Click to collapse
do you have adb and fastboot installed on your computer? If yes, post the output of fastboot getvar all except the imei # and the serialno #
at&t phone must be connected to the at&t network to receive ota update, are you on at&t?
manually installing ota update require s-off, your phone is currently s-on. good new is its "pretty easy" to s-off on hboot 1.44, ok maybe not that easy for a new user but you should be able to s-off if you need to by following revone s-off guide.
if you are not on at&t network:
easiest solution (imo):
unlock the bootloader (this void warranty)
flash twrp recovery 2.6.3.3
flash the guru reset rom 5.12.502.2
or
more complicated but better (imo):
unlock bootloader
flash twrp recovery 2.6.3.3
root
s-off using revone
flash the latest ruu (4.18.502.7)
manually flash ota updates from 4.18.502.7 to 5.12.502.2
update issue
Thank you for the info I don't have adb fastboot installed guess I'll need to start there, I am using the new cricket gsm network which if I'm correct uses AT&T towers but I guess that's why I was unable to get the updates because I'm not actually on AT&T. Will I still need to get s-off with the first solution or not ? Thanks again for the help, I'll get on it and let you know how it goes.
dirtrider129 said:
Thank you for the info I don't have adb fastboot installed guess I'll need to start there, I am using the new cricket gsm network which if I'm correct uses AT&T towers but I guess that's why I was unable to get the updates because I'm not actually on AT&T. Will I still need to get s-off with the first solution or not ? Thanks again for the help, I'll get on it and let you know how it goes.
Click to expand...
Click to collapse
alray said:
do you have adb and fastboot installed on your computer? If yes, post the output of fastboot getvar all except the imei # and the serialno #
at&t phone must be connected to the at&t network to receive ota update, are you on at&t?
manually installing ota update require s-off, your phone is currently s-on. good new is its "pretty easy" to s-off on hboot 1.44, ok maybe not that easy for a new user but you should be able to s-off if you need to by following revone s-off guide.
if you are not on at&t network:
easiest solution (imo):
unlock the bootloader (this void warranty)
flash twrp recovery 2.6.3.3
flash the guru reset rom 5.12.502.2
or
more complicated but better (imo):
unlock bootloader
flash twrp recovery 2.6.3.3
root
s-off using revone
flash the latest ruu (4.18.502.7)
manually flash ota updates from 4.18.502.7 to 5.12.502.2
Click to expand...
Click to collapse
Could you tell me where to find the 5.12.502.2 reset Rom, I went to HTC guru and could not find it in the list, also what are your thoughts on the twrp 2.7, I read a few comments about it and seemed like people were having trouble with it on their One's, I wondered if it would be better to have the new version or if I should just stick with the other one. Thanks again for the help.
dirtrider129 said:
Could you tell me where to find the 5.12.502.2 reset Rom, I went to HTC guru and could not find it in the list, also what are your thoughts on the twrp 2.7, I read a few comments about it and seemed like people were having trouble with it on their One's, I wondered if it would be better to have the new version or if I should just stick with the other one. Thanks again for the help.
Click to expand...
Click to collapse
http://www.htc1guru.com/dld/guru_reset_m7_5-12-502-2_clsa-zip/
better to stick with 2.6.3.3 or 2.6.3.4 unless you want to experiment. there is a charging bug with 2.7.0.0 and it looks like there are also some other bugs with 2.7.1.0 for flashing roms, not sure if it was solved in 2.7.1.1. use 2.6.3.3 or .3.4 and youll be fine.
and no, you dont need s-off to use the reset rom. but a reset rom will not update all the firmware, you'll get an updated rom(software), on the hardware side, only recovery and radio will be updated (if you choose to flash stock radio and recovery at the reset rom installation). hboot will not be updated using this solution.
do a nandroid backup of your current config, just in case you need to restore if something goes wrong.
update question
[/Quote]better to stick with 2.6.3.3 or 2.6.3.4 unless you want to experiment. there is a charging bug with 2.7.0.0 and it looks like there are also some other bugs with 2.7.1.0 for flashing roms, not sure if it was solved in 2.7.1.1. use 2.6.3.3 or .3.4 and youll be fine.
and no, you dont need s-off to use the reset rom. but a reset rom will not update all the firmware, you'll get an updated rom(software), on the hardware side, only recovery and radio will be updated (if you choose to flash stock radio and recovery at the reset rom installation). hboot will not be updated using this solution.
do a nandroid backup of your current config, just in case you need to restore if something goes wrong.[/QUOTE]
After lots and lots of research into this before doing I've decided to go with viperone custom Rom, if I understand it right I won't have to mess with s-off for this,please correct me if I'm wrong. But I have found some conflicting instructions, I read somewhere that I will have to copy the boot.img from the Rom and flash it before flashing the Rom then others without that step, so I'm confused, I wanna male sure I do this right the first time. Also are there any files that I need to have updated before flashing a 4.4 sense 6 custom Rom or will it all be included in the Rom?
Thank you
Dirtrider
Hi there
Been a long time since I've posted and hope I'm in the right place. Did a search for my question and wound up here.
My phone is stock and s-on, I haven't done anything to it, it's exactly the same as when it came out the box, but I haven't been able to update the software in settings>about>software updates for a while now, it just keeps coming back with download unsuccessful. Any ideas how I can sort this, or do it another way?
Thanks in advance
Sent from my HTC One using XDA Free mobile app

Categories

Resources