yashsingh1/xdaforums huggingface dataset:
[Magisk] Nergal di Cuthah:
Play integrity, which replaced safety net, gives me 2 out of 3 as it should. P6P august update mod 2.4.0 mod 2.0 no other modules no lsposed no shamiko, but i haven't tried gpay since the update since i don't use it (it let me enter a card with no problems a few months back)

Edit i went into gpay and tapped "tap to pay" and all worked (nothing to actually tap as I'm home)
[Magisk] Thebear j koss:
Yeah I've never had a problem, but after updating to the August A13 build I started getting the dreaded your device can't use tap to pay pop up. I tried the usual wiping data of all the usual google apps, flashing 2.4.0 mod 2.0 which failed everything for me, flashing back to mod 1.2, mod 1.3, and tried the google play fix posted above. Best I can get is basic integrity. GPay has come in handy when I the gal has the bank card and I forget she has it. Oh well, A14 isn't far off, I'll just wait it out and see what happens with that.
[Magisk] sawdoctor:
Not seen anyone else with this issue on pixels. I recently updated to the android 14 beta on pixel fold, using safety net 2.4.0 1.3 I pass device and basic (think 1.3 is preferred version for pixel). I have had xposed mods like app settings reborn cause root detection though
[Magisk] pndwal:
Google Play Services is removed from denylist on reboot if enforced since we got that (Magisk 24+) and Zygisk because denylist breaks USNF as unlike a proper hidelist it reverts (denies) code injection modifications etc in listed processes and USNF needs to inject fake keystore values into GMS (Play Services) droidguard process...

Try with all modules disabled except @Displax modded USNF and remove all Google items other than G Pay/Wallet from denylist... Ensure Zygisk= Yes on Magisk homepage...

Also, please say device, ROM/OS, kernel if custom, other mods (TWRP, recovery flashed mods etc)...

🙃 PW
[Magisk] Thebear j koss:
So with 2.4 mod 1.3 I can't even get basic integrity. I am on stock rooted A13 with Magisk 26.2, zygisk-lsposed 1.9.1, AOSP mods, Iconify, revanced mods, pixel launcher extended. Never had any issue for over a year now with any tap to pay or banking apps. Always passed basic and device integrity up until the August security update. I was on 2.4 mod 1.2 at that time and started getting the device doesn't meet qualifications for tap to pay. I tried 2.4 mod 2.0, nothing passed. I tried the google play fix, passed basic. Tried 2.4 mod 1.3, nothing passed. Tried going back to 2.4 mod 1.2 passed basic. Just tried 2.4 mod 1.3 again after clearing app data to all the usual google apps, and only having gpay/wallet on enforce deny list. Doesn't pass any integrity. Don't know what google did on the August security update, but they completely broke tap to pay for me after having no issue ever. Never hid Magisk, never used the hide props mod. Have always only used stock rooted with latest magisk and lsposed zygisk. The only thing I did different was iflashed the OTA using Pixel Flasher instead of the update zip because my laptop kept crapping out trying to flash the update zip. That's all I can think of and although it's pretty handy, it's not killing me that tap to pay doesn't work or that I don't meet device integrity. I tried everything besides a complete wipe which is out of the question unless I screw up and I have no other choice.
[Magisk] pndwal:
So did you:

?... If not, keep 1.3 mod USNG and try...

If successful, turn modules on again one by one to narrow down culprit...

If no change, try uninstalling USNF, reboot, clearing Google Play Services data, installing modded USNF and rebooting again...

😶 PW
[Magisk] Thebear j koss:
Yeah. I'll wait for the September update. That's it he next time I will be disabling everything. Gpay is a nice convenience, but I lived 40+ years without it...
[Magisk] pndwal:
So "yeah" as in you did the simple disable modules and reboot test (and Zygisk = Yes)?... So what result?

... Or do you mean you're not going to try it before a ROM update? 🤔 PW
[Magisk] Thebear j koss:
Waiting for the September security update. I will be disabling everything when I update. I did disable all mods for the august update though. Also never had any issues previous to the August update. Have been using the same mods for months now.
[Magisk] pndwal:
Well something's changed and very often a mod has become incompatible... PW
[Magisk] avraum:
Working great! Thank you!!!
[Magisk] 2019registered:
Hi, i have the following device:

Oneplus 9 Pro

Android 12

Security Patch Level 2022-05-05

Google Play 23.34.14

Magisk app: 26301

Magisk (module?): 25205

Magisk modules installed: Systemless Hosts, Safetynetfix 2.4.0 kdrag0n

Basic integrity: pass

CTS profile match: fail

Meets_device_integrity: fail

Meets_basic_integrity: ok

Meets_strong_integrity: fail

I have an issue with one app not starting assuming because not passing the safetynet check although being in the denylist of magisk.

I read the 4 steps in the first post but would need a more detailed step by step guide on how to move from the current safetynet version to this modified/forked one.

Thanks
[Magisk] zgfg:
It's not Magisk "module" 25205 but Magisk (itself) 25205.

Btw, usually when you update Magisk app, you should also update Magisk

Original KDragon's USNF module is well behind. Didn't you try here with the latest Displax fork of USNF or with Play Integrity Fix modules. Try them. Try also with the updated Magisk (although, Canary 26301 does have some issues, but now you would hardly update Canary to 2620x). You may switch Magisk app to Stable and update Magisk to the latest Stable

Also, find the Play Integrity Fix thread on XDA and see what the others discuss there

Of course, you could not pass Strong Integrity (for that, Bootloader must be locked, and phone must not be modded) but you should make to pass Device and Basic Integrity

But the apps looking for 'root' do not rely only on Play Integrity. They use other methods to detect and you may need to use additional methods to spoof. That's out of the scope for USNF and Play Integrity Fix (although in the Play Integrity Fix you may find more about and read about additional hints). See eg in the Magisk general thread...
[Magisk] PhantomZwei:
In case anyone uses the Microsoft Intune Company Portal app (for outlook, teams at work), they recently updated the app and is detecting root. New version is 5.0.5981. I was able to revert back to the previous version 5.0.5975 and working fine again. Put it on do not auto update..so we'll see how long it lasts
[Magisk] spida_singh:
The latest version works fine if you use Alpha with Shamiko
[Magisk] supermansaga:
John Wu's magisk alpha? Canary is the only thing I have been comfortable trying. Also how to update from Canary to Alpha? Thx
[Magisk] zgfg:
No, Alpha is not from TJW, it's not from the official Magisk channel

Magisk Alpha is a fork by Chinese developers, contributors to the official Magisk development, where a subgroup of them also own the development of Shamiko and LSPosed modules (hence, they are not outsiders!!!)

They have also developed Momo, and eg Native Test, hence no wonder that you cannot fully hide 'root' from those detectors

However, they don't participate on XDA, they have TG channel exclusively in Chinese (and it's tricky to obtain the invitation link), and Alpha, as well as Shaniko and LSPosed (and Momo and Native Test aka Minotaur) are not open source projects.

