Ok guys, I've read all of the forum threads for this issue but have found no real answers yet.
Two days ago, I woke up one morning and my phone was dead as f**k! It had maybe 20% charge to it before connected it to the charger and hitting the sack.
Well, I wake up and like I said, the phone is completely dead. The weird thing is that when I try to plug my charger back into it (after removing it) it will not charge. I tried a different cable and it works...BUT, the orange LED that comes on when it is charging blinks rather than remaining solid.
I wake up this morning and same BS. This has only happened these past two days and I have done NOTHING to my phone to cause such odd behavior.
I know someone on here knows why this is happening...
Any advice or opinions would be greatly appreciated as always.
Thanks in advance!
PAinguIN
Is your charge port loose...if itisit might not be making a connection
Sent from my SYNERGIZED **EVO 4G** (Screw 3D!)
Let it stay charged, when it is super drained it will blink, but after a few minutes it should turn solid, then you can turn it on.
Bad usb port.
Sent from my PC36100 using XDA Premium App
Something is killing my battery over night...
Thanks for the responses guys! I have two HTC AC USB adapters and two HTC charge cables. They both work fine from my testing. But something is definitely drinking more juice from my battery than it can trickle charge at night for some reason.
I downloaded System Monitor or something like that, in an effort to see if I could pinpoint what may be hogging all of my batteries power.
But as of right now, it is charging just fine and working just fine... I did download Google+ the other day because I received an invite, I have like 100 invites if anyone wants one by the way, and that's when all of this started. I also downloaded AdFree for Android but noticed that it slowed my phone down to a crawl when it blocked an ad.
I uninstalled it right away....
I guess I'll see what happens tonight. Lol!
I'll post the results in the morning I guess.
Thanks again guys!
Has anyone else experienced this on the GN?
I've had this happen twice in the two weeks since I got it.
The device is stock.
The only common thread I can think of is that in both instances I had plugged the phone into my PC via the USB cable.
I only use 3 sources to charge, my PC at home, laptop at work, or wall charge overnight.
Meh, it is the Nexus (tame dev device). The S was way more unstable. Just pull the battery and all is well.
If you want to be cutting edge then you have to take the rough with the smooth.
R
Sent from my Galaxy Nexus using XDA App
Never happened to mine. You might have a buggy app that doesn't play well with ICS.
Thanks lads, I'm not massively concerned, and yes, it may well turn out to be a bad app, was just posting to find out if it was more "common".
I have of course just seen another thread in this same forum dealing with the same topic (funny that my post flagged up a bunch of other threads in unrelated forums), so this'll probably be closed down...
Think I'll go wade into that other thread now
I've had it twice since I got mine, wasn't plugged in both times so for me it's not down to charging.
mine reboots everytime i try to use the picture frame widget. i select the pic, then it reboots.
The day I got my phone, I had 2 SOD's.
This morning after I woke up, it was in a SOD and 2 minutes ago, the screen went off and I had to take the battery out.
Really strange
Someone have a solution?
I noticed this issue too, whether charging from the PC or the mains charger once the phone hit 100% on the battery it would turn off and could not be started without pulling the battery. I read somewhere that resetting the phone could cure this so, as much of a pain in the ass as that is, that is what I did. SO FAR this seems to have worked for me. I was charging the phone via the USB cable to the PC yesterday and no shut off and when I went to bed last night the phone was on charge all night and again when I woke this morning all seemed good. I'm not sure if this will work for everyone suffering this issue but it worked for me (for now) so thought I would share my experience.
Good luck !
This is so weird, hasn't happened to me since that day. I was able to reproduce the issue after reading another thread on battery saving. Someone mentioned limiting background processes to 3 in Developer Options, when I did this, my phone SODed within seconds. Twice!
Think I mentioned this elsewhere and someone said he used that option with no problems so it's clearly inconclusive. I'm just going to steer clear of that for now.
Sent from my Galaxy Nexus using XDA App
Skysurfer69 said:
Has anyone else experienced this on the GN?
I've had this happen twice in the two weeks since I got it.
The device is stock.
The only common thread I can think of is that in both instances I had plugged the phone into my PC via the USB cable.
I only use 3 sources to charge, my PC at home, laptop at work, or wall charge overnight.
Click to expand...
Click to collapse
This has happened to me a number of times, usually when I was multitasking while listening to the Google Music app. It's a good thing that back cover is easy to pull off and put back on.
Has anyone experienced this before? I'm on 4.2. I went to turn my phone on after work but it wouldn't power on. When I got in the car to charge the phone, it keep rebooting itself and the screen flickered. The flicker is like a bad video driver flicker. I did not root or install any custom roms. The flickering is even happening at the X screen (rainbow).
cool6324 said:
Has anyone experienced this before? I'm on 4.2. I went to turn my phone on after work but it wouldn't power on. When I got in the car to charge the phone, it keep rebooting itself and the screen flickered. The flicker is like a bad video driver flicker. I did not root or install any custom roms. The flickering is even happening at the X screen (rainbow).
Click to expand...
Click to collapse
I had similar issue on N7. Turned off, plug for whole night to a charger, turned on and no problem ever since. That's funny because I had it just after update when battery was low (~5-10%) I thought I it broke down
One more thing you can try: Pull the battery, leave it for 15 minutes to make sure phone doesn't hold any charge, put it in and try to turn on the phone
You'll be fine
I've had it happen several times when my second battery is in...the fake OEM from Shenzhen I got burned on Ebay for. It only happens when the charge is low though and I did have it happen before with the original battery too. Highly doubt it's anything hardware related.
Sent from my Galaxy Nexus using xda app-developers app
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Hi all,
For the last two to three months, I've been running a Universe ROM on my E4GT. Other than an occasional quirk, the phone has been working very well. I noticed that my phone didn't seem to be connecting to my home WiFi, so I put it into Airplane mode, and then took it out of Airplane mode. Instantly, it connected to my WiFi with a MUCH better signal After checking emails on the phone, I set an alarm and went to sleep. I woke up without the alarm since it did not go off. My phone appeared to be off. Holding the power button resulted in the blue LED charge light flashing, but the screen did not come on. I pulled the battery and put it back, thinking that the phone had some odd-ball software glitch that made it turn off in the middle of the night. When I hit power, the blue LED turns on, blinks, and that is all that happens. Once and only once since this started, my screen showed the boot animation, but did not get past that.
Because my screen turned on ONCE, I'm really hoping that I am soft bricked and not hard bricked. It does seem VERY odd for the phone to become bricked after working fine on this ROM for at least a couple months. The only change I made in recent time is to change a governor in ExTweaks from Hyper to Ondemand. I suppose that could have somehow caused this.
I stopped by a Sprint store, but they would not help as I do not have insurance and the phone is out of warranty.
Do you think making a USB jig or buying one may help? There is a Radio Shack close to where I live. And I have an extra USB cable I can take apart.
If that fails, should I send the phone to mobiletechvideos.com for their JTAG repair? It costs $50 plus shipping to them, but that is still cheaper than buying a new phone. If it came to that, I'd certainly hope they could fix it.
The fact that the blue LED light comes on seems like a decent sign of some life. While the battery animation does not come on, the light does.
Thanks for reading and offering any advice/suggestions.
Can you get into recovery or odin mode?
bigdaddy619 said:
Can you get into recovery or odin mode?
Click to expand...
Click to collapse
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
anindrew said:
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
Click to expand...
Click to collapse
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
bigdaddy619 said:
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
Click to expand...
Click to collapse
Thank you! I'll post here if I get that to work or have an alternate solution.
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Brick
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
Thank you very much for the reply. My phone was having a strange issue with connecting to my home WiFi before I put it on the charger for the last time. I wonder if that was a tell-tale sign that something was up.
I went to the Sprint store closer to where I live and explained what happened. They didn't give me any argument at all. Their tech checked out my phone, but couldn't get it to power up at all. They ordered a replacement E4GT (might be new; might be refurbished) for me for $35. I should have it by Friday. I was surprised by how helpful they were. Apparently, they have see this issue occur on some other Android phones as well.
What is the Chainfires app? Does it identify if you have the "older" chipset which can cause the brick issue? That must be what you mean by "GotBrickBug," right?
Since I'm eligible for an upgrade in June, I think I'll just use the stock ROM to avoid any possible issues. I wonder if the GS4 will be out then. It's always interesting to see what the hot new phone is going to be when you're ready for an upgrade.
Again, thank you to everyone for the helpful replies!
Surprised they even had you pay but I'd have paid $35 also if they'd asked me too.
You should get either new or new board at least.
Here's Chainfire's thread and app in OP. By the looks of it, my chips firmware is updated and as much as I've tested and flashed in the last couple weeks, it's holding up great. http://forum.xda-developers.com/showthread.php?t=1693704
My first clue was that my phone was having problems being read by my PC. Couldn't see either the onboard usb or my external usb. It was intermittent and within a week it was gone.
Sprint has been seeing this problem for sure and in Chainfire's thread, Samsung is well aware.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew said:
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Click to expand...
Click to collapse
Sounds like the h/w took a dump on you - the phone replacement was probably the only route left. By any chance did you leave it charging and/or in a location that allowed it to store heat? (Like a blanket, foam cushion, etc)
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Update the next day: I found this thread, which is essentially a match for what I was experiencing. That one ended with a wait-it-out approach, and I basically did the same. I left it plugged in overnight, even though it appeared not to be charging at all (stone cold, no red light). In the morning, it was still all but dead, but I popped out the battery again (I had done this many times before), replugged it into power, and then it charged normally and completely for the first time since the incident. Moral: don't let the phone go below 15%, and if you do, plug it in ASAP. Don't ignore it overnight, even if it's powered off (maybe especially).
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
You're right - folks, this is not the eMMC bug. Let's just clear that up. If you need further information on that you can refer to the discussion thread on that bug and all the research that several folks have put into it.
When I first got my E4GT there was talk of a BLOD or "sleep of death" where the phone would not come back on. Wasn't the eMMC bug. Most people had a low battery so it was thought the batteries were too low and that it booted and messed up the bootloader. Others thought they overheated. Problem is without any way to diagnose the problem it's hard to come up with a "true" answer.
Perhaps a JTAG could revive the phones. Odd that even if plugged in that nothing is happening. But sometimes h/w really can just go south and trash a phone.
I highly suggest backing up your internal usb drive as frequently as possible because I lost a lot of photos that I never transfered, thanks to Samsung and my hardware taking a crap. Emmc blue light bug really sucks, believe me...
---------- Post added at 03:39 AM ---------- Previous post was at 03:29 AM ----------
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
Doesn't sound like emmc at all. All you will have is a blue light and that's it. If you saw ANY display, it's probably a battery and charging issue. You'll know the bug when you don't see anything but blue and no display at all.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew, how did it all turn out?
Hello!
My wife has a Fire HD that she says won't charge. I don't use it, so I'm going to try and explain the issue as I understand it:
She said it charged fine this morning, but when she plugged it in this evening, the battery charge indicator was grey. I guess it is usually green and moves up to show it is charging. So she decided to reset it. When it booted up, it acted as though it was the first time, trying to walk her through the tutorials. She has it plugged in now, and it's still grey.
Anyone else have this issue?
Sent from my SGH-I897 using xda app-developers app
I've never encountered that problem the only thing I can think of is the battery might be failing, but no matter what the problem is you can send it to Amazon and get a new one if its still under its one year warranty.
If I helped please it the thanks button on my post thanks!