HTC 10 Randomly Restarts - Gets Stuck on Bootloop - HTC 10 Questions & Answers

So I am new to the XDA community, but I have not found anything that discusses this already. Has anyone with the HTC 10 had the issue of the phone restarting and then getting caught in a BootLoop? I have tried going through the Recover from BootLoaded and Wiping Data/Factory Reset but I am still having this issue.
Any suggestions?

Hugglester said:
So I am new to the XDA community, but I have not found anything that discusses this already. Has anyone with the HTC 10 had the issue of the phone restarting and then getting caught in a BootLoop? I have tried going through the Recover from BootLoaded and Wiping Data/Factory Reset but I am still having this issue.
Any suggestions?
Click to expand...
Click to collapse
did you install xposed? Rooted? Any other modifications?

jollywhitefoot said:
did you install xposed? Rooted? Any other modifications?
Click to expand...
Click to collapse
Nothing, had it out of the box for about an hour.

Hugglester said:
Nothing, had it out of the box for about an hour.
Click to expand...
Click to collapse
return it then. something isn't right.

Hugglester said:
So I am new to the XDA community, but I have not found anything that discusses this already. Has anyone with the HTC 10 had the issue of the phone restarting and then getting caught in a BootLoop? I have tried going through the Recover from BootLoaded and Wiping Data/Factory Reset but I am still having this issue.
Any suggestions?
Click to expand...
Click to collapse
Hi there.
Yes I have encountered this issue. But I'm not sure if I had it from the box or I got it after the update.
When I got this issue and my phone started boot looping, the only way I tried to recover from it is by hooking up the charger and I got it too boot up, it showed an error report and I sent the error report to HTC.
So the phone works normally after it boots, but is this software related? Should I wait for the next update or also replace my phone, it's so hard after setting up everything to again go through the annoying process of getting a replacement or a fix just to find that the issue still happens or is caused by the update.
UPDATE:
Ok so after testing and trying to recreate the issue I have discovered that when trying to do a normal restart or power off the phone while the phone is on battery this issue doesn't happen.
The last time it happened is when my phone battery drained and powered off then I hook it up to the charger and went to sleep, when I woke up I removed the phone from the charger and powered it on then the issue happened and the phone went into a boot loop, tried restarting with no luck then I figured I would plug in the charger again, then it booted up normally. (Unplugging the charger from the phone makes a weird metallic noise, so I checked my USB type c port and it wasn't lose or rattly). Anyways when the phone booted up it had 99% charge while I was certain it should have been full at 100%, I waited for it till it got to a 100% then unplugged it.
So I tried my best to cover how this issue happened to me, and if it happens I would get the error report thing that the phone had unexpected boot or something like that.
Could it be because I'm using adoptable storage?
Is it hardware or software related?
Could it be a corrupt file or something in the file system?
Or I just need to wait for the next update?

So my issue came right out of the box. I was trying to get everything transferred over from my old HTC device and about half way through downloading my apps the issue started for me. Tried similar steps to you as well with charging the phone and it was only off charger when I had the issue. I am returning the phone and getting a new one as of now. Not sure what else to do to fix it.
p1r8t3 said:
Hi there.
Yes I have encountered this issue. But I'm not sure if I had it from the box or I got it after the update.
When I got this issue and my phone started boot looping, the only way I tried to recover from it is by hooking up the charger and I got it too boot up, it showed an error report and I sent the error report to HTC.
So the phone works normally after it boots, but is this software related? Should I wait for the next update or also replace my phone, it's so hard after setting up everything to again go through the annoying process of getting a replacement or a fix just to find that the issue still happens or is caused by the update.
UPDATE:
Ok so after testing and trying to recreate the issue I have discovered that when trying to do a normal restart or power off the phone while the phone is on battery this issue doesn't happen.
The last time it happened is when my phone battery drained and powered off then I hook it up to the charger and went to sleep, when I woke up I removed the phone from the charger and powered it on then the issue happened and the phone went into a boot loop, tried restarting with no luck then I figured I would plug in the charger again, then it booted up normally. (Unplugging the charger from the phone makes a weird metallic noise, so I checked my USB type c port and it wasn't lose or rattly). Anyways when the phone booted up it had 99% charge while I was certain it should have been full at 100%, I waited for it till it got to a 100% then unplugged it.
So I tried my best to cover how this issue happened to me, and if it happens I would get the error report thing that the phone had unexpected boot or something like that.
Could it be because I'm using adoptable storage?
Is it hardware or software related?
Could it be a corrupt file or something in the file system?
Or I just need to wait for the next update?
Click to expand...
Click to collapse

Hugglester said:
So my issue came right out of the box. I was trying to get everything transferred over from my old HTC device and about half way through downloading my apps the issue started for me. Tried similar steps to you as well with charging the phone and it was only off charger when I had the issue. I am returning the phone and getting a new one as of now. Not sure what else to do to fix it.
Click to expand...
Click to collapse
Hi there, i think the newer update fixed the issue for me. Hope this helps.

Any news?
HTC One M9 cihazımdan Tapatalk kullanılarak gönderildi

same issue for me, just made an update and then got the bootloop.
even ****tory reset didnt help
any idea what to do.
phone never rooted

Your phones right out of the box and on the stock rom should be in perfect working order. If not, I would send it back for a replacement pronto. Don't wait for an update.

you guys got an external sdcard in the phone?
It's reported by a couple of users that the boot up process took a few cycles for them till it booted.
It was caused by a corrupted sdcard. Try to take the external sdcard out and see if the issue is fixed.
If yes, try to format it with the overwrite option in the "SDFormatter" program..if that does not help. get a new sdcard.

El mismo problema de bootloop después de actulizar
me ocurrió el mismo problema después de actualizar mi HTC 10, luego de actualizarlo al Android 7 llegó una nueva actualización luego de completada la descarga procedió a instalarse la actualización y aquí quedo el teléfono en bootloop por más de una hora, se soluciono el problema conectando el teléfono a cargar la batería después de pocos minutos el teléfono arranco correctamente. Al completar la descarga de esta ultima actualización el teléfono tenia más del 90% de carga aun así se generó este problema de bootloop.

I am experiencing the same problem. The phone has the latest update installed. (not rooted, bootloader locked).
Initially soft (backlit) keys weren't working, so i tried restarting and it never booted up as its stuck in boot loop. I cannot go to any recovery modes.
Its so disappointing ! I'm in India but I bought this phone from middle-east on December 2016 and I have to sent it back there for warranty claim which will not happen very soon.
Have anyone found a solution for this problem ??

jeraldsm said:
I am experiencing the same problem. The phone has the latest update installed. (not rooted, bootloader locked).
Initially soft (backlit) keys weren't working, so i tried restarting and it never booted up as its stuck in boot loop. I cannot go to any recovery modes.
Its so disappointing ! I'm in India but I bought this phone from middle-east on December 2016 and I have to sent it back there for warranty claim which will not happen very soon.
Have anyone found a solution for this problem ??
Click to expand...
Click to collapse
I had a similar issue....backlit keys stop responding, a few days later the phone ran out of battery during the night and I got the boot loop when I turned it on the morning after. I can just get into the bootloader (no normal boot, no recovery, no download mode). An purchased in the US but I am now in Argentina .

Same here
I had the same issue. I factory reset a couple of times. I even rooted and installed custom ROM. But it still would do it (though much less frequently). I ultimately exchanged it with a warranty phone with my carrier. Crossing my fingers that my phone will stop doing this.

Hugglester said:
So I am new to the XDA community, but I have not found anything that discusses this already. Has anyone with the HTC 10 had the issue of the phone restarting and then getting caught in a BootLoop? I have tried going through the Recover from BootLoaded and Wiping Data/Factory Reset but I am still having this issue.
Any suggestions?
Click to expand...
Click to collapse
I have same promlem

I had the same problem... After the last update, it entered a BootLoop... It was pretty difficult to even shut down the phone! It got so hot I was afraid it's going to burn out its motherboard...
Mine is not rooted or anything of the sort...
Eventually I managed to shut it down...
Went to claim my warranty... They opened it up... Don't really know what they did... But before throwing it in the garbage... I tried one more time to power it up... And it worked !
I've stopped all the updates since and I never let it run out of battery.. It's clearly a software problem.
And it's not related to HTC only. Samsung has it too. I know for a fact that the S8 has it....

I am having the same problem , has anyone found a fix ?

I had the same problem with mine. Bought it used from Swappa and out of the box it would randomly reboot. I also noticed the phone was abnormally hot doing nothing on the lockscreen or homepage. The random reboots quickly escalated to bootloop. Unfortunately I had to return it. I think the phone during initial stages of booting up relies purely on internal battery power, regardless if it's plugged into AC power or not. So, when the internal battery is dead, in the sense that it can no longer provide sufficient power even at a fully charged state, then you get stuck in the eternal bootloop.
I believe the only fix is to replace the battery with a new cell. However, due to the complexity of the tear down, I literally could not find one shop that would be willing to do it. Otherwise, I would have sucked it up and paid to have a new battery put in.

j to the 4n said:
you guys got an external sdcard in the phone?
It's reported by a couple of users that the boot up process took a few cycles for them till it booted.
It was caused by a corrupted sdcard. Try to take the external sdcard out and see if the issue is fixed.
If yes, try to format it with the overwrite option in the "SDFormatter" program..if that does not help. get a new sdcard.
Click to expand...
Click to collapse
I've been encountering exactly this problem. Anywhere after 40% it'll just die and get stuck in a boot loop until I hook it up to a charger. If the boot loop happens multiple times before I manage to get to the charger, widgets stop working and I'll have to wipe the cache. Sometimes when the phone dies, it'll have said 20% or so before dying, but after hooking it up the charger it'll claim 2%.
So the battery or battery level sensor ain't great, that's a given. But 40% and dying? Something's wrong.
So after it completely died and refused to turn on again because it went through the boot loop until it just stopped trying, I decided to try this trick. I removed the SD card, tried everything to turn it on, finally getting it going by long-pressing volume down and power, went to recovery mode, rebooted the phone and it's working again. For now.
I'm not sure whether the SD card removal will fix the entire problem (or at least limit it to a ****ty battery) but I'll report back if that's the case. At least it got it to boot again, so thanks for at least giving me a strand of hope

Related

Weird charging issues

Ever since upgrading to newest firmware using HTC fastboot (even after ruu back to stock) I have been having the weirdest charging issues. These issues occur when on qc 2.0, standard 2.0, or even standard HTC charger, different cables... Well basically my phone is not overheated right now but plugged into the wall and is not charging. I plugged it in last night everything was fine. Woke up today to 50% battery. I tried unplugging, tried powering off then plugging back in, tried booting to recovery plugging in, restarting phone, changing cords, changing power adapter... Just randomly does not want to charge then after a handle full of times just decides it wants to charge. This has happened over the course of this week and is just driving me crazy. I am s off. Rooted. Custom twrp recovery 2.8.7.0. On viper one 3.0. But this issue is persistent even when in the powered off state... I have no idea wtf could be causing this issue. Only thing I can think of is firmware or something. I don't get it. Anyone have any issues similar? Or fix? Only way is to cross my fingers and hope the connection starts a charge after a lot of plugging and unplugging. Please help thanks.
magesticschu said:
Ever since upgrading to newest firmware using HTC fastboot (even after ruu back to stock) I have been having the weirdest charging issues. These issues occur when on qc 2.0, standard 2.0, or even standard HTC charger, different cables... Well basically my phone is not overheated right now but plugged into the wall and is not charging. I plugged it in last night everything was fine. Woke up today to 50% battery. I tried unplugging, tried powering off then plugging back in, tried booting to recovery plugging in, restarting phone, changing cords, changing power adapter... Just randomly does not want to charge then after a handle full of times just decides it wants to charge. This has happened over the course of this week and is just driving me crazy. I am s off. Rooted. Custom twrp recovery 2.8.7.0. On viper one 3.0. But this issue is persistent even when in the powered off state... I have no idea wtf could be causing this issue. Only thing I can think of is firmware or something. I don't get it. Anyone have any issues similar? Or fix? Only way is to cross my fingers and hope the connection starts a charge after a lot of plugging and unplugging. Please help thanks.
Click to expand...
Click to collapse
Sounds like a hardware issue not software. but not sure. just my 02. cents
If running the RUU for 1.33.605.15 doesn't solve your charging issue, my first thought would be hardware.
That said, HTC has definitely been having trouble with charging and battery issues, so we've gotta hope that the final release of 5.1 for us will resolve the problem. The currently leaked 2.6.605.10 is most likely not the version that will be released publicly.
After troubleshooting I think the charging was being stopped due to overheating while charging. In standby. Had a live wallpaper I think was causing the high Temps. Changed to normal wallpaper and disabled all but two cores and Temps have been cool and haven't had any charging issues since (fingers crossed as its only been one day lol)
magesticschu said:
After troubleshooting I think the charging was being stopped due to overheating while charging. In standby. Had a live wallpaper I think was causing the high Temps. Changed to normal wallpaper and disabled all but two cores and Temps have been cool and haven't had any charging issues since (fingers crossed as its only been one day lol)
Click to expand...
Click to collapse
Still doesn't explain off state not charging tho so idk I'll see after a few more days see if it happens again
O had a similar issue, where it would go from charging to not charging every couple of seconds. I have not had these issues with Fluent or Adrenaline. There's a post in the Adrenaline thread about how to calibrate your battery. Try that, also. FWIW, when I installed Viper after being on Fluent, and calibrated the battery, I haven't had any more issues.
I have the same problem since updating to 2.6.605.15. The phone was fine until the update rolled out. After several hours of troubleshooting with HTC I got a replacement from them and am now updating that one to see if the problem remains. What a PIA this is since it takes all day to set up your phone again when you get a replacement.
Tom Huot said:
I have the same problem since updating to 2.6.605.15. The phone was fine until the update rolled out. After several hours of troubleshooting with HTC I got a replacement from them and am now updating that one to see if the problem remains. What a PIA this is since it takes all day to set up your phone again when you get a replacement.
Click to expand...
Click to collapse
Why would it take all day?
Just restore your last backup to your new device with TWRP. :good:
Instantly back to where you were.
Please tell me how to do this.
sdamark said:
Why would it take all day?
Just restore your last backup to your new device with TWRP. :good:
Instantly back to where you were.
Click to expand...
Click to collapse
What is TWRP?
Tom Huot said:
What is TWRP?
Click to expand...
Click to collapse
TWRP = Team Win Recovery Project.
That's your recovery. You do make backups, don't you?
Plug your old device into a computer, copy and paste your latest backup to your computer.
Plug new device into computer, drop backup onto new device.
Boot new device into recovery and restore backup from your old device.
Now you are right where you left off.
Or...
Back up old device in TWRP to external SD card.
Move SD card to new device, boot to recovery, restore backup from external SD.
BOOM done.
Root?
Do you have to root the phone?
sdamark said:
TWRP = Team Win Recovery Project.
That's your recovery. You do make backups, don't you?
Plug your old device into a computer, copy and paste your latest backup to your computer.
Plug new device into computer, drop backup onto new device.
Boot new device into recovery and restore backup from your old device.
Now you are right where you left off.
Or...
Back up old device in TWRP to external SD card.
Move SD card to new device, boot to recovery, restore backup from external SD.
BOOM done.
Click to expand...
Click to collapse
Tom Huot said:
Do you have to root the phone?
Click to expand...
Click to collapse
You need to have s-off and bootloader unlocked. Currently the only way to do this on Verizon is with a clip or a java card. There is a post in general about java cards with plenty of information. Currently there is no way to root without TWRP and thus you need s-off and the bootloader unlocked.
Sent from my HTC6535LVW using Tapatalk

Random bootloop, Can't find a fix

Good morning guys,
Last night, i was just using my phone like normal when it froze, crashed, and began to bootloop.
I've tried battery pulls, I've tried to factory reset using the volume down + power combo, I've tried to wipe cache and enter safe mode but none of this worked
I was on 10b firmware but since none of the above worked, I tried to KDZ to a stock 11a which still keeps my phone at a bootloop. All I see if the LG logo at startup and a crash.
do you have any suggestions on how I can try to fix this? according to reddit this random bootloop has been happening to multiple people
thanks in advance for your help
It started happening to me, as well, over the weekend. My phone crashed and started bootlooping, stuck at the LG startup screen where it stalls for a few seconds and then goes black. Every now and then it will boot up properly, but the phone crashes after about two minutes and starts bootlooping again. I cannot manage to wipe the phone because it so seldom boots properly. I noticed that the phone gets very hot. I suppose that I will need to return it to Verizon for warranty replacement, but I hate having so much data on the phone when I return it. I was doing nothing unusual with the phone when this started happening.
Katmeat said:
It started happening to me, as well, over the weekend. My phone crashed and started bootlooping, stuck at the LG startup screen where it stalls for a few seconds and then goes black. Every now and then it will boot up properly, but the phone crashes after about two minutes and starts bootlooping again. I cannot manage to wipe the phone because it so seldom boots properly. I noticed that the phone gets very hot. I suppose that I will need to return it to Verizon for warranty replacement, but I hate having so much data on the phone when I return it. I was doing nothing unusual with the phone when this started happening.
Click to expand...
Click to collapse
yeah it's definitely weird. I was rooted on 10b holding out for a bootloader exploit down the line.
I called up verizon and theyre shipping me a new g4 since it was still under the 1 year warranty. I hope it's still rootable with the firmware it'll ship with
Same here
Hey guys! I thought I'd reply instead of making a new post because I think I'm in the same boat. My dads phone has just started doing this, but the weird thing is he wasn't rooted! I was able to get it to the recovery and tried the wipe cache and safe mode options, it didn't do anything.. I then tried flashing the kdz but no luck..
Hope some of the smart folks here can help us!
-Travis
I was fortunate to get it into download mode so I kdz it back to 11a stock so as to wipe all data, thankfully. The stock reset made no difference, as it still would rarely boot, and even when it did boot it would crash fairy quickly. My warranty replacement should arrive tomorrow.
Katmeat said:
I was fortunate to get it into download mode so I kdz it back to 11a stock so as to wipe all data, thankfully. The stock reset made no difference, as it still would rarely boot, and even when it did boot it would crash fairy quickly. My warranty replacement should arrive tomorrow.
Click to expand...
Click to collapse
yup, i kdzed up to 11a and it went from modified status to official so hopefully that wiped everything on my phone too. My new one will be coming in tomorrow
I just received my warranty replacement, and it is an 11a factory refurb device that looks like new. No noticeable screen lag thus far, but it is running awfully warm as it restores all my apps and some data from the Verizon Cloud.
Katmeat said:
I just received my warranty replacement, and it is an 11a factory refurb device that looks like new. No noticeable screen lag thus far, but it is running awfully warm as it restores all my apps and some data from the Verizon Cloud.
Click to expand...
Click to collapse
Is there any downside to refurbished devices?
pfizzle said:
Is there any downside to refurbished devices?
Click to expand...
Click to collapse
I think not, and I actually prefer buying factory refurbs in most cases when possible because you are assured of the product being carefully inspected. In this case, my phone looks brand new and is performing just fine. The initial heat concern has gone away as the phone has settled in.
Please Help!!!!!
I'm trying to help my sister out who is in Ecuador right now. Her phone was a little slow today and kept going to the red verizon sign - so she turned it off and took the battery out.... when she turned it on it said the SD card is blank. She has 800 pics on it from her trip and is wondering if there is anything to get them back???? Please help!!!! Any suggestions would be helpful!
weird i had the same thing happen a few days ago also...using new phone now.
This issue happened to me out of no where last week and had a replaement sent. Wasn't rooted
Sent from my VS986 using Tapatalk
same problem here ...
rooted device. nothing special today .. and then: bootloops.
When i remove the battery for a longer time, sometimes the g4 boots properly. But after a few minutes it'll bootloop again.
Any ideas?
FootballFan141 said:
Hey guys! I thought I'd reply instead of making a new post because I think I'm in the same boat. My dads phone has just started doing this, but the weird thing is he wasn't rooted! I was able to get it to the recovery and tried the wipe cache and safe mode options, it didn't do anything.. I then tried flashing the kdz but no luck..
Hope some of the smart folks here can help us!
-Travis
Click to expand...
Click to collapse
What's the manufacturing date of the phone that failed? I'm trying to figure out if it's just a matter of time (the May ones failed first, then June), or if it's only May boards with the issue.

HELP - (Hard) Brick Z1C

Hi guys, I've a big problem, and it's very strange:
today I've updated lucky patcher, after installed it, the phone showed screen of the turning off. I started again the phone, but at the start screen, showed again the turn off screen. I tried to wipe and restore backup, samre problem. I tried to flash a stock firmware but after the sony logo i've a black screen with phone on. I really don't know what to do, I need your help. thanks a lot :crying::crying::crying:
ULT][MO said:
Hi guys, I've a big problem, and it's very strange:
today I've updated lucky patcher, after installed it, the phone showed screen of the turning off. I started again the phone, but at the start screen, showed again the turn off screen. I tried to wipe and restore backup, samre problem. I tried to flash a stock firmware but after the sony logo i've a black screen with phone on. I really don't know what to do, I need your help. thanks a lot :crying::crying::crying:
Click to expand...
Click to collapse
If you have revovery, you can just delete Lucky Patcher apk from /system or /data, (wherever it is). It's not a hard brick...
levone1 said:
If you have revovery, you can just delete Lucky Patcher apk from /system or /data, (wherever it is). It's not a hard brick...
Click to expand...
Click to collapse
Very bad news: I tried to flash a stock L, after flashed I started it, but it shutted down at waves bootanimation. I putted it on charge and showed this message "your device turned off due to overheating ,charging will continue once the device cools down".
An expert technician said to me that's a processor's cooling problem and, in his opinion, it is impossible to fix it. except sendind it directly to sony. But it should be very very expensive...
ULT][MO said:
Very bad news: I tried to flash a stock L, after flashed I started it, but it shutted down at waves bootanimation. I putted it on charge and showed this message "your device turned off due to overheating ,charging will continue once the device cools down".
An expert technician said to me that's a processor's cooling problem and, in his opinion, it is impossible to fix it. except sendind it directly to sony. But it should be very very expensive...
Click to expand...
Click to collapse
Did you already try waiting until it cools down and restarting? I would try that, or also try reflashing after cool down. First boot after flash is very long, and phone does get hot. If you were already overworking it with bootloops and stuff, and then tried to flash a rom, it might be a bit much...
levone1 said:
Did you already try waiting until it cools down and restarting? I would try that, or also try reflashing after cool down. First boot after flash is very long, and phone does get hot. If you were already overworking it with bootloops and stuff, and then tried to flash a rom, it might be a bit much...
Click to expand...
Click to collapse
Thanks levone for your answer, and sorry if it's passed a lot of time.
Unfortunately i tried everything coud be possible. tomorrow I'll try with an expert friend to open it and see the problem. A technician said to me that probably it's a cooling problem. Processor can't be cooled and phone shut off, or probably is (again) a battery problem. Soon i'll write if i've found a solution, also to try to help someone who could have a similar problem (i hope not).
How can the "processor" not be cooled? There is no cooling hardware that could stop working.. It could still be another hardware defect, yeah.. Have you wiped it or did you just flash system/baseband/kernel/etc ?
levone1 said:
Did you already try waiting until it cools down and restarting? I would try that, or also try reflashing after cool down. First boot after flash is very long, and phone does get hot. If you were already overworking it with bootloops and stuff, and then tried to flash a rom, it might be a bit much...
Click to expand...
Click to collapse
I've used Z1C in sauna (where is 100°C degrees) and the phone becomes so hot it is untouchable to hold and even struggling to play video playback (under clocking). Then i know it is too hot and take it out.
It takes ~1 min and it is cooled enough where is it fast and smooth again. Never has it said too hot, shutting off or something similar. Then again i'm using KitKat which doesn't maybe have that function?
I'd say issue related to battery or software as i had same problem after installing Lucky Patcher. Got bootloop after restarting.
I also used restoring and it succeeded but somehow Lucky Pather was still present but bootloop problem was cured.

My Nexus 5X just died - question about warranty

Hello everyone,
to this day I was a happy owner of Nexus 5X - it was doing pretty well, I even installed Pure Nexus ROM on this device to make it even better and this is where the trouble begins. Today I was listening to music on my device when it froze. I was like - "yeah, another freeze, I will just reboot my phone". It didn't help. The phone started rebooting, but it froze again and then the screen went black. Forever. Now my device is not responding to any commands, I can not even charge it. I still have few months of warranty left, so this is where my question begins:
is it possible for LG employees to detect that my device was rooted and so to cancel my warranty if the phone is totally dead? I think that the components died.
Thanks for your help. :good:
I had the same thing happen to me 21 days after my warranty expired. They told me the motherboard was bad and it had to be replace, and it was going to cost $72. My device was fully rooted and they made no mention of that when I asked for the full diagnostic report from their technician. I would say it is safe to say they can't tell if it was rooted if you motherboard went out like mine.
- Side note: my phone crashes almost once a day since I've gotten back and had small cracks in the back from where they pried it open. But I can't go without my phone for another 3 weeks again while they fix it.
Razeer123 said:
Hello everyone,
to this day I was a happy owner of Nexus 5X - it was doing pretty well, I even installed Pure Nexus ROM on this device to make it even better and this is where the trouble begins. Today I was listening to music on my device when it froze. I was like - "yeah, another freeze, I will just reboot my phone". It didn't help. The phone started rebooting, but it froze again and then the screen went black. Forever. Now my device is not responding to any commands, I can not even charge it. I still have few months of warranty left, so this is where my question begins:
is it possible for LG employees to detect that my device was rooted and so to cancel my warranty if the phone is totally dead? I think that the components died.
Thanks for your help. :good:
Click to expand...
Click to collapse
Sounds TOO familiar. Like exactly what happened to my first N5X mid-March. I was listening to Spotify, the device's software froze and it never turned on again. I connected it to my PC and I happened to have the dreaded Qualcomm HS-USB QDloader 9008 error (that's what showed up in Device Manager). The only thing I did different and for the first time before that happened was using F2FS. I have no idea if it's related.
theGekkoST said:
I had the same thing happen to me 21 days after my warranty expired. They told me the motherboard was bad and it had to be replace, and it was going to cost $72. My device was fully rooted and they made no mention of that when I asked for the full diagnostic report from their technician. I would say it is safe to say they can't tell if it was rooted if you motherboard went out like mine.
- Side note: my phone crashes almost once a day since I've gotten back and had small cracks in the back from where they pried it open. But I can't go without my phone for another 3 weeks again while they fix it.
Click to expand...
Click to collapse
nirogu325 said:
Sounds TOO familiar. Like exactly what happened to my first N5X mid-March. I was listening to Spotify, the device's software froze and it never turned on again. I connected it to my PC and I happened to have the dreaded Qualcomm HS-USB QDloader 9008 error (that's what showed up in Device Manager). The only thing I did different and for the first time before that happened was using F2FS. I have no idea if it's related.
Click to expand...
Click to collapse
Today the diode started to blink red, I connected Nexus 5X to charger and waited ~30 mins to charge a bit. Then I wanted to flash stock system + recovery and unroot but when booting to recovery device again stopped on Google logo and went black. From this moment no sign of beeing alive. I think I'll wait to this situation to happen again and will try to install stock firmware.
Mine would flash red when the battery was completely drained. I could plug it in and get the battery logo, but if I tried to boot it up; the screen would hit to the Google logo and then just go black. I could wait a day and the red battery light would flash again when I pressed the power button. After a few times of doing this, it wouldn't even charge anymore.
Honestly I seriously doubt they have time to go Sherlock Holmes on your phone and void your warranty. They are most likely going to get your phone see if it boots, if not replace the motherboard and go on.
Not to mention if its not responding to anything at this point what do you have to lose. Send it in and see what happens.
This problem is frequent on the Nexus 5x, V10,V20,G4 and G5, the only issu is to use heat gun on the CPU, these devices will starts normally but the problem will appear again
Envoyé de mon HTC One_M8 en utilisant Tapatalk
Same thing happened to me
Same thing happened to me last night. I tried everything I could think of, I was running the latest stock Nougat version with no root and all of a sudden the device froze. After manually powering it down, I could not get it to boot up again. No LED, battery charging icon on the screen, nothing worked, so as it was still under warranty, I got in touch with someone at Google. They've sent me a replacement device that's set to arrive tomorrow and I am to return the faulty one free of charge. Luckily my Nexus 4 still works otherwise I would've missed several calls today. I suggest you get in touch and see what they say. I know of cases where despite the phone being rooted, if they were running stock the warranty was still applicable. With your device being completely dead, you really have nothing to lose.
Okay, update - I was able to reinstall stock firmware via Nexus Root Toolkit on this device, because I booted it into fastboot and it worked for few minutes. Bootloader is still unlocked - should I wait and lock it (I don't know when will my phone be accessible again, red diode is blessing right now because it boots when it's blinking) or should I send it to repair without worrying?
I would lock it.
Okay, yesterday I flashed stock ROM + unrooted and now I locked bootloader. However the device still seems to have something wrong inside - it shows that the custom OS is installed on my phone. Should I flash again or do you recommend something else?
It shows: "Your device has loaded a different operating system". (Yellow).
How can I get rid of it?
Welcome to the boot kingdom
Envoyé de mon HTC One_M8 en utilisant Tapatalk
Razeer123 said:
Okay, yesterday I flashed stock ROM + unrooted and now I locked bootloader. However the device still seems to have something wrong inside - it shows that the custom OS is installed on my phone. Should I flash again or do you recommend something else?
It shows: "Your device has loaded a different operating system". (Yellow).
How can I get rid of it?
Click to expand...
Click to collapse
Try flashing the latest stock package manually. No toolkits. Sometimes toolkits cause flashing issues.
Sent from my Nexus 5X
nirogu325 said:
Try flashing the latest stock package manually. No toolkits. Sometimes toolkits cause flashing issues.
Sent from my Nexus 5X
Click to expand...
Click to collapse
Thanks for your reply. I succesfully flashed the stock image as you said, but unfortunately I couldn't replace recovery - the phone died and can't boot since yesterday. I'm going to take it to LG service, so keep fingers crossed
Razeer123 said:
Thanks for your reply. I succesfully flashed the stock image as you said, but unfortunately I couldn't replace recovery - the phone died and can't boot since yesterday. I'm going to take it to LG service, so keep fingers crossed
Click to expand...
Click to collapse
No worries, you are in luck.
I tried it with oreo and nougat, but it did not work, it keeps freezing.

