Hi all,
A long while back I used an old version of Unrevoked3 to root my 2.1, and I've since installed several of the 2.2 ROMs which has kept me happy. Now I'm really itching to delete some of the Sprint crapware, and I also noticed that even though I ran the WiMAX update, it didn't stick. Both of these issues are, from what I can tell, due to the fact that I do not have NAND unlocked.
So, rather than go and try one of the older methods to get NAND unlock that potentially involves downgrading the PRI, I decided to just try and run the latest Unrevoked 3.2 which does S-OFF, NAND Unlock, etc. I gave it a shot using the ROM I'm most currently running (the 3.28 Leak) and Unrevoked 3.2 is dying out at the "Waiting for Root" screen, probably because I am using a ROM that already has root. I spoke with the guys in the Unrevoked freenode IRC channel and some of them suggested trying to install an unrooted stock ROM, then run Unrevoked 3.2.
So, can someone point me to an unrooted .zip for the stock 2.2 ROM? I found an RUU .exe file here but I'm afraid that running this is going to remove my recovery, which I really don't want to do in case Unrevoked still doesn't work after installing the "Unrooted" 2.2. There's a link to a .zip ROM file in that thread, but the file is corrupt, I've tried downloading it twice and it won't flash and I can't unzip it from my PC (it says it's corrupt).
Failing this, any other suggestions to get Unrevoked 3.2 to play nicely with my pre-rooted Evo?
Thanks!
I found what I was looking for here:
http://forum.xda-developers.com/showthread.php?t=780141
This essentially puts your phone back to "Factory" 2.2. I ran this and then ran Unrevoked 3.2 and now I'm all up to date with full NAND unlock and S-OFF.
Related
This phrase seems to be one of those everyone knows...well except me. What the heck are the EXACT steps to running an RUU?
I am in fastboot with usb showing...then I attempt to double click on the file on my desktop and get an error about it not being a win32 file. Seriously have searched google for hours and the search here is down.
Anyone got the steps to do this?
[A] What exactly is meant by 'run the RUU'?
RUU = Rom Update Utility
http://www.htc.com/uploadedFiles/Common/Software_Download/Detailed_RUU_Instructions_09232009.pdf
Well if this is all you don't know, you are way ahead of me, sheez.
Now root, get nand unlock, install new custom recovery, new PRI, new radio and Burnt 1.2 and you will be good to go, laughing...
An RUU is a Rom Update Utility. It is a program that you run on your desktop that flashes a new ROM image on your phone. So the phrase "run an RUU" literally means to run an RUU. They are version specific. Meaning it is not a program that can flash any ROM for you. There is a different RUU for every OS version.
What file are you clicking on on your desktop that's giving you an error?
[A] What exactly is meant by 'run the RUU'?
I am not quite sure what you are trying to do, but I do have a suggestion. Take a look at regaw_leinad thread on [GUIDE] How to root Android 2.2 on the EVO 4G. He put this out way before unRevoked 3.21. BTW: This was the method I used to root my 2.2 EVO, worked like a charm. Anyway, it's not about the process he used to root an EVO, it's more about all the steps and what does what that you learn going through the process. May help you achieve whatever it is you are trying to do.
Good Luck
the link: http://forum.xda-developers.com/showthread.php?t=765496&page=45
I am already rooted and running a rooted version of 1.47. I have a file called...RUU_Supersonic_1.47.651.1_Radio_2.05.00.06.10_release_CL195459.exe.
This was in an attempt to try to get a 'more' stock version of 1.47 on my phone so that then I could accept the OTA.
I have all of the sdk loaded and yes I have that fastboot in same folder as the adb...(if that means anything.)
When the first 2.2 rolled out many many people with rooted phones accepted the OTA and lost root. So I know it is possible to load the OTA when you have a rooted phone but for some reason I am getting an error. (In another thread, but it is an apply patch error?)
So again....does running a RUU mean...1)You boot to recovery, 2) You go to fastboot, 3) You plug in USB, 4) After you see Fastboot USB (and phone shows up in device manager) you double click the RUU
Is that the process?
Since I didn't see it mentioned. But when you run the RUU, you lose root. If you want to run a "closer to stock" ROM then download SteelH's ROM, and flash that through Recovery.
No, running a RUU is running a PROGRAM that does the update for you. Run the RUU right now without connecting your phone, it will tell you the steps.
Don't even worry about accepting the OTA. Flash this PC36IMG file and it will bring you completely current.
Hmmm...ok. Metalhead, I'll re-read your post when I get home and probably go in that direction.
Debugguy, that document was pretty good at showing me what I should be seeing, but now I am wondering if the file I got was a windows file or not...because it doesn't do that at all.
Thanks ya'll.
Something that may help, go to the unRevoked web site, some really good "back to stock" info here, may
give you some ideas.
go here: http://www.unrevoked.com/#evo
select (1) unrevoked3, then more
select (2) unrevoked Forever, then more
Okay, I'm attempting to gain root access, basically I followed
# Arrow# [GUIDE] How to root Android 2.2 on the EVO 4G
I flashed my phone back to the 2.1 froyo version, but now I am stuck, when I reboot my phone with unrevoked it automatically selects the first option HBOOT with no input from me.
I THINK this may have to do with the fact that I can't get the HBOOT driver's installed. I can't find where the driver's should be installed when rebooted. So now I'm stuck on FROYO 2.1, with no root access. I know that getting to 2.1 is the hardest part of root, but I need to know how to get the phone rooted. Please if anyone can post info, or has had a similar problem please post here if you can help me.
Did your phone originally have 3.30 on it? If so, you need to flash the leaked 3.30 rom back, then follow the instructions about how to turn S-OFF with hboot 2.02.
http://forum.xda-developers.com/showthread.php?t=828437
Where can I find instructions on flashing 3.3 I'm not even sure how I flashed 2.1
bump, if no one can help me get my phone rooted, can you at least let me know how to get it back to normal, so I have the built-in flashlight app etc.
i never thought i would need help with rooting, but i have the same problem. i have boot .97. which should make it easy. i am stock 2.1 and i am trying to flash a pc36img.zip but it simply wont load. it goes all the way to checking, and dumps me back at the hboot. no idea what i am doing wrong. i will try some troubleshooting now. ?!?!
edit i now have .79. trying to flash rooted pc... holding 3.29 now. wish me luck
same problem. goes from checking straight back to hboot. no idea at all.
Long story short;
Bought a used Incredible to replace my rooted D1.
Ended up being rooted and still on 2.1 update-1.
I unrooted/wiped hoping it would update to 2.2 but no luck.
I don't have a problem rooting this phone but I would like to get the official 2.2 update on the phone first.
I searched around and found a couple links;
http://forum.xda-developers.com/showthread.php?t=737400
Now, according to this first link you either need to be rooted with a 2.x radio or root and flash a 2.x radio. (My device does not have a 2.x radio, for the record I have 1.00.03.04.06)
Here's another link;
http://free-pc-guides.com/news/how-to-manually-install-latest-ota-for-htc-droid-incredible-06428
Does this method appear legit? Does this update.zip provide the neccessary radio?
Usually this would be a no-brainer for me but Im confused why the first link requires you to manually flash a newer radio before FroYo...
I would re-root and flash the OTA deodexed ROM thats rooted. PM me for link. or run the most recent RUU to get to most recent release.
After installing unrevoked I am now having a problem with updates. It will start the update, the progress bar makes it about halfway thru, then the phone just locks and a soft reset to follow. I'm new to android, the phone is an EVO, and the only thing that has been done thus far is running unrevoked for the wireless tether. Please help out a noob.
From what I understand the update looks for the stock recovery image. Because your rooted via unrEVOked, your device has a custom recovery (ClockworkMod) installed. You have several options if you wanna do a little research but if your simply looking for an easy answer to your question I would recommend getting a copy of the latest RUU (ROM Update Utility) which will restore your EVO back to a factory fresh state and will allow you to install the update. You will loose root though so be warned. Look around in the EVO developement forum and grab the latest RUU, save to pc, connect your device via USB, run RUU and follow the prompts. Another option would be to find a ROM based off the lastest update. There really not hard to install and this is the perfect time to start learning the ins and outs of Android. If anything should go wrong you always have the RUU to fall back on. Here is the 3.70.651.1 RUU. NO need to manually check for the update, this will leave you with a clean install of the latest software. http://forum.xda-developers.com/showpost.php?p=9836069&postcount=67
Thanks for the info. I actually just moved off of an HD2, so its all greek to me, just not that familiar with it. But again, thanks for the useful info, will get on that right away.
I had the same issue ... Ended up flashing 2.1, OTA update, OTA update and then flashed superuser ... Of course I started out with unrevoked forever ...
If I'm correct the latest version of unrEVOked does the same thing as unrEVOked forever, I say this because I used unrEVOked 3 and after updating my device is still S-OFF but when I download the superuser app from the market I get errors when trying to install clockwork recovery via Rom manager. setCPU is also telling me I'm not rooted. Any advice?
http://unrevoked.com/rootwiki/doku.php/public/forever
Go down to the section that talks about reinstalling an official recovery ...
Thanks so much. Very simple yet so many people are looking for that exact solution. You saved me a ton of searching, thanks again.
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?