[Fascinate Android Development] GizmoDroid:
EDIT [4-26-11]: Sorry guys for the delay on updating this thread. I currently have no free time, so defer to other threads for up-to-date information. I will probably be back in a couple weeks.

EDIT [4-8-11]: jt1134 has put a lot of work into fixing the mounting/filesystem/permissions issues over the last couple days. I will update this post as soon as he makes his latest compile available.

Original Post:

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. Since then, jt has worked on making sure the mounting/permissions work right. I think we finally have a winner.

[SIZE=+1]Changelog[/SIZE]

Bug: The old 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 "Force Close" problems and boot loops came from when flashing roms and also when restoring Nandroids backups. Fix: corrected the init script typo from "ro.secure=01" to "ro.secure=0"

Bug: "Voodoo lagfix is actually: disabled" even when it is enabled. Fix: working (probably as a result of the root fix)

Bug: "Fix Permissions" script is broken. Fix: updated to new version and then modified to auto-mount the correct partitions and use correct files

Bug: Mounting menu typo "umount /dbdata". Fix: corrected to "unmount /dbdata"

Bug: Battery Stats wiping returns immediately to menu. Fix: added a print out to confirm to the user that battery stats wipe was ran

Bug: "Format Boot" option does not work. Fix: not compatible with the Fascinate, removed from menu

Bug: "Enable/Disable Puzzle LockScreen" does not work. Fix: no longer compatible, removed from menu

Bug: Miscellaneous quirks and issues. Fix: mounting and permissions code improved throughout, and making it more robust in handling ext4 and RFS configurations.

[SIZE=+1]Frequently Asked Questions[/SIZE]

Q: After I enter CWM, it says I am at version 2.5.1.x. Does that mean I'm on the correct version?

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. An easy way to check is to go to "Advanced" menu. If you don't see "Enable Puzzle LockScreen", then you are on the newest version (this menu option was removed because it has not been functional for a long time).
​

Q: Does battery stats wipe work yet?

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 before returning to the menu that tells the user that the battery stats had been wiped.
​

Q: Does Fix Permissions work yet?

If you select "Fix Permissions" you should see it doing a lot of work (should take 1-2 minutes). If it returns to the menu immediately, it means one of two things:

You just wiped /data or /dbdata, 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!

Maybe, but I'm guessing you have an old copy, or you have flashed a file that has overwritten your recovery partition to an old version. 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.
​

[SIZE=+1]Most Thorough Method of Fixing Every Problem You Might Have[/SIZE]

If you have an issue with applications force closing or a continual boot loop, a lot of times you can fix this issue by running the Fix Permissions option.

However, if you would like to see your phone be able to have fully functioning Nandroids, and less problems with permission related errors when flashing different ROM's, I encourage you to do the following (this will make your phone as clean and healthy as possible):

Download to PC

CWM-Recovery Odin Package

MD5 Checksum:

CI500_VZW_EB01_FROYO_REL.tar.md5

MD5 Checksum: d04733ce540ab1af291cfa44d42c768e

atlas_v2.2.pit

MD5 Checksum: a0eaf496375cf72b90f7ceef4f0a4538

Place on /sdcard

ROM of your choice

MD5 Checksum:

Now that's done, on to the fun part....

ODIN the full stock EB01 package in PDA, the atlas_v2.2.pit in PIT, and "Re-Partition" checked

Let your phone fully boot into the OS and verify everything is working correctly

Remove your battery

ODIN the CWM Recovery package

Unplug USB Cable, THEN reinsert your battery

Hold both the volume keys and the power button down until a second after you see the Samsung boot logo, then let go

It should now boot into red CWM recovery

Wipe Cache/Dalvik Cache only. Flash the ROM of your choice

Reboot. Since you have installed the Voodoo ROM, then you should hear a Sexy Robot lady telling you that she is converting your partitions. This process will take 10 minutes or so. If you pull the battery, you will have to start all over again.

Let your phone fully boot into the OS and verify everything is working correctly

If you need to install a theme, reboot; enter CWM; wipe Cache/Dalvik Cache only; enter CWM; flash theme

If you need to install a kernel, reboot; enter CWM; flash kernel

Make a fresh nandroid backup. If you try to restore a Nandroid made with the old CWM, you will probably have problems.

I haven't gone into the specifics of how to do all the above, because there are several tutorials with pictures and well-written guides already in existence.​

[SIZE=+1]A couple of things about ClockworkMod Recovery that a lot of people don't know[/SIZE]

The CWM package in this post is the ONLY CWM file you ever need, for any Samsung Fascinate ROM. Even Eclair ROMs. Even Non-Voodoo Roms. Doesn't matter. Delete all your old copies.

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 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).

[SIZE=+1]A few other questions that might get asked[/SIZE]

Q: What is that MD5 gibberish under the download links?

A: MD5 (and other checksums/hashes) can be used to verify the integrity of a downloaded file. Basically, you download the file, then use an MD5 tool to calculate the checksum. You then compare the file's checksum to the checksum I have posted under the link. 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. Also, there are many free MD5 calculators (I use HashCheck).
​

Q: Is this CWM 3? Why isn't my menu orange?

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 this overwrite my kernel/custom kernel files on my system partition/knock up my daughter?

The CWM ZIP package has been cleaned of the system files, and the ODIN package has been correctly configured to flash to the recovery partition only. 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?

Because in the main threads, I answer the same questions every 20 posts. This is more visible. If this information is merged into Adrynalyne's SuperClean thread and JT1134's CWM thread, I will ask for a mod to close this thread.​