• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ClockworkMod Recover Vs. Amon Ra

Open a terminal emulator on your phone, type "su" without quotes to get root (prompt changes to #), then type "grep RSA /dev/mtd/mtd0" without quotes, then enter. As long as you see these last two lines, you're good:

-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----

You can also run "wimax_mtd" from the terminal and make sure it runs successfully.

As to whether or not RA was having problems before, The version of 1.8 that was flashed from ROM manager didn't work on newer phones with different partition info. You can check by typing "cat /proc/mtd" from the terminal. If erase size is 40000 (rather than 20000), then it won't work. There was a patched version of it floating around until RA 2.1.1 was released. Now it doesn't matter.
 
K, so I ran that in Android Terminal Emulator and the query ended with

"-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----"

With nothing in between. Is that right?
 
K, small update. I'd read that Amon RA's latest version was a lot more stable, so I thought I'd give it a try. I flashed it in ROM Manager and then rebooted to recovery to do a NAND backup, which went fine. Then I cleared all the cache's and tried to flash the latest version of MikFroyo that a buddy's been raving about. It flashes and boots fine, but once it gets into the ROM itself, I have all sorts of FC's whenever I do ANYTHING, to the point where the phone is almost unusable.

For some reason all of my data, apps and widgets were restored from the backup too, which I didn't want since I had an AOSP ROM beforehand (Cyanogen). I have a feeling this is what caused the problem.

So am I just cursed not use Amon RA, or is there something else at work here? Thanks!
 
Brian Rubin said:
K, small update. I'd read that Amon RA's latest version was a lot more stable, so I thought I'd give it a try. I flashed it in ROM Manager and then rebooted to recovery to do a NAND backup, which went fine. Then I cleared all the cache's and tried to flash the latest version of MikFroyo that a buddy's been raving about. It flashes and boots fine, but once it gets into the ROM itself, I have all sorts of FC's whenever I do ANYTHING, to the point where the phone is almost unusable.

For some reason all of my data, apps and widgets were restored from the backup too, which I didn't want since I had an AOSP ROM beforehand (Cyanogen). I have a feeling this is what caused the problem.

So am I just cursed not use Amon RA, or is there something else at work here? Thanks!
Click to expand...

Did you wipe data or just cache/dalvik? You need to wipe all three, or something like what you described will happen. I'm surprised it booted up at all. Go back to recovery, wipe data, cache, and dalvik, then flash it again. See if that helps.
 
Brian Rubin said:
Ah, that time it worked perfectly. Thank you!
Click to expand...

Great :). Yeah, it's always very important that you wipe data. Sometimes you can get away with not wiping data when upgrading a particular ROM, but it's generally not recommended even though it usually works. You can't go wrong if you just follow the instructions given by the developer of any given ROM.
 
I didn't wipe data before flashing from stock to Cyanogen, but it seems to work fine. However I'll do that from now on. Thanks again!

PS. I think Cyanogen has ruined me for Sense based ROMS. Within maybe 20 minutes I flashed back, as I much now prefer AOSP.
 
Hehe, yeah that happens to a lot of people. One of the great things about the Evo is that we have a ton of choices. That's surprising that not wiping data worked when going to CM. It's just one of those things where sometimes it works, sometimes it doesn't, but you're more likely to have problems than not.
 
Wiping data technically will make no difference before restoring a nandroid backup. It will just overwrite everything with the contents of the backup. If you're not having problems in CM, you're probably fine, but if you've had any weird issues lately, it could be because of that.
 
wrapkgb said:
Just remember you can't restore nands from clockwork to amon and vice versa.
Click to expand...

So if I switch to Amon-RA, one of the first things to do is do another Nand Backup? What happens to the old Clockwork Nand backup?

Also, anyone know where to download Amon_RA 2.0.1 or newer?
 
Borat38 said:
So if I switch to Amon-RA, one of the first things to do is do another Nand Backup? What happens to the old Clockwork Nand backup?

Also, anyone know where to download Amon_RA 2.0.1 or newer?
Click to expand...

1) Yes, you should make a nandroid backup right after flashing RA. You won't be able to flash CW backups with it. The clockwork backups will stay on your card, and can be restored if you flash back to CW at any point. For that reason, you may as well keep them if you ever want to go back. You can move them to your computer if they're taking up too much space. Just remember - flash CW back first.

2) You can get RA 2.2.1 a number of different places. The quickest is to install ROM manager, if you don't have it, and choose the option to flash an alternate recovery. That will be RA. You could also use the command line tool known as flash_image to flash the official img, which you can get here:

[Recovery] [07-Jan-2011] RA-supersonic-v2.2.1 - xda-developers

If you don't have flash_image, or don't even know what it is, don't bother with that method. It is available, though. If all else fails, you can flash this PC36IMG.zip from hboot:

http://db.tt/PEhJy41

Make sure it stays named PC36IMG.zip, copy it to the root of your sdcard, turn the phone off, turn the phone back on while pressing and holding the volume down button, then you will be prompted to flash it. Only do that if you have trouble with the ROM Manager method, though. That's much simpler.
 
Hello All!

I just noticed after updating CWM to 2.6.0.1 (and 3.0.0.5) that I was getting color fuzz/noise at the bottom of the screen after hitting <reboot> in Recovery mode. I've never had that issue til I updated CWM, unfortunately, I couldn't go back to 2.5.0.1 to see if it'd solve the problem so I updated to 3.0.0.5 and got the same thing. I switched over to RA 2.1.1 and it wasn't present anymore.......not sure if it's really much of an issue but just thought I'd check to see if anyone else has witnessed the same???
 
akazabam said:
Open a terminal emulator on your phone, type "su" without quotes to get root (prompt changes to #), then type "grep RSA /dev/mtd/mtd0" without quotes, then enter. As long as you see these last two lines, you're good:

-----BEGIN RSA PRIVATE KEY-----
-----END RSA PRIVATE KEY-----
Click to expand...

so if i have multiple lines that say "RSA - Request, reply, reject" ive got some problems...4g stopped working after i updated my radios and wimax. running a 3.7 based rom, and a modified #15 kernal. i have the older clockwork, and my radios and wimax werent backed up...i have insurance though, guess that the bright side..
 
MK, as long as your string of stuff ends in those last 2 lines, you should be fine. There are threads somewhere else that give the exact text that you see before those two lines....and there are 2 or 3 "request...reply...reject" sequences. SO don't sweat that. Look around but I am thinking your 4g is fine.
 
fortisi876 said:
Hello All!

I just noticed after updating CWM to 2.6.0.1 (and 3.0.0.5) that I was getting color fuzz/noise at the bottom of the screen after hitting <reboot> in Recovery mode. I've never had that issue til I updated CWM, unfortunately, I couldn't go back to 2.5.0.1 to see if it'd solve the problem so I updated to 3.0.0.5 and got the same thing. I switched over to RA 2.1.1 and it wasn't present anymore.......not sure if it's really much of an issue but just thought I'd check to see if anyone else has witnessed the same???
Click to expand...

I don't seem to recall every seeing that. I haven't used CW 2.6 yet, so I'll give it a try later and see if it does it. If it only does it then, though, I wouldn't worry too much.

mkonei said:
so if i have multiple lines that say "RSA - Request, reply, reject" ive got some problems...4g stopped working after i updated my radios and wimax. running a 3.7 based rom, and a modified #15 kernal. i have the older clockwork, and my radios and wimax werent backed up...i have insurance though, guess that the bright side..
Click to expand...

You will see several other lines with RSA in them. You just need to make sure the last two lines are those specific ones. If they aren't, I'm afraid you've lost your keys.
 
So I played around with Amon RA a little more, and it's working great, so honestly I think I'll stick with it. Question though, is the best way to update it still ROM Manager, or is there a better way?
 
Brian Rubin said:
So I played around with Amon RA a little more, and it's working great, so honestly I think I'll stick with it. Question though, is the best way to update it still ROM Manager, or is there a better way?
Click to expand...

There are several ways, and they all result in the same exact thing.

1) Flash through ROM manager
2) Flash from a terminal with flash_image (comes bundled in some ROMs, otherwise it needs to be installed manually)
3) Flash through a PC36IMG file in hboot

None is "better" than the other. ROM manager is the quickest, but doesn't seem to work 100% of the time.
 
Hah, yeah, I've got two now on my phone so far, one like PC36IMG_recovery for flashable recovery and one like PC36IMG_rom for the Sprint Lovers rom that's my failsafe in case of flashing failure of some type.
 
You must log in or register to reply here.
Back
Top Bottom