Pixelify icon indicating copy to clipboard operation
Pixelify copied to clipboard

Corrupted boot image

Open UTZSTG opened this issue 1 year ago • 8 comments

Device:Pixel 6 pro Android version: 14 Magisk version name:27.0 Magisk version code:27007 27005 it is the pixelify zgisk module https://www.pling.com/p/1794976 that makes pre-release magisk version corrupt. if it is in use , device will corrupt and enter fastboot mode. Pixelify works well in 27000

UTZSTG avatar Sep 08 '24 04:09 UTZSTG

I unfortunately tried installing this module without checking this out :( How do i get out of fastboot mode?

jackforfaltu avatar Sep 12 '24 02:09 jackforfaltu

I unfortunately tried installing this module without checking this out :( How do i get out of fastboot mode?

Use fastboot.exe to flash patched boot.img in fastboot mode(i haven't tried original boot)

UTZSTG avatar Sep 12 '24 02:09 UTZSTG

that unforunately doesnt work (it just boots back into fastboot) i can however do a temp boot into using the stock boot.img but theres no way to uninstall the module because root access is lost and the Modules tab is grayed out in the Magisk app. any advice?

EDIT: i have already disabled the module using a temp boot into TWRP by renaming the folder. but that still does nothing

jackforfaltu avatar Sep 12 '24 07:09 jackforfaltu

that unforunately doesnt work (it just boots back into fastboot) i can however do a temp boot into using the stock boot.img but theres no way to uninstall the module because root access is lost and the Modules tab is grayed out in the Magisk app. any advice?

EDIT: i have already disabled the module using a temp boot into TWRP by renaming the folder. but that still does nothing

A patched boot.img works for me Maybe u can regain root and use a module that will disable all modules except itself? And if Pixelify is disabled, it will not ruin your boot.img

UTZSTG avatar Sep 12 '24 08:09 UTZSTG

I'm using lineage and I had to flash the latest OTA update package to remove Magisk properly and then I was able to reboot. I suspect you could then flash Magisk v27 and uninstall the module.

Cwavs avatar Dec 09 '24 09:12 Cwavs

i was running xiaomi hyper os 1.0.7.0, sunstone, magisk alpha v28. ran OTA to 1.0.8.0, patched again to kitsune mask v27. managed to get into system but google service crashing non stop, cant open google photos and app settings, all magisk modules removed because of OTA. reflashed fastboot rom as last resort

topnexion avatar Dec 21 '24 12:12 topnexion

that unforunately doesnt work (it just boots back into fastboot) i can however do a temp boot into using the stock boot.img but theres no way to uninstall the module because root access is lost and the Modules tab is grayed out in the Magisk app. any advice?

EDIT: i have already disabled the module using a temp boot into TWRP by renaming the folder. but that still does nothing

Not sure have you figured out. You have to reflash entire boot.img and reflash magisk. Not just delete Pixelify module folder. You don't even have to delete Pixelify folder to reboot. I'm not sure why or how this happening. It just do

PL7963 avatar Dec 22 '24 16:12 PL7963

This shit is demonic. Why is there not a version check when installing? I tried to fix the bootlooping on a Pixel 9 Pro XL with Android 15 by reflashing boot/init_boot from the factory image, then rooting with KernelSU just to remove the files under /data/adb/modules_update/Pixelify and /data/adb/modules/Pixelify, then uninstalling KernelSU through its app and then repatch and reinstall Magisk by flashing init_boot, but at some point the userspace fastboot got corrupted on my device and I had to fully wipe and reinstall. Even flash-all (without -w) didn't help. Maybe using magisk --remove-modules with KernelSU might have worked better but I don't care to find out.

alexwh avatar Dec 31 '24 02:12 alexwh