Rooting the HTC Evo 4g – Part 2 (The July 1 2010 OTA Update)
Posted by purehate in Insights at 4:20 PMFirst of I would like to say that none of these hacks and files are my own work. This stuff was done by all the amazing phone developers over at XDA Developers. I am am simply writing a few posts on rooting the HTC Evo since most of the information was all spread out over the forums and I had a hard time gathering it all together in a organized manner.
NOTE: If you have not accepted the OTA Update which was released on July 1 2010 you can go ahead and skip to part 3 of this tutorial.
NOTE: You will have needed to install the adb shell environment in order to complete this tutorial which is outlined in part 1.
You will need to download the files you need for this from here
1. Unzip the hackfiles.zip onto your desktop
2. Mount your Evo as a disk drive and place all the files inside the hackfiles folder onto the root of the sdcard
3. Unmount your phone
4. Change directories into your adb shell which if you followed part 1 is located at C:\android-sdk-windows\tools
(Type adb shell to get a shell on your phone)
adb shell sh /sdcard/part1
5. The script will say to power down, hold your power button and turn off your phone, then turn it back on.
6. When it starts up open your EVO web browser to http://bit.ly/ad0pRn (This will only work if you use the EVO web browser)
7. Wait for the prompt to refresh the browser and then do so when it asks you too.
8. Reboot your phone
adb reboot
9. As soon as the HTC boot logo comes up you need to run a new adb shell. If you get device not found keep trying, you have to do it fairly quickly
adb shell /data/local/part2
10. The finished out put will look something like this:
crw-rw-rw- root root 90, 2 2010-07-05 19:37 mtd1
11. When your phone finished booting, flash the mtd-eng.img to misc:
cat /sdcard/flash_image > /data/local/flash_image chmod 755 /data/local/flash_image /data/local/flash_image misc /sdcard/mtd-eng.img
Once you get all that done reboot the phone and you are ready to go on to the next step which will be in part 3.
*Special thanks to SteelH from the XDA forums for the steps in this tutorial which fixed the OTA update
|
|
|
|




Entries (RSS)
Having trouble with step 4,
I assume you want us to go to command prompt and then go to the TOOLS folder, and type
sh /sdcard/part1
Which doesn’t actually do anything..
[Reply]
purehate Reply:
July 26th, 2010 at 9:53 PM
You are right. I made a typo. It is supposed to be “push”. Thanks for noticing.
[Reply]
I still don’t get it.. push what? where do you write push? you’re assuming and skipping a lot of steps in these instructions.. wouldn’t it be easier to just make a video?
[Reply]
purehate Reply:
July 27th, 2010 at 6:19 AM
Ok I went back to my notes and sh is the correct command. Before doing that you need to type “adb shell” to interact with the phone. I thought that was clear from tutorial number one but if it wasnt I am sorry. I have gone back and made a few edits to try to make it easier to follow.
[Reply]
alex Reply:
July 27th, 2010 at 11:23 AM
Hello Yoav,
Maybe you should search for videos instead of articles if thats what your looking for. A simple thanks to someone spending the time to write an article would be good enough…. In fact why don’t you go make a video if that would help others out. We typically don’t allow links in articles but if you actually make a video we will gladly post a link to it.
Thanks.
alex
[Reply]
when i type push /sdcard/part1 it says permission denied. How do i resolve this issue?
[Reply]
alex Reply:
September 10th, 2010 at 10:54 PM
Hello Duane,
I don’t have an HTC Evo to test with but was curious if you were able to resolve this permissions issue? If so we would love to hear the resolution so others that run into the same issue will find the solution in the comments section of this article.
Thanks.
alex
[Reply]
purehate Reply:
September 10th, 2010 at 11:34 PM
Its not push, its sh which executes the part1 script after you put it on the sdcard. If you are trying to push the part1 file to the sdcard and are still getting a permissions error, then you do not have it mounted properly
[Reply]