yashsingh1/xdaforums huggingface dataset:
[Magisk] fkofilee:
The issue is with MIUI directly and needs to be sorted on their end.

Not a dev issue.
[Magisk] ripereira01:
I managed to make it work, but it didn't work in kernelsu, in magisk
[Magisk] Paz9:
USNF stopped working today.

this is working on P8P november.
[Magisk] xp0sed_relay:
Hi, I recently installed this because USNF stopped working. I already put GMS and Google Play in denylist but CTS is still failing. Someone knows why? I use LineageOS 20 with magisk
[Magisk] xp0sed_relay:
Sorry for the interruption, but, how you done it?
[Magisk] chiteroman:
Don't add any GMS process to denylist if my module is installed.
[Magisk] chiteroman:
Do you have ZygiskNext module installed ?
[Magisk] CZ.Kostra:
Sorry, but I don't have a chance to test app on A9. 😕 Does RESULT message appear? Is FP placed?
[Magisk] ashish1989:
No
[Magisk] CZ.Kostra:
Can you please test this version? I removed the GWallet health testing part.
[Magisk] osm0sis:
If you figure out which one from HuskyDG's repo made a difference let us know. There are some known issues with a number of the ones he's including there (which is why they were removed from ours or never added in the first place).
[Magisk] ashish1989:
After installing it demanded root and grant overlay permissions but still it can't download PIF. The pif folder is empty.

This error is coming
[Magisk] Iridule:
I'm curious if anyone knows... currently everything is working with Magisk and griffin print... however I'm on moto edge 2020 and my security patch hasn't been updated since 2022 I'm becoming worried and was thinking of switching to lineage OS with android 13 for the security patch. Would the current Magisk setup I have now using the griffin print still work?
[Magisk] zgfg:
Griffin does not work only for you but almost all here use Griffin and pass, with newer phones, newer Android versions, up to A14 (and newer Security patches)
[Magisk] Callliope:
Hello guys, so I'm passing device integrity and basic integrity but still i cannot pass the Google wallet requirements for contactless app, anything else that i can try ?

Integrity fix module installed, i didnt do anything else.

Also i'm rooted with unlocked bootloader.

Xiaomi 11 Ultra with Miui13.
[Magisk] Iridule:
I realize that however if I switch to lineage OS wouldn't the kernel be changed? I read some people have issues passing device on certain kernels using lineage OS...
[Magisk] zgfg:
Check posts in the thread about the LOS, kernel and fixing - but it is not related to Griffin prints (that was my point in the previous answer, and I'm not on LOS)
[Magisk] Koeties:
You also need to add it (and play services etc) to the deny list in Magisk so that it will not see that you're rooted. Then clear the cache (and data if needed) of Play Services and Wallet.
[Magisk] Callliope:
I forgot to say that it is already done, also cache & data deleted from wallet,g services, g playstore. It was working but after 1month suddenly not anymore 😅.
[Magisk] Slim2none4u:
Posted on Play integrity Fix Telegram:

no link...go find it

"Finally, after months of testing, one user discovered the way to pass Strong integrity without repogramming TEE. This means that any user with any unlocked bootloader device can pass Strong, even if it isn't a Qualcomm CPU or he doesn't have the eng rom. I'm trying to port it and do something like "PIF-Strong" module, but I don't know if releasing to public... Google will ban in few hours the keybox and it will be useless. In the next hours I will update BootloaderSpoofer and FrameworkPatch code, but I won't share our unbanned keybox (due obvious reasons). I hope that if any OEM reads this message, they will leak more keyboxes out there "
[Magisk] Vision:
Who write this? 🤨
[Magisk] chiteroman:
Me
[Magisk] Vision:
This is very interesting and important, if you can make this, and finally, we only need is a leak keybox (except the knowledge to patch framework), in TEE discussion we write some similar and with some users this similar idea
[Magisk] sawdoctor:
We'd need a lot of leaked keyboxes as they'd be banned within hours if we all use the same one/included in the app
[Magisk] Vision:
Yeah, unfortunately this is the big weakness
[Magisk] BunnyPig1:
Don't release the keybox. Let Google and others know there is a vulnerability out there circulating, as long as that keybox isn't banned, PI will never be bulletproof.
[Magisk] Chaplan:
Hi all. Using autopif.sh with Osmosis module to get device integrity going. My main device is the Google Pixel 7a on stock Rom. The main goal for me has always been to get Google Wallet working because I rely on Gpay on a daily basis.

There is also this app I use, Repsol Move, an app from a petrol distributor, that on its last update stopped working after root is in place, even with basic and device integrity working.

I use the latest module from Osmosis with everything setup as it should, zygisk and denylist also, and shamiko just in case.

For the sake of testing, since I was using KSU on an older tablet and the app still worked there after updating, I tested with KSU on the pixel and the app just works, even without PIF. I later added Play Integrity Fork and custom PIF, app and wallet working fine.

Don't really know what to make of it, I'm reporting here in case developers find it interesting enough to investigate a bit further.
[Magisk] xcl1pse:
Then it has nothing to do with pif. This thread ONLY provide helping for pif related, not stupid app detecting root. Also I can open that app since I know what it detects
[Magisk] Claus….:
This is awesome news! Please use this thread to update us @chiteroman
[Magisk] chiteroman:
View attachment 6096671View attachment 6096673View attachment 6096672

The keybox has not even lasted 1 week. 🤣🤣🤣🤣

But for some reason Strong is passing. 🤔 (Maybe it's cached in their servers)

I attach the keybox if someone want to play with it.

Also, I'm using my KeyAttestationDemo app with auto update for revoked certs, source code: https://github.com/chiteroman/KeyAttestation

Pull request: https://github.com/vvb2060/KeyAttestation/pull/25

Download apk: https://t.me/playintegrityfix/19

Stop banning keyboxes Google!
[Magisk] Chaplan:
As stated, app opens even without pif. How do you open the app without it detecting Magisk?
[Magisk] Vision:
If not need reprogramme TEE and without eng Rom, and only we modified the framework.jar and we can use Magisk module to replace it.

I'm in 😂🤣
[Magisk] pndwal:
... When I successfully MET Google's STRONG_INTEGRITY verdict using @chiteroman's latest BootloaderSpoofer:

View attachment 6096688

... OH, SO sorry for OT but OP started it, OK? 😜 PW

Edit: To clarify for some, this was simply a humorous take on Google's attitude towards spoofing 'strong' verdicts... Bootloader Spoofer 4.0 beta and both un-banned and banned-but-still passing keyboxes may be real, but I haven't tried tried these at home myself!...
[Magisk] linuxares:
The bootloader spoofer. Isn't dangerous to use since it modify your actual device? Like if you need to factory reset your phone to vanilla. Will it still cause issues?
[Magisk] zgfg:
This is a module like any other. No hard-code changes

Like any other module, disable or uninstall

Moreover, you must select for which app to spoof the Bootloader

However, if afraid and not familiar with, don't use
[Magisk] HippoMan:
Is the latest version you mention here version 3.8? Or is there a later version somewhere?

If it's 3.8, then for me, that version's success or failure has depended upon each app that's associated with BootloaderSpoofer. It hasn't been carte blanche, universal bootloader spoofing, but it only has worked for certain apps on my A13 stock device (Nothing 2) running Magisk Alpha 27002 and LSPosed 1.9.2.

Unfortunately due to my less than ideal memory, I forget which apps. I got rid of a number of apps recently, and I have none right now that seem to need locked bootloader. But for sure BootloaderSpoofer 3.8 worked on some apps and not others when I was using it.
[Magisk] Vision:
I think on TG, updated to 4.0
[Magisk] ashish1989:
Can anyone help, I really don't know what am I doing wrong, can't even pass basic. No bank apps is working.

View attachment 6096792View attachment 6096790View attachment 6096791View attachment 6096789
[Magisk] BunnyPig1:
You have a custom kernel, make sure it's not a banned name.
[Magisk] bdr127:
It's not in the known banned kernel list --> https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-518#post-89308909

I guess it *could* be banned and just not "known" yet.

Aside from that, I noticed you're using osm0sis' fork.... Are you providing a custom fingerprint for it?
[Magisk] ashish1989:
Yes, using a custom fingerprint
[Magisk] bdr127:
Do you know for sure that this fingerprint passes device integrity? Is it a known working print (like the current griffin print)? Or is it just a random fingerprint that you put in there, hoping it would pass? Because there are a ton (at least thousands) of fingerprints you could put in that would fail all integrity.... just like you're showing.
[Magisk] makeyourself:
From memory I thought BASIC should pass once PIF is installed regardless of the fingerprint? Although if my memory has failed me it wouldn't be the first time 🤣.

I have also just started failing both BASIC and DEVICE on a setup that was previously working about 24 hours ago 😤. Not sure what, if anything, I've done to f It up. Oddly Google Pay is currently still working, even after about 24 hours and Wallet is showing "meets security requirements" 😕. I only noticed because the ChatGPT app has stopped working and is no longer showing in the Play Store (like that really needs to check for f-ing Play Integrity!!). I'm also using PIF osm0sis fork with the Griffin fingerprint.
[Magisk] osm0sis:
Well it is the end of the month..
[Magisk] sawdoctor:
Just checked I'm on your fork and griffin print (no point changing it until it breaks) and still 2 green ticks
[Magisk] makeyourself:
It's working again but still none the wiser as to why it started failing. I uninstalled your fork, installed the chiteroman version, rebooted and it passed DEVICE. Reinstalled your fork, ran the playcurl script to get the Griffin fp and that also passed.
[Magisk] badabing2003:
That suggests that the previous print you were using was not good.
[Magisk] zgfg:
Nobody can tell you since we don't know what prints you used. Obviously it was not Griffin

Btw, you can easily experiment by manually changing the custom.pif.json

Hence if you still have that prints, you can put again and retest. You could also run that same prints/Json throuogh migrate script, to find if the prints are wrong or something else. And to check PIF logcat to see if Json was correctly read, etc
[Magisk] makeyourself:
No, it was the Griffin print I was using before! The fact that I was failing BASIC as well as DEVICE leads me to think it wasn't the print but that something odd just happened with my PIF installation. Yes I guess I could have checked custom.pif.json to see if that file specifically had been changed/corrupted but well, unfortunately I didn't lol.
[Magisk] bdr127:
Many prints will pass at least BASIC, but many won't pass anything. Also, if your print is formatted incorrectly or has bad data in it, it will likely not pass anything. Just because a "pif.json" or "custom.pif.json" exists does not mean you'll pass at least BASIC.
[Magisk] makeyourself:
It was passing, I didn't do anything (or not directly to the PIF module) and then it stopped passing. And now it's passing again after reinstallation using the same playcurl script to get the Griffin print and populate custom.pif.json. As I said it seems to have been a bit of a freak occurrence.
[Magisk] bdr127:
FYI, my previous reply to you was not regarding your print situation.

I had replied to ashish1989 about not even passing BASIC, and you then noted that you thought "BASIC should pass once PIF is installed regardless of the fingerprint".... to which I responded to you that this is untrue. Nothing to do with *you* not passing.
[Magisk] CZ.Kostra:
Hopefully fixed in v1.6.1.
[Magisk] ashish1989:
Working good, but its not deleting the old pif when placing new.
[Magisk] zgfg:
Upon you reboot then, (how) do you see both the old and new?

(Whenever some Magisk module is installed, updated, disabled, re- enabled or uninstalled), phone must be rebooted)
[Magisk] ashish1989:
Yes, I see both after reboot too
[Magisk] CZ.Kostra:
If you see 'custom.pif.json' and 'custom.pif.json.bak' then it is correct. Bak is a backup.
[Magisk] ashish1989:
I am using PIF by chiteroman
[Magisk] Vision:
Please not write here about TEE.

If you want for TEE Hacking see here:

TEE hacking

Post about hacking TEE on Android devices. I will post here some useful resources: https://github.com/chiteroman/Reprogram-TEE-on-Qualcomm-devices https://github.com/chiteroman/FrameworkPatch And leaked keyboxes...

xdaforums.com
[Magisk] zgfg:
Please decide which 'PIF' module you want to use and first uninstall the others. They cannot work one over the other. Actually, having two PIF modules instead of one will not guarantee 200% chances to pass PI - to the contrary

Once you decide on the module you will use, then take the corresponding policies do you need your own custom prints and how/where you need to provide that PIF file or not. Instructions can be found in their Readme pages on GitHub
[Magisk] V0latyle:
Except John Wu has made it clear he won't use his position and intimate knowledge of Android security to benefit Magisk...or vice versa.

I don't really understand how this is supposed to work unless he's schizophrenic, or works on a part of Android security that couldn't benefit Magisk. Either way, in his State of Magisk announcement, he didn't intend for Magisk to be used to interrupt, circumvent or otherwise defeat any Android security signals or processes.

He's fortunately left it open ended through Zygisk to allow other developers to leverage Magisk for various means.
[Magisk] pndwal:
I don't think he said he couldn't/wouldn't use special knowledge to benefit Magisk going forward or that Google would have any issue with that either... He said 'MagiskHide' specifically, which is why that had to go (and Magisk had to change in that respect)... This:

https://topjohnwu.medium.com/state-of-magisk-2021-fe29fdaee458

Exactly. 🙂 PW
[Magisk] QuadCore_xRV:
I've got the bootloader spoofer on my Note 9 Running Noble rom 4.0.5, but it doesnt pass strong still. Is there something specific I need to do? My modules are: LSPosed 1.9.3 Zygisk, Play Integrity Fix 15.9.7 Chiteroman, Zygisk Next 4-0.9.2.1, and Boot spoofer 4.0...
[Magisk] osm0sis:
Noble is a banned kernel string. Fix that and you might pass DEVICE if there aren't any other issues with your setup. Go to the TEE Hacking thread if you're interested in trying to pass STRONG.
[Magisk] QuadCore_xRV:
Oh I'm passing Device and basic no issues. Google pay works fine. I just want strong for the flex.
[Magisk] HippoMan:
As mentioned, the TEE hacking thread is where to ask about your issues.

This current thread does not pertain to TEE-related situations.
[Magisk] majorfigjam:
For those who may be interested, I can confirm that the Osm0sis fork works just fine with the Griffin print in a rooted version of Google's very latest Android 15 Vanilla Ice Cream beta 1.2.
[Magisk] pndwal:
Because some have taken my light-hearted Python take (post):

seriously, I've now added a rider:

... Re:

actually, this method doesn't need TEE reprogramming (/hacking):

https://t.me/playintegrityfix/16

... The GitHub link gives Framework Patch tutorial... Despite not now needing a TEE hack, the thread above (and possibly BootloaderSpoofer thread) would be the place to discuss this currently...

This is clearly an ADVANCED PI Fix, and as I've said I haven't (and aren't about to) try this at home myself. 😉 PW
[Magisk] Vision:
I get your point.

So the title must change from TEE hacking to TEE hacking and Advanced Modify Methods ? Or something like that
[Magisk] 에어 론 리:
Play integrity fix + play integrity next with last PIF file not working.

Android 9, Kitsune 26.404 stable canary.

It was working about week ago.
[Magisk] fbirraque:
So read the OP (first page) that I'm confident that will understand why didn't work.
[Magisk] 에어 론 리:
read many times, and didn't found why.

quote pls.

rom and kernel are stock, play integrity passed BASIC only test (checked via Google play Store/Dev opts)
[Magisk] 에어 론 리:
okay, wil leave this module sources, will use another sources.

thanks for not helping
[Magisk] zgfg:
With unlocked BL, root, etc, no matter if you have stock ROM you cannot get more with PIF than Device Integrity
[Magisk] Vision:
Hi @chiteroman can you modify this amazing PIF fork to spoof in DG, because now only in key attestation can, @hex3l can't have time to complete it, but he found this excellent solution https://github.com/hex3l/PlayIntegrityForkKsBypass, and make it like PIF-Strong you say this, and if you release, Google can't block it because the above PIF Fork can read the keybox.xml from PIF module folder, so the users must have private like PIF.json or custom.pif.json

View attachment 6098358
[Magisk] pndwal:
🤔... Member said it stopped working a week ago... Had meets DEVICE then... think they just want DEVICE back...

Wow... I can understand your frustration... You waited a whole hour and 36 minutes for responses here!... So sorry! ☹️ PW
[Magisk] pndwal:
Ta... Very interesting info... However:

😬 PW
[Magisk] Vision:
Why are you ruining my dream ? 😂🤣

Let me hope for such a solution.
[Magisk] hex3l:
The point of my fork was pretty much to bypass the AndroidKeyStore in order to work also on devices with borked TEE (that throws KeyStoreException, and does not provide a keypair or attestation) and, as pointed out, it has not been tested in a real world scenario because it is incomplete.

If someone completes the attestation generation, the codebase could just be adapted in order to patch the framework, reducing chances of detection.

(the current Framework Patch, as for my understanding, requires a TEE that at least generates the attestation)
[Magisk] pndwal:
Wanna win the fight?...

Man with a Magisk mask with Google giant:

... Maybe you can win... And get Google just to dream... (of large women?)... 😜 PW
[Magisk] ashish1989:
On android 9, with same setup, device integrity is not working for me too since many days and I also can not find the reason behind it.
[Magisk] 에어 론 리:
it seems I've wrrote wrong passed test, I'm sorry guys, - with Play Integrity FIx module and proper PIF file my device (LG v30,A9) can pass only BASIC, not DEVICE. have to go onto osm0sis work. It perfectly work with A9, but not workin for A12 (LG v50, A12), and that's really strange for me.

So, I'm using own modules with osm0sis sources on LG v30 A9 (Kitsune 26.404) and chiteroman sources onLG v50 (Kitsune 26.404)
[Magisk] casouzaj:
When you are with A12, is it a custom ROM? If so, have you checked if your kennel name contains characters already known to be banned?
[Magisk] 에어 론 리:
You don't understand me.

I have two different devices:

1. LG v30 with own deep modded ROM, based on stock A9.

2. LG v50 with own deep modded ROM, based on stock A12.

both devices uses Kitsune magisk.

both used the same own module based on chiteroman's work. Yesterday I note that my LG v30 (A9) fails DEVICE test, while LG v50 (A12) working perfectly (BASIC + DEVICE).

That's why I have to ask here for help, but hurry up and miss BASIC with DEVICE in my first message. This bring misunderstanding here.

After some tests, now I'm using osm0sis fork work on LG v30 (A9), but still using chiteroman's work on LG v50 (A12).

I hope this information help ppl.
[Magisk] lordman1135:
hello, did you find or know something about it?, i hope that you can help me

do you know how how i can do that?
[Magisk] Vision:
Unfortunately, this mean you must have a leaked keybox.xml

Lot of info and guide here:

TEE hacking

Post about hacking TEE on Android devices. I will post here some useful resources: https://github.com/chiteroman/Reprogram-TEE-on-Qualcomm-devices https://github.com/chiteroman/FrameworkPatch And leaked keyboxes...

xdaforums.com
[Magisk] chiteroman:
Ahh, good days trying to pass Strong using AOSP key 😂😂

Btw, the key is here: https://android.googlesource.com/pl.../+/refs/heads/main/sw_rsa_attest_root.key.pem
[Magisk] swieder711:
Didn't change anything other than some apps updating. Now failing CTS profile match View attachment 6098712and device integrity.

View attachment 6098709View attachment 6098711
[Magisk] Vision:
Have you try to disabled others modules, except the PIF? To see if pass again
[Magisk] Nergal di Cuthah:
Not only is this unclear what you mean, but, seemingly, way off topic for this thread
[Magisk] anthonnyb98:
Is there any way to make this module work with microg?
[Magisk] lordman1135:
Thank you, but how i can add that on my phone?
[Magisk] Vision:
Maybe this help you

TEE hacking

Post about hacking TEE on Android devices. I will post here some useful resources: https://github.com/chiteroman/Reprogram-TEE-on-Qualcomm-devices https://github.com/chiteroman/FrameworkPatch And leaked keyboxes...

xdaforums.com
[Magisk] chiteroman:
Maybe use latest official PIF
[Magisk] swieder711:
Thanks! Updating to the latest official PIF fixed my phone. I am now passing SN test.
[Magisk] firebomber13:
Hello, could you tell me how you were able to solve it?

I have the same modules that you have. Did you add the key that chiteroman published?
[Magisk] zgfg:
Btw, I've had "Your device does not meet Security..." in Wallet for ten days or more (I used plastic in the meantime).

It was result of my testing prints and a moment when I attempted to pay in a hurry in the store while I forgot to replace the correct Json back before paying

I waited for ten+ days but it didn't clean automatically.although I replaced the correct Json back and PI was passing Device Integrity all the time since

Eventually, I just wiped the Wallet Cache and the Wallet works fine again
[Magisk] flobo09:
My "found online" print from November seems to have been banned somehow. My bank is now complaining i'm rooted and i reverted to basic on TB checker (should TB checker show the "modified key" or original because it shows the original on top, wondering if it could that rather than my key being banned ?).

However, i was still able to pay with google pay one hour ago and RCS is still working so i'm confused by it all now (sorry, i last checked the topic a few weeks back during the great fingerprint apocalypse so might have missed something).
[Magisk] Vision:
If you mean show the original FP, yeah is right, other apps still see the original, and not the spoof FP, this is for GMS and DG
[Magisk] majorfigjam:
There has been no obvious recent mass ban of fingerprints, so maybe you were just unlucky. You did well with your "found online" print lasting so long. 95% of mine were lost on 29 February - the 5% seem to have survived up to now.

Try again with the Griffin print** which is the most widely used, and remember to clear your GMS and Play Store Caches before retesting.

**Updating to Chiteroman latest https://github.com/chiteroman/PlayIntegrityFix/releases/latest is probably the easiest way.
[Magisk] swieder711:
The only change that I made was to update PIF.