• 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!

Ok so i have the track ball problem however i followed your process bit for bit but the final step i got this message, " Error: this script is meant for the HTC Droid Eris (desirec): your phone is reported to be a:" and then nothing after that. what would you suggest i do for this problem?

Are you using a Kaos Froyo ROM?

If so, there's a section in the first post that says this:

Code:
[B][COLOR=Red]*** Special Note for those using [COLOR=Blue]KaosFroyo [/COLOR]ROMs ***
[/COLOR][/B]
Note: it appears that the [B]getprop [/B]command that is used in my Gscript script is
not present in KaosFroyo ROMs. The [B]getprop [/B]command is used to verify / validate 
that you are indeed running the script on an HTC Droid Eris.

Please reference the posts starting this with one
 [URL]http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required-2.html#post2089171[/URL] 
for information about how to modify my script to continue the installation of this alternate recovery (specifically this post: 
[URL]http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required-3.html#post2093137[/URL]).

Let me know.

Cheers!
 
Upvote 0
Scary,

Your script worked for me fine last year.

My wife finally agreed to let me root her Eris Now running Shed's GSB 2.8.

Tried to flash your script via Gscipt-lite and it fails. The steaming log says

"flash_image not found". I verified MD5 before unzipping and looked in the Tools folder and it contains all 3 files.

Deleted everything and tried again with same negative results.

Any ideas?

Thanks,

SF
 
Upvote 0
Scary,

Your script worked for me fine last year.

My wife finally agreed to let me root her Eris Now running Shed's GSB 2.8.

Tried to flash your script via Gscipt-lite and it fails. The steaming log says

"flash_image not found". I verified MD5 before unzipping and looked in the Tools folder and it contains all 3 files.

Deleted everything and tried again with same negative results.

Any ideas?

Thanks,

SF

SF,

Weird... I last tested the script on my GSB 1.6 install. I can try it again with the 2.8 version (wow, I am really behind on these releases, lol), but I can't do that until I get home this evening.

It sounds like there's no "/sqlite_stmt_journals" directory on GSB 2.8??? (which is where the Gscript script copies the flash_image utility to and expects to find it and execute it from there later). Although, I'm now looking at the script code and I see where I have an alternate directory coded for in case its not (/data/data/gscript-sa).

Can you post or send me (scary.alien@gmail.com) the whole /sdcard/gscript/tools/logfile.txt file for me to peruse?

The script is actually pretty simple... Its really just staging the flash_image utility where it can be executed with the alternate recovery image.

Also, one last thing...did you ensure that the "Needs SU?" box was checked (I'm just reaching here in hopes that would have prevented copying the flash_image utility to the staging directory).

Let me know.

Cheers!
 
Upvote 0
Scary,

Your script worked for me fine last year.

My wife finally agreed to let me root her Eris Now running Shed's GSB 2.8.

Tried to flash your script via Gscipt-lite and it fails. The steaming log says

"flash_image not found". I verified MD5 before unzipping and looked in the Tools folder and it contains all 3 files.

Deleted everything and tried again with same negative results.

Any ideas?

Thanks,

SF


Did you use scenario 3? Read a little further down and you have to open gscrip-sa in gscrips.
Oops sorry.
 
Upvote 0
SF,

Weird... I last tested the script on my GSB 1.6 install. I can try it again with the 2.8 version (wow, I am really behind on these releases, lol), but I can't do that until I get home this evening.

It sounds like there's no "/sqlite_stmt_journals" directory on GSB 2.8??? (which is where the Gscript script copies the flash_image utility to and expects to find it and execute it from there later). Although, I'm now looking at the script code and I see where I have an alternate directory coded for in case its not (/data/data/gscript-sa).

Can you post or send me (scary.alien@gmail.com) the whole /sdcard/gscript/tools/logfile.txt file for me to peruse?

The script is actually pretty simple... Its really just staging the flash_image utility where it can be executed with the alternate recovery image.

Also, one last thing...did you ensure that the "Needs SU?" box was checked (I'm just reaching here in hopes that would have prevented copying the flash_image utility to the staging directory).

Let me know.

Cheers!

I think I deleted the files from her phone to start fresh one more time.

I'll check when she comes home this PM. If I did delete them, will run again and if it fails, will send you the log. yes, the "SU" was Checked.

Thanks,

SF
 
Upvote 0
I think I deleted the files from her phone to start fresh one more time.

I'll check when she comes home this PM. If I did delete them, will run again and if it fails, will send you the log. yes, the "SU" was Checked.

Thanks,

SF

Okay...figured it out...

Turns out, there's no "mkdir" command native to GSB 2.8...:eek:! (weird...at least to me).

Fix is easy...just add the word "busybox" in front of the "mkdir" command:

Line to be modified:

Code:
    mkdir ${_PROG_DIR}  2> /dev/null     # create our working directory

How its supposed to look afterwards:

Code:
    [B][COLOR=Red]busybox [/COLOR][/B]mkdir ${_PROG_DIR}  2> /dev/null     # create our working directory

I think this should actually work even with older/other ROMs.

I did the above three times (flashed "trackball-optional", flashed "trackball-not-required", and then flashed back to "trackball-optional").

I'll build a new version of the gscript-sa.zip file and post its link for downloading, but you should be able to long-press the "gscript-sa" script in Gscript (after you've loaded it, of course), select "Edit", find the line with the above mkdir command in it, and put "busybox " in front of the "mkdir" text as shown above.

Cheers!
 
Upvote 0
I Unzipped the file on my laptop, added "busybox" and re-zipped.

Will try tonight.

Thanks,

SF

I'll build a new version of the gscript-sa.zip file and post its link for downloading, but you should be able to long-press the "gscript-sa" script in Gscript (after you've loaded it, of course), select "Edit", find the line with the above mkdir command in it, and put "busybox " in front of the "mkdir" text as shown above.

Cheers![/QUOTE]
 
Upvote 0
I Unzipped the file on my laptop, added "busybox" and re-zipped.




Will try tonight.

Thanks,

SF

I'll build a new version of the gscript-sa.zip file and post its link for downloading, but you should be able to long-press the "gscript-sa" script in Gscript (after you've loaded it, of course), select "Edit", find the line with the above mkdir command in it, and put "busybox " in front of the "mkdir" text as shown above.

