Tricky Store OSS | Updates
Ir al canal en Telegram
Mostrar más
El país no está especificadoLa categoría no está especificada
867
Suscriptores
Sin datos24 horas
-67 días
-1230 días
Archivo de publicaciones
Just letting everyone know that I'll be inactive for a few weeks starting tomorrow because of personal reasons. I'll be back by the first week of October, until then development of Tricky Store OSS will be paused.
Just a heads up on what to-dos I have set for the next release:
- Fix known detection points (includes native detector and native test)
- Emulate missing operations
- Fix bugs that exist in the staging branch (ci builds)
Thank You
Tricky Store OSS: A tricky of keystore they forgot to hide
Remember when someone said:
Due to the rampant misuse and the contributions received after open-sourcing being less than expected, this module will be closed-sourceTranslation: "Thanks for the PRs, I'll take it from here… behind locked doors." - AOSP headers? Borrowed/License headers stripped. - LGPLv3 library? Linked statically, license violated. - "PRs welcome"? Sure — until it's "all rights reserved." Know more: https://github.com/beakthoven/TrickyStoreOSS/blob/main/docs/5ec1cff-violations.md So I built Tricky Store OSS: - 100% FOSS (GPLv3 licensed) - Clean rewrite, not “borrowed or forked" - Same features, less sus If your keystore hack locks the source along with your bootloader... maybe it’s time for OSS. https://github.com/beakthoven/TrickyStoreOSS Channel: @TrickyStoreOSS Chat: @TrickyStoreOSS_Chat
