yashsingh1/xdaforums huggingface dataset:
[Magisk] HippoMan:
I believe it will lead to another "enhancement" (ha ha!) coming from the Googlefrinchians to "fix" (ha ha ha!) whatever it is that allows PIF 12.1 to work so splendidly.

And in general, the app developers and the Googlefrinchians themselves are seeing to it that Android continues to deteriorate. I'm not saying that this is their conscious goal ... but it's indeed what's been resulting and what I believe will continue to result.

I don't think that any of us mice (in the ongoing cat-and-mouse game) will be able to reverse this trend.
[Magisk] makeyourself:
I'm on KernelSU with ZygiskNext and able to pass PI fine (not Strong Integrity obviously). I do not have Magisk installed at all. What ROM are you using? I'm on LineageOS.

As for Shamiko, IIRC it doesn't help to pass PI, it just tries to hide Zygisk, which PI API doesn't care about. But if you do want to use Shamiko for that then under the latest KernelSU and Shamiko versions I think the alternative to DenyList is to set the AppProfile to Unmount for apps you want to hide Zygisk from (or to set "unmount modules by default").
[Magisk] chiteroman:
That's an app problem... Check Play Integrity in Play Store.

Play Integrity API has a limit in the number of requests.
[Magisk] chiteroman:
Send module logs 👀
[Magisk] cangurob:
I've attached my kernelSU log - is that what you need?

If something else, let me know how to access it.

I'm running Pixel Extended 5.10
[Magisk] Catarsi:
I tried all this and it worked! Wallet wasnt happy about the date changed and needed to reboot several times but it worked at the end. Managed to add cards (thought didnt test actually paying something) and the Integrity checks passes.

Also just updated to the latest MIUI 14 builds that have been uploaded a few hours ago.
[Magisk] Klappp:
Card is added to wallet and the devices passes all the checks but paying doesn't go through. Payments declined every time.
[Magisk] wfred:
🔧 [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
[Magisk] OzBoy1:
I haven't updated to Nov yet as I am trying to make sure all is set to go before the update.

Can you expand please. I have the same issue Error getting token, I cleared the cache etc in the app, then I uninstalled and reinstalled twice but still getting the same error.

Do I need to update first, or should this work with the Oct update?

Any help would be appreciated.
[Magisk] DanGLES3:
To clarify, apps checking Play Integrity can do so either through a free API key or a paid one

Free API keys (like what that app uses) have an low universal limit for requests (for all users using the app), once that limit is reached Google's servers will refuse to respond until said quota refills

Too many people are testing Play Integrity these past few days and are thus exceeding the app's free API limit

If you want to check Play Integrity reliably, do so through the Play Store

Go to Play Store settings, tap the version name 7 times, go back, go to general options, developer options, Play Integrity

If it says both MEETS DEVICE INTEGRITY and MEETS BASIC INTEGRITY you're good
[Magisk] DougMG:
You can update if you want and everything works. The issue with Play Integrity Checker is that it is only allowed so many checks per day before Googles server quits answering and since everyone has been using checking non stop for the last couple of days the app keeps using up its allotment of tokens.
[Magisk] OzBoy1:
Thank you that cleared it up for me, checked and all good.

Funny thing is wallet has a little hiccup each time I launch, says device is not compatible but then it works! hahahaha for the moment no doubt it will come back to bite me.

Thanks again.
[Magisk] wfred:
Release v12.2 · chiteroman/PlayIntegrityFix

Fix more crash issues. Remove C++ code from main.cpp and strip libraries size. Hardcode classes.dex into libs. Using Shadowhook for arm64 and arm (smartphones), using Dobby for x86, x86_64 (emulato...

github.com
[Magisk] westruk:
Marriott Bonvoy: Book Hotels - Apps on Google Play

Travel and Book 8,000+ Hotels Worldwide with the Marriott Bonvoy™ app.

play.google.com

this app? working fine with ksu
[Magisk] djnata:
link for xiaomi.eu xD. I think the update for xiaomi.eu rom are only for stable and i have weekly version :\
[Magisk] thesingular:
Shamiko on KernelSU works on all apps set to unmount, which is all apps you don't grant root access to on default settings. If you turn "unmount modules by default" off (it's set to on when you install KernelSU), then you'll have to set the apps to unmount manually.
[Magisk] HippoMan:
PIF is a victim of its own success!
[Magisk] zgfg:
Always look to the OP post #1, find the link there
[Magisk] passionicon:
dayum bro, 100! Wow. Kudos.
[Magisk] osm0sis:
Scripts-only mode does this automatically.
[Magisk] Vision:
@badabing2003 can you check this?

So only in the Kitsune Mask don't add it automatically.
[Magisk] osm0sis:
That's because Kitsune is HideList not DenyList; they're not using the same CLI or it'd work.
[Magisk] changhuapeng:
This is the line of code that adds gms.unstable to the DenyList. I don't think Magisk Kitsune has CLI command for MagiskHide.
[Magisk] Vision:
Yeah so it's ok.

So for Kitsune Mask users, don't forget add manually if need it.

Yeah I know, just say.

We can add it manually if we want.
[Magisk] zgfg:
Wishful thinking:-)