Cheers!
[/QUOTE]


SA

It worked.

As usual, your help is most appreciated!

Thanks,

SF
 
Upvote 0
BC when you boot into recovery,does it say:

RA-eris-v1.6.2
[tracball optional]

across the bottom? i just verified the buttons work for me... send goes down,vol+ goes up,power/end selects

since my tracball works i use it to scroll,but always push power/end to select instead of clicking the tracball
 
Upvote 0
BC when you boot into recovery,does it say:

RA-eris-v1.6.2
[tracball optional]

across the bottom? i just verified the buttons work for me... send goes down,vol+ goes up,power/end selects

since my tracball works i use it to scroll,but always push power/end to select instead of clicking the tracball


I do the same as you. Yes it says trackball optional.
 
Upvote 0
Scary,

Just for S&G's I wanted to check (in case I did need it) that I could go into recovery and toggle the buttons without the trackball and the only thing that worked was the on/off button to reboot. Am I doing something wrong?:thinking: I'm using Comdemned CM 7 and before that was GSB 2.8.

Weird, because the ROM you have flashed should not make any difference...

- volume-up: scroll-up
- geen call button: scroll-down
- red end/pwr: select / confirm
- volume-down: previous menu (this was there before)

Both the original "trackball-not-required" and the "trackball-optional" versions support the alternate key menu navigation.

Perhaps try reflashing the custom recovery?

Let me know.

Cheers!
 
Upvote 0
Weird, because the ROM you have flashed should not make any difference...

- volume-up: scroll-up
- geen call button: scroll-down
- red end/pwr: select / confirm
- volume-down: previous menu (this was there before)

Both the original "trackball-not-required" and the "trackball-optional" versions support the alternate key menu navigation.

Perhaps try reflashing the custom recovery?

Let me know.

Cheers!


Ok I'll give her a go when I get home and report back. :)
 
Upvote 0
Okay...figured it out...

Turns out, there's no "mkdir" command native to GSB 2.8...:eek:! (weird...at least to me).

