Note 2 SDS (sudden death syndrome)

Search This thread

jbreyes

Senior Member
Jan 26, 2010
65
8
Manila
You are the first one with N7100 safe :).

thats really helpful real relief. i really hope my unit is out of SDS thing because my unit doesnt have Samsung Warranty just a service warranty. and still at stock 4.1.1 and haven't have any update to 4.1.2.,

My unit is N7100 VTU00M Date :11/2012 FwRev : 0xf7
 

kebabs

Senior Member
Nov 7, 2012
79
17
From what I gathered so far, this patch only identifies chips of a certain batch or date namely 20120413 which if it is from April, it's highly likely our note2 devices aren't affected. That is to say, Samsung have indeed identified the issue and are on top of it. If other batches are identified, then the workaround work. Has any bodies n7100 actually died from SDS or is it too early to tell? Sme will die to unrelated issues, and that's fine as all phones will experience these failures but what's not wanted is the phones dying en-masse
 

bushako

Senior Member
Mar 16, 2007
1,359
327
Dubai
I think it can be concluded that people wanting to buy a Note 2 should first check the date the phone was manufactured or what chip is present in the phone before exchanging money. The question is is it possible to say what chip is present in the phone just by looking at the imei or serial number on the package?

Sent from the Rabbit Hole
 

AlanDS

Senior Member
Oct 18, 2011
717
186
Kuwait
allan.ae
in our country warranty is usselyy for 2 years.if will brick,after one years i coud get a new phone
Thats great.. But here in Kuwait, no manufacturer warranty. Only supplier warranty and its for one year only.. And during the warranty claim, most of the time blame is put on consumer itself and warranty is denied. This is what happened with my Galaxy S2 which got emmc brickbug. Even the binary counter was 0 and these people just gave the report as water-case..

So by looking at my past experience, I am getting worried with this topic..
 

craiigman

Senior Member
May 5, 2012
96
6
London
So is there anything we can do? I checked and I am affected.. Does the 4.1.2 update fix it?

Sent from my GT-N7100 using xda app-developers app
 

Nuvolaz

Senior Member
Dec 19, 2012
79
5
So is there anything we can do? I checked and I am affected.. Does the 4.1.2 update fix it?

Sent from my GT-N7100 using xda app-developers app

I think that only we can do is flash perseus kernel and Philz recovery for now. Couse in their log there is a reference to the sds problem fix.

Naturally if there are other kernel or recovery that seems to fix that big issue let us know in OP please.

Is that the "official" sds thread for note 2, true? There is no mirror threads?

So we can concentrate our knowledge in a place.

I made an xda search and I saw that this is the main thread about the sds. So we can continue here.
 
Last edited:

adytum

Senior Member
Jul 1, 2011
1,018
275
I think all kernels here have the fix implemented now.

Sent from my GT-N7100 using Tapatalk 2
 

owl74

Senior Member
Nov 15, 2012
328
586
TWRP 2.3.3.2 recovery also has the fix.
It is stated in post no. 2 of the original thread here

I will update the op when I get home tonight.
 
Last edited:
  • Like
Reactions: Nuvolaz

