yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] jr313:
reflash the newest CWR after it updates back out RM and go right back in and itll be highlighted
[Thunderbolt Android Development] fixxxer2008:
do you have the payed version of rom manager?
[Thunderbolt Android Development] jr313:
I do have premium i didnt know that would make a difference, but yes.
[Thunderbolt Android Development] yareally:
Nope, I do not.
[Thunderbolt Android Development] fixxxer2008:
i got it now, hell yes!

who ported this?
[Thunderbolt Android Development] jr313:
I would guess either Kush or the man himself brought it over for us.
[Thunderbolt Android Development] yareally:
If you really need a screenshot...
[Thunderbolt Android Development] Nate14:
I'm trying now.

Edit:

Hey it worked! The recovery is awesome. Just like the good 'ol days.
[Thunderbolt Android Development] oc3rulz:
i had used Amon_RA since my G1 days, wow this brings back memories. Then I used his Nexus One Playstation recovery to jailbreak my PS3. goodtimes
[Thunderbolt Android Development] fixxxer2008:
this recovery works great and is super fast. i love whoever ported this!
[Thunderbolt Android Development] bond32:
Since everyone can't contain their excitement, I guess I will try it :P

What makes this better than CWR?
[Thunderbolt Android Development] fixxxer2008:
faster, wipes properly and its amons! :D
[Thunderbolt Android Development] yareally:
number of complaints about amon_ra not working < complaints about cwr not working
[Thunderbolt Android Development] fixxxer2008:
this recovery is just like i had on my evo, i love it!
[Thunderbolt Android Development] Nate14:
It's what I used while learning all about Android. The Thunderbolt was the only phone that I had to use Clockwork with. So pretty much just preference for me.
[Thunderbolt Android Development] BurnOne77:
Sweet dl'ing now, never used anything but cwm, booting into it now :D
[Thunderbolt Android Development] thunderbread:
This is amazing.
[Thunderbolt Android Development] reuuin88:
Why does it say, dangerous!!! Before /wipe system? Under other. I routinely wipe system during fresh flashes. Just curious. I was using teamwins recovery port, this seems equivalent if not better.
[Thunderbolt Android Development] fixxxer2008:
just be aware some zips will not flash unless you toggle off verification. you may need to sign them before use, clockwork uses a different signing method than amon.
[Thunderbolt Android Development] jawonder:
I wanna try this new recover but just wanna make sure i have it clear. When i flash this RA_GNM recovery in rom manager i can't restore any backup i did with clockwork, right ?. I can do backups with this new recovery and restore them with this new recovery ,right ?. If i want to go back to CWM recovery it will be in rom manager for me to flash and go back to, right ? . When i go back to CWM recovery i can still use the backups i did with clockwork before i switch to RA_GNM, right ?.
[Thunderbolt Android Development] himmelhauk:
I don't see what makes this so much better than CWR. It looks about the same, albeit with some different ways to get to the same methods like with wiping and stuff. I've never used Amon, so I'm curious what exactly makes it just so much better? Someone said about it being faster, but it never seemed like CWR was slow to me, nor have I ever had any problems with it. Just wondering :)
[Thunderbolt Android Development] wrich73:
That is correct. If you flash through bootloader/recovery RA is a lot more consistent than CWM, I used it on my EVO and never, ever had a failure.

If you use the Clockwork Mod app to flash/reboot just stick with that, but if you like doing it manually you may be happier with RA.
[Thunderbolt Android Development] ibsk8:
This is my first attempt at using a different recovery. I flashed amon with no problems. Booted to amon no problems, created a backup, no problems.

Its definitely fast.

It looks the same and acts the same as clockwork. Ill probably go back to clockwork because its more widely used and most zips are compiled with cwm in mind. So until amon or twrp are used more readily cwm is the safest course.

I don't want to do to much testing invade something does go wrong, I have no computer to fix anything.

I'm going to try and restore some things
[Thunderbolt Android Development] jawonder:
I never use the app other than for flashing a new recovery i do everything Manually.
[Thunderbolt Android Development] ibsk8:
This may be obvious but it took me a minute to find.

Backup images are saved to /sdcard/nandroid
[Thunderbolt Android Development] jawonder:
Anyone using BootManager with this recovery ?.
[Thunderbolt Android Development] oc3rulz:
Honestly back in the Amon_Ra blew CWM out of the water, it was the only one that could partition SD Cards from recovery, which is a TOTAL UTTER NIGHTMARE otherwise, when we were on the G1. It also was first to mount, USB-MS Toggle, and then the others grabbed on.

