yashsingh1/xdaforums huggingface dataset:
[Magisk] bluerar:
I did get rid of it now, it still doeanot pasa integrity pass, note: i only got rid of lucky patcher modul3 not the app.
[Magisk] Vision:
I think, he mean the app, because the module is just for skip signature, like the core patch in LSPosed.
[Magisk] bluerar:
I got rid of the app too, still integrity fails!
[Magisk] V0latyle:
Disable all Magisk modules

Reboot

Re-install PIF module

Reboot
[Magisk] bluerar:
PIF module ? Can I have the link please! Found the link
[Magisk] bluerar:
did all the steps, still a fail!
[Magisk] Nergal di Cuthah:
Did you read the first post of this thread and all the linked items? Custom kernel? Non stock rom? How to check those is either in the first post or the FAQ
[Magisk] Nergal di Cuthah:
@bluerar
[Magisk] bluerar:
I did those on other post -> https://xdaforums.com/t/safetynet-help-on-samsung-s10-plus-help.4680398/post-89602459
[Magisk] bluerar:
I guess I'll wait for an update, or if there is a rom that is stable with integrity patches.
[Magisk] trevtdogg:
if you are running lsposed or any other xposed replacement, try also disabling all of those modules as well.

so disable all other magisk modules, and all ~posed modules, reboot, then see if that changes anything.
[Magisk] bluerar:
I got no lspsed or xposed, I checked /data/adb only found magisk
[Magisk] bobby.surya26:
I thought it was my device problem, turn out it's not and I'm happy 😅

I've been completely uninstall magisk, dirty flash the rom still gives me "device is not certified" on play store but now I can use banking app
[Magisk] Nergal di Cuthah:
The playstore certification may take a few hours to a day before it returns, if you have basic (and i think device)
[Magisk] flyoffacliff:
Burnt for RCS or Device? I'm on a beta print now that's been working with RCS for over a week after it died for device integrity.
[Magisk] flyoffacliff:
Playstore certification does not need device from my experience.
[Magisk] psone:
Can you share what is working for you? I'm using play integrity fork, magisk and zygisk. Cleared carrier data, messages data, waited over 24 hours, still no RCS.
[Magisk] bobby.surya26:
Playstore certified sometimes bugged in my experience
[Magisk] bluerar:
In my condition Integrity fork will help ? and Is there a tutorial ?
[Magisk] majorfigjam:
Did you read the first post of this thread and all the linked items?

You will find everything you need there.
[Magisk] Aarif goku:
Is it a stock rom or Port rom you are using?

What app you have in denylist?

Also get rid of magiskhideprops module if you have.
[Magisk] maxim.a.petrov:
Please, could you tell me how to pass the Google checks for A9? Only Basic passes, Device does not. I am using MIUI eu build. No additional modules are installed, only play-integrity-fix, magisk kitsune, on Mi8 Lite device. I have asked this question here so many times and still haven't received an answer... Everything passes on firmware with A10+, but I specifically need it for A9...
[Magisk] bluerar:
I got rid of all modules, And now for 30 mins straight i tried pif updater tool integrity fork. Gettings fails.

Ane i have few of apps in deny list, 1 bank and few others
[Magisk] bluerar:
Yeah am trying my best.
[Magisk] CZ.Kostra:
What do you mean PIF updater? Did you use autopif.sh which is part of PIFork v9?
[Magisk] Aarif goku:
Not sure if you used or tried Framework patcher but if you did then restore to original framework.

Remove playstore or play services from Denylist.

Keep enforce denylist off.

Zygisk on

Only install/enable these modules

1. PlayintegrityFix 16.5

2. Shamiko 1.0.1

And reboot.

Check if fails all clear data playstore and play services and reboot.

If still fails you'll need to check what rom you are using something in it might be causing trouble.
[Magisk] bluerar:
'pixelflasher' trying my luck of a working fingerprint
[Magisk] bluerar:
just did this, still no chance : )
[Magisk] Aarif goku:
Stock ROM or unofficial port ROMs?

For me 16.6 is failing all integrity on my old device only 16.5 is working.
[Magisk] bluerar:
Stock ROM
[Magisk] sawdoctor:
16.5 and 16.6 have different included fingerprint so that might be the reason
[Magisk] bluerar:
is there a version of 16.6? github has latest version and its 16.5
[Magisk] sawdoctor:
If it's not on GitHub unfortunately you'll have to go to telegram. Xda rules prevent me from linking it, just checked and it's there
[Magisk] bluerar:
where can i join the telegram group :)?
[Magisk] bluerar:
they have multiple channels, I just joined XDA-General and asked for the file.
[Magisk] sawdoctor:
I'll send you a pm
[Magisk] badabing2003:
It's on Github, it's a CI build because it's not release build yet.

