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…

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

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

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

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.

? Important Announcement for Our Valued Community ?

I'm excited to unveil @Reversrs, a new platform dedicated to advancing our shared passion for digital forensics and reverse engineering.

? Channel Focus:
• Cutting-edge forensic methodologies
• Advanced reverse engineering techniques
• In-depth tool analyses and comparisons
• Emerging trends in cybersecurity

? Featured Tools:
Get insights on industry-leading software like Oxygen Forensic Detective, Cellebrite Suite, IDA Pro, and VMProtect, among others.

? Exclusive VIP Access:
For those seeking to elevate their expertise, our VIP @Reversrs group offers:
• Full access to premium tools
• Collaborative projects with industry experts
• Personalized mentorship opportunities

To join the VIP tier:
1. Demonstrate exceptional skills
2. Contribute valuable research or methodologies
3. Inquire about our membership options

This channel represents our commitment to fostering a community of elite practitioners. Join us in shaping the future of digital investigation.

#DigitalForensics #ReverseEngineering #CybersecurityExperts