Tricky Store OSS | Updates
前往频道在 Telegram
显示更多
未指定国家未指定类别
867
订阅者
无数据24 小时
-67 天
-1230 天
吸引订阅者
十月 '2610月 '26
十月 '26
+405
在2个频道中
九月 '260
在0个频道中
Get PRO
八月 '260
在1个频道中
Get PRO
七月 '260
在0个频道中
Get PRO
六月 '260
在0个频道中
Get PRO
五月 '260
在0个频道中
Get PRO
四月 '260
在0个频道中
Get PRO
三月 '260
在0个频道中
Get PRO
二月 '260
在0个频道中
Get PRO
一月 '260
在1个频道中
Get PRO
十二月 '250
在0个频道中
Get PRO
十一月 '25
+18
在0个频道中
Get PRO
十月 '25
+890
在0个频道中
Get PRO
九月 '250
在0个频道中
Get PRO
八月 '25
+6
在6个频道中
频道帖子
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
| 2 |  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-source
Translation: "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 | 12 040 |
