Bootloop - Nexus 5X Q&A, Help & Troubleshooting

So I've been doing a bit of looking around in the forums and reviewed the report that came with my 'repaired' Nexus 5X (It worked but only temporarily) And I think the bootloop of death seems to have two causes. For some people it's the 2 larger cores and for others (the majority it seems) have an issue regarding the eMMC chip. From what I've seen is it's the solder balls below these parts that seem to loosen up or crack and that's what may be causing the problem. But from what I've seen there's no link between the bootloop and serial number. Personally my story is I tried to downgrade back to 6.0.1 to install my favorite ROM and I got the bootloop, sent it back for repair, tried to downgrade again, bootloop. It sounds like a software bootloop from the story but it showed the same symptoms as the first one which lined up with a hardware bootloop. When they sent the phone back it was printed that the eMMC was replaced. What are everyone else's stories for their bootloops and their beginning and resolution? Maybe we can hope to shed some light as to something connecting. I myself am ready to just get a Moto Z Play

Related

[HARDWARE FAULT] [BSOD] Blank Screen of Death : Information Board - Updated 29/07/12

A few users have reported a Blank Screen of Death, with myself included.
The problem being that the phone's display doesn't switch on when you wake up the device. At this time, Everything else will including the Digitizer and Capacitive buttons.
I have spoken with HTC service centers across Australia and NZ to come to the conclusion that this is a motherboard problem. The infamous flickering issue seems to be involved also, which ends up shorting out the video driver.
The issue isn't just limited to the screen not displaying anything either, there's also the possibility that the back light will cut out, and sometimes leading to corruption on the display.
This isn't just with some devices either, it seems like anyone that has had the screen flickering issue are at risk of this.
To give you an idea of how much it costs to fix this issue, I was quoted at $250 AUD for just the motherboard alone.
The best part is, HTC may also deny your warranty for unlocking your bootloader, as they have with me.
I'll be posting more information as it develops.
EDIT 29/07/12 :: I'm going to request a transcript of my last conversation with HTC but until then, they're denying that this is a problem and saying that it's the user's fault. How? We use our phones to much, or inappropriately.
It's becoming obvious that they're trying to avoid spending anymore money fixing these issues, and have decided just to move on and release a new One X model. (according to news sources.)
Also, Boobinator just posted a video of the One X's screen corrupting while it isn't stuck under the BSOD which you can see here and here
Just to recap.
When the initial issues were found with screen flickering and corruption on the display, we were told it was a software issue.
Many months later, I along with many of you are still experiencing it, even though it's not nearly as bad as it once was.
Now there are growing reports that One X's are starting to lose their displays, and the poly-carbonate weakening and bending the antenna pins. (You can find more information here)
This is something you should all be aware about when purchasing this phone.
Best of luck!
Reserved.
Update Bump
Maybe us in America can file a class action lawsuit? I'm no lawyer here but anyone with better understanding of American consumer laws chime in?
This is problem that occurs with normal usage of the phone.
Another day, another hardware issue. HTC is going down the drain, im hugely disappointed in the way they are handling this mess. Improper testing, too slow to fix problems or ignore/deny them. Bull**** games about unlocking and warranty and now they are already talking about releasing more phones. Its easier for them to move on to a new model than to do the right thing and do a complete recall. Is this a QC issue or a design flaw, with all the negative reports I'm thinking its the latter.
HTC better handle this properly, they need to stop development on all new products untill this is solved.
Sent from my HTC One X using xda app-developers app
Can u please send me details about the store that sells the motherboard ?
I have the same problem...and I need my phone fixed !
Thx
Is this the same flickering that happens in some ROMs when you rotate the phone?
Mine too
This just started happening to mine Nothing displayed on the screen, but it still responds to inputs. Even rebooting into fastboot, same problem. So everything is functioning except the display.
Have just handed it back to vodafone for repair, don't like my odds with the unlocked bootloader though :/
I had this issue on Viper or Android Revolution, but not on other ROMs. But I'm starting to get wifi issue, scratches, scratches on camera lins. I should buy S3, not this.
Sent from my HTC One X using XDA Premium HD app
sent it back because of flickering. I just hope they will fix the problem properly and change the motherboard.
Sent from my Legend using xda app-developers app
This happened to my Incredible S too if any one's interested.....
I'm not buying the HOX, I'm sorry. There's just too many different issues for too many people with this phone. It's an expensive top of the line phone, that does appear to be pretty shoddy put together. I don't care if it's under warranty and I have dumbass-insurance if I break it, but I can't send my phone inn all the time even if it's free. You shouldn't have to send it in at all.......
I presume now know we know why HTC is loosing money, market share and their stocks are going down....
This happened to me too, about a month ago, the phones been in repair since then(1 month, are you freaking kidding me HTC). I also unlocked the bootloader, lets see whether HTC charges me or not.
Also, I managed to get the display to work(somewhat) after shaking the device a bit. But even after that the display wont work properly, I even have 2 short videos of the screen acting weird when i got it to work. Here they are - Video 1 Video 2
Sorry for the ****ty quality, got it on my iphone. This was after I shook the device and the display magically started working. Even with the display working you can see it is really weird, even unresponsive at times.
So guys, there are a lot of places you can buy motherboards from, but they will charge you a lot more than what it's worth mainly because of the shortage within HTC.
I'm so sorry all of you are going through this, but i think we need to raise awareness of this issue. People are buying these phones without realizing there's a good chance they're going to have either bad WiFi antenna's or even a bad motherboard.
Send this to your friends, post it around, contact HTC.
Best of luck!
I am having this problem as well, as well as the WiFi antenna issue. The WiFi antenna somehow bent itself somehow, because after a while it was back to normal signal strength, so I didn't feel like sending the phone away for a month. But now with this screen issue it really is unusable, so it seems I don't have a choice anymore
EDIT
Here is a picture of an example of what happens:
http://i.imgur.com/ScIaM.jpg
And here are two 1 minute videos of what happens:
http://www.youtube.com/watch?v=HIY0_Hy2_mA
http://www.youtube.com/watch?v=WYXXvu11f3o
may heat have damaged gpu? it looks like when pc's video card is about to fail (like faulty memories or damaged gpu)
CAPSGUY said:
I am having this problem as well, as well as the WiFi antenna issue. The WiFi antenna somehow bent itself somehow, because after a while it was back to normal signal strength, so I didn't feel like sending the phone away for a month. But now with this screen issue it really is unusable, so it seems I don't have a choice anymore
EDIT
Here is a picture of an example of what happens:
http://i.imgur.com/ScIaM.jpg
And here are two 1 minute videos of what happens:
http://www.youtube.com/watch?v=HIY0_Hy2_mA
http://www.youtube.com/watch?v=WYXXvu11f3o
Click to expand...
Click to collapse
Heat damage.
I doubt it's heat damage, i hardly played games on mine and it had that problem. I think the most i played was Triple Town, and that was it.
Also, wouldn't it be a massive problem if it was heat damage? That means the tegra 3 processor can't handle stress, and given that the phone inherently has heating issues, this just draws the conclusion that the Tegra 3 is bad news?
it may be a faulty soc
From what I've heard, it's been linked directly to the flickering screen problem. Which could mean that the first batch of One X's have all faulty Soc's? I mean, it's not uncommon for there to be manufacturing difficulties for the first few batches, but this is just absurd.
Atrixx said:
From what I've heard, it's been linked directly to the flickering screen problem. Which could mean that the first batch of One X's have all faulty Soc's? I mean, it's not uncommon for there to be manufacturing difficulties for the first few batches, but this is just absurd.
Click to expand...
Click to collapse
Not all of the first batch flickered. Stop exaggerating.