Rooting was done through the console on the phone and everything was manually done. I have never been an automatic guy and since I learned to use adb and console on the G1, i don't ever use automatic backups or anything, always power down, then enter bootloader, then recovery, to avoid all the reboot errors.

I am sure that CWM, Amon and TWRP are all very close, but they all got their start from one recovery, Amon_RA, that's for sure. I for sure appreciate the person who ported this, cause they did some serious work!!!
[Thunderbolt Android Development] ibsk8:
Been playing around with amon recovery and now stuck at the splash screen. I was converting a cwm backup to amon recovery and now stuck at the splash screen.

Here's what I did.

Flashed amon recovery created a backup of current rom cm7.

Booted to cm7

Flashed back to an older recovery of cwm

Booted to recovery, (cwm). Restored a backup.

Booted bamf

Flashed back to amon recovery

Rebooted recovery (amon)

Created a backup of rom with amon

Tried to restore initial rom (cm7) and it hangs at the splash screen.

Tried wiping and then restoring with no luck.

So I tried restoring another backup

Restored the bamf backup fine.
[Thunderbolt Android Development] GreginNH:
What exactly does that mean? How do you toggle off verification and /or sign a zip?

I want to try this, used it on my Eris and i loved it.....have gotten used to CWR but would love to go back to Amon
[Thunderbolt Android Development] xXJay_RXx:
Oh hell yes.....
[Thunderbolt Android Development] fixxxer2008:
clockwork uses edify scripting and amon does not. this recovery isnt for everyone but i used it all the time on my hero & evo, i missed it.
[Thunderbolt Android Development] GreginNH:
So we can make backups and flash any of the ROMs being built for the TB still, correct?
[Thunderbolt Android Development] fixxxer2008:
unzip this to your android sdk/ tools folder. take your existing zips for roms and kernels/themes and put them in the folder. rename them "update" and hit the sign batch file, it will sign the zips properly. it will create a signed.zip and then you can rename it and flash away. :D

sign them one at a time only!

enjoy!
[Thunderbolt Android Development] fixxxer2008:
yes, use the signer i attached above.
[Thunderbolt Android Development] ibsk8:
As for thoroughness of operations in can not comment.

The speed of the recovery in both backup and restore operations is blazing fast.

Took a little over a minute to restore a backup and only a couple to create a backup.

After the hiccup I had as posted previously I'm back to cwm.

My scenario may be unusual but all it takes is one time for something like a recovery to have a hiccup.

I went in head first as prepared as I could, thankfully I did or we would have another "help!!!!!!!!!!!! I bricked my phone" thread

If you're gonna play around with the recovery make sure you have the cwm pg05img.zip or some other way to recover.
[Thunderbolt Android Development] fixxxer2008:
amon wiped my battery stats and dalvik just fine.
[Thunderbolt Android Development] oc3rulz:
I typed that out of order. I meant that Amon could wipe just fine, but CWM may have fixed the issue of not appearing to (or actually) wipe, but I know battery stats do not wipe properly in CWM.

Sorry for the confusion
[Thunderbolt Android Development] GreginNH:
OK, thank you for the info.

So just so I understand this needs to be done why, because they are built to flash with CWR?
[Thunderbolt Android Development] droidfanatic:
I'm on twr...how does one get this new recovery!
[Thunderbolt Android Development] fixxxer2008:
rom manager under alternative recoveries.
[Thunderbolt Android Development] fixxxer2008:
cwm needs zips signed differently.
[Thunderbolt Android Development] GreginNH:
ok, thanks appreciate the info!
[Thunderbolt Android Development] ibsk8:
Aside from the passing match to which is better, anyone have anything to say about the functionality of the recovery?

Everyone else having success? Any problems? I or was it just me?
[Thunderbolt Android Development] fixxxer2008:
all good soo far with me.
[Thunderbolt Android Development] GreginNH:
I made a backup successfully, wiped davlik successfully.

gonna wipe all and flash a ROM and then restore my nand....stay tuned
[Thunderbolt Android Development] GreginNH:
ROM flashed fine...will backup and try Nand from before
[Thunderbolt Android Development] Ryanmo5:
Keep it on topic people and read the first post on how to flash.

