yashsingh1/xdaforums huggingface dataset:
[Magisk] zgfg:
You cannot find/open post #1 on the page #1 in this thread?

Btw, one of the main rules on XDA (and other forums) says, please read the OP= Original Poster (author) posts before asking

Screenshot below
[Magisk] wolfsoft81:
No more idea for try bypass this ?
[Magisk] chiteroman:
Lock bootloader, any public exploit will be patched by Google.
[Magisk] chiteroman:
Fixed in last update.
[Magisk] Reynald0:
Dobby is back, why don't split it in two variants with shadowhook and Dobby? =)
[Magisk] osm0sis:
All I see is

😂
[Magisk] ykjae:
With magisk alpha 26203 and latest shamiko and latest pif 9.7.2? I'm passing and able to access Microsoft apps. And all banks apps I use. Also using hma though.
[Magisk] magaedy:
Installed latest build v9.8 and everything is good with no root detection and also based on Dobby, Thanks man
[Magisk] zgfg:
¡ No pasaran !

View attachment 6024695
[Magisk] m0han:
This could make a good wallpaper. :cool:
[Magisk] chiteroman:
It is very strange that applications can read the symbol table and find DobbyHook because the zygisk library will close itself if the application is not a GMS process. I think people need to update Zygisk (and Shamiko) 😜

I will try to compile it as Shadowhook so that the symbols are not in the symbol table and publish it as a preview version, as long as this version works there is no reason to publish a new version.

View attachment 6024794
[Magisk] koshakm5:
Hi, can't pass device integrity test

Have magisk 26.1 installed, miui 12.5.1 android 10
[Magisk] chiteroman:
Can you send me the build.prop file? It's weird because you can't pass DEVICE verdict but it's licensed :eek:

You can get it: adb shell su -c cat /system/build.prop > /sdcard/props.txt
[Magisk] chiteroman:
Can you pass DEVICE verdict using this? https://github.com/Displax/safetynet-fix/releases/tag/v2.4.0-MOD_1.3

It's very strange...
[Magisk] koshakm5:
I tried mod_2.0 with the same result, do I need to try mod_1.3?
[Magisk] spida_singh:
@chiteroman

Just re-tested Starling, and it trips with 9.8

Using Kernel SU 0.6.9

ZygiskNext v4-0.8.1

Pixel 6

LineageOS

Though i have since removed the module as I only need PI to pass for Google Wallet, which I can live without, need Starling more. I just liketo test progress.

Im hoping at some point you can get Starling working with this module without it tripping :)

Thanks again for your efforts on this, great work!... I have just donated Cheers
[Magisk] chiteroman:
Starling detects resetprop utility, just remove service.sh and should work.
[Magisk] Hkntai:
9.8 seemingly doesn't work for me so I rolled back to 9.7.3 and that one works well. Can confirm starling works while using zygisk and play integrity works too

(I had to change starlings SSAID to get it to update properly)
[Magisk] pndwal:
To be clear, by "when banks finally flip the MEETS_STRONG_INTEGRITY switch" thus making MEETS_DEVICE_INTEGRITY irrelevant "the lights will surely go out here", I mean the [MODULE] Play Integrity Fix (SafetyNet fix) will also become an irrelevant has-been irrespective of the specific app polling a PI MEETS_STRONG_INTEGRITY verdict... Once an app deems the collateral damage acceptable and and requires this verdict to run, the only Play Integrity Fix will be to revert to stock/locked Android.

Of course rooting itself is not equal to bypassing proper deviceIntegrity attestation, and the lights will certainly remain on in modding threads not aimed at manipulating security signals or bypassing this security mechanism by subterfuge. 👀 PW
[Magisk] PandarianFury:
*Important*

Magisk needs to be up to date for v7 to work

Special thanks to @GabbyWC and @Vision for being patient with me and assisting me. Please reach out if anyone else needs help
[Magisk] HippoMan:
Yes, that was clear and understood.
[Magisk] osm0sis:
You can technically delete them, yeah. It'll recreate them next time you run it.

Sounds like you forgot to copy the file over? You still need to move the correct generated file for the PIF module you're using into wherever the module wants it to be. Not sure why people keep missing this step, it never says anything about copying the file, and I think users should be responsible for that step.

If you did copy the right file over then something else must be wrong in the setup.

PIFS/pickaprint.sh doesn't do the same thing as autopif.sh.
[Magisk] GabbyWC:
12 GB of RAM isn't enough? 🤨 I'll stick with custom ROMs for years to come but perhaps you and I can agree to just say "hell no" to iPhones. 📵 I'm waiting on the announcement and release of the Poco F6 midrange phone which is rumored to be powered by the Snapdragon 7+ Gen 3 SoC. It certainly won't cost as much as a flagship phone. If you think that receiving only four Android OS updates is lame, forget about Motorola with just one or two. 🙄
[Magisk] carlese:
Now it's clear.. I copied the custom pif and my devoice meets BASIC and DEVICE integrity again, thanks a lot!
[Magisk] Lubo99:
guys mim fungerpint worked untill today. today i was not able to pay by google pay... you know the drill... i tried to install chiteromans 13 module and deleted fingerprint but it does not seem to work. of course i overlooked something. :D what is it?

it works now lol

/data/adb/modules/playintegrityfix/pif.json

/data/adb/pif.json

playintegrity directory is where it needs to be removed...
[Magisk] zgfg:
v13?

His latest is v15.9.3 - that one includes now the hardcoded working prints (remove your own pif json)

Prints in the older versions are gone
[Magisk] droidman1992:
It depends on your expectations of performance and longevity, if you charge obscene amounts of money like Samsung it is reasonable to expect the best specs, not only good enough and since today's phones are so good, I think 7 years is right in line with what a user should expect for flagship update length, especially as custom ROMs become unviable.
[Magisk] Iridule:
Yeah I realize the point but I didn't ask to publicly share the print just the dump site. Because if you can Google "Android dumps" "Android system dumps" everything that shows up from any of the sites are all not working. I have systematically tested nearly 250 prints. All 50 I had working were lost a few days ago. I was just curious if @osm0sis got the print from a device they had or from googling sites. Even if you try the Chinese sites and translate them none of the prints work. I'm going to get carpal tunnel before I find another working print.
[Magisk] osm0sis:
That's in the README... Just saying. 🫤

PlayIntegrityFork/README.md at main · osm0sis/PlayIntegrityFork

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

github.com

I've also just tidied up the autopif.sh post to hopefully help with the poor reading comprehension we've been seeing, e.g. people wrongly thinking the old PI NEXT script I referenced at the top was the one I was telling them to download... 🤦‍♂️🙄

🔧 [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

Same places we all got them before, but yes, there are a lot fewer working.
[Magisk] Lubo99:
yeah yeah 15.9.3 is the right one... i pass device integrity and added both bank cards.
[Magisk] mates21:
I installed the latest version 15.9.3 on my mi9 (Magisk 24) but I have device failed. Why?
[Magisk] GabbyWC:
Magisk 24? You're seriously out of date with that version which was released over two years ago. Update Magisk to the current release (v27.0) and try again.
[Magisk] pershoot:
https://github.com/topjohnwu/Magisk/releases/download/v27.0/Magisk-v27.0.apk
[Magisk] mates21:
Unfortunately, I cannot change to the new version because the new version of Magisk does not work on Mi9. so far my print on v14 has been working.
[Magisk] Vision:
Exist and the Kitsune Mask have and a stable version https://github.com/HuskyDG/magisk-files/releases/tag/v26.4-kitsune-2

Maybe this version work for you
[Magisk] rseiler:
I just tried it and it worked well, with a surprise that I can't really explain: after copying over the custom pif to the right location for v7 (which I'd been using for a while with a print I found several weeks ago), I forgot to reboot first...but it passed device anyway. My previous print, which should have still been in effect without a reboot, no longer did as of yesterday. I guess something about the script somehow made that happen.
[Magisk] Vision:
Without reboot

For quick and easy test if FP working, send the new custom.pif.json file to /data/adb/modules/playintegrityfix and replaced the existing, go to setting/apps, found the Google Play Services and click force close (no need close the internet etc.) (i try it this with Total Commander the replace, you can with your file manager you have) after do the test if pass 2/3
[Magisk] mates21:
All right. I copied the print to v15.8 and it works :)
[Magisk] FrogMaster-:
I intentionally omitted deleting that file because it is a requirement every time the tool is run. It's pulling the exact same jar file each run if it's not present, so rather than have it pull it every single time I figured it would be better for it to remain.

That block of code can be pretty quickly updated to remove the jar file as well though if you feel it necessary.

The Xiaomi files will eventually change, which is why I wanted them cleaned up. They're no longer necessary once the FP is extracted.
[Magisk] djcsurf:
Time to change from chits to osm0sis fork, it's installed but i need to add custom pif. I know it's been posted before but my search isn't finding it, can someone give me the location to place it in. Tia
[Magisk] Vision:
View attachment 6075376
[Magisk] Captain_Throwback:
Did you look at the README in the place you downloaded it from?

@osm0sis i just checked the PIFork README, and interestingly you don't explicitly state to put the custom.pif.json into /data/adb/modules/playintegrityfix. It is inferred a couple of times, but you may want to add an "instructions" section of some sort to alleviate any confusion.
[Magisk] djcsurf:
I did, I read it said place in the module directory but wasn't sure of its location. Regardless now done so thanks to Vision.
[Magisk] mates21:
does anyone here use their own print or does everyone use chiteroman's print? :)
[Magisk] norberto_:
Damn 2 of my fingerprints just stopped working. They were working since osmosis fork v3 that was the time i found them and were working till today. ☹️ Need to find more working one.
[Magisk] Vision:
Welcome to the club 🥲
[Magisk] zgfg:
Good luck, hundredths are gone. Seems that very, very few are left

Better look for what was discussed here last two days and go dor the now only a single publicly known working prints, either by using eg autopif.sh, PF or the latest PI Fix version with the hardcoded prints
[Magisk] wrongway213:
You guys think this thread would be over/under 100 pages if everyone read before posting? Normally i'd hesitate to post something like this and contribute to the spam, but since 8/10 posts on any given pages are people "informing" us that their fingerprint doesn't work anymore, that doesn't seem to matter anyway.

TL;DR Sure would be nice if people would read/search before posting.

If only there was a rule about this... (definitely not rule 1)
[Magisk] Vision:
And this very few left, if Google block it ? That's it the game ? We lost and not pass 2/3 ?
[Magisk] bdr127:
I'm on Magisk Canary v26402, and osm0sis' PIFork v7 works for me. 🤷‍♂️
[Magisk] pershoot:
You can think of it as a stress test on the new XDA server(s) ;)

But ya, its a huge thread.
[Magisk] wrongway213:
I think of it as a thread that could seriously use some moderators to begin enforcing Rule #1 so those of us who do read and search don't have to wade through ~15 pages of uninformed rule breaking each day to read ~5 - 10 pertitent posts - because that's exactly what it's been allowed to turn into. I was sort of hoping my casual pointing out of that fact above might lead to positive change, but maybe I need to spell it out a bit clearer - so here I have.
[Magisk] Slim2none4u:
THANK YOU!
[Magisk] i5lee8bit:
Actually not chiteroman's but Xiaomi.eu team's.

osm0sis has already mentioned he found one (maybe more).

I also found [more than] one. But, and I hate to be the bearer of bad news, I feel like there are even less than the semi-arbitrarily estimated 5% of working prints remaining. This was after just one ~2 hour session of mining prints for the first time since late Nov / early Dec, but based on my results from my crazy little process I do, just a week ago (pre-mass-Feb-29-ban) I would have came up with literally dozens of working configs in that time span. But this time around, let's just say I'm still in the LOW single digits. And I'm not planning to go any further this time.

I won't divulge my exact process for obvious reasons, but let's just say the props I obtain are not from easily obtainable sources (well, they are, but requires specific knowledge to be able to extract), and I have a knack for pattern recognition and so I could extrapolate multiple working configs without even having all the unique build props. I've already said too much. But just know osm0sis already mentioned he got his working prints from the same sources used before (which doesn't sound nearly as exclusive as my sources). Search his old but recent posts and you'll find some hints in terms of which initial sdk / first api and Android launch versions to look into for highest success.

There's still working configs out there, people. But it's a HUGE pain in the @$$ now compared to before. And unfortunately, the chances of keeping a low bar of entry seems to keep slowly disappearing (i.e. the bar is only continuing to get raised, despite all the efforts by people to make tools to allow anyone to find an easy working print).
[Magisk] Hisucchi:
Welp, that lasted exactly 3 months. Thankfully I made it a habit to check verdict via play store check before humiliating myself again by getting the payment rejected multiple times... And back to this thread I go.
[Magisk] osm0sis:
Aw man,

"fill out the included template example.pif.json from the module directory then rename it to custom.pif.json"

and

"ensure the filename is custom.pif.json and place it in the module directory before upgrading"

aren't enough?

The low reading comprehension is really hurting my soul today. 🫤
[Magisk] Captain_Throwback:
That assumes that people know what the module directory is, which, to be fair, isn't specified anywhere in the document...
[Magisk] Vision:
You have right, i think the most noobs (include myself in past) not know where is module directory

But this directory manage by Magisk who create the directory data/adb/modules
[Magisk] osm0sis:
People use Magisk and don't know where the files go?

Ackkk my soul. 😵
[Magisk] Captain_Throwback:
This isn't our XDA from years ago - as I know you know, a lot of people here only know enough to follow the instructions that are presented, and aren't necessarily interested in knowing "how it all works". So while I certainly understand your incredulity, it is the current situation we're in.

More details in the instructions aren't going to hurt anyone, and those of us that know will simply ignore the additional information. So in order to avoid further queries regarding this, if you could update the README, it would certainly save us some time (or at the very least, allow us to point to the README as a complete resource, which I tried to do earlier before I realized that particular information wasn't present).

P.S. This, of course, is no indictment of all the work you did to make a reliable fork for us to use! We've worked together on things for a while, so you know I appreciate you 👍
[Magisk] wrongway213:
I see your point, but I think you have it backwards. The issue isn't that we need to accommodate "the new XDA" - those who refuse to read, search and follow the very simple rules of this forum.

We need to stop accommodating those users, start enforcing the rules as they should have been to begin with, and maybe this thread won't be as cumbersome as the process involved in picking prints has become in and of itself.

Anyone who can't take the time to read for themselves - them having a working print should not take priority over

1. The rules of XDA

2. Those of us who are either contributing or at least reading for ourselves instead of clogging this thread with nonsense.

We've been too accommodating for too long and it's turned this thread into a cesspool. Dumbing things down even more is the last thing we need to do.
[Magisk] Nergal di Cuthah:
I don't consider myself a noob, and yes most of my knowledge comes from observing multiple threads and learning from the most learned members here and, until i used fork v7 i didn't know that directory, and probably would forget it if i didn't have a bookmark in total commander for it.

Hell i still copy paste commands from the how to root instruction by @V0latyle for my device so i don't make mistakes.
[Magisk] mates21:
So it turns out that using a custom rom is near the end... :(
[Magisk] justDave:
I figure that reading 15 pages to find 5-10 pertinent posts (down to 1-2 lately) is perfect practice for finding valid fingerprints.

Edit: if you're looking for information, skip this post.
[Magisk] HippoMan:
However, just saying "module directory" would probably give many people the impression that you're referring to /data/adb/modules and not /data/adb/modules/playintegrity. And when some of these people don't see example.pif.json in the /data/adb/modules directory, they might get confused ... assuming that they even know about /data/adb/modules in the first place.

And I don't see either of the following items mentioned anywhere in your README.md file:

/data/adb/modules

/data/adb/modules/playintegrity

I know that it might feel annoying that there are people without that much basic knowledge who come here, but some such people do indeed come here and post repeated questions about where to put custom.pif.json. Putting this little bit of extra info into README.md might help to prevent so many of these repeated questions from continually appearing here.
[Magisk] zgfg:
IMO, for the newbies and newcomers:

- read couple of last pages to be up-to-date with what's going currently on since things change fast and although the thread has hundreds of pages, even the posts that were good and useful a month ago may not be relevant anymore

- look at Most liked posts (scroll down on this page to find the section). Those are the posts that ppl liked for good, hence that's the start to read and learn

- if starting by either of the two above, they will find many posts referring to go and take a look in the FAQ post.

Hence, scroll to the top of the page and click on Search this thread for FAQ and for any other new term, tool that is mentioned, etc

Unfortunately, many people don't even think of using Search this thread (specially those coming from TG or similar platforms are not accostomed to)

For demo, I put to Search this theead for FAQ, it didn't find me the FAQ post itself, but the topmost listed post was a post with the direct link to FAQ - screenshot attached

Unfortunately, ppl come and ask about SafetyNet, showing that they didn't put a minute of their time in reading and learning anything before starting to ask (thus breaking one of the XDA Forum rrules) and when you advice them to do so, they respond with nasty commennts why do you teach them and so on

So you have Senior members that use Magisk and modules but don't know about modules installation directories and/or are not familiar with Forum rules and good practices
[Magisk] Nergal di Cuthah:
A note. This should be done on the website or, as sen in your image, the unofficial xda app (which is pretty much a repackaged mobile website). The official app (modified for new xdaforum url) search thread is broken, and Neo doesn't care enough to be informed that the matrix is broken.
[Magisk] trevtdogg:
in my opinion this should be enough to tell people which directory to use, since the example.pif.json file only exists in one directory.
[Magisk] HippoMan:
But that one directory is not named in the README file. Nor is its parent directory named. Therefore, some people won't even know where to look for example.pif.json
[Magisk] trevtdogg:
then I'll gladly answer people that come in here asking "where is the example.pif.json file found?" but I haven't seen that question pop up yet!
[Magisk] demion90:
Hi. I have been using FP from my own old HTC U11 (ViperU 2.3.0 (based on stock HTC Sense rom) Android 8) on Pixel 3 (LineageOS 20 Android 13) more than month until current ban wave.

Currently Pixel 3 only works with XiaomiEU FP (SafetyNet still passes with old FP).

Interesting thing though, HTC U11 still keeps passing device integrity with its own FP (security patch 2018, first API level 25) with bootloader unlocked and root Magisk installed. I confirmed pif.json is used at /data/adb/pif.json.

Magisk 27.0 and PIF 15.9.3 latest module both.
[Magisk] revengineer:
Thank you for the summary. I skimmed over it some more and found the autopif.sh script. This seems to work for now but it looks like that many are jumping on the same key using this method. So I expect this to stop working on Monday when the Googlers get back to their desk. Keeping fingers crossed for a few extra days but in the long run will have to determine how much of my time it is worth to keep Google Wallet running.
[Magisk] Zytrel:
Funny, cause I just did the opposite and went back from the Fork to @chiteroman's version 15.9.3. I was in a rush and just couldn't be bothered with running scripts and doing stuff manually, when I could just push a button, and a have solution that works just fine (for the moment).

Anyhow, don't get me wrong, I still think @osm0sis's fork is superior, but would it really hurt to just publish a 7.1 with the new print? People could just upgrade and be done with it? It feels like 90% of the posts in here are help requests on how to get the new print working with the @osm0sis Fork.

EDIT: And yes, the info is all there in the FAQ and everyone should read it. But that just not how real life works. If they notice their device integrity is broken, if they have two braincells they check Magisk and see if there's an update, if it's there, they just push the button. If it's not, they come here and just post. :)

Regards,

Zy.
[Magisk] Nergal di Cuthah:
Never going to happen @osm0sis made his fork explicitly because he disagrees with bundling a fingerprint that will get banned in days/weeks
[Magisk] ykjae:
I've been following this thread specifically just waiting for news of a new method/discovery and everyday when I wake up I have to browse pages to find nothing of new news but the same questions.

I support people needing to ask questions but these should be cleaned up as answered.

All I'm saying here is this thread should be cleaned up so answers are immediately found and multiple people don't have to ask the same question.

Sorry for contributing to spamming the thread.
[Magisk] Zytrel:
Doesn't really apply in this case, as there is really only one working print right now (as far as I know). Whether you just include it in the module itself or just tell people how to run a script to download it, doesn't really make a difference. (Except for more users struggling with following instructions.)

Regards,

Zy.
[Magisk] osm0sis:
That was part of it, but it was more that my submitted/merged PRs with important fixes were immediately and repeatedly getting rebased/rewritten out, and my suggestions/guidance for making things more methodically developed and futureproof were being ignored.

There are at least several hundred working prints that we know of. And while it's now significantly harder to do so, no, I do still believe everyone should continue to find their own.