Develop Bugs

Android 10 - Factory reset needed?

Hello, everyone!
I just installed Android 10 onto my Pixel 3 XL a couple of hours ago and I've noticed battery drain and some lag. Is a factory reset suggested at this point, since I flashed a new Android version?
Edit:
I had animations removed under "Accessibility" and I toggled it back on, then I turned Dev. Options on and switched animations to .5x and the problem seems to have went away. I'll have to update you all on battery life later. Still, the question remains... Is a reset suggested?

I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?

animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good

razrlover said:
Had to enter stock recovery and reboot myself, mine was black screen. After that i was good
Click to expand...
Click to collapse
Were you on the latest beta before the update? My update file was only 5.5mb. Went pretty quickly.

is it worth factory resetting device with this latest update?

Jay01 said:
is it worth factory resetting device with this latest update?
Click to expand...
Click to collapse
No, if you used the ota through phone, google would of already done maintenance before the install, ie, removed incompatible apps settings and features.

Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.

animeva said:
I just also did the ota update and now my pixel 3xl is stuck on a Google splash screen. Did I just somehow brick my phone?
Click to expand...
Click to collapse
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.

bobbyphoenix said:
This happened to me too. After about five bootloops I finally got it to boot, but it booted back to B6, and the update said it couldn't install. I tried again, and all went well the second time.
Click to expand...
Click to collapse
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit

animeva said:
Ive tried the update 3 times now and every time it has been stuck at the boot. I would have to turn off and try to restart around 3-5 times for it to go back to Android Pie. So still unable to update to Android 10.
Ill try it one more time later and see if maybe they changed the update a bit
Click to expand...
Click to collapse
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.

For small updates like monthly security patches or version increases of 0.1 or 0.0.1 I usually don't worry about doing a clean install since the changes are usually pretty minimal. For large updates I like to do a clean install just for piece of mind that all the crap that built up on my phone over the past year is gone, to eliminate the general issues that pop up with dirty installs, and having a squeaky clean fresh install just feels nice once in a while.

jmartin72 said:
Has anyone flashed the factory image? If so what one did you use. I can't flash the the 10 factory image. The only was I can get it is to flash the Pie factory image, and then take the OTA. Not sure why I get an error every time I try to flash 10.
Click to expand...
Click to collapse
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.

v12xke said:
I updated 9->10 like I normally do each month by dirty flashing the full image (not full OTA) so I would say you do not need to do a factory reset. I did not previously install any of the betas. Although the install took longer and was different (fastbootd) it completed and booted to system the first time. It may just be time for a fresh install, meaning leave the wipe flag in the flash-all script and let it erase your user data.
Click to expand...
Click to collapse
I was doing a complete wipe.
(Update) I finally got it to do a full factory image flash with a complete wipe. The only thing I changed was, I switched from Slot B to Slot A. Not sure if that was even the issue, but It worked, and now My Pixel 3XL is running really well. No issues that are being reported.

bobbyphoenix said:
I don't know if this had anything to do with it but I disabled my ad blocker and I cleared all recent apps and then when I tried it the second time it worked so maybe make sure everything is clear and you have no ad blocker enabled.
Click to expand...
Click to collapse
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now

animeva said:
i didnt install any 3rd party ad-blocker apps on the phone before... if there is any, it would be google's out of box one... i doubt they have one out of the box.
Im too nervous to do this update again only for it to brick again right now
Click to expand...
Click to collapse
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.

v12xke said:
Suit yourself, but if your adb/fastboot binaries are all up to date (July 2019) and you are flashing the full image (not the OTA image), then you should have no issues at all. There are many guides on how to do this properly and the procedure is no different now than with 9. Also, there is no "change" coming to make the install smoother because there is nothing to fix. If your bootloader is unlocked this phone is virtually un-brickable.
Click to expand...
Click to collapse
if i do a full image, not the OTA version, does that require a factory reset?

animeva said:
if i do a full image, not the OTA version, does that require a factory reset?
Click to expand...
Click to collapse
No, but you do need an unlocked bootloader. If you are unlocked go ahead and flash the full image. Be sure to do a version check of your adb/fastboot. Sometimes you can get into trouble if you have old versions in a different location. You need to be sure you are running version 29.0.2 (July 2019). If you did not lose all your user data on past attempts, do a dirty flash (removing the -w flag from the flash-all.bat file). If you already lost your data, then just run the script as-is. GL.
Edit: If you were trying to update 9->10 using an OTA, that is probably your issue. The full image will properly reformat your file system for 10.

Last Ditch Effort for the Old Girl (P2XL)

I recently bought a P4XL and was going to use my P2XL as a stay-at-home bridge between Google Home and P4XL Tasker. The P2XL was running CarbonRom 8.0 so I decided to upgrade to A9 and that's when all hell broke loose.
Here's the relevant steps I took after the initial update stopped responding:
1. Factory reset to A9, A10 & A8 all failed. In that order. Unresponsive.
2. Extracted the boot image from factory and flashed it. Unresponsive.
3. TWRP won't launch (I assume it was wiped out somewhere during #1's hang).
4. TWRP won't boot from fastboot. Somewhere around #2, I started receiving unknown variable errors for the slot.
5. I've also tried Deus (forgive spelling if incorrect) package for boot loops. No dice.
6. I've switched USB cables (A&C) and rebooted 32⁴³⁶ times to no avail.
That's it. Thanks, all, for listening. She's been a great phone. Hoping I can get a bit more out of her. Anyone have any ideas because I'm fresh out.

You know you have to flash factory images for different android version to BOTH slots right? You can't go from A9 to A10/11 and vice versa without flashing the images to both slots or you won't be able to boot.

Flash the official Factory images first

GohanBurner said:
You know you have to flash factory images for different android version to BOTH slots right? You can't go from A9 to A10/11 and vice versa without flashing the images to both slots or you won't be able to boot.
Click to expand...
Click to collapse
Yeah, I never flashed to A because, like I said in the initial post, I never made it past B. That was something I considered early on but I wasn't able to change slots. Got the unknown var error.

ahm_usa said:
Flash the official Factory images first
Click to expand...
Click to collapse
Dude. Seriously?

General NEW: Solution without wiping. Pixel 6 Pro irregular error message: ''Your device is corrupt. It can't be trusted and may not work properly.

