Considering the imminent release of the s-off exploit (tests are already done), I have two important imho questions:
1. Assuming a device already has s-off, if HTC pushes an update with a patch (say, the ICS for example), will it overwrite the s-off, or it will only affect devices that havent used the exploit ?
2. If affecting all phones, then what processes must be firewalled in order to prevent any auto update that may carry the patch? I'm using Droid Wall, which is a free and very effective tool.
Thanks.
lgtsanev said:
1. Assuming a device already has s-off, if HTC pushes an update with a patch (say, the ICS for example), will it overwrite the s-off, or it will only affect devices that havent used the exploit ?
Click to expand...
Click to collapse
Usually devices with s-off are not able to install official updates.
And you can always downgrade the hboot to an older exploitable version. If you were to upgrade.
At least there are ways to so this on other devices.
Sent from my HTC_Amaze_4G using XDA
You cannot downgrade hboot now, so in my understanding, if an HTC patch goes through and bring your phone back to s-on (assuming you already had it s-offed), u wont be able to do it then as well. This is what I want to prevent, cuz I heard HTC patched some previous exploits for other phones, but dont know nothing about how exactly they do that: do they push an automatic update, will it work on already s-off devices or covers only devices that are still s-on, do we have to block certain processes from accessing the net in order to prevent updates? Thats what im asking, just precaution measures against an eventual f up in the future, because I dont think HTC would let go of one of their most expensive phones. So if anyone knows anything about this, issues with other devices, whatever, just share.
The more we know, the better... Cheers.
mike_seahawk said:
Usually devices with s-off are not able to install official updates.
Click to expand...
Click to collapse
That cannot be true, because there are people who bought s-off Amazes from retail stores with stock ROMs...
lgtsanev said:
That cannot be true, because there are people who bought s-off Amazes from retail stores with stock ROMs...
Click to expand...
Click to collapse
yeah roughly less than 1% of amaze users i'm sure, and the official updates dont usually correspond to the device being s-off, usually its mandated by the status of the bootloader. hence why a device can be s-off and still be downgraded to receive OTA.
Just instal a custom ics rom, and u wont have to worry about this problem
Sent from my NRGized Amaze...
via xda premium
I downgraded HBOOT and radio in the HTC wildfire s forum
Of the Amaze? Can you share how you did that?
Related
I know that the Evo 3D is planned to soon be rooted by AlphaRev. If I take the OTA will I still be able to get S-Off when the root meatod is released?
Take OTA or no?
I wouldn't, I'm still rockin the release day version. I'm sure when rom's are rolling out they will include all the updates and then some.
jedinegotiator said:
I know that the Evo 3D is planned to soon be rooted by AlphaRev. If I take the OTA will I still be able to get S-Off when the root meatod is released?
Take OTA or no?
Click to expand...
Click to collapse
Alpharev hasn't yet announced which hboots it will work with, but they did say it should work across a number of them. Personally, I would hold off on any OTA until you get full root, just to be safe. It would suck to take the ota and then find out that the method is only for the 1.30 hboot.
Sent from my PG86100 using XDA App
Simple answer. No.
If you want to root, NEVER take an OTA. This is rule #1
If you never plan on rooting, you should take the OTA.
I thought I saw somewhere that alparev or unrevoked said that they can s-off all available hboots for the time being
htownrep247 said:
I thought I saw somewhere that alparev or unrevoked said that they can s-off all available hboots for the time being
Click to expand...
Click to collapse
Yep I read that too...
Sent from my SPH-P100 using Tapatalk
htownrep247 said:
I thought I saw somewhere that alparev or unrevoked said that they can s-off all available hboots for the time being
Click to expand...
Click to collapse
Yes, they did announce that the tool they're developing should work across a bunch of different hboots, however they didn't specify which ones. I like to play things safe, so therefore I still say no OTA's. I am very anti-OTA. Soon enough there will be full root and it won't matter anyways.
Don't worry, the latest OTA (for now) using HBOOT 1.40 has been tested sucessfully.
So this works.
1.13.651.7 is (as I understand it), the latest OTA, and works fine.
Yeah, it's best just to play it safe and never OTA unless it fixes a bug that is absolutely critical. I've never taken one, never will. The phone runs just fine.
ieftm said:
Don't worry, the latest OTA (for now) using HBOOT 1.40 has been tested sucessfully.
So this works.
1.13.651.7 is (as I understand it), the latest OTA, and works fine.
Click to expand...
Click to collapse
Well, there you all have it. Right from the horses mouth. Taking the current OTA is safe. So go ahead and take the OTA if you feel the need to do so.
No OTA's ever!!!!
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!!
Due to WiFi issues on the release day OS, I took the 1.22 OTA and screwed root. I knew it would happen but the fixes outweighed the issues. I waited to see if root would be achieved via Regaw or the like since I didn't want to lose any of my configuration. Now... Sense 4.1 was just too tempting to pass up and since I wasn't rooted anyways, I went for it.
I decided to attempt root and start from scratch anyways as I was having random app issues and some bloat problems.
The root method from HTC Dev worked flawlessly on the new new OTA and I was able to load TWRP and SuperUser via fastboot (instructions can be found by searching as I did).
So now here is the question: where does this leave me as far as flashing ROMs... Obviously I am aware that I am S-On and know those limitations. My issue is if and where any limits may apply now that I am HBOOT 1.19. Will I be stuck with only 2.13 ROMs that we're built based on the new HBOOT or can I flash any Rom based on 2.13 (or even older revisions)? I cant risk bricking so I am asking to be cautious as well as your answers providing any new users coming in with new phones running the latest OTA.
Thanks
Why did HTC update hboot 1.15? Because they discovered an exploit flaw that we could gain S-OFF with, which is FAR better than being on HTC Dumlock. If you are not concerned with obtaining S-OFF via LazyPanda and the like, this should not be a concern.
Also, being on the new hboot means that backwards compatibility to ROMs that are not based on the new OTA could become an issue.
Sent from my LTEVO via XDA Premium
New h boot for you only means that you won't be able to get s-off for a very long time probably since nobody has figured out how to even s-off h boot 1.15 yet. You shouldn't have an issue flashing any rom from my understanding as long as it's through recovery.
Edit : I would listen to Michael on this one regarding ROMs sounds like he knows more lol.
Sent from my EVO using xda app-developers app
natefuhr said:
Due to WiFi issues on the release day OS, I took the 1.22 OTA and screwed root. I knew it would happen but the fixes outweighed the issues. I waited to see if root would be achieved via Regaw or the like since I didn't want to lose any of my configuration. Now... Sense 4.1 was just too tempting to pass up and since I wasn't rooted anyways, I went for it.
I decided to attempt root and start from scratch anyways as I was having random app issues and some bloat problems.
The root method from HTC Dev worked flawlessly on the new new OTA and I was able to load TWRP and SuperUser via fastboot (instructions can be found by searching as I did).
So now here is the question: where does this leave me as far as flashing ROMs... Obviously I am aware that I am S-On and know those limitations. My issue is if and where any limits may apply now that I am HBOOT 1.19. Will I be stuck with only 2.13 ROMs that we're built based on the new HBOOT or can I flash any Rom based on 2.13 (or even older revisions)? I cant risk bricking so I am asking to be cautious as well as your answers providing any new users coming in with new phones running the latest OTA.
Thanks
Click to expand...
Click to collapse
Yes, you will be stuck flashing 2.13 roms with the 2.13 kernel. However, you can use one of the workaround methods (fastboot, flash image gui, twrp dumlock) to flashing an older kernel, and then flash roms based on a previous OTA base.
A ROM doesn't include an HBoot though, so there shouldn't be ROM/HBoot compatibility issues, right?
No, you can flash whatever version of android you want
Rxpert said:
No, you can flash whatever version of android you want
Click to expand...
Click to collapse
I don't think that's quite right (I could be wrong though).
If he wants to flash a JB-based ROM, he will definitely have to flash the boot.img separately via one of the workarounds mentioned.
If he wants to move between Sense-based ROMs, he *might* be OK. But he will not get any tweaks the dev may have made to the kernel included with his respective ROM.
I was referring to the question above me that asked about ROMs interfering with hboots
Having an old ROM on a new hboot won't cause issues.
Naturally, you need to have a working kernel for your ROM. So yes, you'll need to make sure you have the right kernel.
If he goes from any ROM to a ROM on a different base you'll have to install the correct kernel. . But I don't think that's what he was asking
Sent from my EVO using Tapatalk 2
Got it. I thought you were replying in general.
natefuhr said:
Due to WiFi issues on the release day OS, I took the 1.22 OTA and screwed root. I knew it would happen but the fixes outweighed the issues. I waited to see if root would be achieved via Regaw or the like since I didn't want to lose any of my configuration. Now... Sense 4.1 was just too tempting to pass up and since I wasn't rooted anyways, I went for it.
I decided to attempt root and start from scratch anyways as I was having random app issues and some bloat problems.
The root method from HTC Dev worked flawlessly on the new new OTA and I was able to load TWRP and SuperUser via fastboot (instructions can be found by searching as I did).
So now here is the question: where does this leave me as far as flashing ROMs... Obviously I am aware that I am S-On and know those limitations. My issue is if and where any limits may apply now that I am HBOOT 1.19. Will I be stuck with only 2.13 ROMs that we're built based on the new HBOOT or can I flash any Rom based on 2.13 (or even older revisions)? I cant risk bricking so I am asking to be cautious as well as your answers providing any new users coming in with new phones running the latest OTA.
Thanks
Click to expand...
Click to collapse
I'd like to re-root after taking the OTA and I've searched all over for the instructions on how to load TWRP and SuperUser via fastboot, but can't find it. Can you assist?
Thanks
Rxpert said:
I was referring to the question above me that asked about ROMs interfering with hboots
Having an old ROM on a new hboot won't cause issues.
Naturally, you need to have a working kernel for your ROM. So yes, you'll need to make sure you have the right kernel.
If he goes from any ROM to a ROM on a different base you'll have to install the correct kernel. . But I don't think that's what he was asking
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Correct me if I'm wrong, but, a ROM includes a Kernel, so when you flash a ROM you're swapping kernels.
The only kernel incompatibility would be if you flashed a ROM then flashed a Kernel, then you have to be careful.
If anybody is absolutely certain that this isn't the case and not just guessing, let me know and I'll stand corrected.
pbarrett said:
Correct me if I'm wrong, but, a ROM includes a Kernel, so when you flash a ROM you're swapping kernels.
The only kernel incompatibility would be if you flashed a ROM then flashed a Kernel, then you have to be careful.
If anybody is absolutely certain that this isn't the case and not just guessing, let me know and I'll stand corrected.
Click to expand...
Click to collapse
That's true for 1.12, since it allows you to flash kernels through recovery. The newer versions don't. That's the reason for using the fastboot or dumlock workarounds. That being said, I haven't heard anyone confirm yet that these methods still work on 1.19...I'm interested to know.
Sent from my EVO LTE
I've been waiting for s-off forever, then it finally came but long story short gf saw update (hboot 1.15) and accepted and I'm wondering since there's still no s-off, and this is a very silly question but I've never used Dev unlock, is nandroid backup possible in case something does go wrong
om4 said:
I've been waiting for s-off forever, then it finally came but long story short gf saw update (hboot 1.15) and accepted and I'm wondering since there's still no s-off, and this is a very silly question but I've never used Dev unlock, is nandroid backup possible in case something does go wrong
Click to expand...
Click to collapse
From what I can tell... No. You have to run HTC Dev first in order to get to where you can load a recovery program at which point you will have already had to wipe your phone to factory defaults.
It's unfortunate and the main reason I waited so long to unlock this way but as previously stated, Sense 4.1 was too hard to pass on
om4 said:
I've been waiting for s-off forever, then it finally came but long story short gf saw update (hboot 1.15) and accepted and I'm wondering since there's still no s-off, and this is a very silly question but I've never used Dev unlock, is nandroid backup possible in case something does go wrong
Click to expand...
Click to collapse
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
PsiPhiDan said:
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
no, I let her take my phone for the weekend. she went camping with her her family and I dont feel comfortable knowing shes out in the middle of no where without a phone. her phone was disconnected because she lost her job 2 months ago and Im not about to pay $135 on top of my own bill
PsiPhiDan said:
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Hell, I don't even let my girlfriend use my phone unless she asks nicely and I always keep an eye on her.
SoraX64 said:
Hell, I don't even let my girlfriend use my phone unless she asks nicely and I always keep an eye on her.
Click to expand...
Click to collapse
Mine doesn't even know how to use my phone...it's "confusing". IPhone ftw
Sent from my EVO LTE
pbarrett said:
Correct me if I'm wrong, but, a ROM includes a Kernel, so when you flash a ROM you're swapping kernels.
The only kernel incompatibility would be if you flashed a ROM then flashed a Kernel, then you have to be careful.
If anybody is absolutely certain that this isn't the case and not just guessing, let me know and I'll stand corrected.
Click to expand...
Click to collapse
Yes, every ROM includes a kernel.
But Hboot 1.15 and above do not let you flash things to the boot partition in recovery. The kernel goes in the boot partition. So you can't flash kernels normally through recovery.
If your on a sense ROM and flash an AOSP rom, the phone wont boot
If your on an AOSP ROM and flash a sense ROM, the phone wont boot
If your on an old base and flash a new base, the ROM will have issues (if it even boots)
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-wip.html
PsiPhiDan said:
I am amazed at how many girlfriends have their boyfriend's phone and update things... I'm beginning to think it's the same cover up as when people say, "so I have this friend who... Blah blah blah..."
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Next, we are going to hear crap like, "my pet hamster ate my nandroid thumb drive."
Sent from my LTEVO via XDA Premium
My friend wants me to root his phone. Going to use HTC method. My question is, can I use the same bin.img from my phone for his phone. That way I can skip the oem unlock code?
Sent from my PG86100 using xda premium
I highly doubt it. Even if it's the same model, it's NEVER a good idea to try to use the same file from another phone, you could easily brick it.
demar01 said:
My friend wants me to root his phone. Going to use HTC method. My question is, can I use the same bin.img from my phone for his phone. That way I can skip the oem unlock code?
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Sitlet is right, it won't work. The codes are phone specific.
You might want to s-off his phone instead, he'll have less problems, and since you're rooting it, he's gonna come to you every time it has an issue.
It will better if you use revolutionary.io method. Thanks to this one your friend won't lose warranty and can easily install every custom kernel by any recovery.
Wysłane z mojego HTC EVO 3D X515m
Yeah, if the phone is on hboot 1.4 I suggest using revolutionary.io. If on 1.5 then downgrade it, it's not as complicated as it may seem and the easier control is nice to have.
Gonna ump-teen back the revolutionary method here. As long as your friend doesn't take OTA updates he should be fine. The only real problem with that is keeping the radios up to date.
But with the source code for ICS on the 3D out, I imagine more support for the 1.5X+ HBOOTs will be cropping up in the months to come
dubsie said:
But with the source code for ICS on the 3D out, I imagine more support for the 1.5X+ HBOOTs will be cropping up in the months to come
Click to expand...
Click to collapse
The JuopunutBear (wire trick) method for gaining S-OFF already supports doing it with hboots through the 1.58 bootloader that came with the official Sprint ICS 2.89 build.
The stock kernel that came with the 2.89 ICS build requires the 1.58 bootloader, but the ROM developers have been replacing that kernel with the VM leak kernel that runs with earlier bootloaders, including 1.4.
Once your phone is S-OFF, no matter which method you use to get there, it will stay that way unless you use the "fastboot writesecureflag" command to set it back to S-ON, so you can flash any OTA, RUU or bootloader you want without having to worry about losing your S-OFF status.
ramjet73
Just wanted some Insight
I got a new but preowned one from a guy he mentioned that it got s update ..some update recently for the software that patches the ability to soff .
What did this update supposedly fix or add?
Sent from my HTC One using xda premium
lojak29 said:
Just wanted some Insight
I got a new but preowned one from a guy he mentioned that it got s update ..some update recently for the software that patches the ability to soff .
What did this update supposedly fix or add?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I am guessing it is for Tmobile?
I have that same version.
It disables revone or moonshine for working so essentially s-off.
I was able to still unlock the bootloader via HTCDev and root using TWRP and SuperSU.
Not really sure what s-off does, since I am able to load custom roms and etc. with current setup anyways....
....
S-off lets us convert to the full GPE version and get ota. I hope devs find a way of getting s-off on 531.11
Sent from my HTC One using xda app-developers app
Htein said:
I am guessing it is for Tmobile?
I have that same version.
It disables revone or moonshine for working so essentially s-off.
I was able to still unlock the bootloader via HTCDev and root using TWRP and SuperSU.
Not really sure what s-off does, since I am able to load custom roms and etc. with current setup anyways....
Click to expand...
Click to collapse
s-off is security check off. it stops the bootloader from checking for signatures pretty much letting you flash Whatever aslong as the recovery accepts it. can also turn off the recoveries signature check but thats alot easier to do as the recovery alows you to do so freely.
And anyone wouldnt happen to know more info on this would they. as ive noticed sense i did the manual OTA update via HTC's site, regaining s-off is proving to be imensley didficult. "i s-on'd whiel debugging things and regret it lol"
From what I have been able to gather the updated 1.44 or 1.54 cannot be s-offed using revone or moonshine currently.
I'm pretty happy right now, all I care about is GPe 4.3 anyways. Running of 4.3 ROM, firmware, and radio with just unlocked boot loader
Sent from my HTC One using xda premium