Develop Bugs

Google Pixel XL keeps rebooting

Hey guys,
I need some help with my pixel. The phone has been rebooting like crazy the last few days, at least 10 times a day. I can't figure what it is. The phone is not rooted and the bootloader is locked

edwardlanti said:
Hey guys,
I need some help with my pixel. The phone has been rebooting like crazy the last few days, at least 10 times a day. I can't figure what it is. The phone is not rooted and the bootloader is locked
Click to expand...
Click to collapse
Try a factory reset. And run it with only the apps that come installed for 24 hours. If it still reboots its a hardware failure. If it doesnt reboot then some software you had on it was causing a crash.

Scott said:
Try a factory reset. And run it with only the apps that come installed for 24 hours. If it still reboots its a hardware failure. If it doesnt reboot then some software you had on it was causing a crash.
Click to expand...
Click to collapse
I had a pixel xl rebooting 2-3 times a day, did exactly this, reboots persisted... Was within 14 days and got the phone swapped out. New phone does not have any reboot issues.

Pretty much any phone that I restore my last backuo from marshmallow causes not stop reboots. When I got Nouget on my 6p somehow the restore screwed something up. When I got my pixel there were 2 dates to restore from. One from my 6p prior to Nouget, and one from Nouget that was a clean install from scratch. The pre 7 restore caused the pixel to reboot constantly just as it had the 6p.

I noticed my phone restarted and the date was set to Jan 1st 1970 while it was in my pocket. I did a adb bugreport but could not find anything. I did find this line though check_reboot_mode: restart_reason: 0x00000000. Does the phone ask for pin only when it restarts? I have fingerprint based authentication setup but it still asks for pin from time to time, now I am wondering if those were restarts.

318sugarhill said:
Pretty much any phone that I restore my last backuo from marshmallow causes not stop reboots. When I got Nouget on my 6p somehow the restore screwed something up. When I got my pixel there were 2 dates to restore from. One from my 6p prior to Nouget, and one from Nouget that was a clean install from scratch. The pre 7 restore caused the pixel to reboot constantly just as it had the 6p.
Click to expand...
Click to collapse
It's generally a good idea not to restore a backup from a previous major system iteration. Anytime a new generation is introduced, one should do a clean install, as you noted in your last sentence. There are potentially a lot of system changes that can cause conflicts.

edwardlanti said:
Hey guys,
I need some help with my pixel. The phone has been rebooting like crazy the last few days, at least 10 times a day. I can't figure what it is. The phone is not rooted and the bootloader is locked
Click to expand...
Click to collapse
Hello,
I had the same issue with the most recent Verizon update on my wife's Pixel. There seems to be a lot of people with Pixels having this issue as well. I needed to return it for a new one...Verizon is aware of the issue as they did not hesitate to replace the unit.
Cheers

Helpful tip, hopefully.
If you want to test the effect of installed apps, Pixels can boot into "safe mode," where installed apps are disabled temporarily. Press and hold power button to open a reboot menu, then press and hold "Power off" button. A menu will open to allow booting into "safe mode."
https://support.google.com/pixelphone/answer/2852139?hl=en

Do you have any apps under beta? I was using around 6-8 apps in beta, I unsubscribed out of the beta and reinstalled all the apps. My phone stopped rebooting.
P.S. My phone was rebooting even under safe mode!

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.

constant "Bluetooth keeps stopping"

