Develop Bugs

Possibly bricked E4GT. Advice please.

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?

My galaxy will not turn on it just vibrates! Bricked?

Two weeks ago my galaxy just stopped working. it was at a decent battery; just stopped. I tried charging it but the phone would vibrate. phone would come on, then shut off. I tried it multiple times and same result; a few times the phone would make it to the samsung startup animation, sometimes it would just flash the samsung logo, once it compleley got to my screen start before shutting off.
I brought my phone to get fixed. It took a whole week and the guy said my phone was just not fixable. It would work for a few hours then shut off again, according to him. I suspect he didnt work much on it though as hed rather fix phones with easy problems as mine was a tough one.
I've had to replace my phone with an iphone now, but right now, out of curiosity, I completely took my phone apart, and started using tweezers to play the power on button. The camera part just broke off (not the actual camera) but now my phone is actually charging! The red light is on, and click the main button, it shows the battery being charged. This has not happened ever since the phone broke.
Am I bricked? Is there hope for this phone??? Please tell me there is lol.
EDIT: My phone seems to have restarted! Turned it on and it's asking for my simcard what is GOING ON LOL

Summertimes said:
Two weeks ago my galaxy just stopped working. it was at a decent battery; just stopped. I tried charging it but the phone would vibrate. phone would come on, then shut off. I tried it multiple times and same result; a few times the phone would make it to the samsung startup animation, sometimes it would just flash the samsung logo, once it compleley got to my screen start before shutting off.
I brought my phone to get fixed. It took a whole week and the guy said my phone was just not fixable. It would work for a few hours then shut off again, according to him. I suspect he didnt work much on it though as hed rather fix phones with easy problems as mine was a tough one.
I've had to replace my phone with an iphone now, but right now, out of curiosity, I completely took my phone apart, and started using tweezers to play the power on button. The camera part just broke off (not the actual camera) but now my phone is actually charging! The red light is on, and click the main button, it shows the battery being charged. This has not happened ever since the phone broke.
Am I bricked? Is there hope for this phone??? Please tell me there is lol.
EDIT: My phone seems to have restarted! Turned it on and it's asking for my simcard what is GOING ON LOL
Click to expand...
Click to collapse
idont know what you did there, but it worked plus you gotta be more specific to how the phone broke and could not boot-up to screen

winosxbuntu said:
idont know what you did there, but it worked plus you gotta be more specific to how the phone broke and could not boot-up to screen
Click to expand...
Click to collapse
It just randomly shut off. It was if someone would constantly be turning the phone off as soon as I turned it on. But then I couldn't even charge the phone. No red light, no screen, nothing, just vibration. I would try to turn it on sometimes it would get to the boot up, sometimes not, sometimes nothing, just a vibrate.
I literally took tweezers and lifted the green board out from around the power on button (it's an actual tiny white button on the inside). and then it randomly started working again

Summertimes said:
It just randomly shut off. It was if someone would constantly be turning the phone off as soon as I turned it on. But then I couldn't even charge the phone. No red light, no screen, nothing, just vibration. I would try to turn it on sometimes it would get to the boot up, sometimes not, sometimes nothing, just a vibrate.
I literally took tweezers and lifted the green board out from around the power on button (it's an actual tiny white button on the inside). and then it randomly started working again
Click to expand...
Click to collapse
Could be a power button failure. Happens somewhat often.
Could be battery related too, a cheap replacement battery could strike that off.

polobunny said:
Could be a power button failure. Happens somewhat often.
Could be battery related too, a cheap replacement battery could strike that off.
Click to expand...
Click to collapse
agree with what he said, it could be a problem with the power button or battery is not working
off topic did you really get 176Mb/s download or is it fake
if its real then was it WIFI or DATA , i have never topped 50Mb/s both wifi and data) but DATA seems to be 10x faster than my wifi

[Q] Help!!!!! Screen going on and off idk what to do!!!

first of all thank you for taking the time to read through this.
Yesterday I woke up and reached over to check my LG G3. I had left it charging overnight as I usually do and while the phone was still plugged in and I tried to go through my notifications, the screen flickered and went off. I was puzzled cause the phone was fully charged and the screen has no cracks and barely any scratches. I was trying to restart it and the LED light started flashing as I heard a notification sound.... I proceeded to take out the battery hoping thatd help out and nothing.
I thought my LCD took a **** on me but I tried to restart the phone once more about an hour later and then the LG logo came on shinny as ever. Then the AT&T logo, I thought all was well but then the screen flickered again and went off. A few moments later I started to hear more notification sounds and I saw the LED light start blinking.... everything in the phone works except the screen.
I changed my sim card to an old blackberry knock off so I wouldnt be cut off from the world while I went to work and when I came home I tried to play with it once more and the phone started working normally! As I was playing with it I raised the brightness and the screen started to flicker again but did not shut off. I immediately brought down the brightness and the phone seemed to work normally I then tried to open the camera and the screen went off completely same happened when I tried to refresh an app. What could this be? the battery? currently I the screen doesnt stay on for more than 10 seconds and does not work at all when plugged in to charge
Also in the last couple of weeks I was experiencing overheating but I assumed it was because of the rise in temperatures and the fact I spend most of my day outside and Im constantly using my phone. I am also guilty of using my phone while charging.
Any input you may have is going to be helpful. I need to figure this out as I use my phone to work more efficiently.
Thank you in advance!

I am having the same issue. I'm going to contact LG about this on Monday.

dKJon said:
I am having the same issue. I'm going to contact LG about this on Monday.
Click to expand...
Click to collapse
got answer ?

Yeah, they changed the entire display and said that the error could come from a defect battery. So i bought a new one and hoped for the best.
I still had the error today. I will try installing another rom so I can be sure it isn't the software.
Or else LG will be getting it again.
Sent from my LG-D855 using XDA Free mobile app

Well, they got it again... Twice. They changed the LCD panel and the mainboard. It seems that the latter fixed it. I got it back on Saturday and haven't had any problems since then.
Fingers crossed
Sent from my LG-D855 using XDA Free mobile app

I forgot about this post but I used my warranty last year and got a new phone or refurbished. They didn't tell me. Here I am a year later with the new phone and the same problem came back. The only thing that seems to work is baking the main board at 350 for 10 minutes and letting it cool down in the oven for 30 yet the problem comes back. After a week or so. I'm convinced the overheating of the phone is he culprit
Sent from my LG-D850 using Tapatalk

LG G4 won't turn on

I have a G4 with Verizon and on Sunday I powered it down to swap my battery. I had about 30% left on the battery in the phone and a fully charged spare. I put the second battery in and since then it will not power on. I have tried both batteries and connected it to the power adapter... nothing happens (no lights, sounds, or vibrations). I called Verizon and they are sending me a refurb replacement but I'll need to send this one back once that device is up and running. I want to see if anyone has ideas on how to eliminate my data. I do have a SD card with my pictures so that's fine. I just want to erase everything else.
I have been playing with the phone for the past day and a half and I have gotten it to power on for a brief moment here or there. It is very random and sometimes it will show the LG splash screen and then it goes back out. I also have had it vibrate like it is turning on only not to show anything. A couple of times it has vibrated for over a minute straight before cutting back out. And while it was sitting on my desk it was rebooting itself several times earlier today until giving up. Also, when I plug it into my PC I do hear the Windows sound that you get when connecting a drive. But no drive letters appear. I am hopeful that I can get it to turn on long enough to erase everything. The phone is not rooted and is using the latest Android OS (I believe it was 5.1.1) that Verizon sent out in November.
I did not notice any other issues recently and I have swapped batteries dozens of times and never had this problem. It was powered off properly prior to this all happening. If anyone has any ideas of ways I can try to get it back on that would be great. Thank you!
Edit: Also, pressing the volume down and power together does nothing. Only way I have ever got the phone to respond in the past 24 hours is holding power for 20+ seconds and maybe it will work. But then it turns back off.

same here. dunno what to do since i bought mine used on swappa!

Sound like the hardware problem other users have had, including myself just about 2 weeks ago. If this is the case try putting the phone in the freezer for 10 to 20 minutes (I know it sounds crazy) but it worked for me and some others. I was able to power the phone up long enough to get it into recover (pressing the power button + volume down) long enough for me to wipe my data before sending it back. When I put the phone in the freezer I left the batter in and the back cover on.

jfriend33 said:
same here. dunno what to do since i bought mine used on swappa!
Click to expand...
Click to collapse
The phone is still not quite a year old. Contact LG as they have a 1 year warranty. You are running out of time though. They never asked me for a receipt as they knew within a year if it died the fix was on them.

LG G4 is a very vulnerable phone and LG’s Head of US Marketing has accepted that the LG g 4s manufactured before september 2015 had its own set of problems. Follow this guide https://appuals.com/fix-lg-g4-wont-turn/ in order to resolve your phone issues. If this doesn't help, you can send the phone for repair or replacement.

nexus 5x dead

My mother's nexus 5x has just died.
no fastboot no recovery nothing.
I have tried to charge it, but after more than an hour connected to the charger still nothing.
I checked that this charger works on my nexus 5x so it's not the problem.
I also tried to connect it to a computer, but the computer detected nothing.
the phone had 7.1.2 stock (either april or may security update I don't remember which one).
Anyone has an idea why it happened or how to fix this?
Thanks,
Orma

Wow, my 5X just died this morning. Wonder if it isn't just a coincidence or maybe some update like to the Fi app or something messed it up. So I'll post in case others have also had the same thing happen. The Fi app was last updated May 8, so that's not it. But maybe there was some other app or something updated that caused problems. Some of the core apps were recently updated and my phone tried to update some behind the scenes type app, but it didn't work. So I tried manually and it did work. Maybe I shouldn't have done that. Can't remember which app, but checking on my Google playstore apps, maybe it was Google Connectivity Services.
Mine was fully charged and I was using it while still connected to the charger after waking up in the morning. It just went black suddenly. I tried holding power button to shut it down, but it never made any vibration as if it was force shutting off. Power button and volume down button didn't work to shut down or boot either. The computer recognized it the first time I plugged it in showing Qualcomm HS-USB QDLoader 9008 has completed setup. But after that it would show as device unrecognized.
The only way I got anything to look like it was starting ok was by disconnecting the battery for a while. Then it started booting and then the screen just went black again. I unhooked the battery again for a while, reassembled, and plugged the phone in and the battery charging screen showed up, but then went black again without showing the filling up graphics.
So it seems to momentarily kinda act ok, but then soon goes black. Disconnecting the battery seems to reset it to a state where it can try again.
The battery read as 4.16 volts, so seems to be fully charged as I thought it was. I'm going to try doing the battery disconnect again, but I'm thinking this thing is done.

This may not just be a random thing. Several people on Google forums have the same sounding issue from yesterday or today.
https://productforums.google.com/forum/#!topic/nexus/iKXTmQ04YeM;context-place=forum/nexus
https://productforums.google.com/forum/#!topic/nexus/DINPhe1nb4c;context-place=forum/nexus
https://productforums.google.com/forum/#!topic/nexus/lWKu7eEfHhc;context-place=forum/nexus

By disconnecting the battery and then reassembling, I was able to get to the recovery menu. I chose Restart Bootloader, and after a few moments, go a screen showing the android character laying on the ground with a triangle with an exclamation point and "No Command" text at the bottom.
Holding power button and volume down got it to go back to the menu.
So I tried Recovery and it showed Google in white letters, then went black. Trying Start does the same thing.

This problem is common in the Nexus 5x, I advice you to check the warranty
Envoyé de mon HTC One_M8 en utilisant Tapatalk

kakah2011 said:
This problem is common in the Nexus 5x, I advice you to check the warranty
Envoyé de mon HTC One_M8 en utilisant Tapatalk
Click to expand...
Click to collapse
Voicebox said:
By disconnecting the battery and then reassembling, I was able to get to the recovery menu. I chose Restart Bootloader, and after a few moments, go a screen showing the android character laying on the ground with a triangle with an exclamation point and "No Command" text at the bottom.
Holding power button and volume down got it to go back to the menu.
So I tried Recovery and it showed Google in white letters, then went black. Trying Start does the same thing.
Click to expand...
Click to collapse
if I open the phone to disconnect the battery will it void the warranty?
any one has any idea on why it happened?
my nexus 5x is totally fine
edit: I tried again to turn it on, but this time the notification light turned red, so i tried to connect it to the charger again and it seems to be alive now,
that's really weird but it turned on with 1% meaning that for some reason when I charged it yesterday it wasn't really charging

orma1 said:
if I open the phone to disconnect the battery will it void the warranty?
any one has any idea on why it happened?
my nexus 5x is totally fine
edit: I tried again to turn it on, but this time the notification light turned red, so i tried to connect it to the charger again and it seems to be alive now,
that's really weird but it turned on with 1% meaning that for some reason when I charged it yesterday it wasn't really charging
Click to expand...
Click to collapse
Sounds like you got lucky.
As far as I could see, there is nothing inside the phone that would indicate that you had opened it up. There's no glue, except under the battery, and maybe under the motherboard. But you don't need to lift those to disconnect the battery connector. However, it does require prying the back off and then unscrewing 10 screws. Then lifting off two pieces with stuff like the fingerprint sensor and speaker attached to them. If you make any dings in the plastic back cover while prying, they could see that. And the screws have lock tite on the threads so take some care to remove. I think I slightly stripped the top of one. So if someone really looked, they could see that. But otherwise, except for leaving fingerprints on parts or debris or whatever in there, I don't think they'd notice. I highly doubt they'd have someone go check for other than obvious signs of prying the back off. I'm 2 months past warranty so it was a non-issue for me.
Following someone's advice on the Google forum, I cooled the phone down in an ice bath (in a bag of course) and was able to get it to boot to recovery and even installed the OTA via adb. It then booted to the point of the 4 colorful circles and died again. After putting it in the freezer, it then returned to acting somewhat normal, as in it showed the battery charging graphic while off. The battery is about 1/2 full. But then I booted and it would get pretty far into the 4 circles spinning, then boot looped. So mine is bootlooping and I'm going to see if I can get Google to step up even though it is 2 months past warranty since I bought it from them. The Google people say to contact them with the bootloop problem. I hope they are quietly replacing them since this this appears to result from the last OS update for many people.
That other person was able to boot it and pull their pictures off it. But looks like mine is down for the count. I luckily had backed up pictures and most of my other stuff recently before I went on a trip. And I uploaded pictures while on the trip and pulled pictures off the phone right after the trip. But I've lost some info that I hadn't copied off the phone.
---------- Post added at 02:17 PM ---------- Previous post was at 01:59 PM ----------
kakah2011 said:
This problem is common in the Nexus 5x, I advice you to check the warranty
Envoyé de mon HTC One_M8 en utilisant Tapatalk
Click to expand...
Click to collapse
I'm 2 months out of warranty, so I hope Google does something since I bought it from them and they seem to be providing some relief since this seems to be due to the most recent OS update. Or at least some of the people in their forums seem to imply they'll do something.

Well here you go. Explanation was at XDA all along. There's a class action lawsuit against LG for using solder that didn't withstand the level of heat or heating and cooling cycles. Started with the G4, but in April the 5X and other phones were added to the class action. So I guess I could try touching up solder points and get my phone maybe to start up, or try for warranty repair since they seem to have extended the warranty because of this lawsuit.
https://www.xda-developers.com/lg-bootloop-lawsuit-adds-nexus-5x-lg-g5-v20-case/
One guy at bottom of this thread has screen capture and says his 18 month old 5X shows as covered by warranty in their system.
https://productforums.google.com/forum/#!topic/nexus/PZrVO8g9Y9M;context-place=forum/nexus

Same here.
Nexus died after some freezes. After 7-10 failed boots it suddenly booted, just to freeze again after 1 or 2 minutes.
Tried every button combo with and without power plugged, no luck at all, just a dead brick with no signs of life at all.
Device was perfectly working till yesterday. No issues at all
Latest purenexus version. Everything was fine.
Don't get it.
Only thing what came to my mind was that we have been to the beach the day before. Had the phone in the backpack, but it went still really hot since the sun was strong.
But hey. Have been to definitiv hotter places last year in Croatia.
I thought i try the revive Motherboard in oven trick, since this oven thing already worked once for my laptop graphic chip which died also from overheating.
Put the MB in the oven for 12min at 200C.
No luck. Dead brick.
Any ideas?
Thanks for reading!

When my Nexus 5x died, LG replaced the motherboard and then everything was even much better than before.

quark-lepton said:
When my Nexus 5x died, LG replaced the motherboard and then everything was even much better than before.
Click to expand...
Click to collapse
Well. Got it from ebay.. No invoice.
Don't know if i can claim warrenty?

SchWeinSAuG said:
Well. Got it from ebay.. No invoice.
Don't know if i can claim warrenty?
Click to expand...
Click to collapse
LG has agreed to extend warranties on a case by case basis after they were sued. One lawsuit was dropped as a result, but the other remains. So they may be more willing than usual to fix it without proof of purchase, but only way to know is to call them.
http://www.androidpolice.com/2017/05/25/one-lawsuits-lg-nexus-5x-bootloop-dropped/
If you can't get any warranty help, then you can try the heatgun method. This seems to basically melt the solder again so that it'll work. If you're lucky, you get the one or few connections that are messed up.
Using a heatgun, I got mine from completely dead to where it performed normally for 9 hours. I thought I was back in business until it rebooted. Then it lasted a bit before rebooting, and every time would get shorter and shorter before rebooting. Now it is bootlooping at startup, but still alive. So I can adb the OTA back on there, clear cache and factory reset. And it charges. But it just bootloops.
https://www.youtube.com/watch?v=KQrsC2VZY0c
https://www.youtube.com/watch?v=wxQehPw4yPY
By they way, I tried a hairdryer for 30 seconds and it did boot to where I could unlock it, then it froze. The hairdryer just doesn't get hot enough to melt solder and only just heats things up to where there might be a temporary restoration of whatever connection or solder is broken. So I tried about 2 minutes and I could boot and swipe one screen left before it died. The heatgun took 1 minute 30 seconds to get it to where it would boot and work. I'm not going to go at it again since I have a chance at just getting a warranty swap if they extend it since I'm 2 months past the year coverage.