google pay not working - Samsung Galaxy S10+ Questions & Answers

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+

Related

Magisk + Google Pay

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).

Google Pay stopped working

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!

Certified device, safetynet passed, google pay doesn't work

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

New to Android: Is safetynet still by-passable as of now?

I only got my first Android device today, the G7, in order to run LineageOS, which I have gotten set up successfully. (I can't believe I didn't brick the phone!)
The only thing not working as far as I can tell (of course) is SafetyNet apps like Google Pay. From what I have read there are various workarounds but I can not be sure whether it's supposed to be working as of today, and whether my device/ROM makes that a hard no. I followed instructions and have installed Magisk, along with thesuggested modules (Didgeridoohan, Safetypatcher), and hidden all apps using Magisk hide. Before installing those modules, the SafetyNet check failed for "basicIntegrity"; afterwards, both tests fail, so that's a step backwards.
Is it possible to get this working given my configuration?

Safetynet fails Basic Eval

device info:
Oneplus 8 Pro IN2025
Oxygen OS 11.0.99.IN11AA
Recently rooted and I was not passing SafetyNet basic Eval and I tried Riru Lxposed and still the same thing. Somewhere online I saw someone said to install Magisk Canary and it should have Denylist which should help hide apps from the root and I don't have to worry about Safetynet with Denylist. So right now I am using Zygisk with Denylist and even with that, some apps are not working like Amazon and eBay. Can't figure out any way to pass even the basic Eval for SafetyNet. I just want all my apps to work anyone figure out a way around safetynet checks or know how to make Denylist work on all apps?
Didn't think this would work but I just fixed it.
[2023 FIX] Fix Magisk CTS Profile False Error - Bypass Safetynet
Magisk CTS Profile False Error is now popping up on almost everyone's device since Google made some changes in March. To Bypass Safetynet...
droidholic.com
The Dec 23rd 2021 update was what fixed it for me. I downloaded the Zygisk fix and put it in my Magisk and was able to pass safetynet and all my apps were working!
Bump! Oddly enough I am passing safetynet but Huntington banking app is still detecting root and Amazon is not working again. Ebay app works though.
Amazon app was working but now I guess its not?
Edit: uninstalling and reinstalling the fix module lets amazon temporary for a couple minutes and then it stops working but huntington app still detects root too.
I'm still rocking a Pixel 2 XL running stock rooted 9.0.0. I've got Magisk 23.0 Stable installed and the following modules installed:
Busybox for Android NDK 1.34.1
Systemless Hosts 1.0
Riru 26.1.4.r552(etc)
Universal SafetyNet Fix 2.1.3
If it matters, I do still have TWRP installed.
I installed Riru, rebooted, installed Universal SafetyNet Fix, rebooted again, and when SafetyNet check failed, I toggled Magisk Hide off then on.
Does anyone know what might be wrong? Suggestions are very welcome!

Categories

Resources