[Samsung Epic 4G Touch] sfhub:
I've gone through and looked at the following publicly available checkins for recovery:

1) Cyanogen

2) CWM - chris41g

3) Rogue CWM - Steady

The latest from Cyanogen has the new ICS 2-argument interface (ie the one that can trigger the EMMC lockup). Technically the 2-argument change was on checked in on 19-Jan-2011 while the "wipe" change was on 26-Jan-2011, but they are close enough in time that it is probably ok to use the interface change as a proxy for determining if a version of CWM is linking with the "wipe" code.

https://github.com/CyanogenMod/android_bootable_recovery/blob/ics/roots.c#L384

if (strcmp(v->fs_type, "ext4") == 0) {
int result = [B][U]make_ext4fs(v->device, v->length);[/U][/B]
if (result != 0) {
LOGE("format_volume: make_extf4fs failed on %s\n", v->device);
return -1;
}
return 0;
}

This is what chris41g has checked in for CWM:

https://github.com/chris41g/android_bootable_recovery/blob/gingerbread/roots.c#L349

if (strcmp(v->fs_type, "ext4") == 0) {
reset_ext4fs_info();
int result = [B][U]make_ext4fs(v->device, NULL, NULL, 0, 0, 0);[/U][/B]
if (result != 0) {
LOGE("format_volume: make_extf4fs failed on %s\n", v->device);
return -1;
}
return 0;
}

Notice how this is the "old" multiple-argument GB interface to make_ext4fs()/libext4_utils.a *IF* the version of CWM source code chris checked into github is the same that is currently being used (and I believe it is from conversations with him) then his CWM should be safe when repacked with ICS-kernel for

1) wipe data/factory reset

2) restoring nandroid backups

It CANNOT BE DETERMINED whether CWM from chris41g would be safe for flashing ICS ROMs because that depends on the update-binary executable and updater-script that is bundled with the ROM install.

This is what Steady has checked in for CWM:

https://github.com/TDR/android_bootable_recovery/blob/stingray/roots.c#L410

if (strcmp(v->fs_type, "ext4") == 0) {
reset_ext4fs_info();
int result = [B][U]make_ext4fs(v->device, NULL, NULL, 0, 0, 0);[/U][/B]
if (result != 0) {
LOGE("format_volume: make_extf4fs failed on %s\n", v->device);
return -1;
}
return 0;
}

Notice how this is the "old" multiple-argument GB interface to make_ext4fs()/libext4_utils.a *IF* the version of CWM source code Steady checked into github is the same that is currently being used then his CWM should be safe when repacked with ICS-kernel for

1) wipe data/factory reset

2) restoring nandroid backups

However, I stress I have

NOT

spoken to Steady about whether he has modified/updated the source code for Rogue CWM when building the ICS releases. If he had updated to latest CWM from Cyanogen's github, then he would have picked up the latest CWM changes and would be susceptible to the EMMC lockup/superbrick issue.

It is CANNOT BE DETERMINED whether Rogue CWM would be safe for flashing ICS ROMs because that depends on the update-binary executable and updater-script that is bundled with the ROM install.

====

I was not able to locate source code for CWM Touch. I suspect it is based off the latest from Cyanogen. This could explain why LOTS of people were bricking with it when doing the temp/fake flash of CWM Touch with the ICS kernel.

If someone can point me to the source for CWM Touch I'd like to look at it and verify these theories.