This is not an officially supported topjohnwu project
Lygisk is a Magisk fork correcting one of the few mistakes legendary @topjohnwu did not fix (yet).
Lygisk fixes the needed /data access in addon.d,
which fails to reinstall Magisk during OTA
if the device does not support FBE decryption in recovery
(more details below).
Brought to you by @Linux4, @programminghoch10 and @binarynoise.
Thanks to @jesec for the initial work. Read more about this here.
Get the latest stable here: Direct Download from GitHub
Any other variant can be downloaded by clicking its name below.
We supply you with four variants of Lygisk:
Stable: Stable and tested versions, which have been manually ported from Magisk stable and have been tested to workBeta: Automated ci-builds from the latest magisk stableCanary: Automated ci-builds from the latest magisk canaryMadness: Automated ci-builds from the latest magisk master
We recommend stable or beta for normal usage.
If you want any of the latest Magisk features you can try canary but we can't guarantee anything there.
If you're a real madlad you can also use madness but only truly insane people would want to do that.
For canary or madness you need to add a custom update URL.
| variant | custom update URL |
|---|---|
| stable | https://programminghoch10.github.io/Lygisk/stable.json |
| beta | https://programminghoch10.github.io/Lygisk/beta.json |
| canary | https://programminghoch10.github.io/Lygisk/canary.json |
| madness | https://programminghoch10.github.io/Lygisk/madness.json |
(stable and beta are just listed for completeness)
For installing Lygisk, just rename the downloaded file to .zip and sideload it.
If the Lygisk app doesn't appear after installation, install the apk manually.
For installing by patching bootimages, use Magisk instead.
Migrating from Magisk to Lygisk is easy and does not remove installed modules.
Just uninstall the Magisk app and install Lygisk via recovery. Full uninstall should not be necessary.
It's the same way for switching back to Magisk.
Lygisk has been developed for one specific case:
A-onlydevice/datais encrypted- the recovery cannot decrypt
/data - the recovery is
addon.dcapable
This is the case for every A-only LineageOS device running the LineageOS recovery.
If you patch boot.img, use Magisk.
If you have /data not encrypted, use Magisk.
If you have an addon.d-compatible recovery (such as LineageOS recovery) with encrypted /data, use Lygisk.
Magisk stores only parts of the install script in addon.d.
All other files required for installation are placed within /data,
which (in our case) is encrypted and thus unavailable.
Lygisk will keep all required files for reinstallation ready within addon.d.
If you use Lygisk with unencrypted /data, it won't give you any advantage over Magisk.
Please only report bugs to us if you are sure that they appear because of our work. If you are unsure, just try out Magisk and if the same issue appears there, report it there.
Only report bugs on stable builds.
If you need to report a bug, install the debug variant first.
In your bug report include a logcat, dmesg, the Lygisk logs found inside the app and /tmp/recovery.log for addon.d and install issues.
Join our Telegram Group for asking quick questions or to get the latest news directly.
Anything further is equal to Magisk.
You can go and check their resources.
Our license obviously is the same as Magisk's license
Magisk, including all git submodules are free software:
you can redistribute it and/or modify it under the terms of the
GNU General Public License as published by the Free Software Foundation,
either version 3 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program. If not, see <http://www.gnu.org/licenses/>.