yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
Ok so now seriously:

- I tested now on my same phone and the same ROM (Xiaomi.eu MIUI 14/A13)

- by using the same PIF Fork v4 and my same automated script for Terminal Emulator::

Etc/pif-test.sh at 01eb87469130f15d186b06528f42620d06ad8242 · zgfg/Etc

Et cetera. Contribute to zgfg/Etc development by creating an account on GitHub.

github.com

(Script supports PI Fork up to v4 and/or PI Fix version that was actual by XMas or so - I stopped then with adaptations for newer PI Fix/Fork module versions and their ever changing formats)

- I have just retested a bunch of 236 PIF JSons that all did pass Device Integrity last time when I mined them over Dec 28 /29 night

Now, of those 236:

139 still pass Device Integrity

97 failed - passing now only Basic Integrity (and downgrading FIRST_API_LEVEL did not help)
[Magisk] osm0sis:
Mine hasn't changed since v5... 🙄

What we have in v5+ was pretty much always my roadmap for supporting all Build fields and all System properties. No need to change it ever again because it's futureproof for all of those things.

Plus it automatically migrates old format to new.

Plus in v6+ I added your feature request for disabling ROM injector apps, but made it customizable/extensible like all the rest of my features. 😉
[Magisk] beardedwonder:
I have tried doing this with one from each manufacturer and no joy!
[Magisk] zgfg:
But by that time I already had hundreds of the mined Jsons, so I stoped spending further time on that game
[Magisk] osm0sis:
Not a game. I'm all done. Nothing needs to be changed ever again since it's futureproof for all fields and props. See my previous post again for my edits.

And for those who have old collections:

sh migrate.sh <path/to/custom.pif.json>
[Magisk] CZ.Kostra:
I also tested my collection today and approx. 30% of FPs are broken.
[Magisk] :
Do those 97 have something in common?
[Magisk] zgfg:
I know all that - but my script takes one by one, adapts from Fork v3 to v4 format and then test

And it downgrades first API level if passing Basic but not Device. Now it would have to ve adapted for the new format, and implemented downgrading for diff property in the script

Since I still have hundreds of passing JSons and since they work fine with your old v4, I don't need to bother ATM

I mentioned all that, if anybody wants to download and use the script (it works nice, automatically using YASNAC + SPIC, crawling through directories, writing statistics of the tested files, etc), he would have to apply these adaptations for the new format

