Related
Hi all,
For the last two to three months, I've been running a Universe ROM on my E4GT. Other than an occasional quirk, the phone has been working very well. I noticed that my phone didn't seem to be connecting to my home WiFi, so I put it into Airplane mode, and then took it out of Airplane mode. Instantly, it connected to my WiFi with a MUCH better signal After checking emails on the phone, I set an alarm and went to sleep. I woke up without the alarm since it did not go off. My phone appeared to be off. Holding the power button resulted in the blue LED charge light flashing, but the screen did not come on. I pulled the battery and put it back, thinking that the phone had some odd-ball software glitch that made it turn off in the middle of the night. When I hit power, the blue LED turns on, blinks, and that is all that happens. Once and only once since this started, my screen showed the boot animation, but did not get past that.
Because my screen turned on ONCE, I'm really hoping that I am soft bricked and not hard bricked. It does seem VERY odd for the phone to become bricked after working fine on this ROM for at least a couple months. The only change I made in recent time is to change a governor in ExTweaks from Hyper to Ondemand. I suppose that could have somehow caused this.
I stopped by a Sprint store, but they would not help as I do not have insurance and the phone is out of warranty.
Do you think making a USB jig or buying one may help? There is a Radio Shack close to where I live. And I have an extra USB cable I can take apart.
If that fails, should I send the phone to mobiletechvideos.com for their JTAG repair? It costs $50 plus shipping to them, but that is still cheaper than buying a new phone. If it came to that, I'd certainly hope they could fix it.
The fact that the blue LED light comes on seems like a decent sign of some life. While the battery animation does not come on, the light does.
Thanks for reading and offering any advice/suggestions.
Can you get into recovery or odin mode?
bigdaddy619 said:
Can you get into recovery or odin mode?
Click to expand...
Click to collapse
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
anindrew said:
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
Click to expand...
Click to collapse
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
bigdaddy619 said:
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
Click to expand...
Click to collapse
Thank you! I'll post here if I get that to work or have an alternate solution.
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Brick
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
Thank you very much for the reply. My phone was having a strange issue with connecting to my home WiFi before I put it on the charger for the last time. I wonder if that was a tell-tale sign that something was up.
I went to the Sprint store closer to where I live and explained what happened. They didn't give me any argument at all. Their tech checked out my phone, but couldn't get it to power up at all. They ordered a replacement E4GT (might be new; might be refurbished) for me for $35. I should have it by Friday. I was surprised by how helpful they were. Apparently, they have see this issue occur on some other Android phones as well.
What is the Chainfires app? Does it identify if you have the "older" chipset which can cause the brick issue? That must be what you mean by "GotBrickBug," right?
Since I'm eligible for an upgrade in June, I think I'll just use the stock ROM to avoid any possible issues. I wonder if the GS4 will be out then. It's always interesting to see what the hot new phone is going to be when you're ready for an upgrade.
Again, thank you to everyone for the helpful replies!
Surprised they even had you pay but I'd have paid $35 also if they'd asked me too.
You should get either new or new board at least.
Here's Chainfire's thread and app in OP. By the looks of it, my chips firmware is updated and as much as I've tested and flashed in the last couple weeks, it's holding up great. http://forum.xda-developers.com/showthread.php?t=1693704
My first clue was that my phone was having problems being read by my PC. Couldn't see either the onboard usb or my external usb. It was intermittent and within a week it was gone.
Sprint has been seeing this problem for sure and in Chainfire's thread, Samsung is well aware.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew said:
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Click to expand...
Click to collapse
Sounds like the h/w took a dump on you - the phone replacement was probably the only route left. By any chance did you leave it charging and/or in a location that allowed it to store heat? (Like a blanket, foam cushion, etc)
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Update the next day: I found this thread, which is essentially a match for what I was experiencing. That one ended with a wait-it-out approach, and I basically did the same. I left it plugged in overnight, even though it appeared not to be charging at all (stone cold, no red light). In the morning, it was still all but dead, but I popped out the battery again (I had done this many times before), replugged it into power, and then it charged normally and completely for the first time since the incident. Moral: don't let the phone go below 15%, and if you do, plug it in ASAP. Don't ignore it overnight, even if it's powered off (maybe especially).
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
You're right - folks, this is not the eMMC bug. Let's just clear that up. If you need further information on that you can refer to the discussion thread on that bug and all the research that several folks have put into it.
When I first got my E4GT there was talk of a BLOD or "sleep of death" where the phone would not come back on. Wasn't the eMMC bug. Most people had a low battery so it was thought the batteries were too low and that it booted and messed up the bootloader. Others thought they overheated. Problem is without any way to diagnose the problem it's hard to come up with a "true" answer.
Perhaps a JTAG could revive the phones. Odd that even if plugged in that nothing is happening. But sometimes h/w really can just go south and trash a phone.
I highly suggest backing up your internal usb drive as frequently as possible because I lost a lot of photos that I never transfered, thanks to Samsung and my hardware taking a crap. Emmc blue light bug really sucks, believe me...
---------- Post added at 03:39 AM ---------- Previous post was at 03:29 AM ----------
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
Doesn't sound like emmc at all. All you will have is a blue light and that's it. If you saw ANY display, it's probably a battery and charging issue. You'll know the bug when you don't see anything but blue and no display at all.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew, how did it all turn out?
Hey, I really need some desperate help.
So I have a Canadian Note 2, SGH-I317.
It has no SIM card inside it, and it is just connected to wifi.
I have flashed 2 Custom ROMS before on this phone.
The first one, was a 4.4.2 Homemade t0lte ROM.
It worked fine for about a week, but then I started to have this big problem.
After I plugged in my friends charger at her house, (a Samsung Note tablet charger) then this problem started shortly after I left her house:
When I leave the phone alone, it will go to sleep automatically like every other phone. Then, when I press any button which wakes the phone, the touch screen is unresponsive, and the phone since no input is coming in, goes back to sleep and doesn't turn on again until after a while, where it will boot back on itself and start working until randomly out of chance (chance meaning atleast once every 1 - 4 hours) it will do the same thing again. It's getting really annoying and starting to be destructive, as it stops important conversations and other stuff.
I initially thought it was the homemade ROM.
So, I changed the ROM. Now I'm using a better one, and it's called W03 Slim v9 t0lte, and it's 4.4.2 and works good.
I was not seeing any problems up until a few hours after the install of the new ROM, and the problem which I thought had been removed was still persistent. Now, its even more often than the old homemade ROM. Just before posting this, it has happened twice in the matter of 1 hour, and it's just getting on my final nerve.
I'm not sure if this is a key factor, but after it goes to sleep, I still see the visible white pixels of the 4.4.2 shutoff effect.
My final thoughts are that it might be the battery, but I have no idea how to get a replacement for that, and how much they cost.
Obviously I can't send it in because the warranty was voided when I flashed the custom ROM.
I really need a solution, and ultimately I could wipe everything and go back to the stock ROM, but that, in my scenario would be a last case scenario.
Thanks, Delbert.
NOTE: Just found out that when I turn it on, and the touch screen is unresponsive, the S pen works with the phone, and the back and menu button doesn't work. But, all physical buttons do. The physical home button works, but all the rest except the S pen works. So I can navigate the phone unless it goes into sleep mode, in that case no matter what I press, nothing will make it come up unless it reboots.
AgentTran said:
Hey, I really need some desperate help.
So I have a Canadian Note 2, SGH-I317.
It has no SIM card inside it, and it is just connected to wifi.
I have flashed 2 Custom ROMS before on this phone.
The first one, was a 4.4.2 Homemade t0lte ROM.
It worked fine for about a week, but then I started to have this big problem.
After I plugged in my friends charger at her house, (a Samsung Note tablet charger) then this problem started shortly after I left her house:
When I leave the phone alone, it will go to sleep automatically like every other phone. Then, when I press any button which wakes the phone, the touch screen is unresponsive, and the phone since no input is coming in, goes back to sleep and doesn't turn on again until after a while, where it will boot back on itself and start working until randomly out of chance (chance meaning atleast once every 1 - 4 hours) it will do the same thing again. It's getting really annoying and starting to be destructive, as it stops important conversations and other stuff.
I initially thought it was the homemade ROM.
So, I changed the ROM. Now I'm using a better one, and it's called W03 Slim v9 t0lte, and it's 4.4.2 and works good.
I was not seeing any problems up until a few hours after the install of the new ROM, and the problem which I thought had been removed was still persistent. Now, its even more often than the old homemade ROM. Just before posting this, it has happened twice in the matter of 1 hour, and it's just getting on my final nerve.
I'm not sure if this is a key factor, but after it goes to sleep, I still see the visible white pixels of the 4.4.2 shutoff effect.
My final thoughts are that it might be the battery, but I have no idea how to get a replacement for that, and how much they cost.
Obviously I can't send it in because the warranty was voided when I flashed the custom ROM.
I really need a solution, and ultimately I could wipe everything and go back to the stock ROM, but that, in my scenario would be a last case scenario.
Thanks, Delbert.
NOTE: Just found out that when I turn it on, and the touch screen is unresponsive, the S pen works with the phone, and the back and menu button doesn't work. But, all physical buttons do. The physical home button works, but all the rest except the S pen works. So I can navigate the phone unless it goes into sleep mode, in that case no matter what I press, nothing will make it come up unless it reboots.
Click to expand...
Click to collapse
your friend's charger could've damaged your phone
i've had a charger that made my touchscreen unresponsive while plugged in... thankfully it didn't do any noticeable permanent damage
all USB chargers are not created equally:
http://www.righto.com/2012/10/a-dozen-usb-chargers-in-lab-apple-is.html
ShadowVlican said:
your friend's charger could've damaged your phone
i've had a charger that made my touchscreen unresponsive while plugged in... thankfully it didn't do any noticeable permanent damage
all USB chargers are not created equally:
Click to expand...
Click to collapse
Thank you for your reply, but if the charger did do damage to my phone, how would it and how does the touchscreen still work with the S pen?
Is there any way to fix this, and if not what do I do?
I have an HTC One X I could use as a backup, but I would like to install a 4.4.2 ROM on it, and with what I've found out I have to root it, which requires a recovery, which recovers an unlock or S-OFF, and when trying to do that, the phone won't connect via USB to my computer. I am frustrated but at the same time sad.
Should I just factory reset my whole phone and erase everything?
So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?
NotRankin said:
So I ended up flashing CM12 located in one of the other threads to play around with 5.0. It worked perfectly, no problems to be found or anything. However at one point, I went to grab it and play a game, the screen refused to turn on. I tried the Power + Vol. up trick and it still didn't do anything. Concerned (as I was toying around with a resolution app to pump it to 1600x900 res) I continued to try to force reboot it, and tried the Power + Vol. down trick to get into recovery. I plugged it into my computer to see if I can use ADB to force it to reboot and I get an error: no device found. So now I'm stuck waiting for the power to drain completely but it's been close to 24 hours and it still doesnt work. However my computer dings immediately as soon as I plug it in so it sounds like it's still alive (however there's no charging light on). How boned am I? Anything else I can try?
Click to expand...
Click to collapse
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.
FoxyDrew said:
I think there are 2 other cases exactly like yours, that makes me not want to use CM12.
Wait for the device to die, then try if adb recognizes it, or if you can get into recovery.
Click to expand...
Click to collapse
ok, I'll continue waiting, thanks for the info. I'll go ahead and flash CM11 and use that for awhile until HTC pushes their 5.0 out or if problems are fixed. Hopefully it won't take too much longer for the device to die...
2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.
NotRankin said:
2 days later, nothing, opened it up and removed the battery (was surprisingly a joke to do it too), plugged it back in, again nothing, plugged it into PC and the usual ding can be heard from the PC (But no charging light). Guess it's dead. If anyone else figures anything out, feel free to lemme know, back to the old broken screen Reverb for now.
Click to expand...
Click to collapse
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.
FoxyDrew said:
Unplug the battery, and then plug the phone into the charger with the battery out. Then after 10-15 minutes, plug the battery back in without unplugging the phone. Then just let the phone charge for a few hours. That has worked for me on other phones several times.
Click to expand...
Click to collapse
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
If theres still no charging lite? Possibly. You could try to charge the battery with a split charger. However thats last resort and can break your battery if it doesn't work.
NotRankin said:
Unfortunately it didn't work, literally nothing changed. Slight ringing noise from under the heatsink though when plugged in. Guessing it's fubar?
Click to expand...
Click to collapse
Or you could use your manufacturers warranty and send that baby back in for a fresh one. Claim a defect... Why? Because it is a defect. If you can't get it to boot with adb / rooted methods then their stock methods won't work nor detect anything. Besides, the worse they'll do is send your phone back the same way it got to them.
Also, if the others who ran into this issue could give feedback on if they modified screen resolution before the device kicked on CM12 that would be most informative.
Sent from my 710C using XDA Free mobile app
a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).
NotRankin said:
a bit of a necro, but a headup/final question.
Amazon gave me a full refund (took awhile) and getting a new Desire. However I'm wondering if anyone else has encountered this issue? I REALLY want to keep using Android 5.0 but I'm slightly worried about if it was just bad luck with 5.0, an actual issue with 5.0, or me screwing it up myself with changing my resolution (I don't think I even touched my DPI)(Virgin Mobile US Desire 816).
Click to expand...
Click to collapse
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.
FoxyDrew said:
A ROM can't fry your phone like this, so you have nothing to worry about. The issue with your last phone wasn't because of CM12.
Click to expand...
Click to collapse
So either I screwed something up or it was a screwed up phone in the first place (I'm inclined to believe this as it was frequently getting into a locked state where I'd have to force reboot it via the vol/power buttons). Guess I'll go for it, thanks!
My G4 seemed to be running hot yesterday and I had to charge it several times more than normal. All of a sudden it shut down would not boot back up. I tried everything but it will not go in to recovery or download mode. No lights come on at all when charger is connected either. One time I was able to get the MEIE number to flash and it said press power to reboot before it blanked out again. I called Verizon and they said it sounded like a complete system/software crash. I am rooted but haven't made any changes to my phone in several weeks. Verizon overnighted a replacement to me and it should be at my house when I get home. I wonder if this is the same issue that has been happening to the Sprint version that was recalled? Possibly the phone was just mad at me because it happened an hour after I ordered my Nexus 6p......lol
Now that it's cooled off can you boot it up?
I would think you could have just rebooted it when you first noticed it was hot.
Colchiro said:
Now that it's cooled off can you boot it up?
I would think you could have just rebooted it when you first noticed it was hot.
Click to expand...
Click to collapse
No it still doesn't boot up. I can get to the LG screen for maybe a second and it shuts back down. When I first noticed that it was hot I could reboot it. I let it cool off before restarting it but the problem persisted. What ever was causing it to overheat was also draining the battery. I had to charge the phone up twice by 2:00 pm. My "certified like new replacement" arrived on Friday and initially everything was good. On Saturday the Wifi disconnected and would not turn back on. The icon just sits there and blinks at me. If I go in the settings menu it is grayed out and doesn't give me the option to turn it on. I just got off the phone with Verizon and they are sending me another G4. Hopefully I will have better luck with this one. I would like to have a working phone that I can sell when my Nexus 6p arrives.
Sorry this is totally off topic but, did you have to pay a deductible to get a new phone?
sefirosu0522 said:
Sorry this is totally off topic but, did you have to pay a deductible to get a new phone?
Click to expand...
Click to collapse
No I didn't. It was Warranty replacement so it didn't have to go through insurance.
I had a similar issue last week, no root, running 12a. Phone shut itself off during normal usage (checking football scores). Running a little hot so let cool. Never booted past Verizon splash screen. Tried fresh battery, factory reset, safe mode. Nothing. Got my "certified like new" model. So far so good, but 6P here I come.
Sent from my VS986 using Tapatalk
Hmmm well good timing if you ordered a Nexus 6P. You can sell it like new.
Haha I was just watching "The Nexus 6P will bend in half if you try to bend it in half" video. I'd be interested in a size comparison between the 2.
So this exact thing happened to me, just several days after I got it (same thing, also rooted, nothing much done to the phone).
I had figured the battery ran dead (because I knew it was low), but it just wouldn't power on. Chargers wouldn't light it up. I put it on the charger for hours, and nothing happened. Lost all hope.
Then, randomly, I decided to see if Download Mode would work on my phone. I don't know why I tried it.
I pulled battery, and put it back. I held on Volume (up?) on the phone, and plugged it into the computer.
OH MY GOD -- IT CAME TO LIFE -- ! DOWNLOAD MODE!
I shut it down from download mode, then turned it back on (I think a battery pull) and it worked again.
I was completely relieved.
This happened to me a second time, weeks later.
The same solution worked.
I hope that this helps someone.
TL;DR: Try Download Mode (pull battery and put it back in -- then, while holding the volume Up key on the phone, plug USB into your computer)
So I've had this phone for about a year now, loved it (other than the lack of custom ROMS but that was my own fault for not doing enough research to begin with..) Anyways, to the problem..
The phone ran completely fine for about 6 months, no issues whatsoever. Then, I cracked the screen while working (oops). I consider myself at least a bit knowledgeable when it comes to phone repair, as I have done many in the past successfully. I purchased a new screen off E-bay, and installed it. No issues other than it had a few weird spots on the screen but it was bearable so I was living with it. About a month later I started having charge port issues. I had to prop it up certain ways to get it to charge, etc etc. I looked it up and apparently many people had this problem. It was running fine still for about another month until the strangest thing happened that I've never seen before.
The batter would immediately say 100% when I first plugged it in, and after powered on, it progressively brings itself down to 0% and then dies completely. Never seen it before and couldn't find anything about it on the internet really.
I figured that it was probably just the battery crapping out on me, so I thought, if I'm going to keep this phone (can't really afford a nicer phone right now), that I may as well purchase a new charge port and battery and repair them both.
The repair went flawlessly. The charge port works again perfectly but the battery problem still remains. It still says 100% and gradually goes down to 0% and dies.
What is going on here? Any ideas? I am now trying a system restore (my phone was encrypted so I wasnt able to get into TWRP without remembering the password which I don't even remember putting on there). I did a wipe on the phone and now I am able to access TWRP just fine on my internal storage, is there anything that may be able to fix this? Assuming this is a software issue and not a hardware one? And if it is a hardware one, what could it be??
Thank you for your time!
EDIT:
I forgot to mention. About a day before the battery started doing this. I downloaded the magisk module "ACC" (Advanced charging controller), thinking it may be useful considering how weird my charge port thing was being. It completely made my phone unable to charge when plugged in. I disabled and deleted the module and it went back to the way it was before (it didn't have the weird issue of discharging constantly). The next day or 2 that's when it started discharging immediately and always says its at 100% when I first plug it in. Don't know if that's relevent or not but I figured I would add it.