Detector to pass :
- Disclosure
- Native Detector
- Hunter ( No Source )
Your setup to configure :
- Re/Zygisk Next
- TEESimulator/TrickyStore
- TSupport Advance / Play Integrity Fix
- KP-Next
- Meta Module ( KSU Only )
- LSPosed : HMA-OSS, FuseFixer.
- Disclosure
- Native Detector
- Hunter ( No Source )
Your setup to configure :
- Re/Zygisk Next
- TEESimulator/TrickyStore
- TSupport Advance / Play Integrity Fix
- KP-Next
- Meta Module ( KSU Only )
- LSPosed : HMA-OSS, FuseFixer.
π8π₯3π±1
My Experience using A16.
When I open some app, it will automaticaly paste my clipboard. I dont know what it for, but a toast showed.
I think this is a vulnerability on A16 or maybe its an old vulnerability.
Do you know any CVE related?
When I open some app, it will automaticaly paste my clipboard. I dont know what it for, but a toast showed.
I think this is a vulnerability on A16 or maybe its an old vulnerability.
Do you know any CVE related?
Question, is FP updater from TSupport help you ?
Anonymous Poll
34%
Yes
21%
No
45%
Neutral ( I didnt care/use )
TSupport-Advance.zip
17.9 KB
R260115
- Remove FP Updater
+ Added LSPosed trace cleaner
+ Added Suspicious prop detection
- Remove FP Updater
+ Added LSPosed trace cleaner
+ Added Suspicious prop detection
β€βπ₯7
Citra Integrity Trick
TSupport-Advance.zip
Pushed new version. You can update from Manager.
Forwarded from Droidwin
Keybox Might No Longer Work from February 2026!
This change will start from February and April 10th is the last date for it to be implemented... So that could be the last date for your keybox...
This change will start from February and April 10th is the last date for it to be implemented... So that could be the last date for your keybox...
DroidWin
Keybox Might No Longer Work from February 2026!
Well, the dreaded day is near. Google might have put the final nail in the coffin for the kyebox, as they might no longer work from February!
π±21π€―2π¨βπ»1
Droidwin
Keybox Might No Longer Work from February 2026! This change will start from February and April 10th is the last date for it to be implemented... So that could be the last date for your keybox...
Maybe this will be the only solution for us :
- Join Here : PlayStrong
- Read Post : https://t.iss.one/meetstrong/91
- Join Here : PlayStrong
- Read Post : https://t.iss.one/meetstrong/91
Forwarded from PlayStrong
Forwarded from κ±α΄α΄Κα΄Ιͺα΄Ι΄
β οΈ Important
A note about βKitsune Magiskβ and GPL compliance
As you all know about Kitsune Mask by Husky DG, appeared and caused many problems in the community. Recently, a similar project has started again using the same name, created by an unknown person (@X_oEG)
Please keep this in mind:
Magisk is released under the GPL (GNU General Public License). This means that anyone who forks or modifies Magisk must publish the full source code under the same license.
If a fork is closed-source, it is breaking the GPL license.
Many people ask why Magisk Alpha is closed-source and still considered okay
The reason is simple: its developer is an official Magisk collaborator, and John Wu (the original creator of Magisk) gave explicit permission. So it does not violate the license.
However, any other closed-source fork (including βKitsune Magiskβ made by unknown developers) does not have this permission and therefore violates the GPL.
For reference, here is Magiskβs license:
https://github.com/topjohnwu/Magisk/blob/master/LICENSE
Please be careful when using or promoting closed-source Magisk forks from unknown sources.
A note about βKitsune Magiskβ and GPL compliance
As you all know about Kitsune Mask by Husky DG, appeared and caused many problems in the community. Recently, a similar project has started again using the same name, created by an unknown person (@X_oEG)
Please keep this in mind:
Magisk is released under the GPL (GNU General Public License). This means that anyone who forks or modifies Magisk must publish the full source code under the same license.
If a fork is closed-source, it is breaking the GPL license.
Many people ask why Magisk Alpha is closed-source and still considered okay
The reason is simple: its developer is an official Magisk collaborator, and John Wu (the original creator of Magisk) gave explicit permission. So it does not violate the license.
However, any other closed-source fork (including βKitsune Magiskβ made by unknown developers) does not have this permission and therefore violates the GPL.
For reference, here is Magiskβs license:
https://github.com/topjohnwu/Magisk/blob/master/LICENSE
Please be careful when using or promoting closed-source Magisk forks from unknown sources.
π42
Wtf, my other android phone which I use for banking, only pass Device Integrity, and its not rooted or unlocked yetπ±.
π€12π«‘1π1
I think theres a way to spoof kbox, converting it to PKCS#8.
Tricky Store should use this instead raw kbox, maybe.
Well, I dont really understand but some rom use this.
Tricky Store should use this instead raw kbox, maybe.
Well, I dont really understand but some rom use this.
I think I should buy Google Pixel and use GrapheneOSπ
π«‘30π₯4π€3π2π€―1π¨βπ»1