Related
I am new to the Android development scene (appro 6 months now) and when I first rooted, I neglected to backup my stock ROM. I'm much more comfortable now, but am still confused about a few things. I'd like to have a stock image to rely on if something goes wrong or I need to call for service. Should I unroot and use a RUU or an odex ROM? Do I really even need to unroot? Is it necessary to update my HBOOT image as well? I know this is a lot of questions, but I remember from my days of DSS testing that I wish I had a backup of my original CAM! Is it too late?
I was a little nervous to use the 'unrevoked-forever-s-on'. I can't re-root?
I don't recall which method I used to root. I think toasted. Does it matter?
Currently I have multiple ROMS. Primarily I use Cyanogen, Warm2.2, or Ava. I have 0.76 hboot, and ROM manager premium... I use whichever recovery is necessary.
Suggestions?
Also, how can I be sure which RUU or ROM to use as stock. I am worried that there were updates that blocked rooting with some methods. How do I know which RUU will be the best bet? I remember having to wait for updates to come down from the satellite stream. Does it matter if I use an older RUU then wait for updates, or just use a recent stock posting?
If you need to take your evo in for servicing, its recommended to unroot, for a few reasons. Also, if you unroot, you'd need to run an ruu appropriate to your hboot version. That will send you back to completely stock, so no need to flash a stock rom after that, then you can simply run an OTA update, then take it in.
And yes, if you run an old/incorrect ruu, you'll just get errors.
Thanks! and I clicked thanks too
my hboot is 0.76. what RUU is compatible with that? (I've checked the ROM sticky and there is none) should i just pick most recent RUU and flash the corresponding hboot, then flash that RUU? When I looked at the most recent RUU posting, it says DO NOT FLASH! YOU WILL LOSE ROOT! Do they mean permanently?
I gotta run! I got kids! Thanks again... be back tonight!
lil_bono said:
Thanks! and I clicked thanks too
my hboot is 0.76. what RUU is compatible with that? (I've checked the ROM sticky and there is none) should i just pick most recent RUU and flash the corresponding hboot, then flash that RUU? When I looked at the most recent RUU posting, it says DO NOT FLASH! YOU WILL LOSE ROOT! Do they mean permanently?
I gotta run! I got kids! Thanks again... be back tonight!
Click to expand...
Click to collapse
You lose root, it returns you back to stock, but you can re-root as well.
Thanks. I guess I am over-thinking this...
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.
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
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?
A while ago I rooted a friends phone so they could play with custom roms. I used the Unrevoked3 tools to do the root and I believe I did the S-off with Unrevoked forever. She doesn't really want to mess with it anymore and as a result of the root she is stuck on Froyo. What needs to be done in order to get her back to a state where she can recieve the OTA updates?
I'm not sure what prevents the OTA but off the top of my head it could be any or all of these:
Custom Recover
S-Off
Custom Rom
Updated Radio
She is using a Sense Rom currently (I believe Virtuous) as she wanted to make it look as similar to what she was used to before. I'm hoping to prevent wiping it as well if possible. Can anyone tell me what I need to do to get this back to a point where she can get the Gingerbread update and possibly point me to the instructions on how to do it?
This will help you get back to stock http://forum.xda-developers.com/showthread.php?t=786436
By doing this she will no longer have root and may not be able to regain root again.
If she wants a stock Gingerbread Rom, just flash the Stock Plus Gingerbread Rom in the dev section. It'd is a lot easier/faster and still have root. Also going back to stock for future updates may be pointless as this phone may no longer get any other updates.
jackbtha1 said:
This will help you get back to stock http://forum.xda-developers.com/showthread.php?t=786436
By doing this she will no longer have root and may not be able to regain root again.
If she wants a stock Gingerbread Rom, just flash the Stock Plus Gingerbread Rom in the dev section. It'd is a lot easier/faster and still have root. Also going back to stock for future updates may be pointless as this phone may no longer get any other updates.
Click to expand...
Click to collapse
I checked out that thread but it looked old and it was a little confusing. What I really need to know is which component needs to replaced in order to get OTAs. I don't need the phone set to factory. In fact I would prefer to keep the current data in tact. I just need to allow the phone to receive the official gingerbread OTA. If that OTA removes root then that's fine. My friend just doesn't want to have to manually load updates going forward and she doesn't care about root.
Go here and download the Froyo RUU the PB31IMG version http://pvillecomp.com/?page_id=22 . Then make sure the file is named PB31IMG and place it on the root of your SD Card boot in to Hboot, let it load and press volume up to accept the install and it'll do it's thing. I'm not sure if this will give you stock recovery, which you need to receive the OTA updates. If it does not get it here http://pvillecomp.com/?page_id=28 and follow the same PB31IMG steps as I mentioned above (Make sure you delete the RUU PB31IMG file first ). Then just wait for the update. I think you can try the Giongerbread RUU as well and you will be good to go but I have never tried that one before.
I would probably just stick with root and get the stock plus rooted rom. The plus features alone are much much better then what the stock offers anyways.
http://forum.xda-developers.com/showthread.php?t=1260994
And if she is still on froyo then I would assume she still has the froyo radio, so don't forget to flash the new gingerbread radio to coincide with the new gingerbread rom you just flashed for her
http://forum.xda-developers.com/showthread.php?t=1227215
---------------------------------------
Of course if you would like to simply revert the phone back to stock with the newest OTA out, simply run this from your computer
http://www.multiupload.com/XF7EG5F2I7
Hope this helps....
here ya go...
http://forum.xda-developers.com/showpost.php?p=19895586&postcount=1
trevoryour said:
I checked out that thread but it looked old and it was a little confusing. What I really need to know is which component needs to replaced in order to get OTAs. I don't need the phone set to factory. In fact I would prefer to keep the current data in tact. I just need to allow the phone to receive the official gingerbread OTA. If that OTA removes root then that's fine. My friend just doesn't want to have to manually load updates going forward and she doesn't care about root.
Click to expand...
Click to collapse
To receive the ota you need to have the stock recovery, and have all stock apps still installed and enabled. To get to complete stock you need to do an ruu. Either a PB31IMG.zip thru hboot, or the ruu.exe with a pc. However this latest released ota is the final update our phones will ever officialy get, so you dont have to worry about future otas. That being said i would just do as others have sugested and flash one of the stock roms, either wildstangs ota rom or jermaines stock plus. Wildstangs is complete stock, and jermaines is stock with some cool features added. You can find them both in the dev section.