Bootloop on LineageOS 23.2 / Android 16 with Pixelify Next Beta v5.8.2; Magisk modules disabled after recovery boot

[lgbtaye777]

Device: OnePlus 9 Pro / LE2123 / lemonadep
ROM: LineageOS 23.2, Android 16
Root: Magisk 30.7
Zygisk: ZygiskNext
Other installed modules before Pixelify:

• ZygiskNext
• Play Integrity Fork
• TrickyStore
• TrickyAddon
  Pixelify version: Pixelify Next Beta v5.8.2

What happened:
I installed Pixelify Next Beta v5.8.2 through Magisk and enabled the options during installation. After rebooting, the device entered a bootloop: it showed the OnePlus logo, then the LineageOS boot animation, then rebooted back to the OnePlus logo. This happened several times.

After a few failed boots, the device eventually booted into Android, but none of the Pixelify changes were applied. The launcher stayed the same. When I opened Magisk, all modules were disabled. Pixelify Next and Play Integrity Fork showed a red warning saying that the module was disabled because Zygisk was not enabled.

It looks like Pixelify caused a bootloop, then Magisk booted in safe mode and disabled all modules, including ZygiskNext.

Is Pixelify Next Beta v5.8.2 compatible with ZygiskNext?

This issue seems more likely related to the Zygisk implementation rather than the device itself. My setup uses ZygiskNext as a Magisk module, not Magisk’s built-in Zygisk. After installing Pixelify, the device bootlooped several times, then Magisk Safe Mode was triggered and all modules were disabled. As a result, ZygiskNext became inactive, and Pixelify / Play Integrity Fork both showed warnings that Zygisk was not enabled.
Are there any known conflicts between Pixelify Next and ZygiskNext?
Does Pixelify require Magisk’s built-in Zygisk specifically, or should it also work with ZygiskNext?
Are there any Pixelify installation options that should be disabled when using ZygiskNext + Play Integrity Fork + TrickyStore + TrickyAddon?

[BasGame1]

@lgbtaye777 Hi, no, there isn't any compatibility issue with Zygisk Next, but pixelify have had similar problems with all the Zygisk version in the past, so it's probably an error of pixelify

[lgbtaye777]

Hi, no, there isn't any compatibility issue with Zygisk Next, but pixelify have had similar problems with all the Zygisk version in the past, so it's probably an error of pixelify

Thank you very much for the quick reply 🙏, I really appreciate it ❤️
Do you think there is anything I could try on my side to make Pixelify boot properly, or is this likely something that needs to be fixed in the module itself?
I’d be happy to test a different setup or provide more logs if that would help.

[BasGame1]

Hi, no, there isn't any compatibility issue with Zygisk Next, but pixelify have had similar problems with all the Zygisk version in the past, so it's probably an error of pixelify

Thank you very much for the quick reply 🙏, I really appreciate it ❤️ Do you think there is anything I could try on my side to make Pixelify boot properly, or is this likely something that needs to be fixed in the module itself? I’d be happy to test a different setup or provide more logs if that would help.

Hi, no, it's a core pixelify bug, it can help getting new logs, but the real problem is with the Zygisk source code, so if you know how to code in c++ it would be awesome! bc with exams I don't have much time, so at any time soon I won't be able to update it, and btw, any contribution, like this comment, it's amazing, so thanks a lot!

[Soggy-Pancake]

I also bootlooped after installing beta 5.8.2.

How do I get the logs for modules?

Device: Sony xperia 10 VII (XQ-FE72)
Lineage OS: 23.2-20260517-NIGHTLY-pdx257
Android 16

Modules:

• aa4mg 0.6.4
• Pixelify Next
• Shamiko 1.2.5
• Systemless hosts (magisk built-in one)
• Vector/LSposed (2.0 / 3021)

[BasGame1]

@Soggy-Pancake Hi, try to use V6. 1

[Soggy-Pancake]

I'm not sure why it initially only showed 5.8 for me. Doesn't bootloop now though.

[BasGame1]

oh, then fixed?

[Soggy-Pancake]

Potential user error but I'm unsure. I've attempted several times to uninstall and reinstall to update to 6.1but the logs written keep reporting 5.8.2. The uninstaller module showed up and I left it enabled to hopefully let me fully reinstall 6.1 but it still shows 5.8.2 and then bootloops afterwards.

[Soggy-Pancake]

Another reinstall after letting uninstaller run and clearing old log files just in case they weren't being overwritten.

magisk_install_log_2026-06-05T08.35.54.log

flaglogs.txt

logs.txt

[BasGame1]

Nah, prob it's a system error and not a user error, and I have another report of the version mismatch