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

Root Replacing clockwork with amon ra

D

dogshed

Member
I downloaded a PC36IMG_RA_2.3.zip renamed it and put it in the root of my sdcard and of course renamed it. PC36IMG.zip
MD5: 6dbb98f9cfa35033982c3803d2520466

The only way to get to a boot menu is to put in the battery while holding the down vol.
It seems to read the file but then goes back to the boot menu.
I still have clockwork. I've also tried selecting the file in clockwork, but that didn't do anything either.

I also tried just going ahead and installing the rom with clockwork. The phone is boot looping on me.

Things that probably don't matter:
I tried running super swipe and it gave an error. Someone on another thread said I might have the wrong version for the evo and it could have messed up my mount points.
 
You should be using the superwipe file that I gave you. Also superwipe just plain won't work with cwm recovery because cwm doesn't support it.

If the phone doesn't recognize the pc36img file it either isnt named correctly or is in a subfolder on your SD card

Double check this again for us. Make sure yoyou don't have. Zip.zip
 
Ok I think you're on the right track. The file you have should be the correct file. My signature has the link to the thread on XDA, so if that's the file you have, you're golden.

Recoveries are ONLY flashed through the bootloader. That's the white screen you get when you hold vol-down and power to turn on your phone. Here's the steps to install Amon RA 2.3 (or any recovery, but really, this is the only you you'll ever need"

1) Put the file on the root of your SD card and rename to "PC36IMG.zip" without the quotes. It needs to be named this exactly. Capital letters included. Be careful...windows can hide extensions sometimes, so be careful not to name your file PC36IMG.zip.zip otherwise it won't read. By the way, the "root" of the SD card means to put it in the top level directory...not in any folders in your SD card.

2) boot your phone into the bootloader (white screen)....if you have the file named correctly in the root of your sd card, it will scan for files and ask you if you want to update. Select Yes. Then it will install and ask you if you want to reboot. Select "no". Then you should be able to enter into recovery. Easy as pie.

3) Make a backup. Your Amon RA 2.3 backups are NOT compatible with Clockwork and vice versa.

4) If you ran superwipe, you just wiped everything off your phone. So you'll need to either flash a new rom or restore an old backup.

Good luck!
 
It goes through its list of files and when it gets to PC36IMG.zip it stops, but it does not ask me if I want to update. It just goes back to the boot menu with the white background.

MizzouBrent said:
Ok I think you're on the right track. The file you have should be the correct file. My signature has the link to the thread on XDA, so if that's the file you have, you're golden.

Recoveries are ONLY flashed through the bootloader. That's the white screen you get when you hold vol-down and power to turn on your phone. Here's the steps to install Amon RA 2.3 (or any recovery, but really, this is the only you you'll ever need"

1) Put the file on the root of your SD card and rename to "PC36IMG.zip" without the quotes. It needs to be named this exactly. Capital letters included. Be careful...windows can hide extensions sometimes, so be careful not to name your file PC36IMG.zip.zip otherwise it won't read. By the way, the "root" of the SD card means to put it in the top level directory...not in any folders in your SD card.

2) boot your phone into the bootloader (white screen)....if you have the file named correctly in the root of your sd card, it will scan for files and ask you if you want to update. Select Yes. Then it will install and ask you if you want to reboot. Select "no". Then you should be able to enter into recovery. Easy as pie.

3) Make a backup. Your Amon RA 2.3 backups are NOT compatible with Clockwork and vice versa.

4) If you ran superwipe, you just wiped everything off your phone. So you'll need to either flash a new rom or restore an old backup.

Good luck!
Click to expand...
 
Rxpert83 said:
Does it stop and scan it? If it scans it it can recognize it. If not it always stops after pc36img
Click to expand...

As near as I can tell it can't find an image on the first file diag.zip
then an nbl file and then it says it is "checking" PC36IMG.zip
Is checking the same as scanning?
 
& from another thread he has h-boot .79. I haven't been in the android world for long enough to have had to use it, but does he need to run unrevoked forever or something to get s-off?
 
Rxpert83 said:
& from another thread he has h-boot .79. I haven't been in the android world for long enough to have had to use it, but does he need to run unrevoked forever or something to get s-off?
Click to expand...

