[Q] Regards to all variants and the 2.49 hboot - HTC One Max

My question is since all variants of the HTC One Max have received it's KitKat update I was wondering if everyone here has remained on the 2.49 hboot?
Also wondering since I'm on Verizon and my software version has gone from 1.11.605.4 to 2.16.605.2 with both firmware version using the 2.49 hboot if it was at all possible if I'm currently s-off and unlocked if I can flash Santods "no red text" 1.11.605.4 2.49 hboot to get rid of that annoying disclaimer about "this build is for development purposes only blah blah blah yada yada yada lol...
Has anyone tried this yet??
I don't want to be the first try and brick over something so stupid.
I went ahead and PM'ed Santod but I haven't received a response back from him yet.. I asked beaups as well and he said he wasn't sure what the out come of that would be.....
Again I don't want to be the first to try lol... I thought though since we are s-off and unlocked that we were able to swap hboots with no issue so long as the hboot is for the device you are using and not from another....
Any insight would be appreciated, and how is everyone liking official KItKat? What have you done with the update?? I'm using Xposed with the official KK update and it's def a little more functional on KK opposed to JB.. We can now actually enable navbar where as in stock JB it wouldn't work.... Thanks guys and gals, looking forward to hearing from everyone!!!!!

Yes I flashed it and im good
Sent from my HTC6600LVW using Tapatalk

So to clarify you are on KitKat and used the Jelly Bean 2.49 hboot and had no problems??
waco2hot33 said:
Yes I flashed it and im good
Sent from my HTC6600LVW using Tapatalk
Click to expand...
Click to collapse

I can only answer your "no red text" answer and that is I've took the update but I was S-on thought I was stuck but used the weaksauce method and gain s-off again unlocked rooted and yes I flashed the no red text with no problems and I'm on the new update with the new bootloader / HBoot
Sent from my HTC6600LVW using Tapatalk

Related

Leak 2.1 v3 or Rooted?

I have the leaked 2.1 v3 does that mean i rooted my phone to put it on it? Is my phone now rooted?
No. Your phone is not rooted. Leaked v3 is essentially the same as the upgrade from Verizon.
-------------------------------------
Sent via the XDA Tapatalk App
and because i have V3 im not able to Root right?
yes
Sent from my Eris using the XDA mobile application powered by Tapatalk
So NO custom ROMS for me...this sucks
Yep. You, me, and loads of others using the leaked versions. Not to worry though. the devs are working on rooting the leak for us. It may take some time so just be patient.
-------------------------------------
Sent via the XDA Tapatalk App
I'm hoping soon too, I just got a replacement with 2.1 and 1.49 hboot loaded because mine had trackball issue. The original was the same but thought I was going to get lucky with replacement. Guess I was wrong.
-------------------------------------
Sent via the XDA Tapatalk App
hang tight guys, devs are still working on root for leakers. they're looking at a couple attack vectors and will notify everyone once they've got something working
jestercing said:
I have the leaked 2.1 v3 does that mean i rooted my phone to put it on it? Is my phone now rooted?
Click to expand...
Click to collapse
What exactly is it that makes you think you have leak-V3?
Check your bootloader version (power phone up holding Vol-down+End/Power).
If it says 1.47.xxxx (S-ON), you can root
if it says 1.49.xxxx (S-OFF), you have already rooted
if it says 1.49.xxxx (S-ON), you have put a "leak" (V1, V2, or V3) on your phone and can not root.
Then, reboot and look at Settings->About phone->Software information. If you put a leak on there, you should be able to decipher which one it was by looking at this post on Androidforums.com
Note that you can not tell the difference between the OTA-2.1 and Leak-V3 from the O/S software information alone - determine that by looking at the bootloader (HBOOT) Version number and security status (S-OFF vs. S-ON).
bftb0
I have HBOOT 1.49 and I have S-OFF and I'm currently not rooted.
crax0r said:
I have HBOOT 1.49 and I have S-OFF and I'm currently not rooted.
Click to expand...
Click to collapse
There is only a single 1.49 S-OFF bootloader "in the wild" - and it is from the ROOT ROM.
That does not mean that you must have a rooted OS on top of it - you can "root" the Eris, in the sense of installing that very bootloader (1.49 S-OFF), and then back-install any OS you like on top of it (manually).
For instance, I have had stock 1.5 running on my phone for experiments, but with the root (1.49 S-OFF) bootloader sitting there as the bootloader. The "O/S" is not "rooted" - but the bootloader is there which would allow me to write anything I want to the phone. So, calling that "not rooted" is semantically accurate - if you are only talking about the OS on top.
Having said that, there is not a single chance that you have 1.49 S-OFF on your phone without it having been touched by the root-PB00IMG.zip HTC ROM at one point or another in its past. Either that or you work for HTC.
bftb0
Lucky you mine is s-on
-------------------------------------
Sent via the XDA Tapatalk App
Question,
I have 2.1 ota My HBoot is 1.46 and s=on
can this be rooted?
And why/how do I have Hboot 1.46 with 2.1 I havn't done anything but the OTA
[email protected] said:
Question,
I have 2.1 ota My HBoot is 1.46 and s=on
can this be rooted?
Click to expand...
Click to collapse
Yes.
[email protected] said:
And why/how do I have Hboot 1.46 with 2.1 I havn't done anything but the OTA
Click to expand...
Click to collapse
Your phone has the 1.46 bootloader precisely because it is an "older" phone (in relative terms), and also because it has only seen OTAs in it's operating history - the OTA process for the Eris has never replaced the bootloader. (There have been 3 OTAs now, and none of them replace the bootloader.)
Good luck with the rooting!
bftb0
Thank exactly what I needed to know.
Now off to root (screw up) my phone

S-OFF and the 3.14.605.12 OTA

Hi guys.
So I am getting a Rezound on Monday and I plan on doing S-OFF overtop the official ICS OTA.
But I don't want to mess up the phone. Has anybody tried S-OFF with the 3.14.605.12 OTA?
Any replies are appreciated.
Best regards,
Sam
droidian1441 said:
Hi guys.
So I am getting a Rezound on Monday and I plan on doing S-OFF overtop the official ICS OTA.
But I don't want to mess up the phone. Has anybody tried S-OFF with the 3.14.605.12 OTA?
Any replies are appreciated.
Best regards,
Sam
Click to expand...
Click to collapse
JuopunutBear s off is for the 3.14.605.5 leak, but that leak has the same radios as the ota.
I personally used the s off method while running 3.14.605.10 firmware with no problems so I don't see why the ota version wouldn't work
Sent from my ADR6425LVW using xda app-developers app
droidian1441 said:
Hi guys.
So I am getting a Rezound on Monday and I plan on doing S-OFF overtop the official ICS OTA.
But I don't want to mess up the phone. Has anybody tried S-OFF with the 3.14.605.12 OTA?
Any replies are appreciated.
Best regards,
Sam
Click to expand...
Click to collapse
You truly don't NEED s-off to get most of the roms to work while on the OTA firmware. Although, the phone will come with gingerbread. I say keep s-on/no root for like a week or 2 just so you can work out any kinks if you get a bad one. Also yes at this point, our current s-off procedure cannot really be patched up.
I think it should work with 3.14.605.12 also. I performed s-off being on 3.14.605.10
Snuzzo said:
Also yes at this point, our current s-off procedure cannot really be patched up.
Click to expand...
Click to collapse
Do you mean you can't go back S-On? Because yes you can. There's a thread in the dev section about it; it's just a fastboot command ("fastboot writesecureflag 3" or something like that).
Like the others have said, you should be able to S-Off when on the OTA since it has the same radios as the .5 and .10.
Thank you for your replies guys. I appreciate it. Do any of you recommend stock or an ICS rom to flash? I haven't had a HTC since I had a OG Droid Incredible (awesome device) so Ive been out of the loop for a while now. Lol.
Sent from my DROID3 using Tapatalk 2 (Soon to be Rezound)
Just did this last night. No problems.
carngeX said:
Do you mean you can't go back S-On? Because yes you can
Click to expand...
Click to collapse
No. You misread, It will be Verizon's failure if they attempt to patch up the s-off wire trick. Sorry I give more info than what's needed. For the OTA & S-off is concerned. Yes the current procedures work with the OTA's firmware.
Snuzzo said:
No. You misread, It will be Verizon's failure if they attempt to patch up the s-off wire trick. Sorry I give more info than what's needed. For the OTA & S-off is concerned. Yes the current procedures work with the OTA's firmware.
Click to expand...
Click to collapse
Oh, I get what you mean now. You mean the vulnerability used to gain S-Off cannot be patched, at the moment. Yeah, misread that initially, my bad.

