Hello,
I bought my note 2 three months ago & It did very well untill 2 days ago
My note 2 had a lagging & hanging issues yesterday and I had to restart it many times when it didnt repond , I thought it may be a virus so I did scans using 3 different antiviruses and was clean , then I thought it may be a bad app. so I uninstalled some of recent installed apps but no improvement ! I even removed some of videos to decrease the memory and get the sd card and the sim card out , but also no improvement !!
P.S. The phone was some times previously give me a crashed touch wiz home messages and some apps were crashed also , so I guessed it may be the launcher so I tried other launchers or may be the apps & uninstalled them but still I found the same problem .
So I got bored & went to sleep with the phone very laggy but working for some time after each restart
When I woke up today , I found the phone turned off , I tried to switch it on , but No Response at all !!! only the small red light near the front camera is fluctuating when I try to switch it on !!!
I removed the battery and tried every thing but NO RESPONSE !!!!
P.S. it`s on stock ROM with 4.1.1 JB
PLZ ppl help me
You are a victim of sds.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
You are a victim of sds.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Actually I used the sd card for only a few hours & I experienced these problems before the SD card used , I think it`s not the problem
Mu_AlTaweel said:
Actually I used the sd card for only a few hours & I experienced these problems before the SD card used , I think it`s not the problem
Click to expand...
Click to collapse
SDS - Sudden Death Syndrome. Its not SD card. If your phone chip was 0xf1 and your phone was on 4.1.1 so its sure sds and phone is dead. You had to update your phone to 4.1.2 with Odin because it has fix from sds .
Sent from my GT-N7100 using xda premium
Have you ever rooted ? If not return phone to service center asap.
If yes then go into download mode and click volume up and tell what is your counter status
Sent from my GT-N7100 using xda app-developers app
T511 said:
SDS - Sudden Death Syndrome. Its not SD card. If your phone chip was 0xf1 and your phone was on 4.1.1 so its sure sds and phone is dead. You had to update your phone to 4.1.2 with Odin because it has fix from sds .
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
thanx for yor reply & explanation , but how can I update it with odin ?! it doesn`t start up or connect to the PC !
UtkarshGupta said:
Have you ever rooted ? If not return phone to service center asap.
If yes then go into download mode and click volume up and tell what is your counter status
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
thanx for reply ,
I never rooted the device
If I return it to the service center , how can I avoid such problem in the future ?
Mu_AlTaweel said:
thanx for reply ,
I never rooted the device
If I return it to the service center , how can I avoid such problem in the future ?
Click to expand...
Click to collapse
When you get replacement phone check its chip ( via "emmc brickbug check" application from play market ) . If its 0xf1 ... do not take it... if its chip 0xf7 or other you can take it. Mainly phones with 0xf1 on 4.1.1 affected sds. And main - upgrade to 4.1.2 as it has fix from sds.
Sent from my GT-N7100 using xda premium
T511 said:
When you get replacement phone check its chip ( via "emmc brickbug check" application from play market ) . If its 0xf1 ... do not take it... if its chip 0xf7 or other you can take it. Mainly phones with 0xf1 on 4.1.1 affected sds. And main - upgrade to 4.1.2 as it has fix from sds.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
thank you very much I really appreciate your help , I will send it to the service center & see what they will say .
T511 said:
When you get replacement phone check its chip ( via "emmc brickbug check" application from play market ) . If its 0xf1 ... do not take it... if its chip 0xf7 or other you can take it. Mainly phones with 0xf1 on 4.1.1 affected sds.
Click to expand...
Click to collapse
If you get the chance to check the chip before you get the new device. Which I doubt you will. You'll probably get the phone sealed, and Samsung will hardly get you the new phone only because there is a chip inside which is prone to fail. This is the main problem. Samsung still doesn't acknowledge the SDS. At least not in whole.
T511 said:
And main - upgrade to 4.1.2 as it has fix from sds.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
This was never confirmed by Samsung. If you ask me, it's a myth. Some devs thought it might be the fix, and Samsung never denied it. That doesn't mean it is a fix. They fixed the exynos bug, but it has nothing to do with this.
I think it's awful how Samsung threats us.
estugarda said:
If you get the chance to check the chip before you get the new device. Which I doubt you will. You'll probably get the phone sealed, and Samsung will hardly get you the new phone only because there is a chip inside which is prone to fail. This is the main problem. Samsung still doesn't acknowledge the SDS. At least not in whole.
This was never confirmed by Samsung. If you ask me, it's a myth. Some devs thought it might be the fix, and Samsung never denied it. That doesn't mean it is a fix. They fixed the exynos bug, but it has nothing to do with this.
I think it's awful how Samsung threats us.
Click to expand...
Click to collapse
so you say that there`s no known solution for this disaster , I should only hope to get the right chip & no clue to avoid this in the future ?!!
I have written 100s of times in this thread.
Update asap.
These kinds of sds threads should be stickied so everyone can get a sneak peek of the fate if they don't upgrade.
Probably you didn't do it because of battery life. Or did even downgrade.
Now you and others may understand something.
Sent from my GT-N7100 using xda app-developers app
Hi guys ,
I got my device back from the service center & they got the chip replaced not the whole device
the new chip is 0x19 now , but in (eMMC brickbug check) says under title of (brick bug) : yes,insane chip
any explanation plz ?!!
Forget about what it says because so far the only.one's that are affected by the SDS are the Note 2 with 0xf1 revisions. Just update your android version to 4.1.2 and you'll be fine.
Sent from the rabbit hole.
bushako said:
Forget about what it says because so far the only.one's that are affected by the SDS are the Note 2 with 0xf1 revisions. Just update your android version to 4.1.2 and you'll be fine.
Sent from the rabbit hole.
Click to expand...
Click to collapse
thank you very much
Related
I don't see Samsung acknowledging anywhere that 4.1.2 fixes SDS. I see a bunch of samsung/android websites ASSUMING as such, but no proof.
The exynos exploit? Yes. But I'm thinking that we're all assuming 4.1.2 is SDS safe.
I'm starting to think that there IS no fix. Samsung doesn't even want to acknowledge it. The only fix is being on the new chip (07).
No phones with dll7+ have been reported to have sds. So theoretically it does patch it.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
No phones with dll7+ have been reported to have sds. So theoretically it does patch it.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Exactly. We're just assuming. So theoretically we could be wrong, and someone could be enjoying better battery life on 4.1.1 and have the same exact risk exposure as we do.
No.
All the cases of sds have been on 4.1.1 roms. Non on dll7 ones.
4.1.1 is highly vulnerable.
Why do you even take the risk.
The glass is half full not half empty.
Be optimistic and not pessimistic.
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
No.
All the cases of sds have been on 4.1.1 roms. Non on dll7 ones.
4.1.1 is highly vulnerable.
Why do you even take the risk.
The glass is half full not half empty.
Be optimistic and not pessimistic.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
You're missing the point. I'm not going to downgrade to 4.1.1, because I'm worried, just like you.
The point is it seems to me that we are throwing around 4.1.2 as FIXED, when it possibly might not be. On this forum we are saying that it is FACT, when it seems to be just assumptions. I believe that's a possible false sense of security we are giving people. I feel that's harmful. We should encourage people to upgrade to 4.1.2, but we should say "it seems the SDS bug is fixed in 4.1.2", not that it IS, when we don't know for sure.
ksc6000 said:
You're missing the point. I'm not going to downgrade to 4.1.1, because I'm worried, just like you.
The point is it seems to me that we are throwing around 4.1.2 as FIXED, when it possibly might not be. On this forum we are saying that it is FACT, when it seems to be just assumptions. I believe that's a possible false sense of security we are giving people. I feel that's harmful. We should encourage people to upgrade to 4.1.2, but we should say "it seems the SDS bug is fixed in 4.1.2", not that it IS, when we don't know for sure.
Click to expand...
Click to collapse
Somewhat I agree
Sent from my GT-N7100 using xda app-developers app
ksc6000 said:
We should encourage people to upgrade to 4.1.2, but we should say "it seems the SDS bug is fixed in 4.1.2", not that it IS, when we don't know for sure.
Click to expand...
Click to collapse
Samsung officially never say it, so i don't think without this some one stamp it. (bcoz this time patch done by themselves, if xda developer have did that then surely they can stamp)
At least myself always use words 'its believed to be fixed for sds'
Now why should we believe
-kernel from ll7 and later have found to have that insane chip version mentioned in its source code(which was never there before) , that strongly suggest samsung have made something patch for that chip, so when kernel found such chip may block issuing such commands
-we have not seen any sds case on those latest rom which believed to have patched for.
PS : if you aware of brick bug on Note1 and s2,there was also related to mmc chip and wiping command was causing brick, samsung till today never acknowledged (or accepted) it was there and thousand bricking case reported
And there was not a single case was reported after kernel was patched by xda developer. (chainfire, philz, hydrocore, soeedmod are examples)
Ultimately when samsung released jb leak, it found samsung have patched it, and somewhat agree with developer in personal communication. So it's samsung policy, I don't expect they will ever do it. Disappointing but true.
Sent from my GT-N7100 using xda premium
dr.ketan said:
Samsung officially never say it, so i don't think without this some one stamp it. (bcoz this time patch done by themselves, if xda developer have did that then surely they can stamp)
At least myself always use words 'its believed to be fixed for sds'
Now why should we believe
-kernel from ll7 and later have found to have that insane chip version mentioned in its source code(which was never there before) , that strongly suggest samsung have made something patch for that chip, so when kernel found such chip may block issuing such commands
-we have not seen any sds case on those latest rom which believed to have patched for.
PS : if you aware of brick bug on Note1 and s2,there was also related to mmc chip and wiping command was causing brick, samsung till today never acknowledged (or accepted) it was there and thousand bricking case reported
And there was not a single case was reported after kernel was patched by xda developer. (chainfire, philz, hydrocore, soeedmod are examples)
Ultimately when samsung released jb leak, it found samsung have patched it, and somewhat agree with developer in personal communication. So it's samsung policy, I don't expect they will ever do it. Disappointing but true.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
So essentially what you're saying is that it appears samsung has fixed it in 4.1.2, but they will probably never acknowledge it? Am I reading that right?
Exactly,
B'coz acknowledging it is indirectly accepting they have used faulty chip.
Sent from my GT-N7100 using xda premium
Mine just died yesterday, N7105 running on 4.1.2.
Not sure the kernel though.
Passed it to Samsung care today. They said they will change the motherboard and .. it will take around 2 weeks as their motherboards are out of stock. So you can imagine the number of spoiled note 2.
From Singapore btw~
Samsung will never acknowledge the SDS issue. Doing so would open them up to one hell of a mess in lawsuits from pee'd off customers.
actually it just fixes the issue if you update before having a corrupted chip. There were lots of reports of 4.1.2 died phones but we assume that it is because, as they said, the phone was having problems before updating.
hope my explanation helped you, bests
Sent from my GT-N7100 using xda app-developers app
Hi Everybody!
I'm seriously considering buying a Samsung Galaxy Note2 but am scared by the sudden death issue in Note 2 being reported by so many people. It would be a really sad thing if I loose my hard earned money due to this issue. I'm aware that Samsung is fixing such mobiles in service center but all they are doing is to replace the motherboard with a similar one (with a faulty eMMC chip, if that is the real cause). So it should be ok for one year till I'm in warranty but what would happen after one year... And Samsung is not gonna acknowledge it and offer a software fix. All I can do from my side is to root and apply Persius Kernel. Being very confused, I decided to ask this question to this knowledgeable community. Please advise me how serious is the sudden death issue and what are the chances that one may encounter it? Please respond...
regards,
dcpathak
Latest rooms have the fix. Wait for s4 release which is just round the corner. Note 2 prices will go down.
Sent from my GT-N7100 using xda app-developers app
koalauk said:
Latest rooms have the fix. Wait for s4 release which is just round the corner. Note 2 prices will go down.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Roms*
Sent from my GT-N7100 using xda app-developers app
koalauk said:
Latest rooms have the fix. Wait for s4 release which is just round the corner. Note 2 prices will go down.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thanks Koaluak!
yes, I'm also waiting for that release. In India, Samsung has reduced prices just some 15 days back (perhaps to deal with Micromax A 116 HD launch).
Has Samsung issued any official ROM with the fix?
regards,
dcpathak
To answer. ..go to Perseus kernel thread and read changelog in first post to understand about sds bug and Samsung fixes
scribbled from my note 2 (N7100)
pakure said:
To answer. ..go to Perseus kernel thread and read changelog in first post to understand about sds bug and Samsung fixes
scribbled from my note 2 (N7100)
Click to expand...
Click to collapse
Thanks Pakure,
Flashing Perseus Kernal means rooting the note 2. I just wanna avoid that for some time. And that is also not a permanent solution, it just keeps on applying the patch at each reboot.
regards,
dcpathak
dcpathak said:
Has Samsung issued any official ROM with the fix?
regards,
dcpathak
Click to expand...
Click to collapse
Yes latst 4.1.2(2013 released) ROM have fix.
You need not to root for that, just get ROM and flash using Odin
Read fiesr post of first line on my signature.
I had sudden death issue. In service center they changed my NOTE 2 and gave another new one..)))
So this sudden death issue has been fixed with the latest software update from Samsung?
Sent from my GT-N7105 using Tapatalk 2
thomasshiow said:
So this sudden death issue has been fixed with the latest software update from Samsung?
Sent from my GT-N7105 using Tapatalk 2
Click to expand...
Click to collapse
Answer is in post#7
How comes s IV would drop note 2 price? That makes no sense at all.. 2 completely different devices
Heck.. Even note I it's still above 550$ so pffft
Tapatalking on my n7100
Anybody tried to revive an SDS-dead phone with the hard reset procedure?
How you can perform hard reset on sds bricked device?
Sent from my GT-N7100 using xda premium
dr.ketan said:
Yes latst 4.1.2(2013 released) ROM have fix.
You need not to root for that, just get ROM and flash using Odin
Read fiesr post of first line on my signature.
Click to expand...
Click to collapse
Thanks a lot dr.ketan,
I've downloaded the rom from your link. Just one question: is this also available as over the air update?
regards,
dcpathak
I didn't get your question
Sent from my GT-N7100 using xda premium
dr.ketan said:
How you can perform hard reset on sds bricked device?
Click to expand...
Click to collapse
1. Remove SD card, SIM and battery.
2. Press and hold the power button for more than 30 seconds..
3. Insert the battery only and try to boot.
I'm using this procedure when my Note 2 goes nuts after playing with kernels. When even full stock over Odin cannot revive it... happened already 4 times.
dr.ketan said:
Yes latst 4.1.2(2013 released) ROM have fix.
You need not to root for that, just get ROM and flash using Odin
Read fiesr post of first line on my signature.
Click to expand...
Click to collapse
One update dr.ketan: please follow this link:
http://forum.xda-developers.com/showthread.php?t=2093599&page=26
here loty78 had sds even when he updated to 4.1.2! Then another guy named estugarda mentions ,"Not all 4.1.2 were DLL7 - the version where the fix supposedly appeared. Many people had 4.1.2 DLL4."So now how should I know if the updates we are applying have this DLL7?
My other question was that can we update our note 2 directly using wi-fi over the air (like I could do for my HTC desire z). This may depend on whether this update is already available in India.
regards,
dcpathak
This you may call hard reboot not hard reset
Btw on sds you can't do anything as this is condition where damage is physically.
Sent from my GT-N7100 using xda premium
Hard reboot is done with the battery inside and requires just a few seconds.
Moreover when I played with kernels and undervolting, my WiFi and BT sometimes self-disabled and could not be revived with any flashing, ODIN, stock/custom, different kernels etc. Only the "hard reboot/reset" helped somehow.
And it does requires 30+ seconds of power button hold, lesser time has no effect.
simple thing, Can physically damaged things get cured with SW ?
your WiFi and BT get to resume b'coz there was no physically damage in it.
---------- Post added at 10:43 PM ---------- Previous post was at 10:25 PM ----------
dcpathak said:
One update dr.ketan: please follow this link:
http://forum.xda-developers.com/showthread.php?t=2093599&page=26
here loty78 had sds even when he updated to 4.1.2! Then another guy named estugarda mentions ,"Not all 4.1.2 were DLL7 - the version where the fix supposedly appeared. Many people had 4.1.2 DLL4."So now how should I know if the updates we are applying have this DLL7?
My other question was that can we update our note 2 directly using wi-fi over the air (like I could do for my HTC desire z). This may depend on whether this update is already available in India.
regards,
dcpathak
Click to expand...
Click to collapse
I have just read that, yes victim is not sure which 4.1.2 ROM he has installed
I have gone through some more details, he has bought it from Thailand so likely he may have Thailand ROM installed and he said he last updated couple of week back ( i think latest update for thailand released hardly 8-10 days and before that there was LL7 was released and exactly i remember due to some reason that LL7 was rolled back suddenly, so possibly there are chances it may not had properly fixed (we never get it know from samsung), otherwise there was no issue on LL7.
Another possibilities is SDS effect is cumulative, if you have run device on older ROM for long time, it is possible it has already damage took place before you have updated it, and can be result to death once it has good quantity of damage occurs.
your other question
yes latest ROM you can update with OTA in india over wifi.
Hey Guys. I've just got my One V's Main Board changed for quite a huge amount. (Accompanied with screen, battery etc)
My phone now is with unlocked bootloader, rooted with Custom ROM installed.
I've read about this QHSUSB_DLOAD problem, that the phone suddenly goes off on it's own and then this problem occurs. Or by pressing Vol Up + Power. Are these the only possibilities ? How common is it to have this problem ? Is this very unlikely to happen ? Sorry, I'm just a little scared. I read somewhere that this problem is sorted out on newer boards. Is it true ? And if, I, by chance, face the same problem, then will HTC repair my phone for free ?
noo..no repair work for free..
there is a very low chance that you'll encounter the problem
unless ofc if u mess with your phone
This means that HTC will charge me for it's repairs. Right ?
But it's very unlikely to happen. I read somewhere that this problem has been sorted on new boards. Is this true ?
GamingFreak said:
This means that HTC will charge me for it's repairs. Right ?
But it's very unlikely to happen. I read somewhere that this problem has been sorted on new boards. Is this true ?
Click to expand...
Click to collapse
Yes its true and HTC will take a long time to fix it as its free
Sent from my One V using xda app-developers app
soham_sss said:
Yes its true and HTC will take a long time to fix it as its free
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
It's true ? You mean that the newer boards have got this sorted out. I got my Mother Board replaced in Feb 2013, so I need not worry about it, right ?
And I've unlocked the bootlaoder, rooted, PA running. So if I face this problem, you mean that HTC will repair my phone for free ! .. As you said.
And one more thing - ' Long time to fix it ' ? What's the meaning of this ?
GamingFreak said:
It's true ? You mean that the newer boards have got this sorted out. I got my Mother Board replaced in Feb 2013, so I need not worry about it, right ?
And I've unlocked the bootlaoder, rooted, PA running. So if I face this problem, you mean that HTC will repair my phone for free ! .. As you said.
And one more thing - ' Long time to fix it ' ? What's the meaning of this ?
Click to expand...
Click to collapse
Most probably a month. So I've heard...
And yeah, They'll mostly replace for free, just never tell that you every rooted the phone
Sent from my One V using xda app-developers app
soham_sss said:
Most probably a month. So I've heard...
And yeah, They'll mostly replace for free, just never tell that you every rooted the phone
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
I got my Main Board replaced in Feb 2013. So, do I need to worry about it ?
GamingFreak said:
I got my Main Board replaced in Feb 2013. So, do I need to worry about it ?
Click to expand...
Click to collapse
I don't think so- I once tried vol up and power combination and nothing happened
But to be on safer side, don't try it- unless you are extremely curious like me
Sent from my One V using xda app-developers app
soham_sss said:
I don't think so- I once tried vol up and power combination and nothing happened
But to be on safer side, don't try it- unless you are extremely curious like me
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
I did too....nothing happened....
Sent from my One V using xda premium
Hmm.
soham_sss said:
I don't think so- I once tried vol up and power combination and nothing happened
But to be on safer side, don't try it- unless you are extremely curious like me
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
handryg555 said:
I did too....nothing happened....
Sent from my One V using xda premium
Click to expand...
Click to collapse
Thanks Guys. I hope that I'll not suffer from that problem.
And as Soham said ; I'm relieved.
Anyway, what are the manufacturing dates of your respective phones (One V) ?
GamingFreak said:
Thanks Guys. I hope that I'll not suffer from that problem.
And as Soham said ; I'm relieved.
Anyway, what are the manufacturing dates of your respective phones (One V) ?
Click to expand...
Click to collapse
Mine is in June.
Sent from my One V using xda app-developers app
Mine was manufactured in March. But didn't get any of the problems that are known so far.
Sent from my One V using xda premium
R: QHSUSB_DLOAD Mode Possibilities
Mine July .. never had any problem
May no prob
My phone was on QHSUSB_DLOAD mode [its rooted + unlocked bootloader + custom FW ] I struggled a lot to get out of that mode but no way so i gone to service center and told them that phone is not getting switched on .......... But Htc serviced its free for me
sreerij said:
My phone was on QHSUSB_DLOAD mode [its rooted + unlocked bootloader + custom FW ] I struggled a lot to get out of that mode but no way so i gone to service center and told them that phone is not getting switched on .......... But Htc serviced its free for me
Click to expand...
Click to collapse
When did this happen ?
So, sometimes, on recovery (rarely, though), while flashing, my phone crashes. I flashed an SDS safe ROM/recovery and haven't looked back since, since there were no symptoms before then. But I'm starting to worry, because I had to restore the stock ROM once, after it crashed during flashing, and won't go into anywhere but download.
My ROM info is in my signature, and recovery is PhilZ, latest (4.91.2, I believe). I have Triangle Away, set to auto reset at boot. So, if it's at 0/Offical/No, they should replace my phone if it goes SDS, right?
Edit: I believe I had some early recovery corruption. When I rooted for the first time with CF auto root, it wouldn't boot into recovery after that, and I had to flash stock recovery all over.
Sent from my GT-N7100 using xda premium
*bump* Can someone answer if these are really SDS symptoms? And whether I'll be affected on a safe chip? Please?
Sent from my GT-N7100 using xda premium
I have an affected chip
I have a affected chip, and i doen't have any symptoms.
I thing is solved by samsung with the last update.
katobest said:
I have a affected chip, and i doen't have any symptoms.
I thing is solved by samsung with the last update.
Click to expand...
Click to collapse
It was. But if you get *any* NAND corruption before updating, that can't be fixed and it WILL get worse steadily, resulting in SDS anyway. At least that's how I understand it.
Sent from my GT-N7100 using xda premium
If you have a SDS safe kernel and your phone crashes, look at your kernel log (adb bugreport) and if you find eMMC errors, it might be related to SDS.
If you don't have a SDS safe kernel, then I believe that as the name suggests, you go directly from a perfectly working device to brick.
see : http://forum.xda-developers.com/showthread.php?t=2096045
Download from market eMMMC BrickBuck Check .Install It.Run it.See what it says.If the FwRev is 0xf1 you may be a victiom of SDS.Note ,that the latest android firmware for Note 2 . 4.1.2,baseband version N7100XXDLK7 and Build:JZ054KN7100XXDMB2 has a patch for stopping SDS.It's kind of a workaround ,the chip is still faulty.I also have the faulty chip with this version.Un-rooted stock.Had it since February 20.Nothing bad happened
Same firmware does not prevent freezing
DonSpeedy7 said:
Download from market eMMMC BrickBuck Check .Install It.Run it.See what it says.If the FwRev is 0xf1 you may be a victiom of SDS.Note ,that the latest android firmware for Note 2 . 4.1.2,baseband version N7100XXDLK7 and Build:JZ054KN7100XXDMB2 has a patch for stopping SDS.It's kind of a workaround ,the chip is still faulty.I also have the faulty chip with this version.Un-rooted stock.Had it since February 20.Nothing bad happened
Click to expand...
Click to collapse
Hi I have the same firmware and and running stock too, bought my UK sim free Note2 N7100 last year on launch, however it has started freezing since last 2 weeks, I restored to factory default but started crashing/freezing as soon as I started restoring my data, took to Samsung service centre who seemed to think it was software related and restored again and told me to load one app at a time. Useless as it is still crashing even though I have not updated any of the preinstalled software.
I have now been told it needs to go to Samsung level 3 techies as service centre not aware of any bugs - will not comment on internet reports, this means the phone will be sent to Poland for repair and I am left without a phone for 2-3 weeks. I had an appointment booked at their "Flagship store" for a week in advance and was called day before to be told they were cancelling the appointment because they are refurbishing the store and could have one in about two weeks!!! Terrible service from Samsung.
They probably will not acknowledge exact cause of fault.
There's a reason the "S" in SDS stands for sudden and not symptomatic. There are no symptoms it's sudden.
Sent from my GT-N7100 using xda premium
bushako said:
There's a reason the "S" in SDS stands for sudden and not symptomatic. There are no symptoms it's sudden.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Not true anymore. With the unofficial fix (as samsung never made any announcements) people are reporting freezes and crashes. In a way it's indicating something is happening and can be considered a symptom.
Sent from my GT-N7100 using xda premium
antt00 said:
Not true anymore. With the unofficial fix (as samsung never made any announcements) people are reporting freezes and crashes. In a way it's indicating something is happening and can be considered a symptom.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
According to the dev of neak kernel, Simone, and a few other dev sources that I can't remember, these freezes on safe kernels is actually the protection kicking in, blocking the harmful eMMC commands.
Better to get a broken nose from an ejected airbag, than a broken body.
Sent from my GT-N7100 using Tapatalk 2
adytum said:
According to the dev of neak kernel, Simone, and a few other dev sources that I can't remember, these freezes on safe kernels is actually the protection kicking in, blocking the harmful eMMC commands.
Better to get a broken nose from an ejected airbag, than a broken body.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
It makes a lot more sense, so we can conclude that these freezes are not symptoms to the SDS but merely a sign that the fixes are doing what they're suppose to be doing.
Sent from my GT-N7100 using xda premium
adytum said:
According to the dev of neak kernel, Simone, and a few other dev sources that I can't remember, these freezes on safe kernels is actually the protection kicking in, blocking the harmful eMMC commands.
Better to get a broken nose from an ejected airbag, than a broken body.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Also the latest 4.1.2 official update fixes that problem.(baseband N7100XXDLK7)
Hey! I just bought 3 days ago a Note 2 and i like it v much, except 1 problem. I installed Android Rev ROM and after 1 hour of using the phone is heating (downloading apps, listening music) and it is freezes (in this time i can lock and unlock the screen, but is still unresponsive). Is a problem from the rom or is a problem on my phone?
i tested this 3 times and always is freezing in same way,
Thank you!
I except it to be SDS so if it keep freezing it is better to send it back again
Sent from my GT-N7100 using xda premium
evaworld said:
I except it to be SDS so if it keep freezing it is better to send it back again
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
I bought a phone from a guy, not from a shop and i dont have warranty . Is there any chance to have a bug fix for this, from Samsung or is a hardware problem?
Is there any custom ROM that can fix this?
Have you done standard procedure of doing a megawipe and then try flashing the rom again? Take out the memory card and use it for a bit to see if it makes any difference.
Sent from my GT-N7100 using xda premium
bushako said:
Have you done standard procedure of doing a megawipe and then try flashing the rom again? Take out the memory card and use it for a bit to see if it makes any difference.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
i've done dalvik cache and normal format from cwm. I dont have a memory card in it.
xTee said:
I bought a phone from a guy, not from a shop and i dont have warranty .
Click to expand...
Click to collapse
So did I.
It doesn't matter, warranty is given to the product, not to the customer. Obtain the invoice given to the guy. They have to fix it.
xTee said:
Hey! I just bought 3 days ago a Note 2 and i like it v much, except 1 problem. I installed Android Rev ROM and after 1 hour of using the phone is heating (downloading apps, listening music) and it is freezes (in this time i can lock and unlock the screen, but is still unresponsive). Is a problem from the rom or is a problem on my phone?
i tested this 3 times and always is freezing in same way,
Thank you!
Click to expand...
Click to collapse
Download and install eMMC Check from playstore and see if the FwRev is 0fx1. If it is so, then your mobile is sds prone. If possible return it to the guy.
It is an Sudden Death Syndrome. Flash the 4.1.2 firmware. If the phone was dead, you can use warranty.
Sent from my GT-N7100 using xda premium
dcpathak said:
Download and install eMMC Check from playstore and see if the FwRev is 0fx1. If it is so, then your mobile is sds prone. If possible return it to the guy.
Click to expand...
Click to collapse
done. FwRev: 0xf1. Note 2 sudden death: YES. Insane Chip
My friend has the same rev, with insane chip and he dosent have problems. he owns the note 2 till dec and no problems. Should i try another roms? I tryed only with Revolution hd+ stock, perseus alpha 35 kernel.
[email protected] said:
So did I.
It doesn't matter, warranty is given to the product, not to the customer. Obtain the invoice given to the guy. They have to fix it.
Click to expand...
Click to collapse
I dont have any papers. Just the phone and the charger
A super wipe and a start over helped me.
Try running stability test to clear out hardware issue.
Sent from my GT-N7100 using xda premium