---------- Post added at 04:08 PM ---------- Previous post was at 04:07 PM ----------
---------- Post added at 04:10 PM ---------- Previous post was at 04:08 PM ----------
As I mention above, the revision 0x19 firmware had a bug that after an emmc erase command, it could leave the internal data structures of the emmc chip in a bad state that cause the chip to lock up when a particular sector was accessed. The only fix was to wipe the chip, and update the firmware. I have code to do that, but I don't know if I can share it. I'll ask.
A method called JTAG bit blasting, which is supposed to bypass all but hardware issues, is known not to work.
Flashing a rom probably won't fix any sectors. I'm sure people have tried it and it it worked XDA would be awash with posts jumping for joy over the relatively simple fix. My understanding is hazy, but the eMMC chip seems to get corrupted internally because its wear leveling code is bugged. Wear leveling is low level stuff independent of write methods used during a flash. It can be recovered, but the code to do so is only known to developers who aren't permitted to share it.
Incidently, chainfire had already provided a link with tons of background on this issue including a link to this very post that says:
CM9 ROMs and kernels are SAFE. You do not have to stop flashing the nightlies. The Samsung official and leaked ROMs and kernels are the faulty ones. Franco and Speedmod kernels are safe as well.
The emmc bug is on the official and leaked Samsung ROMs and kernels. On the Note, CM9 is safe. I'm not sure which ROMs are safe for SII but I'm sure CM9 is one of them. Avoid wiping data on the Samsung ROMs, or in my opinion, avoid Samsung ROMs entirely.
|Thread Tools||Search this Thread|