However, please understand that this thread is far more significant right now (and has been for a while, I'd say, with that regular banning of fingerprints). Greetings! I don't usually post in this thread (and prefer lurking in the shadows, no pun intended), but I had something to say.Īs has mentioned, the tolerance of off-topic posts depends on the thread owner, and hence under the usual circumstances, off-topic chatter is only removed at the request of the thread owner. Just posting this because I'm not sure if ANYONE ever confirmed an old config they used and tested before Feb 29 still survived and is still working today. I mean, good news that a previously used print survived, but also bad for obvious reasons. But the fact I've gone through several dozen already and only hit 1. I still have a few dozen to migrate (these were all made when PIFork was v3 or v4) and test, and thanks to some tweaks I made to osm0sis's migrate script, I've been able to bang them out quickly. Now keep in mind, this is out of a huge amount I've already tested til the first good hit. Launch between Android 6-8 / initial sdk between 23-25 (edit: been brainfarting this whole time, should be initial sdk / api between 23-26 and print with Android version of between 6-8. This particular config's launch version and API level falls within the recommended range for success for those wondering. Definitely was tested at least 1-2 times at the time I mined it (like all of them I found), but somehow it didn't get burned. and only passed to along to anouther module responsible or loading the fp when a app that requires attestation is run this handoff/scheduling would be tricky.įinally found one of my old configs is still working. This module should be keeping the fp in ram in a encrypted state. Taking that a step futher what about some kind of zygisk module that only loads the finger print when a app that requires PI is run some kind of module much like magisks deny list where apps that are on this list only have access to a sandboxed version of play core services (not sure of the fesiablity of this).īut load/unloading of a finger print on the fly is something thats already possible the tricky bit is going to be loading the fp and getting the attestation ready before the app checks it. Maby even rotate known good finger prints every so offen(days?) to make it less obvious (with a option to cache them if you must) I was talking about this in the evox discord what about moving FP's off device store them only in memory downloaded at every boot stored only in ram. Part of the issue is to many guides and too many people spamming FPs Check the Play Integrity status with any capable app or from the Google Play app's developer options menu to see if the fingerprint passes basic and device integrity. Copy the resulting pif.json file to (root)/data/adb/ if you're using chiteroman's Play Integrity Fix module or copy the file to (root)/data/adb/modules/playintegrityfix if you're using osm0sis' Play Integrity Fork module.ġ2. Execute the autopif.sh script in FX with root access and wait for the script to do its work.ġ1. Press the green "Enable" button and agree to the information shown about root access.ġ0. From the FX home screen, press "Upgrade" and navigate all the way to the right where the DEVELOPER/ROOT tab is.Ĩ. Press the "ENABLE ACCESS" button at the bottom and allow FX to have "All files access" in Android.ħ. Uncheck the 7-day "FX Plus" trial option and select OK.Ħ. Allow its notifications if you're asked about that.ĥ. Open FX File Explorer and accept the license agreement.ģ. Download and install FX File Explorer from Google Play.Ģ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |