If ur using latest recovery & kernel ur safe.
Probably that guy was not so lucky
Sent from my GT-N7100 using xda premium
Note 2 SDS (sudden death syndrome)
- Thread starter owl74
- Start date
If ur using latest recovery & kernel ur safe.
Probably that guy was not so lucky
Sent from my GT-N7100 using xda premium
As long as Sammy are replacing the devices that fail, why bother? I'm sure it wasn't intentional...
The problem is that a lot of the phones start misbehaving and become basically unusable shortly before they die. Mine has been freezing every 10-15 minutes and when I sent if to the official Samsung repair partner here in Germany they claimed they couldn't find a problem with it and so they just sent it back to me. Now I'll have to struggle with it until if finally bricks completely at which point I'll have to wait another 1-2 weeks until I get a replacement. Samsung needs to take a hint from the automotive industry and start doing recalls when the **** up so badly...
Glad (but unfortunately) I'm not the only one experiencing SDS. I registered just to express my anger and frustration with Samsung. I had a note 2 bought from Hong Kong only 2 months ago. Its a LTE version N7105 i believe. My phone was operating perfectly until one night after I finished a call and switched off the screen, the next time i took out the phone, it was stuck at the boot screen where Samsung and the model name was displayed. Took it to Hong Kong Samsung repair centre and they said I rooted the phone which resulted in a void in my warranty. They asked for up to HK$2xxx repairing fees, but I swear to god I DID NOT root or in anyway modify the firmware. In recovery mode, the firmware is shown as CUSTOM. I have filed a complaint to HK consumer council but guess it wont help much. Someone said we should do a class action against them, i'm totally up for it!
This doesn't look like SDS... How were they able to check the flash flag at all? If your phone died of SDS they would not be able to read anything from the memory. And even if they could they'd replace it anyway, because they are aware of the issue and they know it has nothing to d with your flashing anything on it. Did you flash a custom recover or a ROM? Did you buy the phone new?
I'd contact Samsung directly if I were you and insist on a replacement. Although if your flash counter is tripped and you did buy the phone new I doubt there's much you can do
Yeah... im quite fresh to android being a ex iphone jailbreaker..
As far as using alliance rom and reading all about it...it looked as though I was covered..but obviously I was not as my phone got bricked. ...
I presume that I done something wrong somewhere. .. but wonder if it's worth patching as it didn't "seem" to work. .. either way if your phone. ...
1. Screen rotation is playing up
2. Starts freezing
3. Randomly crashes
Backup, use triangle away if possible. ...and check your guarantee. ..
Has anybody else used the correct kernel and recovery and still had the SDS???
Sent from my GT-N7100 using xda app-developers app
I am on Omega v13 with twrp latest and stock kernel... I think I am safe...
Sent from my GT-N7100 using xda app-developers app
Sent from my GT-N7100 using xda app-developers app
This doesn't look like SDS... How were they able to check the flash flag at all? If your phone died of SDS they would not be able to read anything from the memory. And even if they could they'd replace it anyway, because they are aware of the issue and they know it has nothing to d with your flashing anything on it. Did you flash a custom recover or a ROM? Did you buy the phone new?
I'd contact Samsung directly if I were you and insist on a replacement. Although if your flash counter is tripped and you did buy the phone new I doubt there's much you can do
Why don't you people read? It was specify many times that exist "half" SDS and full SDS. At "half" SDS even if the phone is not rooted and has the officialy firmware, the download mode shows that the phone has "custom" rom installed, which is NOT true. And because of this in many countries Samsung/service center wants money to replace the mainboard.
It's not about luck or not. The question is if the so called "fix" is really protect us from SDS or not? Because it was reported that even guys using safe kernels got SDS. So now we must figure out if these guys used a safe recovery or not. I tought that safe recoverys was only required if we are using it (for flash roms or wipe partitions). So if they used an unsafe CWM, maybe when they flashed the custom rom, something went bad, damaging eMMC, which caused SDS when they used the installed rom. But if they used a safe recovery, then this mean that the "fix" it's only in our minds, and Samsung don't patched anything.
Not intentional? Samsung are delivering phones with buggy chips from the Galaxy S2 series! (read about S2, Note1 brickbug, S3 SDS, Note2 SDS.) And what about data loss? These phones are now mini-computers with lots of personal data/pics/etc. inside. These premium category phones should be reliable! And what about the discomfort caused? And what about the worries about the warranty-thing? Many people spare for months to buy this phone... Samsung should be replacing dead mainboards no matter how the phone was purchased, because its his fault.
Last edited:
Zetlorf, sorry but I cannot spend all day long reading through all possible threads and responses - some of us have lives you know
I did read all the major threads on SDS and I never saw anything about half SDS.In any case, thanks for informing us!
Why are they even still selling Note 2 with the old rom? At the least they should instruct all their sales center to advice and offer customers updates on the spot. And most importantly acknowledging this serious flaw publicly. This should hit the headlines instead of all the samsung adverts posted all over the place.
Sent from my GT-N7100 using xda premium
Sent from my GT-N7100 using xda premium
Sorry, but i can't appreciate this type of sarcasm (triviality) if you give wrong advice to others who runs into trouble.Zetlorf, sorry but I cannot spend all day long reading through all possible threads and responses - some of us have lives you know
First of all, this I didn't give advice, I just shared what I know and I asked a couple of follow up questions. Second, this is why this is a FORUM and not a support line or customer service. Third, there was no sarcasm or triviality in my post. I'm sorry but I really don't have the time to read every single post on every single issue. I do my best to read as much as I can before I post and when I contribute I do it to the best of my ability.
So, again, thanks for your input and correcting my apparently wrong comment. I learned something new again.
Last edited:
What u mean maybe? There is no maybe..
Who flash patched CWM and patched kernel and gets sds?
Sent from my GT-N7100 using xda premium
Last edited:
Or maybe... you know something for sure?
Just read back and ask the guys who got SDS on 4.1.2 roms if they had safe recoveries or not.
sds had fixed said sammobile. com
http://www.sammobile.com/2013/01/17/galaxy-note-ii-software-update-n7100xxdll7-brings-battery-drain/
Sent from my GT-N7100 using Tapatalk 2
http://www.sammobile.com/2013/01/17/galaxy-note-ii-software-update-n7100xxdll7-brings-battery-drain/
Sent from my GT-N7100 using Tapatalk 2
So what if I bought my N7100 online and I live in the US? If it breaks what do I do? I wouldn't think Samsung in the US could fix the N7100.
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.
![[dcw]aaron](/data/avatars/s/4198/4198891.jpg?1600603410){kind=avatar}
New posts
-
-
Question "Need Help" UBER DRIVER APP NOT GO ONLINE
- Latest: FredMontteiro
-
