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
Related
Regarding HBOOT;
1.46 and 1.47 can root, while 1.49 cannot, correct?
Regarding the rooting process;
Rooting the phone does not change the HBOOT version. The version originally on the phone will remain the same after root, this is assuming Ivan's guide has been used to root.
That is all, thanks in advance.
Anyone? I really don't want to take this to IRC ..
I believe this has already been discussed. Root is only acquired via "root image" no exploit has been found. Meaning old hboot can be rooted, new hboot can NOT. "From what info I know."
-------------------------------------
Sent via the XDA Tapatalk App
From what I have read the old Hboot was never actually rooted. A root access copy was leaked, and that is how we got root.
-------------------------------------
Sent via the XDA Tapatalk App
fKngFtd said:
I believe this has already been discussed. Root is only acquired via "root image" no exploit has been found. Meaning old hboot can be rooted, new hboot can NOT. "From what info I know."
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
homer169 said:
From what I have read the old Hboot was never actually rooted. A root access copy was leaked, and that is how we got root.
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Are either of you developers?
Regardless, if this hold true and the rooting process doesn't change your hboot version, I hold in my hand a miracle. I have a 1.49 Eris that's been rooted when it was on 1.5.
I still don't fully understand the hboot version debate going on, but I do know that my hboot version reads 1.49.
Anyone else want to chime in and explain what's going on here? I'd appreciate it.
I am not a developer, but I have a rooted Eris with hboot 1.49. I rooted before the v3 leak came out. When jcase posted the rooted rom I installed it. That's when my hboot changed. I never lost root, and my hboot was upgraded.
-------------------------------------
Sent via the XDA Tapatalk App
.mak: The rooted roms are all running bootloader 1.47.
Leaked users are on 1.49.
So yes, to all of your questions.
.mak: The rooted roms are all running bootloader 1.47.
Leaked users are on 1.49.
So yes, to all of your questions.
Click to expand...
Click to collapse
Unless you had root and installed Jcase's leakbase4rom. Then you would have root and 1.49.
-------------------------------------
Sent via the XDA Tapatalk App
.mak said:
Are either of you developers?
Regardless, if this hold true and the rooting process doesn't change your hboot version, I hold in my hand a miracle. I have a 1.49 Eris that's been rooted when it was on 1.5.
I still don't fully understand the hboot version debate going on, but I do know that my hboot version reads 1.49.
Anyone else want to chime in and explain what's going on here? I'd appreciate it.
Click to expand...
Click to collapse
I am not a dev, but I will link you to the explanation from a dev. Framework43 explains it well.
http://forum.xda-developers.com/showpost.php?p=6604000&postcount=13
*Edit: Oops, sorry .mak I just saw your reply in that thread. Lolz.
As it turns out, to those who didn't click the link above, the rooting process changes your HBOOT to 1.49 S-OFF, which is an engineering SPL, which is how we're able to install custom images to the Eris.
So, in short, my phone is not a miracle, it's just another rooted Eris, and my questions have been answered
So given your question. Does that mean that you can root, force s-off by following guide "backup before you root"?
Regarding HBOOT;
1.46 and 1.47 can root, while 1.49 cannot, correct?
Regarding the rooting process;
Rooting the phone does not change the HBOOT version. The version originally on the phone will remain the same after root, this is assuming Ivan's guide has been used to root.
That is all, thanks in advance.
Click to expand...
Click to collapse
-----------------------------------
Late reply, I'm not a dev, still in the process of learning how to program.
I'm currently stock (hboot 1.5,, software# 2.08.651.2,,prl version 21083). I am about to root as soon as I'm 100% sure of the procedure from start to finish. My question is, should i take any OTA updates before I root?,,,,,,,I'm fully aware of the risk in doing this, coming from the evo4g( really don't want to be stuck stock for months, while everyone else is flashing away),,,,I'm a firm believer of searching, before asking, but if there's a better software version to gain root from, I want to be running it.
I do realize that starting out with this version of software means I'm stuck with hboot 1.5,,just couldn't find any posts referencing later OTA software versions possibly being better or worse to root from
pappy76 said:
I do realize that starting out with this version of software means I'm stuck with hboot 1.5,,just couldn't find any posts referencing later OTA software versions possibly being better or worse to root from
Click to expand...
Click to collapse
Nope, it matters not what software version you're on. Only hboot, and in you're case, like me, you're screwed either way :'(
I guess I figured as much, thanks,,,I'm a little confused about current root methods for hboot 1.5,,,I see there's fastboot/copynpaste/htc unlock(not too scary),,,install SU,,,something, something can't unlock boot partition(no kernals),,,possibly fastboot install recovery in order to be able to do so. I also read in another thread, there are two ways. The HTC way and a better XDA way, of rooting,,,I'm sold on a better XDA way,,,any suggestions?
The only way to root hboot 1.5 is to use the htcdev unlock.
pappy76 said:
I'm currently stock (hboot 1.5,, software# 2.08.651.2,,prl version 21083). I am about to root as soon as I'm 100% sure of the procedure from start to finish. My question is, should i take any OTA updates before I root?,,,,,,,I'm fully aware of the risk in doing this, coming from the evo4g( really don't want to be stuck stock for months, while everyone else is flashing away),,,,I'm a firm believer of searching, before asking, but if there's a better software version to gain root from, I want to be running it.
Click to expand...
Click to collapse
Take the OTA (2.17.651.5) then unlock with htc method.
If you unlock now and use cstom recovery, you will have to flash stock recovery in order to update to (2.17.651.5) latest OTA.
And it will also break root i think. so better update first then unlock then root.
I have some updated info put together from several posts that may help you on your tour if hboot 1.50
[Guide] My Hboot 1.50 HTC Unlock/recovery/rom/kernel flashing notes
http://forum.xda-developers.com/showthread.php?t=1495358
Sent from my PG86100 using Tapatalk
mpgrimm2 said:
I have some updated info put together from several posts that may help you on your tour if hboot 1.50
[Guide] My Hboot 1.50 HTC Unlock/recovery/rom/kernel flashing notes http://forum.xda-developers.com/show....php?t=1495358
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
i think you have copied that link from another post of yours so it will not work as XDA automatically shortens the link with "...." so please replace the "show....php" with "showthread.php" or use http://forum.xda-developers.com/showthread.php?t=1495358
Thanks man. I've been trying to figure it out for a while.
Sent from my PG86100 using Tapatalk
mnomaanw said:
Take the OTA (2.17.651.5) then unlock with htc method.
If you unlock now and use cstom recovery, you will have to flash stock recovery in order to update to (2.17.651.5) latest OTA.
And it will also break root i think. so better update first then unlock then root.
Click to expand...
Click to collapse
i tryed that and that didnt work for me. i saw in the command line that it was unlock but the phone never when to the unlock screen. what should i do
Thanks for the info, I read another member saying he had to relock to update then unlock again,,,I took the 2.17.651.5 OTA today and plan to root tonite,,,also thanks for the links!!
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.
I'm just learning that there is a new OTA. Whatever the case, I have not received it yet but am curious as to how I should handle it. This phone still confuses me a bit when it comes to unlocking etc.
Currently I am S-On, Rooted and running Shrike's PAC-Man rom. I kinda been lazy about staying up to date with everything and just got in my routine of flashing new releases.
Now i'm reading about this update and new hboot versions and wondering what I should be doing now. Should I accept the update in my current status or should I be doing something else to update? What about my hboot version, i'm still at 2.25. Should I be updating that myself or just take the OTA to handle it. My apologies if this is a redundant question.
braveally said:
I'm just learning that there is a new OTA. Whatever the case, I have not received it yet but am curious as to how I should handle it. This phone still confuses me a bit when it comes to unlocking etc.
Currently I am S-On, Rooted and running Shrike's PAC-Man rom. I kinda been lazy about staying up to date with everything and just got in my routine of flashing new releases.
Now i'm reading about this update and new hboot versions and wondering what I should be doing now. Should I accept the update in my current status or should I be doing something else to update? What about my hboot version, i'm still at 2.25. Should I be updating that myself or just take the OTA to handle it. My apologies if this is a redundant question.
Click to expand...
Click to collapse
First, the updated wont be pushed to you because you aren't on a sense rom, and i think the AOSP has the OTAkill.apk but i would need to look for it.
Second, the update is a good thing. not only does it have a new hboot but it has new radios, firmware and other goodies for the phone.
if you were to do the update, i wouldnt wait for VZW to push it. there is a zip that is in the development forum that you may flash to get the benefits of the update.
if you go down this route it will make the phone 100% stock. You would have to do the dev unlock with token and flash a recovery to get back to root status.
if you were to do this you also need to back up internal sd card just in case.
EDIT: Here are the steps you would take if you wanted to update the phone.
http://forum.xda-developers.com/showpost.php?p=40831457&postcount=59
credit goes to brenuga give him all the thanks you can.
synisterwolf said:
First, the updated wont be pushed to you because you aren't on a sense rom, and i think the AOSP has the OTAkill.apk but i would need to look for it.
Second, the update is a good thing. not only does it have a new hboot but it has new radios, firmware and other goodies for the phone.
if you were to do the update, i wouldnt wait for VZW to push it. there is a zip that is in the development forum that you may flash to get the benefits of the update.
if you go down this route it will make the phone 100% stock. You would have to do the dev unlock with token and flash a recovery to get back to root status.
if you were to do this you also need to back up internal sd card just in case.
EDIT: Here are the steps you would take if you wanted to update the phone.
http://forum.xda-developers.com/showpost.php?p=40831457&postcount=59
credit goes to brenuga give him all the thanks you can.
Click to expand...
Click to collapse
Thanks and thank you brenuga. That clears things up for me.
Is there a better S-Off method? In S-Off and don't want to lose root again and have to lock the bootloader
Sent from my ADR6425LVW using xda app-developers app
sk8bert12 said:
Is there a better S-Off method? In S-Off and don't want to lose root again and have to lock the bootloader
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Flash this in HBOOT. Only will work for s-off people
http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
sk8bert12 said:
Is there a better S-Off method? In S-Off and don't want to lose root again and have to lock the bootloader
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You can be S-OFF and still get the OTA, you just have to be pure stock, or you can flash the files in the thread which Flyhalf posted below.
On my last Rezound, I flashed the updated hboot and radios while already S-OFF, rooted and running Nils' ROM. On my current ROM, I got the OTA downloaded while still pure stock, then unlocked bootloader, flashed Amon Ra, rooted, then got S-OFF. Obviously, if there are any subsequent OTA's, I'll have to wait for a flashable.
Flyhalf205 said:
Flash this in HBOOT. Only will work for s-off people
http://forum.xda-developers.com/showpost.php?p=40767819&postcount=33
Click to expand...
Click to collapse
Thanks for the link/post. But what does this exactly do to an S-Off Rezound? Will this update/install just the HBOOT/Radios?
I'm on Ineffabilis Deus v1.2 ICS 4.0.3. I believe this might have been from the leaked global ruu.
DigiDave said:
Thanks for the link/post. But what does this exactly do to an S-Off Rezound? Will this update/install just the HBOOT/Radios?
I'm on Ineffabilis Deus v1.2 ICS 4.0.3. I believe this might have been from the leaked global ruu.
Click to expand...
Click to collapse
That was from the Global Leak. But the zip will just update firmware such as hboot and radio and few other stuff
I'm s-off. If I flash the latest RUU (whatever it is), then get the new global OTA update, I will retain my s-off-ness, correct? I'll just have to re-root and flash a recovery?
rsage said:
I'm s-off. If I flash the latest RUU (whatever it is), then get the new global OTA update, I will retain my s-off-ness, correct? I'll just have to re-root and flash a recovery?
Click to expand...
Click to collapse
No zip file of any kind will get you back to s-on. you must use fastboot to write to the secure flag. FYI
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.