Nexus 5x bootloop after oreo update

So here is the thing, My Nexus 5x went it to bootloop, and nothing seems to work. the screen just froze, and then It started bootlooping. goes to google logo, the reboots again into google logo. Well since I use to intall custom Rom, I just did what I would usually do, reflashed the image. Didn't help. left the phone for a couple of minutes, it booted, got me to start up, and half way of setup, it rebooted again into bootloop. thought maybe the oreo has something to do with it, ate the oreo and reflashed nougat image. didn't help either. just now after a bit of not using it, it gets past the google logo, but the animation freezes, and back to google. tried factory reset and dalvik/cache wipe, didnt help but now i can not get into recovery.
so basically Im screwed. no warranty, no nothing. now Im just stuck with this ****ty windows phone.
Can you help out your fellow comrade with a bootlooping phone? :crying:
edit: so after nougat image, it gets past google logo, but boot animation freezes and it reboots again
Remygas said:
So here is the thing, My Nexus 5x went it to bootloop, and nothing seems to work. the screen just froze, and then It started bootlooping. goes to google logo, the reboots again into google logo. Well since I use to intall custom Rom, I just did what I would usually do, reflashed the image. Didn't help. left the phone for a couple of minutes, it booted, got me to start up, and half way of setup, it rebooted again into bootloop. thought maybe the oreo has something to do with it, ate the oreo and reflashed nougat image. didn't help either. just now after a bit of not using it, it gets past the google logo, but the animation freezes, and back to google. tried factory reset and dalvik/cache wipe, didnt help but now i can not get into recovery.
so basically Im screwed. no warranty, no nothing. now Im just stuck with this ****ty windows phone.
Can you help out your fellow comrade with a bootlooping phone? :crying:
edit: so after nougat image, it gets past google logo, but boot animation freezes and it reboots again
Click to expand...
Click to collapse
Have you flashed the 4core bootimg/kernel/recovery, or have you done absolutely no research?
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Also, the fix is really only temporary, I'd prepare to move on to a new phone.
negusp said:
Have you flashed the 4core bootimg/kernel/recovery, or have you done absolutely no research?
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Also, the fix is really only temporary, I'd prepare to move on to a new phone.
Click to expand...
Click to collapse
yeah, i was sceptical of that, so was looking for any other fixes, but as I see, there is no other choice
Remygas said:
yeah, i was sceptical of that, so was looking for any other fixes, but as I see, there is no other choice
Click to expand...
Click to collapse
The bootloop is purely a hardware issue. There is no permanent fix except to either get a replacement CPU or send the phone to LG.
Disabling the 2 big cores should allow you to use the phone for another couple of months. Don't expect it to be permanent, though.
i have faced the same issue on mine.
Remygas said:
So here is the thing, My Nexus 5x went it to bootloop, and nothing seems to work. the screen just froze, and then It started bootlooping. goes to google logo, the reboots again into google logo. Well since I use to intall custom Rom, I just did what I would usually do, reflashed the image. Didn't help. left the phone for a couple of minutes, it booted, got me to start up, and half way of setup, it rebooted again into bootloop. thought maybe the oreo has something to do with it, ate the oreo and reflashed nougat image. didn't help either. just now after a bit of not using it, it gets past the google logo, but the animation freezes, and back to google. tried factory reset and dalvik/cache wipe, didnt help but now i can not get into recovery.
so basically Im screwed. no warranty, no nothing. now Im just stuck with this ****ty windows phone.
Can you help out your fellow comrade with a bootlooping phone? :crying:
edit: so after nougat image, it gets past google logo, but boot animation freezes and it reboots again
Click to expand...
Click to collapse
i have find this on my one too, pls reply me if u find the solution and i will give you if i find the solution.
santhoshreddy923 said:
i have find this on my one too, pls reply me if u find the solution and i will give you if i find the solution.
Click to expand...
Click to collapse
The solution is to apply the BLOD boot image patch, as was stated above. Here's a link: https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Unknown025 said:
The solution is to apply the BLOD boot image patch, as was stated above. Here's a link: https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
Click to expand...
Click to collapse
This isn't possible if you have a locked bootloader unless you can somehow get your phone turned on... If I am mistaken I'd love to be corrected so I can fix this. If this really is a hardware issue, then I guess I'm screwed. This phone is just over a year old and Oreo has been installed for a couple weeks, so this pretty much blows.
nexus 5x bootloop brick
i have found that it is due to hardware issue and what is the best place i can get it repaired.
Is there any other way that i can replace it with another processor such as 820 r any other lower one?
Just send it in for $10 (UPS with tracking #) to LG
Remygas said:
So here is the thing, My Nexus 5x went it to bootloop, ... but now i can not get into recovery....so basically Im screwed. no warranty, no nothing. now Im just stuck with this ****ty windows phone.
Can you help out your fellow comrade with a bootlooping phone? :crying:
edit: so after nougat image, it gets past google logo, but boot animation freezes and it reboots again
Click to expand...
Click to collapse
Just send it in for $10 (UPS with tracking #) to LG and they will put a new motherboard in it. I just did it with my out of warranty 5X that I purchased in May 2016. LG show status "In Warranty" and there was not charge. Phone works faster and better than ever. I upgraded to Oreo an it is running great.
If you need a temp phone buy something like and unlocked (tmobile compatible) phone like I did $70 Alcatel Onetouch Idol 3 until you get your phone back. My project Fi sim works great in that phone I just needed a micro to nano SIM adapter which I got for free at a local cell phone shop.
excuse can you please tell me the detailed process of sending phone to lg .
mrbios said:
Just send it in for $10 (UPS with tracking #) to LG and they will put a new motherboard in it. I just did it with my out of warranty 5X that I purchased in May 2016. LG show status "In Warranty" and there was not charge. Phone works faster and better than ever. I upgraded to Oreo an it is running great.
If you need a temp phone buy something like and unlocked (tmobile compatible) phone like I did $70 Alcatel Onetouch Idol 3 until you get your phone back. My project Fi sim works great in that phone I just needed a micro to nano SIM adapter which I got for free at a local cell phone shop.
Click to expand...
Click to collapse
the issue is i live in india and the phone is imported one could you pls help me.
Remygas said:
So here is the thing, My Nexus 5x went it to bootloop, and nothing seems to work. the screen just froze, and then It started bootlooping. goes to google logo, the reboots again into google logo. Well since I use to intall custom Rom, I just did what I would usually do, reflashed the image. Didn't help. left the phone for a couple of minutes, it booted, got me to start up, and half way of setup, it rebooted again into bootloop. thought maybe the oreo has something to do with it, ate the oreo and reflashed nougat image. didn't help either. just now after a bit of not using it, it gets past the google logo, but the animation freezes, and back to google. tried factory reset and dalvik/cache wipe, didnt help but now i can not get into recovery.
so basically Im screwed. no warranty, no nothing. now Im just stuck with this ****ty windows phone.
Can you help out your fellow comrade with a bootlooping phone? :crying:
edit: so after nougat image, it gets past google logo, but boot animation freezes and it reboots again
Click to expand...
Click to collapse
Same..
My phone was working fine today till evening, suddenly it restarted and this boot loop started. I was on PixelRom (Oreo 8.0)
I tried flashing Factory image of 8.1 final release via fastboot. Its still not booting. Keeps restarting.
Any help?
continuous reboot after Oreo update
Hi,
I am facing issues with my Nexux 5x after updating to the latest version of Android. I received a notification for software update and I did it and as soon as the update was done, the phone started rebooting continously. I tried wiping the cache, factory reset via recovery mode, but nothing actually works. Could anyone of you suggest me some ways to get it corrected or to get the old version back.
Thanks
deepa
mrbios said:
Just send it in for $10 (UPS with tracking #) to LG and they will put a new motherboard in it. I just did it with my out of warranty 5X that I purchased in May 2016. LG show status "In Warranty" and there was not charge. Phone works faster and better than ever. I upgraded to Oreo an it is running great.
If you need a temp phone buy something like and unlocked (tmobile compatible) phone like I did $70 Alcatel Onetouch Idol 3 until you get your phone back. My project Fi sim works great in that phone I just needed a micro to nano SIM adapter which I got for free at a local cell phone shop.
Click to expand...
Click to collapse
Do you still have warranty when you send it?
Extended warranty on LG Google Nexus 5X
arem2015 said:
Do you still have warranty when you send it?
Click to expand...
Click to collapse
No, my phone was 1.5 years old and out of warranty. I did not buy an extended warranty. LG extends the warranty on the Nexus 5X well beyond the standard 1 year for the bootloop issue. Also, my phone was in excellent like-new condition.
My 5x was purchased November of 2015, and they covered mine at no cost under warranty. Even provided a mailing label for me to send it in on their dime. They did require me to provide original proof of purchase (which I luckily was able to lookup). I sent it in on a Monday and got it back Friday that same week. Was mind-blowing fast turnaround time.

Categories

Resources