New including my solution without wiping:
I have great news, everyone:
First, a very brief summary of what didn't fix the issue:
I had tried flashing the full February factory image, both manually and using the Google Pixel Flash site without wiping, without any luck.
What just fixed the issue now:
I flashed the new (2nd) February full factory image without wiping. When I noticed I didn't get the corruption paused boot screen during one or more parts of the flash-all.bat flashing process, the phone booted normally after it was completely done.
So at the most, if this issue happens again, hopefully I'd only have to wait until the next full factory image is available.
Not pertinent to the solution, but:
Normally in the past, I go ahead and sign in, and let everything load, and then go back into Fastboot and flash my manually Magisk'd boot.img, but this time when it got to the lock screen, I went back into Fastboot right from there and flashed the Magisk'd boot.img I had prepared from before flashing the factory image. I then shut the phone off. I turned the phone on, and still, no corruption paused boot screen.
I haven't flashed a kernel yet. No idea if any need or can be updated for the 2nd February update - I just haven't checked and don't know if there is updated source code available, or if there will be before the March update.
Click to expand...
Click to collapse
Old:
Yes, I know there's a hair on the screen of my images taken with my original Pixel 1 of my Pixel 6 Pro.
Click to expand...
Click to collapse
I know there are other related threads such as this question thread Unlocked Pixel 6 Pro - "Your Device is corrupted and cannot be trusted" error after trying to manually flash Dec 2021 factory image, and other individual posts in various threads, but I wanted to create a thread where I will maintain the OP with what we figure out about this issue.
Click to expand...
Click to collapse
TL;DR:
So far, it seems the only full way to eliminate the issue includes flashing (via Flash-All.bat from the full firmware zip or Official Google Android Flash Tool) with a full wipe, so losing all user data and system settings. When these flashing methods require temporary rebooting in order to start flashing in a different mode, you may have to manually get the phone past the corruption screen for the flashing method to continue where it left off.​​Temporary workarounds are to use either of those two flashing methods while not wiping (in Android Flash Tool, have all the checkboxes unchecked) - this doesn't keep this screen from showing every time you reboot or turn the phone on after being off, but the phone is useable, even with a rooted stock kernel - I haven't tested a custom kernel again.​
Click to expand...
Click to collapse
​Back to the details you may or may not want to know...
This is the corruption screen in question, it precedes the normal bootloader unlocked screen, but in this case, it always requires a manual press of the power button to proceed:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
The g.co/ABH link takes you to Understand warning about operating system safety. It's not very helpful in my opinion as it doesn't tell a way to fix the issue without a full wipe. Below are the contents of the page:
Understand warning about operating system safety​When you turn on an Android device, it checks the operating system to make sure it's safe to use. This means the code comes from a trusted source and hasn't been changed or corrupted.
If your operating system could have a problem, you can get a warning message that brings you to this page (g.co/ABH).
If you changed the operating system on purpose​You can continue using your device. But you acknowledge that your device might not work properly and your data could be exposed to corruption and security risks.
We recommend restoring your device's operating system. If you have a Pixel or Nexus, learn how to flash your device with the latest factory image.
If you didn't change the operating system yourself​
If your device is a Pixel, learn how to get help.
If it's a different Android device, contact your device manufacturer.
Click to expand...
Click to collapse
Spoiler: My original post from another related thread, in response to someone else's question about the solution.
sybor said:
Did you managed to do it using Android Flash Tool without wipping the device?
Click to expand...
Click to collapse
roirraW edor ehT said:
I'm preparing to create a catch-all thread just for this issue. I just experienced the issue for the first time, although I've observed the others who have encountered it under various circumstances.
For myself, it wasn't flashing the February image that caused the error, it was after I flashed a certain custom kernel.zip through EXKM (EX Kernel Manager) that I had the issue. I won't name the kernel as I don't think it's any particular kernel that's the issue, although I don't know what the cause is.
Previous to updating to the February firmware, I was on the January (and with Verity and Verity NOT disabled either time) and was using a different custom kernel zip without any issue. I went through the process pretty much identically to how I had previously. Using the stock kernel worked fine, and using the stock kernel rooted with Magisk 24.1 worked just fine as well. I first had the issue after rebooting from flashing a kernel.zip through EXKM, and I still have it.
I'm not 100% sure this was necessary but using the Android Flash Tool or the manual firmware flash-all.bat (both without wiping, and the Android Flash Tool with no checkboxes checked) both resulted in the phone being usable again, however when I reboot I still get that first (and different than the bootloader unlocked screen) corruption screen.
I will create my thread with images very soon, but I wanted to share what little I know so far, and at least the phone works, it's just a slight PITA that when I reboot or boot from the phone being off that I get that error which requires a manual power button press to go past. Note that during the re-flashing process that I sometimes had to manually press the button during the times the flash process reboots the phone into a different mode before it would continue the flashing process.
Click to expand...
Click to collapse
As you can see below, after flashing (but without wiping) I'm able to boot as normal (only tested with the stock February kernel, rooted with Magisk 24.1), with the only exception being the third screenshot from the top-left, about corruption, and requiring manually pressing the power button to get past the screen.
​

In case I need this post #2.

In case I need this post #3.

In case I need this post #4. (Last one of these)

It happened to me once when I sideloaded January's OTA and a full wipe with the Android Flash Tool worked, manually flashing via adb did not. However, I got that corrupt boot screen when flashing February's update via AFT. It was worse trying to fix the problem this go-around because I wiped the phone multiple times via AFT with various options (wiped, disable verity, even relocked the bootloader and returned to stock). It finally stuck but I'm not sure what I did.
I tried all the suggestions on XDA and around the Internet but nothing helped. Closest thing I could figure out was maybe one of the boot slots had had encryption and the other didn't so the update failed? It sucked, because now I'm hesitant to flash any kernels or even a patched magisk image because that damn corrupt boot screen appears way too easily.

Had this come up once on my wife's 5a.
This means there is dm-verity corruption:
Boot Flow | Android Open Source Project
source.android.com
Not a big deal really, the Magisk wizards will figure this out eventually. Sideloading the OTA fixed it.

Copied and pasted (for the most part) from another post of mine:
"That corrupt message means you have a dm verity corruption. Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up, thus triggering this warning. Also, pressing the power button puts the phone in restart mode instead of eio mode and will allow you to boot up in this circumstance."
See documentation below (which shows the warning sign in red but with the same message).
Boot Flow | Android Open Source Project
source.android.com
Verifying Boot | Android Open Source Project
source.android.com
EDIT: And Ninja'd by 1 minute by @V0latyle

Lughnasadh said:
Copied and pasted (for the most part) from another post of mine:
"That corrupt message means you have a dm verity corruption. Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up, thus triggering this warning. Also, pressing the power button puts the phone in restart mode instead of eio mode and will allow you to boot up in this circumstance."
See documentation below (which shows the warning sign in red but with the same message).
Boot Flow | Android Open Source Project
source.android.com
Verifying Boot | Android Open Source Project
source.android.com
Click to expand...
Click to collapse
Beat you to it, thanks for the additional explanation

V0latyle said:
Beat you to it, thanks for the additional explanation
Click to expand...
Click to collapse
I edited my post to reflect your Ninja prowess

Lughnasadh said:
I edited my post to reflect your Ninja prowess
Click to expand...
Click to collapse

It happened to me back in December when I first got my P6P and was rooting it. I couldn't get it to boot though. I tried using the repair tool, but it wouldnt find my device. I tried manual flashing via adb, but it would fail. I was about to send it back to google when I figured I would try to switch boot partitions and that fixed it.

dunno how I got this message as I only got it after flashing a custom kernel which dev said includes the magisk version that does not veed verity disabled.
i hope in march ota when I flash that it will go back to previous boot slot it dont say that.
I will probably do a full wipe and flash when I get some time as the message is annoying as it adds delay to boot

V0latyle said:
Had this come up once on my wife's 5a.
This means there is dm-verity corruption:
Boot Flow | Android Open Source Project
source.android.com
Not a big deal really, the Magisk wizards will figure this out eventually. Sideloading the OTA fixed it.
Click to expand...
Click to collapse
Thank you! Sideloading just now didn't fix it for me. I tried it while I was already on the February full firmware.
Spoiler: The details of my sideloading
I just sideloaded the full February OTA after I manually restored the unrooted stock February kernel. This might have been the first time I've sideloaded an OTA, or only the second time - I might have done it once on the Pixel 1. The Result code was 0 (zero) for both verification and installation, which appears to mean success where 1 would mean failure.
After success, I booted Android, unlocked the phone, kept it unlocked, and I waited at least 10 minutes since your instructions say:
Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
Click to expand...
Click to collapse
I never actually saw a notification regarding it, however - like I would if I tried an actual over-the-air update - "Finishing Update" or something like that. I rebooted after than 10+ minutes and still got the paused-boot corruption screen. After unlocking I waited again and then rebooted and same result.
I'm contemplating flashing the full firmware image for January without wiping and with suppressing reboot so no February-specific data is affected by suddenly being on the January firmware, and then immediately applying the February OTA again to see if that helps.
Do you anticipate any problems with this plan, or do you have a better suggestion for me to try first? No worries if anything goes wrong - I have nothing on my phone that isn't backed up, I'm just trying to avoid having to re-copy hundreds of gigs of FLAC formatted music yet again, LOL!
Lughnasadh said:
Copied and pasted (for the most part) from another post of mine:
"That corrupt message means you have a dm verity corruption. Because there is a corruption, you are in eio dm verity mode. A clean flash (or factory reset) without corruption errors will allow the bootloader to see that a new OS has been installed and will switch back to restart mode and remove that warning. Apparently the root hash of the hash tree and the expected root hash aren't matching up, thus triggering this warning. Also, pressing the power button puts the phone in restart mode instead of eio mode and will allow you to boot up in this circumstance."
See documentation below (which shows the warning sign in red but with the same message).
Boot Flow | Android Open Source Project
source.android.com
Verifying Boot | Android Open Source Project
source.android.com
EDIT: And Ninja'd by 1 minute by @V0latyle
Click to expand...
Click to collapse
Thank you! I appreciate the details and the additional link to relevant information.

roirraW edor ehT said:
I'm contemplating flashing the full firmware image for January without wiping and with suppressing reboot so no February-specific data is affected by suddenly being on the January firmware, and then immediately applying the February OTA again to see if that helps.
Do you anticipate any problems with this plan, or do you have a better suggestion for me to try first? No worries if anything goes wrong - I have nothing on my phone that isn't backed up, I'm just trying to avoid having to re-copy hundreds of gigs of FLAC formatted music yet again, LOL!
Click to expand...
Click to collapse
Well, this is how things went wrong on my wife's Pixel 5a:
Restored boot image in Magisk, installed OTA. Rebooted. Successful boot, no root (because she rebooted it before I had a chance to install to inactive slot)
Switched active slot to the "old" slot. Bootlooped.
Dirty flashed January factory image on old slot. Verity EIO corrupt warning. Bootlooped.
Dirty flashed January factory image to both slots. Bootlooped, Rescue Party data corrupt warning.
Downloaded and dirty flashed February factory image to both slots. Bootlooped, Rescue Party.
Sideloaded the February OTA to the "new" slot. Successful boot. Attempted to live boot previously patched image, I believe January patched with 23017. Rescue Party.
Patched February boot image in Magisk Stable 24, rebooted to bootloader and live booted. Successful. Performed Direct Install in Magisk, and rebooted. Successful boot with root.
There is something to do with the OTA mechanism that will bork everything if you try to mess with it. I do know that if it doesn't successfully boot the updated slot, it will mark that slot "unsuccessful" and won't try to boot it again, and will then revert to the old slot. I don't know why it didn't just boot the old slot in my case.
Going forward, at least until we figure out the problem with automatic OTAs, the safest method of update is either dirty flashing the factory image (can use Android Flash Tool as well), or sideloading the OTA.

I posted this back in November/December after trying to flash factory image without the wipe command (factory image not ota). The problem with mine was I couldn't get past the message. At all. I wiped the device twice in recovery menu and it still wouldn't boot. I had to reflash The mid November build (on both slots) and wipe in between.
Then in December I disabled Location for ImsService in the privacy menu and the message appeared again - this time it would boot but only for two seconds, then it would automatically restart. Duplicated the issue after January update but haven't tried it since.
Many posts on Reddit for the 5/5a with this issue and the fix for those devices was to update Play Services and All apps in safe mode (with Bluetooth off - many users experienced their devices restart with the 'device is corrupt' message after turning on Bluetooth). I'll edit my post when I find the other posts to these issues, but it seems like a few things can cause this message to appear.
Awesome thread though. Unfortunately it looks like @roirraW "edor" ehT will be copying 200gb of music soon enough if no solution is found.
searching for 'corrupt' on reddit's GooglePixel sub shows this problem was mostly prevalent from November-December, Pixels 4-6.

Alekos said:
I posted this back in November/December after trying to flash factory image without the wipe command (factory image not ota). The problem with mine was I couldn't get past the message. At all. I wiped the device twice in recovery menu and it still wouldn't boot. I had to reflash The mid November build (on both slots) and wipe in between.
Then in December I disabled Location for ImsService in the privacy menu and the message appeared again - this time it would boot but only for two seconds, then it would automatically restart. Duplicated the issue after January update but haven't tried it since.
Click to expand...
Click to collapse
Interesting experience. Thank you for sharing the details.
Alekos said:
Many posts on Reddit for the 5/5a with this issue and the fix for those devices was to update Play Services and All apps in safe mode (with Bluetooth off - many users experienced their devices restart with the crop message after turning on Bluetooth). I'll edit my post when I find the other posts to these issues, but it seems like a few things can cause this message to appear.
Click to expand...
Click to collapse
I'm trying this now since it won't hurt any. I rebooted to safe mode, eventually remembered to turn off Airplane mode, I turned off Bluetooth just to make it a controlled experiment, then I updated the ~14 apps that had updates available. For the heck of it, I checked to see if there was any Play System update available to me and there wasn't, so next I uninstalled all updates for Google Play services, and reinstalled them.
I then rebooted, but I still have the paused-boot corruption screen. Worth a try, though. If you find more details, let me know, please.
Alekos said:
Awesome thread though. Unfortunately it looks like @roirraW "edor" ehT will be copying 200gb of music soon enough if no solution is found.
Click to expand...
Click to collapse
LOL!!
Edit: I wish going to safe mode didn't cause Nova Launcher Prime from resetting all my home screen widgets. It's not that big a deal to reconfigure them but I wish there was a way to keep that from happening.
My three Weawow weather widgets and my two Multi Timer widgets are the worst - and not terrible, just a little bit tedious. I'm getting used to it, though! LOL!