5x hardware bootloop cause / fix ?

UPDATE:
Confirmation reflow fixes 5x hardware bootloop
http://forum.xda-developers.com/nex...-cause-fix-t3476794/post70123267#post70123267
UPDATE:
If you are having what appears to be hardware bootloop problem update this Poll
https://goo.gl/forms/Ga8gZgG7GEgBIply1
or see results
https://docs.google.com/forms/d/e/1...D4IdwEWZYb2NKA/viewanalytics?usp=form_confirm
====
I was looking into the eMMC chip on this phone on the assumption it was causing the bootloop. I wanted to look at other phones that have the same Toshiba HS400 chip we use. I found some references to LG G4 and then started seeing LG G4 phones were also having a bootloop problem with similar symptoms, phone just turns off all of a sudden then is stuck in bootloop.
This led to finding articles that LG acknowledged a hardware problem with solder connections on the LG G4 mainboard.
I am wondering if this is the same problem affecting Nexus 5x since the LG G4 is pretty much a cousin of the 5x.
I don't know for sure this is the problem we are seeing, just a potential culprit.
This article has more information
http://www.trustedreviews.com/opinions/lg-g4-bootloop-problem-how-to-diagnose-and-fix
In the article there is mention of a special TOT file that can be flashed on the G4 that turns off the big cores and lets the phone boot in a slow mode running on just the small cores.
This video shows you can use a SMD rework station to heat up the CPU and eMMC memory chip, reestablishing the solder connections underneath the chips and getting your phone to work again.
https://www.youtube.com/watch?v=jeuMBD9r4GI
This is the statement LG made about the LG G4
http://www.androidauthority.com/lg-g4-bootloop-petition-669421/
Here’s the full statement LG made to Android Authority:
LG Electronics has been made aware of a booting issue with the LG G4 smartphone that has now been identified as resulting from a loose contact between components. Customers who are experiencing booting issues with their LG G4s should contact their local carrier from where the G4 was purchased or a nearby LG Service Center (www.lg.com/common) for repair under full warranty.
Customers who purchased their G4 devices from non-carrier retailers should contact an LG Service Center with the understanding that warranty conditions will differ. LG Electronics is committed to providing the highest standards of product quality and customer service and apologizes for the inconvenience caused to some of our customers who initially received incorrect diagnoses.
Click to expand...
Click to collapse
sfhub said:
I was looking into the eMMC chip on this phone on the assumption it was causing the bootloop. I wanted to look at other phones that have the same Toshiba HS400 chip we use. I found the LG G4 used the same chip and then started seeing LG G4 phones were also having a bootloop problem with similar symptoms, phone just turns off all of a sudden then is stuck in bootloop.
This led to finding articles that LG acknowledged a hardware problem with solder connections on the LG G4 mainboard.
I am wondering if this is the same problem affecting Nexus 5x since the LG G4 is pretty much a cousin of the 5x.
I don't know for sure this is the problem we are seeing, just a potential culprit.
This article has more information
http://www.trustedreviews.com/opinions/lg-g4-bootloop-problem-how-to-diagnose-and-fix
In the article there is mention of a special TOT file that can be flashed on the G4 that turns off the big cores and lets the phone boot in a slow mode running on just the small cores.
This video shows you can use a SMD rework station to heat up the CPU and eMMC memory chip, reestablishing the solder connection and getting your phone to work again.
https://www.youtube.com/watch?v=jeuMBD9r4GI
Click to expand...
Click to collapse
I do know that LG gave me a new motherboard in my Nexus 5X
Hi. I tested my 5x https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=pl. It showed that emmc is Toshiba 032G74. Test passed without problems. I haven't updated to 7 yet, because I would like to avoid eventually problem with bootloop.
Wuzimu said:
Hi. I tested my 5x https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=pl. It showed that emmc is Toshiba 032G74. Test passed without problems. I haven't updated to 7 yet, because I would like to avoid eventually problem with bootloop.
Click to expand...
Click to collapse
The problem that was pointed out for the LG G4 cousin of this 5x phone is not that the eMMC chip is defective, rather the solder connection to either the eMMC or the CPU is faulty, so in that case it wouldn't matter which eMMC chip you had.
I am trying to get some discussion about what the cause of the problem is on the 5x using the G4 bootloop problem as a starting point.
As to the eMMC info, if you want the information about your emmc you can also do
Code:
su
cd /sys/bus/mmc/devices/mmc0:0001/
cat name date fwrev hwrev manfid oemid
032G74
07/1999
0x0
0x0
0x000011
0x0100
also you can reboot your phone and type
Code:
bullhead:/ $ dmesg | grep mmc0
[ 1.914434] mmc0: no vqmmc regulator found
[ 1.914459] mmc0: no vmmc regulator found
[ 1.914736] mmc0: SDHCI controller on f9824900.sdhci [f9824900.sdhci] using 32-bit ADMA
[ 2.046259] mmc0: BKOPS_EN bit = 0
[ 2.063777] mmc0: new HS400 MMC card at address 0001
[ 2.064305] mmcblk0: mmc0:0001 032G74 29.1 GiB
I found this post on google forum.
#210 [email protected]
Fixed !
A little bit tricky:
- Unlock your phone (this will wipe your data)
- Flash the lasted Nougat release NRD90S with the wipe option (fastboot -w ...) You have to flash all the partitions including userdata.
- Boot
- Do a factory reset, this is important, in some case, the userdata partition has a wrong size.
- Done !
It seems that the last OTA Nougat update bricks the phone. This not an hardware issue in my case.
Google, I hope that the next OTA update won't brick the phone !
Click to expand...
Click to collapse
Is there any info about Nexus 5x or LG G4 reliability (ratio manufactured / repaired or bootloop) like the one in hard drive reliability report? I'm curious how many phones actually got real hardware problem with this nougat bootloop because it seems google / LG hasn't responded quickly for this problem or at least address the root cause of it.
Wuzimu said:
I found this post on google forum.
Click to expand...
Click to collapse
Not all bootloops are hardware problems.
If people experience a random reboot, then bootloop issue using total stock with locked bootloader, this is almost definitely a hardware issue.
This is further confirmed if they go through the effort of flashing TOT file using LGUP and it still doesn't work. With that extra step and the above conditions, it can almost be guaranteed it is a hardware problem.
If one has unlocked bootloader and has been playing with different kernels, restoring stuff in TWRP, switching back between nougat and marshmallow, etc. then yes it could be software problem.
BTW in that post the person indicated needing to do factory reset because the userdata size is wrong. That indicates he at one point flashed the userdata partition by hand, because if you flash the userdata as part of the zip file using -w option (ie what the factory image script does) you will never have the problem of userdata being wrong size.
innov said:
Is there any info about Nexus 5x or LG G4 reliability (ratio manufactured / repaired or bootloop) like the one in hard drive reliability report? I'm curious how many phones actually got real hardware problem with this nougat bootloop because it seems google / LG hasn't responded quickly for this problem or at least address the root cause of it.
Click to expand...
Click to collapse
There is a petition for LG G4 where people were signing on to get LG to replace the G4s. It is unclear if everyone signing on was affected or not but they were up to 8k signature.
https://www.change.org/p/lg-mobile-launch-a-replacement-program-for-defective-lg-g4s
Android Authority mentioned LG acknowledged the problem and would fix phones affected but the details seemed kind of lacking. Main issue being if these would be fixed outside of warranty.
http://www.androidauthority.com/lg-g4-bootloop-petition-669421/
Here’s the full statement LG made to Android Authority:
LG Electronics has been made aware of a booting issue with the LG G4 smartphone that has now been identified as resulting from a loose contact between components. Customers who are experiencing booting issues with their LG G4s should contact their local carrier from where the G4 was purchased or a nearby LG Service Center (www.lg.com/common) for repair under full warranty.
Customers who purchased their G4 devices from non-carrier retailers should contact an LG Service Center with the understanding that warranty conditions will differ. LG Electronics is committed to providing the highest standards of product quality and customer service and apologizes for the inconvenience caused to some of our customers who initially received incorrect diagnoses.
Click to expand...
Click to collapse
I had this bootloop too, after updatong to 7.0. I spent whole day to repair my phone. Wipe, and flashing diffrent images did not work, even twrp backups with working efs. After 20 times of flashing stock images + another twrp backup phone just suddenly booted fine, and working to this day without any problem.
Soo DONT GIVE UP GUYS!
Siljorfag said:
I had this bootloop too, after updatong to 7.0. I spent whole day to repair my phone. Wipe, and flashing diffrent images did not work, even twrp backups with working efs. After 20 times of flashing stock images + another twrp backup phone just suddenly booted fine, and working to this day without any problem.
Click to expand...
Click to collapse
Sometimes if it is emmc eventually it locks out enough bad blocks to start working again.
sfhub said:
Sometimes if it is emmc eventually it locks out enough bad blocks to start working again.
Click to expand...
Click to collapse
Yeah i got mines from Google, so i would rather just replace it, plus i got a few scratches on the screen.
I'm in the same boat. I was scrolling through Instagram when the phone froze, restarted, and then just kept restarting without being able to get past the Google logo. I was on stock 7.0 (but August or September security update), stock kernel, but rooted with SuperSU 2.76 and TWRP 3.0.2-1. I couldn't even boot into TWRP, it would bootloop at the Google logo just the same. After placing it in the freezer for 30min to an hour I was able to boot into TWRP long enough to save all my data. (My original thread: http://forum.xda-developers.com/nexu...osing-t3479986)
Google also sent me a replacement, manufactured 10/2015, the original being 09/2015. I'm afraid this will likely happen again! The problem is we only get the original warranty, so I have until January 21st, 2017.
Flyview said:
The problem is we only get the original warranty, so I have until January 21st, 2017.
Click to expand...
Click to collapse
Wait really? Google said that? If so then my replacement I got a couple weeks ago runs out end of the month. That's kind of BS since its a totally different device.
Sent from my Nexus 5X using Tapatalk
EeZeEpEe said:
Wait really? Google said that? If so then my replacement I got a couple weeks ago runs out end of the month. That's kind of BS since its a totally different device.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yea I asked them twice but please confirm and report back.
Sent from my Nexus 5X using Tapatalk
Flyview said:
Yea I asked them twice but please confirm and report back.
Click to expand...
Click to collapse
Not directed at you, but honestly, for this type of problem, where it is almost definitely a manufacturing defect in components or assembly, I think the least they could do is give you a full warranty from the replacement date. It isn't like you are the only example of this.
If people wanted to organize, from the standpoint of publicity, things could look a lot worse with the media looking for stuff like this after Note 7 and now some reports of iPhone 7 batteries issues.
LG/Google have their own melting USB port problem in addition to the solder joints and/or eMMC chip problem.
Does anyone got this problem with custom rom or just on stock?
slobo2712 said:
Does anyone got this problem with custom rom or just on stock?
Click to expand...
Click to collapse
If it's really a hardware issue (which it seems like) then it doesn't matter which one.
Sent from my Nexus 5X using Tapatalk
Same here. My 5x rebooted on chrome on stock 7.1.1 and on the next boot it has frozen with graphics artefacts on google logo. On the next restart frozen again after few seconds on the settings tab. Before the die, i've reverted to 6.0 and locked the bootloader. After that definetely died. The graphics artefacts led me to think about an hardware issue...
Just realized you had a survey, filled it out, and checked out the results. Good info.
Sent from my Nexus 5X using Tapatalk
Going back to M will not reduce the risk?

Need help!! LG G4(H815) not starting

Hi all,
so here is my problem.
Day before yesterday i had a perfectly working LG g4 H815 model with s/n 511 running on firmware v20h, when i decided to root it and install some mods.
so i flashed TWRP, installed xposed and xtrememusic mod. the phone booted normally after installing these. i didn't install any modules under xposed. the phone worked perfectly for two days. however today morning it hanged while taking photo with the camera app. when restarting it got stuck at LG logo for long time. My brother(who doesn't have any technical knowledge) pulled out the battery and restarted. Again it got stuck at LG logo. thinking somthing wrong he again repeated this only to find that it didn't power on at all this time. No LG logo no notofication light nothing.
Tried charging it(although battery was aroung 60-70%), pressing power button removing the battery. still nothing. the phone is not at all powering up.
However when i connect it with USB cable with laptop, laptop makes sound of getting usb connection detected. i took it to a service centre.
the technical guy there told that IC may have been faulty. he told me that motherboard needs to be replaced. however unofficially he may try heating the IC to get it booting.
What should i do now? Is the IC really fried. had the rooting and installing mod caused it?
Please help.
PS- the phone is imported and cannot be sent back for warranty purpose.
I think you are experiencing the dreaded LG G4 bootloop. I don't think rooting or modding caused a software problem. It "may" have caused a hardware problem simply because it generated enough heat to loosen the IC that little bit that initiates the problems you are describing. I rooted and installed the stock image in Nov 2015. Two weeks ago the phone froze - restarted and then could not be booted. LG sent me a Fedex label and I sent it off. Ten days later I received the same phone back. I assume they replaced the mainboard.
You should contact LG directly. I saw a class action suit that was called off because it appeared that LG will fix this particular problem (failed mainboard) out of warranty. Anyone please correct me on this if I'm wrong.
dsteinschneider said:
I think you are experiencing the dreaded LG G4 bootloop. I don't think rooting or modding caused a software problem. It "may" have caused a hardware problem simply because it generated enough heat to loosen the IC that little bit that initiates the problems you are describing. I rooted and installed the stock image in Nov 2015. Two weeks ago the phone froze - restarted and then could not be booted. LG sent me a Fedex label and I sent it off. Ten days later I received the same phone back. I assume they replaced the mainboard.
You should contact LG directly. I saw a class action suit that was called off because it appeared that LG will fix this particular problem (failed mainboard) out of warranty. Anyone please correct me on this if I'm wrong.
Click to expand...
Click to collapse
Hi thanks for the help.
But isn't the dreaded bootloop is that where the phone is stuck at the LG logo. Mine isn't booting at all. And the bootloop problem is due to big cores or such and not due to ic?
Mine wouldn't start at all - it bootlooped once for about a split second - then it was dead
Same is the problem with me. Bootlooped twice and then its completely dead. I have tried contacting Lg UK. Lets see what they say.
Ok so i got a reply from LG and they suggested me some steps to take (which are obviously not useful as it is completely dead). however they have also told me that they are willing to help me and asked me about details of purchase etc and "whether it was rooted".
so what should i reply rooted or not? will they detect it as it is dead.
dbzgoku said:
Ok so i got a reply from LG and they suggested me some steps to take (which are obviously not useful as it is completely dead). however they have also told me that they are willing to help me and asked me about details of purchase etc and "whether it was rooted".
so what should i reply rooted or not? will they detect it as it is dead.
Click to expand...
Click to collapse
Sorry to be late on reply. I advise to not answer question whether phone was rooted. Here is my reasoning:
1. This problem is widely occuring - only a tiny percentage of people root their phones therefore question is irrelevant.
2. The problem is known to be that an IC becomes loose most likely due to heat - a better question would be - do you place the phone on a hot dashboard with GPS running while you are charging?
dsteinschneider said:
Sorry to be late on reply. I advise to not answer question whether phone was rooted. Here is my reasoning:
1. This problem is widely occuring - only a tiny percentage of people root their phones therefore question is irrelevant.
2. The problem is known to be that an IC becomes loose most likely due to heat - a better question would be - do you place the phone on a hot dashboard with GPS running while you are charging?
Click to expand...
Click to collapse
thanks for the reply (although late). i have already sent the phone to LG replying as no root. Lets hope they repair it without any problems.
second i didnt do anything of anysort like placing on hot dashboard or such. one day while opening the camera app it decided to just hang and later on die on me.
I hope you didn't think I was saying you might have done something that would overheat your phone such as my second example. I was trying to come up with an example reason the IC loosens. Even if you did that the phone should survive such conditions. Let's hope the replacement motherboards somehow do better. My guess is that the soldering job is fine, the problem is probably bad design that doesn't "vent" the heat from chip.
dsteinschneider said:
I hope you didn't think I was saying you might have done something that would overheat your phone such as my second example. I was trying to come up with an example reason the IC loosens. Even if you did that the phone should survive such conditions. Let's hope the replacement motherboards somehow do better. My guess is that the soldering job is fine, the problem is probably bad design that doesn't "vent" the heat from chip.
Click to expand...
Click to collapse
so what do you suggest after repair should i keep it or sell it? Lg g4 is no doubt the best phone when considering the value for money. no phone even twice in price comes close in camera and screen quality especially. but the unreliability of this phone has made me to consider selling it as soon as i get it back.
I'd keep it if your new board is high serial
lukem99626 said:
I'd keep it if your new board is high serial
Click to expand...
Click to collapse
Well my old board was also high serial, beginning with 511
I'm going to take my chances - it's a great phone until it bootloops. I'm going to avoid scenarios best I can that could result in the phone heating up inside. That would be charging only if absolutely necessary while in my ProClip dash mount if the car is hot, using backup battery after depletion instead of charging more often etc. Thinking back I rarely put the phone into heat inducing situations - normal use results in the IC becoming loose at the 1 year mark. If mine bootloops exactly a year from now and LG fixes it again I'm an LG fan. If they blow me off no more LG.
I really regret not paying it off early and taking the $15/month deal for an S7 Edge last month
dbzgoku said:
Well my old board was also high serial, beginning with 511
Click to expand...
Click to collapse
I mean like 611 ect thats what i got from lg
dsteinschneider said:
I'm going to take my chances - it's a great phone until it bootloops. I'm going to avoid scenarios best I can that could result in the phone heating up inside. That would be charging only if absolutely necessary while in my ProClip dash mount if the car is hot, using backup battery after depletion instead of charging more often etc. Thinking back I rarely put the phone into heat inducing situations - normal use results in the IC becoming loose at the 1 year mark. If mine bootloops exactly a year from now and LG fixes it again I'm an LG fan. If they blow me off no more LG.
I really regret not paying it off early and taking the $15/month deal for an S7 Edge last month
Click to expand...
Click to collapse
Well lg did mention in my communication with them that this carries 2 year warranty.
lukem99626 said:
I mean like 611 ect thats what i got from lg
Click to expand...
Click to collapse
Didn't know that serials have gone so high
dbzgoku said:
Didn't know that serials have gone so high
Click to expand...
Click to collapse
I brought a g4 in the new year sale it has the serial of 611 i had a 601 few months back i returned it ran hot and laggy the 611 one is cool running and lag free so i think something changed