S-on firmware upgrade question

I know there is a way to upgrade the firmware for s on but is there a way without updating the hboot?
Sent from my EVO using Tapatalk 2
Nope, the partition is locked and signed, 1.12 did have the ability though
RUU while ulocked bootloader
chriswbush said:
I know there is a way to upgrade the firmware for s on but is there a way without updating the hboot?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
I ran the latest RUU with bootloader unlocked, s-on, rooted and I got everything except the latest radio and hboot. You have to relock the bootloader, then run RUU to get a complete upgrade.
wwsorrells said:
I ran the latest RUU with bootloader unlocked, s-on, rooted and I got everything except the latest radio and hboot. You have to relock the bootloader, then run RUU to get a complete upgrade.
Click to expand...
Click to collapse
I was looking at that but I don't want the latest hboot and are you HTC dev unlocked with 1.15 hboot?
Sent from my EVO using Tapatalk 2
HTC dev unlocked
chriswbush said:
I was looking at that but I don't want the latest hboot and are you HTC dev unlocked with 1.15 hboot?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Yes, I used ZedoMax unlock tutorial to unlock the first time. Why do you not wish to have the latest hboot?
I was hboot 1.15 when I ran the latest RUU unlocked and updated on the firmware. I decided that having the latest radio was important and you can not get one without the other right now from what I could find. So, I now have the latest radio and hboot, I unlocked the bootloader once again and reflashed my custom ROM.
wwsorrells said:
Yes, I used ZedoMax unlock tutorial to unlock the first time. Why do you not wish to have the latest hboot?
I was hboot 1.15 when I ran the latest RUU unlocked and updated on the firmware. I decided that having the latest radio was important and you can not get one without the other right now from what I could find. So, I now have the latest radio and hboot, I unlocked the bootloader once again and reflashed my custom ROM.
Click to expand...
Click to collapse
Well I was just asking just in case they do manage to find a way to get s off on the 1.15 hboot and I would like to get it but it seems like its been forever and I would rather get my texts and calls etc so can you link that tutorial?
Sent from my EVO using Tapatalk 2
Tutorials for unlock, RUU, relock
chriswbush said:
Well I was just asking just in case they do manage to find a way to get s off on the 1.15 hboot and I would like to get it but it seems like its been forever and I would rather get my texts and calls etc so can you link that tutorial?
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Sure, here ya go.
Install SDK tools first - http://www.youtube.com/watch?v=oaNM-lt_aHw&feature=fvwrel
Relock bootloader - http://www.youtube.com/watch?v=5yS7yy4XVA4&list=SP53B1EB8DBE7A5B59&index=1&feature=plpp_video
Update with latest RUU - http://stockroms.net/file/HTCEvo4GLTE/RUU
Hope this helps...I love mine after the latest hboot and radio together. It now has none of those pesky issues I was fighting.
P.S. after you relock, the phone will NOT reboot. Just keep it on "bootloader usb" and then run the RUU from your computer. Then unlock again. It will be all updated and run great.
I would suggest waiting as well. Chances are your missed calls and texts aren't going to be fixed by a new radio
Sent from my EVO using Tapatalk 2
I think the real chances are that s-off will be achieved on hboot 1.19 first, anyway. I haven't found one credible indication of anyone working on either though...
Sent from my EVO using xda app-developers app
wwsorrells said:
I think the real chances are that s-off will be achieved on hboot 1.19 first, anyway. I haven't found one credible indication of anyone working on either though...
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Its being worked on. Nobody is going to announce "oh hay guize I'm working on getting S-OFF". You'll know who is is when they find S-OFF and announce it.
What makes you think 1.19 will be found first? That doesn't really make sense.
I just think it makes more sense to have the latest radio. It was updated by HTC for a reason and everyone that wants it, not being s-off already, has to do what I did. Consequently, since the update I have LTE nearly everywhere I go in NW Houston, prior to the update was spotty connectivity at best.
wwsorrells said:
I just think it makes more sense to have the latest radio. It was updated by HTC for a reason and everyone that wants it, not being s-off already, has to do what I did. Consequently, since the update I have LTE nearly everywhere I go in NW Houston, prior to the update was spotty connectivity at best.
Click to expand...
Click to collapse
Most people don't have LTE coverage yet, so for most the radio isn't worth hboot 1.19
Sent from my EVO using Tapatalk 2
Unless of course, you're having issues running a custom rom on the latest firmware and older hboot. Then, one may wish to look at the options even if they are the "most" as you say or the least as I clearly represent in your estimation.

