Related
Is there a way to solve this (I've got a spare battery)? Any chance of getting an updated NBH?
robuser007 said:
Is there a way to solve this (I've got a spare battery)? Any chance of getting an updated NBH?
Click to expand...
Click to collapse
if your phone truly isn't charging the battery you can always hotwire it to the positive and negative wires from a clipped usb cord.
holding the wire to the terminals of the battery for a few minutes can get you running again.
however...
I have found that often if you just unplug the phone,remove the battery from the phone and then discharge the phone (pressing power button) then reinstall battery, you can then plug in the phone to get a charge...
let it charge for 15-20 minutes and then turn it on without the powercord.
resume charging once running.
I'd advise against the hotwiring method, since unless you have a lot of experience in wiring you run a risk of damaging something due to shorting wires, put it this way, I am experienced in electronics assembly, and wouldn't try this unless there was no other way.
However my method is similar to the one mnjm suggests, I have run out of battery once or twice on android, and I pull the battery, replace it, plug in the charger, wait until the light goes out, disconnect charger, pull and reinsert battery again, power on the phone, wait until it starts the second stage of booting, ( bootanimation), then plug in the charger. Usually works fine.
Or try this:
Pull the battery, replace it, plug in the charger, don't wait wait until the light goes out, power on the phone while light is ON.
I have run out of battery many times while testing battery patch an this always worked for me.
My battery meter was acting up lately and I decided to let my phone die. Let it run out of power to correct the battery meter. It was either 100% charged or less then 1% charge.
Now it won't boot. I see the X animation and nothing happens. I just keep watching the animation. The animation keeps resetting. I hate to think that my Android installation corrupted just by letting the battery run dry?
Will it even charge if I plug it in? I wanna try reinstalling Android to get it working again.
**EDIT**
Yep, corrupt installation.
I have no idea why draining the battery would do that, but it did. I reinstalled Android and it booted again.
My phone lost charge overnight the other day and I found plugging in usb power and using the hard reset button made it boot and then it would charge up OK.
Steve
zenity said:
I'd advise against the hotwiring method, .
Click to expand...
Click to collapse
yeah...I was regretting typing that.
obviously if you are not confident in your understanding of what you are doing then AVOID playing with bare wires.
you don't have to fear electricity...
but you do need to respect it.
I know you are confident, just making sure people knew that there were potential dangers, it's not that a cut down usb lead is dangerous as far as shock hazards go, more the remote possibility that a shorted lead could perhaps cause major battery problems, since hotwiring them, while it does charge the battery, provides no short-circuit protection, it is remotely possible, (but unlikely), that this could cause fire hazards.
If I was really desperate I might do this with a zener diode rather than just bare wires.
I know we like messing with our phones, but also remember that the Darwin Awards exist because people sometimes let enthusiasm get ahead of their capabilities
Dukenukemx said:
**EDIT**
Yep, corrupt installation.
Click to expand...
Click to collapse
One of the dangers, that's why it should be fixed in the NBH, any chances for a fix, anyone working on this at the moment ?
I'm thinking of buying the motorola milestone, but it's still expensive (350 euro's).
robuser007 said:
One of the dangers, that's why it should be fixed in the NBH, any chances for a fix, anyone working on this at the moment ?
I'm thinking of buying the motorola milestone, but it's still expensive (350 euro's).
Click to expand...
Click to collapse
I can actually buy a phone with my upgrade discount, but I love my Kaiser too much to let it go. Plus it's a better learning experience when dealing with Android.
If I bought a new Android phone, I wouldn't do much of anything with it, besides use it as a smart phone.
zenity said:
I know we like messing with our phones, but also remember that the Darwin Awards exist because people sometimes let enthusiasm get ahead of their capabilities
Click to expand...
Click to collapse
I know what you mean. When I use my hammer to smash aerosol cans, I'm always careful enough to cover my face with my hand. Can't be too careful.
I kid, I kid.
Dukenukemx said:
I can actually buy a phone with my upgrade discount, but I love my Kaiser too much to let it go. Plus it's a better learning experience when dealing with Android.
If I bought a new Android phone, I wouldn't do much of anything with it, besides use it as a smart phone.
Click to expand...
Click to collapse
I've seen that the milestone is still locked, no hardspl etc.
robuser007 said:
I've seen that the milestone is still locked, no hardspl etc.
Click to expand...
Click to collapse
Seriously? By the time they unlock it, there will be a new phone to buy.
Meh, besides, I never lose my old phones. They turn into "hand me downs". My sister has my old HTC Wizard right now. If things get really bad, I still have my old Nokia NGage. Yes, I own one of those.
Same thing has just happened to me, except I can't turn the phone back on at all now.
Was running the latest Kaiser NBH from DZO whilst using Myn's rom, I had a number of issues with battery life using android with it going from 75% charge to 0% and soft resetting by itself.
Anyways this time it hasn't woken up after doing just that, it was working fine then it turned off and I can't get it back on.
It just won't power on, there is no charging light but then again that only came on once android was booted never on startup with the android NBH, it was fine with Windows Mobile.
I have removed the battery, put it back in but nothing.
Swapped out for another working battery that I have spare, but nothing.
Tried a hard reset, still nothing.
It's just not starting at all now.
The phone was working and was on the side not charging and all of sudden it turned off and hasn't come back on since.
Bit annoyed.
ST1Cl<^^aN
Stickman89 said:
Same thing has just happened to me, except I can't turn the phone back on at all now.
Was running the latest Kaiser NBH from DZO whilst using Myn's rom, I had a number of issues with battery life using android with it going from 75% charge to 0% and soft resetting by itself.
Anyways this time it hasn't woken up after doing just that, it was working fine then it turned off and I can't get it back on.
It just won't power on, there is no charging light but then again that only came on once android was booted never on startup with the android NBH, it was fine with Windows Mobile.
I have removed the battery, put it back in but nothing.
Swapped out for another working battery that I have spare, but nothing.
Tried a hard reset, still nothing.
It's just not starting at all now.
The phone was working and was on the side not charging and all of sudden it turned off and hasn't come back on since.
Bit annoyed.
ST1Cl<^^aN
Click to expand...
Click to collapse
Sorted it now, note to self and anyone else who has done this.
Usually what occurs is when the phone powers off when the battery has not been calibrated properly it requires you to do a hard reset using the stylus.
Anyway's I did that in the dark and accidentally pushed the stylus into the charger port on the phone and pushed a pin into another so It was short circuiting. Luckily I didn't damage the pins or the phone and was able to straighten it so it wasn't making contact with the other pins.
I'm happy again, its only really a test phone tbh, I have had a HTC Hero for some time now...
Best Regards,
ST1Cl<^^aN
Like most problems, it's due to the kernel. Even if the bugs get sorted out, there's still plenty of room for improvement.
Lets say the following is working 100%.
phone
GPS
3D
power management
wifi
bluetooth
USB
camera
etc
There's always a need for something. Like upgrading 3D to OpenGL ES 2.0, or getting support for ext3/ext4. That's a long way to go and very few people are willing to do it on their spare time.
In the most severe cases, people had to pool together a reward for someone to include support for something.
Considering how similar the Kaiser/Polaris/Vogue is, you could combine this group of people to get something done. There's a lot of talent, but it's spread far apart.
Hi all,
For the last two to three months, I've been running a Universe ROM on my E4GT. Other than an occasional quirk, the phone has been working very well. I noticed that my phone didn't seem to be connecting to my home WiFi, so I put it into Airplane mode, and then took it out of Airplane mode. Instantly, it connected to my WiFi with a MUCH better signal After checking emails on the phone, I set an alarm and went to sleep. I woke up without the alarm since it did not go off. My phone appeared to be off. Holding the power button resulted in the blue LED charge light flashing, but the screen did not come on. I pulled the battery and put it back, thinking that the phone had some odd-ball software glitch that made it turn off in the middle of the night. When I hit power, the blue LED turns on, blinks, and that is all that happens. Once and only once since this started, my screen showed the boot animation, but did not get past that.
Because my screen turned on ONCE, I'm really hoping that I am soft bricked and not hard bricked. It does seem VERY odd for the phone to become bricked after working fine on this ROM for at least a couple months. The only change I made in recent time is to change a governor in ExTweaks from Hyper to Ondemand. I suppose that could have somehow caused this.
I stopped by a Sprint store, but they would not help as I do not have insurance and the phone is out of warranty.
Do you think making a USB jig or buying one may help? There is a Radio Shack close to where I live. And I have an extra USB cable I can take apart.
If that fails, should I send the phone to mobiletechvideos.com for their JTAG repair? It costs $50 plus shipping to them, but that is still cheaper than buying a new phone. If it came to that, I'd certainly hope they could fix it.
The fact that the blue LED light comes on seems like a decent sign of some life. While the battery animation does not come on, the light does.
Thanks for reading and offering any advice/suggestions.
Can you get into recovery or odin mode?
bigdaddy619 said:
Can you get into recovery or odin mode?
Click to expand...
Click to collapse
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
anindrew said:
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
Click to expand...
Click to collapse
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
bigdaddy619 said:
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
Click to expand...
Click to collapse
Thank you! I'll post here if I get that to work or have an alternate solution.
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Brick
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
Thank you very much for the reply. My phone was having a strange issue with connecting to my home WiFi before I put it on the charger for the last time. I wonder if that was a tell-tale sign that something was up.
I went to the Sprint store closer to where I live and explained what happened. They didn't give me any argument at all. Their tech checked out my phone, but couldn't get it to power up at all. They ordered a replacement E4GT (might be new; might be refurbished) for me for $35. I should have it by Friday. I was surprised by how helpful they were. Apparently, they have see this issue occur on some other Android phones as well.
What is the Chainfires app? Does it identify if you have the "older" chipset which can cause the brick issue? That must be what you mean by "GotBrickBug," right?
Since I'm eligible for an upgrade in June, I think I'll just use the stock ROM to avoid any possible issues. I wonder if the GS4 will be out then. It's always interesting to see what the hot new phone is going to be when you're ready for an upgrade.
Again, thank you to everyone for the helpful replies!
Surprised they even had you pay but I'd have paid $35 also if they'd asked me too.
You should get either new or new board at least.
Here's Chainfire's thread and app in OP. By the looks of it, my chips firmware is updated and as much as I've tested and flashed in the last couple weeks, it's holding up great. http://forum.xda-developers.com/showthread.php?t=1693704
My first clue was that my phone was having problems being read by my PC. Couldn't see either the onboard usb or my external usb. It was intermittent and within a week it was gone.
Sprint has been seeing this problem for sure and in Chainfire's thread, Samsung is well aware.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew said:
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Click to expand...
Click to collapse
Sounds like the h/w took a dump on you - the phone replacement was probably the only route left. By any chance did you leave it charging and/or in a location that allowed it to store heat? (Like a blanket, foam cushion, etc)
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Update the next day: I found this thread, which is essentially a match for what I was experiencing. That one ended with a wait-it-out approach, and I basically did the same. I left it plugged in overnight, even though it appeared not to be charging at all (stone cold, no red light). In the morning, it was still all but dead, but I popped out the battery again (I had done this many times before), replugged it into power, and then it charged normally and completely for the first time since the incident. Moral: don't let the phone go below 15%, and if you do, plug it in ASAP. Don't ignore it overnight, even if it's powered off (maybe especially).
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
You're right - folks, this is not the eMMC bug. Let's just clear that up. If you need further information on that you can refer to the discussion thread on that bug and all the research that several folks have put into it.
When I first got my E4GT there was talk of a BLOD or "sleep of death" where the phone would not come back on. Wasn't the eMMC bug. Most people had a low battery so it was thought the batteries were too low and that it booted and messed up the bootloader. Others thought they overheated. Problem is without any way to diagnose the problem it's hard to come up with a "true" answer.
Perhaps a JTAG could revive the phones. Odd that even if plugged in that nothing is happening. But sometimes h/w really can just go south and trash a phone.
I highly suggest backing up your internal usb drive as frequently as possible because I lost a lot of photos that I never transfered, thanks to Samsung and my hardware taking a crap. Emmc blue light bug really sucks, believe me...
---------- Post added at 03:39 AM ---------- Previous post was at 03:29 AM ----------
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
Doesn't sound like emmc at all. All you will have is a blue light and that's it. If you saw ANY display, it's probably a battery and charging issue. You'll know the bug when you don't see anything but blue and no display at all.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew, how did it all turn out?
First of all I read all the possible posts here in the XDA forum about this problem but no one was able to help me :s
I was listening music with my cellphone than it crashed and turned of from nohting. My first thought was "Damm, it crashed!" and I removed the battery and after a couple minutes I put it back and than the cellphone never turned on again. No battery status is showing up, no leds, odin and flash mode doens't work either. I don't no what to do :s
I tried this:
◘ Unplug from USB, remove battery 5 min, put it back
◘ Odin and Flash mode
◘ Turn it on without battery on pc
◘ Turn it on while recharging
My GNexus model is a I9250 GSM.
Could you add some more details? How long the phone's been in operation, refurbished?, rooted?, your current ROM, kernel, radios, advanced kernel settings such as voltage changes, any tweaks, battery type, temperature.
This exactly happened to me on my DroidX. I spent 2 weeks trying everything to revive it including taking the phone apart before adding it to the pile and getting my current GNexus Toro.. so I know how much this sucks. I'm not an expert on phones bricking but I know that connections can go bad or come loose, especially if the phone has been dropped or other impact, components start to lose their integrity over time and voltage shorts 'burn out' op-amps. You mentioned listening to music, so I'm wandering about the IVA components burning out, which usually has voltage too high especially on boot... Hope you can get it working.
7175 said:
Could you add some more details? How long the phone's been in operation, refurbished?, rooted?, your current ROM, kernel, radios, advanced kernel settings such as voltage changes, any tweaks, battery type, temperature.
This exactly happened to me on my DroidX. I spent 2 weeks trying everything to revive it including taking the phone apart before adding it to the pile and getting my current GNexus Toro.. so I know how much this sucks. I'm not an expert on phones bricking but I know that connections can go bad or come loose, especially if the phone has been dropped or other impact, components start to lose their integrity over time and voltage shorts 'burn out' op-amps. You mentioned listening to music, so I'm wandering about the IVA components burning out, which usually has voltage too high especially on boot... Hope you can get it working.
Click to expand...
Click to collapse
Well first of all I thank you for your concern and my phone is on again, thanks to my uncle. The phone is '4 months old', I rooted last month, bootloader unlocked and I was using samsung stock rom (4.2.1 JB). Yeah, that really suck monkey b*lls. If you got the same problem as me (I really hope not) that's what you should do: First remove the battery, plug the charger and than put the battery back. In my case, It kind "shorted" the battery and my phone is back on. I was reading posts and posts and discovered that GNexus has this problem and a lot. Dunno when it can happen again but I really don't want a paperweight. Once again, thank you!
Glad you got your Nexus back up and runnning. Thanks for posting back with details after you figured out the problem and got your phone working, +1 right there. There's always a good chance this will help out someone later on. :good:
Confirmation: balums worked for me
balums uncle's solution worked for me: specifically, (1) removed USB power, (2) removed battery, (3) applied USB power, (4) inserted battery, (5) press power button.
Thanks balums!
Does anybody have technical (design/EE) insight into what would cause this?
This was starting from a device that appeared totally dead.
The battery was *fully charged* (and showed up that way immediately when the device finally booted).
I had done the obvious things of removing/inserting the battery, cleaning contacts, checking the USB power connection.
Was about to pull it apart when I saw balums post, saving me huge time.
Device is about 16 months old. Stock OS and settings. First time this has happened.
Search terms:
CDMA (Verizon) Samsung Galaxy Nexus -- SCH-i515.
Phone won't boot. Device won't turn on. Won't start. Dead. No worky.
Thanks,
Seth
Awesome! You trick worked, balums!
Interestingly I also have the standard stock version of OS and Hardware which I bought 14 Months ago (nearly to the day). I was surfing over WiFi yesterday evening and when I turned the phone off I noticed the screen getting grey for a moment, not black. And this morning the Nexus just didn't turn on.
Anyway, thanks for the solution, have a nice day!
That is very odd because my i515 also did the exact same thing and I have owned it for 15 months. I can't wait to get home and try this trick. More to come.
Drew
Thanks!
balums said:
Well first of all I thank you for your concern and my phone is on again, thanks to my uncle. The phone is '4 months old', I rooted last month, bootloader unlocked and I was using samsung stock rom (4.2.1 JB). Yeah, that really suck monkey b*lls. If you got the same problem as me (I really hope not) that's what you should do: First remove the battery, plug the charger and than put the battery back. In my case, It kind "shorted" the battery and my phone is back on. I was reading posts and posts and discovered that GNexus has this problem and a lot. Dunno when it can happen again but I really don't want a paperweight. Once again, thank you!
Click to expand...
Click to collapse
Hey Balums,
My GNex didn't turn on this morning and I was really confused as to why it would do such a thing, until I saw your post. Thanks a lot for posting your uncle's remedy!
It fixed mine!
-Fupa
bookmarked. thanks op.
Galaxy nexus wont turn on or charge.
I tried (1) removed USB power, (2) removed battery, (3) applied USB power, (4) inserted battery, (5) press power button but my galaxy nexus still dont turn on. i have 4.2.2 stock rooted. i was downloading something and my screen become weird in colors and i cent use the phone. i turn it of and now wont turn on again or charge.
after unlocking and rooting i installed this touch recovery from google play. [ROOT]Recovery Tools
Excellent! balums' suggestion helped me. I thought I had tried this before but apparently didn't quite get this in the right sequence.
The only remaining issue I have now is that when it does turn on, I've got the thunderbolt on the battery indicator, the phone says it's charging at the lock screen, but when I go to Battery under Settings it says that the battery is discharging. This effectively has my phone in a state where I can't unplug it (battery is too low but it also doesn't appear to actually "charge"). I tried replacing the Micro USB charge port PCB board and came up with the same results. To me, this seems like a problem and may indicate a motherboard or battery connection issue. I used the "Battery Monitor Widget" and it indicated that it was getting AC power. Any thoughts?
Thanks to XDA and Balum's suggestion! I thought my phone just died! It was on 70somethign % battery last I looked, connected by USB to the PC and I don't know if I turned it off and walked away for a while or if it turned off by itself, but it would not turn on no matter what I did after I got back to my desk. It is on Android 4.3 takju stock not rooted.
Thank you all again for the instructions on how to revive the GNex!
Samsung Galaxy Nexus won't power up
I got a Samsung Galaxy Nexus. I got it from my cousin and therefore don't have any information about the rooting status as well as the ROM but i guess it was running stock. The phone won't turn ON, it is not detected in the computer. No LED or any other indication. I tried the above method which worked for many people but it failed. What is special about the phone is that the upper part of the screen is heating up more as compared to the rest of the phone. Can somebody help me fix this? Is this a hardware issue?
I have the EXACT same problem as you do. I have no idea where to start to try to fix it. I took a picture, then lines went squiggly across the screen, then it flickered, and died. I cannot power it on at all. I tried Uncle's tricks. No luck.
Anyone have some ideas on what to try? Thanks.
majidkhan said:
I got a Samsung Galaxy Nexus. I got it from my cousin and therefore don't have any information about the rooting status as well as the ROM but i guess it was running stock. The phone won't turn ON, it is not detected in the computer. No LED or any other indication. I tried the above method which worked for many people but it failed. What is special about the phone is that the upper part of the screen is heating up more as compared to the rest of the phone. Can somebody help me fix this? Is this a hardware issue?
Click to expand...
Click to collapse
Also having the same problem. My Nexus has been rebooting randomly for the past week or so, and finally, this morning, it refuses to turn on at all.
It's a Verizon Galaxy Nexus running stock, but it's been rooted. I'm using the extended battery. The trick that was posted earlier in this thread doesn't seem to work for me. I've tried multiple USB cables and power sources.
I'm going to try the standard battery when I get home, but I'm not expecting positive results.
Work-around
About two months ago whenever I turned my Gnex off, it became totally unresponsive to all attempts to start again. After a lot of trial and error, I discovered that if I pulled the battery for 30-60 minutes and reinstalled, it would power on normally. I have completely wiped and rooted the phone and the problem persisted.
Today I thought about it some and realized there may be some residual charge in the phone, and my waiting period is to allow the charge to drain. To test this theory, I powered the phone down and then tried to restart - nada. Pulled and reset the battery - nada. Pulled the battery, shorted out all four pins that would make contact with the battery, reinstalled battery, and it powered right up. I have not been able to successfully repeat a fast restart when shorting out all four pins. Pulling the battery and waiting 30-60 mins still works.
Incidently about the same time, my screen has stopped auto rotating (and yes it is set to do so).
mwjoerin said:
About two months ago whenever I turned my Gnex off, it became totally unresponsive to all attempts to start again. After a lot of trial and error, I discovered that if I pulled the battery for 30-60 minutes and reinstalled, it would power on normally. I have completely wiped and rooted the phone and the problem persisted.
Today I thought about it some and realized there may be some residual charge in the phone, and my waiting period is to allow the charge to drain. To test this theory, I powered the phone down and then tried to restart - nada. Pulled and reset the battery - nada. Pulled the battery, shorted out all four pins that would make contact with the battery, reinstalled battery, and it powered right up. I have not been able to successfully repeat a fast restart when shorting out all four pins. Pulling the battery and waiting 30-60 mins still works.
Incidentally about the same time, my screen has stopped auto rotating (and yes it is set to do so).
Click to expand...
Click to collapse
What are you doing exactly to short out the battery?
galaxy nexus reboot
my galaxy nexus is about 1 year old now and this is the first time that i've encountered a problem with it. It suddenly restarted, and will take about 5-7minutes before it opens, it will be open up to the "X" logo and when it reaches the normal screen it will restart again. I don't know whats wrong with it. please help/
sethbruder said:
balums uncle's solution worked for me: specifically, (1) removed USB power, (2) removed battery, (3) applied USB power, (4) inserted battery, (5) press power button.
Thanks balums!
Does anybody have technical (design/EE) insight into what would cause this?
This was starting from a device that appeared totally dead.
The battery was *fully charged* (and showed up that way immediately when the device finally booted).
I had done the obvious things of removing/inserting the battery, cleaning contacts, checking the USB power connection.
Was about to pull it apart when I saw balums post, saving me huge time.
Device is about 16 months old. Stock OS and settings. First time this has happened.
Search terms:
CDMA (Verizon) Samsung Galaxy Nexus -- SCH-i515.
Phone won't boot. Device won't turn on. Won't start. Dead. No worky.
Thanks,
Seth
Click to expand...
Click to collapse
Thanks alot... this worked for me !!
You saved my Galaxy Nexus
Similar problem + water
Ok, so I have a similar situation I believe. My phone took a swim. I left it off and riced it. Later on after I believed it to be dry enough, i turned it on. (wow it freaking worked) After a few seconds of using the device checking screen the phone snapped off and went into a reboot. I waited until it came back and i shut it down and thought I'd let it go over night. I plugged it in and let it charge (charge icon was displaying). Everything looked good.
Fast forward. Morning time. I go to turn the phone on. Nothing.
This time the phone won't boot. Instead all i see is the white battery icon show up indicating the battery is 100%. When i plug it in to the charger i get the battery with the charging bolt, then it shows the normal battery indicator light. After that, I get nothing.
I tried the method I saw above. remove power, remove battery, apply usb power, insert battery, press power. Sadly it didn't work.
Anyone have any other ideas as to what might be going on?
Hello xba-developers!
>Device HTC One X
>Quad Core 1.5 Ghz processor
>16 GB memory
>Everything is stock, no rooting nothing.
I've been checking this forum for quite a while but just found the need to register obviously because of a problem which I cannot find solution to.
I've checked couple of forum posts like THIS and some others and they KINDA have solution but it's really vague for me and I'll explain why; the reason is that I'm a complete newbie to all this, I've never rooted a device don't even know what that means and all these custom ROMs and everything really confuse me. Plus, my computer can't pick up my phone and generally I don't quite know if the cause of my problem is the same as other posts (Even though the problem is same) which means the solution may be different.
PROBLEM
It was raining, I was outside, some moron bumped into me in the street and phone slipped out of my hand, fell into a pool of water. I took it out as soon as I could but it was all wet. I tried to turn off the device but it kept restarting it wouldn't power down! (When I pressed power off it would do just regular restart) then suddenly it started working but the thing is, BEFORE all of this battery was in 14%, after it magically started working battery was on 80% which means it must have shortened somewhere (Problem with battery). Then all of a sudden it started doing these weird things like turning on music all of a sudden, turning on screen, shutting down, restarting and so on... (The speakers pretty much weren't working but still there was music somewhere). Then it went into a boot loop, I tried to do recovery but it kept restarting even when I was pressing POWER + Volume down buttons.
Then what I feared the most, battery died. Whenever I connect to power source (no matter Computer or Wall charger) it automatically goes into boot loop, the device won't stop working at all it won't shut down nothing. Battery is out of charge and I can't charge the phone enough to do Factory Reset. I took it to Service center but they are having "holidays" because 8th march is women's day and then it's sunday...
I really hate the fact that the battery is sealed inside the phone! It becomes real headache in this situations I could just take the battery out and tried it out but NOPE, can't do that!
Plus it's my first android and it uses this mini sim card thing (which they happily shortened in the store) and I don't really have any other Android phones to use my card on since it's too small for older devices...
So, the question:
How do I charge my phone when it goes into boot loop every time I plug it in?
My PC can't recognize it (it makes the sound when you connect Flash device through USB and then in 0.5 sec makes the one when you disconnect that same device).
I just need my phone to work properly. Or at least start up!
Thanks to everyone who read this huge post and I'm really sorry if I missed one or another forum thread that describes my problem exactly (which is unlikely but still).
Thanks again, have a good day!
LizardProtection said:
Hello xba-developers!
>Device HTC One X
>Quad Core 1.5 Ghz processor
>16 GB memory
>Everything is stock, no rooting nothing.
I've been checking this forum for quite a while but just found the need to register obviously because of a problem which I cannot find solution to.
I've checked couple of forum posts like THIS and some others and they KINDA have solution but it's really vague for me and I'll explain why; the reason is that I'm a complete newbie to all this, I've never rooted a device don't even know what that means and all these custom ROMs and everything really confuse me. Plus, my computer can't pick up my phone and generally I don't quite know if the cause of my problem is the same as other posts (Even though the problem is same) which means the solution may be different.
PROBLEM
It was raining, I was outside, some moron bumped into me in the street and phone slipped out of my hand, fell into a pool of water. I took it out as soon as I could but it was all wet. I tried to turn off the device but it kept restarting it wouldn't power down! (When I pressed power off it would do just regular restart) then suddenly it started working but the thing is, BEFORE all of this battery was in 14%, after it magically started working battery was on 80% which means it must have shortened somewhere (Problem with battery). Then all of a sudden it started doing these weird things like turning on music all of a sudden, turning on screen, shutting down, restarting and so on... (The speakers pretty much weren't working but still there was music somewhere). Then it went into a boot loop, I tried to do recovery but it kept restarting even when I was pressing POWER + Volume down buttons.
Then what I feared the most, battery died. Whenever I connect to power source (no matter Computer or Wall charger) it automatically goes into boot loop, the device won't stop working at all it won't shut down nothing. Battery is out of charge and I can't charge the phone enough to do Factory Reset. I took it to Service center but they are having "holidays" because 8th march is women's day and then it's sunday...
I really hate the fact that the battery is sealed inside the phone! It becomes real headache in this situations I could just take the battery out and tried it out but NOPE, can't do that!
Plus it's my first android and it uses this mini sim card thing (which they happily shortened in the store) and I don't really have any other Android phones to use my card on since it's too small for older devices...
So, the question:
How do I charge my phone when it goes into boot loop every time I plug it in?
My PC can't recognize it (it makes the sound when you connect Flash device through USB and then in 0.5 sec makes the one when you disconnect that same device).
I just need my phone to work properly. Or at least start up!
Thanks to everyone who read this huge post and I'm really sorry if I missed one or another forum thread that describes my problem exactly (which is unlikely but still).
Thanks again, have a good day!
Click to expand...
Click to collapse
See my thread here: http://forum.xda-developers.com/showpost.php?p=50106149
I would suggest replacing the Power Flex Cable and Battery as described. Hopefully it will fix your problem.
de4life said:
See my thread here: http://forum.xda-developers.com/showpost.php?p=50106149
I would suggest replacing the Power Flex Cable and Battery as described. Hopefully it will fix your problem.
Click to expand...
Click to collapse
That seems to be exactly my problem! Thanks!
After a long day streaming Pandora from my Tab S in my car, running on battery, no charger connected, I decided to put it on a charger and turned on navigation about an hour from my destination as I was in an unfamiliar city. After about 45 minutes, I saw a bright green flash from the screen. A few seconds later, and there were more flashes and it turned off. I have not been able to get it to come back on. I have tried charging it, on a charger and on PC. I have tried every combination of home+vol up/down+power I have seen in several threads, while connected to a PC, to a charger, and not connected at all. The PC does not recognize the Tab at all, ever, during any of the manipulations.
I have seen where some have luck just letting the tab sit for a few days, and it will be miraculously revived by charging, so I will try that. I have also seen where some force charge the battery using the wires from a stripped USB cable directly on the battery terminals, and as my warranty is long past void, I will try that too.
Here's my question: If none of that works, given the description, does anyone have a good idea that it may be just the screen or the battery that may need to be replaced? Or is it more likely a motherboard issue? Is there any way of telling? Despite the heavy use, the TAB did not seem excessively hot. I have felt it much hotter in the past .
I'm a tab-a-holic, and use this thing all day, every day. I use it for work, and for reading and movies at home. I'm a little frustrated as I have yet to own any tablet that lasted two years. I really don't want to spend the money for another one right now, and, if needed would prefer to repair this one if I can save a few bucks.
And, if it's relevant, the Tab is rooted, running AOSP 6.0.
I don't know too much about this - but if I were in this situation, I'd put it in a refrigerator for about 1 minute and try booting it up.
As for the cause - AOSP 6.0 has been known to have some overheating issues on this tablet under heavier loads.
Yeah, still don't think overheating was the cause. Not gonna put it in a fridge either. ;-P
Thanks to all for your concern and helpful comments!
My Tab S is unbricked as of just a few minutes ago! I just let it sit for a few days, and then left it on a charger for a few hours today. I was not expecting anything as the battery icon did not pop up when I plugged it in. But, when I came back to it a few hours later, I pressed the power button and there was the battery icon showing a full charge. It booted up normally with no issues and is working fine.
I can't tell you how happy I am!