roirraW edor ehT said:
Interesting experience. Thank you for sharing the details.
I'm trying this now since it won't hurt any. I rebooted to safe mode, eventually remembered to turn off Airplane mode, I turned off Bluetooth just to make it a controlled experiment, then I updated the ~14 apps that had updates available. For the heck of it, I checked to see if there was any Play System update available to me and there wasn't, so next I uninstalled all updates for Google Play services, and reinstalled them.
I then rebooted, but I still have the paused-boot corruption screen. Worth a try, though. If you find more details, let me know, please.
LOL!!
Edit: I wish going to safe mode didn't cause Nova Launcher Prime from resetting all my home screen widgets. It's not that big a deal to reconfigure them but I wish there was a way to keep that from happening.
My three Weawow weather widgets and my two Multi Timer widgets are the worst - and not terrible, just a little bit tedious. I'm getting used to it, though! LOL!
Click to expand...
Click to collapse
what's interesting is, just from reading the posts on Reddit, looks like Pixels 4-5 were fixed by the update solution, but not for the 6. Here's one post.
Also, your message is completely different than the one I saw. Mine looked like the attachment.
edit--
And it looks like at least 10 users on this sub have posted about this issue, including this user who still can't fix his phone.
edit--#2--
shoot I know, Safe Mode causes weird things to happen with Launchers.... dammit sorry!!
edit --#3-- fixed link, woops thanks @roirraW "edor" ehT

Alekos said:
what's interesting is, just from reading the posts on Reddit, looks like Pixels 4-5 were fixed by the update solution, but not for the 6. Here's one post.
Also, your message is completely different than the one I saw. Mine looked like the attachment.
edit--
And it looks like at least 10 users on this sub have posted about this issue, including this user who still can't fix his phone.
Click to expand...
Click to collapse
Very interesting. Maybe there's a slight difference in the cause or some other detail we don't know yet, since the problem on mine wasn't preceded by wired or wireless headphones being used. Very interesting! Your link "this" became garbled. Here's the fixed link. this

Alekos said:
edit--#2--
shoot I know, Safe Mode causes weird things to happen with Launchers.... dammit sorry!!
Click to expand...
Click to collapse
That's quite alright, not your fault. I've only recently started fooling with safe mode so it's still a slight surprise to me each time, but I think it won't stay a surprise for much longer.
Alekos said:
edit --#3-- fixed link, woops thanks @roirraW "edor" ehT
Click to expand...
Click to collapse
You're welcome!

I had this error after a non-wipe upgrade, coupled with bootloops. I had everything backed up so I did a complete factory image install and re-rooted. The phone runs like new again and all rooting conflicts are resolved.

Question February Update caused my phone to reboot all the time

Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?

How did you install it? I'd wipe it and reinstall with the android flashtool
Android Flash Tool
flash.android.com

fil3s said:
How did you install it? I'd wipe it and reinstall with the android flashtool
Android Flash Tool
flash.android.com
Click to expand...
Click to collapse
Directly through the phone's regular system update.

WHOneedsSOX said:
Directly through the phone's regular system update.
Click to expand...
Click to collapse
I don't think you need a unlocked bootloader to sideload just USB debugging enabled if you wanted to try a full wipe. Maybe try factory reseting from settings - I'm going on the assumption that the bootloader isn't unlocked

WHOneedsSOX said:
Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?
Click to expand...
Click to collapse
You can't downgrade once you've upgraded. It's best if you backup your data and try starting fresh on the February build to see if it causes any issues.
Use the flash tool and make sure both partitions are formatted and try again.
Did you do any modifications to your phone that could have caused the random reboots?

fil3s said:
I don't think you need a unlocked bootloader to sideload just USB debugging enabled if you wanted to try a full wipe. Maybe try factory reseting from settings - I'm going on the assumption that the bootloader isn't unlocked
Click to expand...
Click to collapse
That's correct, it isn't unlocked.
RetroTech07 said:
You can't downgrade once you've upgraded. It's best if you backup your data and try starting fresh on the February build to see if it causes any issues.
Use the flash tool and make sure both partitions are formatted and try again.
Did you do any modifications to your phone that could have caused the random reboots?
Click to expand...
Click to collapse
I have done absolutely no modifications other than typical downloading of apps and modifying through there but even that is just theming. By "try again," just wipe and then reinstall the update?

WHOneedsSOX said:
Had absolutely no issues with my Pixel 6 Pro on the January update but as soon as I installed the February update my phone reboots so much when the screen is off. When I'm using it, there are no issues. The second I turn off the screen, it reboots. Then it'll reboot 5 more times before I can even unlock my phone. Then I'll turn the screen off and it'll reboot again. It must have rebooted around 500 times last night.
Is there a fix for this? Or a step by step guide on how to install the January update over the February one?
Click to expand...
Click to collapse
The random reboot bug seems to be a problem with Android 12. I haven't yet seen any clues as to the reason why.
Sometimes it's caused by a backup, sometimes by an update, some claim it's because of a hardware failure.
I experienced the same when I got my Pixel 6 Pro out of the box - about 2 random reboots per day, I had to get a replacement device to fix that.
My Pixel 3 also has the random reboot problem right after I updated it to Android 12, just like you said - every couple minutes, even though it reboots BOTH when in active usage AND when the screen is off. I have not yet tinkered with the device to find the reason, since I don't need that phone (anymore).

As a last resort, if you don't want to lose data on reseting the device, my advice would be to:
Download the latest OTA to your PC & sideload it in recovery mode (hold vol down before screen comes on, upon reboot). That will re-flash all important blocks & will boot you from the opposite partition (A/B) but keep your data/apps, hopefully fixing whatever the issue is in the process.

Morgrain said:
The random reboot bug seems to be a problem with Android 12. I haven't yet seen any clues as to the reason why.
Sometimes it's caused by a backup, sometimes by an update, some claim it's because of a hardware failure.
I experienced the same when I got my Pixel 6 Pro out of the box - about 2 random reboots per day, I had to get a replacement device to fix that.
My Pixel 3 also has the random reboot problem right after I updated it to Android 12, just like you said - every couple minutes, even though it reboots BOTH when in active usage AND when the screen is off. I have not yet tinkered with the device to find the reason, since I don't need that phone (anymore).
Click to expand...
Click to collapse
I'd be happy with 2 random reboots per day. Not even kidding, I must be at 100 a day. It's super random too. None from 9 am until around 1pm and then all of a sudden 10 in a row.
I'm pretty sure it's a software issue, had no random reboots before I installed the February update. Will probably try reformatting the entire phone first and see how that goes.
DanielF50 said:
As a last resort, if you don't want to lose data on reseting the device, my advice would be to:
Download the latest OTA to your PC & sideload it in recovery mode (hold vol down before screen comes on, upon reboot). That will re-flash all important blocks & will boot you from the opposite partition (A/B) but keep your data/apps, hopefully fixing whatever the issue is in the process.
Click to expand...
Click to collapse
Thanks, will try this out if a reformat doesn't work.

Try safe mode and see if it still happens.

neyes said:
Try safe mode and see if it still happens.
Click to expand...
Click to collapse
Still happened in safe mode.

I would honestly try a complete wipe and fresh install of the OS to see if it still happens. If it does you could get it RMAd since it could be hardware related.

RetroTech07 said:
I would honestly try a complete wipe and fresh install of the OS to see if it still happens. If it does you could get it RMAd since it could be hardware related.
Click to expand...
Click to collapse
By "wipe and fresh install" do you mean reformatting it normally through the phone (like if I was returning a used phone)? Or is it as Daniel suggested above?

WHOneedsSOX said:
By "wipe and fresh install" do you mean reformatting it normally through the phone (like if I was returning a used phone)? Or is it as Daniel suggested above?
Click to expand...
Click to collapse
Official Google Android Flash Tool

roirraW edor ehT said:
Official Google Android Flash Tool
Click to expand...
Click to collapse
Thanks!

General Had issue with OTA sideload of 2nd February update, device is corrput, now working

