S-OFF still showing after OTA? - Verizon Droid Incredible 2

My wife got her replacement Inc2 today after the one she got last week just died. She was on Froyo so I might of.. swapped her phones.. anyways, I rooted, went to the bathroom and the stupid ota ran I guess because when I came back the phone was on GB 2.3.3 however my boot screen shows S-OFF. Can anyone help me to verify that S-OFF is indeed still off. I can post any screen shots etc.. I am still a noob when it comes to the Inc2.

If your boot screen says S-Off, you are S-Off
Sent from my stock, bloated ADR6350 using XDA Premium App

Did you flash clockworkmod recovery when you rooted? I didn't think the OTA would take if you had a custom recovery. In any event, since you're still s-off, you're fine.

I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.

kujayhawks77 said:
I actually hadn't flashed recovery yet. Went ahead and flashed recovery. Superuser installed but busybox keeps failing. I am manually installing them since the patch I found also includes a rooted kernel but it is for Froyo.
The biggest deal for me is I am still S-OFF. I'm just confused as to how I managed to remain S-OFF after the OTA went through. If I can't get busybox installed I'll probably install Ginger Sense to obtain it.
Click to expand...
Click to collapse
Alpharev changed ur hboot to a higer version than the one in the OTA.. this is why it kept you S-OFF.. if I'm wrong someone correct me.

So basically I just got really lucky and kept my S-OFF even though the OTA went through.

kujayhawks77 said:
So basically I just got really lucky and kept my S-OFF even though the OTA went through.
Click to expand...
Click to collapse
No. stock hboot is .97. alpharev bumped you up to 1.something.. idk I used XTC clip.. since your hboot is newer than the OTA.. it keeps you S-OFF, pretty smart by alpha.

So does this open a gateway to first root in Froyo and then go gingerbread and retain the root?

Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Now when I use the term "gateway" I say this loosely because it doesn't fix anything for anyone who is already on GB. If indeed this works, it would only work for a small percentage who get Froyo and don't flash clockwork before running the OTA.

I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA

tnez said:
I just got my Inc2 as a replacement for my fascinate, came with 2.1 might try your steps and see if my root will stay after doing the OTA
Click to expand...
Click to collapse
2.1??? I think you are mistaken, sir

beenz said:
2.1??? I think you are mistaken, sir
Click to expand...
Click to collapse
He was mistaken cause it is sense 2.1 but android 2.2
Sent from my Incredible 2 using XDA Premium App

kujayhawks77 said:
Only way to be able to tell is to have someone repeat my steps which were: stock froyo, run AlphaRevX, did not flash recovery, Run OTA (this happened by accident I did not intend for the OTA to go through) after the OTA is finished reboot and if it is indeed a "gateway" then S-OFF would still be on. (After seeing S-OFF was on (and making sure it was okay) I went ahead and installed cwm recovery at that point)
Click to expand...
Click to collapse
I've been wondering about this. I got my Dinc2 early July and I'm still on stock, unrooted Froyo. Somehow the OTA update to GB hasn't hit yet. Could I run ApharevX to get S-off and stop there for now? I am happy with bloated stock for the time being and want to be able to receive OTA updates, but would like to have the option down the road to add Clockworkmod and flash custom ROMs. From kujayhawks experience it seems that this should be possible.
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
P.S. First post, though I've been lurking around for a while. Great forum/community.

xenakis said:
Basically, if I achieve S-off with AlpharevX now, will I be able to pretty much do anything later?
Click to expand...
Click to collapse
It appears from reports that S-off stays after the OTA to 2.3, so yea, that would seem to be the case.
If you turn S-off with AlphaRev, you might want to just go ahead and install Clockwork recovery at the same time. Doing so won't root or install SuperUser or anything, but you would be able to then backup your phone and be ready to flash if you wanted.

If you install clockwork recovery you won't be able to receive OTAs though, just keep that in mind. You can flash back to the stock recovery, but unless you are familiar with ADB, it won't necessarily be an easy process.

