So what exactly is s-off/ s-on, or better yet is this something we can find on the phone, more so what is the exact and best description it's called.
tomh1979 said:
So what exactly is s-off/ s-on, or better yet is this something we can find on the phone, more so what is the exact and best description it's called.
Click to expand...
Click to collapse
S-On/S-Off is the bootloader security. It means either security is on (S-On) or security is off (S-Off). This switches between verifying images before they are flashed. When security is disabled, you can flash anything you want through the bootloader. If security is enabled, you will have to have the proper signatures. This means that if you have S-Off, you can flash any OTA or other update and not worry about losing root, as you can easily flash the root files (superuser permissions) after the update and have it working again. That's the jist of it anyway.
superlinkx said:
S-On/S-Off is the bootloader security. It means either security is on (S-On) or security is off (S-Off). This switches between verifying images before they are flashed. When security is disabled, you can flash anything you want through the bootloader. If security is enabled, you will have to have the proper signatures. This means that if you have S-Off, you can flash any OTA or other update and not worry about losing root, as you can easily flash the root files (superuser permissions) after the update and have it working again. That's the jist of it anyway.
Click to expand...
Click to collapse
if i used simple root, can i do Unrevoked forever over this?
So what exactly is s-off/ s-on, or better yet is this something we can find on the phone, more so what is the exact and best description it's called.
Click to expand...
Click to collapse
S-On/S-Off is the bootloader security. It means either security is on (S-On) or security is off (S-Off). This switches between verifying images before they are flashed. When security is disabled, you can flash anything you want through the bootloader. If security is enabled, you will have to have the proper signatures. This means that if you have S-Off, you can flash any OTA or other update and not worry about losing root, as you can easily flash the root files (superuser permissions) after the update and have it working again. That's the jist of it anyway.
Click to expand...
Click to collapse
Thanks for the reply that was helpful for me, and what I was looking to hear.
Sent from my PC36100 using XDA App
S-On/S-Off is the bootloader security. It means either security is on (S-On) or security is off (S-Off). This switches between verifying images before they are flashed. When security is disabled, you can flash anything you want through the bootloader. If security is enabled, you will have to have the proper signatures. This means that if you have S-Off, you can flash any OTA or other update and not worry about losing root, as you can easily flash the root files (superuser permissions) after the update and have it working again. That's the jist of it anyway.
Click to expand...
Click to collapse
if i used simple root, can i do Unrevoked forever over this?
Click to expand...
Click to collapse
If your already running froyo then you can't run simple root, however if you have eclair 2.1, I'd suggest it, or even suggest unrevoked3.
Sent from my PC36100 using XDA App
unrevoked forever and ROOT are two different things.
you must already have root (any root capable of flashing, does not matter which), in order to use unrevoked forever.
once you have unrevoked forever, then you can easily reroot or flash any rom if you lose root.
TeknoJnky said:
unrevoked forever and ROOT are two different things.
you must already have root (any root capable of flashing, does not matter which), in order to use unrevoked forever.
once you have unrevoked forever, then you can easily reroot or flash any rom if you lose root.
Click to expand...
Click to collapse
i know this!
unless that wasn't directed at me.
Rocklee99 said:
if i used simple root, can i do Unrevoked forever over this?
Click to expand...
Click to collapse
You should be able to just fine. Unrevoked Forever does something entirely different from Simple Root - it just requires that you have root and a custom recovery before you can use it.
Related
Hello, I did a search and wasn't able to find anything definite, so I'm curious: Is there a way to unlock NAND access and keep the current PRI? I know that Toast's method causes the 1.34 PRI so I'm wondering if there is any other way to go about it. Thanks!
Root with unrevoked 3. Unlock NAND with unrevoked forever. This does not require the leaked ENG bootloader (Toast's method) to be flashed as a signed update, so you do not need to flash the associated rcdata image and lose PRI 1.40
Unrevoked forever is a permanent patch which leaves NAND unlocked even if you apply an OTA which would remove the ENG bootloader.
rpearl said:
Root with unrevoked 3. Unlock NAND with unrevoked forever. This does not require the leaked ENG bootloader (Toast's method) to be flashed as a signed update, so you do not need to flash the associated rcdata image and lose PRI 1.40
Unrevoked forever is a permanent patch which leaves NAND unlocked even if you apply an OTA which would remove the ENG bootloader.
Click to expand...
Click to collapse
Awesome! Thanks a lot man!
Unrevoked forever IS NOT ROOT. What is so hard for people to understand about that?
To get the 1.4 pri you'll need too root using toast or similar (NOT unrevoked) and then load a FroYo ron that has a dialer capable of using pound codes. This has been talked about EXTENSIVELY there are tons of threads about this on here.
Sent from my PC36100 using XDA App
unrevoked forever is a tool to set your Android phone's security level to S-OFF. The security level is a flag stored on the radio; when the flag is S-OFF, the bootloader (HBOOT) will no longer check the signatures of firmware images before flashing them. This allows custom firmware images to be uploaded, including unsigned boot, recovery, splash1, and hboot images (as well as official images that have been modified). When the system is S-OFF, the NAND flash memory protection is also reduced; this allows all partitions (including /system) to be written to while the operating system is booted.
Click to expand...
Click to collapse
From their website.
phobos512 said:
Unrevoked forever IS NOT ROOT. What is so hard for people to understand about that?
To get the 1.4 pri you'll need too root using toast or similar (NOT unrevoked) and then load a FroYo ron that has a dialer capable of using pound codes. This has been talked about EXTENSIVELY there are tons of threads about this on here.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This is entirely the opposite of true.
Unrevoked 3 flashes a custom recovery and also allows root access from the system. This is what, prior to the strange and weird and slightly incorrect terminology introduced in these forums, is called "root access".
Since you now have a custom recovery (I fail to see any other way to get one without using the ENG bootloader and thus losing the 1.40 PRI that you intended to keep), you can apply the unrevoked forever update to unlock NAND. This is what reasonable people call "unlocked NAND" because you can write to the NAND chip while the system is booted. It is what is known here as "fully rooted" because... er... I have no idea why it is called that since it is unrelated to root access.
rpearl said:
This is entirely the opposite of true.
Unrevoked 3 flashes a custom recovery and also allows root access from the system. This is what, prior to the strange and weird and slightly incorrect terminology introduced in these forums, is called "root access".
Since you now have a custom recovery (I fail to see any other way to get one without using the ENG bootloader and thus losing the 1.40 PRI that you intended to keep), you can apply the unrevoked forever update to unlock NAND. This is what reasonable people call "unlocked NAND" because you can write to the NAND chip while the system is booted. It is what is known here as "fully rooted" because... er... I have no idea why it is called that since it is unrelated to root access.
Click to expand...
Click to collapse
Unlocked NAND != Able to use "su" command in shell to have root permissions
OP: Use Toast's method, flash a 2.2 Stock rooted ROM, and follow these instructions:
http://geekfor.me/faq/how-to-get-back-to-pri-1-40-on-evo/
drmacinyasha said:
Unlocked NAND != Able to use "su" command in shell to have root permissions
OP: Use Toast's method, flash a 2.2 Stock rooted ROM, and follow these instructions:
http://geekfor.me/faq/how-to-get-back-to-pri-1-40-on-evo/
Click to expand...
Click to collapse
Once again, unrevoked forever unlocks the NAND chip WITHOUT losing 1.40 PRI.
If you have not rooted yet, there is no reason to used the leaked engineering bootloader
Please, read the text of my post before correcting me.
rpearl is correct. I did what he said (unrevoked3 to get the custom recovery, then flashed unrevoked forever) and I now have full write access to /system while the phone is running (all root apps work fine) and I still have my 1.40 PRI.
Lol I find it pretty funny that Phobos tried to argue about that w/ Ryan haha
Just playing around...
I tried to run rageagainstthecage exploit but my adb will not reconnect. I even specified port and device name. My EVO goes unresponsive and won't completely lock screen with the lock button on top. OTA update? Or is this my Windows 7?
rageagainstthecage just not written for 2.3.3?
Anyone working on the Gingerbreak? Maybe I should be posting this in dev...
No, you can't root the OTA update yet. You'll have to wait until someone finds a new root method.
And no, you shouldn't post this in the development section.
(from... Evo/MIUI/Tapatalk)
So you're saying that this is bogus?
http://c-skills.blogspot.com/2011/04/yummy-yummy-gingerbreak.html
I'm saying it doesn't work for the Evo... at least not yet. You can always try it, but my guess is that if you can get it do anything, it'll be temp root.
I'm sure that someone will come out with a method soon enough.
(from... Evo/MIUI/Tapatalk)
temp root should be enough to gain full root, probably with a method like the zikronix method. just temp root, flash mtd-eng from toastcfh, flash rooted build, flash ur-soff, flash sprint lovers w/ amon-ra, and all should be good. might have to unroot and test. we'll see...
dkdude36 said:
temp root should be enough to gain full root, probably with a method like the zikronix method. just temp root, flash mtd-eng from toastcfh, flash rooted build, flash ur-soff, flash sprint lovers w/ amon-ra, and all should be good. might have to unroot and test. we'll see...
Click to expand...
Click to collapse
I only need long enough to flash my hboot, correct?
lil_bono said:
I only need long enough to flash my hboot, correct?
Click to expand...
Click to collapse
with temp root? only long enough to flash the mtd-eng.
gotcha
eng recovery
lil_bono said:
gotcha
eng recovery
Click to expand...
Click to collapse
no the mtd-eng. the part that controls the rules for the other partitions. you can't flash a recovery with temp root, but you can flash the mtd-eng with toast's modded version.
Sorry Im a little confused then. This overwrites the misc partition with engineering controls of some sort?
i think we're confusing eachother a bit lol. so rageagainstthecage lets you get temp root, in which you can flash toast's mtd-eng to the misc partition, allowing you to install a rooted pc36img.zip, allowing you to flash unrevoked forever by booting a recovery from your comp (also toast) which allows you to install a permanent recovery. confusing imo
anyone know which ruu to use to downgrade from 2.3.3?
my idiot friends updated the phones lost root and are crying about it.
The last 2 I have tried both fail with bootloader errors.
anyone know which one to use?
You say they had root, are they s-on or s-off?
It's S-ON now.
the exe is the best way to do this I take it?
**** wrote off and thought on. I swear my fingers are out to get me!
Disable fast boot, reinstall amon ra from sdcard, then flash superuser. Tried to get you links to everything, but bad coverage over where I'm at.
echarette1 said:
Disable fast boot, reinstall amon ra from sdcard, then flash superuser. Tried to get you links to everything, but bad coverage over where I'm at.
Click to expand...
Click to collapse
I should have wrote S-ON.
I have amon ra and the synergy nightly I want. Just need to get it downgraded back!
S-on and updated with the ota, friends are stuck till a new method is developed. This is because the hboot was updated with the ota.
So anyone aware of anyone actively working on a new exploit?
what exactly is the difference between s-on and s-off
Foggie is so Epic said:
what exactly is the difference between s-on and s-off
Click to expand...
Click to collapse
s-on = security on, enjoy your factory phone
s-off = security off, flash your own rom's, customize, really enjoy your phone!
Jadigy said:
s-on = not rooted, enjoy your factory phone
s-off = rooted, flash your own rom's, customize, really enjoy your phone!
Click to expand...
Click to collapse
This is not correct.
The difference between S-Off and S-On is simply the ability to flash unsigned rom image files. It's a security feature of the bootloader. If it's On, you cannot flash unsigned roms/image files, it checks for a specific file signature and if it doesn't find it, it doesn't allow the flash. When it's S-Off, that signature checking is disabled, so you can flash anything you like.
It has nothing to do with Root. You could be S-On and still have root, or even be S-Off and not have root. Root is on the Android operating system level, S-Off/On is on the bootloader/firmware level.
A while back I heard about updating hboot? Why would someone do that? Is it worth it?
Thanks!
Sent from my ADR6300 using xda premium
jimbub said:
A while back I heard about updating hboot? Why would someone do that? Is it worth it?
Click to expand...
Click to collapse
Why would someone update HBOOT?
1. Because we can.
2. Newer is better, right?
3. Because updating HBOOT gives you the option of unlocking the bootloader via htcdev, which in turn gives a more reliable path to root access. It also brings with it some developer-friendly fastboot features, such as booting the system on a test kernel without actually changing the system (thus allowing for much safer kernel testing, things like that).
For the average already-rooted user like myself (especially one who already has s-off, as your sig indicates you do), reasons 1 and 2 are the only ones that are of any real consequence. But, for those reasons - I updated my HBOOT.
I did reason 3 for the ability to to test kernels via fastboot honestly.
musical_chairs said:
Why would someone update HBOOT?
1. Because we can.
2. Newer is better, right?
3. Because updating HBOOT gives you the option of unlocking the bootloader via htcdev, which in turn gives a more reliable path to root access. It also brings with it some developer-friendly fastboot features, such as booting the system on a test kernel without actually changing the system (thus allowing for much safer kernel testing, things like that).
For the average already-rooted user like myself (especially one who already has s-off, as your sig indicates you do), reasons 1 and 2 are the only ones that are of any real consequence. But, for those reasons - I updated my HBOOT.
Click to expand...
Click to collapse
If I were to do it, it wouldn't affect my s-off or root, right? Also, how would I do it?
Thanks!
Sent from my ADR6300 using xda premium
jimbub said:
If I were to do it, it wouldn't affect my s-off or root, right? Also, how would I do it?
Thanks!
Click to expand...
Click to collapse
RIght. You can either download the PB31IMG.zip from here and flash it through the bootloader:
http://dinc.does-it.net/Hboots/Hboot_1.07/
...or, since you're probably going to want to unlock it anyway, you can head on over to htcdev and run their RUU. cmlusco has a good guide for doing that here:
http://forum.xda-developers.com/showthread.php?t=1506258
...and scotty1223 has an even more detailed guide here:
http://forum.xda-developers.com/showthread.php?t=1600904
You'll only care about the first part, unlocking the bootloader via htcdev, as you already have CWM recovery, root, and s-off.
musical_chairs said:
RIght. You can either download the PB31IMG.zip from here and flash it through the bootloader:
http://dinc.does-it.net/Hboots/Hboot_1.07/
...or, since you're probably going to want to unlock it anyway, you can head on over to htcdev and run their RUU. cmlusco has a good guide for doing that here:
http://forum.xda-developers.com/showthread.php?t=1506258
...and scotty1223 has an even more detailed guide here:
http://forum.xda-developers.com/showthread.php?t=1600904
You'll only care about the first part, unlocking the bootloader via htcdev, as you already have CWM recovery, root, and s-off.
Click to expand...
Click to collapse
Okay, thanks! Will the RUU affect my current rom? IIRC, doesn't that wipe your phone? If yes, couldn't I just restore a nandroid?
Thanks a ton!
jimbub said:
Okay, thanks! Will the RUU affect my current rom? IIRC, doesn't that wipe your phone? If yes, couldn't I just restore a nandroid?
Thanks a ton!
Click to expand...
Click to collapse
No, it's not really an RUU. It's an update to Hboot only and it shouldn't wipe anythingg.
I can confirm that using the below attached stock signed recovery will allow S-off stock rooted users to take the update and still be able to flash custom recovery/root with no problems. Thank Zarboz for the recovery
flash this recovery in fastboot... accept the OTA... reboot to bootloader and flash your custom recovery of choice and re-flash SU.zip
https://docs.google.com/file/d/0BxPOyPCGUoH1TGFSNVE2U25uQkk/edit?usp=sharing
Will this also work for those of us who are HTCdev unlocked from day one? Or do we have to have S-off, if so why?
simo24 said:
Will this also work for those of us who are HTCdev unlocked from day one? Or do we have to have S-off, if so why?
Click to expand...
Click to collapse
It did not relock me. I would say you can probably do the same thing. S-off wasn't a factor in this one.
Sent from my Nexus 7 using Tapatalk 4
Can I flash and install if im on bone stock, a custom sense rom?
dottat said:
I can confirm that using the below attached stock signed recovery will allow S-off stock rooted users to take the update and still be able to flash custom recovery/root with no problems. Thank Zarboz for the recovery
flash this recovery in fastboot... accept the OTA... reboot to bootloader and flash your custom recovery of choice and re-flash SU.zip
https://docs.google.com/file/d/0BxPOyPCGUoH1TGFSNVE2U25uQkk/edit?usp=sharing
Click to expand...
Click to collapse
so you are java card s-off'ed?
if so this is good info,as the modified mid was a concern.
are you stock cid,or still vzw cid?
scotty1223 said:
so you are java card s-off'ed?
if so this is good info,as the modified mid was a concern.
are you stock cid,or still vzw cid?
Click to expand...
Click to collapse
Yes. Stock (vzw) cid and that modified mid remember I discovered that
In a nutshell, this ota only cared about stock recovery. Update installed exactly like it should, firmware and all.
Sent from my Nexus 7 using Tapatalk 4
Can we read this to mean that the OTA does not affect the currently used root exploit? If so, I'll let it update before shipping out to Sonic on Monday.
dottat said:
Yes. Stock (vzw) cid and that modified mid remember I discovered that
In a nutshell, this ota only cared about stock recovery. Update installed exactly like it should, firmware and all.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
godhamba said:
Can we read this to mean that the OTA does not affect the currently used root exploit? If so, I'll let it update before shipping out to Sonic on Monday.
Click to expand...
Click to collapse
If you're talking about Sonic's method, it's not a root exploit. It's an actual HTC support tool. Nothing released is going to break HTC's support tools.
Yup, got that. I wasn't being clear. I meant that if this doesn't break the existing root exploit, I wanted to simply go ahead and let it update (and thereby get rid of the intermittent pop-ups) before sending it off to Sonic for his S-OFF. I don't want to be in the situation where the phone is S-OFF'ed, but I am unable to stay rooted because this OTA has patched the known root exploit.
one4thewings said:
If you're talking about Sonic's method, it's not a root exploit. It's an actual HTC support tool. Nothing released is going to break HTC's support tools.
Click to expand...
Click to collapse
godhamba said:
Yup, got that. I wasn't being clear. I meant that if this doesn't break the existing root exploit, I wanted to simply go ahead and let it update (and thereby get rid of the intermittent pop-ups) before sending it off to Sonic for his S-OFF. I don't want to be in the situation where the phone is S-OFF'ed, but I am unable to stay rooted because this OTA has patched the known root exploit.
Click to expand...
Click to collapse
My apologies. With S-OFF you are able to flash a custom recovery, which will then allow you to flash a custom ROM that will have root baked in. If you like the Sense UI, Andybones has a fantastic ROM option in BoneStock which will give you the best of both worlds. Rooted and Stock Sense experience. So you shouldn't worry about the OTA if you plan on getting S-OFF.. because you can run a ROM that will offer you root access.
godhamba said:
Yup, got that. I wasn't being clear. I meant that if this doesn't break the existing root exploit, I wanted to simply go ahead and let it update (and thereby get rid of the intermittent pop-ups) before sending it off to Sonic for his S-OFF. I don't want to be in the situation where the phone is S-OFF'ed, but I am unable to stay rooted because this OTA has patched the known root exploit.
Click to expand...
Click to collapse
Unless I'm mistaken, if you are S-OFF there is no "exploit" needed for root access. S-OFF means you can simply flash SU and you have root - it doesn't require any exploits as S-OFF gives you complete read/write privileges to the entire system.
I flashed it and tried the update but it still failed ... I am thinking it is probably because I de-bloated the stock image and it doesnt like that.
No apologies needed at all. I appreciate the informed reply! And you cleared up a misconception I still retained. I've heard Andy's ROM is a perfect debloat and tweak up of the stock experience. I *cannot* wait to have the ability to kill and app by long-holding the back button. That is something I've grown so used to that, I feel majorly inconvenienced without it.
one4thewings said:
My apologies. With S-OFF you are able to flash a custom recovery, which will then allow you to flash a custom ROM that will have root baked in. If you like the Sense UI, Andybones has a fantastic ROM option in BoneStock which will give you the best of both worlds. Rooted and Stock Sense experience. So you shouldn't worry about the OTA if you plan on getting S-OFF.. because you can run a ROM that will offer you root access.
Click to expand...
Click to collapse
mrjinglesusa said:
Unless I'm mistaken, if you are S-OFF there is no "exploit" needed for root access. S-OFF means you can simply flash SU and you have root - it doesn't require any exploits as S-OFF gives you complete read/write privileges to the entire system.
Click to expand...
Click to collapse
you are not mistaken. correct all around, once S-OFF, your "Security" is now Off.. "S-Off"
anyway, this means you can just fastboot a custom recovery and flash a custom ROM that already has root built into it.
dottat said:
flash this recovery in fastboot... accept the OTA... reboot to bootloader and flash your custom recovery of choice and re-flash SU.zip
Click to expand...
Click to collapse
To verify... the process is this:
Prerequisite: Have all HTC drivers installed with abd, etc. All that android stuff... same stuff to flash custom recovery in the first place, etc.
1. Boot into bootloader. Choose Fastboot.
2. Plug your phone into your computer with the microUSB cable.
3. In your android directory command line.. you're going to type: fastboot flash recovery htconerecovery_signed.img
4. Then you're going to type fastboot erase cache
Now you're going to choose to reboot your device... you're going to take the OTA...
Then you're going to go through a similar process to flash the custom recovery back to the device?
Does that sound about right?
Yep...that's it!
Sent from my HTC6500LVW using Tapatalk 2
one4thewings said:
To verify... the process is this:
Prerequisite: Have all HTC drivers installed with abd, etc. All that android stuff... same stuff to flash custom recovery in the first place, etc.
1. Boot into bootloader. Choose Fastboot.
2. Plug your phone into your computer with the microUSB cable.
3. In your android directory command line.. you're going to type: fastboot flash recovery htconerecovery_signed.img
4. Then you're going to type fastboot erase cache
Now you're going to choose to reboot your device... you're going to take the OTA...
Then you're going to go through a similar process to flash the custom recovery back to the device?
Does that sound about right?
Click to expand...
Click to collapse
is this to get the ROM?
we can just make a ROM out of the update files, have someone make a stock nandroid or something.
or for the firmware, radio, if they were updated
just curious.
dottat said:
Yes. Stock (vzw) cid and that modified mid remember I discovered that
Click to expand...
Click to collapse
right... lol im lucky to remember who I am most days,let alone anyone else
the important thing is your not bricked
one4thewings said:
If you're talking about Sonic's method, it's not a root exploit. It's an actual HTC support tool. Nothing released is going to break HTC's support tools.
Click to expand...
Click to collapse
ive done alot of phones with the xtc clip,and the diag files definately can be hboot specific. in this case,the ota is minor so hboot prolly doesnt change. while the java card is not broken,it may require new diag files to do newer hboots as OTAs happen.
its prolly not that big a deal,as sonics supplier should be able to get him the new diag files. but as was said,there isnt much any advantage to waiting.
fader01 said:
I flashed it and tried the update but it still failed ... I am thinking it is probably because I de-bloated the stock image and it doesnt like that.
Click to expand...
Click to collapse
yup. this is correct. please folks... the OTA is not magic. the updates can be cooked into a recovery flashable rom,and the firmware is easily pulled.
scotty1223 said:
right... lol im lucky to remember who I am most days,let alone anyone else
the important thing is your not bricked
ive done alot of phones with the xtc clip,and the diag files definately can be hboot specific. in this case,the ota is minor so hboot prolly doesnt change. while the java card is not broken,it may require new diag files to do newer hboots as OTAs happen.
its prolly not that big a deal,as sonics supplier should be able to get him the new diag files. but as was said,there isnt much any advantage to waiting.
yup. this is correct. please folks... the OTA is not magic. the updates can be cooked into a recovery flashable rom,and the firmware is easily pulled.
Click to expand...
Click to collapse
This should have to be read in order to S-OFF!
scotty1223 said:
right... lol im lucky to remember who I am most days,let alone anyone else
the important thing is your not bricked
ive done alot of phones with the xtc clip,and the diag files definately can be hboot specific. in this case,the ota is minor so hboot prolly doesnt change. while the java card is not broken,it may require new diag files to do newer hboots as OTAs happen.
its prolly not that big a deal,as sonics supplier should be able to get him the new diag files. but as was said,there isnt much any advantage to waiting.
yup. this is correct. please folks... the OTA is not magic. the updates can be cooked into a recovery flashable rom,and the firmware is easily pulled.
Click to expand...
Click to collapse
just curious if there is anything good in the update. Don't care about Isis, phone hasn't froze up. But I do get drops of wifi and BT. Didn't see anything in there about that.
I'm running a self debloated version of the stock, rooted, deodexed ROM. Think I'll run this way until the 4.3 drops and then repeat... Any "fixes" from this minor update should be in it.