Zygisk cannot activate on some old Samsung devices with old kernel (3.19-)

[yujincheng08]

For some old Samsung devices, there's a kernel restriction that whenever exec an ELF from /proc, the process can no longer call some systemcalls. For kernel 3.19+, the workaround is fexecve, but it does not exist for the old kernel. Users with those devices should use a custom kernel bypassing such a restriction or a newer version.

[chaoscalm]

I am on GalaxyS5 with kernel 3.4.113 which is even older, and Zygisk is successfully activated, I won't blame old samsung devices for something that seems a kernel regression affecting your device.

[pndwal]

I am on GalaxyS5 with kernel 3.4.113 which is even older, and Zygisk is successfully activated, I won't blame old samsung devices for something that seems a kernel regression affecting your device.

@yujincheng08 is a dev; This Wontfix issue pinned as a notice is a spin-off of her fix:
[Refactor Zygisk loading]
ff7ac58

Basically, Zygisk was not turning in for S8 and earlier Sammy phones:
#5353
The issue was fixed for devices with kernel version >= 3.19:
#5372

... There is no specific device! This is a general Wontfix notice re Zygisk issue on "some Samsung devices w/ pre 3.19 kernel version...

[canyie]

@hanoshita It depends on was Samsung added their stupid exec limitation in the kernel of your device, or not. If Zygisk works on your device, just enjoy it. This is just a notice which points out Zygisk bug reports from Samsung devices using old kernels will be ignored.

[gregsskyles]

Device: Samsung Android version: N/A Magisk version name: N/A Magisk version code: 24102
For some old Samsung devices, there's a kernel restriction that whenever exec an ELF from /proc, the process can no longer call some systemcalls. For kernel 3.19+, the workaround is fexecve, but it does not exist for the old kernel. Users with those devices should use a custom kernel bypassing such a restriction or a newer version.

Thank you for such a clear, understandable and explicit explanation of the issue!

[yujincheng08]

Device: Samsung Android version: N/A Magisk version name: N/A Magisk version code: 24102
For some old Samsung devices, there's a kernel restriction that whenever exec an ELF from /proc, the process can no longer call some systemcalls. For kernel 3.19+, the workaround is fexecve, but it does not exist for the old kernel. Users with those devices should use a custom kernel bypassing such a restriction or a newer version.

Thank you for such a clear, understandable and explicit explanation of the issue!

It is just a copy from this issue... He is just spamming.

[gregsskyles]

Sorry, missed the earlier comment- came in the middle of this issue. But the thanks still applies to the OP.

[praveen28624]

I have Samsung device. It's kernel version is 3.18.140. I have same issue

[lovelylittleheart]

Tried to install from magisk 21.4 and Disable_Dm-Verity_ForceEncrypt_03.04.2020 with TWRP and update magisk to latest version all normal Zygisk is on. Tried Patch Magisk 24 to AP File Samsung Zygisk won't turn on. Must Change init.rc

Kernel : 3.18.140

[IverCoder]

The latest Canary has fixed this issue. The changelog says so and I have tested it on kernel v3.10.

[praveen28624]

The latest Canary has fixed this issue. The changelog says so and I have tested it on kernel v3.10.

How do I get latest canary?

[praveen28624]

Tried to install from magisk 21.4 and Disable_Dm-Verity_ForceEncrypt_03.04.2020 with TWRP and update magisk to latest version all normal Zygisk is on. Tried Patch Magisk 24 to AP File Samsung Zygisk won't turn on. Must Change init.rc

Kernel : 3.18.140

How do I get magisk 21.4

[pndwal]

The latest Canary has fixed this issue. The changelog says so and I have tested it on kernel v3.10.

I think there is no fix as stated.

Some 3.19- kernels have the exec limitation, some don't, so some will work w/ Zygisk and some won't...

[xx979xx]

I have Samsung S8 (SM-G950F) running Android 9 Pie, I struggled with this issue and I find the solution that worked for me very well. My kernal is not older than 3.19 obviously.
1- Download and install Magisk canary 24.1 721d8d3(24101) from #5353 Do not install the latest canary.
from @yujincheng08:

At last, plz try this: app-debug.zip

2- After installation, rename the file to magisk.apk and install the manger.
3- Only upgrade the manager to latest canary for better functionality. Do not upgrade Magisk!!!

[yujincheng08]

I came up with an idea that may fix this:

use /system/bin/linker[64] /proc/self/fd/x to exec the origin app_process

but /proc/self/exe is the linker...

[luca990]

hi, with latest canary works, tested on Samsung S7 LineageOS 18.1 Android 11 kernel 3.18.140

[nm17]

I came up with an idea that may fix this:

@yujincheng08 So is this issue a wontfix or not? Is there a fix planned?

[ipdev99]

Canary 24102 broke Zygisk on Nexus 7 (2013) and Pixel C tablets.
[arm kernel 3.4.113] and [arm64 kernel 3.18.140]
After this commit 183e5f2 Zygisk again works on Nexus 7 (2013) and Pixel C tablets.
Both are currently running Lineage 19.1 builds.

[canyie]

@ipdev99 The issue we are talking about is only for Samsung devices

[nm17]

@canyie I think I have the same issue on a Meizu M5 Note (old phone, around Android 7). Not sure how to prove it though. Kernel v3.18.35 on a aarch64.

[canyie]

@nm17 I think it's better to open a new issue for that. Upload boot logcat so devs can take a look.

[canyie]

Fixed by 9fbd079