yashsingh1/xdaforums huggingface dataset:
[Magisk] FIERA03:
I saw a post on reddit once with the main message that "if you clamp down on custom ROMs with Play Integrity, you will ultimately create a lot of e-waste". I agree with this, and Google is effectively encouraging the killing of many still-living devices...(I highly doubt that all devices will be properly disposed of).

As a practical compromise solution, I believe that they should provide a Play Integrity license(for developers), tied to each account. If there are firm terms and conditions (not vague like YouTube's) and the price is not unreasonably high, I would get the license.

We will succumb to the Big G, but it is far better than having a dysfunctional device.
[Magisk] HippoMan:
Exactly!

And this is why from Day One on Android I've refused to use the device for contactless payments. I had to jump through more unnecessary hoops than the steps needed to simply use a dumb card.

And now, the number of unnecessary hoops to jump through has increased.

And regarding PC browser access to banks ...

Banks issue us Android apps which offer the same functions that are offered via PC browser access. But in many cases, these apps are deliberately crippled or non-functional on rooted Android devices, even though PC browser access is fully functional under Linux, MacOS, and Windows, all of which are rooted in the same manner as a rooted Android device.

Again, why do banks bother to make this app access under rooted Android as foolproof as possible under rooted Android, but not via browser access under rooted Linux, MacOS, and Windows?

And even worse, there is no restriction for browser access to these same banks under rooted Android. They only restrict their *apps* under rooted Android.

</rant>
[Magisk] Dark_Diver:
One can use PlayIntegrityFix DEV v1 module.

My Windows script for creating pif.json, which I posted earlier, try to extract ro.build.id & vndk.version from build.prop too.
[Magisk] BROKEN1981:
I can't pass on your fork either. It's super odd. I'm on 14.2 on the other devs . I just deleted his print and used mine. I messed up and updated to 14.2 LoL. His dev version also refuses to pass with my print.
[Magisk] Fishawy:
It's a pre-release, but yes. Please note that PlayIntegrityFix and PlayIntegrityFork require the fingerprint files to have different names and be in different paths.
[Magisk] osm0sis:
Please PM me and I bet I can figure it out. 14.2 has a hardcoded print in the source though, so no file you add is changing anything.
[Magisk] osm0sis:
I've yet to see any evidence presented that VNDK is necessary.
[Magisk] Dark_Diver:
I don't know, if it needed, you are the boss :)

props, which I use, don't have it.
[Magisk] BROKEN1981:
LoL we are the threat actor yet how many times had apps been on Play Store stealing money from bank accounts without the user even knowing it.

Or that time a father noticed a skin condition on his baby, took pictures, and did a medical call and sent the pictures to a doctor. Google banned his account over child porn. The guy lost all his pictures, paid apps, important emails.

If Google wants to talk about threat actors, they need to look in the mirror. Google so far has done the most damage to users.
[Magisk] Nergal di Cuthah:
Mostly results on how to edit build.props from when that was a thing
[Magisk] Fishawy:
You don't need to edit it. I haven't edited a single one, and that's the beauty of PixelFlasher.

Download the entire file, save it somewhere, then load/process it into PixelFlasher, and it will extract the needed json data. Copy the contents from there, click "Edit pif.json", paste, test.

Edit: I may have misunderstood you. If you're talking about the search results, they weren't difficult to find, just your normal search for build.prop dumps.
[Magisk] raulci:
You saved me. Thanks for sharing this!

I spent several hours trying to solve it, didn't understand why Shamiko and PIF were not working. Just downgraded to the version you indicated and now it works.

Again... thanks a lot, mate!!
[Magisk] Nergal di Cuthah:
Sorry i was unclear. My search engine responds with most/all results to do with "how to edit build.prop" which was a thing when system was writtable iirc.

My results in search engines have been horrible. Fingerprint got me "fingerprint reader" a build.props dump got me "how to edit your".

But your advice is solid and I'll soldier on on friday to make a pif.prop. Tomorrow for pixel update and reroot (only 25 min but still ), thursday I'm busy.
[Magisk] fbirraque:
Please correct me if missing something but did you deprecate PI 14.1-resetprop today and all extra hide features?
[Magisk] Fishawy:
I've edited my response above.

Use PixelFlasher tomorrow to reduce those 25 minutes to 4-5 (update + root) :D

Good luck with the prints.
[Magisk] Nergal di Cuthah:
No want to stay skilled with adb commands lol (otherwise might be called ignorant again rofl)
[Magisk] Fishawy:
It's interesting how on one hand we're going through this fingerprints ban war, and on the other hand Google still offers guidance on how to certify rooted devices and custom ROMs here.

So they're okay with rooting phones but Wallet is a no? It's just bizarre.
[Magisk] okotzak:
6. Uninstall Google wallet

7. Install wallet again

8. Add it to Zygisk rejection list again

9. The settings of magisk are in the attachments

This works for meView attachment 6040806
[Magisk] Fishawy:
Hello,

I'm reading on the dev's Telegram group that there are specific instructions for Xiaomi.eu ROMs, and that his generic mod won't work on them since they're now kind of encorporating the solution within the ROM. There's also an additional app floating around.

You can join the Telegram group "with the same name of this thread", then search there for Xiaomi.
[Magisk] purgy:
Well as no one reported getting their individual print axed, I thought I'd give this a go, and found a working fp on my 8th attempt, after a few rather discouraging 0/3 and 1/3s.

Many thanks to all involved.
[Magisk] BROKEN1981:
Am I the only 1 during the switch to 14.0 that did copy and paste by hand in each field? Lmfao

I've always worked harder and not smarter. I guess I would have more than (5) using PF. However, I think 5 is enough. Till the dev decides to use my print, and yes, I have that type of luck
[Magisk] asisandroid:
I really hope things like play integrity api or these ios anti jailbreak practices will be illegal one day or like regulated so you can still have admin access without apps being able to check that.

Because if windows (if you look at windows 11 it may take a similar route in a few years), android, possibly even browsers and ios take this path you will basically be excluded from the internet unless you run a stock rom which makes me worry even more if you think about all the safety regulations currently floating around like e.g. the online safety bill in uk that passed, as bypasses will be close to impossible for normal users, effectively killing privacy in combination with these.
[Magisk] Fishawy:
We all learn something new everyday. :D

Five is safe (for now, until Big G says otherwise lol).
[Magisk] BROKEN1981:
Yeah....Sad but true!

Heh, so many reboots just to check Play Store to see if I would pass. I'm just trying to figure out why I can't pass on the fork. I reached out to the dev. Hate to do that, I'm sure I am screwing up something simple.
[Magisk] purgy:
custom.pif.json vs pif.json? That messed me up initially.
[Magisk] Fishawy:
1) Zero reboots if you use PixelFlasher. Just save and test, and if it doesn't work move to the next one.

