Zygisk doesn't work

[sn-o-w]

For some reason, LSPosed doesn't work. I installed it, and I rebooted it the device many times.

"LSPosed is not installed" despite I can clearly see it enabled inside Magisk Manager.

Modules installed:

• Riru v26.1.7.r535.e2f6971ebe
• Riru - LSPosed v1.9.2 (7035)
• SELinux Permissive v2 [DISABLED IN MAGISK MANAGER]
• TrichromeLibrary Squoosh v1.4
• Universal GMS Doze v1.9.0
• YouTube ReVanced v18.45.41 by j-hc

Magisk log: magisk_log_2023-11-26T15.45.21.log

Magisk Installed on device -> R6561D823-kitsune

[sn-o-w]

I also tried the Zygisk version of LSPosed, I enabled Zygisk inside Magisk Settings, but after every reboot of the device, Zygisk stays disabled.

Log: magisk_log_2023-11-26T16.19.32.log

I also enabled "SELinux Permissive v2" this time, but no use.

[HuskyDG]

Record logcat and send here

[Directox01]

The problem is from android version, I believe. On emulators I've tried memu, nox, mumu android 11+ zygisnk doesn't work and keeps asking for a reboot.

[Directox01]

While on LDPlayer 9 works perfectly but its android 9.

[sn-o-w]

Record logcat and send here

Here you go: logcat_2023-11-26.txt

[HuskyDG]

for pid in $(pidof zygote zygote64); do
    cat /proc/$pid/attr/current; echo " $pid";
done

[HuskyDG]

No reply?

[sn-o-w]

No reply?

What do I have to do with that piece of code? I ran it in Termux, but got no response.

[BeanBelly]

Ofc termux, with root access

[BeanBelly]

I run this code on Mumu and it shows:

u:r:init:s0 833
u:r:init:s0 834

It seems zygote is not switching to u:r:zygote:s0

[sn-o-w]

Ofc termux, with root access

I have root access, I typed that command, but got no response.

[HuskyDG]

05-03 03:45:44.044   342   342 I Magisk  : zygisk32: start tracing 335
05-03 03:45:44.044   342   342 I Magisk  : zygisk32: tracing 335 (tracer 342)
05-03 03:45:44.044   342   342 E Magisk  : seize failed with 5: I/O error

[sn-o-w]

for pid in $(pidof zygote zygote64); do
    cat /proc/$pid/attr/current; echo " $pid";
done

This is what I see on the latest Delta version:

I deleted my previous comment because that screenshot came from another Delta version, so it wasn't useful.

[VisionR1]

The problem is from android version, I believe. On emulators I've tried memu, nox, mumu android 11+ zygisnk doesn't work and keeps asking for a reboot.

Here for emulators https://github.com/HuskyDG/magisk-files/issues/8

[sn-o-w]

I installed the latest version, the issue is still present.

[VisionR1]

I installed the latest version, the issue is still present.

Which emulator?

I installed the latest version, the issue is still present.

Which emulator? See my notes here: https://github.com/HuskyDG/magisk-files/issues/8

[sn-o-w]

I installed the latest version, the issue is still present.

Which emulator?

I installed the latest version, the issue is still present.

Which emulator? See my notes here: #8

No emulator, but a real device - Google Nexus 5.

[HuskyDG]

Test this and send logcat app-debug.apk.zip

[sn-o-w]

Test this and send logcat app-debug.apk.zip

logcat_2023-11-27-first-boot.txt logcat_2023-11-27-second-boot.txt

The first log is after I flashed the new boot image patched.

Magisk showed it needed additional setup. Thus, I pressed YES, and the device rebooted and, therefore, the second log.

[Directox01]

I have followed the guide, which instructs to open /system/etc/init/magisk.rc and add the line: umount /system/bin/su. Additionally, I have inserted the seclabel u:r:zygote:s0 line into /system/etc/init/hw/init.rc in the correct section.

Zygisk is now enabled and appears to be functioning without issues from Magisk's perspective, but in the emulator is not loading. Currently, I am testing this on the Mumu emulator running Android 12.

Yes! I have rebooted the system ofc.

Additionally, I can also note that after adding umount /system/bin/su in magisk.rc root getting broken after reboot.

[VisionR1]

I have followed the guide, which instructs to open /system/etc/init/magisk.rc and add the line: umount /system/bin/su. Additionally, I have inserted the seclabel u:r:zygote:s0 line into /system/etc/init/hw/init.rc in the correct section.

Zygisk is now enabled and appears to be functioning without issues from Magisk's perspective, but in the emulator is not loading. Currently, I am testing this on the Mumu emulator running Android 12.

Yes! I have rebooted the system ofc.

Additionally, I can also note that after adding umount /system/bin/su in magisk.rc root getting broken after reboot.

Yeah with latest Kitsune is not necessarily add /system/etc/init/magisk.rc and add the line: umount /system/bin/su only seclabel u:r:zygote:s0 line into /system/etc/init/hw/init.rc And if you mean the LSPosed not load add the manager.apk and open

[Directox01]

Yeah. seclabel u:r:zygote:s0 did the job to help load the zygisk but for some reason it doesn't show up on android ^^

[VisionR1]

Yeah. seclabel u:r:zygote:s0 did the job to help load the zygisk but for some reason it doesn't show up on android ^^

if you mean the LSPosed not load add the manager.apk and open

[Directox01]

manager apk? can you provide a little info about it, please?

[VisionR1]

manager apk? can you provide a little info about it, please?

Open the LSPosed.zip and extract the manager.apk from inside

[Directox01]

Will try now. Thx!

[Directox01]

Works now! Tell me, please, does Hide my apps get detected for you? I've enabled the isolation feature but seems it doesn't help tho.

[Directox01]

Also, do you use safetynet fix with the current version?

[VisionR1]

Works now! Tell me, please, does Hide my apps get detected for you? I've enabled the isolation feature but seems it doesn't help tho.

Not yet, because and me today do it all this, tomorrow i try it and i tell you

[VisionR1]

Also, do you use safetynet fix with the current version?

I have flash it one, but i think is useless in emulator

[Directox01]

Tell me, please, is it possible to get in touch with you via telegram?

I may need some custom modifications, for which I'm ready to pay well.

[VisionR1]

Tell me, please, is it possible to get in touch with you via telegram?

I may need some custom modifications, for which I'm ready to pay well.

Not take money, I'm not specific, just the most info i read from different websites and after do the necessary modification if need it. About Safetynet read this: https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/ https://github.com/chiteroman/PlayIntegrityFix

[Directox01]

Interesting fact. I've just removed android faker and hide my apps, and all detection checks are passed. But still, there is some apps that detect the emulator :))

Note: Currently using only magisk hide apps by default.

[Directox01]

hehe

[VisionR1]

Interesting fact. I've just removed android faker and hide my apps, and all detection checks are passed. But still, there is some apps that detect the emulator :))

Note: Currently using only magisk hide apps by default.

Yeah this you say there is some apps that detect the emulator, is old problem for all us

[Directox01]

You think we can't bypass the detections? I don't know if you aware but genymotion without anything can bypass 99% of anti-emulator detections.

[VisionR1]

You think we can't bypass the detections? I don't know if you aware but genymotion without anything can bypass 99% of anti-emulator detections.

Yeah different emulator like genymotion and android studio, but emulator like Nox, BlueStacks MuMu etc. is different with another functions

[Directox01]

Hello! Any update planned for today?

[HuskyDG]

Test this and send logcat app-debug.apk.zip

logcat_2023-11-27-first-boot.txt logcat_2023-11-27-second-boot.txt

The first log is after I flashed the new boot image patched.

Magisk showed it needed additional setup. Thus, I pressed YES, and the device rebooted and, therefore, the second log.

Test zygisk

[sn-o-w]

Test this and send logcat app-debug.apk.zip

logcat_2023-11-27-first-boot.txt logcat_2023-11-27-second-boot.txt The first log is after I flashed the new boot image patched. Magisk showed it needed additional setup. Thus, I pressed YES, and the device rebooted and, therefore, the second log.

Test zygisk

Hmmm, Zygisk now seems to work. I enabled LSPosed (Zygisk), rebooted the device, and LSPosed Manager showed that LSPosed is enabled.

But Riru + LSPosed (Riru) seems not to work, tho. I used a very long time Riru + LSPosed because Zygisk kinda screwed the performance of my device. 🤔

Log when I enabled Riru + LSPosed (Riru), but not working: logcat_2023-11-28.txt

[HuskyDG]

Riru is dead and not updated for long

[sn-o-w]

Riru is dead and not updated for long

But the Riru version I used was created by you, and it worked perfectly with an older Magisk Delta version - fdac22ba.

[sn-o-w]

I just updated to latest Magisk Delta version, looks like the changes related to this issue are not pushed yet. 🤔

[sn-o-w]

@HuskyDG Have you pushed the changes to the new released build? Not sure if I can switch back to normal build (not debug). 🤔

[sn-o-w]

@HuskyDG Hmm, I believe there is another problem with Magisk Delta and/or Zygisk. 🤔

Have a look at this LSPosed log: LSPosed_2023-12-08T05_10_01.964.zip

I have an Xposed module that interacts with Snapchat, that module is called SnapEnhance. Once a day the module resets, I don't know why. I saw in logs spammed many times "Operation not supported on transport endpoint".

Before November I used an older version of Magisk Delta + Riru + LSPosed (Riru) and I never experienced SnapEnhance self-resetting. I was forced to stay with that Magisk Delta version for many months. LSPosed code didn't change very much lately, so my guess is that somehow Magisk Delta and/or Zygisk prevent(s) LSPosed to work properly. 🤔

[sn-o-w]

@HuskyDG I tried the new Magisk Delta build, it looks like changes related to Zygisk have not been pushed yet. 😞

[HuskyDG]

Is this an emulator or a real device? It seems zygote has been traced by other debugger? The problem is magisk ptracer can't attach to zygote (I/O error)

[sn-o-w]

Is this an emulator or a real device? The problem is magisk ptracer can't attach to zygote (I/O error)

It's a Nexus 5, so a real device.

[5thofjuly]

Hello, @HuskyDG . I also have this issue wherein zygisk cannot be enabled on my Pixel 6 Pro running on Android QPR2 Beta 2

[sn-o-w]

Is this an emulator or a real device? The problem is magisk ptracer can't attach to zygote (I/O error)

In case you are curious about the kernel my phone runs on, this is its source code: https://github.com/z3DD3r/android_kernel_lge_hammerhead/tree/lineage-17.1 [Notice the branch "lineage-17-1")

---

I want to share some information and findings.

I tried Magisk Alpha, and I swear to God, I have no idea what happens with this device...

Zygisk worked once. I mean, I was able to enable it once. Yesterday, I rebooted my device, and Zygisk stopped working; simply I can't make it stay enabled anymore.

I enabled Zygisk within Magisk and then rebooted the device. After rebooting, I saw "Zygisk: No" in Magisk Manager, and within Magisk settings, I still see a notice "Reboot to apply" at Zygisk, although I rebooted the device... This thing happened on Magisk Delta, too.

Another weird thing I experience with Magisk Alpha is that I reboot the device, and sometimes it won't get past the LineageOS animation; sometimes, the waiting time (between the old Google logo stage and seeing the lock screen inside Android) is double or even triple... But the device seems to boot much faster if Zygisk is disabled in Magisk.

I also tried to install the ZygiskNext module, and the module seems to be enabled. I also disabled the native Zygisk within Magisk settings, but there is no use. Somehow ZygiskNext appears not to be enabled, and LSPosed Zygisk is not working. The nice part about ZygiskNext is that will not make the device boot up slowly, but unfortunately, it doesn't work. I also tried Riru and the LSPosed Riru, but again, it was not working.

Is it something that has changed so dramatically in Magisk Alpha/Delta, even official Magisk, that can cause such problems and prevent older devices from working properly? I guess I will try with Magisk official builds. Perhaps I should stay on official builds. I have a feeling this weird behavior and issues are not caused by Magisk custom builds, maybe I'm wrong.

And yes, I am aware this repo doesn't provide support for Magisk Alpha, but I can't find where I can report the issues to Magisk Alpha, nor on GitHub or Telegram.

I just wanted to see if things are different with Magisk Alpha. And to share my findings, perhaps someone will consider them useful and can help to fix this/these issue(s). 🤔