yashsingh1/xdaforums huggingface dataset:
[Magisk] rexsmith9886:
I converted physical sim to eSIM and getting the following error when verifying the SIM. Could anyone confirm if they can recieve OTP on Gpay India?

Google Pay can't be used on this device

Your device doesn't pass Google Pay's security checks. This may be because your device is rooted, or running an uncertified or custom OS build.

View attachment 5983161

UPDATE: installed v2.4.0-MOD_2.0 SN fix and Gpay worked
[Magisk] gpvecchi:
My two cents: all those security things are really annoying! I can accept them on a stock phone, but if I decide too root it, it's all my damn business. A disclaimer telling that I'm exposing to risks, and I'm done.

We have all the same old boring OS, all the updates are about security.

Doing this requires a certain level of competence, and I think this kind of users wouldn't click on the "enlargeyourpenis" link.
[Magisk] latamboy:
I think that it's purpose it's to protect the environment of apps and app developers. So they safer from bad practices.
[Magisk] famusc:
@chiteroman I just tested v. 7.4 on xiaomi 13 ultra with xiaomi.eu 14.0.17 and it's not stable. It passes verification only if checked 2 times in a row (first time fail, second passes if you fire it immediately, then fail again if you wait some time. The last version that always passes attestation is 7.0

I don't know if v 7.4 is meant to work that way, but I thought this could be a good feedback for increased compatibility. I'm staying on v 7.0 for now.
[Magisk] zgfg:
Did you test on Xiaomi.eu 14.0.X without PI Fix (USNF or MHCP) - only with Google Play Services in DenyList/MagiskHide/UnmountModules list and with Shamiko if Zygisk is enabled?
[Magisk] famusc:
Yup, I don't have usnf nor mhcp, and I have play services (and other google stuff) in denylist with shamiko
[Magisk] acwcanada:
If you spend sometime to read some of the messages here, I believe a lot of people have already explained that it is not achievable and in reality 99.99% you just don't it.
[Magisk] pndwal:
If you have issues with this module, I think most P7 series users are now using @Displax's USNF fork 2.4.0_mod-1.3 build as mod-2.0 has issues w/ LV A13 devices (and official 2.4.0 remains broken)... That works fine for deviceIntegrity which is all you can hope for, but may break VoWiFi due to global shipping level setting... He did say he would produce a fix for that later...

While all these modules bypass hardware-backed attestation on the device, which is needed to pass deviceIntegrity, no fix will allow strongIntegrity (unless Google surprises us with another server end vulnerability) as hardware-backed server-side evaluationType enforcement cannot be bypassed for strongIntegrity verdict; it is always required... The prop mismatch-based bypasses for hardware-backed serverside evaluationType enforcement these solutions use will only ever work for deviceIntegrity verdict... 👀 PW
[Magisk] simpleatom7:
Makes sense :¶
[Magisk] straightcore:
I'm enjoying my coffee and I have nothing to do at the moment :D
[Magisk] rogers11:
Why do I have to read this rubbish? Use private messages.
[Magisk] zgfg:
What exactly were you doing?

Trying various (not working) pif.jsons in TBChecker/PI API Checker or directly in Playstore

Or you also tested GPay with all those (not working) pif.json

Personally, I avoid mining by testing in Playstore.

And I go to use GPay only when I have PIF JSON that Device and Basic are passing
[Magisk] Graveen:
Goodbye GPay. It was usefull, but as i can't safely rely on my phone to pay, i'm forced to have my credit card with me, so it's non-sense.
[Magisk] xSnowLeopardx:
I also felt like this, but since I have a fingerprint right now, I will always try to use GWallet. A card around me is always handy, though, since it can always happen that wireless paying is broken at the machine you're trying to pay, and it accepts cards only temporarily. Have had that happen.
[Magisk] HippoMan:
Agreed. For me, using mobile-phone-based contactless payment has always been less desirable than using physical bank cards for that purpose.

It's even more undesirable now.

If for some reason I ever get forced into having to utilize mobile-phone-based contactless payment, I'll just get a cheap, used device and run it with a stock ROM and a locked bootloader, and only use it for that purpose.

But I hope I never see the day when I have to do this.
[Magisk] kolouch.petr:
yes exactly ! It is not reliable now so I will buy new phone ...
[Magisk] ipilcher:
Any idea what 2 of 2 passing in SafetyNet (but not Play Integrity) means, if anything?
[Magisk] D€INOS:
This solution of custom fingerprint was good until those users started to abuse it. So this won't probably work by the end of next week.
[Magisk] mrasko:
Hi, long time lurker, first time poster here, i've used this forum when i had issues and i always found solutions here to my problems... until now.

