Root Amon_RA 1.6.2 Custom Recovery: trackball not required!

[scary alien]

Excellent, I would love to see what he has to say.

Tomorrow I am going to try running this again on the new mod, as I do hope to get it figured out someday.

Thanks very much for your help, it has been a pleasure
See you around, I really like this community and am hoping to get into some Application Development soon

You are very welcome...I just wish things would have worked "out of the box" for you, but then we wouldn't have gotten to have all this "fun", eh?

I've written a couple of apps...its a fun and interesting hobby...I just wish I knew Java programming and Android a little better. Its like laundry and the dishes, LOL, I'll never be "done" with it since there'll always be something new to learn.

AF would certainly benefit from any of your contributions, app development included. One of our Guides is putting together a new FAQ thread for app development with lots of good stuff in it (not sure when he's going to post it, but I'll be sure to PM you when I find out).

Cheers and have a great rest of your night .

 

[wolfdog54]

You are very welcome...I just wish things would have worked "out of the box" for you, but then we wouldn't have gotten to have all this "fun", eh?

I've written a couple of apps...its a fun and interesting hobby...I just wish I knew Java programming and Android a little better. Its like laundry and the dishes, LOL, I'll never be "done" with it since there'll always be something new to learn.

AF would certainly benefit from any of your contributions, app development included. One of our Guides is putting together a new FAQ thread for app development with lots of good stuff in it (not sure when he's going to post it, but I'll be sure to PM you when I find out).

Cheers and have a great rest of your night .

You as well, thanks. And yes, of you wouldn't mind popping me a PM if he does release the guide, that would be great!

Have a great night!

 

[erisuser1]

I'm a little suspicious that there might be bad blocks in your custom recovery partition , but let's not get ahead of ourselves (and I'm not the one to guide you regarding attempting to fix that--we'll need our "root Godfather" (erisuser1 / bftb0) for that).

Anything is possible, but it seems a little unlikely. The flash memory layout of the Eris has the recovery partition at 40 eraseblocks (128 kB each), or 5,242,880 bytes.

The sizes of the recovery images that you posted here - all of which are just under 75% of the partition size, implies that wolfdog54 would need to have a recovery partition with over ten bad eraseblocks (more than 25%) - that seems pretty unlikely.

I think you've already come to this conclusion, though.

