Just got my phone yesterday. Running Calk's 2.7 and ICS theme, set dpi to 160, looks and runs awesome. However, it always thinks it's either charging or plugged into USB. the red LED never wants to turn off. how can I remedy this problem?
Possibly try turning it off, booting to recovery, clearing cache/dalvik-cache, and then clear battery stats
Was it like this prior to rooting and custom rom?
Apk, that didn't do it.
yes, it did the same thing beforehand. Except takng out the battery solved the problem once.
Get it exchanged ASAP. This is a defect with the USB port. Has NOTHING to do with software. I was outside of my 14 day return and Sprint made me send it to Samsung to get fixed. $7 jig and two weeks later it was fixed.
With my tech background I would say check the charging port. Could be a metal shaving or *gasp* corrosion!
Sent from my SPH-D710 using XDA App
my phone sort of has the same issue...it charges fine but i cant get it to connect to my computer..my phone thinks it still charging yet i have it plugged in my computer it doesnt give me the option to switch it to usb mass storage..
Got it on Craigslist, no exchange possible.
Dioscorus said:
Got it on Craigslist, no exchange possible.
Click to expand...
Click to collapse
Shouldn't matter. The phone has a one year warranty from Samsung. I bought my wife an Epic on craigslist last year and had it repaired under warranty.
Sent from my SPH-D710 using XDA App
Yup. I had the same problem. I think it is related to the USB port (from reading a few SGS2 threads). I took it to the Sprint Store and they said the USB port looks good. They reset it and it still acted that way. However, 2 hours later the problem is gone. They ordered me a replacement so I'm still going to take it because who knows why the problem starts. I did have Calk's rom and also have the battering monitoring widget by 3C and I had cleared the battery stats multiple times prior to the symptoms starting. Just proving as many clues as possible...
What do you mean by reset?
Funny I see you have this problem (not really funny) because I noticed the same thing last night and just figured it was Rom related.
It sucks... can you give more details about the reset process? Soft reset?
and bump...
Dioscorus said:
and bump...
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=1344882 and see if it helps.
Sent from my SPH-D710 using Tapatalk
no dice
I had the same problem.
The red light was on all the time, only went out when I got a text. If I pulled the battery the phone would show like it was charging as soon as I put it back in. It would show the battery animation on the screen not plugged in.
After a battery pull the phone would also not boot using the power button, had to boot to recovery and boot from there.
Took it to sprint, they gave me a new battery. Solved the problem only until phone was plugged in to charge. Then started all over again.
Turned out to be a problem with the USB port and they ordered me a replacement.
got it fixed! looks like the pcb on the port was sitting too close to the lower edge of the phone. pushed it up gently and now it seems to be working. thanks for the direction, nivron.
my other concern is that battery life sucks ass. drains really quick (at the rate of ~6%/hr!). again, running calk 2.7 + ics theme. also, taking out the battery seems to reduce the life 20%. what's the deal...
Hmm, now the USB cable needs to be at a certain angle for the phone to charge. Is there any way a Sprint store could furnish a replacement for me?
I just received my new phone via UPS a couple of hours ago. The sim card was already in it, I popped the battery in, and I turned the phone on. The AT&T chime played but the screen never lit up. The capacitive buttons will light up and make a sound when touched, but the screen is still dead. I've had it plugged in for over an hour and the screen still won't light up. I've restarted it, removed and replaced the battery and the sim card several times and no dice.
Did any of you have to fully charge the phone the first time you started it up before the screen would come on? Definitely sounds like a dumb question to me since I've never needed to fully charge any new phone I've ever had before I could use it, but I figured I'd ask in case this is a weird new feature. I'll leave it charge overnight and if it still isn't working, I'll make my way to the store hoping they still have stock.
Did your phone sit out in cold weather at all?
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
Not as far as I know. I live in Louisiana and it isn't that cold out yet.
No being that I live in Louisiana to id say its not cold enough yet. Well sorry but that's kinda all I got for you. Sucks that its not working. I got mine this morning coming from the s3 this phones amazing
Sent from my SAMSUNG-SGH-I317 using Xparent Blue Tapatalk 2
Good question though, thanks.
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?
Hey XDA, what's good? OK so my wife's note 2 was stolen and we received what I am guessing is a refurbished one from our wireless insurance provider. The first day we got it I noticed the popup (battery disconnected) when I plugged in the charger. Now it's been about a week and the phone only charges when I play with it by pulling out the battery, putting it back in, and turning it on (a few times usually). Otherwise, sometimes it will just hang on the battery screen and the charging animation freezes and then, up pops the dreaded yellow triangle with a battery in it. So, I have been begging her to just let me root and flash a different rom/kernel combo, but she wants/likes it stock , (which is nbd, could flash the stock tw Rom), and the company who supplied the phone to our insurance provider wants us to ship it back so they can either replace, or fix the phone. Funny thing is, Sprint techs wanted nothing to do with it! We dropped it off as they asked and not even 20 min later they called and said come get it we can't fix it!? So, here is my dilemma, could this b a software issue? Or is flashing a Rom not a possible fix? I've tried other usb cords and checked the usb port, battery/phone terminals, and tried gently moving the usb plug around to see if it was the issue, as I've had Samsungs in the past with similar problems. Any help would be awesome! Thanx, from one Android junkie to another.
Sent from my HTCONE using xda premium
fastlyfe941 said:
Hey XDA, what's good? OK so my wife's note 2 was stolen and we received what I am guessing is a refurbished one from our wireless insurance provider. The first day we got it I noticed the popup (battery disconnected) when I plugged in the charger. Now it's been about a week and the phone only charges when I play with it by pulling out the battery, putting it back in, and turning it on (a few times usually). Otherwise, sometimes it will just hang on the battery screen and the charging animation freezes and then, up pops the dreaded yellow triangle with a battery in it. So, I have been begging her to just let me root and flash a different rom/kernel combo, but she wants/likes it stock , (which is nbd, could flash the stock tw Rom), and the company who supplied the phone to our insurance provider wants us to ship it back so they can either replace, or fix the phone. Funny thing is, Sprint techs wanted nothing to do with it! We dropped it off as they asked and not even 20 min later they called and said come get it we can't fix it!? So, here is my dilemma, could this b a software issue? Or is flashing a Rom not a possible fix? I've tried other usb cords and checked the usb port, battery/phone terminals, and tried gently moving the usb plug around to see if it was the issue, as I've had Samsungs in the past with similar problems. Any help would be awesome! Thanx, from one Android junkie to another.
Sent from my HTCONE using xda premium
Click to expand...
Click to collapse
From experience, I think it's a charging-port/usb-port issue. I didn't hear any reports so far of a software issue preventing a phone from charging.
Sent from my GT-N7100
ROM: ARHD 19
KERNEL: Stock
Yes it's a hardware problem for sure...
Thanx guys we sent it out!
Sent from my HTCONE using xda premium