I'm sorry I was confusing rooted ROMs with s=on.
I just restored to a gingerbread that I was using.
My phone constantly reboots so I don't trust doing anything while the operating system is running. I think I'll try
su-2.3.6.3-efgh-signed.zip and see if that switches it.
 
dogshed said:
I think I'll try
su-2.3.6.3-efgh-signed.zip and see if that switches it.
Click to expand...
That did nothing. I misread the instructions.
Should I load back up the froyo? Would that make things easier?
My ultimate goal is to have a phone that doesn't constantly reboot.
What roms can be loaded with clockwork?
 
Rxpert83 said:
& from another thread he has h-boot .79. I haven't been in the android world for long enough to have had to use it, but does he need to run unrevoked forever or something to get s-off?
Click to expand...
Yes.

dogshed said:
I'm sorry I was confusing rooted ROMs with s=on.
I just restored to a gingerbread that I was using.
My phone constantly reboots so I don't trust doing anything while the operating system is running. I think I'll try
su-2.3.6.3-efgh-signed.zip and see if that switches it.
Click to expand...
If you are S-ON in HBOOT, that's why your bootloader isn't recognizing the PC36IMG.zip file. You need to flash unrevoked-forever in recovery (hopefully your baseband is a compatible version), and that'll get you back to S-OFF. Then, you can flash Amon RA Recovery, and MikG. That may get your reboot issue resolved. Stand by for a link.

EDIT: http://downloads.unrevoked.com/forever/current/unrevoked-forever.zip
Full Instructions: http://unrevoked.com/rootwiki/doku.php/public/forever
 
dogshed said:
I wonder if at some point, a year ago, I ran the s=on tool.
Click to expand...
If so, that would probably account for your reboots too. In my experience, when turning the phone S-ON, but still having a rooted ROM, when apps that require root access try to get root, it causes the device to reboot. That could be the ultimate cause of your issue.
 
Thank-you.
That did it.
I was a little worried that it wasn't going to give me the boot menu again, but after a few battery reinsertions I was able to get the boot menu and hboot went to town on amon ra.
I then selected don't reboot and selected recovery from the menu and now I have RA.
I went into the backup menu and then
I chose everything except cache and recovery.
(If your recovery gets messed up what would I do with the backup? Recovery would be broken right?)
I'll probably do the google backup just because it's there.

CapThrowback said:
Yes.


If you are S-ON in HBOOT, that's why your bootloader isn't recognizing the PC36IMG.zip file. You need to flash unrevoked-forever in recovery (hopefully your baseband is a compatible version), and that'll get you back to S-OFF. Then, you can flash Amon RA Recovery, and MikG. That may get your reboot issue resolved. Stand by for a link.

EDIT: http://downloads.unrevoked.com/forever/current/unrevoked-forever.zip
Full Instructions: public:forever [RootWiki]
Click to expand...
 
Wow. In all the rebooting threads I trogged through I never read that.
Maybe I'll just see how it goes before installing a new rom.

CapThrowback said:
If so, that would probably account for your reboots too. In my experience, when turning the phone S-ON, but still having a rooted ROM, when apps that require root access try to get root, it causes the device to reboot. That could be the ultimate cause of your issue.
Click to expand...
 
I had written down all my numbers including baseband before running the file. I guess I was lucky there.
The backup and the log file are dated 1980 so maybe I should have rebooted to set the clock?

Someone has a sense of humor. Check out the log file.


unrEVOked forever S-OFF patch v1.3

Verifying system type...
.
.
Got device:
@PID: 73,"SUPERSONIC_C"
Got radio version:
2.05.00.06.10
Checking system requirements...
Infinite loop duration: user-defined (good)
Brinell hardness: 35-45 (good)
Viscosity: SAE 20 or equivalent (good)
Voltages: Plate=+350VDC (good)
Filament=+12VDC (good)
Grid=-2.4VDC (good)
Operating environment: Yes (good)
Microcode verified CFC-free (good)
Syncing flash...
Verifying update...
Update successful.
unrevoked
 
You must log in or register to reply here.
Back
Top Bottom