Related

[Q] Getting ready for Ota

alrighty so here it is the ota is coming and i silly as i may be rooted like 3-4 days ago. i didnt take the time to s-off just got the custom recovery updated the radio to 2.05 and downloaded sky raider vanilla. hboot is .79.
now from my research that ive gather and correct me if im wrong but all i need to do is :
*s-off
*flash the stock recovery
after that i should be good for the ota correct?
so far i got the s-off done looking for a lil bit of instruction as to how to get the stock recovery flashed safely.
Any and all help is greatly appreciated i thank you all very much.
inessi said:
alrighty so here it is the ota is coming and i silly as i may be rooted like 3-4 days ago. i didnt take the time to s-off just got the custom recovery updated the radio to 2.05 and downloaded sky raider vanilla. hboot is .79.
now from my research that ive gather and correct me if im wrong but all i need to do is :
*s-off
*flash the stock recovery
after that i should be good for the ota correct?
so far i got the s-off done looking for a lil bit of instruction as to how to get the stock recovery flashed safely.
Any and all help is greatly appreciated i thank you all very much.
Click to expand...
Click to collapse
I have attached the stock recovery that needs to be flashed from the HBOOT.
It is my understanding however, that you need to downgrade to the .77 HBOOT, 1.xx radio AND 2.1 system for the update to notify you, give you the option to download, and install successfully. However, I am a few drinks into my night.
If you choose to follow that path. I suggest you read this
awesome stuff really appreciate it man gonna give it a try now, fellow floridian lol
inessi said:
awesome stuff really appreciate it man gonna give it a try now, fellow floridian lol
Click to expand...
Click to collapse
w00t!
If you get hung up anywhere, pm me and I'll give you a number to call me at in the morning/afternoon and I'll walk you through it.
your my hero bud, my freaking hero stock recovery got s-off i think thats all i need to recieve the ota and do it yea?
thnx
See, from this point, I'm not sure if you need the .77 HBOOT 1.xx Radio and 2.1build-1 on your phone (I'm really questioning it, as I beleive I read in a few places that you do, but I'm not sure at this point in the evening). I don't think the Skyraider rom will get a notification when the update is available. I'd say if you don't get a notification for the update when everyone else in the free world is, then you may have to.
As long as you have S-OFF, it doesn't matter either way, you have complete control for the rest of your phone's life. Whatever you do, don't turn it back on lol.
hmmm well if it doesnt show up guess my next set of questions is how to get back to stock everything
inessi said:
hmmm well if it doesnt show up guess my next set of questions is how to get back to stock everything
Click to expand...
Click to collapse
The link I posted above with the "I suggest you read this" line is where you will need to go if it boils down to that.
o haha some how i missed that lil section of text did you just add that recently?
but ok sounds good ill run through it in the morning probably
and holy crap the link you posted makes this all look so simple hah
Well I have stock everything, except for my hboot is .79, im on stock 2.1 stock recovery just have .79 hboot not .77, i think i will still get the update though...
rdmerck said:
thnx
See, from this point, I'm not sure if you need the .77 HBOOT 1.xx Radio and 2.1build-1 on your phone (I'm really questioning it, as I beleive I read in a few places that you do, but I'm not sure at this point in the evening). I don't think the Skyraider rom will get a notification when the update is available. I'd say if you don't get a notification for the update when everyone else in the free world is, then you may have to.
As long as you have S-OFF, it doesn't matter either way, you have complete control for the rest of your phone's life. Whatever you do, don't turn it back on lol.
Click to expand...
Click to collapse
I too am awaiting the OTA update and was concerned. My phone is running 2.1 update 1 and is rooted. Will this prevent me from receiving the OTA update? If so what steps do I need to take to make sure I get the update then? Also should I put on unrevoked forever? If I do so will I need to do anything other than that to still receive the OTA update and keep root access?
magneto417x said:
I too am awaiting the OTA update and was concerned. My phone is running 2.1 update 1 and is rooted. Will this prevent me from receiving the OTA update? If so what steps do I need to take to make sure I get the update then? Also should I put on unrevoked forever? If I do so will I need to do anything other than that to still receive the OTA update and keep root access?
Click to expand...
Click to collapse
Other than the root, did you modify anything else to your phone?
If not, your still with the .77 HBOOT, 1.xx baseband, and 2.1update-1 system?
Add unrevoked forever to remove s-off, then flash the stock recovery back to your phone. Your goal here is to have S-Off
in order to get the OTA (from my understanding) you need the stock recovery, do a little search I have all the faith in the world that you will find what you are looking for. you want to run unrevoked forever BEFORE you accept the OTA2.2, so this is your steps, root, run unrevoked forever getting S-OFF, find the file for the stock recovery, PB..IMG file, flash that in hboot, this will set u back to stock 2.1 update1, stock radio, stock recovery, but still have S-OFF to regain root, after the OTA comes.
So if I have stock everything, and have hboot .79 will I still get the OTA I don't see why not...
BlazeD OnE said:
in order to get the OTA (from my understanding) you need the stock recovery, do a little search I have all the faith in the world that you will find what you are looking for. you want to run unrevoked forever BEFORE you accept the OTA2.2, so this is your steps, root, run unrevoked forever getting S-OFF, find the file for the stock recovery, PB..IMG file, flash that in hboot, this will set u back to stock 2.1 update1, stock radio, stock recovery, but still have S-OFF to regain root, after the OTA comes.
Click to expand...
Click to collapse
Currently the only thing I have done was rooted and removed CityID and but have not changed the radio or anything else. I have installed Unrevoked forever now. So do I still need to flash stock recovery even though I haven't changed the boot files or radio files at all?
Yes from what I've read you HAVE to have the stock recovery. what is your HBOOT once u get stock recovery?
BlazeD OnE said:
Yes from what I've read you HAVE to have the stock recovery. what is your HBOOT once u get stock recovery?
Click to expand...
Click to collapse
My HBOOT is 0.79.0000
Radio 1.00.03.04.06
Any input would be helpful as to whether I will get OTA or do I need to do something.
once in hboot, go to recovery, if you have clockwork you wont get it i dont think, if you get a red triangle you have stock recovery and you are good to go.
magneto417x said:
I too am awaiting the OTA update and was concerned. My phone is running 2.1 update 1 and is rooted. Will this prevent me from receiving the OTA update? If so what steps do I need to take to make sure I get the update then? Also should I put on unrevoked forever? If I do so will I need to do anything other than that to still receive the OTA update and keep root access?
Click to expand...
Click to collapse
Yes, install unrevoked forever. The fact that you are rooted will not affect the ability of your upgrade, it is the lack of the stock recovery that will halt you.
Unrevoked forever will allow you to flash ANY zip file you want to the phone (namely a zip that has su and Superuser.apk) and will allow you to regain root in the event that it is ever lost due to an OTA or user error.
S-OFF is a beautiful thing.
I would love to take my phone to Verizon right now with a manufactured problem, let him see the Superuser, official 2.2 system and then stock recovery. Could be priceless!

