General Play-systemupdate 20220106 - Google Pixel 6 Pro

Just received an update to Security Hub via Playstore and a tad later a Play-systemupdate (3.9 MB).
After reboot, the Play-systemupdate date still shows December 1, 2021.
However, I noticed that the following package was updated:
Code:
BEFORE UPDATE:
com.google.android.modulemetadata 2021-12-01S+ (311234004)
AFTER UPDATE:
com.google.android.modulemetadata 2021-12-01S+ (311235004)

Just checked and I got the same.

My security patch still shows October, it use to say december
Edit: now that I checked again it's on to November now, weird

Mine shows the update is November.

Mine says Nov

Matterhorn said:
Mine shows the update is November.
Click to expand...
Click to collapse
There were some reports of people (when the December play systemupdate was released) that updated (manual push), but the version didn't change (stayed on November). It was unclear back then if people "succesfully" upgraded, meaning it was just a display error, or if the update process failed for no error reason given.
So it might very well be that you are already on the December update.

Installes the first smaller one and got offered a larger second one (~50mb IIRC). After abother reboot, Google Play system Update sais Dec 1st 2021.

any ramifications of this? I saw the update in the playstore too

I have a security update of Dec. 5th and Play System update of Nov. 1st. I've also tried several times to update again.

I just checked my Playstore Systemupdate.
I was on December 1 patch - when I clicked on it, I was told a restart was needed to install the most recent update. Now I installed that update, and I am still on December 1. Odd.

Ever since I accidentally factory reset a few weeks back, I've been on the November Play System update, and still am with no updates available. Running on the December stock rooted firmware on the factory unlocked P6P.

Seems as if Google is rolling out the December update to those who were stuck on October. May be related to that in some way. I have been on December and got and update yesterday that put me on, well, December . I wonder if sometimes they just update a module or two without updating to a full new month because this happens often it seems to many people.
[Dec. update out] Google Play system update stuck for some devices
Some Google Pixel users (other devices too) are stuck on an older Google Play system update and issue has been escalated.
piunikaweb.com

Related

Google pixel XL patch 5 January 2017 update

Hi,
I have a Google pixel XL phone.
I installed the patch on January 5, 2017. After installing patch is alright, as long as the second restart interlock phone the patch is uninstalled, returning to the patch of 5 December 2016. I tried to do a hard reset, but I noticed that the patch is installed and after a restart interlock you uninstall always returning to the patch in December 2016. There has also happened to you? thank you
Perhaps a bad flash? Have you tried flashing the entire factory image manually again?
I'm not following.
ttminh1997 said:
Perhaps a bad flash? Have you tried flashing the entire factory image manually again?
Click to expand...
Click to collapse
No.
I installed the new patch with OTA update. Installing and after the restart interlock for the second or third time you uninstall and return to the old patch. Then I have to re-install and makes me repeat the procedure
Tfilosofo said:
No.
I installed the new patch with OTA update. Installing and after the restart interlock for the second or third time you uninstall and return to the old patch. Then I have to re-install and makes me repeat the procedure
Click to expand...
Click to collapse
Sorry for this dumb question, but what's a "restart interlock"?
ttminh1997 said:
Sorry for this dumb question, but what's a "restart interlock"?
Click to expand...
Click to collapse
I badly explained myself. I installed the patch of January 2015 but after turning on the phone, the patch is unistalled and to return the patch of December. I have an import google pixel xl, it is English but I am using it in Italy.
I do not understand why the patch of January unistalled and return the patch of December 2016
So you're saying you took the January OTA but when the phone rebooted you checked and it looks like it never actually updated?
Sent from my Pixel XL using XDA-Developers Legacy app
it is updated to the phone patch in January 2017, but after the third restart, the update is lost and returns to the patch in December 2016. So endlessly, always reinstall the patch January 2017 update.
Tfilosofo said:
it is updated to the phone patch in January 2017, but after the third restart, the update is lost and returns to the patch in December 2016. So endlessly, always reinstall the patch January 2017 update.
Click to expand...
Click to collapse
Sounds like it booted into the other slot

its october, still dont have september update

so its october 12th, and i still dont have the september update, let alone the october update.
magisk/twrp installed
opted into the beta and back out to try to refresh some kind of hidden cache or something, no luck
going to manually install via pc, but id like to know potential reasons this would happen and how to resolve it so i can do the november one using the magisk method from their github
system update says up to date with august 5th patch installed
EDIT: please move to pixel 2 forum (although same info still applies)
If you are rooted you can't receive OTA, you must sideload it.
Did you sign up for the Android Pie beta testing programme? I was still signed up on my Pixel 2 XL and wasn't getting the update too until I left the programme.
The same happened to my friend's 2xl. I ended up sideloading the ota for him however one of my relatives was complaining as well. No ota notification popped up for her. No root, no custom recovery, full stock. She factory reset the phone and the update notification immediately popped up at the first boot. In the past it worked and triggered the ota update if you force stopped Google services framework and cleared cache and data. I don't know it it works now. Anyway, sideload the update and hopefully next month it will work again or try a factory reset if your device is stock with no root.
dj_ooms said:
Did you sign up for the Android Pie beta testing programme? I was still signed up on my Pixel 2 XL and wasn't getting the update too until I left the programme.
Click to expand...
Click to collapse
I was not in the beta program. I did sign up yesterday and immediately leave it, thinking maybe that would force some kind of hidden cache to be cleared. No luck.
siggey said:
If you are rooted you can't receive OTA, you must sideload it.
Click to expand...
Click to collapse
This is not true. I've always gotten the notifications until these past 2 months. There is now a way to get the ota without side loading, and it worked on our other one, I just wasn't getting the notifications on mine.
I was in the pie beta program and once the official release came out I got the monthly update in September. However, I still haven't gotten the October one which is weird. Guess I shouldn't really care since I have the 3 coming soon anyway.
Ive always had the notification of the update when rooted on this phone.

Google Play system update

Anyone have the Google Play system update on Dec. 2020 on their 5G?
I've been able to get the update, install and reboot. However, after reboot the phone reboots itself again after a minute or so and reverts back to the Oct. 2020 update.
Anyone else?
No one?
January update doesn't stick either..
I have this issue also. Mine will update but revert back to the Feb 2020 version after about 1-2 minutes.
vrman said:
I have this issue also. Mine will update but revert back to the Feb 2020 version after about 1-2 minutes.
Click to expand...
Click to collapse
Thanks for the response.
It had been working fine for me until the latest system update (NA v.8.11).
In any case, I've been able to overcome it by sideloading the .apk(s). I installed the Dec. 2020 .apk and then tried to auto update to Jan. 2021 - same issue, but it would revert back to the Dec. 2020 update instead. Sideloaded the Jan. 2021 update as well and all is fine - now to see what happens when the Feb. update releases (or if we get a system update before then).
If you want to sideloaded the .apk as well, check this XDA thread. (although this .apk might only be changing the date displayed. ).
An Droid said:
Thanks for the response.
It had been working fine for me until the latest system update (NA v.8.11).
In any case, I've been able to overcome it by sideloading the .apk(s). I installed the Dec. 2020 .apk and then tried to auto update to Jan. 2021 - same issue, but it would revert back to the Dec. 2020 update instead. Sideloaded the Jan. 2021 update as well and all is fine - now to see what happens when the Feb. update releases (or if we get a system update before then).
If you want to sideloaded the .apk as well, check this XDA thread. (although this .apk might only be changing the date displayed. ☹ ).
Click to expand...
Click to collapse
Good info, Thank you. I'll side load if the next update doesn't resolve it or we go into March without an update.
Just for reference, my RM5G was purchased as a new EU model. I let it go thru 2/3 EU updates until it was ready for EU V714(Latest) and then downloaded and flashed it to NA V811(Latest) instead. Since I updated with a clean device, no setup or account sign-ins until V811, looks the the Google play system version never updated past that initial shipped version (Feb 2020) and as you said V811 probably broke it.
vrman said:
Good info, Thank you. I'll side load if the next update doesn't resolve it or we go into March without an update.
Just for reference, my RM5G was purchased as a new EU model. I let it go thru 2/3 EU updates until it was ready for EU V714(Latest) and then downloaded and flashed it to NA V811(Latest) instead. Since I updated with a clean device, no setup or account sign-ins until V811, looks the the Google play system version never updated past that initial shipped version (Feb 2020) and as you said V811 probably broke it.
Click to expand...
Click to collapse
I don't know if the Google Play system update is included as part of the rom - from your experience, it doesn't sound like it.
I unzipped the .apk and didn't see any significant content in it - I think it is only updating the date displayed without providing any of the actual update content. Furthermore, it can't be uninstalled or rolled back, so I no longer recommend using it.
Wait and see for now for me...
My RM 5G did update today to the January 1st 2021 version and has yet to reboot or default back. Maybe they got it sorted.
vrman said:
My RM 5G did update today to the January 1st 2021 version and has yet to reboot or default back. Maybe they got it sorted.
Click to expand...
Click to collapse
Good to hear - did you get/install the latest rom update first (v.8.12 or v.7.15)?
An Droid said:
Good to hear - did you get/install the latest rom update first (v.8.12 or v.7.15)?
Click to expand...
Click to collapse
No update yet, I am still on v8.11
Okay, my phone updated to v8.12. After the SW update it reverted back to the February 2020 Play System version within about 5min. I manually updated to January 2021 version after about 4hrs and it has stayed for >24hrs.
We'll see how it goes.
Mine updated and rolled back aswell
Mine is currently stuck on always wanting to restart after checking for updates - even after restarting.
It had updated to the Feb. 2021 patch, but again rebooted on its own and reverted back to Jan. 2021... Since then stuck on the restart prompt.
Mine is also not consistent. It'll stay updated on Feb 2021 version for random day(s) up to a ~week and then just reboot and revert back to Feb 2020 version. I am tracking app updates to see if something triggers it.
Just got a Play Store update (tap on the version number in the Play Store settings) and was able to download/install the Feb. 2021 update and reboot. Rebooted again for good measure and sticking so far...
The Aug. 2021 update seems to have stuck on my phone now after being stuck on April 2021 - no double boot either on a reboot.