So i have a FP from a relatively lesser known device that i'd like to set up on a F150 Raptor phone, the issue i'm having is that i don't even pass BASIC when i don't have USNF installed which is what i've used in the past. I've removed all modules and just installed PIF v14, i can't get BASIC to pass which as far as i understand is a prerequisite to passing the DEVICE_INTEGRITY...

When i used v13.8 i'm passing BASIC but not DEVICE, however when i switch to v14 i can't pass even BASIC when i set up the FP.

The FP i got is from the only appropriate device i have around which is updated to API 27 the initial was 24 on the phone, build is from end of 2018.

Was something removed in v14 or would a banned / bad FP cause the BASIC to fail too?
[Magisk] xSnowLeopardx:
Start looking for other FP devices online.
[Magisk] mrasko:
Ok but is it the FP for sure? coz I've seen some commenting that BASIC should be passing and DEVICE failing when there is and issue with the FP.

I'll try to get another FP.
[Magisk] HippoMan:
I have found that FP's from many older devices (using Android 5, Android 6, and Android 7) will not even yield BASIC integrity.
[Magisk] xSnowLeopardx:
Same here, yeah. I really gotta hit 8.0 - 8.1 for it to work. (never tried 9 to be honest).
[Magisk] Mthw:
Even newer are not entirely hopeless, mine right now is 10.
[Magisk] xSnowLeopardx:
Good to know, thanks!
[Magisk] arda99:
Older ones may have a better chance, there're newer working fps from devices released with A9/A10, found several working A11's, that said, I haven't found any A12 or any FP after 2022 working.
[Magisk] User_15357:
Why does the same fingerprint work on my friend's phone but not on my phones?

I tried 30 pieces and none of them worked. They also sent me 100% working prints - and they also did not fit my two phones.

After replacing pif.json, I reboot the phone, and then check it through GPlay and TB Checker.

View attachment 6039929

Also, I tried to leave only PIFv14 of the modules - to no avail..
[Magisk] xSnowLeopardx:
Do they also use the resetprop like you? I am currently not, for example.
[Magisk] gerard_f:
Maybe you're right and it's gsf instead of gps, I don't remember. But anyway, I'm patient, so I can wait for the cache gets expired
[Magisk] User_15357:
I tried both resetprop and without resetprop - the result is the same :(
[Magisk] xSnowLeopardx:
I do know that when I use PF, and click on a button (after changing jsons) Save and continue, that step will kill the gms process so that I don't have to reboot. Obviously you are rebooting so that would be the same.

Have you tried using PF? It really does help with the total time of trying new ones out.
[Magisk] Gilg@mesh:
well I had nothing to do atm but I could still use Wallet/Pay even though I only met Basic Integrity, I sat down for about 30 min and got Device Integrity back, I noticed before I could not download Netflix (I don't use it anyway) but now my phone meets device and it says it's certified but can't still download Netflix, what else do I need to clear to get it working?
[Magisk] xSnowLeopardx:
Not sure, but I'd put Netflix in the deny list, clear cache + data on more time, also for Play Store and GPS.

Then try it again. Like I said, not sure. I also rarely use it.
[Magisk] Gilg@mesh:
I don't have Netflix installed, wanted to only see if I could download it, but says this app don't work on your device. :)

edit: now it works! cleared data/cache for GPS. :)
[Magisk] AlesiBoss:
not every phone works, if you did everything as you should, then this phone fingerprint doesnt work.
[Magisk] frank93:
forgive me if this has been answered before, but i actually couldn’t find it -- what’s the exact different between the "normal" and the resetprop -versions (of chiteroman’s module)? also: this, and the osm0sis-fork? i mean i read what’s written on the github release pages, but that still sounds vague. what does osm0sis’ fork do differently (better?) compared to the other two, and which one is the "preferred" (best practice currently) to use with a working fingerprint?

thanks in advance!
[Magisk] xSnowLeopardx:
Good question. I am not using the fork but everything's ok so far hehe.
[Magisk] Graveen:
Yes i'll look at what happens with custom FP, and certainly give a try, but since 1 months and update i feel like i'm trying to catch the running rabbit and experienced the "oops sorry my phone not working :p" too often.

I guess after xmas i should have enough motivation to take a look at custom FP, as every geek would :D

(and i won't relock BL because root is very interesting for me)
[Magisk] xSnowLeopardx:
Yes, definitely agree with you. Curious where we will all stand around/after xmas.
[Magisk] HippoMan:
I'm thinking that my own Christmas present to myself might be to get an old, used device, run it with stock and locked bootloader, and use it only for contactless payments if I am ever forced to use that instead of a physical debit or credit card.

... or maybe an old, used, cheap iPhone for that same purpose.

... or maybe an old, cheap, not very smart smartwatch that I would *only* use for telling time and the very rare, occasional contactless payments that I might ever be forced to make using a device.
[Magisk] arda99:
resetprop is a magisk buitlin utility to change props.

However as changes made by vanilla resetprop is detectable some made a modified version, but may cause compatibility issue.
[Magisk] yickhcr:
Does this mean I am good?

View attachment 6039956
[Magisk] xSnowLeopardx:
I mean, a smartwatch sounds like a better thing. You would be able to tell time quickly and you don't really need a second phone for anything else than what you described. With the smartwatch you can tell time quicker and it's very close to you. Also cheaper, if you go for a 2nd hand one.
[Magisk] matrix200200:
Yeah I was trying (on another phone) to add the card with all those.

Anyway, it seems to be a credit company issue, because my other (bank issued card) passed with flying colors.

So for now Wallet is working for me again (as stated by other users, after having found a "lucky", "lesser known" vendor.
[Magisk] mrasko:
Ok thanks for confirming :)
[Magisk] chiteroman:
Released v14.1 on GitHub !

Release v14.1 · chiteroman/PlayIntegrityFix

If you don't want to use your custom props to spoof, remove the file. On terminal as root: rm -f /data/adb/pif.json I will try to update the fingerprint when Google bans it. Instead reinstalling th...

github.com
[Magisk] LaboDJ:
Hi @chiteroman

I saw that you just realeased 14.1 with another FP and the option to update them without the need to flash an updated version...

I'm thinking that this way google will ban every working FP used by the module, eroding the pool of working FPs
[Magisk] 5star02707:
Lemme try this cause Wallet isn't working
[Magisk] OneGuyFrench:
How to 🖕 google.

1. Install https://github.com/Magisk-Modules-Repo/MagiskHidePropsConf/releases/tag/v6.1.2 and reboot.

2. Turn off wifi and enable air plane mode.

3. Go to magisk and put Google Play in the deny list (be sure to expand and select all sub-process of Google Play).

4. Force Stop Google Play and delete data/cache.

5. Assuming you have 'termux' installed "su" then "props".

6. Choose 1 and enter, choose a certified fingerprint from google like Google Pixel 6 pro.

7. Reboot and Enjoy

View attachment 6039959

They dont seem to care about the device model/brand, only the Build fingerprint string matter,

If they keep being retarded then the best idea is to create an official Android Virtual Device with play store from Android Studio, guess that google cant ban their official fingerprints or developers wont be able to use the play store Lol.
[Magisk] Gilg@mesh:
what's the difference between normal and resetprop.
[Magisk] magaedy:
Still not pass device integrity , MIUI 14 STOCK rooted android 12
[Magisk] Lada333:
afaik resetprop may work on certain devices on which the regular one does not.
[Magisk] pxlkeshi:
You're an absolute legend, thank you
[Magisk] Bonoboo:
Thanks. Just curious (as logic into binary?): how long will it take between FP ban and new FP on devices? E.g. how often module checks for update?
[Magisk] AC130PL:
13.8 got banned pretty fast haha
[Magisk] xSnowLeopardx:
Thanks for the continuous updates man. Will sit this one out and keep using my custom fingerprint(s) as long as I can. Will also keep updating everyone here if something happens to them. Thanks once again.
[Magisk] HippoMan:
Yes, that makes sense. I guess it's getting to be the time for me to investigate used, not-very-smart smart watches.
[Magisk] rseiler:
What's the equivalent of

killall com.google.android.gms.unstable

in the GUI?

Force stop on Google Play services?
[Magisk] xSnowLeopardx:
Should not even be expensive. I think you should be good to go with a price of 20-50 EUR/USD. Like a used Samsung Gear S3 Frontier.
[Magisk] xSnowLeopardx:
Rebooting does that + Using when using PixelFlash: Edit -> Save and Continue.
[Magisk] zgfg:
It's been answered but buried under this pile of posts

Module has service.sh to redefine check and if 'needed' redefine globally couple of props

If it has to redefine them, in the 'normal' version it uses the Magisk built-in

resetprop

The 'resetprop' version uses instead Husky's (author of Magisk Delta/Kitsune):

resetprop -n

Difference is not (only) in "-n" or not but in the fact that 'resetprop' build does not use Magisk built-in resetprop but instead a custom resetprop binary packed into the module and developed by Husky

Husky said that in some cases banking apps detect Zygisk if you use Magisk built-in resetprop, but not if using his

However, you most likely have Shamiko installed. Shamiko also has service.sh and if it needs to redefine props, it does by calling the Magisk built-in resetprop

Hence, IMO, in that case banking apps would still detect Zygisk BCS the Magisk built-in resetprop been called from Shamiko service.sh

Ie, I don't see a use of forcing Husky's custom resetprop in PIF, as long as you also have Shamiko using the Magisk built-in resetprop

IMO, it would make sense only for Delta users since they generally don't need Shamiko

----

Besides (but that was an earlier version of his custom resetprop utility), I showed here an example how using his resetprop immediately caused TB Checkers, SCheck and Oprek detector to report finding su, while without using his custom resetprop I had everything green/passing fir all three detectors

However, I saw later that his custom resetprop was improved/fixed for something but I never retested as above

Your mileage may very. I never use PIF with that custom resetprop

And when there was no option to choose PIF without the custom resetprop, I had removed that custom resetprop from my installed PIF and simply modified the service.sh to use Magisk built-in resetprop (like Shamiko does)

---

With all the respect to Husky and his custom Magisk Delta project
[Magisk] Tamsta_T:
Is it possible to disable or block those checks (eg trough hosts or firewall), so google wouldn't be able to disable wallet functionality?
[Magisk] magaedy:
Thank you very much man,V14.1 resetprop version worked for me
[Magisk] rseiler:
Yes, but I'm thinking of it more in terms of 14.1 going forward, say, when he needs to update the sig. A way to do it on the go, like maybe by force stopping Google Play services or whatever.
[Magisk] HippoMan:
Just out of technical curiosity, can the Googlefrinchians actually find out which Magisk module happens to be serving up the pif.json file?
[Magisk] xSnowLeopardx:
I think using the Terminal is the way to go then... I don't know how else.
[Magisk] xSnowLeopardx:
Also: successfully got an A10 one working. Would I be pushing it to try an A11 one haha?
[Magisk] frank93:
ok, makes sense (at least a bit, as i can only hope to understand most of this, not being a developer). :) still, i’m not using shamiko (but root through magisk stable, zygisk, etc) and i’m so far quite happy with the resetprop-version, so i think i’ll keep using that one.

thanks a lot!
[Magisk] miho171:
With the 14.1 update my miui 13 pass the device integrity check again, thank you.
[Magisk] straightcore:
Will it survive at least one day?

Who will take care of placing the bets? :-)
[Magisk] frank93:
so do i get this right, these releasenotes (from 14.1) mean the fingerprint that’s supposed to work is maintained "on a server" (by chiteroman) from now on? that’s .. ballsy, i’d say.
[Magisk] TKruzze:
The question I would have if I were using this updated 14.1 version (which I'm not) is: "Is the module now making an internet connection and phoning home on its own?".
[Magisk] Bonoboo:
According to commit, module now shipped with curl binary, so yes, it can download data (new FP).
[Magisk] Umgak:
You guys are going to get so many props banned. I just hope you leave mine alone.
[Magisk] DivintyQQ:
Don't really like this, as it will probably get a lot of prints banned, thus making it even harder to find a working one. I have a few working prints on hand, hopefully you won't get to these too quickly.
[Magisk] User_15357:
Xiaomi 12s ultra (eu 14.0.23.10.15.DEV) and Xiaomi mix fold 3 (EliteRomLite 14.1.10) - Basic integrity 😭

I think Google is testing its new feature on us and it's working out well. I hope that smart people will still defeat this monster :)

Perhaps I’ll stop here and set up my watch for payment via Mi Pay (I hope it works). End.
[Magisk] xcl1pse:
One day is passable, the new one in latest version already pass 3 days :)
[Magisk] crok.bic:
Hmm.. why a separate curl binary is used when the Magisk build-in busybox has wget applet for a long time? Only because of KSU compatibility?
[Magisk] frank93:
so pif.json is hosted on github now, with access for chiteroman (i suppose). while i get how this may be easier for users who just want to install something and have a fix, .. how exactly is this supposed to be "stable" in the long run? (and by "long" i mean more than a few days.) i’m seriously wondering where the "improvement" is here for the community.

(but i feel this may be a rhetorical question already ..)
[Magisk] crok.bic:
Assuming a pif.json file is already there and you don't have access to GitHub you probably don't have access to Google servers neither - so doesn't really matter?
[Magisk] crok.bic:
I guess they can make a rota with scripts so the online GitHub pif.json can change in every min, hour, day, whatever.
[Magisk] frank93:
okay, that would make sense i guess. like crowdsourcing the "fingerprint sources" there.

still, i feel it’s just escalating the cat-and-mouse-thing .. :/
[Magisk] justDave:
^^^ this!

If this if this goes on much longer, I'll just stick a credit card sleeve on the back of my phone. It's actually even easier to use than Google Wallet - I wouldn't have to unlock.

Is Google bored again and getting ready to abandon Wallet?
[Magisk] maxmax0:
Or maybe there are other options you may want to look into, like nfc wearables you can use to pay. I'm currently looking into those, see:

Android NFC Payment Options & NFC Wearables (without Wallet/Pay)

Hi all! G is currently cracking down on Wallet users utilizing rooted/modded phones. A huge number people are currently having major issues getting wallet to work, and the outlook is quite negative right now, I fully expect to lose my wallet...

xdaforums.com
[Magisk] xSnowLeopardx:
Sure, your approach is very good as well, but I use GWallet to have more than 1 card in there. Using a physical card attached to your back of your phone grants you 1 card, really.
[Magisk] makeyourself:
Whilst I appreciate Chiteroman's work, I'm not sure I see the point in this latest update. Firstly it doesn't actually seem to work for me (I've deleted /data/adb/pif.json as per release notes). If Chiteroman is using the same fingerprint as they pinned in the Telegram group yesterday then I suspect that it's already "banned". It wasn't working for me yesterday either.

But also if the idea is to update the fingerprint remotely ASAP after Google ban it then it's still going to provide a pretty unreliable GPay experience. If there's a significant chance that payment will fail I'm going to have to take my wallet out with me just in case, which rather defeats the object. And not only will it be unreliable, it will also get lots of fingerprints "banned" as stated above.

What I'm interested in is how Google can allegedly "ban" a fingerprint when the exact same fingerprint still works for somebody using a genuine device with locked bootloader. I mean if it were that simple for Google to ban all spoofed prints and still have them work on every genuine device then why wouldn't they just ban all spoofed fingerprints right now??? More likely they are having to manually look at each individual device's props (other than the ones being spoofed in pif.json and service.sh). And then use some of those to work out if the fingerprint is spoofed or genuine. These props may be vendor-wide, but they aren't universal. Or that's my theory anyway!
[Magisk] BrimoFan123:
If there is no ro.product.first_api_level property in build.pro then what to do?

A) "FIRST_API_LEVEL": "null"

or

B) "FIRST_API_LEVEL": ""

or

C) just to omit this line in pif.json?
[Magisk] xSnowLeopardx:
I always do B -> with no API level, leave it open with the "". I think C is also viable, not sure?
[Magisk] Fishawy:
I can't help but smile at the irony of this.

Big G, a multi-billion dollar empire, versus a few individuals such as @chiteroman with the great mod, @osm0sis with the great guide, and @badabing2003 with the great tool. A David vs. Goliath thing. And here we are, still alive and kicking.

Can't thank you enough guys. People like you are the reason why this 13 years old XDA membership is still fruitful.
[Magisk] arda99:
For newer FPs(A8+?), google can force them to go through hardware attestation, and fail these with only basic, just like majority of FPs(as in your new samsung/pixel/xiaomi etc.), which works in real device and never for spoofing.

For older FPs I have no idea, but maybe it's too old to have any real users around, and/or the real users don't use PI at all, or it's too old and G doesn't care.

And no, while I don't know how google detects spoofed FPs, I'm quite sure G doesn't crosschecking spoofed and real props.
[Magisk] Ex novo:
Just write null but without quotes (without " "). At least for me it worked that way.
[Magisk] arda99:
set it to match your FPs android version, or 1-2 lower. It really doesn't matter much, it's mostly for devices launched with A13+.
[Magisk] maxmax0:
Agreed. This will just burn up fingerprints, in the end nobody will be able to use wallet at all.

Right now it's at least working for those willing to invest some time to find their own print.
[Magisk] rom-g:
- A) is not a null value.

- B) should be Ok

- I prefer this one :" FIRST_API_LEVEL": Null