yashsingh1/xdaforums huggingface dataset:
[Magisk] chiteroman:
Some custom rom nuked the persist partition.

You lost attestation keys.
[Magisk] woody4165:
can i unlock bootloader, use custom recovery to flash persist.img from stock rom to persist partition and relock the bootloader or in other way?

Thanks

PS: I tried

fastboot flash persist persist.img

but I get "FAILED (remote: Partition is write protected)"
[Magisk] CityKev:
If you have no success then maybe contact this XDA member as he can fix Xiaomi devices remotely. Check the thread for his work and great reviews. I'm interested as I have the same device as you but I've not unlocked the bootloader as it is my primary daily driver (I have custom ROMs on two Mi Pad 4s).

Xiaomi Auth Flash

Authorised from the site administration. Thanks to @V0latyle @Oswald Boelcke @willverduzco and all other admins. MESSAGE ME on XDA Forums Telegram Support Official MIUI & HyperOS Bootloader Unlock Guide Xiaomi Auth Flash Payments: PLEASE...

xdaforums.com
[Magisk] ihavenolifee:
I recently downloaded a bunch of stuff with playcurl and PIF And the FP downloader and I think I downloaded a fingerprint which causes some of my apps to not work anymore.

Is there any way to cancel or change that fingerprint?
[Magisk] V0latyle:
Can confirm, @mvikrant97 is a real lifesaver, he should be able to help you.
[Magisk] chiteroman:
That won't work. He losts attestation keys forever. Also, he can flash persist and persistbak in recovery using dd.

If the device has a qcom cpu he can follow my guide to repair it.

Unless he finds an unbanned keybox he won't pass Strong.
[Magisk] osm0sis:
He could get an OEM service center to reprovision his persist partition with calibration data and keys, but yeah, not looking good otherwise.
[Magisk] osm0sis:
Well, I guess no news is good news, so... :cowboy:
[Magisk] Flr Power:
Funny how you answer your own post but regardless I'm trying your v7 right now. Thank you 🙏
[Magisk] EfthimisVl:
Lost in the comments, is there a guide for using @osm0sis fork? The FP I was using just got banned after 2 months. Something simple like the pixel flasher program maybe?
[Magisk] mac796:
Just flashed your v7. Working good pixel8 pro
[Magisk] Nergal di Cuthah:
Pixel flasher will accommodate for fork if you have fork installed (am 99.9% sure) @badabing2003
[Magisk] badabing2003:
Yep, this is correct.
[Magisk] V0latyle:
Pixel Flasher detects what module you are using and will put the json in the correct folder on the device. It also automatically converts processed props to the format used for PIFork
[Magisk] yeswap:
My custom PIF got banned today after 33 days. I was able to find a new one in 10 minutes using Pixel Flasher and Play Integrity Fork V7. Thanks @osm0sis, @badabing2003 and @TheFreeman193 for making it so easy.
[Magisk] trevtdogg:
interesting to see a few custom mined prints have been banana-ed recently.

hopefully it's not a sign of more vigilant detection methods being applied by google.
[Magisk] appileh:
Guys can someone help me out still have some issues. I just installed the .zip on the first page what is the next step, i only passed Basic integrity. Cant watch Netflix, e.g. can play Netflix game. Im on OP11 Android 14.

View attachment 6059470
[Magisk] badabing2003:
Would be nice to track all the banana-ed prints

Maybe a separate thread.
[Magisk] BunnyPig1:
But isn't it possible that prints will be reusable after some time?

Maybe I understood wrong but felt like some people in the thread that previously had affected prints became working again.

If this is true, wouldn't it be better to just let the prints be until the community has a better understanding of how they detect prints?
[Magisk] badabing2003:
Yes, possible

But publishing tracking has no adverse effects, Google already knows about their usage and has banned them, and even if they unban, then know about it.
[Magisk] BunnyPig1:
That is very true. Didn't think about that.
[Magisk] pndwal:
Assuming it is persist partition (looks like it is), many (most?) Xiaomi devices have persistbak backup partition that may be used to repair persist partition (if it's still intact)...

You may be able use the first method here if your device is like Redmi Note 8:

https://xdaforums.com/t/guide-about-repairing-fixing-the-persist-partition.4086297/post-82352961

... It's "for users have erased the persist partition, but haven't modified/erased the persistbak partition."

🤠 PW
[Magisk] V0latyle:
You need to find your own working print
[Magisk] pndwal:
I've heard that flashing persist from EDL mode can work since

normal fastboot ROM flash doesn't flash persist any longer despite it being in ROM archive

but EDL flash applies all images... Sounds like your error re. write protection may be related.

However you'd probably need service department to do EDL flash, or someone with an "authorised account" and we can't give details of such (as they're paid services);on XDA... Also, ROM persist image fixes issues when partition is messed up but it's a generic image not containing devices unique numbers...

So if you ever did a /persist backup in TWRP (nandroid backup) or have persistbak on device per my post above, restoring either of these (complete/unique images) will be your best option anyway... PW
[Magisk] CityKev:
Just for reference: There is a paid service on here that offers EDL flashing using an authorised account - I linked it in my post earlier. The XDA member offering it is getting fantastic reviews off people whose device he has rescued.
[Magisk] pndwal:
I used an authorised account holder to recover a Redmi 6 (modding Xiaomi MediaTek is fraught since authorised account needed for emergency download type flashes... Get Xiaomi QCom!) years ago... Cost only AUD $15-20 each time and a respectable small business in Vietnam spent about 45 min with my PC tethered remotely via team viewer for the money...

Countless XDA members pinged me for details at that time but I was warned by XDA staff that I couldn't recommend any such services on XDA forums...

I had quite a long discussion with staff, especially when I was warned I couldn't even give details via PM since this is still deemed 'part of XDA forums' and I'd face infractions if it was discovered I'd continued to do this, so despite my arguing that a nominal fee to unbrick using Xiaomi authorised agents beats XDA effectively saying "sorry, we can't help... If there's no service dept. in your country (a few XDA members had no such option) you'll need to buy a new phone.. your old one will make a great paper-weight!", this is where we're at AFAIK... You'll need to be careful recommending such a service until XDA makes exceptions here sadly Edit: but XDA has now apparently made an exception happily!...

Important Edit:

I just found and checked your linked post/thread, and thankfully it seems that XDA have finally sanctioned exceptions to the policy the told me they couldn't adjust previously... I'd argued black and blue for such a common sense approach frankly (there's principles and there's rules, but when relaxing rules doesn't violate any principle it's time to revisit the rules no?)... Happy to see this about-face, but I wasn't informed of it till you pointed this out, thanks!

Here's the XDA endorsed Xiaomi Authorised Account flashing service thread for others finding this:

https://xdaforums.com/t/xiaomi-auth-flash.4627375/

Wish I'd been able to announce it, but I guess many others will also have argued for common sense to prevail by now...

This will be a boon for Xiaomi users between a rock and a hard place with expensive paperweights or corrupted unique numbers on devices... Well done XDA...

🙄 PW
[Magisk] jabennett:
FYI, I personally ditched Androidacy MM once they got annoyingly aggressive about monetizing it after acquiring it from Fox. I've since switched to MRepo, which seems to work flawlessly at updating PlayIntegrityFork (and everything else, as far as I've seen).

GitHub - MRepoApp/MRepo: A modules manager for Magisk, KernelSU and APatch

A modules manager for Magisk, KernelSU and APatch. Contribute to MRepoApp/MRepo development by creating an account on GitHub.

github.com
[Magisk] CityKev:
This service is approved by XDA staff and has it's own thread in the paid for services section:

Xiaomi Auth Flash

Authorised from the site administration. Thanks to @V0latyle @Oswald Boelcke @willverduzco and all other admins. MESSAGE ME on XDA Forums Telegram Support Official MIUI & HyperOS Bootloader Unlock Guide Xiaomi Auth Flash Payments: PLEASE...

xdaforums.com
[Magisk] pndwal:
Yes, I just made this edit above:

Thanks for the heads-up... 👍 PW
[Magisk] V0latyle:
Yes. Official policy on paid services and content is "not without explicit administrative approval". Any paid services should have a note that they were approved by XDA staff. We do permit them on a case by case basis but they must be approved.
[Magisk] GabbyWC:
Hmmm, the private fingerprint that I've been using since mid-December has stopped passing device integrity as of today. Has anyone else experienced the same thing? I'm currently using Play Integrity Fork v7.
[Magisk] pndwal:
Well we only ever needed one working service with reasonable fees to recommend for Xiaomi users...

It's about time this happened... XDA should have found someone to endorse years ago when Authorised Account holders weren't like hens teeth (as they are now) frankly. (Xiaomi simply shut many down)... FWIW, Xiaomi also began charging AA holders a significant fee per x number of flashes some years ago, so AA holders must still change to cover expenses AFAIK, and only pocket a portion of the payment...

Anyway, I'm happy it finally happened... PW
[Magisk] dilligaf56:
Edit: Please ignore. Was able to get it to pass using TheFreeman193's PIFS list and the PixelFlasher PIF Manager, using chiteroman's module.

Please forgive the dumb question.

Trying to install osm0sis' PlayIntegrityFork module via Magisk. Keep getting:

- Copying zip to temp directory

! Unzip error

If I download the zip file to my computer, it unzips just fine.

This is the first time I've had issues installing a module in Magisk. Is installing this module done differently than most others? Thanks.
[Magisk] Umgak:
2023-12-01 fingerprint still working for me on Fork v6.
[Magisk] droidman1992:
Osm0sis fork v7 works perfectly after updating with Lineage OS 20 (Android 13) on OnePlus 7 Pro. Some people are reporting that their custom prints are banned, hopefully the banning has not become more aggressive. I fear that Google may now be randomly banning even lightly used prints to make life difficult.
[Magisk] rogers11:
No, the two from 12/23 that I now use with v7 still work.
[Magisk] GabbyWC:
Unless I've done something wrong with my tests, all seven of the previously valid custom fingerprints that I found in mid-December no longer pass device integrity. I tried all of them tonight after migrating them to the current Play Integrity Fork custom.pif.json format with osm0sis' migrate.sh script and using the su -c killall com.google.android.gms.unstable command with the Material Terminal app between each test.
[Magisk] Fishawy:
Same, suddenly all my custom fingerprints fail. Using osm0sis's v7 fork.

Trying to play around and see what's happening.
[Magisk] simplepinoi177:
Yeah there are multiple and multiple reports of custom fingerprints no longer passing....

it seems many are from PIFS. Mine from Dec 8. on PIFork v3 is still passing on all 4 of my devices....
[Magisk] GabbyWC:
What's funny to me is that if I don't use a custom.pif.json file, I pass both basic and device integrity with PI Fork v7. 😐

If I remember correctly, three of the now-banned fingerprints in my possession were obtained from the t*d*phone dumps web site and four of them were obtained from a certain manufacturer's official ROM zip files that I downloaded and extracted from elsewhere. It seems like Google is up to something new and this could be the calm before the storm.
[Magisk] simplepinoi177:
mine is from extracted from a firmware image....so I better keep a look out and keep checking...

using GPay checker to help check anytime my screen unlocks...so there's also that...
[Magisk] CZ.Kostra:
"Christmas" FP also not working? I just migrated it (it has an old format), tested it on PIFork v7 and everything is fine.
[Magisk] GabbyWC:
Is your phone also passing basic and device integrity with his module and no custom fingerprint?
[Magisk] Fishawy:
How?

Are you using the normal pif.json instead?
[Magisk] GabbyWC:
My phone is running the PixelOS 14 custom ROM (which might pass Play Integrity when not rooted) but I have Magisk installed so if I completely uninstall the PI Fork module, I don't even pass basic integrity. If I install the PI Fork v7 module and leave it without a custom fingerprint, I pass both basic and device integrity.
[Magisk] Fishawy:
This is weird, do they have a custom print baked in like Xiaomi.eu?

I hope osm0sis looks into this shortly.
[Magisk] CZ.Kostra:
Without FP I will only pass the BASIC.
[Magisk] GabbyWC:
PixelOS offers a CertifiedPropsOverlay.apk file in their Telegram channels but I have never installed that. The APK (or fingerprint that it provides) was apparently last updated on January 16th. The current ROM build that I'm using is from January 20th.
[Magisk] DivintyQQ:
Damn, definitely something weird is going on, can confirm that my custom FPs on Osmosis fork v7 stopped working.
[Magisk] simplepinoi177:
@osm0sis ....doesn't seem to be the case...

many here and on Telegram are reporting PIFork v7 has suddenly stopped passing a good number (some have claimed like half no longer passing all of a sudden)....either Google decided to ban a bunch unexpectedly and it's just a significant coincidence that they did that the same time you released your fork, or something in v7 update is causing some trouble...

what's weird is it seemed to be related to the time -- as users didn't seem to start reporting until a couple of hours ago; that or Google really did just suddenly decide to mass ban a bunch...
[Magisk] GabbyWC:
Is that with the Xiaomi.eu custom ROM?
[Magisk] esatch:
Confirming that my PRIVATE DEVICE fingerprint stopped working.

That fp is not present in any online dump I could look at.

I'm on pif dev v2.
[Magisk] simplepinoi177:
wow...you still dev v2...?!?!

that version's capability to implement a custom fingerprint got implemented in the main branch of PIF in like 13.5 or something....

maybe try the newest 15.3.4 or even the more stable 15.1 or 15.2....
[Magisk] CZ.Kostra:
Yes. PIFork v7 XEUInjector can remove. The only thing you have to do is to uninstall the Injector update after the restart and to be sure to restart at least once. Injector must disappear from installed APPs.
[Magisk] Fishawy:
I don't think it's a version issue, rather prints.

My tests are with 15.2, fork v6, v7, and the two RCs 127 & 128. All my fingerprints fail regardless of the module I use.

Something is definitely wrong.
[Magisk] linuxares:
0smosis fork v7 with my found print works great still
[Magisk] majorfigjam:
I just sampled some of my collection of prints from early December, and they are all stil working with Osm0sis v7. They were sourced from various rom sites, but not the commonly used one, with the build.prop extracted from decrypted system images - they're likely not "common" though I've shared a couple with quite a few people.

If you are failing after a version update, it may be worth checking if your format remains valid for v7.
[Magisk] esatch:
Some other fp are still working (for now).

It's not a module issue.
[Magisk] GabbyWC:
Thank you, CZ.Kostra and Google Translate. The original reply was posted in Czech so here is the English translation.

"Yes. PIFork v7 XEUInjector can be removed. All you need to do is uninstall the Injector update after the reboot and reboot at least once to be sure. The injector must disappear from installed applications."
[Magisk] simplepinoi177:
Thanks for the confirmation guys!

Google really changing gears and ramping things up it seems!
[Magisk] Umgak:
Sent you a DM for testing. Looks like Google might have been collecting prints all this time for a massive wave now that users are more dispersed.
[Magisk] Fishawy:
For those who are failing now while using private fingerprints, are you on the January Google Play System Update by any chance?

A friend sent me their private print which is still working, but it fails on mine. Just trying to pinpoint the root cause.
[Magisk] GabbyWC:
I don't even see where to access Google Play system updates on the PixelOS 14 custom ROM. The Android security patch level of the current build is 2024-01-05.

Edit: I found a reference to what you asked about in the Settings > About phone > Android version screen. The Google Play system update is from August 1, 2023.
[Magisk] Techno_Physics:
Did u find any unbanned keybox?
[Magisk] Migsi:
I've just set up everything (@osm0sis fork v7) and tried to use both available real prints for my phone, but it seems it is not correctly picking up my custom.pif.json. TB Checker always shows me the same fingerprint I get when disabling the PIF completely. I've generated the pif using GeneratePIF, placed it under `/data/adb/modules/playintegritifix/custom.pif.json` and made sure to use the migrate.sh script on it. Magisk is set to enforce the denylist, gms is on the list (but removes itself after reboots?), TB Checker is on the list as well, but no chance. Am I just stupid or is there indeed something broken?
[Magisk] majorfigjam:
My early December print is working still on my Pixel 6Pro with Play Services version updated 18 Jan 24, but Play System still showing 1 Nov 23 and no update available. Play Store is also showing no update available.
[Magisk] simplepinoi177:
This is normal behavior. The device from which you spoof your fingerprint from only displays and presents to DroidGuard; at the very least not TB Checker, SPIC, or Play Store Play Integrity checker...

Why use that? If you are using osm0sis' PIFork, why not use

his

"gen_pif_custom.sh" script as he created both -- so I imagine they work together. There are so many clones of his generate pif script and PINext out there....

You'll find it in the attachments on this post HERE.

And as he created & coded the gen_pif script, you most likely wouldn't need to run the migrate.sh script on it; and just FYI, the migrate.sh script is coded into PIFork and will automatically do so when installing the module with your existing pif.json.

This is normal -- has been since Displax MOD, which PIF and its forks are based off of. Apparently having certain Google services in denylist gets in the way, so the modules take care of things under the hood and removes them at startup.
[Magisk] turonl12:
I've got different issue - Xiaomi Poco F3 - Play Integrity Fix 14.6 with private fingerprint.

The verdict is "meets BASIC/DEVICE integrity| - 2 of 3.

However the Google Wallet says : "The device does not meet security requirements"

The NFC payments does not work (unexpected surprise when paying:( )

It was working fine till yesterday on a private fingerprint - since beginning of December.

Anyone also have an issue with GWallet with device integrity passed?
[Magisk] sawdoctor:
Be curious to know if there's any connection with the banned prints. Maybe worth sending the banned print to one of the Devs to check?
[Magisk] simplepinoi177:
usually when you get that but you're passing 2/3, you can do one of two things; 1) wait 24 hours (in your case, since it worked yesterday, clearing cache and rebooting might be an additional step to this) or 2) clear data on Play Services, Wallet, GPay (and if you want to do more for good measure Google Framework, Play Protect, & Play Store) -- but by doing this your cards will be removed from Wallet and you will have to re-add and re-verify them again.

Also, I'm wondering if you're somehow getting a false positive......
[Magisk] GabbyWC:
Perhaps the Google Play Services version might also be worth mentioning. My phone has v24.02.13 (190400-599553831) installed and it was last updated on January 18th.
[Magisk] Migsi:
Oh, well, so I was indeed stupid and the fingerprints (POCO F1) are probably banned. What a pity :(

I came from chiteromans PIF which linked to it. As far as I can see the resulting file is not different than the one resulting from the migrate script. I'll try to generate a fingerprint using his script later today, but I don't expect it to have a different outcome.

So they are supposed to not be listed at all? Or should I re-add them every time?
[Magisk] Fishawy:
Same version here. Did you try uninstalling the updates and testing?

The fact that a working print elsewhere isn't working for me is mind-boggling.
[Magisk] majorfigjam:
I should add that Google have halted roll out of Play System update in January, as it breaks storage on Pixels. Sound familiar? That might be relevant to why the update may be breaking PIF.
[Magisk] majorfigjam:
This is a question that I should know the answer for, but don't.

Is the v7 Osm0sis format of custom.pif.json usable in the Chiteroman versions of PIF, if it's renamed and put in the correct folder? Or does it need to be reformatted first?
[Magisk] Umgak:
Same version here. My setup still works flawlessly but @Fishawy's is broken. I even tried to uninstall and reinstall gms to force an update. All that did was log me out.
[Magisk] GabbyWC:
I didn't try that but I did a search on my phone's system apps with X-plore File Manager and found a small APK called ca.aospa.android.certifiedprops.overlay which is probably what's causing my phone to pass basic and device integrity with PI Fork v7 and no custom.pif.json file.
[Magisk] turonl12:
I've verified 3 of my set of private fingerprints - all passing DEVICE.

Than i've tried the old one from XIAOMI.EU - only BASIC is passed.

I did a cache data cleanup on all of above services - between each try (unfortunately) the same result - GWallet - states device does not meet security requirements (on each of tested finger prints).

I've looked at the yesterdays updates - nothing suspicious (google app ?) - so it looks something changed on google side ?
[Magisk] Fishawy:
Unfortunately I'm on stock, so such app is not available.

I think we need to wait for osm0sis's updates.
[Magisk] simplepinoi177:
If you look at the quintessential post by osm0sis, at the bottom under the "CLICK TO SHOW CONTENT", you can compare the differences between the two -- namely naming conventions. But it seems since then that chiteroman actually added some fields like "FORCE_BASIC_ATTESTATION": true and such....

you shouldn't need to re-add them every time....but maybe Wallet and GPay and other services....

Thanks for checking....should be useful info. But now I'm trying to manage my worry/concern if this is signs of a big turnover from Google on this and not start panicking...
[Magisk] appileh:
How to install/execute this? Play integrity installed with Magisk, so now the PIF, how to? Im on One Plus 11 Android 14
[Magisk] simplepinoi177:
Read the 2nd most All-time liked post (found if you scroll up and look to the right)

Then, if you have access to a computer and can connect your OP to it, easiest way is to use the PIF Manager component in the Pixel Flasher tool (directions in the below link)

📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

DESCRIPTION As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.) PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence...

xdaforums.com

and if you don't have access to a computer, then use PIFS method (I suggest you use Play Integrity Fork)

GitHub - TheFreeman193/PIFS: A collection of build properties for the PIF module

A collection of build properties for the PIF module - TheFreeman193/PIFS

github.com

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