GSM-Forum  

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 .

Go Back   GSM-Forum > Product Support Sections > Hard/Software Products (official support) > Rocker Team products > RIFFBOX

Reply
 
LinkBack Thread Tools Display Modes
Old 05-21-2012, 23:39   #1 (permalink)
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.
  Reply With Quote
The Following 2 Users Say Thank You to Entropy512 For This Useful Post:
Old 05-24-2012, 09:04   #2 (permalink)
Freak Poster
 
Join Date: Mar 2008
Posts: 210
Member: 731116
Status: Offline
Sonork: 100.1612132
Thanks Meter: 24
Several of these problems, but unable JTAG solution
  Reply With Quote
Old 05-24-2012, 22:52   #3 (permalink)
Junior Member
 
Join Date: May 2012
Location: Turkey
Age: 30
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
...
  Reply With Quote
Old 07-19-2012, 15:10   #4 (permalink)
Freak Poster
 
Join Date: Oct 2001
Location: Moscow, Russia
Age: 38
Posts: 277
Member: 6653
Status: Offline
Sonork: 100.1597550
Thanks Meter: 25
There are no news? It did not turn out to make the device?
  Reply With Quote
Reply

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On


Similar Threads
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

 



All times are GMT +1. The time now is 14:35.



Powered by Searchlight © 2014 Axivo Inc.
vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2014 DragonByte Technologies Ltd.
- GSM Hosting Ltd. - 1999-2014 -
Page generated in 0.47031 seconds with 8 queries

SEO by vBSEO