Welcome to the GSM-Forum forums. |
You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features.
Only registered members may post questions, contact other members or search our database of over 8 million posts.
Registration is fast, simple and absolutely free so please - Click to REGISTER!
If you have any problems with the registration process or your account login, please contact contact us .
| ||LinkBack||Thread Tools|
Join Date: Oct 2005
Thanks Meter: 2
eMMC firmware bug in multiple Samsung Exynos devices
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.
Join Date: May 2012
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
|thread||Thread Starter||Forum||Replies||Last Post|
|How to upload a new firmware...||Brand||Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )||29||06-13-2014 15:30|
|How to add a language in 51xx/61xx||tati||Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )||8||05-21-2013 19:20|
|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|
|"Deskey Device driver not found" ?? Please help||DivAdonis||Nokia Legacy Phones ( DCT-1 ,2 ,3 ,L )||0||06-28-1999 14:56|