Develop Bugs

[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!

[Q] returning phone - what exactly to return to stock?

My 4g was broken with the 3.29 update (really). The Sprint store was nice enough to order me a replacement after they determined they couldn't fix it. It'll come in a day, then I mail back the old phone.
I have used unrevoked 3.21 to root and put Amon-RA on it in the past. Before going to the store to have it checked out, I reflashed the stock 3.29. Amon-RA is still on there but it's not-rooted. Is there anything I should do before returning it so they don't say it was my fault? I think I need to reflash to S-ON. Anything
else?
Also, I think my flashing adventures are over but I'd really like root access on the new phone so I can use Titanium backup. It should have Froyo installed already. If I update to 3.29, flash Amon-RA for nandroid backups and use unrevoked 3.21 - and nothing else - that shouldn't break my 4G right? I plan to backup my mac wimax.img before doing anything.

Unrevoked has the s-on tool posted on their site just flash it first then flash the stock pc36img and ur golden, like u never even turned the phone on in the first place..sorry i would give u a link but im not sure if i can do that from xda app. U can hit me up if u have any probs

Cy_n_ic said:
Unrevoked has the s-on tool posted on their site just flash it first then flash the stock pc36img and ur golden, like u never even turned the phone on in the first place..sorry i would give u a link but im not sure if i can do that from xda app. U can hit me up if u have any probs
Click to expand...
Click to collapse
Got it. Thanks mate.

Welcome, i learned that from deleting all the sprint bloat apps and deleted the sprint voicemail by accident and i realy liked it so i had to flash the img to get it back, at the same time as the ota came out so i unrooted, flashed pc36img, ota, then reroot after making a nand backup....always nand..always

[Q] S-OFF!! im running stock gingerbread too!!

Ok so i know that gingerbread doesnt have root yet, but i installed the mod for the sense launcher it didnt work but my s-on isnt on its off... i dont know if this means anything to anybody ill upload a pictureee. Does this mean we might be closer to root?

i think i uploaded the picture ?

Yup. U r a lucky Guy. Put a copy of amon RA onto the root of ur SD card. Boot onto the bootloader and when it asks if u want to update say yes. U will then be able to flash whatever u like

If you were s-off before, you should still be s-off after. I have two s-off EVOs that I was going to sell, so I restored them to latest OTA (yea I'm a jerk!) but they stayed s-off (lucky for those when I do decide to sell).
I don't get the point of this, unless you had an S-ON phone and somehow got it S-OFF after the 2.16 hboot and 2.3.3 android upgrade.

YES! thats the thing! I unrooted, got the gingerbread update, after installation and what not it said S-ON. now it says s-off and i have no idea what i did, i been doing so much crap to my phone i dotn even remember what i did. I wanted to try the sense launcher from tommytomatoe and it froze my phone and couldnt do nothing. So i pressed power volume down and it now said s-off.

scoot16 said:
YES! thats the thing! I unrooted, got the gingerbread update, after installation and what not it said S-ON. now it says s-off and i have no idea what i did, i been doing so much crap to my phone i dotn even remember what i did. I wanted to try the sense launcher from tommytomatoe and it froze my phone and couldnt do nothing. So i pressed power volume down and it now said s-off.
Click to expand...
Click to collapse
If what you say is true, you might be able to help the rooting effort by pulling some info off your phone that could be valuable to the devs. I would explain the situation to them, and offer whatever info they need from your phone.
They'll probably call shenanigans on you-- I know I would. But maybe-- just maybe, your Evo carries the mutant X gene that we need to crack this puzzle.

Nice man! maybe just maybe your phone is the "root" of all hahahahaha

BigMatza said:
If what you say is true, you might be able to help the rooting effort by pulling some info off your phone that could be valuable to the devs. I would explain the situation to them, and offer whatever info they need from your phone.
Click to expand...
Click to collapse
This!
10char

scoot16 said:
Ok so i know that gingerbread doesnt have root yet, but i installed the mod for the sense launcher it didnt work but my s-on isnt on its off... i dont know if this means anything to anybody ill upload a pictureee. Does this mean we might be closer to root?
Click to expand...
Click to collapse
Did you have root before at all? Did you use Unrevoked3 to root before? If you did, how did you unroot?

Yes i used unrevoke 3 to root but i installed a stock froyo ruu unrooted because after i tried to unroot with unrevoked it didnt work. After i installed the froyo ruu it said S-ON, i then went on to install gingerbread, went back to check the hboot to see if everything was right and it still said S-ON, then i went thru every process to root my phone just to see if i could try soemthing but failed of course. I then wanted to try tommytomatoe sense launcher for unrooted and after my phone froze alot i went to clear data by pressing power and volume down. That is when i saw it was S-OFF. do you want to know anythingg else?

Please unroot again and post pics , you are still trying to unroot are you not. Go go.

Im cant unroot, im not even rooted, im running stock gingerbread ota 4.24.651.1

Did you flash the s-on tool when you unrooted?

complex88 said:
Did you flash the s-on tool when you unrooted?
Click to expand...
Click to collapse
Yes sir. I did all that was needed to unroot my phone.

Don't think running a ruu will turn s-on. Once you are s-off, you are s-off until you run the s-on tool. Correct me if I am wrong.
Swyped from my Supersonic

i am so tempted to try this....
can you provide the link to this tommytomato mod , at this point, i dont care if i brick my evo ill just go harass sprint and get a refurb or something if i do

LCL22 said:
i am so tempted to try this....
can you provide the link to this tommytomato mod , at this point, i dont care if i brick my evo ill just go harass sprint and get a refurb or something if i do
Click to expand...
Click to collapse
This didnt do nothing it was because of the mess up on my end did i go and find the s-on.

You need to write down everything you did and the order you did it. Also please provide the links that you used.

Also, was it the 4.22 or the 4.24 that you updated to?
*Edit* Nevermind I just saw your earlier post

scoot16 said:
Yes i used unrevoke 3 to root but i installed a stock froyo ruu unrooted because after i tried to unroot with unrevoked it didnt work. After i installed the froyo ruu it said S-ON, i then went on to install gingerbread, went back to check the hboot to see if everything was right and it still said S-ON, then i went thru every process to root my phone just to see if i could try soemthing but failed of course. I then wanted to try tommytomatoe sense launcher for unrooted and after my phone froze alot i went to clear data by pressing power and volume down. That is when i saw it was S-OFF. do you want to know anythingg else?
Click to expand...
Click to collapse
I say somehow some way when u attempted to re-root it went thru cuz that's the only logical way s-off could've been attained. Clearing ur data won't and u were s-on before u took the OTA update so it wasn't present before hand. Have you tried flashing another rom from recovery just to see if it works? You my friend maybe the "MVD" lol!!!

S-OFF still showing after OTA?

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.

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?