Related
I never did unrevoked, never cared for it (rooted long ago and used update.zips to get to froyo.) But I wanted to do the combo update (radio, wimax, pri, ect) and saw you had to be s-off with unrevoked. So, if I have an unlocked nand, but didn't use unrevoked meathod, can I still flash the combo update? Maybe it's time I start from scratch again.
S-OFF = NAND UNLOCKED
Boot into HBOOT and you should see S-OFF at top of screen. If you are fully rooted you already have S-OFF.
bender1077 said:
S-OFF = NAND UNLOCKED
Boot into HBOOT and you should see S-OFF at top of screen. If you are fully rooted you already have S-OFF.
Click to expand...
Click to collapse
Cool thanks bender.
However, Unrevoked forever makes the S-OFF permanent, meaning even if you flash an update that is unrootable, you can still flash a custom recovery and rom, so essentially, you can't lose root. If you just have normal full root, you would be vulnerable to an OTA update. So its personal preference, but unrevoked forever is definitely best for the people who tend to be a little update happy.
superlinkx said:
However, Unrevoked forever makes the S-OFF permanent, meaning even if you flash an update that is unrootable, you can still flash a custom recovery and rom, so essentially, you can't lose root. If you just have normal full root, you would be vulnerable to an OTA update. So its personal preference, but unrevoked forever is definitely best for the people who tend to be a little update happy.
Click to expand...
Click to collapse
Never been an issue, I always wait. I honestly can't see who would want s-off permanent, what if you had to claim your phone for an exchange? lol.
jlechner said:
Never been an issue, I always wait. I honestly can't see who would want s-off permanent, what if you had to claim your phone for an exchange? lol.
Click to expand...
Click to collapse
It's not irreversibly turned off. While it wasn't available originally, the Unrevoked folks now have a utility that will turn it back to s-on.
unrevoked forever = SOFF @ the radio/nvram
engineering rooted = SOFF @ the bootloader
OTA will typically update the bootloader, so if you are NOT unrevoked forever, then you will loose SOFF when the bootloader is updated.
with unrevoked forever SOFF, you can simply reflash clockwork/amon via pc36img.zip in the root of your sdcard.
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
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
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
What problems are you having with the RUU that you flashed? You can't downgrade, as you found out, so being stock S-ON you don't have many options other than flashing a different 2.3 stock image, and/or waiting for the actual OTA.
resyek83 said:
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
Click to expand...
Click to collapse
The only way i know to get back to 2.2 is to s-off your phone then ruu the 2.2. which will get you back to s-on 2.2, but you will be get the update nag every day once they start pushing the OTA out again.
resyek83 said:
Ok so I got impatient and installed the Gingerbread update that VZW pushed out a week or so ago, found the file here since I wasnt one of the lucky few to get the OTA push. I flashed it through HBOOT since it was a signed file, please note that I'm not rooted and the phone is completely stock. I want to go back to 2.2 stock and wait for the official, and apparently I'm not doing something right. running the RUU for the 2.2 gives me a bootloader version error, and dropping the zip named PB31IMG.zip and flashing through hboot gives me the "main version is older" error. I have tried installing Unrevoked 3 and it gets past the last reboot, after "waiting for system to settle" message, it says "running root" for a few minutes then says "unable to get root, is your firmware too new?"
...so yea, I'm guessing I'm S.O.L.? Sorry kinda noob here, came from the Eris forum, I guess theres a few things that are different.
Click to expand...
Click to collapse
For the moment, I think you are SOL, only because the same thing happened to me.
If you have 2.3.4 and S-ON, there's not really a way to downgrade back to 2.2, as HBOOT won't allow a downgrade. In fact, only PB31IMG.zip files that are signed by HTC will allow to be flashed. All others will not be recognized by HBOOT.
Unrevoked will no longer root after you have flashed RUU and have S-ON. You will get the error you are describing.
I have also tried newer root tools, such as Revolutionary, which is in the Beta phase.
Unfortunately, this method is not supported for the Incredible, and per Unrevoked's support channel on IRC, this is not likely, as apparently a phone that is only over a year old is considered a 'Legacy' device.
At this point we can only hope for the following:
HTC unlocks the Bootloader for the Droid Incredible on HTCdev.com. Only a handful of devices are listed at the moment.
Team Unrevoked releases a new version of Unrevoked that can find an exploit for 2.3.4 and enable root.
Revolutionary adds support for 'legacy' devices such as the incredible.
We are in a small minority, but hopefully enough devices will get the OTA, or refurbs get sent out with 2.3.4 that users will eventually require a new way to root.
Hang in there.
Yeah, if you're s on then from everything I've read, your screwed for now.
ahh ok....yea i kinda figured. I should have done a tad more research before I did it....everything works ok at the moment, except my battery life isnt as good as it was, but its not terrible. I guess I'll wait for the official OTA or wait and see if Unrevoked can come up with a solution.
your best option woulda been to root first. While you still had S-off flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-on.
TheBr0ken said:
your best option woulda been to root first. While you still had S-on flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-off.
Click to expand...
Click to collapse
Doing that with S-On is what has OP in this position in the first place. You have the right idea but mixed up S-On and S-Off.
TheBr0ken said:
your best option woulda been to root first. While you still had S-on flash the file you found here. Then if you wanted you could have reinstalled Clockwork recovery and superuser and either flash a stock rom or unroot. whats killing you is S-off.
Click to expand...
Click to collapse
Thank you, Captain Hindsight. In my situation, I was coming from a Rooted, 2.3 Sense 3.0 ROM, with S-Off.
I believe S-off is swicthed back to S-ON when you flash the RUU.
In the mean time, my phone is borked. Too new of a firmware on too "old" of a device.
SlimSnoopOS said:
Doing that with S-On is what has OP in this position in the first place. You have the right idea but mixed up S-On and S-Off.
Click to expand...
Click to collapse
yup, fixed.
deadsoulboy said:
Thank you, Captain Hindsight. In my situation, I was coming from a Rooted, 2.3 Sense 3.0 ROM, with S-Off.
I believe S-off is swicthed back to S-ON when you flash the RUU.
In the mean time, my phone is borked. Too new of a firmware on too "old" of a device.
Click to expand...
Click to collapse
what killed you was you musta flashed the s-on patch for some reason. I ran the same file you did. I still have s-off
The RUU does NOT turn the security flag to -ON. You do lose root until you flash a custom recovery and superuser, which is done easily.
Any hope for us S-ONs with 2.3.4? Is there something by way of unrevoked or something we can flash to try and get back to root?
There has to be something...
So I have a droid inc that I'm sending back in, and I want to revert it to stock. Right now, I'm running s-off, with a rooted stock OTA 2.3.4 (Incubusj's, I think) with the latest CWM. What do I need to do to make this thing bone stock to return it? I've done a search, and maybe I just suck at searching, but I can't find good, concise directions, and I don't want to screw it up.
sk8erord said:
So I have a droid inc that I'm sending back in, and I want to revert it to stock. Right now, I'm running s-off, with a rooted stock OTA 2.3.4 (Incubusj's, I think) with the latest CWM. What do I need to do to make this thing bone stock to return it? I've done a search, and maybe I just suck at searching, but I can't find good, concise directions, and I don't want to screw it up.
Click to expand...
Click to collapse
Search for the Ultimate get back to stock thread. It'll tell you what you need to to to get back to Stock 2.2 with S-ON.
That thread seems rather old. I'm running the 2.15.10.07.07 radio on hboot .92. Do I still just run the s-on and then run the RUU?
Well, was probably unnecessary, but I reverted to the old radio, flashed a rooted stock rom, then ran s-on through recovery, then a stock pb31img rom through bootloader. So it is bone stock again.
sk8erord said:
That thread seems rather old. I'm running the 2.15.10.07.07 radio on hboot .92. Do I still just run the s-on and then run the RUU?
Click to expand...
Click to collapse
True, that thread is old, but the info is still good. Good call on reverting back the radio, as you don't want that to cause any troubles. Pretty easy to get back to stock and S-ON huh?