[How-To]Windows -- root your HTC Evo and install Clockwork recovery

Status
Not open for further replies.
boom shocka locka. UTnick do this and it fixes the issue.

C:\Android_DEV\sdk\tools>adb shell
# rm /data/flash_image
rm /data/flash_image
# cat /sdcard/flash_image > /data/flash_image
cat /sdcard/flash_image > /data/flash_image
# chmod 755 /data/flash_image
chmod 755 /data/flash_image
# /data/flash_image misc /sdcard/mtd-eng.img
/data/flash_image misc /sdcard/mtd-eng.img
# exit
exit

and guess what. the pc36img.zip now works. just so you know the work around.

@GBHIL - you may want to make a reference to this if it isn't somewhere. this is needed if you have done the process that I posted about in my Thread.
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17309-bricked-my-evo-but-there-away-un-brick.html
 
Is the pound sign something you typed in or to just indicate you're under su?

I have deleted the image and mtd off the sd card through root explorer already. I just am confused why using
Code:
adb push
wouldn't work either.
 
@UTnick - when you are in command window, try to do adb devices

that will let you know if your computer is talking to your phone. from there do adb ls /sdcard does that bring back anything? if it is nothing then your not talking to your card for sure. What ROM are you running? RvU? or some other one. There are some reports that some of the other ROMS are doing some weird things like instantly connecting to Disk Drive, and even if they set it to something else. what you can do is do this through terminal console. it is a pain in the arse, because you are typing all of that out on you phone. goto this thread and try doing that step like GBHIL says to but using the info from HERE It should work. Basically this right here.


Open a terminal emulator (I used ConnectBot) change ssh to local, give it a name.
su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img