Flashed just fine in bootloader over TWR for me.
[Thunderbolt Android Development] GreginNH:
Works great,...backed up. flashed a new ROM then backed it up and restored to my original ROM.
[Thunderbolt Android Development] dukins:
Thank you for the heads up. I used Amon exclusively for my EVO. CWR never ever wipes my davlik cache. Great day in t-bolt history. :D

Welp tried it, "Oops something went wrong with your backup." Now back on CWR.
[Thunderbolt Android Development] amwenguer:
TeamWin Recovery vs. AMON.

What does everyone prefer? I been on CWR, but too frequently do I get stuck on splash screens.
[Thunderbolt Android Development] SP1986:
Well that's odd. I'm getting the message "Error: Unable to access jarfile signapk.jar" when I try to sign update.zip

Any suggestions?

edit: it appears if you try and run it from the GUI the process fails. Opening an admin level command prompt and running it from the command line worked flawlessly.
[Thunderbolt Android Development] wrich73:
The nice thing about RA is its easy to use both CWR and RA. I have my "stock rooted Sense" backup in the Clockwork backup folder, as well as any Sense based ROM's I may play with.

I do all my AOSP stuff through RA. CWR got buggy for me on my EVO, especially if I was flashing multiple files in the same recovery session, and the only restore failures I have ever had have been through CWR.
[Thunderbolt Android Development] yakitori2:
first of all...Id like to point out some flaws in many of you guys' logic.

1. Why are you wiping dalvik cache in recovery anyway? The only reason I could see one doing this is flashing a kernel that is causing a bootloop (see #3) Dalvik cache resides in /data partition...and sometimes in both /data and /cache partitions. Which leads me to number 2.

2. I see a lot of people wiping dalvik cache, wiping cache, wiping data and then flashing a rom. Even some people doing it 3xs or more. This is pointless. If you are wiping data and cache in recovery...it deletes dalvik cache in the process. Whats the point in going in after doing this and wiping dalvik in advance options? You are wiping NOTHING when you do this. Theres nothing there to wipe. Proper wiping (to start clean with any rom), is wipe data factory reset, wipe cache, format /system under mounts and storage (and format /boot if you have a phone with the option, tbolt is not one of those phones). That removes all...and gives real results on what a rom is doing to your phone when you run one clean...which is what I do when I flash a new rom.

3. you can wipe dalvik cache in terminal like.

su

sysrw

cd /data/dalvik-cache

rm *

reboot

if you have dalvik cache located in both /data and /cache...do this

su

sysrw

cd /data/dalvik-cache

rm *

cd /cache/dalvik-cache

reboot

no need to even go into recovery for that so the argument that cwm sucks for wiping dalvik cache is pointless. Do it through terminal.
[Thunderbolt Android Development] fixxxer2008:
still loving the recovery, no issues for me. flashes fine, restores fine and made new backups fine. i would like to thank the dev who ported this.

this recovery is damn fast and doesn't have all the stupid confirmation prompts like clockwork.
[Thunderbolt Android Development] yareally:
Even better would be doing it through the terminal shell inside of recovery (adb shell, which you can reach via recovery) instead of dealing with the recovery menu.
[Thunderbolt Android Development] xs11e:
How to name Nandroid backups?

I've probably missed something but how can I name backups so I'll know which ROM was used in each?

With Clockwork Mod I'm given the chance to name a backup before backing up and also a chance to re-name a backup after it's made, how can I do that with Amon Ra?
[Thunderbolt Android Development] 52brandon:
Cool. Never got to play with amon ra recovery before. Only ever had SPR, CWR or RZR on my Droid
[Thunderbolt Android Development] 52brandon:
Use root explorer, open the file and rename it
[Thunderbolt Android Development] ibsk8:
A question for those who have created and restored backups with amon, did you rename the folder prior to restoring?
[Thunderbolt Android Development] oc3rulz:
Not unless you do it through Root Explorer. Otherwise it will give you an error
[Thunderbolt Android Development] playpolo4life:
Been missing this recovery from my Eris days, stoked to see it on my tbolt now! Kinda got sick of CWR.

EDIT: Haha woops, I guess full wipe means full wipe. Gotta go and activate my phone again lol
[Thunderbolt Android Development] scotty1223:
as bady as i wanted Amon,i think ill be staying with twrp.i like twrps options and menus,plus the touch screen scroll kicks ass. not to mention there is no emo horse in CW or Amon :D

i did pull an image and put it in a PG05IMG,if anyone would rather download it and flash it that way.

Amon 3.03 http://www.multiupload.com/YQFX94NGS0

md5: 591c14fcc0cadd76ef0f986929d0de68
[Thunderbolt Android Development] oc3rulz:
C'mon the EMO horse adds bonus points and makes it like 100x faster atleast. I personally flashed the pink carebear onto a buddies phone when I had the Nexus One, for Amon RA
[Thunderbolt Android Development] ibsk8:
I don't quite understand what you're saying?

If you rename the folder and then try to restore you'll get an error?

Is that correct?

Is the error an md5 error or what?

I read somewhere in the past that renaming the folders can result in an error. I was wondering if this was the cause of the issue I had mentioned the other day.
[Thunderbolt Android Development] droidfanatic:
So in order to use this recovery I need to download a Rom to my pc and then run update and then push it to my sdcard and flash a Rom?
[Thunderbolt Android Development] fixxxer2008:
i sign mine but you can just toggle off signature verification before flashing, doesn't matter.
[Thunderbolt Android Development] GreginNH:
I dl a ROM last night and did nothing to it, just flashed it and it was fine.
[Thunderbolt Android Development] GreginNH:
I used Root explorer. I went to sdcard\nandroid. in there there is a folder and then under that is the file you backed up. I usually just add something to the end of the backup name to identify so I know what it was I backed up.

For instance, I backed up S3n3e 1.4 and just put a DT1.4 at the end of the name so i know what it was.
[Thunderbolt Android Development] hallstevenson:
I always laughed when I read people's posts either saying they wipe 2x or 3x or strongly suggesting (insisting) that wiping 2-3x was "necessary" in order for it to be done properly. I always thought, if you have to do that 2 or 3 or more times, your tool is broken !!
[Thunderbolt Android Development] scotty1223:
just thot id point out that signing an unsigned file,or toggling signiture verification off does not make said file any safer to flash ;)

