yashsingh1/xdaforums huggingface dataset:
[Magisk] Ginosius:
v8.3 hits the jackpot!

[mastag@razerblade15 ~]$ adb shell "logcat | grep 'SNFix'"

08-29 14:55:27.787 8402 8402 D SNFix/Zygisk: Dex file size: 6072

08-29 14:55:27.787 8402 8402 D SNFix/Zygisk: Got __system_property_read_callback handle at 0x7cd25e50c4

08-29 14:55:27.787 8402 8402 D SNFix/Zygisk: getSystemClassLoader

08-29 14:55:27.787 8402 8402 D SNFix/Zygisk: InMemoryDexClassLoader

08-29 14:55:27.788 8402 8402 D SNFix/Zygisk: loadClass

08-29 14:55:27.788 8402 8402 D SNFix/Zygisk: init

08-29 14:55:27.789 8402 8402 I SNFix/Java: Set new device props

08-29 14:55:27.789 8402 8402 I SNFix/Java: Set new device props

08-29 14:55:27.789 8402 8402 I SNFix/Java: Set new device props

08-29 14:55:27.789 8402 8402 I SNFix/Java: Set new device props

08-29 14:55:27.789 8402 8402 I SNFix/Java: Set new device props

08-29 14:55:27.789 8402 8402 D SNFix/Zygisk: clean

08-29 14:55:27.930 8402 8402 I SNFix/Java: Set new device props

08-29 14:55:28.068 8402 8402 I SNFix/Java: Set new device props

08-29 14:55:28.630 8402 8481 I SNFix/Java: Set new device props

08-29 14:55:28.659 8402 8481 I SNFix/Java: Set new device props

08-29 14:55:28.660 8402 8481 I SNFix/Java: Set new device props

08-29 14:55:28.673 8402 8481 I SNFix/Java: Set new device props

08-29 14:55:28.897 8402 8460 I SNFix/Java: Set new device props

08-29 14:55:28.897 8402 8460 I SNFix/Java: Set new device props

08-29 14:55:28.901 8402 8460 I SNFix/Java: Set new device props

08-29 14:55:28.901 8402 8460 I SNFix/Java: Set new device props

08-29 14:55:29.138 8402 8460 D SNFix/Zygisk: Set first_api_level to 25 (Android 7.1), original value: 29

08-29 14:55:29.342 8402 8460 I SNFix/Java: Set new device props

08-29 14:55:29.344 8402 8460 I SNFix/Java: Set new device props

08-29 14:55:29.379 8402 8416 D SNFix/Zygisk: Set first_api_level to 25 (Android 7.1), original value: 29

08-29 14:55:32.634 8402 8418 D SNFix/Zygisk: Set first_api_level to 25 (Android 7.1), original value: 29

08-29 14:56:16.610 8402 13008 I SNFix/Java: Set new device props

08-29 14:56:16.613 8402 13008 I SNFix/Java: Set new device props

08-29 14:56:16.662 8402 13008 D SNFix/Zygisk: Set first_api_level to 25 (Android 7.1), original value: 29

08-29 14:56:16.876 8402 13008 I SNFix/Java: Set new device props

08-29 14:56:16.878 8402 13008 I SNFix/Java: Set new device props

Device Integrity passes again :)

Great work my friend!
[Magisk] De_Haos:
How did you retain L1 after bootloader unlock? Is there a secret step i don't know about.
[Magisk] Anonshe:
@chiteroman Is there a reason for the code being closed source?
[Magisk] zgfg:
Of course. Could you guarantee that devs from the other side would not investigate the source and quicky adapt their DroidGuard to invalidate the module?
[Magisk] RazielSanchez:
I was in version 8.1, everything was going well, until a moment ago I updated to version 8.3, and when I restarted the device it failed in YASNAC CTS Profile and Basic Integrity, I went back to version 8.1 where it was stable and it was not solved...

Notice: RESTORE_TO_FACTORY_ROM

I recently had the same problem and had to flash everything again :/

Android 12.1 Moto G100
[Magisk] zgfg:
I don't use the module on my Xiaomi.eu MIUI 14 since I still pass Basic and Device Integrity without (just with Shamiko)

Hence I don't know how previous versions worked - except at the very beginning when I tested the module and it worked then (when passing Strong Integrity was in fashion)

However, today I tested v8.2 and v8.3 and with both all three integrities immediately fail (screenshot)

