A few days ago Google pay randomly stopped working. I'm running Magisk 17.3 since the newer versions stop magisk hide spontaneously. (Tried the latest version tho). I'm passing safetynet, play store says my device is certified, latest os, magisk hide works and I've hidden magisk (and enabled systemless hosts) and hidden root from google pay, still it says that the phone has been rooted or altered in some way.
Any other ideas?
Same problem here. Started 1.3.19
Same here, just rooted last week to get Call Screening here in Canada, and finally got around to getting my Google Pay set up again. No luck
There's been quite a few reports about this, but nothing major enough to get traction, I think. You can try checking this thread, there's a number of possible fixes in there, though they didn't help me, maybe it could work for you.
https://forum.xda-developers.com/apps/magisk/help-magisk-google-pay-t3887147/page4
Related
Hey Folks!
Hope someone can help me out here. I've read a whole bunch of forums and have tried a number of potential solutions to no avail. I have Magisk 15.2 installed and am running Lineage OS 14.2. Multiple apps confirm I pass Safetynet and I can successfully add a card to Android Pay. However, when I try to pay at a terminal, nothing happens. I have tried multiple terminals with no success. Nfc is enabled and android beam works.
Thanks!!!
Try enabling Core Only Mode in Magisk settings, try disabling systemless BusyBox, or try uninstalling your version of Magisk and trying the latest beta. SafetyNet is a nightmare to keep up with. Every time it updates, Magisk gets broken and we have to wait for a new update. Unfortunately, the only real solution is to stop using SafetyNet-dependent apps or keep a locked bootloader/unrooted phone. Or perhaps have one phone for custom ROM stuff and another one for SafetyNet stuff. :/ This is why I'm so vocal about ROMs passing SafetyNet. Hopefully you'll find a fix.
Hey there. Thanks! My phone already passes safety net, though, so I don't think that's the issue... That's what's so bizarre about it! Would you still recommend taking those steps with Magisk Manager?
lastconfederate2 said:
Hey there. Thanks! My phone already passes safety net, though, so I don't think that's the issue... That's what's so bizarre about it! Would you still recommend taking those steps with Magisk Manager?
Click to expand...
Click to collapse
You don't get an error message or anything? Sorry, I missed that. Not sure what the issue is, then. I assume by the other apps, you mean legit apps that actually check for SafetyNet, like downloads in Netflix, a game like Fire Emblem Heroes or a banking app like RBS. If you're able to use those apps or use all of the features perfectly, the issue might just be Android Pay, which probably now detects Magisk(?). Anyway, unless you're actually able to use an app that uses SafetyNet, those SafetyNet checkers don't count for much.
Correct. No error messages, Netflix and others work fine, successfully registered a card in Android Pay, it just doesn't do anything at payment terminals.
lastconfederate2 said:
Correct. No error messages, Netflix and others work fine, successfully registered a card in Android Pay, it just doesn't do anything at payment terminals.
Click to expand...
Click to collapse
I am experiencing the same issue but with Omni 7.1 and Magisk 15.2.
Card was added but giving "Card read error" at payment terminal.
If changing the settings or flashing a beta build doesn't get it to work, then I'm not sure what will. If you're able to, backup your existing ROM and factory reset it. If your Pro3 variant has an official LeEco ROM that passes SafetyNet natively, flash that and lock the bootloader and set up Android Pay to see if it works. Can't offer much else to help you, sorry.
Might be nothing to do with your problem, but i noticed when using nfc to add contacts with other nfc phones etc, that this phone has its nfc chip at the bottom/middle of the phone (it was a while ago, hope I've not remembered incorrectly). Until i realised this i had problems getting it to work.
Edit.. my memory is so bad in now thinking it was the very very top of the phone. Try both.
Thanks for your help, everyone. I discovered today that if I initiate the transaction while my screen is locked, it will actually start the process. I can then unlock the screen and re-tap and it will successfully complete about 75% of the time.
Nothing still happens if i tap the terminal with screen unlocked.
Not perfect, but it works for now!
lastconfederate2 said:
Thanks for your help, everyone. I discovered today that if I initiate the transaction while my screen is locked, it will actually start the process. I can then unlock the screen and re-tap and it will successfully complete about 75% of the time.
Nothing still happens if i tap the terminal with screen unlocked.
Not perfect, but it works for now!
Click to expand...
Click to collapse
Are you still able to get it to work like this? What was the last update you installed? I am trying to do some research to figure out why this happens on many different devices with different roms and such. Most seem to have the ability to get Pay to work and load cards into it, but using at stores and tapping the terminals does nothing(currently my issue).
So what is you setup as of now? Magisk ver, universal safetynet fix(if you're using that) ver, OS ver/date, and what security patch?
If you can provide those things it would be helpful.
Thank you.
Yes, that is still how it works, though I've found over time that it works more like 25% of the time. The last LOS update I have installed is February 10th. I'm using Magisk 15.3, running Android 7.1.2, and last security patch is 1/05/18.
Thanks!
Any luck with this?. Havent tried lock screen pay yet, but unlocked it doesn't work.
LOS 15.1- GTi9506
wkwk said:
Any luck with this?. Havent tried lock screen pay yet, but unlocked it doesn't work.
LOS 15.1- GTi9506
Click to expand...
Click to collapse
Google switched the API last week and rebranded Android Pay as Google pay
https://www.xda-developers.com/google-pay-android-pay-google-wallet/
Have you tried installing Google Pay?
https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&hl=en
tsongming said:
Google switched the API last week and rebranded Android Pay as Google pay
https://www.xda-developers.com/google-pay-android-pay-google-wallet/
Have you tried installing Google Pay?
https://play.google.com/store/apps/details?id=com.google.android.apps.walletnfcrel&hl=en
Click to expand...
Click to collapse
Yes same issue.
Interestingly, upgrading to official LOS 15.1 this week completely resolved the issue. Google Pay works great unlocked, now.
lastconfederate2 said:
Interestingly, upgrading to official LOS 15.1 this week completely resolved the issue. Google Pay works great unlocked, now.
Click to expand...
Click to collapse
It will probably work in Lineage 14.1 once its been updated for the newer api.
Hi,
I have a issue with Google Pay,
first of all I've made a succeful contact-less payment while BL was locked (linked paypal to g pay), but now after unlocking BL and flashing Magisk - I can't, it gives me an error on terminal 'Transaction rejected'
Ofc SafetyNet test passes, and google play store sees my phone as certified device;
Google play services, google pay, google play, paypal and phone are hidden in magisk manager.
So the question is - Have somebody made a succeful contact-less payment with unlocked BL on our OP6T?
Thanks!
it works here perfectly fine using magisk 17.3
Pokemon Go works also (and everything else)
I use Gpay everyday no issue
My op6t is also unlocked and root via magisk and I face the same problem, it worked the first time but now I keep trying to gpay in each store but it fails every time.
I'm using gpay on daily basis, I didn't need to hide it in magisk but you can try to clear gpay/paypal cache or reinstall it.
I'm on OOS 9.0.7 with Magisk 18.0
Yep, got the phone the day it came out, rooted it 5 minutes after it arrived, used pay every day since, never hid anything in magisk. I know that's little help but at least you know you've something going on with your specific configuration. I'm .7 with Magisk 18.0.
I've been using Google Pay on my phone every day since launch with unlocked Bootloader and Magisk. I never had a problem. Magisk 18 and OOS 9.0.7 right now.
Same here no issue with GPay linked with my Revolut credit card
And I have been using gpay with Magisk without issues. Bootloader is unlocked.
Unfortunately I'm not having the same luck with Pokemon go. Can you lead me in the right direction.... Do you have anything specifically set up in magisk hide I should be aware of. Main reason I still root is Pokemon Go.
Setup: OS 9.0.2 Magisk v.18.
---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------
OnkeIM said:
it works here perfectly fine using magisk 17.3
Pokemon Go works also (and everything else)
Click to expand...
Click to collapse
Unfortunately I'm not having the same luck with Pokemon go. Can you lead me in the right direction.... Do you have anything specifically set up in magisk hide I should be aware of. Main reason I still root is Pokemon Go.
Setup: OS 9.0.2 Magisk v.18.
Sent from my [device_name] using XDA-Developers Legacy app
unlocked bootloader + root works always for me with this config:
- Magisk 18.0
- marked needed apps in "Magisk Hide"
- use " change Magisk package name"-option in settings
- install Magisk modul "MagiskHide Props Config"
- modul needs to setup in a terminal/console-app (open terminal, type "props" , follow option 1)
works for for me on Pokemon, GooglePay, Ingress and other all other apps that didn't started due root detection
Flakito97 said:
Unfortunately I'm not having the same luck with Pokemon go. Can you lead me in the right direction.... Do you have anything specifically set up in magisk hide I should be aware of. Main reason I still root is Pokemon Go.
Setup: OS 9.0.2 Magisk v.18.
---------- Post added at 09:56 AM ---------- Previous post was at 09:53 AM ----------
Unfortunately I'm not having the same luck with Pokemon go. Can you lead me in the right direction.... Do you have anything specifically set up in magisk hide I should be aware of. Main reason I still root is Pokemon Go.
Setup: OS 9.0.2 Magisk v.18.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
main reason should not be Pokemon Go since it is a multiplayer game...
The only thing i always do is
1. Change package name from magisk
2. Activate desired app in magisk hide
It always worked with every app I tried like Telekom App or Banking App.
Right now I don't have root anymore, I got my 6T replaced because of a dead pixel and currently don't want to increase my widevine level
OnkeIM said:
main reason should not be Pokemon Go since it is a multiplayer game...
The only thing i always do is
1. Change package name from magisk
2. Activate desired app in magisk hide
It always worked with every app I tried like Telekom App or Banking App.
Right now I don't have root anymore, I got my 6T replaced because of a dead pixel and currently don't want to increase my widevine level
Click to expand...
Click to collapse
Gotcha, well yes I did those but no luck.
No worries. Thanks for the response!
Sent from my [device_name] using XDA-Developers Legacy app
Randomly today without any change or update to my OnePlus 6t Google Pay told me "you can no longer use Google Pay in stores." My CTS match is good everything looks fine. Did they patch anything recently?
Sent from my ONEPLUS A6013 using Tapatalk
xlxcrossing said:
Randomly today without any change or update to my OnePlus 6t Google Pay told me "you can no longer use Google Pay in stores." My CTS match is good everything looks fine. Did they patch anything recently?
Sent from my ONEPLUS A6013 using Tapatalk
Click to expand...
Click to collapse
I am seeing the same error starting last night and continuing into today.
alryder said:
I am seeing the same error starting last night and continuing into today.
Click to expand...
Click to collapse
Well at least I'm not alone which tells me they patched the CTS exploit...guess we will have to wait for a possible magisk update.
Sent from my ONEPLUS A6013 using Tapatalk
Before I begin this is just a workaround but works flawlessly and you will be able to use google pay again. uninstall the current version of google play services and google pay. You want to be on the previous version of google pay.. Then Google search previous version of google play services (I believe its 14.7.99). Install then restrict background data on both google play store and google play services and all will work great... Do not update either until magisk comes out with an update that will work with the latest play services update versions... This was driving me crazy until I gave this a try after all else failed... Have Fun Spending your Money!!!lol
anthony10126 said:
Before I begin this is just a workaround but works flawlessly and you will be able to use google pay again. uninstall the current version of google play services and google pay. You want to be on the previous version of google pay.. Then Google search previous version of google play services (I believe its 14.7.99). Install then restrict background data on both google play store and google play services and all will work great... Do not update either until magisk comes out with an update that will work with the latest play services update versions... This was driving me crazy until I gave this a try after all else failed... Have Fun Spending your Money!!!lol
Click to expand...
Click to collapse
Which version of Google Pay are you using? I got 2.84.237487748 and it's still working for now. At least the app opens normally & hasn't told me I can't use it. I haven't actually tried paying for something in a few days. And I think I just updated the GPay app within the last week.
FWIW, I'm still using Magisk 17.3 on OOS 9.0.12. With Magisk 18.x, Magisk Hide would stop working, SafetyNet checks would fail and the device would become uncertified. I've had no such issues with 17.3. Although I don't know if any of those things would cause Google Pay to stop working because even with those things happening, Google Pay has never stopped working for me. But now that I've said that, it'll probably will in 3, 2, 1....
sharksfan7 said:
Which version of Google Pay are you using? I got 2.84.237487748 and it's still working for now. At least the app opens normally & hasn't told me I can't use it. I haven't actually tried paying for something in a few days. And I think I just updated the GPay app within the last week.
FWIW, I'm still using Magisk 17.3 on OOS 9.0.12. With Magisk 18.x, Magisk Hide would stop working, SafetyNet checks would fail and the device would become uncertified. I've had no such issues with 17.3. Although I don't know if any of those things would cause Google Pay to stop working because even with those things happening, Google Pay has never stopped working for me. But now that I've said that, it'll probably will in 3, 2, 1....
Click to expand...
Click to collapse
I downgraded Google pay to 2.81. If you haven't used you're Google pay in the past few days chances are you're Google pay is not working. Google play services updates in the background without you knowing which is why I suggested turning off background data.. staying on magisk 17 shouldn't make a difference..
Even with only an unlocked bootloader it won't let you set up google pay (no twrp, no magisk, no root, just unlocked bootloader).
Hi,
im a little bit confused about this problem. From one day to another, G Pay stopped working with NFC. "This device cant be used because its rootet or modified."
I use Magisk with stock Rom severeal month now and gpay ran without any problems. The confusing thing is that I didn´t changed anything what could cause this behaviour.
What I already tried:
-GPay: Delete cache, uninstalled updates. Tried many times to activate NFC payment.
-Erased Cache in TWRP
-Installed complete offline OTA. (Root and TWRP was gone and it still wont work)
-Tried Magisk Hide and random app name.
Does anybody have an idea? I dont want to reset the whole phone for this or lock the bootloader.
Thanks for your help!
Did you update the Gpay app? Mine still works but I never installed the update
I've got the latest Google Pay version and it's been working fine.
What version of Magisk are you using? Do the SafetyNet checks pass? Does Google Play Store show that the device is certified? I've had issues with Magisk 18 & 18.1 where Magisk Hide would stop working and SafetyNet checks failing.
If you're on Magisk 18.x & SafetyNet checks fail for you, try uninstalling Magisk & Magisk Manager. Install version 17.3. Install Magisk Manager 6.1.0. Enable Magisk Hide and hide Google Pay and Google Play Store. Clear storage on Google Play Store. See if SafetyNet checks pass. Check that the device is certified. Try Google Pay again.
I don't know for sure that this will fix the problem with Google Pay, but it's what I've done after having issues with Magisk.
sharksfan7 said:
I've got the latest Google Pay version and it's been working fine.
What version of Magisk are you using? Do the SafetyNet checks pass? Does Google Play Store show that the device is certified? I've had issues with Magisk 18 & 18.1 where Magisk Hide would stop working and SafetyNet checks failing.
If you're on Magisk 18.x & SafetyNet checks fail for you, try uninstalling Magisk & Magisk Manager. Install version 17.3. Install Magisk Manager 6.1.0. Enable Magisk Hide and hide Google Pay and Google Play Store. Clear storage on Google Play Store. See if SafetyNet checks pass. Check that the device is certified. Try Google Pay again.
I don't know for sure that this will fix the problem with Google Pay, but it's what I've done after having issues with Magisk.
Click to expand...
Click to collapse
Magisk: 18.1 (worked with this version), Safety Net is passing (Thats why im so confused about it)
Playstore is showing me that it is certified.
I never had a failed SN check.
Probably because having a rooted phone, especially if you are using to send/receive money, opens up a SECURITY HOLE, even if you are using something to "bypass" google.
NOTHING is 100% safe, but, I for one, will never root my phone, if I am using it to spend money.
The days of rooting will be over one of these days. Google is locking down things more and more.
hlzocker said:
Magisk: 18.1 (worked with this version), Safety Net is passing (Thats why im so confused about it)
Playstore is showing me that it is certified.
I never had a failed SN check.
Click to expand...
Click to collapse
Make sure you have hide enabled for pay.
I'm on 18.1 and I don't have issues.
I fought with the same problem.
latest Magisk Canary build was the solution that worked for me:
https://forum.xda-developers.com/showpost.php?p=78946079&postcount=31551
Coumodo said:
I fought with the same problem.
latest Magisk Canary build was the solution the worked for me:
https://forum.xda-developers.com/showpost.php?p=78946079&postcount=31551
Click to expand...
Click to collapse
Yes, that solved the problem for me. Now the activation was successfull. Thanks!
Hello there. I have a question regarding getting my phone to be Google Play Protect certified again. I have unlocked the bootloader, which if I understand correctly is what breaks the certification, Flashed TWRP 3.0.4-1, and installed Magisk v20.4 via TWRP. I verified Root by using the app Root Checker on the play store (and also SU requests popped up after rebooting). I enabled MagiskHide inside Magisk Manager and performed a SafeyNet Check and both the ctsProfile and basicIntegrity returned as True (the first time I ran it cts failed so I enabled hide and rebooted). There are a few apps that I use that indicate my device is not compatible and it is because of this I am guessing (Chewy, Disney+ for example). Oddly, as I was typing this I tried again and looked in the "My Apps" list and I could install Disney+ from there (10 minutes ago I couldn't) but clicking on the app it still said that it was incompatible. Chewy, however, remains unable to be used.
Since I could only find references to this on this thread (https://forum.xda-developers.com/pixel-2-xl/help/play-certification-unlocked-bootloader-t3950857) and the second way to correct this problem, that thread says it doesn't resolve the ctsProfile) I figured I'd ask on here. I already soft-bricked it once and successfully used the MSM tool to bring it back so if I screwed something up I'll try again, but probably only once more :fingers-crossed:
*edit* I haven't activated my actual phone use yet since I want it to be stable first! Not sure if that makes a difference, I don't think it should.
*edit 2* I've since activated my phone. I can receive calls but no text messages. The plot thickens.
Thanks!
I'm running magisk 20.4 and can't get the ctsprofile to work, I tried following a guide for 20.3 which changed the props but to no avail. Any help I use my gpay all the time.
due to the new changes Google has implemented into safetynet (namely hardware based verification) all apps that depend on it will no longer work on rooted devices, including g pay, banking apps and even the McDonald's app in Romania. so due to this reason I've reverted to stock, and am looking to sell this phone to buy an s20+