Questions about bootloop, warranty & repairs and heatsink mods

Hello!
Unfortunately, just some days ago my 5X died. Was on the table, it rebooted itself and then it was stuck in a bootloop. I wasn't even able to use the recovery, and none of the 4-cores mod worked to help me get some of my files. I even opened it, disconnected the battery and reconnected it, but nothing.
So, I send it oot for repairments; luckily I still have 3 months of warranty (I live in Italy). However, I have some questions that maybe you can help me clear out:
Will LG be able to see that I opened the back cover of the phone and also that I modified its software?
Before sending it, since at least fastboot was working without issue, I flashed a stock factory image of Oreo and re-locked the bootloader (also like this, it wasn't booting however), so it was totally stock, but they can see that the bootloader has been unlocked and relocked?
I'm a little worried about LG discovering these things and make me pay for the repairments...
Hoping to getting it back repaired for free, will it be safe from the bootloop issue or it can happen again? Since it's a known problem, does LG started repairing with motherboards with better solderings, or I will find myself in the same situation as now?
If answers to question 2 is "no, they will put inside it the same faulty motherboards", there's anything I can do to prevent this issue? I saw someone using copper plate heatsinks to contrast heat, what do you think about that?
Thank you!
Punkiderma said:
Hello!
Unfortunately, just some days ago my 5X died. Was on the table, it rebooted itself and then it was stuck in a bootloop. I wasn't even able to use the recovery, and none of the 4-cores mod worked to help me get some of my files. I even opened it, disconnected the battery and reconnected it, but nothing.
So, I send it oot for repairments; luckily I still have 3 months of warranty (I live in Italy). However, I have some questions that maybe you can help me clear out:
Will LG be able to see that I opened the back cover of the phone and also that I modified its software?
Before sending it, since at least fastboot was working without issue, I flashed a stock factory image of Oreo and re-locked the bootloader (also like this, it wasn't booting however), so it was totally stock, but they can see that the bootloader has been unlocked and relocked?
I'm a little worried about LG discovering these things and make me pay for the repairments...
Hoping to getting it back repaired for free, will it be safe from the bootloop issue or it can happen again? Since it's a known problem, does LG started repairing with motherboards with better solderings, or I will find myself in the same situation as now?
If answers to question 2 is "no, they will put inside it the same faulty motherboards", there's anything I can do to prevent this issue? I saw someone using copper plate heatsinks to contrast heat, what do you think about that?
Thank you!
Click to expand...
Click to collapse
Hi, I'm Italian too and I had your same problem.
1) My phone died and 20 days before the end of the warranty and I sent it to the repair center.
As you, I opened the device and also I wasn't stock, so I reflashed google stock image and I re-locked the bootloader. The repair center has fixed my device changing the mobo and they didn't charged me for anything.
2) I don't know if they have a new rev. of the mobo that fixes the bootloop problem, but I'm going to apply the copperhead heatsink mod and maybe I will underclock the cpu with EX kernel.
3) I hope that the copperhead mod works, I saw some benchmarks and it seems that this heatsink will lower the temperature by 5/7 degrees.
I'm sorry for my English
CapraNorvegese said:
Hi, I'm Italian too and I had your same problem.
1) My phone died and 20 days before the end of the warranty and I sent it to the repair center.
As you, I opened the device and also I wasn't stock, so I reflashed google stock image and I re-locked the bootloader. The repair center has fixed my device changing the mobo and they didn't charged me for anything.
2) I don't know if they have a new rev. of the mobo that fixes the bootloop problem, but I'm going to apply the copperhead heatsink mod and maybe I will underclock the cpu with EX kernel.
3) I hope that the copperhead mod works, I saw some benchmarks and it seems that this heatsink will lower the temperature by 5/7 degrees.
I'm sorry for my English
Click to expand...
Click to collapse
We have exactly the same situation, I just ordered the copper plates, let's see if it will work! As of now, even if I got my 5X back from warranty, I'm still using my galaxy nexus because I don't want the 5X to overheat, I will start using it again after the heatsink mod

Reason for bootloop?

Does anyone know the cause of the bootloop issue with this device? Mine freezes at the Google screen, doesn't even make it to the G screen. Occasionally returns to the recovery screen with the warning of "User data is corrupt". I've tried OTA's to no avail. Sadly my bootloader is locked as it was a new phone which got in to the jam when I upgraded to Pie. One thing I have tried was putting the device in to the freezer which actually produced some results; it got to the shapes screen before freezing! Only reason I tried this was because if the 5x bootloop issue, that helped to boot it sometimes! I might try sticking the motherboard in to the oven in a bit too..... as a last resort.
One thing I would like to know is if there is anyway around this flashing the .kdz files through lg toolkit? If so, anyone have any lying around? Anyone? Bueller? Bueller?
Anyways, thanks in advance,
Dom
Update:
Heating the logic board didn't work, but it did show how amazingly easy this phone is to fix from a component factor!!

Categories

Resources