My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
I wish you a Good luck then.
jeanclaudevandamme said:
My Note 2 has just died It was getting surprisingly laggy at odd moments in the past week, but I didn't think anything was wrong. I was updating a lot of applications one after another tonight (music was playing but it was jumpy, i think because apps were updating so i stopped music) and people were messaging me on the facebook app so I could see the notification light flash green. I was busy on my laptop, so I ignored the phone about 10 mins.
The green light kept flashing, but the screen wouldn't turn on when i pressed home or power key. so i took the battery out from the back and reinserted it. It wouldn't switch on at all, no SGS Note 2, no Samsung logo. nothing at all except a little red light flashing where the infrared light is everytime i tried to turn it on.
I tried connecting it to my computer. nothing happened. recovery mode bootup also failed. I tried charging the phone, even though the battery wasn't empty, still wouldn't switch on during charger plugged in or pulled out. Took out SD/Sim, no effect. A new battery didn't help. The phone doesn't charge either, the charger makes a funny electrical whining noise and the infrared red light flashes every so often.
It's basically dead. What can I do? The phone is also rooted, I can't remember how (think it's original chainfire root? i got my phone last oct). Will Samsung be able to switch on my phone and discover it's rooted? Also I read somewhere that legally speaking if rooting didn't cause the failure, you're still covered by EU law?
I am in the UK, bought Note 2 off a 3rd party reseller (Buymobilephones) who provided a handset, and T-Mobile for the contract.
Thanks
Click to expand...
Click to collapse
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
SacGuru said:
How long ago did you buy the phone?
If you were rooted, were you on stock rom?
If yes, than which build were you on, do you remember?
I have heard of phones dying from sds, were you on an older rom. If that is the case, and if you have hard bricked your phone, AND if you are under warranty you need not fear...the guys at samsung wouldn't be able to open your phone either to check whether its rooted or not, you are covered. Your phone would require a motherboard rwplacement 8n that case. I hope you had backups.
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Click to expand...
Click to collapse
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.
jeanclaudevandamme said:
I bought it at end of last october, 1st gen/batch of Note 2s to hit the UK (IMEI starts with 354.....
I was rooted. The first auto-root Chainfire method via Odin.
Stock samsung rom. Very earliest versions of software.
I basically bought the phone last year when it first came out, rooted it as soon as possible and then did nothing else except enjoying my phone and install new apps. Whatever people were rooting/flashing/roms/kernels etc at the end of last october when the note 2 first came out in the uk is what I would have been on. Never updated since.
I might sound a bit stupid, but does a motherboard change means you lose everything in internal storage? ie photos, texts, contacts etc. I have no backups of anything. my fault I know. And Samsung wont' detect root after motherboard has been changed?
When you say "hardbricked", do you just mean it wont' physically and electrically turn on? Because i didn't interrupt rooting/flashing etc.
I googled SDS for the Note 2. Seems there is an issue I can't think how else my phone would just die.
Click to expand...
Click to collapse
I think we know the cause now, its sds. Only roms and kernels which have been developed after January 2013 are free of this problem. As you had rooted very early you would not have recieved stock updates from samsung. And as you had not flashed anything new, the rom/kernel you used had the sds problem. Had you recieved stock updates or had you flashed any latest rom your device would most probably be working.
Now the good news is, as I said, samsung has no way of learning whether your phone was rooted or not. A soft brick is when your phone is in a bootloop. A hardbrick means it wont't turn on, won't do anything at all. Your phone is hardbricked in a way. So a samsung engineer would be as powerless to turn your phone on in this condition as you are. And thus, you would be under warranty.
The bad news is, yes, all the data on your internal storage is gone. The phone you would be provided would be a new factory reset model altogether. That is of course, if the problem is sds, as it seems right now. Even if the problem is different, something smaller, a factory reset is what you will get in all probability, so no chance of saving the data.
I am really sorry for your data, and I know it doesn't help when I play Captain Hindsight, but you should have made a titanium and nandroid backup at the very least. Do that for your next phone regularly. It is the most useful aspect of rooting your phone if you ask me.
Of course, I could be wrong here. The problem could be something smaller. I suggest you throw this problem @dr.ketan on this thread
http://forum.xda-developers.com/showthread.php?t=1896696
He knows a lot more than I do and can confirm this.
Also, do press thanks if I helped
Sent from my GT-N7100 or the Nexus 10, heaven knows.
Those who help noobs go to heaven. True story.
Related
I was using the phone today and the screen suddenly locked up on me. It wouldn't respond to any button presses so I just did a battery pull to reset it. However, the phone won't turn back on now. It doesn't do anything, even when plugged into the charger, the phone doesn't even indicate that it's charging or anything at all. It's like it has been completely bricked.
It was completely stock, never unlocked it or rooted and never installed any custom rom or anything of that nature. I've only had the phone for a couple of months and I'm completely baffled as to what could have happened. It certainly wasn't anything that I did.
Any ideas? Or does anyone have any experience with this type of thing happening to their phone?
So I've left the battery out for over 30 minutes and it still won't turn on. I have an extended battery and the regulary battery that came with the phone and it won't turn on with either battery.
I have also tried the volume down and power button method and that doesn't do anything at all either.
Plugging the phone into the computer with the USB cable also does nothing.
How long have you had the phone. Did you buy it from a store?
.....Clones & Drones.....
Mine did the exact same thing! It was realy weird, however all i did was keep the power button pressed and it rebooted fine.
Sent from my Galaxy Nexus using xda premium
ptmr3 said:
How long have you had the phone. Did you buy it from a store?
.....Clones & Drones.....
Click to expand...
Click to collapse
I got the phone when it was released and I ordered it online right from Verizon's website.
I hope that you have the warranty from the carrier!
gulmat said:
Mine did the exact same thing! It was realy weird, however all i did was keep the power button pressed and it rebooted fine.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I wish it was that simple for me.. I held the power button down for over a minute and still, nothing happened. This is really frustrating.
!!!!!!!+111111
evolishesh said:
I hope that you have the warranty from the carrier!
Click to expand...
Click to collapse
.....Clones & Drones.....
ptmr3 said:
!!!!!!!+111111
.....Clones & Drones.....
Click to expand...
Click to collapse
I'm not sure about that one. I know I don't have insurance thru verizon but isn't there a manufacturer warranty? Like I could get a refurb from verizon instead of a brand new one?
I've never had a smartphone just stop working for no reason at all and I was never really into modding them so I thought I was safe. I guess I was wrong.
Really disappointed in Samsung right now. This is my first nexus device, not sure if I'll get another.. That's totally lame to have a crap product that just stops working for no reason. This is an unmodded phone, completely stock, never been dropped or anything of that sort. The only thing that I did was swap the regular battery out for the extended version.
russ4h said:
I'm not sure about that one. I know I don't have insurance thru verizon but isn't there a manufacturer warranty? Like I could get a refurb from verizon instead of a brand new one?
I've never had a smartphone just stop working for no reason at all and I was never really into modding them so I thought I was safe. I guess I was wrong.
Really disappointed in Samsung right now. This is my first nexus device, not sure if I'll get another.. That's totally lame to have a crap product that just stops working for no reason. This is an unmodded phone, completely stock, never been dropped or anything of that sort. The only thing that I did was swap the regular battery out for the extended version.
Click to expand...
Click to collapse
I'd definitely go to Verizon with this. Most definitely manufacturer defect.
Hold down volume up and volume down and the power button. Does it boot into fast boot? Id say if it doesn't do anything then go ahead and call your carrier because its a faulty unit. You can also try plugging it in without a battery and then Inserting the battery. That also saw sends a power up signal to the device. Though I don't know if this trick works on a nexus three. This was an old trick to "jump start" a nexus one that had a faulty power button. But aside from all this, it sounds to me like you've got a faulty unit whether you get it running or not. Probably just need to swap it , sounds like something went pop.
Sent from my Galaxy Nexus using Tapatalk
You should be able to get a refurbished phone.its probably just a manufacturer defect.
Sent from my Galaxy Nexus using Tapatalk
android01 said:
Hold down volume up and volume down and the power button. Does it boot into fast boot? Id say if it doesn't do anything then go ahead and call your carrier because its a faulty unit. You can also try plugging it in without a battery and then Inserting the battery. That also saw sends a power up signal to the device. Though I don't know if this trick works on a nexus three. This was an old trick to "jump start" a nexus one that had a faulty power button. But aside from all this, it sounds to me like you've got a faulty unit whether you get it running or not. Probably just need to swap it , sounds like something went pop.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Thanks for the tips, I tried the volume up, volume down, and power button method just now and it doesn't do anything. I Also just tried plugging it in and then putting the battery in and nothing as well.
The thing is, I don't have insurance thru Verizon (i.e. the $5 a month thing). Would going to them even benefit me at all? Do you know if they would offer a refurb or something?
The phone has a 1 year warranty on it. You shouldn't have to pay anything but you might just get a refurbished replacement.
I think I had the same thing happen to me a few days ago. However, I have the GSM version that I bought from amazon (thru a third party seller), so no warranty. Yeah, I know. Smart. Also, in my case, I unlocked the bootloader so I could flash the official yakju so I would get updates faster from google. Despite some lagginess with 4.0.2, it had been working great for a month+.
When mine crashed, all I did was press the back button and the screen went crazy and froze up, then started glitching and made a buzzing sound. I pulled the battery and tried a reboot. The Google logo would glitch and "ghost" and then the animation would start, but it was slower and choppy. After a few seconds, it froze and the screen was all low-rez looking and I could see what I can only describe as strange pixelation or scan lines (with a few of them moving from the top of the screen down to the bottom in a continuous loop). The only way to get it to stop was another battery pull.
I tried to use fastboot to get back in and reflash to the original firmware, but I kept getting a usb error (didn't have that when I first unlocked the bootloader using a mac, so not sure what the problem was). Now, the phone won't get passed the Google logo and just sits there for 30+ minutes without making any progress (that I can see). I keep trying to get back into the bootloader using fastboot, but now it won't even do that.
I've contacted Samsung/UK (as that's where mine originated), but don't think I will be getting any help based on their initial response. And, since my bootloader is unlocked, that probably voided the warranty anyway. I have no idea what happened, but it seems like some sort of combination of hardware/software problem. So, basically I'm screwed and out $700.
russ4h said:
Thanks for the tips, I tried the volume up, volume down, and power button method just now and it doesn't do anything. I Also just tried plugging it in and then putting the battery in and nothing as well.
The thing is, I don't have insurance thru Verizon (i.e. the $5 a month thing). Would going to them even benefit me at all? Do you know if they would offer a refurb or something?
Click to expand...
Click to collapse
I'd say go contact Verizon and see what they say. If they can't help you out then you gotta contact Samsung and I believe (if my memory serves me right) all their products have a one year warrenty from the day the phone was used. So you should see what they have to say.
Similar thing happened to me, it rebooted itself, as it has been doing quite a bit of lately, and then wouldnt turn on no matter what I did.
Eventually just help the POWER and VOL DOWN button together to reboot, and it worked fine again. I'm completely stock wtf.
tandp74 said:
I think I had the same thing happen to me a few days ago. However, I have the GSM version that I bought from amazon (thru a third party seller), so no warranty. Yeah, I know. Smart. Also, in my case, I unlocked the bootloader so I could flash the official yakju so I would get updates faster from google. Despite some lagginess with 4.0.2, it had been working great for a month+.
When mine crashed, all I did was press the back button and the screen went crazy and froze up, then started glitching and made a buzzing sound. I pulled the battery and tried a reboot. The Google logo would glitch and "ghost" and then the animation would start, but it was slower and choppy. After a few seconds, it froze and the screen was all low-rez looking and I could see what I can only describe as strange pixelation or scan lines (with a few of them moving from the top of the screen down to the bottom in a continuous loop). The only way to get it to stop was another battery pull.
I tried to use fastboot to get back in and reflash to the original firmware, but I kept getting a usb error (didn't have that when I first unlocked the bootloader using a mac, so not sure what the problem was). Now, the phone won't get passed the Google logo and just sits there for 30+ minutes without making any progress (that I can see). I keep trying to get back into the bootloader using fastboot, but now it won't even do that.
I've contacted Samsung/UK (as that's where mine originated), but don't think I will be getting any help based on their initial response. And, since my bootloader is unlocked, that probably voided the warranty anyway. I have no idea what happened, but it seems like some sort of combination of hardware/software problem. So, basically I'm screwed and out $700.
Click to expand...
Click to collapse
That's awful man. I've been reading more and more about random reboots happening with this phone and what not.. I just don't know what to think right now, I thought this was supposed to this beast of a phone and now after only a couple of months, it has completely stopped working for no apparent reason at all. Pretty lame, and this has definitely never happened to me before as I always take care of my phones. I just figured that if something were to happen to this phone, it would be from my own doing, just as it has been with every other phone that I've ever owned (ie from modding, from a drop, etc.). Samsung gets a thumbs down from me, I paid a lot of money to get this phone and now I'm going to be stuck with a refurb because they have put out a crap product.
As for you, I wouldn't even tell Samsung that you unlocked it. They probably won't be able to tell if you did or not since the phone won't boot properly. They should offer you a refurb, so you'll be in the same boat as me. I went into Verizon today and that's the best that they could do. I have to wait til Monday for it to come in the mail. I'm stuck without a phone til Monday.
volsey said:
Similar thing happened to me, it rebooted itself, as it has been doing quite a bit of lately, and then wouldnt turn on no matter what I did.
Eventually just help the POWER and VOL DOWN button together to reboot, and it worked fine again. I'm completely stock wtf.
Click to expand...
Click to collapse
Yeah, it's looking like this phone has been giving many people similar problems. Samsung must have let a bad batch slip out or something. I was completely stock as well, no unlock, no root, no custom rom, just a plain old basic user here and mine took a dump on me.
Mine does this about every other day and I have to pull the battery and restart, sorry to hear yours won't reboot. Ouch
My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!
goeundiane said:
My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!
Click to expand...
Click to collapse
does it respond to plugging in to charge? im not 100% but if its responding at all when it gets plugged in its not hardbricked only softbricked so go from there. when i hardbricked my first s2 due to a corrupt kernel file i flashed it would not react to anything at all. complete dead weight
U stated that when u plugged it into ur computer u got a ding then says driver device not found. Sounds to me that ur not in a hard birck when I bricked mine I didn't even get that. Check out the link it well help.
http://galaxys2root.com/t-mobile-ga...ck-t-mobile-galaxy-s2-sgh-t989-android-2-3-6/
on my t989 enjoying sith3, thank u to all
Thanks for everyone's help. I ended up sending in my phone to a Samsung service center (while I was in Korea). They confirmed that it is a hardbrick. They opened it up and said it looked like there was a short and it fried the motherboard. They couldn't tell me what caused the short--they said maybe some water got into the phone through the charging port, but I know that isn't true... I had it plugged into an old power strip and maybe that's why? :crying:
Either way, I was told my only option was to get the motherboard replaced which would be $200. I told them no thanks and that I'd just get a replacement phone from T-mobile for $20.
sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
PJcastaldo said:
sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I know my story sounds unlikely, but it's the truth. Isn't this forum around to help fellow users? I have no reason to lie here. I actually take very good care of my phone and (after almost losing a laptop to a water spill) am extremely cautious about liquids around my electronic devices. You don't have to believe me since I'll get my phone replaced regardless. I just thought I would share the information in case someone else ends up facing the same problem.
Even now, the only cause I can come up with still is the old power strip frying the motherboard. *shrug* I would love to hear any other explanations.
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?
Okay, I originally got this phone as an upgrade over my HTC Inspire in July. It worked great, minus a few random reboots every once in a while (if I left it in my pocket for a long time or if it was really hot in my car it would do this, but that was it). Then, about a month or two ago, I rooted it and installed a custom ROM. I noticed that a bunch of my files were missing from my internal SD card, but I wasn't too worried about it. Then my phone started acting really weird and got stuck in a bootloop. I was able to boot into recovery, but I ended up using the LG Flash Tool and went back to bone stock. Still had the issue, except I noticed that my signal would drop, and then it'd get stuck in the bootloop. So, I contacted AT&T warranty and they sent me a replacement. Now the same thing is happening to this one. It gets warm, loses cell signal, then reboots, sometimes a bootloop. This phone hasn't been rooted at all, it's been left stock. So I contacted AT&T and the guy in warranty said he thinks it's the battery, but he didn't have any in stock so he couldn't send a replacement. So I was thinking it was the battery and called LG after it seemed to get worse. They told me that they could replace the battery free of charge if I send in the one I'm using first. Since this is my only way of communication, I contacted AT&T again, and they're sending me another replacement. (Said if this one screw up too, they'll give me a different phone all together). The guy had me download some AT&T remote support app and he looked at the battery health and said it's reading fine, and that because it's reading fine, he didn't think it was the battery. :|
Here's the weird thing, about two weeks ago, it went into a bootloop. I took out the battery for a minute an tried to put it back in. Nothing. I plugged the charger into it and it basically told me that it didn't have enough juice to power on. (battery was at ~40%). So I took the battery back out and tried again. This time it came on.
Then last friday, I was jammin out to music while I was working, it would reboot when I unlocked the phone. (battery was in upper 90%'s). I plugged the charger in while it did this and everything came up as it should. But after taking it off the charger and trying to do more work, it happened again and again.
Like I said, this phone is straight from AT&T and has not had anything flashed onto it by me, hell I never even disabled all the AT&T bloat this time. I've tried a hard reset, and it didn't help. Does anybody know what would be the cause of my problems? I really like this phone and really hope I can get this figured out.
EDIT: Forgot to mention, the phone still has its IMEI number and it has the value pack update.
Got the second replacement in the mail today. It hasn't screwed up yet, but only time will tell.
-SeCra- said:
Got the second replacement in the mail today. It hasn't screwed up yet, but only time will tell.
Click to expand...
Click to collapse
Wow hope this works for you. I just got 3 Optimus G Pro's on 12/30/13 and all 3 of them to date have not had any issues. 2 black and 1 white. 2 which are running stock. 1 stock which has had a bunch of the bloatware yanked (that we could get off of it). 1 stock which has had nothing pulled, everything left the way it is. And the 3rd one (which is the one I use) which I rooted to CyanFox 4.4.2 and later to CM11 4.4.2 Nightly and haven't had any issues like the ones you've explained.
Good luck though hopefully your issue is gone. Seems like a nice reliable phone (minus LG not wanting to support it furthermore ).
mattverg89 said:
Wow hope this works for you. I just got 3 Optimus G Pro's on 12/30/13 and all 3 of them to date have not had any issues. 2 black and 1 white. 2 which are running stock. 1 stock which has had a bunch of the bloatware yanked (that we could get off of it). 1 stock which has had nothing pulled, everything left the way it is. And the 3rd one (which is the one I use) which I rooted to CyanFox 4.4.2 and later to CM11 4.4.2 Nightly and haven't had any issues like the ones you've explained.
Good luck though hopefully your issue is gone. Seems like a nice reliable phone (minus LG not wanting to support it furthermore ).
Click to expand...
Click to collapse
I really hope my issues with this phone are done too, I really love this phone. If I don't have any issues, it's going to get rooted and updated to KitKat. Otherwise, I'll try to get AT&T to give me a MotoX or a HTC One.
-SeCra- said:
I really hope my issues with this phone are done too, I really love this phone. If I don't have any issues, it's going to get rooted and updated to KitKat. Otherwise, I'll try to get AT&T to give me a MotoX or a HTC One.
Click to expand...
Click to collapse
Yeah I like this phone with KitKat. Looks like a larger Nexus 5
Only problems i'm having with CM11:
1. ATT Visual Voicemail will install but upon playing voicemails program will freeze and crash
2. Tried Google Voice however you can only hear the voicemails through speakerphone, headsets, or bluetooth. Voicemails will no play through earpiece.
3. CM11 doesn't have Screen Recorder yet (Which CyanFox did although CM11 is still fairly fresh).
4. I would like to have the LG Camera app back! Dual video recording and some of those other features are gone with the android stock Camera app. Need to look into porting that back over to KitKat (if I can).
That's bout it though...
mattverg89 said:
Yeah I like this phone with KitKat. Looks like a larger Nexus 5
Only problems i'm having with CM11:
1. ATT Visual Voicemail will install but upon playing voicemails program will freeze and crash
2. Tried Google Voice however you can only hear the voicemails through speakerphone, headsets, or bluetooth. Voicemails will no play through earpiece.
3. CM11 doesn't have Screen Recorder yet (Which CyanFox did although CM11 is still fairly fresh).
4. I would like to have the LG Camera app back! Dual video recording and some of those other features are gone with the android stock Camera app. Need to look into porting that back over to KitKat (if I can).
That's bout it though...
Click to expand...
Click to collapse
Haha yeah, this phone is beautiful with stock Android, I just end up missing certain touches that LG puts in their overlay.
BTW, this phone is doing the same thing as before. I strongly believe it's the battery b/c when it went into a bootloop, I took out the battery it was warm, so I put it in front of the AC for a minute to cool it down and it's been working fine since. So, I'm going to call AT&T and see if they will send me a battery, and if they can't, I'm going to have to send this one in to LG and be without a phone for a week...:'(
UPDATE: AT&T told me "since we have tried everything else-hard resets, replacement phones- and nothing worked, we will send you a battery since it's the only thing that has stayed persistent through this ordeal. We just got some in stock and are sending one your way. If the problem continues to persist, we will replace the phone again." IT'S ABOUT TIME!!!
Just curious, but what if I continue having this issue after I get my new battery? Should I try a similar mah zero lemon battery or just have att give me a different phone altogether?
Sent from my LG-E980 using xda app-developers app
-SeCra- said:
Just curious, but what if I continue having this issue after I get my new battery? Should I try a similar mah zero lemon battery or just have att give me a different phone altogether?
Sent from my LG-E980 using xda app-developers app
Click to expand...
Click to collapse
i think there is an issue with the battery and whatever cable you use to charge the phone.I had to Lge980 when I used a thin cable I have in my room sometimes it did not charged at all and or shut down itself even when the battery had half charge ,sometimes it showed full charged but if I plugged the phone to a thicker cable connected using the oem charger or a usb 3.0 port at my laptop it showed the real charge level at 1/4 charge.I myself could't do anything since I got the phone second hand but as long as I used thick cable connected to a oem charger usb 3.0 or eben 2.0 I had no had any issues.
how'd it go?
-SeCra- said:
Haha yeah, this phone is beautiful with stock Android, I just end up missing certain touches that LG puts in their overlay.
BTW, this phone is doing the same thing as before. I strongly believe it's the battery b/c when it went into a bootloop, I took out the battery it was warm, so I put it in front of the AC for a minute to cool it down and it's been working fine since. So, I'm going to call AT&T and see if they will send me a battery, and if they can't, I'm going to have to send this one in to LG and be without a phone for a week...:'(
UPDATE: AT&T told me "since we have tried everything else-hard resets, replacement phones- and nothing worked, we will send you a battery since it's the only thing that has stayed persistent through this ordeal. We just got some in stock and are sending one your way. If the problem continues to persist, we will replace the phone again." IT'S ABOUT TIME!!!
Click to expand...
Click to collapse
I've had the exact same problem with my E980 and the refurb they sent me. Contemplating a battery replacement now. Did a new battery fix your boot loops?
-SeCra- said:
Okay, I originally got this phone as an upgrade over my HTC Inspire in July. It worked great, minus a few random reboots every once in a while (if I left it in my pocket for a long time or if it was really hot in my car it would do this, but that was it). Then, about a month or two ago, I rooted it and installed a custom ROM. I noticed that a bunch of my files were missing from my internal SD card, but I wasn't too worried about it. Then my phone started acting really weird and got stuck in a bootloop. I was able to boot into recovery, but I ended up using the LG Flash Tool and went back to bone stock. Still had the issue, except I noticed that my signal would drop, and then it'd get stuck in the bootloop. So, I contacted AT&T warranty and they sent me a replacement. Now the same thing is happening to this one. It gets warm, loses cell signal, then reboots, sometimes a bootloop. This phone hasn't been rooted at all, it's been left stock. So I contacted AT&T and the guy in warranty said he thinks it's the battery, but he didn't have any in stock so he couldn't send a replacement. So I was thinking it was the battery and called LG after it seemed to get worse. They told me that they could replace the battery free of charge if I send in the one I'm using first. Since this is my only way of communication, I contacted AT&T again, and they're sending me another replacement. (Said if this one screw up too, they'll give me a different phone all together). The guy had me download some AT&T remote support app and he looked at the battery health and said it's reading fine, and that because it's reading fine, he didn't think it was the battery. :|
Here's the weird thing, about two weeks ago, it went into a bootloop. I took out the battery for a minute an tried to put it back in. Nothing. I plugged the charger into it and it basically told me that it didn't have enough juice to power on. (battery was at ~40%). So I took the battery back out and tried again. This time it came on.
Then last friday, I was jammin out to music while I was working, it would reboot when I unlocked the phone. (battery was in upper 90%'s). I plugged the charger in while it did this and everything came up as it should. But after taking it off the charger and trying to do more work, it happened again and again.
Like I said, this phone is straight from AT&T and has not had anything flashed onto it by me, hell I never even disabled all the AT&T bloat this time. I've tried a hard reset, and it didn't help. Does anybody know what would be the cause of my problems? I really like this phone and really hope I can get this figured out.
EDIT: Forgot to mention, the phone still has its IMEI number and it has the value pack update.
Click to expand...
Click to collapse
If you want to stay on stock i recommend going to jellybean TOT 10k and rooting and installing a custom recovery back up the rom, and flash hkfriends kernel, and see what happens if you raise or lower your phones voltage, that might be the problem with it rebooting.
THE NEW BATTERY SOLVED THE ISSUE, BUT ONLY FOR A SHORT TIME. I upgraded to an HTC One M8 since, and haven't had hardly any problems with it, aside from the death star's BS
-SeCra- said:
THE NEW BATTERY SOLVED THE ISSUE, BUT ONLY FOR A SHORT TIME. I upgraded to an HTC One M8 since, and haven't had hardly any problems with it, aside from the death star's BS
Click to expand...
Click to collapse
Thanks for the response. I talked to the techs at an AT&T direct service center and they told me it's a common problem with the Optimus Pro. I'm on my third one in 8 months now and this one started randomly powering off within 15 minutes of when I took it out of the box three days ago.
zhirrad said:
Thanks for the response. I talked to the techs at an AT&T direct service center and they told me it's a common problem with the Optimus Pro. I'm on my third one in 8 months now and this one started randomly powering off within 15 minutes of when I took it out of the box three days ago.
Click to expand...
Click to collapse
Yeah. My issue was the battery for sure. Make them replace the battery and it should temp solve the issue
From what I read on the first e980 i had these phone tend to have a hardware problem where the power button is creating the same issues as OP. Some refurbished e980s have the hardware problem solved.
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
kiwi32 said:
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
Click to expand...
Click to collapse
is it possible that the LCD went bad?? when you plug it into charge does it react (lcd or vibrate?) I would also suggest trying out a known battery. could be that if it is the original battery that it is so dead that I got "spikey" and finaly just died.
hope it is that simple
kiwi32 said:
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
Click to expand...
Click to collapse
If she wasn't trying to flash anything, doesn't sound like a brick which, to my understanding, results from software failures. The procedure posted in the thread applies when you are trying to recover from a brick caused by firmware failure from attempting to flash the wrong bootloader so I'd be doubtful if it would help you here. This could be a specific hardware failure which is not unheard of with equipment like this. Also sounds like it gave warning of the gradual failure. When you plug it into a charging outlet, does it show any sign of life - a light or vibration? If it's an LCD failure, it probably wouldn't affect charging or recognition by your PC. If there is no sign of life at all even with different batteries, you may want to try a professional repair service as I presume exercising the warranty is not an option in view of the firmware history.
Hi,
Thanks for the replies.
I did try different batteries. The phone does not vibrate or react at all even when plugged in which does not suggest an LCD failure.
I guess you are right,it must be a hardware failure. I'm quite suprised,I thought these phones were well buit and resistant.Oh well.
She's getting a Nexus 5 now.
Thanks for the help !