I just started receiving the error "Bluetooth keeps stopping" on my Pixel 3 XL a week ago. It comes and goes seemingly completely at random, sometimes clicking close app will work and other times it will just keep coming back over and over until I restart my phone. It's a huge problem because it takes my wifi and sometimes I think even my mobile data down with it. I've read a bunch of posts and it seems like many people have been having this issue.
I've tried turning off Wi-fi and Bluetooth scanning.
updating Google Play system update.
Clearing cache and storage of Bluetooth.
resetting every bluetooth device I own
Factory Reset
sideloading an OTA image
Flashing a factory image
I'm all out of ideas. The only thing I can come up with is it's a hardware issue, but generally hardware issues I run into are not so sporadic and random. Usually it's either broke, or not broke. It doesn't seem to correlate to how hot the phone gets. I feel like Google broke something with an Android update. I've tried to warranty it through Google but I purchased it new on Ebay and they want the original purchasers name, email and order number. Anyone know of a way around that for Google's warranty?
As a last ditch effort I just flashed the Sep 18th Android 9 factory image, crossing my fingers that for some reason that does something.
My only other idea is google has driver binaries posted for pixel devices. Do these binaries get written over/rolled back when the factory image is flashed? Or are they isolated and not touched when flashing a factory image? Could flashing new driver binaries fix the problem? If so, does anyone have a guide on how to flash the driver binaries, google gives documentation for sideloading the OTA or flashing factory images, but nothing for how to install the driver binaries.

iwestfall7062 said:
I just started receiving the error "Bluetooth keeps stopping" on my Pixel 3 XL a week ago. It comes and goes seemingly completely at random, sometimes clicking close app will work and other times it will just keep coming back over and over until I restart my phone. It's a huge problem because it takes my wifi and sometimes I think even my mobile data down with it. I've read a bunch of posts and it seems like many people have been having this issue.
I've tried turning off Wi-fi and Bluetooth scanning.
updating Google Play system update.
Clearing cache and storage of Bluetooth.
resetting every bluetooth device I own
Factory Reset
sideloading an OTA image
Flashing a factory image
I'm all out of ideas. The only thing I can come up with is it's a hardware issue, but generally hardware issues I run into are not so sporadic and random. Usually it's either broke, or not broke. It doesn't seem to correlate to how hot the phone gets. I feel like Google broke something with an Android update. I've tried to warranty it through Google but I purchased it new on Ebay and they want the original purchasers name, email and order number. Anyone know of a way around that for Google's warranty?
As a last ditch effort I just flashed the Sep 18th Android 9 factory image, crossing my fingers that for some reason that does something.
My only other idea is google has driver binaries posted for pixel devices. Do these binaries get written over/rolled back when the factory image is flashed? Or are they isolated and not touched when flashing a factory image? Could flashing new driver binaries fix the problem? If so, does anyone have a guide on how to flash the driver binaries, google gives documentation for sideloading the OTA or flashing factory images, but nothing for how to install the driver binaries.
Click to expand...
Click to collapse
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation

billyt1 said:
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
Click to expand...
Click to collapse
Just a precaution, as soon as you start locking and unlocking bootloader you're going to be doing a complete wipe of your device. So backup before hand. You'll also want to do a complete install of the factory image, with the wipe option, before you attempt to lock the bootloader. If you lock the bootloader and you are not 100% stock of something goes wrong you could end up with an expensive paper weight.

billyt1 said:
Try flashing the dec/Jan build then lock bootloader then start phone as normal setup then unlock bootloader. There's also some Bluetooth settings in the developer ootions. Also check battery settings for the app maybe try turning off optizmation for it. There's also a setting somewhere that will let you turn off the ble236a scan it's always on mine new pair list. But the drivers are usually flash with the update or ota. I needed to flash those when flashing Dirty Unicorns. Fastboot flash vendor_a vendor.img and same for vendor_b believe the other is the radio img you would need to extract them with 7zip if using Windows.
Mine did this as well but I was using naptime,and servicly to kill and or deep sleep quicker. Which is what made me think of the battery optizmation
Click to expand...
Click to collapse
The error happened once immediately after a full factory image flash before I had downloaded a single program or changed a single setting, so I don't see how it could be bluetooth settings, battery optimization, wifi/bluetooth scanning, or a rogue app. Oddly enough, since posting this last night I've managed to go 12 hours without an errors after flashing the Sept 2018 factory image. buuuuuuuut now I'm afraid to upgrade to Android 10 again.
jd1639 said:
Just a precaution, as soon as you start locking and unlocking bootloader you're going to be doing a complete wipe of your device. So backup before hand. You'll also want to do a complete install of the factory image, with the wipe option, before you attempt to lock the bootloader. If you lock the bootloader and you are not 100% stock of something goes wrong you could end up with an expensive paper weight.
Click to expand...
Click to collapse
Thank you for making sure I understood this. Yeah, I generally factory reset my phone and laptop once a year so I always back everything up before a reset. And yeah, I haven't changed anything from stock on this phone since I've had it, so unlocking and locking the bootloader should never cause any issues. As I told Billy, the Sept 2018 image seems to have fixed the problem, fingers crossed.
Is it probable that upgrading once again to Android 10 will cause the issue to return? The Sept 2018 image must have changed an internal setting or driver that wasn't functioning properly.