if you are trying to find the > symbol
-Hit "12#" key on the Keyboard.
-then the "1/2" key (it'll turn into 2/2)
-the ">" key is on the second row, 5th key, directly below the "=" and above the first blank in the 3rd row.

That should get you done. It will be a pain in the arse like I said, but should work. Have your phone unplugged from the computer while this is going on so the phone has access to your SD Card. Hope this helps.
 
Is the pound sign something you typed in or to just indicate you're under su?

It means your under su (superuser), you don't type it.

Question for someone who understands the RvU1.3.2 Rom:

When I apply the RvU1.3.2 Rom, AmazonMP3, FriendStream Widget, Peep and Widget, Footprints and Widget, Sprint Nascar, Sprint NFL, Sprint TV and Widget and Sprint Promo all disappear from the phone.

If I reapply the ENG-PC36Img.zip they apps reappear, but I'm using an older ROM. How do I go about getting those apps while using 1.3.2? The thread about that ROM states that they are in there, but I don't show them installed on my phone.
 
How does one go about reinstalling the Sprint Apps that Saepak linked above? Do I copy to my SD card and use recovery or do I push them to my phone via ADB? If I push, what directory would I put them in?
 
@ amc. Sorry doing this from my EVO. Without tapatalk. Okay in the stickys there is a post about removing bloatware. Go there that is the fastest way to get you the info.
 
How does one go about reinstalling the Sprint Apps that Saepak linked above? Do I copy to my SD card and use recovery or do I push them to my phone via ADB? If I push, what directory would I put them in?

are you talking about such apps like sprint NFL live? if so, i believe they're saved as apk files, which means you can put any folder you like, then use Astro File Manager or other file manager apps to install them.
 
Anybody notice that the links for the requisite files for download haven't been working all day? Anybody know where to get them outside of geekforme?
 
boom shocka locka. UTnick do this and it fixes the issue.

C:\Android_DEV\sdk\tools>adb shell
# rm /data/flash_image
rm /data/flash_image
# cat /sdcard/flash_image > /data/flash_image
cat /sdcard/flash_image > /data/flash_image
# chmod 755 /data/flash_image
chmod 755 /data/flash_image
# /data/flash_image misc /sdcard/mtd-eng.img
/data/flash_image misc /sdcard/mtd-eng.img
# exit
exit

and guess what. the pc36img.zip now works. just so you know the work around.

@GBHIL - you may want to make a reference to this if it isn't somewhere. this is needed if you have done the process that I posted about in my Thread.
http://forum.androidcentral.com/htc-evo-4g-roms-hacks/17309-bricked-my-evo-but-there-away-un-brick.html

Done. Thanks for the heads up again!

Just a bug I noticed - it seems my Gmail doesn't push anymore with the RvU 1.3.2 ROM either.

Not seen that issue with this ROM yet. Try clearing Gmail and Gmail storage cache from applications manager in settings.

Anybody notice that the links for the requisite files for download haven't been working all day? Anybody know where to get them outside of geekforme?

If anybody can upload them for a mirror, feel free. Let me know via PM and I'll update first post. If nothing else, I can upload them when I change computers later tonight after the podcast.
 
Not seen that issue with this ROM yet. Try clearing Gmail and Gmail storage cache from applications manager in settings.

I changed ROMs to the stock rooted rom, and am still having issues. Its just delayed at syncing. I just cleared cache for gmail storage and regular gmail - gonna send some tests and see whats up.

Might stick with this ROM as I've already kinda tweaked everything the way I want but who knows. So many possibilities!
 
boom shocka locka

Hey hey hey, so I disappear for a couple days and people and stealing my catch phrases?!? Lol j/k but I would warn you, be careful with the boom-shock-a-lock-a ..... apparently if its used in a sentence while helping someone it's interpreted as being an @$$ ::shrugs shoulders::
 
haha, i know but Your from New York so you instantly are put on that pedestal, and I'm from Tx so We get crap also. Good to see you back KSmithInNY. And I'm just giving you crap about New York.
 
Hmm, this is odd. After I rebooted the phone and I no longer seem to have root. I can't approve any SU requests. Only Rom Manager as superuser permissions stored and will work, if I try to grant them to cachemate or terminal emulator it freezes and SU request will force close.

I am going to back up my nand and repeat step 4. Any idea what I could have done wrong?

Yikes, now even Rom Manager lacks su permissions..
 
haha, i know but Your from New York so you instantly are put on that pedestal, and I'm from Tx so We get crap also. Good to see you back KSmithInNY. And I'm just giving you crap about New York.

;)

Hmm, this is odd. After I rebooted the phone and I no longer seem to have root. I can't approve any SU requests. Only Rom Manager as superuser permissions stored and will work, if I try to grant them to cachemate or terminal emulator it freezes and SU request will force close.

I am going to back up my nand and repeat step 4. Any idea what I could have done wrong?

Yikes, now even Rom Manager lacks su permissions..

Ok well this could be a fun experiment. I'm an "outside of the box" thinker so feel free to disregard this but...

Check to make sure your phone is still rooted (google search it or search these forums, been posted a million times). Assuming your phone is still rooted, the problem could be with SU. SU is an app just like any other, granted you need root to use SU but you get the point.
- Try installing the unrEVOked root method. This may or may not work BUT if it does it will install a new SU on your phone.
- Now try launching an app that uses root and see if it works. Worst case scenario it doesn't work, you go back to a nand restore which you were already thinking about doing. Best case scenario it does work and you don't need to restore.
 
Thanks, KSmith. That's a good place to start! Nothing wrong with an outside the box solution.

Say it fails to give me root, would it be recommended to restore the factory ROM and then start from Step 1, or should I just go through the root method with RvU 1.3.2 still installed?


Edit: Alright, I ran unrEVOked, which claims I was given root, but SU Permissions still force closes. It was worth a shot!
 
Last edited:
Edit: Alright, I ran unrEVOked, which claims I was given root, but SU Permissions still force closes. It was worth a shot!

are opening the SU that comes with your ROM (blue # sign) or the SU that comes with unrEVOked (looks like a ninja ... awesome)?
 
Status
Not open for further replies.