Android 10 - Factory reset needed? - Google Pixel 3 XL Questions & Answers

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.

Related

Nvidia Experience 5.2 ROM

I have not been able to update my shield tv 2015 16gb device to 5.2.
The device is rooted with latest 3.1.1 TWRP recovery. Each time I select upgrade with the stock settings it will reboot into recovery and won't update.
Does anyone have a link to the latest ROM or know where Nvidia stores the OTA file? I would rather flash the image my self if I can find get the ROM.
I'm sure this we'll help a few other people I can't be the only one with this issue. Need the 5.2 image not the 5.0.2 which is the previous version of Shield experience update.
you should not flash TWRP to your device reflash original recovery and remove su then try update again
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
.)
Click to expand...
Click to collapse
i didnt know that :good:
but if he has TWRP installed couldnt he format data pation from TWRP thus saving hours of thumb twiddling
Ichijoe said:
BTDTGTTS Simply unrooting, and replacing TWRP with a Stock Recovery. Will not sadly be enough. The only way out is to Factory Reset. Which, in my case (Pro Owner), means a Two Hours of down time. While the Shield is busy away at nuking the /data Partition. Only after that will you be fully unrooted. Of course if you are using TWRP as your Recovery, you WILL have to replace it with a Stock Recovery for your Update to work.
It's a real PItA for just some extra (Non-working) Plex Channels, and making the needed edits to settings.db to prevent it from kicking iPlayer off after each Power Cycle / IP Address reset. (Though that last one... Has more legs on it then just the Plex Channels.)
Click to expand...
Click to collapse
Obviously thats a much longer and worse route.
afgok said:
you should not flash TWRP to your device reflash original recovery and remove su then try update again
Click to expand...
Click to collapse
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
On another thread looks like others are having this same issue with only this version 5.2.. ill just wait for the Dev Images to show up hopefully soon.
I unrooted but still got the same issue, it wont install. But I also have another issue, i can't restore my 2015 shield 16gb by using official recovery rom and official tutorials. It consistently fails to flash system.img and vendor.img by saying that the data is too large. The only way I got my system back was by flashing this file https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062 through twrp
Diehardshorty said:
Obviously thats a much longer and worse route.
I have upgraded the shield tv many times with OTA updates. Shouldn't need to be stock just to do this. So your saying root has more restrictions....
TWRP is much better than stock recovery, now it might not be finding the OTA update when it gets pushed to recovery.
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Ichijoe said:
Again TWRP can not be used to flash an OTA Update. I mean sure feel free to knock yourself out. But, in the end it will fail. (Error 7 IIRC), As it is it seems that it will only work on a stock Recovery, and not on TWRP. I mean if it were this easy, everyone would be doing it. And again if the Update were working over TWRP, we wouldn't have a constant update loop. (e.g. Download Update, restart Shield, wait forever for the Shield to try (and, fail!) at applying said Update, rebooting, and wash rinse, repeat).
BTW: I never said that my way* was the 'best' way, or indeed the 'only' way. Its just the only way I know of to Nuke it from orbit all the time, everytime. And, yes it is a huge PITA. If you count a /system root as being more restrictive. In the case of Netflix making active noises about blocking rooted Devices. Then yes slowly I would say that rooting has more restrictions than stock.
*My way being to Factory wipe the Shield (Pro) which in the case of the Pro most likely means a Two plus Hours of dead time. I would assume it's much MUCH quicker for our 16GB eMMC Cousins though. But, not having One, I'm unable to confirm it.
P.s. You have also mentioned the fact that you have managed to update your rooted Shield TV on multiple occasions. Would you care to share this info with us? I for One would love to know how to do this. As having to Factory Reset the Device is a real time waster. Because after the reset, comes the rebuild. And, thats an even bigger *****.
Click to expand...
Click to collapse
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
If you're rooted, the right answer is to wait for Nvidia to release the 5.2 image.
If you absolutely need 5.2 right now for some reason, several people said that doing a factory restore worked. Just unrooting and restoring stock recovery won't do it, you need to do a full restore.
Diehardshorty said:
Dirty flashing a dev image is they way I have managed to update my shield but right now the dev images are not updated, still the 5.1.0
Click to expand...
Click to collapse
The Dev images are quite a bit different, and are also on an entirely different timeline to either the Preview, (Which I'm on), or the most current version.
But, yeah I could see how those would work. Alas mores the pitty that the rooted asspects of those Dev Images, only go as far as ADB, and not say a full /system wide root. Than again... It's probably for the best that way.
But, that doesn't really change the answer if you want / need to update (From root), than you are going to have to bite the big One, and run a Factory Reset. Which again, on the Pro, means a 2h+ reformating (zeroing out), of the /data Partition.
16gb version doesn't take as long to format but I've always remember flashing SuperSU.zip after ROM just incase. Short response for now at work.
Diehardshorty said:
The other option I mentioned in the original post was for manually selecting the OTA image with TWRP and flashing.
Does anyone one know where the temp folder is for OTA files or a direct link online?
Click to expand...
Click to collapse
Use to be here:
/data/data/com.nvidia.ota/app_download
You obviously need root to reach that folder...
If i have time i will upload later this small OTA update to MEGA.
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
sammarbella said:
I uploaded the 5.2 small update OTA for Shield TV 2015 (NON-PRO):
https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-small-update-ota-5-2-t3621886
Click to expand...
Click to collapse
Sweet thanks I'll give that a try from the sounds of it it might not work but I'll give a shot after work. Thanks
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Diehardshorty said:
No luck flashing my own OTA zip I took it out of data\data\com.nvidia.ota flashed it with TWRT 3.1.1.
I might end up doing the factory restore then updating and root. Wouldn't mind a new clean OS
Click to expand...
Click to collapse
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Cameron581 said:
Check out https://forum.xda-developers.com/shield-tv/general/how-to-update-ota-5-2-2017-update-t3622540 just posted a guide on how to update
Click to expand...
Click to collapse
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Diehardshorty said:
Only difference there is that your using flashfire instead of TWRP. I can't see how that may work but worth a shot.
Click to expand...
Click to collapse
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Cameron581 said:
Just make sure you flash the right update, and it's because the ota provided by the devs don't support ota due to device fingerprint issues along with partition finding stuff found inside the meta-inf, the reason you can't sideload the room via stock is because there is a check for modified system tables. Granted you could take out that comment and rezip it then it will fail for zip verification, after that I had tried to sign the package to regain that but then it failed due to it only signed the packages not the entire system. Long story short it's super duper picky and ChainFire made one that pleases all of the variables or ignores then.
Click to expand...
Click to collapse
Ahhhhh that missing point for "error 7".
So the new app bypass that problem!
Thanks for posting it. :good:

8.1 OTA reset my tablet

This morning I received the Android 8.1 OTA, it took over an hour to process and when it had finished my tablet had been wiped.
Not happy!
Hi same thing happened to me . I called Google up and they gave me a useless answer.
All I can say to others is do not update to 8.1 just yet or back up your data.
Did you by any chance have your bootloader unlocked?
Bhushan8128 said:
Did you by any chance have your bootloader unlocked?
Click to expand...
Click to collapse
I can't remember, it's possible...
Reset for me, and bootloader is NOT unlocked for either device we have (at least I was the first to take the update, so can plan for my girlfriend). Didn't expect this. Especially after the update to 8.0 left things alone. I had JUST started to install apps with data (long time flasher... left these stock, so I tend to avoid non-cloud apps, especially without root backup options).
Wish I'd come on here half an hour ago. Just got the notification about the update and has wiped mine as well.
Sent from my Pixel 2 using Tapatalk
Same here. Just did the OTA. Basically new tablet, never unlocked the bootloader etc..
Interestingly I could not initialize the tablet as new device.
The error I got was that the device was resetted and only the previous owner can go on with the setup (something like this).
I logged into my Google account and now my Pixel C is loading the backup.
But I highly doubled that many of my apps settings were backuped.
In the same boat. Jumped straight into the OTA when prompted, ended up with factory reset and all internal storage wiped. Stock ROM, only thing possible unusual we that when I first went to install it complained I didn't have free space. Fixed that and tried again, ended up reset and wiped.
with my Pixel C it is looping between "Google" and "erasing" and getting no further
Got the OTA update too and it wiped my device, good thing I just brought it so had nothing on it
Amazingly incompetent - who do they think they are - Apple?!
TimSharrock said:
with my Pixel C it is looping between "Google" and "erasing" and getting no further
Click to expand...
Click to collapse
I tried factory reset, and it seemed to make no difference, but I left it looping for several more hours, and it eventually booted into a wiped state. I reconnected it to my account, and is now merrily reinstalling everything from the backup
I just updated with adb sideload and full OTA Image. No wipe for me.
Apparently this is now fixed, time will tell.
https://productforums.google.com/forum/#!topic/nexus/rwWqnT_397c

Pixel XL 1 not getting OTA Updates

Hi,
am using a Pixel XL 1 on Android 8.1, bootloader unlocked, patch level of February. Now I have the problem that since about December no OTA updates are shown/offered at all. Therefor I always had to manually update.
Even the manual triggering of searching for updates, which has recently been changed so that the devices explicitly should get the currently available update, does not work.
The device was rooted, but I have unrooted it (Magisk) now, and is running the standard firmware from Feburar on it.
Does anyone have any clue why my device is not offered any OTA updates?
Anyone?
What kind of recovery do you have installed? Stock or TWRP?
Kream24 said:
What kind of recovery do you have installed? Stock or TWRP?
Click to expand...
Click to collapse
Stock. So everything should be as vanilla as possible! I'm really clueless.
i don't get it either. pixels running a non-stock os should get notifications about a new update. they won't install successfully though. i'm guessing, but maybe going through the unroot process to get rid of magisk did not return your os to completely stock. maybe some junk was left behind and that's causing your issue.
my suggestion is to flash a full factory image to start fresh. i would edit the flash-all.bat script to remove the -w option to keep data. if that doesn't work, put the -w option back and rerun to wipe data and flash the factory image. if you really want to see if that fixes your problem, flash an older image like the february or january one, and see if the update notification comes back. or flash the march image to be up to date and wait until april to see if you get the update notification.
altwu said:
i don't get it either. pixels running a non-stock os should get notifications about a new update. they won't install successfully though. i'm guessing, but maybe going through the unroot process to get rid of magisk did not return your os to completely stock. maybe some junk was left behind and that's causing your issue.
my suggestion is to flash a full factory image to start fresh. i would edit the flash-all.bat script to remove the -w option to keep data.
Click to expand...
Click to collapse
That's what I've did already No difference.
if that doesn't work, put the -w option back and rerun to wipe data and flash the factory image.
Click to expand...
Click to collapse
It's just the hassle installing everything from scratch again.
I wish recovery/backup was as easy as on iOS. Without necessity of any tricks, root etc.
Is this phone enrolled in the Android Beta Program ? I've had trouble getting OTA updates on my phone after the beta program ended for it until I un-enrolled from the program, then I got updates like normal. There will be warnings about having to wipe the device, but if your on the the stock/stable version already you won't have to.
shaneledford said:
Is this phone enrolled in the Android Beta Program ? I've had trouble getting OTA updates on my phone after the beta program ended for it until I un-enrolled from the program, then I got updates like normal. There will be warnings about having to wipe the device, but if your on the the stock/stable version already you won't have to.
Click to expand...
Click to collapse
Tried that one as well. I was on a beta at some point, but unsubscribed from the beta. Also tried to unsubscribe again, but it the well know link took me to a page where it said that there is no beta, hence I couldn't try to unsubscribe again.
When you flashed the full factory image did you use the newest march update? if you did then you wouldnt get anything because you are already current
Gotta say, exactly the same problem.. stuck on 8.0 November lol. Haven't found a solution, too lazy to manually flash for now. Let me know if you find a solution!
have you tried deleting the data and cache on the google services app?

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 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!

Categories

Resources