iwestfall7062 said:
Is it probable that upgrading once again to Android 10 will cause the issue to return? The Sept 2018 image must have changed an internal setting or driver that wasn't functioning properly.
Click to expand...
Click to collapse
I can't tell you for sure, but i would think the latest firmware should work. There have been a number of Bluetooth fixes since the original firmware, which it appears you're on now. That, and lots of security fixes.

jd1639 said:
I can't tell you for sure, but i would think the latest firmware should work. There have been a number of Bluetooth fixes since the original firmware, which it appears you're on now. That, and lots of security fixes.
Click to expand...
Click to collapse
Yeah, I mean I would much prefer being on Android 10 and having the latest updates, I normally update as soon as they come out. But, given that I flashed the Jan 2020 image and bluetooth was still broken, and then flashed the Sep 2018 which seems to have fixed it, I'm hesitant to go back to the Jan 2020 updates. Kind of tending towards the if it isn't broken, don't fix it philosophy right now. If I had time to monkey around with my phone all the time I wouldn't mind, but the semester just started and I use my phone for everything at school so I don't really have time for it to be not working. >.< Such an odd issue and odd fix.

Looks hardware related, like the cable is loose.

wangdaning said:
Looks hardware related, like the cable is loose.
Click to expand...
Click to collapse
And it's continuing to happen even with the Sept 2018 factory image flash.
Why do you think it's hardware related and that a cable is loose when a reboot fixes it? If the cable is loose a reboot shouldn't fix it.

iwestfall7062 said:
And it's continuing to happen even with the Sept 2018 factory image flash.
Why do you think it's hardware related and that a cable is loose when a reboot fixes it? If the cable is loose a reboot shouldn't fix it.
Click to expand...
Click to collapse
What do you have Bluetooth connected to when it happens?

jd1639 said:
What do you have Bluetooth connected to when it happens?
Click to expand...
Click to collapse
Nothing. It doesn't matter whether anything is connected or not. It literally happened on first boot up of a fresh flashed Jan 2020 factory image, before I had put a single thing on the phone.
Generally I have my Fitbit Versa connected, I got 2 tiles awhile ago, but first troubleshooting thing I did was remove the app and delete those from bluetooth since those were my latest additions to bluetooth. I have backbeat fit headphones I use sometimes, the same with bose soundlink ii headphones, ps4 controllers, a jbl pulse 3, my car radio. But I factory restored all of those items so they weren't trying to connect to my phone, and then flashed the factory image. So I don't see how it has anything to do with an actual bluetooth connection.

Im having this same exact issue. Android 9 was always super smooth. It all started with the Android 10 update. I was having all kinds of Radio related (wifi/bluetooth/data) issues ever since. I noticed sometime in Nov/Dec that google released some kind of radio system app update and things got a little better. But I still have the Bluetooth problem (like today, which prompted me to find this thread) or every once in a while ill lose all data connectivity and have to reboot my phone for everything to come back. I LOVE the dark theme, but this has to be the worst Android update from a stability standpoint ive ever experienced.
Just want you to know it isnt just you. Its something to do with some phones on Android 10

