yashsingh1/xdaforums huggingface dataset:
[Magisk] xcl1pse:
Welp depends on banking app your struggle with...
[Magisk] Vision:
@chiteroman I'm little confused, why say I will release a new version for custom spoof later. v14 is not good?

View attachment 6040552
[Magisk] xcl1pse:
Completely rebase... like always...
[Magisk] xcl1pse:
If your not making any custom pif.json under /data/adb, you'll be fine. This new update will overwrite the older one. Or just check the log. This new update bring pixel prop again
[Magisk] chiteroman:
I'm testing between Dobby and ShadowHook because I want to know which one gives less problems. I remember a user reported me some time ago that using Dobby the module didn't work correctly.

It may one day be necessary. Who knows...

I noticed that DroidGuard gets different properties on different devices, I've added that again so if someone sends me a log I might find something useful.

Yes, sorry for not mentioning it. I'm thinking of making the project wiki for useful things and leaving the README for other things.
[Magisk] eac5:
Such a list would always be incomplete due to Google shenanigans. E.g. the Asus print stopped working for some people days ago, but was only universally banned today. Also it would seem tinkering with first_api_level while leaving every other prop untouched makes the difference between passing and failing device integrity on some configs.

I've tested around 3.5k prints so far, and 103 were working last I checked. No doubt that number could be increased by simply using a lower/higher firmware of the same device and playing around with first_api field seemingly at random. The lowest api I have working is 21 and the highest 30, there really are no universal rules to this except perhaps 33+ always failing.

Just in general though, nearly all of the following: Motorola, Samsung, OnePlus, Oppo, Google, Redmi, Realme are a waste of time. You're unlikely to find working prints from these brands without brute force automation on hundreds of samples and getting a couple positives back.

Acer, Asus, Nokia are among the more mainstream brands worth looking into. And of course the best are the obscure Chinese brands no one has ever heard of.
[Magisk] HippoMan:
Agreed. Android is now accelerating on its downward spiral until it hits rock bottom.
[Magisk] rapidm:
The thing is it is not about root. It's about custom roms. I used custom rom for some time now but always without root. Now I have to root (or install new builds constantly) to pass the integrity.
[Magisk] EuK_V:
I think it's time for the developers to think of a different approach how to pass play integrity cause it's just the matter of time when all the working prints are banned. Even if chiteroman stops distributing prints, eu maintainers will continue doing it, and even if they stop, individuals will finish the job, cause i see on channels, forums people are posting working fingerprints and i'm afraid we can't do anything about it.
[Magisk] badabing2003:
It's fine to experiment and try different things, that's the basis of engineering.

But please for heaven's sake be structured, branch your code, experiment in different branches, and when something proves to good, merge it to main.

Don't go rebasing your code on every release.
[Magisk] titomax82:
I have no idea what it is :D
[Magisk] labeed:
Actually useful piece of information, first device I checked for props was some noname phone company and it showed BASIC and DEVICE passed. Five days later still everything passes just fine.
[Magisk] ShaDisNX255:
As long as you have a custom recovery you're already considered rooted. One could argue even with stock recovery and a custom ROM, that's already considered rooting.
[Magisk] michasssxdd:
The phone does not meet security requirements. I updated to version 14. 2. Wallet and Google data cleared... Where am I going wrong?View attachment 6040566
[Magisk] V0latyle:
Well, this is all a temporary solution. One of the big questions some of us have been asking is how does PI detect a print mismatch? Since the prints aren't banned on the devices those prints belong to (no mismatch), we evidently need to figure out what GMS processes are checking global props.

The way PIF works, at a very elementary level, is that it spoofs the custom fingerprint specifically for PI. All other processes on the device can see the real props. So, it should be relatively simple to spoof complete props for the print we want to use, so that PI doesn't know there's a mismatch.
[Magisk] osm0sis:
But you've already done that literally 10 times just in the last 3 weeks, so what's going to be different with your testing this time? If you're improving your practices that's great, that's what I've been trying to help you with this whole time, but so far, judging by the latest commits, that's not the case.
[Magisk] zgfg:
I'm wondering how many here really use Google Pay and how many Google Wallet:

Google Wallet vs. Google Pay: What's the Difference?

Getting to the bottom of another confusing Google app situation.

www.howtogeek.com

Countries or regions where you can make payments with Google - Google Pay Help

Some Google Pay and Google Wallet payments features are only available in certain countries or regions and on certain devices. Check feature availability Depending on where you live, you can pay the

