[Galaxy S III General] danarama:
Latest Thread update

This section is to alert returning readers to new sections or information as they are added. New readers, please start at "Introduction"

17th Jul 2013 - Added Googy-Max. I thought this thread was dead

21st Jun 2013 - Request: Please don't ask if x.x.x (new release) has SDS fix. See "***" at end of post 1.

19th Jun 2013 - Added Official CWM Link in safe recoveries (Please only use links provided)

18th May 2013 - Revised "Stock section" to be more succinct

13th May 2013 - Added Devil kernel to safe list

3rd May 2013 - Added more about SDS v half SDS in the "What do we think we know" section

12th Apr 2013 - tried to distinguish between Fix 1 and Fix 2

6th Mar 2013 - Added ICS boaotloader to "Other links"

25th Feb 2013 - Added "Other Links" section at end of post 1

26th Jan 2013 - Update on bootloader requirement, courtesy of AndreiLUX

Previous: Added Speedmod K2-5 Test 1 Kernel

Previous: Added quotes around the fixed items for visual prominence

Introduction

Hi All,

I am seeing a lot of Buzz about the Sudden Death issue and recent fixes identified by AndreiLux and implemented into his Kernel here:

http://xdaforums.com/showthread.php?t=1691401 so please take a moment to thank him.

Unfortunately as there seems to be some uncertainty about what is or is not covered by the Fix, I have put this thread together to eliviate some of the many off topic questions posed by members in development threads, which is unfair on the developers.

So what do we think know?

Please be aware, this is not related to the Exynos Memory security issue.

The "Sudden Death" issue is caused by firmware on the (16 GB) VTU00M, revision 0xf1 eMMC (Embedded MultiMedia Card or internal memory if you like). Samsungs Kernel Source Code (Update 7) has been identified as the fix. There is still no evidence that the latest sboot bootloader addresses this issue.

Although we are still not quite 100% Certain this will prevent all S3's suffering the SDS (Predisposition to the fault etc), to the best of our knowledge it does. Even if it does not fully fix it, its closer to a fix and safer than older versions, so if its within your means to do so, an update would be advised. Please don't panic. If it's going to happen, it's going to happen and that's that. It will be repaired under warranty. I had to use a Bold 9000 for 7 days whilst mine was repaired :)

SDS seems to manifest in 2 distinct ways.

1) Complete eMMC failure. This usually happens over night whilst on charge* - The LED may be lit but the phone will not wake. Subsequent removal of the battery will turn off the LED. You will never get the LED back on. The phone will never turn on again. It needs to go to a service centre and have the motherboard replaced

* Being on Charge is NOT the cause. This is a writing to memory issue and it is more likely to happen when teh device is awake rather than in deep sleep. When the S3 is on charge, it holds a wake lock (so remains awake) throughout the entire charging period, meaning SDS is more likely to occur when on charge This does not mean you should avoid charging your phone. If it's going to happen, it's going to happen

2) Half SDS as it has not-so-affectionately become known. This tends to be more of a boot loop of the Samsung boot splash. the eMMC is partially wiped out. You cannot boot into android or recovery. It fails at the boot screen, but the screen does turn on none-the-less. The only; thing you can do is top boot into Download mode.

One problem Half SDS has is that the information download mode uses to show the status as "Official" appears to be wiped out by the bug, leaving your status as "Custom". This can leave you in a precarious position as this is what Samsung uses to establish warranty validity. You may also see your product field is blank.

Please help me maintain this list by identifying fixes as and when released, Please post the Link and Version number of anything with this fix implemented

How do I check my eMMC?

Using the EMMC check app from play, you can see if your eMMC is the VTU00M 0XF1 (affected chip).

Please note:

1) We only need this app to check the version.

2) Nothing you see in this app will change once you apply a fix. It simply gives you the version. If you expect 0xf1 to change to something else, you are mistaken. Only replacing the motherboard will do that.

What do I need to be "Safe"?

The "Fix" is actually a preventative measure. It cannot revive a "dead" device. It has to be applied before failure.

To be 100% safe, you need:

A bootloader with fixes**

[*]A Recovery with a fixed kernel

[*]A Fixed kernel to run Android

If you are a normal user only using official releases (no custom ROMs, Kernels or recoveries) then we treat you as "Stock" - read on.

Lets get to it... Where is it fixed?

-------------------------------------------------------------------

Please be weary of CWM. It can be compiled by anyone which means we cannot guarantee all versions have the latest fixes. Please only download from the links posted above

Obviously, rooted users are probably more familiar with what to do. I don't really want to recommend non-techy people flash official firmwares if they are not comfortable doing it. There will be a fix on its way to you all soon anyway, so the worst that will happen is you are affected and you have to get your phone repaired...

For those who are technical but would prefer to follow an Odin flash guide for official firmware, read the appropriate section here:

http://xdaforums.com/showthread.php?t=1671969

Recap

So to recap, if you checked you have VTU00M 0xf1 with EMMC check , you need to ensure:

If unrooted (never rooted / modded), you are on one of the "Stock" ROMs listed above

If rooted, you have one of the "Custom Kernels" OR "Custom ROMs including kernel" OR rooted "stock" with original kernel AND one of the "Custom recoveries" from the lists below

**Bootloader note

Download mode uses a bootloader packaged micro-kernel

It will only affect those who use download mode. Personally I am rooted so I don't use it so i'll be sticking with one that doesn't mess with the flash counter, however anyone who does use download mode should consider updating. Those who care more about flash counters and will stay with older bootloaders should avoid flashing anything in download mode

*** Please do not ask if newer builds (either not mentioned here, or newer than 4.1.2) include the fixes.

Samsung have a single repository of kernel source code. They continue to develop this code. When they add a fix, it's there forever in every new kernel built after the fix is added. Every fix is in new kernels automatically. They do not have a list of fixes they must add every time.

The only way a new kernel does not contain a fix is if it is manually (and specifically) removed from the source code. Can you think of any logical reason why they would do that?!

Other Links

Ultimate Unusual Freezing thread (The fix causes Freezing, possible solutions)

Ultimate SDS thread (Further discussion of the SDS issue)

ICS Bootloader for those who want to keep custom counter at 1