Top Liked Posts

  • There are no posts matching your filters.
  • 17
    Hi guys, I have been recently reading a few Note 2's dying of SDS (Sudden Death Syndrome). This has affected previous Galaxy S3 phones, and now some versions of Note 2.

    ========= Note: This is different from the exynos bug ==========

    To check, install "eMMC Check" from google play and run it. Disregard the message saying Brick bug = No. Sane chip, and look at your eMMC chip type and FWRev.

    If your:

    Type: VTU00M
    FwRev: 0xf1

    your phone is affected by the bug.

    I have read that Andreilux's Perseus kernel V31.2 (Perseus alpha31 (09/01)) temporarily repairs this bug. I am running his kernel anyway. But my question is, how many of you guys have the above chip?

    It does include the fix but otherwise they're outdated, same story as on the S3.

    Updated to 31.2; same changes as on the S3:

    Samsung's fix for the sudden death syndrome (SDS) included. It is caused by eMMC failure on phones with VTU00M 16GB internal memory chips with revision 0xF1. You can check your phone with the "eMMC Brickbug Check" in the Play Store (Ignore the message if it says you're not affected, the type and revision is what matters). The patch is a firmware soft-patch that is applied on every boot and MMC resume, it is not a permanent fix. You will need to stay forever on kernels which include the patch, this also includes updated recoveries and their embedded kernels.


    Perseus kernel thread:
    http://xdaforums.com/showthread.php?p=36552266#post36552266


    ==============================================================

    Updates and useful links:


    UK/EU Samsung repair: free samsung repairs

    I spoke to these guys this morning asking about the free postage on their site, according to them, postage is free but they are not tracked, and they advised me to use a recorded/insured postage.
    7
    for those of you who can't check the unit with emmc, here are the series of tests you can do to check if the unit has the 0xf7 chip:

    - the 1st four numbers of the IMEI code on the box should be 3550 and up
    - if you can open the box but still can't do installation of the emmc app, you can do this test: on the dial pad input *#12580*369# then look for the HW Rev (last one) and should be: MP 1.301 (MP 1.300 is the 0xf1)

    i've read this somewhere within this thread and did those tests prior to purchasing and yes i got the 0xf7.
    5
    10.000.000 devices have been sold until now.
    60.000 owner of note2 have been reading this thread.
    20-30 SDS's have been reported here.
    Bottom line: the risk of SDS is less than 0.1%!
    Fair, there might be an increase over the next months since many devices are currently not in the critical age.
    However, I don't think we do need to worry to much about it. Especially not if you're on the latest versions of ROM, Kernel and Recovery.
    Just my 2cent...

    I don't care what the statistics say. I know that if even one person encounter this issue, it gives him/her 100% frustration and upset. I may sound biased because my phone just died (no PIT partition), but trust me, I'm definitely in a better state than some of the users who have no idea what the hell is going on, given some of them do not come to the forum. Hell I wish I did not use the phone so much without coming to XDA more often to discover these issues proactively, because I assumed the device I spent this much on should have been more stable or at least not being troubled with serious issue like this.

    I do agree with you that the number is pretty low, but also think of the everyday person who has never heard of XDA they aren't reading about this problem and go to their provider and get there device replaced.... I just want Samsung to make a damn official statement about it already but it's not looking to likely

    So I am with Kjc here. Screw Samsung.

    well according to this poll result after using of 6 months(people who have 0xf1 chip) 6 phones died out of 11

    at that poll most of the people have not used their phone for six month.(11 people)

    the % is much higher!

    Again this is some statistics. Note, however, it is not about how high the chances are. It is about how LOW it is and yet I still happen to be one of the victims. Not to mention that the population of N7100 users in the forum should only be a sample of the total population of N7100 users worldwide. If I can be the one who is this unlucky, anyone can (or could have been). As of today, only 20% of VOTERS are having this issue, but the number of total voters is merely 35.


    BTW, I've only used the phone for 5 months.

    ---------- Post added at 04:19 PM ---------- Previous post was at 03:50 PM ----------

    Ok i sounded like a lil whining b1tch in the last post sorry guys. I was just hit by this sudden death thing and read around a little more and feel much better now. As I realized that it is actually pretty funny to read things like "SDS is coming" LOL. It reminds me of someone saying "OMG I'm gonna die".

    Anyway, I searched in this thread a little bit using keywords "AT&T" "U.S." "US" "United States" but found nothing. My concern is that has anyone in the U.S. who bought thru Amazon's import sellers had this issue and claimed his warranty successfully? I bought the phone Oct 31, 2012 thru an Amazon seller called Wireless Everything (or sth similar). I think the phone was from Austria when I checked after open it, and I flashed Open Germany 4.1.1 firmware. Am I gonna be able to contact and use U.K. customer service for warranty claim and repair? Or does Austria phone get to be sent to Samsung Austria?

    Thanks for any inputs if you know.
    4
    well.... According to "Theory of probability" almost 50% phone is dying after use of six months with insane chip(6 out of 11)
    Fact: Your sample size is too insignificant to make a conclusion according to normal common sense. You dun even need to read whatever theory to know that.
    4
    Oops.

    Done the test. ..

    Insane chip.

    Have the latest software so hope I am okay now.

    No root so can't check anything further.

    Worried about what would happen after warranty expires though....

    How possible is it to get a replacement phone off I explain?

    Are you in the EU law? EU law covers you for up to 5 years for a design flaw like this, or up to 2 years for regular electronic device faults.