yashsingh1/xdaforums huggingface dataset:
[Magisk] maxmax0:
We all would like to have our rooted phones to work perfectly, but sometimes the views and entitlement here truly amaze me.

They are not bitter, they have legal and contractual obligations to ensure a secure and tamper-proof environment to their partners (banks). The banking sector is a highly regulated and risk-controlled environment.

For 99.999 % of the users Wallet will work great, why should they cater for the small fraction of users messing around with their phones, which will have a much higher likelyhood of things going wrong and might lead to all kind of additional problems for G.

Would be nice to have hassle-free wallet and root, but right now, this is not in the cards.
[Magisk] highdiver_2000:
and not buying new handsets.
[Magisk] wyt18:
Thanks, great to know! Using TB Checker, I'm getting often the API error -8 and -2. What does this mean?

Tried 10+ fingerprints so far but none work. Can't tell if I'm entering the info wrongly into the pif.json, or if the prints are ba**ed. Is there any way to tell the difference?
[Magisk] pndwal:
GSM shows launch Android version and stock updated versions for each device under Platform, OS... If it's launched with Android 9 for instance, First API level will be 28... Google will help you map launch Android version to SDK/API level... PW
[Magisk] HRSE:
My point is, GPay and whatever T&C have been around for many years with root, suddenly now Google makes a fuss about this.

In the beginning, it was the small group of tech savvy users that actively used GPay. Now when GPay already becomes popular, Google ditches this group of pioneers.

All the scam cases in my country are because the account holders reveal the OTP or send money to the scammer, not because of rooted phones.
[Magisk] pxlkeshi:
Hey I'm sorry this is off topic but I'm new to this, if you're free can you advise me on what to do about the safetynet fix, like how can I get a valid fingerprint to spoof etc because I have no idea
[Magisk] HippoMan:
Then why do the banks issue us totally unprotected debit and credit cards that we can use for tap-and-pay, while at the same time pushing Google to put extra tap-and-pay restrictions on modded Android devices?

As I've mentioned before, my banks issue me "VISA debit cards" which are fully functional debit cards but which don't require a PIN code when tapping.

Even modded Android devices require a PIN or other screen unlocking mechanism in order to use tap-and-pay.

In other words, my banks gladly issue their customers cards that are even *less* secure than modded Android devices.

So, I don't see any intelligent reason for these banks to put those extra restrictions on the modded Android devices.

Of course, there's no law against being stupid, so there isn't any motivation for these banks to change that policy
[Magisk] Hisucchi:
Wasn't my intention anyway, and I don't think chiteroman did with 14.0 either 😉
[Magisk] beeshyams:
Agreed. But one bank I use (Citibank India) re-directs you to a mobile app interface even using on a browser...
[Magisk] simpleatom7:
Offc it works in ksu..
[Magisk] HippoMan:
Those kinds of policies are part of the reason for why I refer to that particular bank as "Sh*ttyBank".

I feel sad for that bank's customers.
[Magisk] dedalos91:
Thanks for nice work.

With the PlayIntegrityFix_v14.0 module.

I replaced the text in the data/adb/pif.json file with informations from another old phone and rebooted (can i post this info or will Google see it?).

At the moment the exams are passing and Gpay is working normally.

How long will it last? I do not know.

(Magisk and MIUI Global_V14.0.7.0.TKFEUXM)
[Magisk] mumuli:
Mayby there is answer, but this over 200 pages....

If phone are over night on, then if i go wallet it says root etc not work. But if i reboot phone, problem is gone, for while. Is this normal? Same thing, 13.8, 13.9 and now 14.0

And, same as Device integrity. Passes well when install and reboot, but if i wait few hour then its not, and failed. That is normal too?
[Magisk] HippoMan:
Please let us know if it lasts a while. That would give lots of us some hope.
[Magisk] dedalos91:
I just did it and will let you know

Can I publish this information or is it forbidden? or is it not good that many of us use them?
[Magisk] intel_core_i7:
It's weird that an user can use Apple Pay on a jailbroken/tampered iDevice, but you can't do that on an Android phone with unlocked bootloader. Root/jaibreak detection from third party apps is another story though

With the aggression Google is showing these days, having a locked Android device and an iOS based device with TrollStore for daily use I can see little to no difference, I can install apps outside of "the store they make you use", make tap to pay payments, use banking apps, using apps and doing stuff that an average joe would do.

You can literally replace you credit card image in Apple Pay to whatever you want with a TrollStore iDevice, I wonder if you can do that with G's one in a hundred years
[Magisk] sawdoctor:
You have been so helpful so hopefully you can help me.

Running pixel fold with qpr2 beta. I've used several fingerprints which I know are working and the json files have been created (used pixelflasher) unfortunately none of the PIF json releases have passed device. The last one that worked was the modified safetynet fix by @chiteroman . I've seen pixel 8 pro users with the same issue and think it maybe related to the beta software
[Magisk] shoey63:
Don't publish it here.

If you want to help any users who are struggling maybe DM them, but I would suggest keeping it to yourself.
[Magisk] FredMontteiro:
Thank you very much for your work friend. Humbly I don't understand how to make such a far-fetched module, but strangely everything referring to the outdated Riru tends to work better, I went back to Displax 1.3 (Riru) together with Magisk Delta from HuskyDG and the magic happened. I don't know why, maybe because I use Android 11 which is a bit old.
[Magisk] philidor:
On Pixel 7 (android 13) all works well. Have you tried to clear cache? I use shamiko and have Play Store on deny list
[Magisk] andriy_:
7.2 works well on sm-n9860 with latest firmware. No strong security though.
[Magisk] Homeboy76:
I think you mean no 'Meets Strong Integrity'.

The 'Meets Strong Integrity' bug 'exploit' was patched by Google.

If you want to pass 'Meets Strong Integrity' you'll have to unroot it.
[Magisk] quasyl:
I tried the latest 7.3:

Aleatory I obtain 3 fails or meet basic and devices green. My banking app works normally.
[Magisk] chiteroman:
Do you have installed custom fonts ? There is a bug with Zygisk and custom fonts.
[Magisk] sawdoctor:
I've a feeling something is either going on with the Google servers or the play integrity checker app. All my banking apps and Google wallet are working fine but 8 keep getting 3 fails in the app but when i reboot and check again 8 pass device and basic until i get 3 fails again
[Magisk] Marucins:
You've got something really screwed up. S23 Ultra and 7.1 and now 7.3 everything from Play Store works.
[Magisk] philidor:
Have you the update function on Magick with 7.3. The option disappear (I have it with 7)
[Magisk] Xennet:
As mentioned by others above.. v7 passes basic and device all the time..

v 7.1 v 7.2 v 7.3

Passes only occasionally... But most of the time fails both basic and device....

Xiaomi eu rom

Mi 13 pro
[Magisk] Kutunf:
My Uber Driver does not want to work for me after I returned to the stock rom and blocked the bootloader. Any ideas how to get Uber Driver to work?
[Magisk] westruk:
You pass strong integrity now?
[Magisk] zgfg:
Don't know for v7.3 but Update is not showing for v7.2 either

Reason is simple, link in the module.prop:

updateJson=https://raw.githubusercontent.com/chiteroman/PlayIntegrityFix/main/update.json

yields:

404 Not Found

Actually, currently (last changes are showing now as 16 hours ago) there are no (more?) update.json, changelong.md and <package>.zip (as needed for Update mechanism) on the GitHub:

GitHub - chiteroman/PlayIntegrityFix: Fix Play Integrity (and SafetyNet) verdicts.

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

github.com

EDIT:

Just downloaded v7.3 from post #1, updateJson link/line in the v7.3 module.prop is missing (seems that the author has intentionally disabled Update mechanism for his module)
[Magisk] chiteroman:
Updated to v7.4

Fixed.
[Magisk] philidor:
Are there any other changes or only the restore of the update function?
[Magisk] totalolage:
This module seems to be having the same issue as @Displax's SafetyNet Fix mod, I've filed an issue: https://github.com/Displax/safetynet-fix/issues/29
[Magisk] chiteroman:
Yes, I enforce the hook because few devices require it to pass Device.

Broken keymaster... Can you send screenshot of this app?

Key Attestation Demo - Apps on Google Play

Demo for Key Attestation feature of the Android system.

play.google.com
[Magisk] quasyl:
Now I can understand the reason why with the 7.4 version I pass "meet basic and device integrity" 100% of tests. I didn't understand how looking for update can relate with that 😀.

Thank you for this update, it resolves my problems. (Poco X5 pro running xiaomi.eu 14.03)
[Magisk] Lu5ck:
For those trying and keep trying custom pif but never could get one to work, you may want to suspect that your PIF is broken because that exactly what happened to mine.

Personally, I went and delete everything in "/data/adb" and everythng related to magisk in "/system_root/system/addon.d" (depending on device, your's may be just "/system"). Then reroot the device and now PIF is working properly as I could get print that wasn't working previously working now.
[Magisk] pndwal:
7.1.1 no?

It's always using BASIC; no need to revert or for fake keystore registration to trigger fallback to BASIC attestation on device or for any prop mismatches to bypass HARDWARE_BACKED evaluationType enforcement in servers*...

... bootloader state is irrelevant here...

This device doesn't need USNF/PIF for the above reasons, but will need GSM Droidguard/attestation (Play Services.unstable) and possibly main process (if using late Android now) in denylist to hide root from attestation service, and a solution for sensitive props (that's what you recall hides bootloader state and more suspicious property values, and was a function of MagiskHide until 24.0) like MHPC (just install, sensitive props are reset by default with no configuration), Shamiko or other...

Yup... Several solutions for sensitive "MagiskHide" props are available aside from USNF/PIF...

Not sure whay you mean here... 🤔

I think you're thinking of on-device fallback method... That's what uses exception (error) to activate BASIC-only attestations, but not on OP5T... It is only BASIC capable...

Nah, doesn't 'support HARDWARE attest'...

You're correct that Model was the first prop used for HARDWARE_BACKED evaluationType enforcement in servers mentioned above*... OnePlus 5T would never have needed that as Google would never enforce this server end evaluationType on devices not capable (pre Android 8 Launch Version/pre Keymaster 3)... It doesn't need Fingerprint or Shipping level mismatches either, which prop based enforcement bypasses were added later.

👀 PW
[Magisk] awarexda:
TB checker is also a potential threat in the sense that some fingerprints are pinged in high numbers and Google can see them and act accordingly?
[Magisk] beeshyams:
Can I DM you for that or if you prefer please DM and send.. Will try

Thanks
[Magisk] Serveh:
Hello, I installed PiF v14 but I can´t see the data/adb folder.

Should I create it?
[Magisk] maxmax0:
Sure, but they are not bitter, and I explained to you why what they are doing makes perfect sense from a business point of view.
[Magisk] dlads:
No worries man.. I don't hold grudges.. 👍🏼
[Magisk] hayvan96:
I don't understand. I've generated a custom.pif.json thanks to @osm0sis 's script. Using his fork, I've copied the file at the right location. But when I reboot, Yasnac identifies my device as Bluejay (it is actually a Pixel 6a), all checks fail (CTS, basic, etc.) That verdict fails is possible, but shouldn't the fingerprint device appear in YASNAC? I have the impression the json is not taken into account
[Magisk] HRSE:
Many things have perfect sense from a business point of view, such as embedding ads in system apps or installing bloatware in every phones or tracking and selling users' data or disallowing skipping ads in YouTube or removing adblock add-ons from the store, but is it enjoyable to live in such purely profit-driven world?

Do you think people are stupid when they switch to renewable energy and lose profit to reduce carbon emissions?
[Magisk] AlesiBoss:
Dont lose hope people, I was already almost hopeless after 3 hours of trying fingerprints, thinking to myself that nothing will simply work for me and voila! I finally found one! I have one card that i dont have physically, so i kinda needed NFC payments to work, so I am so glad it works now again... lets hope i will not have to spend 3 hours too often...
[Magisk] hassanhassan:
I wish I never rooted my phone now... this is way too complicated
[Magisk] GGYT_YT:
hey! could you dm me with some tips on how you found it? I know that sharing fingerprints in not allowed but I am searching and trying fingerprints for like 8 hours and I can't find any.
[Magisk] AlesiBoss:
Well, I am not sure if I can help, in the end i specifically targeted android 8 devices until one worked
[Magisk] Pietplezier:
How can I see if my PIF is broken or not?
[Magisk] edd080:
Hello and sorry for the noob post, I have a stock rooted Xiaomi redmi note 9s, with magisk (inluding zygisk) upgraded to the latest 14.0 play integrity fix gives me only basic integrity, failing at device integrity. Everything is working fine so far, is this how it is supposed to be at the moment?

Thank you .
[Magisk] GGYT_YT:
me too. I have searched multiple dumps of likes of samsung, asus, sony etc. based on a database that I created myself, but to no avail. this is already getting far too insane for me
[Magisk] GGYT_YT:
yes - you have to search for a fingerprint that meets "DEVICE INTEGRITY", because 14.0 doesn't feature any fingerprints included, compared to previous versions (last ones were banned by Google).
[Magisk] BROKEN1981:
Looking at KSU, you can have root with a locked BL. Does that mean you will always pass safety net so you don't need PIF?
[Magisk] sawdoctor:
Ok i know which devices/firmware to take fingerprints from but can't get any to work. So my question is does it matter which firmware we use. Do i need to take the fingerprint from a firmware before it updated to android 8 or from a firmware after the device updated to android 8 or does it not matter. Is the fingerprint the same in all firmware files for that device
[Magisk] thesingular:
Root with a locked BL? How can you do that in the first place, without "jailbreaking" the phone the way they do to iPhones?
[Magisk] Lu5ck:
You won't know. I only suspect and confirmed my suspicion when tested with a supposedly working key. If you tried dozens of keys and all of them doesn't work, you should really consider doing a clean removal of your root and reinstall it.
[Magisk] Lu5ck:
You can't, because your boot hash won't match.
[Magisk] AlesiBoss:
not every android 8 device works... I tried quite a lot of them until finally one was working, I took print from 8.1.0 version of its image
[Magisk] System23:
thats easy Download STOCKROM and open System.img and take a look into build.prop ,than you find the Fingerprints
[Magisk] zeyad_155:
Hi, i just updated the module to version 14.0, and i noticed it now asks you to manually specify a valid fingerprint. Was this done because google kept banning the fingerprints this module was using? And also how can i possibly find my own fingerprints to use?

Would appreciate if anybody could help me
[Magisk] AlesiBoss:
Here is how to set your own fingerprint https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-179#post-89189970

and finding it is not that easy, but i was using google and looking for build.props dumps, happy hunting, it took 3 hours for me to find working key, you specifically want android 8 devices
[Magisk] System23:
Also PiF is working on my Android 14 without any Problems, but my Banking App detects the Root, i have found only one Solution to Fix them and thats going back to a older Version of my Banking APP in there the new checking procedure not Existet, than its working without detectet root!!!
[Magisk] Lu5ck:
Anyone managed to get https://github.com/althafvly/ih8sn to work? I used a key that is working in PIF, I think it need to spoof more props but I do not know which.
[Magisk] BROKEN1981:
GitHub - chenxiaolong/avbroot: Sign (and root) Android A/B OTAs with custom keys while preserving Android Verified Boot

Sign (and root) Android A/B OTAs with custom keys while preserving Android Verified Boot - chenxiaolong/avbroot

github.com

I saw this
[Magisk] cyycolin:
I tried several FPs but after reboot, play store is not certified and TB checker did not pass device integrity.

If a FP is not banned, do i see play store is certified and TB checker pass device integrity after reboot right away? Or do i need to wait some time?

And

After i update value in the /data/adb/pif.json of v14, do i need to clear cache of play store, wallet and gms before reboot?

Do i need to hide play store, wallet and gms in magisk hide?

I also have shamiko, do i need to disable it?

Many thanks
[Magisk] BROKEN1981:
Ahh ok. The guide seemed easy and I saw that it will preserve Android Verified Boot. So I figured it was a simple solution so this whole PIF stuff can go out the window.
[Magisk] zeyad_155:
so you mean i'll look for devices which last update received for them was android 8?
[Magisk] Lu5ck:
That uses custom key and they say that custom key will not pass strong check. It makes you wonder why they even allow you to flash custom key if it doesn't pass any security check
[Magisk] downhere:
There is only one you can ask to get a long term / permanent solution: Google.

But obviously the pure existence of this thread is Googles answer already.

Lock your bootloader and you're done.
[Magisk] purgy:
To give one a sense that this isn't just a total waste of time, can anyone who has found a working set of props (so hopefully a fairly small amount of PI requests made with those props) post if they start failing?

If they're managing to kill props that should be fairly "unique", then obviously this isn't any kind of real solution, even if you do have 50 pif prop files ready to go.
[Magisk] BROKEN1981:
I don't have shamiko. I deleted the PIF in adb, put one in it and just rebooted. It seems to work. Play Store says I'm ok. I'm honestly starting to think we are getting caught because people are using 3rd party apps to check.
[Magisk] System23:
a Member has sayed that we should use different Methods, heres a working Method too, also i have used MagiskHideProps before Android 12 and it works many Years ,but this Project is out of Support!!! Also we do it itself!!!

Step 1

Download a STOCKROM of your Device, extract them and open System/Super Image with any programm like 7zip and look into the Directory system and extract the build.prop

Step 2

open build.prop with Editor and you would find a working Fingerprint!!!

now Extract MagiskHideProps_6.1.2.zip and go into Directory commons and open prints.sh,

now you see the Entrys of all Supportet Devices and their Fingerprints!!!

Now you can ADD the Fingerprint from build.prop into prints.sh!!!

So easy is it to ADD new Devices or new Fingerprints!!

Now we go back a directory and Found the File module.md5 they have the md5 checksum listend for validiation

process at Setup, also generate a new md5 of prints.sh and change the declared value in module.md5, or you delete the declared entry of prints.sh , so it wouldnt check this on Setup!!!

Now you can Archive the Files back to ZIP again!!!

And the usual way to Install MagiskHideProps_6.1.2.zip in Magisk Modules is Known, dont Forgett UniversalSaftyNet_Fix_MOD_2.0, than it works too!!!

BUT IT NOT PASS STRONG!!!!
[Magisk] Gilg@mesh:
when wallet does not work are you supposed to get any message about it when you open it? I don't get anything.
[Magisk] AlesiBoss:
Some say last update on android 9 works too, but for me, device with last update on 8.1.0 worked, so I am not sure if it matters that much
[Magisk] cyycolin:
Did you hide play store, wallet and gms?
[Magisk] BROKEN1981:
If you don't get a message, you "should" be ok. Either that or it's taking a bit for the message to pop up. Just check what Play store says
[Magisk] maxmax0:
Well, that's easy, Google is a for-profit company, case closed. Also, the reality is that most ppl don't switch to renewables unless incentivized, but this is now getting off-topic.
[Magisk] Gilg@mesh:
I brought this up yesterday day that I only meet basic integrity but could still pay, might try today too.
[Magisk] BROKEN1981:
Yes, there are times when I only meet basic and can still use wallet to pay. I think it's a lag issue. Once the message pops up in wallet, you can't.
[Magisk] straightcore:
Tap to pay setup

Your phone meets the security requirements

or

Your phone does not meet the security requirements
[Magisk] Gilg@mesh:
ok, hopefully this lag is permanent, otherwise I have my banking app that I also can pay with, so no big deal if wallet don't work as long as other apps continues to work.
[Magisk] xXPoWeRx:
I have a question. With v14.0 of PiF we need to spoof a device fingerprint. Now, let's suppose that I have unlocked my phone (it's a Redmi Note 12 5G) and I installed the custom EU rom.

Let's suppose also that my friend uses the very same phone model but has not unlocked the phone so it's using the stock ROM.

Now, can I extract the fingerprint from his phone? And will something happen to his phone? Like google detecting two phones using the same fingerprint and banning it for both of us
[Magisk] maxmax0:
Bank cards with secure NFC are a totally different use case than a phone with a software programmable NFC. Also, I don't know about your local regulations, but where I am, contactless card payments have a set amount limit, over which you need to supply PIN, and/or insert the card. Google Wallet does not have this limit, and thus naturally needs stronger security. And Google needs to find a common security denominator for the global market.

Finally: You think your credit card is totally unprotected? Have fun trying to duplicate your card NFC tag, should be easy going then :)
[Magisk] Fishawy:
@osm0sis @pndwal @badabing2003 The above sounds interesting - and potentially more robust - if it was verified. Do you think something like this can be used as a broader solution?
[Magisk] BROKEN1981:
Nothing will happen to his phone. I had a similar question. Answer I got is no.
[Magisk] BROKEN1981:
So you are still basic only? For how long? I've only had it for about a few hours max.
[Magisk] maxmax0:
My new mornnig routine:

Get up, pee, brush teeth, check DEVICE_INTEGRITY... 😁
[Magisk] Gilg@mesh:
since 13.9 module stopped working.
[Magisk] BROKEN1981:
I check every few hours while I am up. I try to see how long it takes Google. They are actually pretty fast and seems like it's a timed interval.
[Magisk] BROKEN1981:
Awesome luck! I would suggest not to clear any cache or data.
[Magisk] Gilg@mesh:
yeah I never done it since I got the phone.
[Magisk] GGYT_YT:
any help? (i can't edit or check the fingerprint)
[Magisk] BROKEN1981:
Ask in Pixel Flasher thread
[Magisk] GGYT_YT:
+ when I check play integrity, it still shows my phone model and non-edited fingerprint. should that be normal?
[Magisk] mates21:
Is it enough to edit the pif.json file in the v14 module? Do I need to move this file to /data/adb?
[Magisk] GGYT_YT:
ok, thanks
[Magisk] BROKEN1981:
Move to adb
[Magisk] BROKEN1981:
Yes.
[Magisk] iruiz2:
I just checked my old phone (a xiaomi with android 7.1.2 custom ROM launched with API 23 and it passes basic and device PI. But when I pull the print info using build.pro and run it in my Op9pro, it fails... Any idea why?