And, be aware that telemetry is built into the Alpha

Bellow is the XDA thread about Alpha, if you have further questions please ask there (here it's OT), that other Alpha users (but not Alpha developers) could answer you:

[Discussion] Magisk Alpha (Public Released) fork - @vvb2060

This is the spot for the General Support Discussion of Magisk Alpha "Public Released" fork created by @vvb2060. Disclaimer: This Magisk Alpha fork is not supported by @topjohnwu and is not an official channel for him. Use at your own risk...

xdaforums.com

Btw, take a time to read through the thread. Although things are constantly changing, first few pages from the spring of 2022 are interesting from the historical point of view. Also, you will find different opinions about the closed source development, telemetry (later introduced), their forcing of Chinese on TG channel, user experiences when they tried to argue about something with them, etc

In short, it's for mavericks, not for the ordinary Magisk users
[Magisk] Thebear j koss:
You can just say it, they're total @$$3$ on their telegram channel. Good luck if you have an issue or a question. You will either be completely ignored which is fine or you will be torn apart by about 3 billion Chinese followers. Don't even bother trying to use translate either, they all use different dialects...
[Magisk] V0latyle:
And this is why we discourage TG on XDA
[Magisk] mrjuniork:
Mod Info:

Thread has been cleaned.

Those insults aren't appreciated and condoned on XDA.

Remember the humane and respectful approach, it's the better way 🙂

Have a good one all of you 👍🏻

Cheers,

mrjuniork (FSM)
[Magisk] pndwal:
🤔

Private TG group, only 935 members ATM... Mostly cordial banter when not debugging blow by blow... mostly typical uni students/Android hackers/modders in various fiercely competitive computer science studies it seems... Occasionally they give as well as they take... follow it or don't! 🤷‍♂️ PW
[Magisk] ninjakira:
Howdy do I just have a question cuz I haven't updated myself on stuff Ina bit lol I'm currently on the Motorola edge 2021 ( code name berlna) and I'm technically still using Magisk hide props config on stock rooted a13 using the moto edge 2020 (codename racer) fingerprint, do I need magisk hide props config anymore lol, on top of this module im using the magiskhide module from huskyDG, also on magisk beta 26.3
[Magisk] pndwal:
Not sure why you needed MHPC fingerprint with stock ROM... are you using 'force basic ' function too?

You can use this module without MHPC as it sets a (very old) fingerprint and mismatched model props targeting GMS droidguard/attestation process which is better than MHPC globally set props and also allows some devices to meet new Play Integrity APIs deviceIntegrity verdict... If Google doesn't enforce hardware backed server end basic only evaluationType for your device you may have deviceIntegrity with matching fingerprint/security patch values as set by MHPC, but it's likely you'd only pass old S/N ctsProfileMatch that way...

The new USNF (and newer PIF) solutions with work fairly universally on their own and are better for the current PI API anyway... Nb. If not setting props globally for other purposes you should disable MHPC as sensitive prop function will still operate by default (ie. when module is active but not configured) and is duplicated in USNF anyway... 👀 PW
[Magisk] ninjakira:
You fully lost me I'm not going to lie lmao so yes or no lmao? I just needed basic and hardware to be ok cause I wasn't able to play Pokemon go without those 2 lol
[Magisk] pndwal:
No...

But generally USNF needs Zygisk for the module... not sure why you use MagiskHide module, or if use Zygisk...May be able to use Riru version...

What do you mean basic and hardware?

Nb. If Pokemon Go is current, it won't call SafetyNet anymore; it will have migrated to Play Integrity deviceIntegrity enforcement with the new requirements I mentioned above, just like banks...

If it hasn't been updated, the game will become unusable in Jan 2024 when Google ends SafetyNet API support for apps that don't have Play Integrity compliant versions. PW
[Magisk] ninjakira:
As long as those two are green still I'm ok lol, I use the magisk hide module cause it works better for some certain use cases that I'm technically not allowed to talk about on XDA lol, usnf needs zygisk which I still have on specifically for a module that needs it on lol (screenshot is taking after removing mhpc) so I'm good lol (also I meant device not hardware lol)
[Magisk] pndwal:
Yup... Perfect...

MHPC global prop spoofing can interfere with USNF so it's best to lose that... PW
[Magisk] ninjakira:
I will say also sorry if my text sounds aggressive or sarcastic in some way I am just very tired and it's been a difficult night lol, thank you for the help tho fr
[Magisk] 2019registered:
Hi,

thanks for you answer.

I was able to update magik and magisk app, no effect on safetynet though as expected.

In regards to the following fixes I would kindly ask for a thread-link and a more detailed step by step guide. The one mentioned in the first thread is unfortunately not enough for me:

latest Displax fork of USNF

Play Integrity Fix

What do I have to do with the attached zip-file of the first post? Magik->Install->Install to Inactive Slot?
[Magisk] zgfg:
Google eg for

xda play integrity fix

to obtain the link to the thread - screenshot

Please google for how to install Magisk modules - it's described elsewhere and that's basic knowledge you need for all modules (if you don't use modules, what's the point of installing Magisk)

DO NOT use TWRP, installing modules has nothing to do with active slots and so

Use Magisk app, Modules tab, click to Install module from local storage, point to the downloaded zip and reboot when it finishes. As simple as that
[Magisk] 2019registered:
@zgfg big thanks for taking time for this additonal explanation. I was able to get the app running using the XDA play integrity fix. Have a nice sunday.
[Magisk] BavoV:
I have a RPI 4 wit android tv lineage OS 20. Magisk 25.2 installed(later is not available atm) . I tried your module, but it does not pass CTS in YAsnac.

basic integrety is passed.

What are my options ?
[Magisk] chiteroman:
Try my module:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix-updated-fork.4607985/

Or try 1.3 version of Displax:

Release v2.4.0-MOD_1.3 · Displax/safetynet-fix

Changelog: v2.4.0-MOD_1.3 Fix "stat /sys/fs/selinux" access time reading. Also removed archaic MIUI cross-region shenanigans. Thanks to PR by aviraxp! Ignore props changing on Xiaomi.eu. This fixe...

github.com
[Magisk] phone_etix:
Chiming in to say this currently works for me on a OnePlus 5 running LOS 20, thank you very much to the devs, the original USNF didn't work with adding a bank card Google Wallet but this did the trick!! I disabled MagiskHide Props Config as advised.

For any Singaporean residents here... it still doesn't seem to work with Singpass (app just force closes every time before I can even sign in). I've resigned myself to having a burner phone running 100% locked stock, or a cheap iPhone, just to use that app because it's not worth trying to figure it out... especially since I live overseas and rarely use the app.
[Magisk] D4oS:
This is great! I just wish the older version github main page would somehow point here, since I've been there twice before I finally decided to look again.

I added my Revolut card to Google Pay and I finally can generate discount codes in the McDonald's app :ROFLMAO:
[Magisk] nek46:
Greetings from greece :)

