[How to] Install and Use Clockworkmod Recovery w/Screen captures

This is a new problem for me, when I try to make nandroid backups everything is good until i get to generating md5 sum, after that its says error generating md5 sum!

It has never done this before, until today. I tried to delete some of the nadroid backups i had awhile ago thinking there will not be enough space but still did not work.
 
This is a new problem for me, when I try to make nandroid backups everything is good until i get to generating md5 sum, after that its says error generating md5 sum!

It has never done this before, until today. I tried to delete some of the nadroid backups i had awhile ago thinking there will not be enough space but still did not work.

Just another thing that isn't fully fixed with cwm. jt and gizmodroid are working on it, but last I checked, they haven't said anything yet about a fully functioning cwm. Check out gizmodroid's thread to get what is for now the most current and almost completely functioning cwm

http://forum.androidcentral.com/ver...od-superclean-roms-erasing-cwm-confusion.html
 
  • Like
Reactions: pikanate
Enable and Disable Voodoo Lagfix:
After flashing a voodoo kernel lagfix will usually intiate conversion itself but this is not always the case,
the best way to ensure conversion will initiate is to enable lagfix.
When flashing a nonvoodoo kernel after your phone has converted lagfix,
it is Highly recommended to disable lagfix first.
To learn more about Voodoo please join this discussion http://forum.androidcentral.com/ver...ks/55753-how-voodoo-updated-9-mar-2011-a.html

Enabling Lagfix
After flashing a voodoo kernel (see post #5 how to flash) Lagfix should be enabled before reboot.

enablelagfixproc.png


Disabling Lagfix
Before flashing a nonvoodoo kernel to a lagfixed enabled system lagfix needs to be disabled. After it is disabled fully reboot your system then you can power down, boot back into clockwork recovery and flash your new kernel.

disablelagfixproc.png


I am running super_frankenclean v2.9 (voodoo) w/ EC01 radio....I am overclocked and when I run Quadrant it shows that I am running 1385 which is amazing! The only question I have is that when I reboot to recovery and go to the 'voodoo' tab, it shows the text below:

Voodo lagfix is actually: diabled
next boot: enabled

Options:
/system lagfix conversion: yes
debug mode: no

When I reboot I assumed that Voodoo lagfix would switch to 'enabled', but it never does....with my speed I assume that I am actually running voodo (speeds used to be around 845 or so even when overclocked), but why doesn't it show that it's enabled? Maybe I'm missing something
 
@lurch162534

Look at Post #128 in this thread. Context is important, so it may help to read a couple (5) posts before and after to make sure it answers the question you are asking.

I had the same question. This should save you the 20 minutes or so that I spent scanning through this thread.

Hope that helps.
 
****************************************************
Installing and using Clockworkmod recovery as any other hacking is done at your own risk, I nor Android Central are
responsible for anything that users do to their phone. That being said, Have fun :)

****************************************************

Q: What is ClockworkMod Recovery(aka CWM or clockwork)?
A: ClockworkMod Recovery is a custom recovery that allows you to install custom ROMs, themes, patches,applications and more.It can also be used to do many other fuctions which the most commonly used will be outlined in this tutorial. It was developed by Koushik Dutta. The mose recent versions have been modified by jt1134 over at the XDA forums to work with all versions of fascinate builds.

Q:I just downloaded Rom Manager from the market but clockworkmod recovery is not working?
A:At the moment the latest versions of clockworkmod recovery are orange with build numbers 3.x.x. Unfortunatley this can not be used because in order to install any flashable .zip file a script of code is required to direct the installation. At the moment almost everything written for fascinate has been written in a language called Amend. The most recent version 3.x.x only accepts a language called Edify, in previous versions of clockwork (anything under 3.x.x) were compatible with both Amend and Edify. There are also other limitations why Rom Manager can not be used but i dont understand them nor will i pretend i do, but honestly does it really matter? Lets just focus on what works. While the devs take care of finding a way to make it work.

Q: What is the best most recent version of clockworkmod?
A: Currently the latest and greatest version of clockworkmod is Red CWM ALL. There are instructions and downloads in post #2 of this thread.

Q: My clockwork is Red does this mean i have the latest, CWM ALL?
A: No, there is also CWM froyo which was the version just before all, you can not distinguish the 2 because both share the same version number. But the ways you can distingush them is this.
1.
Red CWM ALL:when booting into recovery you directly enter red clockwork screen.
Red CWM froyo:when booting into recovery you first enter Stock blue recovery and need to apply sdcard:update.zip to enter into clockwork
2.
Since Red cwm froyo doesnt have voodoo lagfix support you will see various errors when entering,these wont be see in Red CWM ALL version

Q: I have flashed a custom rom via Odin, Do i really need Clockwork?
A: Yes and no. When using Odin you are limited to what the designer of the package gives you, this is great for people who are beginning trying out different roms but in advanced situations you will want to try different themes, kernels, patches or roms, and unless someone makes a odin package for every combination you need Clockwork. Also clockwork can be used independently of a computer. Simply download what you want from your browser directly to your SD card , boot into clockwork and flash. No computer needed.

Q: Will i lose anything by installing Clockwork?
A: No, when flashing the kernel required to make clockwork possible it flashes to its own partition on the phone and does not touch anything that has to do with data or the OS.

Q: Do i need to root to install clockwork?
A: No, clockwork can be installed via odin and root is not required. If flashing it from Rom Manager yes root is required but as discussed earlier at the moment flashing from rom manager is not effective or recommended.

