yashsingh1/xdaforums huggingface dataset:
[Magisk] V0latyle:
We are such a small subset of the Android user base that we'd just be ignored as "hackers". We really are on the fringe. There's little we can do to effect any sort of change especially for our own benefit. I don't want to get into politics, but everything in the world is going the direction of authoritarianism, not liberty. We, those who actually value freedom with our hardware and software, are such a small fraction that we are insignificant and negligible. The masses want security, and they pay for it by giving up their liberty.

Protest if you want but it will fall on deaf ears. We are, after all, operating outside the limits of the intended ecosystem, and there will come a point where we must either conform, or simply give up these modern conveniences for the sake of our freedom.
[Magisk] sawdoctor:
Such a shame there's so few Linux phones around and the ones that are available don't have the best hardware.

Whatever happened to the xda phone? I was really looking forward to the Ubuntu version but they never actually got built/released did they?
[Magisk] BunnyPig1:
I asked this question a couple of months ago and got a pretty good explanation from @V0latyle.

You can read it Here
[Magisk] Matthew3955:
Custom pif must be called custom.pif.json or pif.json?
[Magisk] GabbyWC:
It must be named pif.json for chiteroman's module or custom.pif.json for osm0sis' module.
[Magisk] zgfg:
Just to confirm, last night I finished (re)testing the whole Freeman's collection (an archive downloaded back on Dec 18,) and none of the cca 1300 JSON prints work anymore

I finally upgraded to PI Fork v7 and used my old script for fully automated testing in Terminal Emulator (or better, directly from MiXPlorer) - hence no ADB and no other tools are needed besides the migrate.sh script to update to the new format required by the latest PI Fork

For each JSON it tests first SN (by YASNAC) and if not passing BASIC, it immediately skips to the next JSON

Otherwise, it tests PI for the same JSON and if passing only Basic it tests PI one more time by downgrading the API level to 25.

Also, if YASNAC passed Basic only,,it immediately downgrades the API level and tests the PI only once

Finally, if it passed Device Integrity ok, if not it looks for the next JSON by crawling through the given tree of local directories on the phone (collection must be downloaded in advance)

It tests automatically about 100 JSON files per hour, and now after the mass-banning, they fail faster, hence the script can crunch over 150 JSON prints per hour

Depending how lucky I was with the SPIC (or now TB-Checker) availability, the script would automatically test 500-1000 JSON files per night - in addition to Freeman"s 1300, I retested also about 750 prints from the old MHPC module plus one more collection of previously all good cca 250 prints that also all fail now

---

Btw, since the last days SPIC was mostly overquota, I had to modify the script to automatically execute PI testing from TB-Checker instead of from the SPIC

It first looked kind of tricky to decode PI test results from TB-Checker screen dumped by uiautomator to an xml file

Namely, I wanted to count the total number of Pass and Fail occurrences but grep counts instead number of lines containing the given word, - hence a single line with the word repeated N times counts as 1 instead of as N

Therefore, it causes a problem since uiaotomator dumps the whole TB-Checker frame to a single line, resulting that grep would count then nPass and nFail both as 1, both for

BASIC Pass

DEVICE Fail

STRONG Fail

VIRTUAL Fail

and for:

BASIC Pass

DEVICE Pass

STRONG Fail

VIRTUAL Fail

But luckily, the following elegant pipe correctly counts the total number of Pass and Fail occurrences:

nPass=$(cat tbchecker.xml | grep -o 'Pass' | wc -l);
nFail=$(cat tbchecker.xml | grep -o 'Fail' | wc -l);

And then the following logic correctly decodes the verdict:

(( nPass==3 )) && verdict=MEETS_STRONG_INTEGRITY;
(( nPass==2 )) && verdict=MEETS_DEVICE_INTEGRITY;
(( nPass==1 )) && verdict=MEETS_BASIC_INTEGRITY;
(( nPass==0 )) && verdict=NO_INTEGRITY;

(( nPass==0 )) && (( nFail==0 )) && verdict=TEST_ERROR;

The latter case corresponds to the TB-Checker overquota, connection error or other potential issues during the automated testing (eg, when phone call temporarily pushes TB-Checker to background, causing that uiaotomator dumps the Dialer screen instead of TB-Checker screen.snd grep finds neither Pass nor Fail words)
[Magisk] osm0sis:
Okay, let's try this again now that it's been a few days and things have somewhat settled down... 😥