But then just think about for how long would they last once made public
[Magisk] passionicon:
i've checked pgs 1 & 2 of your odd and ends thread and couldn't see the prominent dump site you're referring to. can you pls share?
[Magisk] osm0sis:
Keep reading...
[Magisk] passionicon:
i have thought about it,and knowing the pain i'm feeling, i am sure i will, at first, share 10 out of 13, but only if the devs reason with me and approve it, because they know better. i juust don't see why people consider this laughable. i have tried to test prints with pixel flasher but i don't understand the software properly and can't find steps to do it. if i find that and the dump sites, i might stay home and search and submit to devs here to approve and post some here, no biggie for me.13 is a lot to me
[Magisk] passionicon:
ok boss
[Magisk] changhuapeng:
Considering that we have thousands of working prints just a few months back and these thousands were instantaneously "banned" in a single day, 13 is not a lot.
[Magisk] zgfg:
This was just 13 new ones - about 80 were discovered earlier.(And that number was mentioned here several times)..And none of them were ever made public

And there were other users who mined and discovered their private prints, too (maybe partly the same, maybe some different ones)

Methods to mine have been posted and discussed here, last time about two weeks ago (I've seen two users who started then and found few private prints.over the last two weeks)

Hence everybody else is also welcome to do the same. It's not easy, it takes time and patience, thousands need to be downloaded and tested to find a few working ones. But that's their value. And the reason why those who did don't want to throw them now through the window

Besides, even if several people mined independently, if they mined from the same dumps, they would have found the same private prints. If only one of them publishes now, once G bans them, all the others whohaf the same private prints would loose days of their work

There were over a thousand prints published by the beginning of the year. Not here but on GitHub, etc, and links were circulated here, on TG channels, etc. On Feb 29, G BANNED ALL OF THEM that were ever made public by that time

On May 25 they banned again hundreds. After that nobody publishes the prints except the single/same one used in PIF and Xiaomi.eu injector
[Magisk] passionicon:
hmm ok i understand the whole concept waaaaay better now. thanks boss
[Magisk] badabing2003:
This is all I have

View attachment 6114701
[Magisk] Vision:
So you have it in DenyList the gms.unstable.

PIF fork script-only-mode add it automatically.
[Magisk] badabing2003:
I don't see it there
[Magisk] osm0sis:
You didn't expand gms to see it.

I just installed latest Kitsune on a test device and can confirm there's no CLI whatsoever for the lists. Hopefully @huskydg will consider adding a --hidelist and --sulist CLI and also have --denylist as a cross-fork compatible alias for --hidelist in the next release. 🤞
[Magisk] BarackMitzvah:
Sorry if this has already been answered, been reading through the thread and it's not totally clear to me - is there a way to have RCS work on a rooted, bootloader unlocked phone?

I am seeing intermittently that using no PIF may allow this? Does anything else break it like Magisk modules? At this point I am willing to fully ditch PIF since I don't have a private print if it means working RCS

Any help here is massively appreciated, and all of the work going on here is extremely helpful
[Magisk] ScottIsMyName:
It's been answered a ton actually. With a working private print Wallet and RCS can both work. On the publicly available print Wallet and Play Integrity work but RCS does not. There are older banned prints where Wallet doesn't work but RCS does. In addition there are setups where RCS works without even using PIF.
[Magisk] badabing2003:
lol, didn't occur to me that it's expandable :oops:

It's there.
[Magisk] generalculprit:
Fully agreed, but I think he is looking for an older banned print that meets RCS.

There is no commonly known one, but maybe @TheFreeman193's pickaprint.sh contains a matching print. Or has that already been tested?
[Magisk] mac796:
Was curious is the magic number for API still 25?
[Magisk] UberNorse:
I and a few others have tested this and we are seemingly coming to the same conclusion. Most modules you will use will break RCS with this method. I am still working on how to have this work without a private print and will update you via PM if I find out.

For now, if you don't care to use any modules you can use Apatch to root and just not install modules or you can select one at a time to see what breaks RCS. But simply rooted with apatch and no modules allows RCS to work. Albeit, basically nullifies the point of root.

For instance I installed revanced YT and YT music and it broke, so I have installed micro-G and used the revanced apk's to skirt that failure. I'm working on how to get Viper4Android and a couple others going with RCS but as of now I'm dead in the water regarding modules. But RCS is working flawlessly.
[Magisk] aliantonio:
Agreed. I've gotten 3 modules to work but lsposed breaks RCS for me and my most useful modules all require it.
[Magisk] UberNorse:
If I can get Viper and a call recorder to work I'll call it even and forget the rest of my modules until we have a better solution. I may re-install Viper today to see if it will possibly work, I believe I installed the modules without enough time in between to properly vet which one breaks. I believe we need 12-24 hours to properly judge what breaks and what doesn't, although I'm sure some break RCS immediately.
[Magisk] aliantonio:
Lsposed is one of those that break RCS immediately for me
[Magisk] ThatOneGuyOverThere:
I have tried about 100 of the latest prints from tadiphone and none get me device integrity. I take the build prop, put it through the parse build prop chatgpt website and load and test them using pixelflasher on my phone with just magisk and playintegityfork v9. Best I can get is basic. What am I doing wrong or what other places could I go to?
[Magisk] TheFreeman193:
I've heard no reports of prints that fail DEVICE integrity but enable RCS. The PIFS collection (pickaprint.sh) has had very few working prints for Play Integrity/Wallet since February 29th, and none of those are for the most common ABI list (arm64-v8a,armeabi-v7a,armeabi) which I assume would need to match for RCS as well.

I don't have the time or free devices to test for that criteria right now but the collection remains a public archive for any that wish to test them.
[Magisk] TheFreeman193:
There are working prints, but you'll likely need to test more than 100. Try using the gen_pif_custom.sh from @osm0sis to extract properties since it has handling for treble/GSI ROMs. Check the resulting profiles to make sure they're valid JSON and aren't missing important fields.
[Magisk] osm0sis:
Yep, still 25. I just updated all the PIFork-related documentation in the last few days, including the Guide, and the FAQ. Feel free to review.

That website doesn't work very well, especially not for my Fork, so use my gen_pif_custom.sh script as always.

Find it linked (along with the FAQ, the Guide, and lots more) under Resources in my Fork's README: https://github.com/osm0sis/PlayIntegrityFork?tab=readme-ov-file#about-custompifjson-file
[Magisk] mac796:
Thank you very much. Your subtle hints helped me out a lot. Like you said it wasn't easy though. Just a lot of searching and trying. The one I found doesn't even make sense. It almost looks like someone made it....
[Magisk] pndwal:
Even LSPosed w/ no modules installed? (Nb. Not just disabled, I mean not installed.) 👍 PW
[Magisk] chiteroman:
Of all these fps, which is the most recent version of Android?
[Magisk] zgfg:
A14
[Magisk] chiteroman:
A14 working fp ??? Lmao
[Magisk] pndwal:
Edit: Removed... 😂 PW
[Magisk] jnss98b:
Funny thing is I'm pretty sure imessage works on jailbroken iphones lmao. Now rcs as well on ios 18 probably
[Magisk] Thebear j koss:
Jailbroken is not even close to unlocked boot and root.
[Magisk] David B.:
Yes, but it's still pathetic.
[Magisk] chiteroman:
Play Integrity Fix

HOLY ****, GOOGLE WHAT YOU DO HAHAHAHA STRONG PASSING WITH SW ATTESTATION CERTS

t.me

Strong passing with SW attestation certs, WTF

Just flash FrameworkPatchGo, Shamiko, uninstall PIF and enjoy Strong
[Magisk] Cabalisto02:
Not working sir or maybe i did something wrong. What should we select when flashing? Shall we select yes on everything?
[Magisk] immortalwon:
Yes it is lmao. You can do everything that lsposed has and more
[Magisk] HUBERTH:
you're smoking some good crack

Jailbreak doesn't even allow you to do things that are available on Android without root

Good luck trying to for example clone apps (no, Duppy and Crane aren't cloning them, and Duppy doesn't even work for a lot of apps, like Messenger + Crane is a paid tweak xD)

You can't even move your icons freely like on iOS 18 or android... 1 and higher? with jailbreak
[Magisk] Thebear j koss:
Not to veer waaaay off topic here but jailbreak on an iPhone isnt even the equivalent of installing a crappy 3rd party launcher on an android. So yeah, you can laugh all you like but you're just coming off sounding stupid.
[Magisk] cmstlist:
🤨

Looking forward to hearing if anyone here has success trying this with stock Pixels (I have 6a) and whether Pay & RCS work.
[Magisk] passionicon:
Curious too
[Magisk] passionicon:
Does this mean rcs and wallet will work?
[Magisk] chiteroman:
RCS works if you use a different fingerprint (not sailfish), and Wallet requires Device integrity.
[Magisk] shadowstep:
I presume this won't work for devices like OnePlus, where TEE is broken, correct?
[Magisk] immortalwon:
It will, Google / oneplus secretly fixed it without telling anyone recently as I discovered on my oneplus pro9 a11 after msming it was passing strong integrity with locked BL. I can't vouch though for lower then the oneplus pro 9

EDIT: I can't say for sure because I didn't test the module yet but I will test on the weekend.
[Magisk] Reznor7:
Doesn't work on my OnePlus 11. I get No_Integrity after installing the module.
[Magisk] bhinda786:
not working
[Magisk] immortalwon:
Tell us your setup before saying it doesn't work: Is your system patched so you have R/W permissions? What Android version? Are you using the latest framework patch that was uploaded yesterday?
[Magisk] Reznor7:
OnePlus 11, rooted with Magisk 27.0. Stock OxygenOS 14, May security update. Tried both the 1.0.1 and 1.1.1 with the same result.
[Magisk] Cabalisto02:
Mine

Mine pass only device integrity, Realme Gt Master Edition. Rooted with magisk 27, REALME UI Android 13 April Security patch. Using Latest framework patch.
[Magisk] Darklaser38:
Same for me only device integrity, Redmi note 9s, rooted with magisk 27, MIUI 14 android 12. Whoever Key attestation app show the same thing as chiteroman screenshot
[Magisk] chiteroman:
Yes, with broken TEE it doesn't work
[Magisk] Cabalisto02:
Damn :(
[Magisk] chiteroman:
Will try to add support, BootloaderSpoofer already have it 👍 (it's incomplete)
[Magisk] shadowstep:
Yeah, with my 9R, I could only manage basic + device, not strong.

That'll be great, thanks in advance!
[Magisk] Reznor7:
Do all OnePlus devices have broken TEE upon unlocking the bootloader, even newer models?
[Magisk] joeyhuab:
Tried FrameworkPatchGo on Evolution X. It crashes several apps or make them lag out, it says bootloader locked in Key Attestation app but in Play integrity check in Play store, only passes basic + device
[Magisk] chiteroman:
If you can recompile the ROM you can cherry-pick this:

Play Integrity Fix · chiteroman/android_frameworks_base@7565bf3

Change-Id: I13dd2d6e6d586968c0d06e2873c458fe2167e0ae

github.com

Compile FrameworkPatch, get the apk, save it into ROM and load it using PathClassLoader.

Also, you can install the apk and load classes from there, so users can update it, but I never tried that way.
[Magisk] chiteroman:
Also cherry-pick this @joeyhuab

Disable useless Keystore features · chiteroman/android_frameworks_native@6af68ea

Change-Id: I28a2e93d0718e5950948b87a6c6abf4341753552

github.com
[Magisk] aliantonio:
Maybe I'm doing something wrong but I'm on stock pixel 7 and I'm failing both device and basic. Flashed frameworkpatchgo, selected yes to download required dex files. Installed Shamiko although I'm not sure if it's working properly. Added gms and messages to denylist and left it disabled. Fails both device and basic. Anything I missed or messed up?
[Magisk] badabing2003:
@chiteroman

Seems to be not working for Pixels with Shamiko.

If you install PlayIntegrity Fork in script only mode, and enable Magisk denylist, it passes device, but if you turn off the PlayintegrityFork, and Magisk denylist, and enable shamiko, nothing passes.

My tests are on Pixel 5
[Magisk] joeyhuab:
I'll try picking these and patching via FrameworkPatch GO.
[Magisk] generalculprit:
It's more or less hearsay:

🔧 [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
[Magisk] chiteroman:
It won't work, why you want to use FrameworkPatchGo if you can modify Java source files ?
[Magisk] joeyhuab:
Honestly confused how you want me to go through it. So after I pick these into the ROM, I compile the ROM and compile FrameworkPatch and the inject the compiled APK into the ROM?? Seems too much to be done.
[Magisk] geokilla:
I've been following the thread for the past week and I'm a bit confused so forgive me for asking. I don't think we have a solution to passing "Meets_Device_Integrity" yet? Meaning no RCS and Google Play Store updates? I noticed some of my apps aren't showing on Google Play Store because it fails device integrity.
[Magisk] joeyhuab:
If using custom ROMs, you need a signed ROM (either with or without a PIF built in).

If using modules, you need the latest either by osm0sis or chiteroman.
[Magisk] Reznor7:
To add on, this will get you Device, but RCS will still be broken unless you have a working private print.
[Magisk] CZ.Kostra:
FP "sailfish" passes DEVICE but RCS does not work.

What result do you get after typing 'unzip -l /system/etc/security/otacerts.zip' in terminal?
[Magisk] ardiesel:
LOS 21 latest on Pixel 6 pro rooted, frameworkpatchGo won't work. I'm fine with that, but what happens if I remove the module completely from magisk? Does everything, file wise, go back to the way it was prior?
[Magisk] chiteroman:
Cherry-pick that commits and include in system/framework the attached file.

Enjoy Strong integrity.

NOTE: requires a working TEE, if you have a Qualcomm device and TEE doesn't work, follow this guide: https://github.com/chiteroman/Reprogram-TEE-on-Qualcomm-devices
[Magisk] intel_core_i7:
I wonder if the most recent FrameworkPatch developments makes this app works. Perfect opportunity to test things out
[Magisk] Vision:
Wait a second with this, no need anymore classesX.dex, because have inside Pathclassloader and only put this miui.jar in /system/framework and that it ? Can this can happen with frameworkpatch ?
[Magisk] chiteroman:
LEGENDS ARE TRUE, PIF-STRONG HAS BECOME A REALITY

Release v16.0 · chiteroman/PlayIntegrityFix

WORKING TEE = STRONG PASS

github.com

(uninstall FrameworkPatch, reboot and flash this)

(should work on SIGNED custom roms)

(requires WORKING TEE)
[Magisk] Xorio71:
What are the chances that Google bans this in the foreseeable future?
[Magisk] immortalwon:
Within the next 24 hours
[Magisk] Xorio71:
Yup, thought as much.
[Magisk] badabing2003:
Only device, no strong. Pixel 5

View attachment 6115087
[Magisk] Xorio71:
Haha, knew it.
[Magisk] joeyhuab:
Same here, Evo X, POCO F5.
[Magisk] ninjakira:
Hey so how do I even go about checking if I have a broken tee? If it matters I'm just using a Motorola edge 2021 (berlna) on stock root lol
[Magisk] immortalwon:
RCS is still not working even with this new strong module.
[Magisk] CZ.Kostra:
@badabing2003

Also here. MIUI 14 Xiaomi.eu
[Magisk] passionicon:
Rcs, wallet work?
[Magisk] badabing2003:
Didn't bother testing, I wanted to see if strong would pass, I can get those passing by other means.
[Magisk] iTudorS:
passing strong with latest PIF

pixel 8 pro

stock rom latest june patch

magisk 27

no issues at all
[Magisk] RinaZet:
Passing Strong on Pixel 8 Pro

Stock A14 + Magisk 27

No luck on Xiaomis with Custom ROMs though (only basic&device)
[Magisk] chiteroman:
Kill GMS unstable process:

adb shell su -c killall com.google.android.gms.unstable

Execute these commands:

adb shell su -c resetprop ro.board.first_api_level 34

adb shell su -c resetprop ro.product.first_api_level 34

Run test again.
[Magisk] methuntt:
Passing strong integrity with S23 Ultra

Pif v16.0

Stock rom Magisk
[Magisk] changhuapeng:
@chiteroman From what I've gathered, people are passing strong only on stock ROMs. We need more confirmations though.

Can confirm, this works on my LineageOS-based A13 custom ROM using module FPG not PIF.
[Magisk] norz3n:
View attachment 6115089

Redmi Note 8T

PixelOS A14, latest signed build

View attachment 6115092

TEE working

Magisk Delta 27(Kitsune Mask)
[Magisk] ManSamVampire:
Passed strong integrity on Xiaomi Pocophone F1 with Android 13 LineageOS official after running this
[Magisk] Kingcool88:
Passes strong here. Running latest kitsune.

View attachment 6115099
[Magisk] xantrk:
Strong doesn't automatically mean pass for device without relying on fingerprint right? Is there a benefit to having strong from a general daily use POV?
[Magisk] privacyguy123:
By next week
[Magisk] Bonoboo:
But... how it's possible?
[Magisk] officialputuid:
Only device passed, No strong 😢

- AwakenOS, signed + tee ✅

- KernelSU
[Magisk] David B.:
This worked for me on my Pixel 6 Pro running the June 2024 stock version.
[Magisk] romashkatea:
Passed Strong on Pixel 7 Pro Android 15 Beta 3. View attachment 6115102View attachment 6115101
[Magisk] joeyhuab:
This one causes device integrity to go away. I'll have to recompile with frameworks/native change and confirm there.
[Magisk] CZ.Kostra:
BASIC only after typing. After reboot, again DEVICE on Poco F5 Pro MIUI 14.0. 28.0 (Xiaomi.eu).
[Magisk] Rares6567:
Same here, I got BASIC only after using the commands.

I'm using Kitsune with Lineage 21.
[Magisk] g1b50n:
Got OnePlus 11 with Android 13, got only Basic integrity... What i am doing wrong? When i use osmosis fork got also device

Magisk 27.0

PIF 16.1

Only Basic Integrity

Edit:

After changing API level to 28 got back Basic and Device.

Still Strong is far away...