yashsingh1/xdaforums huggingface dataset:
[Magisk] faizalkojang:
Before opening Google Playstore, make sure Google Services on the device is stopped. then delete app data play service & google playstore. delete all modules that are read by the Google server, including lucky patcher, lsposed, and others. enter magisk--mark app as unreadable root: 1. Google Play Services 2. Google Play Store 3. device tracking 4. Google Framework then use mood install via magisk, then restart the device. Once the device is on, make sure the "pass" status is listed in the Yasnac SafetyNet app. then turn on the device's Google Service, enter Google Playstore then log in. now see the results... good luck my friend
[Magisk] Nergal di Cuthah:
Many things here, but most important is YASNAC (and safety net in general) is deprecated. you need to check play integrity (preferably with the checker built into playstore developer options).

All you're solving here is playstore certification, from what i see, which can be achieved by reaching basic pass on PI. There are other considerations that this (deprecated) mod takes care of, including gpay/wallet nfc payments.

Please take some time and read the Play Integrity Fix thread's first post and the posts linked in it. The Safetynet mod by displax will not get you device pass in PI.
[Magisk] Ikarisdruig:
I back this up, I did the usual method to make this work like any other time, but it still doesn't want to be certified, it's either the new builds have found a way to patch this, or that the module gave up the ghost.
[Magisk] Andoreid:
Hello, are there any plans to make usnf work with android 14 ?
[Magisk] Nergal di Cuthah:
Usnf is dead use play integrity fix or play integrity fork. We're fishing for passable fingerprints
[Magisk] tinbilly:
My phone is a Moto G8 Power on crdroid 7.19 with Magisk Alpha. I cannot pass SafetyNest attestation with the latest release (v2.4.0-MOD_2.0). However, version v2.3.1-MOD_3.0 does the trick. So weird...
[Magisk] kidronvalley:
hi, really strange,

on microg have signature spoofing , also passing safety net, but a special app inbank notofy is not working
[Magisk] Mowca:
Hello

Samsung s10e

Lineageos 20, Magisk 26.4

I still have "Device is not certified"

when I add it to the Google Play service deny list in Magisk, after a while it deselects itself. Does SafetyNet Fix V2.4.0 still work?? how to wipe GMS data??

how to repair play certificate?
[Magisk] Nergal di Cuthah:
Couple short answers

Play services is removed from deny list by this module and its descendants (which I'll get to next) so that's what you're seeing there.

Safetynet fix no longer works (for many months now). You need play Integrity fix or play integrity fork. It is a more detailed not plug and play approach. You must find what we've termed a "fingerprint" or "footprint" of an older device to spoof play integrity checks.

So first you'll need to research. Read the thread on integrity, at least the first post and the last two days of posts (it's a giant thread but some detail are needed).

Pi thread pinned to the top of magisk board

How to find a fingerprint https://xdaforums.com/t/how-to-sear...scussion-for-complete-noobs-from-one.4645816/
[Magisk] zfk110:
after flashing my S9 Plus shows as Google Pixel 2 on, is there any way I can fix it back to S9 Plus?
[Magisk] Nergal di Cuthah:
Uninstall this addon and it should go back (may need to clear gms and play services cache or data don't remember). The new Play integrity fix module, read the post above yours, handles this more eloquently and only spoofs for gms.unstable play integrity checks. But yeah read the post right before yours :)
[Magisk] :
Quick question (I hope); I'm running magisk 26.4 with hideprops, PIF & Shamiko. All works fine; banking apps, wallet, etc. Latest Shamiko update says it needs canary. IF I install that, will it mess up PIF? I'm kinda thinking of taking the 'if it aint broke, dont fix it' line here.
[Magisk] simplepinoi177:
It kinda depends on your version of PIF....but I can't imagine updating Magisk to canary messing up PIF...

I mention the version of PIF because I've read somewhere that chiteroman kinda regards his version releases like a beta -- which is why you see a lot of quick version lifespan (14.6 pretty much went straight to 14.8) or how you'll find so many complaining how it doesn't work on 15.1 but if they go back to an older version it works for them (primarily 14.6 because they are implementing the same fingerprint...!

I might say it might've been different if this was an Xposed/LSPosed module, but I can't imagine Magisk modules are that much affected from stable to canary -- from the few interactions I've seen discussing canary issues, it's usually trouble implementing/retaining/detecting root than it is with interaction with the modules. But don't take my word for it....

In the end, it comes down to how much you really want to be implementing the newest version of Shamiko -- I just read somewhere that they figured out a bit of something that was a leak showing up in root detection that they plugged. But as you said, "if it ain't broke, don't fix it", unless you've been waiting on Shamiko to help hide for something in particular, having the "latest and greatest" might not be so meaningful; especially if you consider how much you don't want it to interfere with PIF....
[Magisk] :
That's it really.

Tbh, I don't know how much of a part each module plays in delivering the overall package (of being able to use wallet payments and banking apps) but I assume PIF is the bulk of it. So I'll leave well alone unless/until something stops working. Then, and only then, will it get fixed.

I've found in the past that when wallet stops working, the next phase of whack-a-mole starts and there's invariably a new release of something that addresses the issue. Click install on the module update and I'm away again.

(Btw, I'm on 15.1 PIF)
[Magisk] shoey63:
15.1 has stopped providing new prints.

Better start looking for one

PlayIntegrityFix/module/pif.json at v15.1 · chiteroman/PlayIntegrityFix

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com
[Magisk] chiteroman:
v15.1 provides v14.6 fingerprint

That code is for v15.2
[Magisk] :
Thank you for clarifying that, I was a little confused as I felt sure I'd used the wallet since updating to 15.1.

Fingerprints is/are a new game for me so I'll hang fire on updating until I understand it all a little better!
[Magisk] simplepinoi177:
Yeah...it was addressed during the night for me, but as they said, you can't expect the new updated version of PIF to "addresses the issue" out-of-the-box anymore.

If you don't mind the uncertainty of when you might unexpectedly fail, you can look into Play Integrity Next where it updates the fingerprint sourced from where chiteroman was getting his since 14.3 or something (xiaomi.eu custom ROM) without needing to download & update the actual new module version. But if you want a substantially more consistent and keeping-as-expected experience, finding your own custom fingerprint (rather than it being pulled and/or embedded) yields better results (those who have done it this way [include me] have yet to have their fingerprints banana'd/burned -- going for longer than a month).
[Magisk] bexiglass:
Hello just for information in case someone gets PlayIntegrityFix not working for Google Wallet :

Adding Wallet to DenyList in Magisk is not enough to solve this issue. You have to search for "google", and tick every app using any google services AND every subservices in these apps (need to deploy the apps to be sure)

That worked for me after rebooting.
[Magisk] Jonog:
Mine is working but with playintegrity 'next". Im too thick for doing my own finger print. Just letting ppl know. Thanks
[Magisk] tanjiro_kamado:
Can you give a screenshot of what have you added to the denylist?
[Magisk] pndwal:
It's just wrong advice... Nothing Google is needed in DenyList, not even GPay/Wallet, but won't hurt if that's added... None of these look for root, and adding some can break functions like webview...

PIF hides root from GMS main and DroidGuard processes itself (USNF began doing this with first Zygisk builds) and will remove GMS processes on reboot if DenyList is enforced to fix configuration as adding these breaks essential PIF functions if DenyList is active...

There may still be edge case value adding some Google apps in denylist for use with Shamiko (proper hiding) module (where DenyList is not enforced) to allow Shamiko feature that fixes custom font module issues to work, but I believe most font modules now work around these issues anyway.

👀 PW
[Magisk] :
@pndwal thank you for answering helpfully :)
[Magisk] :
It's what I did too. At least temporarily until I get my own fp.

I was playing with Pixel Flasher (it does indeed look a veritable swiss army knife of a tool!) and it's PIF module but I wasn't finding a single pf that would pass. I was getting quite disillusioned tbh and back-burnered it, resorting to the PIFNext method detailed above (which, to be clear. works fine).

