Pixel Props

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.

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.

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 !

Quick demo of the upcoming release for PixelProps, This demo shows enhanced capabilities at spoofing by integrating sensitive props and passing legacy and new integrity checks without using any Playintegrityfix module.

https://t.me/RiRiRootRealmRedux/265

https://t.me/RiRiRootRealmRedux/261

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).

https://developer.android.com/google/play/integrity/improvements

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://t.me/RiRiRootRealmRedux/210

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

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! 🥂🎉

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

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

Pixel Tablet - Tangorpro
tangorpro-user 15 AP4A.250105.002 12701944 release-keys

Pixel 8 Pro - Husky
husky-user 15 AP4A.250105.002 12701944 release-keys

Pixel Fold - Felix
felix-user 15 AP4A.250105.002 12701944 release-keys

Pixel 9 Pro Fold - Comet
comet-user 15 AP4A.250105.002 12701944 release-keys

Pixel 7 Pro - Cheetah
cheetah-user 15 AP4A.250105.002 12701944 release-keys

Hristos se rodi! (Christ is Born!) ✨ Wishing you a blessed and joyous Orthodox Christmas. Vaistinu se rodi! (Indeed He is Born!)

Happy New Year! ✨🍷 Wishing y'all a year filled with love and happiness. ❤️

Merry Christmas! 🎁

Non beta does not pass Device or Strong integrity anymore, Thankfully the beta is still able to get your device certified.
Edit: In fact it can pass integrity without beta but requires a matching security patch.

Built props for Pixel 9 Pro XL [komodo_beta-user Baklava BP21.241121.009 12787338 release-keys]!

Happy birthday to me 🥳

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

Heads-up! Some of you have reported issues with vendor.usb.product_string causing lock screen problems. This is due to how your ROM handles this specific prop, not PixelProps itself. I'm also considering adding bluetooth.device.default_name in a future release, which might cause similar issues with Bluetooth on some ROMs. If you encounter any problems with props, please contact your ROM developer for support. Let's keep things running smoothly! ✌️

Pixel Fold - Felix
felix-user 15 AP4A.241205.013 12621605 release-keys

Pixel 9 Pro XL - Komodo
komodo-user 15 AP4A.241205.013 12621605 release-keys

Pixel 9 Pro Fold - Comet
comet-user 15 AP4A.241205.013 12621605 release-keys

Pixel 8 Pro - Husky
husky-user 15 AP4A.241205.013 12621605 release-keys

Pixel Tablet - Tangorpro
tangorpro-user 15 AP4A.241205.013 12621605 release-keys

Pixel 9 Pro - Caiman
caiman-user 15 AP4A.241205.013 12621605 release-keys

Pixel 7 Pro - Cheetah
cheetah-user 15 AP4A.241205.013 12621605 release-keys

Since the last update, Google Device activity won't revert to your original device but the one you spoofed to.

ref: https://github.com/gloeyisk/universal-gms-doze/issues/62

Alright i had found the issue regarding the Play Services crash, It was introduced after using the gms doze mode which i had the idea from the module universal gms doze. I will open an issue on their GitHub since they themselves tamper with PixelProps modules.

Here is the google.xml sysconfig that introduced the bug (when deleted):

<allow-in-power-save package="com.google.android.gms" />
<allow-in-data-usage-save package="com.google.android.gms" />

To check if you are spoofing properly the vendor & system dlkm run this command in termux as su:
getprop | grep -E "system_dlkm|vendor_dlkm"

Gzip->Base92->Vigenère->ROT8000 Enjoy!
Happy holidays everyone 🎁❤️

Hey Pixel Fam 👋

Things are a bit tight since my family's recent move, but I'm determined to get myself a new Poco* and some gifts for everyone.🎁 Any support you could spare would be a HUGE help!

Even a small donation would get me closer to my goal. You guys are the best! 💪

⬇️ Donation Addresses ⬇️
- BTC: 16bdqYfPs7tbPQqbKK2jqi2J8CGJRHyWJ3
- USDT TRC20: TSgHFznWfRryW6mQ5mTX3pS3Arca5Xbo1T
- TON: UQB0uGMKN9BGVaXNAPd7PCofj7I7F2AsPdgjfbjiU9_6cUwI

Thanks in advance! ❤️

Pixel 8 - Shiba
shiba-user 15 AP4A.241205.013 12621605 release-keys

Pixel 9 Pro - Caiman
caiman-user 15 AP4A.241205.013 12621605 release-keys

Pixel 8 Pro - Husky
husky-user 15 AP4A.241205.013 12621605 release-keys

Pixel 9 - Tokay
tokay-user 15 AP4A.241205.013 12621605 release-keys

Pixel 9 Pro XL - Komodo
komodo-user 15 AP4A.241205.013 12621605 release-keys

Pixel 8a - Akita
akita-user 15 AP4A.241205.013 12621605 release-keys

Pixel 9 Pro Fold - Comet
comet-user 15 AP4A.241205.013 12621605 release-keys

Pixel 7 Pro - Cheetah
cheetah-user 15 AP4A.241205.013 12621605 release-keys

Pixel 6 Pro - Raven
raven-user 15 AP4A.241205.013 12621605 release-keys

Pixel 5 - Redfin
redfin-user 14 UP1A.231105.001.B2 11260668 release-keys

I'm free 🫡

No more⭐️for me? 🥲

Gzip->Base64, Expired !

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

🚨 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?

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

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

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

be aware from Chinese keybox sellers*? 🤣

Pixel Props pinned «Hey PixelProps Community! Exciting news! We're launching a Design Contest to find a new logo and branding for PixelProps. If you're passionate about design, this is your chance to shine! - Submit your original designs by 4-6 weeks from announcement. - Vote…»

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

Apparently another keybox has been leaked.
The November Beta (BP11) have been released on Pling.
You should be able to pass Strong once again !
Enjoy.

Hey PixelProps Community!

Exciting news! We're launching a Design Contest to find a new logo and branding for PixelProps. If you're passionate about design, this is your chance to shine!

- Submit your original designs by 4-6 weeks from announcement.
- Vote for your favorites right here on GitHub.
- Win $20 in USDT, get credited on our Telegram channel, and potentially join our design team.

Check out the details and submit your entries on our GitHub issue: https://github.com/Pixel-Props/build.prop/issues/21

Let's make PixelProps visually unforgettable together!

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.

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

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

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

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

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

Pixel 8 Pro - Husky
husky-user 15 AP3A.241105.007 12470370 release-keys

Pixel 9 Pro Fold - Comet
comet-user 15 AP3A.241105.008 12485168 release-keys

Pixel 8 - Shiba
shiba-user 15 AP3A.241105.007 12470370 release-keys

Pixel 6 Pro - Raven
raven-user 15 AP3A.241105.007 12470370 release-keys

Pixel 5 - Redfin
redfin-user 14 UP1A.231105.001.B2 11260668 release-keys

https://t.me/pixelpropschat/17821

Here Pling currently has issues.

If you guys wanna give it a try, I had added it to Pling (CrawlPIF) !

Therefore i personally wasn't able to pass CTS profile with my own device as its either not running A15 and/or is running a different security patch.?

Quick showcase of the upcoming pif scalping feature for non beta 😎
Edit: Available on Pling

Apparently the non beta can still pass strong as it downloads the pif.json from chiteroman GitHub.

Google banned the Pixel 9 Pro XL (komodo) fingerprint. I will be adding more in a couple of hours.

Quick showcase 😁

I've added latest builds to Pling !

What changed?
From now on the PixelProps will have volume key selection by default on the Safe/Sensitive Modes. Else can be manually set on the module directory/config.prop

When using an older ROM make sure to set Safe SDK to true so that you don't break CTS Profile.

If you have bootloop issues set all of the Safe/Sensitive modes to true!

Follow-up on LSPosed Team’s Actions and the Continuation of Their Project

28 Oct 2024:

Barely a year after my initial post on 15 Dec 2023, where I raised concerns regarding the detectability of LSPosed by third-party apps and highlighted the unprofessionalism surrounding it, significant developments have occurred. The LSPosed team, who had previously announced they would cease working on the project shortly after my post, has now reversed their decision and resumed development. This flip-flop move appears to be a calculated attempt to discredit my concerns and generate hate toward me, further exemplifying the lack of transparency and professionalism I initially pointed out.

Notably, this decision to continue development comes suspiciously right after the emergence of a popular fork of LSPosed called "LSPosed-Irena", which has gained traction in the community. It raises questions about whether the LSPosed team is trying to reclaim relevance by potentially basing their future work on this highly-regarded fork. The timing of these actions suggests a reactive, rather than proactive, approach to innovation and project management, continuing the pattern of questionable practices within the LSPosed team.