#190 is the new PIFork v8 Release Candidate! Especially needs some attention from those using any of the custom ROMs with conflicting spoof injector apps on this list since that part of the scripts got refactored to support files and overlays now and minimize code duplication: https://github.com/osm0sis/PlayIntegrityFork/blob/main/module/example.app_replace.list

Big thanks to @GabbyWC for helping to test the new robust overlay handling in the module on PixelOS, which required me to automate a few extra steps like extracting/parsing the package name from the .apk and using it to disable the overlay in a copy of the config.xml file that controls it! :cool:🙌

Commit diff log:

Comparing v7...main · osm0sis/PlayIntegrityFork

Fix Play Integrity (and SafetyNet) verdicts, allowing custom fields and props - Comparing v7...main · osm0sis/PlayIntegrityFork

github.com

Build: https://github.com/osm0sis/PlayIntegrityFork/actions/runs/8146538914
[Magisk] HippoMan:
... and it gets installed in /data/adb for chiteroman and in /data/adb/modules/playintegrityfix for osmOsis.
[Magisk] i5lee8bit:
So very OT, but I'm still pissed about this.

From a once 2-3 pack a day smoker, to a 2 can a day chewer (dip), back to a smoker (quit dipping by using patch AND smoking O_O)... vaping finally got me to stop using tobacco altogether. And before the USPS ban had wiped out a huge portion of good juice makers and started other issues in the market, I had worked myself down to vaping 1.5mg / mL, as little as 2-4 mL a day. As products disappeared I was basically forced back to vaping 25mg juice again. I guess it was all "for my own good" though. At least that's what the government and big tobacco tell me.
[Magisk] i5lee8bit:
I don't really fall into any special categories for testing, but at least I can report success across the board for me:

(using my own, i.e. not xiaomi.eu team, print) Working on:

Pixel 7 Pro (stock latest)

Pixel 7 (stock latest)

Pixel 4XL (stock latest, A13)

Pixel 3 (LOS21 official, A14)

Galaxy Tab S8 Ultra (stock latest Samsung ROM, A14)

Galaxy Tab S6 Lite (LOS20, A13)

Nintendo Switch (switchroot LOS, A11)
[Magisk] V0latyle:
Do not resist the Directive, citizen. The government knows best.
[Magisk] Fishawy:
Removing my off-topic post.
[Magisk] Legitsu:
whats the fast way to dump a finger print from a doner phone I got a couple of galaxy S22s running A14

a old motorolla x running android8? and my trusty S10
[Magisk] Nergal di Cuthah:
If the donor is a s22 it's likely the print is too new to force basic instead of hardware attestation. You need to use devices that once used oreo for best donor
[Magisk] Legitsu:
I have a moto running android 7 and a S10 running android 12

but I could probly scare up anouther device
[Magisk] fbirraque:
Already tested #172 and #190 flawlessly:

- Poco F3, MIUI 14 (xiaomi.eu), Android 13

- Redmi Note 8T, EvolutionX, Android 13

Note: I don't know how to explain but I noticed that on both devices the UI seems faster after #190 update 🤷‍♂️
[Magisk] kingpeppermint:
Sadly i must say i have nothing to add to that other than both can be true, what you describe seems to be more of a long term thing. I hope the current anti-trust/monopoly cases against Google and Apple might help to slow their attempts.

You know what the problem with educating and protesting? people don't care about this topic, by the time they start to care it's probably to late. Just like many other things
[Magisk] droidman1992:
What is everyone's consensus regarding finding a custom fingerprint now after the mass ban, do we stick to Xiaomi autopif.sh or is it still possible and worthwhile to get a custom one?

Some people have found that no prints work in thefreeman193 collection which leads me to believe that this is more trouble than it's worth.
[Magisk] rseiler:
@droidman1992 I don't know, but for at least the next while we could benefit from some kind of alert system for the Xiaomi one. Maybe someone especially in the know could setup a Twitter bot which tweets a red X when the current one dies.
[Magisk] CZ.Kostra:
All good on POCO F5 Pro with MIUI14-A13 (Xiaomi.eu). (y)
[Magisk] esatch:
Ok on Redmi note 13 4g (sapphiren) miui stock
[Magisk] traversone:
surely I am doing something wrong but, while flashing the zip : PlayIntegrityFork-CI_#190.zip

View attachment 6076442

this happens
[Magisk] BillGoss:
I have two phones: a OnePlus 8T running LineageOS 21 and a Pixel 8 Pro running the latest stock OS. Both are running Magisk 27.0 stable and Play Integrity Fork v7 with the latest finger print from autopif.sh.

