yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
In a week or so it will be burned and the count of available spoofs will be N-1.

Like for every previously published and thus massively used

Those that are used only by a small number of users who posses them, still go under the G radar

I m not saying it's ethical, right or wrong - just it's the way it is
[Magisk] titomax82:
Did what you suggested and now passes basic and device, positive result when searching netflix in playstore. Logcat points to "asus....."

But now I have warning in google wallet... what can I do?
[Magisk] Nergal di Cuthah:
I don't disagree with you, and would be using a "unique" fp if i can ever get a search to work and find one.

I even stated this when developer hypothesized about the method currently being used. I said that i love the idea but feel it will speed the demise of fingerprints.
[Magisk] HippoMan:
If I'm not mistaken, PlayIntegrityFork_v3 needs the pif.json to be installed here:

/data/adb/modules/playintegrityfix/pif.json

or

/data/adb/modules/playintegrityfix/custom.pif.json

I think the second one is preferred.
[Magisk] majorfigjam:
The two versions use different file names in different locations. Read the information linked from the first post in this thread, and name and place your files accordingly.
[Magisk] shoey63:
What about Uber rider app?
[Magisk] zgfg:
Not Google defenders - but 'technocracy' arguing to hoax, myths, conspiracies and superstitions😁
[Magisk] pndwal:
@ashok, others,

FWIW, google only renamed the SafetyNet API implementation in order to expand it beyond a device integrity attestation service; The updated Device Integrity component itself could well have occured as 'SafetyNet', but added Play Integrity components are the real reason for the switch...

The API responses in addition to Device Integrity are Application Integrity and Account Details ... For available labels and descriptions see:

https://developer.android.com/google/play/integrity/setup#configure-api

👀 PW
[Magisk] pndwal:
If you mean me, I won't defend misinformation, sure... And I do think the supplier of our moddable (by design) mobile OS deserves to be defended against that at least... Try modding iOS!

Any evidence it is already using strongIntegrity?... That would be interesting... PW
[Magisk] chrbur:
Hey, I installed Fix 7.4 and Shamiko. ALL Apps Work finde, including Banking Apps. But Weconnect (Volkswagen) doesnt Work. Any VW Driver online? 😀
[Magisk] pndwal:
Not, but 5.17.2 opening fine still; Nb. It detects current official Zygisk, but not native bridge loaded Zygisk... This post, and see post above:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-88468151

... 👍 PW
[Magisk] FIERA03:
This is a local Japanese app, but I am confident that the MyNumber-Portal App is STRONG checked (numerous friends I know reported that neither the Displax mod nor Fix 7.4 had any effect).

マイナポータル - Google Play のアプリ

子育てや介護など、行政手続のオンライン窓口です。申請のほか、行政機関等が保有するご自身の情報の確認や、行政機関等からのお知らせ通知などのサービスを提供します。

play.google.com

This app is made by the Japanese government, so to some extent it can't be helped.

However, it can be assumed that the number of applications that directly check STRONG will gradually increase, especially government-made app, in the future.
[Magisk] latamboy:
How can I know if an app use a Play Integrity API request? I'm not saying that an app isn't work, but in any way as an app user we could be "flagged" depending on PI veredict
[Magisk] zgfg:
If you use the PI Fix module, then you can look for SNFix in the logcat

However, banking apps do not rely only on Play Integrity, they additionally try other detections that are not related to SN/PI
[Magisk] pndwal:
Please can you say at what point this app detects root/modified device?... It opens fine for me... 👍 PW
[Magisk] sawdoctor:
So many people presume an app is detecting strong integrity when more often than not it's a rouge app or file that's being detected. 2 of my banking apps detect the xposed mod app settings reborn
[Magisk] Ginosius:
Try Magisk Delta and enable MagiskHide with the SuList.

This means no apps can query for root, except for the ones you add to the list.
[Magisk] zgfg:
In the new Delta you have Unmount Modules (no more Magisk Hide). But use the same way
[Magisk] FIERA03:
This app detects Play Integrity when we try to signup.

This signup requires "My Number" which is distributed only to Japanese citizens, so you who live in oversea probably can't perform it (if you are Japanese, I apologize 💦).

My friends testify that it was a futile resistance to hide everything as much as possible using Delta's MagiskHide(Unmount Module), PIFix, as well as HMA.
[Magisk] FIERA03:
As far as I know, there is no example of a successful My-Number Portal signup with the bootloader unlocked (except when STRONG was passed due to a bug at one time).
[Magisk] zgfg:
Ok, that would suffice to prove that it really checks for Strong Integrity
[Magisk] pndwal:
Thanks for the information...

A more conclusive test would be to try on an older stock / bootloader locked device launched with Android 7 or earlier (ie. device lacking strongIntegrity compatible hardware keystore implementation/keymaster3+). This may be running later/latest Android (RV 8.0+) but must have shipped with old Android (LV<=7.x).

If users of such older devices can run MyNumber-Portal app successfully, it is not enforcing PI strongIntegrity.

🤠 PW
[Magisk] chiteroman:
Or they are checking the bootloader status in local attestation. If app doesn't detect Xposed he can try this:

🔐Spoof locked bootloader | "Bypass" TEE check

Modify the root of trust in local attestations. This module modify the byte array obtained from certificate extensions (link) to spoof a fake root of trust, so we get a fake attestation with a locked bootloader. More info about certificate...

xdaforums.com
[Magisk] zgfg:
It's some Japanese government app, I don't use and cannot install (N/A on PlayStore for outside of Japan)

But he said that app did work when USNF/PI Fix was passing Strong Integrity and does not work now, once Goggle fixed the flaw

Hence irregardless of does he and did he use Bootloader Spoofer (and what Key Attestation shows now and did previously), it appears that (if nothing else was changed on his system) that working or not for that Japanese app depends on passing or not the Strong Integrity

Up to my understanding...
[Magisk] sawdoctor:
There's a lot of people who are not happy with the way @chiteroman is implementing his fix, i understand that. But also remember before you throw him under the bus if he hadn't given us his PIF then none of us would have been able to use wallet since Displax stopped maintaining safetynet.

We now have 2 people with @osm0sis working on it as well and @badabing2003 making things easier for us. If we lose these Devs then we make modding even harder
[Magisk] Pakabidu:
*near impossible for some :) Can't lose them!!!
[Magisk] jean019:
I'm not a specialist, but I don't understand.

Mi10T, a13 alphadroid rom with root since 2 months, GPlay was certified (with no patch)...

but since 2 weeks still Certified, without any integrity (not even basic).

I installed the v14.1 patch... GPlay store NOT Certified anymore, but integrity "Device" level2.

Why Google play is not certified if I have integrity level 2 ?

For last weeks I had no integrity at all, and my google play was Certified...

Both things are not related maybe ? (so what's the point of having a GPlay Certified ?)

thanks
[Magisk] Vision:
Yeah true, with v14 with feature pif.json with fingerprint of our choice can prolongs the specific fingerprint, from Google not blocked for some time, understand @chiteroman make the v14.1 with feature with updated only the fingerprint and not the module, with users not have knowledge to do it themselves
[Magisk] Vision:
So easy hah? 🤣
[Magisk] nrd\:
Just posting my experience.

Since I finally caved and Installed android 14 (waiting forncusont rom) pixel 7 pro, I finally got 14.1 working.

Before success I tired (it was a learning curve /guessing) , 13.9, with various options hidden, then updated to 14, and 14.1 enabled this that and other, but failed or had basic only, no device.

So I looked at several posts, here, reddit etc picking at various posts trying this that and other, but no joy.

After last few posts, as the info is now being posted with various uses with success and failures, I slowed down and read the last few posts, with 14.1 working for them. I then revisited my method and I got it working with:

Magisk canary,

Zygisk enabled,

Enforce deny list.

In the deny list I have the usual apps, and Google wallet, play store, Google services framework seems to be highlighted but shows unchecked

Modules installed play integrity fix 14.1 and Shamiko but it's disabled,

I deleted the pif.json file from adb folder, I also checked modules folder and it doesn't exist there.

Clear the app caches, wallet, services and the other in the thread.

Reboot,

Tb check shows 2 passes, integrity api is failing Google error, (before it passed I noticed only basic use to pass so maybe linked?)

I tried various methods but the is 99% of what I did and all is OK.

Google wallet, I've added cards successfully, I'm taking as a success and I tired to make a payment failed but that was due to not entering a text.

Hope above helps.
[Magisk] norberto_:
Actually it is. Its just a dex file.

But i am so grateful for these guys for making these modules.

I was searching a lot for a fp what im using.

Hopefully it will stay ok for long 🙂
[Magisk] Klappp:
So basically delete the old .json file and clear data for wallet, play services and play store and update the module
[Magisk] Vision:
Yeah, oh you mean decompiler the dex, i mean if it is hardcode in the libs
[Magisk] norberto_:
Even if it is in the libs. Thats also not that difficult to decompile. At least to see that bit would be still text.
[Magisk] Vision:
Oh yeah, true that
[Magisk] REM_8:
Thanks man!!! @nrd\ your awesome :)

it worked perfectly as you said , followed your instructions and passed CTS on GP7P Android 13, haven't updated to 14 but still works
[Magisk] Stephenhs:
I am curious, why just don't Google ban all fingerprints in mismatch situation? Why it allows mismatch situation in the first place?
[Magisk] Fishawy:
For anyone having issues with osm0sis's fork while having success with chiteroman's mod (with the same fingerprint), I had those issues while doing the switch.

Ensure you have two things in place for osm0sis's fork to work:

1. The pif file needs to be placed inside /data/adb/modules/playintegrityfix/, not /data/adb/.

2. The pif file needs to be renamed to custom.pif.json, not pif.json. And try renaming the file before moving it. For some reason, Mixplorer didn't like renaming it inside the root path while it was okay doing so in the internal storage.
[Magisk] xlxcrossing:
Followed directions for 14.1 and the result was this

Kill all step yielded : no such process

Deleting my custom props and rebooting allowed me to add cards again (previously deleted them after clearing storage on everything post v14 collapse.

I know it will probably only be a matter of time before it borks but PayPal QR is an ok alternative worked fine at Safeway last night. The main caveat is having retailers with scanners which food service and other businesses might not have.

The quest to never carry a CC again continues 🥴

Thank you for your continued efforts, donation sent!
[Magisk] manjaroid:
And if in doubt, PixelFlasher supports both modules and knows what to do. Even terminal ninjas will appreciate how it streamlines the process.
[Magisk] Fishawy:
True, and mostly effortless as well. I stated how positive my experience was in another thread yesterday.
[Magisk] xSnowLeopardx:
Still curious why a fork was created/wanted. Been doing everything via chiteroman's mod.
[Magisk] Fishawy:
I believe @osm0sis is the best person to answer that. It was listed a couple of pages back and on the Github page as well, but from what I gathered so far, you're talking about: 1) avoiding generic pif.json files at all costs, and 2) a little bit of house cleaning for how the code is written.
[Magisk] xSnowLeopardx:
Ah, so nothing groundbreaking.
[Magisk] Fishawy:
That's your personal assessment, I won't comment on that :D

But at the end of the day, you review and decide which way to go. Plus, it's always good to have options.
[Magisk] Fishawy:
If you're currently passing Device Integrity (level 2), and Google Wallet works (meets security requirements), but your only issue is Google Play not certified, then I would try deleting data and cache of Google Play only and reboot, then give it a couple of hours.
[Magisk] jean019:
Thanks, i'll try.

I'm not used to Google wallet, do you know how to check if "Google Wallet works (meets security requirements), ", ideally without adding credit card ? What to verify ?
[Magisk] HippoMan:
Well, the closest thing to "groundbreaking" is the fact that there is no default pif.json file supplied, and we users must supply our own ... under the assumption that we will do our due diligence to hunt for the fingerprints we use, and under the hope that we will not publicly share them.
[Magisk] V0latyle:
They didn't "allow" it, it's just an as yet unpatched exploit in Play Integrity that we've been using.

I'm not sure how much they can actually update Google Play Services on our phones but at some point I imagine they'll patch this, then we won't be able to use mismatched prints
[Magisk] Fishawy:
If you install the Google Wallet app from the Play Store, open it, click on your picture or icon on the top-right corner, choose "pay contactless setup" from the drop-down menu, ideally there should be 5 checkmarks.

In your case, again ideally and if all is well, your should have 4 checkmarks (and one missing for adding a card). The checkbox we're looking for is (Your phone meets security requirements).
[Magisk] xSnowLeopardx:
Yeah so no different than 14.0 in that regard? I am not acknowledging 14.1 right now, since I don't support that.
[Magisk] mhrussell1:
/data/adb/pif.json
[Magisk] jcp2:
HELP!! I flashed PlayIntegrity Fix v14.1resetprop.zip and now it fails cts match. on my P8P. What can I do to fix it without wiping the phone?
[Magisk] jean019:
Seriously man, you're a killer :cool:(y)

- my google play is now certified... with integrity level 2 ;

- Under the wallet, 4 choices (activate NFC, Google pay not defined bla bla, No card configured, No lock screen)

AND the mention :

"Your phone meets security requirements" :D

Thank you !
[Magisk] Fishawy:
Glad I was able to help!
[Magisk] zgfg:
Smash the phone - that's even better solution😁

How about,uninstalling the module (+ reboot)

Or better, install the same but NOT the version with resetprop in the name
[Magisk] HippoMan:
Yes, not too different from 14.0 in that manner. But indeed different from 14.1 and some of the earlier ones which supplied default fingerprints.
[Magisk] Fishawy:
No need to wipe, don't worry.

1. Have you got your custom fingerprint?

2. Did you test it and confirm it was good (i.e, meeting Device Integrity)?

3. If yes to both 1 and 2, did you place the fingerprint in the correct path (i.e, /data/adb/)?

4. If yes, try uninstalling the resetprop module and reboot, then try again but with the normal v14 or v14.1 (not the resetprop one).

5. If interested in testing another solution, you might wanna look at the other fork a couple of pages back. Different approach, same result.
[Magisk] intel_core_i7:
Not really true. On Xiaomi devices if bootloader is unlocked and unrooted BASIC will pass, just not DEVICE and STRONG. 2/3 will fail. If BASIC does not pass then it will pass DEVICE and fail BASIC. I just don't remember the order well
[Magisk] Iridule:
Been lurking for a while but all was well until beginning of the month then the wallet stopped. However now with 14.1 PIF module seems to be fixed. Should I still seek a custom fp? Only thing I noticed is Google Play store doesn't show certified anymore.

Updated Google Play store now device shows certified.

All apps seem to work as intended. Moto edge 2020 racer with latest magisk canary.View attachment 6040379

View attachment 6040380
[Magisk] Fishawy:
For custom fp, you should. Better to use a print that is not being used by everyone, less chances of being banned. That is, of course, unless you're happy with the current setup, which is fine.

For the Play Store, please check a couple of posts above. I was able to assist someone with it.
[Magisk] locolyric:
so we buy a new phone , safe the fp and use it everytime after we flash custom rom? will that work?
[Magisk] osm0sis:
You clearly take issue with 14.1 and yet somehow don't see the reason for a fork?

The groundbreaking things will be I won't make erratic decisions that ultimately hurt the community, or unnecessary rewrites that introduce regressions. I'll actually methodically test and try to fix something rather than completely revert it. I separate things into commits. I won't impulsively close the source, or delete the commit/release history (in fact I restored what I could find of his pre-v13 into mine). You know, normal development practices.
[Magisk] Fishawy:
No need to "buy a new phone", there's plenty of valid, perfectly-usable fingerprints online. Please check @osm0sis's guide linked to the OP post and here on how to fine and use one.

Stock or custom ROMs - to the best of my knowledge - is mostly irrelevant (with the exception of Xiaomi as they have their own setup, someone please correct me if I'm wrong). You use a fingerprint until it's not valid anymore, then you use another one.

Lastly, regarding the part "use it everytime after we flash custom rom", I would say yes (again to the best of my knowledge). Now that we do not have the fingerprints incorporated inside the modules anymore, one would need to manually place the pif.json files in the proper location(s) if the system was modified.
[Magisk] osm0sis:
Only if you wiped/formatted data. Reflashing wouldn't be necessary after an OTA or anything, same as other Magisk modules.
[Magisk] acwcanada:
Based on my personal assessment I just couldn't convince myself to have a best way in approaching this print issue. Let me give my experience to tell why I am saying this:

1. The TG json only getting basic integrity pass on my Pixel 7P with A14 QPR2 using PIF v14.0, update/install v14.1 without deleting the said json, I got both pass on basic and device integrity. Repeating this process for several times in the past 24 hours always come back with same result.

2. My other phone, a Pixel 6P can't get device pass on PIF v14.0 with a fingerprint which I obtained from my old 2017(?) Pixel XL build.prop (I keep the "marlin" for emergency backup), but the same print got my son's Pixel 8P on PIF v14.0 with 2/3 integrity pass.

So based on the above, which is a correct/good approach? Find a print or just use @chiteroman's? I can't tell!

And one last thing, when I writing this, the thread has 261 pages and approx 5 thousands messages but how many members involved? I would guess it is less than 5 hundreds and how many of us are able to find a print??? And if you go to @chiteroman's TG group, it has almost 6 thousands of members ( I don't participate the discussion there as I have no time to read a few thousands chats every day). I believe at least a few thousand people are not able to find print for themself and rely on @chiteroman's issuing of the module. He actually helps a lot people and please don't judge him from your own stand point, my 2 cents.
[Magisk] Fishawy:
Both sides have valid points.

On one hand, you have a dev who is trying continuously to help thousands of users, particularly those who don't have the means or the knowledge to do a custom config. Temporary solutions, yes, but they still help until today nonetheless.

On the other hand, generic prints are doomed to fail eventually, and we know harder times are looming, so you have those who try to educate, then educate, then educate again, then provide a slightly more sustainable solution on the long run, and still help as much as they can.

No one can fault side A or side B in their entirety. You won't find anyone here who's completely dismissing a certain solution, in fact solution B is originally based on solution A.

What most of us are hoping to see is more help with less damage (if such a word can be used), and the beauty of XDA is having those great minds who produce not one solution, but four (we're not forgetting kdrag0n and Displax), in the times of need.

Kudos to both. Kudos to all.
[Magisk] BROKEN1981:
Do you have any idea why person A can use a print but person B fails on the same print? Is it the 3rd party checkers that are getting people caught?

Is anyone trying to figure out what Google is doing? If they did, would it be explained to the XDA community? Or would it be kept a secret in order to keep fighting Google?

Would this get even harder one day due to on device ML and AI?
[Magisk] Fishawy:
Just a guess, but did either of you try different PIF solutions? Or perhaps multiple mods on different phones?

For instance, PIF v14.0 with build-in print, then v14.1 with no print? Or manually moved one and forgot upon an upgrade? Or even from chiteroman to osm0sis / the other way around (knowing they require placing pif.json in different locations)?

I don't have a solid answer, but I would suggest starting fresh, and making sure beforehand that no residual prints are in /data/adb/ or /data/adb/modules/playintegrityfix/. And, if you're Pixel users, then please utilise the PixelFlasher tool in doing so, which makes things a lot easier.
[Magisk] Nergal di Cuthah:
Just to note any fastboot device can use pixelflasher not just pixels, i believe. Am i right @badabing2003
[Magisk] Fishawy:
Huh! :oops:

If that turns out to be true, I'll beat myself with hammer for every time I wiped a phone due to commands issues.

Edit: Screenshot below.

View attachment 6040416
[Magisk] badabing2003:
@Nergal di Cuthah is right, any device that can use Android platform tools, can use PixelFlasher.

Even though the name bears Pixel in it, it's a UI layer utilizing adb / fastboot commands.
[Magisk] Fishawy:
Where is my hammer? 🤦🏻‍♂️
[Magisk] Nergal di Cuthah:
Tbh i only knew cause he said it somewhere in this 5232 post monstrousity that i wake up early for just to not get left too far behind
[Magisk] acwcanada:
I agree with most what you said, but...

I believe the side B is fighting for a never able to win battle. Think about this way: almost every appliance and electronic whether it is a phone, camera, tv, washing machine etc. which people buy today would come with book of manual, you don't read them and I don't read them, we expect that it is plug and play or a simple install guide with a few sentences in one page, and those manual and install guide always come in with your mother language. I even don't want to read my car's manual before I drive it! Not that @osm0sis's guide is bad, but you have to understand most people come here to have "plug and play" or "an install guide" the most. Plus a lot of people have language barrier including I myself (Engish is my second language and I always have difficulty to present my idea), I have given up but going back to read that guide for several times to understand it. And not just language, you have to have certain level of knowledge to get you going with that guide.

I can say over 95% of phone users are just normal people and they wouldn't or know how to root their phones. The other few percent of phone users whom they rooted their phones for certain purposes are not interest in learning the "know how" of a module or an app, they just want something that can be "plug and play"; and something like @chiteroman's module is what they want, they don't need/want "education" and can't be/ want to be "educated". Unless side B is able to simplify the procedure for a way to achieve obtaining a genuine print, the battle result is already written on the wall.

I have no answer for what will happen and for how long if @chiteroman's module is using up all genuine prints. I myself might giving up in rooting my phones as it is looking like more hassles than benefits now...

Nice changing ideas and good night (it is almost midnight here in the East Coast of Canada).