just because its unsigned does not mean that its bad or dangerous. but the signiture verification is there for a reason. clockwork bricked quite a few eris's by destroying partitions with bad flashes due to no signiture verifications.

IMO there are alot of things folks just take for granted these days.
[Thunderbolt Android Development] yareally:
Very true, anyone can sign anything and do so with their own self generated key. It's just a sanity check as scotty mentioned :)
[Thunderbolt Android Development] fixxxer2008:
i came from amon on my evo4g so im used to signing zips. im right at home now and loving the recovery. im shocked the dev didn't post this here.
[Thunderbolt Android Development] scotty1223:
i always just toggled off on the incredible. it always bothered me... youd NEVER have an unsigned rom in the eris forum. in fact,there was not even a way to toggle amon signiture verification off on the eris :eek: the couple times i wanted to do it,i had to change to clockwork!
[Thunderbolt Android Development] ibsk8:
Did you restore the backup after you renamed the folder?

I'm trying to figure out what went wrong with my restore.

It worked fine before I renamed the folder,but after giving it a common name it didn't restore.
[Thunderbolt Android Development] c_live_lee:
I know there are some Amon Ra purists in this thread and, I'm in no way trying to knock it. I know it's a damn good recovery. Until I found TeamWin, I was anticipating it's arrival to our T-bolts. But, be honest here, am I the only one who was a little underwhelmed after flashing this, coming from TeamWin? I'm not here, trying to troll or anything. I'm just curious about any advantages/disadvantages of AR over TWRP.
[Thunderbolt Android Development] scotty1223:
as i said earlier,as badly as ive wanted Amon for the TB,ill be sticking with team win. i like the menus and options. i love the trouch scrolling. and dont forget emo horse :eek: not one of them in amon or clockwork ;)

twrp has a very amon-like feel IMO. so the pluses it has make me want to stay with it.

but it is awsome to know we have Amon now as a backup- if we have an issue with twrp we wont have to go back to CW :D
[Thunderbolt Android Development] GreginNH:
Yes, I did. After I loaded a new ROM I added DT1.4 to the name it had by default and then wiped and restored the nand backup and it has been running since yesterday.

