so as i was reading up on rooting the EVO for my dad, i ran across people saying that you should use Amon_RA for a recovery and not Clockwork. i have Clockwork installed as my recovery, but i have used Amon before. that one reason that i use clockwork instead of amon is that i can restore certain images of nandroids (not everything if i dont want to, but just the data or system or boot) and i can access my whole sdcard when flashing a zip. and amon looks kinda funny too.
but what are the pros to amon? i know that two of them are that its built from CM sources and that the features in QtADB when in recovery mode work with amon, whereas they dont with clockwork. so what are the technical pros and cons of each? because i think ive done a good job of explaining the interface pros and cons. thanks for the help
PS: the reason why im not just reading the explanations in the evo threads is that i assume that there are seriously major hardware and software differences outside of the htc label on the phones. so yeah.
The Drama with the AmonRa and CW on the EVO forums was because CW would not always flash Cache and Dalvik Cache correctly (one or the other I dont remember off the top of my head) and would also trash their Wimax RSA keys. Recently Koush updated CW to fix all of those problems so the galaxy is at peace again, though rebels still continue to remember the problems that CW brought so they stick to their beautful AmonRa recovery.
I would say it depends on your phone, seems like CW works fine on the Hero CDMA so it should be fine. I came from the Droid Eris where it was known that CW would completely Brick some of our phones
Now I have a Droid1 where CW works magically, like I said, I guess it would depend on the phone Hope this helps.
refthemc said:
The Drama with the AmonRa and CW on the EVO forums was because CW would not always flash Cache and Dalvik Cache correctly (one or the other I dont remember off the top of my head) and would also trash their Wimax RSA keys. Recently Koush updated CW to fix all of those problems so the galaxy is at peace again, though rebels still continue to remember the problems that CW brought so they stick to their beautful AmonRa recovery.
I would say it depends on your phone, seems like CW works fine on the Hero CDMA so it should be fine. I came from the Droid Eris where it was known that CW would completely Brick some of our phones
Now I have a Droid1 where CW works magically, like I said, I guess it would depend on the phone Hope this helps.
Click to expand...
Click to collapse
yes, as a matter of fact, this is good to know. thanks
I've been a long time amon ra user never had a problem with it. I have used clockwork (for weeks at a time) but have had issues with it. I like it though don't get me wrong but I suggest amon ra
Asadullah said:
I've been a long time amon ra user never had a problem with it. I have used clockwork (for weeks at a time) but have had issues with it. I like it though don't get me wrong but I suggest amon ra
Click to expand...
Click to collapse
I'll haave to agree,throughout all the threads I frequent I see people having issues.Don't see it that much with Amon Ra,but I could be wrong.
Plus one on the Sig.
Related
Ok. So I got CyanogenMod 5.0.8 on my Droid, and it has an option for Apps2SD.
Only problem is, I need to create the ext4 partition on my SD Card, and I can't figure out how.
I can't find an AmonRa Recovery for my phone. I currently have SPRecovery.
Am I missing something? And is it possible to flash a new recovery image?
Or is there some way on how to partition the card manually? I've seen some things about SDParted Script and running Parted manually, but don't even have the first clue on how those work, or if they even work on the Droid.
Any help would be greatly appreciated!!!!!
I was running cm 6.0 and had no problems with apps2sd. Never even had to partition the card. As for other recoveries, I've been using ROM manager to flash recoveries. They have SP and Clockwork. Just make sure you maually enter recovery by powering up by holding x. The reboot into recovery has never worked for me.
Honestly Amon-Ra? Dude you are retarded. Amon-Ra isn't for the Droid. I think he only does HTC devices -_-. The two recoveries for the Droid are SPRecovery and ClockworkMod Recovery. Clockwork is the better one. You can partition your SD card right from ROM Manager.
Um... I'm retarded?
You just flamed me over a question I had. That's retarded.
Sorry that I'm not as experienced in this as you and that I don't know these things. I'm brand new to Android. Coming from WinMo, and I was ALL OVER WinMo. Not a Dev, but definitely a Modder. So gimme a freakin' break. Sheesh.
And yeah, I was using SPRecovery and switched over to Clockwork. It just seems better.
And, BTW, eff CyanogenMod. I was reading through their forums... and ALLLLLLLLLLLLLLLLL I see are various bugs and issues... crazy different ones from all sorts of people. Most left unresolved. I'm having some FC issues with .acore, which I have no clue what that is, but if it's what I think it is (which is one of the main system OS/Firmware files), then I just need to dump the ROM altogether.
I was on SimpleRom... and I liked it... but it just got slower, and slower, and slower. I was using Launcher Pro Plus, and I think that was part of the problem, but I'll be damned if I just don't love it. *sigh* I really really really like "Sense" (I put it in quotations because it's not really.... DUH) on my Droid.
I like having Apps2SD... and don't wanna lose that.
SimpleRom + Launcher Pro Plus DEFAULT & DEBUGGED (as much as possible) + Apps2SD = Happy Me.
CyanogenMod == the ****! Like good ****!
@dymic Are you sure you cleared all the cache in recovery? I have never had 1 issue with CM... well one.. my battery lasts forever..
Sent from my Droid using XDA App
Yes. I'm sure.
I switched over to Simply Stunning. And it is... Simply Stunning.
It's fast, it does Apps2SD, and I'm running Launcher Pro Plus, and it's perfect.... so far.
We'll see what it's like after about a week.
I'm having issues with downloading a rom. I used the free version and installed the Shadowrom but it wouldn't reboot in it. I bought the premimum version and now when I go to download rom it gives me a list but I get a pop up message of "error occurred while processing the rom list" I don't know what this means, can someone help?
You should contact the dev over this issue. Also it is in a sticky thread that clockwork recovery could possibly brick your device. Just a heads up!
Clockwork no longer replaces AMON_RA .... it actually uses amon to boot into clockwork .... so although everyone wants to bad mouth Clockwork are there any confirmed cases of brick since they fixed the Eris problem ? I can say I have used it a few times on my wifes phone cuz she has trackball issues and Verizon refuses to replace her phone ... and I know for a fact that Amon_RA is still the recovery on her phone unless I boot into Clockwork from the update.zip or from Rom Manager (on her phone i can't use the update zip, trackball problems)
ok, thanks for the heads up. I probably won't even bother then. Is this issue for the app itself or just certain Roms. I definitely don't want to brick my Eris. My friends Droid was bricked a month ago I just unbricked now. I don't want that headache.
Have posted this a number of places with no luck, including Rom Mgr thread:
If I flash a rom, set it up, then back up, Rom Mgr will not reboot to system. Goes to X and hangs. Sometimes after 3 tries or so it works or if I Restore the recent backup it works. Nothing consistent.
This started when I used amon 2.0 to increase ext to 1024mb for running eVil's desire rom. I had numerous issues where I could not even back up or restore. Seemed to always hang on android-secure part. Since then I reformatted sdcard with sdformatter, then used RM to create 1024 ext3. Flashed fresh eVil HD Gamma rom. All went well, but again after setting everything up and then tapping on reboot into system it hung again. It did not hang after initial flashing of rom and Circle Battery .zip. It booted into system fine.
When I got back to system and homescreens, I uninstalled RM and reinstalled. Although, I had done that before, but before I reformatted sdcard.
So, if this keeps up, only conclusion is RM even though I installed latest from Market, or this rom is messing things up. But, no mention of this issue anywhere else. I will try to boot into Clockwork thru Quick Boot (did that before also) to get to recovery and see how it goes.
Anyone have any idea for a solution to this nightmare, or had a similar experience. Running out of ideas. I am going to dl latest MIUI rom and see how it performs. And maybe load an earlier version of eVil's HD rom.
Thanks for any help, know this is weird,
Ken
Only thing I would suggest is to stop using ROM manager. There is really no need for it. Anything you can do in that, you can do either in recovery, or via a terminal.
efrant said:
Only thing I would suggest is to stop using ROM manager. There is really no need for it. Anything you can do in that, you can do either in recovery, or via a terminal.
Click to expand...
Click to collapse
+1
IMO, using an in-OS software to control the recovery is risky. I prefer having full control by manually flashing everything!
Thanks guys for replying,
I can try reboot recovery thru terminal and Quick Boot. Although, it did it right after repartitioning with Amon_Ra. So, thought it might not be Rom Mgr.
Really thought the reformat of sdcard would do it. May have two issues. Next step is to get the latest eVil rom off and go back to previous version and/or repartition back to 512mb sdext.
Just Frustrated and Confused
Ken
Just an update guys, since you were kind enough to reply to my post
I have kept the 1024 sdext made thru RM/CW removed both eVil's roms and relashed a fresh MIUI. No issues so far, time will tell. Will probably reflash a MicroMod rom too. Can't believe the larger HD rom was the cause. I loved the rom.
If I figure it out one way or the other I'll update. I can't even google my problem and find someone else with it.
Ken
id get rid of rom manager and clockwork. i flashed many many many things/times with amon ra recovery alone without issues, but all i hear are problems with rom manager/clockwork. i mean how easy is it to just go into recovery and flash? or just download something through the browser... my 2 cents
I've been doing this for 8 months and started with amon. Never had issues with either amon or rm/cw. Started using rm/cw just to try when doing a lot of nightlies with cyan.
But, I recently repartitioned to 1024 sdext3 with amon to run desire rom and amon hung too.
Still 1024 and no hanging with MIUI, using rm/cw. I don't have a preference one way or the other, as long as it works.
Don't think it is either amon or rm/cw, but the rom and my ext not working well together. Had no issues with the 512 ext and desire rom. But, I was getting windows warnings on errors on my sdcard and thought it time to reformat anyway.
Thanks for the advice all, I will run MIUI and Micro for awhile and maybe go back to 512 ext.
Did learn for anyone using Rom Mgr that it does now do 1024 ext3 partitioning. Many people thought, as I, it stopped at 512 and ext2. Maybe it use to. Verified the ext 3 thru Mini Partition Tool Wizard. Just FYI.
Ken
Well,
I appreciate all the advice and help, I need it sometimes. But, seems (I hope) that I forgot to reboot into recovery after repartitioning. This tip came from Amon_RA and seems to have fixed my "reboot into system from recovery" issue.
I am now back on eVil's great HD Desire rom and 1024 sdext3 working great.
Thanks,
Ken
ROM Manager says there's an update to Clockwork Mod. 3.0.0.x, is it safe to apply? Running CM7 rc2 right now.
Sent from my Nexus One using XDA App
Why wouldn't it be? And yes it's ok I've been using it since release with no problems.
Yeah it is safe to apply. I've been using it for quite a while.
I've tried to run with clockwork 3.x twice now, and both times my SD card (ext partition) got screwed up to the point that it couldn't mount. The only way I could recover was to reformat the entire card.
I don't know if it was clockwork 3.x, or user error, or just coincidence, but I've never had this problem at other times...
The web is full of similar examples, so until I know for sure, I refuse to use 3.x (I'm a clockwork fan, and use 2.5.1.4).
Sent from my Nexus One using XDA Premium App
Ive had some annoying issues with version 3 also. Never a problem in 2.x
I use RA when I have issues. 3 seems to integrate the GUI but causes problems while actually in recovery mode... I was wondering if I was the only one. I'm definitely a Clockwork fan.
Clockworkmod 3 has problems with sd card, in particular if you are using DT apps2sd.
In my case, it didn't restore to the sd card properly.
I reverted to clockwork 2.5.1.1 and was able to replay my backup. For now, I am staying with 2.5.
yeah cwm 3 has given me nothing but grief. refuses to flash roms, wiping sd card completely, left me in a sticky situation the other day as i had nothing to read my sd card, and have been stuck in the same situation again right now, switching to RA recovery from now on. nothing but grief.
however, glad to see im not just losing my mind and im not the only one experiencing things like this
general consensus is that it is safe some people though like me had issues with it. It wouldnt restore my backups correctly and would freeze in the process. Bc of this i stuck with version 2.5x
I had the same issue with CWM3 totally screwing up my ext3 partition, to top it all off I couldn't access any of my previous backups and wound up having to totally format the SD card complete, repartition and start from scratch with a backup on my PC that was several months old. VERY ANNOYING! Needless to say i now use AmonRA with ZERO issues and I will be pretty hard pressed to go back after that little fiasco...
mrkrizzle said:
general consensus is that it is safe some people though like me had issues with it. It wouldnt restore my backups correctly and would freeze in the process. Bc of this i stuck with version 2.5x
Click to expand...
Click to collapse
I couldn't get CWM 3 to complete a backup...pretty essential, so I went back to 2. May try the update and see if it works.
Long ago I had issues where my backup would freeze. Temp fix was to restore each individual section which allowed me to at least restore that backup.
I hope mods can make this sticky.
Do not use ClockworkMod Recovery 3.0.0.5 to create partitions for SD-EXT. There is a bug with clockworkmod recovery that create faulty partition resulting in data corruption. This prevent a2sd+ from working properly, any attempts to fix a2sd without recreating SD-EXT can corrupt apps and market data.
So please use RA Recovery v2.2.1 for partitioning SD until this bug is plugged.
Yeah, it's old news though.
If you must use CWM use an older version or one of the few modified version floating around.
Just so you know it's not just for partitioning clockwork mod 3.X is unstable in allot of ways some people get away with using it but that's usually the people who flash stuff like max once a month or that just install cm then stop even booting into recovery so I suggest everyone to go either to Amon RA or clockwork mod 2.5.1.4 (which is the latest 2.X clockwork mod recovery).
baseballfanz said:
Yeah, it's old news though.
If you must use CWM use an older version or one of the few modified version floating around.
Click to expand...
Click to collapse
Unfortunately, this news is not visible to people who are new to using CWM. I think making this sticky will be helpful to new users. I had to do several forum hunts the whole day yesterday just to figure out what was breaking A2SD+ on MIUI.
jazzaddict said:
Unfortunately, this news is not visible to people who are new to using CWM. I think making this sticky will be helpful to new users. I had to do several forum hunts the whole day yesterday just to figure out what was breaking A2SD+ on MIUI.
Click to expand...
Click to collapse
I have to say it's true that this is common knowledge to people who spend some time on forums but to noobs and people who are just following a tutorial it's true that this knowledge is not very visible so I think this should either be stickyed or put into the nexus one wiki. Just my 2ยข