Question Google Play System Update

Just set up a NA Red Magic 6 - seems to have a similar issue the RM5G has with Google Play System Updates under the security settings - it won't update past Oct. 2020.
It'll download the update and prompt to reboot. Looks like it reboots twice and is back on the Oct. 2020 update instead.
Anyone else?
The same issue. Rmg6
Do you mean the google play store version? mine is ok everything update.
virus2977 said:
Do you mean the google play store version? mine is ok everything update.
Click to expand...
Click to collapse
No - under settings > security you'll see Google Play system update. This is updated monthly (current update is April 2021) - the RM6 is on Oct. 2020 and attempts to update it fail as described.
Ok. Same cant update. still stick to oct 2020.
Just like my RM5G, my spouse's RM6 finally got the Aug. 2021 update to stick. No double boot on a reboot either. Hope this continues with the Sept. update once it's pushed out.
Suggests this is a Google issue (signing/verification perhaps?)
Having this issue with my RM6S Pro. Stuck at October 2020. Should I be concerned?

Question Spontaneous reboot and rollback of 9.9MB Google System Play Update

On manually installing Google Play System Updates, I encounter problems.
I am on the April Android Security Update and also the April Google Play System Update (and no rooting or custom ROMs).
But there are still 2 Google Play System Updates waiting, one of 9.9MB and one of about 700KB that comes after that.
But after installating the 9.9MB patch, my phone will spontaneously reboot within one minute of starting the phone.
Not every time, I have sometimes rebooted my phone succesfully after installing the patch, and installed the second patch. But always after a couple of phone reboots, my phone will suddenly reboot after restarting the phone.
And when that happens (and only then), the 9.9MB patch is waiting for me again, so apparently it is rolled back when that happens.
I have found at least four forum threads online in different languages of people having the same problem, but I actually thought it would have more coverage.
(I have submitted a bug report with Samsung, previously they were quick to respond when I filed a bug report, but not this time)
I have noticed exactly the same issue. I haven't noticed the 700KB update. When I apply the 9.9MB April update, and reboot, the phone restarts itself before I can do anything else.
Sitting on the March Google Play System update, the phone seems to be working OK otherwise.
The May system update (so not the google play system update) appears to have fixed this issue. I am now fully up to date with patches for both system update (May) en google play system update (April), and could manually reboot 5 times without issue.

Categories

Resources