[Q] Cannot Install Rom with CWM .... Worked before! - Wildfire General

Hi,
Installed CM Nightlies and now wanted to install pre 2.3 roms.
When I select the zip from CWM I'm getting and error saying there is a scripting error and that edify is not supported from 1.5 etc .... hopefully its a common error.
I tried reflashing 3.2.0.0 recovery but didnt help.
Is there an easy solution for this? As I cannot installed any ROM.

You need Clockworkmod 2.5 for this. So you can either change your main clockworkmod Recovery, or, you can use ROM Manager App from within CM7 ROM. Open ROM Manager, then select "Install CLockworkmod Recovery", then select "Reboot into Recovery" from within the ROM Manager App. This will take you to Clockworkmod 2.5, and you can install Sense based ROMs normally.
Or, if you wish to replace your "main" Clockworkmod 3.x with 2.5.0.7 (Not from within ROM Manager), the Recovery.img file can be found here:
http://www.multiupload.com/PSIIJNBD4E

Ah ..... easy solution then....
So my quesiton is originally I was able to install roms with 3.x Recovery and now I can't, how come this has happened?
I take it that going back to 2.5.0.7 I'll be stuck with the off-line charging bug to?
Thanks for the great help!

This is because Sense ROMs (and Radios) use an older scripting technique (called Amend, which is no longer supported in Clockworkmod 3.x). All the new ROMs like CM have moved to the newer scripting technique called Edify.
And Yes, any version below 3.1.0.2, and you will be stuck with offline charging bug, Which is why it is probably better to install this via Clockworkmod 2.5.0.7 using ROM Manager. This way, you wont get the offline charging bug, and you keep to get both Clockworkmods, 2.x and 3.x

Related

CW Rom Manager can't boot into recovery - freeze at HTC splash screen

Searched, but couldn't find an answer to this. I rooted and installed ROM Manager so I can do a nandroid backup before installing a custom ROM. However, when I press back up in ROM Manager, it restarts and hangs/freezes on the HTC MyTouch 4g splash screen.
What am I doing wrong?
Have you flashed CWM recovery after installing Rom Manager. You must flash the recovery before you can backup/restore or install roms. I almost did that myself but luckily i read the thread concerning it again and flashed REcovery before trying to back up rom.
Yeah, I did that first and the problem remains. I just uninstalled and reinstalled ROM Manager and am about to try "backup current rom" again (unless I should reboot into recovery and back up from clockwork recovery?).
FWIW; Current recovery is ClockworkMod 2.5.1.2
anyone?
Did you ever find a solution to this problem? I just started getting exactly the same. Cant reboot manually into clockwork recovery or from Rom manager :/
If you have flashed a recovery beyond that supported by ROM manager, you will not be able to perform recovery functions from the app (i.e. backup). CW3 is required for CM7 ROMs, but will not be supported by ROM manager until the CM7 RC drops. You can still manually boot to recovery (I always Vol up when powering then select Recovery) and if you have CM7 nightly installed, it has a "reboot to recovery" option in the reboot menu.
You need CWM3 to use CM7.
neronian said:
anyone?
Click to expand...
Click to collapse
Sometimes it is necessary to flash clockwork recovery more than once before it will actually stick. Also, occasionally it will freeze on the splashscreen after a backup, but a battery pull and turning out the phone should be fine.
Sent from my HTC Glacier using XDA App
Here's what's going on:
The Clockworkmod Recovery that you can download from the Market only supports up to CyanogenMod 6.x. For CM7, you need to install Clockworkmod Recovery 3.x, but that version isn't available on the Market yet.
What this means is that you need to find the image file for a CWR 3.x on these forums and manually install it through either a terminal emulator or fastboot. The post below explains how to do it:
http://forum.xda-developers.com/showpost.php?p=10862819&postcount=3
If you flash CM7 using CWR 2.x, your phone won't boot. There's just no way around it.
hammondnav said:
Here's what's going on:
The Clockworkmod Recovery that you can download from the Market only supports up to CyanogenMod 6.x. For CM7, you need to install Clockworkmod Recovery 3.x, but that version isn't available on the Market yet.
What this means is that you need to find the image file for a CWR 3.x on these forums and manually install it through either a terminal emulator or fastboot. The post below explains how to do it:
http://forum.xda-developers.com/showpost.php?p=10862819&postcount=3
If you flash CM7 using CWR 2.x, your phone won't boot. There's just no way around it.
Click to expand...
Click to collapse
Careful with the terminology there. ROM Manager, the app you download from the Market, is a GUI front-end to the CWM recovery image, but you can download and install CWM without using ROM Manager at all. Just because you have ROM Manager installed doesn't mean that CWM recovery is also successfully installed.
TeeJay3800 said:
Careful with the terminology there. ROM Manager, the app you download from the Market, is a GUI front-end to the CWM recovery image, but you can download and install CWM without using ROM Manager at all. Just because you have ROM Manager installed doesn't mean that CWM recovery is also successfully installed.
Click to expand...
Click to collapse
Thanks for pointing that out. I didn't imply that CW ROM Manager and CW Recovery are the same thing though...
hammondnav said:
Thanks for pointing that out. I didn't imply that CW ROM Manager and CW Recovery are the same thing though...
Click to expand...
Click to collapse
You said "the Clockworkmod Recovery that you can download from the Market", and that kinda does. No biggie though.
Just an update for my problem, it turned out that clockwork recovery had corrupted for whatever reason and couldn't be reinstalled from rom manager. As I wanted to test Cm7 anyways I just ended up flashing clockwork recovery 3 manually through fastboot and its all gravy again
Sent from my Desire HD using XDA App
How to flash clockwork recovery from fastboot or fron clockwork recovery 2.51?
Sent from my SGH-T959 using XDA App
Thanks, everyone. What happened with mine, I have no idea, but I randomly opened rom manager and was greeted with an update to the recovery. So I downloaded it and voila - I can now boot into recovery and do backups, etc...

[Q] CMW 3.0.0.6 + pack's Battery mods, unable to flash mod

Okay, I'm running Stock Mysense 2.2.1, rooted, S=off, super CID, and unlocked SIM. I got Clockworkmod 3.0.0.6 here (http://forum.xda-developers.com/showthread.php?t=944681), and I installed Faux123's OC kernel from here (http://forum.xda-developers.com/showthread.php?t=941141). So far, not even a hiccup.
I didn't like the stock battery bar, and I saw that pack had made some battery icon mods, so I decided to install one from here (http://forum.xda-developers.com/showthread.php?t=852013). Even though the mod was designed for Mysense and Mysense ports running CWM pre-3.0, I read in the CWM 3.0.0.6 forum I posted above that 3.0.0.6 was designed to bridge Gingerbread CWM with 2.5.1.4, since it runs ext3 and ext4 (at least I that's what I thought it meant).
First, I tried flashing CWM 2.5.1.4, which it did successfully, but on reboot, I got the red ! symbol, so I went back to 3.0.0.6. When I try to install pack's mod using 3.0.0.6, I get the following messages:
Finding update package...
Opening update package...
Installing update...
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery. Please with to Edify scripting (updater-script and update-binary) to create working zip packages.
Installation aborted.
I'm not really sure what I did wrong, anyone have any ideas? Any help you can provide is very much appreciated.
corruptsmurf said:
Okay, I'm running Stock Mysense 2.2.1, rooted, S=off, super CID, and unlocked SIM. I got Clockworkmod 3.0.0.6 here (http://forum.xda-developers.com/showthread.php?t=944681), and I installed Faux123's OC kernel from here (http://forum.xda-developers.com/showthread.php?t=941141). So far, not even a hiccup.
I didn't like the stock battery bar, and I saw that pack had made some battery icon mods, so I decided to install one from here (http://forum.xda-developers.com/showthread.php?t=852013). Even though the mod was designed for Mysense and Mysense ports running CWM pre-3.0, I read in the CWM 3.0.0.6 forum I posted above that 3.0.0.6 was designed to bridge Gingerbread CWM with 2.5.1.4, since it runs ext3 and ext4 (at least I that's what I thought it meant).
First, I tried flashing CWM 2.5.1.4, which it did successfully, but on reboot, I got the red ! symbol, so I went back to 3.0.0.6. When I try to install pack's mod using 3.0.0.6, I get the following messages:
Finding update package...
Opening update package...
Installing update...
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery. Please with to Edify scripting (updater-script and update-binary) to create working zip packages.
Installation aborted.
I'm not really sure what I did wrong, anyone have any ideas? Any help you can provide is very much appreciated.
Click to expand...
Click to collapse
The reason you get that error is because the update script is made with a amend script rather than a edify script. In order to flash something with the old script you must first flash the 2.5.1.2 version of CwM recovery. Then after you flash your mod you can flash back to 3.0.0.6 recovery. Hope this helps clarify it for you
you can use cwm to get the 2.5.1.2 recovery on there...just select older versions of cwm and select 2.5.1.2...once your done flashing whatever...feel free to flash the 3.0.0.6 recovery again

CWM 3.0.2.8...

Hi to all...
Sorry I'm a noob but I can't find a way to flash version 3.0.2.8 or 3.2.0.0 or 3.2.0.1... Is there a how to somewhere... I've been looking for quite a while but, there are so many threads out there it's just impossible to find an answer...
Thanks in advance!
http://forum.xda-developers.com/showthread.php?t=1003723
Here is the right thread.Its better to prefer 3.0.2.8 cause for 3.2.0.0. have reported some issues.
Great, thanks
The .8 version is an ext4 ver. to my knowledge, and it's no compatible with regular ext3 roms, again to my understanding.
Thanks for the info!!
I flashed the version 3.0.2.8 and everything went well... But, in Rom Manager, it says I'm on version 3.0.2.5... Is there anything I need to do to be on 3.0.2.8?
Thanks-
ROM Manager can only recognize CWM recovery till 3.0.2.6.
So even if you have 3.0.2.8, that number wont actually show up in ROM Manager.
To check if you have 3.0.2.8, make sure it says that in the actual recovery, and not in ROM Manager.
The reason for this is because 3.0.2.8 isnt officially released to the DHD by cwm themselves. This doesnt mean that its not built for the DHD, it just means its not their official release, which is why ROM Manager can only recognise till 3.0.2.6.
For a list of official CWM recoveries, CLICK HERE (the DHD is named as 'ace' in the list).
Here the latest release is 3.0.2.6
[FIX] ROM Manager for newer ClockworkMod Recovery versions!
tagme said:
But, in Rom Manager, it says I'm on version 3.0.2.5... Is there anything I need to do to be on 3.0.2.8?
Thanks-
Click to expand...
Click to collapse
gongoscho said:
The ROM Manager from ClockwordMod show now only recovery images from v2.5.1.4 to v3.0.2.5.
To fix it with a newer version of ClockworkMod Recovery: v3.0.2.8, v3.2.0.0, this steps are needed or only extract attached files..
Click to expand...
Click to collapse
With this fix the Rom Manager detect the correct version of your recovery and you can use the Rom Manager!
grEEtZ,
gongoscho
What is a reason to use a Rom Manager?
You can flash new rom by using recovery...
especially beacuse ROM Manager has sometimes problems with proper wiping cache.
And CWM shows version number properly
re_di said:
especially beacuse ROM Manager has sometimes problems with proper wiping cache.
And CWM shows version number properly
Click to expand...
Click to collapse
ROM manager is a GUI for clockwork, so clockwork is doing the wipe even if initiated from ROM manager therefore problems should be common! saying that I tried MOD][DesireHD][RECOVERY][21-Jun-2011] Clockwork 4.0.0.5.z110621 which wouldn't play nicely with ROM manager at all
I've read many times about troubles with wiping cache in ROM Manager (on this forum too). I've experienced this problem too, so believe me- it is difference between using CWM directly and by ROM Manager.

