yashsingh1/xdaforums huggingface dataset:
[Magisk] HippoMan:
This would take a very small amount of human effort. I can find out in a minute or two whether a new version of PIF has been released, and I could install it on a device and check what json.pif it puts into the /data/adb tree in a couple more minutes. And I could check the github PIF repo in another couple minutes to find out what the current FP is for that release. That's why I've said it will take someone probably 5-10 minutes a week to perform these tasks.

The automated Googlefrinchian needle-in-a-haystack procedures can also still be used, as well.

Either way, FP's that are published in widely used venues or released via PIF and which work for spoofing could be easily detected.
[Magisk] simpleatom7:
I got the same error before clearing data & that's what i agreed that it also didn't work for me (earlier).
[Magisk] zgfg:
Some filters ask for FaceApp Pro - but they have Pro sticker over the icon

Impressions, Hollywood 2 filter does not have Pro sticker and does not ask for Pro version, but it checks for Play Integrity - you can see all the subsequent posts here, how and when FaceApp checks for Play Integrity from the logcat and FaceApp own logs
[Magisk] simpleatom7:
Shell is parasitic lsposed. Go to blacklist>show system app & type shell.. And add this to ur preset having magisk, rooted apps... Apply it to banking apps.......
[Magisk] jbing95:
After adding Play Integrity Fix stell not work View attachment 6005001
[Magisk] pndwal:
Oh... so you still didn't realise you said locked when I asked previously and repeated it... but suspected this... 🙃

Yeah, I had strongIntegrity pass using Pixel 2 fingerprint prop (which erroneously caused Google server to issue strongIntegrity verdicts with the correct combination of other props on different devices) despite the server receiving basic-only attestation too... That worked for most (all?) devices at the time...

However, since Google's server end fix, or being found out for an apparently deceitful spoof of strongIntegrity for their 'own' 2nd generation Pixel (HTC manufacturer), whichever way you look at it, failing strongIntegrity is once again as good as 💯% certain on any unlocked device...

Unless Google have failed to fix more stupid server-end spoofs for strongIntegrity (yeah, seems they've been caught playing the spoofing game too, manipulating/spoofing expected security related signals / "subverting their security model" 🤣 - see link below), or someone can "hack TEE" (ie the hardware backed attestations to AVB state etc generated by keymaster in device TEE OS including its encryption algorithm etc), or some other vuln (vulnerability) is found... 😁

FWIW, I put a detailed explanation of this 'Google anomaly' as well as my theory about what they apparently tried to achieve by it here:

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-88869761

🙃 PW
[Magisk] quasyl:
Funziona bene qui (funzionava anche prima). Il mio telefono è Redwood (Poco X5 pro 5G) e la rom è xiaomi.eu 14.03.

Just an observation: every time I update I have to select again "Google play services" in the zigisk ignore list, this happens from the beginning.
[Magisk] zgfg:
You don't need to put it back, no use of that.

Just reboot and gms will be removed from the list again

It was mentioned elsewhere that module removes gms from the list because the module takes care about gms and it needs that DenyList/MagiskHide/UnmountModules or Shamiko do not.

Therefore, USNF or this module, both must remove gms from the list (they llook to the list on every reboot and if gms is found there, it will be removed)

It was already a known case for the original USNF module from KDragon
[Magisk] omerqw41:
Any body have please version 8.1 sourceCode with ShadowHook ??
[Magisk] chiteroman:
Why you want it?
[Magisk] supermansaga:
I ran it from command line on my windows 11. It's been 10 minutes and nothing has come out.
[Magisk] omerqw41:
I think the ShadowHook method is better from now, if you can send this version i really appreciate this ❤️
[Magisk] zgfg:
You will not grep SNFix just by waiting. Trigger PI or SN attestation

Eg, open Play Integrity API Check to check PI. Or check PI through TB checker. Or use some banking app that checks PI. Or YASNAC or an app that tgqt checks SN

Make sure first that logcat (without grep SNFix) continuously prints the logcat

Btw, I always use just Terminal Emulator (no need for PC) and simply run (under su):

logcat | grep SNFfx
[Magisk] zgfg:
Thx. Frankly, searching for Shell didn't come up to my mind (I was thinking of some setting) :)

Btw, I tried but I don't have a real 'banking' app I still need to hide 'root' from, hence couldn't test there

For Momo it just makes things worse and for Native test it doesn't help (with the other root detectors have no problems)
[Magisk] Stillhard:
Cts profile match failed in my device
[Magisk] zgfg:
Same problem for me with today's PI Fix v8.5 on the old Xiaomi.eu A11 - screenshots

Btw, new Bootloader Spoofer v1.2 works for me (like the previous version)
[Magisk] chiteroman:
It doesn't work for some people. But wait I can reupload it.
[Magisk] chiteroman:
Hardware backed :o
[Magisk] zgfg:
Yeah, with v8.4 is software and ok
[Magisk] chiteroman:
@omerqw41 check this version
[Magisk] ykjae:
Whats the changelog?
[Magisk] Nergal di Cuthah:
This is the truest statement, I've hypothesized that it's AI or lower intelligence, such as a crawler or bot, doing this.
[Magisk] purgy:
Can we get bard to create pif.jsons for us to complete the cycle?
[Magisk] Nergal di Cuthah:
I think someone said they did, but they might've been joking
[Magisk] HippoMan:
Well, since the Googlefrinchians control Bard, we should use ChatGPT instead.
[Magisk] ace2nutzer:
Spoiler content hidden.

View attachment 6046656
[Magisk] HippoMan:
That kind of warning will triple or quadruple the number of people who decide to try the utility.
[Magisk] Nergal di Cuthah:
It's been some variation of that since 14.1 i think
[Magisk] HippoMan:
I'm referring to the "Parental Advisory" section.
[Magisk] Nergal di Cuthah:
Yup i was quoting the orginal not yours ;) <3
[Magisk] chiteroman:
A bit of spam 😝

Updated my Xposed module (BootloaderSpoofer) -> https://xdaforums.com/t/spoof-locked-bootloader-bypass-tee-check.4586251/post-89231645

I found an unbanned keybox in Github and I'm using it. Passing Strong if you know how 😋

View attachment 6046665
[Magisk] xcl1pse:
uhhh..View attachment 6046668View attachment 6046669
[Magisk] majorfigjam:
And of course that covers the blindingly obvious fact that when I boot the Oreo, it shows the only the vendor logo, but when I boot the Pixel it tells me that my bootloader is unlocked, and the device is insecure.

Google doesn't need to worry about banning prints from genuine old devices, because it believes (knows?) them to be inherently secure, albeit not "hardware secure" enough to pass Strong Integrity.
[Magisk] HippoMan:
... and the Googlefrinchians might still banana many of those prints from genuine old devices if they are being used as spoofs on more modern devices.
[Magisk] osm0sis:
Honestly glad you've finally seen the light again and come full circle to where you were at a month ago! 😁🙌
[Magisk] majorfigjam:
However, doing so will not affect the actual old devices, because they are "secure" and checking play integrity simply returns the expected values for them of "device integrity" which for now is enough to use Wallet / Pay etc.

Which is no doubt why the more sensitive "corporate" banking apps, (eg key generators for batch payment approving) as opposed to retail banking apps, no doubt require a minimum android version, to attempt to avoid the uncertainty.

Why they care is another question, but given the values of payments passing through them daily, I can see why they may want to prevent root access to a device which is being often used in lieu of a secure RSA token.
[Magisk] HippoMan:
I can see why the banks might prefer that, but this doesn't mean that their preference is intelligent.

After all, they permit contactless payments via plastic debit and credit cards which have no such security associated with them, whatsoever ... the same bank cards that we would install in Wallet. These plastic cards are just as easy to steal as an Android device.

And their banking apps themselves generally offer the same features as web access to the banks, and there is no extra security when accessing the banks via their web interfaces ... even when those same web accesses are being peformed on rooted Android devices via Android browsers. In other words, it's easy to bypass bank-app anti-rooting/modding restrictions on rooted Android devices simply by interfacing with the same bank via Android-based browser access on those rooted devices.
[Magisk] majorfigjam:
Well no. Web interfaces are just that, and they control the actions taking place on the website. Banks also have two sorts of websites - retail and corporate, with different functions.

While you're right for retail, to use a corporate banking site, you need to identify yourself normally with 2FA, and often prove your identity with one time tokens before approving sometimes large payments, or arranging to issue a corporate credit card, or whatever.

Corporate banking apps act as proxy secureID type devices - think specialised Google or Microsoft authenticator - and if I can spoof that ID in my device, then I can present myself as a corporate authoriser, and do whatever the true authoriser can. Absent that, I might be able to access the website with a password, but I couldn't sign a payment without the secureID key or app generated token

Given the retail and corporate apps are usually maintained by the same teams, they will apply the corporate standard to retail.

Which is a PIA for us, but logical for them.
[Magisk] majorfigjam:
And as to the difference between card and wallet, there is a per transaction limit after which a pin is required for a card. There is no such limit for Wallet (except being able to unlock the device).

The same bank fraud heuristics apply to all transactions which hit the Visa MC or Amex networks, and for all I know UnionPay etc as well.
[Magisk] HippoMan:
Yes ... and I'm only talking about retail banking sites (i.e., non-corporate banking functions).

I and probably most of us here don't perform corporate-level banking functions via our Android devices, and we can easily perform our non-corporate functions via an Android browser, even on a rooted/modded device. But at the same time, our non-corporate banking functions are generally restricted or even totally prohibited (depending on the bank) when using the bank app itself in a rooted/modded environment.

And the fact that these non-corporate functions are *only* restricted in the bank apps and not via browser access is simply a result of laziness on the part of the banks themselves, who don't bother to write their banking apps to make a distinction between corporate and non-corporate functions in a rooted/modded environment.

So it's not just stupidity on the part of the banks (i.e., allowing unrestricted contactless payment transactions with plastic debit cards while restricting those same debit cards when running under Android in a rooted environment), but also, it's laziness, as described above.
[Magisk] majorfigjam:
Maybe it's a country thing. None of my 3 retail apps care about my phone being rooted, though they're shamiko'd just in case.

Corporate banking and things like Fraedom and Concur need the full works to get round the restrictions on use.

Fortunately I don't have to fight InTune.
[Magisk] HippoMan:
Actually, it's the same with me. My banking apps are in the Magisk DenyLst, and they are unrestricted. But if I take them out of DenyList, they are crippled, and one of them will not even run. At least there is a workaround for your and my bank apps' restrictions via Shamiko and DenyList.

But some other people here report banking apps that go beyond the basic Googlefrinchian restrictions and also perform additional system checks, and these particular apps cripple themselves if they detect rooting or modding, even when they are "hidden" by Shamiko and DenyList.

But for any of those banks which offer unrestricted non-corporate web access via desktop computer, there is no restiction on the rooted/modded Android device as long as the bank is accessed via an Android browser.
[Magisk] rseiler:
Do you think it can now merge with your fork so we have a single spoon edition between the two of you?
[Magisk] majorfigjam:
True, but there is a limit on what you can do in that browser. You can't change the underlying controls on the site, all you can do is what your bank lets you do, subject to any limitations on the identity you present when logging on, which the bank checks when you log in.

In an app, you may be able to spoof the ID you are presenting, to gain access to someone else's accounts. Think PIF for banking systems. You just can't easily do that in a website login. .
[Magisk] osm0sis:
I'm always open to Pull Requests if someone wants to help tidy up the code on my fork more or bring some tangible improvements. 👍
[Magisk] HippoMan:
Well, yes, I see how that ID spoofing might be more possible with a banking app than with web access.
[Magisk] simplepinoi177:
i wonder what would happen if you tried them or the others you knew worked before on older versions like osm0sis' fork v3 or DEV1 or something...

when i first got mine working, i found that i couldn't get the same print to work on DEV1 like i could PIFork, and some other member's are saying that they're not passing even BASIC on 14.6 but if they go back to 14.4, they are at least passing that...

with the fast pace development that is going on PIF and the versions being shelled out (it was only recently that he allowed two .json's and would check if there's a custom one [in another folder] before loading up the default -- meaning his code has changed fundamentally)...
[Magisk] Nergal di Cuthah:
I think it's a fallacy to compare the single programmed chip in your card- which can only transmit a set code for the handshake between chip and reader - with a nfc chip that's programmable based on what software tells it to transmit.

Software-> hardware communication can suffer man-in-the-middle attacks. These banks don't care about us modders, we're not the reason they restrict. Malware can secretly root an android device, plant a MTM code and learn the card's handshake, which then can be coded into a fake card chip and used.

This is the worry of the banking industry, we're just the flies on the windscreen that is designed to stop rocks from hitting the driver.

And neither of my national retail banking apps, nor my well known investment firm app, care if I'm rooted, one is on deny list enforced jic and the other 2 i never got around to denying and all three work. To me it seems to be non U.S. banks that care.
[Magisk] beeshyams:
I

I get your argument but just as FYI, exceptions are common at least in India :

1. Retail banking apps are separate and they don't run in rooted environments unless you put them in deny list or use more tricks. But they can be run on mobile browser.

2. IIRC, I'd mentioned one bank that forces you to use app interface even if you use a browser

Guess, there are many variations depending on local regulations and the banks own view of running on rooted devices. I use 3 banking apps and surprisingly they haven't yet moved to Device Integrity authentication - surprising because in about an year's time safety net servers will be shut down.

We don't have Google wallet here but have Gpay,which runs fine with just basic integrity! Perhaps, it's due to the fact that it is not NFC based but QR code based. We have multiple wallets available all using QR code or pay using a recipient mobile number all running on a nationwide UPI (Unified Payment Interface)
[Magisk] tom1807:
Where is this a new solution? The pif.json has the same content used by chitoreman (and probably xiaomi.eu).

It just automates it a different way.

Cheers

Tom
[Magisk] titomax82:
Even if I passed to your fork and my personal fingerprint, can you explain me what advantage is linked to chiteroman's stopping his method if he uses the same fingerprint of xiaomi.eu? They won't stop applying their method, they're thousands, so google will continue to discover those fingerprint, and lots of fingerprints will be burned anyway, not one more or one less respect chiteroman's work. The only effect is to create more difficulties to people unable to discover their own fingerprint that continue with magisk and module instead of xiaomi.eu method.

I repeat, I don't appreciate any real advantage, but only a side-effect. Maybe I don't consider something?
[Magisk] simplepinoi177:
it will be at a slower rate... the ones using the xiaomi.eu custom ROMs are a fraction of the total users using PIF (take a look at just the number TG channel members)... so while the same fingerprints are still going out and will inevitably be burned, it won't be at the same rate and thus not be burning through ALL potential possible FPs as fast as it works be just to cater and spoonfeed the masses... yes, they can all just literally copy the values into the pif.json, but, again, they are used to being spoonfed and don't even know where to start with all of that anyways...

because, in the end, this is all an uphill losing battle against Google (David vs. Goliath, but i can't see us David winning in the end) -- so while it might be destined to be doomed, at least we will all not be racing towards it with this decision; and by extension, using PIFork will be employing custom FPs help "slow the bleeding"...
[Magisk] majorfigjam:
Let's face it, this whole forum thread is about making our phones appear to be someTHING they are not, so that we can carry on as before in a way that suits us.

Rooting gives us the opportunity to do that, so it's only reasonable that banks and companies (eg Uber, Netflix, Sky TV) that depend on having certainty about their customers should seek to exclude rooted devices which might allow users to appear as someONE they are not.

Meanwhile, no bank that I know offers a Chrome or Edge app, simply because they know that the whole Windows and Linux ecosystem allows root access, and is inherently insecure. The only way into their systems from a PC is through a browser, which is strictly controlled at the server side.
[Magisk] trevtdogg:
the more people that stop, the better. the less people giving out FP's publicly, the more pressure hopefully on those remaining to stop doing so.

or they will get tired of doing it every few days, and if they see they are doing it alone they are more likely to give up hopefully.

above all, it's the right thing to do. it helps the community more in the long run, if everyone finds their own privately.
[Magisk] zgfg:
What would be the Chrome or Edge app as opposed to the 'way through a browser'?

Btw, some banks do offer though apps for Android, iOS and Windows - so the Windows app but that is not through the browser

Regarding this thread and module - of course, it is about pretending to be a different phone than really. All users should be aware of.

PIF was forked from the USNF module, and USNF was kind of an upgrade from MHPC when Magisk v24 provided Zygisk and the way to target the spoofs selectively, so only to com.google.android.gms.unstable aka DroidGuard instead of globally (spoofing globally caused that other apps thought you have a different phone than you really have, causing troubles elsewhere)

And that old MHPC, that was spoofing for SafetyNet at that time, had it hey days we'll back in 2019-2021 (when it was archived, his developer 'retired' from XDA and everything)

However, it's true, probably most of the boobies here do not know about and they were forced to use this module with the era of the contactless payments, and they hardly learn that PlayIntegrity is not some kind of a Google's conspiracy against Magisk or Xiaomi.eu ROMs - it's about unlocking Bootloader that causes Hardware backed CTS attestation to fail (already in SafetyNet), now known as Strong Integrity in PI, and the only way to overcome is to spoof your phone to be another device, that doesn't require Hardware backed attestation, so that can be spoofed then with the fake prints to pass but the weaker Device Integrity
[Magisk] zgfg:
Seems I missed something since I was offline yesterday. Rebasing the strategy - New Era, The Hunger Games
[Magisk] Sergykm:
I did it, but I don't have all buttons. Why? Can you help?
[Magisk] BrimoFan123:
If so then just provide them a link to the guide how to search and test own fingerprint.

I'm repeating myself: time for babysitting need to be over.
[Magisk] furdiburd11:
Thats a dummy json. It gets the new one from a github repo at boot and when the json is deleted
[Magisk] woody4165:
Today I've tried again to use GWallet with no success

Redmi Note 10 Pro with PixelOS Android 13, Magisk 26.4 hidden, PIF 14.6, check ok for DEVICE and BASIC INTEGRITY

Cleared cache and data under Play Store, Play Services, GFramework and GWallet, adding again the credit card

The message on the POS is that the card is not recognized, while using same card directly worked.

Any suggestion?

I have a Poco X3 NFC with Xiaomi.eu installed, do you think it will work?

Thanks
[Magisk] CZ.Kostra:
It gets data for JSON from Xiaomi.eu.
[Magisk] Nicknoxx:
Mine is>
[Magisk] miss:
I'm useless and I don't control the technical terms that developers use. In the past, tutorials were written step by step so that everyone could understand it. I have read three of this thread and I have not understood any of them but I have opened the pixerflasher application as the tutorials mention. Finding a personalized signature is easier than it seems. 1. download a custom rom, from any Android terminal, I use Android 10 2. in the downloaded rom, look in the system folder for the buil.pro file. 3. copy and paste the build.pro file into the pixelflhaser directory on your computer. 3. in pixelflhaser connect the phone to activate magisk above, click on magisk and click on edit buil.pro. 4. save builf.pro and open it in your temporary folder. 5 open the generated .joson file with 7zip. 6. Download the play integrity fix zip, open it with 7zip and delete the joson fingerprint, and then paste the joson fingerprint generated with pixelflhaser that we have open. 7. Flash the new Play integrity fix zip file on the phone with magisk and test if it works
[Magisk] badabing2003:
Are you using v6.4.0.0?

That was released yesterday which has a pif manager, click on that button.

It's more powerful than the previous versions.

I just haven't had the time to update the docs.
[Magisk] Wolfcity:
As @badabing2003 says. Maybe your question is better repealed in his thread for pixel flasher:

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

xdaforums.com
[Magisk] bakaekze:
You have over-complicated things in the end. Pixelflasher can directly replace json.pif on your phone, no need to zip or flash anything once you have pif installed in your magisk/
[Magisk] tom1807:
The repo has a link to this thread, on the right side it shows the most thanked posts.

How much more babysitting is required? :ROFLMAO:

Cheers

Tom
[Magisk] tom1807:
The release notes state that the PIF Manager is now decoupled from the Magisk Manager.

View attachment 6046863

Cheers

Tom
[Magisk] jac0b:
Thanks for the instructions. Finally got my own custom PIF/FP created.
[Magisk] awarexda:
The pixelflasher 2019 version works on my win7 computer and it seems like it is the portable version. Now I have to play with pif and based on the insights here on the forum, it shouldn't be difficult to test fingerprints.

Fingers crossed...
[Magisk] Vision:
@chiteroman a little question (maybe noob), why the space front of " change between the v14 and v14.6 ?

View attachment 6046880

View attachment 6046881
[Magisk] osm0sis:
He switched to tabs 🤮🤦‍♂️