Develop Bugs

GT-N7100 Won't turn on or charge

Hey guys,
From what I've read, this seems to happen to a lot of different phones, but not out of the blue and I didn't find anything on the Note 2, so I'm wondering if it's the same issue and if my only hope is to get a replacement. It seems to be dead at the moment.
Before going to bed, I charged my phone to about 90% and then unplugged it and left it on my desk.
This morning when I woke up, it was off, which was kind of odd, since there's no way it would fully discharge over night. I tried turning it on, plugging it to charge, swapping out the battery for another original one I purchased directly from Samsung, trying other chargers, even the PC and different USB cables, all to no avail.
The only thing I noticed was that the proximity sensor seems to flash every 5-10 seconds, and I'm not sure what that would mean, other than the fact that it's getting some power somehow so that it can light up.
For the time being, I removed the battery and left it like that while I'm at work.
The phone is running the stock ROM for the GT-N7100, nothing was ever modified, it's not rooted or anything.
I know there was a firmware update pop-up on it at some point, but I hadn't installed it.
Any clues guys? I know there's some really knowledgeable people here, so I'm hoping someone might have an idea!
Thanks for the help and sorry for the text!

That sounds like the dreaded sudden death syndrome, how long have you had your device? You need to take it to a service shop. Was it rooted?
Sent from my GT-N7100 using xda app-developers app

Sorry to hear it . Last week I left mine on my bedside table around same charge 90% full and it was completely discharged and just wouldnt turn on but after leaving it on charge for about 30 min when I checked it started working .
Sent from my GT-N7100 using xda app-developers app

Heard of that for the S III but not the Note II!
Never rooted, nope :/
I've had it since November, got it from Newegg while I was in the US.
I should contact Samsung for a service shop location then? I've never done anything like that before.
Thanks!

koalauk said:
Sorry to hear it . Last week I left mine on my bedside table around same charge 90% full and it was completely discharged and just wouldnt turn on but after leaving it on charge for about 30 min when I checked it started working .
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
When you plugged it in to charge, did the LED light up at all? Mine acts as if it wasn't plugged in.

No it didnt but at the time I didnt think of it and walked away leaving it on charge. And also I didnt even know anything sds . Did you try leaving your battery out overnight or use another battery? You called call in to any mobile phone shop and maybe ask them to see if uou can at least tey theirs
Sent from my GT-N7100 using xda app-developers app

All the sign and symptoms indicating its sudden death.
- Have you updated to 4.1.2 which is believed to be patch for SDS?
-Can you reboot to recovery/download mode?

Well, I did try just plugging it in for a few hours, when I went back to it the battery was cold and nothing happened.
I do have 2 original batteries, so I've been trying everything with both of them.
It just seems like the SDS because of the proximity sensor lighting up.
Right now it's unplugged and without a battery, just in case the capacitors need to discharge or something.
I guess I'll try again tonight!
It's really complicated with the GT-N7100 being an international phone, I can't register it on Samsung for warranty, so I've been trying to talk to Newegg and haven't been successful with them so far.
Thanks for the replies guys.

dr.ketan said:
All the sign and symptoms indicating its sudden death.
- Have you updated to 4.1.2 which is believed to be patch for SDS?
-Can you reboot to recovery/download mode?
Click to expand...
Click to collapse
The crazy part is that I think the phone was asking me to update firmware, but I didn't have time to update it before it died like this... what luck, right?
For the download mode, it never reacts while plugged in other than the sensor, so even if I hold the key combinations, it doesn't seem to react. I'll try again more thoroughly tonight.

You didn't update that's prove you were not on latest rom which have fixed sds, really bad luck otherwise it could have took 10min on good network.
Anyway Goodluck for replacement.
Sent from my GT-N7100 using xda premium