You can find it here, you need to log-in to Github to be able to download it.
[Magisk] V0latyle:
He should be able to pass Basic even without a valid print, yes?
[Magisk] tom510:
16.6 Causes bootloop on android logo for me. Not sure how to get logs.
[Magisk] V0latyle:
Did you disable all other Magisk modules?
[Magisk] tom510:
yes, I did
[Magisk] V0latyle:
Are you passing BASIC in Play Integrity?

What does YASNAC show?
[Magisk] badabing2003:
Valid print is embedded in 16.6, so he should be able to pass device.
[Magisk] V0latyle:
@tom510 Try disabling DenyList
[Magisk] zgfg:
Debugging needs something to start with, eg PIF logcat, (custom) kernel name, and (custom) ROM otacerts info, screenshots from Magisk modules, LSPosed modules, Magisk app Settings related to Zygisk and DenyList
[Magisk] bluerar:
Nope 16.6 didnot work.
[Magisk] alonsoj636MW:
For me, RCS and Device Integrity working with 16.6 PiF :)
[Magisk] majorfigjam:
OK @bluerar, you've had a lot of help, gone back to basics, and still nothing.

Can someone here confirm that a rom with "asks_update.x509.pem " is even capable of passing? It doesn't say testkey, but it doesn't say release either.
[Magisk] Nergal di Cuthah:
And the kernel string looks sparse to me, maybe it's normal just to have only the kernel version, but it's not what I've observed when others post their kernel string.
[Magisk] bluerar:
Here is everything is disabled, only pif is enabled.View attachment 6122296View attachment 6122297View attachment 6122298
[Magisk] bluerar:
:'》View attachment 6122300
[Magisk] osm0sis:
PixelOS? 🧐
[Magisk] tom510:
Yes, poco f3
[Magisk] osm0sis:
Yep, thought so. Follow the link and read. I said this would happen.

You should switch to my fork since I put a lot of work into supporting all the different ROMs that had their own print injector implementations, and keeping things stable.
[Magisk] tom510:
Just did, works fine. Thanks!
[Magisk] majorfigjam:
Your deny list is not relevant to disabling modules.

Your folder list shows 9 items in module folder. What are they?

Maybe disable and delete all modules in Magisk and reboot to remove traces, then reinstall pif module and shamiko, reboot and test again.

For what its worth, your problem likely lies in a badly signed rom, and you need to get one signed with release keys.
[Magisk] bluerar:
How and where i can get one
[Magisk] flyoffacliff:
My reboot on Pixel 5 took super long right after flashing v16.6. It had me clenching my teeth getting more nervous by the second, lol. But no issue.

When flashing it said backing up custom PIF, but I'm pretty sure that one is dead now, so guessing the backup failed somehow due to a bug, and I'm back on the new default one.
[Magisk] Nergal di Cuthah:
It says in the first post, again please (re?)read it
[Magisk] osm0sis:
But why roll the dice when you could just switch to my fork and enjoy stability?

😶‍🌫️
[Magisk] flyoffacliff:
I actually thought I had yours installed until I double checked.

I think I just used the other one because yours had an older last released date and it was easier to get started when I was new since it included a default FP. And it's worked ok for the most part.

Not sure on any of the differences between yours and his besides one includes a FP and one doesn't. I know there's got to be something in that 200 commits though, lol.

Yours mentions something about the GMS unstable process. I later found out that it's some kind of Google service. But never found a clear answer on what it is and why it's called "unstable", lol.

I'd be willing to try yours though.
[Magisk] 4sz0m:
I'm still on PIFork v7 (released 25 Jan) and works like a charm.
[Magisk] osm0sis:
Lots. And easy to find out. 👇

Changelog:

Releases · osm0sis/PlayIntegrityFork

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com

README:

GitHub - osm0sis/PlayIntegrityFork: Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com

v8 is where I added support for replacing PixelOS' overlay-based injector to my customizable app replacement. v9 adds my autopif script so while it doesn't directly include a json, it's now dead easy to get the public print everyone else is using without needing a module update.

Note my last 3 release dates. More numerous and more recent releases does not mean better. 😉

