Develop Bugs

Fake Flash? Quick Boot? Confused

I tried this in the Q-n-A but no response so thought I would post it here. Sorry for the clutter.
I am rooted with Toasts method and have his .6 rom running (Thanks Toast )
I have been trying to follow the fake flash thread as well as the quickboot.
Are they dependent on each other? Do I need to do fake-flash THEN quick boot to get the rom manager to be able to reboot into recovery?
Or do all I need to do is push the reboot and follow the quick boot instructions?

Well atm quickboot is how you get to the recovery. They havent frigured out how to get there from just booting up yet.*It will come in due time, we have great devs here.*
But you can either have one or the other, hell even both. But the Fake flash you can do with out a computer*Toash method*
The Rom Manager is basicly the same thing as the fake flash there is just a app for that. from what I know
Hope this could be of some help

Ok cool, so if I do the Quick Boot thing, I can reboot to recovery through the Rom Manager directly? Sounds like the way to go for now.

Bielinsk said:
Ok cool, so if I do the Quick Boot thing, I can reboot to recovery through the Rom Manager directly? Sounds like the way to go for now.
Click to expand...
Click to collapse
I did the fake flash first......which will install the update.zip to sdcard which is ur on board recovery then you will have to read the quickboot thread to fix the ability to reboot, the reboot file needs to be replaced before quickboot or Rom manager can reboot the phone into recovery.

beerock said:
I did the fake flash first......which will install the update.zip to sdcard which is ur on board recovery then you will have to read the quickboot thread to fix the ability to reboot, the reboot file needs to be replaced before quickboot or Rom manager can reboot the phone into recovery.
Click to expand...
Click to collapse
OK, I thought all I needed to do was the quickboot thread, then your response got me all confused again about what I need to do.
From my understanding, Rom Manager and Quickboot do the same thing as far as rebooting to recovery.

just get the free version of Rom Manager and then the paid license.. thats all you need

Bielinsk said:
OK, I thought all I needed to do was the quickboot thread, then your response got me all confused again about what I need to do.
From my understanding, Rom Manager and Quickboot do the same thing as far as rebooting to recovery.
Click to expand...
Click to collapse
You are not alone buddy.. I just want to flash custom roms away from a pc the easiest way but not sure now either.
Sent from my EVO using Tapatalk!

OK, if you are rooted with Toasts all you have to do is follow the instructions that are in the Quickboot thread.
I loaded Rom Manager and clicked download clock thingy.
Then I rebooted to toasts recovery and ran the windows.bat file to get access to ADB.
follow the quickboot thread.
Now from Rom Manger you can select reboot to recovery and that will take you into a reboot and end up in recovery where you can backup, wipe, flash etc.
No computer needed.

Bielinsk said:
OK, if you are rooted with Toasts all you have to do is follow the instructions that are in the Quickboot thread.
I loaded Rom Manager and clicked download clock thingy.
Then I rebooted to toasts recovery and ran the windows.bat file to get access to ADB.
follow the quickboot thread.
Now from Rom Manger you can select reboot to recovery and that will take you into a reboot and end up in recovery where you can backup, wipe, flash etc.
No computer needed.
Click to expand...
Click to collapse
thanks..so you didnt do anything in the fake flash thread?

MrDSL said:
thanks..so you didnt do anything in the fake flash thread?
Click to expand...
Click to collapse
Nope, I posted all I did and now can reboot into recovery from Rom Manager.

well ROM Manager force closes on me when I try and download clockwork and then if i try and relaunch it without rebooting it will run and download clock but then just stays at su request and then force closes..i imagine because it force closes the first time i try and click the clock button.

MrDSL said:
well ROM Manager force closes on me when I try and download clockwork and then if i try and relaunch it without rebooting it will run and download clock but then just stays at su request and then force closes..i imagine because it force closes the first time i try and click the clock button.
Click to expand...
Click to collapse
Please send me a logcat using the free Android Log Collector app from the Market to [email protected]

Koush said:
Please send me a logcat using the free Android Log Collector app from the Market to [email protected]
Click to expand...
Click to collapse
sent..it looked pretty long though

Okay I wiped everything and reloaded ROM using clockwork and then installed ROM Manager and choose manual override and the su permisssion screen came up correct and choose allow all and then hit recovery rom and nothing happens..it doesnt force close though

I don't know if it was my rom or what but I wiped everything and loaded a new version of rom and now rom manager boots to recovery!! I think it had something to do with Su permission cause this time it went to the correct screen and I selected allow all always and its all good.
I flashed right from phone! I purchased rom manager to support your wonderful work.
Thank you!
Sent from my EVO via Tapatalk!

[RECOVERY] ClockworkMod Recovery for Galaxy S i9000 (FINAL! SAFE!)

First things first, if you flashed a previous version of Clockwork Recovery using Odin, FLASH BACK TO A STOCK KERNEL. (There's another link in the forum to do this, I can't find it at the moment)
This recovery is *very* safe to use. It does NOT flash your kernel; it is a completely uninvasive recovery method.
How it works: The recovery is packaged as an update.zip that you run from STOCK recovery. The update.zip unpacks Clockwork Recovery onto the ramdisk and restarts recovery. When you reboot, it reverts back to the original, unmodified, stock recovery. So, you will need to keep the recovery on the root of your SD card as an update.zip, and apply the zip every time you want to start Clockwork.
HOWEVER, if you use ROM Manager, all of the recovery installation and management are done for you!
Installation instructions:
Download ROM Manager from the Market.
Flash Recovery.
Choose Galaxy S i9000 as your phone.
Accept the Superuser prompt.
Use ROM Manager to create a Backup.
On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
Watch the backup go!
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!
If you can't seem to get ROM Manager off the market, you can get it from my homepage:
http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html

Just installed! Working great!

Installed with ROM manager. Works like a charm! Thanx alot Koush!

works fine

works like a charm

Installed, everything working without problems.
To install roms with clockwork we need roms in *.zip format? Where to get them?
Sent from my GT-I9000 using Tapatalk

Just got my phone
will try it after charging ]
YOU ARE THE MAN
thank you and thanks all Xda devs and members

hmm ... I know this might sound stupid but, acually GSG is my first android phone, though I know how to flash roms with odin and how to apply update.zip and all that but what is the difference between this and ClockworkMod Recovery ?? and does it use the same components as odin ? (I mean CODE, CSC, MODEM and Pit) ?

Stickied. Closing the other one. Not sure why you would start a new thread instead of modifying the old one though...

Thanks Koush your the man. Coming from a htc magic I hate this odin bull

Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
EDIT: After rebooting my phone and trying to open ROM Manager again, I have some sort of "Recovery Failure" screen with 3 options:
- Recovery mode is broken.
- ROM Manager doesn't reboot.
- Other.
?

Arkymedes said:
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
Click to expand...
Click to collapse
Do you already have an update.zip on your internal sdcard? If yes, rename it, and then should boot just fine!

kalpik said:
Do you already have an update.zip on your internal sdcard? If yes, rename it, and then should boot just fine!
Click to expand...
Click to collapse
Ahhh... I guess I'm not very used to this "Internal SD Card" thing... there was the update.zip I used to root the phone there and I only checked my regular External SD.
Everything is fine now, sorry for bothering.

Arkymedes said:
Hmm... did every step and in the first reboot, after using rom manager to create a backup, it was supposed to go to the cloclworkmod recovery screen as mentioned, but instead it goes to the regular recovery screen.
Bug? I'm using the JM1 FW
EDIT: After rebooting my phone and trying to open ROM Manager again, I have some sort of "Recovery Failure" screen with 3 options:
- Recovery mode is broken.
- ROM Manager doesn't reboot.
- Other.
?
Click to expand...
Click to collapse
I had the same issue. Must have been the update.zip, but I didnt remove it, just pressed the other option, went into manual recovery mode, rebooted went into rom manager and backed up my files. Worked a charm

Does this mean there will be no more work on a permanent recovery solution?
I have the Korean version M110S - and it does not have the standard recovery (it is crippled - no apply:update.zip). Is there and abd command to "apply update.zip" ?

May I ask if this work for me using mimocan ext4 fix on the backup/restore?

This may sound stupid, but I'm kinda new to Android modding (SGS is my first droid, moving here from WiMo on SE-X1) and.... What is Clockwork?

So if I ever needed to send this phone in for warranty purposes, I could just flash the backup of my stock ROM in and I should be good to go?

does this method works for captivate and vibrant???
edit: just install/ captivate and vibrant option available.

Rithina said:
May I ask if this work for me using mimocan ext4 fix on the backup/restore?
Click to expand...
Click to collapse
Worked for me with mimocan ext4 fix

[Q] How to install MotoGinger 2.3.4 :(

Hi Guys,
I could not install the Rom MotoGinger 2.3.4 Can some one please guide me with proper steps? I have installed froyo and its rooted, Also installed the 2init.
I didnt understand the 2nd step steps, When exactly should I install the nandroid-backup and after installation why should I wipe? Please can someone help me out?
- Starting installation with any original froyo 2.2.2 (rooted)
- Install original 451-134 in "normal way"---> nandroid-backup (thx to walter79)
1. wipe via CWM
2. advanced restore (system/only)
3. flash fixed-sbf
4. wipe via stock recovery, then reboot.
----> DOWNLOAD
- From market download and install defy 2nd init
- Choose latest recovery (cwm 4.0.0.6)
- Download MotoGinger.zip and copy in microsd
- Enter in recovery, wipe/data and install motoginger as a zip file, then reboot!
- To return to any froyo rom, you just flash with rsd lite in the usual way! Before the flash, i suggest wipe/data and cache from recovery!

I did it in the following way:
Recieved my phone with 2.1, booted the phone and rooted the phone.
Installed Clockwork Mod recovery.
Booted in clockworkmod recovery.
Made a nandroid of my current device.
Restored nandroid of my choice 2.3.4
Cleared cache and factory reset.
Booted into Flash mode
flashed fixed SBF
booted phone.

gommers1978 said:
I did it in the following way:
Recieved my phone with 2.1, booted the phone and rooted the phone.
Installed Clockwork Mod recovery.
Booted in clockworkmod recovery.
Made a nandroid of my current device.
Restored nandroid of my choice 2.3.4
Cleared cache and factory reset.
Booted into Flash mode
flashed fixed SBF
booted phone.
Click to expand...
Click to collapse
Okay I followed your steps but once I flash the 3.4.3-36-1.7.fixed.sbf It boots up to the bootmenu and when I set the boot mode to 2ndinit or normal its still not booting

chuck tat process..here is the new way to install motoginger
- From market download and install defy 2nd init
- Choose latest recovery (cwm 4.0.0.6)
- Download MotoGinger.zip and copy in microsd
- Enter in recovery(press vol down when u see blue led during boot), wipe/data and install motoginger as a zip file, then reboot!

arpith.fbi said:
chuck tat process..here is the new way to install motoginger
- From market download and install defy 2nd init
- Choose latest recovery (cwm 4.0.0.6)
- Download MotoGinger.zip and copy in microsd
- Enter in recovery(press vol down when u see blue led during boot), wipe/data and install motoginger as a zip file, then reboot!
Click to expand...
Click to collapse
Buddy I did that.. It didnt work.. I had rooted stock froyo before I flashed.. which version you were in?

wat actually happened when u entered bootmenu? did u go to custom recovery?did u wipe partition,cache,data and all before installing from sd card?

arpith.fbi said:
wat actually happened when u entered bootmenu? did u go to custom recovery?did u wipe partition,cache,data and all before installing from sd card?
Click to expand...
Click to collapse
I did "wipe data/factory" and wipe cache partition then installed the motoginger and when i reboot it takes me to the boot menu then i selcted boot->2nd-init and it again boots to the boot menu and if i select boot->normal the screen hust goes blank and nothing happens.

looks like 2nd-init is acting weird..make sure ur 2nd-init is 0.6.1..and entering bootmenu check whether cmw is 4.0.0.6..

arpith.fbi said:
looks like 2nd-init is acting weird..make sure ur 2nd-init is 0.6.1..and entering bootmenu check whether cmw is 4.0.0.6..
Click to expand...
Click to collapse
Yes I have installed 2nd-init 0.6.1 and when I go to custom recovery I see the version 2.5.1.8 at the top.. BTW are you using that rom still? howz the battery life?

Oh.. boy.. finally I got it.. shadow4.5.1-134rootednandroid.zip is not a nandroid backup but it has system.img which I must restore it..
@arpith.fbi Thank you for your support..

Hi Guys,
i just installed the 4th test Ginger but not really get what is
motoginger-4.zip for?
Could you explain it a bit.
I also do not know how to get 720p recording with this 4th test version?
My camera seems to work but only the usual stock resolutions are listed
in the camera mode...
I also do not find the new live wallpapers and all the mentioned nice added stuffs?
Thank you and sorry for my bad english.
Br
Attila

I was wondering the same question Thanks!

MooonWalker said:
Hi Guys,
i just installed the 4th test Ginger but not really get what is
motoginger-4.zip for?
Could you explain it a bit.
I also do not know how to get 720p recording with this 4th test version?
My camera seems to work but only the usual stock resolutions are listed
in the camera mode...
I also do not find the new live wallpapers and all the mentioned nice added stuffs?
Thank you and sorry for my bad english.
Br
Attila
Click to expand...
Click to collapse
well motoginger-4.zip is another way to install the ROM through custom recovery...no restoring no flashing in required..supposed to be an easy way to install a ROM..
720p patch is only for red lens defy..it wont work on green lens..again u have to install the patch through custom recovery..

kyut said:
I was wondering the same question Thanks!
Click to expand...
Click to collapse
I solved the problem by myself.
The reason was that i tried to apply motoginger-4.zip with
goapk custom recovery because it seemed to work!!
I got a success message!
Finaly i installed 2ndInit and latest recovery and used it.
Finally everything worked.
My only problem that i can not switch off the lock screen in security menü as in 2.2.2 worked fine.
Br
Attila

Question regarding kernel

Ok... this is weirdest bug i ever seen.
After wipe all data (all thing) up new rom eg. paranoid, AOKP, myOneV... all of them.
1/Stock kernel is default, but modder need uploaded new kernel to run ether rom.
2/Flash new rom needed...yeah we got new kernel at first time... but when reboot phone.... what the f.... auto back-up to default kernel??
IE: AOKP, myOneV, CM10, ... need newest kernel to run, done... but only first time, the second boot is bricked....
=>Solve this for me plzzzz
My idea: why we don't cook new kernel vs new rom when release new version?

u need to do fastboot flash recovery (nameofrecovery). img
u must have done fastboot recovery (nameofrecovery). img
Sent from my One V

paarthdesai said:
u need to do fastboot flash recovery (nameofrecovery). img
u must have done fastboot recovery (nameofrecovery). img
Sent from my One V
Click to expand...
Click to collapse
"Flash new rom needed...yeah we got new kernel at first time" i know so do i ... that's my problem, flash done 1st run is ok but reboot in 2nd is bricked. So i MUST flash recovery when 2nd and 3rd and 4th when reboot... fk... i my phone gonna R.I.P

i ain't understanding a **** u tokn dude
Sent from my One V

paarthdesai said:
i ain't understanding a **** u tokn dude
Sent from my One V
Click to expand...
Click to collapse
lemme explain what did he say, he got prob when up new rom, the rom needed flash boot (new kernel), he know about it. The 1st is flash, boot to phone, he can see new kernel in setting then use whatever like overclock, undervolt, install app,... then he make a reboot (restart) go to setting menu, he regconize the original kernel is back, overclock is disable, same at undervolt and bricked phone if original kernel no compatible with that rom. That's the PROBLEM.

kenintel said:
lemme explain what did he say, he got prob when up new rom, the rom needed flash boot (new kernel), he know about it. The 1st is flash, boot to phone, he can see new kernel in setting then use whatever like overclock, undervolt, install app,... Then he make a reboot (restart) go to setting menu, he regconize the original kernel is back, overclock is disable, same at undervolt and bricked phone if original kernel no compatible with that rom. That's the problem.
Click to expand...
Click to collapse
bootloop is not bricked phone!!!
If you had a bricked phone you will never ever be able to power up your phone!

1ceb0x said:
bootloop is not bricked phone!!!
If you had a bricked phone you will never ever be able to power up your phone!
Click to expand...
Click to collapse
err my bad, so how to solve this?
I mean default kernel loop when 2nd reboot...

Do this
Go to fast boot
Open cmd
Fastboot flashboot boot.img
Now don't restart go to the recovery and wrote all cache and then flask which ever roms u want, believe me this will work ....
Sent from my One V using xda app-developers app

cybervibin said:
Do this
Go to fast boot
Open cmd
Fastboot flashboot boot.img
Now don't restart go to the recovery and wrote all cache and then flask which ever roms u want, believe me this will work ....
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
1/Go to fast boot
Open cmd
Fastboot flashboot boot.img <---- which boot.img? "stock kernel"
When flashboot device MUST restart, i cant resist that...
2/Now don't restart go to the recovery and wrote all cache
Wipe all data or wipe all cache? dalvik cache? can u explain....

See when u go.to a rom page there will be a link for kernel......and take the kernel and don't restart our it will be stuck in boot loop....
No go to recovery with out restarting....wipe all data if a new rom...
And then download the link and
Sent from my One V using xda app-developers app

i think they are using hassoon tool to flash the kernel, because that script will automatically reboot the phone after the kernel is flashed .
1.You need to first, take THE kernel for the RESPECTIVE ROM
2. Rename it to boot.img
3. You have to have installed the Android SDK + the platform tools to be able to take advantage of fastboot
4. Reboot your phone into bootloader.
5. Connect your phone to your PC.
6. Press start, enter RUN and type cmd. Press enter.
7. Type your path where your sdk is installed (i.e CD C:\Program Files\Android\android-sdk\platform-tools\)
8. Put the boot.img into the platform-tools folder
9. Now go back to CMD use "fastboot flash boot boot.img" without the quotes.
10. It will send a message like "sending boot.img.... done... writing boot img.... done.... elapsed x seconds).
11. Reboot Recovery from bootloader.
12. Wipe everything and then flash your rom.
13. Reboot and that's it.
As simple as that. If you don't know how to use android sdk or you don't have it installed, simple use the search bar and type android sdk tutorial.

thanhi said:
Ok... this is weirdest bug i ever seen.
After wipe all data (all thing) up new rom eg. paranoid, AOKP, myOneV... all of them.
1/Stock kernel is default, but modder need uploaded new kernel to run ether rom.
2/Flash new rom needed...yeah we got new kernel at first time... but when reboot phone.... what the f.... auto back-up to default kernel??
IE: AOKP, myOneV, CM10, ... need newest kernel to run, done... but only first time, the second boot is bricked....
=>Solve this for me plzzzz
My idea: why we don't cook new kernel vs new rom when release new version?
Click to expand...
Click to collapse
I edited your thread title. In the future, please follow forum rules and include a relevant and descriptive thread title. Using vulgarity is unnecessary, offensive, and not welcome on XDA.

[Guide] 2012 WFS CWM/Root

Intro: People with 2012 WFS reported to have no CWM visuals (i also do)
*NOTE: Even if you DID install this CM based rom wont work only stock based one*
CWM:
1. Unlock bootloader via HTCdev.com (look for guides there are plenty here)
2.Download http://www.mediafire.com/?pqtgftm40909r31 *updated*
3.Extract to C:/
4.Go to fastboot
4.Open Command prompt
5.type cd c:/WFS
6.type fastboot flash recovery recovery.img
7.wait for flashing to finish
8.Remove battery
9.Go to bootloader
10. click recovery wait for visuals
ROOTING:
*same as other methods*but..
1.move the cursor up then down until you see ( back button enabled)
2.Backup
3.Flash root.zip
Credits to fellow member pashaa for sharing recovery file
*NOTE* Dont blame me if anything happens to your device. I've Warned yah!
If you cant understand or want help post here and i'll try to help you out
ScreenShot of my recovery below

i dont get any visuals of black screen..just htc logo...and would you mind telling which cwm recovery version is this?? and will it work ony on this particular recovery?

vshl2995 said:
i dont get any visuals of black screen..just htc logo...and would you mind telling which cwm recovery version is this?? and will it work ony on this particular recovery?
Click to expand...
Click to collapse
modded 5.0.2.8
Sent from my Nexus 7 using xda premium

are youu sure you downloaded the recovery file correctly because it works for m
e??? all other recovery doesn't work except for that one
Sent from my Nexus 7 using xda premium

ngoralph said:
are youu sure you downloaded the recovery file correctly because it works for m
e??? all other recovery doesn't work except for that one
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
no i havent done this right now..i was asking because i tried to do the same procedure with official recovery some days ago..actually its my girlfriend's phone not mine and she is eating my head off because of low memory!!! anyway thanxx..ill try this asap and report back..!!

Link updated
Sorry for inconvenience
http://www.mediafire.com/?pqtgftm40909r31

WORKS
Works gr8...great job :good::good:

Confirmed, works here too. THX!

Thanks man,great job!.Finally I have visual recovery!Flashing ROMs or ZIPs allways conected to PC is not a pleasure!

sorinaugusto said:
Thanks man,great job!.Finally I have visual recovery!Flashing ROMs or ZIPs allways conected to PC is not a pleasure!
Click to expand...
Click to collapse
you can flash cm roms before?????

No,for my phone just Roms based on stock works.I have flashed and was working EQDKP roms,WildChild roms ,Superior sense rom,Kims mod rom.I have tried CM 7 and MIUI but did not work.But I am very interested to try CM roms or MIUI,so if you have any solutions for this please share with us.Thanks again.

cwm
I`m so Happy! It works on my wildfire s 2012! Thank you very, very much for your gift .

custom
ngoralph, i have one question - Can i flash a custom ROMs or kernels? or can i flash cyanogen any version (may be on stock kernel, if it`s possible?). Answer please, and thanks again!

