Develop Bugs

Issue upgrading a rooted evo from 2.2 to 2.3

Ok let start by getting a few things out of the way.
1 I'm sorta a Noob ok kick me crack a joke or two I don't care as long as you help
2. I have Htc evo of course running stock 2.2 (baseband ver 2.15.00.11.19)
Kernel ver 2.6.32.17-gee557fd htc-kernel and18-2 #15) (S-ON)
Radio-2.15.00.11.19 and I'm using a Mac (if that help)
3. I rooted it using the unrevoked method.
The device works fine but bit I'm having a big issue trying to upgrade from 2.2 to 2.3.
I have been trying to unroot the phone so that I can update OTA.
But no matter how many times I try to unroot it my super user is still there
I would rather flash the phone to a 2.3 GB rom thats 2.3 with sense 2.1 or 3.0.
I've tried this the method found on youtube using the s-on and dropping the image file (zip) on the sd card and flashing it
by making sure you install the (s-on) patch
and re-flashing the RUU (PC36IMG).
but when I did that it said that i was re-flashing a old version.. so I found a newer version.
But when I drop it on my SD card as (PC36IMG.zip) it reads it, checks it then... takes me right back to the Hbot screen like nothing never happen!!!
I've been working on this for 3 days I've even tried restoring and everything.
I've been searching online for answers but I can't find anything that helps either its not up to date or just flat out dont work.
at the end of the day i just want a damn evo running BG 2.3 sense 2.1 or 3.0 would be nice.
​
oh by the way when i try to run the OTA it reboots startes to load get about 35% then goes to the exclamation mark / triangle.
I'm out of options please help me out! I've searched and read on for about 3 days now.
please either help flash the device to a stable working 2.3 with sense 2.1-3 or un root it so i can update it ota and re root it again...

http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
http://theunlockr.com/2010/06/14/how-to-unroot-the-htc-evo/
try these...
this link below should be a valuable resource for you...
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/Guides_&_Tutorials

Wow man, between the general and q&a sections there are seven threads dealing with this very topic. Yet you couldn't find any of them?
If you want to unroot and take the ota you will need to flash the s-on update and run the 3.70 ruu to unroot. Once you do that you'll be completely unrooted and like new. Then just take the update and it should go through without any issues. If, however, your bootloader shows a firmware version higher than 3.70 and you are s-on then I'm sorry to say you are stuck like that.

xHausx said:
Wow man, between the general and q&a sections there are seven threads dealing with this very topic. Yet you couldn't find any of them?
If you want to unroot and take the ota you will need to flash the s-on update and run the 3.70 ruu to unroot. Once you do that you'll be completely unrooted and like new. Then just take the update and it should go through without any issues. If, however, your bootloader shows a firmware version higher than 3.70 and you are s-on then I'm sorry to say you are stuck like that.
Click to expand...
Click to collapse
I've dont that and i still can not remove the root

You'll need to flash the PC36IMG through fastboot to see what's going wrong with it then. To do that download the AutoRoot tools zip and the PC36IMG_3.70.651.1.zip from the link below. Once you have them both unzip the tools folder and place the PC36IMG in it, then run the FlashZip script and tell it to flash the 3.70.651.1 zip
It should flash ok but if not it'll give you an error message saying what went wrong with it. Keep in mind you're going to be completely unrooted if your bootloader shows S-ON.

tailsthecat3 said:
http://forum.androidcentral.com/htc...19278-how-unroot-return-stock-ruu-method.html
http://theunlockr.com/2010/06/14/how-to-unroot-the-htc-evo/
try these...
this link below should be a valuable resource for you...
http://forum.xda-developers.com/wiki/index.php?title=HTC_Supersonic/Guides_&_Tutorials
Click to expand...
Click to collapse
ok I've been trying this method but im getting a error 140 BOOTLOADER VERSION ERROR
where can i get a more up to date ruu?

