yashsingh1/xdaforums huggingface dataset:
[Magisk] chiteroman:
v15.7.1 released !

This build (should) fix all issues with older release.

Release v15.7.1 · chiteroman/PlayIntegrityFix

Fix crash issue when JSON file have comments. Fix hooking in older Android versions. Fix CTS profile / Device verdict failures in few devices due bad spoofing code. Fix spoofing Provider issue. Add...

github.com
[Magisk] Zilla0617:
Just to confirm, this should be used assuming you have a working fp?
[Magisk] xcl1pse:
New module include working fp to give some time for you to search a new one. If already have one, this update should not be a problem. Just place custom fp to correct place and check the log to make sure that custom fp one is used by the module
[Magisk] zfk110:
Praise God! I'm passing it with the newer update. on the new update I didn't use PlayCurl module as I was using it with older ver. TY!!

View attachment 6065602View attachment 6065603
[Magisk] Zilla0617:
After installing I'm still getting device not certified
[Magisk] xcl1pse:
Revert to previous version work?
[Magisk] Zilla0617:
I

That's the problem I can't get any of them to work
[Magisk] xcl1pse:
Already tried with oldest release available on github like 14.0 etc? Ofc with working fp. The problem raise because chiteroman only push 1 commit per release so it's hard to narrow down the regression until your device tried previous release and other problem like banned kernel name
[Magisk] Zilla0617:
To clarify i was referring to having my device being certified. Although my device is listed as device not certified, i can download apps like netflix and disney plus. However, unable to add cards to wallet. This is on playintegrityfix 15.7.1.

On previous versions i couldnt do none of the aforementioned actions, just trying to get device certified by finding working prints
[Magisk] aadish:
Just installed v15.7.1 and it works! Device is certified and I was able to successfully add my card to Wallet (Android 9 on LG V35). Thank you!
[Magisk] xcl1pse:
Ah got it, for wallet problem you can search on this thread for more information as I don't use wallet again
[Magisk] Utini:
Is your fork still up-to-date and recommended or should I wait until you update your fork or rather switch to chiteroman 15.7.1?

Thanks!
[Magisk] zgfg:
Playcurl is compatible with the PIF v15.6, v15 7 or the latest v15 7.1changes?

Btw, first of all, you had to check the PIF log to see does PIF v15 6 or higher correctly reads custom PIF json, etc
[Magisk] pauljblo:
I have the same problem. Just tried latest version and still not working.
[Magisk] majorfigjam:
Definitely it's up to date, and far more stable than the latest Chiteroman 15.5/6/7/7.1 ....

It uses a different print format, but otherwise still works flawlessly (for me).
[Magisk] pauljblo:
Which fork is that
[Magisk] V0latyle:
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

@osm0sis makes a point of keeping his code clean, he doesn't reinvent the wheel every time he makes a change. And, when people suggest changes and improvements he's actually willing to listen and collaborate 👀
[Magisk] sga999:
I can't believe I have so much trouble with scripts. badabing helped me the other day with his. He said to put it in /data/local/tmp. I've tried that with yours, made it executable. In adb shell with su, I entered ./kr_offset.sh --auto, and it says "inaccessible or not found". Does it have something to do with that top line? badabing had #!/bin.sh but you have system before that. Sorry that I'm so bad at this!

EDIT: I entered the script name incorrectly. It would be nice if I saw this before I wrote that! Apologies.
[Magisk] Spartacus500:
v15.7.1 released !

Not working 🤷😔
[Magisk] matfcb:
Basic, Device passed, Device certified in Google Play Store on 15.7.1. Xiaomi Mi 9 Pro 5G Android 11.
[Magisk] pauljblo:
With the new version it breaks hiding apps from root went back to v7 fork. Still can't fiqure out why won't pass device integrity
[Magisk] Captain_Throwback:
Why would you leave the Fork 😂
[Magisk] chasehammer:
After Feb OTA and installing this Im still failing Strong Check. *shrug*
[Magisk] pndwal:
And worth noting that while things generally work with GMS components in denylist with DenyList not enforced (eg with Shamiko), PIF functions will certainly break with DenyList enforced (although PIF should remove GMS processes on reboot in that case if it's working as it should), so if swapping Shamiko for DenyList for testing, also ensure Google Play Services is not in the list. 👀 PW
[Magisk] tom1807:
The you have to unroot your mobile and lock the bootloader.

Passing Strong with unlocked bootloader is not possible, only basic and device passing is necessary.

Cheers

Tom
[Magisk] V0latyle:
Was it working before you updated?
[Magisk] Spartacus500:
No, not working 🤷
[Magisk] xSnowLeopardx:
Why update when you can chill with me @ 14.4 ;)
[Magisk] okij:
How true! I'm also still on 14.4, using my FP from beginning of December, no problems at all. :)(y)
[Magisk] V0latyle:
Probably a configuration issue then. What's your setup? Magisk version, modules, DenyList configuration?
[Magisk] Spartacus500:
Samsung Galaxy S7 edge Custom Pie 9.0 Rom NFE everything worked, i.e. SafetyNet Fix and passed the MEETS_DEVICE_INTEGRITY test without any problems on the older version of Google Play Services, on the new version no playintegrityfix works, only MEETS_BASIC_INTEGRITY all the time 😔
[Magisk] sga999:
This is a great tool. I'm trying all options, just for fun, because I've already had gotten the patch done before you created this. I have tried all 4 usages, and the only one that fails for me is the --image one. I've tried a few different boot image files, but they all get:

Unpacking boot image...

ERROR: Failed to unpack boot image.

I'm sure I'm missing something. Amazing how many mistakes I make when trying this stuff.

EDIT: Are these lines the problem? Sorry if I'm off base.

if [ $mode -ge 2 ]; then

kernelFile="kernel"

[ $quietMode -eq 0 ] && echo "${NL}Unpacking boot image..."

/data/adb/magisk/magiskboot unpack "$imageFile" 2>/dev/null

if [ ! -f "$kernelFile" ]; then

echo "ERROR: Failed to unpack boot image." >&2

cleanupQuit 7

fi

fi

EDIT2: I deleted a few lines there (I think line 264 for 4 lines), and it got past that but later on after unpacking the boot image, it gets:

+ /data/adb/magisk/busybox strings -t d kernel

+ grep -F 3.18.140-lineage-g4b91b133f4b7

strings: kernel: No such file or directory

So strange because the same busybox occurs with --kernel (vs. this --image), yet it works. I tried googling, and it says something about missing libraries? But they aren't missing for --kernel!
[Magisk] zgfg:
Do you mean com.google.android.gms upgrade v24.03.15 from Jan 24?
[Magisk] Spartacus500:
Yes, today new version update
[Magisk] osm0sis:
It's because of exactly what I told him for 15.6, but he continues to never learn from his previous experience or my repeated advice.

I don't plan on updating my fork until next month maybe for just some minor QoL stuff because it simply works great and doesn't need much now. Anyone tired of constant updates that break more than they fix here is welcome to come try the quiet life with my fork; this is all why I created it in the first place. 👍

That or I'd recommend camping out on the historic good PIF versions like 14.0, 14.4 and maybe 15.1, though they all also have their varying issues. 🤷‍♂️
[Magisk] pauljblo:
Do you think a older magisk version would help in passing device integrity
[Magisk] osm0sis:
No, newest would help, if anything, due to resetprop and Zygisk improvements.
[Magisk] pauljblo:
Anything you can think of I could try to get it working?
[Magisk] pndwal:
To see if PIF is working you should be checking Play Integrity's Device integrity verdicts, not Play Protect certification status... If you have MEETS_DEVICE_INTEGRITY (ie. the default Device integrity label, nb. both MEETS_BASIC_INTEGRITY and MEETS_STRONG_INTEGRITY are opt-in Device integrity labels for app Devs) PIF is doing it's job...

Check using Play Store Developer options (enable by tapping About, Play Store version 5 times) menu, Check integrity, or in Play Integrity API Checker app.

Only check Play Protect certification status after achieving MEETS_DEVICE_INTEGRITY as it may still be failing even with MEETS_DEVICE_INTEGRITY (ie. PIF spoof working) until some time (days?) has passed or until you clear Play Protect Service (newer devices only) data or (alternatively) wipe Play Store data several times to force Play Store to recheck Play Protect service status...

🤠 PW
[Magisk] Zilla0617:
Thanks for the clarification. Unfortunately I'm not meeting neither device integrity or basic integrity. And to make matters worse every now and then I'll get Google play services crash warning
[Magisk] Nergal di Cuthah:
I went as far back as the quoted posts allowed and could not find where you told us what phone what other plugins where'd you get your fingerprint and other vital information. Maybe i missed it because i went back a page to the first time you didn't have a quote quoted chit

Could you (maybe again) provide that info :)
[Magisk] mxz55:
I've verified that the module works well for Motorola Edge 40 Pro running LineageOS for said device, so there don't seem to be compatibility issues with the latest hardware, like sm8550. So far i haven't seen any signs of that first_api_level problem from OP, despite that it launched with Android 13. Thanks
[Magisk] chiteroman:
V9.3 released!