Yesterday both devices passed Basic and Devices integrity.

But after I updated the Pixel to the new software update (husky-ap1a.240305.019.a1) today, it only passes Basic integrity even after clearing Google Play Services storage and rebooting.

Any ideas as to what's changed and how to fix it?

Other odd things:

I can no longer force stop Google Play Services (the option is greyed out).

killall com.google.android.gms.unstable responds with com.google.android.gms.unstable: no process found
[Magisk] tom1807:
I cannot recall now whether there was ever a possibility to force stop GPS.

But, I updated today my Pixel 6 to the latest March image and still have Basic and Device Integrity.

Cheers

Tom
[Magisk] FrogMaster-:
It's normal for the process not to be found if play integrity checks have not been recently ran. It's simply means droidguard is not running.
[Magisk] derSeddy:
I had a working custom fingerprint since December, so I didn't follow updates on this topic anymore, but now I fell back to basic integrity. So, can I just search for my own fingerprint again, or did anything change since Dezember, such that there is a better method?
[Magisk] BillGoss:
Even after doing an integrity check through Play Store Developer options?
[Magisk] FrogMaster-:
Google has performed a mass banning of they already limited number of working fingerprints available, even more prints now are not functional. You can search for one and well you may find a print It will be significantly harder to locate.

A lot of people are still depending on the Xiaomi print and are retrieving it with osm0sis autopif.sh script.
[Magisk] FrogMaster-:
DroidGuard only runs for so long, it may have already finished running by the time you attempted to kill the process. You should be able to check the logs to see what fingerprint is being passed.

logcat | grep PIF
[Magisk] majorfigjam:
I had a similar issue on a Pixel6 pro, which in the end turned out to be due to the way I disabled magisk & modules before doing the adb / ota update today.

I reinstalled magisk, and fork v7, and recopied the fingerprint, then rebooted, and it's now passing 2/3 again.

I didn't have any issues force closing play services or play store from the app menu to clear their caches.
[Magisk] zgfg:
Don't understand how did you do

Simce this is CI, you should have GitHub account to login and download the zip

Then, from Magisk app, Modules, Install from storage - navigate to the downloaded zip and install
[Magisk] batboy00:
I will expose my strange situation. Like most of you, 5 days ago I realised that my own print does not work anymore. So I manually extracted the Xiaomi print, put it in the pif.json and worked as expected (basic and device integrity). Also tried dozens of fingerprints from various sources but I found none working so I just let it like that and continued using the Xiaomi print.

Yesterday, I noticed I only pass basic without doing/changing anything on my phone except regular usage. So tried to use the autopif.sh script and I pass nothing, not even basic. I checked the differences and I realised that when I manually extracted the values I put a space " " in front of device name, like " griffin". Until yesterday, even with this "space error" it worked to have device integrity. Today I also updated Magisk from v26.1 to v27.0 and Shamiko (1.0.1) but same result. Phone is Xiaomi Redmi Note 10 5G MIUI 12. The only two other modules in Magisk that I have from the beginning of Magisk instalation is Axet's Call Recorder and Systemless Hosts.

To sum up, currently, with the Xiaomi fingerprint I don't pass anything (tried with both PIF and Play Integrity Fork v7, so at least the results are consistent). If a add a space in front of device name, I have basic integrity (with both PIF, chiteroman and osm0sis). I know I am asking a lot, but I would be curious if with another working fingerprint, I could pass device integrity or not. Google definitely continues playing with their Play Integrity / Droidguard algorithm.
[Magisk] traversone:
exactely what I did (as for all other modules), will try to re-download it
[Magisk] mates21:
I also had a problem on my Xiaomi Mi 9 phone. I installed the latest version 15.9.3. But I only had 1/3 pass. I downloaded version 15.8, replaced the pif.json file with the latest version and now I have a 2/3 pass. Try this
[Magisk] ScubadooX:
I have a Xiaomi Redmi Note 9 running LineageOS 20. With Magisk 27.0, Zygisk enabled, and PIF 15.9.3, my phone passes Device and Basic Integrity and contactless payments work in Google Wallet. There are no other settings or any other modules required in Magisk for contactless payments to work on my XRN9 (and my Google Pixel 4 running LOS 21).
[Magisk] Claus….:
@V0latyle Is it possible to run an app that has PI, in the emulator and pass play integrity? Would it detetect that it is not a real device?
[Magisk] niko26:
Thanks for the script! Wouldn't it make sense to add an (default?) option to copy it over?