Fix is easy...just add the word "busybox" in front of the "mkdir" command:

Line to be modified:

Code:
    mkdir ${_PROG_DIR}  2> /dev/null     # create our working directory

How its supposed to look afterwards:

Code:
    [B][COLOR=Red]busybox [/COLOR][/B]mkdir ${_PROG_DIR}  2> /dev/null     # create our working directory

I think this should actually work even with older/other ROMs.

I did the above three times (flashed "trackball-optional", flashed "trackball-not-required", and then flashed back to "trackball-optional").

I'll build a new version of the gscript-sa.zip file and post its link for downloading, but you should be able to long-press the "gscript-sa" script in Gscript (after you've loaded it, of course), select "Edit", find the line with the above mkdir command in it, and put "busybox " in front of the "mkdir" text as shown above.

Cheers!

Okay, so here I go again, quoting myself, lol.

Here's a version of the gscript-sa.sh script that includes a "busybox " command in front of the mkdir command to help the script work on the more recent GSB ROMs (that apparently don't have the mkdir command supported in their shell script?).

Anyway, after you extract the contents of the gscript-sa.zip file, replace the /sdcard/gscript/gscript-sa.sh script with the one attached below (you'll have to first remove the .txt suffix with a file manager):

View attachment gscript-sa.sh.txt

You can, as I indicated before, simply use the mini-editor that comes with Gscript Lite to manually insert "busybox " (note the space character at the end before the ending quote).

Cheers!
 
Upvote 0
Scary,

Just for S&G's I wanted to check (in case I did need it) that I could go into recovery and toggle the buttons without the trackball and the only thing that worked was the on/off button to reboot. Am I doing something wrong?:thinking: I'm using Comdemned CM 7 and before that was GSB 2.8.

Sorry Scary, I'm a dumbass.:eek: It works juuuust fine.;):D
 
Upvote 0
Hi everyone,

Heres my problem, when I download the zip file its only 3kb and when I try to open it windows says there are no files in the zip folder... and the trackball option file downloaded just fine, im just not sure how to use adb lol

If anyone feels like helping it would be much appreciated!

Hey, jlab89, so you are trying to download the gscript-sa-171.zip file (this is probably the version you should be downloading)?

https://sites.google.com/site/scaryalienware/downloads/gscript-sa-171.zip

MD5 sum of gscript-sa-171.zip: 2580f0c92f3e1e8acd9c8af1b5eae513
File size of gscript-sa-171.zip: 3,915,425 bytes

Which scenario are you trying to use (i.e., what is the state or your phone? i.e., do you already have a custom rooted ROM installed, etc.).

If you have Asto File Manager installed (its free in the Market), there is a menu setting (menu -> More -> Preferences -> Enable Browser Downloader) that can help with the downloading of files from the stock browser. Otherwise, you might try a different browser like Opera Mini since it seems to play nicer with downloads at times or for some files.

Let us know.
 
Upvote 0
Hey, jlab89, so you are trying to download the gscript-sa-171.zip file (this is probably the version you should be downloading)?

https://sites.google.com/site/scaryalienware/downloads/gscript-sa-171.zip

MD5 sum of gscript-sa-171.zip: 2580f0c92f3e1e8acd9c8af1b5eae513
File size of gscript-sa-171.zip: 3,915,425 bytes

Which scenario are you trying to use (i.e., what is the state or your phone? i.e., do you already have a custom rooted ROM installed, etc.).

If you have Asto File Manager installed (its free in the Market), there is a menu setting (menu -> More -> Preferences -> Enable Browser Downloader) that can help with the downloading of files from the stock browser. Otherwise, you might try a different browser like Opera Mini since it seems to play nicer with downloads at times or for some files.

Let us know.

Thanks for the reply scary alien. I fall into scenario 3 I think (all ready rooted, and already have custom ROM installed(XtrSense)). I was trying the 171 zip, but I was trying to download it on my computer (my plan was to then move to my phone). Before I did anymore I checked the file size and that wasn't the correct size as you listed in your first post so I stopped there.

I honestly never thought of downloading it from my phone!

So I used the basic provided browser, followed the directions you listed and it worked! Thanks for all your help with such a simple problem!
 
Upvote 0
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones