Red Clockwork Recovery

CWM Red was initially created to work with voodoo kernels, but has been adapted to work with both voodoo and nonvoodoo kernels. It will always say "Voodoo Lagfix Recovery" regardless of which type you are using.

If you haven't intentionally flashed a voodoo kernel, you're not running one. Once you do flash one, you will hear a female robot voice describe the process of the system conversion from RFS to EXT4, and usually takes 5-10 minutes to complete.

As far as the bitmap errors, those will always be there too, and don't mean anything.
 
  • Like
Reactions: JOrtenzi
CWM Red was initially created to work with voodoo kernels, but has been adapted to work with both voodoo and nonvoodoo kernels. It will always say "Voodoo Lagfix Recovery" regardless of which type you are using.

If you haven't intentionally flashed a voodoo kernel, you're not running one. Once you do flash one, you will hear a female robot voice describe the process of the system conversion from RFS to EXT4, and usually takes 5-10 minutes to complete.

As far as the bitmap errors, those will always be there too, and don't mean anything.

Great, just what I was looking for... thanks!
 
CWM Red was initially created to work with voodoo kernels, but has been adapted to work with both voodoo and nonvoodoo kernels. It will always say "Voodoo Lagfix Recovery" regardless of which type you are using.

If you haven't intentionally flashed a voodoo kernel, you're not running one. Once you do flash one, you will hear a female robot voice describe the process of the system conversion from RFS to EXT4, and usually takes 5-10 minutes to complete.

As far as the bitmap errors, those will always be there too, and don't mean anything.

Great, just what I was looking for... thanks!

If you upgrade to sc 2.9, Adrynalyne has included the most current red cwm-all which does not have the bitmap error messages and seems to be completely stable. Once you upgrade to 2.9, all you would need to do is delete update.zip from your sd card, power down the phone, pull battery and flash this file MEGAUPLOAD - The leading online storage and file delivery service in ODIN, power up phone. Then every time you boot to recovery you will boot directly to red cwm-all without the error messages without having to go through blue stock recovery and apply sdcard:update.zip
 
If you upgrade to sc 2.9, Adrynalyne has included the most current red cwm-all which does not have the bitmap error messages and seems to be completely stable. Once you upgrade to 2.9, all you would need to do is delete update.zip from your sd card, power down the phone, pull battery and flash this file MEGAUPLOAD - The leading online storage and file delivery service in ODIN, power up phone. Then every time you boot to recovery you will boot directly to red cwm-all without the error messages without having to go through blue stock recovery and apply sdcard:update.zip


I agree with Shark. A very stable ROM!!! Have not FC once.
 
I agree with Shark. A very stable ROM!!! Have not FC once.

Thanks Mike. I was actually saying the cwm-all is really stable, but I agree that 2.9 is stable as hell. I've been flashing like crazy trying to figure out our previous problems of getting force close loops at boot animation, and I haven't had one force close even with flashing some wacky combinations. I think it is the combination of how stable 2.9 is paired with how stable cwm-all is which we got from jt1134 over at XDA. Time for me to go donate to him too.
 
  • Like
Reactions: JOrtenzi
Thanks LandShark...

Next question...

Being new to the whole darkside of rooting, flashing, etc...

I have only used ODIN so far to flash roms/kernels. What are (if any) the advantages of using CWM Red to do it? And also.... how exactly do you do it?? lol

Thanks!
 
Like JOrtenzi, I have only used Odin, but last night I updated using CWM to SFC_2.9nv... and to get there, I ran the Odin version of "cwm-recovery-ALL" to get to the RED CWM, and then CWM'ed to get to 2.9... and all seemed to work GREAT...BUT... now when I check the folders on my SD card, I see a VooDoo folder... am I now VooDoo'ed (how can you tell?), and if so, what sort of problems have I created for myself...The notification pull down shows "SC 2.9"... can I un-VooDoo?? Thanks, DJ
 
Like JOrtenzi, I have only used Odin, but last night I updated using CWM to SFC_2.9nv... and to get there, I ran the Odin version of "cwm-recovery-ALL" to get to the RED CWM, and then CWM'ed to get to 2.9... and all seemed to work GREAT...BUT... now when I check the folders on my SD card, I see a VooDoo folder... am I now VooDoo'ed (how can you tell?), and if so, what sort of problems have I created for myself...The notification pull down shows "SC 2.9"... can I un-VooDoo?? Thanks, DJ

No you are not voodoo'd, you are fine. cwm was originally intended for voodoo but has been converted to work for nonvoodoo. You will notice when you boot to red cwm it says voodoo lag fix at the top. Just ignore that. If you didn't flash a voodoo kernel and a voodoo rom you didn't go to voodoo.
 
Thanks LandShark...

Next question...

Being new to the whole darkside of rooting, flashing, etc...

I have only used ODIN so far to flash roms/kernels. What are (if any) the advantages of using CWM Red to do it? And also.... how exactly do you do it?? lol

Thanks!

The only reason you have flashed roms and kernels in ODIN is because DroidXcon packaged them up in ODIN flashable files. ROMs and kernels are normally flashed in cwm. Right now the only way to flash themes, mods, and add-ons is through cwm. There really aren't advantages or disadvantages of one over the other. Tar and bin files get flashed through ODIN, and zip files get flashed through cwm. In order to use cwm, you save the zip file to your sd card like the way you did for the update.zip when you used DroidXcon's all-in-one ODIN package. I have laid out step by step instructions. Start by following my instructions in post #14 on page 2 of this thread: http://forum.androidcentral.com/ver...answer-phone-when-receiving-calls-rooted.html then follow the instructions in the link in my signature.
 
Thanks LandShark... So if I'm not VooDoo'd... what about the VooDoo folder on the SD card ?? Do I need it, or can I just blow it away? DJ
 
Thanks LandShark... So if I'm not VooDoo'd... what about the VooDoo folder on the SD card ?? Do I need it, or can I just blow it away? DJ

Don't delete it. It gets put there when you install the cwm. It's not going to hurt anything and it doesn't take up any space or memory.
 
  • Like
Reactions: DJKnut
i went in to recovery and it was blue. what do i need to do to get red, install update.zip from there or flash the cwm-recovery-all in odin?
 
when i try to extract it, it gives me a file called recovery.bin. no .tar
 
Thanks LandShark... So if I'm not VooDoo'd... what about the VooDoo folder on the SD card ?? Do I need it, or can I just blow it away? DJ

That folder contains a file labeled disable_lagfix if i'm not mistaken, and basically tells a voodoo kernel not to convert the system data formatting to voodoo. Delete it if you're not using a voodoo kernel with no ramifications. It's just there to keep voodoo from activating if you want it turned off, and will be regenerated after you disable voodoo from CWM, and the file in question will be removed when you enable it.
 
new to the fascinate, big DX user. I cant flash an themes. I'm using red CWM on 2.9.1. transbluhoney or bluesteal. Boot loops. Doing complete wipes and everything. Data/Cach/ Dal and still nothing
 

Trending Posts

Forum statistics

Threads
956,708
Messages
6,969,579
Members
3,163,599
Latest member
Marabishi