Database Develop

Google Pay setup failure: rooted devices not supported

Hi,
I'm running Magisk Manager 6.1.0 (165) and Magisk v18.0 on Omni-ROM.
The issue is that I cannot complete Google Pay setup, means after confirming the payment details (credit card) I get an error message saying that the device cannot be used because it is either rooted or modified.
I tried to solve this issue with function "Magisk Hide", but this does not work.
Any advise?
THX

Did you figure this out yet? Been trying different things all morning.

Afaik magisk v18 doesn't pass safetynet entirely on some devices, basicIntegrity usually passes but ctsProfile fails.
After scouring the forums I managed to get a banking app, PoGo and Google Pay to work, here's a list of things that eventually worked if you also get the same safetynet result:
- Turn Magisk Hide and Repackage Magisk Manager (from Magisk settings) and delete the MagiskManager folder in Internal Storage and remove other mentions of magisk in filepaths
- Install the magisk module "ShellHide" and tick "Google Services Framework" (Google Pay doesn't need to be hidden but it wouldn't hurt to also hide root from it) and others eg: Banking apps or PoGo
- Install the magisk module "MagiskHide Props Config" and "Busybox" then follow the forum post for MagiskHide Props Config on how to change/update your devices fingerprint
- If you want to go the extra mile you can also follow the forum post for the props config to "improve root hiding" as well

Magisk safetynet no longer passing

Within the past month Magisk can no longer pass the safetynet check. Ctsprofile fails and basicintegrity fails. I am on Magisk v20(20000) and Magisk manager v7.3.5(243). I've performed the following steps...
1. Turned off USB debug
2. Confirmed root check fails when hidden by Magisk and does NOT fail when not hidden by Magisk.
Any suggestions?

I found out it was Riru Exposed module. I went into Edexposed, enabled black/whitelist, rebooted, black listed Google play and Google play services, rebooted and safetynet check passed in Magisk.

JDubbed said:
I found out it was Riru Exposed module. I went into Edexposed, enabled black/whitelist, rebooted, black listed Google play and Google play services, rebooted and safetynet check passed in Magisk.
Click to expand...
Click to collapse
I was just about to post the same. Blacklisting those in Edxposed worked for me when nothing else did.
Does this indicate that Google is deploying countermeasures against Xposed framework?

I swapped out the Xposed installer for the Xposed manager and now the blacklist method is working at the moment. Google pay works.

gboybama said:
Does this indicate that Google is deploying countermeasures against Xposed framework?
Click to expand...
Click to collapse
Google has ALWAYS updated SafetyNet to block root users and Xposed users-- That's a large reason why both Magisk and edXposed were created, in the first place. LOL! While it's there to prevent hacking/abuse to understandably legitimate sources (banking apps, auction sites and storefronts, etc.), it's collaborated heavily with Niantic (developers of Pokémon GO) and updated a bunch of its more strict checks because of Pokémon GO.
Thanks to everyone for the tips, though!
Sent from my LG V20 (VS995), Alpha Omega ROM, Oreo 8.0, rooted (Magisk 19.3), using Tapatalk

KIA Connect Linageos 18

Hello,
I'm want to use KIA connect on my Samsung S10+.
I tried LOS 18 and LOS19
Magisk 24.100
Zygisk
KIA, Google Play Store, GP-Service, Framework in "Verweigerungsliste"
MagiskHide Props v6.1-v137
Hide Magisk and frozen
but the App won't to start because of root
I use this app and Magisk on my rooted OnePlus without problems.
Any idea, how to fix this?
Thanks
Frank