Can I still get S-off?

I am using a T-mobile HTC One. It was previously rooted. I restored to stock by using the RUU from HTC. I unlocked the bootloader so I currently have unlocked S-on. My HBOOT Ver is: 1.44.0000. Radio Version is 4A.17.3250.20. Am I screwed or can I still get S-OFF? I have tried Revone but it's not working. Any Ideas?
toaks said:
I am using a T-mobile HTC One. It was previously rooted. I restored to stock by using the RUU from HTC. I unlocked the bootloader so I currently have unlocked S-on. My HBOOT Ver is: 1.44.0000. Radio Version is 4A.17.3250.20. Am I screwed or can I still get S-OFF? I have tried Revone but it's not working. Any Ideas?
Click to expand...
Click to collapse
Sorry dude, pretty much screwed until they find a work around for the .11 update. I made the mistake of accidentally S-On and forgetting to lock instead of relocking my bootloader (wanted to return for warranty purposes). After that I've tried pretty much everything from downgrading to the stock ROM using customs ROMS trying to edit RUU's to work with my phone (Do not try this, easiest way to brick your very expensive phone) Nothing works as of now, Htc and t-mobile screwed us by not giving us the Stock RUU they knew what they were doing. But yes you have to wait.
*NOTE* On the otherhand i did learn that i didn't need to lock my bootloader to return it for warranty purposes the guy at the t-mobile store replaced it right there for me no questions asked. But the replacement i got came with the updated .11 ROM which means no S-Off for me still.
Damn. That's what I was afraid of. I just kept reading that as long as you had 1.44 h-boot it was still possible, but that doesn't appear to be the case. Well thanks anyway for responding.
Sent from my HTC One using XDA Premium HD app
Wait I thought you could s-off with that hboot i thought 5xxx was unable to s-off
You can s-off hboot 1.44 as long as you haven't taken the latest tmobile ota or used the tmobile ruu, they patched whatever it was that allowed us to s-off in the latest version
Sent from my HTC One using Tapatalk 4 Beta
Can we downgrade?
If we go back to .8, can we S-OFF? I want to take this thing to GPE, but need S-OFF.
Tylormde said:
If we go back to .8, can we S-OFF? I want to take this thing to GPE, but need S-OFF.
Click to expand...
Click to collapse
Take a look at http://forum.xda-developers.com/showthread.php?t=2314582&page=469
Lots of info there. Some of it conflicting but in a nutshell, no if you've taken the .11 update from T-Mobile.
i would wait till revone or moonshine get a fix on it.
Or go the HTC dev way
Sent from my HTC One using xda app-developers app
cenedbs assiduous
Tylormde said:
If we go back to .8, can we S-OFF? I want to take this thing to GPE, but need S-OFF.
Click to expand...
Click to collapse
I have tried this and was unsuccessful. Luckily I was able to run the RUU and it was fine again but it won't achieve S-OFF
You can downgrade from .11 to .8 using a custom ruu. Google " downgrade from .11 to .8 rootzwiki" and you'll find it.
Sent from my HTC One using Tapatalk
Ok guys not to sound stupid but I've rooted plenty of phones and have had pretty much every top tier phone. I've rooted all my android phones. I just don't understand the s-off portion of it all. I have s-off and currently rooted. What advantage do I have over someone that doesn't have s-off? I got my one already rooted so I never went through the process. I guess that's why I'm confused. I'm used to Samsung phones.
When the update comes next week should i just wait for a rooted version of it? I'm assuming so.
Sent from my HTC One using Tapatalk
S-OFF basically allows you to do 2 main things you couldn't otherwise pertaining to Roms and such:
1- flash unsigned RUUs. You can flash custom firmware that don't belong to your device. IE: you can flash the newest 4.3 firmware prior to 4.3 releasing for the T-Mobile One.
2: get yourself out of a jam. Here's a great example. Let's say you flashed the stock GPE recovery and ROM. Your S-ON. You wanted the full GPE experience. Your phone took the newest update. It will flash 1.54 Hboot and update the boot loader to the black GPE version although you are S-ON and not running the GPE device. Without S-ON your SOL if you needed to go back to stock for whatever reason because the HBoot can't be rolled back on S-ON.
Its a good protection to have in your back pocket IMO
Sent from my HTC One using Tapatalk
So that would explain how I am able to flash Roms from the international version. Well I guess I better be careful with any RUUs that are to come. I need to figure out how I'm going to update when the tmobile One's 4.3 update comes this week.
Sent from my HTC One using Tapatalk
Jjday7 said:
So that would explain how I am able to flash Roms from the international version. Well I guess I better be careful with any RUUs that are to come. I need to figure out how I'm going to update when the tmobile One's 4.3 update comes this week.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
So once S-OFF is achieved, can flashing any RUU set it back to S-ON? If so, how can that be avoided?
I have a tmobile phone flashed with launch WWE firmware; don't care about WiFi calling or any carrier bloat, but did want the 1700 HSPA+. I'm thinking of clean flashing to latest Tmobile RUU to get the supposed LTE reception improvements, then going from there to back to launch WWE and to latest WWE (to try to retain settings).
zaos said:
So once S-OFF is achieved, can flashing any RUU set it back to S-ON? If so, how can that be avoided?
I have a tmobile phone flashed with launch WWE firmware; don't care about WiFi calling or any carrier bloat, but did want the 1700 HSPA+. I'm thinking of clean flashing to latest Tmobile RUU to get the supposed LTE reception improvements, then going from there to back to launch WWE and to latest WWE (to try to retain settings).
Click to expand...
Click to collapse
No you would have to purposely set it back to s-on, an RUU won't do it. Would you be doing the tmobile Thu then installing WWE Rom ? Or flashing WWE RUU? Cause the ruu would just reset everything XP
Sent from my HTC One using Tapatalk
grim489 said:
No you would have to purposely set it back to s-on, an RUU won't do it. Would you be doing the tmobile Thu then installing WWE Rom ? Or flashing WWE RUU? Cause the ruu would just reset everything XP
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm thinking:
Full backup with twrp
Flash ruu
Restore backup with twrp
Apply WWE update
Oh yeah then that should work just wanted to make sure :thumbup:
Sent from my HTC One using Tapatalk
grim489 said:
Oh yeah then that should work just wanted to make sure :thumbup:
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks. It does seem a bit like voodoo magic but I want to avoid any possible issues that people in the radio only thread have reported.
use rumrunner to achirve s-off. thats the only way then use revone to reset tamper
toaks said:
I am using a T-mobile HTC One. It was previously rooted. I restored to stock by using the RUU from HTC. I unlocked the bootloader so I currently have unlocked S-on. My HBOOT Ver is: 1.44.0000. Radio Version is 4A.17.3250.20. Am I screwed or can I still get S-OFF? I have tried Revone but it's not working. Any Ideas?
Click to expand...
Click to collapse
use rumrunner to achieve s-off then use revone to reset tampered flag on your bootloader.

