Determine Your Device’s Hard Brick Risk with Got Brickbug
Posted June 6, 2012 at 04:30 pm by Will Verduzco
By now, we’re all familiar with the hard brick bug that’s plagued various Samsung when updating to leaked builds of ICS. The bug has shown up on various Samsung Exynos 4210-based devices including the Galaxy Note GT-N7000, Epic 4G Touch, AT&T Galaxy S II, and the Korean SHW-M250S/K/L.
However, as we quickly found out, not all eMMC revisions were equally afflicted. Instead, the 0x19 revision was highlighted as known bad, whereas the 0x25 is thought to be safe. Revisions between 0x19 and 0x25 are thought to be possibly bad, whereas those newer than 0x25 are probably safe. Adding insult to injury, those keen on hex will be quick to notice that 0x19 converted to decimal is 25!
Naturally, someone was bound to create a simpler way of determining the status of your device, and that someone is XDA Elite Recognized Developer Chainfire. With his new app Got Brickbug, users can easily check their device to see their risk status for the hard brick bug. As explained by Chainfire himself:
Attached is a simple APK that reads out your chip’s type and CID, and lets you know if we know that chip is dangerous or safe.
Just uninstall again after using.
Obviously, this comes “as-is”, we’re not responsible what you do with your device, etc. No rights can be derived from the output of the program!
Internal data used:
MAG4FA, VYL00M, or KYL00M fwrev 0x19 –> known bad
MAG4FA, VYL00M, or KYL00M fwrev >= 0x25 –> probably safe
MAG4FA, VYL00M, or KYL00M fwrev != 0x19 && < 0x25 –> probably bad
Everything else: unknown chip
As this is relevant information for any flashaholic, we recommend you head over to the application thread to test your device.[Image stolen from egzthunder1’s fantastic article on the matter.]
Want something on the XDA Portal? Send us a tip!