Pixel 7 Pro - Cheetah
cheetah-user 15 AP3A.241105.007 12470370 release-keys

Pixel 9 - Tokay
tokay-user 15 AP3A.241105.008 12485168 release-keys

Pixel 9 Pro XL - Komodo
komodo-user 15 AP3A.241105.008 12485168 release-keys

Pixel 8a - Akita
akita-user 15 AP3A.241105.007 12470370 release-keys

Pixel 9 Pro - Caiman
caiman-user 15 AP3A.241105.008 12485168 release-keys

Alright this poll did summarize the current status of our solution, in order to pass the Device integrity you must match with the module SDK for non Beta. In a few days Google will be able to ban/revoke most if not all shared keyboxes (online), That will mean the only solution will be the same as it was years ago. Spoofing system properties and relying on Basic or Device integrity. Remember that when Pixel Beta releases will be closed you might only be able to pass Basic. To pass Basic you need to have a working SElinux status. Otherwise there is still a possibility for PIF to be used and pass Device but no Strong. The same goes for TrickyStore, only with broken TEE status it could be semi-useful.

The November Beta (BP11) have been released on Pling.

Enjoy.

Apparently i cannot be participating in any Public chat anymore. That's shameful coming from Telegram...

Hey everyone,

I need your help! @Telegram has unfairly banned me (@T3SL4 ID: 923755395) from public chats & non-mutual DMs. I've spent 5+ years contributing to the #Root community and running @PixelProps. They've given me no explanation and ignored my appeals.

Please Tweet your support and help me get unbanned! 🙏

Let's show them how strong our community is! 💪 #UnbanT3SL4 #TelegramBan #RootCommunity

The November Android 16 (BP21) Komodo props has been added to Pling !

If you care and trust Android modification and customization you should care enough to let Google know!
Vote: https://chng.it/VhwHbQvkhN

TamJiGi — 探知機（탐지기）

detection demo app that allows one to detect traces left by most – if not all, of the publicly available LSPosed builds

requires Google Play Services to be installed for the detection due to how it's programmed (make no mistake, it's wholly possible to perform the detection on a device without GMS). that being said, the app will not perform any kind of network activity, nor will it use any of the API provided by Play Services

it also may take a while (we're talking days, or even weeks) for the detection to kick in, due to the unique dependency on GMS. one may periodically check the app for a nice surprise

this app is provided as is; there are currently no plans to update the app in the foreseeable future

🚨 Android Devs: New Feature Could Impact Device Integrity Checks (Especially for Unlocked ROM Users!) 🚨

Google's introducing destroyAttestationIds(), a method that erases identifiers used to verify device integrity. This could affect how your app checks for tampered devices (wiped data, unlocked bootloader).

Why this matters (especially for unlocked ROMs):
- Unlocked ROM users often modify their devices, including unlocking the bootloader.
- This new method could make it harder for apps to distinguish between legitimate modifications and malicious tampering.
- This could lead to false positives in security checks, potentially blocking access to apps or services.

- Learn more:
  - Android Keystore Attestation
  - Keymaster Authorization Tags
- Android Keymaster Struct Types v4.0
- Investigate:  Does your app rely on these identifiers?

Another working keybox, should i share? Let's see some ⭐

Gzip->Base64, Expired !

I'm free 🫡