Pixelify causes bootloop when used with Magisk versions >27.0 and Android 15

[kwala007]

Device name: OnePlus 5t
Rom name: LineageOS 22.1
Android version: 15
Pixelify version: 3.0

Pixelify causes a bootloop when used with Magisk versions >27.0. I had a working Pixelify installation with Magisk 27.0, and upon updating to Magisk 28.1 and rebooting, my phone entered a bootloop. I also tried Magisk 27002, which also resulted in a bootloop. Upon uninstalling Magisk with TWRP and reinstalling version 27.0, I was able to reinstall Pixelify without a bootloop.

Steps to reproduce:
Install Pixelify module with a Magisk app version >27.0 and reboot OR have a working Pixelify installation and update the Magisk app to a version >27.0 and reboot.

Unfortunately, I submitted this bug report a while after fixing my phone, so I don't have the boot logs.

[0944-tw]

Looks like its not because of >27.0 Because Magisk >27.0 Works Fine On My Android 14 Device.
Maybe its because android 15?

[kwala007]

It looks like you're correct. I just updated Magisk to 28.1 on a Oneplus 6t with LineageOS 21.0 (Android 14) and Pixelify 3.0, and everything works as before. The issue seems to occur only when using Android 15 and Magisk >27.0 together.

[owlery7]

Can confirm on a fresh install of LOS 22.1 and magisk 28.1, it bootloops upon flash, and removing the module in /data/adb does not resolve it.
I only manage to get the device to boot by wiping data.
MAybe someone more clever than me has a solution.

[kwala007]

I was able to fix it without having to wipe my data. This is the solution I came up with:

• Obtain device's stock boot image
• Boot into stock boot image without flashing with "fastboot boot <image_name>.img"
• Download the apk of your installed Magisk version and rename it to "uninstall.zip"
• Reboot to bootloader with "adb reboot bootloader"
• Download a TWRP recovery image for your phone to your computer. Boot into TWRP without flashing it with "fastboot boot <TWRP_img_name>.img". If you already have TWRP on your phone, just boot into it normally. You can also use any other custom recovery that decrypts the phone storage and allows the installation of zip files. Lineage recovery does not do this - I wasn't even able to access data/adb with lineage recovery.
• Once in TWRP/your custom recovery, go to the install section and install "uninstall.zip" from storage. This will remove root, Magisk, and all modules. You have to do it this way because you can't access Magisk's normal uninstall or remove modules features with the boot loop, and Pixelify can't be easily removed through ADB like other modules.
• Reboot into your now working phone with all data minus root and Magisk modules. Download Magisk 27.0 apk and install it. Then, use it to patch your stock boot image.
• Reboot to bootloader and do "fastboot flash boot <patched_img_name>.img" to regain root. Now you have working root and just need to reinstall your modules.
• Reinstall whatever modules you'd like.

[Xenon177]

I have Lineage 22.1 and magisk 28, and the only problem with pxelify is that it doesn't work, says that I need to enable in LSposed, even though it is.

Anyway, if you turn your phone on with volume down, I think magisk disables all modules. This could possibly fix the bootlooping. Take this with a pinch of salt cos I'm new to this.

[kwala007]

This github is for the Pixelify magisk module, not the lsposed module. The lsposed module hasn't been updated since 2022.

[QueenieeQ]

I had the same problem when using Magisk 28. I have LineageOS 20 with Magisk 27.0 and Pixelify 3.0 worked perfectly. However, after updating the Magisk from 27.0 to 28.1 and rebooting, i experienced a bootloop. I tried a fresh install of LineageOS with Magisk 28 without Pixelify, and it booted normally. But after a successful boot, if I installed Pixelify in Magisk, it caused a bootloop the next time.

[christmaswreath]

Same issue, fastboot is also fucked up which means I'm gonna have to send it in for repair.

[zun43d]

On a side note, when device bootloops, clearing cache partition from recovery always worked for me. It allows the system to boot and after that simply remove the module.