yashsingh1/xdaforums huggingface dataset:
[Magisk] simplepinoi177:
All users who have not implemented their own custom fingerprint has "the same problem" (on 14.9)

passing safetynet is not enough to get google pay to work.

Play integrity fix 14.9 requires a custom fingerprint to get it to work (passing MEETS_DEVICE_INTEGRITY) with google pay.

Confirmed on Play Integrity Fork (a fork of Play Integrity Fix, so I assume if properly set up will work just as well) -- was able to search and find it on Play Store (confirming this because I imagine they might be like Netflix or Turo and if you don't pass DEVICE it might not show up).

It still detected root, but I just had to put them in DenyList and make sure all their submenu toggles were checked. Was able to successfully launch the app after that -- I don't have accounts to check any further, but I imagine that's enough.
[Magisk] akaloith:
safetynet test passes

when i try to add my card to google wallet I get the message

Not possible to configure phone for nfc payments

phone does not meet security standards to do nfc payments. someone may have administrator privilleges or the device may not have certified software

what more should i do? "Play integrity fix 14.9 requires a custom fingerprint to get it to work" ???????

how to do that???
[Magisk] V0latyle:
I didn't ask about Safetynet, you need to check Play Integrity.

Again, check your Play Integrity verdicts.
[Magisk] simplepinoi177:
edited...

Below is a good starting place; if not a full step by step guide/walkthrough to get you there...

How to search & find your own fingerprints [noob friendly]: A Comprehensive Guide w/ tips & Discussion for Complete Noobs (from one)

It seems Google has banned more than 95% of custom fingerprints, so this thread/guide has kind been laid to the wayside. But it's still a great resource to understanding the foundations of fingerprints and all that... This is for any/all utterly...

xdaforums.com
[Magisk] badabing2003:
I know WearOS has this issue, and that's both recent Samsung watches and Pixel watches.

I don't know if older Samsung watches on Tizen support contactless pay, and I know Garmin has their own OS and do have contactless payment, but I don't know if you need to enable wearos feature in Garmin to be able to use contactless pay.

I'm answering here because one of the main criteria for using this module is to be able to make contactless payments, and smart watch solutions has been discussed on many occasions, so are leather wallets ;)

If any moderator or @chiteroman feel that this is OT, please kindly delete it.
[Magisk] simplepinoi177:
This thread is so fast pace (the fastest pace on the site) and so much traffic is coming from Telegram, that this thread has become not that much better than a Telegram channel -- so a good amount of OT is expected and/or is flexible on (unless OP judges and actively requests differently).

But to bring it back to being on-topic (if you're concerned/nervous about it) -- I want my Pixel Watch 2 to have an unlocked bootloader for preparation in case advanced restoration techniques need to be done (as seen innumerably on Pixel devices; so many users on locked devices begging for help that could easily be resolved if unlocked). But because of it, I can't achieve tap to pay on it (which is one of the main features I desire on my smartwatch!); even if it's not rooted (yet)! The only way to get it working is PIF (then PIFork; the exact same set up & fingerprint I have on my phone). So I'm very glad this module works for smartwatches as well -- even though many have suggested simply having a smartwatch locked bootloader to simply get tap to pay working than trying to get it working on phone...
[Magisk] simplepinoi177:
omg...just going through & catching up on the TG channel...

some have (resorted to?) asking chatgpt to "generate" fingerprints...!!!! 🤣☠️

I don't know if it's a joke or not, but if serious, man -- some people really just are so very desperate for 1 step solutions (like the dev or most experienced experts wouldnt've thought of them already if possible)....

**sigh** if only it were as easy as that....
[Magisk] kdsgn3:
I updated the module in my Google Pixel 7 Pro last night (from the old Universal SafetyNet Fix to the latest Play Integrity Fix inside Magisk) which sent it into a bootloop of sorts after restarting.

It will say "Pixel is starting..." while a loading bar flashes across underneath, but never starts up. Which leads me to believe it might be something with Google Play Services, because I wiped the data in that service before restarting to try to get Google Wallet working again.

Any ideas on how to get it out of the loop or reverse the problem without wiping the phone?
[Magisk] simplepinoi177:
That's crazy to think that PIF module caused a bootloop....

but the usual course of action is to unroot (so in your case, flash the stock init_boot.img) and see if you can get back into the OS; then you can try fixing whatever you think you is causing the issue (without root access though), then re-rooting.

But if the issue with the bootlooping persists, because modules can remain in the root folder and come back after re-rooting (patching the init_boot partition), then you'll have to remove the problem module; and the only way to do that is the either entering safe-mode (which also resets all system settings) or running the command adb wait-for-device shell magisk --remove-modules; this will keep whatever problem module interfering with normal startup, but will remove all modules as well in the process; which obviously requires you to reinstall your modules (so please be aware of that).
[Magisk] kdsgn3:
🙏 Thanks! I'll have to try this late tonight and let you know how it goes tomorrow
[Magisk] FrogMaster-:
Pixel Flasher should allow you to disable the problematic Magisk Module.

📳🔥 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] simplepinoi177:
How do you find out or what is the command to see/confirm what device you're spoofing when it's being triggered by DroidGuard?

Because if you run YASNAC or TB Checker, it still will show your actual device....

Sorry, this thread is massive, and searching the term "own" & "device" is too broad a term to not result with every post saying "own fingerprint"; but I know I've seen it somewhere (most likely here)...
[Magisk] majorfigjam:
adb shell "logcat | grep 'PIF'"
[Magisk] HippoMan:
Thank you very much for sharing this info!
[Magisk] akiller123:
Hello everybody!

I am trying to get Google pay to work with my galaxy j5 (2015) which runs lineage OS 18. I have installed magisk , with zygisk enabled and I have the latest version of play integrity fix installed (v14.9). I have also added Google play services , store and Google pay added to the denylist which is enforced. However I cant get device integrity test to pass (Basic integrity passes). I have also tried installing shamiko but it doesn't work either.

I have basic knowledge of what I am doing but I'm not an expert . Any help would be appreciated.

Thank you very much !!!

P.S I clear the cache before running integrity check.
[Magisk] majorfigjam:
You need a custom fingerprint file.

Read the most liked post in this thread, and follow along. Also, if you check back a few pages here, there are many many hints on what you need to do.
[Magisk] downhere:
PIF v14.9 is "empty". You have to fill it with a working fingerprint.
[Magisk] dmenezes:
oh man, another one of these "I don't know what I'm doing and I need help" posts. Another one out of a dozen just today. 😵‍💫

Seriously, it seems people can't be bothered to back-read just a couple of pages, because if they did, they wouldn't been asking -- and there would be a lot less useless traffic in this thread for everyone else to wade through.

I suggest that, instead of responding to these posts individually, that we pin the answer (or put it at the top of the first message in this thread) and simply ignore any posts where it's obvious the poster didn't do his/her homework -- or else this thread will end up being as useless as the TG channel, and as someone else has already pointed, it's quickly getting there.
[Magisk] akaloith:
this is needed in 14.9 ???

14.8 did not need these?

can i revert to previous version?

will newer versions also need this?
[Magisk] cyrax12v:
Thx, module worked 100% for me...I have a motorola g9 plus "odessa" and I couldn't use Google Pay, because it didn't pass "Meets_Device_Integrity", now I'm using it without any problems, with the finger print of my own stock rom, God Bless!!!
[Magisk] BunnyPig1:
Another thing I will suggest is that when you start your pixel device, hold down the vol- button once you see the Google logo and keep holding it. The phone will vibrate in a different pattern and start in safe mode. This will disable all Magisk modules on reboot.

So simplified:

1. While booting, as soon as you see the colorful Google logo, hold vol- (hardware button) until the phone boots. Let go once it has passed the funny vibration pattern.

2. Wait until the phone boots entirely (will boot with only the necessary apps required for android, a lot will be missing but don't panic).

3. Reboot again, open Magisk and re-enable all modules you wish to use and delete the ones causing issues.

Keep in mind that this will reset some settings on android (like default keyboard, launcher etc)
[Magisk] sawdoctor:
Can you boot into safe mode? That will disable all your magisk modules including pif. You can also use pixelflasher to disable magisk modules too
[Magisk] stefaca:
Tried this one. To be honest installation was easy, Google Wallet started BUT after payment in the store bank declined my payment. So, pissing in the wind :(

Problem with Google Wallet was solved on my side: I went to the shop and bought a Google Pixel 7. Wallet is working :D
[Magisk] Lughnasadh:
You should also be able to delete a specific module using this command (with adb root access granted):

rm -rf /data/adb/modules/<module folder name>
[Magisk] V0latyle:
We were all noobs once, and very few of us bothered reading the thread before posting. In fact, many of us who have been around a while still don't.

This thread is one of the busiest on XDA, so information gets buried quickly. It doesn't help that a lot of the critical information isn't copied into the OP or at least linked, so unless we expect people to read 8200 posts and counting...
[Magisk] dmenezes:
I appreciate your trying to protect the noobies and yes, of course you're right: each and every one of us were noobies once, no one is born knowing anything except crying and suckling, everything else is learned.

But that said, I don't understand why people can't at least read one or two pages back -- these questions are so frequent that

more often than not the answer they need is in the *same* page they're posting to.

And their saving a few minutes of their lives by not doing so, of course means that *everyone else* has to spend time of *our*lives wading thought those unnecessary and useless posts.

It gets old really fast, and I don't think it should be encouraged.
[Magisk] gpvecchi:
I used the script to find a fingerprint, I kept trying, but none can pass.

Pixel 8 Pro with 14 QPR2 beta, any suggestion?
[Magisk] Slim2none4u:
And this adds to the discussion how? More useless clutter!
[Magisk] Vision:
ATTENTION NOOB QUESTION

@chiteroman i see on TG, you doing something with TEE, can make it something similar to pass 2/3 permanent either google block it or not the fingerprint it will still work
[Magisk] V0latyle:
Normally I'd agree, because it's proper forum etiquette, but again consider how fast this thread moves. There's no definitive answer or update in the OP, there's no FAQ, and even though you and I know these questions are frequently answered on almost every page, try to see it from a newcomer's point of view, and realize that a lot of this information isn't immediately visible. None of Chit's release notes state that he's removed the built in print, and there's no links in the OP to helpful projects like @TheFreeman193's JSON picker.

If you want to be truly helpful, maybe think about creating a comprehensive guide, or at least collaborating with someone who already has such as @simplepinoi177
[Magisk] dmenezes:
I don't think we need another guide -- the ones already posted on the thread (and helpfully referenced right on the side (or bottom, on mobile) of every page are IMHO more than enough.

But I agree (and even suggested) that the 1st post could have a link to these prominently (ie, right at the top, in blinking red and starting with "PLEASE READ THESE FIRST BEFORE POSTING HERE").

Problem is, AFAIK only the OP (@chiteroman) or a moderator can edit that first post.

@chiteroman, can you please do it?
[Magisk] akaloith:
how to check my play integrity verdicts?
[Magisk] purgy:
Commonwealth doesn't seem to care about safety net/ integrity at all, I've had it happily running with unlocked / rooted etc, with just magisk deny list.

I've even had it on a rooted custom rom, but magisk manager uninstalled, it didn't complain at all.
[Magisk] majorfigjam:
With a play integrity checker app from the play store, or from the playstore app itself, in Developer Options.
[Magisk] V0latyle:
Please read this post

[INFO] Play Integrity API - replacement for SafetyNet

THIS IS NOT A SUPPORT THREAD. For questions and support regarding how to fix your Play Integrity verdicts, see the Play Integrity Fix thread. ⚠️BEFORE YOU ASK A QUESTION, READ THIS POST AND THE FAQ!⚠️ ****Update 12/11/23**** Google has been...

xdaforums.com
[Magisk] simplepinoi177:
Yes....if you read the post below or the pinned post in Telegram (the link in the post), the dev of PIF chiteroman stated he will no longer give what is "needed" (this was v14.6 or something...). Though there has been reports that going back a couple of versions (14.6 or 14.4 or whatever) now has passed since Google has lifted the temporary ban on the fingerprint used...but with everyone starting to do that, it'd only be a matter of time when it doesn't work and/or is permanently banned forever

I tried this when my phone soft-bricked due to Iconify and modifying the QS, and it didn't work; I tried it as you wrote it and as a adb shell command. I should've recorded the error it gave, but essentially it didn't work -- I imagine adb didn't like doing that in Recovery Mode.

I've seen/heard around here that the latest PIF version doesn't work well with Android 14 QPR betas...it might've been QPR2, or earlier....

Is this more likely because a device is too old or something? I kinda assumed all devices would pass if it's locked bootloader and unrooted. Why were some devices OEM keys revoked?

I mean....I know not many people are really/truly digging out some old Android phones from cabinets/storage, but it is good to know for those that are or are-considering-to....
[Magisk] mike.s:
I miss the days when XDA was full of posts by people making positive contributions to Android (and other mobile platform) development, and those who couldn't do so mostly lurked in the background, learning. Now people can't even be bothered to read the first post ("The module has no fingerprint by default. From now on you will have to find one yourself. Good luck.") or the conveniently shown top posts ("How to create and use a custom.pif.json!"). Now they just bust in like a bull in a china shop, saying "It broke! Why? Anyone else? Help!". I'm sorry, but stupidity and laziness should be painful. Being new is not an excuse. Just the opposite, if you're new you should take the time to learn a reasonable amount about things before asking questions about them and expecting others to spend time and effort answering.
[Magisk] thf1973:
I had the same problem with a Pixel 7a, look here for the solution:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com
[Magisk] majorfigjam:
For all of us who (sometimes) feel the same way, who have found a print or two, maybe even shared some, the answer really is in our hands.

There's no point getting wound up. Use your f**k budget wisely.

Stop checking in obsessively just to see who has drifted in from telegram, who is asking the same old questions over and over, and who frankly adds nothing of value to the forum.

We really don't need to be here, unless Google stop our prints working. We should leave this space to those who need help, and if someone is kind enough to give them pointers to existing information, then let those kind people carry on.
[Magisk] sawdoctor:
Can you not just add some of the important information/links to the OP? And if chiteroman has any objections you can always remove them
[Magisk] sawdoctor:
Which pif are you using? Osmosis fork won't work on QPR beta
[Magisk] rseiler:
Fork v5 worked well for me, taking my original-flavor json and doing the substantial conversion to the new format.
[Magisk] niko26:
Hm, I'm confused. I am using chiteroman's module, but I don't see pif.json file inside /data/adb.

I see a folder named /data/adb/modules/playintegrityfix but there is no custom.pif.json file - and I'm not even using osm0sis module.

What the hell...
[Magisk] badabing2003:
I don't have the link handy but if you go to my profile on GitHub and look for Magisk repository, there is a special Magisk build in there if safe mode does not work.
[Magisk] simplepinoi177:
While we could...it would be improper to do so without proper request or permission -- moderator access/tools is more for forum/site maintenance than modifying members' threads (even if it would be more or less helpful). Easily leads to a slippery slope of abuse of power....
[Magisk] thf1973:
Play Integrity Fork v5 works great for me, thank you @osm0sis. I migrated all my working fingerprints with migrate.sh. Thank you for all the work you do!
[Magisk] simplepinoi177:
It wasn't that safe mode didn't work, it was that the adb command @Lughnasadh posted didn't work in Recovery Mode.

But I am curious bout this "special Magisk build"....so if one uses this build, one could supposedly remove a specific module before loading up the OS (where the bootloop hits), or the build somehow does a "safe mode" but without the resetting the system settings or akin to the adb shell --remove-modules command but simply disabling all the modules so one could remove the problem module?

Apologies OP and everyone if this is OT...but I imagine it might still prove helpful/assistive in the context of this thread's module, in case any member gets into further issues with it...
[Magisk] Lughnasadh:
Yeah, don't do it in recovery. You first need to grant adb root access if you haven't already:

adb shell
su

Accept superuser request from Magisk

Then type "exit" (without the quotes) twice to exit.

This should allow you to access /data/adb
[Magisk] simplepinoi177:
how do you do it if one is soft-bricked/bootlooping? Because the OS never loads for Magisk to grant superuser access...right?
[Magisk] makeyourself:
That isn't Alpha that you're using it's Kitsune. See here: https://xdaforums.com/t/banking-app-starling-detecting-magisk.4576421/page-19#post-89235002

I don't know if the fix is in Kitsune yet or not but it's definitely in Alpha.
[Magisk] xcl1pse:
Already fix in kitsune also. Just need weishu to update resetprop in KernelSU
[Magisk] beeshyams:
Good point

Maybe if in Magisk settings if you give Su access to "apps and adb" and set automatic response to "grant" always? Risky...to grant "always"

I never tried this since safe boot always worked for me but just guessing
[Magisk] Lughnasadh:
What I meant is if you have already granted root access to adb beforehand. It's one of the first things I do when I get a phone. But I feel we're getting off topic here...
[Magisk] HipKat:
As I'm JUST finding out.... Grrrrr
[Magisk] HippoMan:
Chiteroman's latest release requires you to obtain a fingerprint file of your own and then install it as /data/adb/pif.json

Osm0sis' module requires you to obtain a fingerprint file of your own and install it as /data/adb/modules/playintegrityfix/custom.pif.json
[Magisk] akaloith:
View attachment 6048843

this is bad? what can i do for this?
[Magisk] tom1807:
On the right side of this thread, the two most liked posts have all the information necessary.

Logic tells me, if something is most liked, there must be something useful.

How many more "Golden Plates" should be handed out?

Cheers

Tom
[Magisk] majorfigjam:
It's not good if your app - eg wallet - needs device integrity.

You could try reading the most liked post, the one immediately above this one, or any one of the often mentioned guides. You will find the answer many times there.
[Magisk] V0latyle:
I personally can't as I don't have mod permissions in this section of the forum.

However, even though a moderator in this section would be able to edit the OP, we don't do this unless necessary to remove things that violate the rules. We aren't going to do someone else's job for them, and neither are we going to make them include certain information in their post besides what is required for GPL compliance for kernels.
[Magisk] akaloith:
Labels: [MEETS_BASIC_INTEGRITY]

Build fingerprint: OnePlus/OnePlus7T/OnePlus7T:12/SKQ1.211113.001/Q.202303230244:user/release-keys

Brand: OnePlus

Device: OnePlus7T

Model: HD1900

TestId: dGVzdGluZy01NjhkN2IzOS02NDMyLTQzYmQtODQzMC03NzAzNTVlOThjMjg=

If there is data that shouldnt be shown please tell me

tried also installing Play Integrity Fork (just install it)

cleaning data cache of google play, wallet, services etc

still cant use google wallet

anything left to do?

I have a oneplus 7t, latest oos12
[Magisk] HippoMan:
Could this be a motivation for us to start a new thread, perhaps?

In this hypothetical new thread, all the useful information about PIF modules, relevant utilities, locations to find build-prop collections, the necessity to find ones own fingerprints, etc., etc. could be included and/or linked in that thread's OP, along with a very prominent and hard-to-miss admonishment at the top of the OP to read that entire OP in detail before posting redundant questions.

If such a new thread comes into being, any and all redundant questions here could then be answered with the following short message:

Please read here: http://xdaforums.com/path/to/OP/of/the/new/thread/
[Magisk] V0latyle:
Nobody's gonna stop you from writing whatever guide you might want with whatever resources you want :)

We generally prefer people use existing threads instead of posting new ones but I think we can make an exception

Otherwise maybe collaborate with someone who already has a guide
[Magisk] osm0sis:
Brilliant! Thanks for the feedback! Official release posts are over in my Odds thread for any interested:

[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]

osm0sis' Odds and Ends -- Misc./Batch Tools, Flashable Zips, Scripts, etc. General Information In a nutshell, I just wanted a single thread to gather links to some of my other, larger projects, but also serve as a spot I could put some smaller...

xdaforums.com

🎅🤘:D
[Magisk] Fishawy:
@osm0sis that's your green light :D
[Magisk] osm0sis:
I'd love for someone else to put a proper FAQ together that could preface @simplepinoi177's explainer/help thread. ;)
[Magisk] Fishawy:
Well, a collab thread between @simplepinoi177 and yourself sounds like the perfect recipe lol