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://news.1rj.ru/str/meetstrong/91
- Join Here : PlayStrong
- Read Post : https://news.1rj.ru/str/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.
👍49
Wtf, my other android phone which I use for banking, only pass Device Integrity, and its not rooted or unlocked yet😱.
🤔14🫡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.
👍1
I think I should buy Google Pixel and use GrapheneOS😂
🫡34🔥8👍3🤔3🤯1👨💻1
Citra Integrity Trick
Okay, you dont want people to take benefits of your work by decoding this right ? so dont share it in the group.
The invitation is limited by the way.
The invitation is limited by the way.
🫡3
Btw guys, I will renew the /notes.
Will focus on passing DroidGuard and Integrity.
Especially for stockrom.
Will focus on passing DroidGuard and Integrity.
Especially for stockrom.
❤🔥19👍2
Forwarded from KernelSU Next
This media is not supported in your browser
VIEW IN TELEGRAM
Now we officially have an online module repo but it's gonna be limited and UpTo my choice on which modules should be there
But if you have any suggestions
Then you can PR it to
https://github.com/KernelSU-Next/KernelSU-Next-Modules-Repo
But if you have any suggestions
Then you can PR it to
https://github.com/KernelSU-Next/KernelSU-Next-Modules-Repo
👍2
KernelSU Next
Now we officially have an online module repo but it's gonna be limited and UpTo my choice on which modules should be there But if you have any suggestions Then you can PR it to https://github.com/KernelSU-Next/KernelSU-Next-Modules-Repo
This is good.
My opinion, its better to allow custom repo link, and use
Mostly module on github has the
but
This is just my opinion, cuz if its me I dont have time to keep updating the repo, denoscription, updatelink and others.
My opinion, its better to allow custom repo link, and use
module.prop format.Mostly module on github has the
module.prop so directly use it, no need to write it manually.but
module.prop path is not static, so need auto crawl and find module.prop.This is just my opinion, cuz if its me I dont have time to keep updating the repo, denoscription, updatelink and others.
Citra Integrity Trick
This is good. My opinion, its better to allow custom repo link, and use module.prop format. Mostly module on github has the module.prop so directly use it, no need to write it manually. but module.prop path is not static, so need auto crawl and find module.prop.…
Example :
https://github.com/KOWX712/PlayIntegrityFix/blob/inject_s/module%2Fmodule.prop
Following updateJson
https://raw.githubusercontent.com/KOWX712/PlayIntegrityFix/inject_s/update.json
zipUrl= will be the download source and will be flashed by KSU when user click install.
https://github.com/KOWX712/PlayIntegrityFix/releases/download/v4.4-inject-s/PlayIntegrityFix_v4.4-inject-s.zip
This is the same as updating module, but the difference is the module is not installed yet.
https://github.com/KOWX712/PlayIntegrityFix/blob/inject_s/module%2Fmodule.prop
id=playintegrityfix
name=Play Integrity Fix [INJECT]
version=v4.4-inject-s
versionCode=44
author=chiteroman, KOWX712
denoscription=Universal modular fix for Play Integrity on devices running Android 8-16
updateJson=https://raw.githubusercontent.com/KOWX712/PlayIntegrityFix/inject_s/update.json
Following updateJson
https://raw.githubusercontent.com/KOWX712/PlayIntegrityFix/inject_s/update.json
{
"version": "v4.4",
"versionCode": 44,
"zipUrl": "https://github.com/KOWX712/PlayIntegrityFix/releases/download/v4.4-inject-s/PlayIntegrityFix_v4.4-inject-s.zip",
"changelog": "https://raw.githubusercontent.com/KOWX712/PlayIntegrityFix/inject_s/CHANGELOG.md"
}zipUrl= will be the download source and will be flashed by KSU when user click install.
https://github.com/KOWX712/PlayIntegrityFix/releases/download/v4.4-inject-s/PlayIntegrityFix_v4.4-inject-s.zip
This is the same as updating module, but the difference is the module is not installed yet.
GitHub
PlayIntegrityFix/module/module.prop at inject_s · KOWX712/PlayIntegrityFix
Fix Play Integrity verdicts. Contribute to KOWX712/PlayIntegrityFix development by creating an account on GitHub.