Possibly bricked E4GT. Advice please. - Samsung Epic 4G Touch

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?

Related

Why does my phone act like it's plugged in all the time...

Just got my phone yesterday. Running Calk's 2.7 and ICS theme, set dpi to 160, looks and runs awesome. However, it always thinks it's either charging or plugged into USB. the red LED never wants to turn off. how can I remedy this problem?
Possibly try turning it off, booting to recovery, clearing cache/dalvik-cache, and then clear battery stats
Was it like this prior to rooting and custom rom?
Apk, that didn't do it.
yes, it did the same thing beforehand. Except takng out the battery solved the problem once.
Get it exchanged ASAP. This is a defect with the USB port. Has NOTHING to do with software. I was outside of my 14 day return and Sprint made me send it to Samsung to get fixed. $7 jig and two weeks later it was fixed.
With my tech background I would say check the charging port. Could be a metal shaving or *gasp* corrosion!
Sent from my SPH-D710 using XDA App
my phone sort of has the same issue...it charges fine but i cant get it to connect to my computer..my phone thinks it still charging yet i have it plugged in my computer it doesnt give me the option to switch it to usb mass storage..
Got it on Craigslist, no exchange possible.
Dioscorus said:
Got it on Craigslist, no exchange possible.
Click to expand...
Click to collapse
Shouldn't matter. The phone has a one year warranty from Samsung. I bought my wife an Epic on craigslist last year and had it repaired under warranty.
Sent from my SPH-D710 using XDA App
Yup. I had the same problem. I think it is related to the USB port (from reading a few SGS2 threads). I took it to the Sprint Store and they said the USB port looks good. They reset it and it still acted that way. However, 2 hours later the problem is gone. They ordered me a replacement so I'm still going to take it because who knows why the problem starts. I did have Calk's rom and also have the battering monitoring widget by 3C and I had cleared the battery stats multiple times prior to the symptoms starting. Just proving as many clues as possible...
What do you mean by reset?
Funny I see you have this problem (not really funny) because I noticed the same thing last night and just figured it was Rom related.
It sucks... can you give more details about the reset process? Soft reset?
and bump...
Dioscorus said:
and bump...
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=1344882 and see if it helps.
Sent from my SPH-D710 using Tapatalk
no dice
I had the same problem.
The red light was on all the time, only went out when I got a text. If I pulled the battery the phone would show like it was charging as soon as I put it back in. It would show the battery animation on the screen not plugged in.
After a battery pull the phone would also not boot using the power button, had to boot to recovery and boot from there.
Took it to sprint, they gave me a new battery. Solved the problem only until phone was plugged in to charge. Then started all over again.
Turned out to be a problem with the USB port and they ordered me a replacement.
got it fixed! looks like the pcb on the port was sitting too close to the lower edge of the phone. pushed it up gently and now it seems to be working. thanks for the direction, nivron.
my other concern is that battery life sucks ass. drains really quick (at the rate of ~6%/hr!). again, running calk 2.7 + ics theme. also, taking out the battery seems to reduce the life 20%. what's the deal...
Hmm, now the USB cable needs to be at a certain angle for the phone to charge. Is there any way a Sprint store could furnish a replacement for me?

My Samsung Galaxy Nexus won't turn on

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?

[Q] No power, no charging LED, no Fastboot

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!

Extreme battery drain