How about a wrapper/app which executes that script once a day?
[Magisk] V0latyle:
Did you read my explanation? You'd have to model TEE in your emulator too, and since it is cryptographically signed, you'd have to have the private key, otherwise Droidguard would know that it's compromised.

You could in theory build an emulator that for all intents and purposes appeared to client apps and services to be a genuine device, but you have to remember that both Play Integrity as well as native Android security and verity functions are designed to prevent this very thing - so that a malicious rootkit couldn't simply hijack the boot path to load the OS in an emulated environment and spy on it from the outside.

Others such as @pndwal have a better grasp of these concepts than I do and can therefore better explain why or why not
[Magisk] osm0sis:
That's a ROM/download/Magisk problem. Definitely try downloading and trying again.

I don't want to overwrite any existing file in case a user has multiple working json and also wants to run autopif.sh, so no, I don't like the idea of copying it automatically.

Running it daily also isn't a good idea, since at scale it would hammer SourceForge.
[Magisk] Slim2none4u:
Yeah don't read or anything. Just go into a thread and post any question you want. Hell it don't even have to be about PIFs,, can be about f*cking vape juice!
[Magisk] Anchewei:
Just back to this thread since December, it looks that there was a massive ban from Google...

Something weird happened to me, after updating to the March security update, using Play Integrity 15.9.3 and using pif.json from PixelFlasher, I can pass the Play Integrity check in the Google Play store, but some of my apps (e.g. banking app, McDonald app or even some communication app) are frozen in the starting screen.

Does anyone know what happened here?

Very appreciate your help and suggestions here.
[Magisk] niko26:
Couldn't we instead patch the part which communicates with TEE instead?
[Magisk] intel_core_i7:
Spoiler content hidden.
[Magisk] Vision:
Anyone know official XDA app or similar trusted? because 3+ months now, always sign out itself form xda website from chrome in my phone

@V0latyle i read for the orginal XDA app with fix domain and you contribution in this
[Magisk] batboy00:
Same, using PIF 15.8 I pass nothing with Xiaomi fingerprint. So same result as with PIF 14.0 that I previously had and Play Integrity Fork v7 that I also tried (of course using migrate.sh script to use a proper json file). I really don't understand what is different with my phone compared with most of the other. Until now, I had the same behaviour when fingerprints were being "banned" and needed to change. For some unknown reason, now it is different. Google is gaining more and more advantage on this war unfortunately..
[Magisk] fbirraque:
[15.03.24] [NEW] XDA Forum Apps I Official with Domain Fix + Unofficial

XDA Forum Android Apps I am presenting here two apps for android for XDA Forums. 1.Original Fixed App Intro : As you might know, official XDA app is stopped working since migration of the domain. We've long waited to get official app to get...

xdaforums.com
[Magisk] mates21:
If you only installed version 15.8 without changing the fingerprint inside, it will not work because it contains an old fingerprint that is banned. Take the fingerprint from the latest version 15.9.3, upload it to version 15.8 and then Install version 15.8
[Magisk] cubandanger05:
So I updated to March's pixel 7a update and I'm passing again....? 🤷‍♂️

View attachment 6076542
[Magisk] traversone:
3 out of 3 devices have same behaviour.

Last one is S21 stock
[Magisk] batboy00:
I replaced the pif.json with Xiaomi fingerprint from 15.9.3 but same result, no labels. I have the feeling that this fingerprint is completely "banned" for my device because no matter what version/fork of PIF, the result is consistent and the same. Not even basic integrity, but if I use " griffin" (note the extra space) for device name I get basic integrity (no matter what version/fork of PIF, same result).
[Magisk] philidor:
I was using a private FP untill some days ago and I had 3 working FP. Now my FPs don't work anymore; I read about the huge banning and the theory around google behavior.

I tried to extract a working FP (with different methods) without success. So, just for be sure I have understand it correctly, is the extraction process the same? (and is only much more difficult to find a working one)

Thanks
[Magisk] manjaroid:
Nicotine delivery, smartphones... Tomato tamotto.
[Magisk] V0latyle:
I just use Chrome, I didn't contribute anything. The "official" XDA app is in limbo as no one is supporting or maintaining it.
[Magisk] sawdoctor:
If you are usin osmosis fork you need to run the script or reflash his module to add the missing fields to the fingerprint. (Sorry if this has already been answered but there's so many posts). For me when i was mining for prints and then went back to xaiomi i failed all 3 checks until I reflashed osmosis fork again and then the print started to pass again
[Magisk] batboy00:
Indeed, I used the right format for either PIF or osm0sis fork (depending on which one I had installed). And every time I was looking at 'logcat | grep PIF' to double-check the values being used. But now device integrity seems so far away.. and not reachable anymore.
[Magisk] Lughnasadh:
Are you by chance using HMA? If so, there have been several reports that the March update broke it, leaving users unable to start the selected apps.
[Magisk] Claus….:
Yes, what I read from your post is in theory yes, but in practice maybe no. Please confirm?

@pndwal Please advice with any direction that might work, so we can test it out.
[Magisk] Vision:
Oh unerstand, me too i want use chrome but after log in and i tick the stay log in my phone, all good until i close from recent the Google Chrome, i go back and again say log in, not even 1 minute has passed since I closed it from recent, i try log in in another forum and not have this issue
[Magisk] Anchewei:
No idea about what is HMA (a VPN?).

Since the update just came out, I don't realize whether this is a universal problem, but I'm hoping there will be some solutions...
[Magisk] CZ.Kostra:
HMA is a 'Hide My Applist' module for LSPosed.
[Magisk] zgfg:
The following app is not 'official' but from this Forum.

I use it from the beginning (since the last Forum migration and then when the app was published)

[CLOSED] [Development] [UNOFFICIAL] XDA Forums App

INTRO : Instead of that XDA app on Google play that the Devs does not update it regularly, takes a lot of time to open and has some bugs, so I decided to introduce for you a new unofficial replacement --- a new XDA Forums app ! In-app...

xdaforums.com
[Magisk] 4sz0m:
Try a bit harder next time:

Hma android module - Google Search
[Magisk] Anchewei:
Haha..

Yes, I'm using that, is there any problem with it?
[Magisk] Anchewei:
Hmmm, I searched "Hma android" on Google, and the first one that came out was a VPN...
[Magisk] Vision:
Thanks, first time see this.

Thanks for info. I appreciate as always
[Magisk] rodken:
I also read that according to Google, after this year, if one has an unlocked bootloader besides RCS messaging not working, there might be a chance that one might not be able to receive SMS/MMS from users who have RCS enabled.
[Magisk] pershoot:
Yea, I believe to have ran in to this, as well. I asked a few senders, in bulk, during, to explicitly use SMS after I reached out to them via the same, so they would get my latest status; for precaution.
[Magisk] Vision:
What? This is a blackmail from Google.

Google take it too far this time 😤
[Magisk] Vision:
With RCS until now, when a users send to another and the RCS can't delivered for some reason, after the Google messages tell you want send again the message as sms? if Google remove this feature, this bad strategy
[Magisk] rodken:
[Off-Topic] It seems as though the issue has leaked over to the fact that Messages for Web is not working for some folks on rooted Pixel devices. Several attempts to access Messages on Web would results in 'Something Went Wrong...' try again in a few....

As soon as a friend of mine unlocked the bootloader on his Pixel Fold, all went to hell in a hand basket with his device no longer passing PlayProtect device certification.
[Magisk] HippoMan:
The Googlefrinchians are not out to get us. We modders make up a minuscule percentage of Android users, and Googlefrinchian management hardly even take us into consideration at all -- neither negatively nor positively -- when making their corporate decisions.

Our woes are mostly just collateral damage as a result of these Googlefrinchian decisions.
[Magisk] unicornambition:
As here are a lot of experts about PI in this thread: I am having strange problems with PI / AppCheck with an unaltered device. Anybody knows anything about that? Link
[Magisk] Vision:
Yeah unfortunately, the irony is Google this days not listen anyone even the normal users without mod and all that.

Example in Android 12 the feature overscroll stretch animation, the beta test, Google ask the users try this feature and review, the 90% of users say is cause tension for nausea and headache and not add this feature.

What Google did? Add it despite negative reviews
[Magisk] sga999:
I've tried also. No luck. I have never gotten a release candidate file, so I am a bit baffled. I'll keep trying, but it does not show me a zip file that I can download.
[Magisk] Captain_Throwback:
Does this link work for you?

https://github.com/osm0sis/PlayIntegrityFork/actions/runs/8146538914/artifacts/1296272711
[Magisk] sga999:
Weird, on 2 Android devices, it got 404 error, page not found. But on a laptop, it downloaded just fine! Thank you.