Can someone explain to me the difference between unrevoked 3 and unrevoked forever? I have read the entire unrevoked site, and searched, and it seems that unrevoked 3 does essentially the same as forever, in that, it seems that forever used to do nand unlock and be a permanent root, and unrevoked wasn't, but now they seem to be the same exact thing. I just ran unrevoked3 on an evo with the latest OTA update on it. Can someone please explain to me what the limitations of this root are compared to unrevoked forever, or even a more traditional rooting method? I still just don't get it, and this is coming from someone who rooted a G1 an a N1, and ran CM on both, and flashed recoveries, and did it through ADB.
I'm curious about this too. It does sound like Unrevoked 3.2 basically includes Unrevoked Forever.
Noxious Ninja said:
I'm curious about this too. It does sound like Unrevoked 3.2 basically includes Unrevoked Forever.
Click to expand...
Click to collapse
you are correct its like a combination of unrevoked 2 and unrevoked forever. full root, nand unlock included
I never used forever but my understanding is that forever is not full root. It just turns s off and gives you the ability you flash zips through hboot.
unrevoked = standard root + recovery
unrevoked forever = SOFF (meaning security is turned off at the radio and you can forever flash any valid rom/update even if you do an OTA that removed root and/or recovery, just flash a new amon/clockwork).
I believe that the latest unrevoked does include/run unrevoked forever also, but if you already rooted and have a custom recovery, you can simply flash the unrevoked forever directly.
from what i gather unrevoked forever lets you do OTA and you just reflash Su and your recovery
Related
I never did unrevoked, never cared for it (rooted long ago and used update.zips to get to froyo.) But I wanted to do the combo update (radio, wimax, pri, ect) and saw you had to be s-off with unrevoked. So, if I have an unlocked nand, but didn't use unrevoked meathod, can I still flash the combo update? Maybe it's time I start from scratch again.
S-OFF = NAND UNLOCKED
Boot into HBOOT and you should see S-OFF at top of screen. If you are fully rooted you already have S-OFF.
bender1077 said:
S-OFF = NAND UNLOCKED
Boot into HBOOT and you should see S-OFF at top of screen. If you are fully rooted you already have S-OFF.
Click to expand...
Click to collapse
Cool thanks bender.
However, Unrevoked forever makes the S-OFF permanent, meaning even if you flash an update that is unrootable, you can still flash a custom recovery and rom, so essentially, you can't lose root. If you just have normal full root, you would be vulnerable to an OTA update. So its personal preference, but unrevoked forever is definitely best for the people who tend to be a little update happy.
superlinkx said:
However, Unrevoked forever makes the S-OFF permanent, meaning even if you flash an update that is unrootable, you can still flash a custom recovery and rom, so essentially, you can't lose root. If you just have normal full root, you would be vulnerable to an OTA update. So its personal preference, but unrevoked forever is definitely best for the people who tend to be a little update happy.
Click to expand...
Click to collapse
Never been an issue, I always wait. I honestly can't see who would want s-off permanent, what if you had to claim your phone for an exchange? lol.
jlechner said:
Never been an issue, I always wait. I honestly can't see who would want s-off permanent, what if you had to claim your phone for an exchange? lol.
Click to expand...
Click to collapse
It's not irreversibly turned off. While it wasn't available originally, the Unrevoked folks now have a utility that will turn it back to s-on.
unrevoked forever = SOFF @ the radio/nvram
engineering rooted = SOFF @ the bootloader
OTA will typically update the bootloader, so if you are NOT unrevoked forever, then you will loose SOFF when the bootloader is updated.
with unrevoked forever SOFF, you can simply reflash clockwork/amon via pc36img.zip in the root of your sdcard.
I have rooted my Hero before using some of the older methods, but will be purchasing an Evo in a couple of weeks and was just looking for a very simple explanation of the difference between unrevoked 3 and unrevoked forever. Can anyone help answer that without starting another thread on the process of actually performing the root? I certainly do not want to create a duplicate thread. Thanks.
I just asked the same question yesterday. I read the entire unrevoked site, and searched like mad for at least an hour. From what i understand unrevoked used to just be a temporary unlock, in that S stayed ON, and you could lose root pretty easily, but unrevoked forever turned S off, so that your nand unlock remained regardless of what you flashed.
From what I understand though, with the latest unrevoked 3 (3.21), they basically do the exact same thing, but unrevoked forever is still useful for people that applied unrevoked, prior to the latest build, and now want a full nand unlock.
At least thats what I took from it.
ssolomon said:
I have rooted my Hero before using some of the older methods, but will be purchasing an Evo in a couple of weeks and was just looking for a very simple explanation of the difference between unrevoked 3 and unrevoked forever. Can anyone help answer that without starting another thread on the process of actually performing the root? I certainly do not want to create a duplicate thread. Thanks.
Click to expand...
Click to collapse
Unrevoked 3 - Installs Super User and Clockwork and unlocks NAND
Unrevoked Forever - Turns S-OFF permanently unlocking NAND even if an official update removes clockwork and superuser NAND remains unlocked so you can just re flash them.
The latest version of Unrevoked 3 ver 3.2 and 3.21 both have Unrevoked Forever included to choose as an option. So just get Unrevoked 3 ver 3.21 and it includes them both in one easy install.
tws101 said:
Unrevoked 3 - Installs Super User and Clockwork and unlocks NAND
Unrevoked Forever - Turns S-OFF permanently unlocking NAND even if an official update removes clockwork and superuser NAND remains unlocked so you can just re flash them.
The latest version of Unrevoked 3 ver 3.2 and 3.21 both have Unrevoked Forever included to choose as an option. So just get Unrevoked 3 ver 3.21 and it includes them both in one easy install.
Click to expand...
Click to collapse
In recovery, it shows s-off...I ran 3.21, does this mean my nand is permanently unlocked? Is that the default option with 3.21, I basically just ran it right "out of the box".
I think the unrevoked crew could do a better job of explaining this on the website. But don't take that the wrong way, they really don't owe anyone anything,we owe them and should be thankful for what we got, just a suggestion though.
What does this do and where do I get this?
Google it
Sent from my netarchy_toast, froyo beast of a machine evo!
I dont know the answer, but evohack99's answer was really not helpful. This is the right section for the question...
Why when I can ask you??? Isn't this what this forum is for????
i still dont know what s-off is. I agree this is the right section which is why i dont understand your getting a sarcastic answer from evohack.
RichTJ99 said:
i still dont know what s-off is. I agree this is the right section which is why i dont understand your getting a sarcastic answer from evohack.
Click to expand...
Click to collapse
Ok, I found something...
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.
I guess this process is a part of the Unrevoked 3.21...
fechina said:
Ok, I found something...
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.
I guess this process is a part of the Unrevoked 3.21...
Click to expand...
Click to collapse
No. It is an ADDITIONAL process. While not required, it is often recommended.
See Unrevoked's website for the definitive answer.
HTH
--Chris
Sorry, that is just a common question in which can be found all over the forum or on google, sorry I was being an ass,
Sent from my netarchy_toast, froyo beast of a machine evo!
fechina said:
Ok, I found something...
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.
I guess this process is a part of the Unrevoked 3.21...
Click to expand...
Click to collapse
fechina , I think it is an ADDITIONAL step using unrevoked forever, been a while since I did this and the code has changed, review the "more" option after selecting unrevoked forever at there website and it will fill in the blanks. Your definition/understanding is right on. The point, I think you need to flash unrevoked forever to have nand-off, but verify and understand the process before you do it.
debugguy said:
fechina , I think it is an ADDITIONAL step using unrevoked forever, been a while since I did this and the code has changed, review the "more" option after selecting unrevoked forever at there website and it will fill in the blanks. Your definition/understanding is right on. The point, I think you need to flash unrevoked forever to have nand-off, but verify and understand the process before you do it.
Click to expand...
Click to collapse
Correct debugguy, it IS an ADDITIONAL process. In fact, this was the route I took
to root my supersonic; Unrevoked 3.21 > Unrevoked forever.
I can state that after recently rooting my phone via Unrevoked 3.21, the
process went as intended & w/o error. But when completed && rebooted to the
newly rooted phone, S-OFF was not implemented. So I downloaded & installed
Unrevoked forever. Now S-OFF is implemented.
--Chris
From what I read before I rooted.
S-Off prevents the rom from reverting back to the original data every time you reboot.
It also lets you flash custom roms.
UnrEVOked 3.21 sets it to S-Off, but unrEVOked forever will make S-Off permanent.
Permanent... as in safe to update using OTA's.
If you aren't unrEVOked forever an OTA can actually remove the S-Off flag and prevent you from re-rooting.
xNotta said:
From what I read before I rooted.
S-Off prevents the rom from reverting back to the original data every time you reboot.
It also lets you flash custom roms.
UnrEVOked 3.21 sets it to S-Off, but unrEVOked forever will make S-Off permanent.
Permanent... as in safe to update using OTA's.
If you aren't unrEVOked forever an OTA can actually remove the S-Off flag and prevent you from re-rooting.
Click to expand...
Click to collapse
Yes.
Unrevoked 3.21 = S-OFF && r/w long enough to rewrite your ROM with the one provided in Unrevoked 3.21
Unrevoked forever = S-OFF forever
It's all at their website and in numerous threads in these forums.
--Chris
Thanks.....
WOW, thanks...
xNotta said:
.....
If you aren't unrEVOked forever an OTA can actually remove the S-Off flag and prevent you from re-rooting.
Click to expand...
Click to collapse
This is the line I don't understand. If you don't run Forever and an OTA removes the S-OFF flag, why couldn't you just re-run Unrevoked again to gain root access?
Is it because a new OTA could block Unrevoked?
Thanks!
daystrom said:
This is the line I don't understand. If you don't run Forever and an OTA removes the S-OFF flag, why couldn't you just re-run Unrevoked again to gain root access?
Is it because a new OTA could block Unrevoked?
Thanks!
Click to expand...
Click to collapse
Unrevoked exploits a vulnerability to "root" the phone.
So, an OTA could patch that vulnerability and you would have to wait for another exploit to be found in order to regain S-Off and root again.
Ex. When OTA froyo came out unrevoked would not work since htc fixed the vulnerability used in rooting 2.1.
Sent from my Evo using XDA App.
Cool, thanks for that good info.
One more question -
Many are saying that you have to run Forever AFTER you have installed 3.21.
HOWEVER when you run 3.21 and click File, there is an option that is checked that says "Disable security on Phone".
When you select this a prompt comes up saying "unrEVOked Forever will not be installed".
When you select it again to enable it a prompt comes up saying "unrEVOked Forever will be installed to disable device security.".
To me this sounds like Forever IS installed with 3.21.
No?
daystrom said:
One more question -
Many are saying that you have to run Forever AFTER you have installed 3.21.
HOWEVER when you run 3.21 and click File, there is an option that is checked that says "Disable security on Phone".
When you select this a prompt comes up saying "unrEVOked Forever will not be installed".
When you select it again to enable it a prompt comes up saying "unrEVOked Forever will be installed to disable device security.".
To me this sounds like Forever IS installed with 3.21.
No?
Click to expand...
Click to collapse
I've actually wondered the same thing, since after rooting with 3.21 it is set to S-Off.
I wanted to be safe so I still flashed unrevoked forever.
It's a flashable zip so it's not hard to do and it take only a few seconds.
Better safe then without root, imo.
Sent from my Evo using XDA App.
Quick question. I had to use simple root method because of issues with unrevoked 3.21. Can I still run unrevoked forever?
It's called supersonic for a reason.
Can someone please explain clearly the difference between Unrevoked 3 (.22) and Unrevoked Forever (for EVO use).
I've read both Wiki's and it seems, for the EVO, that both permanently give root, unlock NAND, and s-off.
If I root with Unrevoked 3, what exactly would be the reasoning for flashing Forever?
Please answer specifically for EVO use.
Thanks
sent from my bad-ass EVO!
sweet...
sent from my bad-ass EVO!
Unrevoked forever achieves S-OFF, which means, even if for some reason you become "unrooted" (such as accepting an OTA) you can always go to recovery and flash a rooted rom. S-OFF is a somewhat permanent NAND unlock.
Unrevoked 3.22 includes the forever flash after the root process, however, I have noticed sometimes it doesn't flash properly, so anyone using unrevoked 3.22, should verify they are S-OFF in bootloader. If you are still S-ON, then download and flash the unrevoked forever .zip until you get S-OFF.
Thanks, but its just hard for me to believe that the whole point of Forever is "just in case" you don't achieve s-off with 3.22. It has to do something extra right?
What is this stuff I've been reading that its not permanent... or is this just old info. When I read the 3.22 wiki it says that it "now" achieves root as of 3 whereas before it did not.
sent from my bad-ass EVO!
generalExpert said:
Thanks, but its just hard for me to believe that the whole point of Forever is "just in case" you don't achieve s-off with 3.22. It has to do something extra right?
What is this stuff I've been reading that its not permanent... or is this just old info. When I read the 3.22 wiki it says that it "now" achieves root as of 3 whereas before it did not.
sent from my bad-ass EVO!
Click to expand...
Click to collapse
Well forever was released after other root methods. So people who rooted either manually or simple root or whatever.. won't have S-OFF, unrevoked were the first to come out with that, and the forever .zip download, lets those people have it too.
Old versions of unrevoked did not reach permanent nand unlock so you'll read a lot of old stuff about how unrevoked isn't a "full root", but now with forever, it does.
Ok, so by rooting with Unrevoked 3 I don't need to flash Unrevoked Forever, right? Because now with version 3 I achieve the same things that Forever does??...
Is this correct.
sent from my bad-ass EVO!
I rooted with unrEVOked 3 and have S-OFF so you should be fine.
generalExpert said:
Ok, so by rooting with Unrevoked 3 I don't need to flash Unrevoked Forever, right? Because now with version 3 I achieve the same things that Forever does??...
Is this correct.
sent from my bad-ass EVO!
Click to expand...
Click to collapse
In theory yes, as I stated, unrevoked 3.xx has included the forever flash, but you just need to double check that it all went through, there have been many reports (in the IRC chan, and my own experience with a replacement EVO) that people are rooted but not S-OFF after finishing unrevoked 3.xx.
VDub2174 said:
I rooted with unrEVOked 3 and have S-OFF so you should be fine.
Click to expand...
Click to collapse
As above.
op-put simply, do the unrevoked3.xx to root your phone. if you get s-off in the process then good no need to do anything else. if you still got s-on then you need to run unrevoked forever. simple as that. just because it worked for someone else does not mean that it will work for you. just do it and then verify it is nand unlock.
OK, just rooted my EVO for the 2nd time ever. Went pretty easy. However, I was using Ubuntu 10.10 64bit and it took a minute to figure out how to run the reflash program as a root user. I did get some errors about the radio not being supported and update failed. After a reboot I noticed that I did not have s-off but did have the ClockworkMOD recovery and the superUser Permission app. So, I ran unrevoked forever and viola I now have s-off (and the unrevoked splash screen). I see now why this is useful, just wondering why I had errors with my radio version.
Code:
unrEVOked forever S-OFF patch v1.1
Verifying system type...
E:unsupported radio version
E:Update failed. Check /sdcard/soff.log.
E:Error in /data/local/unrevoked-forever.zip
(Status 42)
Installation aborted.
Failure at line 1:
install_zip DATA:local/unrevoked-forever.zip
Why the **** won't UnrEVOked 3.32 ****ing run on my Windows XP and EVO??? WHAT THE ****???
HTC Sync is NOT installed
USB debugging is enabled
What the **** am I missing here?
Did you install the driver from the help section?
jstn76rs said:
Did you install the driver from the help section?
Click to expand...
Click to collapse
No... and I totally did read that! Crap! Thanks, hopefully that will be why...
So I would assume I just need to run the .exe file with the phone turned booted back up?
I hope I Don't have to redownload everything...
eyeballer1 said:
Well forever was released after other root methods. So people who rooted either manually or simple root or whatever.. won't have S-OFF, unrevoked were the first to come out with that, and the forever .zip download, lets those people have it too.
Old versions of unrevoked did not reach permanent nand unlock so you'll read a lot of old stuff about how unrevoked isn't a "full root", but now with forever, it does.
Click to expand...
Click to collapse
Using the engineering bootloader, like simple root did, has unlocked the NAND (s-off) since day one. Unrevoked just figured out a way to do it with other bootloader versions
Even more questions of whether I'm truly rooted or not...
First time posting although I've been lurking for quite a while so hopefully I don't get flamed out of here on my first attempt.
First I did root my Evo using unrevoked 3, all seemed to go well and correctly as I ended up with S-OFF, superuser app, etc. I created a backup and everything, (still running stock Sense ROM.) Do I need to try using Unrevoked Forever now?
I started reading posts about backing up RSA keys and WiMAX partitions etc and when I connected the phone (yes usb debugging and charge only); opened a command prompt and browsed to the ADB directory I never get the # confirming I have root access. (I only get the $)
Now from what I'm reading Clockwork mod backs up the WiMax anyway but I still wanted to walk through the process to get more familiar with it. I guess my first question is do I really need to back up the partition and keys if I have a successful nandroid backup?
Also I installed root check and the under the basic setting it said I had no root access, and then under the advanced setting it said I did.
I tried installing Ti backup and clicking under problems to install busy box thinking that may be the problem, but I don't see the setting it describes there where I can change to install busybox.
Finally I also downloaded the busybox installer. It gives two options of where to install it in either /system/bin/, or /system/xbin/....does it matter? Will installing it this way be ok or do I need to push through ADB? If I need to push through ADB then obviously I need to get my # root access figured out.
Thanks in advance to anyone who can try and help me make heads or tails of this situation.
Radio: 2.15.00.11.19
Software Number : 3.70.651.1
Hardware Version: 0003
HBoot: 2.10.0001
Dilema - I purchased a previoulsy rooted phone, is there a way to tell if unrevoked forever has been run?
OR
Can I just run unrevoked forever regardless?
It doesnt matter if unrevoked forever has been run or not. The only thing that matters is whether or not you have s-off
Jim M said:
Dilema - I purchased a previoulsy rooted phone, is there a way to tell if unrevoked forever has been run?
OR
Can I just run unrevoked forever regardless?
Click to expand...
Click to collapse
It wouldn't hurt anything to run it again, but if you go into the bootloader by holding the Volume Down key when you power on the phone you can look at the top and see if it says S-Off or S-On. If it's S-Off, then you're good and you can flash a recovery if you don't already have one, and flash whatever ROM you want if you do.
I want to keep s-off forever, that's why it matters, ergo my question, can unrevoked forever be run regardless?
Jim M said:
I want to keep s-off forever, that's why it matters, ergo my question, can unrevoked forever be run regardless?
Click to expand...
Click to collapse
Check the hboot version in the bootloader for s-off. if it's s-off it is rooted. If its version 2.10 and s-on, it can be rooted. If already rooted, you can run the unforever zip, but it really won't do anything, as its been depreciated in the latest builds of unrevoked; it was used to give s-off in older versions and was then since incorporated into unrevoke 3.x.
Jim M said:
I want to keep s-off forever, that's why it matters, ergo my question, can unrevoked forever be run regardless?
Click to expand...
Click to collapse
S-Off is permanent (unless you intentionally run the S-On tool), so if you have it, you're good. The information is stored in the radio memory, not on the ROM system partition. Unrevoked forever gives you S-Off, which is why it has that name. Unrevoked3 just gives you superuser status in Android.
I've heard people say that running an RUU can sometimes reset you to S-On. I don't think that's true. Maybe the newest update... but I doubt it. Either way, just don't ever take an official update or run an RUU .
I went ahead and ran unrevoked forever again. My phone still functions, so it didn't hurt anything. It's beer-thirty now.
Sent from my PC36100 using Tapatalk