Related
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
zander21510 said:
So I'm watching tv, and I plug in my phone to charge it a bit because the GPS had gotten stuck on this morning and I burned my battery down to 40%. All of a sudden I hear it buzzing over and over again...like a reboot loop.
So I pull it out of the charger, pull the battery and let it try to boot. Gives the samsung screen for a moment, then flickers, and again to the reboot loop. Holding down power for 10 sec makes it do the same thing, I can't force it into recovery or DL mode without it bootlooping either! At one point I was able to get to the download mode screen, but just 3 seconds and the screen goes black, and back to bootlooping.
I literally did nothing to it. Only thing I did different today was the GPS got stuck (which it has done before), I rebooted the phone, then when it booted again I went ahead and just shut off the GPS. But this was like 20 minutes before this started happening.
So what can I do? Right now its plugged into my computer charging while off, seems to be the only thing it can do without bootlooping.
Running CM9.1 Nightly 9/3 with included kernel and LC8 radio (I think)
Click to expand...
Click to collapse
My first guess is your battery is shot. i was gonna recommend the power button failure but if its staying off it might not be that. but id let it charge fully then try to boot up.
Thanks, oddly after a bit of messing around finally got it to boot up. Immediately backed up in CWM....seems to be acting OK now. Idk what happened...
i'll guess, the USB connector got short-circuited when you plugged in, and it caused a cascade failure that fried the SD card or something else inside the phone
there was a factory defect back then with the old SGS 1 (i9000m) model, they fixed that after the 3rd batch, everyone with an old phone from 1st and 2nd release batches, were able to exchange i for a new one.
however in your case, that's not a factory defect, but you plugged it wrong (my guess)
because it has happened to me before when i plugged it in, but the battery was still not charging even after several minutes, yet the phone was getting really really hot
then i unplug, and plug it back in and got the sound feedback "tuu tuud" and then it was actually charging after a few minutes
the first time around even though the charging icon changed, there was no feed back sound, and that was the key, it was not plugged in properly.
so after that time, i always made sure to verify to make sure the phone was plugged in properly and not just relay on he visual icon.
check back after a few minutes, to make sure the phone doesn't get very hot, and it actually increased 1%
It happened again today! After a full charge overnight and no problems for the day up to a little while ago, I opened my email app, it froze, then proceeded to start boot looping. I'm in class so I don't have my computer to try to bring it out of it...so yeah that sucks...
I do remember when I got it to charge yesterday it showed it was charging for 20-30 minutes, but after I "revived" it, I found it hadn't charged at all.
I have been using a Nokia USB cable to charge my phone since I got it, because it was longer than the cheapie Samsung cable that came with it...but it hasn't ever caused problems before. And it charged just fine last night.
How long is the warranty on these things thru tmobile? I may just swap it out while I still can.
Also on an unrelated note, I upgraded to the LG3 radio because I was meaning to anyways...
I pulled it out of it again! This time I held the power button while putting the battery in, when it vibrated I let go, it vibrated again, showed the Samsung logo, and then booted like normal
May I ask what rom are you currently on?
datrapstar said:
May I ask what rom are you currently on?
Click to expand...
Click to collapse
CM9.1 nightly 9/3 with included kernel
It did it a third time during class while it was in my pocket, the power button trick didn't work this time, I had to pull the battery after the samsung logo, plugging it back in to get it to boot...but...
near the end of the CM9 boot animation, when it vibrates and the auto brightness kicks in, it started it again! I have yet to revive it...
This is a bit upsetting because I had just got CM9 the way I liked it and I don't exactly have the time right now to mess with warranty and a new phone...I would like to fix it.
There are about 20 different threads on here on how to revert to stock...let me as a last ditch try to revert to stock and see if it keeps doing it...unless somebody has any ideas...
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
zander21510 said:
I was working in recovery mode, i super-wiped my phone to see if installing a ROM from scratch would help, and my phone even does it in recovery mode. Warranty time.
So whats the fastest way to restore to stock? Who knows how long I will have after reviving it before it breaks again.
Click to expand...
Click to collapse
Here you go!!
http://forum.xda-developers.com/showthread.php?p=30832325
Sent from JMT Goodness
Well, finished playing stupid for T-Mobile, in two weeks I will have my replacement T989. Now all that's left is returning this thing to stock before it starts acting up again.
And my temporary replacement phone?
HTC Dream, aka the G1, the first Android phone! Lol what a difference...GB feels like a dinosaur...
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
datrapstar said:
http://forum.xda-developers.com/showthread.php?t=1513359
[HOWTO]Restore to Stock/Recover from a Bad Flash. Could try the last 3 pages on this thread. That will help you go back to stock without an issue. Hell might make you wanna keep your phone if you can get it to work again.. good luck
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Thanks! got it all done, back to ugly, ugly stock lol...and just when I thought maybe I would have to brick it myself it did the reboot thing again...so pulled the battery and there it sits factory reset.
Hi all,
For the last two to three months, I've been running a Universe ROM on my E4GT. Other than an occasional quirk, the phone has been working very well. I noticed that my phone didn't seem to be connecting to my home WiFi, so I put it into Airplane mode, and then took it out of Airplane mode. Instantly, it connected to my WiFi with a MUCH better signal After checking emails on the phone, I set an alarm and went to sleep. I woke up without the alarm since it did not go off. My phone appeared to be off. Holding the power button resulted in the blue LED charge light flashing, but the screen did not come on. I pulled the battery and put it back, thinking that the phone had some odd-ball software glitch that made it turn off in the middle of the night. When I hit power, the blue LED turns on, blinks, and that is all that happens. Once and only once since this started, my screen showed the boot animation, but did not get past that.
Because my screen turned on ONCE, I'm really hoping that I am soft bricked and not hard bricked. It does seem VERY odd for the phone to become bricked after working fine on this ROM for at least a couple months. The only change I made in recent time is to change a governor in ExTweaks from Hyper to Ondemand. I suppose that could have somehow caused this.
I stopped by a Sprint store, but they would not help as I do not have insurance and the phone is out of warranty.
Do you think making a USB jig or buying one may help? There is a Radio Shack close to where I live. And I have an extra USB cable I can take apart.
If that fails, should I send the phone to mobiletechvideos.com for their JTAG repair? It costs $50 plus shipping to them, but that is still cheaper than buying a new phone. If it came to that, I'd certainly hope they could fix it.
The fact that the blue LED light comes on seems like a decent sign of some life. While the battery animation does not come on, the light does.
Thanks for reading and offering any advice/suggestions.
Can you get into recovery or odin mode?
bigdaddy619 said:
Can you get into recovery or odin mode?
Click to expand...
Click to collapse
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
anindrew said:
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
Click to expand...
Click to collapse
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
bigdaddy619 said:
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
Click to expand...
Click to collapse
Thank you! I'll post here if I get that to work or have an alternate solution.
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Brick
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
Thank you very much for the reply. My phone was having a strange issue with connecting to my home WiFi before I put it on the charger for the last time. I wonder if that was a tell-tale sign that something was up.
I went to the Sprint store closer to where I live and explained what happened. They didn't give me any argument at all. Their tech checked out my phone, but couldn't get it to power up at all. They ordered a replacement E4GT (might be new; might be refurbished) for me for $35. I should have it by Friday. I was surprised by how helpful they were. Apparently, they have see this issue occur on some other Android phones as well.
What is the Chainfires app? Does it identify if you have the "older" chipset which can cause the brick issue? That must be what you mean by "GotBrickBug," right?
Since I'm eligible for an upgrade in June, I think I'll just use the stock ROM to avoid any possible issues. I wonder if the GS4 will be out then. It's always interesting to see what the hot new phone is going to be when you're ready for an upgrade.
Again, thank you to everyone for the helpful replies!
Surprised they even had you pay but I'd have paid $35 also if they'd asked me too.
You should get either new or new board at least.
Here's Chainfire's thread and app in OP. By the looks of it, my chips firmware is updated and as much as I've tested and flashed in the last couple weeks, it's holding up great. http://forum.xda-developers.com/showthread.php?t=1693704
My first clue was that my phone was having problems being read by my PC. Couldn't see either the onboard usb or my external usb. It was intermittent and within a week it was gone.
Sprint has been seeing this problem for sure and in Chainfire's thread, Samsung is well aware.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew said:
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Click to expand...
Click to collapse
Sounds like the h/w took a dump on you - the phone replacement was probably the only route left. By any chance did you leave it charging and/or in a location that allowed it to store heat? (Like a blanket, foam cushion, etc)
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Update the next day: I found this thread, which is essentially a match for what I was experiencing. That one ended with a wait-it-out approach, and I basically did the same. I left it plugged in overnight, even though it appeared not to be charging at all (stone cold, no red light). In the morning, it was still all but dead, but I popped out the battery again (I had done this many times before), replugged it into power, and then it charged normally and completely for the first time since the incident. Moral: don't let the phone go below 15%, and if you do, plug it in ASAP. Don't ignore it overnight, even if it's powered off (maybe especially).
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
You're right - folks, this is not the eMMC bug. Let's just clear that up. If you need further information on that you can refer to the discussion thread on that bug and all the research that several folks have put into it.
When I first got my E4GT there was talk of a BLOD or "sleep of death" where the phone would not come back on. Wasn't the eMMC bug. Most people had a low battery so it was thought the batteries were too low and that it booted and messed up the bootloader. Others thought they overheated. Problem is without any way to diagnose the problem it's hard to come up with a "true" answer.
Perhaps a JTAG could revive the phones. Odd that even if plugged in that nothing is happening. But sometimes h/w really can just go south and trash a phone.
I highly suggest backing up your internal usb drive as frequently as possible because I lost a lot of photos that I never transfered, thanks to Samsung and my hardware taking a crap. Emmc blue light bug really sucks, believe me...
---------- Post added at 03:39 AM ---------- Previous post was at 03:29 AM ----------
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
Doesn't sound like emmc at all. All you will have is a blue light and that's it. If you saw ANY display, it's probably a battery and charging issue. You'll know the bug when you don't see anything but blue and no display at all.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew, how did it all turn out?
Hi guys, TMO Galaxy S III. I was running Cyanogenmod 10.2.
I was driving home from a road trip to the race track, used GPS on my phone as it was plugged in charging. Turned it off as soon as I got to a familiar place. Put the phone in my pocket after I got home. Pulled it out 30 minutes later and it's turned off.
Efforts to turn it on failed. I plugged it in (even though it had batter left before it died) and nothing happens. No LED, no battery charge graphic, no vibration.
I switched batteries. I switched plugs. Tired to reboot into recovery. Nothing. I can't get Kies to recognize it.
I didn't drop it. No water damage. Any ideas?
If after putting battery back in, and unplugged, you get zero response from pressing power, then yes it sounds like it's dead
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
If after putting battery back in, and unplugged, you get zero response from pressing power, then yes it sounds like it's dead
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Yup. Zero response. The only way I can get it to do anything, is to pull the battery, then plug in the phone w/ no battery. That gives me a red LED. Nothing else. That's the only sign of any life. No vibration or anything. Just the red LED.
Try a different battery, ?
Sent from my SGH-T999 using xda app-developers app
illegal machine said:
Yup. Zero response. The only way I can get it to do anything, is to pull the battery, then plug in the phone w/ no battery. That gives me a red LED. Nothing else. That's the only sign of any life. No vibration or anything. Just the red LED.
Click to expand...
Click to collapse
That battery may have died from heat. Navigation while plugged in tends to heat up the phone.
It's unlikely enough that I would not recommend buying a new one just to test though. Maybe go to a T-Mobile store and swap with someone just to test.
Sent from my SGH-T999 using Tapatalk
I mentioned in my first post I switched batteries. First tried my wife's battery and it didn't do anything. She tried my battery and her phone booted with 89% life.
Took it to a store and tired a new battery and it didn't work.
My wife just emailed me. Her phone was acting strange, turned itself off once. She booted it back up and it turned itself off again and won't turn back on. SHE AT LEAST gets the "Galaxy SIII" screen. She couldn't get it into recovery mode, but she could get it into download mode. I'll try and flash it tonight.
Samsung is garbage.
Sorry bout the battery thing. A few of us answer so many of these things it sometimes gets mixed up a bit and we will just add to someone else's information, not always rereading each thread...
There is a debrick thread stickied in development you may want to try. Can't guarantee anything of course, but you never know, it could end up fixing one or both of the devices.
On your wife's, take out the battery and then put back in. Wait a few to see if it attempts to turn itself on w/o pressing power.
If it does, then it's probably got a broken power button. This has become a common occurrence recently, but from what I hear is a relatively easy fix.
It may not be this though if she can get download mode to stay booted every time. But it's an easy test.
Also, when plugging into the computer, if it says something like QHSUSB in device manager, it's probably hard bricked. The debrick thread can probably help in this case.
Sorry you're having such issues with both devices. It's not the norm though. If it is a hardware failure, and you got both at the same time, it could be that one of the components may not have been completely up to par for the batch yours came from. That's just speculation though...
Sent from my SGH-T999N using Tapatalk
DocHoliday77 said:
Sorry bout the battery thing. A few of us answer so many of these things it sometimes gets mixed up a bit and we will just add to someone else's information, not always rereading each thread...
There is a debrick thread stickied in development you may want to try. Can't guarantee anything of course, but you never know, it could end up fixing one or both of the devices.
On your wife's, take out the battery and then put back in. Wait a few to see if it attempts to turn itself on w/o pressing power.
If it does, then it's probably got a broken power button. This has become a common occurrence recently, but from what I hear is a relatively easy fix.
It may not be this though if she can get download mode to stay booted every time. But it's an easy test.
Also, when plugging into the computer, if it says something like QHSUSB in device manager, it's probably hard bricked. The debrick thread can probably help in this case.
Sorry you're having such issues with both devices. It's not the norm though. If it is a hardware failure, and you got both at the same time, it could be that one of the components may not have been completely up to par for the batch yours came from. That's just speculation though...
Sent from my SGH-T999N using Tapatalk
Click to expand...
Click to collapse
For sure, I know how many times the question comes up. No worries on the battery thing.
Ok, so I was able to get my wife's phone into recovery and wiped dalvik/factory restore. It turned itself off twice over the next 30 min. But at least it boots every time.
Would you guys suggest I use Kies to factory restore? Or if it keeps restarting after factory restore via recovery, is it not going to do any good?
My wife said it's turned itself off 7 times today (over 5 hours). Ohhhh Sammy....
illegal machine said:
For sure, I know how many times the question comes up. No worries on the battery thing.
Ok, so I was able to get my wife's phone into recovery and wiped dalvik/factory restore. It turned itself off twice over the next 30 min. But at least it boots every time.
Would you guys suggest I use Kies to factory restore? Or if it keeps restarting after factory restore via recovery, is it not going to do any good?
My wife said it's turned itself off 7 times today (over 5 hours). Ohhhh Sammy....
Click to expand...
Click to collapse
I'd try the Kies to Factory Restore. You've got not much to loose that way. Keep an eye on it afterwards to see if the reboots go away.
But before you do that, can you let me know if wife's phone has its own battery or your phone's battery ? If its was your Battery that was in there when she experienced the reboots then put her own battery and check.
Perseus71 said:
I'd try the Kies to Factory Restore. You've got not much to loose that way. Keep an eye on it afterwards to see if the reboots go away.
But before you do that, can you let me know if wife's phone has its own battery or your phone's battery ? If its was your Battery that was in there when she experienced the reboots then put her own battery and check.
Click to expand...
Click to collapse
Soooo on Sunday her phone completely shut off again. It would only boot to the swirling galaxy S circle, the turn itself off (in mid animation). I can boot it into recovery and download mode, but it only stays booted for 3 seconds or so, before turning off. Not long enough for Kies/Odin/factory restore via recovery.
SO we fixed the problem permanently. I got an HTC One and she got a Nexus 5.
Samsung can die in a fire. Never again are they getting my money.
illegal machine said:
Soooo on Sunday her phone completely shut off again. It would only boot to the swirling galaxy S circle, the turn itself off (in mid animation). I can boot it into recovery and download mode, but it only stays booted for 3 seconds or so, before turning off. Not long enough for Kies/Odin/factory restore via recovery.
SO we fixed the problem permanently. I got an HTC One and she got a Nexus 5.
Samsung can die in a fire. Never again are they getting my money.
Click to expand...
Click to collapse
You may consider donating the devices to some developer on here. The community will benefit from better code.
illegal machine said:
For sure, I know how many times the question comes up. No worries on the battery thing.
Ok, so I was able to get my wife's phone into recovery and wiped dalvik/factory restore. It turned itself off twice over the next 30 min. But at least it boots every time.
Would you guys suggest I use Kies to factory restore? Or if it keeps restarting after factory restore via recovery, is it not going to do any good?
My wife said it's turned itself off 7 times today (over 5 hours). Ohhhh Sammy....
Click to expand...
Click to collapse
Well, I'm glad you solved the issue to your satisfaction. Sorry we weren't able to help in getting it fixed w/o needing to spend your money.
Good luck to the future and your new toys!
I have a G4 with Verizon and on Sunday I powered it down to swap my battery. I had about 30% left on the battery in the phone and a fully charged spare. I put the second battery in and since then it will not power on. I have tried both batteries and connected it to the power adapter... nothing happens (no lights, sounds, or vibrations). I called Verizon and they are sending me a refurb replacement but I'll need to send this one back once that device is up and running. I want to see if anyone has ideas on how to eliminate my data. I do have a SD card with my pictures so that's fine. I just want to erase everything else.
I have been playing with the phone for the past day and a half and I have gotten it to power on for a brief moment here or there. It is very random and sometimes it will show the LG splash screen and then it goes back out. I also have had it vibrate like it is turning on only not to show anything. A couple of times it has vibrated for over a minute straight before cutting back out. And while it was sitting on my desk it was rebooting itself several times earlier today until giving up. Also, when I plug it into my PC I do hear the Windows sound that you get when connecting a drive. But no drive letters appear. I am hopeful that I can get it to turn on long enough to erase everything. The phone is not rooted and is using the latest Android OS (I believe it was 5.1.1) that Verizon sent out in November.
I did not notice any other issues recently and I have swapped batteries dozens of times and never had this problem. It was powered off properly prior to this all happening. If anyone has any ideas of ways I can try to get it back on that would be great. Thank you!
Edit: Also, pressing the volume down and power together does nothing. Only way I have ever got the phone to respond in the past 24 hours is holding power for 20+ seconds and maybe it will work. But then it turns back off.
same here. dunno what to do since i bought mine used on swappa!
Sound like the hardware problem other users have had, including myself just about 2 weeks ago. If this is the case try putting the phone in the freezer for 10 to 20 minutes (I know it sounds crazy) but it worked for me and some others. I was able to power the phone up long enough to get it into recover (pressing the power button + volume down) long enough for me to wipe my data before sending it back. When I put the phone in the freezer I left the batter in and the back cover on.
jfriend33 said:
same here. dunno what to do since i bought mine used on swappa!
Click to expand...
Click to collapse
The phone is still not quite a year old. Contact LG as they have a 1 year warranty. You are running out of time though. They never asked me for a receipt as they knew within a year if it died the fix was on them.
LG G4 is a very vulnerable phone and LG’s Head of US Marketing has accepted that the LG g 4s manufactured before september 2015 had its own set of problems. Follow this guide https://appuals.com/fix-lg-g4-wont-turn/ in order to resolve your phone issues. If this doesn't help, you can send the phone for repair or replacement.
I have a N5X, unrooted, bootloader locked, 7.1.2 stock. It happened twice in the last week, the phone used to work perfectly before that. I just pick it up as usual but it doesn't turn on anymore, I tried multiple times to boot it normally or in bootloader mode but nothing happened; then the next morning I plug it into the wall the led flashes red and it reboots normally. I thought it could only happen once but it happened again yesterday night and as usual this morning it booted up. Does anybody know what the problem may be caused by? What can I do? The phone still has warranty and if no solution is found I'll send it back to Google. Sorry for my english.
I have had the exact same problem, mine only occurs when the phone is ran down to 0% and powered off. I never let that happen but I have a 3 year old son who repeatedly does it, and every time i hold my breath, praying it will come back on. Well i am holding my breath and praying once again this morning,hoping it will power back on. Do you think it could be some kind of "protected mode"to keep the battery or something else from overheating or whatever?
alezmoroni said:
I have a N5X, unrooted, bootloader locked, 7.1.2 stock. It happened twice in the last week, the phone used to work perfectly before that. I just pick it up as usual but it doesn't turn on anymore, I tried multiple times to boot it normally or in bootloader mode but nothing happened; then the next morning I plug it into the wall the led flashes red and it reboots normally. I thought it could only happen once but it happened again yesterday night and as usual this morning it booted up. Does anybody know what the problem may be caused by? What can I do? The phone still has warranty and if no solution is found I'll send it back to Google. Sorry for my english.
Click to expand...
Click to collapse
If you need the phone and are confident, try unlocking the bootloader, reflashing stock factory image and relocking the bootloader again. You will lose all the data, though.
If you can live without a phone for a while, just send it to Google/LG. Nothing else one can do imho.
When my phone was in the last steps of dying (eventual bootloop), I could disconnect the battery and it'd get farther through the boot cycle, or even once booted. Basically, after it wouldn't react to any buttons or combos, I would disconnected and reconnected the battery. Then I could give things another shot. So I'd start it, it'd make it to the colored circles, or I could boot to the recovery menu, and try some things, but at some point it would go black. Then it would not react to anything unless I disconnected the battery. Then it would react to the buttons again and eventually one of the steps would make it go black. And then take a disconnect to get another try.
It sounds like your phone may be close to dying.
By the way, I only opened it up since I was past the warranty expiration date, and LG extending the warranty to about 18 months wasn't a known thing at the time. It is actually easy to get everything apart, but hard not to make dings in the plastic cover even using plastic tools.
I would say, back up everything you can from it and expect it is going to get worse. Redoing the OS didn't save mine.