Related
I searched here and google and found various charging issues but none quite like what I am seeing. The night before last, I plugged my A100 in before bed like I normally do and saw the power light turn orange. In the morning, I unplugged it without even looking at the LED because I just expected it to have charged completely. When I got to my car and turned it on, it was at 32%. I thought maybe I had something running that was eating battery or I didn't plug it in all the way overnight so it didn't charge. I plugged it into the car charger and went to work. When I got to work it was still at 32% but I didn't use it the whole time so I thought that was odd. I pretty much didn't use it the whole day since I knew it was low on power and I didn't have a charger at work. I got home and saw that it was at 28% so I plugged it in. About an hour later, I checked and it was still at 28%. Thinking that was odd, I turned it off and left it charging with it off for an hour. Turned it back on an hour later and still at 28%. I spent a little time using it while plugged in trying to kill off apps and things but it drained to 18% even though it was plugged in, the power LED showed orange, and the battery icon on screen showed charging (lighting bolt). At this point I started to worry that something was seriously wrong. I turned it *off* and left it plugged in all night after checking to make sure the LED was orange. In the morning, the LED had turned off completely (not blue or orange). I turned it on and saw that it was still at 18% even after charging all night turned off. I unplugged and replugged and the LED came on orange again.
So here is where it gets really strange.. I decide to go through RMA process since I'm still under warranty. I don't want my private data on it when sending it to them so I do a wipe. On a whim, I plug it back in after the wipe and guess what? It's charging! What the heck?!?! I had thought maybe I installed something that was causing problems but since it wasn't charging even when turned off, I figured it couldn't be an app. Can an application cause the device not to charge even in the off state? I thought maybe my battery stats had gotten corrupted so the percentage readout wasn't accurate but right after wiping the data, the battery was reading 18% just as before the wipe.
Any thoughts? Anyone ever see anything similar? My gut says to RMA it still.
Reboot the device.
It's a bug that happened to me on Honeycomb all the time with A100. (No longer happens on ICS)
Did you actually read the OP?
Sent from my Acer Iconia Tab A100 using Tapatalk
Yes, multiple reboots didn't help. No charging even when off. Started charging after wipe. Very odd.
So, after my wipe, I set out to see if I could get it to fail again. I loaded a couple of apps that I had loaded a couple of days before this happened and it stopped charging again. Unloaded each of those apps and still no charging. Did another wipe and still no charging. Conclusion is it's busted and just randomly charges on occasion. Sending it in for RMA today. Still very odd that it was reliably charging after that first wipe.
I myself am experiencing exactally the same problem. Any fix found?
Sent from my A100 using xda premium
Similar thing happened to me. The only thing is I didn't realize it wasn't charging until it was too late and the battery was at 5%. After it shut off, the only way i could get it to turn on was by holding down the power button and plugging in the charger. It didn't get to try a data wipe (didn't have enough time lol). I sent it back and they replaced the system board. Said it was not recognizing the battery properly.
I own two tabs, and one had this issue, the fix is actually quite simple. Let the tab die. No battery life at all. Then, when your sure its dead, plug it back in, and let it charge to full. I haven't had the issue on the tab since.
Sent from my Bad-Ass Acer Iconia Tab a100
Ciao. Same problem: my a100 only power on when plugged on charger.
i'm using a cooked ics with ulocked bootloader and i tried wipe, new installation, varius reboot, etc... and nothing heeelp!
thnx
flskio said:
Ciao. Same problem: my a100 only power on when plugged on charger.
i'm using a cooked ics with ulocked bootloader and i tried wipe, new installation, varius reboot, etc... and nothing heeelp!
thnx
Click to expand...
Click to collapse
Blow in the charge hole (in the tab) and try again, i had a similar problem, my charge was stuck into 3%, i tried that and worked for me : )
Enviado desde mi A500 usando XDA Premium HD app
luisxd said:
Blow in the charge hole (in the tab) and try again, i had a similar problem, my charge was stuck into 3%, i tried that and worked for me : )
Click to expand...
Click to collapse
my charge is on 3% too, but no good luck for me. seems a most serius problem
thanks.
any news guys? I bought a old ACER A100 and only power on while it plug in, so I went ahead and changed the battary, it still does not get charge.
Is the happening on complete stock? Or a custom ROM, if so, which one.
Also, reflash said ROM if applicable, and make sure the data is wiped.
I like the drain the battery idea, although its risky, these tabs can brick if it gets below 10%, current/voltage act weird when its low and blow a breaker inside and keep it from turning on.
Sent from my A100 using Tapatalk 2
What percent does it show the battery at while it's on?
Sent via Acer Iconia A100 on CM10_Build090212; godmachine v2.0 kernel, Smooth, Stable, Fast
My tab has the charging issue, but it is self inflicted. It was dropped, which cracked the lcd screen. I ordered one after a week or so and replaced it. At this point is when the charging issue cropped up. It powers on only if plugged in, and will get to 3% charge no matter how long it is plugged in. It will also only show the 3% if the charger is unplugged. It will then run for a few minutes until the battery dies. Also, the orange charge blinks about one minute after the charger is plugged in.
I found a reference on the web that if the battery charge gets too low the A100 can't charge it. I also found references that people had this problem, and Acer replaced the mb. I took a shot on the battery since it was a lot cheaper. Still the same. That doesn't the battery was not the issue since it was an ebay battery. So for now I just use it in the living room, plugged into outlet. Works good for that.
Jim
Ha! Found my own post by doing google query. Wow, didn't know this thread was still somewhat alive. So, I sent mine back as I mentioned in my last post back in February and they took a week and sent it back to me completely untouched. Basically said it was fixed but the same problem existed. I sent it in after a wipe but I did configure my wifi access point before I sent. When I got it back, my access point connected immediately and it still would not charge. I called them right back furious and demanded they provide shipping back to them because they clearly did nothing. They finally agreed and I shipped it back. After another two weeks of transit and repair time, I got my tablet back and this time it appeared to be fixed.
So, flash forward to 3 weeks ago. One morning I woke up and the tablet wouldn't power on. Black screen but the home "button" would light up when touched and power button would light up when plugged in and such. After several attempts to reset by holding down power button and using the recessed reset button, it was still not responsive. Tried up volume (and down volume) while powering pressing power button.. tried holding down reset button while pressing power button.. all with no result. Submitted rma request and was immediately granted without review. Sent it in and after about two weeks, got it back and it appeared to be working fine. Just this past weekend (about a week after I got the tablet back), I noticed that it was 3% after sitting on the charger for 2 days straight over thanksgiving. ARG!! Looks like another round of RMA here. I have not tried wiping but last time the charging issue happened, it was intermittent for about 2-3 weeks getting worse and worse before finally never charging. I am now near the end of my warranty period and I worry that if I send it back now, they will just turn it around and say it started charging after a wipe. What a piece of ... this is? This will be the 4th times in one year of ownership. I've almost spent the difference in cost between this tablet and other more expensive options in time and shipping alone.
I will try wiping it and then running it all the way down. Although I almost want it to fail hard right now so I can get it RMA'd before my warranty is up.
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
zander21510 said:
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
Click to expand...
Click to collapse
My first guess is your battery is shot. i was gonna recommend the power button failure but if its staying off it might not be that. but id let it charge fully then try to boot up.
Thanks, oddly after a bit of messing around finally got it to boot up. Immediately backed up in CWM....seems to be acting OK now. Idk what happened...
i'll guess, the USB connector got short-circuited when you plugged in, and it caused a cascade failure that fried the SD card or something else inside the phone
there was a factory defect back then with the old SGS 1 (i9000m) model, they fixed that after the 3rd batch, everyone with an old phone from 1st and 2nd release batches, were able to exchange i for a new one.
however in your case, that's not a factory defect, but you plugged it wrong (my guess)
because it has happened to me before when i plugged it in, but the battery was still not charging even after several minutes, yet the phone was getting really really hot
then i unplug, and plug it back in and got the sound feedback "tuu tuud" and then it was actually charging after a few minutes
the first time around even though the charging icon changed, there was no feed back sound, and that was the key, it was not plugged in properly.
so after that time, i always made sure to verify to make sure the phone was plugged in properly and not just relay on he visual icon.
check back after a few minutes, to make sure the phone doesn't get very hot, and it actually increased 1%
It happened again today! After a full charge overnight and no problems for the day up to a little while ago, I opened my email app, it froze, then proceeded to start boot looping. I'm in class so I don't have my computer to try to bring it out of it...so yeah that sucks...
I do remember when I got it to charge yesterday it showed it was charging for 20-30 minutes, but after I "revived" it, I found it hadn't charged at all.
I have been using a Nokia USB cable to charge my phone since I got it, because it was longer than the cheapie Samsung cable that came with it...but it hasn't ever caused problems before. And it charged just fine last night.
How long is the warranty on these things thru tmobile? I may just swap it out while I still can.
Also on an unrelated note, I upgraded to the LG3 radio because I was meaning to anyways...
I pulled it out of it again! This time I held the power button while putting the battery in, when it vibrated I let go, it vibrated again, showed the Samsung logo, and then booted like normal
May I ask what rom are you currently on?
datrapstar said:
May I ask what rom are you currently on?
Click to expand...
Click to collapse
CM9.1 nightly 9/3 with included kernel
It did it a third time during class while it was in my pocket, the power button trick didn't work this time, I had to pull the battery after the samsung logo, plugging it back in to get it to boot...but...
near the end of the CM9 boot animation, when it vibrates and the auto brightness kicks in, it started it again! I have yet to revive it...
This is a bit upsetting because I had just got CM9 the way I liked it and I don't exactly have the time right now to mess with warranty and a new phone...I would like to fix it.
There are about 20 different threads on here on how to revert to stock...let me as a last ditch try to revert to stock and see if it keeps doing it...unless somebody has any ideas...
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
zander21510 said:
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
Click to expand...
Click to collapse
Here you go!!
http://forum.xda-developers.com/showthread.php?p=30832325
Sent from JMT Goodness
Well, finished playing stupid for T-Mobile, in two weeks I will have my replacement T989. Now all that's left is returning this thing to stock before it starts acting up again.
And my temporary replacement phone?
HTC Dream, aka the G1, the first Android phone! Lol what a difference...GB feels like a dinosaur...
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
datrapstar said:
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks! got it all done, back to ugly, ugly stock lol...and just when I thought maybe I would have to brick it myself it did the reboot thing again...so pulled the battery and there it sits factory reset.
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?
First of all I read all the possible posts here in the XDA forum about this problem but no one was able to help me :s
I was listening music with my cellphone than it crashed and turned of from nohting. My first thought was "Damm, it crashed!" and I removed the battery and after a couple minutes I put it back and than the cellphone never turned on again. No battery status is showing up, no leds, odin and flash mode doens't work either. I don't no what to do :s
I tried this:
◘ Unplug from USB, remove battery 5 min, put it back
◘ Odin and Flash mode
◘ Turn it on without battery on pc
◘ Turn it on while recharging
My GNexus model is a I9250 GSM.
Could you add some more details? How long the phone's been in operation, refurbished?, rooted?, your current ROM, kernel, radios, advanced kernel settings such as voltage changes, any tweaks, battery type, temperature.
This exactly happened to me on my DroidX. I spent 2 weeks trying everything to revive it including taking the phone apart before adding it to the pile and getting my current GNexus Toro.. so I know how much this sucks. I'm not an expert on phones bricking but I know that connections can go bad or come loose, especially if the phone has been dropped or other impact, components start to lose their integrity over time and voltage shorts 'burn out' op-amps. You mentioned listening to music, so I'm wandering about the IVA components burning out, which usually has voltage too high especially on boot... Hope you can get it working.
7175 said:
Could you add some more details? How long the phone's been in operation, refurbished?, rooted?, your current ROM, kernel, radios, advanced kernel settings such as voltage changes, any tweaks, battery type, temperature.
This exactly happened to me on my DroidX. I spent 2 weeks trying everything to revive it including taking the phone apart before adding it to the pile and getting my current GNexus Toro.. so I know how much this sucks. I'm not an expert on phones bricking but I know that connections can go bad or come loose, especially if the phone has been dropped or other impact, components start to lose their integrity over time and voltage shorts 'burn out' op-amps. You mentioned listening to music, so I'm wandering about the IVA components burning out, which usually has voltage too high especially on boot... Hope you can get it working.
Click to expand...
Click to collapse
Well first of all I thank you for your concern and my phone is on again, thanks to my uncle. The phone is '4 months old', I rooted last month, bootloader unlocked and I was using samsung stock rom (4.2.1 JB). Yeah, that really suck monkey b*lls. If you got the same problem as me (I really hope not) that's what you should do: First remove the battery, plug the charger and than put the battery back. In my case, It kind "shorted" the battery and my phone is back on. I was reading posts and posts and discovered that GNexus has this problem and a lot. Dunno when it can happen again but I really don't want a paperweight. Once again, thank you!
Glad you got your Nexus back up and runnning. Thanks for posting back with details after you figured out the problem and got your phone working, +1 right there. There's always a good chance this will help out someone later on. :good:
Confirmation: balums worked for me
balums uncle's solution worked for me: specifically, (1) removed USB power, (2) removed battery, (3) applied USB power, (4) inserted battery, (5) press power button.
Thanks balums!
Does anybody have technical (design/EE) insight into what would cause this?
This was starting from a device that appeared totally dead.
The battery was *fully charged* (and showed up that way immediately when the device finally booted).
I had done the obvious things of removing/inserting the battery, cleaning contacts, checking the USB power connection.
Was about to pull it apart when I saw balums post, saving me huge time.
Device is about 16 months old. Stock OS and settings. First time this has happened.
Search terms:
CDMA (Verizon) Samsung Galaxy Nexus -- SCH-i515.
Phone won't boot. Device won't turn on. Won't start. Dead. No worky.
Thanks,
Seth
Awesome! You trick worked, balums!
Interestingly I also have the standard stock version of OS and Hardware which I bought 14 Months ago (nearly to the day). I was surfing over WiFi yesterday evening and when I turned the phone off I noticed the screen getting grey for a moment, not black. And this morning the Nexus just didn't turn on.
Anyway, thanks for the solution, have a nice day!
That is very odd because my i515 also did the exact same thing and I have owned it for 15 months. I can't wait to get home and try this trick. More to come.
Drew
Thanks!
balums said:
Well first of all I thank you for your concern and my phone is on again, thanks to my uncle. The phone is '4 months old', I rooted last month, bootloader unlocked and I was using samsung stock rom (4.2.1 JB). Yeah, that really suck monkey b*lls. If you got the same problem as me (I really hope not) that's what you should do: First remove the battery, plug the charger and than put the battery back. In my case, It kind "shorted" the battery and my phone is back on. I was reading posts and posts and discovered that GNexus has this problem and a lot. Dunno when it can happen again but I really don't want a paperweight. Once again, thank you!
Click to expand...
Click to collapse
Hey Balums,
My GNex didn't turn on this morning and I was really confused as to why it would do such a thing, until I saw your post. Thanks a lot for posting your uncle's remedy!
It fixed mine!
-Fupa
bookmarked. thanks op.
Galaxy nexus wont turn on or charge.
I tried (1) removed USB power, (2) removed battery, (3) applied USB power, (4) inserted battery, (5) press power button but my galaxy nexus still dont turn on. i have 4.2.2 stock rooted. i was downloading something and my screen become weird in colors and i cent use the phone. i turn it of and now wont turn on again or charge.
after unlocking and rooting i installed this touch recovery from google play. [ROOT]Recovery Tools
Excellent! balums' suggestion helped me. I thought I had tried this before but apparently didn't quite get this in the right sequence.
The only remaining issue I have now is that when it does turn on, I've got the thunderbolt on the battery indicator, the phone says it's charging at the lock screen, but when I go to Battery under Settings it says that the battery is discharging. This effectively has my phone in a state where I can't unplug it (battery is too low but it also doesn't appear to actually "charge"). I tried replacing the Micro USB charge port PCB board and came up with the same results. To me, this seems like a problem and may indicate a motherboard or battery connection issue. I used the "Battery Monitor Widget" and it indicated that it was getting AC power. Any thoughts?
Thanks to XDA and Balum's suggestion! I thought my phone just died! It was on 70somethign % battery last I looked, connected by USB to the PC and I don't know if I turned it off and walked away for a while or if it turned off by itself, but it would not turn on no matter what I did after I got back to my desk. It is on Android 4.3 takju stock not rooted.
Thank you all again for the instructions on how to revive the GNex!
Samsung Galaxy Nexus won't power up
I got a Samsung Galaxy Nexus. I got it from my cousin and therefore don't have any information about the rooting status as well as the ROM but i guess it was running stock. The phone won't turn ON, it is not detected in the computer. No LED or any other indication. I tried the above method which worked for many people but it failed. What is special about the phone is that the upper part of the screen is heating up more as compared to the rest of the phone. Can somebody help me fix this? Is this a hardware issue?
I have the EXACT same problem as you do. I have no idea where to start to try to fix it. I took a picture, then lines went squiggly across the screen, then it flickered, and died. I cannot power it on at all. I tried Uncle's tricks. No luck.
Anyone have some ideas on what to try? Thanks.
majidkhan said:
I got a Samsung Galaxy Nexus. I got it from my cousin and therefore don't have any information about the rooting status as well as the ROM but i guess it was running stock. The phone won't turn ON, it is not detected in the computer. No LED or any other indication. I tried the above method which worked for many people but it failed. What is special about the phone is that the upper part of the screen is heating up more as compared to the rest of the phone. Can somebody help me fix this? Is this a hardware issue?
Click to expand...
Click to collapse
Also having the same problem. My Nexus has been rebooting randomly for the past week or so, and finally, this morning, it refuses to turn on at all.
It's a Verizon Galaxy Nexus running stock, but it's been rooted. I'm using the extended battery. The trick that was posted earlier in this thread doesn't seem to work for me. I've tried multiple USB cables and power sources.
I'm going to try the standard battery when I get home, but I'm not expecting positive results.
Work-around
About two months ago whenever I turned my Gnex off, it became totally unresponsive to all attempts to start again. After a lot of trial and error, I discovered that if I pulled the battery for 30-60 minutes and reinstalled, it would power on normally. I have completely wiped and rooted the phone and the problem persisted.
Today I thought about it some and realized there may be some residual charge in the phone, and my waiting period is to allow the charge to drain. To test this theory, I powered the phone down and then tried to restart - nada. Pulled and reset the battery - nada. Pulled the battery, shorted out all four pins that would make contact with the battery, reinstalled battery, and it powered right up. I have not been able to successfully repeat a fast restart when shorting out all four pins. Pulling the battery and waiting 30-60 mins still works.
Incidently about the same time, my screen has stopped auto rotating (and yes it is set to do so).
mwjoerin said:
About two months ago whenever I turned my Gnex off, it became totally unresponsive to all attempts to start again. After a lot of trial and error, I discovered that if I pulled the battery for 30-60 minutes and reinstalled, it would power on normally. I have completely wiped and rooted the phone and the problem persisted.
Today I thought about it some and realized there may be some residual charge in the phone, and my waiting period is to allow the charge to drain. To test this theory, I powered the phone down and then tried to restart - nada. Pulled and reset the battery - nada. Pulled the battery, shorted out all four pins that would make contact with the battery, reinstalled battery, and it powered right up. I have not been able to successfully repeat a fast restart when shorting out all four pins. Pulling the battery and waiting 30-60 mins still works.
Incidentally about the same time, my screen has stopped auto rotating (and yes it is set to do so).
Click to expand...
Click to collapse
What are you doing exactly to short out the battery?
galaxy nexus reboot
my galaxy nexus is about 1 year old now and this is the first time that i've encountered a problem with it. It suddenly restarted, and will take about 5-7minutes before it opens, it will be open up to the "X" logo and when it reaches the normal screen it will restart again. I don't know whats wrong with it. please help/
sethbruder said:
balums uncle's solution worked for me: specifically, (1) removed USB power, (2) removed battery, (3) applied USB power, (4) inserted battery, (5) press power button.
Thanks balums!
Does anybody have technical (design/EE) insight into what would cause this?
This was starting from a device that appeared totally dead.
The battery was *fully charged* (and showed up that way immediately when the device finally booted).
I had done the obvious things of removing/inserting the battery, cleaning contacts, checking the USB power connection.
Was about to pull it apart when I saw balums post, saving me huge time.
Device is about 16 months old. Stock OS and settings. First time this has happened.
Search terms:
CDMA (Verizon) Samsung Galaxy Nexus -- SCH-i515.
Phone won't boot. Device won't turn on. Won't start. Dead. No worky.
Thanks,
Seth
Click to expand...
Click to collapse
Thanks alot... this worked for me !!
You saved my Galaxy Nexus
Similar problem + water
Ok, so I have a similar situation I believe. My phone took a swim. I left it off and riced it. Later on after I believed it to be dry enough, i turned it on. (wow it freaking worked) After a few seconds of using the device checking screen the phone snapped off and went into a reboot. I waited until it came back and i shut it down and thought I'd let it go over night. I plugged it in and let it charge (charge icon was displaying). Everything looked good.
Fast forward. Morning time. I go to turn the phone on. Nothing.
This time the phone won't boot. Instead all i see is the white battery icon show up indicating the battery is 100%. When i plug it in to the charger i get the battery with the charging bolt, then it shows the normal battery indicator light. After that, I get nothing.
I tried the method I saw above. remove power, remove battery, apply usb power, insert battery, press power. Sadly it didn't work.
Anyone have any other ideas as to what might be going on?
Howdy, guys.
I've got my One rooted, unlocked, and was running a CM10.2 nightly build. Everything was working fine until yesterday, when my battery started to rapidly discharge. I woke up with 100% battery, and after about 15 minutes of playing music it was down to 30%. I recharged it and started noticing rapid battery loss, about 10% per 15 minutes when the phone was idle.
Worried that this had to do with my ROM, I flashed the Eclipse Google Play Edition v1.2 ROM. However, the drain issue continued. I decided to let the phone fully discharge, then try powering it up again.
When it was fully discharged, I tried plugging in the phone. No LED came on and I couldn't turn the phone on. I've let it sit for over 2 hours now with the same result.
Some posts with similar symptoms have mentioned plugging the phone into a Windows PC and experiencing the "USB device plugged in" sound alert. I am not having any such luck, and what I currently have is a very aesthetically pleasing paperweight with no function whatsoever.
Has anyone else experienced a similar issue, or found a fix?
none
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Last Sunday, listening to music with HTC One (bought on Sep 11) on the charger, it suddenly went dark. Would not reboot, no charge light either. Went to a VZW store, they're shipping me a warranty replacement.
I wonder whether my habit of leaving it charger-connected whenever it's sitting on my desk (i.e., way beyond the fully-charged point) somehow stressed the battery (or the charging circuitry) -- though that habit never impacted my two previous HTC models.
When you hold Vol+Down and Power do your home and back arrows blink? If so, point the phone sensors (the two on the front on the left hand side) into a bright light. Then hold down Vol+Down and Power. It should boot. I'm not sure why. But it worked for me today after installing a custom recovery. -shrugs-
musicman625 said:
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Click to expand...
Click to collapse
I've got a replacement being shipped to me, and I'll send them the old one when it comes in. Currently using an old Samsung Stratosphere as a replacement, I was just hoping there'd be an easier fix or something simple. Thanks, though!