will there be a simple root for 2.2? i hear unrevoked isnt trusted t be a full root
In due time
Sent from my PC36100 using XDA App
Rocklee99 said:
will there be a simple root for 2.2? i hear unrevoked isnt trusted t be a full root
Click to expand...
Click to collapse
Unrevoked 3 isn't a "full root", but it is when combined with Unrevoked Forever.
Sent from my HummerPhone using the XDA App
A fulll root and s-off is being worked on for 2.2 OTA.
Noxious Ninja said:
Unrevoked 3 isn't a "full root", but it is when combined with Unrevoked Forever.
Sent from my HummerPhone using the XDA App
Click to expand...
Click to collapse
You are correct.
Sent from my PC36100 using XDA App
Unrevoked isn't exactly needed to root 2.2. Once you've returned to stock 2.1, you can use whatever 2.1 root method you want - I used SimpleRoot.
Beknatok said:
Unrevoked isn't exactly needed to root 2.2. Once you've returned to stock 2.1, you can use whatever 2.1 root method you want - I used SimpleRoot.
Click to expand...
Click to collapse
Once again: The term full root is completely meaningless. You either have root, in which case you can run code as the root user, or you do not. There is no "full root" and there is no "partial root."
There is, in addition to the normal linux access control model, a NAND lock, implemented in hardware, on these phones. This means that without a particular exploit or an ENG bootloader, there is no way to reflash a partition. Luckily, an ENG bootloader was "obtained" "in some way" from HTC. I am not sure of the legal standing of said code, but "it's worked so far."
Now, the ENG bootloader is a signed update. This means that you have to flash the whole thing: you lose all your data, and you lose your 1.40PRI. Also, since the phone is not well and truly S-OFF, if you accept an OTA, you lose your unlocked NAND.
On the other hand, unrevoked forever ALSO unlocks NAND, and it does so at a level below the radio. This means that the update is permanent. If you accept an OTA, S-OFF remains. If you RUU, S-OFF remains. You can flash our s-on.zip update to revert it. Furthermore, every line of code in Unrevoked Forever was developed by us. HTC has no legal standing to tell us to remove it.
rpearl said:
Once again: The term full root is completely meaningless. You either have root, in which case you can run code as the root user, or you do not. There is no "full root" and there is no "partial root."
There is, in addition to the normal linux access control model, a NAND lock, implemented in hardware, on these phones. This means that without a particular exploit or an ENG bootloader, there is no way to reflash a partition. Luckily, an ENG bootloader was "obtained" "in some way" from HTC. I am not sure of the legal standing of said code, but "it's worked so far."
Now, the ENG bootloader is a signed update. This means that you have to flash the whole thing: you lose all your data, and you lose your 1.40PRI. Also, since the phone is not well and truly S-OFF, if you accept an OTA, you lose your unlocked NAND.
On the other hand, unrevoked forever ALSO unlocks NAND, and it does so at a level below the radio. This means that the update is permanent. If you accept an OTA, S-OFF remains. If you RUU, S-OFF remains. You can flash our s-on.zip update to revert it. Furthermore, every line of code in Unrevoked Forever was developed by us. HTC has no legal standing to tell us to remove it.
Click to expand...
Click to collapse
so even if i am already rooted, and did so by simple root, is my nand unlocked? i would think it is right? and even if it is can i still use unrevoked forever?
rpearl said:
Once again: The term full root is completely meaningless. You either have root, in which case you can run code as the root user, or you do not. There is no "full root" and there is no "partial root."
There is, in addition to the normal linux access control model, a NAND lock, implemented in hardware, on these phones. This means that without a particular exploit or an ENG bootloader, there is no way to reflash a partition. Luckily, an ENG bootloader was "obtained" "in some way" from HTC. I am not sure of the legal standing of said code, but "it's worked so far."
Now, the ENG bootloader is a signed update. This means that you have to flash the whole thing: you lose all your data, and you lose your 1.40PRI. Also, since the phone is not well and truly S-OFF, if you accept an OTA, you lose your unlocked NAND.
On the other hand, unrevoked forever ALSO unlocks NAND, and it does so at a level below the radio. This means that the update is permanent. If you accept an OTA, S-OFF remains. If you RUU, S-OFF remains. You can flash our s-on.zip update to revert it. Furthermore, every line of code in Unrevoked Forever was developed by us. HTC has no legal standing to tell us to remove it.
Click to expand...
Click to collapse
Currently. A future update is easily capable of overriding forever.
Sent from my PC36100 using XDA App
Rocklee99 said:
so even if i am already rooted, and did so by simple root, is my nand unlocked? i would think it is right? and even if it is can i still use unrevoked forever?
Click to expand...
Click to collapse
Yes all around.
Sent from my PC36100 using XDA App
Rocklee99 said:
so even if i am already rooted, and did so by simple root, is my nand unlocked? i would think it is right? and even if it is can i still use unrevoked forever?
Click to expand...
Click to collapse
You wouldn't be nand unlocked if u used simple root. After you use that do toasts part two for nand unlock.
Sent from my Evo 4G using Tapatalk
I rooted my phone according the following link http://forum.ppcgeeks.com/showthread.php?t=123714 . I did this after getting the ota. I followed the instructions in the ROOTING AFTER OTA 1.47.651.1 (Full Root). Am running Baked Snack, kernel #5 and riptide's theme. It shows up as android 2.2 but on boot it show in the boot up screens as 2.1. If I did forever can I take the ota and retain root and nand? Is there any benefit to it other then getting PRI 1.4.003? I don't have any problems now, can't check 4G because it's not here in Crystal River,Florida. Thanks for your help in advance
islandreamer said:
I rooted my phone according the following link http://forum.ppcgeeks.com/showthread.php?t=123714 . I did this after getting the ota. I followed the instructions in the ROOTING AFTER OTA 1.47.651.1 (Full Root). Am running Baked Snack, kernel #5 and riptide's theme. It shows up as android 2.2 but on boot it show in the boot up screens as 2.1. If I did forever can I take the ota and retain root and nand? Is there any benefit to it other then getting PRI 1.4.003? I don't have any problems now, can't check 4G because it's not here in Crystal River,Florida. Thanks for your help in advance
Click to expand...
Click to collapse
The reason you are seeing 2.1 on the boot screens is because those boot screens are static png files, not the system actually booting. If you are good with graphics manipulation you can make it say 3.0 (Gingerbread).
kf2mq said:
The reason you are seeing 2.1 on the boot screens is because those boot screens are static png files, not the system actually booting. If you are good with graphics manipulation you can make it say 3.0 (Gingerbread).
Click to expand...
Click to collapse
Thanks for the response! I should have been more specific, the 2.1 I see is really not the boot screen that are rom gods put on their roms but the system checks the phone goes through during boot up. It shows root access and success, initialization , type of processor, memory check and activating android 2.1 setup. Don't know if this means I have 2.1 or not. Under software it shows as android 2.2 just assume that is from hero's rom (Baked Snack).
islandreamer said:
Thanks for the response! I should have been more specific, the 2.1 I see is really not the boot screen that are rom gods put on their roms but the system checks the phone goes through during boot up. It shows root access and success, initialization , type of processor, memory check and activating android 2.1 setup. Don't know if this means I have 2.1 or not. Under software it shows as android 2.2 just assume that is from hero's rom (Baked Snack).
Click to expand...
Click to collapse
kf2mq is right. Android doesn't show any system checks when booting up. Everything you see after the white screen that says htc EVO 4G is all a series of image files carefully placed together as a gif to give you something pleasant to look at. In your case it just so happens that your boot animation mimics a system start-up like you would see on a computer. Mine even has an Energy Star certification in the top, right corner.
If you'd like to change the animation to say 2.2 check this thread out.
http://forum.xda-developers.com/showthread.php?t=754679
SharkUW said:
Currently. A future update is easily capable of overriding forever.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well, not so easily. But it's certainly possible. I would still wait before applying any new OTAs just in case they've figured out the magic way to undo UF without killing all legit dev phones.
Sent from my HummerPhone using the XDA App
onewaycourt said:
kf2mq is right. Android doesn't show any system checks when booting up. Everything you see after the white screen that says htc EVO 4G is all a series of image files carefully placed together as a gif to give you something pleasant to look at. In your case it just so happens that your boot animation mimics a system start-up like you would see on a computer. Mine even has an Energy Star certification in the top, right corner.
If you'd like to change the animation to say 2.2 check this thread out.
http://forum.xda-developers.com/showthread.php?t=754679
Click to expand...
Click to collapse
I will check that out. We must have the same one because the energy star is also on mine. Thank you for the enlightenment everyday I find more I need to learn. Some day I will be able to answer a question instead of ask.
SharkUW said:
Currently. A future update is easily capable of overriding forever.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Well... such an update would be very interesting. Since the same exploit is used on the radio code to allow us to set S-ON as to set S-OFF, they would be revealing how to do it.
And quite likely, we'd be able to exploit or use that too.
Furthermore, there's no magic that wouldn't kill all existent testing phones too. There's no way to tell between an unrevoked forever phone and a test phone.
Don't worry... we'll still go through and confirm updates. But the process should be much easier ("hey, you can accept the OTA straight up when you get it") rather than "here is a rooted rom, you lose all your data, but it's basically the same as the update."
rpearl said:
Well... such an update would be very interesting. Since the same exploit is used on the radio code to allow us to set S-ON as to set S-OFF, they would be revealing how to do it.
And quite likely, we'd be able to exploit or use that too.
Click to expand...
Click to collapse
Awesome.
rpearl said:
Furthermore, there's no magic that wouldn't kill all existent testing phones too. There's no way to tell between an unrevoked forever phone and a test phone.
Click to expand...
Click to collapse
Could they keep a list of the MEIDs of all dev phones and selectively push updates based on that?
It's simple if you carefully follow the instructions...
http://forum.xda-developers.com/showthread.php?t=765496
In General terms, this method sets you back to 2.1 and uses Unrevoked Forever to root Stock 2.2 in the end.
Related
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.
i have installed the gingerbread keyboard file on my sd card and have rooted my phone using the visonary method but now i cant seem to get into recovery mode. I have rom manager installed and have flashed clockwork recovery mode. it said that it had sucsessfully installed.
I then flashed it again as i read somewhere that i might need to do it twice as sometimes it dosent work.
when i now click on the recovery option in rom manager all i get is the red triange with the ! in the middle.
any ideas what im doing wrong?
Have tried reading the threads but with 30 plus pages i am now completley confused
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
just done the hboot hing and at the top of screen it says
vision pvt ship s-on
hpsauce37 said:
thanks for the quick reply, i think from what i have read that this s-off thing maybe the problem.
can you tell me how do this please
simple steps please as i am struggling with this
Click to expand...
Click to collapse
It's a bit confusing because there is more than one way to do this. But by far the safest way is to follow the guide at http://forum.xda-developers.com/showthread.php?t=857390
Have a good read, then if you're not sure, ask questions in that thread on the process.
steviewevie said:
Sounds like you don't have S-OFF. What does it say in HBOOT (e.g. hold down volume down and the power button with the phone powered off) ?
Click to expand...
Click to collapse
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
S-OFF is a completely different animal. Don't get it confused with being able to boot into recovery.
Click to expand...
Click to collapse
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
steviewevie said:
I didn't think you could flash recovery without S-OFF though ? Surely ROM Manager doesn't have the ability to write to the NAND, since the write protection will be on if you're at S-ON ?
Click to expand...
Click to collapse
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Again. S-OFF is a different issue altogether. Being able to write to NAND is a part of the rooting process. Setting security off is not a part of the rooting process. It's a totally different process for a totally different purpose. The caveat would be if unrevoked has been revised to full root and set S-OFF during the same process. I haven't used it in awhile so on that point, I'm not certain.
Click to expand...
Click to collapse
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
steviewevie said:
Sorry but that's not right for the DZ/G2. I wonder if you're thinking of how it works on a different Android phone ? The security has been increased on the DZ/G2/DHD compared to, say, the original Desire.
Writing to the system and recovery partitions isn't possible until you get S-OFF. This has nothing to do with rooting, it it because of the increased security on these phones where the NAND is in a hardware write-protect mode for those partitions by default. You can appear to write to the partitions, but it's actually going to cache and is lost when you reboot, until you get S-OFF.
Click to expand...
Click to collapse
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Actually yes. S-OFF on the EVO is to make sure no matter what, you're always rooted. It came about after the new stock flash would unroot the phone. With S-OFF active, you can flash any stock rom and not lose root. All you would need to do is reflash RA or Clockwork to get back to recovery and flash roms again. Unrevoked forever is the program we used to change the security setting.
So. That is only true for the EVO?
Sent from my EVO using Tapatalk Pro
Click to expand...
Click to collapse
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
hpsauce37 said:
im going to have to give up on this
i have tried to follow the guide to get s-off but i find it too complicated. I have my phone rooted with visionary but i think thats as far as im going to get.
tried to install the adb thing and get that working but it never recognises the phone. when i remove the drivers and plug it back in then windows automatically installs the drivers again so i never have the option to manually instll them.
this is just becoming a nightmare
someone make it simple for me please....the thread is pages and pages long and even then it seems there are problems
Click to expand...
Click to collapse
Have you tried my guide on adb ? http://forum.xda-developers.com/showthread.php?t=865685
OK, I can use some help too
I have a DZ with stock ROM, root and s-off and CWR.
In my enthusiasm that I knew how to flash rom updates with clockwork (I am running the Godspeed 1Ghz) I downloaded the Gingerbread keyboard rom update from the G2 forum. I think I jumped off a bit too fast...
And now I am stuck in an infinite boot loop. I can get into Clockwork recovery but it just loops the "HTC Quietly Brilliant" forever including the annoying boot sound...
I tried some suggestions to download and reflash a second time, no effect.
I tried to mount /system before flashing, no effect.
Am I forced to go back to factory now?
Also, I found 2 gingerbread keyboards, one in the G2 forum and one over here.
Anyone know what the difference is? They have a different filesize..
Any help is welcome...
*edit*
OK so now I read that it is only to be flashed on a non-stock ROM... so I am now flashing Cyanogen 6.1
try wiping all the caches...
Lennyuk said:
yeah I think so.
The new HTC Desire Z and HD had "better" security from htc, basically you can't write anything to nand (/system) until you perma rooted, even then some things such as recovery needed s-off before we could write to that partition.
Click to expand...
Click to collapse
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Sent from my EVO using Tapatalk Pro
rwcj63 said:
Wow. I'm really sorry guys. I never knew that's how non evo worked. That totally sucks.
Click to expand...
Click to collapse
S'alright.
HTC really ramped up the security on these new phones, as Lenny said, with this hardware write-protection on certain partitions. But even given that, I was amazed by just how quickly the guys on the #G2ROOT IRC channel, especially Scotty2, managed to crack it !
It also looks like they've opened the phone even wider than many others before, with the "true" radio S-OFF that they achieved.
You can read up all about it in the Wiki - http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Is the phone s-off?
Sent from my PC36100 using XDA App
badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.
animal7296 said:
No, you can not run an older ruu. If he updated to today or yesterdays update hes stuck. If he is on HBOOT 2.02 he can flash the 3.30.651.3 ruu or ths 3.70.651.1 but you can not ruu further back.
Click to expand...
Click to collapse
Are either of these rootable yet?
and can someone explain what S-on and off means?
badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
badutahboy said:
Are either of these rootable yet?
and can someone explain what S-on and off means?
Click to expand...
Click to collapse
1. 2.02 is rootable 2.10 is not and is the newest one.
2.0 S-ON means you can not flash roms s-off means you can. It is the security of the phone kind of.
If you can not get into bootloader then you can try running the oldest ruu and then the next. It wont hurt the phone at all (I just did it today) it will just give you an error and reboot the phone.
pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?
pseudoremora said:
Yes, they're both rootable.
S-ON vs S-OFF; is just basically a security parameter that's being locked/unlocked. This allows for PC36IMG's files to be flashed via the bootloader without having to use or have authenticated signature keys from Google.
Basically, if you ever accept an OTA and it flashes and removes your recovery (CWM or Amon_RA); then you have no way of flashing custom roms/mods, etc... however with S-OFF, you have the ability to get your recovery back and set yourself back to root if need be.
Essentially, S-OFF allows for another method of flashing stuff to the phone besides just using the CWM or Amon_RA recoveries.
Hboot versions however can affect S-OFF; so it's important that if there is a new OTA that you always hold off, until a developer can validate that the hboot can be exploited and that the OTA can be rooted.
Click to expand...
Click to collapse
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Sent from my PC36100 using Tapatalk
badutahboy said:
Thanks for the explanations and the help.
How do I find out if it's S-on or off, and is it possible to change?
Click to expand...
Click to collapse
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
animal7296 said:
I have been trying to root 2.10 since yesterday and it has proven to not be possible as of yet. If you have a rooting method that works for me then would you share please?
Click to expand...
Click to collapse
luckylui said:
Im with u brotha im stuck on 2.10 from a mistake i made. Was originally on 0.76.2
Sux man
Click to expand...
Click to collapse
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
pseudoremora said:
To see if you're S-OFF or S-ON; you can boot your phone into bootloader mode.
To do this:
1. Power down the phone
2. Hold the Volume Down + Power button
3. You'll see a white screen with three little Androids
4. Read the very top of the screen; should tell you if you are S-ON or S-OFF.
You can reboot afterwards.
And yes, you can switch from the S-ON to S-OFF and vise versa, though I don't see why you would want to do the latter.
I apologize to the both of you guys; I was under the impression that 2.10 was S-OFF, apparently testing is still being done. For now, looks like you'll have to sit tight. Sorry guys.
Click to expand...
Click to collapse
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Sent from my PC36100 using Tapatalk
tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
True this, but when i did it i was at 0.76.2 and now screw at 2.10 cause it updated all the way n i didnt want to do that.. Got lost in the tangle haha
Sent from my PC36100 using Tapatalk
tpbklake said:
However it has been verified that if you were S-OFF on 2.02 you can install the OTA and you will end up with HBOOT 2.10 with S-OFF.
Click to expand...
Click to collapse
Yea, I heard about this in the IRC; too bad these guys can do that... unfortunate; but I'm sure the Unrevoked team will have a fix soon enough.
luckylui said:
No prob pimp
Ima call sprint n see if i can some how get me a phone w the 2.02 hboot and just pretty much get an upgrade from 0003 hardware to 0004 Lol
Im like jumpy rite now ahaha
Click to expand...
Click to collapse
Good luck with Sprint; I don't know how helpful they're going to be, but you never know...
@luckylui and animal7296, check out the 2.02/2.10 rooting thread again, it seems they got something working. Good luck.
badutahboy said:
Here's my question. My friend's brother attempted to root his stock Evo using simpleroot instructions I sent my friend 4-5 months ago (pre-2.2) without knowing that simpleroot isn't supported. His phone is now borked. When he tries to load into bootloader, he gets an error (not sure which one), but his phone will boot into android.
What I'm wondering is this: As of yesterday, his phone was updated and current as per sprint and the update commands in the system menus... Can he flash back to an older stock rom via RUU (such as this one) without causing other problems? If my understanding is correct, the latest sprint updates aren't yet rootable, right?
Any help on this issue?
Thanks
Click to expand...
Click to collapse
There actually is a way to downgrade without rooting, all you need to do is flash the mtd-eng.img file to your misc partition as explained in toast's rooting part 2 thread. After you do that it will let you flash any ruu that is compatible with your phone
Sent from my PC36100 using XDA App
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
Are you following the guide in the wiki?
Sent from my T-Mobile G2 using XDA App
Manarch101 said:
I have permerooted my DZ but now I seem to be having trouble understanding How to get S-Off and I can't do a nandroid backup unless I get S-off right.
Click to expand...
Click to collapse
First, yes you need S-Off to do a nandriod back up.
Second, you do not have permroot if you do not have S-Off. To get S-off there are several ways but I recommend using Rage+gfree found Here: in sub section "Rooting the Vision (G2/DZ) and DHD" This by far is the safest way to root.
But to let you make an informed decision there is also Visionary, now people in properly using this method, has produced a lot of soft bricks, I my self rooted this way, but again I still recommend using Rage+Gfree. But if you wish to still give Visionary a shot, Heres a link on how to properly use Visionary, make sure you follow everything to the "T". Read everything I have written in the post, do everything I have written in the post, then follow the videos exactly. But just to be clear, I am still recommending using the Rage+Gfree method. Happy Rooting.
ok joemm I tried the rage directions that you told me and I am not sure if it worked is there a way of knowing if it worked or not
Edit: nvm I can now get into CWM area which I could not get into before thanxs for the help and info.
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).
KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
This is a technical forum not some fire and brimstone 'do it or you'll die' sermon. Let's not construe fact and fiction/personal opinion on here. Just dish the facts unless otherwise rerquested.
As for gaining s-off, follow the wiki, push the files and you can literally copy and paste the commands if you need to (I suggest that so you don't screw up and brick your phone).
Click to expand...
Click to collapse
LOL..........how does he flash a custom CWM recovery with out having a rooted phone? Remember he is using ClockWorkMod to do a back up?
KCRic said:
What!!?? I know for a fact that you don't need s-off to do a nandroid. In fact, the ONLY thing s-off does that's of any significance is allow you to write to the system while it's booted - that's it. It's not some magic thing you absolutely need, just like having an ENG hboot isn't necessary to do 99% of the modifying you'll ever do.
Click to expand...
Click to collapse
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z
steviewevie said:
S-OFF lets you flash unsigned images and overrides version checking ,it isn't just about writing to the system while booted. I think you may be confusing defeating the NAND write protection with the actual S-OFF.
As far as I know you need S-OFF to flash a custom recovery, and you need CWM recovery to do a nandroid backup. I have never tried flash_image but I would be suprised if that let you flash a custom recovery while S-ON, because flash_image is just a regular binary.
Sent from my HTC Desire Z
Click to expand...
Click to collapse
True you can't flash a custom recovery and have it stick after a reboot but you can package it into an update.zip and flash it when you get into recovery. Aside from that you're phone performs the same. That's how we did everything on the MT slide before some one found a method to gain s-off. Of course there were no custom MTD partitions and we couldn't change the splash but that falls into the 1% of things the average 'rooter' will not attempt. The only reason we needed the ENG hboot was so that adb would catch our phone in recovery every time without running a loop.bat and praying to god. As far as NAND write protection, normally when a dev manages to break s-on they also break the write protection. At least that's what I've seen in phones with s-off. Are there any not like that?
Hopefully I didn't come off as an ass earlier, didn't mean it. I got 3 hours of sleep and I'm pulling a 13 hour day with a foot of fresh snow outside
I think you might be drawing too much comparison with earlier phones. The DZ and DHD have much stronger security than earlier phones. People familiar with experience of older HTC Android phones have often made incorrect assumptions about how things work on the DZ, some things are quite different (and typically much more complicated to unlock)
Sent from my HTC Desire Z
steviewevie said:
People familiar with experience of older HTC Android phones have often made incorrect assumptions...
Click to expand...
Click to collapse
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...
schaggo said:
Hell yes! And I'm one of them!
Last night I put some Cyanogen 6.1 flavoured ROM on my Magic/Sapphire. It was so easy: like 2 years ago or so I flashed some S-OFF ENG hboot, put some nice custom recovery on the phone and there I went, peacefully since ever. Reason for flashing the 6.1 CM was me giving the fone to my GF so that I can pick up a brand new Desire Z.
I came here, wanted to quickly crack that thing to play around with it and I find some gFree, Visionary, adb push stuff blah blah blah (I know my way around adb, that's not the point), it seems to have become alot more difficult than back in the days, as pointed out by steviewevie.
So, anyone willing to *quickly* summarize what has changed in the last 12 months regarding "rooting", "cracking" and ROM-customizing HTC devices for me...? I'm still, uhm... well, I'm shocked and overwhelmed. In the store I thought: cool, 7pm, device mine, home by 7:30, rooted by 8, Gingerbread-flavour on it by 8:30-9pm, ROM customization (settings and such) from 9-10, sleepy time by 10:30pm. Nah, it's past 10:30 and I'm still trying to figure out what's what with the new devices...
Click to expand...
Click to collapse
Its become more difficult because device manufacturers have made it more difficult. The "official" means to root the Vision is posted on the Vision wiki page here at XDA.
Sent from my T-Mobile G2 using XDA App
Thanks for the answer. I got the thing cracked in the meantime. The device feels so much smoother without Sense... and Gingerbread is good for one's soul
I am new to rooting a phone and have read count less threads on this site. First I have to say that this is one of the best forums I have come across. My first question I have decided to use the Universal Auto Root method found here http://forum.xda-developers.com/showthread.php?t=838448
First I want to stay with the Stock Evo Rom for now, not the Sprint Lovers Rom. Is there a way to not flash that rom using UAR or can I just Flash the Stock rom back after I have rooted the phone. If I have to flash the stock rom back then can someone point me in the right direction for a tutorial with the stock rom. I have modded other things besides phones and have no problem reading to find the answers. Most people that have problems just say "Oh I will root my phone today" and do not do the research before hand and in up with a paper weight. I have been read for about a week now and am just now getting to where I understand parts of the process.
Smurph82 said:
I am new to rooting a phone and have read count less threads on this site. First I have to say that this is one of the best forums I have come across. My first question I have decided to use the Universal Auto Root method found here http://forum.xda-developers.com/showthread.php?t=838448
First I want to stay with the Stock Evo Rom for now, not the Sprint Lovers Rom. Is there a way to not flash that rom using UAR or can I just Flash the Stock rom back after I have rooted the phone. If I have to flash the stock rom back then can someone point me in the right direction for a tutorial with the stock rom. I have modded other things besides phones and have no problem reading to find the answers. Most people that have problems just say "Oh I will root my phone today" and do not do the research before hand and in up with a paper weight. I have been read for about a week now and am just now getting to where I understand parts of the process.
Click to expand...
Click to collapse
I'm not familiar with that root method, so I'm not sure if there's a way to bypass the flashing of SpringtLovers, although I'd assume there is a way. Any time I've ever used Unrevoked to root, it never touched the ROM. After using Unrevoked, all the apps I previously had are still there and its on the same ROM. The only differences are that the bootloader will be S-off, you'll have clockwork recovery flashed, and you'll have the Super User app. With all that said, Sprint Lovers is about the exact same thing as stock, as far as I can tell. I flashed it on my girl's phone, because she liked her stock rom. The only differences are I noticed are very subtle, such as the battery indicator having the % value in it, the wireless tether app being added, and I believe it's deodexed. (and probably a few other things, maybe some optimizations and stuff) But as far as looks, it's identical to a stock ROM.
k2buckley said:
I'm not familiar with that root method, so I'm not sure if there's a way to bypass the flashing of Spring Lovers, although I'd assume there is a way. Any time I've ever used Unrevoked to root, it never touched the ROM. After using Unrevoked, all the apps I previously had are still there and its on the same ROM. The only differences are that the bootloader will be S-off, you'll have clockwork recovery flashed, and you'll have the Super User app. With all that said, Sprint Lovers is about the exact same thing as stock, as far as I can tell. I flashed it on my girl's phone, because she liked her stock rom. The only differences are I noticed are very subtle, such as the battery indicator having the % value in it, the wireless tether app being added, and I believe it's deodexed. (and probably a few other things, maybe some optimizations and stuff) But as far as looks, it's identical to a stock ROM.
Click to expand...
Click to collapse
You're correct, the only thing unrevoked does is root your phone and roots your current rom, in this case, stock with root access. So OP, I think you may want to use unrevoked for this case.
I have read that Amon Ra is better than clockwork recovery that was the main reason I was thinking of the UAR. Weird thing is that my system just finished a virus scan and it said that the UAR had something called Lotoor in it. Now I don't that I will download it. Is there a way to use unrevoked and then put Amon Ra on it. Better yet I have read that the Toast method is good but I have not found it in a tutorial. Is there one available. If I use unrevoked then how do you get clockwork removed and install Amon Ra.
Smurph82 said:
I have read that Amon Ra is better than clockwork recovery that was the main reason I was thinking of the UAR. Weird thing is that my system just finished a virus scan and it said that the UAR had something called Lotoor in it. Now I don't that I will download it. Is there a way to use unrevoked and then put Amon Ra on it. Better yet I have read that the Toast method is good but I have not found it in a tutorial. Is there one available. If I use unrevoked then how do you get clockwork removed and install Amon Ra.
Click to expand...
Click to collapse
Flash the file attached in the bootloader. Apply update, reboot, and then reboot back into recovery and you'll be on amon_ra 2.3. The amon_ra recovery is inside it, no needc to rename or extract the file.
teh roxxorz said:
Flash the file attached in the bootloader. Apply update, reboot, and then reboot back into recovery and you'll be on amon_ra 2.3. The amon_ra recovery is inside it, no needc to rename or extract the file.
Click to expand...
Click to collapse
Yup, like teh roxx said, you can use Unrevoked, then change to Amon Ra. And yes, Amon Ra is better (in my opinion). You can change recoveries any time you want, you could try them both out and see which works better for you if you wanted to. If you do run Unrevoked, just be sure that you remove htc sync, that you install the hboot drivers, and that you have no programs on your pc running that can talk to your phone (htc sync, pda net, easytether, doubletwist etc etc) and you also want to disable your anti virus when you run it, as that can also interfere.
Ok just so I get this straight first. The easiest way to do this would be to first use Unrevoked v3.32 to get root. Then go into recovery and with that image in the root of the sd card and update the phone with it. Then reboot and I would have Amon Ra installed after that. Would the affect unrevoked from working by changing from clockwork to Amon Ra. After I ran unrevoked would I need to run the unrevoked forever as well.
Smurph82 said:
Ok just so I get this straight first. The easiest way to do this would be to first use Unrevoked v3.32 to get root. Then go into recovery and with that image in the root of the sd card and update the phone with it. Then reboot and I would have Amon Ra installed after that. Would the affect unrevoked from working by changing from clockwork to Amon Ra. After I ran unrevoked would I need to run the unrevoked forever as well.
Click to expand...
Click to collapse
After using unrevoked, you boot into the bootloader, the white screen with the androids skating boarding to flash the file, not recovery, and then reboot. And no, changing recoveries after using unrevoked won't affect it, and yes, you would flash the forever zip in recovery after doing the previous steps.
Last question I promise because it is getting late here and I am not going to do this right now maybe tomorrow, well later today. Does running Unrevoked give you a full root. I have read that a full root is where the nand is unlocked and that gives you the ability to run nandroid to back up your phone. Also To remove root if I ever needed to go stock again do I uninstall unrevoked or to I install the lastest RUU from Sprint, and if so where to find them.
Smurph82 said:
Last question I promise because it is getting late here and I am not going to do this right now maybe tomorrow, well later today. Does running Unrevoked give you a full root. I have read that a full root is where the nand is unlocked and that gives you the ability to run nandroid to back up your phone. Also To remove root if I ever needed to go stock again do I uninstall unrevoked or to I install the lastest RUU from Sprint, and if so where to find them.
Click to expand...
Click to collapse
Unrevoked give you root, but flashing the unrevoked forever gives you the nand unlock. And to unroot, you flash the S-ON tool, then you flash the lastest RUU for you hboot, in this case, 3.70.
Smurph82 said:
Last question I promise because it is getting late here and I am not going to do this right now maybe tomorrow, well later today. Does running Unrevoked give you a full root. I have read that a full root is where the nand is unlocked and that gives you the ability to run nandroid to back up your phone. Also To remove root if I ever needed to go stock again do I uninstall unrevoked or to I install the lastest RUU from Sprint, and if so where to find them.
Click to expand...
Click to collapse
Unrevoked does give you full root, nand unlocked. Full root capabilities. Nandroid backups and restore galore. To unroot, you flash the unrevoked s on tool with recovery. Then run RUU. That's it. Nice and simple.
Sent from my PC36100 using XDA App
Smurph82 said:
Last question I promise because it is getting late here and I am not going to do this right now maybe tomorrow, well later today. Does running Unrevoked give you a full root. I have read that a full root is where the nand is unlocked and that gives you the ability to run nandroid to back up your phone. Also To remove root if I ever needed to go stock again do I uninstall unrevoked or to I install the lastest RUU from Sprint, and if so where to find them.
Click to expand...
Click to collapse
http://androidforums.com/evo-4g-all-things-root/194918-rooting-dummies.html
this thread is very helpful for the unrevoked method, and yes unrevoked gives you full root including nand
k2buckley how did you get your details and specs in your post. I looked for somewhere to add them but I could not find them anywhere.
teh roxxorz said:
Unrevoked give you root, but flashing the unrevoked forever gives you the nand unlock. And to unroot, you flash the S-ON tool, then you flash the lastest RUU for you hboot, in this case, 3.70.
Click to expand...
Click to collapse
Actually, Unrevoked unlocks NAND, too. Honestly, I don't know what the difference it between Unrevoked and Unrevoked Forever, but the regular Unrevoked turns "s" off, too. I've rooted two Evo's within the past month with the regular Unrevoked, and "s" was off and I flashed custom roms and all on both of the phones.
From the unrevoked website:
"unrevoked3 will permanently unlock NAND write protection by default on the following phones"
"unrevoked forever is a tool to set your Android phone's security level to S-OFF."
I've wondered what the difference is between one and the other for a good while now.
Smurph82 said:
k2buckley how did you get your details and specs in your post. I looked for somewhere to add them but I could not find them anywhere.
Click to expand...
Click to collapse
Go into the "user CP" and edit your signature.
rugedraw said:
Actually, Unrevoked unlocks NAND, too. Honestly, I don't know what the difference it between Unrevoked and Unrevoked Forever, but the regular Unrevoked turns "s" off, too. I've rooted two Evo's within the past month with the regular Unrevoked, and "s" was off and I flashed custom roms and all on both of the phones.
From the unrevoked website:
"unrevoked3 will permanently unlock NAND write protection by default on the following phones"
"unrevoked forever is a tool to set your Android phone's security level to S-OFF."
I've wondered what the difference is between one and the other for a good while now.
Click to expand...
Click to collapse
Well yes, it does give you nand unlock, but if you don't flash the forever zip, you won't be able to make the system changes, like changing the splash screen.
From the site: "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."
teh roxxorz said:
Well yes, it does give you nand unlock, but if you don't flash the forever zip, you won't be able to make the system changes, like changing the splash screen.
From the site: "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
Hmmm....so on the phones I used Unrevoked3 on, I will not be able to push/flash a splash screen onto it? I still don't quite understand the difference, but thanks for your input. I obviously still have A LOT to learn. lol
I keep seeing where people are using something called the Toast method to root their phone. Is that where you do everything from the command line. I bet a lot of people don't even remember the command line haha. Is there really any difference between the two (Unrevoked and Toast). What about security. Does rooting with Unrevoked have any back doors or anything like that. I don't mean to offend anyone just asking the question, I think that all the work people put into things like this are great. I work in high security areas and this is always on my mind. If I install something like Lookout Mobile Security could that mess with the phone being rooted. You all are great.
rugedraw said:
Hmmm....so on the phones I used Unrevoked3 on, I will not be able to push/flash a splash screen onto it? I still don't quite understand the difference, but thanks for your input. I obviously still have A LOT to learn. lol
Click to expand...
Click to collapse
Yea, it'll tell you no permissions, ect. And if you used unrevoked, to flash a splash is slightly different than the standard method, and I can tell you if you want to know. The unrevoked, goes to a low level to unlock those permissions.
Smurph82 said:
I keep seeing where people are using something called the Toast method to root their phone. Is that where you do everything from the command line. I bet a lot of people don't even remember the command line haha. Is there really any difference between the two (Unrevoked and Toast). What about security. Does rooting with Unrevoked have any back doors or anything like that. I don't mean to offend anyone just asking the question, I think that all the work people put into things like this are great. I work in high security areas and this is always on my mind. If I install something like Lookout Mobile Security could that mess with the phone being rooted. You all are great.
Click to expand...
Click to collapse
Well i started using the toast method, but it didn't work for me, since when I got my Evo 2.2 JUST came out, and people were scrambling blah blah, I digress. And what do you mean by backdoor? If you root using unrevoked you get all the same permissions/benefits of rooting as those with the toast method. And using a program like lookout security wouldn't affect your phone at all.
Smurph82 said:
I keep seeing where people are using something called the Toast method to root their phone. Is that where you do everything from the command line. I bet a lot of people don't even remember the command line haha. Is there really any difference between the two (Unrevoked and Toast). What about security. Does rooting with Unrevoked have any back doors or anything like that. I don't mean to offend anyone just asking the question, I think that all the work people put into things like this are great. I work in high security areas and this is always on my mind. If I install something like Lookout Mobile Security could that mess with the phone being rooted. You all are great.
Click to expand...
Click to collapse
I used Toast's Part 1 & 2 method to root back in June mainly because it was the only thing available. It was not a noob friendly process, IMO, but it worked and my phone is still rooted to this day using his method. Also, it forced me to learn a few things that I wouldn't have had I had Unrevoked at my disposal.
However, I believe Toast's methods are outdated now as the current Evo software and hboots require different exploits to obtain root.
teh roxxorz said:
Yea, it'll tell you no permissions, ect. And if you used unrevoked, to flash a splash is slightly different than the standard method, and I can tell you if you want to know. The unrevoked, goes to a low level to unlock those permissions.
Click to expand...
Click to collapse
Thanks, man.....I always see you on here helping people out and you are an asset to the XDA community. However, I Unrevoked the phones for some people that wanted wireless tether and screen shots......they could care less for the splash screens. Plus, I'm sure I can Google it and figure it out if it comes down to it. Mainly, I was asking for the knowledge as to "why" more than "how", and I think I follow now.
Your help is much appreciated, though.