I have a rooted evo and recently I think it suffered from humidity and high heat when it was left in a ziplock bag outside for a short period. Anyway, I went to turn on my phone later and nothing happened, no boot, nothing. I took the battery out and put it back in, nothing. Tried to boot to recovery, nothing. You get the picture. Dead. I tried plugging it in and couldn't even get the orange light to turn on. I figured moisture was the culprit so I left it unplugged without the battery and by a fan to dry out. Still yet, nothing a day later. Two days later now the phone will boot up and stay running for anywhere from 5 minutes to 8 hours, and then just quit like the battery is dead, even when it charges. Sometimes it will turn right back on by hitting the power, others it won't do anything unless I wait an hour. Whenever it is in this dead time, it won't take a charge, but when it is alive, it will take a charge. Anyway, does this sound like the battery is hosed or is it some other type of issue? When it is running, everything works fine, date, 4g, wifi, etc. I want to take it to Sprint to have them look at it, but am rooted and fear they will say tough ****. I want to unroot so Sprint will look at it, but am worried the phone will die partway through the process, totally bricking the phone. Please offer your opinions and any help you may have!! Thanks a million.
legasus233 said:
I have a rooted evo and recently I think it suffered from humidity and high heat when it was left in a ziplock bag outside for a short period. Anyway, I went to turn on my phone later and nothing happened, no boot, nothing. I took the battery out and put it back in, nothing. Tried to boot to recovery, nothing. You get the picture. Dead. I tried plugging it in and couldn't even get the orange light to turn on. I figured moisture was the culprit so I left it unplugged without the battery and by a fan to dry out. Still yet, nothing a day later. Two days later now the phone will boot up and stay running for anywhere from 5 minutes to 8 hours, and then just quit like the battery is dead, even when it charges. Sometimes it will turn right back on by hitting the power, others it won't do anything unless I wait an hour. Whenever it is in this dead time, it won't take a charge, but when it is alive, it will take a charge. Anyway, does this sound like the battery is hosed or is it some other type of issue? When it is running, everything works fine, date, 4g, wifi, etc. I want to take it to Sprint to have them look at it, but am rooted and fear they will say tough ****. I want to unroot so Sprint will look at it, but am worried the phone will die partway through the process, totally bricking the phone. Please offer your opinions and any help you may have!! Thanks a million.
Click to expand...
Click to collapse
I would recommend a new battery see if that helps any.
well are your moisture indicators tripped?
deathsled said:
well are your moisture indicators tripped?
Click to expand...
Click to collapse
The one on the battery doesn't seem to be, not sure where any others are though.
I think that it might be best if you just tried to unroot... when I did it, it didn't take very long at all (maybe 5 minutes?) I used Good and Evo's method of unrooting, I'd post a link, but XDA won't let me. Just Google "unroot Evo".
But if it is insanely flakey, maybe try a new battery first? I can't think of anything else that would go bad in those conditions...
One more thing: I've herd many stories of people simply deleting the Superuser apk and getting away with it. Many techs at stores like Best Buy won't dig deeper than your program menu. It might be worth a try if it's your last resort...
Sorry if that was no help, best of luck!
Related
Is there a way to solve this (I've got a spare battery)? Any chance of getting an updated NBH?
robuser007 said:
Is there a way to solve this (I've got a spare battery)? Any chance of getting an updated NBH?
Click to expand...
Click to collapse
if your phone truly isn't charging the battery you can always hotwire it to the positive and negative wires from a clipped usb cord.
holding the wire to the terminals of the battery for a few minutes can get you running again.
however...
I have found that often if you just unplug the phone,remove the battery from the phone and then discharge the phone (pressing power button) then reinstall battery, you can then plug in the phone to get a charge...
let it charge for 15-20 minutes and then turn it on without the powercord.
resume charging once running.
I'd advise against the hotwiring method, since unless you have a lot of experience in wiring you run a risk of damaging something due to shorting wires, put it this way, I am experienced in electronics assembly, and wouldn't try this unless there was no other way.
However my method is similar to the one mnjm suggests, I have run out of battery once or twice on android, and I pull the battery, replace it, plug in the charger, wait until the light goes out, disconnect charger, pull and reinsert battery again, power on the phone, wait until it starts the second stage of booting, ( bootanimation), then plug in the charger. Usually works fine.
Or try this:
Pull the battery, replace it, plug in the charger, don't wait wait until the light goes out, power on the phone while light is ON.
I have run out of battery many times while testing battery patch an this always worked for me.
My battery meter was acting up lately and I decided to let my phone die. Let it run out of power to correct the battery meter. It was either 100% charged or less then 1% charge.
Now it won't boot. I see the X animation and nothing happens. I just keep watching the animation. The animation keeps resetting. I hate to think that my Android installation corrupted just by letting the battery run dry?
Will it even charge if I plug it in? I wanna try reinstalling Android to get it working again.
**EDIT**
Yep, corrupt installation.
I have no idea why draining the battery would do that, but it did. I reinstalled Android and it booted again.
My phone lost charge overnight the other day and I found plugging in usb power and using the hard reset button made it boot and then it would charge up OK.
Steve
zenity said:
I'd advise against the hotwiring method, .
Click to expand...
Click to collapse
yeah...I was regretting typing that.
obviously if you are not confident in your understanding of what you are doing then AVOID playing with bare wires.
you don't have to fear electricity...
but you do need to respect it.
I know you are confident, just making sure people knew that there were potential dangers, it's not that a cut down usb lead is dangerous as far as shock hazards go, more the remote possibility that a shorted lead could perhaps cause major battery problems, since hotwiring them, while it does charge the battery, provides no short-circuit protection, it is remotely possible, (but unlikely), that this could cause fire hazards.
If I was really desperate I might do this with a zener diode rather than just bare wires.
I know we like messing with our phones, but also remember that the Darwin Awards exist because people sometimes let enthusiasm get ahead of their capabilities
Dukenukemx said:
**EDIT**
Yep, corrupt installation.
Click to expand...
Click to collapse
One of the dangers, that's why it should be fixed in the NBH, any chances for a fix, anyone working on this at the moment ?
I'm thinking of buying the motorola milestone, but it's still expensive (350 euro's).
robuser007 said:
One of the dangers, that's why it should be fixed in the NBH, any chances for a fix, anyone working on this at the moment ?
I'm thinking of buying the motorola milestone, but it's still expensive (350 euro's).
Click to expand...
Click to collapse
I can actually buy a phone with my upgrade discount, but I love my Kaiser too much to let it go. Plus it's a better learning experience when dealing with Android.
If I bought a new Android phone, I wouldn't do much of anything with it, besides use it as a smart phone.
zenity said:
I know we like messing with our phones, but also remember that the Darwin Awards exist because people sometimes let enthusiasm get ahead of their capabilities
Click to expand...
Click to collapse
I know what you mean. When I use my hammer to smash aerosol cans, I'm always careful enough to cover my face with my hand. Can't be too careful.
I kid, I kid.
Dukenukemx said:
I can actually buy a phone with my upgrade discount, but I love my Kaiser too much to let it go. Plus it's a better learning experience when dealing with Android.
If I bought a new Android phone, I wouldn't do much of anything with it, besides use it as a smart phone.
Click to expand...
Click to collapse
I've seen that the milestone is still locked, no hardspl etc.
robuser007 said:
I've seen that the milestone is still locked, no hardspl etc.
Click to expand...
Click to collapse
Seriously? By the time they unlock it, there will be a new phone to buy.
Meh, besides, I never lose my old phones. They turn into "hand me downs". My sister has my old HTC Wizard right now. If things get really bad, I still have my old Nokia NGage. Yes, I own one of those.
Same thing has just happened to me, except I can't turn the phone back on at all now.
Was running the latest Kaiser NBH from DZO whilst using Myn's rom, I had a number of issues with battery life using android with it going from 75% charge to 0% and soft resetting by itself.
Anyways this time it hasn't woken up after doing just that, it was working fine then it turned off and I can't get it back on.
It just won't power on, there is no charging light but then again that only came on once android was booted never on startup with the android NBH, it was fine with Windows Mobile.
I have removed the battery, put it back in but nothing.
Swapped out for another working battery that I have spare, but nothing.
Tried a hard reset, still nothing.
It's just not starting at all now.
The phone was working and was on the side not charging and all of sudden it turned off and hasn't come back on since.
Bit annoyed.
ST1Cl<^^aN
Stickman89 said:
Same thing has just happened to me, except I can't turn the phone back on at all now.
Was running the latest Kaiser NBH from DZO whilst using Myn's rom, I had a number of issues with battery life using android with it going from 75% charge to 0% and soft resetting by itself.
Anyways this time it hasn't woken up after doing just that, it was working fine then it turned off and I can't get it back on.
It just won't power on, there is no charging light but then again that only came on once android was booted never on startup with the android NBH, it was fine with Windows Mobile.
I have removed the battery, put it back in but nothing.
Swapped out for another working battery that I have spare, but nothing.
Tried a hard reset, still nothing.
It's just not starting at all now.
The phone was working and was on the side not charging and all of sudden it turned off and hasn't come back on since.
Bit annoyed.
ST1Cl<^^aN
Click to expand...
Click to collapse
Sorted it now, note to self and anyone else who has done this.
Usually what occurs is when the phone powers off when the battery has not been calibrated properly it requires you to do a hard reset using the stylus.
Anyway's I did that in the dark and accidentally pushed the stylus into the charger port on the phone and pushed a pin into another so It was short circuiting. Luckily I didn't damage the pins or the phone and was able to straighten it so it wasn't making contact with the other pins.
I'm happy again, its only really a test phone tbh, I have had a HTC Hero for some time now...
Best Regards,
ST1Cl<^^aN
Like most problems, it's due to the kernel. Even if the bugs get sorted out, there's still plenty of room for improvement.
Lets say the following is working 100%.
phone
GPS
3D
power management
wifi
bluetooth
USB
camera
etc
There's always a need for something. Like upgrading 3D to OpenGL ES 2.0, or getting support for ext3/ext4. That's a long way to go and very few people are willing to do it on their spare time.
In the most severe cases, people had to pool together a reward for someone to include support for something.
Considering how similar the Kaiser/Polaris/Vogue is, you could combine this group of people to get something done. There's a lot of talent, but it's spread far apart.
Hi all,
For the last two to three months, I've been running a Universe ROM on my E4GT. Other than an occasional quirk, the phone has been working very well. I noticed that my phone didn't seem to be connecting to my home WiFi, so I put it into Airplane mode, and then took it out of Airplane mode. Instantly, it connected to my WiFi with a MUCH better signal After checking emails on the phone, I set an alarm and went to sleep. I woke up without the alarm since it did not go off. My phone appeared to be off. Holding the power button resulted in the blue LED charge light flashing, but the screen did not come on. I pulled the battery and put it back, thinking that the phone had some odd-ball software glitch that made it turn off in the middle of the night. When I hit power, the blue LED turns on, blinks, and that is all that happens. Once and only once since this started, my screen showed the boot animation, but did not get past that.
Because my screen turned on ONCE, I'm really hoping that I am soft bricked and not hard bricked. It does seem VERY odd for the phone to become bricked after working fine on this ROM for at least a couple months. The only change I made in recent time is to change a governor in ExTweaks from Hyper to Ondemand. I suppose that could have somehow caused this.
I stopped by a Sprint store, but they would not help as I do not have insurance and the phone is out of warranty.
Do you think making a USB jig or buying one may help? There is a Radio Shack close to where I live. And I have an extra USB cable I can take apart.
If that fails, should I send the phone to mobiletechvideos.com for their JTAG repair? It costs $50 plus shipping to them, but that is still cheaper than buying a new phone. If it came to that, I'd certainly hope they could fix it.
The fact that the blue LED light comes on seems like a decent sign of some life. While the battery animation does not come on, the light does.
Thanks for reading and offering any advice/suggestions.
Can you get into recovery or odin mode?
bigdaddy619 said:
Can you get into recovery or odin mode?
Click to expand...
Click to collapse
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
anindrew said:
Nope. When I try either, I get the blue LED light, it blinks once, and then stays on. Nothing happens on-screen.
Click to expand...
Click to collapse
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
bigdaddy619 said:
Well the jig may work give that a shot at least if you can get into odin mode you can start over using a one click good luck :d
Click to expand...
Click to collapse
Thank you! I'll post here if I get that to work or have an alternate solution.
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
BluesRulez said:
Charge your battery. Use an external charger if need be.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Brick
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I hate to be a downer but, I can guarantee you that you will not get any more than the dreaded blue light no matter what you do.
Take it to Sprint and let them go thru the entire process of trying to get it to boot and they may even give you some kind of excuse like "well I'm gonna take it to the back and disassemble it and see if the screen connection came loose".
They will never get it to boot and it is a hardware problem!!
Free replacement and may be backordered because this problem is happening to quite a few of the first run Galaxies.
I spent hours on the phone with "supposed techs" and went to 2 stores because my home store "child" said I must have gotten it wet and handed me a card with Asurion and said to contact them and I'd have to pay my deductible. BS, i wasn't paying for a hardware issue and YOU NEED TO TELL THEM THAT!!!
I spent a week and a half checking components (after they had taken it apart already at the store) while I waited on my replacement because I wanted what was on my internal memory and nothing. I know enough about electronic repair doing it my entire life since I was 12, that you will not get it back.
Sorry but like I'd said "i just went thru this 2 months ago" and plenty to read here on that situation.
They won't see any mod or even any display so you're safe with the Sprint techs. Just tell them when you woke up after setting your alarm, it was dead.
One good thing, is your replacement should be pretty safe from the emmc problem and download Chainfires app to see what chipset you get. (GotBrickBug)!!
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
Thank you very much for the reply. My phone was having a strange issue with connecting to my home WiFi before I put it on the charger for the last time. I wonder if that was a tell-tale sign that something was up.
I went to the Sprint store closer to where I live and explained what happened. They didn't give me any argument at all. Their tech checked out my phone, but couldn't get it to power up at all. They ordered a replacement E4GT (might be new; might be refurbished) for me for $35. I should have it by Friday. I was surprised by how helpful they were. Apparently, they have see this issue occur on some other Android phones as well.
What is the Chainfires app? Does it identify if you have the "older" chipset which can cause the brick issue? That must be what you mean by "GotBrickBug," right?
Since I'm eligible for an upgrade in June, I think I'll just use the stock ROM to avoid any possible issues. I wonder if the GS4 will be out then. It's always interesting to see what the hot new phone is going to be when you're ready for an upgrade.
Again, thank you to everyone for the helpful replies!
Surprised they even had you pay but I'd have paid $35 also if they'd asked me too.
You should get either new or new board at least.
Here's Chainfire's thread and app in OP. By the looks of it, my chips firmware is updated and as much as I've tested and flashed in the last couple weeks, it's holding up great. http://forum.xda-developers.com/showthread.php?t=1693704
My first clue was that my phone was having problems being read by my PC. Couldn't see either the onboard usb or my external usb. It was intermittent and within a week it was gone.
Sprint has been seeing this problem for sure and in Chainfire's thread, Samsung is well aware.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew said:
I thought that it could be the battery. My original got bloated about a month or two ago, so I bought an Anker battery from Amazon. It's been working great since I got it.
I had my Anker battery tested yesterday at a "Batteries Plus" store. The clerk put a new battery in the phone to see if it would help the phone, but it did the same blue LED thing. He used a multimeter to test my battery and the new one the store was selling. He said mine had more power in it than the one on the shelf and indicated that either battery has more than enough power to start the phone. While this still could be caused by my battery, it does seem strange for a new battery that has charge in it to not allow the phone to start. I don't have an external charger, but I could always visit my parents as they each have an E4GT.
Click to expand...
Click to collapse
Sounds like the h/w took a dump on you - the phone replacement was probably the only route left. By any chance did you leave it charging and/or in a location that allowed it to store heat? (Like a blanket, foam cushion, etc)
Teknician said:
Just went thru that and you have the same EXACT symptoms as my emmc brick. Jtag will not help so don't waste the money. Plenty to read on the emmc bug in the E4GT and SGS2 forums.
I will say that everything was working fantastic on the Rom I was using and it wasnt due to a botched flash. I was taking a couple pictures and when I plugged it into my laptop, I'd noticed it must have shut down never to boot again. It could happen at anytime I'm noticing.
Click to expand...
Click to collapse
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Update the next day: I found this thread, which is essentially a match for what I was experiencing. That one ended with a wait-it-out approach, and I basically did the same. I left it plugged in overnight, even though it appeared not to be charging at all (stone cold, no red light). In the morning, it was still all but dead, but I popped out the battery again (I had done this many times before), replugged it into power, and then it charged normally and completely for the first time since the incident. Moral: don't let the phone go below 15%, and if you do, plug it in ASAP. Don't ignore it overnight, even if it's powered off (maybe especially).
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
You're right - folks, this is not the eMMC bug. Let's just clear that up. If you need further information on that you can refer to the discussion thread on that bug and all the research that several folks have put into it.
When I first got my E4GT there was talk of a BLOD or "sleep of death" where the phone would not come back on. Wasn't the eMMC bug. Most people had a low battery so it was thought the batteries were too low and that it booted and messed up the bootloader. Others thought they overheated. Problem is without any way to diagnose the problem it's hard to come up with a "true" answer.
Perhaps a JTAG could revive the phones. Odd that even if plugged in that nothing is happening. But sometimes h/w really can just go south and trash a phone.
I highly suggest backing up your internal usb drive as frequently as possible because I lost a lot of photos that I never transfered, thanks to Samsung and my hardware taking a crap. Emmc blue light bug really sucks, believe me...
---------- Post added at 03:39 AM ---------- Previous post was at 03:29 AM ----------
rseiler said:
That's disturbing. I always thought that bug occurred when attempting to reset to defaults in the wrong way. I didn't think it could happen out of the blue.
In my case, which is awfully similar to the OP, my battery was running low, somewhere between 10 and 15%, and since I couldn't charge at the time, I powered down the phone. Next morning, I plugged it in to the usual wall charger and saw the battery charging symbol come up on screen as expected.
Instead of simply waiting for that screen to go off, I hit the power button to turn it off right away, but I might have inadvertently also pressed Vol Up with power or Vol Down with power, since I was doing it casually with one hand.
I didn't notice what might have happened right then, but a little later I saw that there was no charging LED. So I tried all the button combinations I knew to get it to come back to life, with and without the battery and power.
A couple times I got the blue light and then the battery charging screen, before it disappeared. Once I saw, in small print, "Battery low!! Can't Download," which makes me think that it's stuck in ODIN mode, which AFAIK doesn't support charging.
Right now I'm in the midst of looking for another battery or an external charger. I hope this is not what you're talking about.
Click to expand...
Click to collapse
Doesn't sound like emmc at all. All you will have is a blue light and that's it. If you saw ANY display, it's probably a battery and charging issue. You'll know the bug when you don't see anything but blue and no display at all.
Sent from my Blu Kuban FI27 E4GT SGS2 SPH~D710 (and whatever else they can call this phone) using Tapatalk 2
anindrew, how did it all turn out?
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.
My phone isn't responding no matter what I do. I've tried a jig and every combination you could possibly think of to turn it on and nothing works. I didn't flash anything or drop it in any way so I am just wondering what could have happened? I had to get rushed to the hospital and I was there for a little over a week. My phone was left in my pants in my room and there it sat the whole time that I was in recovery.
Might be a battery gone bad friend. Your phone is definitely not bricked... But we must find a solution to the problem. Is it charging?
No that's the thing that has me confused. I figured it might be the battery cause I did leave it on and it obviously it had run out of power. I tried taking the battery out with just a usb cord in and nothing.
Usually they do a 2x short vibrate with the battery out. I had my D710 flake on me after overcharging once and come back after a week and a fresh battery. Replace the battery, then test. If no go, try to vet the new battery to ensure its a gold one and pack your phone in a rice bag for a week and repeat.
It would be very surprising if its truly bricked. If all else FSA and testing has been thorough, wrote a detailed letter to Sammy regardless of warranty status and see if they will back it. If you get rejectee call and don't mention prior attempt at begging. If you are well spoken and have thoroughly ensured its just a random failure you might be pleasantly surprised by their willingness to investigate.
Sent from my SPH-D710 using xda premium
I'll go get a new battery now and see if that works, thanks for the reply. Also it didnt get wet or anything. I took my pants off in my room and there it sat in my pocket till I got back.
Also if it were the battery wouldn't it still at least show that splash screen when you attach a usb cable?
What also helps is charging the phone on an apple charger. But charge it 3 days.
Apple charger: it will not load with full power.
I assume that the battery is below 2V.
And then nothing is displayed.
So it wasn't bricked it just had some water damage I guess. Thanks for all the help everyone
My nexus 5x just doesn't boot up.
I had the same problem twice, last tine a few weeks ago.. A solution by a friend; Put the device in a plastic sack, close it very good. Then put the (enveloped) device in afreezer for a least 8 hours. After this time the batteryis absoltely empty. Now close it to yor USB-Lader and it takes only a few mitutes that in runs again. It worked for me twice, nd in worket with other deviceslike Samsung and Huawei.
I had it also some days ago but I had no time to put it in the fridge or just wait to fix it by itself.
My trick was to open the back cover and remove the battery connection for some seconds. After re-connecting it started up right away.
I have the same problem. I just want to turn it on to download some of my data. I have tried putting it in the freezer though only for about half an hour to an hour. I'm afraid the condensation may damage it too much.
Someone advised me to put it in the oven for a bit (lol), not sure if this is actually gonna do anything.
I tried that heat gun multiple times, put into freezer for about 4 hours, removed battery, charged it 5 days in a row.
I only managed to get the red light flashing, but it still wont turn on.
Is there anything more to try?
I personally think the battery is completely dead, but I dont have another battery to try it out.
I know this is an old thread but thought I'd post this anyway in case anyone is still trying to fix their Nexus 5x. I've tried everything to get a sign of life out of this phone, nothing worked. I was messing around with it and without even paying attention to what I was doing, I was holding just the Power button down for somewhere between 1 and 2 minutes and out of nowhere the phone vibrated. Looked at the screen and sure enough it booted up just fine! Can't believe it! If anyone reads this and gives it a try, let me know if you have any success.