[How to] Install and Use Clockworkmod Recovery w/Screen captures
- Thread starter DroidXcon
- Start date
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
are these verified working?
and why is there a seperate cwm for custom kernels
the CWM zip is working perfectly fine for me...
however, not sure if this has always been like this, or if this is a bug/glitch. The soft "back" key acts the same as the power button in CWM. Meaning that it selects the highlighted operation. I have accidentally hit it 2 times now when "reboot system" has been highlighted. Wasn't a big deal for me, I was only flashing a patch, but I could see how it could cause problems for someone who accidentally hits the back key when doing other things.
Has this always been like this? Or is this a glitch that can be fixed? Thanks!
APeaceOfStrange
Well-known member
- Feb 13, 2011
- 125
- 11
- 0
I have a cwm related question/issue. I was on adrynalynes new ec10 kernel from the first post of his superclean thread. I created the disable_lagfix folder before flashing so I was never converted to voodoo. I then flashed times_infinty's comavolt nonvoodoo kernel in cwm. After flashing that, now when i go to recovery i go to blue instead of red. So to get my red cwm back do i just flash one of these new cwm files via odin?
FrankWhite77
Well-known member
- Jan 15, 2011
- 153
- 6
- 0
Having the same issue as the guy above me. I click update.zip, it starts to load and then I get E: error in /sdcard/update.zip (status 2) installation abored
the CWM zip is working perfectly fine for me...
however, not sure if this has always been like this, or if this is a bug/glitch. The soft "back" key acts the same as the power button in CWM. Meaning that it selects the highlighted operation. I have accidentally hit it 2 times now when "reboot system" has been highlighted. Wasn't a big deal for me, I was only flashing a patch, but I could see how it could cause problems for someone who accidentally hits the back key when doing other things.
Has this always been like this? Or is this a glitch that can be fixed? Thanks!
Check out post #2 for CWM controls
Having the same issue as the guy above me. I click update.zip, it starts to load and then I get E: error in /sdcard/update.zip (status 2) installation abored
i addressed this also in post #2
are these verified working?
and why is there a seperate cwm for custom kernels
They are working for me.. The zip flash that is non-custom kernel flashes over the custom kernel.
"Gizmodroid:
Yes, this is true (however as of right now, nearly all the custom kernels are using JT's as a base, so those files are the same. This is subject to change in the future, I know).
The bad thing is that ROM's like Superclean have kernel/recovery/OS all bundled together, so if they flash CWM first, then flash the rom, CWM will be overwritten.
Here is a version of the flash with the /system files stripped out. I would recommend using this, or the odin file, if you are using custom kernels.
cwm-recovery-ALL.zip - 3/31/11 - Newest - Custom kernel friendly
The odin file in the OP is fine the way it is.
If you want to modify SuperClean to prevent it from flashing the old CWM (say, if you flash often, like me ), then you can do so by opening the SF_SFC_v2.9.2 zip file, and going to META-INF\com\google\android\update-script
Inside, just delete this line "run_program /tmp/kernel_update/redbend_ua restore /tmp/kernel_update/zImage2 /dev/block/bml8" . Save the file and drag it back into the zip folder, where you found it."
FrankWhite77
Well-known member
- Jan 15, 2011
- 153
- 6
- 0
I download cwm all but it still is giving me an error, should I rename it update.zip?
No do not rename it.
I would suggest you download the cwm-recovery-ALL.tar and flash it in Odin.
FrankWhite77
Well-known member
- Jan 15, 2011
- 153
- 6
- 0
I only have macs in my house, I've been using "pushtosd" to get files onto my card.
When you boot into recovery you boot to blue text or red?
FrankWhite77
Well-known member
- Jan 15, 2011
- 153
- 6
- 0
I boot to blue, hit update.zip and get that error I mentioned a couple posts back. I put the CWMall on the sd and hit update.zip in blue again and get an error also. Everything was fine until I flashed a kernel.
I boot to blue, hit update.zip and get that error I mentioned a couple posts back. I put the CWMall on the sd and hit update.zip in blue again and get an error also. Everything was fine until I flashed a kernel.
What ROM are you using?
FrankWhite77
Well-known member
- Jan 15, 2011
- 153
- 6
- 0
Superclean 9.2 and dont even remember what kernel I flashed, I think it may be the comavolt one, pretty sure its timeinfinity's though. I flashed it when it first came out.
Superclean 9.2 and dont even remember what kernel I flashed, I think it may be the comavolt one, pretty sure its timeinfinity's though. I flashed it when it first came out.
I would almost guarantee that is the kernel you flashed... Running it now.. When you flash it it removes your resident CWM..
To get your CWM back you may have to flash your base ROM again sc 2.9.2 - you do not have to clear your data/wipe your phone..
Clear your dalvik cache and your cache partition.. Super Clean 2.9.2 has it CWM built in. Once you have that back you will retain all your user info and your apps.
Your CWM will be back..
If you choose to use that kernel again you will need to flash this CWM Version in the same flash session for both the kernel (first) and the CWM to stick.
I just realized after I typed this you have lost your flashing capability.. Sorry. I am so far out of my league with Mac to Fascinate connections.
I am going to have to turn this over to someone with more experience.
APeaceOfStrange
Well-known member
- Feb 13, 2011
- 125
- 11
- 0
I would almost guarantee that is the kernel you flashed... Running it now.. When you flash it it removes your resident CWM..
To get your CWM back you may have to flash your base ROM again sc 2.9.2 - you do not have to clear your data/wipe your phone..
Clear your dalvik cache and your cache partition.. Super Clean 2.9.2 has it CWM built in. Once you have that back you will retain all your user info and your apps.
Your CWM will be back..
If you choose to use that kernel again you will need to flash this CWM Version in the same flash session for both the kernel (first) and the CWM to stick.
I just realized after I typed this you have lost your flashing capability.. Sorry. I am so far out of my league with Mac to Fascinate connections.
I am going to have to turn this over to someone with more experience.
I am in the same boat. Im a mac user also but my phone is running fine now, so i am not in a rush to get to a pc, but can use a friends if needed.
I could reflash through odin correct? and would I want to reflash SC 2.9.2 or would I want to flash one of the new cwm all recoveries in odin?
I boot to blue, hit update.zip and get that error I mentioned a couple posts back. I put the CWMall on the sd and hit update.zip in blue again and get an error also. Everything was fine until I flashed a kernel.
Do NOt hit the update zip file. all thats needed is to select chose zip from sd card and then select what you want to run and it will roll right on down the road.. That is if you have the CWM All installed.. and it should be the red CWM..No Blue No More.... red red red..
FrankWhite77
Well-known member
- Jan 15, 2011
- 153
- 6
- 0
I am in the same boat. Im a mac user also but my phone is running fine now, so i am not in a rush to get to a pc, but can use a friends if needed.
I could reflash through odin correct? and would I want to reflash SC 2.9.2 or would I want to flash one of the new cwm all recoveries in odin?
You are correct. That should resolve your issues. It did for me.
[FIX][4-1-11]Latest ClockworkMod and SuperClean ROM's - Erasing the CWM Confusion
Direct from Gizmodriod - XDA:
[FIX][4-1-11]Latest ClockworkMod and SuperClean ROM's - Erasing the CWM Confusion
Because of the confusion over the different versions of ClockworkMod Recovery, I will try to address the major questions in this thread.
This all started out when some people started asking questions about why themed nandroid backups always had problems when they were restored (very informative thread detailing the process). After figuring out that something was broken in CWM, I decided to try to find it. Thankfully, it was an easy fix that me and jt discovered whilst chatting in the IRC. While I was poking around, I fixed a few other small problems too.
Issues fixed
CWM did not have root shell access because of a typo in the old initramfs, so this caused lots of issues when ROMs and themes did not set the correct permissions in their scripts. This is where most of the Forced Close problems and boot loops came from when flashing roms without wiping data first, and also when restoring Nandroids backups
This also caused the "Voodoo lagfix is actually: disabled" even when it was enabled bug to be fixed
"Fix Permissions" script updated to a new version, and then modified to auto-mount the correct partitions and use correct file
Mounting menu typo fixed from "umount /dbdata" to "unmount /dbdata"
Added a Battery Stats wiping confirmation
A couple of things about ClockworkMod Recovery that a lot of people don't know (and may help erase the confusion for some)
When you flash a CWM Recovery, you are writing an entire kernel into the recovery partition of your phone (bml8). This does not affect your current kernel because it is stored on your kernel partition (bml7).
When you download a ROM, it is up to the ROM author to decide if they want to include a kernel and/or the CWM. For example, SuperClean bundles the ROM/Kernel/CWM all into one flash file. When you flash SuperClean, it will overwrite your kernel partition (bml7), your recovery partition (bml8), and your system partition (stl9).
Q: After I enter CWM, it says I am at version 2.5.1.x. Does that mean I'm on the correct version?
A: Unfortunately, the last several updates have been minor bugfixes, and the version number has stayed at 2.5.1.x. Hopefully this will be remedied soon.
Q: Does battery stats wipe work yet?
A: It was working on the on the old CWM, it just didn't give you a confirmation after wiping. If for some reason it wasn't working on the old CWM recovery (because of the ro.secure bug that was fixed), then I can definitely confirm that it is working now.
In the newest fix, I added a notification telling the user that the battery stats had been wiped before returning to the menu.
Q: Does Fix Permissions work yet?
A: If you select "Fix Permissions" you should see it doing a lot of work. If it returns to the menu immediately, it means one of two things:
You just wiped all the data, in which case, there is nothing to fix permissions for (completely normal)
Your /data or /dbdata partition is unable to mount, which means you may have had a bad voodoo conversion, or something that will probably require Odining back to stock to repair (not normal)
Q: I have the new CWM and the feature you said was fixed doesn't work!
A: Maybe, but I'm guessing you either grabbed one of the messed up versions that was posted on 3/29, or you have flashed a file that has overwritten your CWM partition. That's why I have included the SuperClean ROM's with the updated CWM, because most people don't know about this. If you prefer to not re-download the whole SuperClean file, you can take the zImage2 file from the CWM ZIP file and drag and drop it into the /kernel_update/ directory in your current SuperClean file.
ClockworkMod Recovery (3/30/11 Bugfix)
Odin Package
http://www.mediafire.com/file/06al8p...L-3-30-FIX.tar
MD5 Hash: 00e90e790a70e2d66b6cba6a152de504
Zip Package
http://www.mediafire.com/file/jldavb...L-3-30-FIX.zip
MD5 Hash: cc3e1885ac2131a39aa049cabdb9bf0b
SuperClean v2.9.2 with updated CWM (3/30/11 Bugfix)
Voodoo Kernel
http://www.mediafire.com/file/53akvc..._2v_CWMFIX.zip
MD5: 183e41d58e931b73f3429bfc101e4cbf
Non-Voodoo Kernel
http://www.mediafire.com/file/r8r9p5...2nv_CWMFIX.zip
MD5: 06bed73a07f4b4f3cc32d6a0d60a05ee
A few other questions that might get asked
Q: What is that MD5 gibberish?
A: MD5 (and other checksums/hashes) can be used to verify the integrity of a downloaded file. Basically, you download the file, and then use a program to calculate the checksum. You then compare the file to the checksum I have posted. If it matches, then you know that your download is not corrupt.
The whole process is much easier/quicker then it sounds, even if you've never done it before. There are many free MD5 calculators (I use HashCheck).
Q: Is this CWM 3? Why isn't my menu orange?
A: While this is the newest fully compatible CWM for the Fascinate, it has NOT had any of the CWM 3.0 code base ported into it. As of CWM 3.0, Koush ripped Amend scripting support for flashing. Most of the rest of the world has already moved to Edify scripts, but in Samsung Fascinate land, we still cling to Amend scripts in a lot of our ROM/patch flash files because of some of the issues that Edify has had with the way Samsung laid out the partitions and devices. This is why we have stuck with CWM 2.5 for so long, because so many ROMs, themes, and patches are still using Amend scripts.
Really though, its time to merge the CWM 3.0 base, port the voodoo options, cut ties with amend, and get the Samsung Fascinate's funky mounting/partitions/layout fully compatible with CWM. Someone just has to do the work, because Koush doesn't seem to be that interested in it any more.
There are a lot of improvements in the back end of CWM 3.0 that make it more reliable. Also, if someone were to be slightly ambitious, there are quite a lot of previously unseen (on the Fascinate) features that could be ported from other people's CWM mods. One easy one would be backup and restore of the kernel, which would allow for a more complete Nandroid. It's actually already half-way implemented in the code, so it wouldn't take much more work to get it done, even on the current version.
Then there is the EFS partition... which is a subject avoided by most people but is an important aspect of the phone that no one currently is backing up. There has been a lot of work done for the other SGS variants, but no one has really spoken up about it in the Fascinate world.
Q: Will overwrite my kernel/overwrite custom kernel files on my system partition/knock up my daughter?
A: The CWM packages have been cleaned up and all of the problems have been removed. SuperClean will behave like normal, which involves flashing your kernel/CWM/system/daughter.
Until Adrynalyne and jt1134 adopt these files (or make their own), then this applies to files that are downloaded from the links provided in THIS THREAD ONLY.
Q: Why did you start a new thread for this?
A: Because in the main threads, I answer the same questions every 20 posts. This is more visible. Hopefully, this information will be merged into Adrynalyne's SuperClean thread and JT1134's CWM thread, at which point I will ask for a mod to close this thread.
Direct from Gizmodriod - XDA:
[FIX][4-1-11]Latest ClockworkMod and SuperClean ROM's - Erasing the CWM Confusion
Because of the confusion over the different versions of ClockworkMod Recovery, I will try to address the major questions in this thread.
This all started out when some people started asking questions about why themed nandroid backups always had problems when they were restored (very informative thread detailing the process). After figuring out that something was broken in CWM, I decided to try to find it. Thankfully, it was an easy fix that me and jt discovered whilst chatting in the IRC. While I was poking around, I fixed a few other small problems too.
Issues fixed
CWM did not have root shell access because of a typo in the old initramfs, so this caused lots of issues when ROMs and themes did not set the correct permissions in their scripts. This is where most of the Forced Close problems and boot loops came from when flashing roms without wiping data first, and also when restoring Nandroids backups
This also caused the "Voodoo lagfix is actually: disabled" even when it was enabled bug to be fixed
"Fix Permissions" script updated to a new version, and then modified to auto-mount the correct partitions and use correct file
Mounting menu typo fixed from "umount /dbdata" to "unmount /dbdata"
Added a Battery Stats wiping confirmation
A couple of things about ClockworkMod Recovery that a lot of people don't know (and may help erase the confusion for some)
When you flash a CWM Recovery, you are writing an entire kernel into the recovery partition of your phone (bml8). This does not affect your current kernel because it is stored on your kernel partition (bml7).
When you download a ROM, it is up to the ROM author to decide if they want to include a kernel and/or the CWM. For example, SuperClean bundles the ROM/Kernel/CWM all into one flash file. When you flash SuperClean, it will overwrite your kernel partition (bml7), your recovery partition (bml8), and your system partition (stl9).
Q: After I enter CWM, it says I am at version 2.5.1.x. Does that mean I'm on the correct version?
A: Unfortunately, the last several updates have been minor bugfixes, and the version number has stayed at 2.5.1.x. Hopefully this will be remedied soon.
Q: Does battery stats wipe work yet?
A: It was working on the on the old CWM, it just didn't give you a confirmation after wiping. If for some reason it wasn't working on the old CWM recovery (because of the ro.secure bug that was fixed), then I can definitely confirm that it is working now.
In the newest fix, I added a notification telling the user that the battery stats had been wiped before returning to the menu.
Q: Does Fix Permissions work yet?
A: If you select "Fix Permissions" you should see it doing a lot of work. If it returns to the menu immediately, it means one of two things:
You just wiped all the data, in which case, there is nothing to fix permissions for (completely normal)
Your /data or /dbdata partition is unable to mount, which means you may have had a bad voodoo conversion, or something that will probably require Odining back to stock to repair (not normal)
Q: I have the new CWM and the feature you said was fixed doesn't work!
A: Maybe, but I'm guessing you either grabbed one of the messed up versions that was posted on 3/29, or you have flashed a file that has overwritten your CWM partition. That's why I have included the SuperClean ROM's with the updated CWM, because most people don't know about this. If you prefer to not re-download the whole SuperClean file, you can take the zImage2 file from the CWM ZIP file and drag and drop it into the /kernel_update/ directory in your current SuperClean file.
ClockworkMod Recovery (3/30/11 Bugfix)
Odin Package
http://www.mediafire.com/file/06al8p...L-3-30-FIX.tar
MD5 Hash: 00e90e790a70e2d66b6cba6a152de504
Zip Package
http://www.mediafire.com/file/jldavb...L-3-30-FIX.zip
MD5 Hash: cc3e1885ac2131a39aa049cabdb9bf0b
SuperClean v2.9.2 with updated CWM (3/30/11 Bugfix)
Voodoo Kernel
http://www.mediafire.com/file/53akvc..._2v_CWMFIX.zip
MD5: 183e41d58e931b73f3429bfc101e4cbf
Non-Voodoo Kernel
http://www.mediafire.com/file/r8r9p5...2nv_CWMFIX.zip
MD5: 06bed73a07f4b4f3cc32d6a0d60a05ee
A few other questions that might get asked
Q: What is that MD5 gibberish?
A: MD5 (and other checksums/hashes) can be used to verify the integrity of a downloaded file. Basically, you download the file, and then use a program to calculate the checksum. You then compare the file to the checksum I have posted. If it matches, then you know that your download is not corrupt.
The whole process is much easier/quicker then it sounds, even if you've never done it before. There are many free MD5 calculators (I use HashCheck).
Q: Is this CWM 3? Why isn't my menu orange?
A: While this is the newest fully compatible CWM for the Fascinate, it has NOT had any of the CWM 3.0 code base ported into it. As of CWM 3.0, Koush ripped Amend scripting support for flashing. Most of the rest of the world has already moved to Edify scripts, but in Samsung Fascinate land, we still cling to Amend scripts in a lot of our ROM/patch flash files because of some of the issues that Edify has had with the way Samsung laid out the partitions and devices. This is why we have stuck with CWM 2.5 for so long, because so many ROMs, themes, and patches are still using Amend scripts.
Really though, its time to merge the CWM 3.0 base, port the voodoo options, cut ties with amend, and get the Samsung Fascinate's funky mounting/partitions/layout fully compatible with CWM. Someone just has to do the work, because Koush doesn't seem to be that interested in it any more.
There are a lot of improvements in the back end of CWM 3.0 that make it more reliable. Also, if someone were to be slightly ambitious, there are quite a lot of previously unseen (on the Fascinate) features that could be ported from other people's CWM mods. One easy one would be backup and restore of the kernel, which would allow for a more complete Nandroid. It's actually already half-way implemented in the code, so it wouldn't take much more work to get it done, even on the current version.
Then there is the EFS partition... which is a subject avoided by most people but is an important aspect of the phone that no one currently is backing up. There has been a lot of work done for the other SGS variants, but no one has really spoken up about it in the Fascinate world.
Q: Will overwrite my kernel/overwrite custom kernel files on my system partition/knock up my daughter?
A: The CWM packages have been cleaned up and all of the problems have been removed. SuperClean will behave like normal, which involves flashing your kernel/CWM/system/daughter.
Until Adrynalyne and jt1134 adopt these files (or make their own), then this applies to files that are downloaded from the links provided in THIS THREAD ONLY.
Q: Why did you start a new thread for this?
A: Because in the main threads, I answer the same questions every 20 posts. This is more visible. Hopefully, this information will be merged into Adrynalyne's SuperClean thread and JT1134's CWM thread, at which point I will ask for a mod to close this thread.
Similar threads
- Replies
- 10
- Views
- 15K
- Replies
- 390
- Views
- 47K
- Replies
- 2
- Views
- 3K
- Replies
- 17
- Views
- 8K
Trending Posts
-
Can't Add Google App to Multistar Launcher Widget- Started by silverfang77
- Replies: 2
-
-
-
-
Members online
Total: 5,485 (members: 10, guests: 5,475)
Forum statistics
Space.com is part of Future plc, an international media group and leading digital publisher. Visit our corporate site.
© Future Publishing Limited Quay House, The Ambury, Bath BA1 1UA. All rights reserved. England and Wales company registration number 2008885.
Facebook
Twitter
Instagram