Pixel 9 Pro XL - Komodo
komodo-user 15 AP4A.250105.002 12701944 release-keys

Pixel 9 Pro - Caiman
caiman-user 15 AP4A.250105.002 12701944 release-keys

Srećna Nova godina! Happy New Year! ✨ Wishing you a blessed and prosperous New Year filled with zdravlje (health), sreća (happiness) and uspeh (success)! May your slava be rich and joyful! 🥂🎉

The Beta January Android 15 (BP11) props have been added to Pling !

Are you using KernelSU and SusFS but having mount issues with YouTube RVX?

Then try that version of the popular module i modified to make it work:
https://news.1rj.ru/str/RiRiRootRealmRedux/210

Btw i get the same results when not using the Pif module (but only PixelProps & sensitive props v6.5.0, ksunext+susfs), meaning it's either working as an integration to the ROM framework (even if disabled by pihooks) or the root hiding capabilities have evolved, but still not to the point of having a clean sheet without manually compiling the ROM (tldr; lineageos userspace detections).

First test, Lemme know if works.
If it doesn't it could be due to multiple factors, such as not having a ROM with the latest 2025-01-05 security patch or else mount detection points. Choose your root manager wisely, I recommend kernelsu next and susfs !

Alright so I've got some confirmations, You can clearly pass Strong Integrity without PlayIntegrityFix as a module* but not on Legacy root solutions (Magisk) as droidguard (gms) has implemented checks to prevent it from passing integrity and therefore you need to use pif, On new root solutions like KernelSU + SusFS you are free from pif hassles as it hides custom rom, mounts and so on pretty well.

Furthermore if you have internal hooks that spoof your device and don't rely on pihooks props, there will be no way to disable them and you will be left trying FrameworkPatching.

Fortunately PixelProps work with and without Pif for the sake of your integrity.

Big News for PixelProps and Sensitive Props Users!

We've got two important updates to share that significantly enhance device security and Play Integrity bypass capabilities.

1. Sensitive Props v6.5.0-hexpatch: Introducing the PIHooks Disabler

A new version of the Sensitive Props module has been released, featuring a powerful PIHooks Disabler. This new feature actively prevents internal property spoofing, a technique used by some apps to bypass security measures.

- What does it do? It detects and disables properties used by "PIHooks" for spoofing, making it much harder for malicious apps to manipulate your device's internal state.
- How does it work? It continuously monitors for specific properties and sets them to safe values (either 0 for booleans or an empty string).
- Why is it important? It significantly strengthens security and improves the chances of passing Play Integrity checks.

2. PixelProps Now Integrates Sensitive Props Functionality for Strong Integrity!

The core functionality of Sensitive Props has now been directly integrated into PixelProps! This means that PixelProps users can now achieve strong integrity on eligible ROMs without needing to install the separate Sensitive Props module.

- What does this mean for you? If you're using PixelProps, you now have a built-in solution for passing strong integrity checks, offering a streamlined and convenient experience.
- How does it work? PixelProps now includes a new "sensitive sysprop mode" based on the proven techniques from Sensitive Props. It actively monitors and modifies system properties to maintain a secure and verified device state.
- New Settings: You can control this new mode using the SAFE_PROPS and SAFE_PIHOOKS settings in the config.prop file.

Download it on Pling !

Alright after i had done some research especially in my ROM framework integration of pihooks it seems that it wasn't fully disabled, therefore the last modifications i had done had helped me among a handful of pihooks users to achieve integrity without using Pif as a module.

Tldr; It fixes pihooks internal PropImitationHooks, allowing for Strong integrity without much modules.

https://news.1rj.ru/str/RiRiRootRealmRedux/309

That's what will happen to shared keyboxes, we can thank those copycat modules who leak them keyboxes. If you get a hand of a keybox you better only share it with people you trust.