Root Universal Eris Root for Dummies!

[kcolemanlisk]

Repeat both part1 and part2, making sure that you reboot the phone normally in between part1 and part2.

The symptoms you describe sound like the flashing of the recovery image is occurring, (as evidenced by the "missing" stock recovery), but not completing correctly.

I suppose it is possible that somehow the recovery image stored in /sdcard/gscript/tools/ got corrupted; this can be checked using the free market application "AFV" (Android File Verifier). Use it to compute the MD5 signature of the recovery image file, and compare that with the value given in Amon_RA's announcement post .

eu1

Okay, so I think that is the problem, my MD5 checksum does not match the MD5 sum posted. Now what? I just downloaded the mirror, is it as easy as connecting my phone and dropping the new file into the /gscript/tools/ and replacing the old recovery image? 'Cause that would be awesome if it were.

 

[erisuser1]

Okay, so I think that is the problem, my MD5 checksum does not match the MD5 sum posted. Now what? I just downloaded the mirror, is it as easy as connecting my phone and dropping the new file into the /gscript/tools/ and replacing the old recovery image? 'Cause that would be awesome if it were.

Yes, that would work.

Or you could just unpack the "gscript.zip" file again.

Something seems rather odd, frankly... if the original "gscript.zip" file got corrupted somehow, it would have failed integrity checks during unpacking. I suppose it is possible that your SD card has some bad blocks that are not yet detected, and you got unlucky enough that the "recovery.img" file got unpacked on top of them, but that seems a little bit unlikely.

In any event, the MD5 signature of the file /sdcard/gscript/tools/recovery.img should be e3932991f097993602af3c7a4b61a4f8

( I just downloaded the link in the OP, unpacked it and checked it - it is correct. The "gscript.zip" file should be 3,915,189 bytes and itself have a MD5 checksum of 92796a8c6e61e8f1ee36e315c0acae7d )

(Note that you can actually install any recovery you want - for instance scary alien's "trackball-free" recovery - by replacing that file before you run the root_part2 script).

eu1

 

[kcolemanlisk]

Well that didn't work at all. I got frustrated, started over. Deleted everything, re-downloaded the gscripts zip file from my phone, went to extract it and it said it was a bad zip. I think I found the problem... Where can I locate a good one?


****UPDATE*** After going back and transferring gscripts.zip over USB I was able to transfer the zip and unpack successfully. Not even messing with the packaged recovery.img I downloaded scary alien's track ball free recovery - replaced the original recovery file with that one and it got me through the wall. Thank you all for your help and patience. I read back a few pages and was able to get some answers too. You all do wonderful work!

 

[erisuser1]

Glad you got it working... welcome to the land of root!

 

[knitpurlgurl]

HELP - Got through fig 31 and it said I have root! then I booted up into recovery and got a red triangle with exclamation point. What the heck did I do?!

 

[scary alien]

HELP - Got through fig 31 and it said I have root! then I booted up into recovery and got a red triangle with exclamation point. What the heck did I do?!

KPG,

Did you reboot after figure 29?

You can always repeat the root_part1 and root_part2 steps again...no big deal. Just follow the steps carefully.

By the way, since you are using eu1's Universal thread, if you want to install the trackball-optional recovery, now is a good time to slip it in--i.e., replace the the one that eu1's scripts contained and just install the one I built.

Just use the "Scenario 1" installation instructions in this thread:

http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html

Cheers!

 

[knitpurlgurl]

KPG,

Did you reboot after figure 29?

You can always repeat the root_part1 and root_part2 steps again...no big deal. Just follow the steps carefully.

By the way, since you are using eu1's Universal thread, if you want to install the trackball-optional recovery, now is a good time to slip it in--i.e., replace the the one that eu1's scripts contained and just install the one I built.

Just use the "Scenario 1" installation instructions in this thread:

http://androidforums.com/eris-all-t...2-custom-recovery-trackball-not-required.html

Cheers!

Okay, Got it to work AND slipped in the Alternate Amons! YAY!! Thanks!

 

[scary alien]

Okay, Got it to work AND slipped in the Alternate Amons! YAY!! Thanks!

Very nice! Congrats!

This should provide you with a little insurance for the future .

Cheers!

 

[ihapfm02]

New to this, but after following directions exactly- I have installed everything. So after last step: I rebooted it, and it is not loading. It is hung up on the Android silver screen doing nothing. it sat for an hour or two before I rebooted again. It's been half an hour and isn't doing anything. What to do?

 

[erisuser1]

New to this, but after following directions exactly- I have installed everything. So after last step: I rebooted it, and it is not loading. It is hung up on the Android silver screen doing nothing. it sat for an hour or two before I rebooted again. It's been half an hour and isn't doing anything. What to do?

I am having a hard time deciphering what you are intending to describe.

Q1) What ROM did you attempt to install, if any? (What do you mean by "installed everything").