JJT211 said:
Im having this same exact issue. Android 9 was always super smooth. It all started with the Android 10 update. I was having all kinds of Radio related (wifi/bluetooth/data) issues ever since. I noticed sometime in Nov/Dec that google released some kind of radio system app update and things got a little better. But I still have the Bluetooth problem (like today, which prompted me to find this thread) or every once in a while ill lose all data connectivity and have to reboot my phone for everything to come back. I LOVE the dark theme, but this has to be the worst Android update from a stability standpoint ive ever experienced.
Just want you to know it isnt just you. Its something to do with some phones on Android 10
Click to expand...
Click to collapse
Yeah, I wish this thread held a solution for you. I've searched and searched and tried every solution I've found on google and nothing has worked, and really none of the threads I have found have ever had a concrete solution either, just one or two people going "well I did THIS and it worked", and a bunch of people saying it didn't work for them. I just cannot fathom how a full factory flash back to the very first image would not revert the changes that came with Android 10. That's why I was questioning whether or not a factory flash replaces driver binaries. It's the only way I could see the factory flash to Sept 2018 not fixing our issue. (Other than it really being a hardware issue, but that doesn't seem possible to me.)

Oh wow, you're still having same issues on Android 9??
Im still on Android 10, most recent update. I did do a full factory flash a few weeks ago and it was quite the improvement. But I still do have the Bluetooth/radio issue every once in a while, like yesterday.
I wonder if it's a hardware issue and/or substandard hardware performance that Android 10 made more prevalent? That's something we'll probably never know

I only pointed to hardware as I had a similar issue years ago. The radio connections were slightly loose so it would come and go. I do hope you are able to figure out what is wrong, was not trying to be rude.

wangdaning said:
I only pointed to hardware as I had a similar issue years ago. The radio connections were slightly loose so it would come and go. I do hope you are able to figure out what is wrong, was not trying to be rude.
Click to expand...
Click to collapse
Oh no, I didn't think for a second you were being rude. And I appreciate your idea, just with what I'm experiencing with my specific phone it doesn't seem to be a hardware issue.
Strangely enough, the issue has been tapering off as of late, after the factory resets I just continued to use my phone while I wait to figure out if I can get a refund or a warranty replacement, etc. The issue has been occurring with much less frequency since then. Still happens, but not like it was.

Damn, the Bluetooth bug is back again. It was so bad the other day, my phone kept bootlooping for like 20 mins while I was on the road.
I finally just let phone sit for a while and it fixed itself. Man this is completely sporadic.

JJT211 said:
Damn, the Bluetooth bug is back again. It was so bad the other day, my phone kept bootlooping for like 20 mins while I was on the road.
I finally just let phone sit for a while and it fixed itself. Man this is completely sporadic.
Click to expand...
Click to collapse
Yeah, mines been better for like 4 days, and then it just crashed and rebooted by itself earlier today.

has anyone gotten to the bottom of this yet? it seems to be a result of the play store system update being "stuck" on Sept 1st...even if you get it to download to the current version, currently March 1st, after a reboot it will not show the March update has been applied. And should it actually show that the March update has been applies, within a day the phone will reboot and the bluetooth bug will return, strangely the update to the play store system reverts to Sept 1st.
I'm having this issue with my son's phone. I tried unlocking the bootloader and flashing the factory img from April but of course the bug is still there, and after signing in the Play Store system is of course dated Sept 1st

There is no fix. I made an official Android Issue Tracker thread.
https://issuetracker.google.com/issues/151033055
and a Google Pixel Phone Help thread.
https://support.google.com/pixelphone/thread/32828289?hl=en
Google's being ****ty about it. I eventually just bought a new Pixel 4 XL. I needed a functional phone for school and work, and as much as I hate to spend money on another Google product after this mess, they do make the most powerful pure android phones with the best camera. Ebay FTW, $600, never giving them another penny directly.
If you still have warranty, get it warrantied immediately, and don't take no for an answer. I dawdled around thinking it would get fixed and even though I reported that I was having issues with it directly to Google's phone support BEFORE the warranty expired, by the time I called a second time and pushed a manager to see if they could warranty it, my warranty had expired so they told me to go jump in a lake.

