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

Root Can't flash with CW Mod

markdmac

markdmac

Well-Known Member
This morning I noted that VZW provided a Froyo update, so I flashed back to stock using ODIN and allowed the OTA upgrades. After re-rooting I installed ROM Manager. I have since been trying to replace the boot animation and the battery icon. When I try to load the zip files with ROM manager, the phone reboots but then gives the following error messages:
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.


I'm trying to get the Honeycomb animation and the circle battery icon (with battery percentage) on my phone. Can anyone assist or provide me with links to downloads that should work? What I have I got from XDA.

I have also noted that ROM manager is unable to make a backup of the current ROM. I get the exact same error, that scares me.
 
Well, I seem to have partially figured this out I found I can use ODIN to push CWM RED, then as long as I boot directly into CWM RED I can do a backup and load ROMs. If I let the phone boot first I cannot get into RED and the phone always goes to the stock Android BLUE Recovery. I read in a thread that some ROMs overwrite some settings, but can't find the solution. Does anyone know how to prevent this from overriding?
 
Some ROMs are compatible with 2.x CWR and some with 3.x. It depends on what ROM you are trying to install VS what CWR you have.
 
Well, that makes sense. So how do I determine the version of CWM I have so I can try downloading and installing the other. version. Is there a way to tell from the tar file?

If I extract the contents of cwm-recovery-ALL there is a recovery.bin file with a date of 3/30/2011.
 
When you boot into recovery mode it will list the version number at the bottom.
Most of the current roms are compatible with the lastest cwr 3.x that uses Etify scripting (versus Amend scripting).
 
Thanks again for your assistance. I've continued to research this issue on about 6 different Android forum sites and have learned the following:

After flashing CWM Red you cannot use ROM Manager anymore (perhaps a combination of certain ROMS and Kernals). The only real downside to this is that when making a backup you can't name it at the time, but you can rename them after the fact by mounting the SDCard. You can still install zip files via CWM RED.

  1. If you do use ROM Manager, the phone reboots into Android Blue and you will need to reflash RED with ODIN.:mad:
  2. I can select Reboot from the Power Button shutdown menu and the phone will reboot into CWM RED, without the need of a Vulcan Android Three Button Pinch. :D
  3. While trying to flash the Honeycomb boot animation, CWM RED would seemingly hang. I was sweating bullets when I had to yank the battery to get control back. Pushing the ZIP file with ADB was painless and successful in replacing my boot animation. :cool:
 
markdmac said:
Well, I seem to have partially figured this out I found I can use ODIN to push CWM RED, then as long as I boot directly into CWM RED I can do a backup and load ROMs. If I let the phone boot first I cannot get into RED and the phone always goes to the stock Android BLUE Recovery. I read in a thread that some ROMs overwrite some settings, but can't find the solution. Does anyone know how to prevent this from overriding?
Click to expand...

If you are reverting to blue after flashing and booting I think you have to flash CWM and then immediately flash a ROM. If you don't it overwrites the recovery partition, returning you to blue recovery.

And DO NOT use ROM Manager to get into recovery more often that not its broken. Do it manually by booting to recovery yourself either with the boot menu or by holding both volume buttons while you power in on.
 
That is the process I followed. Happily using CWM Red at will now that I know not to use Rom Manager to initiate the reboot.
 
Anytime you do anything root access requiring reboit you will get that error. Either Sammy or Big red put some script in that makes your phone check and replace the recovery if it isn't the stock one. That is easily fixed though, if u are rooted you need something like root explorer. Edit the file extension for /ect / install-recovery.sh. and /system / recovery-from-boot.p and also /system /bin/ recovery I have done this on my debloated debinged, but not yet deodexed, but will be soon, used to be bone stock ed03 fascinate. I actually like it a lot, I have blue cwr3 from times_infinity on xda so I don't know if rom manager works with this or not, I don't use it on the fascinate. Hope this helps.
 
DaleV said:
Anytime you do anything root access requiring reboit you will get that error. Either Sammy or Big red put some script in that makes your phone check and replace the recovery if it isn't the stock one. That is easily fixed though, if u are rooted you need something like root explorer. Edit the file extension for /ect / install-recovery.sh. and /system / recovery-from-boot.p and also /system /bin/ recovery I have done this on my debloated debinged, but not yet deodexed, but will be soon, used to be bone stock ed03 fascinate. I actually like it a lot, I have blue cwr3 from times_infinity on xda so I don't know if rom manager works with this or not, I don't use it on the fascinate. Hope this helps.
Click to expand...

I have never run into this issue at all, and I've been rooted and running various ROMS for quite a while now. And ROM Manager doesn't play well with the Fascinate in general now, regardless of CWM version.
 
You must log in or register to reply here.
Back
Top Bottom