😶‍🌫️
[Magisk] bluerar:
removed all denylists/modules/any root apps, restarted the phone, installed 16.6 pif and 16.5, still no chance, And yes I did read the first post, I even downloaded few rooms took their build prop information, failed too, then I used pixal flasher for about 1 hour, not even single integrity was passed!
[Magisk] V0latyle:
@bluerar what version of Magisk are you using? I'm on v27 as well and I don't see the "Tapjacking Protection" option, I think that was in earlier versions?
[Magisk] V0latyle:
Something is wrong with your configuration. Without a valid print you should be passing Basic
[Magisk] bluerar:
Not Sure, what exact version it was when I rooted the device, but at the time ui was white, and yeah I have version: 27 too. 4 to 5 years ago.
[Magisk] sir_bazz:
Nice to have RCS back again.

Thanks @osm0sis 👍
[Magisk] oldman20:
does anyone know how to check countries support RCS? I tried even on non-root, stock rom S10 RCS not work
[Magisk] Nergal di Cuthah:
Best i could find is carriers in the commercial deployment section of wikipedia

Rich Communication Services - Wikipedia

en.m.wikipedia.org

Even the official website didn't have an easy to find country list sorry
[Magisk] Nergal di Cuthah:
Please make an image like this

View attachment 6122338

You couldn't have had 27 4 to 5 years ago, so i don't understand the sentence
[Magisk] lpedia:
It's not just the country that matters. The particular carrier you're using must provide RCS services, and your phone brand and model must be one they support for that service.

@oldman20, have you asked your carrier whether they provide RCS, and if that particular phone model is included?
[Magisk] V0latyle:
Magisk 27 was released this February. I think you're using an old version.
[Magisk] fulano123:
How to check for ROM signature if I cant find the "/system/etc/security/otacerts.zip" path ?

Currently using LineageOS15
[Magisk] bluerar:
I just kept updating it till version 27, just to clerify. I was referring to "Tapjacking Protection" maybe it was 4-5 years ago.
[Magisk] bluerar:
View attachment 6122357
[Magisk] CZ.Kostra:
Ramdisk is not created. This means that Magisk is not working properly. I would unroot and re-root.

Edit:

I looked further and it seems your device doesn't have Ramdisk.
[Magisk] bluerar:
Hmmm, do I have to re-install the stock image all over again? I am a bit confused howd i just unroot and reroot
[Magisk] bluerar:
+ @V0latyle said i should get basic integrity pass without all these fixes
[Magisk] cabagekiller:
That's correct.
[Magisk] maxim.a.petrov:
My A9 on my Mi 8 lite phone passed the tests finally after so much wasted time on Play Integrity Fix 16.6 beta module, thanks to the developer
[Magisk] cabagekiller:
How'd you fix it?
[Magisk] maxim.a.petrov:
Magisk Kitsune, Play integrity fix 16.6 beta, clearing data and updates from the play market and services
[Magisk] cabagekiller:
What was the issue not letting it work that took you a while to fix?
[Magisk] maxim.a.petrov:
None of the versions before 16.5 worked, and the fork also didn't work. For 4 months I had problems with passing it on A9. On 10+ everything worked fine with other versions
[Magisk] cabagekiller:
Weird. I wonder what changed for it to work.
[Magisk] V0latyle:
Don't worry about ramdisk, it's something your device either has or doesn't, the only thing it has to do with Magisk is whether Magisk uses the ramdisk or not

I'm not sure what is wrong. You're on the stock ROM, rooted with Magisk 27, you have PIF 16.6 installed...As long as nothing else is interfering, you should be able to pass.
[Magisk] pndwal:
For clarity, Magisk is always installed in ramdisk (on real devices)...

Spoiler content hidden.

🤠 PW
[Magisk] bluerar:
ima wipe everything, and upgrade to android 12, then root from there and see what happens
[Magisk] simonpunk2013:
@chiteroman Thank you for the source code again! I successfully passed PI again by making a little changes to the framework, though I don't know if the api_level must be 25, I just make it to 25 globally anyway, no bugs so far, may observe for one more week.
[Magisk] itsmir:
Just to add to the woes:-

Mi 9T on EvoX (A13) rooted with KernelSU

My Wallet stopped working a few days ago along with everyone else

I installed Zygist Next v4.-0.81 & PIF v12.3

Still not working,

Cleared Play services, store & wallet data, reboot - nope, still not luck.

Not a fan of Magisk so reluctant to install - hoping for a fix for us KernelSU users
[Magisk] Klappp:
I'm using KernelSU and I have no problems.

