another boot loop thread - Moto Z2 Force Questions & Answers

Hi,
I have a Brazilian stock mMoto Z2 Force, XT1789-05, never unlocked the bootloader or root or whatever in this phone, just did the normal Motorola updates as they arrived.
2 months ago I had some battery issues, changed it and was working just fine until this morning. Today the phone restarted after I closed the alarm, and got stuck in boot loop.
I read some threads about this problem for people messing with Roms and baseband, but they don't really apply for me.
The phone reaches the Motorola logo and after a few seconds it restarts.
I can go into fastboot and select recovery mode, but then there's just a black screen with "No commands" written.
Tried Factory Mode with no success.
LMSAA don't recognize the phone, and don't let me select the correct one.
Is there anything else I could try? Maybe force LMSA to do it's magick? manually selecting my phone model for example?

Related

[Q] Phone boots into Firmware Update

I flashed the stock firmware onto my phone, and all was going well until it turned itself off. It then rebooted into Download Mode, and got itself stuck on 'Firmware Update'. I pulled the battery, rebooted and it went from the LG logo straight to the Firmware Update screen. I've tried going into recovery (which works, but pressing yes OR no still takes it to Firmware update. Going into download mode doesn't work either.
I tried to re-flash it using the LGFlashTool, but my PC can't find the phone in this state. I bought it off a guy on eBay 4 months ago, and it worked fine until the first sentence of this post happened.
EDIT: it's the international D855. The Firmware Update screen says '910K B0 QEM'
Galilwithit said:
I flashed the stock firmware onto my phone, and all was going well until it turned itself off. It then rebooted into Download Mode, and got itself stuck on 'Firmware Update'. I pulled the battery, rebooted and it went from the LG logo straight to the Firmware Update screen. I've tried going into recovery (which works, but pressing yes OR no still takes it to Firmware update. Going into download mode doesn't work either.
I tried to re-flash it using the LGFlashTool, but my PC can't find the phone in this state. I bought it off a guy on eBay 4 months ago, and it worked fine until the first sentence of this post happened.
EDIT: it's the international D855. The Firmware Update screen says '910K B0 QEM'
Click to expand...
Click to collapse
Thats not actually right
Booting into recovery normally should factory reset the phone. Would you be able to post a picture of the firmware update screen
itsbighead said:
Thats not actually right
Booting into recovery normally should factory reset the phone. Would you be able to post a picture of the firmware update screen
Click to expand...
Click to collapse
I tried it then. When I do it, I get the normal 'No (Exit)' and 'Yes' and then the same thing to confirm it. It then goes to the LG logo, and boom! Firmware Update!
I don't have a camera (stupid, I know) but, if you boot into download mode, it looks just like the screen there. Except it shows '910K B(0-99) QEM' in the update box thingo.
Hi, i have the exactly same problem, even if i try to power up the device normally or in download more it goes directly in to firmware update. Any way to fix it or install LGE MTP Driver so my PC will see my phone in order to flash it again?
LE: Video
I have run into the same problem like you guys. I recently updated my phone and it started to malfunction with resets, crashing and eventually got it stuck in boot loop. Then it booted into a green screen that said "demigod crash handler/tz crash" thrice. Instead of a hard reset I decided to using the lg mobile support tool to fix it. During the upgrade recovery my phone went into download mode/firmware update. I could see the progress bar moving and then get stuck and my mobile would switch off. Took out the battery, disconnected and reconnected the phone and tried the process all over again but in vain. I repeated this at least 8 times and eventually gave up. Now my phone is basically useless and only boots into firmware update. Hard reset doesn't work either. Can somebody please help me fix this?
I HAVE THE SAME PROBLEM :crying:
910k b0 qem
I tried to flash TOT file and it kept failing around 10%. I read somewhere that I should select the "Flash Board" option so I did. This also failed and left my phone booting to "Firmware Update" screen with following text in the gray box at the bottom.
910K B0 QEM
Windows no longer recognizes the devices and fails to install drivers.
I believe that what is required here is the "910K resistor flash cable"
Something like this ebay[dot]com/itm/OCTOPUS-Z3X-MICRO-USB-LG-P970-P990-P999-CABLE-56K-130K-910K-VARIABLE-RESISTOR-/131321398015
Can someone confirm or offer a solution?
P.S. This 10 post URL limit has got to go!
Galilwithit said:
I flashed the stock firmware onto my phone, and all was going well until it turned itself off. It then rebooted into Download Mode, and got itself stuck on 'Firmware Update'. I pulled the battery, rebooted and it went from the LG logo straight to the Firmware Update screen. I've tried going into recovery (which works, but pressing yes OR no still takes it to Firmware update. Going into download mode doesn't work either.
I tried to re-flash it using the LGFlashTool, but my PC can't find the phone in this state. I bought it off a guy on eBay 4 months ago, and it worked fine until the first sentence of this post happened.
EDIT: it's the international D855. The Firmware Update screen says '910K B0 QEM'
Click to expand...
Click to collapse
It is possible you flashed the wrong KDZ or TOT file
You can also try to hold the power button and wait untill the LG logo appears
anyone have any luck? Im stuck in this mode also

