• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Amon_RA 1.6.2 Custom Recovery: trackball not required!

Scary, after reading about this on the other thread today, I finally did this. It worked perfectly.

It took me 5 months, and while my trackball works perfectly, I guess that an Eris trackball that works may be just an Eris trackball that hasn't broken yet. I used the gscript method because I was too lazy to fastboot.

Anyway, I still wish I could hit the thanks button more times. Thanks for doing this.

Thank you too, sir, for all of your contributions!

I appreciate the thanks and it means a lot to me coming from you.

I'm happy to have helped.

Cheers!
 
Quote:
Originally Posted by doogald
Scary, after reading about this on the other thread today, I finally did this. It worked perfectly.

It took me 5 months, and while my trackball works perfectly, I guess that an Eris trackball that works may be just an Eris trackball that hasn't broken yet. I used the gscript method because I was too lazy to fastboot.

Anyway, I still wish I could hit the thanks button more times. Thanks for doing this.
Thank you too, sir, for all of your contributions!

I appreciate the thanks and it means a lot to me coming from you.

I'm happy to have helped.

Cheers!
---------------------------------------------------------------------------
Sigh. And then there's me. I still can not get this updated version in my phone. I'm stuck with a ROM that isn't working as great as I hoped and a battery that needs to be reset using the method I read about in here. (Wipe battery)
I don't know what I'm doing wrong. Makes no sense to me, I installed the original in seconds. It was quite easy. I have to do it by phone only, but every time I download the gscripts I get "bad zip file", yet it works for everyone else.

OH AND FOR THE RECORD!!!!! To the left it says I am running Shed's Red Glass. I did, but no longer. I just didn't update that. That is NOT the ROM that I mentioned above. That is one that I LOVED. Phenomenal ROM!!!! I plan to go back to it!
 
Sigh. And then there's me. I still can not get this updated version in my phone. I'm stuck with a ROM that isn't working as great as I hoped and a battery that needs to be reset using the method I read about in here. (Wipe battery)
I don't know what I'm doing wrong. Makes no sense to me, I installed the original in seconds. It was quite easy. I have to do it by phone only, but every time I download the gscripts I get "bad zip file", yet it works for everyone else.

GJW419,

I'm still at work, but I hope to leave in about 30-45 minutes...if you shoot me a PM with your Gmail address, I'll walk you through this in a Gmail-chat session if you are interested.

Let me know.
 
Where do I put the.img file. Do I move it to the SD card along with the gscrip.zip file.
if i understand it correctly,you dont put the img file anywhere. the recovery image is inside the gscript.zip file. this is why you move it up to your sd card and extract it.

all you need to do is download either:
https://sites.google.com/site/scaryalienware/downloads/gscript-sa-171.zip for the 1.7.1 new version
or
https://sites.google.com/site/scaryalienware/downloads/gscript-sa.zip for the original 1.6.2 version.

then start with the instructions in the box under scenario 3 on page 1 to move it up to root level and extract it.


Also do I need to download gcript lite.

yes :)
 
just thinking out loud here... i have installed recoveries in hboot on my incredible. i wonder if it would be possible to package up your recovery as a PB00IMG file so it could be automagically detected and installed thru hboot?

this could be useful for the users that are having a hard time for whatever reason,or for the users whose tracball has stopped working. all thats needed is to get the file to root level of the sd card,power off,then power on/vol - and select yes to update in hboot. :)

again,thanks for all your efforts here... i installed it as soon as i started messing with my phone just in case. :cool:
 
Where do I put the.img file. Do I move it to the SD card along with the gscrip.zip file. Also do I need to download gcript lite.

Ok, here is what I did.

I downloaded the option 3 .zip file. Using Astro, I moved that file to the /gscripts folder that was already on my phone (which, it turns out, merely proves that I am absolutely terrible with reading comprehension sometimes.) The right thing to do is to move that file to the root directory of the SD card. From there, you long press and choose extract, choose to extract it to the current directory, and that will put these script that you need, plus a tools directory that actually has the recovery image, into the gscripts folder.

Yes, you need to install gscript lite (or full, if you want to pay for full and pay the developer for such a useful app.) And then run gscripts, press menu, load the script.

Or, you can do a better job of reading the original post than I did. Follow the instructions in "Scenario 3". Scary did an excellent job documenting precisely what you need to do. It's only people like me who think that they occasionally don't need to RTFM who will mess those up.

It all worked fine for me, but, ironically, in an attempt to try to capture the location of the new OTA for stock I've already replaced Scary's recovery, but just temporarily. I waited 5 months to install it and kept it on my phone for five hours.
 
Ok, here is what I did.

I downloaded the option 3 .zip file. Using Astro, I moved that file to the /gscripts folder that was already on my phone (which, it turns out, merely proves that I am absolutely terrible with reading comprehension sometimes.) The right thing to do is to move that file to the root directory of the SD card. From there, you long press and choose extract, choose to extract it to the current directory, and that will put these script that you need, plus a tools directory that actually has the recovery image, into the gscripts folder.