I didn't read through the whole sequence of posts starting with wolfdog54's first post (I'm suffering from the TLDR syndrome this morning), so I'm not really sure of the state of the phone - despite the lack of a functioning recovery, does it still have a bootable ROM on it? If so (you might have already gone down this route), if there is a rooted ROM on the phone, using flash_image (from Amon_RA v1.6.2) could be used to attempt to re-flash the factory recovery. That would be a simple test to see if there is a flashing problem. It might also be worthwhile to flash the misc partition with jcase's "flash any RUU" - doing that alone might clear up recovery bootability issues, but also open up the door to flashing the Root PB00IMG.zip file to get the S-OFF bootloader onto the phone. If nothing else, that would allow "soft booting" of any recovery desired (via fastboot), even if problems with hard-booting a custom recovery persisted.

cheers

eu1

 

[erisuser1]

whoops - I got up the gumption and read back a little ways. I see that wolfdog54 is booting the Amon_RA (original?) v1.6.2 recovery, and also has a working ROM, so no need to muck things up further, I suppose ... so long as his trackball works in recovery. (I didn't read back far enough to figure out whether he got started on this path in the first place because of a bad trackball).

eu1

 

[scary alien]

eu1,

Thank you for the reply.

Well, wolfdog54 is up and running okay...he did have xtrSense 5.0.1 initially installed and his phone was operating okay, outside of the inability to flash the trackball-optional recovery.

He is very savvy and computer literate and had no problems installing the SDK and using adb to manually wipe/flash, etc. a new ROM via adb through a freshly-installed version of the original Amon_RA custom recovery using jcase's 1-click app.

So, he's all-good...I was just trying to figure-out a reason for the skating Androids issue when he booted into a freshly flashed version of my recovery.

I'll try re-packing jcase's 1-click app first to see if that makes any difference. Then, I might run the "flash any RUU" thing to try to get the S-OFF bootloader so we can use FASTBOOT like you mentioned.

Thanks again!

 

[scary alien]

whoops - I got up the gumption and read back a little ways. I see that wolfdog54 is booting the Amon_RA (original?) v1.6.2 recovery, and also has a working ROM, so no need to muck things up further, I suppose ... so long as his trackball works in recovery. (I didn't read back far enough to figure out whether he got started on this path in the first place because of a bad trackball).

eu1

LOL...yeah, I knew you wouldn't be able to resist a mystery .

Yeah, I think he was led here because of a wonky trackball, but he can successfully flash and boot into the original Amon_RA 1.6.2 recovery via the 1-click app... Just strange to me that he can't boot into my versions...

But he's obviously proficient in following your directions from the ppbb thread (mentioned a few posts up) where you laid-out how to flash via adb while custom recovery was booted.

Thanks!

 

[scary alien]

wolfdog54,

Okay, got one more thing for you to try, if you are game.

I've re-packed jcase's 1-click Eris rooter to include my trackball-optional version of the custom recovery.

https://sites.google.com/site/scaryalienware/downloads/one-click-tbo.apk

MD5 sum: 15763b51cf707c027cc73bc117e1fc39

(feel free to use my AFV app to check the above MD5 )

After downloading to your phone, you should be able to single-click it from Astro File Manager and choose "App Manager" and then install.

Now, I flashed xtrSENSE 5.0.1 to test this and I was able to flash the original and my trackball-optional custom recovery back and forth using jcase's original 1-click rooter and the .apk (above).

I might have steered you astray in some of the posts above where I had you use Quickboot to do the reboot after running the 1-click app instead of actually powering-off the phone. I had a little trouble getting this to work until I actually started powering-down after running the app.

Anyway, make sure you've un-installed the old 1-click version before running this one (you'll actually have to since it won't allow you to install an app with an identical package name).

I don't know for sure that this will work on CM7 like I know you've got currently installed, but it won't hurt to try...

Oh, two last things:

1. Here's the link to the developers FAQ that I mentioned before:

http://androidforums.com/application-development/377722-welcome-start-here-faqs-tips-learning-resources-tutorials-helpful-threads.html

2. If you still can't get the trackball-optional recovery to install, we can pursue getting you the engineering bootloader installed to give you S-OFF so you can use the FASTBOOT utility to help you try to install the custom recovery.

Cheers and let me know if you have any questions.

 

[scary alien]

Little self-thread bump...

I've updated the first post to include a "Scenario 5" installation method...I finally and kindly received permission from jcase to re-package his 1-click app to include the trackball-optional custom recovery.

Hopefully, this should give at least one other option for helping-out those with Eris trackball issues.

Cheers!

 

[doogald]

Little self-thread bump...

I've updated the first post to include a "Scenario 5" installation method...I finally and kindly received permission from jcase to re-package his 1-click app to include the trackball-optional custom recovery.

Hopefully, this should give at least one other option for helping-out those with Eris trackball issues.

Cheers!

Pity we cannot hit thanks multiple times...

 

[CondemnedSoul]

Pity we cannot hit thanks multiple times...

I agree.

 

[scary alien]

Pity we cannot hit thanks multiple times...

I agree.

Thanks guys! I appreciate the sentiments... You guys deserve a ton of credit sticking-around with all of us, even with our ever dwindling numbers.

If anything, I've keep finding new stuff to do with my Eris now that I'm not reliant on it like before.

This past week's fun with Scotty makes me want to build my own ROM someday...(when I find a little more time...that's really the precious commodity, eh?).

Cheers!

 

[scotty85]

Pity we cannot hit thanks multiple times...

I also agree... it certainly doesn't get much easier than simply running the one click app

 

[prj]

Little self-thread bump...

I've updated the first post to include a "Scenario 5" installation method...I finally and kindly received permission from jcase to re-package his 1-click app to include the trackball-optional custom recovery.

Hopefully, this should give at least one other option for helping-out those with Eris trackball issues.

Cheers!

I've done scenario 5 twice already. I can't get the trackball optional recovery to work. It keeps the old one after I install the APK and run one click root program.

 

[scary alien]

I've done scenario 5 twice already. I can't get the trackball optional recovery to work. It keeps the old one after I install the APK and run one click root program.

prj,

The 1-click app is a little finicky (even for me when I was testing it...).

Did you:

1. Install the app
2. Run the app and click "accept"
3. Immediately after doing the "accept", power down the phone and reboot (don't use a reboot app like Quickboot).

When the reboot happens, the alternate recovery should be flashed.

If you look at this post by eu1, you'll see that there are some circumstances in which this app might not re-"root" a phone:

http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required.html#post1874718

(not sure exactly why this is, but I know enough to trust eu1 ).

If scenario 5 won't work for you, there are others for you to try, too (although they aren't quite as simple as the scenario 5 alternative).

If you do get it to work, please let us know.

In either case, it would also be helpful to know how you rooted (i.e., do you have an S-OFF HBOOT), which rooting method, and are you running a custom ROM (if so, which one?), so that I can start cataloging which options might not work for certain ROMs (certainly with respect to scenario 5).

Thanks!

 

[prj]

prj,

The 1-click app is a little finicky (even for me when I was testing it...).

Did you:

1. Install the app
2. Run the app and click "accept"
3. Immediately after doing the "accept", power down the phone and reboot (don't use a reboot app like Quickboot).

That's exactly what I did.

When the reboot happens, the alternate recovery should be flashed.

If you look at this post by eu1, you'll see that there are some circumstances in which this app might not re-"root" a phone:

http://androidforums.com/eris-all-t...overy-trackball-not-required.html#post1874718

(not sure exactly why this is, but I know enough to trust eu1 ).

Looked at it. Option 3 is where I am at, but I get lost in the rest of that paragraph.

If scenario 5 won't work for you, there are others for you to try, too (although they aren't quite as simple as the scenario 5 alternative).

If you do get it to work, please let us know.

In either case, it would also be helpful to know how you rooted (i.e., do you have an S-OFF HBOOT), which rooting method, and are you running a custom ROM (if so, which one?), so that I can start cataloging which options might not work for certain ROMs (certainly with respect to scenario 5).

Thanks!

I tried Scenario 3 numerous times in that post and could never get it to work.

I rooted using 1 click root from the market. Close to 2 years ago. I have no idea what S-OFF HBOOT means????

I am using Ginger Tazz 18

 

[scary alien]

That's exactly what I did.

Looked at it. Option 3 is where I am at, but I get lost in the rest of that paragraph.

I tried Scenario 3 numerous times in that post and could never get it to work.

I rooted using 1 click root from the market. Close to 2 years ago. I have no idea what S-OFF HBOOT means????

I am using Ginger Tazz 18

prj,

Since you use the 1-click app, I'm guessing that you had previously installed one of the 2.1 leaks and would have had an S-ON (security "on") bootloader (vs. rooting with the original method of the leaked, base root ROM which had an S-OFF bootloader that would give you a few more installation options (like using the fastboot commands)).

Okay, that helps... I'll load-up Ginger Tazz on my phone and see how the app behaves for me and I'll get back to you.

 

[scary alien]

prj,

Okay, well, I also tried Ginger Tazz with the one-click-tbo app and it doesn't work for me either... ...

Clearly, this is one of those "non-Sense" ROM references that eu1 was talking about, so I'll have to dig-in a little more to at least understand the reasons why this doesn't want to work.

The good news is that the "Scenario 3" method should work for you...I tested this and you'll have to make sure you replace your gscript-sa.script with an updated version as discussed in the section labeled *** Special Note for GSB 2.8+ ROMs *** since it looks like the Ginger Tazz ROM also does not natively support the mkdir command.

There's a new version of the gscript-sa.sh script in this post:

http://androidforums.com/eris-all-things-root/214240-amon_ra-1-6-2-custom-recovery-trackball-not-required-4.html#post2594769

Its really identical to the one that you load when you set things up, its just got a "busybox " command (note the space character, too) in front of the mkdir command in the script.

It might just be easiest for you to follow the Scenario 3 directions, and when you do the "Load file" and select the gscript-sa.sh script, use the mini-editor in Gscript Lite, scroll-down to the mkdir command and insert "buysbox " in front of that command (so it looks like "busybox mkdir ..."). Here's the code snippet for how it should look before and after:

before:

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

after:

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

Good luck...(its worth the extra effort, eh? ).

Cheers!

 

[prj]

prj,

Okay, well, I also tried Ginger Tazz with the one-click-tbo app and it doesn't work for me either... ...

Clearly, this is one of those "non-Sense" ROM references that eu1 was talking about, so I'll have to dig-in a little more to at least understand the reasons why this doesn't want to work.

The good news is that the "Scenario 3" method should work for you...I tested this and you'll have to make sure you replace your gscript-sa.script with an updated version as discussed in the section labeled *** Special Note for GSB 2.8+ ROMs *** since it looks like the Ginger Tazz ROM also does not natively support the mkdir command.

There's a new version of the gscript-sa.sh script in this post:

http://androidforums.com/eris-all-t...ery-trackball-not-required-4.html#post2594769

Its really identical to the one that you load when you set things up, its just got a "busybox " command (note the space character, too) in front of the mkdir command in the script.

It might just be easiest for you to follow the Scenario 3 directions, and when you do the "Load file" and select the gscript-sa.sh script, use the mini-editor in Gscript Lite, scroll-down to the mkdir command and insert "buysbox " in front of that command (so it looks like "busybox mkdir ..."). Here's the code snippet for how it should look before and after:

before:

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

after:

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

Good luck...(its worth the extra effort, eh? ).

Cheers!

Thanks SA. I will try that tonight and see how it goes.

 

[prj]

Alright!!! I did scenario 3 and inserted busybox in front of mkdir. Worked perfect. Thanks SA!!!

Stupid trackball.

 

[scary alien]

Alright!!! I did scenario 3 and inserted busybox in front of mkdir. Worked perfect. Thanks SA!!!

Stupid trackball.

LOL, prj, you are most welcome!

Glad it worked for you...

Cheers and have a great rest of your day!

 

[tproctor]

SA, you also have to do the Busybox command with CCM7. I found out the hard way after beating my head against the wall for a few days on my wife's phone.

 

[scary alien]

SA, you also have to do the Busybox command with CCM7. I found out the hard way after beating my head against the wall for a few days on my wife's phone.

LOL, thanks and sorry you had to go through that ...

I'll make a note that if the "regular" Gscript doesn't work to try the "busybox " tweak.

Thank you, tproctor, for the heads-up!

Cheers and glad this helped you out.

 

[roscuthiii]

Hey Scary, long time no type. Hope all is going well.

My gf has finally killed the trackball on her Eris, no longer scrolls left and is pretty insolent when it comes to the other directions as well and I've managed to talk her into letting me have at her phone to make it me own little playland.
Well, I was just wondering about that qualifier where you said you think it will work with the old Amon_Ra Recovery already installed. Willing to go out on a limb and say it's a definite or is hot or miss?
Was also curious about scenario 3 if 5 is a crap-shoot... will the script work if I have Script Manager, or must it be used in conjunction with GScript?

Thank you and hopefully you're still monitoring this thread. It's been a while since I've had to do anything other than flash updated ROM's that I can't really remember how I did anything before. :-(

 

[scary alien]

Hey Scary, long time no type. Hope all is going well.

My gf has finally killed the trackball on her Eris, no longer scrolls left and is pretty insolent when it comes to the other directions as well and I've managed to talk her into letting me have at her phone to make it me own little playland.
Well, I was just wondering about that qualifier where you said you think it will work with the old Amon_Ra Recovery already installed. Willing to go out on a limb and say it's a definite or is hot or miss?
Was also curious about scenario 3 if 5 is a crap-shoot... will the script work if I have Script Manager, or must it be used in conjunction with GScript?

Thank you and hopefully you're still monitoring this thread. It's been a while since I've had to do anything other than flash updated ROM's that I can't really remember how I did anything before. :-(

Yep, still here!

Your installation method depends on what ROM is installed... Is her Eris running stock or what ROM is is running?

I don't know anything about Script Manager but it sounds similar to Gscript...(the Gscript methods are pretty straight-forward--there's just lots of details for folks that needed a little more guidance, so it should be pretty easy for you).

Lemme know...

Cheers!

 

[roscuthiii]

Basically, just what I have running for now, GSB and the original Amon_Ra... figured if I made hers a clone of mine I could take some chances I wouldn't normally take. But, I tend to proceed with caution.

Guess I could always just take a shot with the script... it's not like it'll cause Global Themal Nuclear War if it's not compatible right? (fingers crossed)

In retrospect... I could have saved myself a heap of time if I'd just put the trackball optional recovery on hers from the get go. New work schedule - sleep deprived.