SixReasons said:
ok I've been trying this method but im getting a error 140 BOOTLOADER VERSION ERROR
where can i get a more up to date ruu?
Click to expand...
Click to collapse
What version does it say your firmware is?

xHausx said:
What version does it say your firmware is?
Click to expand...
Click to collapse
3.70.651.1 cl294884

SixReasons said:
3.70.651.1 cl294884
Click to expand...
Click to collapse
What HBoot do you have... I think just flashing one of the stock GB roms probably would of been easier just my opinion....
Sent from my EVO rocking Evervolv Gingerbread

i just found a ruu for 3.70.651.1 ... installing so far so good

You do realize that you'll lose root until a new method is found, correct? If you want to stay rooted, you need to reroot, then flash the stock rooted 2.3 rom.
If you want a newer version of Sense, you'll be outta luck there too - the new update is same ol' Sense 1.0.
Just making sure you realize this, since so many people are whining about not being able to root the OTA and being stuck with the uneventful update.
(from... Evo/MIUI/Tapatalk)

hey guys i got it working thanks for your help!!!!

[Q] downgrading to froyo

How could one downgrade to froyo from gingerbread. Do I just get the stock ruu and downgrade it?

jojo4747 said:
How could one downgrade to froyo from gingerbread. Do I just get the stock ruu and downgrade it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1164432
Question was just asked earlier today, Search before making a new thread. Thanks.

No - will not work
Hi,
Nope it will start up the process then stop saying no downgrade possible.

michaelbsheldon said:
Hi,
Nope it will start up the process then stop saying no downgrade possible.
Click to expand...
Click to collapse
Is ur phone s-off? You should be able to flash roms from froyo to gb as long as your s-off and have CWM installed.
Sent from my Incredible 2

No I don't have Linux and can you get s off on gb?

jojo4747 said:
No I don't have Linux and can you get s off on gb?
Click to expand...
Click to collapse
If you did the OTA Gingerbread from Verizon then you are pretty much stuck with it. You can still get s-off if you get the XTC clip. And you could have got s-off yesterday since AlphaRev released the windows download yesterday. You can be the guinea pig and try it now to see if AlphaRev does work with the Gingerbread update. Let us know if you do and it does.
And what is so wrong with the update that you actually want to go back to froyo? If it is the bloat and you were going to root, then why did you blow off the warning not to update?
Anyway way you choose, good luck!

I tried alpharev x and it didn't work but I saw that it didn't work for others on the post for windows users. Plus my hboot is still the .97 or what ever the prerequisite is. So shouldn't it still work? And I just want sense 3.0 sooo bad lol. I did it to get rid of the massive bugs like the back button not working and the keyboard u

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.

Downgrade from 2.3 to 2.2 problems

Hey!
I have problems downgrading to 2.2, since I dont like the new update at all. Alot of bugs and etc.
So I've tried installing the RUU from the computer, also renaming the file to PB99IMG.zip and putting it into the memory card.
Ive done this a thousand times when unrooting but now I get the error that my bootloader is up to date or something like that, I don't really remember.
Anyone who can help me ?
Thanks
EDIT: I get the error 140 bootloader error

Edit: It appears you can now unlock the bootloader and gain root access
Sent from my HTC Desire using XDA App

Is it possibly to root my phone and flash in a rom, and then unroot the phone to 2.2 froyo like I've always used to?

Understand that the hboot is locked with it locked you cannot do anything untill someone or team alpha and unrevoked come up with something that can..

Damnit, the damn 2.3 update sucks. Well then I have to wait then, I regret updating. I should have stayed on the 2.2.

2.3 update has just been unlocked using revolutionary!

yeah but i dont know the meaning of that.. im not used to s-off and i dont wanna brick my phone..

But if someone could do a quick guide for me for this s-off thing, and how to go back to the standard 2.2 froyo without s-off and root. By that I mean, that the phone is back to it's standard after doing this revolutionary.
Thanks

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?