Endracion said:
Hey guys,
From what I've read, this seems to happen to a lot of different phones, but not out of the blue and I didn't find anything on the Note 2, so I'm wondering if it's the same issue and if my only hope is to get a replacement. It seems to be dead at the moment.
Before going to bed, I charged my phone to about 90% and then unplugged it and left it on my desk.
This morning when I woke up, it was off, which was kind of odd, since there's no way it would fully discharge over night. I tried turning it on, plugging it to charge, swapping out the battery for another original one I purchased directly from Samsung, trying other chargers, even the PC and different USB cables, all to no avail.
The only thing I noticed was that the proximity sensor seems to flash every 5-10 seconds, and I'm not sure what that would mean, other than the fact that it's getting some power somehow so that it can light up.
For the time being, I removed the battery and left it like that while I'm at work.
The phone is running the stock ROM for the GT-N7100, nothing was ever modified, it's not rooted or anything.
I know there was a firmware update pop-up on it at some point, but I hadn't installed it.
Any clues guys? I know there's some really knowledgeable people here, so I'm hoping someone might have an idea!
Thanks for the help and sorry for the text!
Click to expand...
Click to collapse
Have you tried hard reset, or soft reset. and if you cant get into recovery then sorry buddy :/ it seems like the SDS bug.
The proximity sensor light indicated the system is booting up but if no system boots up then you should send it back to samsung for repair.
Mine should be arriving tomorrow with an engineer's report. I will fill you guys in on what the service centre says.

soljakid said:
Have you tried hard reset, or soft reset. and if you cant get into recovery then sorry buddy :/ it seems like the SDS bug.
The proximity sensor light indicated the system is booting up but if no system boots up then you should send it back to samsung for repair.
Mine should be arriving tomorrow with an engineer's report. I will fill you guys in on what the service centre says.
Click to expand...
Click to collapse
It seems to indeed be the SDS, and I can't reset it or anything since it won't boot up, nor can it go into download mode.
Biggest problem is that seeing as it's a GT-N7100, after calling Samsung; they're telling me it's an international phone and that it can't be serviced in the US or Canada, so I'm basically stuck with a $700 paper weight... this majorly blows. I wish there was someone higher up at Samsung I could speak to, since this is just an extremely bad experience with the product...

Endracion said:
It seems to indeed be the SDS, and I can't reset it or anything since it won't boot up, nor can it go into download mode.
Biggest problem is that seeing as it's a GT-N7100, after calling Samsung; they're telling me it's an international phone and that it can't be serviced in the US or Canada, so I'm basically stuck with a $700 paper weight... this majorly blows. I wish there was someone higher up at Samsung I could speak to, since this is just an extremely bad experience with the product...
Click to expand...
Click to collapse
Dude that sucks hard! I can try and get management number of the people in the uk of you like?

soljakid said:
Dude that sucks hard! I can try and get management number of the people in the uk of you like?
Click to expand...
Click to collapse
I would definitely appreciate any help! You think this would help? I know phones don't exactly carry international warranty, but if I could send it there for replacement or something; that's already a step forward.
I do believe that since Samsung knows of this problem, they should offer outright replacements for anyone suffering of this issue though - because it's literally putting a faulty product on the market; there should be something we can do about this.
Appreciate it, once again!

soljakid said:
Dude that sucks hard! I can try and get management number of the people in the uk of you like?
Click to expand...
Click to collapse
Would you be able to tell us about your engineer's report?

[HELP] My Note 2 just died ! by it's self ....

I've searched and read about this SDS thing ,and i think my phone just had one :crying:
basically it was lying on the table for a few minutes , then i picked it up and tried to start the screen, but nothing happens !
battery removed , charging , sim/sdcard removed ,recovery/download mode didtn show up neither , ALL DID NOT WORK !!!!
its just stuck and wont start up. and it shows that blinking red light near proximity sensor.....
it was perfectly fine a few moments ago but now its just dead.. i am non rooted on stock 4.1.1.
any suggestions please, really in need of the community help now ? :crying:
i've read that in 4.1.2 they fixed it , so is there a way to flash thru Odin while its dead already??
thx

If it IS an SDS, then it's dead and gone. No way to recover. You'll have to send it back to Samsung and they're replace the motherboard. Take your SD card out before you send it.

How do i know it is an SDS ? is there any other specific symptoms that i missed out ?
so far ,nothing worked trying to revive it , black screen with that flashing red (proximity sensor) when i press power or plug it in :crying: .

Did you root it? If not, you can send it back to Samsung for repairs.

Which custom ROM / Kernel were u using before it died ?
Did the kernel has fix for SDS ? like Perseus kernel ?
The recovery your using has SDS fix too ? tell us these details with versions included.

Goodm7sn said:
How do i know it is an SDS ? is there any other specific symptoms that i missed out ?
so far ,nothing worked trying to revive it , black screen with that flashing red (proximity sensor) when i press power or plug it in :crying: .
Click to expand...
Click to collapse
Yup, that's an SDS alright. All of them have the same symptom once dead. Time to call Sammy.

n4naveen said:
Which custom ROM / Kernel were u using before it died ?
Did the kernel has fix for SDS ? like Perseus kernel ?
The recovery your using has SDS fix too ? tell us these details with versions included.
Click to expand...
Click to collapse
He already said he was running stock 4.1.1
Sent from the mighty Note II.

Goodm7sn said:
I've searched and read about this SDS thing ,and i think my phone just had one :crying:
basically it was lying on the table for a few minutes , then i picked it up and tried to start the screen, but nothing happens !
battery removed , charging , sim/sdcard removed ,recovery/download mode didtn show up neither , ALL DID NOT WORK !!!!
its just stuck and wont start up. and it shows that blinking red light near proximity sensor.....
it was perfectly fine a few moments ago but now its just dead.. i am non rooted on stock 4.1.1.
any suggestions please, really in need of the community help now ? :crying:
i've read that in 4.1.2 they fixed it , so is there a way to flash thru Odin while its dead already??
thx
Click to expand...
Click to collapse
i mean this SDS warning was all over the place, im surprised you werent aware that it was highly recommended you upgrade to 4.2.1 or above to avoid this very issue since you seem like an active xda participant.

Goodm7sn said:
I've searched and read about this SDS thing ,and i think my phone just had one :crying:
basically it was lying on the table for a few minutes , then i picked it up and tried to start the screen, but nothing happens !
battery removed , charging , sim/sdcard removed ,recovery/download mode didtn show up neither , ALL DID NOT WORK !!!!
its just stuck and wont start up. and it shows that blinking red light near proximity sensor.....
it was perfectly fine a few moments ago but now its just dead.. i am non rooted on stock 4.1.1.
any suggestions please, really in need of the community help now ? :crying:
i've read that in 4.1.2 they fixed it , so is there a way to flash thru Odin while its dead already??
thx
Click to expand...
Click to collapse
I'm afraid I am on the same boat as you and bad news is they will boot it in download mode and find that the firmware will read 'custom' which means they think you might have rooted the phone and won't repair it free of charge. I am currently looking for ways to deal with them. My case happened in Hong Kong though.....Good Luck to you.

bushako said:
i mean this SDS warning was all over the place, im surprised you werent aware that it was highly recommended you upgrade to 4.2.1 or above to avoid this very issue since you seem like an active xda participant.
Click to expand...
Click to collapse
yeah i am an active participant. but unfortunately, for the past 3 months i was off xda and didnt read or check anything , only if i knew , i truly regret it. bcos updating it wont even take 5 minutes....
the problem is , i made 5 other friends of mine buy Notes 2 !!! now im too scared to tell them all about this ,
very frustrated from Samsung and their stupid software department , cant believe the user have to look after his device bcos they cant get it right. had my Note 1 on the bricking risk due to that emmc bug as well but i took care of it thanks to xda.
jzjman said:
I'm afraid I am on the same boat as you and bad news is they will boot it in download mode and find that the firmware will read 'custom' which means they think you might have rooted the phone and won't repair it free of charge. I am currently looking for ways to deal with them. My case happened in Hong Kong though.....Good Luck to you.
Click to expand...
Click to collapse
how will they find it on "custom"? i've never rooted the device , never felt the need for it, and did that on purpose to keep the warranty.

