yashsingh1/xdaforums huggingface dataset:
[Magisk] Fishawy:
Completely agreed about the users and the plug-and-play parts (by the way, English is my second language too. Most of my edits here are fixing typos and sometimes grammar, lol).

Unfortunately, the reality of the situation is that they're cracking down, and what's being done here is trying to educate people on how to manage an individualistic solution, and provide them the necessary tools to do so, since a manual part will need to be done no matter what (so long, plug-and-play, or at least this is what it looks like).

Understandably, many of us here won't be able to proceed with this due to several reasons (knowledge, tools, language, you name it), but what's happening now is merely an attempt to try and save as much as possible before it's too late.

Thanks for sharing your views on this, and have a good night. (from the future, 4pm the following day in Australia).
[Magisk] xSnowLeopardx:
Ok, very fair. I take my words back. I'll be thinking about switching to the fork myself, thanks for the explanation.
[Magisk] titomax82:
@Nergal di Cuthah

Following your advices, I have again "basic" and "device" pass, positive result when searching netflix in playstore. Logcat points to "asus....."

The only problem is Google Wallet not meeting security requirements. Something changed from previous versions of the module? Do I need do add something in the deny list? (never had any google related check before)
[Magisk] Nergal di Cuthah:
I dont use pay but i believe if you clear pay cache and someother cache (maybe play services, hopefully someone will correct me). Sadly the other option is dats for the two which means reentering your cards and/or smartwatch
[Magisk] Fishawy:
I know first hand how painful re-adding bank cards and transport passes to Wallet can be, so don't wipe it (yet).

I've read on here multiple reports that it auto-fixes in about 24 hrs. Maybe while you wait, try adding Wallet to DenyList and wipe cache only.

Good to see you made it to the green side (almost).
[Magisk] jabennett:
This, ultimately, is the decision most users here will face. You can buy a phone, camera, TV, or washing machine that will do a fine job making calls, taking pictures, watching movies, and washing clothes, without ever reading a manual. But every one of those manuals will say something like, "NO USER SERVICEABLE PARTS INSIDE."

So those of us who want to force our washing machine to also do dishes, accept the risk and responsibility of doing so - including educating ourselves accordingly. What frustrates us most, I think, are other users who also want non-standard features, but complain that they should be just as simple as factory defaults. Sometimes, that's possible, thanks to the selfless work of developers here. Sometimes, it isn't. And often, it is for a while, and *then* it isn't, like now... at which point, all the self-entitled wannabe "power users" get upset and show up here demanding the functionality and simplicity to which they've become accustomed, can't be bothered to even scroll back a few pages to understand the issue, and then act like they want to talk to a manager for "breaking" their phone. 🙄

*That's* what's becoming tedious, in my opinion. If you want your dishes washed, buy a dishwasher. Don't buy a washing machine, knowingly "abuse" it in the eyes of the manufacturer, and then publicly complain that it stopped doing something it was never intended to do.
[Magisk] Nergal di Cuthah:
@titomax82

I just checked, i meet both and am playstore certified, but wallet says I'm not secure enough to do nfc, well i guess that's why i see a therapist
[Magisk] meiser:
True, but I was very careful to use the right file names/folders. So this might not be the root cause.
[Magisk] Oswald Boelcke:
Madam, Sir! Please contact me privately if you want to discuss this. Thanks a lot.

Respectfully

Oswald Boelcke
[Magisk] Iridule:
I'm using a stock version of android with magisk and when I check integrity using ps it shows my stock fingerprint and other details passing 2/3...can I input those into the custom.JSON ? I do have 14.1 pif working. I was just curious.
[Magisk] Nergal di Cuthah:
Off topic: the search box on top of pay's screen is suggesting apple deals, so you guys jumping ship from android over pif can pay your way.
[Magisk] Nergal di Cuthah:
No what you see on the integrity checks is what the checker sees not what gms sees. The way to see the fingerprint sent you need to logcat
[Magisk] Yeedatoy:
This is in developer options, shared data. Wonder if this has something to do with some people being unable to get theirs to work after trying later on well past setup.
[Magisk] HippoMan:
Does anyone know of an app that is guaranteed to crash immediately when launched without DEVICE integrity, and will always successfully launch when DEVICE integrity is in effect?

It could be any app whose initial screen properly comes up when DEVICE integrity is in effect, and which just crashes immediately after launch without DEVICE integrity.

If such an app exists, I think I can write a Tasker task which does something like the following in order to automatically check whether my currently installed (custom.)pif.json is still giving me DEVICE integrity ...

* Install a Tasker profile which monitors the launching and killing of that app (this kind of profile is easy to write in Tasker).

* In Tasker, launch the app, wait maybe 30 seconds, and then kill the app.

* If during that 30-second interval Tasker detects that the app has died on its own, assume this means that we've lost DEVICE integrity, and then take appropriate action.

The definition of "appropriate action" depends on the user. Some people might just want a notification about losing DEVICE integrity to be triggered. Others (like me) might want another stored (custom.)pif.json that was previously downloaded to be automatically installed.

Any suggestions as to which app might exist that I could use for such sacrificial purposes?

Thank you in advance.
[Magisk] Fishawy:
Love the idea.

Can you try Uber Driver (not rider)? I'm reading it even requires STRONG integrity (dunno if it crashes). Not sure if that's helpful to this Tasker implementation, but check it for the crashing part.
[Magisk] Nergal di Cuthah:
Maybe that starling bank that everyone has trouble with, read the last few pages of displax's mod for a version that does this
[Magisk] Yeedatoy:
Would this help? https://github.com/vvb2060/KeyAttestation
[Magisk] Yeedatoy:
Obviously not what you asked for but could be helpful otherwise unless I'm misunderstanding you
[Magisk] HippoMan:
Thank you!

I'll give Uber driver a try. I'm not looking for a crash in non-STRONG mode, but rather, in non-DEVICE mode, but perhaps there's a way to get Uber driver to perform that way.
[Magisk] HippoMan:
Thank you. I know that there are apps like this which will tell us our integrity status, and I know we can also check that via GooglePlay Developer mode settings.

But I'm looking for some way to test for DEVICE integrity in a totally automated manner, without my having to take any manual action.
[Magisk] HippoMan:
Aha！Thank you! I'll give starling a try.
[Magisk] Nergal di Cuthah:
On second look, maybe starling is detecting magisk

Banking app (Starling) detecting Magisk

A banking app I've been using for years has always worked after putting it on the Deny List. I updated it recently and it now won't work with Magisk installed regardless of what I do. As soon as I patch the boot image with Magisk it complains...

xdaforums.com
[Magisk] HippoMan:
Well, your starling suggestion was still helpful, because it gave me the idea to investigate banking apps in general. I'll check others, now.
[Magisk] makeyourself:
Yeah Play Integrity is one thing the Starling app couldn't care less about, for now at least. It tries to detect a few things, root, Zygisk/Riru injection and ro prop changes being the ones that come to mind. But not PI status.
[Magisk] jabennett:
Have you seen this already? It's a similar effort that leverages GPay's own background device attestation process, querying the current status from its local database:

GPay Checker: monitor of Google Pay availability

Google Play Protect now triggers onto app (that's honor for me), but here nothing criminal. You can safely skip warning. There is non-zero theoretical possibility, that using this app increases risk of banning your personal fingerprint. There...

xdaforums.com
[Magisk] makeyourself:
I'm sure some do exist but I'm yet to come across a banking app that cares about Play Integrity, Google Wallet aside obviously.
[Magisk] zgfg:
If courious, please find the answer in this thread. Been answered many times

Play integrity does not display you back your phone and ROM. Play Integrity (based on the spoofs) displays only:

- what you pass

- requestor app's package name

- nonce and so

Use poor PI API Checke and you will not find there any detail about your phone and ROM. Open JSon verdict and check what is exactly inside

Requestor app (TB Checker, PlayStore) displays how it sees your phone.

But spoofs are not global but targeted exclusively to the DroidGiard app (by package name) hence requestor app sees and displays real things.

Only DroidGuard is blinded by the spoofs, so spoofs are used only between DroidGuard and G server that responds verdict

You wouldn't like that PlayStore (not being Droid-Guard but requesting PI API Checking) thinks that you have 5 years old phone (based on spoofs) with older Android, smaller display, etc, and that PlayStore, based on that, dictates which apps you can install or not

More details back in the theead
[Magisk] titomax82:
@Fishawy and @Nergal di Cuthah

I will go to a therapyst too.... Tried to delete Wallet data and nothing changed (cards still present). Then tried to delete all, I mean uninstalling the app and then reinstalling and all cards were present! (I noticed something loading for less than one second at first app opening). At the end I still have security requirements warnings...

Google changed something in Wallet maybe.

I'm even more confused....
[Magisk] HippoMan:
Oh, this looks promising, and I'll be investigating it. Thank you!

It might not quite help me, however, because it might check other things besides just DEVICE integrity ... such as whether screen locking is enabled, for example. I don't use GPay itself, and I always use Swipe locking.

But I'm definitely going to look into this app!
[Magisk] Nergal di Cuthah:
Do you use wallet or pay? I have pay, but knew wallet was a seperate app at one point. Just wondering, thread wide i wondered this.
[Magisk] zgfg:
That app checks the CACHED status of GPay

You now know the trick:

- apply wrong JSon prints and force by killall

- check PI and it will fail

- but GPay still runs on its previous positive cashed PI API results, hence it did not change its status and the given app will not provide you instantly any info about the now failing PI API

- only when GPay refreshes its PI API test (in the background), it will change its status and only then this app will know and inform you about

There can be hours in between

Two times I had the case that when G banned spoofs in the morning, that I was still shopping and paying from G Wallet - without updating the module/spoofs
[Magisk] locolyric:
i am wrong with the "new phone" as i just try on a unroot phone , getprop command doesn't have enough information. and i already try to get buildprop files on the website.

Too bad all setting i use can only meet basic integrity pass .

do you have any hint that i can find some model to get device integrity pass too?
[Magisk] Fishawy:
Check the post right above mine from zgfg, confirming what we discussed earlier. Wallet refreshes the API in the background periodically (hours), so you might need to wait a bit longer.
[Magisk] Fishawy:
It wouldn't be wise to post links here, but check the guide by osm0sis linked in OP post. This will tell you how to search for and use one.
[Magisk] oneaminra:
I have managed to get google wallet to continue work yet once again by installing magiskhide props config and change to certified device fingerprint, i also disabled everything inside "edit magiskhide props config", then install latest play integrity fix
[Magisk] carlese:
You need to delete all data from google play services to get it to work again after a reboot..
[Magisk] titomax82:
This means "hours" to set my wear os again.... Solution not possible to me.

The strange thing is that I succeded paying with Wallet some minutes ago despite the warning.

@Fishawy - @Nergal di Cuthah - @zgfg

Is there a way to clear GPay cache?
[Magisk] Fishawy:
If you're talking about Google's end, then this is a server-side thing that none of us have control of.

If paying is successful as you say, then you're not really losing anything by waiting. Don't wipe (so you'll avoid the "hours" needed to re-setup wear OS), and wait until it's refreshed and fixed.
[Magisk] zgfg:
In the case I described I used Wallet just to pay - enable NFC, come close with the phone, pay, force close Wallet (and switch off NFC)

Intentionally I did not manually open Wallet to play with my cards - in that case, I think, it will go to refresh its cached PI status

In the Settings, Apps, I do have Clear Cache for Wallet - check the screenshot.

I haven't played with that option
[Magisk] m0han:
That YMMV in the Pixel Flasher description! ;)
[Magisk] Imperator_Dei:
I don't know if I understood correctly, but it seems like you're trying to automate PI checks on a regular basis, wouldn't doing so create a spike in usage for the fingerprint you're using and allow google to easily ban it?
[Magisk] maxmax0:
I confirm that deleting wallet data does not remove cards. Once I had DEVICE_INTEGRITY, deleting wallet data fixed all wallet issues instantly.

PS: I will also need to see a therapist, because since a couple of days I obsessively check for DEVICE_INTEGRITY at random times, and always chuckle like a madman when it's there. I dread the day it will disappear, I am not sure what I will do, I am afraid, help me....
[Magisk] zgfg:
No, I don't push constant updates - to the contrary, except when I'm testing the jsons to work - but then I avoid testing (jsons I don't know if they would work or not) through Playstore, Developer options
[Magisk] Fishawy:
Welcome to the club.

I have it on good authority that XDA mods will provide therapy services for all impacted 🤦🏻‍♂️
[Magisk] simplepinoi177:
MODERATOR ANNOUNCEMENT

​

Even though it has been mentioned previously before (the previous post to this to name one), I wanted to make a whole other post/PSA so it is properly re-iterated and comes across as clearly and definitively as possible.

ANY FURTHER COMMENTS/STATEMENTS/REMARKS IN THIS THREAD ON ANY MODERATOR ACTION TAKEN (FROM ANYWHERE ON THIS SITE; NOT JUST THIS THREAD) WILL BE INDISCRIMINATELY REMOVED!

​

If any member has thoughts/concerns/criticisms/comments/etc. on any moderator action, I am more than willing to hear them out -- but discussing it here (and not in private) is both

inappropriate and off-topic.

In the end, it can be discussed elsewhere privately -- so if you still feel strongly about it and wish to discuss it, my inbox is always open and to please feel free to send me a PM conversation.

So, as this thread is a fast-paced/moving one, these kinds of posts might not be seen or removed right away, but be forewarned and don't be surprised if you suddenly find your post completely removed from the discussion/thread eventually.

Everyone's cooperation is appreciated,

simplepinoi177 FSM (Forum Specific Moderator)
[Magisk] RichyRicho:
Unfortuantely my bank penalizes me for not using my virtual card, so I cannot hold out anymore.

Its been a bloody good run gentlemen!

Thank you to TopJohnWu and everyone else involved.

I won't be surprised if TopJohnWu is behind all of this, Google forcing him to kill off what he created.View attachment 6040474
[Magisk] BROKEN1981:
Thanks for that! Now I understand why I can fail and still use Gpay for awhile
[Magisk] sawdoctor:
Looks like the fingerprint in 14 and 14.1 has now been banned. Lasted longer than the last one
[Magisk] Gilg@mesh:
my custom one I found still works.
[Magisk] rogers11:
As expected.
[Magisk] sawdoctor:
I have about 100 build props downloaded took about 10 attempts to find one that worked. Several failed all 3 integrity lol
[Magisk] osm0sis:
So, now we know, Mr. Play Integrity working at Google sometimes takes Mondays off. 😉
[Magisk] Gilg@mesh:
proof so no BS. :)
[Magisk] straightcore:
Mine still works too
[Magisk] sawdoctor:
I know it's a bit of a pia trying different build props until you get a working one but with your guide and @badabing2003 pixelflasher even an old duffer like me can't really go wrong. Once you have downloaded your buildprop it's literally 2 clicks on the mouse to create the json. Really can't make it much easier for us old duffers can you
[Magisk] osm0sis:
Yep, that's the beauty of it really! I'm still on my first print that I found 3 weeks ago when chiteroman first implemented the idea I proposed for pif.prop. 🙌
[Magisk] titomax82:
Stock 14.1 stopped working for me :(
[Magisk] chiteroman:
Asus fingerprint rip

View attachment 6040508
[Magisk] Fishawy:
That's your chance to try the fork then.
[Magisk] sawdoctor:
Do you have any idea how big the pool of working fingerprints is? I know it's not infinite and sooner or later we'll run out and be screwed. Just hoping it's later
[Magisk] franco985:
Could MAgisk Delta fix play integrity? I just ask, thanks in adavance.
[Magisk] straightcore:
Did you expect something else?
[Magisk] sawdoctor:
I get it i really do but @chiteroman is damned either way. He keeps trying to help users and then we run out of fingerprints and he gets burnt. He stops providing fingerprints and then he gets a 100 pms a day with sob stories from less technical users who start begging him for a working json.

Untill/unless we find another way of bypassing play integrity we're on borrowed time. Other Dev teams are providing/updating an online fingerprint and sooner or later Google will just get bard to test every fingerprint on their servers and ban all the working one's
[Magisk] swour:
What you correctly pointed out last Thursday should be more obvious today.
[Magisk] makeyourself:
In short, no
[Magisk] chiteroman:
v14.2 updated to fix latest Google changes !

Release v14.2 · chiteroman/PlayIntegrityFix

OUTDATED, NOT WORKING. Plug and play version! If you want to spoof your custom props use: https://github.com/chiteroman/PlayIntegrityFix/releases/tag/DEV-v1

github.com

DO NOT UPDATE TO THIS VERSION IF YOU ARE USING CUSTOM FINGERPRINT!

This build doesn't support pif.json. I will release a new version for that later.
[Magisk] xSnowLeopardx:
I'm sorry- (not really but that's how you start this sentence)

I'm sorry, but the latter in your first paragraph is just the most fair thing. Less technical users really did everything else up to this point with altering the bootloader and rooting, but fail some research and trial/error?

I think I am allowed to say this, since I was one of them. Couldn't understand for the life of me what fingerprints were and whatnot. Now, I have 15 working ones. Not giving up and actually reading helps.

Rather chiteroman ignore the PMs than getting fingerprints banned, 14.1 style.
[Magisk] Virnik0:
this warning was exactly what I was looking for. So if I run 14.0 with custom FP which works reliably since day one, I am not supposed to update to this version. Understood and thanks.
[Magisk] magaedy:
Worked for me both passes, Thank you so much
[Magisk] osm0sis:
Aaand back to ShadowHook 🤣

chiteroman still changing ABI like days of the week. 😛

It also adds build ID, mirroring the latest changes from custom ROMs though all my prints still work fine without that, adds back that weird cache/debug prop dumping log noise that none of us were happy about, and he completely removed all resetprop module files and pif.json support again. 🤷‍♂️

Edit: He then brought over my full android.yml Actions CI build fixes (even though he still isn't using submodules correctly so those ones aren't needed for him), which makes the CI artifacts zip the actual module zip, without any credit. 😠

Edit 2: Back to burning taimen prints, btw. 🤦‍♂️

PlayIntegrityFix/app/src/main/java/es/chiteroman/playintegrityfix/EntryPoint.java at main · chiteroman/PlayIntegrityFix

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

github.com
[Magisk] ELAD098:
Does this solve the problem of the apps like the bank's not opening ? I installed 14.1 and deleted the pif.json

And I 2 pass but can't open the bank
[Magisk] sawdoctor:
I'll rephrase my post then as I was being polite. Users who just come to xda for free stuff and are too lazy to do things for themselves. But still i don't envy the amount of pms he must get. We both agree if he keeps trying to help everyone then we will run out of fingerprints. If it was 1 a month ok but we'll run out of them in weeks at this rate
[Magisk] quasyl:
Previous version 14.1 didn't work anymore, updated to the last one (14.2) and now 2 pass work again. Thank you!
[Magisk] jean019:
Just a question, after v14, then v14.1 installation, I have a pif.json finguerprint under :

/data/adb/modules/playintegrityfix/

Do I have to delete it or is it normal ? (I'm not a specialist)

Thanks
[Magisk] awarexda:
I don't consider myself a leecher, but please understand that the devious process of finding a working FP (which eventually I will need to find - today I would so if 14.2 wasn't kindly offered by chiteroman) is a NIGHTMARE because...

1) I must find dumps (not that hard)

2) Get the right fields that are spread in a mess of fields

3) Input them in txt file on PC

4) Send txt file to phone, rename to pif.json

5) Overwrite with Solid Explorer

6) Open termux, kill gms

7) Run integrity checker

8) Rinse & Repeat

Well all these after I try to avoid non-working API_LEVELS, Android Versions etc

It's a lottery feeling in some way

Not complaining here, but please undestand the "clog" some of us feel
[Magisk] wfred:
How do they do that? Is there an extra fee for using the physical card?
[Magisk] Claus….:
How is it going with your fps?
[Magisk] zee3are0:
Has anyone compiled a list of compromised fingerprints anywhere? I have a couple of old devices that are stock ROMs I already know don't work (I get unevaluated when using them in a pif.json) and would like to know where to avoid my own wasted time when going out to get my own custom fingerprints.
[Magisk] Gilg@mesh:
if you just use Pixelflasher it's alot easier, takes 1 minute to check if the fingerprint works.
[Magisk] Claus….:
What is your thought on this new strategy? Personal fps is that the way forward?
[Magisk] PieroAnt:
I tried different ROMs but some didn't have the build.prop file inside and if I found it they didn't work. It wasn't easy for me even using pixelflasher. any suggestions on where to find the right roms are welcome.
[Magisk] xSnowLeopardx:
Man, you were 2 minutes earlier with this haha
[Magisk] awarexda:
but isn't pixelflasher only for pixel devices?
[Magisk] Gilg@mesh:
no, this method works for all phones as stated by the developer.
[Magisk] wfred:
Pixelflasher will pretty much automate 2-7 for you

Edit: beaten to it 😐
[Magisk] maxmax0:
Completely pointless exercise. Fingerprint burned? Let's kill the next one! 🤦‍♂️
[Magisk] Serinor:
I second the notion of not providing fingerprints bundled with the module, not because I found working fingerprints but because of the reasons already stated by others. A ban on said fingerprints is inevitable and the pool isn't endless. It's time to accept it: concealing root isn't as easy as it used to be and it's only gonna get worse the more such updates are pushed. I sincerely hope for everyone's sake that this is the last time such an update is published, otherwise (at least this method of) hiding will end soon.

Now, I've been thinking of ways to help conceal this module further and I wondered, couldn't big G simply listen to logcat and ban fingerprints this way? If that's the case perhaps it'd be wise to remove that part of the code.
[Magisk] Iridule:
Would one be able to spoof a fp using Windows Subsystem for Android?