[Q] New HTC1: Any reason not to get OTA 4.3? - T-Mobile HTC One (M7)

I just bought a new HTC One on T-mobile, my first Android phone (I've been jailbreaking/modding/hacking an iPhone for the last 3 years). I'm used to the iOS world where you should never update to a new OS release because you'll lose the ability to jailbreak, but my impression is that that is not true for Android, so my question is...
Is there any reason I should not update my phone OTA to 4.3, or is there anything I need to do first if I plan to unlock/root my phone later, or are there any other warnings you would like to throw at me?
Thanks for any advice you can provide?

If you have hboot 1.44 I would soff first then you can update to whatever newer hboots tend to block certain hacks you can always update manually after that
Sent from inside the T.A.R.D.I.S

joselv456 said:
If you have hboot 1.44 I would soff first then you can update to whatever newer hboots tend to block certain hacks you can always update manually after that
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
actaully i think rumrunner works with 1.54 and 1.55 not certain though.
And so far nothing bad with OTA in my opinon other than the fact it wiped my data the first time i did it on device :/ but yea good idea to S-off before updating

Rumrunner does work with 1.54 and 1.55 it's very easy to use.
Sent from my HTC One using xda app-developers app

Thank you ALL for the replies - really great to get such quick helpful info.
I meant to say in my initial post something like "explain it to me as if I were a medium-smart 11-year-old" but I forgot. Some of your replies were a mystery to me but I think I've figured out most of it on my own now. Let me make sure I understand:
- I do in fact have HBOOT 1.44.0000, so I take it that your advice is to S-OFF first, before OTA update.
- I believe (from this RumRunner guide thread) that I cannot use RumRunner to S-OFF, and that I "should use other tools to S-OFF, like moonshine or revone".
- After S-OFF, I can just run OTA update to Android 4.3 normally without causing problems for future rooting/hacking/modding/etc.
- [Unclear on this part] I should wait to upgrade my HBOOT because it might "block certain hacks"?
Please let me know if I'm harboring any massive misconceptions or need to seek more education before I start mucking about with a phone ecosystem that's only 3 days old for me.
Any advice on using "moonshine" or "revone" or some other method for S-OFF with HBOOT 1.44? [I'm sure I can find guides on XDA, but since you've been so helpful I thought I might as well ask]
Does any of this cause a problem for either taking the phone to T-Mobile for warranty service or for returning the phone within the 14-day return period? Or is it easy to cover my tracks so that T-mo doesn't know I've messed with the bootloader etc? Or do they just not care?
Thanks again for the help, past and future...

Related

[S-ON ONLY!!!]How to re-rootif you have downloaded the newest OTA

<MOD EDIT>
THIS IS NOT SAFE FOR REGAINING S-OFF
DO NOT PERFORM THIS METHOD IF YOU WISH TO KEEP S-OFF
</MOD EDIT>
So i didnt want to wait for the devs to update thier roms, and i wanted the radio updates as well. for all those ppl say not to do the OTA you will losew root until a new method is found are not correct. Yes you will lose root, but you can get it back. and its easy. Here are the steps
1. Relock boot loader
2. apply RUU for the same rom version you are running http://forum.xda-developers.com/showthread.php?t=1645890
3. rerun RegawMOD EVO 4G LTE Rooter
3a. It will sucessfully unlock and flash the recovery on your phone, but it will fail to root it.
3b. Download the rooting files http://downloadandroidrom.com/file/HTCEvo4GLTE/rooting/Evo4GLTERoot2.zip
4. Extract the contents of the zip file
5. Copy the file CWM-SuperSU-v0.87.zip to your SD card
6. Reboot to recovery
7. Flash CWM-SuperSU-v0.87.zip
8. Reboot to system and Viola you have have a rooted install
But can you still unlock with Lazy Panda?
EDIT: I realize you can unlock with the RegawMod unlock, but I have no doubt HTC's unlock tool will work.
Try to lazy panda your new hboot
{ParanoiA} said:
Try to lazy panda your new hboot
Click to expand...
Click to collapse
This is really the main(only?) concern.
Sent from my LTEvo
You are not correct. People are not saying "Don't do the OTA because you'll lose root", they're saying "Don't do the OTA because you'll lose the ability to S-OFF".
This happened with the Evo 3D. We had S-OFF for HBOOT 1.4, and then an OTA comes that upgrades to HBOOT 1.5. The S-OFF exploit was patched with 1.5, making it damn near impossible to S-OFF.
Seriously. If you're even remotely considering S-OFF, don't bother with applying the OTA. Wait for ROM devs to incorporate the OTA into their custom ROMs, because they will do it in a way that doesn't change your HBOOT or any other sensitive partition.
LiquidSolstice said:
You are not correct. People are not saying "Don't do the OTA because you'll lose root", they're saying "Don't do the OTA because you'll lose the ability to S-OFF".
This happened with the Evo 3D. We had S-OFF for HBOOT 1.4, and then an OTA comes that upgrades to HBOOT 1.5. The S-OFF exploit was patched with 1.5, making it damn near impossible to S-OFF.
Seriously. If you're even remotely considering S-OFF, don't bother with applying the OTA. Wait for ROM devs to incorporate the OTA into their custom ROMs, because they will do it in a way that doesn't change your HBOOT or any other sensitive partition.
Click to expand...
Click to collapse
Sure you may lose the ability to "S-OFF" but in all honesty, with these phones I can do every thing with S-ON, that you can do with S-OFF, except i have a couple of extra steps. Honestly the only reason i would S-OFF is to flash the radios easier. but how many times do you acutually flash a different radio to your phone? I do about every time there is a new update.
This is really for the people the HTC and RegawMod Unlock. Lazy Panda ppl continue to heed the disclaimer. I have no desire to completly S-OFF, unless someone can come with with a compelling reason to do so.
HseloMein said:
Sure you may lose the ability to "S-OFF" but in all honesty, with these phones I can do every thing with S-ON, that you can do with S-OFF, except i have a couple of extra steps. Honestly the only reason i would S-OFF is to flash the radios easier. but how many times do you acutually flash a different radio to your phone? I do about every time there is a new update.
This is really for the people the HTC and RegawMod Unlock. Lazy Panda ppl continue to heed the disclaimer. I have no desire to completly S-OFF, unless someone can come with with a compelling reason to do so.
Click to expand...
Click to collapse
Dude, just listen to LiquidSolstice on this one. DO NOT OTA an already S-OFF PHONE! Literally in a few hours we will probably have a stock / rooted ROM posted. Just have patience.
HseloMein said:
Sure you may lose the ability to "S-OFF" but in all honesty, with these phones I can do every thing with S-ON, that you can do with S-OFF, except i have a couple of extra steps. Honestly the only reason i would S-OFF is to flash the radios easier. but how many times do you acutually flash a different radio to your phone? I do about every time there is a new update.
This is really for the people the HTC and RegawMod Unlock. Lazy Panda ppl continue to heed the disclaimer. I have no desire to completly S-OFF, unless someone can come with with a compelling reason to do so.
Click to expand...
Click to collapse
The compelling reason to S-OFF is the fact that HTC and Sprint are never made aware in the slightest that you have done anything to your phone. The Dev unlock runs and tells HTC and Sprint that you are messing with your device. If done correctly, S-OFF gives you complete unfettered access to your phone, and with the proper tools, you can ensure you don't have to deal with the warning text on the screen that almost criminalizes you for having the audacity to unlock your phone.
People who are S-ON and HTC Dev unlocked ultimately run into strange issues down the road. You just wait until full AOSP comes around. On the Evo 3D, it was a nightmare. Even on the One-X, they're having issues because their boot partition is still locked and they can't use custom kernels (though I don't think that's as much of an issue with our phones).
S-OFF is so easy to perform, and the ONLY type of soft-brick that sometimes happens when performing it can be easily fixed with a dedicated tool. There is literally no downside to being S-OFF.
HseloMein said:
with these phones I can do every thing with S-ON, that you can do with S-OFF
Click to expand...
Click to collapse
I'd love to see you have the H-boot say S-ON and ***locked*** while still rooted
While your at it, go ahead try to remove the red HTC text as well.
HseloMein said:
Sure you may lose the ability to "S-OFF" but in all honesty, with these phones I can do every thing with S-ON, that you can do with S-OFF, except i have a couple of extra steps. Honestly the only reason i would S-OFF is to flash the radios easier. but how many times do you acutually flash a different radio to your phone? I do about every time there is a new update.
This is really for the people the HTC and RegawMod Unlock. Lazy Panda ppl continue to heed the disclaimer. I have no desire to completly S-OFF, unless someone can come with with a compelling reason to do so.
Click to expand...
Click to collapse
Lol so much fail. Good luck with that bro. I'm keeping my s-off
No one should follow this guy. You better hope it doesn't come back to bite you in the ass.
And you sir are in denial.
Sent from my EVO using xda premium
Rxpert said:
I'd love to see you have the H-boot say S-ON and ***locked*** while still rooted
While your at it, go ahead try to remove the red HTC text as well.
Click to expand...
Click to collapse
And although this may seem like just a visual thing, I have a friend who sent his phone in Dev unlocked and they denied his Google Wallet claim to replace the phone.
He then got his phone S-OFF'd through LazyPanda, changed the bootloader text, and sent it in again, and granted, I didn't think it would go through, but they accepted it that time.
LiquidSolstice said:
And although this may seem like just a visual thing, I have a friend who sent his phone in Dev unlocked and they denied his Google Wallet claim to replace the phone.
He then got his phone S-OFF'd through LazyPanda, changed the bootloader text, and sent it in again, and granted, I didn't think it would go through, but they accepted it that time.
Click to expand...
Click to collapse
Well that is a compelling reason for me, but i still think the 1st post is good for ppl that do not want to S-OFF after doing an HTC unlock. Im sure there are other users out there like me. The disclaimers and watermarks dont bother me in the slightest.
HseloMein said:
Well that is a compelling reason for me, but i still think the 1st post is good for ppl that do not want to S-OFF after doing an HTC unlock. Im sure there are other users out there like me. The disclaimers and watermarks dont bother me in the slightest.
Click to expand...
Click to collapse
While I respect your choice, I must also respectfully disagree with it. Regardless of what I think, you did take the time to explain how to re-root, and for that, I can't fault you. Thanks for your contribution.
HseloMein said:
Well that is a compelling reason for me, but i still think the 1st post is good for ppl that do not want to S-OFF after doing an HTC unlock. Im sure there are other users out there like me. The disclaimers and watermarks dont bother me in the slightest.
Click to expand...
Click to collapse
A recognized developer warning us should be enough reason.
OMG pbedard thanking my post? The world has just ended, lol.
Nice to see you again pbedard
Forgive me if this is a stupid question, but if you do accept the new update and lose S-OFF can you not just run the original RUU to get back to the release image which allows you to S-OFF again?
Once you apply the ota it installs a new hboot that blocks the current s-off method so keep that in mind. I don't know if running a ruu reverts the hboot.
Sent from my EVO 4G LTE
RoidPusher said:
Forgive me if this is a stupid question, but if you do accept the new update and lose S-OFF can you not just run the original RUU to get back to the release image which allows you to S-OFF again?
Click to expand...
Click to collapse
Nope. Keep your hboot. It can be difficult if not impossible to downgrade hboot.
Sent from an EVO 4G LTE using Tapatalk 2.
HseloMein, would you mind editing the title of this thread (maybe add [S-ON] at the beginning) to indicate that it may affect the ability to get S-OFF in the future.
david279 said:
Once you apply the ota it installs a new hboot that blocks the current s-off method so keep that in mind. I don't know if running a ruu reverts the hboot.
Sent from my EVO 4G LTE
Click to expand...
Click to collapse
Is this fact or assumption on the HBOOT Update? I'm S-off and no damn way am I taking the update BUT I thought I'd ask just for general knowledge. Back on the 3D, while we did get the HBOOT update, at least if you were S-off before the HBOOT update you held on to that and weren't stuck like chuck with HBOOT 1.50.000, what a nightmare. We were able to downgrade the HBOOT as long as you were S-off but why go through all that pain. I guess the saving grace here is that we really do have a pretty good "official" Dev unlock that doensn't totally screw you like the half baked unlock we got from HTC for the EVO 3D.
I need to get the word out to any and all LTE owners I know to not take it before I can S-off their phones.... might be a busy rest of the week! :laugh:
Thanks

up-to-date instructions on downgrading to 1.4 for S-Off then upgrading to ICS.

up-to-date instructions on downgrading to 1.4 for S-Off then upgrading to ICS? *that period was supposed to be a question mark. opps*
SPRINT CDMA!
I've read many of the threads and have been keeping myself up to date on everything. HOWEVER, there really aren't any good real step by step instructions on start to finish. I DID NOT take the OTA to 4.0. I NEVER take OTA's! It's just that I received the phone with 1.5 already installed and made a choice to wait until ICS.
I'm still on 2.3.4
2.17.651.5
1.5 bootloader.
I've read through http://forum.xda-developers.com/showthread.php?t=1563342
I'd like it if someone can just re-write the entire thing from start to finish to end up with the OTA rooted S-off. Do I need to be 1.58 for ICS? There is just so much useless information throughout the entire site, it is hard to get exacts. Sadly I'm ready to do all of this now but after reading ALL of the instructions... It's not clear on exact steps for ICS without having issues. All those youtube videos are also out of date.
So what I need are exact files to download, exact steps.
I've currently downloaded:
1.Superwipe.zip 144KBs
3d-ICS-Deodex.zip 465,310 KBs
PG86IMG_2.17.651.5.zip 409,064 KBs
revolutionary-0.4pre4.zip 1,583 KBs copied my key too
PG86IMG.zip *no idea what this one does because it wasn't labelled right so won't use it* 12,190KBs
RUU_Shooter_S_Sprint_WWE_1.13.651.7_Radio_0.97.10.0530_NV_NV_SPCS_1.16_release_198109_Signed.exe
Also downloaded the [TOOL] HBOOT Downgrade Toolkit Live 8.2 CD and tested it to insure it works correctly.
When I got my phone, I already had the 1.5 bootloader on it. Therefore, I just waited. I knew that ICS was coming out so I didn't root my phone just yet. I've rooted my other phones in the past before like my original Evo.
The biggest favor I need is just Good instructions on what I really need for getting ICS fully installed as stock and stable as I can while being S-off and rooted.
Of course I'll press your thanks button for anyone that helps me out. plz no smartass replies on here. I think I've at least made an attempt. I just don't want to make any mistakes. Mistakes cost time and money.. I don't have the time. I'm not a beginner. I believe that if this gets created in a simple set of instructions... It would HELP A LOT OF people from asking the same question or saying, "HELP, I BRICKED MY PHONE" or something else silly like that.
ps, I really hate putting this in this thread as I don't think it'll get the right viewers to help me and others out the best. But I DO THANK YOU FOR TRYING.
I'd like it if someone can just re-write the entire thing from start to finish to end up with the OTA rooted S-off.
Click to expand...
Click to collapse
Well there really isn't a need to re-write that. The process is still the same for getting s-off. I can't really help you with that, as I have hboot 1.4 and never had to do that. But I do know the process for getting s-off is still the same.
Do I need to be 1.58 for ICS?
Click to expand...
Click to collapse
It seems to be that if you want to run the new kernel, you must be on hboot 1.58. That may change in the coming weeks, I'm sure someone will find a way around that. But you can run the kernel from the 2.17 VM leak, and from what I've been reading, that should work fine with the new rom.
sitlet said:
Well there really isn't a need to re-write that. The process is still the same for getting s-off. I can't really help you with that, as I have hboot 1.4 and never had to do that. But I do know the process for getting s-off is still the same.
It seems to be that if you want to run the new kernel, you must be on hboot 1.58. That may change in the coming weeks, I'm sure someone will find a way around that. But you can run the kernel from the 2.17 VM leak, and from what I've been reading, that should work fine with the new rom.
Click to expand...
Click to collapse
So therefore, what's the point of going to 1.40 if it is going right back to 1.58?
In other words... Should I continue to wait? But those instructions really aren't that clear when trying to go ICS. like maybe just add a few more steps for ICS?
If you don't downgrade to hboot 1.4, then you cant run revolutionary to gain s off... Once you are s off, you are good to go, because if you decide to upgrade the bootloader to 1.58, you will retain your s off status
sent from my EVO 3D
So therefore, what's the point of going to 1.40 if it is going right back to 1.58?
Click to expand...
Click to collapse
So you can get s-off.
In other words... Should I continue to wait?
Click to expand...
Click to collapse
Personally, I would wait at least a week or so to see if someone comes up with a workaround for the new hboot. But that's up to you.
But those instructions really aren't that clear when trying to go ICS. like maybe just add a few more steps for ICS?
Click to expand...
Click to collapse
Again, there is no need to re-write those instructions. ICS is just another rom/update like any other rom/update. Do those instructions, then flash an ICS rom like normal.
sitlet said:
So you can get s-off.
Personally, I would wait at least a week or so to see if someone comes up with a workaround for the new hboot. But that's up to you.
Again, there is no need to re-write those instructions. ICS is just another rom/update like any other rom/update. Do those instructions, then flash an ICS rom like normal.
Click to expand...
Click to collapse
when we allow 1.58... can it be downgraded without issues? I remember with other phones, we had to rewrite it to allow that to occur.
but yeah, I'm just going to wait a little longer. I refuse to allow sprint to rip of off on a phone then say we can't use it. that's why I root. They don't have the right to do that. I don't care about their profits. If they would invest in a good network, they wouldn't need to rip us off. because everyone would want them instead. yeah, I know I did a 360 on my subject. lol. my 2.3.4 crashed again today. lol. wth.

[Q] Stupid hboot questions

Hello all,
Just a quick question, I google'd around a bit with no solid answer. What's the deal with Hboots? Do you need a certain version to run a certain version of AOS? from what I could tell it sounds like toy need the 2.09 or above hboot to run JB. this true? I'm on 1.12 Hboot, stock rooted rom, S-on with TWRP recovery and going for s-off, but apparently need to update my hboot to do so. Is there an Hboot that is more desirable than another? are there still ENG bootloaders out there? Just dont wana bork my phone or myself with this last step.. sheesh, when did rooting get so complicated? Thanks in advance
9X
They have progressively become stricter. Each time a new hboot is released its due to changes made. Patching exploits, adding support for changes in hardware, little things like that. 1.12 was relatively open, 1.15 removed access to areas of the boot partition requiring kernels to be flashed differently, not too sure what 1.19 changed if anything, 2.09 removes r/w access to your system so any changes to system will revert upon reboot.
x9x0 said:
Hello all,
Just a quick question, I google'd around a bit with no solid answer. What's the deal with Hboots? Do you need a certain version to run a certain version of AOS? from what I could tell it sounds like toy need the 2.09 or above hboot to run JB. this true? I'm on 1.12 Hboot, stock rooted rom, S-on with TWRP recovery and going for s-off, but apparently need to update my hboot to do so. Is there an Hboot that is more desirable than another? are there still ENG bootloaders out there? Just dont wana bork my phone or myself with this last step.. sheesh, when did rooting get so complicated? Thanks in advance
9X
Click to expand...
Click to collapse
You only have to update your HBOOT to get S-OFF because the tool to S-OFF the 1.12 HBOOT is no longer supported. After that, there's no reason to touch your HBOOT.
is there a "best" hboot? as in enables the most hardware / most bug fixes / still exploitable?
x9x0 said:
is there a "best" hboot? as in enables the most hardware / most bug fixes / still exploitable?
Click to expand...
Click to collapse
No. They're all S-OFF-able at this point. Just stick with the DirtyRacun HBOOT you get after S-OFF is complete and you'll be fine.
And why is s-off for 1.12 no longer supported? If it's not detrimental anyone know how I can s-off it?
x9x0 said:
And why is s-off for 1.12 no longer supported? If it's not detrimental anyone know how I can s-off it?
Click to expand...
Click to collapse
Because Team Unlimited isn't supporting it anymore. Because it's a simple matter to RUU to a newer version and S-OFF it. There's no reason not to - I don't understand your hesitation.
Just dont want a newer more restrictive hboot period. but here goes 1.15
x9x0 said:
Just dont want a newer more restrictive hboot period. but here goes 1.15
Click to expand...
Click to collapse
Once you're S-OFF, it doesn't matter. Restrictions are all removed.
x9x0 said:
Just dont want a newer more restrictive hboot period. but here goes 1.15
Click to expand...
Click to collapse
The restrictions of Hboot are gone once you're S-off. It's just a number afterwards.
This is regardless of what Hboot you're on
Edit: Captain beat me to it. Hopefully you get the point now
The advice is free....the bandwidth, not so much
FinZ28 said:
The restrictions of Hboot are gone once you're S-off. It's just a number afterwards.
This is regardless of what Hboot you're on
Edit: Captain beat me to it. Hopefully you get the point now
The advice is free....the bandwidth, not so much
Click to expand...
Click to collapse
Not exactly - the stock HBOOTs don't have fastboot commands enabled unless they're unlocked. So while you have the freedom to flash whatever HBOOT you want, it's still best to have one of the DirtyRacun modded HBOOTs to get the full benefit.
Captain_Throwback said:
Not exactly - the stock HBOOTs don't have fastboot commands enabled unless they're unlocked. So while you have the freedom to flash whatever HBOOT you want, it's still best to have one of the DirtyRacun modded HBOOTs to get the full benefit.
Click to expand...
Click to collapse
Very true.
+1 for Captain Throwback.
The advice is free....the bandwidth, not so much
hboot 1.15 s-off completed, thanks guys... just didnt want to do something i was going to regret.
Who on earth would regret soff?
om4 said:
Who on earth would regret soff?
Click to expand...
Click to collapse
Someone who bricked their device because they flashed something they could, but shouldn't have . . . . I will say, there are probably some people that shouldn't S-OFF, just because they'll find a way to break stuff. But I would hope those people don't frequent this forum (though I'd probably be wrong . . . )
Captain_Throwback said:
Someone who bricked their device because they flashed something they could, but shouldn't have . . . . I will say, there are probably some people that shouldn't S-OFF, just because they'll find a way to break stuff. But I would hope those people don't frequent this forum (though I'd probably be wrong . . . )
Click to expand...
Click to collapse
You know better than that
The advice is free....the bandwidth, not so much
Well it seems everybody has had that sort of day even with s-on, at least in this forum. Most of the time it's hardly ever been device wrecking. There was a time when my inbox would flood lol
om4 said:
Well it seems everybody has had that sort of day even with s-on, at least in this forum. Most of the time it's hardly ever been device wrecking. There was a time when my inbox would flood lol
Click to expand...
Click to collapse
Thank God for devs
The advice is free....the bandwidth, not so much
Just didnt want to lockout or loose options. when I started doing this, it was easy to update to a version that sucked, in the process of trying to root or s-off and sometimes there was no way back, you were essentially stuck in limbo. That being said, I've rooted a LOT of phones for my self and other people, and never once bricked a phone. Not to say I havent been in no mans land where 90% of the people out there would call it bricked. Had more than a few looooong night undoing experiments gone bad. Although the victory of escaping brick-dom is super sweet, I Just dont have time right now to visit no mans land, reflow, jtag/reflash again. seems that now the devs have made this pretty much idiot proof, Incredible how far things have come.
x9x0 said:
Just didnt want to lockout or loose options. when I started doing this, it was easy to update to a version that sucked, in the process of trying to root or s-off and sometimes there was no way back, you were essentially stuck in limbo. That being said, I've rooted a LOT of phones for my self and other people, and never once bricked a phone. Not to say I havent been in no mans land where 90% of the people out there would call it bricked. Had more than a few looooong night undoing experiments gone bad. Although the victory of escaping brick-dom is super sweet, I Just dont have time right now to visit no mans land, reflow, jtag/reflash again. seems that now the devs have made this pretty much idiot proof, Incredible how far things have come.
Click to expand...
Click to collapse
Tell me about it. I took my son's OG EVO out last week and finally got S-off via Revolutionary. For $hits and giggles I even got my old Hero out and got it S-off, too. Probably the easiest phone I've done yet-just had to flash a zip file in recovery
The advice is free....the bandwidth, not so much

Update to .15 without new HBoot?

My device is stock, unrooted, S-On, AT&T. I want to get the new software pieces from the OTA update without taking the actual OTA itself because I do not want to update HBoot in case I decide to do S-Off again in the future. Is there a file or set of files I can install from the outside? Or can I flash just the new radio, or even get the phone to quit bugging me about the update?
My HBoot is 1.44, May 2013. My roommate has the same setup but he took the OTA and now his HBoot is 1.44, June 2013 and revone doesn't work on that version.
K.AuthoR said:
My device is stock, unrooted, S-On, AT&T. I want to get the new software pieces from the OTA update without taking the actual OTA itself because I do not want to update HBoot in case I decide to do S-Off again in the future. Is there a file or set of files I can install from the outside? Or can I flash just the new radio, or even get the phone to quit bugging me about the update?
My HBoot is 1.44, May 2013. My roommate has the same setup but he took the OTA and now his HBoot is 1.44, June 2013 and revone doesn't work on that version.
Click to expand...
Click to collapse
Just flash the stock 1.26.502.15 ROM from this thread. It doesn't contain any firmware files so your firmware will remain untouched.
K.AuthoR said:
My device is stock, unrooted, S-On, AT&T. I want to get the new software pieces from the OTA update without taking the actual OTA itself because I do not want to update HBoot in case I decide to do S-Off again in the future. Is there a file or set of files I can install from the outside? Or can I flash just the new radio, or even get the phone to quit bugging me about the update?
My HBoot is 1.44, May 2013. My roommate has the same setup but he took the OTA and now his HBoot is 1.44, June 2013 and revone doesn't work on that version.
Click to expand...
Click to collapse
I wouldn't wait to s-off if I were you. That update will end up running when you least expect it and then you're done.
jdk2 said:
I wouldn't wait to s-off if I were you. That update will end up running when you least expect it and then you're done.
Click to expand...
Click to collapse
I might as well.
My concern is, if I S-Off, can I then accept the OTA? Or how could I go about updating everything EXCEPT for HBoot?
K.AuthoR said:
I might as well.
My concern is, if I S-Off, can I then accept the OTA? Or how could I go about updating everything EXCEPT for HBoot?
Click to expand...
Click to collapse
S-Off doesn't affect OTA's. You just need stock recovery to accept them. But if that update installs to your phone, there's no telling when S-Off may be available. Once you're S-Off, you can flash anything and you'll remain S-Off.
jdk2 said:
S-Off doesn't affect OTA's. You just need stock recovery to accept them. But if that update installs to your phone, there's no telling when S-Off may be available. Once you're S-Off, you can flash anything and you'll remain S-Off.
Click to expand...
Click to collapse
Gotcha, excellent!
(first HTC Android device after coming from nothing but Nexus devices, so HTC's setup is totally foreign to me)
I just went ahead with the S-Off. Am I good to accept this OTA or will this override HBoot / return me to S-On? Or what if it runs while I'm asleep one night, would that screw me?
K.AuthoR said:
Gotcha, excellent!
(first HTC Android device after coming from nothing but Nexus devices, so HTC's setup is totally foreign to me)
I just went ahead with the S-Off. Am I good to accept this OTA or will this override HBoot / return me to S-On? Or what if it runs while I'm asleep one night, would that screw me?
Click to expand...
Click to collapse
Once you're S-Off, you remain S-Off until you change it. Accepting OTA at this point won't change that.
You can also manually update firmware and ROM.
Sent from my HTC One using xda app-developers app
ilal2ielli said:
Once you're S-Off, you remain S-Off until you change it. Accepting OTA at this point won't change that.
You can also manually update firmware and ROM.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Question, I understand the need for stock recovery to attain the OTA. I'm already s-off and Super CID and the like. What I'd like to know is the best method for flashing just the stock recovery to receive the OTA. Also, would having the device rooted, with bloatware removed, effect the device in any way, during installation of the OTA, or after?
Or on the other hand, would it just be best to manual flash the rom from here? I'd like to pretty much attain the all of the aspects of the rom, including firmware, radio etc. I'm wary of changing the H-Boot, even though i'm already s-off. I'd hate to fall into a situation later where I need to go s-on, then turn around and want to do s-off again, but can't, because of the h-boot change. I am trying to read up on everything as best as i can, but some of it is quite confusing, and i don't keep up with the forums like I used to. So I'd totally apprecate a little clarification. thanks.

[Q] S-Off/Root for HTC1 still running 4.1.2

I have an HTC One on T-Mobile still running Android 4.1.2 (Sense 5.0). I haven't updated because I intend to root the device (tbh, intended to 3 months ago) and when I asked about it back then I was advised to S-OFF first, then run OTA update, then root.
I'm just checking back to make sure that that is still the correct course of action, and that my understanding is more or less correct ... I believe that because I have hboot 1.44 I can *not* use rumrunner for S-OFF, and should use revone or moonshine instead (and I have no idea how to choose which one to use).
So my plan, unless anyone corrects my noobish misconceptions, is to:
1. decide between revone and moonshine
2. S-OFF
3. root
I have also read something about not updating my hboot from 1.44, but honestly I don't know when that would normally happen or what I have to do (if anything) to prevent/avoid it, or what relationship updating hboot has to the rooting process.
I hope you'll forgive my ignorance, and warn me if I'm headed in the wrong direction. Obviously I have some learning to do, and I plan to seek at least a remedial education in these concepts before embarking ... I guess that's what I'm doing now.
thanks for any assistance you can provide...
lhuge said:
I have an HTC One on T-Mobile still running Android 4.1.2 (Sense 5.0). I haven't updated because I intend to root the device (tbh, intended to 3 months ago) and when I asked about it back then I was advised to S-OFF first, then run OTA update, then root.
I'm just checking back to make sure that that is still the correct course of action, and that my understanding is more or less correct ... I believe that because I have hboot 1.44 I can *not* use rumrunner for S-OFF, and should use revone or moonshine instead (and I have no idea how to choose which one to use).
So my plan, unless anyone corrects my noobish misconceptions, is to:
1. decide between revone and moonshine
2. S-OFF
3. root
I have also read something about not updating my hboot from 1.44, but honestly I don't know when that would normally happen or what I have to do (if anything) to prevent/avoid it, or what relationship updating hboot has to the rooting process.
I hope you'll forgive my ignorance, and warn me if I'm headed in the wrong direction. Obviously I have some learning to do, and I plan to seek at least a remedial education in these concepts before embarking ... I guess that's what I'm doing now.
thanks for any assistance you can provide...
Click to expand...
Click to collapse
You can achieve S-Off and unlock (without HTCDev) using the HTC One toolkit (which utilizes revone) from squabbi here:
http://forum.xda-developers.com/showthread.php?t=2364445
From there you should have no problems updating or flashing to whatever you want. At that point - even a full conversion to Gev Edition, GPe, etc is most definitely do-able.:good:
PhoenixPath said:
You can achieve S-Off and unlock (without HTCDev) using the HTC One toolkit (which utilizes revone) from squabbi here:
http://forum.xda-developers.com/showthread.php?t=2364445
From there you should have no problems updating or flashing to whatever you want. At that point - even a full conversion to Gev Edition, GPe, etc is most definitely do-able.:good:
Click to expand...
Click to collapse
Wow, I just downloaded & opened that toolkit, thanks! I wish I had it three days ago (though probably learned more by not having it), but I'll still get good use out of it now.
I've seen a few statements implying that it's better to unlock "without HTCDev", but haven't seen an explanation ... have I lost something specific by going through HTCDev to get my unlock token? (Or is it just a general desire to not have big brother know that we're mucking around with our device?)
I'm now unlocked, rooted, S-OFF, and updated to 4.3, deciding what to tinker with next...
lhuge said:
Wow, I just downloaded & opened that toolkit, thanks! I wish I had it three days ago (though probably learned more by not having it), but I'll still get good use out of it now.
I've seen a few statements implying that it's better to unlock "without HTCDev", but haven't seen an explanation ... have I lost something specific by going through HTCDev to get my unlock token? (Or is it just a general desire to not have big brother know that we're mucking around with our device?)
I'm now unlocked, rooted, S-OFF, and updated to 4.3, deciding what to tinker with next...
Click to expand...
Click to collapse
Unlocking through HTCDev puts a flag on your device (in their database) making it harder to get repairs or warranty service (exchanges).
Have fun tinkering!

Categories

Resources