Can i flash a custom ROMs or kernels? or can i flash cyanogen any version (may be on stock kernel, if it`s possible?).
Click to expand...
Click to collapse
I can answer this question: it is impossible. There are certain problems in work of this Mod. The first: does'nt making full nandroid backup. The second: does'nt flashing boot.img. It is necessary to develop this program still. But something, already is able: root, interface modding, ect....

Howdy.
I have flashed this recovery image and for the first time, can boot into recovery and see what I'm meant to see! Thanks. Previously (2012 hardware) I just hung on the white HTC logo screen.
Now, if I select backup and restore, press the power button, all the text disappears and I'm left with the central hat image... but nothing much happens. Pressing power again brings me back to the main menu. Same thing with -power off. The top option of reboot system now works just fine.
Any ideas? I'd like to backup my current system before flashing WildChild 3, you know - just in case anything goes wrong!
EDIT: immediate edit. cancel all of the above, I'm just new to recovery (obviously!). I went through the main menu a few times, it told me the back button was now active and away I go - backing up as we speak! Apologies!!! and thanks!

cwm
You must press one time into recovery volume + and several time volume - , while apear "back button is enable" and then such as in any cmw.

nitnit said:
You must press one time into recovery volume + and several time volume - , while apear "back button is enable" and then such as in any cmw.
Click to expand...
Click to collapse
i dont fully understand you but click volume up then down then up then downthenvolume up then down until back button enabled shows up

nitnit said:
ngoralph, i have one question - Can i flash a custom ROMs or kernels? or can i flash cyanogen any version (may be on stock kernel, if it`s possible?). Answer please, and thanks again!
Click to expand...
Click to collapse
haven't tried cm roms on stock kernel would anyone here like to try???

Uksus17 said:
I can answer this question: it is impossible. There are certain problems in work of this Mod. The first: does'nt making full nandroid backup. The second: does'nt flashing boot.img. It is necessary to develop this program still. But something, already is able: root, interface modding, ect....
Click to expand...
Click to collapse
agree with you here but i dont think anyone is willing and able to work on this recovery.

ngoralph said:
haven't tried cm roms on stock kernel would anyone here like to try???
Click to expand...
Click to collapse
i.m using now a custom kernel on my wfs2012 (overclocked 815 MGz) without trouble, but i can`t flash any CM roms because it hapens error Status7 in CWM. I think that this CWM is too old to flash CM ROMs. But we have no any choise