Pixel 3XL - constant bootloop - Google Pixel 3 XL Questions & Answers

So I updated to Android 11 on Tuesday, and all seemed fine. Last night my phone was trying to install an app, and seemed to freeze.
After a few minutes, I forced it to shut-down (power + vol down) and it started to reboot. It got to the G logo with the small bottom bar animation for a number of minutes and eventually kicked back into Recovery mode.
I decided to try rebooting, and it started to reboot, got to the Google logo (the full word, not the "G"), and then kicked back into rebooting.
The phone now constantly reboots and even if I get into fastboot mode, it only stays in fastboot until I hit a key (vol up/down or power) and it then reboots into constant bootloops described above.
If I don't push a button on fastboot mode, it will just start booting anyways after about 3-5 seconds.
Does anybody know of what I could do? Not sure if replacing the battery would help (e.g. a power issue) or if it may be a corruption of the flash memory and that the system and underlying partitions are corrupt leading to nothing I could do to repair the phone.
I have really enjoyed this phone, but I am afraid that this phone is all-but-dead and unusable.
Any assistance is greatly appreciated.
Cheers,
B.D.

You can try flashing the stock rom from recovery or from fastboot.

Had something similar on an og Pixel... Turned out to be a broken power switch.

I had a weird issue last week. Phone would freeze after a couple of minutes and would reboot. It would also boot loop while connected for charging (wireless and corded.). The battery would not charge. I would shut down the phone and when I plugged in the charger, it would boot loop. The battery finally discharged to 0% and shut off. I plugged the charger in and it remained off. I let it charge to 100% and it's been working for the past week without issue. I'm not sure what happened.
I would suggest letting the battery drain to 0% and go from there. HTH

I updated my 3XL to Android 11 two days ago and since then I have caught it rebooting at seemingly random times, though only when it is on the wireless charger. I guess it's back to Android 10 for now. Hopefully reverting a Pixel is as easy as it was on the Nexus. Thanks Google.

BostonDan said:
So I updated to Android 11 on Tuesday, and all seemed fine. Last night my phone was trying to install an app, and seemed to freeze.
After a few minutes, I forced it to shut-down (power + vol down) and it started to reboot. It got to the G logo with the small bottom bar animation for a number of minutes and eventually kicked back into Recovery mode.
I decided to try rebooting, and it started to reboot, got to the Google logo (the full word, not the "G"), and then kicked back into rebooting.
The phone now constantly reboots and even if I get into fastboot mode, it only stays in fastboot until I hit a key (vol up/down or power) and it then reboots into constant bootloops described above.
If I don't push a button on fastboot mode, it will just start booting anyways after about 3-5 seconds.
Does anybody know of what I could do? Not sure if replacing the battery would help (e.g. a power issue) or if it may be a corruption of the flash memory and that the system and underlying partitions are corrupt leading to nothing I could do to repair the phone.
I have really enjoyed this phone, but I am afraid that this phone is all-but-dead and unusable.
Any assistance is greatly appreciated.
Cheers,
B.D.
Click to expand...
Click to collapse
Are you familiar with how to use commands in platform-tools to flash stock images? How did you upgrade? OTA? Are you rooted? Is it unlocked or Verizon variant? If unlocked, do you know how to unlock the bootloader?

jjlane86 said:
Are you familiar with how to use commands in platform-tools to flash stock images? How did you upgrade? OTA? Are you rooted? Is it unlocked or Verizon variant? If unlocked, do you know how to unlock the bootloader?
Click to expand...
Click to collapse
I am proficient in using the bootloader. Phone has been bootloader unlocked since day one.
I upgraded to Android 11 with ota and all was good for a day (rooted with Magisk canary). Then the phone started acting up, first not booting system and then bootlooping.
I can get into the bootloader (fastboot) but only for maximum 3-5 seconds before the phone reboots, or if I hit any button (vol up/down) the phone reboots. Also, if connected to my computer the USB does not recognize fastboot anymore (before it reboots anyways)
I think it's dead, Jim.
Cheers,
B.D.

Related

Nexus 5X stuck at Google Screen. Won't boot stock recovery.