to make it worse, Google told me the phone still has an extended warranty but I'm not the original owner and have no way to contact that individual. But you need that person's email address for it to work. So it was purchased but because of this technicality it's null and void. I get the security of it but it's still garbage

General December update woes...

The past few years, I usually install the ota manually on my pixels if they don't come right away on my phone (they usually do in CA). I keep my bootloader unlocked (just in case things go haywire) but haven't modified or rooted in many years. So today, because the update was so large (more reasoning below), I decided to flash the factory image and remove the "-w" command so it wouldn't wipe the phone. Done this many times.
So my usual process is to flash both slots one after the other. I flashed the current slot it was on (b) then switched to the (a) slot. Been doing the same since Android 4 (and A9 for a/b slots), hundreds of times. After flashing slot (a), it restarted like it's supposed to. I then get the dreaded "Your device is corrupt" message. First time I've seen this on any of my 4 Nexus and 5 Pixel phones. Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
Not sure what happened here. I don't think anything is wrong with the latest image. The reason I flashed this image was because I had a thought today - does flashing the "ota zip" update the bootloader and other firmware versions (they were different different versions this update). So I guess my curiosity killed the cat ... I should have just ran the ota first to see if the bootloader/radio versions updated, but of course the ota updates them (or they would never get updated otherwise). Ahh well. Now I will have to deal with the silly carrier warranty circus.
Also - I never thought an update could cause a phone to completely corrupt itself where it can't be fixed by the user. All of these posts on xda/red_dit etc over the years - I really didn't think it was possible. I always thought corruption must have been there before, but now I'm not so sure.
update: flashed the last build from November using flash.android.com and was able to get my system back. 2nd flash for that build worked.

Alekos said:
The past few years, I usually install the ota manually on my pixels if they don't come right away on my phone (they usually do in CA). I keep my bootloader unlocked (just in case things go haywire) but haven't modified or rooted in many years. So today, because the update was so large (more reasoning below), I decided to flash the factory image and remove the "-w" command so it wouldn't wipe the phone. Done this many times.
So my usual process is to flash both slots one after the other. I flashed the current slot it was on (b) then switched to the (a) slot. Been doing the same since Android 9, hundreds of times. After flashing slot (a), it restarted like it's supposed to. I then get the dreaded "Your device is corrupt" message. First time I've seen this on any of my 4 Nexus and 5 Pixel phones. Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
Not sure what happened here. I don't think anything is wrong with the latest image. The reason I flashed this image was because I had a thought today - does flashing the "ota zip" update the bootloader and other firmware versions (they were different different versions this update). So I guess my curiosity killed the cat ... I should have just ran the ota first to see if the bootloader/radio versions updated, but of course the ota updates them (or they would never get updated otherwise). Ahh well. Now I will have to deal with the silly carrier warranty circus.
Also - I never thought an update could cause a phone to completely corrupt itself where it can't be fixed by the user. All of these posts on xda/red_dit etc over the years - I really didn't think it was possible. Corruption must have been there before, but now I'm not so sure.
If anyone has any fastboot tricks - I'd try anything at this point.
Click to expand...
Click to collapse
All you got to do is go to the factory image page. Click on the Android flash tool and follow that it'll bring you back

mac796 said:
All you got to do is go to the factory image page. Click on the Android flash tool and follow that it'll bring you back
Click to expand...
Click to collapse
Not sure if I wasn't clear:
Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message.
I tried flashing 4 different Factory Image builds (flashing manually the Factory Image not ota). The android flash tool (webiste) completes but same message appears after it restarts.

