Tricky Store now has its open source alternative!
The popular Tricky Store module, which is used for modifying the certificate chain generated for Android Key Attestation, finally has its open source alternative. This module is flashed along with Play Integrity Fix/Fork to pass the Integrity Test on rooted devices or custom ROMs. However, there was one major issue with this- it has been closed source beginning with version 1.1. Here’s what the developer 5ec1cff had to say in this regard:
Due to the rampant misuse and the contributions received after open-sourcing being less than expected, this module will be closed-source starting from version 1.1.0.
While this module was still getting this job done, however, there’s always an element of risk involved in using a closed-source app/module. Thankfully, you can now put all your doubts to rest. This is because we finally have a FOSS alternative to Tricky Store! Made by the developer beakthoven, it’s titled TrickyStoreOSS and should now be your go-to choice. Here’s why.
- Why You Should Switch to FOSS Tricky Store 🔓🔑 Open Sourced 📦 Use of Open-Source Code Without Proper Licensing 🚫 “All Rights Reserved” 🔒 Shift to Fully Closed-Source
- How to Flash New Open Source TrickyStoreOSS
- Concluding Remarks
Why You Should Switch to FOSS Tricky Store
🔓🔑 Open Sourced
The first and most obvious reason to choose this module is its open-source nature, so everything that’s going on with this module is right there in front of your eyes. Apart from that, it follows the GPL-3.0 License as well, which is not the case with its closed-source counterpart.
Apart from that, here are a few “violations” that the original module by 5ec1cff seems to have done, as explained by the developer Beakthoven [the man behind the FOSS version of this module]:
📦 Use of Open-Source Code Without Proper Licensing
Took headers from AOSP for stubbing without providing proper attribution or respecting licensing norms. Statistically linked an LGPLv3 library into their binary but failed to release their source or comply with LGPL requirements.
🚫 “All Rights Reserved”
Initially published code with no license, making it “all rights reserved” despite using open-source components. Invited pull requests (“PRs welcome”) while keeping the code legally closed – taking from the community without giving back.
🔒 Shift to Fully Closed-Source
After releasing a few open-source versions, they decided to fully close-source the project with: -Encrypted module binaries -Obfuscated APKs
How to Flash New Open Source TrickyStoreOSS
The flashing steps are the same as before. Here’s what you need to do:
- Launch Magisk / KernelSU / APatch and uninstall the older Tricky Store.
- Then download the open-source TrickyStoreOSS from its GitHub page .
- Go to the Modules section, hit Install, choose this module, and install it.
- After that, do a reboot, and that’s it; the module will be up and running.
Concluding Remarks
While I am not the one to take sides, but here the choice and its reasoning are right in front of your eyes. Just to reiterate it once again, the “closed-source” module is still doing its job as intended, but it’s those two words that would repel me from trying out this module from now onwards, more so because we have finally got an open-source alternative at hand.
What are your views on it? Are you still going to stick with the original one because you don’t want to try out a newer one, or is FOSS something that is included in every love story of yours, if there’s one [ouch, shots fired!].
- What is the Target TXT File in Tricky Store, and How to Use it?
- Cannot Set Security Patch Date via Tricky Addon/KsuWebUI [Fix]
- How to Pass Strong Integrity Using Revoked/Banned Keybox File
- How to Run Banking Apps on Rooted Android Device [14 Methods]
(Cancel Reply)
Δ
