Hey guys,
I have rooted my new evo 4g with the "[GUIDE] How to root Android 2.2 on the EVO 4G" and the first time around i did it all with no trouble (Although it was time consuming) I uploaded a couple of themes, also no problems... Then i tried flashing the Fresh Evo 3.3.0.1 and since i never had any other previous version of Fresh (or any other ROM for that matter) i didn't bother backing up or wiping, and when i rebooted the phone (After i flashed the ROM) it got stuck at the white "HTC EVO 4g" screen and stayed that way, and after about 10 minutes of that i decided to pull the battery and go back into recovery and wipe the drive & cache ect... That also did nothing, once i rebooted i was still getting stuck at that screen, So after that i did some sort of combination of updating the fastboot and then doing the "Clear Storage" option, i was able to at least get the phone to go through that whole startup process again, and i was able to use the phone again. but i ended up in the long run wiping EVERYTHING off my phone in the process, and after i was finally able to get my phone to work again, i promise myself i would NEVER mess with that stuff again... BUT, being as stupid as i am, 2 days later i was back into trying to install stuff again, But everytime i did, i was meant with the same results again. (Startup screen freezing) So after about 5 tries i decided to give up, within the past few days i noticed that HTC had the new 3.29XXX software version up... Now i figured since i can't get the themes and ROM for that matter to work anymore, i just ended up installing the new updates. but yesterday i tried to go into recovery and start messing around with it again, but i can't get to AMON-RA recovery screen anymore, My guess is when i updated the phone, it removed the necessary files for the recovery to work... So last night i deleted all the files i put onto the SD Card (For rooting) and started the full rooting process over again (pushin adb through command prompt ect) and i was able to get the RA recovery back, but when i tried installing a theme, and reboot it takes me through the startup and gets to the "4G Bootscreen" and then it just keeps looping over, and over again. So i had to end up wiping, clear storage ect again to get the phone to work again.
Sorry for the long explanation but i feel the more information there is that better help someone can provide me help with. So i guess my question is does anyone know what i should do to get the recovery to work again to i can start using themes & ROMS again? I'm just pissed off that everything was fine until i tried to flash freshes ROM, I must have done something wrong.
Thanks for all the help in advance, I realize I'm a noob to this site but any help would be greatly appreciated.
Holy crap. If you don't know what you're doing, you need to read hundreds of posts! I probably spent two weeks on these forums before I even considered rooting.
1. First off, regaw's root method is a little outdated. Unrevoked 3.21 is out and fully automated (or nearly). No adb, no command line, etc. Unrevoked is root privileges + nand unlock.
2. Never accept an ota update if you rooted! Ever! Best case is that it breaks root (which is what happened to you).
3. You must have s-off on you're boot loader screen to be able to install custom roms/kernels. This is nand unlock.
4. Always and forever wipe data and dalvik cache when switching between roms or when recommended during upgrade by the rom developer! Boot loops can happen!
5. To install a rom, wipe data cache in recovery then apply the zip of the rom. Phone may take 5 minutes at the boot screen because it's rebuilding the cache you wiped.
6. Always do a nand backup! Always, no excuses!
Greetings,
Everything dom085 said is gospel - really.
For convenience, I'm adding links to the rooting apps mentioned, as it appears
these are the ones you need. Do not forget to follow a successful root
process with Unrevoked forever (S-OFF). You will most assuredly want/require this
for all your rooting and MOD changing activities.
Once S-OFF has been achieved, you will not be required to do it again,
as it's a lower-level (radio) process, and other activities won't affect it.
Unrevoked 3.21 for HTC-EVO(supersonic)
Unrevoked forever for HTC-EVO(supersonic)
If unsure, start here to insure you get the correct
version(s) for your phone.
HTH
--Chris
Chris, thanks for adding the links, I'm not able to do that yet.
However, the newest Unrevoked 3.21 method includes permanent nand-unlock by default. No more separate Unrevoked-forever process. From the Unrevoked 3.21 website:
Does this permanently unlock the NAND flash on my phone?
Yes. The default configuration of this tool disables the phone's security, which also disables the NAND locks placed on the storage by the bootloader. If you choose not to disable security, the /system partition will be read-only after the tool completes
dom085 said:
Chris, thanks for adding the links, I'm not able to do that yet.
However, the newest Unrevoked 3.21 method includes permanent nand-unlock by default. No more separate Unrevoked-forever process. From the Unrevoked 3.21 website:
Does this permanently unlock the NAND flash on my phone?
Yes. The default configuration of this tool disables the phone's security, which also disables the NAND locks placed on the storage by the bootloader. If you choose not to disable security, the /system partition will be read-only after the tool completes
Click to expand...
Click to collapse
Strange. I rooted with Unrevoked 3.21. Everything went flawlessly. But S-OFF
wasn't indicated. So I downloaded the S-OFF, and performed it. Now S-OFF
shows up.
Strange, because I did it pretty recently (after the "new improved" version was released).
Please note, I'm not arguing with you. Just sharing my own experience.
--Chris
CTH-EVO said:
Strange. I rooted with Unrevoked 3.21. Everything went flawlessly. But S-OFF
wasn't indicated. So I downloaded the S-OFF, and performed it. Now S-OFF
shows up.
Strange, because I did it pretty recently (after the "new improved" version was released).
Please note, I'm not arguing with you. Just sharing my own experience.
--Chris
Click to expand...
Click to collapse
Interesting.
It does say "default configuration of this tool." I didn't see any way to change it though when I was rooting (I've done two phones through Unrevoked 3.21). In fact, I didn't see any menus or options at all. Perhaps you changed the "default configuration" somehow?
Related
i am a noob I tried three methouds to root. Unrevoked, needless to say I got OTA and killed it, Simple root and simple root OTA. Simple root Ota just fails to do the job but on the first pass it did finish. On the second pass I ended up in a boot loop. and ow i am still trying root. Phone is still working I have not bricked it yet. But recovery mode seems to go to a black screen with a small phone and a Big red arrow. Can anyone help. I want to fully root but cant get the job done.
hmm. Did you wipe appropriately (never used that method). Boot loops usually indicate that
If you got the first half done, see if you can complete the nand unlocked with this:
http://forum.xda-developers.com/showthread.php?t=701835
You might be able to get into your recovery if you connect it to your computer and perform: adb reboot recovery. That black screen is sign that you don't have a custom recovery flashed. Following the link above, if you can complete it, will flash a custom recovery that can be accessed through boot loader
I think all this stuff has been done by simple root OTA version. I can now use unrevoked to get root and use Wi Tether.
Have you looked at simple root. I think NAND is still locked. and unrevoked does the unlock. Is there a simple way to do this part. and why does the simple methoud promis full root with NAND unlock. I would like to put in a custom rom. but I have come so close to bricking. Is there a simple methoud to finish this. Half of this stuff I dont understand
Anyone up on Simple Root methoud and hw to fix this simply Remember I'm a noob.
Do a factory reset, go through SimpleRoot, and when you get your recovery flashed, wipe ALL of the data: /data, cache, and dalvik-cache. That *should* solve your issues.
What is DaLVIK Cache I tried the Flash recovery in simple root, I choose Clockwork. That cache name is not there and thats when I ended up with the loop. Do you wipe the phone before flash or after.
IUt would realy help if I had good instructions Simple root dosen't give any.
Sorry for all the pitiful noob stuff And thanks for careing enough to answer.
I can root with unrevoked and use tether. I just want to get this right next time.
Clockwork must be running because the Sprint startup screen is gone and it says HTC quietly brillient.
Reply to:
Do a factory reset, go through SimpleRoot, and when you get your recovery flashed, wipe ALL of the data: /data, cache, and dalvik-cache. That *should* solve your issues.
__________________
Sprint HTC EVO 4G
"I have more power, RAM, and storage space in this one phone, then in my first four computers, combined."
Stock ROM 1.47.651.1 Rooted
Amon_RA Recovery 1.7.0.1
Cingular Samsung SGH-X427. VZW Samsung SCH-a950. VZW Palm TREO 650. Cingular Motorola RAZR v3. AT&T Pantech Duo C810. AT&T Motorola RAZR v9. AT&T iPhone 3G. AT&T iPhone 3GS.
I tried this, still no real root. I must use unrevoked to root. When i run Wireless teather I get the message Your phone is in an unrecognized state and after a few tries the teather does run. Superuser Permission shows up after I run unrevoked.
I have not installed a custom rom yet. Cant find any good instructions I heard damage controll is good and also Fresh new version. Do you think doing this will give me real root or am I missing somthing. Also where can I find some clear instructions on installing a custom rom. I cant understand the ones Ive seen. They assume your an expert at this. I am not. I have electronic engineering and IT experience but this is a little different.
This time I flashed Clockwork I found the Dalvik cache line.
I've completed the steps on SimpleRoot OTA, along with spending several hours now online trying different walkthroughs. None of them are resulting in me having a rooted system. I installed ROM Manager and I still get error when trying to run privileged command.
I would flash back to factory, then use unrevoked 3
*This was posted from my Evo 4G*
Okay, before the question can be answered:
1) What version is your phone currently at: i.e. 1.47, 1.32?
2) Have you tried any other versions of rooting besides SimpleRoot for your phone?
PM me if your really stumped. I'm always willing to help out where I can.
~Jasecloud4
my software number is 1.17.651.1. The boot animation is the HTC logo and 'silently brilliant' (ironically it plays a really loud chime while writing this).
As far as methods I've tried:
Toast 1 and 2
Simple Root OTA 4-click
whitslack's method
jiqqaman's simpleroot 3-click
Start by determining your HBOOT version. Full root means you have NAND unlocked which allows you to do anything.
79.00 = locked
76.20 = unlocked
Reboot and upon start-up hold down the volume down and power buttons at the same time until the white screen appears. HBOOT version will be listed at the top in green letters I believe.
If you have 76.20 I would recommend going back to the Whitslack method and starting there. If it is 79.00 you have additional work to do.
I believe that version number is the pre-release version and I never had that one. It probably came from one of the different methods you tried. I was lucky enough to root prior to the OTA using Toast 1 & 2. Since your version seems "older", if you don't have HBOOT 76.20, you may be able to use the original toast 1 & 2 method.
Bottom line....once you get HBOOT 76.20....you are GOD
I have 76.20. I don't feel like a god =[
I discovered that i can in fact su to root in a terminal.
However, I'm trying to install Fresh ROM, and since I've not found any instructions on here on how to actually do that, I'm guessing it's with this ROM Manager app. When I run the first part of that app I get error when trying to run privileged command. This is what led me to believe I wasn't rooted.
I would suggest starting with the Whitslack method. I know you indicated that you tried it but I'm not sure of the order in which you did so. Its a piece of cake with the 76.20 HBOOT.
Whitslack gives you the best "starting" point for future ROM's and is in fact where I began before flashing Fresh 1.01.
I did NOT have to flash the Radio and WiMax updates included in the Fresh thread.
1. Whitslack
2. Install Clockwork (ROM Manager) and flash alternate Recovery (Amon RA)*
3. Wipe Data/Dalvick/Cache (Use Amon RA Recovery)
4. Flash Fresh 1.01
5. Setup
6. Configure Fresh Updater using instructions at the link in the Fresh 1.01 thread
* This step may be optional if you already have Amon RA installed as a recovery. It works better than clockwork during the wiping process and I recomend just sticking with it once you get it installed.
As far as I can tell whitslack's method doesn't work. I've tried it twice, to the T.
At step 15, instead of a menu I get a red triangle with an exclamation mark. That's it. Cannot continue.
n4th4nr1ch said:
As far as I can tell whitslack's method doesn't work. I've tried it twice, to the T.
At step 15, instead of a menu I get a red triangle with an exclamation mark. That's it. Cannot continue.
Click to expand...
Click to collapse
Honestly I have not reviewed the Whitslack thread for sometime now. When I did it it was 2 steps total and it worked. Apparently he has added new information for a select few people.
Did you receive that "Fail-PU" Error?
Do you know what recovery you are currently running?
I finally figured out that he has failed to mention you need to hold volume up and press power at this page apparently.
However the next step is 'Using the Volume and Power buttons as before, select "Flash zip from sdcard."'
There is no option for Flash zip from sdcard.
I see:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Have you seen this thread?
http://forum.xda-developers.com/showthread.php?t=717955&highlight=toast+part
Between this and the "Starting Over" thread your answers are there. Didn't realize that it had become more complicated than when I (luckily I guess) performed it.
Bottom line...like I said...having HBOOT 76.20 is the majority of the battle. Follow the flowchart in the thread I posted above and report back.
I finally got into Fresh. Thanks. Wish there was somewhere which clearly in plain english outlined the relationships between all these steps; would have made this a lot easier to get to, since all the walkthroughs seem to have trouble keeping up with each new change every version, or whatever.
So I never rooted, I have been waiting for the Over the Air.
If I root now, when I get the OTA will I still be rooted? And if so, what steps should be taken?
I know there are two unrevoked applications that need to be run...the first for root...the second for s-off (which I am still not entirely sure what this is)....
I have also seen that unrevoked is much simpler on a Mac and thankfully I just got one.......
So if rooting now and getting the OTA and keeping root is possible.... is there a step by step of the order I should do this in? (please don't flame and say I can search...I did...couldn't find.. I did however find a ton of threads where people say to search.......if you need to flame me can you at least post a link to where I was stupid enough to miss it)
Thanks
I am wondering the same. I have rooted with unrevoked3 and forever but have not touched the radio. Will I receive the OTA like this? If not what do I have to do to get the OTA and then get root back ?
Assuming you have a truly stock Incredible (meaning you didn't force any third party roms or leaked radios), then you follow this order:
1. Unrevoked Flash/Recovery - Adds Clockwork Mod and Superuser permissions to your phone
2. Unrevoked Forever - Adds S-OFF functionality, which means that the HBOOT startup will no longer check for updates that are signed with HTC's super secret signature... Meaning you can flash anything to the phone.
3. Flash Original Stock Recovery - Removes the Clockwork Mod recovery console. Since you have S-OFF, you can return CWM to the phone whenever you damn well please. The original stock recovery is necessary for the OTA to commence, because it is developed to rely on the stock recovery console.
4. Wait for OTA
5. Upon receiving OTA, flash Clockwork Mod to the phone via HBOOT (using a PB31IMG.zip containing it)
6. Flash the root payload via Clockword Mod recovery console.
7. Go to bed and make love to your wife after beating on your chest in victory like tarzan.
8. Reboot phone, bask in Official Froyo coupled with Superuser permissions.
9. Download the busybox installer from the market and install busybox to the system.
10. Make love to your wife again.
UPDATED: with slightly better instructions
Note: If u are s-off and on a custom rom, or have already s-off and customized your current rom you can start at step 3. make sure u have s-off by checking hboot. i put this in because many people asked me what to do if they ddnt start in a stock state.
This process is for people with a fully stock phone who want to apply the stock 2.2 update and maintain root.
I just went through this process.
(sd card must be formatted to fat32. without that most of this will fail.)
Step 1: do this -> http://unrevoked.com/recovery/
(this will root your phone and flash clockworkmod recovery.)
Step 2: do this -> http://unrevoked.com/forever/
(this will use clockworkmod recovery to permanently unlock the nand, also known as s-off.)
-- To backup apps that you want after the phone is fully updated at this point download titanium backup and backup whatever apps u need. make sure u take the backup folder from the sd card and store it on ur pc for later use.
Note: Titanium is probably going to tell u that it couldnt get root. that is because busybox is missing. hit the problems button on titanium and upgrade busybox. this will upgrade busybox if ur using an older version, or download the right version if u dont have one. this should take care of all busybox needs.
Step 3: do this -> http://forum.xda-developers.com/showthread.php?t=756850
(put into sd card and hboot apply)
(this will restore the recovery back to stock as it is needed for the RUU)
now u have an s-off phone with everything else stock.
Step 4: now either get the RUU -> http://forum.xda-developers.com/showthread.php?t=765596
or wait for OTA
(install htc sync to be able to run this. the RUU will load the stock 2.2 rom 2.15 radio that is needed. everything will be wiped, but that is a good thing imo.)
once u have updated ur phone fullly
Step 5: get recovery here http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
put in sd card and hboot apply
(this will load clockworkmod recovery on your phone so that u can apply updates.)
Step 6: put in sd card -> http://forum.xda-developers.com/attachment.php?attachmentid=388592&d=1282834695
and
http://bit.ly/su234ef
and use recovery to install both those zips.
(clockworkmod recovery allows u to apply .zip files, use that option to do this.)
(this will re-root the newly updated phone and install the superuser.apk.)
congratulations now u have an OTA/RUU applied phone with root.
-- If you had titanium backups you want to restore, paste the folder u saved on the desktop back here, re-install titanium from the market and restore apps. It is recommended to redownload the app from the market and just restore the data for the app if possible.
Note: Titanium is probably going to tell u that it couldnt get root. that is because busybox is missing. hit the problems button on titanium and upgrade busybox. this will upgrade busybox if ur using an older version, or download the right version if u dont have one. this should take care of all busybox needs.
notes:
* to enter hboot turn off phone then hold vol down and power till hboot appears.
* to enter recovery, enter hboot and select recovery.
* to check if nand is unlocked, hboot must read S-OFF
* you only need stock recovery to load the RUU, so if you have flashed a different rom, simply revert to the stock recovery and apply the RUU
* all links are property of their original creators, thanks to all of them.
EDIT: and yes please make love multiple times.
Wow... Thanks... This should definitely be stickied as a guide!
Sent from my HTC Incredible
No prob, if you need any help when you are getting to the nitty gritty pm me and I'll give you a phone number to call me at, I love doing this stuff.
Thanks... Will probably wait til the phone starts nagging me to update (from other phones I have seen its pretty persistent). This way in case anything new pops up I can add it to the process.
Also its 2 AM in New York right now, I have never rooted, let alone do everything to get ready for the OTA (definitely waiting for the push... Not applying it manually).... I'd probably frak it up at this hour!
Sent from my HTC Incredible
Thanks rdmerck and k.electron...very helpful and exactly what I've been looking for. After waiting a while, I finally decided to root tonight prior to the impending OTA update.
One cautious newbie question for step 3 (Flashing The Original Stock Recovery). Once in hboot (I entered this by holding down the volume down while powering up, right?), how do you know it will be running the PB31IMG.zip file (Stock Rom)? I didn't see it listed anywhere on the screen and it only offers the option of running recovery or not. I want to make sure that it's running off the correct .zip file. It lists:
INCREDIBLE XC SHIP S-OFF
HBOOT-0.77.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06
Mar 23 2010,19:26:22
HBOOT
Parsing...[SD ZIP]
[1] RECOVERY
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Just wanted to be sure before running the update. I assume you can delete the unrevoked-forever.zip once it's run, but can you delete the "update.zip" that appeared on the sdcard after running unrevoked?
Thanks in advance for any and all help!
chaint said:
Thanks rdmerck and k.electron...very helpful and exactly what I've been looking for. After waiting a while, I finally decided to root tonight prior to the impending OTA update.
One cautious newbie question for step 3 (Flashing The Original Stock Recovery). Once in hboot (I entered this by holding down the volume down while powering up, right?), how do you know it will be running the PB31IMG.zip file (Stock Rom)? I didn't see it listed anywhere on the screen and it only offers the option of running recovery or not. I want to make sure that it's running off the correct .zip file. It lists:
INCREDIBLE XC SHIP S-OFF
HBOOT-0.77.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06
Mar 23 2010,19:26:22
HBOOT
Parsing...[SD ZIP]
[1] RECOVERY
Do you want to start update?
Yes
No
Just wanted to be sure before running the update. I assume you can delete the unrevoked-forever.zip once it's run, but can you delete the "update.zip" that appeared on the sdcard after running unrevoked?
Thanks in advance for any and all help!
Click to expand...
Click to collapse
I just went through doing the same thing. I deleted the update.zip from my SD card just to make sure there was no confusion. Then I clicked yes when it asked to apply the update. Also, after this, if you boot into recovery ( its a couple options down in hboot, move with your volume button) you should get a red caution sign after a few seconds. Apparently this means you are back to stock. All credit goes to someone who helped me in another thread but I cannot find it right now.
chaint said:
Thanks rdmerck and k.electron...very helpful and exactly what I've been looking for. After waiting a while, I finally decided to root tonight prior to the impending OTA update.
One cautious newbie question for step 3 (Flashing The Original Stock Recovery). Once in hboot (I entered this by holding down the volume down while powering up, right?), how do you know it will be running the PB31IMG.zip file (Stock Rom)? I didn't see it listed anywhere on the screen and it only offers the option of running recovery or not. I want to make sure that it's running off the correct .zip file. It lists:
INCREDIBLE XC SHIP S-OFF
HBOOT-0.77.0000
MICROP-0417
TOUCH PANEL-ATMEL224_16ab
RADIO-1.00.03.04.06
Mar 23 2010,19:26:22
HBOOT
Parsing...[SD ZIP]
[1] RECOVERY
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
Just wanted to be sure before running the update. I assume you can delete the unrevoked-forever.zip once it's run, but can you delete the "update.zip" that appeared on the sdcard after running unrevoked?
Thanks in advance for any and all help!
Click to expand...
Click to collapse
Yes, where it says
Parsing...[SD ZIP]
[1] RECOVERY
It is informing you that the only thing contained in the PB31IMG.zip file is a recovery image to be flashed. In this case, it is the stock Android 2e recovery that you will need. Press the volume up key to flash it, and then you can boot into the recovery console to verify that it works.
When you see a black screen, with a phone and a triangle with an exclamation point, you are in Android 2e recovery (your goal all along), press power+plus volume up, and you will see a meaningless error message and then a menu will appear at the top of the screen.
The first option will be to reboot the system, make sure it is selected and press the power button again. When you do, it will bring you back into your operating system.
Wait. I went out of order and started with the love making. That's as far as I got....
Sent from my ADR6300 using XDA App
amdpimp said:
Wait. I went out of order and started with the love making. That's as far as I got....
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
what? nooooo.... rooted 2.2 is the main thing your wife is interested in.. and your incredible too..
amdpimp said:
Wait. I went out of order and started with the love making. That's as far as I got....
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I most certainly hope you bricked lol
Sent from my ADR6300 using XDA App
When I do this method (and waiting for the OTA) do I need to back up anything? Or does it leave my apps and data untouched?
Sent from my HTC Incredible
Format FAT32 required on storage card
I'd like to point out that step 3 REQUIRES your storage card to be formatted FAT32. Clockwork will not update to "[Recovery] Stock 2.1 Recovery Image for DI" without you having first formatted your storage card to FAT32. This may be common sense but for a first rooter like myself, I figured it out by trial and error.
k.electron said:
I just went through this process.
first do this -> http://unrevoked.com/recovery/
then do this -> http://unrevoked.com/forever/
then do this -> http://forum.xda-developers.com/showthread.php?t=756850
(put into sd card and hboot apply)
now u have an s-off phone with everything else stock.
now either get the RUU -> http://forum.xda-developers.com/showthread.php?t=765596
or wait for OTA
once u have updated ur phone fullly
get recovery here http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
put in sd card and hboot apply
put in sd card -> http://forum.xda-developers.com/attachment.php?attachmentid=388592&d=1282834695
and
http://bit.ly/su234ef
and use recovery to install both those zips.
congratulations now u have an OTA/RUU applied phone with root.
EDIT: and yes please make love multiple times.
Click to expand...
Click to collapse
NYC Coyote said:
When I do this method (and waiting for the OTA) do I need to back up anything? Or does it leave my apps and data untouched?
Sent from my HTC Incredible
Click to expand...
Click to collapse
It will leave all data and apps untouched but get in the habit of backups ALWAYS. You never know when playing around like this. You may do one thing wrong and will be wishing you had taken 5 minutes to do a backup.
anothen said:
I'd like to point out that step 3 REQUIRES your storage card to be formatted FAT32. Clockwork will not update to "[Recovery] Stock 2.1 Recovery Image for DI" without you having first formatted your storage card to FAT32. This may be common sense but for a first rooter like myself, I figured it out by trial and error.
Click to expand...
Click to collapse
thank you and yes fat32 for all things sd card related.
anothen said:
It will leave all data and apps untouched but get in the habit of backups ALWAYS. You never know when playing around like this. You may do one thing wrong and will be wishing you had taken 5 minutes to do a backup.
Click to expand...
Click to collapse
frankly its much better to just use the ruu and have it update everything and wipe the phone. 2.1->2.2 app and data moving can sometimes leave behind some stale stuff that u dont want.
before i did the RUU i installed titanium and saved any apps that had states that i needed, like games. then after i installed the RUU and reinstalled the apps from the market, i just titanium restored the data for the app so it still had the latest app, but my save games were back in. that will give u a good factory like device but with whatever data you find necessary.
i also mounted system in recovery after the whole process and removed things like cityid, vzwnav, stocks etc.
k.electron said:
frankly its much better to just use the ruu and have it update everything and wipe the phone. 2.1->2.2 app and data moving can sometimes leave behind some stale stuff that u dont want.
Click to expand...
Click to collapse
If you ran the RUU straight up were you rooted before hand with S-off? Then you ran the full RUU and retained root?
I currently have root, stock radio and no s-off yet. and want to update and retain root.
Thanks.
-Lil'
rdmerck said:
Yes, where it says
Parsing...[SD ZIP]
[1] RECOVERY
It is informing you that the only thing contained in the PB31IMG.zip file is a recovery image to be flashed. In this case, it is the stock Android 2e recovery that you will need. Press the volume up key to flash it, and then you can boot into the recovery console to verify that it works.
When you see a black screen, with a phone and a triangle with an exclamation point, you are in Android 2e recovery (your goal all along), press power+plus volume up, and you will see a meaningless error message and then a menu will appear at the top of the screen.
The first option will be to reboot the system, make sure it is selected and press the power button again. When you do, it will bring you back into your operating system.
Click to expand...
Click to collapse
Thanks rdmerck. I didn't see the phone and triangle when flashing, however. When I originally pressed volume up to flash, it took just a few seconds, then prompted me to reboot which I did, then it loaded the OS as normal. Not sure if I needed to do something else, or if there's a way to check to see if it worked (I still see SU Permissions in my apps). Should I just try again? Any thoughts. Thanks, and sorry for these newbie questions!
Help a noob out
OK can someone help out ANOTHER noob here?
I have been following this thread among 30 others since yesterday and there seems to be a ton of different ways to go about getting the same results, which for me is the new leaked build with root. I am hoping someone can set me straight as I have info overload right now.
I am currently running stock 2.1 and used unrevoked to root.
I have not done anything else at this point. No radio update, no s-off, no roms.. nothing. I do not mind wiping the phone and reinstalling all my apps and probably would want to start fresh with the new install.
Someone made a reference a few post up about just running the RUU. Can I do that without losing root? Do I need to update my radio first? Should I installed 'forever' s-off before hand?
Any help would be greatly appreciated. I basically want to install what seems to be the official OTA/RUU and retain my root access so I can run wireless tether and remove bloat I dont want. Once some of the roms get cooked with the new build I can full around with them. Just need some help getting over the hump right now, so I can be running some Froyo goodness.
Thanks so much for any help you can lend.
-Lil
Hi all.
I'll start by saying I have gotten in way over my head. I rooted my Evo with unrEVOked's one-click method, and then began to experience some problems with my 3g. Thinking I had somehow botched the rooting process, I tried to unroot using the two-step method I also found on xda (cannot post link.. further proof I am a noob ). More problems sprang up, one thing led to another, various fixes were tried (HUGE thanks to everyone in the IRC channel last night that tried to help my sorry ass..) but to no avail.
Here is where my phone is at now: booting using vol down+power shows me S-ON. Trying to flash mtd-eng.zip results in an error, so I am seemingly stuck with S-ON. Normally I would be happy about this (that's one step closer to unrooted, right?) but I notice I still have Superuser in my apps. My 3g is working again for whatever reason (no complaints here! maybe it was a Sprint-side problem in my area.. what timing!) but I'm confused as to whether my phone is rooted or not.
Ideally, I would like to go back to unrooted, since I have made it abundantly clear to myself that I am not yet prepared to embark in rooting. If anyone could guide me in the right direction, I would be very thankful.
You no longer have root access. Nothing you do at this point will allow you to run a .img on your own.
Your best bet would be to try and run one of the RUU programs to get it all back to stock.
I don't know if the Superuser application will be removed by this but you can try it:
Go to Settings>SD & Phone Storage>Factory Data Reset
Your phone should reboot and may have erased the Superuser app.
Jim M said:
You no longer have root access. Nothing you do at this point will allow you to run a .img on your own.
Your best bet would be to try and run one of the RUU programs to get it all back to stock.
I don't know if the Superuser application will be removed by this but you can try it:
Go to Settings>SD & Phone Storage>Factory Data Reset
Your phone should reboot and may have erased the Superuser app.
Click to expand...
Click to collapse
I did this, and my phone is now in RA-evo-v1.8.0 (it rebooted into recovery). Should I reboot the system now? I find it strange that it took me here in the first place.
The current PC36IMG that is flashed to the Evo is one with Amon Ra built into it.
The only RUU program that I am allowed to run (from the list that was given out in one of the unrooting evo threads) gives me the 170 error before anything happens.
You don't have root access, but your phone still has a custom recovery (Amon_RA) right now. No way to get rid of the custom recovery now except through an official update that replaces the recovery file.
Like I said you can try to run one of the RUU Official updates found in the Developer forum.
Don't know your location, but if you post it, someone close to you might try to help you out in person.
Jim M said:
You don't have root access, but your phone still has a custom recovery (Amon_RA) right now. No way to get rid of the custom recovery now except through an official update that replaces the recovery file.
Like I said you can try to run one of the RUU Official updates found in the Developer forum.
Don't know your location, but if you post it, someone close to you might try to help you out in person.
Click to expand...
Click to collapse
With a little digging and poking and reading, I found the proper RUU, ran it, and I believe I am now back to fully unrooted. Thank you very much for your help!
I was trying to install a new rom on my Desire Z, following the directions here, but something went wrong somewhere and now I can't mount /data. I don't want to go any further in the rom installation process, as I'm afraid to brick my phone. The same thing happened to me while upgrading my Windows 6.5 phone (unexpected problem during rom install) and I ended up with a brick (corrupt bootloader).
I have found several threads here discussing the same problem. However, all of them use highly technical language and seem to be advice from experts to other experts. There are a lot of terms I don't understand or only understand partially, like nandroid, parted, hboot, and so on. Everyone assumes too much. Can anyone explain the procedure in terms a novice can understand?
gromky said:
I was trying to install a new rom on my Desire Z, following the directions here, but something went wrong somewhere and now I can't mount /data. I don't want to go any further in the rom installation process, as I'm afraid to brick my phone. The same thing happened to me while upgrading my Windows 6.5 phone (unexpected problem during rom install) and I ended up with a brick (corrupt bootloader).
I have found several threads here discussing the same problem. However, all of them use highly technical language and seem to be advice from experts to other experts. There are a lot of terms I don't understand or only understand partially, like nandroid, parted, hboot, and so on. Everyone assumes too much. Can anyone explain the procedure in terms a novice can understand?
Click to expand...
Click to collapse
"Mount" data to flash a rom? You sure? Looking at the link you provided just says place on sd, wipe, flash. Where exactly are you stuck or am i just missing the obvious.
The /data corruption occurred halfway through the upgrade process. I'm not sure what to do, so I stopped and asked for advice. I kept going the last time I had a problem, and got a bricked phone for my trouble.
The only "data" I see in that guide (Same one I used in fact), is the comment bout doing a "Factory Reset/Wipe Data" which is what it says, says nothing about /data/ partition, just to do a full wipe.
Naturally you do this from recovery, not from within an app or while the phone is still booted into normal usage.
So, wiping the phone will fix everything? And then install cyanogen? Sorry, just want to be totally completely sure.
Aye, indeeed, as KB said, full wipe, then flash new rom.
OK, thanks! I was just reeeealy nervous about the "wipe the phone" part. My phone still sort of works now, most programs not available, but Google Maps and the telephone still work...the most important parts of the phone as I travel a lot.
gromky said:
OK, thanks! I was just reeeealy nervous about the "wipe the phone" part. My phone still sort of works now, most programs not available, but Google Maps and the telephone still work...the most important parts of the phone as I travel a lot.
Click to expand...
Click to collapse
Factory Reset/Wipe will only clear the internal partitions ( /system /data /cache ) , and additionally if you choose Dalvik Cache, then that as well is usually good to do with a brand new rom.
It will not wipe your radio, hboot, recovery, etc, just the system-related areas for roms.
Generally speaking:
Factory Reset + Wipe Cache/Dalvik Cache
Flash CyanogenMod
Flash the Google Apps Zip specific to that CM version (as CM doesn't come with Google Apps by default)
Reboot
Just remember that doing a backup before doing anything to your phone like above is available, as a factory reset and such will wipe contacts and settings and so forth unless you got a google account setup to restore them (or using something like Titanium Backup on an already rooted phone).
OK, I was following the rooting guide, as that must be done before installing cyanogen. I performed all the steps to "reboot". Md5 #2 & md5 #3 matched. Upon rebooting, I can't use su from the terminal (permission denied). I also tried "cd /sdcard && ./su" and got the same thing. Does this mean the rooting didn't work? Or can I proceed with wiping the device regardless? After I wipe the device I won't be able to perform the rooting steps again...and will likely have a brick...just totally paranoid here.
gromky said:
OK, I was following the rooting guide, as that must be done before installing cyanogen. I performed all the steps to "reboot". Md5 #2 & md5 #3 matched. Upon rebooting, I can't use su from the terminal (permission denied). I also tried "cd /sdcard && ./su" and got the same thing. Does this mean the rooting didn't work? Or can I proceed with wiping the device regardless?
Click to expand...
Click to collapse
I followed that one as well. And I assume you rebooted after that point.
Did you continue forth and factory-reset/wipe and then install CM7 over your stock install?
Basically the downgrading/etc makes the phone exploitable, and then the rooting portion puts you back up to a engineering hboot and such that is unlocked with S-OFF, from there you either flash a pre-rooted ROM (i.e.: CM7 etc), or you root an existing stock (which would have gotten wiped from the hboot replacement).
If you already flashed CM and can't do su via adb then it's possible that under "Security" or "Development" in your phones system memory that su is restricted to "app only" and you may need to change that to "app and adb".
You shouldn't be running su from /sdcard (since that's not a linux style partition, and /sdcard is a no exec area). The su binary should already be installed to system in CM.
Clarification If you did not yet reboot (i.e.: Step #7 and onward), and then wipe/flash cyanogenmod (or another pre-rooted custom rom), then proceed with the steps, otherwise you're just working with a half-processed phone and naturally nothing would work in that state.
kbeezie said:
I followed that one as well. And I assume you rebooted after that point.
Click to expand...
Click to collapse
Yes.
Did you continue forth and factory-reset/wipe and then install CM7 over your stock install?
Click to expand...
Click to collapse
You mean hold "down" and boot into recovery, and immediately do these steps? No, I did not. I let the phone boot as normal, to try to run su to verify if the rooting process worked or not.
I suppose my question should be: how can I verify that the rooting process worked, and I'm ready to wipe? The su on /sdcard was pushed there by adb and used during the procedure. From the guide:
adb push su /sdcard/
adb push Superuser.apk /sdcard/
Basically the downgrading/etc makes the phone exploitable, and then the rooting portion puts you back up to a engineering hboot and such that is unlocked with S-OFF, from there you either flash a pre-rooted ROM (i.e.: CM7 etc), or you root an existing stock (which would have gotten wiped from the hboot replacement).
Click to expand...
Click to collapse
I didn't downgrade, I still have my stock rom (phone bought from Hong Kong so it's one of the Asia roms) which temprooted just fine with visionary.
gromky said:
Yes.
You mean hold "down" and boot into recovery, and immediately do these steps? No, I did not. I let the phone boot as normal, to try to run su to verify if the rooting process worked or not.
I suppose my question should be: how can I verify that the rooting process worked, and I'm ready to wipe? The su on /sdcard was pushed there by adb and used during the procedure. From the guide:
adb push su /sdcard/
adb push Superuser.apk /sdcard/
I didn't downgrade, I still have my stock rom (phone bought from Hong Kong so it's one of the Asia roms) which temprooted just fine with visionary.
Click to expand...
Click to collapse
Don't use Visionary unless for some strange reason your phone came with Froyo (2.2) on it (it's an outdated method, and has a high brick rate). Given that you may have an asian rom etc, I would just go ahead and do a factory reset /wipe via recovery, and flash CM7 or a pre-rooted stock rom found here on the XDA forum for the best result.
I think even one of the AOKP or Adromudus comes with Pinyin input support already if you need it.
It did have Froyo. I have uninstalled visionary per instructions before performing all these steps. But since I only get one shot at rooting correctly, I want to make absolutely positively sure the process worked before I do something irrevocable like wiping the entire phone, only to discover I can't install a new rom because the phone isn't rooted.
I use third-party programs (GO keyboard) for all of my Chinese needs, and they've worked fine so far.
gromky said:
It did have Froyo. I have uninstalled visionary per instructions before performing all these steps. But since I only get one shot at rooting correctly, I want to make absolutely positively sure the process worked before I do something irrevocable like wiping the entire phone, only to discover I can't install a new rom because the phone isn't rooted.
I use third-party programs (GO keyboard) for all of my Chinese needs, and they've worked fine so far.
Click to expand...
Click to collapse
Rooting is at the rom/kernel level. But in order to flash a new custom kernel would need an unlocked bootloader which you already did with S-OFF.
So you would either flash a pre rooted rom like almost everything available via the developer section here (via recovery not hboot) or a stock rom then root that.
If you do everything via recovery you are less likely to accidentally lock/unroot the phone since recovery normally deals with the rom/kernel /cache and not hboot.
Sent from my T-Mobile G2
It worked - thanks! I was so concerned about bricking the thing. The whole process was easy...now that I've done it. Cyanogen came up in Chinese...couldn't figure out how to change it to English for a while. I suppose there's some setting in my phone that tells it to default to Chinese. It also appears to be locking up frequently on my phone - but at least I got the software on there, and now I can play with other mods. Thanks again!
gromky said:
It worked - thanks! I was so concerned about bricking the thing. The whole process was easy...now that I've done it. Cyanogen came up in Chinese...couldn't figure out how to change it to English for a while. I suppose there's some setting in my phone that tells it to default to Chinese. It also appears to be locking up frequently on my phone - but at least I got the software on there, and now I can play with other mods. Thanks again!
Click to expand...
Click to collapse
If I had to make a guess, I would probably say you flashed Cyanogenmod onto the phone WITHOUT first doing a factory-reset/wipe, in which case you probably broke it (hence the language and freezing) by merging cyanogenmod on top of the pre-existing rom.
No, I definitely wiped the phone first. I got a few lockups in cyanogen so I went to install another rom. Now I'm getting "E:error in /cache/recovery/log" and "E:can't open /cache/recovery/log". When I install a new rom, it won't take and boots into cyanogen. It was in a reboot loop for a while but now it has booted into cyanogen again. Sigh. This is what I was afraid of.
Boot into boot and write down everything on that screen (power+volume down) just to check all is well, what is your recovery?
Search out two things (just use search function in g2 xda threads)
1 superwipe+ext4.zip
2 elitemod cm7
Boot into recovery and flash the super wipe like you did the from
Now flash elitemod
Is all well at this point?
Sent from my GT-I9100 using xda premium
Actually the phone seems to be working with cyanogen now. I suspect the internal memory is corrupt somehow, and that's a problem that can't be fixed. I'm going to stop messing with it before I brick it. If any more problems I'll revive the thread. Thanks so much to everyone who helped. I really can't afford a new phone right now and cyanogen seems to have fixed the problems I was having with the stock rom.
gromky said:
Actually the phone seems to be working with cyanogen now. I suspect the internal memory is corrupt somehow, and that's a problem that can't be fixed. I'm going to stop messing with it before I brick it. If any more problems I'll revive the thread. Thanks so much to everyone who helped. I really can't afford a new phone right now and cyanogen seems to have fixed the problems I was having with the stock rom.
Click to expand...
Click to collapse
If the emmc is faulty then it's going to eventually brick itself, and should probably be sent in for warranty if available.