Amon_RA 1.6.2 Custom Recovery: trackball not required!

Last Updated:

  1. scary alien

    scary alien not really so scary Moderator

    Okay guys, we've seen lots of reports of people whose Erises (Erii?) have or are starting to have trackball issues and are unable to properly navigate through Amon_RA's custom recovery. Well, I've been trying to figure-out how to tweak Amon_RA's custom recovery to work without relying on the trackball.

    Anyway, after a lot of thrashing about, and with some sage guidance from Amon_RA, I was able to modify and recompile Amon_RA's 1.6.2 Eris custom recovery to allow an alternate set of keys to be used in lieu of having / needing to use the trackball--not just for scrolling, but for selection / confirmation! I left-in the support for using the trackball so that it will work either way.

    Here's the new, alternate key mappings:

    Code (Text):
    2. [FONT=Courier New][B][COLOR=blue][SIZE=3]volume-UP[/SIZE][/COLOR][/B]:  [B]scroll-up[/B] (trackball scroll-up still works too)[/FONT]
    4. [FONT=Courier New][COLOR=blue][B][COLOR=green]green[/COLOR] [SIZE=3]Call button[/SIZE][/B][/COLOR]: [B]scroll-down[/B] (trackball scroll-down still works too)[/FONT]
    6. [FONT=Courier New][COLOR=blue][B][COLOR=red]red[/COLOR] [SIZE=3]End/Power button[/SIZE][/B][/COLOR]: [B]select / confirm[/B] (trackball-press still works too)[/FONT]
    8. [FONT=Courier New]The [COLOR=blue][B]volume-DOWN[/B] [/COLOR][COLOR=black]key,[/COLOR] which is used to take you back to the prior[/FONT]
    9. [FONT=Courier New]menu / screen, remains unchanged.[/FONT]
    Here's a screenshot of the new version: recovery-RA-eris-v1.6.2-trackball-not-required.jpg

    Notice the [trackball optional] (or [trackball not required]) text at the bottom of the screen under the "Build : RA-eris-v1.6.2" line that lets you know you are using the new, alternate version.


    Note / Edit: 20-November-2010: Click below to read the note:
    I became aware that the menu options for partitioning the /sdcard were "missing" from my initial version of this custom recovery (I didn't notice it because I don't use apps2sd).

    The reason for this was that the Amon_RA custom recovery source I used was pulled from the "desirec" (HTC Eris) branch of the amonra_bootable_recovery github (kindly managed by packetlss). All of the files in this branch are labeled as "1.6.2" (including the only file that I modified, recovery.c).

    Then, late last night, early this morning, AF member TheLedge93 and guide mhotovec pointed-out that there were menu options missing for the Partition sdcard function. I double-checked the "1.6.2" source that I used and those menu item references indeed were not present. They are/were, however present in the "mahimahi" (Nexus One) branch of source for this recovery, many of whose files are listed with a version number of 1.7.1 :)confused:).

    So, I spent this morning seeing if the mahimahi source branch would compile in lieu of the desirec branch I was using--and indeed it did. So, I re-made my tweaks to support the alternative trackball navigation keys in the 1.7.1 version of recovery.c. I've compiled and flashed this new version, testing the trackball, alternate keys, Nandroid backup, Nandroid restore, and saw (but did not test) that the "missing" menu items for the Partition sdcard function were again present.

    What does this mean? Here's the scoop:

    1. I don't exactly know which version of the recovery.c source (or branch) was used by Amon_RA to compile the "1.6.2" recovery that virtually everyone has is and is using (other than those using the tweaked, trackball-optional version that I made a few weeks ago). The build number listed at the bottom of the screen still reads "1.6.2" since this value is gleaned from the default.prop (property) file that is not directly associated with the source (i.e., not involved in the compilation process). I would guess that the build version was not changed in the property file when a version newer than the 1.6.2 source was used to create the recovery images widely-used today.

    I don't believe that the version that most people have is actually the same version that I just built since I have identified at least one slight difference in behavior: Nandroid backups will now backup the /cache filesystem, resulting in Nandroid backup directory names being prefixed with "BCDS-" instead of "BDS-" like were all used to seeing [this threw me for a loop for a while until I finally figured-out that each letter of the prefix indicates what is actually being backed-up by the script: B=boot, C=cache, D=data, S=system].

    2. Anyway, so I'm posting both the old and new versions of this alternate recovery image. The old (1.6.2) version is named:


    and the new ("1.7.1") version is named:


    I also changed the text string below the build number at the bottom of the recovery screen to indicate the different versions.

    I don't think this is too big of a mystery or issue since my hope is that there will be very few of you that will have trackball problems and need either of these tweaked recoveries (although if you are reading this you might be one of those :eek:). Anyway, the old version should suffice for those that don't want or need to partition their /sdcard and hopefully the new version will behave properly for those that do need to (i.e., for a2sd).

    Disclaimer: Again, your mileage may vary, etc., etc. Use these custom recoveries at your own risk. I am not responsible for any bad things that might occur to your phone should you use these.


    Here are the download links to the trackball alternative custom recovery:

    New ("1.7.1") version:

    File size: 3,926,016 bytes
    MD5 checksum: 3217768b831a3841180699942204762d

    Old (original, "1.6.2") version:

    File size: 3,923,968 bytes
    MD5 checksum: 9ec2510f53a25658ca5d52b34b6c1524
    Always (please!) verify the checksum of this file after you download and place it on your phone.

    Please reference Amon_RA's thread over on XDA for additional details regarding this custom recovery:

    [Recovery] [17-Mar-2010] RA-eris-v1.6.2 - xda-developers


    Special thanks to:

    Amon_RA: for creating this custom recovery and providing much needed guidance to allow me to tweak his code

    Packetlss: for hosting the github and guiding me to Amon_RA

    erisuser1: for his continued guidance, knowledge, and contributions to the Android community (especially the Eris folks)

    Disclaimer: Use these custom recoveries at your own risk. As always, read carefully, be careful, and use caution when rooting and/or attempting anything discussed in this thread. I cannot be responsible for any "bad things" that might happen to your phone in the course of you using any of the information contained herein. I hate including something like this, but this is meant to give pause to any casual reader that isn't fully prepared for the consequences, intended or otherwise, related to rooting and installing a custom recovery.


    Since there are a variety of states for phones to "accept" or have custom recovery installed on it, there are a few different scenarios for installing. For a better breakdown (and source ;)) of these different scenarios, please reference this post that appears later in this same thread (thank you again, eu1!):

    | SCENARIO 1| Stock/unrooted Eris phones:

    For "stock", unrooted, HTC/VZW phones, can use erisuser1's method, use his thread's instructions but do the following steps after the section labeled Setting Things Up with a File Manager (i.e., after figure 18) and before the section labeled Rooting with Gscript Lite:

    A. Download the recovery-RA-eris-v1.6.2-trackball-optional.img file from the link above, being sure to verify the file size and MD5 sum (listed above) and transfer it to your phone's /sdcard/gscript/tools directory (that was created by the time you get to figure 18). I recommend using the free AFV (Android File Verifier) app [shameless plug :D] for checking a file's MD5 sum on your phone.

    B. Use a file manager such as EStrongs File Explorer or Astro File Manager to navigate to the /sdcard/gscript/tools directory and rename the "recovery.img" file to "old-recovery.img".

    C. Next, while you are still in the /sdcard/gscript/tools directory, rename the "recovery-RA-eris-v1.6.2-trackball-optional.img" file to "recovery.img".

    D. Continue/resume the rooting process in eu1's thread from the section labeled Rooting with Gscript Lite. It should use the new, trackball optional custom recovery.

    | SCENARIO 2| Partially rooted phones (process halted by wonky trackball):

    This scenario covers phones that were "partially" rooted--i.e., the "Universal Dummies" or "1-click" method was used to root the phone, but a ROM could not be flashed because of a non-functioning trackball. If this is the case, you should be able to follow the steps indicated in Scenario 1 above.

    If you were able to flash a ROM via some other means (i.e., ClockworkMod or manual flash via adb), then you can't use the Scenario 1 method above.

    | SCENARIO 3| Rooted phone w/non-stock ROM & 1.6.2 Amon_RA Eris custom recovery installed:

    This is for most folks that are already rooted and don't want to use their PCs and/or are not familiar with the Android SDK and using adb.

    What you'll need:

    A. Download and install the Gscript Lite app (don't run it yet):

    B. Download or transfer the file to your phone (we'll assume that you placed it in the /sdcard/download directory):

    Here is the new "1.7.1" version (see notes above) that includes the "lost" Partition sdcard menu items:

    MD5 sum of 2580f0c92f3e1e8acd9c8af1b5eae513
    File size of 3,915,425 bytes

    Here is the original ("1.6.2") version:

    MD5 sum of c04a56675c103448ff4a5cdc1b48267f
    File size of 3,914,222 bytes
    C. Extract the contents of the file to your SD card:

    Code (Text):
    1. [FONT=Courier New]Using [B][COLOR=blue]Astro File Manager[/COLOR][/B] (free in the Market), let's move [COLOR=blue][B] [/B][/COLOR][/FONT]
    2. [FONT=Courier New]from the [COLOR=blue]/sdcard/download[/COLOR] folder to [COLOR=blue]/sdcard[/COLOR] and extract its contents:[/FONT]
    4. [FONT=Courier New]A. [B]long-press[/B] the [COLOR=blue][B][/B][/COLOR] file[/FONT]
    5. [FONT=Courier New]B. [B]select[/B] [COLOR=blue][B]Edit[/B][/COLOR][/FONT]
    6. [FONT=Courier New]C. [B]select[/B] [COLOR=blue][B]Move[/B][/COLOR][/FONT]
    7. [FONT=Courier New]D. [B]press[/B] the [COLOR=blue][B]Up icon[/B][/COLOR] at in the tool bar at the top of the screen[/FONT]
    8.    [FONT=Courier New](this will navigate to the [COLOR=blue]/sdcard[/COLOR] directory)[/FONT]
    9. [FONT=Courier New]E. finally, [B]select[/B] the [COLOR=blue][B]Paste icon[/B][/COLOR] in the tool bar at the top of the screen[/FONT]
    10. [FONT=Courier New]F. [B]long-press[/B] the [B][COLOR=blue][/COLOR][/B] file and select [COLOR=blue][B]Extract[/B][/COLOR][/FONT]
    11. [FONT=Courier New]G. [B]select[/B] [COLOR=blue][B]Extract To This Directory[/B][/COLOR][/FONT]
    12. [FONT=Courier New]H. let it do its extracting thing...and then [B]exit[/B] Astro File Manager[/FONT]
    Note: If you have to re-extract the file (via Astro) and re-run the 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).

    *** Special Note for those using KaosFroyo ROMs ***
    Code (Text):
    1. [B][COLOR=red]*** Special Note for those using [COLOR=blue]KaosFroyo [/COLOR]ROMs ***[/COLOR][/B]
    3. Note: it appears that the [B]getprop [/B]command that is used in my Gscript script is
    4. not present in KaosFroyo ROMs. The [B]getprop [/B]command is used to verify / validate
    5. that you are indeed running the script on an HTC Droid Eris.
    7. Please reference the posts starting this with one
    8.  [URL][/URL]
    9. for information about how to modify my script to continue the installation of this alternate recovery (specifically this post:
    10. [URL][/URL]).
    Note: if you have problems using the above "regular" scripts, you might have to use the method mentioned below where it might be necessary to add the "busybox " command (note the trailing space char) in front of the mkdir command in the script before it will work. So, check out the instructions below if you get stymied.
    *** Special Note for CM7, GSB 2.8+ and other Gingerbread-based ROMs ***
    Code (Text):
    1. [B][COLOR=red]*** Special Note for CM7, GSB 2.8+ and other Gingerbread-based ROMs ***[/COLOR][/B]
    3. It appears that the more recent Gingerbread-based and CyanogenMod (CM7)
    4. ROMs might not support the "[B]mkdir[/B]" command in the shell that Gscript
    5. uses. So, to get around this, the [B]busybox [/B]"mkdir" command must be
    6. referenced. Please reference this post:
    8. [URL][/URL]
    10. for more information about details for getting the script to work on the
    11. GingerBread and CyanogenMod (CM7) ROMs.
    D. Launch a new Gscript Lite app instance and do the following:

    Code (Text):
    2. [FONT=Courier New][B]Launch[/B] a new [B][COLOR=blue]Gscript Lite[/COLOR][/B] instance and:[/FONT]
    4. [FONT=Courier New]A. [B]press[/B] the soft menu button[/FONT]
    5. [FONT=Courier New]B. [B]select[/B] [B][COLOR=blue]Add script[/COLOR][/B] option (lower left)[/FONT]
    6. [FONT=Courier New]C. [B]press[/B] the [B][COLOR=blue]Load file[/COLOR][/B] button[/FONT]
    7. [FONT=Courier New]D. [B]select[/B] the [COLOR=blue][/COLOR] script[/FONT]
    8. [FONT=Courier New]E. leave the [B][COLOR=blue]Needs SU?[/COLOR][/B] checkbox checked (you need root for [/FONT][FONT=Courier New]the flash to work)[/FONT]
    9. [FONT=Courier New]F. [B]press[/B] the [COLOR=blue][B]Save[/B][/COLOR] button (lower left)[/FONT]
    10. [FONT=Courier New]G. you'll now be returned to the main Gscript Lite menu and you should[/FONT]
    11.    [FONT=Courier New]see [COLOR=blue]gscript-sa[/COLOR] available at the bottom of the list of scripts[/FONT]
    12. [FONT=Courier New]H. to run the script, [B]short-press[/B] the [COLOR=blue]gscript-sa[/COLOR] script name[/FONT]
    13. [FONT=Courier New]I. you should be prompted by the SuperUser whitelist app to allow[/FONT]
    14.    [FONT=Courier New]the Gscript program to run the [COLOR=blue]/system/bin/sh[/COLOR] as root ([B]select[/B] [COLOR=blue][B]Allow[/B][/COLOR])[/FONT]
    The screens should look like this:

    gscript-sa main.JPG gscript-sa su request.JPG gscript-sa flash successful.jpg
    If you are not rooted, didn't enable the Needs SU? checkbox, or there's a problem flashing the custom recovery image, you'll see something like this:
    gscript-sa not-run-as-root.jpg

    | SCENARIO 4| Old-school :p (already rooted; Android SDK/adb-familiar):

    If you have a rooted phone, have the Android SDK installed, and are proficient / knowledgeable about using adb and flash_image, then you can follow these steps (note: I am purposely omitting some details that those familiar with this process should not need--if you need it, you probably shouldn't be using this):

    Via flash_image through adb

    A. Download the new (1.7.1) recovery-RA-eris-v1.6.2-trackball-optional.img file or the old (1.6.2) recovery-RA-eris-v1.6.2-trackball-not-required.img file from one of the links above, being sure to verify the file size and MD5 sum (listed above) and transfer it to your Android SDK's tools directory.

    B. Use adb to push the new custom recovery over to your phone's /sdcard:

    Code (Text):
    1. [COLOR=blue][B]adb push recovery-RA-eris-v1.6.2-trackball-optional.img /sdcard/[/B][/COLOR]
    C. Wait/pause 5 seconds to allow the push/transfer to complete (this data transfer actually occurs in the background via the adb service on your PC that talks to the adb daemon on your phone)

    D. Now, flash the updated custom recovery image to your phone:

    Code (Text):
    1. [FONT=Courier New][COLOR=blue][B]adb shell flash_image recovery /sdcard/recovery-RA-eris-v1.6.2-trackball-optional.img[/B][/COLOR][/FONT]
    E. Reboot into recovery to enjoy your new trackball-optional custom recovery! ;)

    Via fastboot (note: requires S-OFF bootloader)

    Also, LexusBrian400 pointed-out in this post: that you can also flash the recovery using the fastboot utility (if you have it):

    Note: a quick word of caution, courtesy of erisuser1 and excerpted (verbatim) from this post:

    If you ever use fastboot to flash things to the phone, be very very careful about md5 checksums and so forth - the one thing which is nice about the signing methodology used with ROMs and Amon_RA is that it makes it impossible to flash a corrupted ROM file - but when flashing with fastboot, no protection is provided for you, so you need to be damn sure you are working with correct and unmangled files.

    1. Make sure your USB cable is plugged-in between your phone and your PC.

    2. From a powered-off state, boot your phone into FASTBOOT USB mode by simultaneously pressing the green CALL and the red END/PWR buttons. This should take you into the FASTBOOT menu/screen. Note: if you don't have the USB cable plugged-in, the "FASTBOOT USB" (white text w/red background) will simply show "FASTBOOT".

    3. Place the alternate custom recovery image you wish to flash in the Android SDK's tools directory.

    4. Next, from your Android SDK's tools directory, flash the alternate custom recovery:

    Code (Text):
    1. fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img
    5. Here's what it will look like from the Windows (DOS) Prompt:

    Code (Text):
    1. d:\android-sdk-windows\tools>[B][COLOR=blue]fastboot flash recovery recovery-RA-eris-v1.6.2-trackball-optional.img[/COLOR][/B]
    2.   sending 'recovery' (3834 KB)... OKAY [  0.844s]
    3.             writing 'recovery'... OKAY [  1.390s]
    4. finished. total time: 2.236s
    5. d:\android-sdk-windows\tools>
    6. After the flash, press the volume-DOWN key to enter HBOOT. From HBOOT, press volume-UP to enter your shiny-new custom recovery.

    | SCENARIO 5| jcase's 1-click app, now with trackball-optional custom recovery:

    I finally received permission from jcase to re-pack his Eris 1-click app to include the trackball-optional recovery. This version is identical to his original--I simply replaced the file containing the original Amon_RA custom recovery with the trackball-optional version.

    You can use this version to root or re-root a stock Sense Eris (which should also include those running Sense-based ROMs such as xtrSENSE, and some of the very old, original Eris ROMs). If you are already rooted, you don't need to re-root (i.e., you don't need to re-flash the file), you just need to re-run the app as you normally would in order to get the special trackball-optional Amon_RA custom recovery installed.

    I also think that this app will work if you already have the original Amon_RA custom recovery installed and you need to replace it with the trackball-optional one.

    MD5 sum: 15763b51cf707c027cc73bc117e1fc39

    I won't repeat the installation instructions here, but instead will point you towards both of jcase's threads (here at AF and over at XDA):

    Universal 1 Click Eris Root App Apk - No PCs, No Scripts Needed, EASY - xda-developers

    If you are simply replacing your custom recovery with the trackball-optional one, then you basically just run steps 1-3.

    I would also urge you to honor the spirit of jcase's threads regarding donations to help-out those less fortunate. All credit to jcase and his team for creating this app that has helped so many people.

  2. doogald

    doogald Guides Guide

    I wish I could hit the thanks button many times for this. Great work!
  3. scary alien

    scary alien not really so scary Moderator

    No problem :)...and thank you too for all that you do around here for all of the Eris folks!

    I'm just imagining the time when we'll have a cascade of folks whose trackballs have gone kaput and they will give up root or upgrade to a new phone when they don't have to.

    This was a fun and pretty challenging project...I've learned more than I ever expected to...;).

    I hope to finish getting this coded and tested tonight or tomorrow...the testing cycle is a bit of a challenge since I can only actually test by flashing a new recovery.

    LexusBrian400 and MrDangerous like this.
  4. Podivin

    Podivin VIP Member VIP Member

    Very cool Scary. Congrats on pulling it off! :)
  5. scary alien

    scary alien not really so scary Moderator

    You are very welcome! :cool: Thank you!
    LexusBrian400 likes this.
  6. scary alien

    scary alien not really so scary Moderator


    I've updated the first post above with information about the changes I've tested and got working tonight.

    I've got this working:

    - an alternative to the trackball scroll-up (volume-UP)

    - an alternative to trackball scroll-down (green Call button)

    - an alternative to trackball-press select/confirm (red End/Power button)

    I was working with hoban_eris over at XDA to try to include a patch to the base code to allow for file selection to occur from places other than the /sdcard path. Unfortunately, we've got a version mis-match or something and we're having trouble getting this in. This doesn't mean that I will stop working on this, mind you... I can still try to (and might have to) incorporate it manually (instead of a code merge).

    I'll try to finish documenting and posting this (hopefully) by tomorrow evening. If you really can't wait, shoot me a PM and I can email you the new custom recovery image (its pretty sweet, I must say :D).

    LexusBrian400 likes this.
  7. scary alien

    scary alien not really so scary Moderator

    Okay...the new version is ready for download (link provided in the first post above).

    This version should operate identically to Amon_RA's original 1.6.2 Eris custom recovery, except that three new, alternate buttons/keys are supported for menu navigation and selection/prompt confirmation (i.e., as an alternative to using the trackball -- which is still supported for those with working trackballs). See details above.

    I have not yet written-up instructions for installing this on your phone. Many of you had your custom recovery automatically installed via the jcase's 1-click or erisuser1's universal root methods, so you did not have to mess-around with installing the Android SDK or having to use adb (or encountering issues regarding USB drivers).

    One step at a time...:p ;) :D

    Thanks and enjoy!
  8. varkie

    varkie Well-Known Member

    thanks scary. flashed it using fastboot and it works perfectly. nice to have an amons recovery thats usable again.
  9. knitpurlgurl

    knitpurlgurl Well-Known Member

    Ya, I used the universal 1-click root method so this is a little over my head. Still learning.. But tweaking Amon's is AMAZING! Just months ago, I couldn't root because I had a bum trackball. I did finally get a refurb phone from Verizon. So this would've been terrific. Now, if I can learn how to put it on my phone in case my trackball ever goes kaput again, that will be something. Like I said, I'm still learning.. ;)
  10. scary alien

    scary alien not really so scary Moderator

    You are very welcome! (now, you won't have to go back to ClockworkMod :D).

    Yeah, I won't say it was easy because there was so much that I had to learn and figure-out (the journey was very educational ;)), but I got the missing pieces of the puzzle (thanks to Amon_RA) on Sunday and was very excited.

    I'll try to figure-out something for making flashing this a little less painful.

    LexusBrian400 likes this.
  11. doogald

    doogald Guides Guide

    We can probably work something up from the Rooting for Dummy's gscripts procedures?
  12. scary alien

    scary alien not really so scary Moderator

    I was thinking along these same lines too...I was wanting to have eu1 weigh-in on things before suggesting this since he's The Man regarding the example thread re. this (he might want to simply make an alternative script to reference the new file?) and I'm sure he will have some good ideas re. this.

    I also do have jcase's 1-click root app project (that he kindly shared with me) that could be modified, but I would have to discuss this with him since its his baby and I don't want to hijack his app or methodology.

    I'm still trying to catch my breath from a busy weekend trying to get this all done (I didn't get my "aha!" moment until mid Sunday afternoon when Amon_RA kindly replied to my email with the information that made me understand how all the pieces fit together (it makes sense now, of course ;))). This was after being up until 5 AM due to having to do some DST tasks for work. Then, I was up late Sunday night trying stuff when I finally got things to start working. I was a little excited :D.

    In the mean time, I guess I could simply republish the manual, SDK/adb method for folks that might need it? What do you think?
    LexusBrian400 likes this.
  13. doogald

    doogald Guides Guide

    Oh my gosh, did I really type "Dummy's" and not "Dummies"? Somebody besides you is sleep-deprived.

    I know that EU1 is away, so that's why I suggested one of us could do it for now. That said, it can definitely wait. That said, I think it might be useful to work up a single script that can install the new recovery for everybody who already has root and the existing Amon's but who have trackball problems.

    I think showing the "old" way is just fine, but still requires people to install the SDK and all of that stuff and it may be better to avoid that. I'm figuring that anybody who can install the SDK without help can manage getting the new recovery installed without help as well...

    I don't think that I'll get time for this until tomorrow night; maybe tonight, though.

    (This seems like a good template, by the way, now that I think about it more: xda-developers - View Single Post - [HOW-TO] Safely Switch Back To Amon From Clockwork Recovery)
  14. scary alien

    scary alien not really so scary Moderator

    Lol, I fixed my post where I quoted your reply :D.

    Just to throw more fuel onto the fire is the set of changes that hoban_eris suggested/provided that he got from Koush's ClockworkMod recovery that would allow custom recovery to navigate to any directory to search for files to flash instead of requiring that they be put in the top-level of the /sdcard. It'll take me some time to try to incorporate this, but will yield yet another version of this recovery :eek: (but a good problem to have, eh?).

    Ooo! That's a good link for an excellent example for flashing recovery--I looked for something like this last night, but found way too many examples. The one you posted is pretty good.

    So much to do, so little time! [and I still haven't gotten time to watch Monday night's espisode of "House" :p]

    LexusBrian400 likes this.
  15. knitpurlgurl

    knitpurlgurl Well-Known Member

    Good golly.. I feel lucky I know how to turn my phone ON. :eek: ;)
  16. scary alien

    scary alien not really so scary Moderator

    Lol! Hey, by the way, nice avatar you made, kpg :D :) -- I like it!


    for anyone reading this: this is a temporary / test table that I'm trying to see if I can load-up paid app package information to help me with a Java app I'm writing to help identify ROM that included paid apps (that shouldn't)

    sa-314159-package: com.keramidas.TitaniumBackupPro # Titanium Backup PRO Key
    sa-314159-package: com.speedsoftware.rootexplorer # Root Explorer
    sa-314159-package: com.aurorasoftworks.quadrant.ui.advanced # Quadrant Advanced
    sa-314159-package: com.quoord.tapatalkpro.activity # Tapatalk Forum App
    sa-314159-package: com.mhuang.overclocking # SetCPU for Root Users
    sa-314159-package: com.mseven.msecure # mSecure Password Manager
    sa-314159-package: # Nova Launcher Prime
    sa-314159-package: sa.afv.donate # AFV - donate
    sa-314159-package: sa.battmonx.donate # BattMonX - donate
    sa-314159-package: com.rcreations.WebCamViewerPaid # IP Cam Viewer Pro
    sa-314159-package: com.jrummy.liberty.toolboxpro # ROM Toolbox Pro

    note: SetCPU is available for free on XDA for members, but is not supposed to be included in ROMs per dev's request (
    LexusBrian400 likes this.
  17. knitpurlgurl

    knitpurlgurl Well-Known Member

    {Giggle} Thanks! :D
  18. scary alien

    scary alien not really so scary Moderator


    I spent a little time Wednesday night looking at eu1's Gscript scripts used in his Universal Root thread regarding evaluating methods for people to flash an alternate (new) custom recovery. It got me thinking about the scope of creating a method for people to easily "update" their custom recovery.

    Since the custom recovery is typically installed as an integral part of the rooting process, this almost makes developing a "method" equivalent to duplicating the efforts aleady in-place (by eu1, jcase, surgeon0214, old-school method, etc).

    I see a couple of different scenarios / issues to keep in mind:

    1. method (SDK/adb/USB, Gscript, custom app, other)

    Clearly, a custom, 1-click type app would be most desireable with an eu1-like Gscript method very close behind. Those with the knowledge and skill using the Android SDK/adb.exe and a USB connection are already set.

    2. current root state (unrooted, root w/S-ON HBOOT, root w/S-OFF HBOOT)

    I'm unclear as to whether the eu1's or jcase's root method (using wag3slav3's exploit) that's been already used on a phone is relevant to how next to proceed. I mention this because I can simply use the flash_image utility to re-flash my custom recovery without having to tweak the security of the mtd1 partition like the root-leak methods do...(I suspect that this is directly related to whether or not one has an S-OFF HBOOT--which is what I have).

    If the S-ON HBOOT phones still need to re-do the mid.txt symlink exploit each time to resecure mdt1, then they would basically need to re-do all of the rooting steps up to just the installation of the custom recovery.

    If the S-ON HBOOT phones can simply use the flash_image utility, it should be fairly straightforward to either build a simpler (one-step) Gscript script (or even an Android app) to do this.

    I rooted the old-school way, so I have an S-OFF HBOOT and am a little leery of reverting to S-ON, but I'm betting eu1 (or maybe yourself) can very easily and eloquently clear-up the confusion. ;) Any ideas?

    Thanks and cheers!
    LexusBrian400 likes this.
  19. erisuser1

    erisuser1 Well-Known Member

    Look out, St. Jude!

    There's a new Patron Saint of Lost Causes in town - his name is scary_alien!

    But seriously - nice work; the trackball-challenged Eris owners will be forever in your debt.

    As far as the installation of your custom patch of Amon_RA goes,

    (1) For people with "stock" HTC/VZW phones, merely replacing the "recovery.img" file in the gscript/Dummies method (with your version of the recovery) would get it installed. I haven't unpacked jcase's OneClick app to see if it stores the recovery.img file as a resource - but if so, you could simply replace it with yours and resign... with permission of jcase and his crew, of course.

    (2) For people with previously rooted phones (Dummies or One-Click), but still with a stock HTC O/S, the same thing applies - a modified version of Dummies or One-Click will work to install your version of Amon_RA's custom recovery. The dependencies of those rooting methods are primarily upon the "init.rc" script in the stock boot partition (boot.img) - so you can't "reroot" (e.g. with OneClick) with any old ROM, but if you still have a "stock" OS and boot partition, you can "re-root". Obviously, this case would only apply to those folks that performed the initial process of rooting using either method, and then gave up when they discovered that they had a trackball that Amon_RA was not happy with.

    (3) The third case - a rooted phone with a non-stock ROM and the original v1.6.2 Amon_RA (for the Eris) installed, you could simply create a gscript method using "flash_image" as you suggest. The script would need to run as root under the OS, but there's no problem doing that with a rooted phone, right?

    As to your question about /dev/mtd/mtd1 - it is a volatile file system that is recreated on each boot, but also you wouldn't need to "chmod" it if you are already running as root - the whole symlink/chmod nonsense happens during the rooting exploit so that an unprivileged user can write a file to /dev/mtd/mtd1. (The symlink is created at /data/local/rights/mid.txt that points at /dev/mtd/mtd1 because it is known that a "chmod 777 /data/local/rights/mid.txt" command happens in the stock boot image's "init.rc" file - and that process is running as root).


    scary alien likes this.
  20. scary alien

    scary alien not really so scary Moderator


    Welcome back from your brief hiatus and thank you very much for the kind words--I very much appreciate them.

    I also appreciate you (yet again ;)) lifting the fog on (at least my) confusion regarding what is might take to make this more widely available to those that might want or need it. That helped me a lot.

    You are correct about jcase's 1-click app: it does indeed include a copy of Amon_RA's 1.6.2 recovery.img. I have not yet contacted jcase regarding tweaking his app since I am actively working on a few additional tweaks and I didn't want to bother him prematurely. His app has really been education for me, not just in helping me create the AFV app, but in looking at it again this week I learned some things I didn't know before--pretty cool, jcase!

    I also didn't want to hold-off (releasing the initial version) with the changes I'm working on now, since I wanted to make my first version with the trackball alternative keys available to those that needed it (I've already heard from a few happy users of this new version).

    I'll try to write-up some installation instructions that cover the above scenarios that you so kindly outlined:

    For #1, I'll contact jcase (hopefully soon) and see what we can do.

    For #2, if you don't mind, I can simply reference your Universal thread and provide instructions on how / when to replace the recovery.img that comes with your file (i.e., after figure 18, replace recovery.img with a new one).

    For #3, like you indicated, it should be fairly-straightforward to create a Gscript package to do the flash_image thingy :p. I haven't played too much with Gscript, but this should be a fun thing to do and your examples will certainly make this a much easier task.

    Thank you again! Cheers!
  21. starflorida

    starflorida Active Member


    Droid Explorer has an option for flashing recovery, will it work for this?

  22. scary alien

    scary alien not really so scary Moderator

    I'm not familiar with Droid Explorer...if it "knows" about the Eris and you can/get to specify the custom recovery .img file, you should be able to.

    I'll have to check in to this...

    I'm going to start writing-up the installation instructions this evening...

    Can you tell me how you rooted? I might be able to get you going with this if you really need it...


    edit: okay, now I remember...Droid Explorer is a PC-based tool...never used it, but I'll look over how it might fit into this...thanks! :)
  23. starflorida

    starflorida Active Member

    My tracball works.

    Just thought it might help others.

    (Droid Explorer)


    scary alien likes this.
  24. scary alien

    scary alien not really so scary Moderator

    Aha! I thought you might just be trying to be helpful ;). I appreciate that.

    After I saw your reply, I did a quick Google search and realized that I had heard of the app before. I might try downloading and installing it to see if this might be easier for people to use.

  25. starflorida

    starflorida Active Member

Share This Page