Use shadowhook instead Dobby

Drop support for x86 and x86_64 (shadowhook doesn't support them)

Removed useless code

Removed libcxx

Using system STL

Should work in more devices

Release v9.3 · chiteroman/PlayIntegrityFix

Use shadowhook instead Dobby Drop support for x86 and x86_64 (shadowhook doesn't support them) Removed useless code Removed libcxx Using system STL Should work in more devices

github.com
[Magisk] chiteroman:
I'm using stable Magisk Delta v26.1 and I can install Netflix and their games...

You are using unstable Magisk build... Maybe something is wrong with it, I told you before, try to change Magisk, use official one, stable Magisk Delta or Magisk Alpha...

Completly uninstall Magisk and check if you can install them.
[Magisk] blinoff82:
I confirm functionality on my 1+9RT with latest stock Oxygen 13.1 and Magisk Delta (26301). All banking apps and NFC payment via MirPay (Russian GPay) works fine. Thx dev.
[Magisk] chiteroman:
Try reinstalling rom.
[Magisk] zgfg:
v9.3 good for me
[Magisk] Vision:
Thanks for advice and answer, keep the good work, that's what I'm trying to avoid
[Magisk] Bladius:
How create log?
[Magisk] Homeboy76:
Create a log
[Magisk] CiLiBi18:
Ok thanks I'll test it ASAP, thanks for responding
[Magisk] CiLiBi18:
Still not working with 9.3 :(

How can I get module logs ? (I'll ask google btw)
[Magisk] CiLiBi18:
Don't know if it helps.
[Magisk] Bladius:
Can this be done in Termux without ADB? I don't have a computer and ADB doesn't want to work on ArrowOS
[Magisk] chiteroman:
From device you can open Termux, type "su" and then run: logcat | grep 'SNFix'

Seems like your Android build is very strange... 😯
[Magisk] zgfg:
Attachement
[Magisk] osm0sis:
Anything I could think of to help you get 15.7.1 to work? ..What? 🤔:confused:
[Magisk] majorfigjam:
Uninstall all Chiteroman versions, install Osm0sis v7, find a working print (maybe copy from Chiteroman latest if it hasn't been banned yet & use Osm0sis supplied script to convert format), install it in correct folder.

Then stop and clear caches of Play Services and.Play Store, and retest in Play Store developer options.

If it doesn't work, then there are other issues, eg kernel string, various magisk apps or lsposed interferences.
[Magisk] Zilla0617:
Nah I didn't mention it. Im using P8P on stock rom with Despair Kernel. I got my previous fingerprint from daboynb/PlayintegrityNext. Can't recall what version but it was from around middle of December and was working fine till about a couple of days.

Don't know if Google banned the print or coincided with me upgrading to Magisk 27 beta. But ever since I've been struggling to find working prints. Before upgrading to Magisk 27 beta I was using Shamiko .75. I had no Google apps on the deny list. Just some apps that don't like root (Aetna, ADP, etc.).
[Magisk] pndwal:
Please clarify, still no Google processes in denylist?... Which PIF build? No other mods like selinux change etc?... 👍 PW
[Magisk] purgy:
I think despair kernel is on the "naughty list", if you look through the last maybe 10 or so pages, there's a list posted by @osm0sis which details the known ones so far.
[Magisk] HippoMan:
Small issue: I had to tap "About, Play Store version" 7 times.

I'm only mentioning this in case someone also needs 7 times on their device but gives up after 5 taps.
[Magisk] osm0sis:
You're thinking of Deathly. :p

Despair wasn't banned last I checked for it.

Very, uh, positive kernel names these days... :LOL:
[Magisk] pauljblo:
No I mean to get it to pass integrity
[Magisk] Zilla0617:
I think u missed the part when I mentioned that were no Google processes on the deny list. As for pif module, it was version 14 of daboynb/PlayintegrityNext. No mods like selinux
[Magisk] pauljblo:
What do you mean convert format of the print I thought they both use the same apart from the filename and location. I used a working pif from pixel flasher
[Magisk] majorfigjam:
Read my reply, or your DM inbox. And no, they use different formats and file locations. That may be your issue?
[Magisk] pauljblo:
Where do I find the tool to convert the format to test
[Magisk] majorfigjam:
Use the print I sent you.
[Magisk] pauljblo:
Thankyou. It still didn't work unfortunately
[Magisk] pndwal:
Bit stumped, but no BASIC_INTEGRITY is a clue especially if it's always lacking.

It can be caused by some print props/fields l with recent Google "banning", but mostly you'll only lose DEVICE_INTEGRITY (test by ensuring fingerprint string is definitely not a real one by adding random characters and you should then have BASIC_INTEGRITY, otherwise it's fairly certain print/prop set is not the issue).

... Custom ROMs/kernels should still pass BASIC_INTEGRITY with no spoofing without Magisk or other mods installed if not breaking security Linux rules etc (you can check that without root), and with Magisk installed PIF should be hiding root from DroidGuard/GMS, so perhaps kernel or other setting is causing your Despair... Some ROMs/kernels just break BASIC_INTEGRITY, but so do many other factors including mods/modules... So test with all other modules disabled also... 🙃 PW
[Magisk] V0latyle:
Forced update, still passing for me.

Try clearing Play Services data. If that doesn't help try a new print
[Magisk] Zilla0617:
That's so weird about what's going on, I don't have any of three. I even removed root to see if I can get either device or basic integrity and it didn't work. I have a bad feeling I'll have to factory reset my phone to resolve this issue.

I highly doubt it's despair kernel, he added a fix to his and his kernel was never blacklisted. There are others who are using the kernel with no issues passing both basic and device integrity. I'm stumped as well
[Magisk] Utini:
Alright. I guess it's time then for me to move from 13.0 to your fork :)
[Magisk] owenjm:
Ah, interesting, thanks. Upgrading to PIF 15.7 and using the built-in print brings back Device for me, so that must've been it. Annoying the other prints I'd found all must have all been banned in that batch, though ...

Yep, I realise that, but I'd hate to provide any identifiable kernel string that could be banned. Paranoia seems strangely healthy at this point ... :)
[Magisk] osm0sis:
perf and anything generic will never be banned, no need to be paranoid. 😄
[Magisk] owenjm:
If it helps, I just switched over from PIF to Osmosis' PI Fork v7. I tested the built-in PIF 15.7.1 print, using PixelFlasher to convert the format. It works for me as of writing this (although I'd guess that print will get banned fairly soon).

PixelFlasher makes the print-finding process pretty much failsafe.
[Magisk] pndwal:
With no mods and no root you should certainly pass basic if kernel dev didn't break basic android/linux security protocols or try to spoof something Google can detect... Custom kernel strings they're now detecting should only break DEVICE_INTEGRITY anyway...

Did you edit system at all or ever use any TWRP flashed mods etc?... If so a dirty flash of stock ROM + custom kernel may actually be enough (and easiest way to remove system mods or corruption)...

Factory reset would fix anything in /data that's causing issues but I can't think what. PW
[Magisk] Princknoby:
Can anyone tell me why I can't change the number of characters in the kernel string? I tried changing it to perf (the kernel name was lineageos), and the rom didn't start. I edited it with a hexadecimal editor.

It only works when I keep the same number of characters.

In this case, would I have to recompile the rom using perf name for the kernel?
[Magisk] Spartacus500:
I've tried clearing Google services many times with no success 🤷 fp doesn't work at all for me, it means it downloads a new 'pif', but it's still the same fingerprint, and the fp log stays like this:
[Magisk] V0latyle:
Try using Pixel Flasher to pick a new print
[Magisk] wrongway213:
This is simply the nature of hex editing... You can't patch characters that aren't supposed to exist, or leave out characters that are expected.
[Magisk] nicoco19:
Hello everyone,

I wanted to give you a little feedback, my phone is a Samsung Galaxy S23 Ultra, it is Rooted, yesterday by launching the Magisk application it suggested that I update my version of Magisk 26.4 to the version from Magisk 27.0 what I did.

Then, in the Magisk modules, I had an old version of Play Integrity Fix (Play Integrity Fix_V15.1), unfortunately my Play Store was no longer certified and it was impossible for me to download certain applications such as Disney+, Netflix. .. Then I realize that I have the possibility to update my old version of Play Integrity Fix_V15.1 to the new version of Play Integrity Fix_V15.7.2, so I do the update and the installation, and out of curiosity I tell myself that we are going to test, so I empty the cache and I also empty the storage of the Play Store application, then I go to about the Play Store and there I see that it is certified again and that I can download applications such as Netflix or Disney+.

There you go, there you go, I just wanted to give you a little feedback.

Thank you again for your help everyone.

Nicoco19
[Magisk] TheFreeman193:
Good spot! There was a mistake in the script where passing a relative boot image path caused that error.

The script processes all files in a temporary directory to avoid clobbering people's image/kernel files in the working directory, but it didn't get the absolute path of the image before changing to the temporary location. It's now fixed. 🙂
[Magisk] mike.s:
If you shorten the string, everything after gets moved up, to a new location. Then all the linked code breaks because it's no longer pointing to the right place, because the code has changed location. And it's not just code, the same applies to any embedded data.
[Magisk] osm0sis:
Just for everyone's knowledge, 15.7.1 reverted the switch to cJSON and fixed the USNF and GMS DenyList checks by moving them back to post-fs-data.sh like I told chit was necessary, but he forgot/chose not to move back the important early resetprops, leaving things broken for some users. 🤨

That's fixed in 15.7.2, but now chit has reverted to include another change we have also previously directly discussed being a bad idea, so things will now be broken for a different group of users, specifically those on framework-level spoof ROMs. 🤷‍♂️

His Xiaomi.eu app disabling still has also never correctly worked, though I've made him aware of it a few times.

None of these issues are on my fork, because my memory is long and I develop methodically. 👍
[Magisk] dosbuddy:
Where is the official announcement of 15.7.2?
[Magisk] osm0sis:
Right here I guess?

Releases · chiteroman/PlayIntegrityFix

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

github.com
[Magisk] dosbuddy:
Sure. But in this thread?
[Magisk] osm0sis:
Not sure why it matters? It's released to auto-update 4 hours ago so it's therefore released.

PlayIntegrityFix/update.json at main · chiteroman/PlayIntegrityFix

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

github.com
[Magisk] dosbuddy:
Ok, so I have to ask me myself, why I am reading everything here...
[Magisk] Umgak:
Kernel stuff is actually a fixed width buffer, so you don't HAVE to keep the width, so long as you're careful.

In your hex editor, you have to replace all bytes after the uname string with 00 bytes, NOT delete them. Deleting them will cause offsets later into the file to change, which will send you into fastboot as it will fail to read data or jump to code after that name string.

For more technical people, it looks like it's a char[64].

View attachment 6065997

DO NOT edit this with a normal text editor. Edit it with a hex editor (HxD pictured).

View attachment 6065995

EDIT: changed image to have a shorter and longer name, and threw it in a hide tag so that it's not huge. Sorry!

EDIT 2: Added note about how null-terminated strings work.
[Magisk] Spartacus500:
After installing PlayIntegrityFix_v15.7.2, the same thing 😔 I also tried 14.4 etc. MEETS_DEVICE_INTEGRITY ❌ doesn't work on any of them 😔
[Magisk] V0latyle:
You're passing BASIC though, so I think you just need to find a working print.
[Magisk] Spartacus500:
I don't know if it's true, but maybe it's because my kernel is banned 🤔 It's not on the list, but I know that not all of them are listed there, I have them MoRoKernel 🤷
[Magisk] V0latyle:
That's also a possibility. I believe others have covered how to change that, so I would look into doing that first, especially if the print you have been using passed previously.
[Magisk] Spartacus500:
Yes, but it passed the MEETS_DEVICE_INTEGRITY test when Google hadn't introduced kernel checking yet, so it's probably a boot hash.
[Magisk] :
So if you'd post the exact outcome of uname -r from a terminal emulator, you might be lucky for osm0sis to check it.
[Magisk] V0latyle:
If you tag him and ask really really nicely, I'm sure he'd be happy to help
[Magisk] tom1807:
That you have an idea what to do, when Play Integrity Fix fails.

Cheers
[Magisk] Umgak:
Don't need it, I just dumped the name from the image.

-MoRoKernel is banned.
[Magisk] badabing2003:
Yes it is banned
[Magisk] :
I don't think tagging him in his livingroom is necessary. 😉
[Magisk] Umgak:
I see we were both flashing modified kernel images for test purposes.
[Magisk] Utini:
Switched from chiteromen 13.0 to your latest fork.

I still pass basic but not device integrity (but I also have not installed a custom fringerprint).

So it seems like everything is working as intended for now.

Once some of my apps fail to work due to missing device integrity, I will start looking for a fingerprint.
[Magisk] :
The problem - at least for me - is that playstore hides apps from you that you might be interested in if you don't pass DEVICE.
[Magisk] Utini:
You can download the .apk via google or backup it from another device.

I did that with netflix. Netflix then updates correctly and also starts as it is supposed to.
[Magisk] :
That would imply that I already knew that app. 😉 A game like Adventure Reborn I wouldn't have found.
[Magisk] samhhmobil:
Just updated from 15.7.1 to chiteroman's 17.2

Aaaargh, it leads to a crash of GooglePlayServices.

Falling back to 15.7.1 and it works again.

samhhmobil

(PS:

My configuration

Xiaomi Mi10Tlite5G (gauguin)

LineageOS20 (Android13)

Magisk 27

MindTheGapps

Fingerprint changed to work by MHPC)