EVERYTHING EVO - Latest Rooting | NAND | Flashing Roms | Wipe

[fenixjn]

Originally Posted by FastRX8

Dude that hilarious, I just signed on to post this exact same thing, although I think you worded it better.
I talked to Meatgel on the phone and walked her through the process.
Had the same issue. I had her type in the .bat file and it worked. I'm going to take your explanation and tweak it a little to add to the tutorial.

Yeah, I forgot to write that after the CMD you need to type anything that follows in the new command prompt window.

Also, I have found that sometimes windows will deny access to some applications when the calling program is running as administrator, I guess this is one of those cases.

[FastRX8]

Originally Posted by fenixjn

Yeah, I forgot to write that after the CMD you need to type anything that follows in the new command prompt window.

Also, I have found that sometimes windows will deny access to some applications when the calling program is running as administrator, I guess this is one of those cases.

In my tutorial, I'm just going to have people paste the following command into the run window.
"c:\evo-recovery\recovery-windows.bat"
Assuming they followed my directions and extracted to "C" this command will do the trick w/o trying to explain how to use dos.

[iknowsquat]

Originally Posted by FastRX8

@winmonewbie - And yes, I'm going to make a video for this.

lol of COURSE you are, excellent.

btw-dunno if it matters or not but when I went to OMJ 1.3 I used the Auto Recovery but did NOT use the "apply sdcard:update.zip" option, I used "install zip from sdcard"
I noticed you and other talking about that amidst your issues and just thought I'd throw that out there.

btw#2-OMJ posted the updated tethering app in his thread, WPA2 security enabled, works great.

btw#3-I killed my boot up sound again

[FastRX8]

Originally Posted by winmonewbie

lol of COURSE you are, excellent.

btw-dunno if it matters or not but when I went to OMJ 1.3 I used the Auto Recovery but did NOT use the "apply sdcard:update.zip" option, I used "install zip from sdcard"
I noticed you and other talking about that amidst your issues and just thought I'd throw that out there.

btw#2-OMJ posted the updated tethering app in his thread, WPA2 security enabled, works great.

btw#3-I killed my boot up sound again

The apply sdcard:update.zip is happening because the SU icon issue. You didn't have a problem because you had the icon and went from a rooted custom--->rooted custom. Rom manager works excellent in that situation.

I'm too lazy to change all the pc's in my house to WPA2 so I never use it. However, I'll get the app anyways because I'm sure there are other fixes too.

I spent all day flashing and trouble shooting why the rom manager wasn't working, I haven't had a chance to look in to the bootup sound. I may hit you up for help on that.

[amw1972]

@FastRX8:

Great guide...I now have a rooted EVO running OMJ's latest. Couple of comments...
I wasn't able to get auto recovery working directly from boot. I was stuck on the red triangle screen...til I realize that I should go back and run the recovery-windows.bat.
When I ran the .bat file as admin on Win7...it flashed the dos screen...then it went away. I just double clicked it like most other .exe. Not sure if this was addressed...but no harm no foul.

Once again...thanx for the instructions...very easy to follow...and the videos were a great help as well!

[imtjnotu]

after i root and use rom manager i go into bootloader and click recovery i get the /!\ in red and it does nothing...any help?

[ruckstande]

Originally Posted by imtjnotu

after i root and use rom manager i go into bootloader and click recovery i get the /!\ in red and it does nothing...any help?

This is where I'm at. Also, how come I don't have an OTA now? I'm still on .1.

[pastert33]

I'm at the step where I need to locate the bat file but that's the problem...I've tried to run in from Command Prompt and nothing

[iknowsquat]

Originally Posted by amw1972

@FastRX8:

Great guide...I now have a rooted EVO running OMJ's latest. Couple of comments...
I wasn't able to get auto recovery working directly from boot. I was stuck on the red triangle screen...til I realize that I should go back and run the recovery-windows.bat.
When I ran the .bat file as admin on Win7...it flashed the dos screen...then it went away. I just double clicked it like most other .exe. Not sure if this was addressed...but no harm no foul.

Once again...thanx for the instructions...very easy to follow...and the videos were a great help as well!

Yup, see that too. The instructions and video lay it out nicely but maybe a little disclaimer to NOT run as admin would be helpful....

Originally Posted by imtjnotu

after i root and use rom manager i go into bootloader and click recovery i get the /!\ in red and it does nothing...any help?

Originally Posted by ruckstande

This is where I'm at. Also, how come I don't have an OTA now? I'm still on .1.

Originally Posted by pastert33

I'm at the step where I need to locate the bat file but that's the problem...I've tried to run in from Command Prompt and nothing

I'm learning troubleshooting slowly as I did not have any issues (not rubbing it in )
It appears as fast describes below that the issue is with ROM Manager on rooted but Stock ROMs, it's just not playin' nice.
The simplest solution is to forget ROM Manager until your on a custom ROM, just do the manual recovery.

fenixjn and fast had a convo last PM that may help you guys out as well.

Originally Posted by fenixjn

Note for some of the unrevoked user or OTA: I had both, I removed unrevoked but could not get clockwork to do anything on recovery or run the .bat file on windows (it would flash and then dissapear running it as administrator).

Go to Run (or Win+R)
type cmd and press ENTER
type cd \evo-recovery and press ENTER
type recovery-windows and press ENTER

From this point, recovery should work. Note that you dont need admin access to make it happen but it is recommended (the method above does not use admin).

I did this on my Win7 x64 system with UAC enabled (so no, I'm not running admin by default)

Originally Posted by FastRX8

Actually, turns out, you're not doing anything wrong. I tried this countless times. I had meatgel try it, and you're reporting the exact same issue.

Here's what's happening...

Problem:
When you rooted your phone, you did not get a Superuser Permission Icon.
Why, I don't know. Once the PC36IMG.zip file ran and you rebooted, you should see the SU Icon in the apps. Your phone is rooted, so it should be there, but it's not. That missing icon causes the error.
Rom manager works fine when you are running it from a custom rom. That's why so many people are reporting success w/ Rom Manager. They already went through the process of rooting and flashing before. They have a rooted rom w/ the SU Icon. Since they just want to flash other roms or radios, they have no need to downgrade or go to stock. They use Rom Manager and it works.
You have the stock rom and I don't remember if you said or not, but I'm guessing that you did the OTA. Meatgel had the stock rom too. She did the OTA and when she rooted, her phone was rooted but she was missing the SU Icon. She downloaded Rom Manager and it failed to install a new rom.


Solution:
Install your 1st custom rom using the manual method. When you get to step #6, if you have trouble double clicking the .bat file, just go to a cmd prompt and type it in.

Originally Posted by FastRX8

In my tutorial, I'm just going to have people paste the following command into the run window.
"c:\evo-recovery\recovery-windows.bat"
Assuming they followed my directions and extracted to "C" this command will do the trick w/o trying to explain how to use dos.

[pastert33]

Originally Posted by winmonewbie

Yup, see that too. The instructions and video lay it out nicely but maybe a little disclaimer to NOT run as admin would be helpful....







I'm learning troubleshooting slowly as I did not have any issues (not rubbing it in )
It appears as fast describes below that the issue is with ROM Manager on rooted but Stock ROMs, it's just not playin' nice.
The simplest solution is to forget ROM Manager until your on a custom ROM, just do the manual recovery.

fenixjn and fast had a convo last PM that may help you guys out as well.

Thank you for pointing this out however, I've read over this and it's not helping...
I've tried to do it the manual way and I can't get the file to run on the comp. Where do I find the evo-recovery.zip file?