Related
I was trying to backup using Titanium backup 8.0 and my phone hard crashed, I allowed it to reboot and tried again (same thing), however this time it is very-very messed up. It continually cycles at the LG screen, I've been able to get into TWRP twice, but then it randomly reboots from there as well after the screen locks up, after about 20 seconds. At this point the phone is stuck in a boot loop and is unable to proceed, now luckily I have a v20 coming, sadly not for over a week. I can not see how titanium backup resulted in a boot loop that does not end unless it corrupted the system partition, but even then it should not have affected TWRP, which is also encountering issues and is not stable enough to attempt a recovery of the system. So any suggestions as to a cause and a solution to it looping on the LG screen?
After the first crash from TI it booted fine and ran well enough (no issues encountered), and doing a reboot restarted cleanly, it was the second crash that seems to have done it in.
ERIC
egandt said:
I was trying to backup using Titanium backup 8.0 and my phone hard crashed, I allowed it to reboot and tried again (same thing), however this time it is very-very messed up. It continually cycles at the LG screen, I've been able to get into TWRP twice, but then it randomly reboots from there as well after the screen locks up, after about 20 seconds. At this point the phone is stuck in a boot loop and is unable to proceed, now luckily I have a v20 coming, sadly not for over a week. I can not see how titanium backup resulted in a boot loop that does not end unless it corrupted the system partition, but even then it should not have affected TWRP, which is also encountering issues and is not stable enough to attempt a recovery of the system. So any suggestions as to a cause and a solution to it looping on the LG screen?
After the first crash from TI it booted fine and ran well enough (no issues encountered), and doing a reboot restarted cleanly, it was the second crash that seems to have done it in.
ERIC
Click to expand...
Click to collapse
This may not be necessarily an app fault but cpu intensive processes like restoring many apps can enforce a very known hardware fault. Check the first 3 digits of your serial. Starts it with 5xx or 600-602? Then you will likely have the ilapo/bootloop issue which means you need to replace the main board / warranty replacement.
.
Sent from my LG-H815 using XDA Labs
Yep, that is likely it 505K.... Serial. oddly I can get into TWRP sometimes, but can not get to fastboot at all, sometimes I can even get Android to boot, but never complete, so it does not seem completely crashed, only mostly so.
Glad I odered a new phone today,
Eric
I ran into a issue whereby the phone went into a boot loop. It's not a total shutdown, but a reboot as it came back within 10 seconds. I running Audible (in the background, not playing), Waze and broadcasting Periscope. After the first reboot, I stop using Periscope. The phone went into another reboot after I startup Waze. After 2 more reboot, I tried to do a graceful shutdown. The phone was stuck on shutting down for a couple of minutes (with the arrow circle stuck). I finally does power+volume down to do a full reboot. Afterward, I powered down another time and make sure comes back correctly.
Not sure if this is caused by too many apps running, the phone does appear to be warm.
The phone is unlocked straight from Google, rooted with Magisk.
dyingearth said:
I ran into a issue whereby the phone went into a boot loop. It's not a total shutdown, but a reboot as it came back within 10 seconds. I running Audible (in the background, not playing), Waze and broadcasting Periscope. After the first reboot, I stop using Periscope. The phone went into another reboot after I startup Waze. After 2 more reboot, I tried to do a graceful shutdown. The phone was stuck on shutting down for a couple of minutes (with the arrow circle stuck). I finally does power+volume down to do a full reboot. Afterward, I powered down another time and make sure comes back correctly.
Not sure if this is caused by too many apps running, the phone does appear to be warm.
The phone is unlocked straight from Google, rooted with Magisk.
Click to expand...
Click to collapse
any chance you are using substratum theme? I had that problem and had to clear the theme to make it go away.
lucky_strike33 said:
any chance you are using substratum theme? I had that problem and had to clear the theme to make it go away.
Click to expand...
Click to collapse
Other than unlocking the phone and rooting, the phone doesn't have much in ways of alternative theme. I'm still using factory everything.
dyingearth said:
I ran into a issue whereby the phone went into a boot loop. It's not a total shutdown, but a reboot as it came back within 10 seconds. I running Audible (in the background, not playing), Waze and broadcasting Periscope. After the first reboot, I stop using Periscope. The phone went into another reboot after I startup Waze. After 2 more reboot, I tried to do a graceful shutdown. The phone was stuck on shutting down for a couple of minutes (with the arrow circle stuck). I finally does power+volume down to do a full reboot. Afterward, I powered down another time and make sure comes back correctly.
Not sure if this is caused by too many apps running, the phone does appear to be warm.
The phone is unlocked straight from Google, rooted with Magisk.
Click to expand...
Click to collapse
There was another thread about random reboots of the Pixel 2 XL, there are threads on the Google Product Forums as well. I would recommend to star them and also to follow the steps in this thread to submit a bug report to Google - https://forum.xda-developers.com/showpost.php?p=74472984&postcount=65
please close this thread.
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Sussudioo said:
Okay, so i have an LG G3 D855, few months ago it worked like a charm.. But then shortly after i started noticing random reboots everytime during using apps. Then it went in bootloop. I tried to turn it on again, entered recovery screen, choosed factory reset and it did, but then it went through the same process, random restart. Eventually stuck up in factory resetting screen. However i think i made mistake when the phone freezed in reset screen : pulling out the battery. later it lost its IMEI & kept heating up (probably tried to find its cellular framework of some sort).
Days passed, several factory resets has been done. Now the phone's at its worst state. It refused to get past the boot logo. everytime it finishes booting, the display just goes black, tried to plug usb charger, chargin indicator doesn't want to turn on, neither after i pulled out the battery. I have to leave it a few days to get it working again, but it keeps persisting.
Addition : The phone's also feels warm post the blackscreen.
Any thoughts whether can this be fixed or i have to replace something inside the phone's board?
thanks in advance.
Click to expand...
Click to collapse
Reflash with lgup.
Remove the SIM card and the memory card. try again. Full wipe system data ...
I've had the same problem. I've tried. Worked
found the problem. memory card
EDIT: Some kind of voodoo happened right now! I was about to unbrick again and wanted to give the phone a try to boot before. And it did! So no problem at the moment, but still a strong feeling of uncertainty...
EDIT: Phone is still randomly rebooting and gets stuck in bootloops
-----
Hej guys, I really need your advice,
but first things first: Thank you very much for all of your wonderful work on custom roms and further support of older devices. I've been reading here for a few years now and was more or less happy to have up-to-date-roms for some of my phones.
Now I'm facing quite the same problem like OP did / does. Everything started with me, following this guide to root my D855 (coming from stock rom) and flash TWRP: you tube.com/watch?v=8VOgM3jLas4 (Note: The guide told me to flash "3__HacerPermisivo.zip" for updating the kernel, which I did.)
Next, I flashed a newer version of TWRP ("twrp-3.2.3-0-d855.img") than the one provided in "2__AutoRecMMD855.apk" by the guide above. I wiped dalvik and cache and after that, I flashed "lineage-15.1-20190410-nightly-d855-signed.zip", wiped dalvik and cache again and flashed "open_gapps-arm-8.1-pico-20190411.zip". I wiped dalvik and cache again and told TWRP to reboot.
Here is, where problems began to occur. The phone got into a bootloop, showing up the LG splash screen again and again instead of booting into LOS correctly and set it up. At some point I decided to remove the battery. When I did, at the same time LOS was just going to load, which I saw because of its beginning boot animation. So I screwed it up right at the wrong moment, I guess.
From here, the phone bootlooped every time, I wanted it to start. No battery acrobatics helped and on top I couldn't get it into recovery mode. Any attempts ended in bootloops. I think, this might be what is called a brick / to brick your device, isn't it? I found this guide to unbrick a D855 and followed its steps: open -freax.fr/guide-unbrick-your-lg-g3/
Believe me, it was a real pain in the ass! Because of me, messing up something or the phone getting stuck into a bootloop during the unbrick process, I had to do it 4 to 5 times until success... I have to say: I didn't follow the last steps beginning from "Root". Instead, I followed the guide from the beginning of my post.
Finally, I got "lineage-15.1-20190410-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190411.zip" to run. I set it up and began to load some of my apps of my Play Store collection. While downloading, the phone froze, crashed and began to bootloop, from here unable to boot normally or to get into recovery mode. So I unbricked and flashed again (again several times because of bootloops before LOS first set up). When I got it to work again, I was able to install my apps without being trolled by the phone again. But scrolling through the eBay app froze the phone and it began bootlooping again...
You can believe me, I was about to throw the D855 against the hardest piece of wall, I could possibly find in my rage. The reason why I didn't give up at this point is, that I LOS-rommed two other D855s just a few days before. Those were my mom's and my girlfriend's and they work fine until today. I bought this third one for myself, because I was impressed, how good LOS worked on the D855s. On top I wanted to get rid of my Samsung Galaxy S4 (GT-I9515), because LOS kinda sucks on it, but this is another story...
So I figuered that the earlier LOS version I used for the women's phones, could solve the problem. So I unbricked again and flashed "lineage-15.1-20190327-nightly-d855-signed.zip" and "open_gapps-arm-8.1-pico-20190329.zip". And hell yeah, that did work! No bootloops, eBay worked fine, just everything was as I loved it on the other phones, I flashed. Until tonight. I've been lucky for almost two days, but tonight this happened: I plotted a route in Google Maps and saved it as a shortcut on my homescreen. I closed Maps and tapped the route icon. Freeze - crash - bootloop - no recovery mode! I wanted to start crying, because Maps has already worked fine yesterday. And it still does on the other two phones, which run exactly the same rom...
So now, I'm sitting here, not knowing what can be done further. I'm not a programmer / developper or any of those cracks providing us the newest software for old phones. So I just can do wild guesses. Maybe the moment I removed the battery the very first time after flashing messed something up very deep inside the phones internals and it can not be cured any more. Maybe some of you guys have experienced similar things and know a tweak or a simple step, I forgot. Anyway, I hope I can use my phone on LOS some day which I bought especially for this case.
Keep up the great work, folks!
Greets
I ordered a new mainboard. It should arrive within 3 weeks. I'll keep you updated.
My Pixel XL 128GB on Android 10 just randomly started bootlooping during normal use. Totally stock with Verizon sim card, but received directly from Google (actually it is a warranty replacement received about 2 years ago for a Nexus 6P that I bought directly from Google in Feburary of 2016 due to faulty battery).
Bootloader is still locked. USB debugging is disabled.
Google logo just keeps appearing and disappearing on screen. I can get into fastboot by holding power and volume down, but choosing recovery mode just goes back into bootloop.
Am I hopelessly bricked?
thomase00 said:
My Pixel XL 128GB on Android 10 just randomly started bootlooping during normal use. Totally stock with Verizon sim card, but received directly from Google (actually it is a warranty replacement received about 2 years ago for a Nexus 6P that I bought directly from Google in Feburary of 2016 due to faulty battery).
Bootloader is still locked. USB debugging is disabled.
Google logo just keeps appearing and disappearing on screen. I can get into fastboot by holding power and volume down, but choosing recovery mode just goes back into bootloop.
Am I hopelessly bricked?
Click to expand...
Click to collapse
After looping several times I was able to reboot once. I went into developer mode and enabled "USB debugging" soon after which it crashed again. Only then did I realize that I was SUPPOSED to enable "OEM Unlocking" rather than "USB debuging"!
I still haven't been able to boot it again since. Any suggestions? Would heating or cooling the device help? What are the chances that re-flashing the factory image will even help?
thomase00 said:
After looping several times I was able to reboot once. I went into developer mode and enabled "USB debugging" soon after which it crashed again. Only then did I realize that I was SUPPOSED to enable "OEM Unlocking" rather than "USB debuging"!
I still haven't been able to boot it again since. Any suggestions? Would heating or cooling the device help? What are the chances that re-flashing the factory image will even help?
Click to expand...
Click to collapse
Well, I was able to get in again and barely had enough to enable "OEM Unlocking". I proceeded to unlock the bootloader and re-flash the latest Android 10 factory image (the one ending in .20). I can't get through the new phone setup process before it crashes and eventually reboots. It might get as far as connecting to Wifi but always eventually crashes while "Checking for updates...".
I could try an older Android 9 image, but it seems like I have a straight-up hardware failure (SoC, DDR, flash memory, etc.).
At this point I'm resigned to the fact that it is most likely dead. Are there any custom recovery images that I can flash that can run hardware diagnostics so I that I can pinpoint the failed component?
The same thing happened today to my wife's xl pixel still with android 9, now I've updated it to 10 and for now it works but I think it seems like there's a battery problem. I think the battery is bad but it is strange that it happens this way
Looks like i have the same issue. If you remember one of the android betas (beta 4 i believe) had this issue where the phone got stuck in bootloop. I had this issue and im unable to fix it. My phone keeps bootlooping on the google logo...i tried reflashing the factory image for 9.0 or 10.0 but no luck. I even tried installing a custom rom and that too reboots on the google/custom rom logo. Is there any other way to fix this? Is this a hardware issue? please help
A week ago, all of a sudden, my Pixel decided to freeze and become unresponsive. To make a long story short, it only goes to the Google logo screen and will not go into bootloader or recovery mode. Took it to a repair shop and they said it needed to be sent back to Google (it's three years old so long past its warranty) which would cost a fortune. They said it is soft bricked.
I'm looking into things and since my phone is already useless, I surely can't make it any worse. (fingers crossed.)
I'm wondering if anyone has any tips on how to get my phone back up and running whilst also keeping all of the data on my phone. I'm not keen on wiping the data as it has important information on it. Is it possible to unbrick a Pixel XL without factory resetting it?
Does anyone have a simpletons guide on how to do it? I've looked at numerous guides and they are either long winded or far too complicated for me. I'm not familiar with downloading a file to unzip it or extracting it. Although, I am very much willing to learn given my circumstances.
If anyone can provide any information, I would be very grateful!
i think if anything at this point, you need to assume none of your data can be saved. if you send it to google for them to fix, no data will be kept most likely, nor if you find any solution to do yourself. what happens if on the google screen you hold down power and voldown until it turns off and then keep holding them down?
It goes into fastboot with the android guy on it's back and it gives me the "restart bootloader", "recovery mode", "barcodes", etc, options. None of which the phone can enter apart from the barcodes and the powering off option. :crying:
HanaTruly said:
A week ago, all of a sudden, my Pixel decided to freeze and become unresponsive. To make a long story short, it only goes to the Google logo screen and will not go into bootloader or recovery mode. Took it to a repair shop and they said it needed to be sent back to Google (it's three years old so long past its warranty) which would cost a fortune. They said it is soft bricked.
I'm looking into things and since my phone is already useless, I surely can't make it any worse. (fingers crossed.)
I'm wondering if anyone has any tips on how to get my phone back up and running whilst also keeping all of the data on my phone. I'm not keen on wiping the data as it has important information on it. Is it possible to unbrick a Pixel XL without factory resetting it?
Does anyone have a simpletons guide on how to do it? I've looked at numerous guides and they are either long winded or far too complicated for me. I'm not familiar with downloading a file to unzip it or extracting it. Although, I am very much willing to learn given my circumstances.
If anyone can provide any information, I would be very grateful!
Click to expand...
Click to collapse
I have the same exact problem. Started Nov. 14. Talked to google asked me to take it to uBreakiFix. They ran diagnostics and said they can't fix it.
My phone used to boot up randomly but would freeze after 2-3 mins and crash again into a bootloop. Now it's stuck on white "google" screen and can't get into recovery or any other modes.
Nilkong said:
I have the same exact problem. Started Nov. 14. Talked to google asked me to take it to uBreakiFix. They ran diagnostics and said they can't fix it.
My phone used to boot up randomly but would freeze after 2-3 mins and crash again into a bootloop. Now it's stuck on white "google" screen and can't get into recovery or any other modes.
Click to expand...
Click to collapse
by boot up randomly do you mean it would randomly reboot or turn on while it was off?
sudoxd said:
by boot up randomly do you mean it would randomly reboot or turn on while it was off?
Click to expand...
Click to collapse
I mean it would boot successfully and take me to lock screen where I can use the phone for few minutes until it freezes again.
Currently I am connected to computer with adb shell open and have phone on the screen where I can see options to select 'barcode' 'recovery mode' 'power off'. The screen shows baseband version, CPU, UFS, DRAM, "Device is locked".
Adb is recognizing the devices (I can't unlock because I had the option to "OEM unlock" turned off in settings). But when I try selecting 'recovery mode' its back to 'Google' screen and stuck there.
Nilkong said:
I mean it would boot successfully and take me to lock screen where I can use the phone for few minutes until it freezes again.
Currently I am connected to computer with adb shell open and have phone on the screen where I can see options to select 'barcode' 'recovery mode' 'power off'. The screen shows baseband version, CPU, UFS, DRAM, "Device is locked".
Adb is recognizing the devices (I can't unlock because I had the option to "OEM unlock" turned off in settings). But when I try selecting 'recovery mode' its back to 'Google' screen and stuck there.
Click to expand...
Click to collapse
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
sudoxd said:
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
Click to expand...
Click to collapse
I flashed the new version of OTA from google's site. And it looks like it's booting up. Will report back if it crashes or continues to hold up.
Thanks!
EDIT: It's back to boot looping. It was at the "G" screen with white loading bar underneath. It froze there and went back to bootloop. Looks like there might be no avail.
Similar issue here. I gave up on it a month ago, but I figured it can't hurt to ask around. FWIW, there seem to be a lot of similar reports on Google's Pixel support forum.
Anyway, during the 2nd year of owning my Pixel XL (got it in Septempter 2017), I started experiencing slowdowns and random reboots more frequently, but never any bootloops until after receiving Android 10. After receiving Android 10, the random reboots seemed to be happening more frequently. I also experienced a weird issue where the phone would spontaneously exit out of the Google app (reached by left edge swipe from home screen) consistently within a few seconds of entering it.
Eventually, after another increasingly common random freeze, the phone rebooted and got stuck in a bootloop. Initially, chances were high that I would be able to complete the boot process after a few attempts, but inevitably, it would freeze and start bootlooping again. During the handful of successful boot attempts, I was able to backup some photos, and more importantly, enable OEM bootloader unlock in the developer options. After several more failed attempts to boot successfully, I did a total reflash of the latest factory image as of September 2019, after which I was able to get partially through the new phone setup process before crashing. For each subsequent attempt, the crash would happen earlier and earlier in the setup process until it wouldn't get further than the 'G' logo before rebooting. When the October 2019 factory image became available, I tried flashing that as well, but no luck.
On one hand, considering that the failures got progressively worse over time, it seems that this is fundamental hardware failure in the SOC, motherboard, RAM, etc. On the other hand, there seems to have been so many recent reports of this, especially after the Android 10 update, that I wonder whether or not it is software issue. Or could it be some combination of both, where the Android 10 update is pushing the hardware in new ways that is more likely to exacerbate an underlying hardware flaw?
Should I try re-flashing with Android 9 instead? At this point, it is a total brick...
sudoxd said:
try sideloading the latest OTA and see what happens, this doesnt require an unlocked bootloader, just adb sideload.
Click to expand...
Click to collapse
Would this be possible to do with a phone that doesnt turn on but the computer does see it as a qualcom device?
ckidmcd said:
Would this be possible to do with a phone that doesnt turn on but the computer does see it as a qualcom device?
Click to expand...
Click to collapse
Needs to boot to any recovery, custom or not, to sideload an ota
sudoxd said:
Needs to boot to any recovery, custom or not, to sideload an ota
Click to expand...
Click to collapse
Do I have any options to pull the data from the device since it does see a qualcomm device when plugged into a computer?
ckidmcd said:
Do I have any options to pull the data from the device since it does see a qualcomm device when plugged into a computer?
Click to expand...
Click to collapse
does fastboot see your phone at all if you type `fastboot devices`