programminghoch10 / lygisk Goto Github PK

For that reason the manager doesn't get installed after boot and needs to be installed manually

It seems possible that the addon.d would be removed from Magisk, and a Magisk module was cooked up to deal with addon.d. Anyway, it seems cleaner to do this in a module. It seems possible to port the patches there.

Lygisk Canary doesn't automatically update from latest magisk, seems like a code they did broke it, fix needed

Very happy with Lygisk (it survives reboots on my Galaxy Note 10 + LOS 20.0) but It seems that Lygisk is not updated as often as Magisk. (still says v27.000)
Is Lygisk just a point-in-time fork of Magisk, or will it be updated with backports, too?

There is a problem when you hide the Manager and want to use it from a secondary user. Only the stub gets installed for him and the stub prompts the user to download the full app, so it can load it and show the Manager. That fails.
In logcat we find java.io.FileNotFoundException: https://cdn.jsdelivr.net/gh/topjohnwu/[email protected]/app-release.apk

In https://github.com/programminghoch10/Lygisk/blob/master/stub/build.gradle.kts#L17 there is a link to some Magisk APK, getting the correct version by looking at https://github.com/programminghoch10/Lygisk/blob/master/config.prop.sample#L7 which we don't override, so the lookup fails as the file does not exist because the correct version would be v25.2 instead of v25.200.

On my Samsung S6 Lite, there is a separate vbmeta partition. When I update LOS, the system cannot boot anymore, saying that the magic code and the signature of vbmeta is incorrect.

The terminal output of survival scripts is however all "OK".

In the guide of magisk, these cases are distinguished manually.

It can only be solved by formatting system partition and flash again LOS, then Lygisk.

Hey,

the usual Magisk Manager for Recovery Module wont work, my installation fails instantly.
I could imagine why, and guess its due to different file systems.
So asking the dev for the Module may not be suitable, thats why I ask here:

Any way to Manage Lygisk from Recovery via adb?
(@Linux4 I use LOS Recovery and some File Based Encryption device, so there is no way for me to use the Recovery and mount/decrypt the system/data and manipulate in there from Recovery. I may try via adb shell but that would require constant activation of USB Debugging, so a security risk - which is why some Recovery based manipulation to atleast deactivate Lygisk would be great).

Thanks

Ps.: If have not narrowed down the problem properly I am happy to receive advise how to understand the situation.

EDIT: Okay after using https://themagisk.com/magisk-manager-for-recovery-mode/ which fails to install,
I found https://github.com/Rikj000/Magisk-Manager-for-Recovery-Mode/releases which installs fine. So it was no filesystem issue but just the version issue.
Hard to find .
Anyways: The Module wont work as expected.

I still end up with the issue that my Phone, with LOS Recovery (your lates LOSRecovery 12.1 for SamsungGalaxyS10+/G975) and FBE(knox) + activated USB Debugging + Root Debugging + Host Device RSA Key accepted wont work as expected: I start LOS Recovery and mount the system and ADB sideload, but have no ADB shell access to the system.
I can ls and cd to my sdcard, but there is no mm folder in there.
Also, any other system access wont work - f.e. pm.

How to get adb root access to the system?
How to decryopt/mount the system with the LOS Recovery?
I know thats less Lygisk than LOS Recovery, but I just ask here. If you like me to repost it at some LOS Recovery threat in XDA just go ahead

Hello!

Canary and Madness still point to dated versions of Lygisk/Magisk.

Can you bump Canary to 26404 or at least Madness?

I cannot seem to be able to updeate Shamiko, as the latest version in Lygysk Madness is 26402 and Shamiko requires 26404 or newer.

Not an issue of course but i didn't know how to ask/request.

Cheers and thanks for the awesome work 🥂🥂

In Settngs-> App-> Hide the Lygisk App, the behavior isn't as expected.

Expected Behavior:
Renaming the App reloads the system and app, after reload the system/launcher should rename the app to the changed name with annoying generic Android head icon. (This behavior works on current upstream)

Actual Behavior:
System and app are reloaded/refreshed, app icon changed, app name not changed.

Device/OS: Samsung SM-P610, Lineage OS 18.1

Long Version:
Clicking the 'button' to begin the process loads another screen, which is typical, and prompts the user to choose a new name for the app. I've chosen 'Manager', rather than the default 'Settings', but the behavior I'm about to describe remains regardless of the name typed in. Next the app asks for a confirmation, and whether or not the user wants to add to the the home screen- I've done this both ways. Result- ugly icon, but app is still named Lygisk. Tried with/without icon on desktop, rebooting, with/without modules loaded, Trebuchet & Nova Launcher, all results the same.

It says "unsupported environment". I've heard this is due to Shamiko scanning Lygisk's signature. Is there a way to just pretend to be regular Magisk? (Make all signature verification return TRUE?)

Do not put APK s into repo.. Github has already given bad fingers at OpenGapps for doing exactly that.. Use the releases feature instead...

Ignore it or something else?

Apparently in the Lygisk app it's not possible to install modules directly from the official magisk repository. However manual installation works just fine

I cannot select this option in Lygisk 26.4 latest stable after updating OS.

This option is really useful so I do not have to flash Lygisk in recovery in LineageOS.after update.

Device: Sony Xperia 1 III
OS: Latest official LineageOS build

Hi, Some mediatek devices have restrictions to flash boot partition in system, read-only fs, etc. direct install not working. Since 26.1 magisk requires install from system (direct or patch boot) i need to build lygisk manually to fix that. Can you revert 4e55ead or parent commit?

Situation:
Currently on Lygisk v24.300
Manager indicates an update for the app to v25.100, which installs flawlessly.
New version of the Manager indicates an update for Lygisk, which does not install and exits with a failure code: 1.

Sideloading v25.100 works though, but then the Manager disappears.
Trying to install the Manager manually from the APK seems to work, but the app does not open and has disappeared from the system.
Device is still rooted though.

The only way for me to recover was sideloading Magisk v25.100, installing the Magisk Manager, and from there I could restore the boot image and delete the Magisk Manager app.

Installing v25.100 through sideload with the original boot image also results in a disappearing Manager app. I uninstalled Lygisk again with the method above. Now I'm back on v24.300 and the app is staying.

Can you please upgrade to Magisk 25? Current ci release is still on 24.3.

I got a reminder that an new Magisk 26 is out. Downloading it - do I download Magisk or Lygisk?
That is not clear.
As of now you can here download latest stable or canary but there is no info about what version it is actually.
Would be great to have this info (and maybe keep one older version too, just in case).
Anyhow, thanks for sharing!

I had to reflash lygisk with ADB as suggested within install. It kept the modules, but the root was gone. Then I had to install lygisk as an APK, because the root apps and modules were there, but lygisk wasn't

Hi together,
first of all many thanks for your efforts! I've been happy Lygisk user for some years. 😃

Today I updated LOS 18.1 and Lygisk on a long time unused device, to find out that it bootloops with all available Lygisk versions.

So I tried upstream Magisk and found out, that all versions > 26.1 also bootloop. Magisk 26.1 works fine but of course doesn't survive LOS updates. 😋

Would you please point me to the download of Lygisk 26.1? Maybe I'm blind, but I cannot find a Releases page. 🙈

Thank you very much! 😃

As far as I am aware, Magisk will be removing Magisk Hide support (because of politics?)
Will Lygisk still support and maintain MagiskHide when official Magisk hide is removed?

Although hardware based detections may not work, but most of the apps work if we simply just hide root from app (using Magisk Manager).

Currently the latest Beta build of Lygisk is 26300. However, some LSposed modules, like Shamiko, require 26302 or greater. Build 26302 is the current beta build of upstream Magisk.

Does Lygisk have a release schedule for how often it tracks available updates from upstream Magisk beta? Very understandable if not, given that this is a hobby fork for a very limited number of devices that Magisk will (hopefully, someday) incorporate into its own supported edge cases.

It is stuck at reverting. Even when I reboot it remains. Any solution?
I want this as root is not recognized in second profile.

When hiding the Lygisk app Lygisk isnt recognized/ working on a 2nd user profile (not the working profile) . Even root isnt detected after a manuaal install of Lygisk on the second profile.

I testen multiple times. Lygisk is working on the second user if the app named by its default.

""We recommend installation via recovery. Just rename the downloaded file to .zip and sideload it.""
Receives an error: Signature Verification failed E:error: 21

This is attempting to rename the downloaded .apk to .zip

please update to the last release

Device: Mi 10T Pro
OS: LineageOS 18.1 for MicroG

Flashing from PBRP. Such an issue happens after the latest build of LineageOS 18.1 for MicroG (I have not tested latest 19.1). There is no issue flashing the patched boot.img.

Here is a part of log:

Target: Redmi/apollo_global/apollo:11/RKQ1.200826.002/V12.5.5.0.RJDMIXM:user/release-keys- Mounting /vendor
- Device is system-as-root
- Mounting /apex/com.android.adbd
- Mounting /apex/com.android.apex.cts.shim
- Mounting /apex/com.android.art
- Mounting /apex/com.android.cellbroadcast
- Mounting /apex/com.android.conscrypt
- Mounting /apex/com.android.extservices
- Mounting /apex/com.android.i18n
- Mounting /apex/com.android.ipsec
- Mounting /apex/com.android.media
- Mounting /apex/com.android.media.swcodec
- Mounting /apex/com.android.mediaprovider
- Mounting /apex/com.android.neuralnetworks
- Mounting /apex/com.android.os.statsd
- Mounting /apex/com.android.permission
- Mounting /apex/com.android.resolv
- Mounting /apex/com.android.runtime
- Mounting /apex/com.android.sdkext
- Mounting /apex/com.android.tethering
- Mounting /apex/com.android.tzdata
- Mounting /apex/com.android.vndk.v30
- Mounting /apex/com.android.wifi
unzip: can't open [.zip]
! Unable to extract zip file!
- Unmounting partitions
- Mounting /vendor
- Device is system-as-root
- Mounting /apex/com.android.adbd
- Mounting /apex/com.android.apex.cts.shim
- Mounting /apex/com.android.art
- Mounting /apex/com.android.cellbroadcast
- Mounting /apex/com.android.conscrypt
- Mounting /apex/com.android.extservices
- Mounting /apex/com.android.i18n
- Mounting /apex/com.android.ipsec
- Mounting /apex/com.android.media
- Mounting /apex/com.android.media.swcodec
- Mounting /apex/com.android.mediaprovider
- Mounting /apex/com.android.neuralnetworks
- Mounting /apex/com.android.os.statsd
- Mounting /apex/com.android.permission
- Mounting /apex/com.android.resolv
- Mounting /apex/com.android.runtime
- Mounting /apex/com.android.sdkext
- Mounting /apex/com.android.tethering
- Mounting /apex/com.android.tzdata
- Mounting /apex/com.android.vndk.v30
- Mounting /apex/com.android.wifi
unzip: can't open [.zip]
! Unable to extract zip file!
- Unmounting partitions
- Mounting /vendor
- Device is system-as-root
- Mounting /apex/com.android.adbd
- Mounting /apex/com.android.apex.cts.shim
- Mounting /apex/com.android.art
- Mounting /apex/com.android.cellbroadcast
- Mounting /apex/com.android.conscrypt
- Mounting /apex/com.android.extservices
- Mounting /apex/com.android.i18n
- Mounting /apex/com.android.ipsec
- Mounting /apex/com.android.media
- Mounting /apex/com.android.media.swcodec
- Mounting /apex/com.android.mediaprovider
- Mounting /apex/com.android.neuralnetworks
- Mounting /apex/com.android.os.statsd
- Mounting /apex/com.android.permission
- Mounting /apex/com.android.resolv
- Mounting /apex/com.android.runtime
- Mounting /apex/com.android.sdkext
- Mounting /apex/com.android.tethering
- Mounting /apex/com.android.tzdata
- Mounting /apex/com.android.vndk.v30
- Mounting /apex/com.android.wifi
unzip: can't open [.zip]
! Unable to extract zip file!
- Unmounting partitions
! Unable to extract zip file!
! Unable to extract zip file!
! Unable to extract zip file!
[libfs_mgr]Unmapped logical partition system
[libfs_mgr]Unmapped logical partition vendor
[libfs_mgr]Unmapped logical partition product
[libfs_mgr]Unmapped logical partition odm
[libfs_mgr]Unmapped logical partition system_ext
[liblp]Partition system will resize from 0 bytes to 1031593984 bytes
[liblp]Partition vendor will resize from 0 bytes to 1172340736 bytes
[liblp]Partition product will resize from 0 bytes to 487784448 bytes
[liblp]Partition odm will resize from 0 bytes to 32444416 bytes
[liblp]Partition system_ext will resize from 0 bytes to 249634816 bytes
[liblp]Updated logical partition table at slot 0 on device /dev/block/by-name/super
Wrote updated marker to /cache/recovery/dynamic_partition_metadata.UPDATED
Patching system image unconditionally...