2) If you're passing on the Fix but not on the fork, then yeah something is borked. Start fresh, and keep in mind that the fork requires a different name and the file to be in a different location.
[Magisk] BROKEN1981:
Next time I'll use my PC if anything.
[Magisk] BROKEN1981:
Can you show me file system structure? I'll just copy it.
[Magisk] Umgak:
Here you go. The fork has it in a different place and with a different name.

EDIT: Also, a custom.pif.json with prop names. Just replace the values in quotes with the values from the build.prop/vendor.prop in question.

{
"PRODUCT": "ro.product.name",
"DEVICE": "ro.product.device",
"MANUFACTURER": "ro.product.manufacturer",
"BRAND": "ro.product.brand",
"MODEL": "ro.product.model",
"FINGERPRINT": "ro.system.build.fingerprint",
"SECURITY_PATCH": "ro.build.version.security_patch",
"FIRST_API_LEVEL": "ro.product.first_api_level"
}
[Magisk] BROKEN1981:
Thanks! I was waaayyyyyyy off lol
[Magisk] BROKEN1981:
Is there a guide on how to use PF with this? I googled but can't find anything.

Edit: don't bother. I'll just edit these by hand and keep rebooting to test. Just seems easier that way for me.
[Magisk] sawdoctor:
Yep those that fail all 3 and you really expected to pass really make you think your doing something wrong don't they
[Magisk] Umgak:
🔧 [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

Linked from PlayIntegrityFork's github page ;)

Haven't used PixelFlasher myself yet, though. Haven't tried enough prints to feel like it's necessary yet - first one I found isn't banned 6 days later.
[Magisk] Fishawy:
Yep, linked in my simplified guide a couple of pages back.
[Magisk] sawdoctor:
🔧 [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] awarexda:
Just for the mystery of it, I will try 1 or 2 fp today but I think then I should revert to 14.1. Correct? Because the dev version isn't that straightforward.
[Magisk] maxmax0:
Truth is they are doing this to satisfy legislation and public/NGO pressure over CSAM. When you are obliged to scan billions of messages, there will be false positives. It's not like they enjoy the negative publicity, or the users ranting over it.
[Magisk] zgfg:
Yes. I omitted package name by reasoning that if the same app is requesting PI API attestation again, that kind of info will be the same (nonce and timestamp not)

But nevertheless, here we repeatedly see ideas to 'reuse' old/passed verdicts, even being taken from another phone (in real time or from the past) with unlocked BL and unmodified firmware. It cannot work, at least the nonce will be wrong
[Magisk] titomax82:
I would like to try the custom pif way, but I'm surely unable to find that kind of files searching within roms (I've a non flat data plan also...). I tried to search build.prop files in internet, but I only find single files from unknown sources. Is there any website that has lots of build.prop file I can try?

Please PM me in someone can help me
[Magisk] zgfg:
One more burned yesterday evening on the Xiaomi.eu side
[Magisk] maxmax0:
I have seen this come up recurringly, so maybe this will give some answers/information.

If you live in any of the major markets, your dumb plastic card is severly gimped/limited in what it can do. E.g. transaction number/amount limit, requirement of physical card and PIN at random/set intervals etc.

The only way Wallet can manage not to have these limitations is to fulfill requirements of SCA (strong customer authentication). I have paid hundreds of times with Wallet, without needed the physical card. Yesterday I paid 800 € with wallet contactless - could not do this via tap & go with my physical card, would need to insert card, enter PIN etc.

Banking sector regulation is no joke. If there is misuse, and G cannot demonstrate reasonable effort to secure it's payment solution or is found negligant, there will be huge lawsuits on top of loss of trust and negative publicity. This is not a risk they will take for a couple thousand guys that like to tinker with their phones.

You can read up on SCA here:

Strong Customer Authentication explained | SCA

Get all the key information about SCA, as well as when and were it will apply.

gocardless.com

Strong Customer Authentication

www.visa.co.uk

About strong customer authentication - Google Workspace Admin Help

Make online card payments more secureThis article is for administrators in the European Economic Area (EEA). The EEA includes Austria, Belgium, Bulgaria, Czech Republic, Cyprus, Denmark, Estonia,

support.google.com
[Magisk] maxmax0:
Well maybe you should stop burning them then...
[Magisk] Lord Sithek:
I quickly lurked on the PIF Telegram group and what is happening there it's totally outrageous. Fingreprints just flying there and back, regardless they are valid or not. I think that chat should be shut down...

@chiteroman Maybe consider just keeping a channel for important posts... Btw personally I vote for not providing incorporated prints in the module, rather providing well-documented guide for harvesting each own prints
[Magisk] BROKEN1981:
Oh sure....let's just keep giving up our privacy in the name of finding "CSAM". A major white hat infiltrated a huge group just for the government to show no interest. The guy was in there and able to give the information of every single person.

Or the guy who had 59TB of child porn. Government does not care. If they did, Jeffrey Epstein's client list would have been made public and he wouldn't have been murdered for a cover up.

People are so used to not having privacy since E-ZPass became a thing in the early 90's.

Also if Google cared about false positives, the guy would have his account back. He never got it back. Even after actually getting a human. If you want your messages scanned, good for you. I do not consent.
[Magisk] Fishawy:
One fingerprint used by a couple of individuals = Most probably goes unnoticed, basically flying under the radar.

One fingerprint used by thousands of people = Attention followed by a permanent ban for the print and all its users.

It cannot be more obvious than this.

We don't have the luxury of trying and replacing indefinitely. This stock is limited, and we'll run out. Generic use of prints is killing this whole thing sooner rather than later.

And the Telegram group scene is just pure chaos. More prints getting banned at a much faster rate.

Not to mention that if the next random choice for a print happens to be the same one I - as an individual - found and used privately, and it gets banned due to a spike on Big G radar after sudden generic use, I would be furious.

@chiteroman please stop helping them with this. I've been advocating how helpful your mod is for the many users who don't have the knowledge, but right now we're just shooting ourselves in the foot.
[Magisk] BROKEN1981:
He's knows. He doesn't care so it's no use to appeal to him.

I'm tempted to give a print to a guy who was called noob on here. However, I'm waiting 3 or 4 days for him to learn it himself. I don't think he would pass it around.
[Magisk] zgfg:
LIAPP alert is not related to SN/PI, details like su in the path are not provided in JSON verdicts returned to the apps

Have you put the given 'banking' app to DenyList (and rebooted afterwards)?

If still would not help, try with installing the module as on screenshot
[Magisk] GWARslave119:
You're right on both parts. I did see the screenshot and wondered why it didn't mention the strong integrity even though I couldn't understand the rest of what it was saying ;P So I went ahead and downloaded it anyways. But yeah, I think a screenshot like what you just showed would leave almost 0 doubt as to what to expect.

Edit: Also in the modules section, the description does kinda say it as well ha...

View attachment 5985819
[Magisk] GWARslave119:
Well it's jsut a game, and oddly enough, my banking app works fine without needing to put it on the DenyList. But yeah, it's been on the list for quite some time now since I remember it first happening, I just probably gave up and uninstalled it back then ;p I'll try installing that module you showed and see if it helps.
[Magisk] GWARslave119:
Yep that fixed it. Do you know where at that this module changes? Or can I see the changes in a log somewhere?
[Magisk] chiteroman:
View attachment 5985879
[Magisk] pndwal:
FWIW, since I had this detection with Alpha I raised it in the Chinese-only Alpha discussion TG channel...

Here's the conversation w/ english translation added by my TG client (it may help, but I'm not clear on the interpretation; seems to be a known issue with Shamiko however 😜):

View attachment 5986003

View attachment 5986017

View attachment 5986015

View attachment 5986013

View attachment 5986011

... Hope it sheds some light... 😜 PW
[Magisk] Spartacus500:
For me Blind app work, Magisk 26.1 stable + HMA
[Magisk] Spartacus500:
The new version of the BM Online app detects the root, adding the application to the denylist or HMA does not help 🤷
[Magisk] gpvecchi:
I don't want to say a stupid thing, but my phone seems to overheat more with this module than the old safetynet fix...
[Magisk] chiteroman:
Yep, understable. I will try to fix in next versions.
[Magisk] chiteroman:
Update to v8.0 !

I removed all C++ STL from Zygisk libraries (also I removed x86 and x86_64 libs).

Try new version.
[Magisk] Captain_Throwback:
FYI - The update screen in the Magisk app is messed up.
[Magisk] chiteroman:
Yeah, I don't know why
[Magisk] chiteroman:
View attachment 5986499

Magisk Alpha and Magisk Delta can bypass this with MagiskHide, just disable Zygisk.
[Magisk] WhoIsJohnGalt1979:
All good here on Pixel 7 Pro with A13.
[Magisk] WhoIsJohnGalt1979:
Magisk Stable 26.1, Play Integrity Fix 8.0, Shamiko, Zygisk Enabled, HMA blacklist. Blind works fine.
[Magisk] zgfg:
Not needed to disable Zygisk.

See the posts yesterday, #541:

https://xdaforums.com/t/module-play-integrity-fix.4607985/post-88921019

and #545:

https://xdaforums.com/t/module-play-integrity-fix.4607985/post-88921409

The LIAPP alert was removed by installing HuskyDG's module:

GitHub - Magisk-Modules-Alt-Repo/sensitive_props: Reset sensitive properties to safe state, take from MagiskHide code

Reset sensitive properties to safe state, take from MagiskHide code - Magisk-Modules-Alt-Repo/sensitive_props

github.com

I guess the alert removes his oem.rc mount

Btw, there is also one interesting prop redefinition in his module, service.sh, upon the boot finishes:

resetprop -n sys.oem_unlock_allowed 0

That makes to pass root detection in SCheck - see the screenshot
[Magisk] pndwal:
... I added that to my Alpha setup when I saw those comments... Didn't fix on RN8T, A11 stock MIUI... PW
[Magisk] Ginosius:
The 8.0 update broke device integrity for me.
[Magisk] titomax82:
If you'd like to help another noob, I just need to know where to find a pool of build.prop files to test to make my own pool of fingerprints.... I tried searching, but with useless results....
[Magisk] Fishawy:
Even better, help - in DM - as much as you can, and keep your print.
[Magisk] BROKEN1981:
I did tell him where to look. Only because so many sites seems sketchy.
[Magisk] Fishawy:
We are all noobs at many things. No shame in that, and this should never be used to show off by those who know.

Search for "build.prop dumps". There will be many results, some are useless. Try focusing on those links that allow you to actually download the build.prop file for easier use.
[Magisk] BROKEN1981:
You don't have to download them. There is a file structure text. That's how I did it.

If I should delete that, let me know
[Magisk] Fishawy:
No mate, some people are using the file structure which is as good. I just download them for convenience.
[Magisk] sawdoctor:
Someone in there has created a group and asking people to join to test and share fingerprints so they can have a collection they can all share. Dumb doesn't cover it, talk about making it easy for Google, I'm sure no one at Google has a telegram account 😂
[Magisk] sawdoctor:
I'll happily help anyone by pm. I'll tell them where to look and how to create a json file and even which are the best types of firmware to look in. (I'm sure Google knows all this). But I won't provide a working fingerprint/json/buildprop
[Magisk] BROKEN1981:
Looking at the file structure let's me know pretty much immediately if it's worth trying. I guess the same could be said about downloading them. I just haven't downloaded anything yet.

At the start I was copying like crazy and they didn't work. That's how I learned what to look for. That combined with Omisio guide on API level and looking at a json. Truth is, I never looked inside of a Magisk module till 14.0.

Everything was just plug and play.

To this day, the hardest thing was rooting the T-Mobile LG V30. Runningnaked cracked that. First time I had made a bootable thumb drive , used a Linux distro. I was looking for .exe files to install on it lmfao. True noob. I learned I never want to use Linux again in my life.

I think what's frustrating people the most is finding a site to get a dump. After getting a dump, you quickly learn what to look for. Then messing with API level on the same dump because sometimes the json won't work with the listed API level. However, I had 2 files where I changed the API level and made it work.

This is my experience. To people getting frustrated, just hang in there. Take a deep breath. It seems way more complicated than it is.
[Magisk] osm0sis:
First one should be ro.product.name, which is different. Otherwise all good!

There can be some other ones to use instead in case of generic values due to GSI. My script is pretty readable for the next options to use, don't be daunted just by the fact that it's a script, just check out the prop names. 👍

[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
[Magisk] thomaskmaagaard:
My working FP - that I know is used only by two phones - just got banned. It was taken from a private device, not a public ROM and it was not shared.
[Magisk] frasca61:
this is a big problem....
[Magisk] thomaskmaagaard:
Yuuup
[Magisk] michasssxdd:
View attachment 6040849How to fix it?
[Magisk] thomaskmaagaard:
Custom FP or v13.9?
[Magisk] BROKEN1981:
Maybe many people chose the same one and were passing it around.

Many people, including myself had found our own and it's still working.
[Magisk] michasssxdd:
View attachment 6040851
[Magisk] sawdoctor:
Mine is still working just checked. There's been an update to Google wallet on the playstore yesterday, you haven't installed that have you? If it's related to that then we are screwed
[Magisk] thomaskmaagaard:
Sounds rational, but I would've thought an Asus device would be one of the less used ones😅
[Magisk] thomaskmaagaard:
Not updated. Actually haven't updated in a while.
[Magisk] Fishawy:
Did you happen to see it in the Telegram group by any chance? There's literally dozens of these being posted publicly, and it could be that someone found it online and shared it there or elsewhere.

I really hope this is the case.
[Magisk] thomaskmaagaard:
Not found online. Taken from own device. The private Asus phone is still in use, my main phone uses the Asus FP and I put the FP on my friends phone. He doesn't know how it works so he hasn't shared it. So I guess that's three (known) instances of the FP in use.