Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Corrupted boot image #341

Open
UTZSTG opened this issue Sep 8, 2024 · 8 comments
Open

Corrupted boot image #341

UTZSTG opened this issue Sep 8, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@UTZSTG
Copy link

UTZSTG commented Sep 8, 2024

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 UTZSTG added the bug Something isn't working label Sep 8, 2024
@jackforfaltu
Copy link

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

@UTZSTG
Copy link
Author

UTZSTG commented Sep 12, 2024

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)

@jackforfaltu
Copy link

jackforfaltu commented Sep 12, 2024

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

@UTZSTG
Copy link
Author

UTZSTG commented Sep 12, 2024

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

@Cwavs
Copy link

Cwavs commented Dec 9, 2024

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.

@topnexion
Copy link

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

@PL7963
Copy link

PL7963 commented Dec 22, 2024

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

@alexwh
Copy link

alexwh commented Dec 31, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants