Hello, I was wondering if anyone else suddenly lost the ability to use google pay, the last time it worked was march 14, but by saturday it was gone, the message is "You can no longer use google pay"
nothing was installed or modified during those days.
If anyone had this situation and find a solution/workaround please let me know
device info:
Os 9.0.12
root/magisk v18.1 magisk manager v.7.0.0/
apps do not auto-update.
Device is certified
SafetyNet Check Success
Yep.... Me too. I ended up updating to Canary. All is good for me now.
mavogaro said:
Yep.... Me too. I ended up updating to Canary. All is good for me now.
Click to expand...
Click to collapse
What do you mean by Canary?
It's beyond the beta build of Magisk, similar to what Chrome Canary is. Can be unstable. I found the link through XDA.. You enter the link under settings, update channel, then the URL.
The search is your friend. Check this thread for discussion of this issue. There is also multiple work-arounds to get Google Pay working again.
https://forum.xda-developers.com/apps/magisk/discussion-google-pay-magisk-discussion-t3906703/
Related
Hello,
Not sure if this is the correct forum to ask, sorry if it isn't.
I've noticed that after the lollipop upgrade I don't have the "smart lock" option in my settings->security. After digging through the www for a while it seems that I don't have the latest Google play services update (which brings the "trusted places" feature).
Is this correct? This is the reason I'm not seeing the "smart lock' feature?
Play store says I have the latest version (I currently have 436, which is NOT the latest version). Why? I got the play services update this morning and yet it's not the latest version. Should I wait a little longer for the update?
Is it safe to update the latest Google play services manually? apkmirror.com/apk/google-inc/google-play-services/google-play-services-6-5-87-1599771-446-apk
Thanks in advance.
ekmo said:
Hello,
Not sure if this is the correct forum to ask, sorry if it isn't.
I've noticed that after the lollipop upgrade I don't have the "smart lock" option in my settings->security. After digging through the www for a while it seems that I don't have the latest Google play services update (which brings the "trusted places" feature).
Is this correct? This is the reason I'm not seeing the "smart lock' feature?
Play store says I have the latest version (I currently have 436, which is NOT the latest version). Why? I got the play services update this morning and yet it's not the latest version. Should I wait a little longer for the update?
Is it safe to update the latest Google play services manually? apkmirror.com/apk/google-inc/google-play-services/google-play-services-6-5-87-1599771-446-apk
Thanks in advance.
Click to expand...
Click to collapse
apk mirror is a site of android police to upload their apk's. i trust them and i installed stuff from there a lot of times. the apk signatures are correct and the apk update correctly to newer versions after the insallation. so it is a matter of trusting the source. i trust them so a lot of other readers.
android police is a serious site. so do your research about the site and decide for yourself if you are willing to trust them or not.
P.S. the reason that you don't have the latest version is that the roll out is usually done within the span of a few days to weeks depending of where you are. so the update will come eventually.
116
ttheodorou said:
apk mirror is a site of android police to upload their apk's. i trust them and i installed stuff from there a lot of times. the apk signatures are correct and the apk update correctly to newer versions after the insallation. so it is a matter of trusting the source. i trust them so a lot of other readers.
android police is a serious site. so do your research about the site and decide for yourself if you are willing to trust them or not.
P.S. the reason that you don't have the latest version is that the roll out is usually done within the span of a few days to weeks depending of where you are. so the update will come eventually.
Click to expand...
Click to collapse
I always prefer to do the update the "regular way", via play store, so according to your advice I think I'll wait a little longer for the update.
Thanks. :good:
ekmo said:
I always prefer to do the update the "regular way", via play store, so according to your advice I think I'll wait a little longer for the update.
Thanks. :good:
Click to expand...
Click to collapse
for me the only reason to update via apk mirror is if i want to check something immediately. for example when the new google apps with material design was out i updated from there instead of waiting. i couldn't help my self
ttheodorou said:
for me the only reason to update via apk mirror is if i want to check something immediately. for example when the new google apps with material design was out i updated from there instead of waiting. i couldn't help my self
Click to expand...
Click to collapse
Well, in my case it's just a cool new feature I want to try out. I'll give it a few more days and if it won't come on it's own then I'll update it manually.
It's basically just getting the apk and running it (wherever it's located), correct?
ekmo said:
Well, in my case it's just a cool new feature I want to try out. I'll give it a few more days and if it won't come on it's own then I'll update it manually.
It's basically just getting the apk and running it (wherever it's located), correct?
Click to expand...
Click to collapse
you download the apk on your phone and install it like any other app. it is called side loading. there is an option under settings/security to allow you install apps outside the play store if you haven't done it already you must unclick it.
ttheodorou said:
you download the apk on your phone and install it like any other app. it is called side loading. there is an option under settings/security to allow you install apps outside the play store if you haven't done it already you must unclick it.
Click to expand...
Click to collapse
Yep, I'm familiar with this option, but thanks for reminding me to recheck it before installing. :good:
ekmo said:
Yep, I'm familiar with this option, but thanks for reminding me to recheck it before installing. :good:
Click to expand...
Click to collapse
glad to help
For the Nexus 4 (with Lollipop), I believe this is the version you want from apk mirror:
Google Play services 6.5.87 (1599771-436)
Edit: the notes section on apk mirror explains the version naming/numbering for the Play Services apks. The last three digits indicate which version of Play Services is right for your device.
I was notified immediately after upgrading to L that my Google Services are outdated and I was redirected to Play Store before even could get to home screen. Maybe it only happens after standard OTA...?
urfel said:
I was notified immediately after upgrading to L that my Google Services are outdated and I was redirected to Play Store before even could get to home screen. Maybe it only happens after standard OTA...?
Click to expand...
Click to collapse
Same here, but for some reason it did not update for the latest version.
ekmo said:
Hello,
Not sure if this is the correct forum to ask, sorry if it isn't.
I've noticed that after the lollipop upgrade I don't have the "smart lock" option in my settings->security. After digging through the www for a while it seems that I don't have the latest Google play services update (which brings the "trusted places" feature).
Is this correct? This is the reason I'm not seeing the "smart lock' feature?
Play store says I have the latest version (I currently have 436, which is NOT the latest version). Why? I got the play services update this morning and yet it's not the latest version. Should I wait a little longer for the update?
Is it safe to update the latest Google play services manually? apkmirror.com/apk/google-inc/google-play-services/google-play-services-6-5-87-1599771-446-apk
Thanks in advance.
Click to expand...
Click to collapse
It's perfectly safe, as it is the exact same version you will recieve from play store.
I'm not sure what the problem is anymore.
I looked at a friend's Nexus 4 that was also updated with Lollipop and he has the same Google play services build as me and he still gets the 'smart lock' option.
Could it be something with the settings on my phone? Maybe I need to do something in order to enable it? I've already tried enabling a security lock screen but that didn't help.
So i recently updated to 338. Updated magisk to 18 and phone pe app itself got an update. Yesterday i tried paying through phone pe on flipkart and the transaction failed. It said the device is insecure. Now i don't know which among the 3 updates caused this. Can someone help? Thanks.
chaitanya.v said:
So i recently updated to 338. Updated magisk to 18 and phone pe app itself got an update. Yesterday i tried paying through phone pe on flipkart and the transaction failed. It said the device is insecure. Now i don't know which among the 3 updates caused this. Can someone help? Thanks.
Click to expand...
Click to collapse
Use Magisk Hide to hide root and also disable start on boot for Phone pe.
Try disabling telephone and sms permission from Google Play services
That might work.
Google pay and banking apps worked for me
Got a message from Google Pay saying that my phone is rooted or is running uncertified software.
I have a T-Mobile variant that I converted , without root, to international. Anyone else see this issue?
Read. This is an old problem for years. Is your bootloader unlocked? Not rooted? Yes this breaks GPay. Hence, Magisk, root, systemless and Hide.
Easy fix.
I'm not rooted. Bootloader is locked.
I just booted into bootloader to double check, and it is locked and secure boot is enabled
coolmaster121 said:
I'm not rooted. Bootloader is locked.
I just booted into bootloader to double check, and it is locked and secure boot is enabled
Click to expand...
Click to collapse
It's a known issue for converted TMobile variant and I'm one of them. OP aware of the issues and hopefully an update coming soon.
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
coolmaster121 said:
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
Click to expand...
Click to collapse
You're going to need root to get this fixed. So first go this link and follow the instructions in the first post to get Magisk on your device.
Next, you may need to install the latest Magisk Manager. Link here.
With Magisk Manager on your device, you can install both "Busybox for Android NDK" and "MagiskHide Props Config" modules.
After a reboot, use a terminal app (I used Termux) to setup MagiskHide Props as per the instructions here. I just used the available OnePlus 6T fingerprint.
With it all setup, the device will show up as certified.
plasmamax1 said:
You're going to need root to get this fixed. So first go this link and follow the instructions in the first post to get Magisk on your device.
Next, you may need to install the latest Magisk Manager. Link here.
With Magisk Manager on your device, you can install both "Busybox for Android NDK" and "MagiskHide Props Config" modules.
After a reboot, use a terminal app (I used Termux) to setup MagiskHide Props as per the instructions here. I just used the available OnePlus 6T fingerprint.
With it all setup, the device will show up as certified.
Click to expand...
Click to collapse
Thanks for the suggestion.
I'm not rooted, and really don't want to root.
That is besides the point though, why is the official release of the OS having the issue.
coolmaster121 said:
I'm not rooted, and really don't want to root.
That is besides the point though, why is the official release of the OS having the issue.
Click to expand...
Click to collapse
When you say "official" release, did it come OTA, or did you download it, or use the updater from
the play store?
OnePlus isn't releasing 10 "officially" to the 6T, got a few bugs left to squish.
p51d007 said:
When you say "official" release, did it come OTA, or did you download it, or use the updater from
the play store?
OnePlus isn't releasing 10 "officially" to the 6T, got a few bugs left to squish.
Click to expand...
Click to collapse
It was a zip I downloaded and did a local update.
Caltinpla said:
It's a known issue for converted TMobile variant and I'm one of them. OP aware of the issues and hopefully an update coming soon.
Click to expand...
Click to collapse
Is there an existing thread on this? I didn't see one and am keeping an eye out for a fix that doesn't require root or an unlocked bootloader.
coolmaster121 said:
Seems like onplus6t lost play protect certification with Android 10 also.
Is everyone in the same situation also?
Click to expand...
Click to collapse
Yep
No, works fine. But I don't have a converted variant - all stock.
If you go back to stock as it is with T-variant (search for MSM tool), is it certified again?
https://forum.xda-developers.com/showpost.php?p=80844361&postcount=7
noideas4thisname said:
Is there an existing thread on this? I didn't see one and am keeping an eye out for a fix that doesn't require root or an unlocked bootloader.
Click to expand...
Click to collapse
Nope, I tried everything I heard of but nothing worked. Hopefully, OP releases an update with the fix soon!
I'm getting, "Your device isn't compatible with this version" error when I try to install it on my phone.
I'm still on 8.1 due to some Xposed modules not being updated for 9.0.
Disney+ support states that they have installs blocked unless you're on the latest version of your ROM... is this true?
IdrisMC said:
Disney+ works for me, i think your phone failed a test. I recommend installing a outdated disney+ apk. And the play store will update it automatically for you. And it will keep doing that so you dont notice a difference
Click to expand...
Click to collapse
Are you still on Android 8.1 or have you upgraded to 9?
Honestly, this is the first time an app has been incompatible with my device.
I've also got the play store and playstore services enabled for Magisk Hide.
Wasn't too comfortable with installing the APKpure app as the site requires it now, but after doing some digging it seems like they're trustworthy enough.
Once I had that, installing the latest Disney+ version went flawlessly.
So thank you for the encouragement!
Makes me think that the CS rep was right and they put a condition that only devices on their latest android version are allowed to install it from Google Play.
IdrisMC said:
That could be the test you failed, it would be a stupid discission from Disney tho, since most people are outdated..
I am on android Q btw.
Click to expand...
Click to collapse
Extremely stupid on their part... Apologies, I thought I already pressed the thanks button!
Hey,
Long time. Rooter (since HTC desire HD) here.
I remember on my older Oneplus phones, installing an beta would stop you passing Safetynet, so banking apps wouldn't work etc. Is this still the case? Can anyone on the 11 betas see if it passes safetynet? I'm not rooted currently!
Anyone?
Havent tried the beta's yet either. But I am rooted and pass safetynet on my 8pro. One of my 1st rooted devices was the HTC DesireHD as well and I did like the Nexus 5 alot.
atm I'm using XXX flashed with magisk and the current Radioactive kernel and my phones gr8 and passes safetynet for banking apps , gpay , netflix etc.
mapester said:
Havent tried the beta's yet either. But I am rooted and pass safetynet on my 8pro. One of my 1st rooted devices was the HTC DesireHD as well and I did like the Nexus 5 alot.
atm I'm using XXX flashed with magisk and the current Radioactive kernel and my phones gr8 and passes safetynet for banking apps , gpay , netflix etc.
Click to expand...
Click to collapse
Yeah with magisk I know you can pass, but I havnt felt the need to root this phone (nor my 7 Pro when I had it) - especially since a lot of people have had a fingerprint enrollment problem (I know you have to backup the persist partition) - I just wanted to test out some android 11 stuff, but it used to be that if you were in a beta, you failed safetynet even if BL was locked. Was just curious, thats all!
manor7777 said:
Yeah with magisk I know you can pass, but I havnt felt the need to root this phone (nor my 7 Pro when I had it) - especially since a lot of people have had a fingerprint enrollment problem (I know you have to backup the persist partition) - I just wanted to test out some android 11 stuff, but it used to be that if you were in a beta, you failed safetynet even if BL was locked. Was just curious, thats all!
Click to expand...
Click to collapse
Just to clarify - the fingerprint enrollment problem has nothing to do with root. It's all about the bootloader. Something happened when the bootloader was relocked (manually or by msmdtool). I believe the issues is fixed on later OOS versions, but haven't really looked into it as I'm not relocking.
Your question, however, the answer depends on when you flash the OB. It seems the OB is released around the same time the build is sent too google for verification, so if you're too quick to flash safetynet fails. If you wait for google to verify the ROM it's all good. There is, as far as I know, no information about when builds are verified. If you flash the ob too soon you can clear ps data and it will pass once google has updated on their part.
Edit: That's how they do it with pre-11 betas, not sure about 11, I guess that's up to google as it's an unreleased OS version. I believe even pixels fail their safetynet checks at this time.
efex said:
Just to clarify - the fingerprint enrollment problem has nothing to do with root. It's all about the bootloader. Something happened when the bootloader was relocked (manually or by msmdtool). I believe the issues is fixed on later OOS versions, but haven't really looked into it as I'm not relocking.
Your question, however, the answer depends on when you flash the OB. It seems the OB is released around the same time the build is sent too google for verification, so if you're too quick to flash safetynet fails. If you wait for google to verify the ROM it's all good. There is, as far as I know, no information about when builds are verified. If you flash the ob too soon you can clear ps data and it will pass once google has updated on their part.
Edit: That's how they do it with pre-11 betas, not sure about 11, I guess that's up to google as it's an unreleased OS version. I believe even pixels fail their safetynet checks at this time.
Click to expand...
Click to collapse
Ah OK, that makes sense. Most of the OnePlus betas I've installed n the past have been after Google. Released the OS to pixels, and they still failed Safetynet, but I also know Google is constantly changing safetynet stuff so that's why I wondered. Thanks anyway!