Goodm7sn said:
yeah i am an active participant. but unfortunately, for the past 3 months i was off xda and didnt read or check anything , only if i knew , i truly regret it. bcos updating it wont even take 5 minutes....
the problem is , i made 5 other friends of mine buy Notes 2 !!! now im too scared to tell them all about this ,
very frustrated from Samsung and their stupid software department , cant believe the user have to look after his device bcos they cant get it right. had my Note 1 on the bricking risk due to that emmc bug as well but i took care of it thanks to xda.
how will they find it on "custom"? i've never rooted the device , never felt the need for it, and did that on purpose to keep the warranty.
Click to expand...
Click to collapse
I think instead of blaming each other for not updating and what not we should be pointing fingers at samsung for their ignorance in this matter. The least you'd expect from them is their acknowledgement of this serious flaw and compensate the customers by offering recalls and updating the phones at the nearest service centers coz not everyone has time or knowledge to do updates and not to mention this is a mandatory update. So many people get turned away from the service center simply because their phones were rooted which has absolutely nothing to do with the cause of SDS to top it up they're still selling the phones off with the old 4.1.1 rom in most places. Just frustrating. Good luck with you getting your issue resolved.
Sent from my GT-N7100 using xda premium

Update :
i got the phone back today from the service center :victory: :laugh: , they repaired it for almost 300$ , fortunately it went under warranty, so i payed nothing (ive never rooted).
they replaced the chip or the motherboard , i dunno what exactly, but still with the emmc checker app i still have that buggy chip !!!!!
i guess im on the safe side now since samsung pushed DMB2 update here in switzerland (4.1.2.) and it came already installed on my repaired phone. however i cant explain the relief (and frustration at Samsung continuous stupidity with high-end devices), since ive been really struggling without my Note 2 (used a cool but very slow nexus one).
thx for the help guys , cheers.

I need help

