Is there an easy way to find out if I have unlocked nand?
I rooted from 2.2 using the method on the forum (downgrading to 2.1). This was the unrEVOked3 way of rooting. I read on the forum that unrEVOked3 is only a root, and does not unlock the nand?
If I haven't unlocked nand, can I use the Toast method to do so?
Thanks in advance.
ckombo said:
Is there an easy way to find out if I have unlocked nand?
I rooted from 2.2 using the method on the forum (downgrading to 2.1). This was the unrEVOked3 way of rooting. I read on the forum that unrEVOked3 is only a root, and does not unlock the nand?
If I haven't unlocked nand, can I use the Toast method to do so?
Thanks in advance.
Click to expand...
Click to collapse
You can use Unrevoked Forever or Toast pt 2 to do a NAND unlock. Doing it with Toast's method will downgrade your PRI, which may or may not affect you and can be hard to fix. I recommend Unrevoked Forever, but it's your choice.
You can go into the bootloader by turning off the phone, then holding power+volume down until you get to the white screen. If the first line ends in S-OFF, you have NAND unlocked.
Thanks for the reply! I did use unrevoked forever and also double checked in the bootloader. S-off!
There's a copy of the engineering bootloader Toast used that has the PRI downgrade removed, you may have to hunt for it though.
xHausx said:
There's a copy of the engineering bootloader Toast used that has the PRI downgrade removed, you may have to hunt for it though.
Click to expand...
Click to collapse
Or look in my sig.
ahah! That's the one, I've been meaning to download a copy of it myself so thanks for pointing that out.
Related
I am currently rooted with Unrevoked 3 and want to finish the full root with NAND unlock. My plan is to use netarchy's 2.2 ROM and 3.7.6 kernal as I do not want to lose the FPS fix (been using it on 2.1 and LOVE it!!)
Anyway, there are a lot of different methods out there to root and I am trying to determine which method is going to be sucessful following Unrevoked 3 and will not be overly complex. I would appreciate any input.
I am assuming that I will lose all my settings/programs/etc so I should do a complete backup first? I have MyBackUp Pro which I have used before but I am open to suggestions for a better method.
Thanks
Alto101 said:
I am currently rooted with Unrevoked 3 and want to finish the full root with NAND unlock. My plan is to use netarchy's 2.2 ROM and 3.7.6 kernal as I do not want to lose the FPS fix (been using it on 2.1 and LOVE it!!)
Anyway, there are a lot of different methods out there to root and I am trying to determine which method is going to be sucessful following Unrevoked 3 and will not be overly complex. I would appreciate any input.
I am assuming that I will lose all my settings/programs/etc so I should do a complete backup first? I have MyBackUp Pro which I have used before but I am open to suggestions for a better method.
Thanks
Click to expand...
Click to collapse
Did you ever get an answer to this? I'm in the same situation and what to determine the best solution.
I finally got my hands on an evo with 2.1 update 1 and have read about every method out there. Wich rooting method should I start with if I want full root?
Sent from Evo 4g
energizer1389 said:
I finally got my hands on an evo with 2.1 update 1 and have read about every method out there. Wich rooting method should I start with if I want full root?
Sent from Evo 4g
Click to expand...
Click to collapse
some people use simpleroot.. the most 'foolproof' way in my opinion, is toast's method.. just make sure you do part 1 and 2 ( it should be in wiki ).. 1 does root, 2 does nand unlock.
energizer1389 said:
I finally got my hands on an evo with 2.1 update 1 and have read about every method out there. Wich rooting method should I start with if I want full root?
Sent from Evo 4g
Click to expand...
Click to collapse
This thread:
http://forum.xda-developers.com/showthread.php?t=761307
In particular this post:
http://forum.xda-developers.com/showpost.php?p=7780604&postcount=2
And for more detail, this one:
http://forum.xda-developers.com/showpost.php?p=7780857&postcount=6
This will allow root access and unlocked NAND without downgrading the PRI or otherwise messing with your system. Everything will be the same, save for root access and unlocked NAND. (what the people of this forum have decided to call "full root" for... err... still confused on the reason for this stupid term).
So it sounds like unrevoked forever is the recommended method for getting full root after rooting with Unrevoked3. My issues is I'm having trouble flashing certain roms with just Unrevoked3. From what I've read not all roms can be flashed with Unrevoked3. I want to try a different root method, but I don't want to screw anything up. It seems like Unrevoked Forever is the best option at this point, but seems kind of extreme. Does anyone agree or disagree?
I've already downloaded forever on my phone...just waiting to get the courage to install it.
ohseedee said:
I've already downloaded forever on my phone...just waiting to get the courage to install it.
Click to expand...
Click to collapse
I used Unrevoked Forever and didn't have a single issue. I've flashed a number of ROMs since then, and still no problems. I'm currently running Baked Snack 1.3 with Netarchy's latest kernel and Clockwork. Hope this helps you with your fear.
Sent from my Baked EVO via the XDA app.
onewaycourt said:
I used Unrevoked Forever and didn't have a single issue. I've flashed a number of ROMs since then, and still no problems. I'm currently running Baked Snack 1.3 with Netarchy's latest kernel and Clockwork. Hope this helps you with your fear.
Sent from my Baked EVO via the XDA app.
Click to expand...
Click to collapse
There is no difference between the recovery unrevoked3 installs and one installed by flashing an image after using the leaked ENG bootloader.
Some roms had problems with the unrevoked3 exploit because it did not unlock NAND and they made the assumption that NAND was unlocked. With unrevoked forever (or, if you wish to lose your 1.40 PRI, the leaked ENG bootloader), this is no longer an issue.
+1 for Unrevoked Forever. Unrevoked 3.1 + Unrevoked Forever worked flawlessly on my phone. You can even flash the ENG bootloader as a separate package if you want, so that you have the fastboot commands without downgrading the PRI.
The only downside is that there is currently no way to completely undo Unrevoked Forever. If you have to get the phone replaced, a tech who knows what he's doing could easily tell that you've rooted your phone.
Noxious Ninja said:
+1 for Unrevoked Forever. Unrevoked 3.1 + Unrevoked Forever worked flawlessly on my phone. You can even flash the ENG bootloader as a separate package if you want, so that you have the fastboot commands without downgrading the PRI.
The only downside is that there is currently no way to completely undo Unrevoked Forever. If you have to get the phone replaced, a tech who knows what he's doing could easily tell that you've rooted your phone.
Click to expand...
Click to collapse
Thanks for the info. Yeah I'm a little worried about the lack of undo, but I have Sprint's insurance on the phone so I guess I could always get it replaced (+ deductible). I think I'm going to do the Forever method.
I do not know if I need nand unlocked, as I do not know what exactly it does. But I know some roms do require it and it is recommended to do. I do not know hot to unlock nand on the netarchy Froyo rooted rom though. I do have root but I never downgraded hboot and unlocked nand previously. I am not sure which methods of downgrading hboot and unlocking nand work with this new build.
Any suggestions? Any help is appreciated.
Errroneous said:
I do not know if I need nand unlocked, as I do not know what exactly it does. But I know some roms do require it and it is recommended to do. I do not know hot to unlock nand on the netarchy Froyo rooted rom though. I do have root but I never downgraded hboot and unlocked nand previously. I am not sure which methods of downgrading hboot and unlocking nand work with this new build.
Any suggestions? Any help is appreciated.
Click to expand...
Click to collapse
look in the android development forum. at the top are some 'stickies', look through them. one of them will contain a link to toastcfh's method for getting a full, nand unlocked, android setup. there is also a simpleroot method that seems to work for many people.
timothydonohue said:
look in the android development forum. at the top are some 'stickies', look through them. one of them will contain a link to toastcfh's method for getting a full, nand unlocked, android setup. there is also a simpleroot method that seems to work for many people.
Click to expand...
Click to collapse
i second Taostcfh's method. It may look complicated but jsut go one step at a time and if you run into a problem post in this thread and we will try to help yuo through it.
As far as NAND unlock basically what it does it it replaces your HBOOT with an engineering build. This basically allows you to mount r/w system files. while rooted with out nand most system files are still locked away from you. I know its not the best explanation but i think it gets the idea across.
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
I've been searching to find a root for the Evo that I'll be getting in the next few weeks, yet the unrEVOked root seems frowned upon from what I have seen. Please correct me if I'm wrong. If the unrEVOked root is not the best, please point me to what is.
Thanks,
SmallFry
SmallFry_ said:
I've been searching to find a root for the Evo that I'll be getting in the next few weeks, yet the unrEVOked root seems frowned upon from what I have seen. Please correct me if I'm wrong. If the unrEVOked root is not the best, please point me to what is.
Thanks,
SmallFry
Click to expand...
Click to collapse
Different s-off methods for different hboot versions. Whatever works. Make sure u use smelkus' updated amonra recovery once u have s-off.
fitz420 is correct, depends on hboot. Gonna have to wait and see what you get. I recommend Revolutionary method, simple directions and a clean root.
JollyGrnReefer said:
fitz420 is correct, depends on hboot. Gonna have to wait and see what you get. I recommend Revolutionary method, simple directions and a clean root.
Click to expand...
Click to collapse
Unrevoked is still the easiest way to root, basically the same though.
Hboot:
2.10 > unrevoked root
2.16 > revolutionary root
2.18 > HTC Dev root [most painful]
I imagine that the H-Boot is up to the latest since the guy that I'm purchasing the Evo from left it completely stock while he had it activated with Sprint... Thus, I think that I'll have to do the HTC Dev Root. I'll post back when I have the device in hand. Thanks guys!
teh roxxorz said:
Unrevoked is still the easiest way to root, basically the same though.
Hboot:
2.10 > unrevoked root
2.16 > revolutionary root
2.18 > HTC Dev root [most painful]
Click to expand...
Click to collapse
HTC Dev+Captain Throwback's method = Painful and funnest.