In light of these events, I reiterate the importance of discussing the implications this has on privacy and security. The detectability of LSPosed by third-party apps, which remains a core concern, continues to pose risks to users who rely on these tools for legitimate purposes. Additionally, the behavior of the LSPosed team in relation to the wider developer community — including spamming repositories, as I previously mentioned — reflects poorly on their commitment to fostering a healthy, collaborative development environment.

For those who may have missed the context, my initial post shed light on how the LSPosed team had, at one point, created a native detection project, only to remove it later after forks emerged. My attempts to address these issues were met with hostility, leading to my expulsion and banning from their group. This pattern of behavior, along with their recent actions, continues to highlight the need for accountability and professionalism in the development community.

As we move forward, it is crucial to remain vigilant and push for transparency, especially when projects like LSPosed have such widespread influence over user privacy and security. The emergence of alternatives like LSPosed-Irena is a reminder that there are better ways to govern these types of projects — ones that prioritize the community’s needs over personal agendas.

Let’s continue to advocate for a more open, secure, and professional development environment that upholds the values of transparency and user protection.

Thank you for your support and for continuing to engage in this important conversation.

What do you guys think about this? The first screenshot shows when configs are already set. The second screenshot shows when a config is missing and asks for the user to set it.

New Game — DeGENS!

💡 From the creators of the well-known Cats and Activity Launcher, as well as the top mobile game publisher Azur Games!

🐸 The essence of the game is the combination of crypto characters: the higher the character's level, the more income you earn!

🔥 Today, the first beta version has launched with a limited number of participants; the first players can earn extra rewards. So, don’t miss out!

What do we do?

1️⃣ Join the bot @DegensCryptoBot
2️⃣ Open eggs and combine characters
3️⃣ Improve various metrics (egg spawn speed, character rank, passive income, etc.)
4️⃣ Spin the wheel of fortune
5️⃣ Tap (the higher the character's rank, the more you earn per tap)
6️⃣ Complete tasks (some are basic, while others are hidden under specific characters)
7️⃣ Invite friends and receive additional rewards

🍬 The game is super interesting, and considering the founders' project capabilities, there’s a great chance for good drops!

‼️ They have over 11 million subscribers on their channel. The official game launch hasn’t happened yet. You get exclusive access to the game. Be one of the first to join!

Has anyone else experienced issues with device CTS profile certification tests on the latest Android 15 beta releases? We're unable to pass them, which makes me wonder if Google is about to drop the official version and thus closing beta tests. 🤔

I had updated the props once again, Now it should pass Strong. Still trying to figure out why exactly it cannot pass CTS profile meanwhile i am using the original Pixel Props... Google what are you doing?!

Finally brought an update to build.prop (commit 1452c8a)
Check it out !

Hotfix v6.4.8.3
This hotfix addresses an issue where boot.hash was not correctly verifying the presence of the necessary file.

Action Required:
1. Obtain your verifiedBootHash: Use the KeyAttestationDemo to retrieve your device's unique verifiedBootHash.
2. Set the verifiedBootHash: Save your verifiedBootHash to a file named boot.hash in the /data/adb/ directory on your device.

Troubleshooting:
If you encounter problems with hexpatch not removing properties, ensure you have removed any duplicate magiskboot files. These duplicates can sometimes be leftover from using KSU and not properly cleaning up files afterward.

Pixel Props pinned «Power Up Your Digital Experience with PetroSky VPS Solutions! Hello there, tech enthusiasts and digital explorers! More recently, I've encountered some cool VPS solutions that might just change the game of working, playing, and creating in the digital world.…»

Pixel 9 Pro XL - Komodo
komodo-user 14 AD1A.240905.004 12196292 release-keys

Pixel 8 - Shiba
shiba-user 14 AP2A.240905.003 12231197 release-keys

Pixel 8 Pro - Husky
husky-user 14 AP2A.240905.003 12231197 release-keys

Pixel 9 - Tokay
tokay-user 14 AD1A.240905.004 12196292 release-keys

Pixel 8a - Akita
akita-user 14 AP2A.240905.003.A1 12234140 release-keys

Pixel 9 Pro Fold - Comet
comet-user 14 AD1A.240905.004 12196292 release-keys

Pixel 9 Pro - Caiman
caiman-user 14 AD1A.240905.004 12196292 release-keys

Pixel 7 Pro - Cheetah
cheetah-user 14 AP2A.240905.003 12231197 release-keys