Yes, you need to install gscript lite (or full, if you want to pay for full and pay the developer for such a useful app.) And then run gscripts, press menu, load the script.

Or, you can do a better job of reading the original post than I did. Follow the instructions in "Scenario 3". Scary did an excellent job documenting precisely what you need to do. It's only people like me who think that they occasionally don't need to RTFM who will mess those up.

It all worked fine for me, but, ironically, in an attempt to try to capture the location of the new OTA for stock I've already replaced Scary's recovery, but just temporarily. I waited 5 months to install it and kept it on my phone for five hours.


Ok, what I did was long-press the zip and selected extract to this directory. It loaded but I didn't get the screen scary showed. So how do I know it there.
 
Ok, what I did was long-press the zip and selected extract to this directory. It loaded but I didn't get the screen scary showed. So how do I know it there.

I just looked again and Scary doesn't have a screen shot showing the result of extracting the zip file. However, you can use Astro to go into /gscripts on the SD Card. There should be a tools folder in there. In there should be three files - flash_image, md5info, and recovery-RA-eris-v1.6.2-trackball-optional

If you see that (and also a file called gscript-sa in /gscripts itself) the file extracted properly.
 
I just looked again and Scary doesn't have a screen shot showing the result of extracting the zip file. However, you can use Astro to go into /gscripts on the SD Card. There should be a tools folder in there. In there should be three files - flash_image, md5info, and recovery-RA-eris-v1.6.2-trackball-optional

If you see that (and also a file called gscript-sa in /gscripts itself) the file extracted properly.


It's all there but the md5 info.
 
I could be mistaken about the md5info.

You should be able to install gscript lite, follow Scary's instructions and run the gscript-sa.sh script in gscript lite. It should tell you at the bottom that the recovery should be installed. When you restart the phone to recovery, at the bottom it will tell you that you are using the trackball not required version of Amon's Recovery.
 
You should still be good to go on with the rest of scenario 3. I think the MD5 info is just in there to check the status of the downloaded info.


I guess I only did half of it huh? I went into gscript lite and the rest is history.;) That was like taking candy from a baby (which is pretty easy by the way). And oh yea and I should've had a "v8". :D
 
Hello, Scary alien. haven't been on in a while. but i recently fixed my phone from other non thread related problems, and i stopped by to root your optional trackball img. I just wanna thank you again for sticking with me, and helping me out with this nightmare (back then) of a root. thumps up to you sir.
 
Hello, Scary alien. haven't been on in a while. but i recently fixed my phone from other non thread related problems, and i stopped by to root your optional trackball img. I just wanna thank you again for sticking with me, and helping me out with this nightmare (back then) of a root. thumps up to you sir.

Hey, TL93! Good to hear from you again and thank you for the kind words!

You probably had a slightly easier time this time, eh? ;) :p

Thank you for your assistance way back then when we discovered the source version issue re. the missing partitioning options.

Cheers and have a great rest of your day!
 
Hi scary alien :)
Stopped by this thread to do some preventative maintenance to my little rooted Eris in case the trackball decides to go wonky on me in the future.

Just have one little (probably dumb question). My scenario would be option 3:
Rooted phone w/non-stock ROM & 1.6.2 Amon_RA Eris custom recovery installed

So I downloaded your gscript-sa-171.zip, but before I extract it to the root of my sdcard, do I need to delete my original gscript folder that I put there from rooting originally with erisuser1's "Universal Eris Root for Dummies?" before I run the gscript-sa.sh script with Gscript Lite?

And this note you wrote:
"If you have to re-extract the gscript-sa.zip file (via Astro) and re-run the gscript-sa.sh script from Gscript, its probably a good idea to delete the gscript-sa script from inside Gscript (long-press the gscript-sa script name and select Delete)."

Does that apply only if the first try of replacing the recovery image failed and I need to do it a second time?

Thanks in advance and sry for being so longwinded. Just making sure I'm doing everything right :) Rooted only a few days ago, but so far everything was easy and GSB is up and running beauuuuutifully!
 
Hi scary alien :)
Stopped by this thread to do some preventative maintenance to my little rooted Eris in case the trackball decides to go wonky on me in the future.

Just have one little (probably dumb question). My scenario would be option 3:
Rooted phone w/non-stock ROM & 1.6.2 Amon_RA Eris custom recovery installed

So I downloaded your gscript-sa-171.zip, but before I extract it to the root of my sdcard, do I need to delete my original gscript folder that I put there from rooting originally with erisuser1's "Universal Eris Root for Dummies?" before I run the gscript-sa.sh script with Gscript Lite?

And this note you wrote:
"If you have to re-extract the gscript-sa.zip file (via Astro) and re-run the gscript-sa.sh script from Gscript, its probably a good idea to delete the gscript-sa script from inside Gscript (long-press the gscript-sa script name and select Delete)."

Does that apply only if the first try of replacing the recovery image failed and I need to do it a second time?