Both modules are installed and working fine
[Magisk] immortalwon:
I use EvoX as well on poco X3 Pro and I pass PI with the mod and KSU. Clear storage data + cache of these: Google play services, google play store, google services framework, wallet as well and try again
[Magisk] trax69:
One question, do I have to install safetynet v. 3.0 Displax Mod together with PIF? It works now only with Samiko and PIF.
[Magisk] immortalwon:
If it works, why would you suggest installing another module? Just use PIF.
[Magisk] itsmir:
Thanks for the info - I have tried that several times and no luck. Once I try to add my cards back it gives "this device does not meet security standards" message. Integrity checker shows I'm failing deviice_integrity. Bit stumped on what to do next.
[Magisk] osm0sis:
Things can still get flagged on Google Pay's side as suspicious and you need to call them to get it lifted.
[Magisk] osm0sis:
Because chiteroman mentioned it and updated it, causing this ensuing confusion in an already chaotic thread. 😛
[Magisk] trax69:
Shamiko +PIF =

View attachment 6032468
[Magisk] SchmilK:
12.3 fixed my tap to pay on Pixel 7 Pro :) Thank you!!
[Magisk] immortalwon:
Make sure you also use shamiko and select the right google processes in the deny list.

EDIT: Technically you shouldn't have to do this, but just try it anyway. Deny list: G. pay services, g. play store, g.play wallet.
[Magisk] chiteroman:
Locked bootloader or spoofing hardware attestation ?
[Magisk] zgfg:
No need to put G Playstore and Wallet to DenyList

Edit: I saw now your Edit...
[Magisk] cangurob:
Sadly I'm in exactly the same boat... Getting close to going down the magisk route just to see if it'll work...

I DID try using Shamiko as well - didn't make a difference.

@chiteroman - are you able to provide some instruction on how to check the logs specific to your module? The KernelSU logs don't show anything related to PIF ...
[Magisk] zgfg:
Terminal emulator:

su -c logcat | grep PIF

And run Play Integrity checking to catch that logcat
[Magisk] cangurob:
Thanks for the reply.

Here's the steps I've taked:

Grant my terminal APP SU access in KernelSU manager.

Open Terminal, run the code you gave me.

It sits there with cursor below the line (screenshot).

I open play store, go to developer settings and press "check integrity".

The checker returns [MEETS_BASIC_INTEGRITY] only.

I go back to the terminal, and it still shows the same screen.

I've included screenshots of my kernel SU, zygisknext and PIF versions...
[Magisk] krkhaha:
About safetynet. It works some time after procedure. One day and later I get problems again. Each time is same thing. All the time I have informed my device is certified.

After I flashed again integrity fix and reboot everything was coming back to safetynet pass but it's not working well at the moment because I randomly lose my safetynet pass.
[Magisk] zgfg:
Instead of:

su -c < command 1 >
su -c < command 2 >
...

You can do:

su
< command 1 >
< command 2 >
...
[ exit ]

So test just logcat command does it constantly print out (stop by Ctrl c ) - if not, something is wrong with your Terminal Emulator or su with your KSU

And logcat | grep PIF assumes that PIF module must be installed

For older versions of the module it was logcat | grep SNFix

grep just filters out those (logcat) lines that contain PIF or SNFix

Btw, you can redirect output to PIF.txt file in Download folder:

su
logcat | grep PIF > /sdcard/Download/PIF.txt
[Magisk] cangurob:
su -c logcat is a mass of constant text, but grep PIF doesn't return anything.

I have PIF 12.3 module installed as per my screenshot above!