Owner of international Note 2.
This morning I found my phone dead. I cannot start it either through power button or other combination of buttons. I took out the battery and back in. Through ADB no luck it doesn't even register that I plugged in the phone.
From time to time the first led on the right of the camera blinks (I think it's one of the sensors).
Can anyone through an idea what I can do to recover my phone?
Sent from my Nexus 7 using XDA Premium HD app

daniel_cassian said:
Owner of international Note 2.
This morning I found my phone dead. I cannot start it either through power button or other combination of buttons. I took out the battery and back in. Through ADB no luck it doesn't even register that I plugged in the phone.
From time to time the first led on the right of the camera blinks (I think it's one of the sensors).
Can anyone through an idea what I can do to recover my phone?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
have you rooted your phone ? .. can you go to recovery ? download mode ?

My phone was rooted. I had MIUI on it. I was on the same ROM for 2 weeks, so it can't be the ROM. I cannot access the phone in any way possible

Unfortunately looks like its SDS ( sudden death syndrome ) . Was your phone on 4.1.1 or 4.1.2 firmware? Its supposed that 4.1.2 has sds fix. Anyway if its sds so only option is to replace motherboard.
Sent from my GT-N7100 using xda premium

T511 said:
Unfortunately looks like its SDS ( sudden death syndrome ) . Was your phone on 4.1.1 or 4.1.2 firmware? Its supposed that 4.1.2 has sds fix. Anyway if its sds so only option is to replace motherboard.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Agree with T511.. One of my frns S3 also had SDS n like he mentioned, motherboard had to be changed... if you have warranty n bill they will do it free.. doesnt matter if its rooted.. they cant check either..

It seems so. I've read for the last hour about it. What i don't know is: if i go to service, will they detect i was rooted and on custom rom? If so... can they refuse my service completely (After all SDS is not ROM related) or at least they can service me but with charges (which i presume it will be allot, but after all less then a new phone)?

daniel_cassian said:
It seems so. I've read for the last hour about it. What i don't know is: if i go to service, will they detect i was rooted and on custom rom? If so... can they refuse my service completely (After all SDS is not ROM related) or at least they can service me but with charges (which i presume it will be allot, but after all less then a new phone)?
Click to expand...
Click to collapse
Even they cant access it pal.. so they wont come to know.. just take it to service.. they will surely do it free if its under warranty..
but your data cant be revived.. hope you had a backup of contacts and msgs.. (5 mins'm waiting to post this .. as i've just started postin after a decent learning)

I had everything on my card. Titanium Backup few days ago....so i won't lose anything important. I just hope that the service will do it without arguing. I am under contract to Vodafone since november 2012. But in my country service or service period are words which are still foreign to distributors or sellers in general

Hard Bricked! Help (T999/mobilicity)

I have a 9 month old S3 (T999/Canadian/Mobilicity Variant)
I had a ROM on there since day 2, but recently *this week* had a lot of hard lock ups. I could manage a reboot if I pulled the battery.
I tried 3 diff roms CM10, AOKP, and a recent 4.1.1 (all without apps) all worked but still caused the hard lock requiring a reboot.
It was annoying as you know what, but I was testing diff options wondering if the lockups were the OS/an app/or hardware.
Last night the phone was working on AOKP 4.2.2 while on the charger. I woke up and noticed it was hard locked, so I batt pulled, rebooted and went to sleep.
Now (this morning) it wont boot at all. I thought maybe it was the charger or the battery. I swapped batteries with a different S3, mine still does not boot.
So. What now?
Time for S4 and lose a $600 phone? Time to go to a Samsung or Carrier shop?

Have you tried Odin? Plug it into a computer see if things register if so go further with Odin.
I'd say that and see if it persist while on a stock then don't install your apps, if problem still persist call Samsung or whom ever and see about that. Or get it up and running and if steady put on Craigslist then get s4....
T-Mobile SGS III

mt3g said:
Have you tried Odin? Plug it into a computer see if things register if so go further with Odin.
I'd say that and see if it persist while on a stock then don't install your apps, if problem still persist call Samsung or whom ever and see about that. Or get it up and running and if steady put on Craigslist then get s4....
T-Mobile SGS III
Click to expand...
Click to collapse
It used to be that when connected to PC Device man said: SGH-T999
Now the phone is connected via usb cable, but isnt booted and it says: QHSUSB_DLOAD

AMRivlin said:
It used to be that when connected to PC Device man said: SGH-T999
Now the phone is connected via usb cable, but isnt booted and it says: QHSUSB_DLOAD
Click to expand...
Click to collapse
Google search that piece "QHSUSB_DLOAD" and see what it is. I've never seen that. Install Odin (in the dev section) and see what happens (read that thread) I'm at work on mobile or I'd give you links. Just a little reading and no panicking and you might get out of this alive lol.
T-Mobile SGS III

mt3g said:
Google search that piece "QHSUSB_DLOAD" and see what it is. I've never seen that. Install Odin (in the dev section) and see what happens (read that thread) I'm at work on mobile or I'd give you links. Just a little reading and no panicking and you might get out of this alive lol.
T-Mobile SGS III
Click to expand...
Click to collapse
QHSUSB_DLOAD means your need JTAG. Because it's bricked.

mt3g said:
Google search that piece "QHSUSB_DLOAD" and see what it is. I've never seen that. Install Odin (in the dev section) and see what happens (read that thread) I'm at work on mobile or I'd give you links. Just a little reading and no panicking and you might get out of this alive lol.
T-Mobile SGS III
Click to expand...
Click to collapse
That is found on XDA and the interwebs as a bricked device. it applies to captivate/HTC/s3 others.
I downloaded odin, but I can't get into download mode Power+Home+VDown (Nothing happens)
I didn't flash an incorrect ROM, since my phone was working, it bricked itself over night? Power Surge?

Aerowinder, if I am under warranty, can i take it to my carrier/samsung for repair? I can't get into Download mode.

Call them up and find out. It might be failing/tired internals/hardware... Did you have your phone over clocked at all in the 9 months, just curious?
T-Mobile SGS III

AMRivlin said:
Aerowinder, if I am under warranty, can i take it to my carrier/samsung for repair? I can't get into Download mode.
Click to expand...
Click to collapse
I had the exact same problem and was still under the warranty and they exchanged it. I just told them that I plugged my phone before going to bed and when I woke up I wasn't able to turn it back on.

I actually remember this now. This a bug not common but its here for users on all D2 SIII decices... They've publically admitted it
T-Mobile SGS III

No over clocking.
Jan-April 30th Touchwiz 4.1.1 (Frosty ROM) Lockups Started monday (No Changes)
May 1 AOPK 4.2.2 ROM (Hard Lock/Brick today)
Time to find a receipt

AMRivlin said:
No over clocking.
Jan-April 30th Touchwiz 4.1.1 (Frosty ROM) Lockups Started monday (No Changes)
May 1 AOPK 4.2.2 ROM (Hard Lock/Brick today)
Time to find a receipt
Click to expand...
Click to collapse
Ya I suggest just avoiding the headache of trying to fix, tell them you plugged it in over night to charge and now its completely dead and that its been acting weird for a while before. You should be good.
T-Mobile SGS III

rener78 said:
I had the exact same problem and was still under the warranty and they exchanged it. I just told them that I plugged my phone before going to bed and when I woke up I wasn't able to turn it back on.
Click to expand...
Click to collapse
Not sure how this is going to turn out. The carrier refused to do the warranty, and gave me the # to samsung canada. I went to the Samsung Canada store, where they took the phone and gave me a GNexus (loaner)
So... lets hope they dont see the romming, my triangle should be 0.
If they do figure out my romming and their quote to fix is absurd, I will get HTC1 and repair the S3 on my own time.
I prefer Apple's warranty to be honest.

Does anyone know how much 3rd party Brick repair should cost? In the crap chance Samsung gets me for ROMing

AMRivlin said:
Does anyone know how much 3rd party Brick repair should cost? In the crap chance Samsung gets me for ROMing
Click to expand...
Click to collapse
Mobiletechvideos does it for $60.
http://mobiletechvideos.mybigcommerce.com/
Sent from my SGH-T999 using xda premium

Update:
7 days after submitting for service, the phone came back from a 3rd party repair shop in Burnaby, BC. PBA replaced due to bad BGA (Ball Grid Array)
So I guess they couldn't boot it to see the root.
Working fine. The new phone came back carrier locked, original unlock # worked again.

Da Kine said:
Mobiletechvideos does it for $60.
http://mobiletechvideos.mybigcommerce.com/
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Some kijiji advertisements are charging $49.99 same day repair.

ysr84 said:
Some kijiji advertisements are charging $49.99 same day repair.
Click to expand...
Click to collapse
Managed to get it repaired under warranty.

can u help me out
AMRivlin said:
Managed to get it repaired under warranty.
Click to expand...
Click to collapse
Did you buy the warranty when u bought the phone?
I have the same issue. But not sure where to send the galaxy too?
Please help coz the local stores were not able to help
JBn

Help
AMRivlin said:
I have a 9 month old S3 (T999/Canadian/Mobilicity Variant)
I had a ROM on there since day 2, but recently *this week* had a lot of hard lock ups. I could manage a reboot if I pulled the battery.
I tried 3 diff roms CM10, AOKP, and a recent 4.1.1 (all without apps) all worked but still caused the hard lock requiring a reboot.
It was annoying as you know what, but I was testing diff options wondering if the lockups were the OS/an app/or hardware.
Last night the phone was working on AOKP 4.2.2 while on the charger. I woke up and noticed it was hard locked, so I batt pulled, rebooted and went to sleep.
Now (this morning) it wont boot at all. I thought maybe it was the charger or the battery. I swapped batteries with a different S3, mine still does not boot.
So. What now?
Time for S4 and lose a $600 phone? Time to go to a Samsung or Carrier shop?
Click to expand...
Click to collapse
I Hard Bricked my Samsung Galaxy S3 and if you dont mention anything about rooting they will give you a new one no questions asked. Now if you dont have a warranty or some type of insurance then call samsung and see what you can do about it. i did a warranty exchange and i got a new one. As long as you dont mention brick or root you will be find they will right it down as defective.

[Q] Note bricked / died by itself?

My note is about 6 months old and rooted since I got it. Was using it yesterday at work. A couple house later at home when I pulled it out it was dead.
doesnt boot on power button press
doesnt react to "vol+/menue/power"
doesnt react to "vol-/menue/power"
nothing detected when connecting to the laptop
coneccting to the charger does absolutely nothing
The only sign of life is a red led that weakly blinks every 7-8 seconds.
Are there any options other than taking it in to the service center?
Thanks for any help!

MutantWizard said:
My note is about 6 months old and rooted since I got it. Was using it yesterday at work. A couple house later at home when I pulled it out it was dead.
doesnt boot on power button press
doesnt react to "vol+/menue/power"
doesnt react to "vol-/menue/power"
nothing detected when connecting to the laptop
coneccting to the charger does absolutely nothing
The only sign of life is a red led that weakly blinks every 7-8 seconds.
Are there any options other than taking it in to the service center?
Thanks for any help!
Click to expand...
Click to collapse
Try starting the phone with some other battery. It might be due to battery problem.
Incase it doesn't change anything, then the only way is to send it to service center.

Its SDS . Sudden Death Syndrome . Mostly all phones on 4.1.1 affected this. On 4.1.2 its fixed. You might be on 4.1.1. Only solution - Its motherboard should be replaced.
Sent from my GT-N7100 using xda premium

Thanks guys, its with the service center now!

Could you please tell us on which android version was your note 2?

Delux9364 said:
Could you please tell us on which android version was your note 2?
Click to expand...
Click to collapse
Wish I could be certain but I believe 4.1.1 How can I find out now that it is dead???
In any case the service center just advised that they will replace the motherboard under warranty.

Got my note back with the explanation that the motherboard was replaced.
Only problem is that its now back on the Saudi Arabian ROM and will have to go through the whole flashing and rooting and................. but at least its alive even though Oding doesnt reconize it in download mode so will have some research to do.

Mine just got the similar symptom yesterday, but it even doesn't have weekly led blinking.

MutantWizard said:
Got my note back with the explanation that the motherboard was replaced.
Only problem is that its now back on the Saudi Arabian ROM and will have to go through the whole flashing and rooting and................. but at least its alive even though Oding doesnt reconize it in download mode so will have some research to do.
Click to expand...
Click to collapse
Did u chk with eMMC brickbug app for version?

jdomadia said:
Did u chk with eMMC brickbug app for version?
Click to expand...
Click to collapse
My Note 2 also was succumubed to the same symptoms as your's and it's mother board also got replaced.I checked it then eMMC brick apk and it shows insane chip.The only thing we have to do now is to take precaution to be in the latest firm ware and recovery which is SDS patched.Luckily the latest stock firm wares and kernels are SDS patched.

yes checked the returned note and still have the insane chip and 4.1.1
but I have another bigger problem. the returned note with the new motherboard is not detected by Odin in download mode. I intended to flash a non Arabic pre-rooted ROM but no luck. for a week now researching to find a solution but have not managed it yet.