Q2) Can you boot into Amon_RA's recovery (Power up with Vol-Up+End/Power), or boot first into HBOOT (by powering up with Vol-Down+End/Power), and then using the on-screen menu to continue to the Recovery boot?

Q3) "Silver Screen" is not particularly helpful... is this something a specific ROM displays, or is it the white background screen with three skateboarding droids?

If it is a ROM splash screen you are talking about (not the 3 skateboards), then the solution is to either follow the dev's instructions to install the ROM, watching carefully for any "E" messages (error messages) which appear on the screen - or install a different ROM.

Also, note that the instructions tell you to immediately perform a Nandroid Backup before you flash a new ROM. You didn't mention that - did you do this? Did it succeed? (If so, then you should also be able to restore it).

eu1

 

[doogald]

New to this, but after following directions exactly- I have installed everything. So after last step: I rebooted it, and it is not loading. It is hung up on the Android silver screen doing nothing. it sat for an hour or two before I rebooted again. It's been half an hour and isn't doing anything. What to do?

I am having a hard time deciphering what you are intending to describe.

Q1) What ROM did you attempt to install, if any? (What do you mean by "installed everything").

Q2) Can you boot into Amon_RA's recovery (Power up with Vol-Up+End/Power), or boot first into HBOOT (by powering up with Vol-Down+End/Power), and then using the on-screen menu to continue to the Recovery boot?

Q3) "Silver Screen" is not particularly helpful... is this something a specific ROM displays, or is it the white background screen with three skateboarding droids?

If it is a ROM splash screen you are talking about (not the 3 skateboards), then the solution is to either follow the dev's instructions to install the ROM, watching carefully for any "E" messages (error messages) which appear on the screen - or install a different ROM.

Also, note that the instructions tell you to immediately perform a Nandroid Backup before you flash a new ROM. You didn't mention that - did you do this? Did it succeed? (If so, then you should also be able to restore it).

eu1

One more question: if you installed a custom ROM, did you wipe data/factory reset first? If you installed a close-to-stock ROM (xtrSENSE, PlainJane) you shouldn't need to wipe data, but anything else (including xtrROM) should have a data wipe done before you restart the phone.

 

[zapjb]

Just wanted to say thanks to OP. Rooted my Eris. And overclocked. So much more to learn.

 

[Bob Cat]

Just wanted to say thanks to OP. Rooted my Eris. And overclocked. So much more to learn.

Welcome to the world of rooting.

 

[oh2guy]

Thank you for a great tutorial! The process went very smoothly. I'm rooted and on xtrSENSE and everything is working great!

 

[darkdream666]

alright so heres my problem
everything works fine up until i have to do the recovery stuff...
when ever i try to go to the recovery menu it just gets stuck on the skating androids screen. i have a 2.1 eris the hboot says 1.46.
i am kind of new at all this rooting and droid stuff and i loved the tutorial, it just wouldnt go past the skating androids o.o
it will load fine if i DONT push vol up and end.
it will load fine if i push vol down and end, and it goes to the boot menu where i push vol up to go to recovery, it gets stuck on the skating androids...
it will load the fastboot if i do send and end, and my only choice there is to go to hboot and try vol up again which just leads to it freezing on the skating androids....

this is really frustrating i feel like i have tried all i could, any suggestions would be great :]
ive tried doing it over like 3 times and no luck(erasing everything off the sd card)

 

