(EVERYONE!) Pixelfy 3.0 is not compatible with Magisk newer than 27! (OG Title) Magisk 28.1 and oos 12 not compatible with 3.0

[Bradford1040]

Device name: OnePlus 7t pro NR (HD1925)
Rom name: oxygen os
Android version: 12
Pixelify version: 3.0

Bug Description:
I updated magisk 27000 to 28.1and was stuck at fastboot, was able to get into OOS 12 recovery but had lost all my backup files so fixing that ROM was a lost cause! I used MSM unbrick back to OOS 11, and updated back to OOS 12, installed magisk 28.1 booted & flashed fine, after pixelfy install and reboot stuck at fastboot again so booted stock boot.img and it started, uninstalled 28.1 and installed 27.0 (27000) patched boot.img reboot to bootloader first booted patched image booted fine and showed rooted and pixelfy installed,so went back to bootloader and flashed, no issues

EDIT and FIX!

Two of the biggest killers in this I have found to be the boot animation & launcher if you avoid installing those two things you should be much better off!

1. If you installed with anything over Magisk 27.0 (stable) you are most likely at fastboot wondering what you did wrong! . It is ok, unless you are on Android 15 which is 100% not supported, even very few Android 14's work

2. You have the copy of your stock boot.img, at fastboot with device connected to PC, Type fastboot boot boot.img (which should still be in your platform-tools folder) do not flash it! Your device should boot normally and you will not be rooted, but you will be able to uninstall Magisk 27001~28.2 (at the time of this post it is the newest magisk). After you have uninstalled, Click on the Magisk 27.0 apk and install, after it is, patch your boot.img, with device connected to PC still open terminal adb pull /sdcard/Download/magisk_patched-27000_UfmXx.img (name of your patched img might be different) check to see it pulled the patched image and it is located in your platform-tools folder

3. In the terminal on the PC, type adb reboot bootloader which should bring you back to fastboot, now type fastboot boot magisk_patched-27000_UfmXx.img just to double check everything is ok, If it boots up and you are rooted then we have to make it permanent (I am one that likes to double check everything before I flash anything) so once again in terminal adb reboot bootloader and at fastboot we type fastboot flash --slot=all boot magisk_patched-27000_UfmXx.img some devices you will have to manually select power off and after it shuts off then hold power button and turn device on after a flash

[CallMeShepard]

Same bootloop issue.
For some reason couldn't get a log file from TWRP during bootloop. (I hope I'll retrieve it somehow in future)
Tried with Magisk 28.1 and Magisk 27008, but it leads to bootloop after flashing Pixelify in Magisk.
(Was enabling only Google Photo unlimited storage and Google Photo backup options)
But with Magisk 27000, as mentioned, everything works fine.

Device name: Samsung Galaxy M21 (M215F)
Rom name: OneUI 4.1
ARM64 device
Android ver.: 12
Pixelify ver.: 3.0

P.S. I managed to exit bootloop without data loss, but with TWRP and Magisk uninstalled after flashing a .tar archive with one stock boot.img.lz4 file inside it. Flashing in AP slot via Odin3 v3.14

[Bradford1040]

You should be able to patch your stock boot.Img with magisk 27000, of course try booting it before you boot flash it, I am a big double check guy, my biggest issue with me device/phone it is a special device with T-Mobile branding so finding a good custom ROM is difficult, and there really is no way to TWRP mount & back the device up, I can only boot TWRP not flash to both recovery slots, I mean I can but it's basically useless for what TWRP main reason is!

[CallMeShepard]

Yeah, thanks for the recommendation, I thought about it, but the point is that TWRP for some reason couldn't get into internal storage and root (like /data/adb/ where you can remove broken Magisk modules that cause bootloop). And to make backups in general, apparently. I tried entering the command twrp decrypt <mypassword> but it notified me that there is no crypto support in this build, which is very annoying (this TWRP is from the official site, specifically for M21). I decided to try to rebuild my TWRP with support for this feature, but the result was a bootloop, but because of the recovery.

