yashsingh1/xdaforums huggingface dataset:
[Magisk] V0latyle:
That doesn't necessarily mean anything. I pass both without even using a custom print.

I'm willing to bet that you are failing DEVICE if you check Play Integrity
[Magisk] Nergal di Cuthah:
Yasnac is outdated, you need a PI checker (such as the one built into PLAYSTORE developer settings) and see if you pass basic and device.
[Magisk] zgfg:
ok so back in business now but for how long if so many will use the same prints

btw, while spic was still working (now overquota) i quickly rested by script 30 prints that worked fine (device integrity) yesterday evening (i was cleaning my collection of duplicates and re-tested many yesterday) and today, few hours ago they were all passing yasnac and only basic integrity in pi

hence they really did mass banning
[Magisk] Spartacus500:
Working 😘

View attachment 6074609
[Magisk] cambunch:
This got my RCS working again instantly after a reboot. Pixel 7 on stock kernel, FWIW.

Thanks!
[Magisk] Vision:
Thanks for info, and good to know that for your fork.

I want to spoof not only for DroidGuard, but spoof this specific line in global to apps show this: ro.build.keys=release-keys and not test-keys

Netflix say this: Build: RKQ1.200826.002 test-keys

And other apps in the Display say the same
[Magisk] heathrow1:
Indeed play store just shows basic integrity. :(
[Magisk] osm0sis:
Updated my autopif.sh to automatically use migrate.sh to convert it to custom.pif.json for my fork if it's detected from my module being installed. 👍

🔧 [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] Vision:
@chiteroman can you add this line from ro.build.keys=test-keys to ro.build.keys=release-keys

to spoof in DroidGuard ? Or maybe global if not break something
[Magisk] V0latyle:
No, they didn't "just banned fingerprint"

I had a dozen or so working prints saved before. Not a single one of them works now, and I seriously doubt anyone else was using them. I've been testing a bunch of prints from a known working collection, and very very few of them are passing. So, Google threw a wrench the size of a Cadillac into this.

Whatever they did was much bigger than just banning/flagging/breaking/banana-ing particular prints; it's broken things for the vast majority of us.
[Magisk] osm0sis:
Yeah, then edit it in the module .sh script like I said.

Everybody's had global literally since the USNF days.
[Magisk] Vision:
Really? Because i see the line ro.build.tags and etc. but no one with say "keys" in the end

in which .sh of all ?T

hanks again for extra info

View attachment 6074624
[Magisk] jpm92:
Unfortunately I came to the same conclusion as you. None of my previously working PIFs work now, and every new I've tried don't either...I almost finished the collection already without luck...
[Magisk] HippoMan:
Oh, now I see that I misread a couple of the earlier messages.
[Magisk] V0latyle:
I've found at least one Samsung print that works, but so far none of the other prints from that device, or build, or security patch, or API level work.

I don't what Google did, but it is having pretty wide effects.

This could be a blessing in disguise because once we figure out how they're doing this (and we will, it's just a matter of time) it will likely give us more insight as to how to defeat this in the future.
[Magisk] Javiolini:
So here im back again to this jolly old thread to see what surprise google has cooked for us this month, always keeping us on our toes these guys...

Anyway anybody willing to go through all of @TheFreeman193 collection to see if its been axed?
[Magisk] jpm92:
Yeah, let's wait for now, and thank you guys very much for your effort.

As developers, do you guys know what is so freaking dangerous about having google wallet on a rooted phone? Why can't Google leave us the hell alone? 😅
[Magisk] jpm92:
I have finished it and none of them worked for me (at least I got the message that no more PIFs were available for my device type)...
[Magisk] aerotox:
Will placing own custom pif.json in /data/adb override the default FP included in chiteromans module? I was last time on Dev 2 version, updated it now to 15.9
[Magisk] magaedy:
Thanks man, It worked for me
[Magisk] HippoMan:
I've debated about the following a few times in the past ...

Running Wallet on a rooted device is actually *safer* than using plain old plastic credit cards and debit cards. That's because even on a rooted device, Wallet requires the screen to be locked on that device, and the user has to unlock the screen before using any of the stored bank cards.

I can use all my plastic debit and credit cards without even a PIN. And my banks repeatedly and gladly try to get me to sign up for these plastic cards which offer lower security than even running Wallet on a rooted Android device.

Furthermore, the percentage of Android users who have rooted and modded devices is minuscule, so there are literally millions of more cases where people are using freely issued plastic bank cards than there are rooted Android users who would want to use those cards via Wallet.
[Magisk] bakaekze:
yes it will
[Magisk] frank93:
i’m not expert enough here, but .. "dalvikvm: inaccessible or not found" sounds like some crucial tool/module is missing on my system for your script to extract the xiaomi-fp correctly. :/ android 14 stock, magisk 27.0, running autopif.sh as superuser from /sdcard/Download.
[Magisk] D€INOS:
Went back from osmOsis v5, v7 to this 15.9

It passes device & basic. 🎈🏆🎈

Fingerprint from December that like others went to only basic today.
[Magisk] vMAC:
That's what the KA hackers thought too...
[Magisk] kholdstayr:
This just fixed the issue for me. Thanks
[Magisk] badabing2003:
Update Release:

Feb 29, 2024 v6.8.1.0 change log:

Update Xiaomi apk download function to handle exceptions and work with the latest version (getting the pif print).

#160 Update readme to add pre-requisites for MacOS and Windows platforms.

#161 Auto detect file encoding before opening a file.

Don't check for Magisk path if in recovery mode.

Misc. bug fixes and improvements.
[Magisk] osm0sis:
You could just take the fingerprint from it 🙄

It's Xiaomi.eu's as usual.
[Magisk] D€INOS:
I thought it read my JSON in data/ADB/pif.json. Isn't it?
[Magisk] osm0sis:
Yeah that's weird. Type `which -a dalvikvm` on your device and then `which -a dalvikvm32` and `which -a dalvikvm64` and show me the outputs. Even on my arm64-only Pixel 8 Pro dalvikvm exists as a symlink to dalvikvm64.

Edit: Are you using Termux? I just use the basic Terminal Emulator/TermOne Plus app, or run it from FX File Explorer.
[Magisk] osm0sis:
He's back to hardcoding again: 🤷‍♂️

PlayIntegrityFix/app/src/main/java/es/chiteroman/playintegrityfix/EntryPoint.java at 32c119e4ac1be9e99cd4ded7569b809903039e63 · chiteroman/PlayIntegrityFix

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

github.com

And forced fallback to first API level 21 again: 🤨

PlayIntegrityFix/app/src/main/cpp/main.cpp at 32c119e4ac1be9e99cd4ded7569b809903039e63 · chiteroman/PlayIntegrityFix

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

github.com
[Magisk] Vision:
@chiteroman @osm0sis

I found a backup with the official ROM.

I figured out eventually in my Xiaomi Poco X3 NFC buy it from official store with Android 10 have this inside in the /System/build.prop file

Have this line: ro.build.keys=test-keys

if anyone with Xiaomi (official ROM, the same from when buy it) can check this, to confirm this line
[Magisk] nanodan:
Hey bud. Just tried your updated autopif.sh and the custom print it gave me worked. Really appreciate your time and effort in this, sucks Google has this specific bee in their butt. Can you DM me your donations link? Want to buy you a couple beers.
[Magisk] V0latyle:
Well, I've tried to explain this before. Whether intentional via rooting or unintentional via rootkit, a system with user root access is considered compromised in the Android world. So from a security perspective, there's little difference.

However...I don't think Google is really pursuing security here. If they were, they could easily require STRONG for GPay/Wallet - or, bypass Play Integrity altogether and use Android's native hardware key attestation feature.

When you consider what the BASIC and DEVICE verdicts really mean, they aren't necessarily indications of security so much as they are indications of compatitibility. BASIC doesn't mean much at all. DEVICE means that the device is running a CTS approved build, and Droidguard thinks it's been verified as such.

But, I don't want to necessarily attribute motive when I really don't know. They could be working to directly defeat our workarounds, or they might have just made a major "improvement" or other change that just happens to break our workaround. At some point, someone's going to figure out what is going on, and the game will continue.

I do find it interesting that a few certain prints are still working. Maybe if we can figure out why those specific prints are working, we can figure out why all the others aren't.

KA?
[Magisk] D€INOS:
Thanks for the heads up buddy 😃👌 , it's too bad that using a custom fingerprint isn't an option anymore.

Thanks for keeping developing your version, I wouldn't call it a fork anymore since you have gone a long way and above from the original PIF 🏆
[Magisk] osm0sis:
Much appreciated! 😍

Check out the sponsorship and one-time donation info on my Fork's GitHub page: https://github.com/osm0sis/PlayIntegrityFork

I think only the defaults are hardcoded in chit's again, but yeah, thanks for your support! 😁

As an aside, it really sucks, I was planning to release PIFork v8 today, but with all the turmoil from this mass ban I might as well take the extra time to iron out handling the PixelOS injector overlays correctly first (and @GabbyWC I'll probably need your help again testing that... 🙌). Guess Google's Play Integrity Guy and I had a similar idea and couldn't resist doing a release on Leap Day. 😅
[Magisk] jpm92:
Is the new PIF supposed to work? Because I dont pass device with the v15.9 (just curious as the release was 3h ago, so I imagine it should work).

Thanks
[Magisk] zgfg:
Look for the product name in that build.prop, does it refer to your Poco or to some geberic Qualcom (chipset)

Take a look for the proper fingerprinnt in the other build prop files you have, like in /vendor
[Magisk] D€INOS:
Yeah the module deleted my pif.json , so it was EU print that passed. Copying my pif.json and it only passed basic.
[Magisk] Iridule:
Xia print is the only working one for me. My cache of 50, some of which were private and others which were very obscure were all burned. Very unfortunate.
[Magisk] chiteroman:
What??

I just hardcoded the default values into Java, you can still use your own pif.json (/data/adb/pif.json)
[Magisk] purgy:
Back in business, thanks so much!
[Magisk] justDave:
I'm seeing the same error. It doesn't look like dalvikvm is in the termux path (not with 32 or 64 either). I did find one in /data/data/com.termux/files/usr/bin but that's not in the path, at least not in mine.
[Magisk] HippoMan:
Either way, the Googlefrinchians aren't working *for* us at all, and we shouldn't ever expect them to help us ... except perhaps by some sort of very improbable coincidence.

Much more likely, modding will continue to become increasingly difficult and precarious for us.
[Magisk] Vision:
Yeah is like this exactly in other show the right, we discussed this again in past i think

For this i believe this is normal for Xiaomi users, for some reason

/System/build.prop file

Have this line: ro.build.keys=test-keys

View attachment 6074643

For that i ask, if anyone with Xiaomi (official ROM, the same from when buy it) can check this, to confirm this line, if say the same with mine
[Magisk] D€INOS:
Yeah okay, when flashing the module, the pif.json was deleted, so that's one reason I got that wrong
[Magisk] thefinger:
Same happened to me. Actually been on "BASIC" only for the past week and wallet has been working without any issues. Store is also showing as certified. RCS does not work though
[Magisk] osm0sis:
Weird. Termux always gotta be different... 🙄

Does it work with that Termux one? Any way Termux has to use the actual normal Android shell PATH?
[Magisk] HippoMan:
It's interesting to me that Wallet is working for you, even though you haven't had DEVICE integrity for a week.

Is anyone else able to use Wallet for an extended period of time recently without DEVICE integrity?
[Magisk] zgfg:
At the end of the day, no matter which module you updated/installed snd/or which method or tool you applied today to get the new working prints

you have to say BIG THANKS to Xiaomi.eu, since all those now point to the same prints they quickly released today afternoon when they had to update the injector

On the other side, again, it's bad bcs we're all hanging on the same rope now
[Magisk] immortalwon:
Uber enforces strong integrity play integrity, which simply means you need a locked bootloader and unrooted. Good luck unless you have a 0-day exploit, which only the american NSA probably has.
[Magisk] Lione2:
Same on lenovo tablet p11 pro gen 2 A13 with 9.7 ( was ok on 9.6 )
[Magisk] shadowillusion:
There is some (risky) way to relock bootloader while maintaining root: https://github.com/chenxiaolong/avbroot

By risky is that not all phone support it and doing it wrong might hardbrick the phone.
[Magisk] immortalwon:
Yes, this method should never be attempted unless you have $$ to waste buying new phones or have a tool similar to MSM tool for one plus phones to restore the phone back to factory.
[Magisk] chiteroman:
Pushed new update, check 👍
[Magisk] chiteroman:
Uber driver needs:

✔MEETS_STRONG_INTEGRITY

So you must flash stock rom and lock bootloader. Unlucky :(
[Magisk] Lione2:
Same issue on both devices
[Magisk] Depressed T.Bear:
I'm on 9.6, the two possible checkmarks for play integrity show up and I can use all my banking/root sensitive apps and the Play Store shows 'device certified'.

However, all the different detection apps find stuff like 'abnormal environment', zygisk app process (even though I've Shamiko) or some kind of injection.

One of the main selling points for my current rom by the dev is the possibility to relock the bootloader while maintaining magisk root. It's a paid feature, so I haven't tried it yet.

I might do, once detections get more sufisticated. 😂
[Magisk] cloudpeople:
Xiaomi.eu marble came out with A13 and probably with displax 2.0 patch, without root it can only be basic in yasnac.

Is installing your module version 9.0 enough?
[Magisk] magaedy:
I think for any miui and xiaomi.eu v9.2 is the perfect build compatible with them
[Magisk] immortalwon:
This sounds interesting, let us know how it goes if attempted. But also be aware Google shills watch these threads
[Magisk] chiteroman:
Lol, sometimes PI passed and sometimes it did not. Seems like unstable process isn't the only who check system props. Well, latest update should fix all problems, also people with devices which in old versions gave problems I want to know if this build works for you.
[Magisk] Lione2:
9.7.2 fixed on both devices, thanks 👍
[Magisk] spida_singh:
Does anyone know if this module with kernel su+ zygiskonkernelsu work with starling?

@chiteroman what combination did you use to have starling not trip?

Masgisk

Alpha

Delta

With your 9.7 module?
[Magisk] chiteroman:
Starling detects resetprop utility, I recommend you to disable all modules if you want to use it.
[Magisk] magaedy:
Still on Shadowhook, Because for me I have better device performance with Dobby I don't know it is related to performance or not ?
[Magisk] aygul12345:
Make a donation to you, for updating this project. As I promised, by keeping update this wonderfull project I will support your project. ❤️
[Magisk] HippoMan:
... and we're likely to all get bitten in the not-too-distant future because of this single point of failure.
[Magisk] kornball:
Thanks for this! If I'm running v7 of your fork, I just need to run autopif.sh via something like root explorer on my phone? Really appreciate all your efforts.
[Magisk] osm0sis:
Oh absolutely. We wouldn't know it was just a mass ban without them having found a working print already so quickly. Full marks for speed! 🤘
[Magisk] bakaekze:
Can you elaborate what PixelOS inject looks like and why it's important please?
[Magisk] Wolfcity:
Exactly. Put autopif.sh and xiaomi.eu.apk in a folder, execute and you'll find a custom.pif.json.:)

Nice work @osm0sis !

Edit: Corrected.
[Magisk] kornball:
Ah okay, thank you! I did not realize there was another file needed.
[Magisk] Fishawy:
Sorry, where is that Xiaomi.eu apk?
[Magisk] osm0sis:
Just like all the other interfering ROM PI spoof injector apps, except a little trickier to mitigate because it's an overlay apk with a config.xml.

See my commit here:

Don't hide CertifiedPropsOverlay config.xml by default to not break GSIs · osm0sis/PlayIntegrityFork@34966f5

- GSIs and possibly other ROMs use /system_ext/overlay/config/config.xml with overlay package names and options - replacing/hiding either CertifiedPropsOverlay.apk or config.xml alone causes bootloops

github.com

There isn't. He got that part incorrect. My script downloads everything you need. You only need the script and to then run the script. 👍
[Magisk] Nergal di Cuthah:
Just to catch up, we don't know why the eu print passes when most (all?) freeman fail, correct?
[Magisk] osm0sis:
It passes because it wasn't banned. Yet. 😜
[Magisk] HippoMan:
That's correct.

My wild guess is that the Googlefrinchian Telephone Sanitizers may have performed a mass banana-ing at a certain point in time for of all the FP's that they knew about at that moment, and that the new eu FP just happened to show up a bit later.

If so, it would likely get hit by the next mass banana-ing, if there is one.
[Magisk] Nergal di Cuthah:
Yeah i don't want to use their print. But every freeman failed (tried five will try more when i get back to a pixel flasher).
[Magisk] Stillhard:
Trending apps :LOL:

View attachment 6074646View attachment 6074647
[Magisk] Nergal di Cuthah:
Yup use playstore, its checker has a higher threshold
[Magisk] osm0sis:
Yep, I'm on the hunt as well, but autopif.sh has my daily driver working in the meantime. 👍
[Magisk] D€INOS:
Is dalvikvm a dependency for autopif.sh?
[Magisk] kornball:
I don't know what went wrong, but I ran the script and rebooted. It didn't change anything with my custom print using your fork. I must have done something incorrectly.
[Magisk] osm0sis:
Yes, but it is part of Android, so as long as you aren't using Termux it's always available.
[Magisk] D€INOS:
:/sdcard # sh autopif.sh
Xiaomi.eu pif.json extractor script
by osm0sis @ xda-developers

- Downloading Apktool ...
Connecting to github.com (140.82.121.3:443)
Connecting to raw.githubusercontent.com (185.199.108.133:443)
saving to 'apktool_2.0.3-dexed.jar'
apktool_2.0.3-dexed. 100% |*****| 6958k 0:00:00 ETA
'apktool_2.0.3-dexed.jar' saved

- Finding latest APK from RSS feed ...
XiaomiEUModule_2024.02.29.apk

- Downloading XiaomiEUModule_2024.02.29.apk ...
Connecting to sourceforge.net (104.18.37.111:443)
Connecting to downloads.sourceforge.net (204.68.111.105:443)
Connecting to netcologne.dl.sourceforge.net (78.35.24.122:443)
wget: TLS error from peer (alert code 40): handshake failure
wget: error getting response: Connection reset by peer

- Extracting APK files with Apktool ...
autopif.sh[52]: dalvikvm: inaccessible or not found

- Converting inject_fields.xml to pif.json ...
grep: XiaomiEUModule_2024.02.29/res/xml/inject_fields.xml: No such file or directory
{
"FIRST_API_LEVEL": "25"
}
:/sdcard # sh autopif.sh
Xiaomi.eu pif.json extractor script
by osm0sis @ xda-developers

- Finding latest APK from RSS feed ...
XiaomiEUModule_2024.02.29.apk

- Downloading XiaomiEUModule_2024.02.29.apk ...
Connecting to sourceforge.net (172.64.150.145:443)
Connecting to downloads.sourceforge.net (204.68.111.105:443)
Connecting to netix.dl.sourceforge.net (87.121.121.2:443)
saving to 'XiaomiEUModule_2024.02.29.apk'
XiaomiEUModule_2024. 100% |*****| 12766 0:00:00 ETA
'XiaomiEUModule_2024.02.29.apk' saved

- Extracting APK files with Apktool ...
autopif.sh[52]: dalvikvm: inaccessible or not found

- Converting inject_fields.xml to pif.json ...
grep: XiaomiEUModule_2024.02.29/res/xml/inject_fields.xml: No such file or directory
{
"FIRST_API_LEVEL": "25"
}
:/sdcard # sh autopif.sh
Xiaomi.eu pif.json extractor script
by osm0sis @ xda-developers

- Finding latest APK from RSS feed ...
XiaomiEUModule_2024.02.29.apk

- Extracting APK files with Apktool ...
autopif.sh[52]: dalvikvm: inaccessible or not found

- Converting inject_fields.xml to pif.json ...
grep: XiaomiEUModule_2024.02.29/res/xml/inject_fields.xml: No such file or directory
{
"FIRST_API_LEVEL": "25"
}

Is dalvikvm a dependency for autopif.sh?
[Magisk] osm0sis:
It generated the file, you still have to put it in the right place.
[Magisk] osm0sis:
You already asked and I already answered. 😜
[Magisk] D€INOS:
Okay I can't use Termux, what is easiest instead of Termux?
[Magisk] kornball:
Thanks, I'm dumb lol
[Magisk] GabbyWC:
FX File Explorer works nicely with .sh scripts. It needs root access for autopif.sh to function correctly.
[Magisk] Gilg@mesh:
generated with Termux, the right place is? Thanks. :) I guess it's the custom.pif.json that should be moved?
[Magisk] osm0sis:
First, don't use Termux. Next, RTFM my dudes.

GitHub - osm0sis/PlayIntegrityFork: Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - osm0sis/PlayIntegrityFork

github.com

See back 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] gj4560:
Hello everyone,

Have there been any major changes to the process for this? Asking because I noticed the fingerprint I've been using for a while now (set with PIFS) no longer passes device integrity so I have been trying to set a new fingerprint using PIFS but after 10 or so attempts I can still only get basic integrity passing. I am using Play Integrity Fork v7 on my Pixel 7 Pro with the February 2024 update.
[Magisk] bakaekze:
Essentially, the process is the same, but there are a lot less working fingerprints now.
[Magisk] Iridule:
I think there are maybe less than 20 prints online that work. I've tried about 70 all fail. That's not including the 50 I had that were all burned. I'm guessing hundreds, possibly thousands of prints no longer work. Some of mine were from private devices others were from very obscure websites that had to be translated in order to navigate and then the API of a found print had to be tweaked. All gone in one day. :(
[Magisk] bdr127:
My dozen prints I got back on December 3 all not passing DEVICE anymore... All of them were manually extracted from ROMs of relatively obscure unrelated devices from various global websites, not just build.prop files in a public repo. Some of those ROMs required third party tools to decompress/extract the img files. Everything from Android 6/First API Level 23 to Android 9/First API Level 28. And I've only been using one of them since December, yet they're all now dead. :(

Using the Xiaomi.eu print for now like everyone else.
[Magisk] D€INOS:
autopif.sh with Terminal Emolator works great , reverted back to @osm0sis v7

Overall I think this might be the end of the line seeing that so many fp stopped working. Hopefully something revolutionary is developed otherwise Google have more or less won.