Originally Posted by sfhub
There may be some versions of the EMMC more susceptible to this problem and the bug could lie in sections of the EMMC firmware designed to make sure flashes don't keep flashing the same blocks to reduce "wear".
I am familiar with wear leveling as well as the basics on the interface controller. I would actually be curious to see if there is anything in the area of storage the controller has access to internally that is not presented outside of vendor specific queries and commands. I assume they are able to see and write that area with jtag so there is probably nothing there. But would be interesting to see a dump before and after brick on the same phone. That is unless the combined package prevents direct access to the flash itself, unlike what I am used to.
I haven't bothered keeping up because I know you guys are on it and there is nothing I can do. I don't even have the time in the day. Keep it up guys, much better than anything I can do.
Desktop i5 2500K @ 4.5Ghz | ASUS P8Z68-V PRO | 16GB Corsair Vengeance 1600 | Seasonic X750
MSI GTX570 TF III @ 950/1900/2300 | 2TB 5900 + 2X320GB 7200 RAID0 | Zalman CNPS9900 MAX
Laptop ASUS G50VT | Core2Duo T9600 @ 3.3Ghz | 9800M GS/GTS @ 650/1625/900
Phone Galaxy SII Epic 4G Touch | CyanogenMod 10 | FI25 Modem