and

************************
 Lygisk v24.300 addon.d 
************************
- Mounting /vendor
- Device is system-as-root
- Mounting /apex/com.android.adbd
- Mounting /apex/com.android.apex.cts.shim
- Mounting /apex/com.android.art
- Mounting /apex/com.android.cellbroadcast
- Device is system-as-root
- Mounting /apex/com.android.conscrypt
mount: mounting /dev/block/loop4 on /apex/com.android.conscrypt failed: No such file or directory
- Mounting /apex/com.android.adbd
- Mounting /apex/com.android.extservices
- Mounting /apex/com.android.apex.cts.shim
mount: mounting /dev/block/loop7 on /apex/com.android.apex.cts.shim failed: Invalid argument
- Mounting /apex/com.android.i18n
- Mounting /apex/com.android.art
- Mounting /apex/com.android.ipsec
- Mounting /apex/com.android.cellbroadcast
- Mounting /apex/com.android.media
- Mounting /apex/com.android.conscrypt
mount: mounting /dev/block/loop14 on /apex/com.android.conscrypt failed: Invalid argument
- Mounting /apex/com.android.media.swcodec
- Mounting /apex/com.android.extservices
- Mounting /apex/com.android.mediaprovider
- Mounting /apex/com.android.i18n
- Mounting /apex/com.android.neuralnetworks
- Mounting /apex/com.android.ipsec
- Mounting /apex/com.android.os.statsd
- Mounting /apex/com.android.media
- Mounting /apex/com.android.permission
- Mounting /apex/com.android.media.swcodec
- Mounting /apex/com.android.resolv
- Mounting /apex/com.android.mediaprovider
- Mounting /apex/com.android.runtime
mount: mounting /dev/block/loop26 on /apex/com.android.runtime failed: Invalid argument
- Mounting /apex/com.android.neuralnetworks
- Mounting /apex/com.android.sdkext
- Mounting /apex/com.android.os.statsd
- Mounting /apex/com.android.tethering
mount: mounting /dev/block/loop30 on /apex/com.android.tethering failed: Invalid argument
- Mounting /apex/com.android.permission
- Mounting /apex/com.android.tzdata
- Mounting /apex/com.android.resolv
- Mounting /apex/com.android.vndk.v30
- Mounting /apex/com.android.runtime
- Mounting /apex/com.android.wifi
unzip: can't open [.zip]
! Unable to extract zip file!
- Unmounting partitions
- Mounting /apex/com.android.sdkext
mount: mounting /dev/block/loop37 on /apex/com.android.sdkext failed: No such file or directory
- Mounting /apex/com.android.tethering
- Mounting /apex/com.android.tzdata
- Mounting /apex/com.android.vndk.v30
- Mounting /apex/com.android.wifi
- System-as-root, keep dm/avb-verity
- Encrypted data, keep forceencrypt
- Target image: /dev/block/sde50
/tmp/addon.d/99-magisk.sh: eval: line 1: /system/bin/dalvikvm: not found

When opening the Lygisk app, Zygisk status displays "No." Additionally, app pops up with error: "Requires Additional Setup... Your device needs reflash Magisk to work properly. Please reinstall Magisk within app, recovery module cannot get correct device info."

Is this normal? Or should I proceed with the "Direct Install"?

First time migrating from Magisk to Lygisk, so a bit lost. Additionally, Google search results is confusing "Lygisk" with "Magisk" so can't get the correct search results.

Edit: Should add some context: I installed Lygisk via LineageOS recovery. Also factory reset/wiped device before doing so.