[erisuser1]

alright so heres my problem
everything works fine up until i have to do the recovery stuff...
when ever i try to go to the recovery menu it just gets stuck on the skating androids screen. i have a 2.1 eris the hboot says 1.46.
i am kind of new at all this rooting and droid stuff and i loved the tutorial, it just wouldnt go past the skating androids o.o
it will load fine if i DONT push vol up and end.
it will load fine if i push vol down and end, and it goes to the boot menu where i push vol up to go to recovery, it gets stuck on the skating androids...
it will load the fastboot if i do send and end, and my only choice there is to go to hboot and try vol up again which just leads to it freezing on the skating androids....

this is really frustrating i feel like i have tried all i could, any suggestions would be great :]
ive tried doing it over like 3 times and no luck(erasing everything off the sd card)

You have a couple of options.

1. Re-download and repeat, but this time use the (free) app AFV (Android File Verifier) to check the MD5 signature of the recovery.img file to make sure that nothing is going wron with the unpacking of the gscript.zip file.

2. Use jcase's one-click app instead of this method. Make sure you reboot normally once after you run the app before trying to boot into the (new) recovery.

3. Root the old-fashioned way with the "root" PB00IMG.zip. file


eu1

 

[scary alien]

A heartfelt, "welcome back", eu1!

Many (most, I'm sure) missed your presence around here (its certainly not the same without you).

Cheers!

 

[darkdream666]

You have a couple of options.

1. Re-download and repeat, but this time use the (free) app AFV (Android File Verifier) to check the MD5 signature of the recovery.img file to make sure that nothing is going wron with the unpacking of the gscript.zip file.

2. Use jcase's one-click app instead of this method. Make sure you reboot normally once after you run the app before trying to boot into the (new) recovery.

3. Root the old-fashioned way with the "root" PB00IMG.zip. file


eu1

i actually did try that pb one first, the pb zip file wouldnt show up in the boot menu, no matter what i did, and i couldnt get the usb drivers to install for sdk whatsoever =[
im thinkin this thing just doesnt want to be rooted.... lol
and i followed the instructions exactly and rebooted when and how it told me to lol

 

[darkdream666]

You have a couple of options.

1. Re-download and repeat, but this time use the (free) app AFV (Android File Verifier) to check the MD5 signature of the recovery.img file to make sure that nothing is going wron with the unpacking of the gscript.zip file.


eu1

not quite sure what you meant by that D: kinda new to this thing hahaha

 

[scary alien]

not quite sure what you meant by that D: kinda new to this thing hahaha

eu1 meant that you should verify that the files that you downloaded to your phone were whole and uncorrupted. You can do this by using something like my app, "AFV (Android File Verifier)", which is free in the Market, to compare the MD5 checksums with the ones that were published in the first post.

You can also use Astro File Manager to check a file after its downloaded (long-press the downloaded file, select Details, and wait a few seconds for the MD5 checksum to be displayed).

The implication of you skating Androids issues is that the custom recovery that you flashed wasn't a good file, so making sure that the file is good takes away an obvious reason for the issue.

Let us know...someone will be here to help you.

edit: also, if you are not familiar with the Eris 1-click root app, its in the Android Market under "HTC Eris 1 Click Root App" (https://market.android.com/details?id=net.andirc.erisrooter&feature=search_result). The AF thread for this app is: http://androidforums.com/eris-all-things-root/139178-universal-1-click-eris-app-apk-no-pcs-no-scripts-needed-easy.html which might be a simpler route for you to take.

 

[darkdream666]

eu1 meant that you should verify that the files that you downloaded to your phone were whole and uncorrupted. You can do this by using something like my app, "AFV (Android File Verifier)", which is free in the Market, to compare the MD5 checksums with the ones that were published in the first post.

The implication of you skating Androids issues is that the custom recovery that you flashed wasn't a good file, so making sure that the file is good takes away an obvious reason for the issue.

Let us know...someone will be here to help you.

edit: also, if you are not familiar with the Eris 1-click root app, its in the Android Market under "HTC Eris 1 Click Root App" (https://market.android.com/details?id=net.andirc.erisrooter&feature=search_result). The AF thread for this app is: http://androidforums.com/eris-all-t...is-app-apk-no-pcs-no-scripts-needed-easy.html which might be a simpler route for you to take.

so i checked it out, they match perfectly, so im not sure where that puts me lol
and i tried that app, same problem, when i try to go to recovery it just freezes me on the skating androids....
this phone obviously hates me hahaha

Edit: or maybe it just really wants to skate? =\

 

[scary alien]

so i checked it out, they match perfectly, so im not sure where that puts me lol
and i tried that app, same problem, when i try to go to recovery it just freezes me on the skating androids....
this phone obviously hates me hahaha

Edit: or maybe it just really wants to skate? =\

dd666,

Sorry, for not getting back to you sooner... I'm a little stumped too, but I've re-scanned this same thread for something similar to your issue... Check out vannman17's post and subsequent replies from eu1 starting from here:

http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies-7.html#post1363990

vannman and eu1 continued their discussion over to this thread:

http://androidforums.com/eris-all-things-root/125436-detailed-leak-root-tutorial-10.html#post1390066

Hopefully, these posts will be enough to get you going.

Hope that helps! Cheers!

 

[doogald]

dd666,

Sorry, for not getting back to you sooner... I'm a little stumped too, but I've re-scanned this same thread for something similar to your issue... Check out vannman17's post and subsequent replies from eu1 starting from here:

http://androidforums.com/eris-all-things-root/127861-universal-eris-root-dummies-7.html#post1363990

vannman and eu1 continued their discussion over to this thread:

http://androidforums.com/eris-all-things-root/125436-detailed-leak-root-tutorial-10.html#post1390066

Hopefully, these posts will be enough to get you going.

Hope that helps! Cheers!

To summarize what happened:

vanman also had 1.46.0000 HBOOT. Neither this method nor the 1-click app method would successfully root the phone - it had the same problem that you are reporting - the Recovery boot getting stuck at the skateboarding Androids. Even trying to start the phone in HBOOT (by powering up while holding VolDn) and then pressing VolUp to start Recovery would not work.

Vanman was able to root, though, after installing the old LeakV3 image, which installed the 1.49.0000 bootloader, and then running through one of these two procedures. (To explain what the "leak v3" is, back when we Eris users were running Android 1.5 and waiting for the official 2.1 over the air update, there were three builds of the official 2.1 build that were leaked out, and many people were able to install 2.1 early using the leak.)

You can download it from here: xda-developers - View Single Post - [HTC ROMs] Consolidated HTC Eris RUU/OTA/ROM URLs

Go to the link that says this: PB00IMG.ZIP: Eris_LeakV3_v2.36.605.1_PB00IMG.ZIP. You need to rename the file that you download to PB00IMG.zip (in other words, get rid of the rest of the file name) and copy that file to the root (or top) directory of your SD card. (In other words, do not put it in a folder on the SD card.) Please be sure to check the MD5 hash, or at least verify that the file length is 109,946,224 bytes.

The instructions to install are in this post: http://androidforums.com/htc-droid-eris/51383-upgrading-2-1-tutorial.html starting with the words, in red:

This is the Point of No Return
Once you do this, you cannot go back to 1.5, PERIOD.

Please be aware that this is your phone, not mine, and anything that ruins your phone is your responsibility. I do not mean to scare you away from this; I think that if you check that the PB00IMG.zip file is correct and proper you will be all set (you will end up with a freshly-installed version 2.1 phone that may prompt you almost right away to install an over the air update - since you are going to root, you can ignore that.) You have to really want to root to do this, I think.

 

[scary alien]

Thanks, doogald!

Glad to know that my bleary-eyed analysis and reply meshes with what you posted and eu1 had previously guided vannman17 through.

Your summary will be very helpful to dd666.

Cheers!

 

[noirtest]

I hit a brick wall when using ES File Explorer to unzip GScript. It doesn't produce the "Tools" folder and two shells- just a single file named "GScriptLite.apk". Shucks. Are these instructions outdated somehow?