Alekos said:
Not sure if I wasn't clear:
Okay so I decided to try flash it again, this time with the wipe command (recovery wouldn't work, same message). Flashing completes, same message. Then tried the flash.android.com - flashed all slots, wiped options on - same thing. The " pixelrepair.withgoogle.com " website doesn't recognize the phone which is odd because flash.android.com does. I tried flashing the original image from November and 2 other build versions. Still no go.
I tried flashing 4 different Factory Image builds. The android flash tool completes but same message appears after it restarts.
Click to expand...
Click to collapse
You're trying to flash with fastboot right? Use that Android flash tool. You'll see a link to it in the factory image page. I went through the same thing you did, I got the corrupt device. at the very end It'll ask you to Lock the bootloader just don't do it if you want to stay unlocked.

Oh maybe I misunderstood you tried that and it's not recognizing it

mac796 said:
Oh maybe I misunderstood you tried that and it's not recognizing it
Click to expand...
Click to collapse
flash.android.com recognizes it and it completes but the corrupt message still appears.
I'm going to try the original build from October, using the flash.android.com website - and pick all the Advanced Options, see how it goes (disable verity and verification, force debuggable and flash all partitions). I guess it's worth a try. pixelrepair website doesn't recognize the phone.

Alekos said:
flash.android.com recognizes it and it completes but the corrupt message still appears.
I'm going to try the original build from October, using the flash.android.com website - and pick all the Advanced Options, see how it goes (disable verity and verification, force debuggable and flash all partitions). I guess it's worth a try. pixelrepair website doesn't recognize the phone.
Click to expand...
Click to collapse
That's no good. Hope it works out. I had a hell of a time getting mine back too

mac796 said:
That's no good. Hope it works out. I had a hell of a time getting mine back too
Click to expand...
Click to collapse
ok what the hell. what a mess. it was weird, long-pressing the power button would never restart the device. it took multiple tries. I've learned over the years to remove the case because it can hinder the restart sequence. But even just getting into fastboot was difficult.
Anyhow it looks like I'm back.
2nd time flashing this exact image, but this time it worked - I used the flash tool website and flashed the November SD1A.210817.037 (non vzw build). I just chose options "All Partitions, and full wipe"(my next step was to try disabling verity and debugging but this worked).
a few reports on red_dit of corruption on the 6 Pros. hopefully Google pulls it soon. if people don't have the "oem unlocking" option enabled, their toast.

Alekos said:
ok what the hell. what a mess. it was weird, long-pressing the power button would never restart the device. it took multiple tries. I've learned over the years to remove the case because it can hinder the restart sequence. But even just getting into fastboot was difficult.
Anyhow it looks like I'm back.
2nd time flashing this exact image, but this time it worked - I used the flash tool website and flashed the November SD1A.210817.037 (non vzw build). I just chose options "All Partitions, and full wipe"(my next step was to try disabling verity and debugging but this worked).
Lots of reports on red_dit of corruption on the 6 Pros. hopefully Google pulls it soon. if people don't have the "oem unlocking" option enabled, their toast.
Click to expand...
Click to collapse
I'm glad you got out of it

I also had the pixel 6 pro briked when I put the root of the last base.
I have revived it by putting the ota december by sideload from recovery in the adb section

victoraran said:
I also had the pixel 6 pro briked when I put the root of the last base.
I have revived it by putting the ota december by sideload from recovery in the adb section
Click to expand...
Click to collapse
so if I didn't have "OEM unlocking" enabled - I'd have a brick right now. just actually trying to help someone else that also got the corruption message and can't get back into Android to enable oem unlock. Recovery doesn't work (like my situation).
What a mess...

That's what can happen when we're inpatient and not willing to wait for the right version to actually push to the device.

Battery life is awesome, still on 44% at half 10 at night from half 6 this morning

prohibido_por_la_ley said:
That's what can happen when we're inpatient and not willing to wait for the right version to actually push to the device.
Click to expand...
Click to collapse
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.

Alekos said:
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.
Click to expand...
Click to collapse
Well in the 4 years of me being on Android I've never had it happen.

I literally just got my Pixel 6 Pro and attempted the December update and got a firmware corrupt. The only options is try again or factory reset. I just finished going through the first time setup and already got this.

JodyBreeze901 said:
I literally just got my Pixel 6 Pro and attempted the December update and got a firmware corrupt. The only options is try again or factory reset. I just finished going through the first time setup and already got this.
Click to expand...
Click to collapse
same

Alekos said:
seriously? the right version? I installed the right version, and others also had the same issue just by updating normally through Android interface.
you shouldn't be able to "corrupt a system" just by updating to the official update build. this isn't 2012... anyway, I mostly posted and updated for others who might have had issues also.
Click to expand...
Click to collapse
Why not just adb sideload the OTA image, rather then flashing on both slots the factory image? It just sounds a bit of a hassle to me.
I know, I used to fastboot flash without -w my nexuses as well, but that was before the OTA images were available.

prohibido_por_la_ley said:
Well in the 4 years of me being on Android I've never had it happen.
Click to expand...
Click to collapse
yeah it's super rare. been flashing images and ota's since Nexus 4. But it happens.
I usually get the updates right away but sometimes I'll update the ota. I usually reflash the factory image every year after the beta. just seems odd how it corrupted the device. couldn't get into the system at all (or recovery/rescue modes).

yolandabecool said:
same
Click to expand...
Click to collapse
apparantly it has something to do with Bluetooth? I don't know how, but if you can get into safe mode and disable Bluetooth, clear cache/data for it and update all your google service apps, it can fix it (keeping Bluetooth off while restarting phone in regular mode) - but I couldn't load Android.
The trick to getting into Safe Mode is this: Turn off the device. Hold down power and and as soon as you see the "G" Logo, hold volume down. it will directly boot you to Safe mode. cool little trick. you'll have to manually enable wifi because it gets turned off.
At this point, if you can, enable OEM Unlocking. at least you'll be able to save the device if anything serious happens (like what I went through). the pixel repair website also works but I couldn't get into "Rescue Mode"

Question Screen issue or OS issue on Pixel 6 Pro?

Hello all,
Please help me to detect the exactly issue on my Pixel phone - Google Pixel 6 pro:
+) Somtimes my screen goes black, I press the power button and it still makes a sound - I mean it looks like still working).
+) But tp get it working again as normal, the only way is to press and hold the power button in 30 seconds to reboot.
+) A my friend said that it was due to the current version software? But I am not sure, please help to detect exactly reason at here.
I attached the video about the issue and the picture about the current version sofware.
Appriciate alls.

