...By running the app in the OP... They cannot "repair" the chip. It either has the faulty chip, or it has a different chip. It's not complicated...
Note 2 SDS (sudden death syndrome)
- Thread starter owl74
- Start date
...By running the app in the OP... They cannot "repair" the chip. It either has the faulty chip, or it has a different chip. It's not complicated...
Most of your posts are in this thread, so I assume you have been following things closely,
any advice?
About Device is reporting;
Version 4.1.2
Baseband Version N7100XXDLK7
Build Number JZ054K.N7100XXDMB2
Kies is reporting current firmware version is; PDA:MB2 / PHONE:LK7 / CSC:MA5 (XXX)
Last firmware update was last month OTA
Question is, which number do I look at to tell which update I have?
And does it have an SDS fix built in?
If not, what should I do?
(new kernel? New ROM? Both?)
.
----------------EDIT---------------
Done a bit of reading round, and I gather it's the Build Number not the Baseband Version I should be concerned with. My build number is XXDMB2 (which it turns out was released start of March for UK). Does this build protect me, seeing as my symptoms started just about the time of the update?
Initially, I thought it was the update that was causing the symptoms and tried a factory reset, not realising that the firmware is NOT reset when you do that.
.
.
.
.
---------- Post added at 10:12 AM ---------- Previous post was at 10:09 AM ----------
You are not being clear as to your situation.
There is nothing you can see on the phone that will tell you this, you must run the app.
So, if you have the second hand phone in your hands, download and run the app.
If you are buying the phone, get the vendor to do it for you and report.
Last edited:
...By running the app in the OP... They cannot "repair" the chip. It either has the faulty chip, or it has a different chip. It's not complicated...
but according to this post #412
i thought his phone came back from repair?
and this man is also talking about repair
The chip itself cannot be repaired. They can repair the phone by replacing the board with the affected chip on it.
![[dcw]aaron](/data/avatars/s/4198/4198891.jpg?1600603410){kind=avatar}
if you guys could just back read..all infos are already posted in this thread..it's becoming redundant to answer same questions over and over again..
I know you're new here and all, but geez dude... It's not rocket science! Try thinking a little first, yeah?
Had the same experience in Germany. I think they are working on instructions from Samsung. Either try to get a replacement from your vendor or send it back a second time - usually it gets repaid the second time around.
Sent from my GT-N7100 using Tapatalk 2
TRIED EVERYTHING but ISSUE BEYOND FIX
Model: GT-N7100
Baseband: N7100XXDLK7
Build: JZo54K.N7100XXDLK7
eMMC Chip:
Type: VTU00M
Date:08/2012
FwRev:0xf1
So I bought this phone back in Oct2012 and from last month I am start having this so called "Sudden Death" "Freeze" issue so check with EMMC app and yup the result is Insane Chip. Now from last 3 days I have tried all the kernels including(persius and XDLL7) and bunch of other recoveries and ROMS and nothing is fixing this problem. Now this is "Made in UK" version and I am living in USA so Samsung Mobile USA has declined to honor the warranty so Samsung UK has suggested to me to contact Samsung USA. Now I have spend $700 for this so called flag shipped device and all I have got is brick for this price.As this point I am so mad at Samsung that I have decided to go "DARKSIDE with APPLE or WP8 NOKIA" as they honor warranty worldwide does not matter where it manufactured . One thing I dont understand though it was perfectly fine for first 4 months without having any problem working like a charm without any root or custom rom and now suddenly its start behaving so crazy that almost unable to use. If any one can suggest me the solution so I dont have to waste my $700. Thanks so much for all your support and efforts in advance my fellow XDA members
Model: GT-N7100
Baseband: N7100XXDLK7
Build: JZo54K.N7100XXDLK7
eMMC Chip:
Type: VTU00M
Date:08/2012
FwRev:0xf1
So I bought this phone back in Oct2012 and from last month I am start having this so called "Sudden Death" "Freeze" issue so check with EMMC app and yup the result is Insane Chip. Now from last 3 days I have tried all the kernels including(persius and XDLL7) and bunch of other recoveries and ROMS and nothing is fixing this problem. Now this is "Made in UK" version and I am living in USA so Samsung Mobile USA has declined to honor the warranty so Samsung UK has suggested to me to contact Samsung USA. Now I have spend $700 for this so called flag shipped device and all I have got is brick for this price.As this point I am so mad at Samsung that I have decided to go "DARKSIDE with APPLE or WP8 NOKIA" as they honor warranty worldwide does not matter where it manufactured . One thing I dont understand though it was perfectly fine for first 4 months without having any problem working like a charm without any root or custom rom and now suddenly its start behaving so crazy that almost unable to use. If any one can suggest me the solution so I dont have to waste my $700. Thanks so much for all your support and efforts in advance my fellow XDA members
Can try sending the phone back to the UK for repair. It is still under warranty rite?
Sent from my GT-N7100 using xda premium
Sent from my GT-N7100 using xda premium
Samsung's poor limited warranty
I had a similar issue with Samsung's limited warranty. I was on vacation in India when my Note 2 had SDS and Samsung India would not honour the warranty so I had to wait until I returned to the UK before sending my Note 2 for a warranty repair. This delayed repair spoiled my holiday and I was without a working Note 2 for 5 weeks.
I will not be buying Samsung again due to it's poor limited warranty.
I had a similar issue with Samsung's limited warranty. I was on vacation in India when my Note 2 had SDS and Samsung India would not honour the warranty so I had to wait until I returned to the UK before sending my Note 2 for a warranty repair. This delayed repair spoiled my holiday and I was without a working Note 2 for 5 weeks.
I will not be buying Samsung again due to it's poor limited warranty.
Not that I am excusing Samsung, I've had my fare share of problems with them too, but I don't think that any of the other major players are any different. I've had exactly the same problems with Apple and Cannon and in both cases we're talking much bigger sums - the canon was a 7k camera and while I'm a professional service member that didn't help the issue either...
Sent from my GT-N7100 using Tapatalk 2
Sell yours if it is still in working condition & buy something else. I did the same with mine. Don't get me wrong, i loved my note2 but couldn't risk getting SDS after warranty expiry. Damn you, Samsung!
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
17Hi 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?
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.7for 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
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.
So I am with Kjc here. Screw Samsung.
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
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
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.