[q] cm7 to jokersdroid4.2 how to??

I'm currently using Cyanogen Mod7 and its awesome!
But I wanted to try Jokersdroid 4.2 and I'm having this error in recovery-->
Installing update...
Amend script (update-script)is no longer supported.
Amend scripting was deprecated by Google in Android 1.5
It was necessary to remove it when upgrading to ClockworkMod 3.0 Gingerbread based recovery.
Please wsitch to Edify Scripting(updater-script and updater-binary) to create working update zip packages.
Installation aborted.
Please Help me out!
Keep your CM running, and open "rom manager" app. Select "install new rom", select JD zip, make sure to keep selected "wipe data/factory reset" and it will go.
Please do some search before creating threads.
There will be 2types of scripting in creating flashable zips. One is the older amend and other is edify. Some roms need amend and some need edify. The recovery 2.x can flash amend files only whereas recovery 3.x and + can flash edify files only.
So you need to shift between recoveries according to that need. Best way is to flash 2.x recovery (select "flash recovery") from rom manager which creates update.zip in root of your sdcard. Just reboot to your current 3.x + recovery and first flash the update.zip file like any other Rom. It gives you 2.x recovery which can flash your amend files.
Sent from my HTC Wildfire using XDA App
sorry bharat for me starting a new thread.. But I was completely lost on how do I overcome this! I was also thinking about the similar solution but I wasnt exactly sure on how to push lower ver. recovery through fastboot usb... Your reply did the thing
ROM manager and clockwork recovery combination is a powerful tool... bharatgaddameedi already said what I typed for the last 5 minutes....
DELETE !!!
Note to self : Read all answers before typing a reply
Don't forget to backup your cm7 using rom manager first. You can then restore cm7 later on if you desire without the need to switch back to clockworkmod 3
Sent from my HTC Wildfire using XDA App

[Solved]Can't boot CWM 2.5.x through ROM Manager - keeps going to CWM 3.2

Hi
I am currently running the latest CM 7 nightly build. However, I have issues with GPS which doesn't find any satellites.
In order to re-flash the radio (which I have tried previously), I need to use ClockWorkMod Recovery 2.5.x. Currently I have 3.2.0.0.
I have previously used ROM Manager to do this, but now when I install 2.5.0.7 through ROM manager and select Reboot to recovery it simply reboots into 3.2.0.0.
I have tried reinstalling ROM Manager from Android Market after complete uninstall. But the same things keeps happening.
Any suggestions?
BR, Martin / mhca
Is a small "bump" allowed...?
I haven't found a solution yet. I have even played around with different ROMs without success. Is it a bug in ROM Manager?
Do I have to first upgrade CWM to 5.0.0.2 and then afterwards try to use ROM Manager to hopefully reboot into CWM 2.5.0.7 ?
Flash this ZIP in your existing CWM3/4/5 setup. Then you can get temporary 2.5.0.7 without touching the ROM Manager app:
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
(It's the same temp 2.5.0.7 which ROM Manager downloads.)
Thanks a ton!
I just realised that this was even written with small text in The Complete Wildfire index, right next to the links to the radio. But somehow I missed that.
Really glad that you gave me a fail-safe method which doesn't require Rom Manager.
Radio didn't flash with CWM - used Android Flasher
Although I got a working CWM 2.5.0.7 with the above-mentioned method, I couldn't properly flash the radio.
I got error message "no space left on device", must likely due to custom partition sizes.
I found out that I could use the Windows app Android Flasher to flash the radio. And now my GPS works

Categories

Resources