Related
I have a rooted evo and recently I think it suffered from humidity and high heat when it was left in a ziplock bag outside for a short period. Anyway, I went to turn on my phone later and nothing happened, no boot, nothing. I took the battery out and put it back in, nothing. Tried to boot to recovery, nothing. You get the picture. Dead. I tried plugging it in and couldn't even get the orange light to turn on. I figured moisture was the culprit so I left it unplugged without the battery and by a fan to dry out. Still yet, nothing a day later. Two days later now the phone will boot up and stay running for anywhere from 5 minutes to 8 hours, and then just quit like the battery is dead, even when it charges. Sometimes it will turn right back on by hitting the power, others it won't do anything unless I wait an hour. Whenever it is in this dead time, it won't take a charge, but when it is alive, it will take a charge. Anyway, does this sound like the battery is hosed or is it some other type of issue? When it is running, everything works fine, date, 4g, wifi, etc. I want to take it to Sprint to have them look at it, but am rooted and fear they will say tough ****. I want to unroot so Sprint will look at it, but am worried the phone will die partway through the process, totally bricking the phone. Please offer your opinions and any help you may have!! Thanks a million.
legasus233 said:
I have a rooted evo and recently I think it suffered from humidity and high heat when it was left in a ziplock bag outside for a short period. Anyway, I went to turn on my phone later and nothing happened, no boot, nothing. I took the battery out and put it back in, nothing. Tried to boot to recovery, nothing. You get the picture. Dead. I tried plugging it in and couldn't even get the orange light to turn on. I figured moisture was the culprit so I left it unplugged without the battery and by a fan to dry out. Still yet, nothing a day later. Two days later now the phone will boot up and stay running for anywhere from 5 minutes to 8 hours, and then just quit like the battery is dead, even when it charges. Sometimes it will turn right back on by hitting the power, others it won't do anything unless I wait an hour. Whenever it is in this dead time, it won't take a charge, but when it is alive, it will take a charge. Anyway, does this sound like the battery is hosed or is it some other type of issue? When it is running, everything works fine, date, 4g, wifi, etc. I want to take it to Sprint to have them look at it, but am rooted and fear they will say tough ****. I want to unroot so Sprint will look at it, but am worried the phone will die partway through the process, totally bricking the phone. Please offer your opinions and any help you may have!! Thanks a million.
Click to expand...
Click to collapse
I would recommend a new battery see if that helps any.
well are your moisture indicators tripped?
deathsled said:
well are your moisture indicators tripped?
Click to expand...
Click to collapse
The one on the battery doesn't seem to be, not sure where any others are though.
I think that it might be best if you just tried to unroot... when I did it, it didn't take very long at all (maybe 5 minutes?) I used Good and Evo's method of unrooting, I'd post a link, but XDA won't let me. Just Google "unroot Evo".
But if it is insanely flakey, maybe try a new battery first? I can't think of anything else that would go bad in those conditions...
One more thing: I've herd many stories of people simply deleting the Superuser apk and getting away with it. Many techs at stores like Best Buy won't dig deeper than your program menu. It might be worth a try if it's your last resort...
Sorry if that was no help, best of luck!
I am REALLY unhappy with this phone. Aside from the poor signal and other issues well known to the Nexus, I now have a phone that has a charging problem. Sometimes when I plug the phone in, it does not recognize that it is plugged in and will not charge. This is not an issue in itself, because if I unplug and plug back in a few times it will eventually charge. The big problem is when it is NOT plugged in. The phone will often switch between charging and not charging on the battery indicator.... even though it is NOT plugged in.
I read up on this and found that... shocker.. this is just one more issue plaguing Nexus owners. The real problem for me is that everytime the phone switches from thinking it is charging to not charging, about every two seconds mostly, the screen comes on. This results in the screen constantly going on an off and the battery draining extremely fast. It is 8:17 am, and I unplugged the phone at 6:40 this morning. In less than an hour and a half, the battery has fallen to 38% and I have not used the phone at all today. It is sitting on my desk, flashing like a disco club.
I have searched but have only found an option to keep the phone ON while charging. Is there an option or app available that will prevent the screen from lighting everytime it thinks I have plugged it in to charge? I am rooted, so any option known would be helpful.
I cannot wait to throw this thing in the garbage, but I am not happy with any of the other options currently available. I like the look of the Galaxy S3 but the Gnex has left a bad taste in my mouth for Samsung... it was my first Samsung phone and I'm not sure if I should judge the product line on all the problems I have had with this phone. I loved the HTC Incredible it just got a little old.
Can anyone help me with this problem... please! It is now at 30% since I typed the last few lines. I can sit and watch this thing draining like a bathtub.
Jim
try changing the usb port on the phone
http://www.ifixit.com/Guide/Repairi...zon-LTE-Micro-USB-Charge-Port-Main-Mic/9641/1
I had this issue caused by water damage quite recently - it was in my pocket during some absolutely unprecedented rain here in the UK, and although it seemed I could charge it without problems, when it was off the charger it'd be confused and flash on and off as you say. I just threw it in some rice and took it out at midnight, problem solved (whether the rice was actually responsible for solving it, I have no idea). Has your phone been used in the rain or anything like that, or been in the pocket of clothes that aren't very 'rainproof' during rain? Could be it.
Is it the charger? I had a bad car charger that did the same thing. If not, I would contact Samsung and see what they can do for you.
Sent from my GSM Galaxy Nexus using Tapatalk 2
I read about the water damage being a possible culprit but I cannot remember it getting wet anytime recently. It is not the charger, it does the same thing with two different chargers and the car charger. It does actually charge, thats not the problem. The problem is when I am away from the charger the screen just comes on all the time and the battery is drained rapidly. It has been having issues for a week or two now but just recently started having the problem when not actually plugged in.
Someone just needs to make an app with an option NOT to turn on the touchscreen when first plugged in.
Jim
calaski8123 said:
I read about the water damage being a possible culprit but I cannot remember it getting wet anytime recently. It is not the charger, it does the same thing with two different chargers and the car charger. It does actually charge, thats not the problem. The problem is when I am away from the charger the screen just comes on all the time and the battery is drained rapidly. It has been having issues for a week or two now but just recently started having the problem when not actually plugged in.
Someone just needs to make an app with an option NOT to turn on the touchscreen when first plugged in.
Jim
Click to expand...
Click to collapse
Have you been able to fix your issue? I've had zero issues with my Galaxy Nexus for months, and now I'm having the same problem you describe. Initially I thought it was the ROM, but last Sunday I noticed that the phone will simply not sleep without being charged. The USB port appeared to be bent downward, so I used a tiny flat head screwdriver to raise the port. This seemed to fix the issue for a few minutes, but then the phone kept waking up. It's murdering my battery, and I'd like to fix this situation. The problem seems to be intermittent, and occasionally it will work for hours at a time. This leads me to believe that the problem could be internal.
I'm wondering if you tried anything else? I don't have a problem replacing the USB port myself because it seems like an easy and cheap fix. I'm not a novice when it comes to repairing phones, but I'd rather not open the device quite yet.
The new part is $8.00 shipped, and the seller is in the US. You can't go wrong. I will report back once I fix the problem.
Not really, the problem just sort of went away a week ago... I'm getting the Galaxy S3 end of October so I'm not going to replace the USB port. I messed around with the usb thing too, bent it with a knife so it wasnt touching anything. I also tried cleaning the contacts and blowing it out with air... not sure if any of these things helped or not. Like I said if I made it worse didnt matter as I'm getting GS3 soon. So for now its working but not sure why or how or how long...
Jim
calaski8123 said:
I am REALLY unhappy with this phone. Aside from the poor signal and other issues well known to the Nexus, I now have a phone that has a charging problem. Sometimes when I plug the phone in, it does not recognize that it is plugged in and will not charge. This is not an issue in itself, because if I unplug and plug back in a few times it will eventually charge. The big problem is when it is NOT plugged in. The phone will often switch between charging and not charging on the battery indicator.... even though it is NOT plugged in.
I read up on this and found that... shocker.. this is just one more issue plaguing Nexus owners. The real problem for me is that everytime the phone switches from thinking it is charging to not charging, about every two seconds mostly, the screen comes on. This results in the screen constantly going on an off and the battery draining extremely fast. It is 8:17 am, and I unplugged the phone at 6:40 this morning. In less than an hour and a half, the battery has fallen to 38% and I have not used the phone at all today. It is sitting on my desk, flashing like a disco club.
I have searched but have only found an option to keep the phone ON while charging. Is there an option or app available that will prevent the screen from lighting everytime it thinks I have plugged it in to charge? I am rooted, so any option known would be helpful.
I cannot wait to throw this thing in the garbage, but I am not happy with any of the other options currently available. I like the look of the Galaxy S3 but the Gnex has left a bad taste in my mouth for Samsung... it was my first Samsung phone and I'm not sure if I should judge the product line on all the problems I have had with this phone. I loved the HTC Incredible it just got a little old.
Can anyone help me with this problem... please! It is now at 30% since I typed the last few lines. I can sit and watch this thing draining like a bathtub.
Jim
Click to expand...
Click to collapse
I've got the exact same issues, it's ruining my battery life. Has anyone found a fix for this yet?
Its a physical problem. You need to replace the charging port, or get new phone like me.
calaski8123 said:
Its a physical problem. You need to replace the charging port, or get new phone like me.
Click to expand...
Click to collapse
@calaski8123 -> how would I replace the charging port? Should I contact samsung/google?? I have the exact same issue being discussed here and its driving me nuts. And I got this phone just a couple months ago so getting a new phone is not a solution...
best,
-Nripesh
If its new I'd take it back under warranty. If not, you can buy the parts on ebay and other sites... Search the Forums here, there are details. You can also search Youtube for a guide. Samsung probably would fix but it would cost much more.
Mine is better, but not sure what fixed it. The battery still doesn't last but half a day so I'm still getting the S3 in week or so.
Jim
Gnex Charging Issue
Hi all! Yes, I am another one of the unfortunate owners of a Gnex with this issue. I wanted to send out a reply to everyone that says to replace the USB charging port. I just had mine replaced, and it did not fix the problem. I have also tried different batteries, and I have read where some people are fixing this by *** gently *** bending the USB connector up ( toward the screen ). That also did not fix my problem. A few days ago I installed AOKP 4.2.1, and that was ineffective as well. I am stumped. My Samsung Fascinate was a very good phone, but the Gnex is really making me wonder if I ever want another Samsung. Has anyone found a solution for this? Unfortunately for me, I bought mine used and don't have the option of returning to Verizon for help. 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?
Last night my phone died after 2 days off cable due to me having to use my cord for another device. I plugged it in today to find that it wasn't charging at all. I decided to give it a few minutes before trying, thinking it may not be turning on because it still needs some juice. I waited 30 minutes and it wouldn't turn on still, just gave me the little animation of a battery draining to indicate that it needs to be charged. After this, I figured that it's possible the cable is just dead, so I opted to borrow a cable from my brother. The cable charges his phone just fine, but it doesn't work with charging my phone. I took a shower while waiting for it to perhaps get the juice it needed, and still no dice. I tried several different outlets thinking perhaps the outlet was dead, and still nothing.
I've had the phone for a little over a month, so I'm not sure how long I have to turn it in or not; I'd hope it'd be 3 months for factory issues, but judging from how people mention 14 days, I'd assume that they're eager to push responsibility of broken devices onto the customer as fast as they can. Do you guys have any idea of what could be wrong? Perhaps if it's possible for me to get a replacement at this point?
I've been running the Lifeless v.11 Rom for a while with no issues, I haven't flashed anything in possibly a week or two, so I honestly doubt this is a software issue. It's never been exposed to water, but then again I really don't trust phones to detect if they've been damaged or not since it seems even a humid day is enough for those small water damage detection stickers to run pink.
WASSHOI said:
Last night my phone died after 2 days off cable due to me having to use my cord for another device. I plugged it in today to find that it wasn't charging at all. I decided to give it a few minutes before trying, thinking it may not be turning on because it still needs some juice. I waited 30 minutes and it wouldn't turn on still, just gave me the little animation of a battery draining to indicate that it needs to be charged. After this, I figured that it's possible the cable is just dead, so I opted to borrow a cable from my brother. The cable charges his phone just fine, but it doesn't work with charging my phone. I took a shower while waiting for it to perhaps get the juice it needed, and still no dice. I tried several different outlets thinking perhaps the outlet was dead, and still nothing.
I've had the phone for a little over a month, so I'm not sure how long I have to turn it in or not; I'd hope it'd be 3 months for factory issues, but judging from how people mention 14 days, I'd assume that they're eager to push responsibility of broken devices onto the customer as fast as they can. Do you guys have any idea of what could be wrong? Perhaps if it's possible for me to get a replacement at this point?
I've been running the Lifeless v.11 Rom for a while with no issues, I haven't flashed anything in possibly a week or two, so I honestly doubt this is a software issue. It's never been exposed to water, but then again I really don't trust phones to detect if they've been damaged or not since it seems even a humid day is enough for those small water damage detection stickers to run pink.
Click to expand...
Click to collapse
wish i could help you man:/ only thing i can think of is taking of the back plating and make sure the connector is fine.it would suck if we have another evo 4g on our hands, especially without a removable battery
WASSHOI said:
Last night my phone died after 2 days off cable due to me having to use my cord for another device. I plugged it in today to find that it wasn't charging at all. I decided to give it a few minutes before trying, thinking it may not be turning on because it still needs some juice. I waited 30 minutes and it wouldn't turn on still, just gave me the little animation of a battery draining to indicate that it needs to be charged. After this, I figured that it's possible the cable is just dead, so I opted to borrow a cable from my brother. The cable charges his phone just fine, but it doesn't work with charging my phone. I took a shower while waiting for it to perhaps get the juice it needed, and still no dice. I tried several different outlets thinking perhaps the outlet was dead, and still nothing.
I've had the phone for a little over a month, so I'm not sure how long I have to turn it in or not; I'd hope it'd be 3 months for factory issues, but judging from how people mention 14 days, I'd assume that they're eager to push responsibility of broken devices onto the customer as fast as they can. Do you guys have any idea of what could be wrong? Perhaps if it's possible for me to get a replacement at this point?
I've been running the Lifeless v.11 Rom for a while with no issues, I haven't flashed anything in possibly a week or two, so I honestly doubt this is a software issue. It's never been exposed to water, but then again I really don't trust phones to detect if they've been damaged or not since it seems even a humid day is enough for those small water damage detection stickers to run pink.
Click to expand...
Click to collapse
Pull your battery, try again
Sent from my LG-LS970 using xda app-developers app
Yea, going to update this. Sprint was giving me issues and trying to cough up money from me, so I pulled the battery and cleaned the port with a q-tip and it charged fine again. I was in for a scare there, but it's back to life.
Same problem...didn't have to pull battery
WASSHOI said:
Yea, going to update this. Sprint was giving me issues and trying to cough up money from me, so I pulled the battery and cleaned the port with a q-tip and it charged fine again. I was in for a scare there, but it's back to life.
Click to expand...
Click to collapse
Just wanted to chime in with my experience.
I had same issue. Battery completely drained with a visit to the relatives (low cell signal).
Got home and plugged it in for 5min, the "battery charging" animation came on when short pressing the power button.
Had to move the phone to a different charger for the night and noticed that I couldn't get it to even show the charging animation while on the charger. Indeed after 8 hours on the charger the next morning it still wouldn't turn on. I thought I would have to take it back to Best Buy. On a whim, I thought I would drain all of the capacitance from the system by pressing and holding the power button to see if that would allow it to restart the charge cycle. So I held the power button for about 30-45sec off the charger, then waited about 30min and plugged it in at work.
It worked. Not sure why, but I didn't have to return it to Best Buy, so I'm happy.
Okay, gonna try and explain this as best I can, bear with me.
2.5 years ago or something I got a Gnex from Verizon, brand new. The phone would act like a ghost was using it, like someone was interacting with the touchscreen. It'd randomly call contacts, send texts (random letters/numbers), all kinds of weird stuff. Video of it on day 1 HERE doing this. Took it into Verizon, got a new replacement. Never had the problem again. 2 or so years go by, not a single problem, unlocked, flash, all that, never had the problem again.
About a month ago, I upgraded to a Moto X and passed this phone on to a family member. At the time was running the latest stable Cyanogenmod ROM, the last for JB. 10.2 maybe? Anyway, that's what ROM was on it, again, no problems. Factory reset the phone to wipe my stuff, left it rooted and unlocked. I gave them the phone, battery, extended battery, and a few cases as well, no charger cause I know they'd twist up and destroy the factory cable. Setting the phone up for them battery starts going low, used their charger. Cable had shorts and crap, scavenged around looking for good charger. Get phone set up for them, and I'm done, handed off.
A day later, they're complaining that the phone is going crazy, like a ghost is using it, and it's randomly calling people, sending texts, opening menus, not charging, etc. Sounds like EXACT same issue I had with my very first Gnex that I exchanged. Figured that was really strange, maybe it was the software. Factory reset to latest factory image 4.2.2, lock BL back up, completely bone stock. Re-setup phone and all that jazz. Phone's acting fine. Decided this time that'd I'd let them have the original stock charger, thinking maybe that'd help with the charging issues too. All seems well....
However, during the reset and all, and after re-setting up the phone, battery is low.... plug it in with a known good charger of mine, but not stock original, and all the sudden the phone's freaking out again. Turn screen off, turns itself back on. Dialing people, opening apps on its own, etc. Figure maybe this Gnex just won't take any charger except it's original. Pull battery, reboot, phone's fine, fine for 10+ minutes. Plug in OEM charger this time, wait a few seconds, unplug, phone goes crazy.
Also interesting, they brought another charger of theirs with a little red LED on, plug it into wall, red LED comes on. Interestingly, if the charger is unplugged from wall with red LED off and I plug it into the phone.... the red LED on the wall charger turns on... that's not right. So.... here's where I'm at now. If I pull battery, reboot, and never attach a charger, the phone acts perfectly fine. The instant I plug in ANY charger, it'll start going wacko and continue to until I pull battery and reboot. At first I thought this was a charger issue, but now... I'm thinking it's battery related. This little experiment of getting the phone to go crazy after plugging in a charger applies to both the OEM and extended battery, regardless of what charger I use.
When I owned the phone, I almost exclusively used the OEM charger, occasionally another charger I had that I know works fine. Gave Gnex to family member WITHOUT a charger, so they were forced to use who know what condition phone charger. I'm wondering if maybe some rogue jacked up phone charger with shorts in it and crap somehow killed the extended battery. Then, they switched to the OEM battery, and again, unknowingly killed that battery too with the same crap charger. So maybe buying a new battery would fix the issue and only using the OEM charger from now on or the other one that was mine that I know works? Or maybe the phone is just broken now? It just doesn't seem right that plugging a phone into the micro-USB should turn ON the red LED on the charger when it's not plugged into the wall, like the power is coming out of phone and going into the LED...
I just refuse to believe that on the exact same day and within hours of me upgrading to a Moto X and passing on my Gnex that had worked perfectly for 2 years in my possession somehow just happens to "break" or "go bad" on its own. Thought it was software glitch/bug in CM, no. Thought it was incompatible charger, no. Maybe the batteries are bad? Maybe the phone's circuitry got jacked up too? Just seems weird that, as far as I can tell, pulling the battery and rebooting fixes it for good until the battery dies. Within 30 seconds of connecting a charger, the phone goes bonkers.
Any ideas? Feel bad, family member probably thinks I dumped a bad phone on them!
Thanks!
What kind of sorcery was that? I honestly don't know what to say about this other than bad timing? I highly doubt a ghost is possessing the phone.
I know a ghost isn't possessing the phone, I just, that's how I best described it when it was going wacko by itself. Plus, interesting topic title, maybe get a few more people to read it and maybe offer some advice or info or something :laugh:
However, I do have a ghost in my house, or a spirit or something. I've seen him, sitting on my couch before. He died in a fire, smoke inhalation, no smoke alarms in the house. House was sold, completely rebuilt, and I am first to live in it since then. Crazy story for a different forum lol
From what I can see, it's just that the screen isn't working properly because of leaked currents from the battery or the charger... Just get the whole screen replaced (it's hard to only replace the glass layer) and should be fine.
Sent from Google Nexus 4 @ CM11
Leaking currents, had it happen to me before from a bad charger. I doubt it's the battery, try an outlet in a different house, they may have bad power.
Sent from my Galaxy Nexus using Tapatalk
So this "leaking currents" problem, it's a problem with the battery? A problem with the phone, in particular, the screen? It definitely sounds like a rogue bad charger could have done this based on the feedback so far. The "damage" or whatever happened at their house. Just the other night, they brought the chargers and phone and stuff to my house, a different house, problem persisted. So I'm not thinking it's a dirty power issue or anything.
...and so you should have the screen replaced. I've had Motorola and HTC phones with issues responding to touches when charging, and replacing the screen largely eased the problem (although I still ended up getting a new charger because I don't want it to also damage the newly replaced screen).
Sent from Google Nexus 4 @ CM11
Op may also want to consider relocating... ghost home and ghost phone, that's too much!
LOL
Mike7143 said:
So this "leaking currents" problem, it's a problem with the battery? A problem with the phone, in particular, the screen? It definitely sounds like a rogue bad charger could have done this based on the feedback so far. The "damage" or whatever happened at their house. Just the other night, they brought the chargers and phone and stuff to my house, a different house, problem persisted. So I'm not thinking it's a dirty power issue or anything.
Click to expand...
Click to collapse
Could be the battery, could be the USB cables or chargers, could be the USB port on the device, could be the screen. The fact that it only happens when plugged in but with more than one charger and battery makes me suspect the USB port on the device. From my understanding you can buy a replacement. A temporary fix would be to use a charger that charges the battery outside of the phone.
Sent from my Galaxy Nexus using Tapatalk
No ghost... i think
I think its because the charger you use....
I had the same problem, but not with gnx... before gnx I used galaxy i5801...
when I put my mobile in charge, my mobile did some crazy things, like operating itself,...I figured out that the charger I used is not the one I shouldn't use.
every mobile has a charging limits, like voltage restriction..
little difference in voltage could make big difference.
so I changed the charger. problem solved for me.
other than charger.. there are some things can do this, I don't know about all.
I doubt it may caused by your digitizer...maybe is has too much sensitivity, caused by water, dust, pressure, etc....
digitizer and display are not the same.
I faced this one too ( galaxy i5801) before charging problem, but not with gnx.
A digitizer is the part of a touch screen that senses your touch and "digitizes" your gestures into impulses that the phone can understand as commands.
if it continues my last suggestion.... call the priest
Well, I borrowed an OEM standard and extended battery from a friend, neither fixed the problem. My friend did say that similar to my first Gnex, when he first got his, it did the same exact thing, but after a while it stopped and it hasn't done it ever since. I also narrowed it down, or, widened the issue, in that it's not just AC chargers, the exact same stuff happens with a brand new 12V car charger.
Dirty power on the fifth rail of a USB wire. Its either the charger not supplying enough power or a damaged cable.
Sent from my Galaxy Nexus using Tapatalk
My vote is on the screen, due to the digitiser. Replacing the touchscreen could help solve the problem. I was in your family's position when I got a used Motorola Cliq from a friend and the battery was all good, no leaks. Ghosts just started touching it everywhere like a crazed groupie when it went into my possession. No explanation as to why it happened and I didn't look into it that much but replacing the screen is the most likely solution.