How to update system when your HTC is rooted

Bros, please help
My Desire is running Froyo 2.2 and I rooted it.
There is an OTA today for version 2.29. I already download it. But when it restarted and installed, it failed with error like wrong signature or sth like that.
Please help me if you got any clue on this.
warmest regards,
Don't apply OTA updates on rooted devices, either use a custom rom which is based on 2.29 or use a 2.29 RUU and root again.
TheGhost1233 said:
Don't apply OTA updates on rooted devices, either use a custom rom which is based on 2.29 or use a 2.29 RUU and root again.
Click to expand...
Click to collapse
Exactly. I think you have too little knowledge of rooting. Don't even think about the word "official" when you rooted your phone.
Actually I toggled Sig off in Clockwork mod and
was able to install the update, it went well and the phone was working
fine, i did loose my root tho , so I had to root again....
I am a beginner, so don't take this as advice, cause I don't know
the downside off togling Sig off. I just wanted to state that in fact
it is possible to ota a rooted device..
grtz
Lanbase said:
Actually I toggled Sig off in Clockwork mod and
was able to install the update, it went well and the phone was working
fine, i did loose my root tho , so I had to root again....
I am a beginner, so don't take this as advice, cause I don't know
the downside off togling Sig off. I just wanted to state that in fact
it is possible to ota a rooted device..
grtz
Click to expand...
Click to collapse
Thx for your advice.
It's generally considered that if you're rooted you should not apply an OTA as you won't truely be back to 'stock' and it can cause issues further down the line. It can be done, though, as highlighted above but if people just used some common sense as opposed to just saying OK to any updates this question wouldn't get asked 30 times a day