Or keep the script as is but by testing with Fork v4, and then run your migration script over those JSons that passed with the script and v4 - I give my hand that 99 99% prints that pass with the old v4 would also pass with your latest, and vice versa (that's the substance, the rest is just about adapting for one format or another)
[Magisk] zgfg:
Various manufacturers, various Sec Patch and 1st API level, at the first glance I don't see any specific pattern
[Magisk] :
Mined from the same source?
[Magisk] HippoMan:
My FP from early December has now finally stopped yielding DEVICE integrity some time since my previous check on February 11. It was from an old, offbrand device running Android 6.0 with API level 23.

I have another FP from a device of a popular brand which originally ran Android 10 with API level 29. After setting this PF to API level 25 and installing it, I'm back to DEVICE integrity again.

Based on this and some other recent reports here, it looks like the Googlefrinchian Telephone Sanitizers have indeed made another FP banana-ing effort lately.
[Magisk] V0latyle:
What's the common theme among these, though? Does it seem to be mainly 6.0/API 23?

They've probably just ended CTS support for the older API level, so maybe they're doing a "rolling drop" sort of thing where they will progressively drop CTS for older API levels. So maybe it'll be 7.0/24 next, then 7.1/25...?
[Magisk] PatrickJK:
I was using a print from 8.1/api 25 that has been banned after 2 months. Switched to a print from a rom thats 7.0/api 24 and it's now working again, so at the moment I don't think the version matters either
[Magisk] V0latyle:
Where did you get that 8.1 print from? Any print that is in common use is likely to get flagged sooner, so if you were sharing the same print used by a lot of other people, that's probably why.

My point was that if 6.0/23 is now unsupported, 7.0/24 will quite possibly be next.
[Magisk] HippoMan:
Yes, it seems like this might indeed be the methodology which is being pursued by the Telephone Sanitizers during this current banana-ing effort.

Time will tell.
[Magisk] :
OT: Why do I still see "various Sec Patch and 1st API level" while in my quote there's "various Android versions" ? I guess you've edited your post, but even after almost one hour xda doesn't show? Strange.

So they don't have an Android version in common?
[Magisk] PatrickJK:
I mined it myself from one of the bigger rom dump repos. I haven't shared it but others could have easily mined it and shared it. I avoid using publicly shared prints.

I did just now switch to a pif from a different device that was from the same manufacturer as my banned pif, android version 6, api 22, and it's passing device.
[Magisk] HippoMan:
More OT: Are you sure it isn't the opposite (where "various Android versions" is what actually appeared in the *original* message before later having been edited to contain the other text)?
[Magisk] zgfg:
Back in Dec, they were mined from dedyn (it had thousands of JSons, mostly never working but that link is dead now) and they were based on Tadi***** dumps (AFAIK, link was banned here but it can be found in the TG Dumps Channel) - now I retested from my copy with only those JSons that passed for me back in Dec
[Magisk] sawdoctor:
My fingerprint working from end of November is still working. It is from a firmware dump that shouldn't have worked but did by changing the 1st api level to something lower. So definitely think your on the right track and it's earlier devices getting banned.
[Magisk] CZ.Kostra:
I had FPs banned from various Android versions: A6.0.1, A7.0, A8.1.0, A9, A10
[Magisk] zgfg:
They have various Android versions

Btw, I will probably not count now over those two hundreds (I would rather unpack another zip with the previously mined JSONs and retested them these days again), but as I mentioned in an earlier post today when I initially re-tested only couple of them, among those few there was one with A 5.01 and one with A 6.0 1 that still passed today (they were originally mined from MHCP back in Dec)

In that batch I had 5 others with Lollipop and Marshmallow that didn't pass today, but I was not 100% sure did that my zip contained really only that passed back in Dec, so I unzipped the other zip (documented with the results from original adapting, testing and filtering), but among those 236 majority are A7-A9
[Magisk] sawdoctor:
Mines A10 but from 2020 . If I'm correct it released with A10 so shouldn't really work (presuming I've understood everything correctly)
[Magisk] Nergal di Cuthah:
My self found fingerprint (found on xda) is basic only now. Initial sdk is 27. To my knowledge, others weren't using it. Will try freeman's later, i dont google pay so not urgent.
[Magisk] zgfg:
Not really, there are some A10 that pass and I mined back in Dec even very few with A11 (but you really have to mine over dumps from various vendors, and some obscure ones)
[Magisk] CZ.Kostra:
The device was built with A8.1 but got an update to A10.
[Magisk] justDave:
I keep seeing this sentiment...

I discovered yesterday that RCS stops working if Google detects that you're rooted. It's subtle too. Settings still shows you're connected to RCS but sending and receiving fails.
[Magisk] Nergal di Cuthah:
Yup, i use textra so no RCS done by me. I do use netflix and other drm apps so i do need to fix, just not immediately.
[Magisk] osm0sis:
There are working Android 12 prints, just for everyone's knowledge, but you need to lower the INITIAL_SDK/FIRST_API to get them to pass.
[Magisk] zgfg:
Yeah, you can have a device with a dozen of dumps from its various OTA upgrades spanning over two or even three Android versions (and the corresponding Sec Patch levels with dates spanning over two years), some of them pass and some not, and eg some older don't but newer do
[Magisk] sawdoctor:
I know, was just making the point that "they're not supposed/expected to work as they weren't shipped with android 8.1 or earlier.

Hopefully we can find a pattern to which prints are getting banned, that's what we're all trying to do
[Magisk] pedritopl:
Look @osm0sis - at least I know I'm not alone with this problem and I confirmed that older Shamiko works fine. The problem is only present with Shamiko v1.0.0 & 1.0.1. :)

[Discussion] Magisk - The Age of Zygisk.

This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...

xdaforums.com
[Magisk] xSnowLeopardx:
Crazy how my first found FP is still alive. I check it every day. Will have to check what my collection says.
[Magisk] zgfg:
But I was now looking into the one with A11 (from 2021), Sec Patch Jul '21, and it (still) passes with 1st API level A30 (=A11)

So the rule is - there are no rules but mine pedantically 👍
[Magisk] sawdoctor:
Been reading through the thread and can see it's affecting some people and not just you. Like osmoSis latest shamiko on latest magisk canary isn't causing me any issues. Must be something connecting you all that are having issues just got to figure out what you have in common
[Magisk] purgy:
Well after all the "my FP I mined myself is ded" posts, I got paranoid and checked, still all good on my second FP since my first (Gionee) was unfortunately used by xiaomi.eu (aside from the kernel name shenanigans).

First API is 25 if that adds anything to the pool of useful info?

TJW magisk 27.0, osm0sis' pifork v7.
[Magisk] aNGERY:
I'm working right now and was only able to skim the thread.

Basically they banned the fingerprint I was using and I should be able to edit the current pif.json file with another fingerprint and proceed until Google bans that, right?
[Magisk] trevtdogg:
yes
[Magisk] Toronadian:
Apologies if what's happened to me is completely normal, but I've only been occasionally reading this thread here and there and stopped using Google Pay after they started cracking down on things. I never dabbled into creating a fingerprint with a different device etc, just updated the module whenever.

For the last 2 months or so, Google Wallet just said it "didn't meet device security requirements" or something along those lines, but had been mostly too busy to go through all the steps to make it work again. Didn't bother me too much.

Last week, I updated my Pixel 6 to the latest monthly update (Feb 2024), and rooted it with the latest stable version of Magisk (27.0), and also installed the latest version of this module (15.7.2). I've also hid Magisk and configured deny list to include Google Wallet. First day or 2 after updating, the Wallet still had the "didn't meet device security requirements" warning. But randomly after, the warning went away and it appeared that it was working again. I tested it at a store today and Google Wallet worked again.

I'm surprised it worked as like I've said, after my initial monthly updates/re-rooting, it didn't work, but suddenly it did again. Is there any particular reason it has?
[Magisk] aNGERY:
Alright what the heck is going on now :(

My 9 pro works fine with this pif.json. 10 Pro not so much

View attachment 6068221
[Magisk] trevtdogg:
chiteroman's module has been sometimes including a working shared print (working temporarily until it no longer does) and sometimes not.

the latest version has a currently working print, so that's why.

the modding community is somewhat split on if shared prints should continue to be provided (for ease of use), or if people should have to find their own (to reduce the rate and number of burned prints).

the majority here at xda seem to be on team 'find your own'.
[Magisk] Ferdimage911:
For weeks I have not had one issue with Google wallet after installing playcurl module and Fp_downloader.apk , combined with Chiteroman's fix.
[Magisk] SOCOM-HERO:
Well, my FP from early december was banned. Got a working one after a few tries. Not fun.
[Magisk] cubandanger05:
Still going strong with custom pif :DView attachment 6068264
[Magisk] purgy:
Do the phones have different ARMABI versions? V7, V8 etc.

I remember reading that may be relevant
[Magisk] Umgak:
You're failing BASIC, which means that something is wrong with your setup. Try disabling other magisk/xposed modules other than this one. Ensure that Google services aren't denylisted. Ensure that your kernel is not on the list of known banned kernels, if you are using a custom ROM or kernel.

Edit: removed incorrect information about using PIF with no spoof at all. That will not yield Basic, but rather an infinite loop.
[Magisk] pndwal:
FWIW, some prints do now break BASIC_INTEGRITY if used in PIF, but as soon as you append any spurious characters (or change fingerprint value to gobeldygook), only DEVICE_INTEGRITY (and STRONG_INTEGRITY) will fail if that was the issue. 👀 PW
[Magisk] olajbogyo:
Hello! My Google Wallet was updated 06.02.2024 and has not worked since then. The Play Integrity fix 15.7.2 does not work. Google Wallet app locked due to root. Can you help me? Thank you.
[Magisk] majorfigjam:
You can help yourself by reading the PiF FAQ down below ( on a phone) or to the right ( on a computer).
[Magisk] omokas:
My previous FP using the osmosis pickaprint.sh worked for 2 months now it got banned. With many tries I found another working one ,let's see how long this one will be passing device

Redmi Note 9 Pro MIUI 13.0.4

Osmosis fork v7

Magisk v27
[Magisk] osm0sis:
Banned kernel only fails device integrity as well. 👍
[Magisk] Matthew3955:
What's happened after I adding finger print from samsung to xiaomi with magisk hide props

P.S Sory my English
[Magisk] purgy:
Magisk hide props module is obsolete for this, you want either the module linked in the 1st post or one of its forks.

Have a look at this post https://xdaforums.com/t/pif-faq.4653307/ maybe run it through google translate.
[Magisk] zgfg:
FYI, FPs passing Device Integrity .

You can see Android versions and Sec Patch Level dates, the rest is masked (hence they cannot be used as below):

A13:

"FINGERPRINT": "nnnnn/CN_P*****/P*****:13/TKQ1.2*****.001/20230704.2*****:user/release-keys"

"FINGERPRINT": "nnnnn/CN_P******/P******:13/TKQ1.2*****.002/20221229.0*****:user/release-keys"

"FINGERPRINT": "mmmmm/mmmmm_20_CN/mmmmm20:13/TKQ1.2*****.001/1*********:user/release-keys"

A14:

"FINGERPRINT": "nnnnn/N*****/N*****:14/UKQ1.2****.001/20231121.2****:user/release-keys"
[Magisk] aNGERY:
i deleted the module and my pif.json, i used the default xiaomi one in pixelflasher and now it's passing
[Magisk] :
Strong OT 😉: but it doesn't even say "last edited:"?

Maybe just a glitch in the matrix. I can't even remember taking the red or the blue pill today....
[Magisk] :
🤔

Could be interesting to re-test those 97 in a few weeks to see if they get unbanned like we've partly seen before.
[Magisk] CBMC:
Every fingerprint I've tested from the biggest online dump site has been blacklisted. Thinking Google targeted these first?
[Magisk] Umgak:
It's possible, but I wouldn't be surprised if it's also just that publicly dumped props are much more likely to be in use by people spoofing. The very first print I ever even attempted to use is still working, but it isn't in any public dumps. All of the prints I generated from my script that were in one of those dumps have been restricted for some time.
[Magisk] Nergal di Cuthah:
@TheFreeman193's script worked for me on first try. Thanks freeman and @badabing2003 for PiF Manager in PF and of course @osm0sis for fork and chit and disp[lax and evryother developer and tester involved. TLDR: Thanks all
[Magisk] badabing2003:
You either tested only a handful or have a setup issue (perhpas Kernel on blacklist?). Have you tested with xiaomi print to make sure your setup is functional?

Definitely not every one of those is blacklisted.
[Magisk] BunnyPig1:
One of my FPs just got blacklisted.

Using a fairly known brand on my secondary phone and it doesn't pass DEVICE anymore.

Worked for about 1,5 month (31/12/2023-14/02/2024), worked with API-LEVEL 00.

I've tried with 25, 24 and 23 just to make sure, but seems to be dead.

Just adding this for statistical purposes.

Edit: might as well mention that my FP I'm using on my primary device is still good, been using it since 20/12/2023 and got it from the popular dump site. So all prints are not banned.
[Magisk] CBMC:
I had tried about 20 prints at that point. Almost all where on AP level 23-27. Eventually found a working one.
[Magisk] Umgak:
Decided to do some testing, since I haven't done any since December. Mine hasn't broken, so I haven't needed to, really.

From my original stash of 39 known working prints, a whopping 26 have been restricted, leaving me with 13 remaining. Interestingly, every single new restricted print was an open beta print.

My original round of dumps contained 29 "Open Beta" and 29 "Stable" builds. Of them, 1 "Open Beta" and 18 "Stable" were restricted. Now, 27 "Open Beta" and 18 "Stable" are restricted.

Also, sorry to anyone trying to use SPIC tonight. My bad.
[Magisk] zgfg:
Tested tonight another bunch of my previously working custom pifs, 99 of 232 are banned as of now

Tested under the same conditions as a 1,5 month ago when they worked. And downgrading 1st API level (for most it was already since my original mining) does not help

They go from Device Integrity down to only Basic Integrity.

But interestingly (I also observed in the first test) few of them went down even to No Integrity - I retested them, and got the same. What bothers me, they pass CTS with Basic Attestation in YASNAC but fail Basic Integrity in SPIC and TB-Checker (I double-checked with TBC)

...

Various vendors, Android versions and so - I still cannot see any pattern, just it looks that G tests on their side and once they find (and decide that it will be safe), they close one by one loophole

Sad that I found relatively a lot banned from one low-budget CN vendor that AFAIK has never been mentioned here (not even mentioned and then the name removed from the posts, and apart of their specific subforums and threads, very, very rarely in other threads like Magisk General and so).

I had (still have) many custom pif jsons with their prints

...

Btw, now while they shrink, I looked better under those that remained, and found that I actually have 3 working A13 prints and one A14

And yeah, they have all Sec Patches from 2023 (one from 2022)

All the three A13 require 1st API level downgraded to 25, but the A14 works with 1st API level 32 (Android 12L) - btw, from the same CN vendor mentioned above (name disclosed)
[Magisk] sawdoctor:
Just a heads up. I've read latest zygisk next update breaks device integrity and also chiteroman last bundled fingerprint has just been banned as well
[Magisk] Matthew3955:
Where i can get system dump fore Redmi Note 10 pro (sweet)
[Magisk] GabbyWC:
I can't speak for the original pif.json that comes with chiteroman's PIF v15.7.2 release. However, osm0sis' PIF Fork v7 and the Xiaomi.eu fingerprint which was extracted with his autopif.sh script and converted with his migrate.sh script passes device integrity. I also tested the pif.json from chiteroman's zip file after running it through the migrate.sh script and it too passes device integrity with PIF Fork v7.
[Magisk] Lord Sithek:
didn't break it for me
[Magisk] majorfigjam:
Have you tried searching for "redmi note 10 pro sweet build.prop"? I did, and found one.
[Magisk] Matthew3955:
I just don't know which site to trust
[Magisk] majorfigjam:
Well in that case, I respectfully suggest that you give up, revert to stock, and relock your bootloader.

This whole thread is about deception, after all.
[Magisk] chiteroman:
View attachment 6068678

Fingerprint still works...
[Magisk] xSnowLeopardx:
At this point, I am waiting for mine to be banned, too.
[Magisk] sawdoctor:
Just what was posted in a certain devs telegram group
[Magisk] tom1807:
Well, well, well.

Out of curiosity I tested my 20 fingerprints and 6 out of 20 failed.

4x Google Devices, 1x Nokia and one China print.

Two Google devices were Android 7 and first API 24, the other 2 were Android 7.1 and first API 24, the Nokia was on Android 8 and with first API 24, and the China device Android 8.1 and first API 27.

Changing these to first API 25, didn't help.

But... (and that's a big but).

Played with Cleanup DG in Pixel Flasher and now all my FPs are failing incl. Basic.

Checked \data\data\com.google.android.gms\dg_cache and 2 updated files are showing up.

So, I guess I have to wait up to 24 hours or delete the storage from Google Play Store.

Cheers

Tom
[Magisk] badabing2003:
After doing Cleanup DG, run YASNAC once or reboot.

I prefer running YASNAC once, and you should be fine.
[Magisk] tom1807:
That was easier than I thought. Back in business again with my FP from December.

Cheers

Tom
[Magisk] :
But thy may still work on another device or be working again if the ban is temporary?

What if... they introduced some kind of score for every device? Let's say 3P and you're out (DEVICE attestation).

kernel string means unlocked bootloader - 3P (directly out)

using wallet (or other critical apps) - 1P

frequent integrity checks - 1P

using a frequently used fingerprint - 1P

... (magisk/zygisk/shamiko) ...

Am I thinking in a totally wrong direction or is this just not feasible?
[Magisk] osm0sis:
Maybe don't quote it either. 😛
[Magisk] Oswald Boelcke:
Hello and good good afternoon, @candrariyanto Welcome to XDA! I hope you'll always get the support you require and have enjoyable times on our Forums.

However, I've edited your post! Edit or change of IMEI is illegal in quite a few of countries. XDA doesn't allow and doesn't accept discussions about or support for such an edit or change.

XDA Forum Rules (excerpt):

Please refrain from such support requests on XDA in future. Thanks for your cooperation!

Regards

Oswald Boelcke

Senior Moderator
[Magisk] osm0sis:
This isn't a search engine, it's a forum..
[Magisk] Spartacus500:
For me also works ☺️
[Magisk] Lord Sithek:
Moment ago I tested 10 prints I mined two months ago and only 2 of them still passes DEVICE. Well... The noose around the neck tightens
[Magisk] Nergal di Cuthah:
Please be clear about what you are trying to say. We can't help unless you do. If english isn't your primary language use google translate to give us a clear and informative post.
[Magisk] V0latyle:
And, make sure you're following the Forum Rules, especiially Rules 1 and 5:
[Magisk] trevtdogg:
so what is the latest thinking about how 'universal' fingerprints work these days?

there's been more and more examples of users where a fingerprint works for one device but not for a different device.

how are devs like xiaomi mod team and chiteroman finding "universal" prints? how many different devices do you need to test on before you can be fairly certain it's a universal print?

and what about the usability of non-universal prints? a lot of people have recently discovered that a large number of previously working prints no longer work - but how many of these are "universally" dead vs just no longer working for that particular device?

is there any way to know?

could we start to see some private sharing of recently banana-ed prints to see if they are universally banana-ed or just for some devices?