[SOLVED] Android Pixel XL Boot Loop, Never Seen Before

My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
I would fastboot latest factory image.
Just hold vol- when a reboot comes it will go into bootloader.
piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709
piz333 said:
My XL is stuck in a boot loop that I haven't found described anywhere. It begins with the bootloader unlocked warning screen then goes to the white "Google" boot screen, but within one second the screen goes black, waits about 10 seconds and runs through that cycle again. It also randomly (it seems) does the "Writing to EX4 file" screen before the bootloader unlocked warning screen.
It will cycle through this sequence forever if it's plugged in but when not plugged in it will seemingly power off after a random number of cycles. However, powering on does not require holding down the power button - it jumps directly to the beginning of the cycle, sometimes at the bootloader unlocked screen and sometimes at the EX4 screen.
At no point does my Windows 10 PC show the phone as being attached when plugged in to USB. Also, no combination or duration of the phone's physical buttons affect this in any way.
I was following the steps in this article and had just performed the second-last line in the post, "Reboot into the installed recovery." That's when the cycle started. Prior to the step "In TWRP, install twrp.zip" everything was working correctly, though I hadn't rooted yet, of course. I didn't reboot normally in between those two steps, so I can't say which of them caused the problem.
I'm running Android Update, 7.1.2 N2G47E and had been before beginning the procedure. It came from the OTA update and had unrooted the phone from the previous version.
Any and all help will be rewarded with 137 Antique, Pre-Web Internet Points and The Thanks of a Grateful Nation™.
Click to expand...
Click to collapse
Just started with me today too.
I cannot get into recovery or boot loader
rebooting using the hard button just brings up this Dump to EXT4 and then into the ROM that is havnig a ish ton of force closes.
My plan is to back up some stuff I need to copy off the phone and then start factory reset from within settings.
EDIT:
I was rooted running stock
All i did was run a backup in TWRP
issues started after reooting.
Once i factory reset and re Root i will see if I can restore backup, maybe
sb1893 said:
Sounds like you were coming from the April 2017 update to the May 2017 OTA update. The May update included a new bootloader which performs additional verification on the boot image. I suspect that when you installed TWRP and rebooted, the May bootloader detects the changes TWRP installation made to your boot image and aborts the boot process resulting in your bootloop. Additional detail and information can be found in the linked thread and solution should be towards the end of the thread. You have a few options I think (assuming you can get into fastboot/recovery mode) - you can temporarily resolve by reverting back to the April 2017 bootloader which does not have the additional boot verification procedure or you can follow the steps to flash Chainfire's VerifiedBootSigner.zip if you prefer to get fully on the May update (including the May bootloader). Details are in the thread below. Good luck!
https://forum.xda-developers.com/pixel-xl/how-to/images-t3599709
Click to expand...
Click to collapse
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!
piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April. How do I revert the bootloader?
Also, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful so far. Thanks!
Click to expand...
Click to collapse
They flashing all the parts of the image manually. Something like this happened to a buddy of mine and using the flash all wouldn't fix. He couldn't get the device to boot until he did all the images manually.
piz333 said:
I had forgotten that after I booted normally just before installing TWRP, the May OTA happened to arrive and I went ahead and installed it. Then the problem started after I installed TWRP. I used @mikaole's advice and got into bootloader (can't believe I hadn't done that, given all the button combinations I'd tried).
I re-flashed the April update and now the behavior is exactly the same except that the white Google boot screen lasts about 5 seconds and after a few boot tries I land on the "No command" screen. That sits for about a minute and boots again, landing again on "No command." Power+vol-up gets me to recovery mode but all I can do is go to bootloader or get back to "No command." I tried a factory reset, same result. I tried re-flashing April again, same result. Now I think I have the May bootloader with all else April.
I ran this:
Code:
fastboot set_active a
because I noticed that flashing the bootloader was always going to b. After flashing the bootloader again and seeing it go to a, the phone boots normally. I'm going to let the May update happen and wait to root again until after that.
One thing, I don't think the link you provided is the one you intended - there's none of the info you said would be there.
This has been very helpful. You and @mikaole got me through this. Thanks!
Click to expand...
Click to collapse
Glad you got it working. I checked and I did link the thread I intended to. Starting at post #57 onward from that thread has the information on how to update to the May update and leverage Chainfire's VerifiedBootSigner.zip.
Thx,
S
Pixel bootloop
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!
rosendomurilo said:
Hey guys, this is the only thread thqt i found here on XDA about pixel and pixel XL bootloop issue.
I'm about to buy a used Pixel 1st gen phone for really great deal, because it is in this bootloop. As the owner sad, it was on the Oreo upgrade. I'm wondering if its possible to fix it... What you guys say?
Thanks!!
Click to expand...
Click to collapse
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.
Phalanx7621 said:
Well that depends. If the owner unlock the bootloader and then relocked it it could have screwed it up depending on what he was doing with it at the time resulting in a bootloop that cannot be fixed because it's hard brick now. I say can't be fixed only because the only way to get it fixed as far as I know is to contact someone here on the forums I'm not exactly sure who it is but they do fix hard bricked pixels for money. If I were you I would try and figure out if that's the case before buying it.
Click to expand...
Click to collapse
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...
rosendomurilo said:
Yes, that's my biggest fear right now... He sad he never had done anything like root or custom rom, he just had done a system update and the phone never boot correctly again.
I have a little bit of knowledge in android, i was thinking if just putting a custom rom it wouldn't solve, because i had other devices that i had put in bootloop and i was able to fix it just putting a custom rom...
Click to expand...
Click to collapse
Can you get to recovery ?
Phalanx7621 said:
Can you get to recovery ?
Click to expand...
Click to collapse
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...
rosendomurilo said:
I'm not with the phone right now, I'm going to buy it next week... Correct if I am wrong, but if i can get to recovery or bootloader i can fix it, right?
I think he had tried to unlock the bootloader but without experience had bricked...
Click to expand...
Click to collapse
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.
Phalanx7621 said:
Yeah if you can get into recovery you can side load things. And if you can get to the boot loader screen you're fine.
Click to expand...
Click to collapse
Perfect! Just as I expected... Probably i will do an youtube guide if it works... Thanks bro!

