Open NightMean opened 5 months ago
What's changed in your 3.1 build? Working on later android 14 QPR builds or?
What's changed in your 3.1 build? Working on later android 14 QPR builds or?
I have only tried 3.0 release build. I have not built 3.1 from the source so I can't confirm if it works.
Same issue I faced weeks ago.
For everyone experiencing this, just boot your phone into safe mode so that the modules will be disabled when rebooted again.
As my phone was stuck in a boot loop with Kitsune Mask 26.4, I couldn't get into safe mode so I had to use
adb wait-for-device shell magisk --remove-modules
Unfortunately that removed all the modules that I had but it did get my phone back to bootable state.
Feature Description: Pixelify currently does not support SuList that is used in Kitsune Mask (Magisk fork). With latest stable of Kitsune Mask (26.4) and enabled SuList, the whole system locks up on boot and nothing can be done. With Canary release R65C33E4F, the phone boots up but right after boot, every application starts crashing and nothing can be opened.
I'm currently using Kitsune Mask instead of Magisk only because the root is not detected in Office 365 apps. With latest Magisk (27.0), root is detected even with Shamiko, blacklist, etc. Kitsune SuList is currently the only known solution for work apps.
Device information: Phone: Nothing Phone (1) - Stock NOOS 2.5.5 (Android 14) Root: Kitsune Mask Canary (R65C33E4F)
Module list: Call Recorder - SKVALEX
2.3.0
Fullscreen/Immersive Gestures (Q-U)26.1
Pixelify3.0
PlayIntegrityFix15.9.8
Zygisk - LSposed1.9.2
Zygisk-detach1.15.0