[Q] S-OFF on hboot 2.16

I have a few questions about s-off and being in the latest OTA.
Here is the short and skinny...
When my wife got the evo when it first was released last year i tried to root it since i wanted to install a program that needed root. i had no real idea on what i was doing and think i might have gotten root, although I am not sure. I never flashed any rom nor did I ever flash that apk and just gave up since I didnt want to break her new phone. (basically got a bit scared)
As for the main screen if you reboot and hold down volume and power, it will display "s-OFF".
She did the two Gingerbread updates OTA and is now on GB 2.3.3. stock.
I noticed that the hboot is set at 2.16...and it still displays "s-off".
I just read that there are different types of "s-off".
Now, the questions are:
1. Is her phone actually rooted?
2. Can I turn on the "s-off" to "S-ON" so that we can bring the phone in for repair?
3. Is there anything that anyone here can gain from her phone being in the state that it is in for people who cant get root under the latest hboot version?
4. I just read that s-off has multiple meaning. How can i tell which one I have on her phone? ie. radio, nand??
Thanks in advance.
pretty sure sprint wont notice the s off so dont bother going s on to ttake it in, even if they do, they dont really care anymore, so long as its got the stock os at least, but they really dont care bout it being rooted anymore
but yeah, your phone basicaly kept the root
I agree with LCL22.
Unrevoked does have an S-ON tool, but I've never used it and I'm not even sure it works anymore. Just leave it S-OFF and flash one of the stock unrooted ROMs from recovery. But I've heard people take their phones back with CM6/CM7 on there, MIUI, etc. It probably depends on the store/rep to be honest.
"Rooted" means having access to the SU binary (superuser). It's a linux thing. It's like having Administrator access to a windows computer. This allows complete control over the currently installed phone software.
S-OFF means that the phones protections have been disabled and you are free to flash unsigned ROMs via the bootloader (HBOOT).
S-OFF is nice, because you can flash any ROM you want via the bootloader; there is no need for a custom recovery to be installed. Of course you can also use the bootloader to flash a custom recovery such as ClockworkMod or Amon_RA.
github said:
I agree with LCL22.
Just leave it S-OFF and flash one of the stock unrooted ROMs from recovery.
Click to expand...
Click to collapse
Will flashing the latest unroot ROM from sprint (which is already on there from the OTA update) will turn the s-off to s-on??
Also, if it says s-off, does that mean that it is fully rooted?
The reason why she is considering bringing it into sprint for repair/replace is that is having problems sending texts multiple times to the person she is texting...basically, she sends one text and the receiver gets the same text 20 times.
Either there is something wrong with the phone, the network, or the fact that it is s-off and she is running a non-rooted rom. This issue has been happening since January and on the stock Froyo.
Lastly, I just noticed that she had advanced task killer and I uninstalled it just to make sure it wasnt anything that she has running which is causing the issues.
Thanks in advance.
amart79196 said:
Will flashing the latest unroot ROM from sprint (which is already on there from the OTA update) will turn the s-off to s-on??
Also, if it says s-off, does that mean that it is fully rooted?
The reason why she is considering bringing it into sprint for repair/replace is that is having problems sending texts multiple times to the person she is texting...basically, she sends one text and the receiver gets the same text 20 times.
Either there is something wrong with the phone, the network, or the fact that it is s-off and she is running a non-rooted rom. This issue has been happening since January and on the stock Froyo.
Lastly, I just noticed that she had advanced task killer and I uninstalled it just to make sure it wasnt anything that she has running which is causing the issues.
Thanks in advance.
Click to expand...
Click to collapse
S-off only means you are nand unlocked so you can flash a custom recovery and flash a ROM. To be rooted, you have to flash a rooted rom which 99.999% of all the ROMS are rooted on XDA.
S-off just means that you can flash an alternate recovery and custom roms. It doesn't mean that it is rooted.
check in your app list and see if the Superuser app is there. If it isn't, it probably isn't rooted.
S off is perfect! Don't go s on if you can help it.
At my local repair store I chatted with the tech (after running s on tool) if they even check. The guy said not usually. They mainly check if it is stock sense like the Rosie and stuff. And even then they don't usually. They only check if someone brings in their phone with technical or software issues. With hardware they don't bother.
But that is my store.
S off and root are separate things but they kind of depend on each other. To root permanently you need s off, at least for devices with nand.
Sent from my PC36100 using Tapatalk
But since the Hboot is listed as 2.16, Should I just flash a rooted stock rom to see if this clears up the texting problems she was experiencing?
Most importantly, will flashing a odexed rooted rom work or brick it because it has the 2.16?
amart79196 said:
But since the Hboot is listed as 2.16, Should I just flash a rooted stock rom to see if this clears up the texting problems she was experiencing?
Most importantly, will flashing a odexed rooted rom work or brick it because it has the 2.16?
Click to expand...
Click to collapse
Sprint is currently having issues on their end in regards to texting. I've attached an article that you can read over.
http://m.wired.com/gadgetlab/2011/07/sprint-sms-text-problem/
ENG S-OFF
EDIT: Nevermind, I just took the risk and it paid off.
I was actually about to start a thread asking the exact same thing. I'm selling my phone and I've heard that if it's not relocked it can't be activated on the Sprint network so I've been trying to get S-ON. I have "EVT2-2 ENG S-OFF" right now.
By the sounds of this all I really need to do is flash a good PC36IMG and all should be good, right? No chance of a brick?
i will read that shortly, but i am more interested in the fact that there is a OTA update done and it now has 2.16 as the hboot. Is this now going to brick if i try to flash a rooted stock rom since she isnt into custom roms?
Now, the questions are:
1. Is her phone actually rooted?
2. Can I turn on the "s-off" to "S-ON" so that we can bring the phone in for repair?
3. Is there anything that anyone here can gain from her phone being in the state that it is in for people who cant get root under the latest hboot version?
4. I just read that s-off has multiple meaning. How can i tell which one I have on her phone? ie. radio, nand??
Thanks in advance.
Click to expand...
Click to collapse
Answers :
1. If you flash a recovery.img it will be.
2. You can't really do anything with the s-off right now because I don't think that any of the tools that would do that have been updated to work with hboot 2.16.
3. I'm not sure if anyone can use what you have but I would write up a post in a dev thread to be sure.
4. There are only two meanings that I know of when it comes to s-off. The first is accepting the OTA while rooted which will put your phone in a weird state. If you can use your phone after then I don't think this applies to you. The other is just not having a recovery installed which will render you just unlocked and not rooted.
amart79196 said:
i will read that shortly, but i am more interested in the fact that there is a OTA update done and it now has 2.16 as the hboot. Is this now going to brick if i try to flash a rooted stock rom since she isnt into custom roms?
Click to expand...
Click to collapse
No. Flashing a regular rooted odex or deodex version of the RUU won't hurt you if your s-off. I would make a nand backup using amon ra recovery before flashing anything just to be safe.
Amon Ra Recovery - http://forum.xda-developers.com/showthread.php?t=705026
Rooted OTA ROM - http://forum.xda-developers.com/showthread.php?t=1133379
amart79196 said:
But since the Hboot is listed as 2.16, Should I just flash a rooted stock rom to see if this clears up the texting problems she was experiencing?
Most importantly, will flashing a odexed rooted rom work or brick it because it has the 2.16?
Click to expand...
Click to collapse
It doesn't matter what hboot you have so long as you're s off
No bricks don't worry. Bricks usually occur during manual radio updates
Sent from my PC36100 using Tapatalk