So my phone was at full charge. Took it off the charger and ate dinner. I was not using my phone and noticed it was extremely hot. Battery was down to 40 percent in less than an hour. I reboot phone thinking it was a wake lock issue. Phone battery dies and drains to 0 percent. I had to plug it into a charger in order to turn it on. From here I notice that the phone gets extremely hot and charges extremely slow. It's been charging for an hour and only 5 percent has been charged. I think maybe it was my ROM or a persisting wake lock. I wipe my phone and clean flash cyanogen. Phone still getting hot and charging extremely slow. Could I possibly have a malfunctioning battery or something?
Sent from my Nexus 7 using Tapatalk
Woke up in the middle of the night after about 4 hours of charging. Battery was at about 40% or so but the phone was the hottest it's ever been. I decided to turn it off and unplug it from the charger. Woke up this morning and it's officially dead dead. The orange/red LED won't turn on when plugged into the charger and I can't turn it on or try to boot into recovery.
I'm going to take it to Costco and see if I can get a replacement since I'm in my 90 day period. This certainly has to be a manufacturer's defect since I did not have water damage, drop my phone, overclock, or anything risky.
Sent from my Nexus 7 using Tapatalk
There have been a few people who have had the same issue. I haven't read of a fix or even what causes it.
Sent from the One and Only
Check and see what is using the battery. A day ago Google play store was the cause of battery drain for a lot of people.
It's not just a One its a tiKtaK One
Well my phone can't even turn on right now - it is literally a dead phone. I'll check one more time before trying to exchange it at Costco. I don't think it's Google play because I did a full wipe and fresh install of Cyanogen. I did not even setup my WiFi and put my phone on Airplane mode while charging. It was still running hot and charging extremely slow.
Cares said:
Well my phone can't even turn on right now - it is literally a dead phone. I'll check one more time before trying to exchange it at Costco. I don't think it's Google play because I did a full wipe and fresh install of Cyanogen. I did not even setup my WiFi and put my phone on Airplane mode while charging. It was still running hot and charging extremely slow.
Click to expand...
Click to collapse
I had this all happen to me a few weeks ago. Was inexplicable. Not sure how it happened while the phone was OFF. Brought into Verizon, they sent me a new one, without much hassle.
dbornack said:
I had this all happen to me a few weeks ago. Was inexplicable. Not sure how it happened while the phone was OFF. Brought into Verizon, they sent me a new one, without much hassle.
Click to expand...
Click to collapse
Just got back from Costco. Got a brand new phone without questions asked. Great service.
This is happening to me again right now..
I'm in luck though, as I'm on a charger and around 50%.. I went from about 100% to 11% in 20 minutes this morning. I've been running SlimKat for about a week now, and have had no issues.
I have no idea why this just pops up at a seemingly random time.
Now, I've wiped the entire phone, installed BoneStock, and it's still persisting.
What can I try to get this fixed?
I've held PWR and Vol+/- to reset the phone.. but this is still occuring.
Anything? Anyone?
dbornack said:
I had this all happen to me a few weeks ago. Was inexplicable. Not sure how it happened while the phone was OFF. Brought into Verizon, they sent me a new one, without much hassle.
Click to expand...
Click to collapse
I'm having a similar issue. I'm worried that I won't have enough battery to return the phone to stock and relock the bootloader, which is what I meant in the other thread when I said unable to return to stock.
sdot_sd said:
I'm having a similar issue. I'm worried that I won't have enough battery to return the phone to stock and relock the bootloader, which is what I meant in the other thread when I said unable to return to stock.
Click to expand...
Click to collapse
Have you tried turning it off and plugging it into a wall outlet for a while?
What recovery are you using?
If I was you, I would probably plug it in with it off, hope that I get enough juice into it over a period of time, that I could flash the full odex stock rom.
The Faux Hboot in my Red Text Hex Edited hboot thread, so that it appears as though it's s-on and locked.
Flash stock recovery and warranty it to HTC. They should just take it apart and put a new battery in and send you the same device back.
Those are pretty much the steps I would take if I was in your shoes.
Hope that maybe that helps a little and that you can get enough of a charge to do so.
santod040 said:
Have you tried turning it off and plugging it into a wall outlet for a while?
What recovery are you using?
If I was you, I would probably plug it in with it off, hope that I get enough juice into it over a period of time, that I could flash the full odex stock rom.
The Faux Hboot in my Red Text Hex Edited hboot thread, so that it appears as though it's s-on and locked.
Flash stock recovery and warranty it to HTC. They should just take it apart and put a new battery in and send you the same device back.
Those are pretty much the steps I would take if I was in your shoes.
Hope that maybe that helps a little and that you can get enough of a charge to do so.
Click to expand...
Click to collapse
OK got it powered off and charging now. I've heard a lot of horror stories about HTCs customer service, any reason you would deal with them directly instead of VZW?
sdot_sd said:
OK got it powered off and charging now. I've heard a lot of horror stories about HTCs customer service, any reason you would deal with them directly instead of VZW?
Click to expand...
Click to collapse
I've heard good things about HTC's Customer service, compared to Verizon's especially.
Not to mention, Verizon will wanna know if you have Insurance, will maybe make you pay a deductible.
Even if they don't, you will likely get a refurbished CLN replacement, which may or may not exhibit it's own issues of some kind.
I would rather have my own device fixed and sent back to me, then receive someone else's fixed device that may have had a bigger issue or stress to parts not yet known.
Just how I feel about it, and I do not much care for Verizon, other then for actual phone service.
You are more then welcome to try your hand with Verizon if you would prefer.
I also have a Blue One, so Verizon wouldn't do much for me...
sdot_sd said:
OK got it powered off and charging now. I've heard a lot of horror stories about HTCs customer service, any reason you would deal with them directly instead of VZW?
Click to expand...
Click to collapse
My wife got a DNA with a bad cable and I called htc. They didn't fuss or ask any questions. They took my info and sent a new one. It was much easier than dealing with vzw.
Sent from my HTC6500LVW using Tapatalk