I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Same thing just happened to me. I have no root or anything but it will not boot the OS. I hope there is a fix for the problem because I really want to use the phone.
Same thing just happened to me.
Click to expand...
Click to collapse
No recovery for you either?
What was the latest Build you had when it was working fine?
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Druas said:
I was just using my phone like normal today opening up the transit app at the bus stop and it randomly froze and restarted. After that, it only shows the initial Google screen and just keeps bootlooping, but never even gets to the part where the OS is loading (with the google animation). It was just on stock 6.0.1, MTC20K I think. Was not rooted. Bootloader was/is unlocked. Secure boot was/is enabled. It won't even go into stock recovery (when I select recovery it immediately goes back to the Google screen and continues as if I had never selected recovery). I have tried manually flashing each piece of the latest factory 7.0.0 build (NRD90S), but even though fastboot says everything was successful, nothing seems to have changed. Any ideas on how to fix this?
Click to expand...
Click to collapse
Had the same thing happen - Now typing to you from my warranty replacement. Only option.
blackpaw78 said:
To get into the recovery plug the phone into your computer. Go into fastboot (vol down + power) and select the power off option. When it turns off or goes to the charging screen, hold volume up + power to boot to download mode. Once in download mode, turn the phone off by holding vol down + power, then go back into fastboot and you should be able to now access recovery mode. This is what I did, and then flashed back to 6.0.1 and it runs fine now. No Idea why going into download mode allows you to then access recovery and get one clean boot, but it does
Click to expand...
Click to collapse
Surprisingly, this worked. I forgot about download mode being an option. I also am not sure why this worked.
Edit: The phone boots, but is still randomly rebooting rather often. Not sure why, as everything was wiped and it should have been a fresh install of everything.
Another Edit: Back to boot looping/not getting to the Android loading screen. I didn't do anything other than let it download my apps. Maybe it is a hardware problem after all because it did successfully boot into Android a couple times.
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Janny82 said:
This seems to be a common problem which I have, too. Looks like a whole series of devices had these issues. Currently LG is unable to repair my device because auf missing spare parts they say. So after effortless 3 weeks they will send my unrepaired device back to me with a letter for my dealer to get back my money.
Nice quality and service, LG - NOT!
Click to expand...
Click to collapse
That is actually pretty good outcome. Pixel phone is coming out soon.
Just had this happen today. Streaming music over Bluetooth and using another app, then tried switching tracks in Google Play Music and the app froze. Phone was unresponsive with app on the screen, then screen went off and wouldn't power on.
I finally got it on by holding down power for 30 seconds, but kept boot-looping to Google boot screen. I was able to get into fastboot mode and wipe everything and install the factory image. Still doing the same thing!
Just got off phone with Google. Told the rep everything I had tried and she is working on a replacement order. Supposed to call me back after chatting with higher level support. I wish they would just send me a new Pixel phone, or the 6P at least!
Ive had the same issue, where I just couldnt get passed the Google screen, the only solution for me to get back on to my phone was to let it happen until the battery died. After i let the battery die i turned it back on normally and connected it to my charger, it hasnt turned off since but im sure it will sooner or later
Edit: Issue is still happening but the only way for me to turn it back on is because the battery dies
This just happened to my and my wifes phones...all within a week of each other. I sent my wife's in about a week and a half ago to LG for warranty service. I am hoping that they are able to fix it...it is still in the 'repair' phase. I am trying to decide whether or not I want to send my phone in (which just died yesterday) before or after LG figures out what is going on with my wifes. In both cases, the phones were running fine and just shut down by themselves. The battery was not dead. Each time, the phone will boot to the Google screen, but then immediate shut down. I can get in to recovery and do actions within there, so I do not believe it to be a battery issue. However, as soon as you attempt to boot the phone, it will die.
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Its a 'known' issue. Google has confirmed there is an issue. Only solution appears to be a warranty replacement.
https://productforums.google.com/forum/#!topic/nexus/r29mtzLFS0g;context-place=topicsearchin/nexus/nexus$205x$20bootloop
---------- Post added at 10:22 AM ---------- Previous post was at 10:21 AM ----------
Psychofrantics said:
Were you guys using stock setups or custom ones?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
on both phones, bone stock. Only difference was I was running the beta before getting the stock OTA and my wife's was full stock and received the stock OTA.
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Same HERE !!!!
the samed for me, and still now i can't light it up
sagshar said:
I'm having the exact same problem here. Running Android 6.0.1, rooted. Phone suddenly turned off and won't start past the "Google" screen, except for once when it booted fully then immediately shut down, and three times when it loaded the boot animation and shut down. Bootloader is unlocked and TWRP recovery is installed. I can access fastboot but not recovery. I've tried the suggestion of booting into download mode then recovery again, but that didn't work. I have NOT tried updating to Android 7 yet, so this isn't the same boot loop issue faced by some other users. I don't want to try flashing stock yet and lose my data because I have a ton of Tasker profiles and tasks that I haven't backed up in months and I don't want to risk losing them! Serves me right...
Any suggestions?
Click to expand...
Click to collapse
In my opinion your EMMC probably died, but you can try reflashing factory images to see if it is some other problem.
I would only try LGUP as a last resort because it will set Allow OEM unlocking to false and lock your bootloader, making further experimentation difficult.
BTW IMO the Android 7 bootloop probably isn't related to Android 7. I think they are just saying hardware problem (EMMC failure) that happens to show up more frequently when you have large updates of OS.
The way Google worded it, it made it seem like Android 7 is killing some hardware because of some incompatibility with just some isolated hardware builds.
I would suggest you let it keep booting and flash some factory images and sometimes EMMC will come back briefly and boot. If it does, immediately backup as much as you can before doing anything else.
Same deal for me and they are sending a replacement. This is a MAJOR blackeye!
Is your phone under warranty then? I am having the same problem as everyone on here. I've tried everything. I bought the phone just over a year ago though, so am a little concerned Google will turn around and tell me it's not their problem... Even though this is clearly a fault!