Q: Does having clockwork void my warranty?
A: As always , Yes and no. if you are caught then most likely but if you are at the point of flashing clockwork then you are savvy enough to use Odin to flash a stock rom and problem is solved.



newest CWM is Purple...ssssss---------straight "edify"
 
Sorry to rain on your parade but for the fascinate it's actually red even though it should be orange.

There are several right now actually. CWM 3.x from times_infinity comes in red, blue, and purple. CWM 3.x that you get from nemesis2all's OTB kernel is red. And CWM 3.x that you get from imnuts' PBJ kernel is yellow.
 
There are several right now actually. CWM 3.x from times_infinity comes in red, blue, and purple. CWM 3.x that you get from nemesis2all's OTB kernel is red. And CWM 3.x that you get from imnuts' PBJ kernel is yellow.

now its just getting redic
 
Forget aesthetics, all I care about is functionality. Times_infinity's versions seem to have a problem doing nandroid backups, which I don't really do anymore so not a big deal. The version that comes with nemesis2all's OTB kernel cannot wipe dalvik as of last night. And imnuts' version seems to have a few problems, but he is on top of them and they will be fixed. Everyone seems to be concentrating their efforts on CM7 right now, and they should as this would be an amazing feat. The problems listed are minor, and I have no doubt these great devs will be able to repair them.
 
Forget aesthetics, all I care about is functionality. Times_infinity's versions seem to have a problem doing nandroid backups, which I don't really do anymore so not a big deal. The version that comes with nemesis2all's OTB kernel cannot wipe dalvik as of last night. And imnuts' version seems to have a few problems, but he is on top of them and they will be fixed. Everyone seems to be concentrating their efforts on CM7 right now, and they should as this would be an amazing feat. The problems listed are minor, and I have no doubt these great devs will be able to repair them.

I totally agree. I need function over a pretty face... I was not aware of the issues with nemesis2all's recovery.. I can write a script to clear a dalvik cache but not do a backup.. I did not see this in the OTB thread.. This turn up in IRC?

I just did a Dalvik wipe on my phone using CWM 3.2.xx OTBv2 - worked fine..

I was watching times_infinity and saw the backup stuff.. I agree ~~ not a nandroid fan anymore..
 
Last edited:
3. boot into cwr (3.0 preferred..should work with 2.5 but edify scripts can be nasty with it sometimes..testers say it worked though)

Where does one get the latest and most complete version of CWR 3. I can't seem to find it anywhere. I am currently using the version that came with ComRom 1.3.

Thanks in advance!
 

I have / had issues with the above CWM. Coulda just been me, but when wiping data, it never completes, I had to reboot by hand, and it would boot back to recovery. I went back to the cwm-recovery-ALL-3-30-FIX and I'm havingn zero issues with flashing the ROM and / or anything else.

Also After flashing to the new CWM My phone no longer comes down to 100mhz, there's an option to enable 100 and disable, neither worked for me. After flashing back to cwm-recovery-ALL-3-30-FIX, my phoen is operating normally again.
 
If an Update.zip file is UNsigned will it still install? I ask because I used TiBu to make an Update.zip file that I can put on my sdcard and not have to download it from the Market when restoring my phone after a ROM change. I don't think the option for signing the file was selected when I made the file. When I was in CWM and used "install zip from sdcard" the file appeared to install correctly but TiBu did not appear in my apps drawer as I expected it to. So I'm wondering if a) It needed to be signed and faked me out with the install; or b) I was supposed to use the CWM option for installing "update.zip." I don't think it's option b because it shouldn't matter which way I access the file, right?

Alternatively, I sent an email to TiBu support and in reply was asked if I'd looked in the Settings/Applications/Manage Applications list, which I had not. Might it have appeared there but not in the apps drawer?

I'm not sure if this is a CWM question or just a TiBu one but I was researching the difference between zip installation methods and came across this thread so I thought I'd ask.
 
Did you back up the app or the pro key?
If it wasn't signed it would spit out an error.

I just opened TiBu to see what the choices were to answer your question and see that the fine print says it is an unsigned file, which answers that question. It also says it is suitable for installing TiBu in recovery mode. I think the last time I did it (and therefore the one I used) was set to install TiBu as a System application. But, yes, it was supposed to be the app. The support email I received in response to my question stated that it should have done what I expected it to do. I guess it boils down to whether or not it is designed to show up in the app drawer or just in the Settings/Apps/Manage Apps location.

I just need to know where to find it when I want to begin the restore process. I have to set up the Google account to get to the Market and rather than disabling all the auto download stuff from Google, it would be nice to have TiBu already on my card to run it that way.
 
Hey this is an amazing write up! However. I flashed with ODIN it said Passed. I turned the phone off and held down the Volume up and Down buttons along with the Power button and after the second flash of the Samsung Logo I let go. I just boots into stock recovery. I do have root. :) Any help would be amazing!

EDIT: Works now, had to flash it in Odin again.
 
Last edited:
Ok so nevermind, I am still having issues with it. Is this normal?

It worked once at work, I get home to try installing a ROM and I cannot get into CWM.

I hold the buttons til right after the second SAMSUNG goes away. Am I doing something wrong?
 

Trending Posts

Forum statistics

Threads
956,457
Messages
6,968,330
Members
3,163,550
Latest member
jimmyrichard