I could of course forget about it, but the funny thing is that in order to install TWRP I have to erase the data (and system won't replace TWRP with stock recovery), which makes me stumped. I wanted to backup boot with patched Magisk and also TWRP at the same time, but again the problem is that TWRP doesn't get root access, although it should. That's sucks.

The best I've been able to do so far is to revert to stock boot, as I said before, and exit bootloop with loss of TWRP and Root, but without loss of personal data. I would like TWRP to be fully functional with Magisk and perform its tasks (backup in particular) and retrieve log file to help Pixelify developers to fix that strange bootloop issue

[Bradford1040]

well I always was under impression that Samsung had to use odin to do everything? I left samsung devices as I hated odin and bricked a few phones (many years ago) I have been using OnePlus phones for a long time now, this one I use is a bit of a pain (did not know going in) but found out most ways around the short falls, and its still a beast! Even though it's a 2019 flagship phone. still handles it all today with no issue! SD 855+, 12gb ram, 256 storage, 1440p 90hz screen, so todays phones are not much better, My daughter has an S21+ and its only got that 100x zoom that destroys my idea that I have a good phone LMAO! But other than that we are equal

[sanaullah22444]

"- Device platform: arm64-v8a

• Installing: 28.1 (28100)
  Processing zip file ! Installation failed"
  I'm facing this problem in Google Pixel 3Xl device
  Android version 12

[Bradford1040]

I would just uninstall 28.1 and install 27.0 patch the boot.img and flash the 27 patched image

You should be able to do what I did. Just boot with un-patched boot.img

[sanaullah22444]

Kindly guide me how can i install Magisk on pixel 3xl device

…

On Fri, Feb 21, 2025, 1:23 AM Bradford1040 (aka-Hammer) < ***@***.***> wrote: I would just uninstall 28.1 and install 27.0 patch the boot.img and flash the 27 patched image — Reply to this email directly, view it on GitHub <#361 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BPWE2KV7DKD3S2FOMOXKMKT2QY2T5AVCNFSM6AAAAABXFE7AOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZSGU4TSMZXGU> . You are receiving this because you commented.Message ID: ***@***.***> [image: Bradford1040]*Bradford1040* left a comment (Kingsman44/Pixelify#361) <#361 (comment)> I would just uninstall 28.1 and install 27.0 patch the boot.img and flash the 27 patched image — Reply to this email directly, view it on GitHub <#361 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BPWE2KV7DKD3S2FOMOXKMKT2QY2T5AVCNFSM6AAAAABXFE7AOCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNZSGU4TSMZXGU> . You are receiving this because you commented.Message ID: ***@***.***>

[Bradford1040]

Kindly guide me how can i install Magisk on pixel 3xl device
…

I would say look on XDA or ask someone in a Telegram or discord group, I am not a Pixel Owner so not 100% sure of how pixel's work to do that, I am only used to what devices I have

[AnAnonymousPotato]

Happened to me as well. Android 13 with Magisk 28.2. I had to flash stock boot.img, then uninstall magisk app, then installed v27.0, then patched stock boot.img using it.

Maybe the reason why the module doesn't work (ChatGPT said this):

1. Magisk 27.1+ removed support for legacy sepolicy.rule files – many modules, including Pixelify, depend on this for modifying SELinux policies.
2. Magisk 28.0+ fully switched to seccomp filtering, which blocks older modification methods.

[Bradford1040]

Happened to me as well. Android 13 with Magisk 28.2. I had to flash stock boot.img, then uninstall magisk app, then installed v27.0, then patched stock boot.img using it.

Maybe the reason why the module doesn't work (ChatGPT said this):

1. Magisk 27.1+ removed support for legacy sepolicy.rule files – many modules, including Pixelify, depend on this for modifying SELinux policies.
2. Magisk 28.0+ fully switched to seccomp filtering, which blocks older modification methods.

I see that Johnwu changed a bunch in magisk itself, like moved to JDK 21 from 17, and think Python3, and of course what you mentioned! (Or should say ChatGPT) lol I am still on the lower end of the learning curve, got a late start on doing this stuff, I am trying to make a PixelOS ROM for my older device based on AOSPA or AOSP 15 I am just getting started on it in my free time though

[ItzLevvie]

Pixelfy 3.0 is not compatible with Magisk newer than 27!

It is compatible.

I have no issues installing Pixelify 3.0 on Android 16 with Magisk Canary but I am on a Google Pixel device so the situation will be different for other OEM devices.

It also works on AVD using the latest GSI.

[Mia-Rain]

Unable to get the launcher and boot animations working on Lineage OS 22.2, recovering is possible however as the launcher never actually installs and the boot animation just does nothing

everything else including the submodules seem to be work

our device is a Pixel 4a (not 5g, sunfish)
notably it was working perfectly on android 13 via grapheneos previously