As @chiteroman mentioned previously, it's as if zygisknext just doesn't register the existence of the PIF module at all! (Hence why I'm also happy to be a test guinea pig to work out why!)

EDIT: I'm wondering if it could be that my rom (Pixel Experience) has some sort of it's own in-built spoofing that could be messing with this module?
[Magisk] nanoumax2:
Hi, I'm on stock, rooted with magisk, pif 16.5. if I want to update to 16.6 do I need to disable all my modules first?
[Magisk] zgfg:
But open Modules tab in Magisk app and screenshot which Magisk modules you have installed there (it will also show which are enabled or not), form the /data/adb foldernothing can be read about

Also screenshot top of the main window in Magisk app - to show which Magisk is installed, does it show that Zygisk is enabled and so

If you have LSPosed, open LSPosed mngr and screenshot which LSPosed modules are installed and enabled

And see in the FAQ how to capture PIF log
[Magisk] bluerar:
already removed root with all its modules, I am in a process of trasfering my data now
[Magisk] sawdoctor:
No, should be fine to just update. As long as you haven't got any props spoofing or anything, only real change is a different fingerprint
[Magisk] nanoumax2:
Ok, it's strange because when I download the file, the zip file is not recognised by magisk whereas the 16.5 version yes🤔
[Magisk] Vision:
Maybe is relative to this.

Test version?!

View attachment 6122515
[Magisk] nanoumax2:
Ok, it's strange because when I download the file, the zip file is not recognised by magisk whereas the 16.5 version yes🤔

Yes, this one. It's Because it's a test one that I can't install it?
[Magisk] Vision:
Maybe is relative.

Can't install when try to update? If yes, just delete the previous version of PIF, and after install the v16.6
[Magisk] nanoumax2:
Ok, it's strange because when I download the file, the zip file is not recognised by magisk whereas the 16.5 version yes🤔

Yes, this one. It's Because it's a test one that I can't install it?

Actually the file doesn't appear in my download folder when I use magisk. Maybe I should wait for the official 16.6 version, the update will be automatic like from 16.4 to 16.5
[Magisk] Vision:
Oh that's is strange.

Have you try to reboot, your device to see if after is there in the download folder?
[Magisk] nanoumax2:
O

Look at this! I've downloaded the 16.6 the 16.5. there are in my download folder and when I want to install a module via magisk only the 16.5 appears....
[Magisk] V0latyle:
Are you sure you downloaded to the same place? Try renaming the zip
[Magisk] Vision:
Oh, now understand what you mean.

But just for test, have you try to reboot your device, to see if after is appear from Magisk?
[Magisk] fulano123:
I am using an Unoficcial (not signed) Lineage build.

Any way I can sign it to pass integrity ?
[Magisk] markdewet:
Regrettably not, the ROM developer has to sign it. (Thanks very much to the wonderful people on this thread that assisted me with this answer.)
[Magisk] nanoumax2:
O

Look at this! I've downloaded the 16.6 the 16.5. there are in my download folder and when I want to install a module via magisk only the 16.5 appears....

Yes I rebooted my phone, and I renamed the file. It's the same problem. Don't worry I Will wait for the official update. 16.5 is working fine, I just wanted to check if the RCS worked with the 16.6
[Magisk] manjaroid:
RCS should work with chiteroman's 16.6. Instead of waiting why not have it working today with osm0sis's fork and the same or similar print (minus chiteroman's extras)?

Magisk not locating the 16.6 zip is peculiar. Can the Files app see it?
[Magisk] V0latyle:
You probably downloaded the wrong file. It has to end in .zip for Magisk to see it as a module.
[Magisk] Nergal di Cuthah:
Nope screenshot above shows both as zip. I thought maybe a breaking character in name, but according to the same ss the two files' names are formatted the same

🔧 [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] nanoumax2:
I finally found the problem ! Files app located the file but it was in the download folder of telegram that's why I didn't find it in the first view of magisk. So I finally installed it and RCS works so thanks a lot for your help and your work.
[Magisk] Nergal di Cuthah:
Magisk uses the default file picker, are the two screenshots the same file picker? I'm leaning toward they aren't . If they aren't can you see the 16.6 in the default file picker.

Edit: you posted while i typed, but sounds like i was right so good feelings, glad you're working again
[Magisk] zgfg:
In the Files switch to Storage or use a decent

file mngr (you have root, you can use MiXPlorer with access to everything), instead of relying on those baby toys like (My) Documents, Download, Pictures, etc - you will never know real path to your files and be aware potentially their copies everywhere (while Magisk and other tools for modders, assuming to be power users, address files by their proper paths)
[Magisk] sawdoctor:
You can always take the fingerprint from 16.6 and use it with 16.5. Most of us with working rcs were using that fingerprint anyway before chiteroman released the update
[Magisk] manjaroid:
The Files app isn't useful for managing much but since it's integral to the locator it can be useful for confirming file system troubles. @nanoumax2's problem almost sounded serious.
[Magisk] V0latyle:
Yeah I figured you had downloaded from a different source or something, apps are stupid and like to save files wherever they want instead of the common download folder

@bluerar how you doing?
[Magisk] badabing2003:
PixelFlasher Update Release:

July 11, 2024 v7.1.0.0 change log:

Add license headers to source files.

Improved logging.

By request, PIF Manager now supports processing .img files to extract PIF prints. (This is in addition to supporting .zip files of factory / OTA images).

Check keybox.xml tool now provides more extensive report about the keybox.