Congrats to you on mod status, and thanks.
Congrats to you on mod status, and thanks.
So, like I said the other day, one of my FSM forums (Galaxy Tab 8.9) are having the superbrick EMMC bug and they have narrowed it down to the kernel (sort of).
From what I have read, it sounds eerily similar to ours and it seems to be happening to most Samsung devices. Anyways, while reading through their CM9 thread (troll hunting, muhahaha), I came across this linked post from the Epic 4g thread (Discussion thread for /data EMMC lockup/corruption bug). Beware there are 80 pages going on in that thread. But the post I mentioned can be found here. There is a direct link to CM9/AOKP ROMs and the bug. IIRC, almost all our EU locks have been in some derivative of CM9 or AOKP.?.?
I still think that we need a kernel cook to check out our CWR/Kernels and how they interact. Might be making progress on this after nearly a year's worth of lockups.
Edit::
I would also suggest reading from post 784 to the end. Seems Sammy knows something is wrong. Now just need to see if our chips are included in the "bum" batches. Here is the page, just scroll down a bit to #784.
I would also suggest reading from post 784 to the end. Seems Sammy knows something is wrong. Now just need to see if our chips are included in the "bum" batches. Here is the page, just scroll down a bit to #784.
Well I suppose that my other post is no help then, considering it's the external being identified.I was hit using a CM9 nightly (don't remember exactly which one, sorry) in early July, iirc
Chip: SU16G
Rev: 0x0
Hey guys, i've got EU screen a few minutes ago after flashing CM 9.1 stable (i got bootloop after flashed LANIGHT 4.2 then go to CM 9.1). Fortunately i've read this thread months ago, i pull out battery and go back to stock safely now. Thank you very much :good:
* After a few times playing with EU screen, i found out :
1. If you do a Format Factory in CWM, and one of the messages say "... using format unknow... " and the EU screen will show up if you flash any rom. DO NOT touch the button, pull out battery now.
2. I fixed it by flash a Glitch kernel, then go to CWM and mount USB -> Windows will show a "scan and fix..." USB storage, only tick the "Automatic fix file system errors." then wait a minute. when Windows finish the scan, unmount your phone, format Factory again (the message above should not be shown) and flash your ROM.
But are you with internal memory back, or using the swap extsd workaround?
After a few times playing with EU screen, i found out :
1. If you do a Format Factory in CWM, and one of the messages say "... using format unknow... " and the EU screen will show up if you flash any rom. DO NOT touch the button, pull out battery now.
2. I fixed it by flash a Glitch kernel, then go to CWM and mount USB -> Windows will show a "scan and fix..." USB storage, only tick the "Automatic fix file system errors." then wait a minute. when Windows finish the scan, unmount your phone, format Factory again (the message above should not be shown) and flash your ROM.
# internal sdcard that is no longer working
dev_mount emmc /mnt/emmc 1 /devices/platform/s3c-sdhci.0/mmc_host/mmc0
# external sdcard
dev_mount sdcard /mnt/sdcard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc2
As I mentioned in the previous post, firmware rev 0x19 has a bug where the emmc chip can lockup after an erase command is given. Not every time, but often enough. Usually, the device can reboot after this, but then lockup during the boot process. Very rarely, it can lockup even before fastboot is loaded. Your tester was unlucky. Since you can't even start fastboot, the device is probably bricked. :-( If he could run fastboot, then the device could probably be recovered with the firmware update code I have, assuming I can share it. I'll ask.
I think we should find a way to raise awareness for this issue. tons of people running around completely oblivious of how serious this is.
I used ics for a couple months before learning about this, quickly rolled back cause I'm not one to play with fire.
ROM threads have the responsibility dump in big bold letters as we all know, but they all know about this and it seems they chose to close their eyes to it hoping it goes away. A simple warning would hurt their downloads but would do wonders fire their character.