I had a strange and new issue for me today. Went to sideload the OTA update (2nd February 2022 update). I have been doing it this way for the last few, with no issues. All seemed fine, but got an error when trying to flash the new magisk boot.img. Tried again and seemed to go thru. Rebooted then to bootloop. Keep trying and nothing, tried to get back in and flash again, also tried flashing stock boot to all slots, nothing.
So I had to resort to using the flash tool (in chrome). I assumed I would lose all and had made backups prior, so I would make it work. Using the flash tool, got in, got device connected. Then I selected the .004 build and unchecked all options. I can't remember for sure but I think I also unchecked the force flash all partitions/slots (I think that is what it was called). The flash tool did its thing and came back online, and seemed like no data loss, which was great. I then re-downloaded platform tools, factory image and OTA, got fresh boot.img, patched in magisk, flashed it and all good. After that, I did the direct install too, just in case, but I don't think that is needed, but doing so didn't mess anything up.
Not sure if this is normal, or helpful to anyone, but in my frantic searching, I didn't see a ton on this, so thought I would share it in case it happens to anyone else.
I have a feeling I should do what I normally do, reboot my pc and then download all items needed and flash away. I usually do that and haven't had issues to date. All ended up being good. If anyone runs into this, hope this helps you out.
Thanks for all the info on this forum, it is a great help to keeping my phone updated and running.

I had same problem

I had no issues. Same process... Recovery, ota sideload, reboot, let it finish setting up, patch boot.img extracted from full image, reboot into bootloader and flashed boot sector. All is fine.

I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.

DirtyPISTOLA said:
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
Click to expand...
Click to collapse
I think you can just use the flash tool. Check the appropriate options and it should wipe everything and return it to stock. It looks like you can even use it to lock bootloader again, if you wanted to. This was my first time using it. I may play around with it on one of my old pixels. Never had a use for it before, but came in very handy this week. Probably good for me if I know a bit more about it and how to use it.

DirtyPISTOLA said:
I know this is a little dumb but this is my first pixel and I usually restored my samsung phones with odin. Does anyone have a guide how to unroot the Pixel 6 Pro and flash stock firmware incase I need this in future instances, All I can seem to find is Rooting guides.
Click to expand...
Click to collapse
Within the guide is this post and I'm sure many other posts.
[GUIDE] Pixel 6 "oriole": Unlock Bootloader, Update, Root, Pass SafetyNet
⚠️⚠️⚠️WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST! ⚠️⚠️⚠️ If you are looking for my guide on a different Pixel, find it here: Pixel 3 Pixel 3XL Pixel 3a Pixel 3aXL Pixel 4 Pixel 4XL Pixel 4a Pixel 4a (5G)...
forum.xda-developers.com
Here's the guide: https://forum.xda-developers.com/t/guide-root-pixel-6-oriole-with-magisk.4356233/

Thank you all, I figured out that online flash tool is a thing. I got it now.

hpower1 said:
I had a strange and new issue for me today. Went to sideload the OTA update (2nd February 2022 update). I have been doing it this way for the last few, with no issues. All seemed fine, but got an error when trying to flash the new magisk boot.img. Tried again and seemed to go thru. Rebooted then to bootloop. Keep trying and nothing, tried to get back in and flash again, also tried flashing stock boot to all slots, nothing.
So I had to resort to using the flash tool (in chrome). I assumed I would lose all and had made backups prior, so I would make it work. Using the flash tool, got in, got device connected. Then I selected the .004 build and unchecked all options. I can't remember for sure but I think I also unchecked the force flash all partitions/slots (I think that is what it was called). The flash tool did its thing and came back online, and seemed like no data loss, which was great. I then re-downloaded platform tools, factory image and OTA, got fresh boot.img, patched in magisk, flashed it and all good. After that, I did the direct install too, just in case, but I don't think that is needed, but doing so didn't mess anything up.
Not sure if this is normal, or helpful to anyone, but in my frantic searching, I didn't see a ton on this, so thought I would share it in case it happens to anyone else.
I have a feeling I should do what I normally do, reboot my pc and then download all items needed and flash away. I usually do that and haven't had issues to date. All ended up being good. If anyone runs into this, hope this helps you out.
Thanks for all the info on this forum, it is a great help to keeping my phone updated and running.
Click to expand...
Click to collapse
Did you check the downloaded files via checksum?

If you update via OTA, whether via delta or sideload, you CANNOT interrupt the boot process, otherwise the device assumes the update has failed.
Additionally, if you try to use an older boot image, you'll get the same result.
The recommended means of update is either delta OTA + install to inactive slot in Magisk, or factory image + patch new boot image in Magisk.