I just got Pixel XL few days ago with Feb, 2019 Security Patch. And I neither couldn't update my phone via OTA nor install any apps on Google Play. Then I have HARD WIPED my phone by using STOCK RECOVERY, and it did work. But I was still stuck in Feb, 2019 Security Patch!!!
Then I have patched FACTORY IMAGE of XL "9.0.0 (PQ2A.190405.003, Apr 2019)". And yes, I finally got the lastest security patch but the same issue was back. I CAN'T UPDATE MY APPS ON GOOGLE PLAY, AGAIN!
I tried to solve this problem by installing PixelDust thru TWRP, but can't get rid of this...
Please help!!!
I did try to do all the possible tricks with Google Play and Google Play Services... But I didn't work out
Related
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
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.
Hello guys
this monrning i had a popup of googleplay service ota installed, i opened magisk manager installed it after ota , reboot device and now im stuck on boot with the logo , I have too many important files of my job in the phone that i cannot lost, i will appreciate any help if somebody could help me fiix it without format it, i promise a donation for who will help me without format it! Thanks in advance!
you have made a Google play system update and not an ota firmware update. after the google play system update you do not need to go to the magisk manager and flash magiks in the inactive slot you can only do this after an ota firmware update. but since you did this with the google update, you switched from the active slot to the inactive slot, you have to switch to the other slot by fastboot, then the box should boot again.
I flashed twrp and flashed again the Rom and fixed it
I guess you have a custom rom?
ChrisFeiveel84 said:
you have made a Google play system update and not an ota firmware update. after the google play system update you do not need to go to the magisk manager and flash magiks in the inactive slot you can only do this after an ota firmware update. but since you did this with the google update, you switched from the active slot to the inactive slot, you have to switch to the other slot by fastboot, then the box should boot again.
Click to expand...
Click to collapse
Just wanted to say THANK YOU for posting this answer!
If anyone's reading this because you got a bootloop due to a Google Play Services update, this could be the reason why. I was soft-bricked because Google Play Services decided to push an update to the latest version even though I intentionally did not update my Pixel 3 firmware to the latest build (wanted to stay on Android 10 but update for was for 11).
If this is you, and you have an unlocked bootloader, go ahead and OTA to the latest firmware (be sure to remove the "-w" flag in the flash-all.bat file to prevent a data wipe!). The bootloop will fix and you'll be able to boot correctly. You'll have to re-flash Magisk again, but at least you'll be able to recover your files.
JeffXT said:
Just wanted to say THANK YOU for posting this answer!
If anyone's reading this because you got a bootloop due to a Google Play Services update, this could be the reason why. I was soft-bricked because Google Play Services decided to push an update to the latest version even though I intentionally did not update my Pixel 3 firmware to the latest build (wanted to stay on Android 10 but update for was for 11).
If this is you, and you have an unlocked bootloader, go ahead and OTA to the latest firmware (be sure to remove the "-w" flag in the flash-all.bat file to prevent a data wipe!). The bootloop will fix and you'll be able to boot correctly. You'll have to re-flash Magisk again, but at least you'll be able to recover your files.
Click to expand...
Click to collapse
Hey! This was what happened to me this evening. My dad's phone suddenly bootlooped again and again. Initially, I thought that a factory reset could solve this. Did that and after reinstalling everything the same thing happened again. Found out that this only happened after I updated google play services. Is there any way I could download 'not' the latest version of google play services?
EDIT: After a factory reset I downloaded a previous version of Google Play services and the bootloop was fixed. Thought I could share this here so that others could be helped. Maybe the latest version (23 Feb 2022) was not compatible with the phone. But does anyone know any workaround so that I could download the latest version of Google Play services?
EDIT EDIT: Today, 25 Feb 2022, the phone was stuck on boot again. Found out that Google decided to force push an update to Google Play service (ver. 22.02.21). I was able to reboot the phone into lock screen and turned on airplane mode. The phone is working fine on airplane mode but as soon as I turned it off, the same thing happened again. Really frustrated with this incompatibility between the phone and Google's services.
masymereJ said:
Hey! This was what happened to me this evening. My dad's phone suddenly bootlooped again and again. Initially, I thought that a factory reset could solve this. Did that and after reinstalling everything the same thing happened again. Found out that this only happened after I updated google play services. Is there any way I could download 'not' the latest version of google play services?
EDIT: After a factory reset I downloaded a previous version of Google Play services and the bootloop was fixed. Thought I could share this here so that others could be helped. Maybe the latest version (23 Feb 2022) was not compatible with the phone. But does anyone know any workaround so that I could download the latest version of Google Play services?
EDIT EDIT: Today, 25 Feb 2022, the phone was stuck on boot again. Found out that Google decided to force push an update to Google Play service (ver. 22.02.21). I was able to reboot the phone into lock screen and turned on airplane mode. The phone is working fine on airplane mode but as soon as I turned it off, the same thing happened again. Really frustrated with this incompatibility between the phone and Google's services.
Click to expand...
Click to collapse
I have the same problem here, after google play service auto-update to version 22.x, my phone bootloop. Are you have found a solution for this?
Download another Google play services apk for your android 10 or 11 or 12 from apkmirror and install
HueyT said:
Download another Google play services apk for your android 10 or 11 or 12 from apkmirror and install
Click to expand...
Click to collapse
thanks for your response, but I've done it many times. I have downloaded google play ver 21.x, disabled auto-update, and disabled internet permission, but it always forces update to 22.x when I'm going to install or update some application. I'm very stuck with this incompatibility, are you have another solution?
dwickycandralesmana said:
thanks for your response, but I've done it many times. I have downloaded google play ver 21.x, disabled auto-update, and disabled internet permission, but it always forces update to 22.x when I'm going to install or update some application. I'm very stuck with this incompatibility, are you have another solution?
Click to expand...
Click to collapse
Google Play services 22.06.15 (150408-428792003) (150408) APK Download by Google LLC - APKMirror
Google Play services 22.06.15 (150408-428792003) (150408) APK Download by Google LLC - APKMirror Free and safe Android APK downloads
www.apkmirror.com
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?
I flashed my Verizon s21 fe to the unlocked firmware and by default had the Google play system update from Sept 2021. Everytime after I try to update it after rebooting I see it's on may 2022 but then the phone crashes, says I have Sept 2021, I update rinse and repeat. I've tried downloading the update from apkmirror and still have this problem. Safe mode, using another Google account, and erasing the app cache doesn't help either. Does anyone know what to do i'd appreciate any help.