Nexus 5X mixed boot loop & hard brick after replacing screen

tl;dr summary:
- Replaced screen, worked for 1 week
- Randomly switches between hard-brick no response, and soft-brick boot loop
- Boot loops on loading TWRP as well as OS
- Running latest 7.0.0 NBD90W
- Phone is H790 variant
- Flashed Android 7 in the bootloader, not through OTA. This was as soon as Nougat came out, and it worked great for weeks.
- Bootloader unlocked (for temp-booting twrp only, "fastboot boot twrp.img" otherwise kept stock)
- Phone NEVER rooted
- No charging indicator when plugged in
- Battery bent during previous removal, maybe causing issues a week later?
Replaced screen with genuine LG front frame assembly after a running accident cracked my screen/digitizer. Phone worked fine for about a week, then randomly shut off and went into a boot loop.
Now it randomly switches between a boot loop and a hard brick. When it's acting like a hard brick, sometimes it goes back into boot loop temporarily if I disconnect and reconnect the battery. It eventually returns to hard brick.
Hard brick mode:
-- Doesn't respond to any power button presses. Does not indicate charging when plugged in. Entirely unresponsive.
Soft brick mode:
-- Normal boot: normally gets to Google logo and restarts. Rarely makes it to the flashing dot animation. Twice has booted into Android, past the lock screen, and works perfectly for ~10-15 seconds before rebooting.
-- Boot into bootloader: On occasion will reboot itself from bootloader, but rare. Usually works correctly including all adb commands.
-- Boot into stock recovery: Same as bootloader, usually works, sometimes reboots.
-- Boot into TWRP 3.0.2-2 bullhead: boots for a few seconds and then locks up. Has never made it through decryption - will either a) freeze and reboot right after I draw my pattern, throwing an error that it could not mount storage right before restarting or b) freeze and reboot anyway if I take too long before drawing my pattern. It seems to be more time-based than a function of anything I do.
Things I've tried:
Since my bootloader is unlocked, I've re-flashed these partitions with no fix:
bootloader.img
boot.img
recovery.img (stock)
radio.img
vendor.img
I've cleared cache through stock recovery, can't remember if I tried flashing cache.img
I have yet to flash system.img or userdata.img as I have a few files I'm trying to recover... The fact that I can't boot into TWRP, and the sporadic hard-brick behavior, doesn't give me enough confidence that wiping my data will help.
Phone tends to live in hard-brick mode unless I disconnect and reconnect the battery, then it sometimes goes into soft-brick boot loop for a while before once again hard-bricking itself. When hard bricked, no charging indicator appears when plugged in. When soft-bricked and turned off, will sometimes display the battery status after short-tapping the power button. No change when plugged in except only once it displayed the battery with lightning bolt icon for about 2 minutes, before returning to the icon without the lightning bolt.
My best guess is that I damaged the battery during removal.
- The adhesive was really strong, and while I didn't puncture the case, I did bend it somewhere between 30-45 degrees in the process. If I damaged the Li-Po foil, would that make sense for the phone to work, only to go belly-up a week later? I ordered an OEM LG battery for $13 because it's worth a shot at that price point. Arriving next week.
- The reboots sound in-line with it crashing when it tries to draw too much power? Bootloader and stock recovery usually run okay and I assume have a low power draw. The OS and TWRP probably draw more power and that's where it fails? The reboots seem to be more time-dependent than depending on anything in particular that I do, such as rebooting before OR after drawing my pattern on TWRP. And that it sometimes boots into full Android for a few seconds implies to me that the OS is working on at least some level.
Does anyone have any better ideas for when the new battery inevitably doesn't fix it, or things to try in the meantime? Could the common Nexus 5X boot loop under Nougat be causing issues booting into TWRP too? It feels hardware-related to me. I took it all apart and looked for loose/oxidized/bent contacts on all the connections but couldn't spot anything.
My Pixel isn't arriving until Nov 23-25, and to make matters worse I switched to Google Fi 3 days ago and I have no compatible phones to use in the meantime. Oops, lesson learned.