Logcat is attached (but it doesn't reveal a lot)

When I disable the module and reboot, Basic and Device integrities pass again

Btw, I inspected the props in service.sh, no problem with them - I already have the same values without the module.

Hence something is really in the (closed source) Zygisk binary part
[Magisk] Anonshe:
That's an age-old argument and this module was always open source so my question to the creator is pretty fair without malice.
[Magisk] RazielSanchez:
I just deleted the module and nothing, I don't pass the basic integrity or the CST profile, I think I have no choice but to flash from 0 :/

Sorry for my bad English I use google translator.
[Magisk] zgfg:
This module was not

You're probably talking about the OTHER module, USNF

That module is also from different developer, and in different thread(s)

If the argument is OLD in YOUR eyes, apparently it's not in developer's and most other users here (we also remember how it went with the short time working spoof for Strong Integrity)
[Magisk] zgfg:
@chiteroman - sane for me with v8.1. It also invalidates me Basic and Device
[Magisk] chiteroman:
This ROM is very strange, also happen me in my device. The purpose of this module is for using in stock ROMs, if you have a custom ROM you don't need it, except few ROMs like Lineage.

Ask developers if the ROM include PI bypass. (Very easy to do by yourself).
[Magisk] Anonshe:
It was, here's an old capture: https://web.archive.org/web/20230727204646/https://github.com/chiteroman/PlayIntegrityFix

Obviously I know that.

Are you being dense? Kindly don't reply if you've nothing to add to the conversation.

I've no qualms with it being closed, it was a simple question for the creator not some butt hurt kid.
[Magisk] ninjakira:
So like is this actually working and "meets strong integrity" because I feel one of the first app devs going to implement that check is gonna be Niantic/Pokemon go, currently using moto edge 2021 if that matters
[Magisk] Xennet:
Strange so strange..

But still your v7 and only v7 not v7.x or v8.x works... But 7.0 works perfectly on xiaomi eu roms that i use even today coz only that passes both device and basic for eu roms.. So there must be something right??? That is there in v7 that is not there in latest versions...can u look into it...
[Magisk] sawdoctor:
The "loophole" that allowed us to pass strong integrity has long since been patched Google server side. Unless someone finds another loophole think passing strong integrity is extremely unlikely
[Magisk] ninjakira:
Ok I figured as much cause that what I was reading on other stuff but this thread is making it seem like there's another fix lol
[Magisk] zgfg:
I don't need to ask developers of Xiaomi.eu to implement - they already implemented the spoofs and they still work fine for me in their ROM itself

Hence something got wrong in the module, particularly in the latest versions v8 x, that nullifies those working spoofs and causes that Device and Basic Integrity do no more pass

My hope was that my tests could help you to pinpoint what of your changes cause that, for the benefit of the module - and for the benefit of those who cannot pass without the module but some of them also claim that they did pass but with the older versions of the module

Anyway, I will not test if of no use👍
[Magisk] dcarvil:
Does your device show as certified in the play store? If not, clear Play Store cache and data.

At one time, Netflix app could not be installed if Play Store did not show certified. I haven't used Netflix in years, so don't know if this is still the case.
[Magisk] osm0sis:
Netflix and (weirdly) Leo's Fortune are the best examples I've seen of apps that restrict visibility/installation based on Play Integrity now.
[Magisk] xSnowLeopardx:
We have custom fingerprints which makes the module work. You need to read the first post (OP) and then search for a fingerprint.
[Magisk] xcl1pse:
Custom pif is no longer needed if you using PIF 14.2 by chiteroman. Is needed for backup or using PIF Dev or using osm0sis fork or like me, using older PIF version which is still using custom pif
[Magisk] HippoMan:
Yes, I don't have that problem, but I'm sure I'm spoofing from a device upon which Netflix has indeed been supported. But perhaps your spoofed device is not one of those such devices.

Perhaps you could temporarily try other fingerprints from different devices to see whether or not the problem disappears.
[Magisk] WhoIsJohnGalt1979:
Kindly don't mind if the solution that I suggest sounds too trivial, but for some odd reason, is always the case with most users who can't see Netflix and Hulu in playstore. More often than not, this happens when you have any google entries in the deny list. As long as you are not enforcing deny list and are using PIF, just remove all google components from the deny list, in airplane mode delete data from playstore, wallet and play services, reboot and disable airplane mode. I have a good feeling you will be able to see netflix and hulu etc back in playstore.
[Magisk] Nekromantik:
is PIF 14.2 by chiteroman best version to use that includes the reset props fix to make it not get detected by banking apps? or is there another version called reset props?
[Magisk] xcl1pse:
14.2 doesn't include resetprop. 14.0 does
[Magisk] Nekromantik:
Oh ok

So reset prop's won't be included in future versions?
[Magisk] xcl1pse:
Only chiteroman can answer it
[Magisk] Nekromantik:
hope it does as without it my bank app detects root haha
[Magisk] sga999:
I don't consider your suggestion trivial. You are offering a possible solution, and I appreciate that.

I have no Google components in the deny list. I have deleted data from Play Store before, I don't have wallet, I have deleted Play services data. But I have not ever done anything about airplane mode. Maybe you can tell me why that matters? Anyway, I will give it a try.

EDIT: I forgot to mention that I do have other apps in the deny list and I am enforcing it. You seem to imply that I should not be? But I do need those apps there.

Edit2: No luck yet. Both Netflix and Hulu cannot be installed. But since it has gone back and forth before, I will continue to check and see if I it changes.
[Magisk] majorfigjam:
Your print is too new. Find one from a older model. I know there are older Moto prints that work.
[Magisk] samuelpoc:
Can you show me a guide on how to extract the build.prop from a rom on another device because I have no idea how to extract those "super_img_sparsechunk.*" files and get the build.prop to test
[Magisk] Nergal di Cuthah:
Link in original post to osmosis guide
[Magisk] samuelpoc:
I was only able to obtain this by physically having the device (in this case it was mine)
[Magisk] Nergal di Cuthah:
Search google for android system dumps
[Magisk] flawless911:
Yes, Netflix is always available on my Playstore
[Magisk] peikojose:
Version 14.2 doesn't pass Strong Integrity in my Pixel 8.

Netflix is available in the play store and it says certified device
[Magisk] samuelpoc:
ok, thx, is there any recommendation, from what I read it seems to be android 8.0 is that correct?
[Magisk] majorfigjam:
If you want to do it yourself from scratch, find a program called SparseConverter_1.0.1.zip. You might need ImgExtract as well.

Or look for prop dumps that you might use without needing to extract.
[Magisk] majorfigjam:
Version 14.2 won't pass strong integrity in ANY device!
[Magisk] zgfg:
Ofc we don't pass Strong

But yes, as I wrote above, not only that Netflix is available but I have it installed, use it and regularly update Netflix from Playstore

And Netflix shows DRM Widewine L1 and plays in FullHD, Dolby Vision
[Magisk] Nergal di Cuthah:
Minimum of sdk 24 i believe. It's all in the guide linked in the original post
[Magisk] chill145:
I believe it could be earlier but to help you in your search, that's what I was looking for. 8.0 and 8.1 and the one I found has held up without me needing to find another one. Once you find one, you'll know how to find more but I just stopped after one.
[Magisk] sga999:
I'm pretty sure I could sideload Netflix. And once it is installed, I also think it will continue to be updated. But I'm just trying to figure out what is unusual about my device and why I can't get Netflix (or Hulu) to install at various times. Device is definitely certified.
[Magisk] HippoMan:
STRONG integrity will never pass in a modern device that has an unlocked bootloader. PIF (no matter what version) can't help with that, except *maybe* in an extremely rare case where the fingerprint is from one of a tiny number of ancient devices with a broken OS. But even that might have been blocked by now by the Googlefrinchians.
[Magisk] badabing2003:
New Release:

Dec 09, 2023 v6.3.3.0 release

When selecting build.prop to generate pif.json, you can now do multi-select, PixelFlasher will process them in a priority order based on the filename. build.prop being the highest priority.

Added Auto Copy to Clipboard which automatically copies the generated pif.json content to clipboard.

Added Auto Push pif.json which automatically pushes the file to the device and kills GMS process (after generated build.props processing).

Added Auto Check Play Integrity which automatically triggers the selected Play Integrity checker after editing or auto-pushing pif.json.
[Magisk] dvhttn:
Hmmmmm. Been following this thread for a while and the other day Wallet stopped working so I did what people were doing here and looked for a build.props file. No luck (for me anyway!). Then Magisk got updated to 26402 and what do you know, Wallet seems to work again. At least, I updated Magisk yesterday, then reinstalled Wallet this morning (about 15 hours ago) and it's still working - though I've not paid with it, just opened it where this has been enough to 'fail' before.

The screenshot shows the Magisk modules I have installed. And as the recent discussion has been about Netflix I installed and used that app with no problems. In fact I just realised I didn't 'hide' it with Magisk, just installed and ran it (after logging in). So, just added it to the 'denylist' in Magisk, rebooted, and it still works.

Go figure ...

Oh, in the UK, with a Note 20 Ultra running Dr. Ketan's last A13 build for it.

Maybe it'll all stop working in the morning (Sunday) .... I'll let you know ....
[Magisk] WhoIsJohnGalt1979:
I am not sure which Magisk version you are currently on, if you are on the official versions (stable/canary) or alpha, enable zygisk-disable enforce deny list, flash PIF and Shamiko back to back without rebooting, keep whatever you want non-google related in the deny list. Preferrably do all this in airplane mode (why? well the lame reason would be well dont let the apps or services report anything while you are making changes to respective google/app authentication servers). You havent rebooted till now, so now, again delete data from playstore and play services (since you said you dont use wallet), reboot and disable airplane mode. I can guarantee you there many who will get similar results without going through these hoops. But I prefer to do it this way (OCD). If you are using Kitsune Mask magisk, you don't need Shamiko, just Enable Zygisk - Enable Magisk Hide - Dont not enable Enforce Sulist - Put all the non-google stuff in the Configure Magisk Hide section-flash PIF - delete data from playstore and play services (since you said you dont use wallet), reboot and disable airplane mode. Apologies for the long answer for such a simple problem, and am sure you can sideload the apk, just ensuring that you don't end up posting 10 times and getting different replies.
[Magisk] nowster:
It looks like Canary 26402 has been deleted off the file host. Magisk Manager gets confused if you try to update. If you try to access its files using curl or wget it gives a "403 Forbidden" response.
[Magisk] wfred:
A rooted phone will never pass Strong
[Magisk] majorfigjam:
You can get Canary 26402 from the Github Magisk page, and install manually. Remember to restore the magick app (ie unhide it) first.

It's too big a file (ie >20MB) for the normal "in app" update.
[Magisk] TotallyAnxious:
You need to wipe play store once you're passing. It recertifies the device in the play store and allows apps that require it. Bank apps and such check this on every app start, but the play store seems to only checks this once, on first app start up.
[Magisk] sga999:
I'm using the official 26.4 Magisk. No shamiko, 2 apps added to the deny list. No Magisk hide. I'll keep trying, but no energy for it at the moment! I don't really want to sideload it because I want to figure out what's wrong. I was just saying that is an option that I don't want to do.
[Magisk] rseiler:
What we're doing here reminds me of the hunt for and discovery of exoplanets, just a lot more impressive than that so-called feat. After all, has any astronomer ever boasted that they just found 48 exoplanets on their first try, while watching a Seinfeld rerun no less? I think not. Case closed.
[Magisk] beeshyams:
Weird. I am using your for fork and with custom pif, I pass basic & device integrity but can't see both those apps "this app won't work for your device" says Play Store even after clearing cache. Play store is certified

I don't need those apps but as an observation
[Magisk] osm0sis:
I can see both. We found a while back in one of these threads that clearing Play Store data/cache doesn't always have an immediate effect, and sometimes people had to clear it more than once to clear whatever cached result was knocking around behind the scenes. 🤷‍♂️
[Magisk] sga999:
Maybe that is what is happening for me since you say there can be a delayed effect. I guess I can see how that could happen when trying to enable seeing an app. But then after it does show, I don't know why it goes back to being uninstallable.

Anyway, you mentioned Leo's Fortune. On one of my devices, it shows and says it cost $4.99. That device has Android 13. But on one with Android 11, it tells me that it was made for an older version of android. But its info in the Play Store says it works with Android 9 and up. So strange.. 11 and 13 are both higher than 9!

I had only noticed Netflix. Then someone mentioned Hulu as having this issue. Once I read that, I looked at it, and I am having the same problem with it. Leo's Fortune is another one to add to that list... except that it's even crazier. I think I'm going to quit bothering you all about this problem. I will just pursue it privately and hope for the best!

EDIT: That stuff about being made for an older version of android makes me wonder if somehow the Play Store temporarily misinterprets the version of the device due to the new fingerprint. But then it figures it out. Very unlikely, just throwing it out there.
[Magisk] BillGoss:
One also needs to clear storage from Google Play Services
[Magisk] makeyourself:
Yeah clearing Play *Services* data works for me every single time, must have done it about 50 times in the past lol.
[Magisk] TKruzze:
I NEVER clear GPS and everything works fine. Sometimes I have to wait overnight for things to clear up, but wiping GPS comes with too many side effects for my devices.
[Magisk] EuK_V:
What kind of side effects?
[Magisk] WhoIsJohnGalt1979:
lol the most irritating one is, if you do have a pixel watch set up, you end up setting it up all over again :p
[Magisk] Fishawy:
Re-authenticating and re-adding your bank cards, re-configuring watch with all its headache, re-adding transport passes (with potential money loss due to the stupid setup some operators might have such as mine), etc.

If you haven't experienced any of these, then you are one of the lucky ones.
[Magisk] HippoMan:
So, even switching to a smart watch for contactless payments still leaves us with some painful side effects that we have to suffer nowadays as a result using a modded device.

Android's deterioration continues.
[Magisk] EuK_V:
@WhoIsJohnGalt1979 , @Fishawy

oh, those i'm aware of. I thought there might be somthing else..
[Magisk] rogers11:
Good morning and many thanks for the update. I've found two things, that do not really work:

1. Checking integrity with Play Store opens Play Store but nothing more, no check, no result.

2. Having "VNDK_VERSION": "" in custom.pif.json results in endless checks (from within Play Store) or error -17. Removing this entry fixes it.
[Magisk] osm0sis:
So I did look into that, and currently unsupported fields get skipped correctly in my fork as long as they were added correctly (i.e. not breaking proper json formatting/parsing), and the values aren't explicitly null (which causes crashes, not fails).

I'll see if I can tighten up null handling just because the GMS crashes it causes are a little annoying/concerning, but I don't think anyone would/should be trying to send null for anything right now anyway.
[Magisk] simplepinoi177:
Thanks for checking. I'm sure it at least gives a better idea what might be going on...

Maybe I inadvertently put in a space or comma or double quoted or something...

(y)
[Magisk] hayvan96:
ih8sn seems to have been updated as well https://github.com/althafvly/ih8sn

I haven't tested it, as my personal FP seems to hold for a week, so sticking to "if it's not broken, don't fix it".
[Magisk] simplepinoi177:
Look at this guy bragging.... 😉😜

I grinded for 2 and a half days straight and only finally got one!

As you are so successful, can I ask for a hint -- in the 19 FPs, were they all Oreo devices? Or is there some hope to find fingerprints on devices that are past 2018?
[Magisk] niko26:
Since using 14.2 Netflix updates appear correctly again!

I hope someone can make sense out of it:

IIRC since using PIF (for about a few weeks now) Netflix updates were not available. WHILE Play Store showed it was passing Basic and Device integrity AND Google Pay was working (including the cat and mouse result, meaning thsr suddenly it was only passing Basic and Gpay stopped working until updating PIF).

With PIF 14.2 everything seems to work fine.

🤷🏾‍♂️
[Magisk] osm0sis:
It was the reboot. 😛
[Magisk] FERRARI81:
Noob here. May i use FP from an older mine device?

In which way Google recognizes them as false FP?
[Magisk] dvhttn:
I just used the 'update' button in the Magisk app and everything just updated (well, first the app then Magisk itself when I prompted it). Oh, I am on the 'alpha channel' update setting but all good so far. More reboots and Wallet has been working (though just opening the app with no problems - I've not been anywhere to pay for anything yet). And Netflix still works. Go figure ....
[Magisk] purgy:
I'm using a nougat fp, for a device I can't find any mention of an oreo rom (or any update at all, ever) for.
[Magisk] niko26:
Which reboot exactly? 😂

Oh wait... I forgot that I updated to the December patch on Thursday. Maybe that made a difference.
[Magisk] osm0sis:
Probably the 14.2 installation reboot after you cleared Play Store data/cache.
[Magisk] simplepinoi177:
I might be reading your reply wrong, but as osm0sis' quintessential post says

and how he said

....so there has been "mention of...oreo rom..."; unless I misunderstand and am reading your reply wrong....
[Magisk] zgfg:
Both:

"SOMETHING": ""

and

"SOMETHING": null

(add comma at the end if it's not the last property) are valid by JavaScript Object Notation

"" and null are valid in JSON,

NULL or nullptr are not valid

To validate, minify, reformat JSON, use eg:

JSON Formatter, Validator, Viewer, Editor & Beautifier Online

Online JSON Formatter, Validator, Viewer, Editor & Beautifier. JSONFormatter is a simple and easy to use online tool to format, validate, edit, and beautify JSON data online in real time. It also contains several articles on how to Validate and Parse JSON data in different programming languages.

www.jsonformatter.io

Select/checkmark Empty Schema, paste in JSON, and 'Play'

----

The module (all versions I tried that read JSON files) correctly supports "" but hamgs on null (there is no exception handling, hence it just dies and does not spoof anything)

However, I don't see a use, eg with FINGERPRINT replaced by empty/null string you'll not pass Device Integrity

For proper deserialization of the input JSON in the main.cpp, consider to replace std with a proper JSON library:

A guide to JSON using C++

Best C++ Open-source Libraries For Parsing JSON

medium.com
[Magisk] niko26:
I thought you were joking.

Of course I rebooted everytime after updating PIF. So for each version I had at least one reboot.

I haven't cleared the cache manually, at all.

Maybe updating to the December Google Patch Update cleared the cache?
[Magisk] nowster:
If you look in the canary.json file you can get the filenames. Those filenames resolve to 403 errors.