I don't have much to say that can help. I just wanted to mention that my wife and I haven't had this issue in the 3 1/2 months we've had our P6Ps, including on this latest update (same as the version you're on).
There are several things you can try to see if it'll help.
A Factory Reset, or if you're going to do that anyway, might as well try Official Google Android Flash Tool with having the option chosen to do a full wipe and flash all partitions. With any luck, the issue would be solved. I would be careful about what apps you reinstall after resetting or reflashing, although I wouldn't expect any particular app to be the culprit, but this should be ruled out.
I am assuming your phone isn't rooted, or even have the bootloader unlocked. For Official Google Android Flash Tool, OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own.

roirraW edor ehT said:
I don't have much to say that can help. I just wanted to mention that my wife and I haven't had this issue in the 3 1/2 months we've had our P6Ps, including on this latest update (same as the version you're on).
There are several things you can try to see if it'll help.
A Factory Reset, or if you're going to do that anyway, might as well try Official Google Android Flash Tool with having the option chosen to do a full wipe and flash all partitions. With any luck, the issue would be solved. I would be careful about what apps you reinstall after resetting or reflashing, although I wouldn't expect any particular app to be the culprit, but this should be ruled out.
I am assuming your phone isn't rooted, or even have the bootloader unlocked. For Official Google Android Flash Tool, OEM Unlocking needs to be toggled on - you may not have to manually unlock the bootloader - the "site" will do that on its own.
Click to expand...
Click to collapse
Many thanks for your response, I tried flash to factory image sq1d.220105.007 last night yesterday. I will not try update, install some needed apps and continue monitor to see if it repeats or not? I will get back to you if need help anymore. Tks again.

hichichachac said:
Many thanks for your response, I tried flash to factory image sq1d.220105.007 last night yesterday. I will not try update, install some needed apps and continue monitor to see if it repeats or not? I will get back to you if need help anymore. Tks again.
Click to expand...
Click to collapse
Good luck! I hope it helps.