4.3 JB ruu will NOT save you after you upgrade hboot

Edited for accuracy:
For those happy folks finally moving to 4.4.2 (Verizon and Sprint most recently) please keep in mind that we do NOT yet have an ruu for 4.4.2. If you are S-ON you will NOT be able to save yourself using any 4.3 ruu if you have updated your hboot. Keep in mind an hboot can be flashed without any other part of an update so make sure you know what you are doing and what you have done to your device.
Just a public service announcement to hopefully bring people back to reality before they go modding their new 4.4.2 goodness.
Can't 4.4's hboot replace itself with the RUU's hboot,
(like usual 2 pass RUU install)?
Or did you mean for S-ON devices?
Im sure some magic can be worked for those that are s-off and can flash non encrypted. S-on folks definitely have to watch out. Overall its just best that people think before they play.
Jiggity Janx said:
Im sure some magic can be worked for those that are s-off and can flash non encrypted. S-on folks definitely have to watch out. Overall its just best that people think before they play.
Click to expand...
Click to collapse
S-off should download. Might have to test lol
Sent from my HTC6600LVW using Tapatalk
Aren't the s-off'ed and unlocked devices able to use their respective RUU's to downgrade? Example like myself I wen't from 1.11.605.4 official to the new 2.16.605.2 that if I ran in to a problem I could do the 0P3PIMG.zip from SD method or do the fastboot oem rebootRUU with the vzw.t6.0P3PIMG_1.11.605.4.zip and I was under the impression we could downgrade or upgrade as we see fit so long as we are s-off??? Isn't that how it's always been? I thought s-on users only really had to be careful since they could only upgrade due to main version issue and also not having a KitKat RUU now available if they took the update while s-on.... Some clarity would be great! Honestly though I thought the way I just worded it is how it's always been with HTC devices...
Jiggity Janx said:
Im sure some magic can be worked for those that are s-off and can flash non encrypted. S-on folks definitely have to watch out. Overall its just best that people think before they play.
Click to expand...
Click to collapse
ALL of this discussion is why I started this thread!
It is important we get to the complete truth. IMO my OP stands valid until we have confirmation otherwise.
Jiggity Janx said:
ALL of this discussion is why I started this thread!
It is important we get to the complete truth. IMO my OP stands valid until we have confirmation otherwise.
Click to expand...
Click to collapse
Last night, @waco2hot33 ran the RUU and went s-on to take the OTA...and was able to regain s-off, root, and unlocked via WeakSauce/firewater s-off...Here's how he did it
But, once you're back to s-off, and have root, no matter what hboot you have, you can run the commands from @scotty1223's thread found HERE to unlock the new hboot
End of discussion?
Yeah that's incorrect hehe... For s-on users that stands true... They need to be extremely careful until something becomes available, but speaking for the Verizon users that took the OTA and are s-off... Unlocked is NOT necessary, just as long as they are s-off they can actually downgrade back to stock 4.3 for whatever the reason may be.. i.e.: warranty, bad flash, etc etc... It's 100% always been this way for all HTC devices that are s-off... It's by far the greatest feature or perk of having an HTC device... If you don't believe me then grab the encrypted vzw.t6_1.11.605.4 RUU and run it, you will see you will have no issues downgrading. While s-on users if they attempted they would get the main version to low error, s-off bypasses that...
Jiggity Janx said:
ALL of this discussion is why I started this thread!
It is important we get to the complete truth. IMO my OP stands valid until we have confirmation otherwise.
Click to expand...
Click to collapse
Murrda said:
Yeah that's incorrect hehe... For s-on users that stands true... They need to be extremely careful until something becomes available, but speaking for the Verizon users that took the OTA and are s-off... Unlocked is NOT necessary, just as long as they are s-off they can actually downgrade back to stock 4.3 for whatever the reason may be.. i.e.: warranty, bad flash, etc etc... It's 100% always been this way for all HTC devices that are s-off... It's by far the greatest feature or perk of having an HTC device... If you don't believe me then grab the encrypted vzw.t6_1.11.605.4 RUU and run it, you will see you will have no issues downgrading. While s-on users if they attempted they would get the main version to low error, s-off bypasses that...
Click to expand...
Click to collapse
Please read my post above yours. Waco went s-on, took the update and installed it, and was able to regain s-off via the link i posted above. Therefore, one COULD root the newest update whether they are s-on or s-off.
I did something similar but why did he s-on?? Def didn't have to do that... I got the OTA and it failed 2 times so I said F it and ran the encrypted RUU just to get back to a complete stock state in case it was a boot.img or something missing issue and I remained "s-off" and "unlocked", redownloaded the OTA after booting back up and the OTA then flashed perfectly fine with booting in to KitKat and still s-off and unlocked. Only thing I had to do was fastboot TWRP back and flashed the SuperSU v1.94 and I was straight!
Did he think he needed to be s-on to take the OTA?
Vinchenzop said:
Last night, @waco2hot33 ran the RUU and went s-on to take the OTA...and was able to regain s-off, root, and unlocked via WeakSauce/firewater s-off...Here's how he did it
But, once you're back to s-off, and have root, no matter what hboot you have, you can run the commands from @scotty1223's thread found HERE to unlock the new hboot
End of discussion?
Click to expand...
Click to collapse
Murrda said:
I did something similar but why did he s-on?? Def didn't have to do that... I got the OTA and it failed 2 times so I said F it and ran the encrypted RUU just to get back to a complete stock state in case it was a boot.img or something missing issue and I remained "s-off" and "unlocked", redownloaded the OTA after booting back up and the OTA then flashed perfectly fine with booting in to KitKat and still s-off and unlocked. Only thing I had to do was fastboot TWRP back and flashed the SuperSU v1.94 and I was straight!
Did he think he needed to be s-on to take the OTA?
Click to expand...
Click to collapse
Noob moment? Tired? Acid flashback? Your guess is as good as mine, but he went s-on and was able to regain s-off via WeakSauce temp-root and firewater s-off with newest OTA/firmware. So...success? lol
I got what you are saying.. You are stating it is possible to root unlock and s-off official KitKat but what Jiggity Janx created the OP for was saying to everyone to be careful in case they soft bricked hard bricked boot looped or what have you that when on official KitKat there phone may be rendered unusable because there is no KitKat RUU.... What good is a rooted phone if you can't boot it? I was stating that if you are s-off and can at least boot to hboot that you are 100% safe and can run the Jelly Bean RUU....
Vinchenzop said:
Please read my post above yours. Waco went s-on, took the update and installed it, and was able to regain s-off via the link i posted above. Therefore, one COULD root the newest update whether they are s-on or s-off.
Click to expand...
Click to collapse
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
But yes that is indeed good to know though, thanks for the info! Good to know s-on or off we can work with KitKat!
Verdict.....s-off allows full downgrade of everything via ruu. Firmware and hboot. Just tested myself.
Sent from my Nexus 7 using Tapatalk
Murrda said:
I got what you are saying.. You are stating it is possible to root unlock and s-off official KitKat but what Jiggity Janx created the OP for was saying to everyone to be careful in case they soft bricked hard bricked boot looped or what have you that when on official KitKat there phone may be rendered unusable because there is no KitKat RUU.... What good is a rooted phone if you can't boot it? I was stating that if you are s-off and can at least boot to hboot that you are 100% safe and can run the Jelly Bean RUU....
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
But yes that is indeed good to know though, thanks for the info! Good to know s-on or off we can work with KitKat!
Click to expand...
Click to collapse
I understand and agree, but if you're s-on, the likelyhood of you bricking your device is nearly null. If you're s-off, you could likely use the 4.3 RUU and downgrade your hboot (i did this yesterday during a brain lapse after taking/applying the update).
So if you're looking if being s-off allows you to downgrade your hboot, then the answer is yes.
dottat said:
Verdict.....s-off allows full downgrade of everything via ruu. Firmware and hboot. Just tested myself.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
And that's a second confirmations
LOL..... Thank you!!
dottat said:
Verdict.....s-off allows full downgrade of everything via ruu. Firmware and hboot. Just tested myself.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
---------- Post added at 10:25 PM ---------- Previous post was at 10:24 PM ----------
OP and or title should be corrected so it is not misleading to some looking for answers... Maybe I'll make a thread for users as reference for all the variants
I think the intent of the op was really meant for the users who are currently s-on and running KitKat. If they run into issues they likely won't be able to root and s-off and will be screwed as there currently isn't public KitKat ruu available.
Good discussion. Please don't discuss the intent of the thread anymore.
Sent from my Nexus 7 using Tapatalk
What did that mean ~~~> Don't discuss the intent of the thread anymore
dottat said:
I think the intent of the op was really meant for the users who are currently s-on and running KitKat. If they run into issues they likely won't be able to root and s-off and will be screwed as there currently isn't public KitKat ruu available.
Good discussion. Please don't discuss the intent of the thread anymore.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Vinchenzop said:
Therefore, one COULD root the newest update whether they are s-on or s-off.
Click to expand...
Click to collapse
Vinchenzop said:
I understand and agree, but if you're s-on, the likelyhood of you bricking your device is nearly null.
Click to expand...
Click to collapse
IMO if you can root it you can f it up. So s-on users do have some risk and currently there is no fix for them on 4.4.2 where there was a fix for them on 4.3 (encrypted ruu).
Good to see that soff users should be good to use a lower version ruu to downgrade if needed.
I have updated and downgraded to the stock version OS and hboot. But I'm also S Off. I had to use the decrypted RUU file though....
TappEd from my HTC One Max
Check out my website for encouragement....
www.projectintercession.blogspot.com
Murrda said:
What did that mean ~~~> Don't discuss the intent of the thread anymore
Click to expand...
Click to collapse
Lol...I meant let's not lose sight of the warning here. Noobs will be confused.
Sent from my Nexus 7 using Tapatalk

Categories

Resources