Then with my last effort I noticed that Pixel Flasher wasn't playing nice on my Linux Mint laptop and I couldn't see the console window (I didn't even know it was there at first!) so couldn't see error messages. Then I noted I was getting a message (possibly an error) flashing up briefly on my my phone. So I clicked a bit and revealed a bit of the console window, cut and paste and here's a snippet....

bash arg: -p
bash arg: gr.nikolasspyr.integritycheck
bash arg: -c
bash arg: android.intent.category.LAUNCHER
bash arg: 1
args: [-p, gr.nikolasspyr.integritycheck, -c, android.intent.category.LAUNCHER, 1]
arg: "-p"
arg: "gr.nikolasspyr.integritycheck"
arg: "-c"
arg: "android.intent.category.LAUNCHER"
arg: "1"
data="gr.nikolasspyr.integritycheck"
data="android.intent.category.LAUNCHER"
Events injected: 1
## Network stats: elapsed time=43ms (0ms mobile, 0ms wifi, 43ms not connected)
tap 1247 928 on the device ...
uiautomator dump /data/local/tmp/pi.xml path on the device ...
Pulling /data/local/tmp/pi.xml from the phone to: ~/.local/share/PixelFlasher/tmp/pi.xml ...
Pulling remote file: /data/local/tmp/pi.xml from the device to: ~/.local/share/PixelFlasher/tmp/pi.xml ...
Return Code: 0
Error: during processing the response from gr.nikolasspyr.integritycheck.

So I'm thinking that Pixel Flasher may have some kind of problem doing what it needs to do to my phone, and that was why every pf I tested failed.

Edit: ok, sorted now AND I have my own fingerprint :D I followed the instructions here and kept on eye on the (very small) console window for messages etc.
[Magisk] Bio69:
Hello 👋

Great, that wirk with Google Wallet and ItsMe (identification app).

But not with BoursoBank (french Bank app).

Regards 😊

Sent from M2102J20SG using ReLabs
[Magisk] marisaleh:
I hope that somebody can help me

I dug out my poco x3 pro, updated it to

latest miui version 14.0.3 with android

version 13, unlocked bootloader and

installed the latest version of twrp ,

rooted from twrp using the latest

version of magisk

I installed the latest mod of safetynet

fix by displax.

When I run the safetynet check, it passes everything

But now I have a problem with the

play store, it says device not certified

I tried everything, wiped data in all

the google play files, store, system

etc etc,,,,,

Does anybody have a fix for this

or can anybody confirm if google

has now made it impossible to

certify devices that are rooted in

this way !!!
[Magisk] sawdoctor:
This module is out of date and no longer supported. You need to use play integrity fix now

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com

Make sure to read the op and then the FAQ thread my osmosis. It seems a little overwhelming but honestly it's not. As you are on xaiomi if you are using xaiomi EU it might be baked in, either way you need to post in the thread i linked
[Magisk] marisaleh:
Thank you very much for getting back

I am using poco x3 pro global ROM

I have just tried the latest version of

PlayIntegrityFix module

The module is asking for :

A certified fingerprint

To move pif.json template to

/data/adb/ to spoof the values

I don't really know how to do this

I was looking for a module that

will do all of this for me

I used an earlier version of safetynet fix

by displax on rooted umidigi pro max 5g

running android 12, and everything passed including play store device

certification
[Magisk] Nergal di Cuthah:
PIF FAQ

PIF FAQ Abbreviations DG = DroidGuard (SafetyNet/Play Integrity) GMS = Google Mobile Services (Google Play Services) PIF = Play Integrity Fix Frequently Asked Questions Q: What is a fingerprint and where does it come from? A: A fingerprint...

xdaforums.com
[Magisk] marisaleh:
I used the latest version of safetynet

fix modded by displax

version 2.4 mod 2

and this is what I got when I

run YASNAC

With all this I am still failing in play store it says device not certified

what else do I need to do, I cleared

all data from the play store and rebooted.

I don't know how to use the other module, it is very complicated, it

talks about obtaining a fingerprint

and spoofing and so on , I give up
[Magisk] Lord Sithek:
You can't do anything else but reading and trying to understand. There is no shortcut here

This module is dead and won't help you at all
[Magisk] V0latyle:
This is because you need to check your Play Integrity verdicts. See this thread:

[INFO] Play Integrity API - replacement for SafetyNet

THIS IS NOT A SUPPORT THREAD. For questions and support regarding how to fix your Play Integrity verdicts, see the Play Integrity Fix thread. ⚠️BEFORE YOU ASK A QUESTION, READ THIS POST AND THE FAQ!⚠️ ****Update 12/11/23**** Google has been...

xdaforums.com

Then ask for help....in that thread.

It really isn't hard.
[Magisk] YairHa:
I followed the guide and it doesn't work

In the manual it is not written that CTS should be passed

Is it necessary?

Xiaomi Redmi Note 13 Pro+

androaid 13
[Magisk] fbirraque:
@YairHa

As already said many times recently...

Read #1 before post:

Thread '[INFO] Play Integrity API - replacement for SafetyNet'
[Magisk] mr_reaper:
Works fine on OnePlus 11 rooted OOS14
[Magisk] seen_bawl:
result for one plus 11

basic integrity pass

CTS profile match fail

how to fix it
[Magisk] fbirraque:
Read the OP at the first page
[Magisk] crypticc:
Hello

@huskydg module from this thread helped me find how my Citibank uk app was detecting root... Portable MagiskHide: https://github.com/HuskyDG/magiskhide/tree/v1.6

This module doesn't need Zygisk. Installing module and with Zygisk disabled instead of Shamiko then banking app works.

I take it to mean app is looking for either Zygote or Shamiko. (There is a subprocess called .... Zygote)

The problem was that @Displax USNF mod fix needs zygist and on reboot without that I fail PlayStore certification and Wallet "device does not meet security requirements", even though banking app still worked.

Enabling zygist to turn on USNF, while leaving Shamiko disabled then allows PlayStore and wallet to work, but Banking app detects root (zygisk) again.

So I think my issue is zygisk which (HuskyDG) magiskhide module doesn't need, but USNF does.

Any ideas how I can have my cake and eat it? USNF and MagiskHide module from the Delta without triggering Zygisk detection?

Thanks,

Chris

P.s. I'd already tried fully paid Storage Isolator / AppOps etc. and had already ruled out file access.
[Magisk] zgfg:
Don't you see that it is named Zygisk, not Zygist?
[Magisk] crypticc:
Fixed thanks. Soz.

Was writing while walking and must've typed incorrectly at some point in the past and then dictionary took care of the rest this time around
[Magisk] ipdev:
Just to give all hope. 🙂

I though I would share a screenshot from my Nexus 7 (2013).

Still marching on even though it is still using the 3.4 kernel. 🙃​

Unofficial Lineage 19.1.

Unofficial OpenGapps 12L Pico (MOD).

Current Magisk (debug +).

Displax's current mod Safety-net fix module.

Cheers all. :cowboy:
[Magisk] pndwal:
Answered here:

https://xdaforums.com/t/discussion-...third-party-magisk-fork.4460555/post-88211201

🤠 PW
[Magisk] Jon8RFC:
I don't recall what exactly I read or where, and can't find info...

Does USNF/MOD spoof get_unlock_ability to 0?

Is that something worth spoofing for the pretentious & undeserving apps which try every trick in the book to deny usage on a rooted device, like municipal garbage collection calendars or LG ThinQ?
[Magisk] V0latyle:
I remember reading something about changing props to spoof GREEN bootloader state: ro.secureboot.lockstate=1
[Magisk] osm0sis:
OooOoooohh, Play Store has their own built-in Integrity checker now!

Tap the Play Store version multiple times to show the developer options, then it'll get added to the main Play Store settings under General!
[Magisk] V0latyle:
Nice. I should add this to the OP of the PI discussion thread
[Magisk] WhoIsJohnGalt1979:
2.3.1 Mod 3.0. lol have not upgraded since, won't be upgrading as long as this works

Labels: [MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY]

Build fingerprint: google/cheetah/cheetah:13/T2B3.230109.006.A1/9623504:user/release-keys

Brand: google

Device: cheetah

Model: Pixel 7 Pro

TestId: dGVzdGluZy1iMGZjN2NlNy03Mzg5LTRiNWYtYTRmZC05NWEzYWI2YmVlNTM=
[Magisk] osm0sis:
Manually forcing the Play Store to do another check might help things show up quicker after fixing a previous fail too. 🙂
[Magisk] Lughnasadh:
Ah, finally. I posted about this back in mid-December (via someone else's Twitter post). Glad it's finally here.

https://xdaforums.com/t/magisk-general-support-discussion.3432382/page-2703#post-87874523
[Magisk] m0han:
Is there a chance that the fail will be 'recorded' and held against the user at some point later?
[Magisk] V0latyle:
Not likely, because this would prevent people from fixing the issue by restoring OEM firmware and relocking the bootloader
[Magisk] osm0sis:
A fail is recorded by Play Services, so you'd still need to wipe app data there anyway. But we were finding a weird lag time between wiping after passing again and apps like Netflix and Leo's Fortune showing up again in the Play Store as installable, so that's what I'm wondering if doing a manual check will make happen more quickly.
[Magisk] rogerty:
Thanks for your information ! Caixabank apps are a unbearable pain in the ass for rooting. I have v1.30 for CaixaBank Sign and I cannot downgrade to v1.29; Where can I get that version from a reliable place ? Thanks in advance...
[Magisk] spider1163:
Apk mirror is a safe place

CaixaBank Sign - Digital sign 1.29.0 APK Download by CaixaBank - APKMirror

CaixaBank Sign - Digital sign 1.29.0 APK Download by CaixaBank - APKMirror Free and safe Android APK downloads

www.apkmirror.com
[Magisk] Daniel_Laixer:
Reliable... that's the problem.

As dangerous and stupid as it may seem, I got mine from here: https://www.apkmirror.com/apk/caixa...ign-digital-sign-1-29-0-android-apk-download/
[Magisk] V0latyle:
APKMirror is perfectly safe, all the apps are signed backups from the Play Store.
[Magisk] Daniel_Laixer:
That's good to hear, because I thought I was taking risks...
[Magisk] V0latyle:
Nope. Perfectly safe.

They have a strict no piracy policy, so they won't even host paid apps.

There are other sites that claim they are just as safe (such as APKPure) but have been known to host malicious and unsigned apps. APKMirror is by far the safest and most comprehensive source.
[Magisk] rogerty:
I had followed the steps, with my mi mix 2, crdroid with Android 13. But the integrity test passes only the two first tests, but not the STRONG one. As a consequence, CaixaBank Sign fails...

Using also MindTheGapps; I don't know what else can I try to fix...
[Magisk] Nergal di Cuthah:
Will only be green in a bootlocked untouched (no root no nothing xda) device
[Magisk] rogerty:
ok, thanks ! but why is it that CaixaBank is still not woorkingg ?
[Magisk] zgfg:
Don't bother about Strong Integrity failing - that's not a showstopper for any app yet

But did you put your banking app to DenyList, are you using Shamiko (MagiskHide on Delta and no Shamiko)?

Did you try with HMA, etc

Maybe you will need Magisk Delta (with MagiskHide) instead of Magisk (with DenyList). Although, there is MagoskHide module to substitute that

All that is not needed for PI API (Integrity tests) but these are additional thing the 'banking' apps look for.

Play Integrity is just the beginning of the story
[Magisk] rogerty:
Ups ! My fault !!! CaixaBank working now; I forgot to add it to the exclusion list after erasing its data...

If this lasts, it's a WIN !!! THANKS...
[Magisk] Daniel_Laixer:
Ah, there you go. I got the quote notification from XDA and I was about to reply with this, lol:
[Magisk] Marco Lino:
Now after this last version, apps that I didn't look for are showing up in my play store history. Could anyone tell me why?
[Magisk] crypticc:
Hello @Displax

Forgive me for being bold but could you take a look here...? Any thoughts about a ptrace version of your modified module

https://xdaforums.com/t/discussion-...third-party-magisk-fork.4460555/post-88237473

[New Idea] Bypass Safetynet by without having to depend on MAGISK · Issue #269 · kdrag0n/safetynet-fix

Maybe you didn't know, most banking apps prefer to detect Riru or Zygisk. No matter we try to hide it, or use closed source module like Shamiko, Zygisk will be detected again time by time. Most use...

github.com

Feel free to tell me to bugger off and do it myself. :-D I won't because I don't have the skills like you and not that practiced in low level stuff since dipping toes into scrolling demos during the 68000 days.

Chris
[Magisk] matadorprobr:
I think it's better to report my issue here because probably on GitHub I will receive no response.

I'm using your module and it works fine for SafetyNet but for Play Integrity, it doesn't work at all. Using Play Integrity API Checker will say that my device doesn't MEETS_DEVICE_INTEGRITY and even MEETS_BASIC_INTEGRITY

and no, it's not my device that is under Android 8 since it's on Android 12 or because my device is not signed by Google because using the stock rom with locked bootloader works fine

and even trying using MagiskHide Props Config doesn't fix it too.

I can even use the Google Wallet app fine and even Play Store will supposedly say that my device is certified with Play Protect so I really don't know why this is happening, tried using other modules, a updated version of MagiskHide Props Config, enabling vbmeta verification again, wiping Play Store and Google Play Services, looking at the comments on this thread, looking the GitHub Issues but nothing works.

Using the stock rom of my motorola edge 30 neo (miami)
[Magisk] pndwal:
Any mods we can't see?... Selinux enforcing? Have you changed to permissive ever?... Flashed any .zips in custom recovery?...

Try with all modules disabled except USNF after wiping Play Services data... PW
[Magisk] Daniel_Laixer:
What

Forget about MagiskHide Props Config, it doesn't seem to help with PI. Also, forget about SafetyNet, the problem has become now Play Integrity.

What is your Magisk Hide list? Do you have Shamiko installed?

Anyway, you could try this, it works at the moment at least on Android 11: https://xdaforums.com/t/module-mod-universal-safetynet-fix.4553699/post-88194951

Just ignore the banking app. May still work with aditional modules aside of the listed ones. Focus on having those modules, clearing apps' data and rebooting when indicated.

Edit: Also, as @pndwal said, no messing with seLinux.