Note 2 SDS (sudden death syndrome)
- Thread starter owl74
- Start date
mine too but that doesn't mean anything. in android reboots and freezes are quite common. i remember my old galaxy ace what reboots every day or so and freezes constantly...
if your are safe thats all, maybe try to make a full wipe and it will work better (i do it like every 3 months or so and there's a difference)
Sent from my GT-N7100 using xda premium
I'm pretty sure the most of stability problems of S3/N2 is in their poorly developed power manager.
To stabilize mine at maximum I have to raise voltages all over the list of clocks. My 200MHz voltage is the same as 1300MHz. WiFi and BT is stable more or less, GPS less so...
Reboots, locks etc. are common when the hardware pushed too much.
To stabilize mine at maximum I have to raise voltages all over the list of clocks. My 200MHz voltage is the same as 1300MHz. WiFi and BT is stable more or less, GPS less so...
Reboots, locks etc. are common when the hardware pushed too much.
Freezes and random reboot was the sds signal for sure.
My phone come with 4.12 when I bought it and also flash secure / fixed patch kernel.
But sds still happened.
My phone binary count was 1, samsung refuse to change chip with foc.
I paid usd 200 and fixed within 3 hours and ready for collection.
And now my phone was sane chips f7.
Sent from my GT-N7100 using xda premium
A solution, maybe.
I solved the issue by installing Wake Lock - PowerManager by darken and setting it to PARTIAL_WAKE_LOCK. The app also has an auto-start option. Surprisingly, battery drain is bearable. Never had SDS since. Give it a try, and if it works, maybe you could also buy the donate version of the same app.
I solved the issue by installing Wake Lock - PowerManager by darken and setting it to PARTIAL_WAKE_LOCK. The app also has an auto-start option. Surprisingly, battery drain is bearable. Never had SDS since. Give it a try, and if it works, maybe you could also buy the donate version of the same app.
Interestingly I have a 32G N2. over the last 2-3 weeks it has died on me. from random freezes. Middle of use to have to hard reboot.
I tried re flashing with the latest wanamlite rom... and I can get to the type your google account name details and then it just gets stuck. sometimes the screen is viewable other times it locks hard .
not sure if its the same issue as these ...
I tried re flashing with the latest wanamlite rom... and I can get to the type your google account name details and then it just gets stuck. sometimes the screen is viewable other times it locks hard .
not sure if its the same issue as these ...
Yes it could be affected...and if it is the 16GB model there's still no firmware that fix that. There are some software that delay but sooner or later the problem comes back.
But you could get lucky and receive a good unit.
I want to buy a used note 2 and I asked the owner to check the chip . This is what he sent me is it sds safe or is it the affected chip I dont want to buy it just to die on me from sds. Thanks for the help in advance.
eMMC chip
Type: VTU00M
Data: 11/2012
CID: 15010056545530304df7d21f3ababff7
FwRev: 0xf7
Sent from my GT-I9300 using xda app-developers app
eMMC chip
Type: VTU00M
Data: 11/2012
CID: 15010056545530304df7d21f3ababff7
FwRev: 0xf7
Sent from my GT-I9300 using xda app-developers app
Sent my Note 2 to repair. i got it back after a week and they said that the problem was the USB connector (BIG LIE!)
i came back home and i freezed 3 times in 5 minutes more or less. Once dialing PIN, once making backup of Samsung account and once connecting to WIFI. Now i wonder if here in Italy they tried at least to boot my phone....It is so damaged that is impossible to use!!!!!! There 2 options or they are stupid or they are totally unqualified to solve this problem! i already have another phone and will keeping sending my Note 2 back until they replace the MB.....I wonder who will win...
i came back home and i freezed 3 times in 5 minutes more or less. Once dialing PIN, once making backup of Samsung account and once connecting to WIFI. Now i wonder if here in Italy they tried at least to boot my phone....It is so damaged that is impossible to use!!!!!! There 2 options or they are stupid or they are totally unqualified to solve this problem! i already have another phone and will keeping sending my Note 2 back until they replace the MB.....I wonder who will win...
My Note2 is on the Samsung loving hands for the 4th time. In all 3 first attempts, Samsung mostly incompetent assholes, did just a "Software Update". I wonder what will they do now...
Patient my friend...good thing you got a phone replacement, I did that too!
Cheers!
My Note2 is on the Samsung loving hands for the 4th time. In all 3 first attempts, Samsung mostly incompetent assholes, did just a "Software Update". I wonder what will they do now...
Patient my friend...good thing you got a phone replacement, I did that too!
Cheers!
I bought a Huawei to use these days...is not so fast but at least it does not freese every 2 seconds...Monday i will print all these 106 pages of the forum and will bring to assistance to show what is the problem! I dont want that the stupid clerk will say to me again: "Samsung knows what to do, thare only 2% of cases of return of a defected device"
I am 2%!!!
I bought a Huawei to use these days...is not so fast but at least it does not freese every 2 seconds...Monday i will print all these 106 pages of the forum and will bring to assistance to show what is the problem! I dont want that the stupid clerk will say to me again: "Samsung knows what to do, thare only 2% of cases of return of a defected device"
I am 2%!!!
It's not "just" 2%...at least not for this model. The second time I was in the line to sent it (again) to Samsung there were two more Note2 and one SGS3 complaining about the exact same thing...and then the third time there it was another Note2 in the same line. I am talking about just one Store...if it is just 2% that's a hell of a coincidence.
LOL...anyway she meant that only 2% of broken devices return not working still. I know that there a lot of these ****phones with these issues...
Had to send off my Note II for repair last week as it was constantly freezing and shutting down. It had the 0fx1 chip.
Got it back from repair, and of course, it still has 0fx1. It hasn't been freezing or anything though,
Can anyone tell me if all those chips are faulty? Am I looking at having the same issues again in six months time?
Got it back from repair, and of course, it still has 0fx1. It hasn't been freezing or anything though,
Can anyone tell me if all those chips are faulty? Am I looking at having the same issues again in six months time?
I don't think so, but back to my original question, are all the 'insane' chips faulty?
Hi,
My Note 2 was also "FwRev: 0xf1". Main problem was not freezes but lost internal memory. After reset everything looked good for a few weeks. Then internal memory started to shrink. And finally I get error about no internal memory. After two resets I went to Samsung technical centre. It was yesterday. Today I got my Note 2 back. They changed mainboard and something more. Now I got "eMMC chip Type:V3WM, FwRev: 0x00". So it seems that not in every country Samsung is stupid.
My Note 2 was also "FwRev: 0xf1". Main problem was not freezes but lost internal memory. After reset everything looked good for a few weeks. Then internal memory started to shrink. And finally I get error about no internal memory. After two resets I went to Samsung technical centre. It was yesterday. Today I got my Note 2 back. They changed mainboard and something more. Now I got "eMMC chip Type:V3WM, FwRev: 0x00". So it seems that not in every country Samsung is stupid
.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 S23 - call recording - possibility of changing CSC ?
- Latest: nguyenlucky
