yashsingh1/xdaforums huggingface dataset:
[Magisk] Nergal di Cuthah:
Not long probably. 2 series is banana-ed from old versions of usnf and pif, if i understand correctly.
[Magisk] Nergal di Cuthah:
Probably, but it's obvious knowledge (as i just posted 2 series is banana-ed and 4 is too new afaik). I don't know if the inbetween work so not really spilling fingerprints or google crumbs.
[Magisk] JustSom:
I went with the stock rom route, got it working on my fourth attempt

takes a little longer to get everything running but it worked
[Magisk] Gilg@mesh:
if I buy used Galaxy S8/S9, is it guaranteed to work?
[Magisk] ArzZenic:
I know, but, less info is better info :) even through those fingerprints
[Magisk] jurluk:
How do you edit /data/adb/pif.json? I'm using Total Commander but it doesn't have persmission to change it
[Magisk] JustSom:
There's no guarantees, it could be already flagged and you will just throw your money away.

The best thing long term is to learn how to extract the files from stock roms, so if something goes wrong, you can just look up some other fingerprint.

Even then we are not sure until when we're safe with this whole cat and mouse game...

Good luck!
[Magisk] yaqib:
Why I pass the basic and device integrity ，Even though I can use gpay, my Google Wallet still shows that the phone does not meet the security requirements. Do I need to wait 24 hours for Google Wallet to update the verification?
[Magisk] yickhcr:
can someone explain how one might go about resolving "Google Play Service API error, unknown status code -8", please...
[Magisk] JustSom:
I did it through adb using vim, not sure how it would work on total commander though, have you given it root permissions?

My route was, plug your phone on usb, then "adb root" to change the server to root mode, then "adb shell" to get a shell, then "vim /data/adb/pif.json" to edit it.

you could push the edited file from your pc to android too, instead of doing the vim route, adb server as root, then just "adb push local.pif.json /data/adb/pif.json". Doing this way, you might have to change the permissions on the pushed file.

The permissions for /data/adb/pif.json are 0644, so after pushing do an "adb shell", then "chmod 644 /data/adb/pif.json"
[Magisk] ArzZenic:
Use TB Checker or default Play Store Integrity Checker through dev. options.
[Magisk] JustSom:
Try clearing cache/data from google play services and google wallet, then reboot. It will reset your app though, you will have to add your cards again, but to me the only way that worked when it glitched like that was doing this.
[Magisk] yaqib:
我试过没有成功

Mod translation: I tried without success
[Magisk] 0czko:
Everytime i put different pif.json file in adb/data folder, GP Integrity test shows my current true fingerprint, not the one provided in pif.json file, thus failing to get device integrity. Should GP test show spoofed fingerprint when checking integrity?
[Magisk] ArzZenic:
🔧 [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] BettlePimp:
A lot of posts of people who won the lottery explaining how they did it and why you could do it too.
[Magisk] ArzZenic:
Everything was already said. Just go through 190 - last page.. I said it repeatedly in last 20pages.
[Magisk] DissCent:
I just tried both apps and they all receive this -8 error stating that the app makes too many requests. Are there any more ways we can use to check play integrity? Otherwise testing different fingerprints isn't really possible.
[Magisk] JustSom:
Its weird, ignore the other stuff and focus only on the "Labels" one, if you got a fingerprint that works, it will check [MEETS_BASIC_INTEGRITY, MEETS_DEVICE_INTEGRITY].

I tried a couple of stock rom pifs and everytime that I changed, it kept the same values and changed only this "Labels" one. Got it working after a couple of attempts.
[Magisk] ArzZenic:
You can go through default Play Store checker via developer options. This will never give you -8, since its Google internal. (TB never gave mě -8 until today)

Alot of people are using those checkers these days, TB Checker worked for me, if its not working for you. Just use Pixel Flasher to "Save & ...." PIF and then go to GPlay Store and check through internal tool.
[Magisk] JustSom:
Play Store has a developer mode that you can check your integrity, instead of relying on third party apps, I think on the first post there's a guide on how to do it.
[Magisk] Nergal di Cuthah:
Correct you'll see the correct data in the app. The way to see if the spoofs are passing on is logcat (i think logcat | grep PIF)
[Magisk] ipilcher:
Not really.

There are important bits missing. (Note that I fully understand why people omit those bits.)

For example, finding stock firmware images for older phones is not simple, and most of them don't seem to be formatted as standard ZIP files containng a system.img or payload.bin. I've spent my entire afternoon on this, and I've only been able to find a single stock ROM file from which I was actually able to extract the build.prop files.

I've seens OZIP files, RAR files, sparse files, and many unmountable filesystem images. I suppose that the availability and format of these files is mainly determined by the device manufacturer, and I obviously haven't been picking the right ones. But (again for understandable reasons) those who know what the right manufacturers are aren't going to share that information.
[Magisk] jurluk:
Although TC had root acces it couldn't overwrite pif.json 🤷‍♂️

I managed to do it using another file explorer. Thanks anyway

But still no luck after maybe 10 jsons tested :(
[Magisk] bakaekze:
All of those are extractable. There are tools on this very forum for every kind of ROM.
[Magisk] mates21:
Isn't it easier to edit a blank file in pif14 and complete it with the appropriate fingerprint?
[Magisk] ArzZenic:
That's what exactly everybody is doing now- v14 is blank from the start.

Not everybody knows, what are the correct parameters in build.props /system @ /vendor

So I'll just post again:

pif.json from build.props should be:

ro.product.name -> PRODUCT

ro.product.device -> DEVICE

ro.product.manufacturer -> MANUFACTURER

ro.product.brand -> BRAND

ro.product.model -> MODEL

ro.build.fingerprint -> FINGERPRINT

ro.build.version.security_patch -> SECURITY_PATCH

ro.product.first_api_level -> FIRST_API_LEVEL
[Magisk] digger16309:
Even though it is working for me at present, this entire ongoing debacle has me really thinking it's time to get out. I don't like Samsung OneUI and Google hardware isn't good enough to use non-rooted. It's been almost 10 years since I ditched Apple, but I've lost interest in playing the mouse. It's exhausting.
[Magisk] revengineer:
My luck with yesterday's fingerprint find was short-lived as it was banned today. The PI checker apps are all over their limit. I am sure by the end of the weekend you guys will get the last fingerprint banned. Good luck, have at it...
[Magisk] bigknowz:
Good call, set up my watch and it worked. Thanks for sparking the idea.
[Magisk] HippoMan:
There have traditionally been lots of Telephone Sanitizers among the Googlefrinchians and their ancestors. They'll be able to fix this soon.
[Magisk] HippoMan:
The internal tool also sometimes returns a message saying, in effect, that it's overloaded. If that happens, just wait maybe 60 seconds and then select "Retry".
[Magisk] mates21:
Yes, I know. But can't I just edit the empty file without moving it to adb?
[Magisk] ArzZenic:
Google overloaded themselves, hehe. Shame on them, nobody is doing any harm via optimising their OSs
[Magisk] linuxares:
Anyone got a clue why the "spoof" doesn't seem to work as in I have edited the pif.json file, yet it's the wrong fingerprint showing up in TB Checker and when I try using Pixelflasher it shows the wrong one and the logcat is empty when I got in via a shell and ask it for logcat | grep 'PIF'

When I check the following:

./debug_ramdisk/.magisk/modules/playintegrityfix/pif.json and ./data/adb/modules/playintegrityfix/pif.json both show this one:

{
"PRODUCT": "",
"DEVICE": "",
"MANUFACTURER": "",
"BRAND": "",
"MODEL": "",
"FINGERPRINT": "",
"SECURITY_PATCH": "",
"FIRST_API_LEVEL": ""
}

While

./data/adb/pif.json

and

./data/local/tmp/pif.json

show the correct one. I guess it's a bug somewhere?

EDIT:

Logcat showed something now after editing the /data/adb/modules/playintegrityfix/pif.json and rebooting

12-03 01:08:45.719 9079 9284 D PIF/Native: [ro.vendor.api_level]: 33 -> 33
12-03 01:08:45.879 9079 9284 D PIF/Native: [ro.build.version.security_patch]: 2023-11-01 -> 2023-11-01
12-03 01:08:45.884 9079 9284 D PIF/Native: [ro.product.first_api_level]: 33 -> 33

But the device fingerprint isn't changed :/
[Magisk] ArzZenic:
🔧 [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

Don't be lazy. Check my posts.
[Magisk] neelchauhan:
I am fortunate to win the fingerprint lottery, for now that is.

Like @nil? said, if you live in the EU, get the European Commission involved: https://citizens-initiative.europa.eu/how-it-works_en

I'm an American with parents from India so I can't take part in this. But if I were an EU citizen, I would start it myself.
[Magisk] JustSom:
Its exhausting, yes, but one thing to note is that this community only came to be, and grew to the point that it is today, as a response to a necessity

It would be great if we could just buy a phone, install whatever and be done with it, but unfortunately that's not how it works, and companies aren't in our favour, as time has proven over and over.

The best we can do is try to keep this alive for as long as we can, teaching people on how to mod and stuff, there's no other way around it.
[Magisk] Yeedatoy:
You can have root with Magisk with a locked bootloader. KSU is pointless unless you use it only for root access and nothing else. Banking apps and several it other apps will fail to work due to an unlocked bootloader, developer options enabled, and adb debugging way before failing due to magisk. It's not even typically magisk....it's Zygisk or busybox. KSU has went from one direction since it's early 2018 stages to a bandwagon lemming-like human centipede headache that makes me want to slap a someone with an oversized gelatin dildo
[Magisk] zgfg:
For v14, you must fill /data/adb/pif.json

That's the new lath the module reads pif.json

---

Btw, since all are fishing now for themselves, all three apps are thtottled

It remains only testing through Playstore, Dev options - btw, I don't like testing from Playstore and letting it to see when my testing prints fail
[Magisk] Yeedatoy:
If you don't get the message, typically you have a red nfc circle, and when you go to settings and click set up tap to pay you will see the issue. I've noticed the pay app will typically provide a prompt more often than wallet
[Magisk] BROKEN1981:
Google is not mining this thread. My mother has a P6P that I rooted. She is still using 13.3 and passing. It has to be something else. While no details should be posted, it's not against forum rules to actually post them.
[Magisk] linuxares:
I have provided prints :)

Let me show you what I try to give it (they're probably banned but still they don't change the FINGERPRINT

{
"PRODUCT" : "cheetah",
"DEVICE" : "cheetah",
"MANUFACTURER" : "Google",
"BRAND" : "google",
"MODEL" : "Pixel 7 Pro",
"FINGERPRINT" : "<removed because testing!!>",
"SECURITY_PATCH" : "2023-11-01",
"FIRST_API_LEVEL" : "32"
}

More logcat

130|cheetah:/ $ logcat | grep 'PIF'
12-03 01:28:00.629 8045 8045 D PIF/Native: Read from file descriptor file 'classes.dex' -> 7024 bytes
12-03 01:28:00.629 8045 8045 D PIF/Native: Read from file descriptor file 'pif.json' -> 303 bytes
12-03 01:28:00.648 8045 8045 D PIF/Native: JSON contains 8 keys!
12-03 01:28:00.648 8045 8045 D PIF/Native: Found '__system_property_read_callback' handle at 0x7e7ead6af0
12-03 01:28:00.648 8045 8045 D PIF/Native: get system classloader
12-03 01:28:00.648 8045 8045 D PIF/Native: create class loader
12-03 01:28:00.648 8045 8045 D PIF/Native: load class
12-03 01:28:00.648 8045 8045 D PIF/Native: call init
12-03 01:28:00.649 8045 8045 D PIF/Java: Spoof KeyStoreSpi and Provider done!
12-03 01:28:00.649 8045 8045 D PIF/Java: [FINGERPRINT]: google/cheetah/cheetah:14/UP1A.231105.003/My original?:user/release-keys -> google/cheetah/cheetah:14/UP1A.231105.003.A1/testkey:user/release-keys
12-03 01:28:01.352 8045 8069 D PIF/Native: [ro.vendor.api_level]: 33 -> 32
12-03 01:28:02.281 8045 8069 D PIF/Native: [ro.build.version.security_patch]: 2023-11-01 -> 2023-11-01
12-03 01:28:02.289 8045 8069 D PIF/Native: [ro.product.first_api_level]: 33 -> 32
12-03 01:28:02.437 8045 8145 D PIF/Java: DroidGuard detected!
12-03 01:28:02.480 8045 8145 D PIF/Native: [ro.product.first_api_level]: 33 -> 32
12-03 01:28:02.955 8045 8145 D PIF/Native: [ro.vendor.api_level]: 33 -> 32
12-03 01:28:03.118 8045 8145 D PIF/Java: DroidGuard detected!
12-03 01:28:03.344 8045 8145 D PIF/Native: [ro.build.version.security_patch]: 2023-11-01 -> 2023-11-01
12-03 01:28:21.063 8045 11757 D PIF/Native: [ro.product.first_api_level]: 33 -> 32
12-03 01:28:21.070 8045 11757 D PIF/Native: [ro.build.version.security_patch]: 2023-11-01 -> 2023-11-01
12-03 01:28:21.070 8045 11757 D PIF/Native: [ro.vendor.api_level]: 33 -> 32

Just edited my keys to they aren't showing. Still no spoofing working :/
[Magisk] BROKEN1981:
Then Google would pull out of the EU. Google is an American company.
[Magisk] philidor:
How do you root your phone? Magisk?, kernelsu? If you used magisk do you hide magisk app and root from your banking app? And how? Can you give us a log
[Magisk] zgfg:
Forget the posts a month old

Google has fixed the hole on their side, you will no more pass Strong Integrity with the unlocked Bootloader

Forward to post #216, July 28, when Google made a fix on their side and everybody confirmed they stopped passing Strong
[Magisk] simpleatom7:
I'm on Redmi Note 8 Pro (India) & i used Magisk.

By hiding magisk, root, ig u mean hidemagisk which changes its name & package & the answer is yes. I also add bank app to deny list along with google & google play services.

Regarding log, u mean magisk log right?
[Magisk] simpleatom7:
Man this is so sad. I didn't care about strong integrity however ig this is the reason my YONO bank app is crashing :|
[Magisk] simpleatom7:
Does it pass strong integrity as well. + can u use banking apps like YONO?
[Magisk] shoey63:
Broken TEE/Bootloader plus exploit in Play Integrity.

But not anymore. Google patched everything.
[Magisk] quasyl:
Don't think you can pass the "strong integrity", it is now impossible without locking again the bootloader.

Yes I use my banking app (Intesa San Paolo) without problems. I don't know YONO.
[Magisk] zgfg:
No more Strong Integrity since July 28, post #216, page 11!!!

I found one Yono on the PlayStore and I'm not from India to Register. With (Basic and Device Integrity but not Strong) Magisk Delta and HMA I can get up to as on the screenshots
[Magisk] pndwal:
Previously:

https://xdaforums.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-88681803

... Still working for me. 🙂

Do you have

- Magisk App hidden in stub,

- Latest Shamiko public release (for proper root hiding),

- App processes selected in denylist?

🤠 PW
[Magisk] simpleatom7:
Daaammmm the fact the app didn't force close & displayed login page already shows u passed the requirements!

Can u guide me what else i need?

Magisk delta & hide my app are sufficient? However HMA needs lposed which again might cause detection issues?
[Magisk] simpleatom7:
You are correct bro.
[Magisk] simpleatom7:
I'm getting the "This is the solution vibes"! Would update u after i try this!
[Magisk] simpleatom7:
Which magisk delta version r u using since latest one has got "magisk hide" option removed!
[Magisk] sawdoctor:
Sorry for ot but I know you are really knowledgeable on this.

Is there any advantage to using shamiko over magisk enforce denylist ? All my banking apps are currently working with just magisk enforcing and displax universal safety net. If it's not broke don't fix it is what I'm going with
[Magisk] zgfg:
Of course that HMA requires LSPosed

Magisk Delta has its own thread and download the latest version from TG Channel. Use Unmount modules (as it has replaced MagiskHide)

HMA has also its thread, find a link to the guide in the post #1 there
[Magisk] zgfg:
Btw, I came now to the same point on the other phone with Magisk Canary latest and also HMA. Hence you don't need Delta or Alpha

No force-closing. Only when I press to 'Existing customer' (of course, I'm not) it tells me that I have no SIM card inserted - however, I do have two working SIM cards. Maybe it looks for an India SIM card
[Magisk] simpleatom7:
Yep that screen in yono means u have already fixed this man. You and other guy are legends.

Guide me if i'm doing it correct

>Magisk canary(26105)

>Zygisk enabled

>Added YONO bank, all google processes + 1st & com.google.android.gms.unstable (8th) in deny list. Didn't enforce deny list

>Shamiko installed

>Play integrity fix module installed (by Displax)

>Busy box module for PI Fix

>YASNAC = Both pass

>PI = Device, Basic integrity pass

>Play store verified

>Lsposed installed

>HMA installed (would be runningit now)

Hope i didn't miss anything. Anything else i need?

Btw ig i have installed extra apps/mdoules like busybox or PI fix by displax, if so, do let me know.

Can't thank u enough.
[Magisk] m0han:
So, did you actually get Yono to work for you?
[Magisk] zgfg:
You have to configure HMA to hide Magisk app and HMA itself (and other LSPosed modules if you have) from Yono. And reboot then

Follow the guide on GitHub for configuring HMA. As said, link for is in XDA thread. Actually, I'm simply using Whitelist method as on the screenshot
[Magisk] yickhcr:
seems like if you are getting the "Google Play Service API error, unknown status code -8" error, then just wait like 20 mins before trying again and it should be okay? or at least that's the case for me..

btw looks like i might be okay now with this last fingerprint i loaded........... google wallet isnt giving me that "doesnt meet security requirement" pop-up anymore so lets hope that's it
[Magisk] Gilg@mesh:
well I just did what you said and all seems good.
[Magisk] ArzZenic:
View attachment 6039651

Until it's possible! :D Just go through system/vendor and find the one, that works!

Don't give up, its all a plan. They can't ban all.
[Magisk] Yeedatoy:
Yeah you're good!
[Magisk] digger16309:
Fair enough but I've been in this ecosystem 9 years and it seems now like the walls are closing in. I don't recall a week like this one where Google went on the attack to kill USNF and multiple versions of PIF in a matter of days. There are hundreds (thousands?) of us scrambling around the internet mining fingerprint crumbs like rats, somewhat desperately, to keep our devices functional. I love how my device is customized but I need all my apps to work without me spending hours on it every week.
[Magisk] zgfg:
After I re-read your first post I edited my answer there - so please read again

Ie, you must fill you prints to

/data/adb/pif JSON

If using v14, that's the path where module reads from
[Magisk] ArzZenic:
Then Cheers mate, this scene just turned to rat race. No more comfortable patches via Magisk from our beloved (all +++) developers.

Go for BL lock & non-root with original ROM.

Buy Apple if you feel this way. Android is customizable (either working nor not)
[Magisk] Gilg@mesh:
can someone please upload the 13.3 version? thanks
[Magisk] ArzZenic:
Doesn't work.
[Magisk] Wolfcity:
As far as I found out you can also go to settings -> apps -> Google Play services -> force stop.

Faster than running killall com.google.android.gms.unstable.
[Magisk] pershoot:
Thank you.
[Magisk] ArzZenic:
Pixel Flasher has is it one click, if you don't want to be in terminal.
[Magisk] yickhcr:
what cache do i have to clear after adding a new fingerprint file to test and before i reboot?
[Magisk] gogos558:
You mean like Apple did? Yeah, sure...
[Magisk] pershoot:
adb shell

su

vi /data/adb/pif.json

keys: h is left, l is right, k is up, j is down, a is append, Esc is come out of insert mode (when performing an append).

move to just after a start quotation, hit a, enter text and hit Esc.

When you are all done hit colon then w then q and hit enter.

reboot

done.
[Magisk] BROKEN1981:
You really think the EU forced Apple with USB c or RCS?

LoL.........
[Magisk] linuxares:
I have edited it there. Still sadly the same. It won't "spoof" my fingerprint, but the rest maybe it changes? Since I have a Pixel 7 Pro I can't say if it does or not.
[Magisk] JustSom:
I did cache and data, on both google play services and wallet. Doing that way you will have to re add your cards to google wallet, but its the easiest method to verify if the fingerprint is valid.
[Magisk] dmenezes:
This is, at its very possible best, what we call anedoctical evidence, and sincerely, it doesn't prove anything.

> While no details should be posted, it's not against forum rules to actually post them.

Whether it is or it is not against forum *rules* means nothing. What matters is respecting the common good and the manifest will of the developers and contributors who worked so hard for us to have what we have.
[Magisk] BROKEN1981:
You can just reboot after the change. If you have Netflix, you have to clear data from Play Store. That's what I had to do for my phone. If no Netflix, just reboot. No need to clear cache and data.
[Magisk] BROKEN1981:
I understand and I'm not arguing that. Also I think I saw a dev post that even blacklisted fingerprints are working for other people. I'm wondering if it's the constant checking that is getting people caught. I used a fingerprint from the TG channel, checking at so many times and it no longer works.

I had to get another fingerprint. Checked it once. Now I am just waiting to see how long it lasts.
[Magisk] dmenezes:
That's exactly what I do. But there's a weird glitch: contrary to the Play Store app, when I press [force stop] at the Play Services screen, the button blinks but then comes on again -- on the Play Store app, it stays off.

Anyway, force-stopping then clearing all data for both (all the while keeping Airplane Mode ON) and then rebooting has worked perfectly for me. I don't remember, back in this long thread, who recommended doing that -- but whoever it was, I'm much obliged and the best I can do is to pass along the knowledge.
[Magisk] jurluk:
I've made pifgen.sh script which can generate pif.json from your build.prop file.

(edit: script is updated here)

If you have extracted build.prop from your rom image, you can use this script to generate pif.json to save few seconds.

It's bash script, so you obviously need Linux or WSL on Windows to run it.

Example usage:

# expects build.prop in the same folder
./pifgen.sh

# custom path
./pifgen.sh /some/path/build.prop

# custom file
./pifgen.sh /some/path/example.txt

It outputs props of interest, generates pif.json and outputs that pif.json.

For example (not valid for PI check, just example):

ro.build.product=bullhead
ro.product.device=bullhead
ro.product.manufacturer=LGE
ro.product.brand=google
ro.product.model=Nexus 5X
ro.build.fingerprint=google/bullhead/bullhead:8.0.0/OPR6.170623.013/4283548:user/release-keys
ro.build.version.security_patch=2017-08-05
ro.build.version.sdk=26
ro.product.first_api_level=23

{
"PRODUCT": "bullhead",
"DEVICE": "bullhead",
"MANUFACTURER": "LGE",
"BRAND": "google",
"MODEL": "Nexus 5X",
"FINGERPRINT": "google/bullhead/bullhead:8.0.0/OPR6.170623.013/4283548:user/release-keys",
"SECURITY_PATCH": "2017-08-05",
"FIRST_API_LEVEL": "26"
}
[Magisk] NGGMU:
Sorry, but does anyone know how to extract system.img files for build.prop? Thanks!