It is a sign of bootloop?

Hi,
When i use my 5x for a hour or so, then try to reboot it, it stucks at the google logo. When i restarted with the physical button, its usually starts, but not always. There was a time when i couldn't make it work for at least 30minute, then i waited a hour and it started finally.
Every time when i stucked at google logo, i'm able to get to twrp. Tried with stock rom, locked bootloader, stock recovery too, but its same. When i use it for a long time and its get hot, its stucks at google logo when restarting.
But it never restarted automatically. I can use it for 10hours if i want, just if i restart it, its stucks.
Is it because faulty motherboard or what do you think?
Because it dont stuck forever, and i can access recovery mode.
That's probably some random issue, the BLOD happens like this:
You do your stuff on the N5X,
everything freezes for several seconds,
phone restarts itself and doesn't get past google logo,
can't access recovery, however you can access bootloader, which is very laggy,
starting up again is nearly impossible, you can hold the button for an hour and the phone won't even get to the google logo.
ZLevente said:
Hi,
When i use my 5x for a hour or so, then try to reboot it, it stucks at the google logo. When i restarted with the physical button, its usually starts, but not always. There was a time when i couldn't make it work for at least 30minute, then i waited a hour and it started finally.
Every time when i stucked at google logo, i'm able to get to twrp. Tried with stock rom, locked bootloader, stock recovery too, but its same. When i use it for a long time and its get hot, its stucks at google logo when restarting.
But it never restarted automatically. I can use it for 10hours if i want, just if i restart it, its stucks.
Is it because faulty motherboard or what do you think?
Because it dont stuck forever, and i can access recovery mode.
Click to expand...
Click to collapse
I had the same issue when I flashed the newest bootloader version (bhz31b). Issue resolved when I reverted to bhz31a.
Wakamatsu said:
I had the same issue when I flashed the newest bootloader version (bhz31b). Issue resolved when I reverted to bhz31a.
Click to expand...
Click to collapse
Thanks, i'll try bhz31a thanks
(I'll write in some days if it worked or not)
Wakamatsu said:
I had the same issue when I flashed the newest bootloader version (bhz31b). Issue resolved when I reverted to bhz31a.
Click to expand...
Click to collapse
Which bootloader is bhz31a? I tried the bootloop fixes, none worked. Only have access to bootloader, no recovery.
edit: i see bullhead-opm1.171019.011-factory-3be6fd1 has the bhz31a bootloader. I tried this, with no luck on my end. Even with the 4core modified recovery/boot. I must have one of the unfixable BLOD.
I tried that bootloader too, same
My phone can boot, just sometimes it's stucks at google logo, but i can access recovery every time, even if it's stucked at google logo.
Usually every 2. reboot stucks.

Help to unbrick a Moto Z2 Play Xt1710-06

Hi
I begun experiencing some random freezings at homescreen. When that happenned I rebooted and resumed working. I thought it was some app or OS problem and ignored that.
Until phone didn't boot anymore and now I'm stuck at boot screen. It does not pass through it
I cannot do anything at recovery. I can see the menu, but when I release any of the keys I used to access recovery, everything dissapear and turns off.
Is there any way to debug which could be the problem? Or any tools I could use to repair it
PS: I did not try to unlock bootloader, flash any other recovery, kernel, rom, etc. Its stock as I took it off its package since bought it.
Thanks a lot for any tip you could give me :good:

Soft bricked Pixel XL

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`

Categories

Resources