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

[iknowsquat]

Originally Posted by FastRX8

Full Root Nand Protection video is done and in post #2
Edit - nevermind. Too long. Be right back.

Ok, here it is.
http://www.youtube.com/watch?v=tUXTB0eydwE
Still processing though.

Killer soundtrack Bro

Looks great! Glad to see I'm not the only one with a schizo HTC Sync

[FastRX8]

Originally Posted by winmonewbie

Killer soundtrack Bro

Buckethead FTW I use the same stuff for my Call of Duty XBOX 360 videos.

Originally Posted by winmonewbie

Looks great! Glad to see I'm not the only one with a schizo HTC Sync

Actually the 1st htc sync worked, I didn't know what to do. Totally through me off guard.
I just watched the finished video. Man that was rough editing. I was trying to get it posted quickly. Also, it was my very first time running through this.
When I read the directions on XDA I realized I had to finally figure out what "adb shell" meant.
I always see it written, but had no idea what they were referring too, until I typed "c:\evo-recovery\adb-windows shell" in run command and it all made sense.

[jrmatics]

hey guys and gals. i am quite new to android. been messing around windows mobile for a while, but when i got my evo i started to see ADB and all this other stuff. i havent messed around linux/unix since 2001. i wanted to root my evo then all this adb push and shell stuff got me confused for a second. the guide in this thread is the best i have seen so far but to know all of this adb shell stuff would be great knowledge along side all the wm stuff. if u go here and read carefully it will give u the sdk u need and how to install and use. i read it about 10 times and i am gonna read some more. it was very helpfull. go here http://developer.android.com/sdk/index.html and happy reading

[iknowsquat]

Don't forget to rename PC36IMG post flash. I forgot and went to test my new ability to boot into recovery and bout had a heart attack when the system started reading the zip! I was going to be at work all day without the ability to fix it. Alls well though, after the zip is read there is one more safety where it asks if we want to continue the update, I said hells NO! I rebooted and went and changed the file name.
Just thought I'd remind y'all to spare your blood pressure.

[FastRX8]

Originally Posted by jrmatics

hey guys and gals. i am quite new to android. been messing around windows mobile for a while, but when i got my evo i started to see ADB and all this other stuff. i havent messed around linux/unix since 2001. i wanted to root my evo then all this adb push and shell stuff got me confused for a second. the guide in this thread is the best i have seen so far but to know all of this adb shell stuff would be great knowledge along side all the wm stuff. if u go here and read carefully it will give u the sdk u need and how to install and use. i read it about 10 times and i am gonna read some more. it was very helpfull. go here http://developer.android.com/sdk/index.html and happy reading

The sdk is fine and all, but I didn't include this in the guide because I didn't want to confuse people.
Everything I did was done on a windows machine using the EVO-recovery.zip file and no Android SDK.
I was totally confused when I started trying to figure out Android. None of the original directions about rooting mentioned the SDK, (probably because everyone knew about it in the thread at XDA) so I fumbled around just using the evo-recovery.zip files until I figured out that "adb" could be substituted for "adb-windows" from the zip file I had.
As long as I was in the right folder, the command worked.

So, for people familiar w/ Android, they use

adb shell
adb reboot recovery

For people that don't know what that means, they can use
"c:\evo-recovery\adb-windows reboot recovery" in a run window.

Again, I'm not saying that learning the SDK is bad, only that it is not necessary to do any of these steps. It will help w/ any future hacking/mods individuals might want to do.

[FastRX8]

Originally Posted by winmonewbie

Don't forget to rename PC36IMG post flash. I forgot and went to test my new ability to boot into recovery and bout had a heart attack when the system started reading the zip! I was going to be at work all day without the ability to fix it. Alls well though, after the zip is read there is one more safety where it asks if we want to continue the update, I said hells NO! I rebooted and went and changed the file name.
Just thought I'd remind y'all to spare your blood pressure.

You know after it reads it, it gives you the choice to run it or not.
Volume up=run
Volume down=go back to the bootloader menu
Then you can just select Recovery.

Still a good idea to rename it, but if you forget, it's not the end of the world.

[jrmatics]

Originally Posted by FastRX8

The sdk is fine and all, but I didn't include this in the guide because I didn't want to confuse people.
Everything I did was done on a windows machine using the EVO-recovery.zip file and no Android SDK.
I was totally confused when I started trying to figure out Android. None of the original directions about rooting mentioned the SDK, (probably because everyone knew about it in the thread at XDA) so I fumbled around just using the evo-recovery.zip files until I figured out that "adb" could be substituted for "adb-windows" from the zip file I had.
As long as I was in the right folder, the command worked.

So, for people familiar w/ Android, they use

adb shell
adb reboot recovery

For people that don't know what that means, they can use
"c:\evo-recovery\adb-windows reboot recovery" in a run window.

Again, I'm not saying that learning the SDK is bad, only that it is not necessary to do any of these steps. It will help w/ any future hacking/mods individuals might want to do.

thanx i am still a little confused with this android stuff and ur method completely made it possible for me to root my phone. when i saw the threads on xda i was like.. . then came back to ppcgeeks and saw ur thread and said to my self YES thank u, now i can root my evo. thanx again for the great guide for us noobs to android

[nvrnugh]

Whooo hoooo supern00b nod of thanks! Custom Rom via OMJ and Radio!

Thanks so much for putting this together.

Rooter and flashers unite!

[RichTJ99]

Great guide, I am about to get started. I was curious, if I do this method, can I install various roms once I am done?

[iknowsquat]

Originally Posted by RichTJ99

Great guide, I am about to get started. I was curious, if I do this method, can I install various roms once I am done?

Yup, flash yer brains out!

I posted this in OMJ's thread but figures it was worth a repost here. What is full root.
Originally Posted by frankenstein @ xda:

Originally Posted by frankenstein

There are a couple of key things that it does. First it unlocks the bits of your system that remain locked via nand. basically the system is being told to mount certain directories like /system as read only and not let you remount it as RW. This means your rooted but not completely because you can't re-mount these directories as RW under the android os. Doing this will allow you to remount /system as RW or read/write under the andriod os which will allow you modify things in the /system/app directory letting you clean up bloatware you don't want without having to boot into recovery to do so. (Among other things... that's just a good example of what this gives you.)

The second key thing it does is flash a custom recovery image, basically the same one you load now via toast's recovery-windows.bat process, that you can boot into directly from the HBOOT menu. This means that when you want to flash a new ROM or do a nandroid backup, you don't have to go find a computer with the android sdk and toast's evo-recovery.zip extracted on it to run recovery-windows.bat in order to do so. you can dl a new rom directly to your devices sd card and go to town or boot directly into recovery and run your nandroid backup without needing a computer and the previously mentioned tool set to do so. This was also prevented by the nand locking that this process overcomes.

in short, part 1 gave you root but only about 1/2 of it. You could run apps that require su/root but you can't modify key parts of the system that you should have access to as root. Part 2 completes the root process giving you 100% control of your system without having to jump through hoops to achieve it.