eMMC firmware bug in multiple Samsung Exynos devices - GSM-Forum

Entropy512 · 05-21-2012, 23:39

I've seen a few posts regarding this issue scattered around here, but I figured I'd post a bit of information gained over the past few weeks by various people in the XDA-Developers community.

There's a nasty firmware bug in the eMMC chip of a number of Samsung devices. So far, all of them are Exynos-based but there may be other devices out there.

The affected chips are:
VYL00M, KYL00M, MAG4FA with fwrev 0x19. fwrev 0x25 (as found in the Galaxy Nexus, AT&T Galaxy Note (SGH-I717), and some other devices is not affected.

A high level overview can be found at:
Hard Brick Bug on Galaxy S II and Note Leaked ICS Kernels | xda-developers

As stated there, the following kernels can trigger the bug as of May 22, 2012 (the bug itself is in the eMMC flash chip):
All Sprint Epic 4G Touch (SPH-D710) ICS leaks
All Galaxy Note (GT-N7000) ICS leaks, along with the official XXLPY and ZSLPF releases.
The AT&T Galaxy S II (SGH-I777) UCLD3 leak, and probably all other ICS leaks for this device
All SHW-M250S/K/L ICS official releases, along with their source code releases. This is the source of the devices damaged by "SiyahKernel 3.1rc6" that some have reported, as it was based on the SHW-M250L Update4 sources.

More detailed information is at:
Discussion thread for /data EMMC corruption bug - Page 16 - xda-developers

Devices damaged by these kernels are usually damaged by a wipe/format operation, or another operation that includes a wipe/format as part of it (such as a Nandroid restore from Clockworkmod recovery). Attempting to restore these devices with a RIFFBOX fails due to the eMMC chip being out in la-la-land.

Hopefully Mr. Sumrall will be able to provide the community, including the RIFFBOX team, with information on how to recover these devices. Perhaps even without the information he is trying to get permission to provide, with the information already provided the RIFFBOX team may be able to identify a solution for these devices to at least get the eMMC chip back into a usable state, even if it is not possible to update its firmware to a revision not affected by the bug.

ken6430841 · 05-24-2012, 09:04

Several of these problems, but unable JTAG solution

eralp · 05-24-2012, 22:52

Hi, i have GT-N7000 (hardbricked - affected by kernel eMMC bug) and riff jtag box. When i first tried to recover over jtag, it can't read/write/resurrect eMMC chip and gets error codes 0x23 0x3E. I tried many many times, but suddenly write/read some blocks of eMMC chip with direct jtag access plugin. Now i can read/write/erase successfuly some blocks but still can't read/write other address. I don't now how to jtag communicate and works with mcu and emmc, but i hope rocker team can improve this plugin and recover eMMC chip may be.

I'm sharing part of which address can/can't read/writing now..
0000 0000 <--> 0140 0000
0140 0000 <--> 0180 0000
0180 0000 <--> 01C0 0000
01C0 0000 <--> 1000 0000
1000 0000 <--> 1100 0000
1100 0000 <--> 1140 0000
...

sp-lox · 07-19-2012, 15:10

There are no news? It did not turn out to make the device?

05-21-2012, 23:39	#1 (permalink)
Entropy512 Junior Member Join Date: Oct 2005 Posts: 2 Member: 193027 Status: Offline Thanks Meter: 2	eMMC firmware bug in multiple Samsung Exynos devices I've seen a few posts regarding this issue scattered around here, but I figured I'd post a bit of information gained over the past few weeks by various people in the XDA-Developers community. There's a nasty firmware bug in the eMMC chip of a number of Samsung devices. So far, all of them are Exynos-based but there may be other devices out there. The affected chips are: VYL00M, KYL00M, MAG4FA with fwrev 0x19. fwrev 0x25 (as found in the Galaxy Nexus, AT&T Galaxy Note (SGH-I717), and some other devices is not affected. A high level overview can be found at: Hard Brick Bug on Galaxy S II and Note Leaked ICS Kernels \| xda-developers As stated there, the following kernels can trigger the bug as of May 22, 2012 (the bug itself is in the eMMC flash chip): All Sprint Epic 4G Touch (SPH-D710) ICS leaks All Galaxy Note (GT-N7000) ICS leaks, along with the official XXLPY and ZSLPF releases. The AT&T Galaxy S II (SGH-I777) UCLD3 leak, and probably all other ICS leaks for this device All SHW-M250S/K/L ICS official releases, along with their source code releases. This is the source of the devices damaged by "SiyahKernel 3.1rc6" that some have reported, as it was based on the SHW-M250L Update4 sources. More detailed information is at: Discussion thread for /data EMMC corruption bug - Page 16 - xda-developers Devices damaged by these kernels are usually damaged by a wipe/format operation, or another operation that includes a wipe/format as part of it (such as a Nandroid restore from Clockworkmod recovery). Attempting to restore these devices with a RIFFBOX fails due to the eMMC chip being out in la-la-land. Hopefully Mr. Sumrall will be able to provide the community, including the RIFFBOX team, with information on how to recover these devices. Perhaps even without the information he is trying to get permission to provide, with the information already provided the RIFFBOX team may be able to identify a solution for these devices to at least get the eMMC chip back into a usable state, even if it is not possible to update its firmware to a revision not affected by the bug.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
"Deskey Device driver not found" ?? Please help	DivAdonis	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	1	06-08-2017 13:21
How to add a language in 51xx/61xx	tati	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	8	05-21-2013 19:20
How to upload a new firmware...	Brand	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	8	06-08-2012 18:29
The multiple errors of Winlock ... ???	Genata	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	0	09-20-1999 19:12
Lock 2 in nokia 51xx/61xx	Pablo	Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )	1	07-31-1999 04:35

05-24-2012, 09:04	#2 (permalink)
ken6430841 Freak Poster Join Date: Mar 2008 Posts: 227 Member: 731116 Status: Offline Sonork: 100.1612132 Thanks Meter: 28	Several of these problems, but unable JTAG solution

05-24-2012, 22:52	#3 (permalink)
eralp Junior Member Join Date: May 2012 Location: Turkey Age: 40 Posts: 5 Member: 1763577 Status: Offline Thanks Meter: 0	Hi, i have GT-N7000 (hardbricked - affected by kernel eMMC bug) and riff jtag box. When i first tried to recover over jtag, it can't read/write/resurrect eMMC chip and gets error codes 0x23 0x3E. I tried many many times, but suddenly write/read some blocks of eMMC chip with direct jtag access plugin. Now i can read/write/erase successfuly some blocks but still can't read/write other address. I don't now how to jtag communicate and works with mcu and emmc, but i hope rocker team can improve this plugin and recover eMMC chip may be. I'm sharing part of which address can/can't read/writing now.. 0000 0000 <--> 0140 0000 0140 0000 <--> 0180 0000 0180 0000 <--> 01C0 0000 01C0 0000 <--> 1000 0000 1000 0000 <--> 1100 0000 1100 0000 <--> 1140 0000 ...

07-19-2012, 15:10	#4 (permalink)
sp-lox Freak Poster Join Date: Oct 2001 Location: Moscow, Russia Age: 47 Posts: 284 Member: 6653 Status: Offline Sonork: 100.1597550 Thanks Meter: 26	There are no news? It did not turn out to make the device?