Rooted 2.2 then OTA update to 2.3... half root?

Hi,
I rooted my phone with Unrevoked when it was at 2.2 froyo. When the gingerbread OTA came around I was cautious about me being rooted and accepting a OTA update. I searched all around saying it wouldn't do anything, this will happen, etc.... When I first updated it everything was fine...Until I used one of my root apps. OK fine I'm not rooted. But when i used this app called the blizzard authenticator it would say i have a rooted phone. So is my phone half rooted? If its possible, I would like to go back to the day that i first bought the phone and restart everything. I can provide further details about my phone if asked.
S-off
HBoot 2.16.0001
Thanks!
I don't quite get what you want.
But if you just want to go back like it was out of the box, hop over the development forum and grab an RUU and return to stock.
here is a link, pick one http://forum.xda-developers.com/showthread.php?t=884060
Oh ya i forgot. Im a n00b. So get the RUU and hope for the best?
Yep, it will erase everything (not SDCARD) and you will be back like the day it came out of the box.
Alright my noobness is kicking in haha. I see like 15 of them. [ROM] RUU SuperSonic EvO 3.70.651.1 OTA - Stock - Sense - Deodexed & Odexed Version originally posted by teshxx would be the one?
Nevermind i didnt even see ur link. Thanks so much ill post the results
Muffspring18 said:
Hi,
I rooted my phone with Unrevoked when it was at 2.2 froyo. When the gingerbread OTA came around I was cautious about me being rooted and accepting a OTA update. I searched all around saying it wouldn't do anything, this will happen, etc.... When I first updated it everything was fine...Until I used one of my root apps. OK fine I'm not rooted. But when i used this app called the blizzard authenticator it would say i have a rooted phone. So is my phone half rooted? If its possible, I would like to go back to the day that i first bought the phone and restart everything. I can provide further details about my phone if asked.
S-off
HBoot 2.16.0001
Thanks!
Click to expand...
Click to collapse
If you used Unrevoked and got s-off, and then ran the ota update, to get your full root back you just need to flash either Amon ra or Clockworkmod recovery and make sure the superuser app is up to date.
Ok everything went well with the RUU. How do i know for sure this is stock 2.3 no root. Say i were to bring my evo into the sprint store for repair would they find out that i was rooted before?
before u run a ruu or pc36img u need to flash the s-on tool from unrevoked. since ur hboot is 2.16 now u have to run the 4.24 ruu or pc36img. if u do flash s-on tool and 4.24 ruu, u will NOT be able to root again as of now b/c no root method has been developed yet!! you have been warned
Muffspring18 said:
Ok everything went well with the RUU. How do i know for sure this is stock 2.3 no root. Say i were to bring my evo into the sprint store for repair would they find out that i was rooted before?
Click to expand...
Click to collapse
when u boot into bootloader does it say S-ON or S-OFF???? s-off means it has been rooted
S-Off. I might want to root in the future when there has been a root developed tho. For right now i want to go back to being non rooted.
ok...since ur s-off u can flash a recovery (clockwork or amon) from the bootloader and then start flashing roms again at anytime now. If ur trying to take ur phone to the store i dont think being s-off will really matter. As long as u have deleted any apps or files from ur sd card that are root give aways u can just play dumb at store like "uh idk maybe it came that way".
Ok so besides the fact that the S-Off Im all set? Or am i still half rooted?
u should be set

back to stock 2.2....

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?

Categories

Resources