I do remember using Amon on my Eris and there was a time when it didnt work for me but I think I remember I renamed the file completely.....If I just add a couple of characters to the end it always seems to work.
[Thunderbolt Android Development] c_live_lee:
I thought I remembered someone expressing those thoughts but, I didn't recall that it was you. Sorry about that. I did read though. And I do agree with you, in that it is most definitely a good thing to have this recovery in our arsenal. :)
[Thunderbolt Android Development] jasonbiggs:
Ok, since no one has compared these features...pertaining to this compared to teamwin recovery. does RA have continuous toggling when holding down the volume rocker as does teamwin? does RA have options to save preferences as does teamwin? Is RA quick to function by not prompting for too many "are you sure" or extra clicking dialogues? Does RA allow to use front menu buttons for selections instead of the power button for all activities? Is the speed difference any better than teamwin? Right now, using teamwin, it about cuts in half the time it took CWR to steam through actions. :)
[Thunderbolt Android Development] drellisdee:
To do so you have to append the end of the name no spaces

Ex.

BCDAS-20110828-1340

to

BCDAS-20110828-1340-STOCK

Thanks!

Few items to note here guys.

1. Signature check is on by default and can be turned off by Toggle Signature Verify under flash zip menu.

I like to have this on in the rare case a rom has a recovery binary in /system/bin if an ota update process calls recovery --update_package=CACHE:update.zip this is a failsafe to prevent it from trying to flash it as it will have a signature mismatch.

2. To those that had an error on restoring a nandroid the battery level must be at least 30% to restore a nandroid if off charger. This can be overridden if device is plugged into charger. This is a fail-safe to prevent a device powering off due to low battery during a restore and to prevent a partially restored device that is unable to boot normally. The user that had an error message if he had checked his recovery log it would have stated the battery was too low and thats why an error was thrown. You can also check battery level in recovery under "other" menu.

3. Full description of features can be found here

4. Any errors that you may encounter need to have a recovery.log uploaded or pastebin'nd so I can trouble shoot. Error reporting without this is useless.

5. Clockwork & TWR nandroids are not interchangeable with RA nandroids!!

6. Enjoy!!!

Please update 1st post with link to this one also.
[Thunderbolt Android Development] fixxxer2008:
1. thanks for this

2. how can i donate to you?

3. will there be updates or is this a final port?
[Thunderbolt Android Development] ibsk8:
I think this explains my problem. Thank you very much.
[Thunderbolt Android Development] drellisdee:
Donate link is in my sig. I have made ra recoveries for 15+ devices and added quite a few additions to the opensource code with it. Updates will come as needed (as bugs are found) as I'm using the almost exact same recovery for my dinc2 and I updated it to add full emmc partition support from the ra dinc1 version I used for nearly a year (that only only supported partial emmc as it was mixed emmc and mtd setup). I only released it for mecha due to several requests for it but plan to continue support on it.
[Thunderbolt Android Development] fixxxer2008:
so to get this straight after i do a backup i cannot just name it "stock"? i have to add it to the end of what is already generated? back in my evo days with amon i know i could just totally rename it.
[Thunderbolt Android Development] scotty1223:
i made 2 backups of shift th3ory,and was unable to restore either of them. changed back to twrp and restored one of those backups. flashed amon back tried one more time to restore both backups,and both hang at splash. :mad: went ahead and flashed black ao5p,and that seemed to work fine.

those that have used this,is there a trick to getting bakcups to restore?? :confused:
[Thunderbolt Android Development] superchilpil:
Wrong and you know how, the signatures are exactly the same, the fact that very few people sign their zip files anymore is why no one even cares anymore

The purpose of the signature is to prevent you from flashing a bad zip file that got corrupted or modified in some way, its similar to a md5 sum

The update scripts have nothing to do with it, we upgraded from amend to edify because its a more advanced scripting method that has more functionality, koush knew this and forced it on us because it was a needed upgrade. And since clockwork is on most android phones he did a good job of it.

Nothing against amon_RA its a good recovery but I prefer clockwork.
[Thunderbolt Android Development] drellisdee:
Please get me a recovery.log of restoring the shift th3ory from this recovery. After done restoring use "other" move the recovery.log to sd mount sd card mass storage in recovery and copy recovery.log from sdcard to pc and upload it here.
[Thunderbolt Android Development] scotty1223:
thanks,i will do this later for you. im off to work right now,and had switched back to twrp.
[Thunderbolt Android Development] drellisdee:
Also can you give me a logcat of the rom not booting after a restore.

This is after you reboot.

Use

adb shell logcat > logcat.txt and pastebin that for me

Is there anything unusal about how this rom is setup or partitioning? And you are restoring a backup of this rom that was backed up via RA recovery correct not a twrp one?