support.google.com

Many refer to GPay but think actually about Wallet

AFAIK, GPay is only available in some countries, States, Singapore) - the rest should use Google Wallet and for GPay should see like on the screenshot
[Magisk] osm0sis:
It could also be as simple as it checking for an unlocked bootloader only on those specific prints, in which case we can't do anything to fight it.

But again, the fact they're not just enforcing this for all available prints by default actually suggests they do want us to just be more clever about it, and perhaps all use our own found prints instead of using public ones en masse.
[Magisk] V0latyle:
Weren't we able to hide unlocked bootloader on older devices?
[Magisk] BROKEN1981:
I say Gpay but yes, I actually mean wallet
[Magisk] simo2001:
Probably a noob question but is it not possible to modify the real build prop to avoid any mismatch?
[Magisk] osm0sis:
Not that I recall, not actually. My memory is very long, but not infallible, so you'd have to look into that. 🤔
[Magisk] osm0sis:
Same as global prop spoofing, which can just totally break your device/ROM since it's not what it thinks it is at that point.
[Magisk] DrTrax:
I tried to use the build.prop info of my Fairphone 4 stock ROM but somehow I always get BASIC, not higher... without the PIF, everything fails! Maybe I did something wrong, since I found two different values for device name :/

Now with PIF v14.2 (w/o custom pif-file) it passes BASIC and DEVICE AND I cna finally use Wallet, banking apps, ... again! c:

Edit: Removed attachment
[Magisk] DrTrax:
Actually yes... Magisk Denylist does, I still use Momo v4.0.1 and without the app in the denylist, it detects an unlocked bootloader...
[Magisk] inconnn:
I can hide unlocked bootloader on my phone (Nothing Phone 2) using the LSPosed module BootloaderSpoofer, but I think it only works on specific phones that are set up a specific way, and when I use it on Momo, it removes the unlocked bootloader result, but then it's able to detect Zygisk and stuff
[Magisk] xSnowLeopardx:
Damn, didn't know GPay was still a thing.
[Magisk] xcl1pse:
That's old, why not using latest?
[Magisk] titomax82:
14.2 = Green again :D

@zgfg My Google Pay was automatically replaced by Google Wallet since the end of 2021.
[Magisk] V0latyle:
Has anyone using a custom print had their print stop working?
[Magisk] michasssxdd:
Mine is also green... But a message pops up that the phone does not meet the security requirements... Where am I making a mistake?View attachment 6040586
[Magisk] BROKEN1981:
Can you delete that? I fixed it for you and will pm you.

Edit: PM'd you and fixed it.
[Magisk] xSnowLeopardx:
Delete cache + data of the app you get the message from (GWallet perhaps?)

+ do the same for Play Store

+ do the same for Google Play Services (manage -> delete everything)

Then reboot.
[Magisk] dmenezes:
72 hours and counting, custom self-mined pif.json still good! 👍👍👍

View attachment 6040595
[Magisk] BROKEN1981:
Mine is still working.
[Magisk] miss:
uninstalled magisk, wallet doesn't work, I have the bootloader unlockedView attachment 6040597
[Magisk] BROKEN1981:
Bro, delete that prop. The dev will grab it and make it useless for you. LoL Check PM I sent you
[Magisk] V0latyle:
Same here
[Magisk] Umgak:
Day 4, still going strong. Set it, test it, forget it. Don't be a usage spike.

If your bootloader is unlocked, you will fail every time unless you use magisk to patch keystore and spoof an older device (which is what PIF does). Uninstalling Magisk and not relocking is a sure-fire failure because it will try to use hardware backed attestation as shown in the screenshot.
[Magisk] V0latyle:
I almost want to create a poll and ask how many people are still on a custom print, as a running comparison to the published prints in these modules that quickly get defeated

@chiteroman if we can't figure out how to prevent the mismatch detection, at the very least we should make it slightly simpler for everyone to come up with their own print.

Ideally, this means that your module doesn't have any prints at all and it's the end user's responsibility to pick one but at the very least, choose randomly from a list of working prints so that each person is using a different one

I'm not sure how many people are using this module but I suspect it's just a couple hundred at most
[Magisk] xcl1pse:
3 weeks and still counting 👀 even I still on 14 beta lmao
[Magisk] eac5:
The Telegram group alone has 5.3k members so the number of users should be quite a bit higher than your estimate, maybe 10-15k
[Magisk] psychoela:
3 devices with 3 different fp still fine here😁
[Magisk] HippoMan:
I assume you mean a custom print other than the ones offered with the @chiteroman builds, correct?

It's too early to tell with my own custom print.
[Magisk] HippoMan:
Oh, now I see what you mean by "custom print" ... *not* the ones published with the PIF releases.
[Magisk] V0latyle:
Yeah. Exactly.
[Magisk] miss:
whit 14.2, in Android 14 pixel 6, now work wallet

thanks
[Magisk] xSnowLeopardx:
Still chilling @ v14 with my first found FP working.
[Magisk] awarexda:
Thanks for the reply. I would like to try - is there any guide?
[Magisk] BROKEN1981:
LoL just got off the phone with my mother. She's wondering why she can't use wallet. Guess 13.3 stopped working for her lmfao 🤣🤣

That took a long time though to be honest. I'll have to give her one of mine.
[Magisk] d4m4s74:
Why did you root your mother's phone anyway if she doesn't know how to use it?
[Magisk] Klappp:
I modified the software on my mother's phone to get the latest Android, unlimited photos backup and adaway. She likes her phone and she only wants to replace it once it croaks.
[Magisk] kokica2000:
@chiteroman Thank you for your hard work and trying to outsmart the big G, but I really hope that resetprop version of your module returnes fast, because my banking app refuses to work without it.
[Magisk] zgfg:
@chiteroman could get number of downloads from Github
[Magisk] DrTrax:
Magisk 26.4 or Momo 4.0.1?
[Magisk] PatrickJK:
Momo. The latest is 4.4.1
[Magisk] shajman:
Hey all. I'm on v14.2

I'm passing basic and device. And Google Wallet doesn't give me an error anymore.

However, I still can't use it because it shows me that my device doesn't meet security settings in the 'Tap to Pay Setup' screen.

What could the reason be?

View attachment 6040617
[Magisk] javisky:
unlimited photos backup???
[Magisk] PatrickJK:
It's a standalone module based on pixelify that gives you the unlimited google photos backup. Github
[Magisk] DrTrax:
WTH?! I though Momo was deprecated/abandoned!

Fuu... TEE broken and Zygisk found >.<
[Magisk] mkcs:
Awesome! It worked on xiaomi.eu MIUI 12.5.6 on Redmi K20 Pro, immediately changed from HARDWARE_BACKED to BASIC after flashing this magisk module. Tried both kdrag0n and displax universal safety fix, however, they both fail to switch back from hardware attestation.
[Magisk] FIERA03:
Officiall said that the supported version is from 6.0, so it's worth a try👍.
[Magisk] pndwal:
If it really does support Android 6.0, then that clinches it: the app is NOT enforcing strongIntegrity! 🙃 PW
[Magisk] zfk110:
still failing on my S5 running LineageOS based Android 11, but I can pass Safetynet check
[Magisk] pndwal:
Interestingly Uber Request a Ride, Uber Driver and Uber Fleet all require Android 8 so it's quite possible that any of these now require strongIntegrity...

Looks like you can still order your Uber Eats with older devices however... But not much older 😜 PW
[Magisk] pndwal:
Not failing... Working.,.

Nb. deviceIntegrity is equivalent to ctsProfileMatch + Basic only evaluationType... strongIntegrity is equivalent to ctsProfileMatch + Hardware evaluationType...

👀 PW
[Magisk] FIERA03:
I tried bootloader spoofer but still could not sign up 😭
[Magisk] zgfg:
What's failing - you cannot pass Strong Integrity with the Bootloader unlocked.

Googled fixed their flaw on Jul 28 and that fact has been commented in the thread tens of times

Newcomers, please read the thread before asking....
[Magisk] FIERA03:
There is a slight error in this and I would like to correct it.

My-Number Portal can get to the screen that does STRONG detection even if you do not have a unique Japanese citizen number.

I found apkmirror, so you can try it if you want. Luckily, there doesn't seem to be any program like TB-Checker or CarX Street that prohibits it from installing from outside the Play Store.
[Magisk] zgfg:
I don't have Jap Pin number but I can get this far with no 'problem' related to Strong Integrity failing

Tested on Magisk Delta

Zygisk + Shamiko

Play Integrity Fix

Unmount Modules + Hide My Apps
[Magisk] FIERA03:
View attachment 5985119

Maybe this is a Japan-specific problem and the restrictions are not so strict in other countries.

I tested under almost the same conditions (only Shamiko isn't installed), but this screen appeared and I could not proceed.

It seems that the government is treating the bootloader and other(STRONG Integrity) problems as "root" all together. I guess it's too much trouble to explain to the public.
[Magisk] chiteroman:
View attachment 5985123

Working even without adding to denylist in Magisk 🤣
[Magisk] FIERA03:
Activation can be done in Japan too. Try pressing the "登録・ログイン" button😅.
[Magisk] FIERA03:
As an addendum to this, I will show that TB-Checker hides everything without STRONG. Sorry for the long image💦.
[Magisk] GWARslave119:
to be fair, 27 pages IS a lot to sift through, I just happened to read the last page as well and saw this ha. Maybe if they had some kind of format for posting important updates instead of just happening to see a post that shows it?

Unless there is an easy to see that info and I'm just blind ;p
[Magisk] GWARslave119:
I'm not sure if this is directly related to the integrity check api thingy, but is there a way to get around this? Or does it depend on phone model and android version, or other things...

I have the safetnet fix module and Shamiko installed , so I pass device and basic integrity, and the app is checked in the DenyList..

View attachment 5985701
[Magisk] pndwal:
Please say which screen... I haven't found a page that fails in this app. 🙃
[Magisk] zgfg:
Ok but reading just few last pages should be enough to find. I'm sure that I've repeated the same every time to another newcomer couple of times during eg the last week.

Hence it becomes pretty frustrating seeing again and again somebody new asking/complaining about the same, questioning yourself why do I waste time when the answer will read only that single one who asked plus many who well know (they also get annoyed reading the same questions and answers repeatedly), but those who should read will not bother to
[Magisk] GWARslave119:
True, but there's times when I don't think to read the last few pages. Like on here actually, it wasn't until after I installed the module and still didn't pass strong that I thought to skip to the last couple pages. I dunno, just seems the info would be easier to pass along if main post contained updates or something. Its whatev

Edit: Either way, I don't even know if passing strong will fix that issue I mentioned, was just a thought to try
[Magisk] zgfg:
Actually, in the OP post #1, @chiteroman attached a screenshot of JSON result from Play Integrity attestation, showing:

MEETS_BASIC_INTEGRITY,

MEETS_DEVICE_INTEGRITY

Hence MEETS_STRONG_INTEGRITY is not listed

But probably a plain screenshot like below would better point out what to expect and what not
[Magisk] inconnn:
have you cleared the cache of google wallet?
[Magisk] FIERA03:
I've been wondering for a while now, is it possible to directly trick DroidGuard into passing PI by hacking GMS directly (BigG will claim it's a crack) or using a microG(modify) instead of a fingerprint and prop?

(This is only "in theory" and assumes no risk of a lawsuit from BigG)
[Magisk] manjaroid:
Still good as long as the module is 14.0 and not 14.1 or osm0sis's fork.
[Magisk] frank93:
clear wallet cache, reboot, and/or wait. PI looks good/okay with 2/3 green checks, but wallet result is a bit delayed as far as i understood.
[Magisk] shajman:
Yes I have. Multiple times.

I don't get why it's failing when wallet itself isn't giving me any errors.
[Magisk] michasssxdd:
I'll check tomorrow because I've cleaned everything that needs to be done and it still doesn't meet the safety requirements...
[Magisk] D€INOS:
Day 5, still working fine.

Using v14 until the fingerprint is vaporized, then it's time for osm0sis' fork.
[Magisk] xSnowLeopardx:
And you also did this?
[Magisk] manjaroid:
Pages 177 and 179 or thereabouts.
[Magisk] wugga3:
Reminds me of the days of the key generators/cracks/fixed executables etc for all things on the old PC for all kinds of software

Need the Android version of something like that for this fingerprint thing... An app that could just randomly generate / verify working or not... then update itself or not and then move on as needed on the fly ... (Caught all kinds of other nasty stuff also lol that only dos could remove)
[Magisk] shajman:
I had done all except wallet.

Just cleared all data from the three above now. Rebooted. No difference.

The thing is that google wallet doesn't give me the usual security message when I open it. It's perfectly fine there.

Issue is when I check Tap to pay setup and I get the error shown in the screenshot I shared before.

And I know it's not working coz I used my card in a store about n hour ago and even though it showed a tick on wallet, the merchant machine asked for the transaction to not be authorized.

And then I got a message from wallet stating the transaction had failed and the amount reversed.

This is what lead me to check the 'tap to pay Setup' screen.

It's the first time I've ever faced this kind of issue.
[Magisk] xSnowLeopardx:
And you meet both integrities?
[Magisk] Captain_Throwback:
Been using a custom print since @osm0sis updated his pif generation script to support json, and found a couple of backup prints, but haven't needed them as the first one I found continues to work fine for my phone and my wife's.

I just have the other two if ever needed, and I already know where I can get others, just not going to bother unless it becomes necessary.

It seems most "technical" users and devs are in agreement that self-provided fingerprints are the way to go (outside of @chiteroman, I suppose), so I'll continue using the Play Integrity Fork for the foreseeable future.

I really do miss the days when this site was called "XDA-Developers" and even the non-devs would do their best to try and understand and learn rather than just expect a simple working solution without any effort or research. And to think it all started going downhill because of Pokémon Go...
[Magisk] inconnn:
maybe try disabling all your other modules? it could be possible you have a module or app or something that's setting Google Wallet off just enough to disable Tap to Pay
[Magisk] dcarvil:
Unfortunately, eventually you will not be able to find any working FPs, because they will all be blocked. There is a limited amount, and we are losing one every day or two.
[Magisk] gpvecchi:
Google is pushing everyone to use KernelSU...
[Magisk] shajman:
I have just two modules. Integrity Fix and Zygisk detach.

Yes I do. Checked both integrity checked app as well as Play Store Developer options.
[Magisk] xSnowLeopardx:
Fascinating... My knowledge/advice really ends there, sorry mate
[Magisk] V0latyle:
Well, some of us are going through lists of props and confirming which ones work vs which ones don't. There are hundreds.

But.

The problem is disseminating them without Google getting ahold of the list and targeting every single print for mismatch checks.

So far, that does seem to be the case. However, one user was recently able to get a print from a certain recent generation Pixel working, and we haven't even come close to touching bottom on how many working prints there are.

Source?
[Magisk] shajman:
Thanks for the help.

This is so frustrating. Not sure why I seem to be the only one facing this issue 😔
[Magisk] xcl1pse:
Even KernelSU can't help. It just KernelSU modify kernel itself instead of boot image. If your on Custom ROM with KernelSU embedded and working fingerprint then yes, but eventually google will banned that fingerprint and your no longer pass device integrity 🙂
[Magisk] xSnowLeopardx:
Can you either edit the above post or make a new one and tell us (in a list for example) everything you have got going on? What mod (and its version) you're using (fork or not), if you're using a custom FP, since when that FP stopped working or if it ever worked at all, Magisk version, modules and their version, stuff like that.

I really want to help people in here, so yeah let's see what's up.
[Magisk] chiteroman:
Release DEV v1 · chiteroman/PlayIntegrityFix

Module will read /data/adb/pif.json file to spoof your custom props. Added ro.build.id Added vndk.version If you aren't a developer or advanced user, do NOT use this version.

github.com

Released the build with pif.json reading support.

It will be a separate version so it doesn't confuse normal users.

pif.json template: https://github.com/chiteroman/PlayIntegrityFix/blob/dev/module/pif.json

You can remove this three props: FIRST_API_LEVEL, BUILD_ID, VNDK_VERSION if you don't find them.

I recommend to set FIRST_API_LEVEL to 21.

BUILD_ID is "ro.build.id", you can get it from fingerprint.
[Magisk] osm0sis:
Nice! Had that idea (PM'd it to chiteroman actually haha) awhile back as well, glad someone else landed on it and implemented it. Now, the only (big) question would be, will it kill the advanced editing options on a Pixel 8 Pro? 🤔

Okay, you've mentioned that a few times now, but I assume you double checked your filename/path as /data/adb/modules/playintegrityfix/custom.pif.json for mine? Failing that, I hope that you would be willing to PM me your json so that I can investigate. My fork comes from directly before chiteroman released V14.0, so is currently operating the same as his PROPS-v2.1 release under the hood. There should be no technical difference, so it should work.
[Magisk] sawdoctor:
My fingerprint isn't particularly new but it is one that shouldn't have worked but did so there's hope
[Magisk] SOCOM-HERO:
did you clear play store data and play services data?
[Magisk] shajman:
Multiple times. And restarted after each time.
[Magisk] shajman:
Gimme until tomorrow. It's late where I am now. I will attempt to use my card again tomorrow and see if the issue persists.
[Magisk] m0han:
Tried v14.2 from @chiteroman. New entry seen in TBChecker app.