[Q] Phone gives no response, but heats. Fixable?

Been coming here a while.. forums are nothing new to meh.. we'll skip the fact I just made this account and immediately made a thread ^^;
We'll get right to the details:
Had her since Autumn last year. Best phone I've ever used. No problems besides freezes I know I caused, etc.. never an issue. Til about October this year. Seen similar issues, looked for two months and found nothing close besides a Nexus 7 that physically needed its battery pulled for it to power on again. Anywho, here's how the moment went down: In the span of an hour or so, my GNex had crashed on me about three times... normally it'll do that maybe three times a day to three a week, depending how hotplugx on leankernel felt that day (having only one core on 90% of the time was pretty sweet). Was running the PA 3.99 based "Built With Love" ROM- the first build to incorporate any Saber stuff afaik- and the flat out 8.0 version of leankernel. Now.. the laast time she froze, the battery was already near dead, so when I popped it back in I plugged it up to the charger. All going as normal, right? Done this plenty from tinkering with kernels and seeing which android ROMs & versions I could hop back and forth to without wiping (had the current said setup for a month straight, surprisingly) Nope. It brings up the charging logo with the lighting bolt in the middle of the battery... and freezes there. Pulled out the cord, waited a bit and everything. Nada. Freaked out, I popped the battery. Went to put the battery back in and power it.. nothing. Okay, maybe that just killed the charge. Nope. Power cord fails to bring up any kind of light or charging animation. No screen activity. Will not boot into odin, recovery, or anything.
The ONLY signs of life still coming from this phone, are heat when it's on the charger, heat after 'USB jumping' the phone -after disconnecting the cord as well, and for at least two hours it continues producing heat- (had to do that when I first got it from Google) , and if I plug her into the laptop via USB WITHOUT a battery, it'll show as "OMAP 4440" for a split second in device manager.
Any more details will come from answering questions. As this happened over two months ago, I'm a little fuzzy on outright recalling details.
Cannot find this problem elsewhere at all. Either it's rare or I suck at looking around.
So I'm coming to you guys. Is she bricked? Stuck in charging.. idk what. Toolkits won't detect a device either, even after the USB jump when I know the battery is discharging and the phone is -technically- powered on.
If you guys could help me out for Christmas, even if it's to tell me she's busted, it would be so indescribably appreciated... <3
[Edit] Nabbed this really quick (attachment). Holding the button combo for download/odin mode has Windows searching this.
No battery inserted, as the dialog disappears and the taskbar pops with a bubble saying "device not recognized" etc. when the battery is put back in or is simply in it when plugged into the laptop.
Also to note: a third party battery yields the same results as the stock one. What kills me is Windows can see it, but aside from that and the heat production, it's essentially dead. What gives? :c
Shameful bump. Need to know if it's completely bricked, or possibly a hardware issue that's repairable or not.
Had to save up for over a year for this phone. Really need to figure out if it's gone or not. If it is, then I'll need to start saving for an N5, which I consider a downgrade ._. Can't beat the community support though, and that extra screen space :3
Aside from irrelevant blabble.. any answer would be appreciated. I can provide any additional information if need be, as well.
Have not seen this issue anywhere.
Bump..? :c
There's almost nothing on charge animation freezes. And what there is, the owner was able to boot their device with some simple workarounds.
If there's anyone who knows what's going on, even to tell me I'm a retard who bricked his phone, please do. Please.
Can't even afford glue to put my shoes back together. Saving up for another phone is impractical this year and probably next as well :\
Would I need the OMAP 4440 driver and some other stuff? If there's some way to push a boot.img to /boot while the phone is in this state, that would fix it..
I'm somewhat sure, at least. Since the kernel's in charge of that from what I understand.. any ideas?
Search for OMAP flash. I think your phone can be revived. i can't search right now but i believe there are some tutorial about OMAP flash of galaxy nexus. Good luck

Categories

Resources