December update scared me to death (Freeze, long boot) - Google Pixel 4 XL Questions & Answers

I'm just putting this here to hopefully help someone else not lose their mind after a bad December update. I just got my OTA for my 4XL on VZW about 40 minutes ago. MY PHONE JUST BOOTED.
After applying the update and the phone restarting, per usual, I noticed the lock screen was super sluggish and intermittently not responsive. More concerning still, it said my PIN was invalid, which I KNOW it wasn't. So.... I rebooted. Just held power for a second, and clicked Restart in the menu. That may have been where I went wrong. For the next 25 or so minutes, I had nothing but a black screen. No sounds, no vibrations, nothing registered when plugging into my PC. Even holding the power key for 30+ seconds or attempting safe mode or bootloader did not work.
In retrospect, I am now considering that even though the phone initially rebooted and was at the lock screen, Android may still have been in the process of updating which could cause the slow down and maybe even the invalid pin. Mostly, I think that may be what happened when I rebooted the phone, I basically did it in the middle of it finalizing the update which very well could have caused all sorts of issues.
TLDR: I don't think I did anything to fix it, I gave up after 1000 times of trying and set it down, then about 5 minutes later (off the charger) it just started booting up. So don't throw your phone at the wall if it doesn't turn on right away after the update.

lessthanzach said:
I'm just putting this here to hopefully help someone else not lose their mind after a bad December update. I just got my OTA for my 4XL on VZW about 40 minutes ago. MY PHONE JUST BOOTED.
After applying the update and the phone restarting, per usual, I noticed the lock screen was super sluggish and intermittently not responsive. More concerning still, it said my PIN was invalid, which I KNOW it wasn't. So.... I rebooted. Just held power for a second, and clicked Restart in the menu. That may have been where I went wrong. For the next 25 or so minutes, I had nothing but a black screen. No sounds, no vibrations, nothing registered when plugging into my PC. Even holding the power key for 30+ seconds or attempting safe mode or bootloader did not work.
In retrospect, I am now considering that even though the phone initially rebooted and was at the lock screen, Android may still have been in the process of updating which could cause the slow down and maybe even the invalid pin. Mostly, I think that may be what happened when I rebooted the phone, I basically did it in the middle of it finalizing the update which very well could have caused all sorts of issues.
TLDR: I don't think I did anything to fix it, I gave up after 1000 times of trying and set it down, then about 5 minutes later (off the charger) it just started booting up. So don't throw your phone at the wall if it doesn't turn on right away after the update.
Click to expand...
Click to collapse
Were you rooted ?

reboot took longer than normal, should have left it
factory reset will clear up everything lol

prgopala said:
Were you rooted ?
Click to expand...
Click to collapse
I am not rooted. Gave up my rooting back when it made Google pay and Pokemon Go a complete ***** to use, even with magisk. So I've left this stock out of the box.

lessthanzach said:
I'm just putting this here to hopefully help someone else not lose their mind after a bad December update. I just got my OTA for my 4XL on VZW about 40 minutes ago. MY PHONE JUST BOOTED.
After applying the update and the phone restarting, per usual, I noticed the lock screen was super sluggish and intermittently not responsive. More concerning still, it said my PIN was invalid, which I KNOW it wasn't. So.... I rebooted. Just held power for a second, and clicked Restart in the menu. That may have been where I went wrong. For the next 25 or so minutes, I had nothing but a black screen. No sounds, no vibrations, nothing registered when plugging into my PC. Even holding the power key for 30+ seconds or attempting safe mode or bootloader did not work.
In retrospect, I am now considering that even though the phone initially rebooted and was at the lock screen, Android may still have been in the process of updating which could cause the slow down and maybe even the invalid pin. Mostly, I think that may be what happened when I rebooted the phone, I basically did it in the middle of it finalizing the update which very well could have caused all sorts of issues.
TLDR: I don't think I did anything to fix it, I gave up after 1000 times of trying and set it down, then about 5 minutes later (off the charger) it just started booting up. So don't throw your phone at the wall if it doesn't turn on right away after the update.
Click to expand...
Click to collapse
Hey got the same issue as you. Either it's stuck on a black screen (adb works), either it hangs on Applying update when starting the phone. Can't seem to get past this crap... I'm trying with a patched magisk image btw, not sure if it's the issue, I already applied the magisk adb commande in order to remove the magisk modules but to no avail.

