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?
Last night my phone died after 2 days off cable due to me having to use my cord for another device. I plugged it in today to find that it wasn't charging at all. I decided to give it a few minutes before trying, thinking it may not be turning on because it still needs some juice. I waited 30 minutes and it wouldn't turn on still, just gave me the little animation of a battery draining to indicate that it needs to be charged. After this, I figured that it's possible the cable is just dead, so I opted to borrow a cable from my brother. The cable charges his phone just fine, but it doesn't work with charging my phone. I took a shower while waiting for it to perhaps get the juice it needed, and still no dice. I tried several different outlets thinking perhaps the outlet was dead, and still nothing.
I've had the phone for a little over a month, so I'm not sure how long I have to turn it in or not; I'd hope it'd be 3 months for factory issues, but judging from how people mention 14 days, I'd assume that they're eager to push responsibility of broken devices onto the customer as fast as they can. Do you guys have any idea of what could be wrong? Perhaps if it's possible for me to get a replacement at this point?
I've been running the Lifeless v.11 Rom for a while with no issues, I haven't flashed anything in possibly a week or two, so I honestly doubt this is a software issue. It's never been exposed to water, but then again I really don't trust phones to detect if they've been damaged or not since it seems even a humid day is enough for those small water damage detection stickers to run pink.
WASSHOI said:
Last night my phone died after 2 days off cable due to me having to use my cord for another device. I plugged it in today to find that it wasn't charging at all. I decided to give it a few minutes before trying, thinking it may not be turning on because it still needs some juice. I waited 30 minutes and it wouldn't turn on still, just gave me the little animation of a battery draining to indicate that it needs to be charged. After this, I figured that it's possible the cable is just dead, so I opted to borrow a cable from my brother. The cable charges his phone just fine, but it doesn't work with charging my phone. I took a shower while waiting for it to perhaps get the juice it needed, and still no dice. I tried several different outlets thinking perhaps the outlet was dead, and still nothing.
I've had the phone for a little over a month, so I'm not sure how long I have to turn it in or not; I'd hope it'd be 3 months for factory issues, but judging from how people mention 14 days, I'd assume that they're eager to push responsibility of broken devices onto the customer as fast as they can. Do you guys have any idea of what could be wrong? Perhaps if it's possible for me to get a replacement at this point?
I've been running the Lifeless v.11 Rom for a while with no issues, I haven't flashed anything in possibly a week or two, so I honestly doubt this is a software issue. It's never been exposed to water, but then again I really don't trust phones to detect if they've been damaged or not since it seems even a humid day is enough for those small water damage detection stickers to run pink.
Click to expand...
Click to collapse
wish i could help you man:/ only thing i can think of is taking of the back plating and make sure the connector is fine.it would suck if we have another evo 4g on our hands, especially without a removable battery
WASSHOI said:
Last night my phone died after 2 days off cable due to me having to use my cord for another device. I plugged it in today to find that it wasn't charging at all. I decided to give it a few minutes before trying, thinking it may not be turning on because it still needs some juice. I waited 30 minutes and it wouldn't turn on still, just gave me the little animation of a battery draining to indicate that it needs to be charged. After this, I figured that it's possible the cable is just dead, so I opted to borrow a cable from my brother. The cable charges his phone just fine, but it doesn't work with charging my phone. I took a shower while waiting for it to perhaps get the juice it needed, and still no dice. I tried several different outlets thinking perhaps the outlet was dead, and still nothing.
I've had the phone for a little over a month, so I'm not sure how long I have to turn it in or not; I'd hope it'd be 3 months for factory issues, but judging from how people mention 14 days, I'd assume that they're eager to push responsibility of broken devices onto the customer as fast as they can. Do you guys have any idea of what could be wrong? Perhaps if it's possible for me to get a replacement at this point?
I've been running the Lifeless v.11 Rom for a while with no issues, I haven't flashed anything in possibly a week or two, so I honestly doubt this is a software issue. It's never been exposed to water, but then again I really don't trust phones to detect if they've been damaged or not since it seems even a humid day is enough for those small water damage detection stickers to run pink.
Click to expand...
Click to collapse
Pull your battery, try again
Sent from my LG-LS970 using xda app-developers app
Yea, going to update this. Sprint was giving me issues and trying to cough up money from me, so I pulled the battery and cleaned the port with a q-tip and it charged fine again. I was in for a scare there, but it's back to life.
Same problem...didn't have to pull battery
WASSHOI said:
Yea, going to update this. Sprint was giving me issues and trying to cough up money from me, so I pulled the battery and cleaned the port with a q-tip and it charged fine again. I was in for a scare there, but it's back to life.
Click to expand...
Click to collapse
Just wanted to chime in with my experience.
I had same issue. Battery completely drained with a visit to the relatives (low cell signal).
Got home and plugged it in for 5min, the "battery charging" animation came on when short pressing the power button.
Had to move the phone to a different charger for the night and noticed that I couldn't get it to even show the charging animation while on the charger. Indeed after 8 hours on the charger the next morning it still wouldn't turn on. I thought I would have to take it back to Best Buy. On a whim, I thought I would drain all of the capacitance from the system by pressing and holding the power button to see if that would allow it to restart the charge cycle. So I held the power button for about 30-45sec off the charger, then waited about 30min and plugged it in at work.
It worked. Not sure why, but I didn't have to return it to Best Buy, so I'm happy.
Howdy, guys.
I've got my One rooted, unlocked, and was running a CM10.2 nightly build. Everything was working fine until yesterday, when my battery started to rapidly discharge. I woke up with 100% battery, and after about 15 minutes of playing music it was down to 30%. I recharged it and started noticing rapid battery loss, about 10% per 15 minutes when the phone was idle.
Worried that this had to do with my ROM, I flashed the Eclipse Google Play Edition v1.2 ROM. However, the drain issue continued. I decided to let the phone fully discharge, then try powering it up again.
When it was fully discharged, I tried plugging in the phone. No LED came on and I couldn't turn the phone on. I've let it sit for over 2 hours now with the same result.
Some posts with similar symptoms have mentioned plugging the phone into a Windows PC and experiencing the "USB device plugged in" sound alert. I am not having any such luck, and what I currently have is a very aesthetically pleasing paperweight with no function whatsoever.
Has anyone else experienced a similar issue, or found a fix?
none
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Last Sunday, listening to music with HTC One (bought on Sep 11) on the charger, it suddenly went dark. Would not reboot, no charge light either. Went to a VZW store, they're shipping me a warranty replacement.
I wonder whether my habit of leaving it charger-connected whenever it's sitting on my desk (i.e., way beyond the fully-charged point) somehow stressed the battery (or the charging circuitry) -- though that habit never impacted my two previous HTC models.
When you hold Vol+Down and Power do your home and back arrows blink? If so, point the phone sensors (the two on the front on the left hand side) into a bright light. Then hold down Vol+Down and Power. It should boot. I'm not sure why. But it worked for me today after installing a custom recovery. -shrugs-
musicman625 said:
I would take that back to Verizon were i you, sounds like a bad battery to me, chances are remote that it's the phone/hardware/software. they have to repair it despite the fact it's rooted, they probably wont even notice lol
Were it me, back to verizon we go
Click to expand...
Click to collapse
I've got a replacement being shipped to me, and I'll send them the old one when it comes in. Currently using an old Samsung Stratosphere as a replacement, I was just hoping there'd be an easier fix or something simple. Thanks, though!
Hello all... I've just received the FIre Phone I ordered off Ebay (qualitycellz seller). The phone is supposedly brand-new in original box, but upon taking it out of the box and trying to turn it on it did not respond at all. I connected the charger, tried again, nothing...... had to leave it connected for around 5 minutes and tried again and this time the screen woke up to show me the ultra low battery indicator with a 0% charge level. I had to wait for it to charge for around 5 minutes to re-attempt turning it on. Fortunately it did turn on after that time.
My concern is that from what I know all cellphone manufacturers ship phones with at least 60% charge in order to keep the battery in good condition while on storage, so receiving the phone completely dead raises a concern on me that there might be damage to the battery. Could this be related to the long time Amazon had these units in storage since the phone launched?... I would expect that these phone might have been around a year in storage before Amazon decided to pull the plug.
This is the seller that Amazon unloaded all their remaining Fire Phone inventory to, so phones are new in box. I'm also concerned that the seal on the box was broken, even though the phone and packaging inside did not show signs of being used in any way. The phones are AT&T version but they include an unlocking code, so they should not need to open the box in any way since they generate the Unlock code based on the IMEI visible on the box label. One option is that they open the boxes to confirm that the phones are not DOA and then they forgot to turn it off after testing.
Should I be concerned about this?... I've not activated the phone yet and I've contacted the seller first to at least request their explanation and thoughts on this, and check if we should proceed with a return on this case. Your comments are appreciated.
Mine was exactly the same. Think about it, they've probably been sitting for a year. I've had no problems and charge seems to be just fine. (ATT Unlocked)
wiseguywood said:
Mine was exactly the same. Think about it, they've probably been sitting for a year. I've had no problems and charge seems to be just fine. (ATT Unlocked)
Click to expand...
Click to collapse
Thanks Wise... that helps. It makes sense to think about that due to the long time the poor phones were collecting dust on Amazon's shelves.
Did your box had the little plastic seal broken also?
I purchased from the same person I think and I just got my phone it as the same way. The battery life is still great
GeorgeRod said:
Thanks Wise... that helps. It makes sense to think about that due to the long time the poor phones were collecting dust on Amazon's shelves.
Did your box had the little plastic seal broken also?
Click to expand...
Click to collapse
I think I had to cut mine, but it honestly looked untouched inside. I have had it for 3 weeks so far, no problems battery seems pretty good. After sideloading google services a few times, I have not had to reload it and am currently only experimenting different program launchers besides the default one. Haven't been able to settle on one yet. Good luck!
I got an AT&T one from qualitycellz about a week and half ago and my battery was also completely drained. Everything was sealed up nice and I haven't had an issue since.
Yeah my Fire Phone was fully discharged as well, freaked me out a little when I couldn't turn it on, even when I plugged it in. But after giving it a few minutes to charge it powered up just fine.
Thanks all for replying... I guess we can conclude that all these phones were sitting on Amazon's shelves for a long time, so everyone that purchased their Fire Phone on the "Fire Sale" on Ebay can assume that the phone will come fully discharged and you'll need to plug it in for a few minutes before attempting to turn it on.
IMPORTANT NOTE FOR NEW BUYERS: The most confusing factor on this is that when you plug the phone to the charger for the first time the phone does not gives you any indication that it is charging, not even when pressing any button. That's what can be frustrating because you actually have to wait around 5 and press one of the buttons and then it will give you the charging screen. Keep that in mind before you throw your Fire out of the window.
Mine was same. I'm using Nova 3.x launcher, you can find this 'old' version online...the newer versions aren't as pretty..IMHO
Sent from my SD4930UR using XDA Free mobile app
I think I bought the phone through the same eBay auction that you all are discussing. However, when I plug in the phone and try and charge it... nothing happens. I've tried several cables, several chargers, and all for at least an hour - none seem to work.
If I long-press on the power button for about 8 seconds, I can get it to vibrate once, but then nothing happens.
If I plug it into a computer, press the power button for 8 seconds, it will start to vibrate about every second. I've never seen any other phone do this. It's only if it is plugged into a computer (mac).
Any thoughts?
hospadam said:
I think I bought the phone through the same eBay auction that you all are discussing. However, when I plug in the phone and try and charge it... nothing happens. I've tried several cables, several chargers, and all for at least an hour - none seem to work.
If I long-press on the power button for about 8 seconds, I can get it to vibrate once, but then nothing happens.
If I plug it into a computer, press the power button for 8 seconds, it will start to vibrate about every second. I've never seen any other phone do this. It's only if it is plugged into a computer (mac).
Any thoughts?
Click to expand...
Click to collapse
Use the charger that came with the phone and let it sit charging in the off state for 15 minutes or so. Mine took a while before I could power it on the first time.
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)