Same problem, I managed to find a solution.
All I needed was to pass as SafetyNet test:
Install MagiskHide Props Config: https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf (download and install as module in Magisk), reboot.
Open any terminal (e.g. Termux), run: `su -c props`
Grant superuser permission.
The MagiskHide Props Config is launched within the terminal, select 2: Force BASIC Key Attestation.
Find your device or leave default value (for my OnePlus One the value 'A001' was ok.
Confirm, reboot.
Ensure that Zygisk and Enforce deny list are enabled in Magisk settings.
Add Kia Connect to DenyList.
Download Universal SafetyNet Fix: https://github.com/kdrag0n/safetynet-fix
Install it as Magisk module.
Hide Magisk app (in Magisk settings)
Clear Google Play Service and Google Play Store data (app settings).
Install YASNAC from Play Store, run SafetyNet Attestation, all results should be green now.
I was now able to launch the Kia Connect app.

On Lineage OS 19 on Xiaomi A1 I needed to install Magisk 25.2 in LOS recovery. After that the installation of Universal Safetynet Fix was enough. So I could skip the 1 to 6.

How can I get Netflix, Hulu, and Google Pay to work on rooted Pixel 5 with Lineage OS 19 rom?

I'm aware it's a safety net issue, but is there any simple fixes? I feel with older versions of magisk and los, it was as easy as magisk hide.

With the Universal Safetynet Fix module.
MAGISK MODULE ❯ Universal SafetyNet Fix 2.4.0
Universal SafetyNet Fix Magisk module Magisk module to work around Google's SafetyNet attestation. This module works around hardware attestation and recent updates to SafetyNet CTS profile checks. You must already be able to pass basic CTS...
forum.xda-developers.com

Having the same issue with my OnePlus 10 Pro, even after saftynetfix
I'm running the OnePlus 10 Pro NE2213 (Global)
Bootloader unlocked / OEM unlock
Rooted, Magisk 24.3
Magisk: Zygisk enabled, deny list off - Google playstore, Services, Framework, Hulu, Disney+
Magisk modules: Shamiko,liboemcrypto disabler, MagiskHide Props Config, Universal SaftyNet Fix, Zygisk LSPosed
LSPosed modules: (mock mock location) Hide Mock Location, Hulu, Disney+
Google Play store shows as 'Device is Certified'
I've disabled Private DNS and disabled Adaway

MAGISK 25.2 - SafetyNET not passed

I have Redmi Note 7.
It was running on xiaomi.eu_multi_HMNote7_V11.0.6.0.PFGCNXM_v11-9. I had magisk installed, there were no problems with root detection.
I installed xiaomi.eu_multi_HMNote7_V11.0.7.0.PFGCNXM_v11-9 using OrangeFox Recovery.
Then my problems with Magisk began. I uninstalled magisk completely via orangefox recovery and install again v21.4 as zip. Finally I updated magisk manager and magisk module with success and now it is latest version 25.2. I can't check safetynet via magisk app, cuz there is no option, so I used app called YSNAC. It shows: Basic integrity: failed, CTS profile match: failed. I perform hide Magisk app, named new app as "Settings", but the old Magisk icon did not disappear (I don't know if it's ok).
I activate Zygisk and enforce deny list and set deny list (banking apps, play services, google play store).
I installed modules like MagiskHide Props Config and Universal SafetyNet Fix.
BTW. Why there is no more online searching modules via magisk manager?
Root working ok.
I don't know what can I do more. My banking apps detects that I have root.

mcichy10 said:
I have Redmi Note 7.
It was running on xiaomi.eu_multi_HMNote7_V11.0.6.0.PFGCNXM_v11-9. I had magisk installed, there were no problems with root detection.
I installed xiaomi.eu_multi_HMNote7_V11.0.7.0.PFGCNXM_v11-9 using OrangeFox Recovery.
Then my problems with Magisk began. I uninstalled magisk completely via orangefox recovery and install again v21.4 as zip. Finally I updated magisk manager and magisk module with success and now it is latest version 25.2. I can't check safetynet via magisk app, cuz there is no option, so I used app called YSNAC. It shows: Basic integrity: failed, CTS profile match: failed. I perform hide Magisk app, named new app as "Settings", but the old Magisk icon did not disappear (I don't know if it's ok).
I activate Zygisk and enforce deny list and set deny list (banking apps, play services, google play store).
I installed modules like MagiskHide Props Config and Universal SafetyNet Fix.
BTW. Why there is no more online searching modules via magisk manager?
Root working ok.
I don't know what can I do more. My banking apps detects that I have root.
Click to expand...
Click to collapse
I have the same issue since today on Galaxy s21 Ultra!

I decided to uninstall completely Magisk. Unfortunately SafetyNet still doesn't pass, banking aps not working. Only thing I can do is wipe all data, format to factory and install MIUI again. Maybe I'll try MIUI 12.

mcichy10 said:
I decided to uninstall completely Magisk. Unfortunately SafetyNet still doesn't pass, banking aps not working. Only thing I can do is wipe all data, format to factory and install MIUI again. Maybe I'll try MIUI 12.
Click to expand...
Click to collapse
try using Shamiko together with Zygisk and without forcing the denylist

I tried this before with zero success

With the MagiskHide Props config, you need to open a terminal, enter "su" and then "props". Then set the fingerprint to the certified one.

neelchauhan said:
With the MagiskHide Props config, you need to open a terminal, enter "su" and then "props". Then set the fingerprint to the certified one.
Click to expand...
Click to collapse
yup, I did that. Didn't work for me.

I performed "Format Data", flashed latest MIUI for my device, installed Magisk, Hided Magisk, activated Zygisk, Forced deny list and it's working well.

i tried like 4 different ways and NONE work
Universal SafetyNet Fix (didnt work)​zydisk (didnt work)
denylist (didnt work)
magiskhide proops config (didnt work)
i have a mi 9 with miui 13+android 12
EDIT: it just takes trial and error, had to try a couple of different devices and one that worked for me was mi 9 europe

I can pass safety net on magisk 25.2 . I don't install magisk hide props. I have few things installed and a modified Verison of universal safety fix and I am using zygisk.

Alot times I forget about messages on here . Telegram me if I don't get back to u on @Assassin4Hire

GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
Flash this.
Enjoy.

yot2703 said:
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
Flash this.
Enjoy.
Click to expand...
Click to collapse
I tried this workaround in my Samsung SM-G531H with Android 7.1 and I tested it with the previously mentioned YASNAC app, and the SafetyNet Attestation tests (Basic Integrity and CTS profile match) PASSED!
Now, I'm able to use my bank app (BBVA) Thanks.