Related

Any Merit To What I've Done? "Crashed" Tilt2

Hi All,
While on a business trip last week, my Tilt 2 (at the time, running the April 14 Energy ROM), my phone--for lack of a better word--crashed on me.
Everything had been working fine, I was sitting there with my phone connected to my laptop via a USB cable, and out of the blue, for no apparent reason, my phone re-booted, and never came back up. It would get to the splash screen, start loading the OS, reboot mid-stream, and get stuck in a loop. Weirder still, if I pulled the battery, let the phone sit, then put the battery back in, hitting the power button did nothing--even with the phone plugged in to power. On top of that, even if the phone was off, after a few minutes, it would power itself back on randomly, and get stuck in the re-boot loop. Very weird.
So, when I got home, before heading to the AT&T store and asking for a replacement, I thought I'd try to restore the phone myself.
At first, I pulled the battery, then stuck it back in, and sat there holding the volume down button, waiting to put the phone into bootloader mode. That worked, but even in bootloader mode, it would randomly re-boot. So, I started the process again, and immediately plugged the phone into my computer while in bootloader mode and ran the Task 29 tool. That completed properly.
At this point, I popped in another battery I had laying around and just let the phone charge for a few hours. Then, for the heck of it, I re-ran the HardSPL tool. Re-Flashed to the .91 radio (it was already on the phone), and then flashed to the latest Energy ROM.
Since then, my phone has been better than ever. Seems faster, battery life is better (Went three days without having to charge it), no dropped calls, and no weirdness with the latest ROM (that I've found so far).
Does it pay to REALLY start fresh from time to time, and re-flash everything on the phone?
Thanks for any input.
I have no idea, but hopefully the WinMo experts will see this and have an idea, so here's a bump for you. Most of my computer expertise revolves around Unix, Linux, and a bit of Windows, not so much these phones.
I do know that task 29 is awesome, though. It seems like DBAN for your phone...
DBAN=Darik's Boot and Nuke. Look it up.
I don't know what happened with your phone, sounds like something broke in the area of booting.
I don't think you should need to re-flash HardSPL radios just for the sake of it, but I'd strongly recommend task29 every time you flash a new ROM.
bricked my TP2
My TP2 seems to have a similar problem which I haven't been able to fix it just yet. The bootloader reboot loop is too short to succesfully run task 29 and flashing it using the microSD gets stuck around 40%
during bootloader mode there's an unreadable errormessage since it's on the same line as some of the usual information.
any thoughts/suggestions would be very welcome since i can't afford to send it to the factory.
cheers.

[Q] [HELP!]

I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
GreenMunky said:
I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
Click to expand...
Click to collapse
If a factory reset does not fix the issue, all I can suggest is find the thread "Return to Stock" and follow the instructions to flash the entire stock SBF for your carrier. This should fix any corrupted files, if present. Either option WILL erase everything, so backup anything you need first.
Good Luck
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
KJ said:
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
Click to expand...
Click to collapse
Nope, phone had been off the charger only a few hours, still had 85% or so. I actually tried plugging the phone in while it was booting up to see if an extra jolt of juice would somehow help it to fully boot up... made no difference. After 6-8 failed boot attempts, it finally booted up and has been running fine since... although I have yet to try to manually reboot it.
Well, if it acts up anymore...I'd consider a full wipe and return to stock. Same android version you're on now of course.
Otherwise...probably a fluke. ?

Random reboot this morning

My phone randomly rebooted around 4 am this morning (mountain time) The only way I noticed it was I was looking at battery stats and there was a white gap or is there some other explanation for that? I have not seen this before... stock no root no unlocked bootloader.... kind of weird no?
how are we supposed to know why your phone rebooted? you provided no info besides that it rebooted around 4am. no logs, nothing. my guess is that a spaceman came and made your phone reboot, just to watch the google logo as its booting up :silly:
simms22 said:
how are we supposed to know why your phone rebooted? you provided no info besides that it rebooted around 4am. no logs, nothing. my guess is that a spaceman came and made your phone reboot, just to watch the google logo as its booting up :silly:
Click to expand...
Click to collapse
No, definitely not a spaceman... Not in mountain time
If I knew how to provide logs I would have, guess I'll check with the spacemen and see if they have them. Thanks for the help, you can close the thread......
My phone used to reboot 2-3 per day. I removed the Amazon app and it hasn't rebooted since. If you have that app installed, uninstall it.
My phone had random reboots before, but it went away.
Today i had a freeze again, before a reboot happens i cant wake my phone up . So i tired the power button like 10 times. It came back on, stayed on lock screen for 2 second and everything went black. Had to turn it back on.
Its like a deep sleep of death. I don't get notifications or anything when this happens, but my Moto 360 somehow stay connected but cant do any voice search.
This i how i usually discover the problem. When i want to do some OK Goggle with my watch and it does nothing... Checking my phone and its always dead.

[HELP!] A series of events led to an infinite boot loop i can't do anything about.

The first time I got my phone was about two days ago. I got the MotoG2 from ebay at such a cheap price ($20), I won the auction and so yeah (26 bids). HOWEVER, this is what the description says from the seller:"This smart phone sells working as-is because screen is cracked, LCD has liquid damage, other components work as they are supposed to. SIM slot/cellular feature has not been tested on any networks. Customer data have been deleted from smartphone. *Battery life and performance on used electronic devices can not be guaranteed. * Entire screen is cracked; there are many scratches and scuffs on the bezels and on the back side. Smart phone sells with battery and non-OEM box.
I finally got it and shipped to my house, on'ed it and everything worked fine the camera, audio, basically it was brand new except for the front screen that is shattered. Later on, i decided to root my Android phone with KingRoot on kingroot.net and it was fast and easy. I didn't know what to do after, my friend told me about it and you can do many things with root. My phone was successfully rooted. I was browsing Google Play untill i saw an app that says "boot animations" I was like "Cool, gonna test it out" so it did install and i opened it. It has a ton of animations and i chose one to be as my boot animation. Unfortuanately, I so stupid forgot to backup the previous original (Motorola boot animation). It now takes a bit longer to boot up (idk whether it was the animation itself, or the fact that my phone is now rooted). I decided to uninstall the root, hoping the boot animation was gone(also kinda blurry). Well it did not, but i was like whatever. Phone still worked fully, and decided to stuck it up with that boot animation.
Now that my phone is unrooted, i decided to root it again since it did not work. I tried to install an app that AdAway and it did work. Ads were gone and i was happy.
Until. A motorola screen popped up saying it has a system update. I forgot what the update is about. All i remember is something do with "stabilizing and other stuff" and takes about 10 min.
So I did install it, phone off'd and on with an android logo with a progress bar. After it was complete A picture of an android lying down with an exclamation mark saying "Error". I was like wtf, what happened. I couldn't boot up my device because of this error. I off'd my phone and then on'd it again. It now says "no command." with the same android guy. I gave up and tried to "wipe data and personalized content" "THIS CANNOT BE UNDONE" so i just accepted it. I off'd my phone and boot it up. There was an infinite boot loop, and tried to do as much as i could. But it always led to this(phone on's then offs a few seconds later then on a few seconds later and a few seconds later An android guy says"Erasing..."few seconds later phone off's again. REPEAT!" It was like this and left it the entire night with a cable charged to it so it will not die. So its now unusable and i do not know wtf i should do. The same friking Android guy saying "erasing" i dont think its erasing because when i hold the (power button + Volume up) it says "data wipe complete". It was just repeating over and over and over again with the say frikin vibration everytime it turns on. Tried to Enter Factory, Recover, normal recovery, wipe data again. Basically i did everything that was reasonable that would fix this boot loop. HELP PLS!
Sorry have bad english.

Samsung Galaxy A71 died after updating to Android 11

Ok, so here is to explain what happened, so you can have a clue what am I talking about.
I bought Galaxy A71 a month ago (give or take), so out of the box it had Android 10. The phone was working flawlessly. Battery life awesome, pictures from camera great, etc. So, few days ago on March 26, 2021, an update to Android 11 came in. I am a tech nerd, I know about phones, rooting, flashing, etc.
So, I saw that I have around 78-80% of the battery so it was enough to download and install Android 11.
Downloading and installing and optimizing apps after went smooth as silk. I usually soft restarting my device after any software update, so I did that after the installation of Android 11 was entirely finished.
But, this is what happen when I restart my phone the normal way. I press and hold the power button, the dialog of Power off, Reset and Airplane mode came out, tapped twice the reset button and phone went restarting and just.... died. I remember that when I soft restarted my phone, the battery was on 72%. So I tried any trick in the books to turn on my phone again like combinations of pressing buttons, then with USB cable, charger, etc, but nothing was responsive. It's like the phone was clinically dead.
My phone is still under warranty and I will probably end up taking it to the T-mobile store, but the point of this thread is to inform others of the situation like mine and see if someone else had the same problem?
Maybe someone will post a solution what to do in situations like this?
If I find any solution, I will update this post with all the details.
You probably done it.But have you plugged it into A computer to see if the computer can detected it?
Essex_Hal said:
You probably done it.But have you plugged it into A computer to see if the computer can detected it?
Click to expand...
Click to collapse
Yes i did, nothing shows in Device Manager. As I said, I tried every possible trick to wake the phone up, but it was unsuccessful.
I end up taking it to the carrier store cuz it is still under warranty. They told me if they can't fix it, they'll probably give me a new one or to wait for Galaxy A72 To arrive in 2 weeks. We'll see what happens.
BorisMKD said:
Yes i did, nothing shows in Device Manager. As I said, I tried every possible trick to wake the phone up, but it was unsuccessful.
I end up taking it to the carrier store cuz it is still under warranty. They told me if they can't fix it, they'll probably give me a new one or to wait for Galaxy A72 To arrive in 2 weeks. We'll see what happens.
Click to expand...
Click to collapse
Least you still have A warranty to help you.
Good luck with it.Hope you don't lose your data if it's still on the phone.
Essex_Hal said:
Least you still have A warranty to help you.
Good luck with it.Hope you don't lose your data if it's still on the phone.
Click to expand...
Click to collapse
They fix it, it said it was software problem, got stuck on rebooting. I get it today (2 weeks later) and it worked. They managed to turn it on but without a factory reset, every app was there, every picture, video, contacts, call history, etc. I don't know how they did it, but they did. So when I got my phone back I tried to restart it normal way, long press of the power button, then tap Restart and again restart. The phone restart it without a problem. I was happy. Then later that day (2 hours ago when I'm writing this, I notice that always on display when i touch the phone screen will show up but doesn't switch off after 10 seconds (I set it up like that), instead it started to blink in intervals like i was touching the screen continuously. Then I did a deep soft reset. You know, when you press Volume down and Power button at the same time and.... got the same problem again. Phone is non functional, none combination of pressing buttons worked, just like i describe it in the OP. Just for information, I did the same on my previous phone Galaxy A7 2018 and never had this problem. I did it on this phone too, never had a problem. Then I remember it that on both phones when i do that and not having problems were running on Android 10. this phone now update it to Android 11 and that buttons combination is probably bricking the phone. It's just a thing I notice. So I am planning to call the official service that fixed the phone how did they do it, so maybe I can do it myself too. I don't want to wait for another 2 and a half weeks.
I am facing the same issue. And I think my warranty is out. Did you get to ask them how can you turn it on yourself!!
I would really appreciate some help here!
BorisMKD said:
Ok, so here is to explain what happened, so you can have a clue what am I talking about.
I bought Galaxy A71 a month ago (give or take), so out of the box it had Android 10. The phone was working flawlessly. Battery life awesome, pictures from camera great, etc. So, few days ago on March 26, 2021, an update to Android 11 came in. I am a tech nerd, I know about phones, rooting, flashing, etc.
So, I saw that I have around 78-80% of the battery so it was enough to download and install Android 11.
Downloading and installing and optimizing apps after went smooth as silk. I usually soft restarting my device after any software update, so I did that after the installation of Android 11 was entirely finished.
But, this is what happen when I restart my phone the normal way. I press and hold the power button, the dialog of Power off, Reset and Airplane mode came out, tapped twice the reset button and phone went restarting and just.... died. I remember that when I soft restarted my phone, the battery was on 72%. So I tried any trick in the books to turn on my phone again like combinations of pressing buttons, then with USB cable, charger, etc, but nothing was responsive. It's like the phone was clinically dead.
My phone is still under warranty and I will probably end up taking it to the T-mobile store, but the point of this thread is to inform others of the situation like mine and see if someone else had the same problem?
Maybe someone will post a solution what to do in situations like this?
If I find any solution, I will update this post with all the details.
Click to expand...
Click to collapse
have same issue too anyways to fix it?

Categories

Resources