yashsingh1/xdaforums huggingface dataset:
[Magisk] BrimoFan123:
Install Termux on your rooted phone, launch it and run su command, then Magisk will ask if you want grant Termux root and for how long. Answer yes for "Forever" or choose how many hours.
[Magisk] purgy:
From command prompt on your PC run "adb shell", then "su", then accept the root request in magisk
[Magisk] zgfg:
Termux is an app on the phone, not adb shell

For Superuser access for adb, test:

adb shell su

And ADB must be granted SU in Magisk app Settings as on the screenshots
[Magisk] frasca61:
OK !!!
[Magisk] frasca61:
thank you all !!! This is my first step, I will definitely still need your help ..

THANK YOU !!!!!
[Magisk] rodken:
Incidentally, what steps did you mitigate besides deleting data for Play Store, GPS and following the guide from @osm0sis after applying your FP?
[Magisk] mike.s:
That was almost 6 months ago. :rolleyes:
[Magisk] xSnowLeopardx:
Off topic: I don't think you used mitigate correctly there, oh well.

On topic: after applying a FP, you can choose to do nothing. If your app, let's saying GWallet, is misbehaving, then you can delete its cache (data if you are impatient like me), PS cache + data, and GPS cache + manage, delete everything.

Reason why I said do nothing in the beginning, is that you can see the results (= FP working or not) after a reboot or killing gms (with PixelFlasher, for example). But, if you want to check if an app is working properly, then you have to do what I said in the beginning.
[Magisk] rom-g:
Github show me a v14.2 updated an hour ago...

Releases · chiteroman/PlayIntegrityFix

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

github.com

I'm a bit lost with the versioning here.
[Magisk] makeyourself:
Well obviously the fact that there have been zero reported security breaches as a consequence of many many people using rooted phones for contactless payments and banking apps for many years demonstrates that the risk is absolutely minimal. Far more minimal than carrying a physical card around which has far less security protections than a rooted phone. Yet that is ironically what Google and the banks are trying to force rooted users to do!

I see why you think it is an understandable strategy and you're entitled to that view of course. But it seems to me to be more based on ignorant preconceptions about the actual risk level that rooted devices pose and the fact that the number of users affected is small in relative terms, so they don't really care anyway. From Google's point of view if they are successful then it is also going to lead to a sizeable decrease in custom ROM usage, which is not a fair practice in my view. Google also care even less because they have a near-monopoly on Android contactless payments.
[Magisk] frasca61:
For now I have not taken anything good

Many "Build.prop" that I found do not contain the "First_api_level" field ... what can I write ??
[Magisk] Vision:
@chiteroman Why v14 Outdated ? :unsure:

View attachment 6041279
[Magisk] rodken:
You are correct, which is what happens when multi-tasking at work while responding to hoards of emails.
[Magisk] beeshyams:
To all those struggling to get a custom PIF - I was like you, read the guides and excellent tips given by others in this thread and keep at it. I collected a dozen working prints ( Incidentally, in India we don't have Google wallet and GPay works fine with basic certification and so do the bank apps I use. These prints are an insurance if stricter controls are enforced)

Bottom line- perseverance pays , informed perseverance pays faster
[Magisk] osm0sis:
First API is in vendor build.prop. If the device doesn't have it in there, or no vendor partition, then it's a very old ROM indeed. I've checked later ROMs (Android 8+) from the same device to get the correct First API value, but you can also try the Version SDK prop value instead. First API is a tricky value anyway, and sometimes only passes when lower or higher than the actual correct one, so experiment with it.
[Magisk] PatrickJK:
If it's not in the build.prop from the system folder, check the one in the vendor folder. That prop is sometimes only in the vendor build.prop, but some older roms don't have it at all.
[Magisk] zgfg:
IMO, concerns are mainly due to ThreeD Security v2 (3DS2):

What is 3DS2 (3D Secure 2.0)?

3D Secure 2.0 is an authentication protocol that aims to reduce fraud and enhance security for online card payments.

www.emerchantpay.com

Supported (and mandated) by major card brands like Visa, MC, AmEx, Discover, etc

Payments approved by 3DS2 can be Frictionless (low risk) or Challenge (high risk), determined by Risk Based Assessments (RBA) and Transaction Based Analysis (TRA)

Frictionless are always preferred by customers, and hence by merchants (specially, in 3DS1, Challenge type authenticated payments were pain in the ass, causing that customers often aborted the purchase)

However, in case of fraudulent type disputes for payments approved by 3DS2, chargback liability is shifted from merchants to card issuer (regulations may depend on the countries, card brands and issuers, etc).

Hence, that's the push from financial institutions, and specially for the Mobile and Frictionless payments:

Native Mobile Authentication with mobile SDK

An introduction to 3D Secure 2 native mobile integration, and how it can be natively integrated into merchants' apps. This leads to users being less suspicous about the authentication process, and as a result, drastically decreases cart abandonment.

3dsecure2.com

Frictionless Authentication with 3D Secure 2

An introduction to the 3D Secure 2 frictionless flow, its benefits, and how it can provide online shoppers a seamless checkout experience.

3dsecure2.com

where the RBA is based, among others, also on Device information
[Magisk] Iridule:
Got my custom fp... Thanks @chiteroman for the PIF module @osm0sis for the tips and thanks @badabing2003 for PF (made the process much faster) Took me about an hour to get a working print. If I am correct it would be best to try to find a device that is upgradeable so you can have multiple prints?
[Magisk] latamboy:
For me everything working well

View attachment 6041294
[Magisk] chiteroman:
Few users reported me an issue with that version on Telegram group, so I updated it.
[Magisk] Iridule:
Passing strong with custom fp? Is it worth it to hunt for one that passes all 3?
[Magisk] Claus….:
What is your channel on telegram?
[Magisk] intel_core_i7:
A joke, definitely.

Here's mine :ROFLMAO:

View attachment 6041296
[Magisk] chiteroman:
Definitely locked bootloader. Don't waste your time.
[Magisk] zgfg:
OP Post #1 -> GitHub -> TG
[Magisk] tinhsoftware:
I have couple of android phones that i want to inject the print, anyone know instructions to inject the print and build to .zip file to flash in Magisk? Thank you
[Magisk] Lord Sithek:
Isn't that you found some prints from devices with broken TEE? 😏 Maybe you just don't want people to search for them and burn them out 😂
[Magisk] fede2782:
Are you really unlocked?
[Magisk] Umgak:
Better to just use the fork or dev version. Then you can put the print in the config file instead of fully recompiling.
[Magisk] Iridule:
@badabing2003 am I doing something wrong with PF? I tried to verify the sha256 .exe and they don't checkout. Avira Notified me of a warning for virus, virus total gave some results as well.

VirusTotal

VirusTotal

www.virustotal.com

View attachment 6041305
[Magisk] Isbra:
Guys i'm running stock rom with magisk and unlocked bootloader. A while ago, like as for most of you, gpay stoppd working. Today i installed playintegrityfix module cleared app data and everything as it should be done but it still doesn't work. i meet both basic and device integrity and that's the strange thing for me. What do you think i should do? I also have denylist with all google apps & services
[Magisk] JpegXguy:
Did you clear data on Wallet? That's not it. You need to clear data of Play Services
[Magisk] Umgak:
You hashed the hash. The hash isn't the same file contents as the file itself, so the hash's hash isn't the same as the program's hash.

Or, to be less confusing: the .sha256 file is just text. It should contain the text

SHA256 hash of dist/PixelFlasher.exe:
7bbfe1a25a4badc645afa84bc8ecc655373742659fdbec572d73206e7e536642
CertUtil: -hashfile command completed successfully.
[Magisk] Isbra:
i cleared data + cache on wallet, and play and only cache on google play services as i didnt understand if by clearing data on google play services i will need to insert my account again. i obviously rebooted. i do not post the picture as it is in italian, but it says "are you sure to clear all data? your account, settings database will be deleted"
[Magisk] VitorMSA:
The same thing happened to me. The only way I managed to get everything working again was to remove root and uninstall magisk. I kept the bootloader unlocked to test new solutions in the future
[Magisk] JpegXguy:
Also this reply by @Nodens is so spot on that I made a bookmark of it

🔧 [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] maxmax0:
For the banks/regulators, it is more a risk management exercise. You ask yourself "what could happen", and "what are my attack vectors". You are right that there have probably not been any huge fraud cases with rooted phones, at least I am not aware of any, but this is not necessarily a huge factor in the calculation. Also don't forget that the EU PSD2 with SCA requirement is quite strict, would be a disaster for G to lose SCA with wallet, so I understand why they are nervous.

I think it's a situation where you simply cannot please everyone. And if you were the Product Manager who has to chose between 3.6 billion Android users and securing a huge transaction volume vs. a couple of guys who like to root their phone and an unknown risk of possible financial/reputation/litigation risk, wouldn't you do the same?

Also don't forget that you can still use a completely Google-free Android, fork and modify the source, install alternate markets, flash custom ROMs, root your phone etc., but you also have to accept the consequences that some companies will chose not to service/support you. The freedom level we have vs. Apple is still mind blowing.

Finally I agree with you about the contactless payment monopoly, I think it would be nice if there were other universal apps that could do that (the API is there, so anyone can develop this), however, I believe that these apps would face the same restrictions/crackdown on modified devices. My bank offers contactless payments via a native app for the cards I have from them, but the app is also a huge pain to get running when rooted.
[Magisk] Iridule:
Silly me I should have realized that, didn;t sleep well last night. It checks out now , Thanks :D
[Magisk] Isbra:
it feels like google is really having that ****ty what is mine is mine behaviour. i would start pulling my card out of my pocket rather than uninstalling magisk...
[Magisk] Vision:
Is totally safe clean the data of Goole Play Services (GMS) not deleted the Google account from your phone
[Magisk] JpegXguy:
Yeah you need to clear Play Services data not cache

I was also scared of the message but it doesn't delete your accounts. It just makes it so you have to input the cards' CVV again
[Magisk] sawdoctor:
You don't need wallet etc on deny list if you are passing device and basic integrity's then you just need to wait for wallet/Google play services to update Thier cache
[Magisk] VitorMSA:
In my case, I don't use magisk and root privileges for almost anything. Other apps that aren't related to banking don't open either because they detect security changes, even though I've "hidden" them in magisk...
[Magisk] badabing2003:
This is from the OP of PF
[Magisk] Isbra:
ok thanks everyone. i inserted my card and now it seems like it's working. the thing here @VitorMSA is what i'm also kinda of reading in these messages, like a lot of apps that i didn't expect to find root are now finding it. and i'm not talking about bank apps. luckily mine is working by hiding magisk.... but here in italy we have postal services managing our "digital identity" to access national services and i had to hide everything. but also stupid apps do this
[Magisk] Nodens:
There are some very old devices, like the one who's fp I'm using currently, without separate vendor partition (vendor is part of the system image directory tree), that have first_api prop in system build.prop and no build.prop at all in /vendor.
[Magisk] Nodens:
It is very easy. Open the zip with 7zip, drag and drop the json file in the window (in the path that the existing one is) to overwrite the existing.
[Magisk] Iridule:
Wallet will be moving to its own app soon from what I understand bit won't use Google Play services?
[Magisk] osm0sis:
I'll update my script for this, good to know!
[Magisk] HippoMan:
I would only do it if I also put lots more controls on the use of plastic debit/credit cards, which are just as easy to steal and commit fraud with as are rooted Android phones ... and those plastic cards are much, much, much more prevalent than Android devices ... rooted and non-rooted.

In other words, screwing over a relatively small number of rooted Android users for using a mechansim that is equally unsafe as plastic bank cards is not addressing the larger plastic bank-card security problem at all ... which means I would be failing at the security-related aspects of my job by not addressing bank-card security in the same way as rooted Android security.

SInce there are many fewer rooted Android users than plastic bank-card users, the customer outcry by only restricting rooted Android users is much lower than the flood of outrage that would result if equally onerous restrictions were put on the use of plastic bank cards. So ignoring the bigger bank-card security problems is simply taking the easy, cowardly way out.
[Magisk] JpegXguy:
I encountered this and in order to get your script to work I symlinked vendor-build.prop to build.prop

Awesome script btw
[Magisk] Nodens:
There was a person posting in the thread a few days back that they have a relative with a device that uses a banned print and validating properly.

Since I don't remember who it is and I can't find the post on search, if you see this, please PM me which device it is, what android build it is running exactly and what other magisk/ksu/lsposed modules it is running (if any).

Thanks in advance.
[Magisk] osm0sis:
Classy things happening and being said in the TG right now, everybody... 😯
[Magisk] xxlakis:
Hi guys. Is it possible with unlocked bootloader and custom rom but unrooted to have only Gpay failing but everything else working fine? I was on Magisk but I un-installed it for Gpay but no luck.
[Magisk] Nodens:
Unlocked bootloader is automatic fail when without magisk and spoofing module. It doesn't matter if rooted or not.
[Magisk] ArzZenic:
What's going on in there? :D
[Magisk] HippoMan:
This same thing was done in TG a few days ago: delete the previous group of thousands of messages, close the group for posting, and print the long, explanatory message like the one that is showing there now.

And then, a day or so later, the TG group was re-opened, and the same kind of message flood returned.

I wonder how long posting will remain blocked this time.
[Magisk] osm0sis:
Did he say "I will keep burning fingerprints because that's how I want it" a few days ago? And call everyone who disagrees "f***ing p***ies" ? 😶
[Magisk] sawdoctor:
But everyone in the group has root so all have the ability to enable anti delete. So deleting messages from a group of rooted users makes zero sense
[Magisk] D€INOS:
Pretty much.

I would have hoped for , update with a new fingerprint only when testing a new idea of solving the issue. Otherwise is it just being a part of the problem and not the solution.
[Magisk] sawdoctor:
At the very least couldn't all the parties burning fingerprints agree to burn the same ones and agree a maximum they'll burn? In all fairness to chiteroman he isn't the only one burning fingerprints.

What peeves me off is he gives everyone the ability to use thier own prints, you and badabing make it super simple to find and process prints and the vast majority of users that aren't using their own prints really don't deserve to be gifted them. Yes i know some people have found it difficult but i wager the majority are just lazy
[Magisk] titomax82:
Not completely. For example it destroys Wear OS asssociation
[Magisk] zgfg:
He is just rebasing the TG chat from time to time
[Magisk] titomax82:
This is one of the factors that made me surrender. You have to be expert about devices: year, codename different respect commerciale name, OS version, different position of build.prop, sometimes more than one and you need a piece from one and another piece from another again and so on.

Things are easy for people who have daily experience with these aspect through the years.

To follow guide's instructions is easy. They clear, it's difficult to make mistakes, but they leave you alone to build your own experience that require's lot of time through a long period and this is what experts forget!
[Magisk] Vision:
Sorry for the misunderstanding, i mean safe, after clean, the google account that exists in the device not deleted, i don't say anything about other stufff (like Wear OS asssociation you mention) 🤣
[Magisk] Whyherro1:
Hey all, first post here. But I've been following everything.

I'm a little confused as of what's going on I've updated to 14.2 but haven't bothered to use a custom fingerprint yet. The past week wallet has been saying I haven't met the security requirements but today everything is seemingly working? I even tested with a payment in store everything is working?
[Magisk] sawdoctor:
I found it difficult at first but this is a community built by people who want to help each other. If you reach out there's plenty of us who will help by pm with the right places to look for build props and how to easily find codenames etc and how to use tools like PF to process build props.

Anyone who actually wants help to do it themselves will quickly find lots of people offering the help, never be scared of asking for help on XDA
[Magisk] Nergal di Cuthah:
14.2 has its own builtin fp
[Magisk] Kingcool88:
No he didn't. Read it again.

Stop feeding the trolls and make things up.
[Magisk] Iridule:
@badabing2003 will PF work on linux mint 21.2? I had tried but it closes shortly after the donation notification shows up.
[Magisk] V0latyle:
I beg to differ...

View attachment 6041352
[Magisk] osm0sis:
By the way, I can safely say that any instance I've investigated of a user saying a json worked on chit's versions that didn't on mine was due to some level of user error or confusion.

1) "" for FIRST_API_LEVEL value

2) Incorrect PRODUCT value

3) Probable banned print

For 1 & 2 I was able to get their print working by fixing their error, and for all presumably it only worked on chit's just because of some fallback to hardcoded print/values, which my fork doesn't do (and I don't believe it should).

Note: Blank FIRST_API will just use your system's, so depending on your real device and donor print you could fail or pass. That's why I think FIRST_API is mandatory to include now.

Edit

: Another user's worked fine for me with no changes, so it was just an issue of them not using the correct /data/adb/modules/playintegrityfix/custom.pif.json path for my fork.
[Magisk] majorfigjam:
Thanks. I was thinking about posting something similar, but as I'm not a mod, I would likely have been banned!
[Magisk] V0latyle:
I'm not posting this because I'm a mod. I'm posting this because I think transparency is important, and I don't particularly appreciate one of our distinguished developers being called a liar.

In most situations though, we would definitely prefer whatever conflict is on Telegram, to stay on Telegram. Don't bring that here. @chiteroman can run his TG channel/group/thingie (I'm 36 what is this) however he wants, and as the developer of this project we've afforded him the privilege of posting his TG link in the OP in keeping with the Telegram Policy.

If you're wondering what you actually could get in trouble for, read the Forum Rules, because that's what we operate by. We don't play favorites or petty games here on XDA and you won't get in trouble if you aren't doing anything wrong.
[Magisk] HippoMan:
... and keeping it blocked for a while, until he changes his mind again.
[Magisk] wfred:
He likes to remove older versions when he launches a new one
[Magisk] maxmax0:
Right, I catch your drift, but don't forget that Google Wallet gives you a lot more freedom than your plastic card, because it can fulfill PSD2 SCA, which your card cannot, see here:

🔧 [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] chiteroman:
Yes, sorry about that message, I was very angry about something that is best forgotten.... I've put a vote on the Telegram group about the future of this module. I don't know whether to do the poll here as well.
[Magisk] majorfigjam:
It was the blanked out sweary bits that concerned me about posting! I'm a native speaker of anglo-saxon profanity, and not in the least concerned if others are equally fluent.

However, other eg mods may take a different view, as we have seen earlier in this very thread with entire posts being deleted.
[Magisk] sawdoctor:
May i suggest you reword the question a little so that people don't think they are saying yes to agreeing to finding thier own print. I know I'm nit picking but the clearer your message the less flack you'll get
[Magisk] maxmax0:
Obviously it's your module, you're the boss, your call - however, I truly would appreciate if you would.
[Magisk] sawdoctor:
You do understand if he does and Google keeps banning prints 3 or 4 a week in 2 months no one will be able to use his mod ever again thats it full stop gone forever. It's important people realise that when they are voting. You have to marry the hassle of finding prints yourself and how long provided ones last
[Magisk] HippoMan:
... and with a modded device, Google Wallet gives me a lot *less* freedom.

If banks detect that a transaction is coming via Google Wallet on a modded device, then all they should do is stop enforcing PSD2 SCA for that one transaction and let it go through with the same level of security as if it's coming from a plain plastic card.

But instead, the banks "punish" modded device users by blocking the transaction altogether in this case. This is simply more laziness on the part of the banks.
[Magisk] osm0sis:
I'll say it again... I'm still on my first custom prints that I found 3 weeks ago.

I would hope it's pretty obvious what people should want to do for stability, if they really think their options through... the options, honestly, are a) update a module every 1-3 days for the rest of time as the included prints continue to get burned, or b) take a single day, find a print themselves and use it for a long long time, (and hope no ROM or module uses it so that it doesn't get burned 😝).

Edit: Just realized "for the rest of time" is more accurately "until all the prints are burned" 😄