Related
Hi all,
For the last two to three months, I've been running a Universe ROM on my E4GT. Other than an occasional quirk, the phone has been working very well. I noticed that my phone didn't seem to be connecting to my home WiFi, so I put it into Airplane mode, and then took it out of Airplane mode. Instantly, it connected to my WiFi with a MUCH better signal After checking emails on the phone, I set an alarm and went to sleep. I woke up without the alarm since it did not go off. My phone appeared to be off. Holding the power button resulted in the blue LED charge light flashing, but the screen did not come on. I pulled the battery and put it back, thinking that the phone had some odd-ball software glitch that made it turn off in the middle of the night. When I hit power, the blue LED turns on, blinks, and that is all that happens. Once and only once since this started, my screen showed the boot animation, but did not get past that.
Because my screen turned on ONCE, I'm really hoping that I am soft bricked and not hard bricked. It does seem VERY odd for the phone to become bricked after working fine on this ROM for at least a couple months. The only change I made in recent time is to change a governor in ExTweaks from Hyper to Ondemand. I suppose that could have somehow caused this.
I stopped by a Sprint store, but they would not help as I do not have insurance and the phone is out of warranty.
Do you think making a USB jig or buying one may help? There is a Radio Shack close to where I live. And I have an extra USB cable I can take apart.
If that fails, should I send the phone to mobiletechvideos.com for their JTAG repair? It costs $50 plus shipping to them, but that is still cheaper than buying a new phone. If it came to that, I'd certainly hope they could fix it.
The fact that the blue LED light comes on seems like a decent sign of some life. While the battery animation does not come on, the light does.
Thanks for reading and offering any advice/suggestions.
Can you get into recovery or odin mode?
bigdaddy619 said:
Can you get into recovery or odin mode?
Click to expand...
Click to collapse
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
anindrew said:
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
Click to expand...
Click to collapse
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
bigdaddy619 said:
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
Click to expand...
Click to collapse
Thank you! I'll post here if I get that to work or have an alternate solution.
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Brick
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
Thank you very much for the reply. My phone was having a strange issue with connecting to my home WiFi before I put it on the charger for the last time. I wonder if that was a tell-tale sign that something was up.
I went to the Sprint store closer to where I live and explained what happened. They didn't give me any argument at all. Their tech checked out my phone, but couldn't get it to power up at all. They ordered a replacement E4GT (might be new; might be refurbished) for me for $35. I should have it by Friday. I was surprised by how helpful they were. Apparently, they have see this issue occur on some other Android phones as well.
What is the Chainfires app? Does it identify if you have the "older" chipset which can cause the brick issue? That must be what you mean by "GotBrickBug," right?
Since I'm eligible for an upgrade in June, I think I'll just use the stock ROM to avoid any possible issues. I wonder if the GS4 will be out then. It's always interesting to see what the hot new phone is going to be when you're ready for an upgrade.
Again, thank you to everyone for the helpful replies!
Surprised they even had you pay but I'd have paid $35 also if they'd asked me too.
You should get either new or new board at least.
Here's Chainfire's thread and app in OP. By the looks of it, my chips firmware is updated and as much as I've tested and flashed in the last couple weeks, it's holding up great. http://forum.xda-developers.com/showthread.php?t=1693704
My first clue was that my phone was having problems being read by my PC. Couldn't see either the onboard usb or my external usb. It was intermittent and within a week it was gone.
Sprint has been seeing this problem for sure and in Chainfire's thread, Samsung is well aware.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew said:
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Click to expand...
Click to collapse
Sounds like the h/w took a dump on you - the phone replacement was probably the only route left. By any chance did you leave it charging and/or in a location that allowed it to store heat? (Like a blanket, foam cushion, etc)
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Update the next day: I found this thread, which is essentially a match for what I was experiencing. That one ended with a wait-it-out approach, and I basically did the same. I left it plugged in overnight, even though it appeared not to be charging at all (stone cold, no red light). In the morning, it was still all but dead, but I popped out the battery again (I had done this many times before), replugged it into power, and then it charged normally and completely for the first time since the incident. Moral: don't let the phone go below 15%, and if you do, plug it in ASAP. Don't ignore it overnight, even if it's powered off (maybe especially).
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
You're right - folks, this is not the eMMC bug. Let's just clear that up. If you need further information on that you can refer to the discussion thread on that bug and all the research that several folks have put into it.
When I first got my E4GT there was talk of a BLOD or "sleep of death" where the phone would not come back on. Wasn't the eMMC bug. Most people had a low battery so it was thought the batteries were too low and that it booted and messed up the bootloader. Others thought they overheated. Problem is without any way to diagnose the problem it's hard to come up with a "true" answer.
Perhaps a JTAG could revive the phones. Odd that even if plugged in that nothing is happening. But sometimes h/w really can just go south and trash a phone.
I highly suggest backing up your internal usb drive as frequently as possible because I lost a lot of photos that I never transfered, thanks to Samsung and my hardware taking a crap. Emmc blue light bug really sucks, believe me...
---------- Post added at 03:39 AM ---------- Previous post was at 03:29 AM ----------
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
Doesn't sound like emmc at all. All you will have is a blue light and that's it. If you saw ANY display, it's probably a battery and charging issue. You'll know the bug when you don't see anything but blue and no display at all.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew, how did it all turn out?
Hey Guys,
Over the last year or so I've had intermittent charging issues with my Galaxy Nexus. About 4 months ago is when it first started happening, the phone would either not charge or only charge when it is turned off. Somehow the issue was resolved through tons of troubleshooting, I'm not even sure what fixed it or why it started working again.
Same thing happened about 2 weeks ago, except this time it won't charge at all. Then 2 days later all of a sudden started charging again. Now it's happening again today, I have no idea what is going on or why this handset won't charge properly. The phone won't turn on with just the charger in and the battery out either.
I've tried various chargers including the OEM charger, I've tried up to 6 different chargers and 7 seperate micro-USB B cords. Nothing. I've tried a brand new battery that a friend bought for his phone before he threw it in and no results.
At this point I think it's the USB charger board, however I'm not sure why it would not work and then work again. Does anyone have any ideas or any solutions? I've read thousands of threads on this, from this forum and many others and have gone through some ridiculous troubleshooting methods.
SCH-I515 Korean Version.
Seriously, anyhelp is appreciated.
As of now, all of a sudden it will charge while it's off. But only to about 4% then it just stops charging. It will not charge while it is on at all.
Because it's getting worse and worse?
Relock bootloader, and return it in for warranty, if you can. I'm afraid there's not much help if you already checked for damage to the USB port.
sent from my Google Galaxy Nexus
hi
had the same problem until a few minutes ago.
received my usb/charging flex part today and changed it just before to post here.
took me like 20 min, really easy to do, everything works perfectly and i also took time to clean up a bit the phone inside of some dirts and change the housing i bought with the flex part.
As my screen is under protection since the beginning (4 months old), and that i recently bought a 2000mah battery, well i have to say that i have a new phone ready to handle the new year easily!
operation is easy and you will find plenty of videos on youtube showing how to change the usb flex (7€/$ , +/-) so pretty cheap.
Good luck
Why not buy an external battery charger and a spare battery?
Sent from my Galaxy Nexus using xda app-developers app
I'd get a replacement daughterboard and switch it out yourself. It's easy dude, just like a previous poster already said. I just did it myself, took me all of 20 minutes and cost me $10. ifixit.com has a step by step direction sheet, if you have any questions feel free to contact me about it.
Try the following:
1.) Turn off your phone.
2.) Get a flat head screwdriver (small one)
3.) Push the flat connector inside the microusb port up. (It often gets bent downwards because it's so thin compared to other phones...)
4.) Boot into the bootloader
5.) Hit volume down until restart bootloader appears. Press power button.
6.) Start phone manually.
farshad525hou said:
Try the following:
1.) Turn off your phone.
2.) Get a flat head screwdriver (small one)
3.) Push the flat connector inside the microusb port up. (It often gets bent downwards because it's so thin compared to other phones...)
4.) Boot into the bootloader
5.) Hit volume down until restart bootloader appears. Press power button.
6.) Start phone manually.
Click to expand...
Click to collapse
i dont know why, but this fixed it for me, for a short while. now the charging is intermittent and seems to come and go as it pleases.
Hi,
I had the same problem of ghost charging, it started with phone not charging when connected to charger and then randomly showing charging...
Now discovered it causes vbus_tuna_otg wake lock, resulting in high system usage in settings> battery and not letting phone go to deep sleep, causing battery drain.
Sent from my Galaxy Nexus using Tapatalk 2
Same Problem
I've come into the same problem with my Galaxy Nexus as well. If my phone is turned on, my phone will recognize that a charger is plugged in but the battery will not charge at all. If the phone is off and plugged in, the charging screen won't appear. I've tried multiple chargers and cords, 2 different batteries, and even replaced the micro usb and board, but the problem hasn't changed at all. I've managed to charge my batteries with an external charger but would like to get my phone back to normal working condition. Does anyone think that changing the actual motherboard itself might solve the problem?
Sayword said:
I've come into the same problem with my Galaxy Nexus as well. If my phone is turned on, my phone will recognize that a charger is plugged in but the battery will not charge at all. If the phone is off and plugged in, the charging screen won't appear. I've tried multiple chargers and cords, 2 different batteries, and even replaced the micro usb and board, but the problem hasn't changed at all. I've managed to charge my batteries with an external charger but would like to get my phone back to normal working condition. Does anyone think that changing the actual motherboard itself might solve the problem?
Click to expand...
Click to collapse
I had this problem before, using something small and flat to push the charging connector off the housing will work for awhile. The pin in the charging port is bent down and is very thin it's easy to lift up just use a tiny bit of force to lift it up. The pin touching the housing is causing a short and that is causing your no charge while it's on and mine even went as far as draining my battery very quickly. I did research and found alot of people having this issue on the gnex. I eventually had to turn mine in for replacement, no problems since. Hopefully yours is still under warranty or you can buy the peice that is broken and replace yourself, there is a post above saying what to do for that.
Looks like my phone developed this problem. It sometimes won't charge be it via my pogo dock or USB cord. It seems to start taking a charge after I pop out the battery and then put it back in. I'm going to order another battery and see if that is the problem.
Thank yoiu!!
solved my problem!! I am in your debt
popping the battery out just worked for me too
hlaalu said:
Looks like my phone developed this problem. It sometimes won't charge be it via my pogo dock or USB cord. It seems to start taking a charge after I pop out the battery and then put it back in. I'm going to order another battery and see if that is the problem.
Click to expand...
Click to collapse
I just did the remove battery trick as well and it worked. I just noticed my battery not charging yesterday but figured it was because I was trying to use a different charging in my dad's car. got to work where i left my normal charger and no luck.
thefayeride said:
I just did the remove battery trick as well and it worked. I just noticed my battery not charging yesterday but figured it was because I was trying to use a different charging in my dad's car. got to work where i left my normal charger and no luck.
Click to expand...
Click to collapse
That's good, I tried it a few times but the issue still pops up. To be fair though, I've had this phone and battery since launch day... Almost three years old. I ordered a new battery so hopefully I won't have the issue anymore... And I won't be surprised if my battery life is a little better too.
Sent from my Nexus 10 using Tapatalk 2
hlaalu said:
That's good, I tried it a few times but the issue still pops up. To be fair though, I've had this phone and battery since launch day... Almost three years old. I ordered a new battery so hopefully I won't have the issue anymore... And I won't be surprised if my battery life is a little better too.
Sent from my Nexus 10 using Tapatalk 2
Click to expand...
Click to collapse
The Galaxy Nexus is nowhere near three years old. Your phone would be 18 months old if you had it since launch.
Sent from my Nexus 7 using Tapatalk HD
Excuse me, two years. According to Samsung their lithium batteries have a life of about 500 cycles. So my point is still valid, my battery is probably just on it's way out. I'll find out for sure when my new one comes tomorrow.
Sent from my Nexus 10 using Tapatalk 2
Yeah, since battery life hasn't exactly been the strong point of the GN and some of us had to go though a complete cycle daily, I suspect a lot of folks are going to be seeing more and more issues. Not too long ago, I had a battery that failed in such a way that it would randomly crash the phone and had to be pulled in order to allow a reboot. I would've suspected anything but the battery in that case.
Sent from my SCH-I545 using Tapatalk 2
farshad525hou said:
Try the following:
1.) Turn off your phone.
2.) Get a flat head screwdriver (small one)
3.) Push the flat connector inside the microusb port up. (It often gets bent downwards because it's so thin compared to other phones...)
4.) Boot into the bootloader
5.) Hit volume down until restart bootloader appears. Press power button.
6.) Start phone manually.
Click to expand...
Click to collapse
This kind of worked for me, but the "boot into bootloader and restart it" killed my phone, don't know why. After a lot of a hassle i got it on, with 2% left, again not charging...tried to repush the connector towards the center and now i cant get my charger into the phone, maybe overbend it...what to do?...
I have a strange problem, my Gnex does not charge the battery, first i thought that it was the battery so, I tested the battery on other phone and it charged just fine, and then i ordered the usb/charging assemble from ebay and replaced on my gnex, and still not charging the battery, but when i connect the phone to the pc it recognize it immediately, but still won't charge the battery, anybody has an idea of what my problem is?? and how can i solve it?
Please help!!!
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?
I have recently purchased the A50 and love it. However, this morning I woke up late for work as my phone had switched off during its overnight charge. There was no way to turn it back on until at least 10 minutes after taking it off charge and frantically running to work. Once the phone was on, it had 100% battery.
Does anyone have any idea why this happened? Could it be an overheating issue?
This has never happened to any other phone I've owned.
I have been charging with the cable the A50 comes with but with the S7 plug. Could that be the culprit?
If that's the case I will just use the A50 plug itself.
I have looked everywhere for an answer. This only happened today and may never happen again but I would like to know other people's opinions.
Don't know why this happened,bug somewhere,software update,don't know,but do you really need to leave the phone on an overnight charge,
The treakle charge at 100% is known to cause heating issues, and I hear the a50 is not the most durable phone,.
Strange that it would just turn the phone off completely
manus31 said:
Don't know why this happened,bug somewhere,software update,don't know,but do you really need to leave the phone on an overnight charge,
The treakle charge at 100% is known to cause heating issues, and I hear the a50 is not the most durable phone,.
Strange that it would just turn the phone off completely
Click to expand...
Click to collapse
To be honest, it could have been as simple as electric fluctuation. I have no idea.
I didn't charge last night as I as slightly reluctant to do so.
So far, the phone is working flawlessly and hasn't restarted or shut off on its own. I will eventually charge it once the power drops to almost 0.
Will update so as to let everyone know in case there are similar issues out there.
daveydoo said:
To be honest, it could have been as simple as electric fluctuation. I have no idea.
I didn't charge last night as I as slightly reluctant to do so.
So far, the phone is working flawlessly and hasn't restarted or shut off on its own. I will eventually charge it once the power drops to almost 0.
Will update so as to let everyone know in case there are similar issues out there.
Click to expand...
Click to collapse
sounds like a bad battery in the phone, you should return it. i left it for overnight charging(forgot to remove it) and nothing happened.
kkarakk said:
sounds like a bad battery in the phone, you should return it. i left it for overnight charging(forgot to remove it) and nothing happened.
Click to expand...
Click to collapse
When it happened to me it was the second time I had charged over night, the first time was fine.
I haven't done it since and so far the phone has been fine.
During Update my phone A50, I just press Power button+Vol down button together. After that my phone was off and can not on till now. I tried to press vol up + power button together but it did not work. Can you please Help.
My Samsung A50 just went off by itself after power went off and has refused to come up. Truth is i have charged it several times using this same power and i can tell power is almost stable except that i am using a different charger head to charge for some time now. Wont sill come up, any help or suggestion?
We have several of these A50's and up to now we had 3 of them with this problem.
At the moment that it refuses to turn back on i noticed that the back of the phone is warm , between the top of the phone and the word SAMSUNG . The rest of the phone is cold.
I left the phone alone for about 4 hours without power cable plugged in , after those 4 hours i plugged it in and after a minute it started charging with a indicator of 0% .
You can also try a forced reboot ( hold volume up and down + power button for 5 sec )
Did anyone manage to solve this issue? My girlfriend's A50 has shut down twice overnight now, and the only way to turn it on is by pressing power and volume down for 10 seconds. She has the May update.
Same issue here, i reset my phone to factory settings then install all of my applications and since do that, the issue doesn't occurs any more till now (1 week)
Same here!
Same situation here!
It turned off during the night 3 times now!!
I was late to work The first time, now I have to activate the alarm on my wife's phone, because I don't trust this one anymore.
To turn it back on, you don't need to wait 4 hours, you just have to press power and volume down.
Samsung has to do something about this!
manssons said:
Did anyone manage to solve this issue? My girlfriend's A50 has shut down twice overnight now, and the only way to turn it on is by pressing power and volume down for 10 seconds. She has the May update.
Click to expand...
Click to collapse
That doesn't sound like it's actually turning off. More like it gets stuck with screen off and you're making a forced reboot with the button combination.
tys0n said:
That doesn't sound like it's actually turning off. More like it gets stuck with screen off and you're making a forced reboot with the button combination.
Click to expand...
Click to collapse
Yeah that might actually be the case, and it's completely hung since alarms won't go off. Apparently it does not seem like an isolated case so I guess we'll see what the store says.
Same situation at my A50 to. No notifications,no reaction, no alarm, no reacttion after simple power button press,only black display. It get alive only with described buttons combination-power+vol up .
The problem occure only after night charging time, in the morning.
I was advised not to leave on charge overnight. I have just got this phone and was asking live chat about something else and she mentioned new smart phones did not require full overnight charges and unplug as soon as it’s finished charging.. also that fully discharging battery to 0% is not recommended either and should be charged around 20% to increase the life of the battery. I think I will try that advice. Always had Samsung phones and been happy with my S5 for many years..but it’s very outdated and decided on upgrade but can’t justify the price of S10 lol.
So, I bought my HTC 10 sometime last week and I love it, I got the red 2PS6500 version. I have been excited to see people like Leedroid and Faygi working to make this phone so amazing. But I always had a rough battery experience.
At first, symptom was fast draining. It rarely got 3-4hrs SoT, but some days I had good battery life. More recently, I noticed that when using my camera around the 20-30% range, the phone would shut down, and I'd see that it was at 0%-1% and not booting.....
From my research here, this seems like I could try to re-calibrate my battery. I had it charge (powered off) for 2 minutes, then I held both volume buttons + power while still charging. I then let it go up to 100%. When I turned it on, the percent showed 70%. So while it was on, I let it go to 100%. After that, I unplugged it, and rebooted it. It went down to 70% again. I repeated the full charge to reboot. This time, I was 99%. I wanted to reboot once more, just to close the gap from 99% and 100%. USB connection is clean and good, cable works on other phones.
Then the phone just stopped working. It no longer boots up, no LED's, no vibration, buttons don't function no matter the combination. I tried connecting it to my PC and I get nothing recognized. Cannot get the screen on at all.
So I am guessing two things:
(1) Battery might have fired and the connection to the board is gone. I might have bought one that already had issues and this was the last leg of it.
(2) Motherboard damage from the battery? This is something I'm afraid of if I go and replace the battery and I still have issues with it not turning on.
I was hoping anyone with experience might be able to confirm anything I mentioned with the battery issue, and if replacing it solved that.
TL;DR, HTC 10 no longer powers on, shows no sign of life. Battery previously had calibration issues. Should I replace the battery, and then it will turn on, or could there be further damage. Most situations I found were from users that were still able to turn on their HTC 10.
I've replaced my battery recently. I had the same deal. I had to use the actual charger plugged in for a while and it eventually came on
Yayodroid said:
I've replaced my battery recently. I had the same deal. I had to use the actual charger plugged in for a while and it eventually came on
Click to expand...
Click to collapse
Thank you for responding. My issue/question was more about "if" i replace the battery, will it solve my issue. I have not replaced it yet, and I ordered an OEM battery in hopes that should fix my issue. So hopefully a new battery will allow me to boot up my HTC 10 again.
At least I still have my HTC m8, and I'm replacing it's battery too (swelling and making the screen bulge). The community around the M8 is still strong and there is even the latest RR pie available too.
I gotcha. Sorry I have a terrible habit of skimming and then assuming. Mine was similar but not exact. I was always able to get it to show life after it was on charge for a while.
When I replaced the screen once, i forgot to unplug the battery from the board before I started. I got it all back together and it wouldn't turn on. It wouldn't show that it was charging. So I went in and unplugged the battery and plugged it back in. It acted after like it never happened.
Yayodroid said:
I gotcha. Sorry I have a terrible habit of skimming and then assuming. Mine was similar but not exact. I was always able to get it to show life after it was on charge for a while.
When I replaced the screen once, i forgot to unplug the battery from the board before I started. I got it all back together and it wouldn't turn on. It wouldn't show that it was charging. So I went in and unplugged the battery and plugged it back in. It acted after like it never happened.
Click to expand...
Click to collapse
I hope after I replace the battery, it finally boots up. I had to order a new heat blower because mine broke. I'm surprised after I charged it to 100%, it hard bricked and died. I have a feeling th battery was the culprit, since it was always bad at holding a charge....and even more oddly enough, using RR pie on my HTC M8 is FASTER than it was using RR pie on the HTC 10. That battery was very likely affecting my overall experience.
Please do update us with your progress and conclusion. It might help the next person
Yayodroid said:
Please do update us with your progress and conclusion. It might help the next person
Click to expand...
Click to collapse
DEFINITELY. I hope nobody has the issue I am facing at the moment.
UPDATE
So I replaced the battery, was very easy to do with patience and the right tools.
AND, it did not fix my issue. As I opened the phone, I noticed stickers on the chips from a company that apparently did work on it prior to me buying it, and the work they did was bad. I think it is safe to say that the motherboard has suffered severe EDP damage, and it would not be worth the cost to fix it. Burnt pins near almost every chip.... It was so happy being a part of this awesome group, working on the HTC 10 and having Fagyi making the amazing Pie roms. I will be selling my HTC 10 for parts on Ebay if anyone is interested (1 new battery, 1 lcd screen in excellent condition, both cameras, charging ports. . . basically everything but the motherboard that is dead)
So, I am torn between three options. Since my HTC m8 is fixed (top third inch of touchscreen no longer works with tough), I can keep the HTC m8 until it dies and replace it's digitizer/LCD. I can buy another HTC 10 and hope it will not be a crappy one, or I can save and get the HTC u11 (that red color looks so nice!) or go for a Samsung Note 4. I've had the M8 for about 5 years now and it's running RR-P like a brand new phone. I am so sad my 10 just died like that. I was so spoiled with the HTC 10, it was the best phone I ever had. I'd love to have a new device with tons of potential for modding in the future.
Any recommendations then: any device will be modded like crazy, especially with RR or LOS
- keep M8 / replace LCD+Digitizer
- buy HTC 10
- buy HTC U11
- buy Note 4