small feedback ,device htc u ultra custom rom, leedroid ultra android 8

magisk version 26.3 safetynet fix 2.4.0 from post #1 run safetyNet attestation with YASNAC all pass ok(y)

added my bank card in the google pay, and hide of course .. all ok.

shopping test tomorrow Sorry for my bad english

Τhank you very much:)
[Magisk] OldNoobOne:
I tried Majisk Delta BTW & it seemed to have a mind of its own (some AI thingy going on i guess LOL), It seemed to popup anywhere everywhere and seemed like it was like device administrator LOL. I had to reflash to get it out. Hmm..chynaware?
[Magisk] zgfg:
You are quoting my mail that was an answer to somebody what is Magisk Alpha and then you write about Magisk Delta?!

MagiskmDelta and Magisk Alpha are totally different forks

And Magisk Delta (you write in your mail) is not Chinese but Vietnamese developer

Besides, I run Delta (again, Delta is not Alpha) on one of my phones and it is excellent. It has nothing AI. But you need to set it properly. If interested, please read the posts in XDA Magisk DELTA thread. There, you can also find where to download Delta, etc
[Magisk] fifi49:
I using magisc 26.3 and safetynet 2.40 mod 2.0. all app incl gpay wrorking fine only since last week the banking app card complete control has new update what decect now the root of my device. I have searched a lot but so far for this app not find any solurton. does anyone has a solution for this app?
[Magisk] pershoot:
you can try shamiko module if doing purely with magisk, as-is, is not working for it / you.
[Magisk] pndwal:
Please say device...