5X HW brick? No loop

Wanted to seek some clarity on whether my phone is HW bricked. Here're the conditions:
Rooted/Unlocked Bootloader/Custom ROM/Stock Kernel
Randomly found the phone not responding last night, no software updates or heavy usage that day.
Have to long press power to get to turn on. Typical bootloader unlocked warning message then Google screen, then phone turns off. No screen content when charging (battery indicator or booting).
I can get to fastboot with power/vol down and interact with from Nexus Toolkit but attempting to boot to anything including TWRP just produces the same sequence: boot warning, google logo then complete shutdown. Tried booting recovery, wiping, etc from toolkit, nothing.
Occasionally it'll loop once or twice but most of the time it just shuts right off.
Phone is in the freezer now, will try heating solder later. Am I looking at a new phone here? Anything else I can try before heading to the store?
Same issue
Did the freezer trick work?
I have the same issue.
Nexus 5X
Rooted/Unlocked/TWRP/Stock ROM
Randomly turned off, Long press to get back on. Turns off during boot. Managed to access Recovery the first time but havent been able to since, just shuts off.
Google chat thinks it hardware issue.. still under warranty, but would be nice to back up the userdata from it some how...
Surprisingly enough the freezer trick allowed the device to boot into recovery.. unfortunately it wasn't long enough to recover any data and now the phone won't turn on at all :/

HTC M9 Stuck on Bootload After Battery Dropping to 0 Fix/Work Around

Hi all,
My phone is rooted (still S-ON)(TWRP installed) and running viper's ROM. Last night I forgot to charge the phone when I got home, when I looked it was 1% and shut off. I plugged in the phone and foolishly tried to reboot right away instead of waiting a good ten minutes. Well the phone never got out of the HTC logo screen. I would hold down the power and it would vibrate twice, no clue what that mean't. Anyways I waited for at least 10 minutes to give the battery a chance to chare and see if it rebooted but it didn't. Finally I was able to get into recovery doing the following. Hold down the volume up and power button till the phone reboots (screen will be black) Then quickly hold volume down and power until you see the HTC logo on the black background. Then you should have the options to boot into recovery and into twrp. I had to do a data wipe as something in the OS got hosed. I lost all apps and SMS but at least I was able to boot back into the phone. Hope that helps some out there.
I have encountered this same issue on 2 phones but couldn't recover either without reflashing a stock firmware.

H815 does not start or enter recovery

Hi,
a few hours ago I dropped my G4 H815. The back fell off and the battery got out. I put the Battery back in and after a few tries I could load the device. However, I just can`t start the phone now. When I press the power Boutton, nothing happens.
When plugging in the microUSB-Cable the screen turns on and I sometimes see the screen with the LG Logo, but no matter how often I try, it does not boot into recovery (the volume down key was always a bit tricky though). It just goes on to the Screen saying your battery is loading and it´s at 100%.
I can reach Download-Mode, but I do not see any way to force a reboot from there.
My Bootloader is unlocked and the device is rooted. Im running TWRP and LineageOS 14.
Norkzlam said:
Hi,
a few hours ago I dropped my G4 H815. The back fell off and the battery got out. I put the Battery back in and after a few tries I could load the device. However, I just can`t start the phone now. When I press the power Boutton, nothing happens.
When plugging in the microUSB-Cable the screen turns on and I sometimes see the screen with the LG Logo, but no matter how often I try, it does not boot into recovery (the volume down key was always a bit tricky though). It just goes on to the Screen saying your battery is loading and it´s at 100%.
I can reach Download-Mode, but I do not see any way to force a reboot from there.
My Bootloader is unlocked and the device is rooted. Im running TWRP and LineageOS 14.
Click to expand...
Click to collapse
Well it sounds like the infamous Bootloop at least the symptoms are the same. The Bootloop issue is not caused by dropping the phone but while booting Android as this is a very CPU intensive process.
Ilapo or not I would take a backup with SALT before anything else.
You can also boot to fastboot and assuming you haven't installed the nougat v29 bootloader stack you can just boot TWRP temporary by using
fastboot boot twrp.img
(where twrp.img should be my latest TWRP version preview 144 or higher)
Sent from my LG-H815 using XDA Labs
No Bootloop. It seems like the power Button is broken. Using SALT I could reboot the phone and it starts and works normal. The knok-on feature makes this situation, at least temporally, bearable.
I will probably try to fix the Button.

Categories

Resources