[Samsung Epic 4G Touch] sfhub:
If you plan on running through this test plan, you should be able to deal with a superbrick (having TEP or within return period would be best). Through code analysis, it is believed these are all safe operations, but until we test, we don't know for sure. I would like to start with one volunteer, then expand from there if successful.

Downloads

a) SPH-D710.ODIN_FF02_KERNEL_CWM_AGAT.exe

b) update-BRICKFIXv1-cm-9-20120606-SNAPSHOT-epic4gtouch-alpha5-signed.zip

c) update-kernel-CM9a5.zip

d) SPH-D710.FF02_CL663858_ROOTED-oc-sfx.exe

e) AOKP_BRICKFIXv1_Build-37_epic4gtouch.zip

f) update-kernel-AOKP-37.zip

g) Format_Cache_Data-E4GT.zip

Pre-requisite

First, verify your EMMC is susceptible to the superbrick using this app from Chainfire

http://xdaforums.com/showthread.php?t=1693704

Test Plan

0a) ODIN Flash FF02 Stock (SPH-D710.FF02_CL663858_ROOTED-oc-sfx.exe) (Power+VolDown)

0b) will automatically boot to stock FF02

1a) ODIN AGAT FF02 CWM Repack (Power+VolDwn)

1b) boot to recovery (Power+VolUp)

1c) Flash Format_Cache_Data-E4GT.zip

1d) Flash CM9a5 BRICKFIXv1

1e) reboot to CM9

2a) ODIN AGAT FF02 CWM Repack (Power+VolDwn)

2b) boot to recovery (Power+VolUp)

2c) Flash CM9a5 BRICKFIXv1

2d) reboot to CM9

3a) ODIN AGAT FF02 CWM Repack (Power+VolDwn)

3b) reboot to recovery (Power+VolUp)

3c) perform wipe data/factory reset

3d) Flash CM9a5 *kernel* update.zip

3e) reboot to CM9

4a) ODIN AGAT FF02 CWM Repack (Power+VolDwn)

4b) boot to recovery (Power+VolUp)

4c) Flash CM9a5 BRICKFIXv1

4d) reboot to CM9

4e) make change to home workspace like adding/removing an app

5a) ODIN AGAT FF02 CWM Repack (Power+VolDwn)

5b) reboot to recovery (Power+VolUp)

5c) Flash CM9a5 *kernel* update.zip

5d) perform nandroid backup

5e) perform wipe data/factory reset

5f) reboot to CM9

5g) confirm your change from 4e is not present

6a) ODIN AGAT FF02 CWM Repack (Power+VolDwn)

6b) reboot to recovery (Power+VolUp)

6c) perform nandroid restore

6d) reboot to CM9

6e) confirm your change from 4e is present

7) Repeat Steps 0-6 using AOKP-37 BRICKFIXv1 / kernel instead of CM9a5 BRICKFIXv1 / kernel

DISCLAIMER: you should understand that the core problem is a bug in the EMMC firmware. Unless that is "fixed", which is unlikely, you will

ALWAYS

be exposed to the superbrick to some extent. What we are doing is eliminating common paths you may reach the problem. If the workaround is placed in the kernel mmc driver, then all ROMs/Recoveries that use that kernel will have the call to the buggy EMMC firmware code disabled, however, you may unwittingly install a different kernel/recovery which doesn't have the mmc driver patch and expose yourself to the superbrick again. If you workaround the problem in the userspace utilities, you could always find a ROM which hasn't eliminated the format() call from the edify install script and is using an unsafe update-binary. Both workarounds are being actively pursued to reduce (but not eliminate) your chances of hitting the core EMMC firmware bug.

Results so far:

Esoteric68 - no issues - 6 flashes CM9 BRICKFIXv1, 3 flashes AOKP BRICKFIXv1, 3 wipe data/factory resets, 3 nandroid restores, 1 stock FF02 flash

http://xdaforums.com/showthread.php?p=27127645#post27127645

http://xdaforums.com/showthread.php?p=27127645#post27127645

krazy_smokezalot - no issues - Ran Test Plan twice - 6 flashes CM9 BRICKFIXv1, 6 flashes AOKP BRICKFIXv1, 4 wipe data/factory resets, 4 nandroid restores, 4 stock FF02 flash

http://xdaforums.com/showthread.php?p=27137440#post27137440

http://xdaforums.com/showthread.php?p=27161837#post27161837

dexter35803 - no issues - 4 flashes CM9 BRICKFIXv1, 3 flashes AOKP BRICKFIXv1, 6 wipe data/factory resets, 3 nandroid restores, 2 stock FF02 flash

http://xdaforums.com/showthread.php?p=27185711#post27185711