-
Notifications
You must be signed in to change notification settings - Fork 86
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
Comments
I unfortunately tried installing this module without checking this out :( |
Use fastboot.exe to flash patched boot.img in fastboot mode(i haven't tried original boot) |
that unforunately doesnt work (it just boots back into fastboot) 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 |
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. |
i was running xiaomi hyper os 1.0.7.0, sunstone, magisk alpha v28. |
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 |
This shit is demonic. Why is there not a version check when installing? |
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
The text was updated successfully, but these errors were encountered: