[Magisk] i5lee8bit:
Yup, rip HTC prints. I kept it secret for a long time (except for a very few select group of peeps from a certain kernel testing group that I shared with), but I mined some insanely obscure prints from various HTC devices in late November / early December. I eventually noticed patterns and logic in how the prints corresponded to the ROM versions, and was able to generate working prints for devices from obscure regions/carriers/variants... but most of all, for ROM versions which literally had NO EXISTING DUMPS EVER. As in no RUU's or dumps of ANY kind EVER existed. Devices ranged from back when HTC was still popular (M8, M9, 10) to much more obscure later ones (Exodus 1, U11 Plus, U11 Life, and more).

I bring this up to perhaps help the smarter people to clue in more on what's going on. Because I got so good at finding HTC prints, I definitely had some (many/several) that 100% for sure the props didn't exist ANYWHERE on the internet.

Perhaps even more interesting is that although seemingly ALL of the HTC prints I mined stopped working on my Pixel 7 Pro and Pixel 7 about 2 weeks ago (looking back at the private group chat, it was that other confusing "mass ban" that happened or started between Feb 12 and 13), all of those same HTC prints continued to work perfectly fine on all my other devices, including and not limited to Nintendo Switch (switchroot A11), Pixel 3 (LOS 21), Pixel 4 (factory latest), Galaxy Tab S6 Lite 2020 (LOS 21), Galaxy Tab S7+ (factory latest) and Galaxy Tab S8 Ultra (factory latest). Maybe this last bit was explained in the last several dozen pages; unfortunately I haven't had much time recently for hobbies due to our growing family ♥️. But of course, all of them are now dead for real as of this morning. [edit - integrity on all my other devices now dead, not any of my family... just proofread my post and realized how that last part sounded 🤣]

Anyway like I said, hopefully all that info helps you brighter people clue in further on what's going on behind the scenes. Because I can say for sure it was NOT just a mass banana of publicly available posted props as many are suspecting... It's something well beyond that.

One last thing, @osm0sis, considering I needed to fix integrity on SO MANY DAMN DEVICES, I added a tiny bit to the end of your autopif script to further automate the process. If anyone wants to make it a tiny bit easier to "deploy" on multiple devices, feel free to give it a try. It also wouldn't surprise me if you're already working on further automations and you already have something like this in the works anyway, ya know? 😉

This is just super ghetto and sloppy, but the general idea is obvious:

# adding the remaining lines to further automate process
echo "\n- Copying generated custom.pif.json to module path ..."
cp custom.pif.json /data/adb/modules/playintegrityfix/custom.pif.json
echo "\n- Killing GMS unstable process ..."
killall com.google.android.gms.unstable
echo "\n- Test integrity now. Done."

So just copy and paste it to the end of the autopif.sh script. All it does is copy the generated custom pif file to the module path [for os's fork specifically, that is], then kill GMS unstable process for you so the new print immediately takes effect. So basically I can just run the script once on each device and done and done. And so long as (hopefully not too long!) I'm relying on XEU prints, I can just run the script again and be immediately done again, should the need arise.