@Displax latest 2.0 mod hasn't worked for devices launched with A13 for some time due to experimental shipping level setting... mod 1.3 should work for most devices, but still sets shipping prop globally so breaks VoWiFi etc for some A13+ LV devices...

For A13+ LV devices, @chiteroman's PIF module should work better as I believe shipping level prop is set to target GMS processes only on these devices rather than changing this globally...

Nb. @Displax was intending to publish an update with targeted shipping setting also... I don't know why it was never produced.

👀 PW
[Magisk] fifi49:
if check the Safetytest it pass the check but only on the new update of the banking app card complete control it seem they using an advanced root detection. all other banking app working well expect this one. i have also tried Shamiko but also for this app not working. it´s weired.
[Magisk] pndwal:
Still not sure what you mean... Again, please say device... also, do you have passing Play Integrity API DEVICEINTEGRITY verdict?... And I don't think you've even said which bank app is giving issues... 🤔 PW
[Magisk] fifi49:
My device Xiaomi 11 with Android 13, i have passed Play Integrity API. My Banking app is from Visa Credit card it´s called Card complete, you need to release payments with Visa Credit card. It worked until the last app revision perfect but since the new update the app say ma device is rooted.
[Magisk] OldNoobOne:
Thankyou, (I know Majisk Delta & Alpha are different) Yes its my mistake to post on wrong thread but I was just sharing my expirience, actually the majisk Delta that I was using was baked into a Custom ROM that I had used and it seemed to be bhaving wierdly (like AI) so I guess the Dev who had made the ROM must have further tweaked the Majisk Delta perhaps. I'm okay with standard majisk thanks for the help though. Sorry again.
[Magisk] pndwal:
This App?:

https://play.google.com/store/apps/details?id=com.cardcomplete.completecontrol

🤔 PW
[Magisk] fifi49:
Yes exacltly this app. :-D
[Magisk] pndwal:
Working to this point:

using Alpha fork (builds WIP native bridge loaded Zygisk from LSP devs)... So you may need this, or it may be something else...

🤠 PW
[Magisk] fifi49:
Hi, yes this looks fine. Cause on my phone before come a pop up window and say my phone is rooted. Where i can find magisk Alpha fork? I searched many link but not successfully find a download version. After install i need turn on ZYgisk and select at deny list this app right?
[Magisk] fifi49:
Hi i have managed it! Many thanks for your great help!! It worked again.

:-D
[Magisk] Kojiking:
Samsung A54 (security patch 01 Aug 2023)

Magisk 26.3 Stable / Zygisk (active)

Enforce Denylist (not activated)

Modules : MagiskHide 1.10.3, Seamless Hosts 1.0, Universal SafetyNet Fix V2.4.0-Mod 1.3

YASNAC

Basic Integrity (Pass)

CTS Profile match (Pass)

Google Play Store

(Device is certified)

Able to use government app and digi card payment app. Still no luck with digi banking app. But I can use Web base Internet banking, so it's no biggy for me on this.

Just discovered that some how, these app kinda will detect my rooting. I need to clear those app cache and data then restart the phone to be able to use them again.

Any idea what's a permanent solution for this issue?
[Magisk] fifi49:
use magisk alpha, zygisk active, denylist not activated. should work
[Magisk] nadeemakhtar1994:
Two apps - Icici Imobile and Indusbank Indusind detecting root. How to bypass? Check
[Magisk] aygul12345:
@Displax can I support your project by a donation?
[Magisk] ZgredekLCD:
Hey, I have a Xiaomi Mi 9 with ROM Xiaomi.eu and after install it (+ magiskhide) still I have a "HARDWARE_BACKED", what I miss? I'm trying to fix a mcdonald app :D
[Magisk] Nergal di Cuthah:
Only bootloader locked unadulterated systems will pass hardware backed, asked and answered millions of times in this and other threads
[Magisk] zgfg:
Uninstall old (deprecated) MHCP and if needed install latest SafetyNet Fix from Displax

Btw, read posts about v,9.0 here in this thread (couple of last pages)
[Magisk] zgfg:
No luck with v9.1. Please wait / Checking until timeout

Spoiler content hidden.
[Magisk] pndwal:
Which version did you install?...

Useing USNF 2.4.0 mod 1.3 should be best for your device (avoid mod 2.0), but XiaomiEU's integration of SNF if fraught...

Despite what readme for USNF says, you don't need MagiskHide Props Config module... is that what you meant you installed?... Or do you have Magisk with MagiskHide???... Nb. Configuring a print in MHPC can break new Play Integrity DEVICEINTEGRITY verdict and cause conflicts as MHPC sets props globally rather than targeting GMS processes only...

You should pass SafetyNet w/ BASIC only evaluationType, but should also use a Play Integrity API Checker to see if have DEVICEINTEGRITY also now since S/N is deprecated...

If using USNF 2.4.0 mod 1.3 alone doesn't fix (w/ nothing Google in denylist other than Google Pay/Wallet), then (assuming XiaomiEU ROM is up to date and was passing PI DEVICEINTEGRITY with integrated spoofing before installing Magisk) you should be able to uninstall all modules and simply hide root from GMS main and Droidguard processes, ie Google Play Services, com.google.android.gms and com.google.android.gms.unstable , by adding these to denylist and vola!...

If no dice, remove Play services from denylist and install @chiteroman's PIF module... This may fix bad shipping level (first API) value if ROM still tries to pass STRONGINTEGRITY by exploiting settings for erroneously passing Pixel 2 which Google have now fixed... PW
[Magisk] pndwal:
FWIW, latest good build from @Displax is 2.4.0 mod 1.3 (apart from using non-targeted shipping level spoof). PW
[Magisk] EthanG01:
Is there some more detailed steps for complete beginners somewhere on how to do this? I don't get how to do this at all as I'm a newbie to rooting and android modding. Being a visual learner naturally it makes it even harder for me to properly understand what all this means and how to do it properly.
[Magisk] nate4551:
Had to create an account just to thank you!
[Magisk] sawdoctor:
A little bit more information if you can. Which device are you using and which android version then we can make sure you flash the correct safety net version, this one seems to work for most people .

Also which magisk version are you using and what do you need help with? If root is being detected by a certain app then it's better to create a separate thread for it
[Magisk] EthanG01:
Moto x40 with magisk 26.0 I believe I am waiting for the device to be delivered so I don't have it as of yet. I'm hoping to use this bypass to get Halifax banking app working and Google pay.
[Magisk] sawdoctor:
Google pay should work with safety net but Halifax will probably need adding to deny list and Magisk hiding to work. There are so many options shamiko, magisk alpha HMA etc but for me tsb, Lloyds and MBNA all work with just Magisk canary (hidden), safetynet and the apps added to denylist (enforced).

Best advice is just read through the magisk forum especially threads about banking apps
[Magisk] EthanG01:
Thank you I really appreciate it! As a complete beginner it can be overwhelming all of this from not knowing anything aha. I'm hoping to do this given Motorola's, reputation for short term updates & wanting to use LineageOS.
[Magisk] EthanG01:
The play integrity fix do I install this as well as the safety net fix?
[Magisk] m0han:
@chiteroman wrote earlier:

if you device has come out with Android 13+ you should use this together with the one from Displax.

That post with 11 likes has since been edited and is now 'empty'. No idea why. https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89084404