yashsingh1/xdaforums huggingface dataset:
[Magisk] purgy:
I'm still passing with 13.3 and whatever fp it's using as default.
[Magisk] pndwal:
@chiteroman notes:

v13.7

Latest

Removed custom resetprop.

Removed custom props spoof.

Removed weird code.

If you want an undetectable resetprop, use Kitsune Magisk.

If you want to spoof your own props, modify the props in source code and build by yourself.

Should work and don't crash nothing.

Maybe in a future I do a custom spoof version... But I won't release it as stable build.

I recommend to clear GMS data and cache before reboot.

👀 PW
[Magisk] HippoMan:
I had originally skipped 13.2 and 13.3 and previously went from 13.1 to 13.4. But given your report as well as the number of other positive reports about 13.3 that I've read here, I have now switched to that version, and thankfully, I still have BASIC and DEVICE integrity.

So far, so good ... although as I've mentioned, I avoid banking apps like the plague, so I can't comment on how any of them might or might not work under the current configuration of my device: Nothing 2 OS 2.0.3 (A13) running Magisk Alpha 26401 and LSPosed-Zygisk 1.9.2.
[Magisk] LuisNara28:
Is possible to pass strong check?

View attachment 6036603
[Magisk] HippoMan:
To get your answer, please read the OP (first post in this thread).
[Magisk] V0latyle:
No one ever reads the OP 😕😒

I haven't been keeping up with the goings on, Thanksgiving stuff. Are only custom props breaking or are old versions failing? I'm still on 13.3 and everything is good here, but I don't know if I want to tempt fate by clearing Play Services/GSF data to see...
[Magisk] HippoMan:
Based on what I've been reading here, it seems like 13.4, 13.5, and 13.6 are kind of "iffy" ... it depends on the device, the OS version, the manner in which the print is managed, and perhaps even the version of Magisk as to whether or not people are reporting success or failure with those versions. However, 13.3 seems to generally be reported as being functional ... at least noticeably more so than the newer versions.

Even though 13.4 has been working well for me, I recently decided to go back to 13.3, just because of the quantity of positive reports about 13.3 in relation to those about the newer versions. And it's also working well (i.e., BASIC and DEVICE integrity).
[Magisk] pndwal:
If you wish to test 13.5 only... custom settings were likely breaking it since 13.5 defaults were ok for A12 LV and less... A13 users actually needed the pif.prop to override system "null" for first API with "32" or less set...

Backup 'old' won't do anything unless moves to working directory... Can test just by removing pif.prop, but only good reason keep 13.5 / 13.6 now would be to try custom props... If not, I'd just be using latest... Nb. For 13.7: • Removed custom props spoof... 😉 PW
[Magisk] dimm0k:
let me know where you're headed with the Bonvoy cracking!
[Magisk] pndwal:
If you/others can't use latest Bonvoy with TJW Magisk ATM, they may need to wait for next Magisk build with native bridge loaded Zygisk (this massive refactoring is already merged upstream), or use Alpha which already has it... This allows effective hiding of Zygisk memory etc in combination with Shamiko like late Riruhide principle...

I'm using a CI TJW build with the commits and have no detection for latest Bonvoy app...

👍 PW
[Magisk] BROKEN1981:
Thanks for the heads-up. Ever since 13.3 I've been having issues. Thing is, they all pass the test except for the newest version. I'll see how 13.3 goes.
[Magisk] BROKEN1981:
Woolworth is still around? I thought they closed in early 90's?
[Magisk] rseiler:
Probably a reference to the one in Australia (or maybe elsewhere), which has a different lineage than the defunct U.S. one. "Woolies" might even be their #1 store.

Hey, do you or someone know what is meant by a "clean install" of this module? I've seen it mentioned a couple times. Is that simply removal of it and a reboot or something more?
[Magisk] arda99:
So I tried 13.7 with custom prop...

Most values are defined in the java, but SECURITY_PATCH and first_api_level is in the c++, so make sure to change both. The java classes.dex can be updated on the fly but must reboot for the the zygisk module(arm64-v8a.so), so obviously it's not very mod friendly.