Thanks in advance and sry for being so longwinded. Just making sure I'm doing everything right :) Rooted only a few days ago, but so far everything was easy and GSB is up and running beauuuuutifully!

Neera,

Not a problem ;).

You shouldn't have to delete the original gscript folder that eu1's thread created, but you can if you want to or don't use Gscript Lite for anything else (that will make everything "clean" and you'll know that all of the files in the gscript directory are just from my .zip file).

You could also rename that folder to something else and then rename it back after you are done.

The comment about deleting the gscript-sa script was for the script itself from inside Gscript Lite (I think I had some issues while I was developing the script that scared me into posting that ;), so I'm pretty sure you should be okay (but it won't hurt you if you delete and re-extract either)).

You sound pretty savvy re. this and should be just fine.

Let me know if you have issues.

Cheers!

edit: by the way, when I tested this with GSB 1.6, it worked, but the output of the script scrolled off the screen (which was different from how it behaved on other rooted ROMs)--but it did successfully flash the alternate custom recovery (you'll know from the "trackball-optional" text at the bottom of the custom recovery screen).
 
Wow that was a fast reply scary alien! Thanks so much.
I feel the love in our Eris forums :)

It worked flawlessly btw. I got rid of the old gscript folder from rooting and extracted your zip, added the script in Gscript Lite and ran it.

Got a little queezy when I saw some error messages fly by (is there a log file somewhere btw?).
But in the end it did successfully flash the alternate custom recovery ("Congrats! You now should now have the new trackball-optional custom recovery installed.") and I of course booted into recovery for the final check and yep it had the
"[trackball optional]text at the bottom of the screen under the "Build : RA-eris-v1.6.2"

I am a happy camper now, in full control of my little Eris and do not fear my trackball going out on me, rawr!
 
Wow that was a fast reply scary alien! Thanks so much.
I feel the love in our Eris forums :)

It worked flawlessly btw. I got rid of the old gscript folder from rooting and extracted your zip, added the script in Gscript Lite and ran it.

Got a little queezy when I saw some error messages fly by (is there a log file somewhere btw?).
But in the end it did successfully flash the alternate custom recovery ("Congrats! You now should now have the new trackball-optional custom recovery installed.") and I of course booted into recovery for the final check and yep it had the
"[trackball optional]text at the bottom of the screen under the "Build : RA-eris-v1.6.2"

I am a happy camper now, in full control of my little Eris and do not fear my trackball going out on me, rawr!

No problem! We're all here to help. ;)

Go get 'em, tiger! (you "rawr!" sounds like Scotty's avatar, lol :D).

By the way, there is a log file that my script writes (in the gscripts/tools directory, if I recall correctly). I don't have it capturing everything (like the output of the flash_image command), but there's some stuff in there that would give you the warm and fuzzies that it worked right.

Cheers!
 
Log located, copy/paste below:

================================================================
-=[ gscript-sa.sh - invoked Mon Mar 28 15:46:34 CDT 2011 ]=-

Info: _SD_DIR = /sdcard/gscript/tools
Info: _PHONE_MODEL = desirec
Info: _RCVRY_IMAGE = recovery-RA-eris-v1.6.2-trackball-optional.img
Info: _LOGFILE = /sdcard/gscript/tools/logfile.txt
Info: _RO_BLD_PROD = desirec
Info: we'll use /data/data/gscript-sa for housing flash_image
Info: flash_image installed and secured:

-rwxr-xr-x 1 root root 9640 Mar 28 15:46 /data/data/gscript-sa/flash_image

Info: alternate recovery image successfully flashed
-=[ gscript-sa.sh - terminating Mon Mar 28 15:46:40 CDT 2011 ]=-
================================================================
Warm fuzzies all over :D
 
Also BTW for all, and I think this has been covered but so what, Scary's version of Amon's adds the ability for Nandroid to backup the cache partition as well, so restored ROMs will boot a lot faster, and also has the ability to completely wipe the cache partition rather than the previous "Wipe Dalvik cache", which seemed to only wipe the third party app Dalvik cache on /data rather than the internal apps' Dalvik cache in /cache.
 
Also BTW for all, and I think this has been covered but so what, Scary's version of Amon's adds the ability for Nandroid to backup the cache partition as well, so restored ROMs will boot a lot faster, and also has the ability to completely wipe the cache partition rather than the previous "Wipe Dalvik cache", which seemed to only wipe the third party app Dalvik cache on /data rather than the internal apps' Dalvik cache in /cache.

doogald,

Thanks! Excellent point.

Also, I think this might only be true for the "trackball-optional" version that was built using the 1.7.1 recovery.c source. So, this is the version to grab / use (since its will create a "BCDS-ccyymmdd-hhmm" Nandroid backup subdirectory (containing the boot / cache / data / system partitions).

I think the "trackball-not-required" (1.6.2 recovery.c source) will act (except for the (bizarrely missing) partitioning commands) act like the "original" Amon_RA that most folks have. This was my first version that I built before user TheLedge93 discovered the missing commands.

Cheers!
 
Back
Top Bottom