[MODULE] Google Play Services "Incompatible" Fix for Lenovo Vibe K5 (and maybe more!)
Not a long ago, my devices Lenovo Vibe K5 is blocked to update Google Play Services. What i mean is blocked is that all of my device user (K5 and K5+) can't update Google Play Services with error message "Your device is not compatible with this version" both on stock rom and custom rom.
So, i started experimenting and made this module.
How does it work?
1. It clear data for Google Play Services and Google Play Store
2. Then change device prop using magisk system.prop
How to install?
1. Download zip file from Magisk, it's called "Google Play Services Fix for Lenovo Vibe K5" or from here
2. Install the module
3. Reboot immediately after module installed
This module is specifically made for my device, but other devices can try it too. But in note that your device model on "About phone" will changed to my device.
Special thanks to @topjohnwu for creating magisk
Reserved for updates
Hi, thanks for the module. I'm trying to use it so that I can update apps like Netflix on the Play Store. I installed on a Oneplus One (bacon), running TugaPower's Nougat 7.1 ROM with systemless Xposed. After a number of reboots the play store still shows that Netflix is not compatible with the device. I disabled the Xposed module and cleared data for Google Play Services and Google Services Framework. Magisk shows that I am passing SafetyNet, Google Play is showing the device is certified and your module seems to work as my device shows as yours in system settings/about. Still no luck with Netflix, I am preparing to give up so any advice is welcome Did you manage to use Netflix through the Play Store with this module?
JoroBo said:
Hi, thanks for the module. I'm trying to use it so that I can update apps like Netflix on the Play Store. I installed on a Oneplus One (bacon), running TugaPower's Nougat 7.1 ROM with systemless Xposed. After a number of reboots the play store still shows that Netflix is not compatible with the device. I disabled the Xposed module and cleared data for Google Play Services and Google Services Framework. Magisk shows that I am passing SafetyNet, Google Play is showing the device is certified and your module seems to work as my device shows as yours in system settings/about. Still no luck with Netflix, I am preparing to give up so any advice is welcome Did you manage to use Netflix through the Play Store with this module?
Click to expand...
Click to collapse
for that, try to clean install your ROM.
first, you install ROM+Gapps. then boot to system and login. look at the netflix see if its there or not.
then you can install magisk etc. that trick always stay me away from many problems about play store
Finally unlocked bootloader and installed HavocOS to my Xiaomi with all needed wipes: data, system, cache. However, I've faced an issue with Play Market downloads. When I try to download a large app it goes up to 100% and then starts over, stops at 2% and awaits for wi-fi connection ( though I am connected over Wi-Fi). It is the same for all apps over 1Gb in size (e.g. PUBG, Asphalt 9 and so on). Also tried to clear cache and data for Play Market, Google Play Services and no good too.
I've tried to reinstall ROM, gapps, tried Xiaomi EU Rom (stable) and got the same error there. I guess it has something to do with security, so I've tried different google account - but result was the same.
Please suggest any resolution
Just bought this phone myself. But this my guess based on my experience with other devices.
I suspect that your play store status is uncertified?
I am sure it is!
You need to fix that first, then play store function should return to normal.
The easiest way to resolve this issue without reinstallation to use the Magisk Module : Magiskhide Props Config
Next go to the main page for that module and read the instructions ( Google it)
Note, you must also install Termus and enter commands per instructions on Op page for the module. Trust me it's easy.
Essentially you are changing the fingerprints to a Play Store certified device (It only works as long as the module and Magisk stays installed)
I have attached screenshots from my other phone, where I had the same issue and resolved it.
Sent from my Xiaomi MI 8 using XDA Labs
I have been using Google Pay on my Galaxy S8 (SM-G950F) for year with Magisk, I was still able to use Google Pay no problem on Feb 28. I noticed on March 1 when I try pay with Google Pay I got message saying "You can no longer pay in stores with Google Pay". I checked Magisk to make sure it still pass SafetyNet and check was success yet I try to add the credit card again on Google Pay I got message "Couldn't finish setup to pay in stores - This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way.
henban89 said:
I have been using Google Pay on my Galaxy S8 (SM-G950F) for year with Magisk, I was still able to use Google Pay no problem on Feb 28. I noticed on March 1 when I try pay with Google Pay I got message saying "You can no longer pay in stores with Google Pay". I checked Magisk to make sure it still pass SafetyNet and check was success yet I try to add the credit card again on Google Pay I got message "Couldn't finish setup to pay in stores - This phone can't be used to pay in stores. This may be because it is rooted or altered in some other way.
Click to expand...
Click to collapse
I am getting this error too. Working fine until a few days ago. SafetyNet reports all true, Magisk Hide set to Google Pay, Play, etc.
The same on my Galaxy S5
Same here on my OnePlus 6t
Same with my xiaomi 6, magisk 18.1 + manager 7.0. Safetynet is passed
same with my note-9 using bank applications as magisk failed to hide root
No one mentions what ROM they are using
fwiw Google Play works fine on My Note 4 with unofficial LOS 16 (Pie) and Magisk 18.1
Used it last 2 hours ago...
Google Pay never worked on the previous LOS 15.1 (Oreo) on ANY build/version of Magisk, it was a ROM issue.....only worked on stock ROM for the Note 4
So i got quite the surprise when i flashed Pie and it was workies....
73sydney said:
No one mentions what ROM they are using
fwiw Google Play works fine on My Note 4 with unofficial LOS 16 (Pie) and Magisk 18.1
Used it last 2 hours ago...
Google Pay never worked on the previous LOS 15.1 (Oreo) on ANY build/version of Magisk, it was a ROM issue.....only worked on stock ROM for the Note 4
So i got quite the surprise when i flashed Pie and it was workies....
Click to expand...
Click to collapse
I am running on stock rom, my S8 is still running on Android 7.0 and as I said Gpay was working just fine until March 1. I thought about upgrading to latest stock rom with Android 9.0 but currently there isn't any instruction on how to root Android 9.0 on S8 yet.
The new Google Play services update caused this.
Temporary workaround:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-14-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
Or
1. Upgrade to Magisk Canary by following steps here:
https://forum.xda-developers.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337
Not recommended for daily use!
Never EVER update Google Play services manually, until a Magisk update is available that bypasses the upgraded SafetyNet. Note that Google Play services is responsible for adding/verifying the card, not the Google Pay app! Hence why there seems to be an overlay when adding a card/verifying an existing one.
Tested Google Pay versions:
2.79.x-2.83.235070858 - working
Tested Google Play services versions:
14.7.99 - working
14.8.49-15.0.10 - works on Magisk 18.2 Canary
JarlPenguin said:
The new Google Play services update caused this.
Temporary workaround:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-14-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
Never EVER update Google Play services manually, until a Magisk update is available that bypasses the upgraded SafetyNet. Note that Google Play services is responsible for adding/verifying the card, not the Google Pay app! Hence why there seems to be an overlay when adding a card/verifying an existing one.
Tested Google Pay versions:
2.79.x-2.83.235070858 - working
Tested Google Play services versions:
14.7.99 - working
14.8.49-15.0.10 - not working, downgrade to 14.7.99
Click to expand...
Click to collapse
Thanks! I can use google pay again!
Thank you and backing up and protecting backup of Google Play Services version
JarlPenguin said:
The new Google Play services update caused this.
Temporary workaround:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-14-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
Never EVER update Google Play services manually, until a Magisk update is available that bypasses the upgraded SafetyNet. Note that Google Play services is responsible for adding/verifying the card, not the Google Pay app! Hence why there seems to be an overlay when adding a card/verifying an existing one.
Tested Google Pay versions:
2.79.x-2.83.235070858 - working
Tested Google Play services versions:
14.7.99 - working
14.8.49-15.0.10 - not working, downgrade to 14.7.99
Click to expand...
Click to collapse
Thank you so much for this. Your instructions were followed to the letter and it worked. I had to use a terminal emulator, su, and "pm uninstall com.google.android.gms" to uninstall updates for Google Play Services for steps 2 & 3 on my OnePlus 6T.
Now that it's working I used Titanium Backup to backup this version of Google Play Services and protected the backup.
Again, thanks.
JarlPenguin said:
The new Google Play services update caused this.
Temporary workaround:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-14-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
Never EVER update Google Play services manually, until a Magisk update is available that bypasses the upgraded SafetyNet. Note that Google Play services is responsible for adding/verifying the card, not the Google Pay app! Hence why there seems to be an overlay when adding a card/verifying an existing one.
Tested Google Pay versions:
2.79.x-2.83.235070858 - working
Tested Google Play services versions:
14.7.99 - working
14.8.49-15.0.10 - not working, downgrade to 14.7.99
Click to expand...
Click to collapse
Yeah, thanks it work though install older version of Google Play service didn't seen to helped which Google Pay wouldn't work at all without update Google Pay service to latest version. Even though I updated Google Play service to latest version my Google Pay work again somehow. For the time being Gpay seen to work again hopefully it will continue to work or at least long enough until I upgrade to S10 later this year.
I don't have the three dots to uninstall Google Play Services updates.
OnePlus 3T, Resurrection Remix rom.
Help w/ downgrading Google Play Services
anotherxdauser said:
I don't have the three dots to uninstall Google Play Services updates.
OnePlus 3T, Resurrection Remix rom.
Click to expand...
Click to collapse
If you have already disabled device admin for Google Play Services and Google Pay, you can downgrade Google Play Services like this:
1. Open a terminal emulator on your Android OR an adb shell on your PC connected to your Android.
2. Use "su" to root your shell.
3. Use "pm uninstall com.google.android.gms" to downgrade Google Play Services.
You can then proceed with the remaining steps.
---------- Post added at 10:04 AM ---------- Previous post was at 09:56 AM ----------
JarlPenguin said:
The new Google Play services update caused this.
Temporary workaround:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-14-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
Never EVER update Google Play services manually, until a Magisk update is available that bypasses the upgraded SafetyNet. Note that Google Play services is responsible for adding/verifying the card, not the Google Pay app! Hence why there seems to be an overlay when adding a card/verifying an existing one.
Tested Google Pay versions:
2.79.x-2.83.235070858 - working
Tested Google Play services versions:
14.7.99 - working
14.8.49-15.0.10 - not working, downgrade to 14.7.99
Click to expand...
Click to collapse
While these steps worked for me, I'm having a problem with Google Play Services updating itself back to the newest version each night (even w/ background data services disabled for Play Services and for Pay).
Any advice on a way to prevent updates to Google Play Services until I want it updated?
If I open Google Pay without checking to see if Play Services is still downgraded to 14.7.99, I lose all my payment methods.
OnePlus 6T, stock rooted ROM, 2019 Jan Update, Magisk 18.1.
JarlPenguin said:
The new Google Play services update caused this.
Temporary workaround:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google-inc/google-play-services/google-play-services-14-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
Never EVER update Google Play services manually, until a Magisk update is available that bypasses the upgraded SafetyNet. Note that Google Play services is responsible for adding/verifying the card, not the Google Pay app! Hence why there seems to be an overlay when adding a card/verifying an existing one.
Tested Google Pay versions:
2.79.x-2.83.235070858 - working
Tested Google Play services versions:
14.7.99 - working
14.8.49-15.0.10 - not working, downgrade to 14.7.99
Click to expand...
Click to collapse
Worked for me, thanks for including the bit about version 14.7.99.
chriv said:
If you have already disabled device admin for Google Play Services and Google Pay, you can downgrade Google Play Services like this:
1. Open a terminal emulator on your Android OR an adb shell on your PC connected to your Android.
2. Use "su" to root your shell.
3. Use "pm uninstall com.google.android.gms" to downgrade Google Play Services.
You can then proceed with the remaining steps.
Click to expand...
Click to collapse
Thanks for the instructions but I just can't get this to do anything.
I have no dots so I have to use the above method.
Using terminal emulator I get errors about uninstall from pm command asks to ruin as user 1 but is calling from user 0 blah blah blah
Also the APK link has so many different options....any idea what would be the right one for note 4 910F?
Any help would be appricated, googling the error message I get no results.
Only a guess
MatsyLR said:
Thanks for the instructions but I just can't get this to do anything.
I have no dots so I have to use the above method.
Using terminal emulator I get errors about uninstall from pm command asks to ruin as user 1 but is calling from user 0 blah blah blah
Also the APK link has so many different options....any idea what would be the right one for note 4 910F?
Any help would be appricated, googling the error message I get no results.
Click to expand...
Click to collapse
This is only a guess, but it sounds a little like Linux namespace separation might be related to the problem. Is Magisk your "su" program, or did you use something else to root?
My skills with some types of Linux security are limited, so I might not be any help.
chriv said:
This is only a guess, but it sounds a little like Linux namespace separation might be related to the problem. Is Magisk your "su" program, or did you use something else to root?
My skills with some types of Linux security are limited, so I might not be any help.
Click to expand...
Click to collapse
Yes I am using magisk on Resurrection Remix Pie note 4.
The terminal has root access.
I've tried a few different things like manually uninstalling the Google play services and installing the one from the link but doesn't work.
I've tried other variants like pm uninstall --user 0 com.google.android.gms.apk but I always get the user 0 user 1 error
Full error is
:/ $ pm uninstall com.google.android.gms
Security exception: Permission Denial: runUninstall from pm command asks to run as user -1 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
java.lang.SecurityException: Permission Denial: runUninstall from pm command asks to run as user -1 but is calling from user 0; this requires android.permission.INTERACT_ACROSS_USERS_FULL
at com.android.server.am.UserController.handleIncomingUser(UserController.java:1527)
at com.android.server.am.ActivityManagerService.handleIncomingUser(ActivityManagerService.java:20661)
at android.app.ActivityManager.handleIncomingUser(ActivityManager.java:3904)
at com.android.server.pm.PackageManagerShellCommand.translateUserId(PackageManagerShellCommand.java:2402)
at com.android.server.pm.PackageManagerShellCommand.runUninstall(PackageManagerShellCommand.java:1464)
at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:193)
at android.os.ShellCommand.exec(ShellCommand.java:103)
at com.android.server.pm.PackageManagerService.onShellCommand(PackageManagerService.java:21468)
at android.os.Binder.shellCommand(Binder.java:634)
at android.os.Binder.onTransact(Binder.java:532)
at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:2821)
at com.android.server.pm.PackageManagerService.onTransact(PackageManagerService.java:3922)
at android.os.Binder.execTransact(Binder.java:731)
255|:/ $
Click to expand...
Click to collapse
So today i finally hit the issue
Nothing short of removing gms via TWRP file manager, booting and installing (as a user app) the earlier build worked
Im assuming those with "three dots" are on stock ROMS?
Also pm uninstall com.google.android.gms just error-ed out as above
Hopefully the magisk folks figure out a far easier fix for this
Regardless i made a google pay purchase just an hour ago...
Hit the same issue. I could fix it by disconnecting PayPal from GPay, blocking GPay as device administrator, hiding it and GPlay in Magisk hide and then reconnecting PayPal and re-activating contactless payments. It did not have to remove any GPlay Services Updates or anything.
Guys I'm in a major fix here. Any help would be appreciated.
K20 Pro Global Version - Currently on MIUI Global 11.0.1.0(QFKMIXM)
Rooted via Magisk
Everything was perfectly fine until I noticed 'microG installer Revived' on Magisk and decided to install it.
After I rebooted, Youtube Vanced wouldn't open stating that it won't run without Google Play Services. Same issue with Gmail as well. I went into the microG settings and accepted all the missing permissions. Added my Gmail account, signed in and accepted all the other permission pop-ups that came after.
Despite this everything is still messed up. Gmail and Youtube still gives the same error msg and Chrome keeps crashing.
I tried uninstalling microG but that was an even bigger mistake as the Google Play Services I installed via apk kept crashing.
If someone could pls guide me on how to get the system to how it was prior to the microG installation :crying:
So I managed to fix it somewhat. Uninstalled microG then installed the right version of Google Play services as well as the calendar and contacts sync apks.
No more crash messages but the issue I'm having now is that some app notifications don't work and others (such as Whatsapp) work only sometimes.
And for some really weird reason my Gmail no longer is (or has the option) in dark mode.
Anyway to fix these issues guys?
I've the same problem with my Huawei Mediapad M5 tablet. I've tried to reflash the original "SYSTEM.img" from fastboot mode, but nothing changed. I don't want to do a full reinstall because of this mistake, is there any solution?
Messing with microG is a recipe for disaster because in and of itself it is disastrous, reflash the firmware from scratch and use the Vanced magisk version even though it isn't the last version it works just fine
heynando said:
Messing with microG is a recipe for disaster because in and of itself it is disastrous, reflash the firmware from scratch and use the Vanced magisk version even though it isn't the last version it works just fine
Click to expand...
Click to collapse
It's an absolute nightmare, not sure why the devs don't just update the Magisk version, and I agree the Magisk version works perfectly fine
MicroG works only on systems that don't have GAPPS. That should have been included in the documentation.
I had the same problem (I installed the microG installer revived on a cell phone that had google play services, which caused me that error; I installed the magisk module without knowing what it was for), I solved it by doing the following:
1. Uninstall micro-g and google play services and then restart the terminal.
2. Download and Install (install as system application with lucky patcher) the latest version of the google play services apk, restart.
3. Log out or remove google account from device, reboot device.
4. Login or add google account on the device again, restart the device for the last time; and voila problem solved.
I can't remove my account for some reason, and also I can't add a new google account
Hi Guys, have the same problem. has anyone found a solution? would hate to reset it
Trying to work out what it could be for the first post. It sounds like MicroG was installed while the Google Play services were already on the device.
I have actually manually removed Google Services using the debloater magisk module and run it via terminal.
I'm currently using CrDroid Android 12 and it's working fine with MicroG revived version. I have been testing the Android 13 with MicroG and have issues with the Play Store signing in