Oneplus OOS11 with Kitsune Magisk(Magisk delta).
[Magisk] highdiver_2000:
Out of the 2 apps, I got the Trust Bank app to work. Citibank SG still detects the root/bootloader even after clearing data and hiding it.
[Magisk] Nergal di Cuthah:
Download (don't install) the update in magisk ,Remove the module, reboot install the update from zip
[Magisk] BillGoss:
Not in Australia!
[Magisk] LuisNara28:
Sorry, I read it, but some people posted screenshots passing the strong verification and I thought it was possible.
[Magisk] amk316:
13.6: Property Modified (4)

13.7: Property Modified (6)

S23
[Magisk] rseiler:
This sounds crazy, but when I tap Remove, I see a faint outline of a trashcan appear, but it does nothing. The only other thing that changes on the screen is the word "Remove," which is now "Restore." If I tap it, then Remove reappears. There appears to be no way to remove it, but that can't be, it must be some kind of graphical glitch with the trashcan.
[Magisk] prot-:
Would be nice if you could explain how you do these things ? Got no idea how to custom spoof
[Magisk] craigacgomez:
This is the expected behaviour. When you click remove, you have the option to undo that operation before you reboot. The module isn't removed until you reboot
[Magisk] FIERA03:
Custom props can now only be done by those who can build some modules, v13.7.

In other words, chiteroman seems to have given up on stable support for custom props (it was mentioned in Telegram that they would be added in experimental version).
[Magisk] Lada333:
A reboot should be enough. As pndwal pointed out here, you might want to clear storage of GMS before rebooting.
[Magisk] Lada333:
Or maybe he was compromised/contacted by Google? 🛸👽

/s
[Magisk] FIERA03:
lol

I think he will close all PIFix Projects then
[Magisk] FIERA03:
The previously osm0sis's v13.4-mod is is the last PIFix I can "play" with stably.

I'm using it by rewriting the module.prop to prevent updates from coming.
[Magisk] rseiler:
Yes, it worked.

On GMS (Google Play services), I've somehow been able to get away with just cache. I try to clear the data for this one, but it never seems to manage to do it, or at least finish. My phone is on the slow side, but it shouldn't be that slow. I'm used to being able to clear storage in other apps almost instantly.
[Magisk] gpvecchi:
What happens if I don't clear caches? That's a PITA!
[Magisk] highdiver_2000:
Do not clear GSF data ever. Unless you want a random app hanging. The only fix is reinstall.
[Magisk] zgfg:
There was something that always caught my eyes - those logs start with PIF/Native while the 'real' ones are PIF/Java
[Magisk] zgfg:
For any Magisk module:

Remove only creates file remove in the module's folder:

/data/adb/modules/<module>

Un-remove deletes that file

You can also do that manually by root explorer, or from TWRP (that's also what the module mngmt tool in eg OrangeFox does)

On next reboot, Magisk finds the remove file and starts the uninstallation procedure:

- if the module has uninstall.sh script it executes the script (it may delete some files that module installed out of it's folder and so)

- it deletes the module's folder

----

Similarly for Disable, it creates the disable file, and on next reboot Magisk will not load that module

Those disable or remove file can be empty, doesn't matter but must be called exactly as that, lowercase and no extension

You create them by touch comnand

----

When you Install a folder, Magisk creates update file in the module's folder and prepares the new folder with the new module's stuff at

/data/adb/modules_update/<module>

On the next reboot it moves that subolder from modules_update to modules and loads the new module

---

Hence:

- Eg, when you update the module in Magisk app, you don't need to reboot immediately

- You can go to that modules_update subfolder and do some changes if you want, like edit the service.sh script (or remove it or rename to eg service.bak if you don't need) and the pif.prop or pif.json file

- Then you reboot, the module will already load with your changes, so you don't need to do changes now and then reboot one more time
[Magisk] Gilg@mesh:
13.6 still works for me on P8P, can I just update to 13.7 without clearing anything?

edit: updated to 13.7, not clearing anything, all good.
[Magisk] xSnowLeopardx:
Still chilling at v13
[Magisk] Vision:
Oh understand put it again in the module zip the pif.json file and flash it, the json file can edit with notepad from Total Commander app? Or need another notepad?
[Magisk] badabing2003:
Yes you can, any text editor would do.
[Magisk] Vision:
Now i see the new description, i have this version 😂the pif.prop is the best feature,now all gone, I'm using for play store certified and not for bank, must module keep simple but with pip.prop (or something similar) feature inside, many not know how compile a classes.dex and change the model of the phone used by default

View attachment 6036719
[Magisk] pndwal:
Re this convo:

And my response above:

... Just addressing this:

But you already said you don't use latest!:

... Have you been able to update now? 🤔 PW
[Magisk] xSnowLeopardx:
You never gave me my answer, for the PW thing :/
[Magisk] digger16309:
I did reply in the other thread about a week ago and it worked perfectly with the latest version at that time. However, I just updated again and have now found that version detects Magisk. I reverted to the prior version.
[Magisk] rom-g:
Just upgraded to v13.7 and everything seems to be working nicely again.

No more booting issue.

No more "play services has stopped".

Device Integrity and Basic Integrity are GREEN.

Device appears Certified in Google Play Store.

Thanks a lot @chiteroman
[Magisk] andi_79:
strong is red at OP9 with magisk 26.1 and Zygisk, shamiko 0.7.3, no other saftynet fix is enabled
[Magisk] eac5:
Installed this in place of Displax and did not work - Play services was constantly crashing and all 3 checks failed. Had to reinstall/clear all Google stuff to fix and go back to Displax 1.3, strangely 2.0 was also producing the same errors despite working before.

This was the logcat output, some how it seems the dex file was not copied to the GMS dir during install? Pixel 7, Lineage OS

08-01 20:39:12.271 16370 16371 I SNFix/Zygisk: [ROOT] Received app data dir from socket: /data/user/0/com.google.android.gms
08-01 20:39:12.272 16370 16371 E libc++abi: terminating with uncaught exception of type std::__ndk1::__fs::filesystem::filesystem_error: filesystem error: in copy_file: No such file or directory [/data/user/0/com.google.android.gms/SNFix.dex] [/data/adb/SNFix.dex]
08-01 20:39:12.293 16375 16375 F DEBUG : Abort message: 'terminating with uncaught exception of type std::__ndk1::__fs::filesystem::filesystem_error: filesystem error: in copy_file: No such file or directory [/data/user/0/com.google.android.gms/SNFix.dex] [/data/adb/SNFix.dex]'
08-01 20:39:12.327 16368 16368 I SNFix/Zygisk: hooking
08-01 20:39:12.327 16368 16368 I SNFix/Zygisk: Get __system_property_read_callback at 0x79d96a8d60
08-01 20:39:12.327 16368 16368 I SNFix/Zygisk: get system classloader
08-01 20:39:12.327 16368 16368 I SNFix/Zygisk: create PathClassLoader
08-01 20:39:12.327 16368 16368 W System : ClassLoader referenced unknown path: /data/user/0/com.google.android.gms/SNFix.dex
08-01 20:39:12.327 16368 16368 I SNFix/Zygisk: load class
08-01 20:39:12.328 16368 16368 I SNFix/Zygisk: call init
[Magisk] chiteroman:
Yep, more problems with this... I don't know why this happen but I know a solution.
[Magisk] zgfg:
Strong fails since Bootloader is unlocked.

This or other modules do not spoof Strong Integrity but only Device and Basic
[Magisk] Johnny Eng:
S23 Ultra June Patched One UI 5.1

I removed Unsf by Displax 2.0 Mos strong.

Installed version 5.0

Rebooted but strong still failed, try to use default font - same

Any idea? Thanks
[Magisk] Stillhard:
Well, i don't know if this will be called as an idea..

But i'll try my best :D aaaand... the idea is: maybe, just maybe if you read the fist post from op here, you would get my idea
[Magisk] Johnny Eng:
Oh thanks for highlighting! So what the differences between this and Displax Unsf?
[Magisk] Stillhard:
Basically for now it's just ALL the same (earlier, this is as much as equal to Displax's STRONG one)
[Magisk] andi_79:
ok thanks. could this be the reason why my bank app doesn't work as it says its has an abnormality detected?

but the device is certified by the play store and YASNAC is also fine
[Magisk] Ramme:
Unfortunately, the fix no longer works with both version 4.0 and 5.0.

Can you do us all a favor and attach a version number to the uploaded file, otherwise it's really tedious to be Up-To-Date. Thank you. And thank you for your efforts.
[Magisk] zgfg:
Didn't you read that Google has fixed their glitch and module can no more spoof the Strong Identify
[Magisk] Spartacus500:
Today my Samsung 😳

MEETS_DEVICE_INTEGRITY ❌

MEETS_BASIC_INTEGRITY ✅

BASIC Integrity ✅

CTS Profile Match ❌
[Magisk] Lord Sithek:
Dang, for me too o_O

Went back to Displax mod 2.4.0 1.3 and sadly it's same... Seems like common thing, all my devices fail DEVICE_INTEGRITY

EDIT: I fogot to remove Play Integrity Fix by @chiteroman, looks like @Displax's 2.4.0 1.3 still passes DEVICE_INTEGRITY
[Magisk] chiteroman:
Uninstall my module and install Displax one.
[Magisk] Lord Sithek:
FYI, Displax's 2.4.0 2.0 breaks all 3 checks for me, 1.3 passes two out of three
[Magisk] Spartacus500:
Thank you 👍 now pass 🙂
[Magisk] Bladius:
Google messed up againView attachment 5969331View attachment 5969333
[Magisk] Spartacus500:
For me 2 Meets integrity pass
[Magisk] Homeboy76:
The fix is, use @Displax module:

safetynet-fix-v2.4.0-MOD_1.3-microG.zip

or

safetynet-fix-v2.4.0-MOD_1.3-Riru.zip

or

safetynet-fix-v2.4.0-MOD_1.3-Zygisk.zip

Which ever one meets you phones configuration.

Please, remove [MODULE] Play Integrity Fix before you install Displax's module.
[Magisk] sawdoctor:
Thanks for this it's the only one that passes device and basic on the pixel fold. Displax latest releases from the op only passes basic now. Think this probably needs to be pinned in the OP's of both threads?
[Magisk] chiteroman:
Release CUSTOM SPOOF · chiteroman/PlayIntegrityFix

DO NOT USE THIS BUILD IF YOU AREN'T A DEVELOPER, ALWAYS USE LATEST STABLE. THIS BUILD IS JUST FOR TESTING PURPOSES. Removed custom resetprop. Fix JSON parsing. Less libs size. Few code improvements.

github.com

For advanced users 🤗
[Magisk] osm0sis:
There should be Native ones for security patch and first API level, but that's it I think. Good to know where the noise is coming from so it can likely be removed.
[Magisk] osm0sis:
Upload the props branch this release is from? Also, why stick with json? It's more annoying to work with in every way. 😛
[Magisk] chiteroman:
Because nlohmann solves all my problems and it's more easy to implement in code XD.
[Magisk] zgfg:
JSon.Net
[Magisk] Vision:
The feature pif.prop is good for many reason, is easy to understand from users and edit and anyone write own old fingerprint, and not all have the same fingerprint and send request to play ingritity, and split if anyone have different when request from play ingritity. example if google see a 10.000 request from the same device know his use this module and block the fingerprint and after must waiting again @chiteroman update the fingeprit, but if users have different fingerprint and send it request in play ingretity from different devices like 2000 of this 1000 of this and similar, google is more less block it all or maybe nothing because the request is less from different devices
[Magisk] pndwal:
Ah yeah... Was going to get back as low priority... Been asked before...

It's just my initials/way to sign off... Maybe I'm a creature of habit... Maybe my way of being non-conformist... Or maybe I just like to see to get people guessing! 😜...

Also, when I'm ready bored I do sign to indicate my real persona... My Sirius Cybernetics Corporation one I mean... "Let's build robots with Genuine People Personalities," they said. So they tried it out with me. I'm a personality prototype. You can tell can't you?...

Actually, it did serve a purpose... Way back when using the old XDA Labs app (not the last 'XDA App' recently broken by migration to new domain 'https://xdaforums.com' that was supposed to bring Search Engine Optimisation 😆 ... the one before the transition from vBulletin to XenForo...) I responded to a similar query here:

https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-83733755

Hope it satisfies your curiosity... I can't satisfy mine you know... brain the size of a planet and they ask me to park cars... Call that job satisfaction? 'Cos I don't... Don't talk to me about life... 🤖 Marvin.

PS. Very sorry for answering OT... And for non-hitchhikers here...
[Magisk] xSnowLeopardx:
OT: LOL I understood maybe 25% of that. But I get it now.

On topic: V13 still working, getting absolutely spoiled with it. Google, please don't ruin? Okay, thanks.
[Magisk] dosbuddy:
Seems not to work here. 😢

POCO X3 NFC on latest xiaomi.eu ROM.

View attachment 6036758
[Magisk] pndwal:
Mine edits ok.. why more annoying?... Just curious... PW
[Magisk] HippoMan:
At least trying to cope with the Googlefrinchian Telephone Sanitizers can provide a bit of distracting stimulus for your planet-sized brain as you continue to have to park all those cars.
[Magisk] chiteroman:
Uh? Send logs. Mine isn't crashing.
[Magisk] Vision:
@osm0sis, @pndwal, @zgfg, you know more than the rest of us, when you say which is the best and working version of this module, then we will flash it (Still have v13.3) and of course thanks to @chiteroman for all his hard work, and tries to make the best of his module for us
[Magisk] osm0sis:
Most developers hate it, just more difficult to parse, more difficult to create, more difficult to work with for end users (e.g. forgetting/adding a line-end comma breaks the whole thing, etc.) 🤷‍♂️
[Magisk] bycolxxiv:
Hey everyone, I need some help...

I installed MicroG systemless in Magisk using MicroG_Installer_Revived. Signature Spoofing works via Zygisk and FakeGapps Module for LSPosed. However when I activate the Play Integrity Fix Module (or USNF instead of PIF), MicroG keeps constantly crashing. Anybody got some ideas on how to fiy this?

Oh yeah and as soon as I disable the magisk module and reboot, MicroG services work mas expected again.

Just in case it helps, I'm on the Qin F21 Pro, Bootloader unlocked, rooted, Android 11.

Cheers and thanks in advance!
[Magisk] HippoMan:
JSON provides some ways to automatically parse various data types, and it therefore is potentially less error prone than parsing solely via shell-script facilities. This allows more reliable distinguishing between null, zero, and blanks, as one example.

Yes, JSON is somewhat less convenient for those of us who are creating and editing the data, but IMO that is counterbalanced by fewer parsing-related edge-case bugs that could make the software less reliable for us to use.
[Magisk] Vision:
Sounds silly, xml ?
[Magisk] HippoMan:
... or YAML, for that matter?

XML requires more typing than JSON and YAML, given the necessity for both start- and end-tags.
[Magisk] Vision:
Yeah for that, oh yeah i forgot, needed <string name=, the purpose is what is the best now
[Magisk] zgfg:
But this one is so simple, I always edit directly from MiXPlorer on the phone

Maybe I'm missing something but not sure if v1.37 really reads the json (I changed in v3 3 JSON to FIRST_API_LEVEL and rebooted but I see in logcat the same apoofs as before)
[Magisk] Vision:
I edit directly from Total Commander on the phone
[Magisk] chiteroman:
Hahahahha, good joke!
[Magisk] Vision:
Yeah, I know
[Magisk] dosbuddy:
Here is the crash log (of PlayIntegrityFix-PROPS_v1.0.zip):

*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'POCO/surya_global/surya:12/RKQ1.211019.001/V14.0.2.0.SJGMIXM:user/release-keys'
Revision: '0'
ABI: 'arm64'
Timestamp: 2023-11-25 16:59:57.139908519+0100
Process uptime: 0s
Cmdline: zygote64
pid: 9777, tid: 9777, name: id.gms.unstabl >>> zygote64 <<<
uid: 10183
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'JNI DETECTED ERROR IN APPLICATION: java_class == null
in call to GetStaticMethodID
from void com.android.internal.os.Zygote.nativeSpecializeAppProcess(int, int, int[], int, int[][], int, java.lang.String, java.lang.String, boolean, java.lang.String, java.lang.String, boolean, java.lang.String[], java.lang.String[], boolean, boolean)'
x0 0000000000000000 x1 0000000000002631 x2 0000000000000006 x3 0000007ff19dea30
x4 00000079fa833000 x5 00000079fa833000 x6 00000079fa833000 x7 00000000000049ea
x8 00000000000000f0 x9 b784458ad99e07b9 x10 0000000000000000 x11 ffffff80fffffbdf
x12 0000000000000001 x13 0000000004b95e80 x14 0000007ff19dd840 x15 00002064086a7599
x16 00000079df524d30 x17 00000079df4fe930 x18 00000079fa5d6000 x19 0000000000002631
x20 0000000000002631 x21 00000000ffffffff x22 0000000000000016 x23 0000000000000016
x24 0000007953cb627e x25 0000000000000001 x26 0000007954caf15c x27 0000007954617000
x28 b4000079f93a1660 x29 0000007ff19deab0
lr 00000079df4aecdc sp 0000007ff19dea10 pc 00000079df4aed08 pst 0000000000000000
backtrace:
#00 pc 000000000008bd08 /apex/com.android.runtime/lib64/bionic/libc.so (abort+168) (BuildId: 2f84be24a19d511a358a9050af5b3974)
#01 pc 0000000000634d04 /apex/com.android.art/lib64/libart.so (art::Runtime::Abort(char const*)+744) (BuildId: 824f7ca55f9cdc7b2f2fa3478577b69e)
#02 pc 0000000000016bc4 /apex/com.android.art/lib64/libbase.so (android::base::SetAborter(std::__1::function<void (char const*)>&&)::$_3::__invoke(char const*)+80) (BuildId: 96895dcea0300fc102132e9762aef6bc)
#03 pc 0000000000016184 /apex/com.android.art/lib64/libbase.so (android::base::LogMessage::~LogMessage()+368) (BuildId: 96895dcea0300fc102132e9762aef6bc)
#04 pc 0000000000458898 /apex/com.android.art/lib64/libart.so (art::JavaVMExt::JniAbort(char const*, char const*)+2524) (BuildId: 824f7ca55f9cdc7b2f2fa3478577b69e)
#05 pc 0000000000494534 /apex/com.android.art/lib64/libart.so (art::JNI<false>::GetStaticMethodID(_JNIEnv*, _jclass*, char const*, char const*)+1400) (BuildId: 824f7ca55f9cdc7b2f2fa3478577b69e)
#06 pc 000000000000fa5c /memfd:jit-cache (deleted)
#07 pc 000000000000ede4 /memfd:jit-cache (deleted)
#08 pc 000000000002d050 /system/bin/app_process64 (BuildId: ab730e57ddecfc72f8825b79ca4385b6)
[Magisk] HippoMan:
Looks like it might be an attempted dereference of null.

Missing input attribute, perhaps?
[Magisk] dosbuddy:
everything untouched, including pif.json
[Magisk] dosbuddy:
this makes it hopefully clearer:

:/ $ su -
:/ # logcat | grep PIF
11-25 17:19:36.469 14561 14561 D PIF/Native: Couldn't load pif.json file in memory
11-25 17:19:36.469 14561 14561 D PIF/Native: Received 'classes.dex' file from socket: 7298 bytes
11-25 17:19:36.469 14561 14561 D PIF/Native: Received 'pif.json' file from socket: 0 bytes
11-25 17:19:36.517 14561 14561 D PIF/Native: get system classloader11-25 17:19:36.517 14561 14561 D PIF/Native: create class loader
11-25 17:19:36.521 14561 14561 D PIF/Native: load class
11-25 17:19:36.521 14561 14561 D PIF/Native: call init

pif.json is in /data/adb/modules/playintegrityfix with 644 rights (root:root) and has a size of 274 bytes.
[Magisk] chiteroman:
I know where is the problem...

I'm not updating file descriptor pos 😂
[Magisk] chiteroman:
Yep, bugged file descriptor, that was my bad.
[Magisk] dosbuddy:
Works! Thank you!
[Magisk] TraderJack:
Also, if this is more than a one time thing (or if you prefer) you can modify the contents of the zip file before you flash. This is what I did to out my own pif.json file in so that it already exists in the correct location after flash.

Edit: I see this solution was posted prior. I responded before I got there!
[Magisk] dosbuddy:
Unlike the other module, this one (PlayIntegrityFix-PROPS_v1.1) doesn't like a missing system.prop file.

But an empty one will do.