Database Develop

Error while installing Magisk through Magisk manager

I'm trying to instal Magisk 19.3 through Magisk Manager Version: v7.3.4
and getting this error:
Device platform: arm64-v8a
Coping image to cache
unpacking boot image
!unsupported/unknown image format
!installation failed
Any ideas how to solve it?
I have used Stable Magisk Version: v19.3 (also tried Beta Magisk Version: v19.4)

Maybe something's wrong with the boot image? Try to re-download magisk stable zip and reintall it via TWRP.

@LogicalMaverick, tried to download it again from this thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 but still the same error message
I did try to install in TWRP mode and also from the Magisk Manager and still not working.
When I install in TWRP mode the result is the phone is getting into loop mode and the only way out if it is to uninstall it

try to wipe data after flashing magisk before booting to system

Kzak25 said:
try to wipe data after flashing magisk before booting to system
Click to expand...
Click to collapse
Yeah, for me there are 2 ways:
1. Wipe data after flashing magisk before booting system
2. Complete phone setup first after installing new ROM, and then boot into recovery, then you're good to install magisk

Kzak25 said:
try to wipe data after flashing magisk before booting to system
Click to expand...
Click to collapse
Didn't work. Still getting to the same issue where the phone is stuck in bootloop and the only way out of it is to uninstall Magisk

What phone are you using?

cohenelad said:
Didn't work. Still getting to the same issue where the phone is stuck in bootloop and the only way out of it is to uninstall Magisk
Click to expand...
Click to collapse
are you on stock or custom ROM (if stock what MIUI Ver)

Kzak25 said:
are you on stock or custom ROM (if stock what MIUI Ver)
Click to expand...
Click to collapse
I'm on stock ROM.
Was on MIUI 10.3.2 Now I'm on 10.4.8.
Tried to install Magisk on bot ROM through TWRP and didn't work.
Tried also through Magisk manager and didn't work
When I installed TWRP on my phone it asked if I want to give it permission to modify the system or to leave it read only mode.
I choose read only mode as I thought it will be easier to get OTA updates.
Maybe that's the reason Magisk cannot be installed correctly ?
TIA for your help

cohenelad said:
I'm on stock ROM.
Was on MIUI 10.3.2 Now I'm on 10.4.8.
Tried to install Magisk on bot ROM through TWRP and didn't work.
Tried also through Magisk manager and didn't work
When I installed TWRP on my phone it asked if I want to give it permission to modify the system or to leave it read only mode.
I choose read only mode as I thought it will be easier to get OTA updates.
Maybe that's the reason Magisk cannot be installed correctly ?
TIA for your help
Click to expand...
Click to collapse
Yeah i think you should give TWRP all permission when you boot into it the first time
you can re-flash TWRP and try again

reboots to fastboot
Kzak25 said:
Yeah i think you should give TWRP all permission when you boot into it the first time
you can re-flash TWRP and try again
Click to expand...
Click to collapse
I can flash over twrp. then it says no rom installed so flash over magisk-error unknown image. this is a fresh download tried 3 new downloads same error. use adb sideload to flash rom. successful do the reboot and it reboots to fastboot. what do i do

Not able to root

Hello, guys. I have an issue with magisk 19.3.
I flashed MIUI 10 Global version in my Mi 9. After that, I flash TWRP then reboot to TWRP install magisk 19.3 and reboot system, but not able to get in the system instead boot to recovery. Does anybody know why?

Any Magisk modules installed? In this case delete them first.
Cheers
Toscha

toscha42 said:
Any Magisk modules installed? In this case delete them first.
Cheers
Toscha
Click to expand...
Click to collapse
No. I didn't installed anything. I just flash MIUI 10 and flash in TWRP, then flash Magisk from TWRP.

Flash ROM, boot system to setup, then flash magisk.

badaas said:
Flash ROM, boot system to setup, then flash magisk.
Click to expand...
Click to collapse
I did the samething as you said, but it keep rebooting after I installed the Magisk. (Keep rebooting on the screen shows Xiaomi logo and unlock)

Try Canary magisk

badaas said:
Try Canary magisk
Click to expand...
Click to collapse
Yeah, I'm using Canary, but still same issue not able to boot the system.

Edexposed bootloop on a Pixel 4, how to flash zip?

Hi. I have recently rooted my new pixel 4 with magisk and was installing Riru Edexposed to try and get fingerface working. Unfortunately during installing edexposed my phone got stuck in a bootloop. Because the pixel 4 doesn't have a custom recovery I don't know how to flash the exposed uninstaller zip or even to just access my files. Any help would be much appreciated. Thank you.

Have a look in the apps/themes section.
tulsadiver offers a boot image which removes all magisk modules....

pa.pn2 said:
Have a look in the apps/themes section.
tulsadiver offers a boot image which removes all magisk modules....
Click to expand...
Click to collapse
Is there really no Custom recovery or TWRP for Pixel 4's even tho Root works & ontop of that how're you supposed to flash disable dm-verity if you don't have a flashing ROM installed?

Nightshadex543 said:
Is there really no Custom recovery or TWRP for Pixel 4's even tho Root works & ontop of that how're you supposed to flash disable dm-verity if you don't have a flashing ROM installed?
Click to expand...
Click to collapse
No, no custom recovery yet. I thought it was gonna be a pain but I was able to flash DirtyUnicorns ROM without any issues.

Prey521 said:
No, no custom recovery yet. I thought it was gonna be a pain but I was able to flash DirtyUnicorns ROM without any issues.
Click to expand...
Click to collapse
Goddamnit thanks. TWRP 3.3.1 or Blu-spark don't work? So, that means computer based flashes. That's unfortunate, I'd rather have something installed incase of a Bootloop after attempting root. Makes things less problematic.
Thanks again.

Nightshadex543 said:
Goddamnit thanks. TWRP 3.3.1 or Blu-spark don't work? So, that means computer based flashes. That's unfortunate, I'd rather have something installed incase of a Bootloop after attempting root. Makes things less problematic.
Thanks again.
Click to expand...
Click to collapse
Nope, just fastboot and adb commands for now.

Looks like magisk will add a "module disabler mode" in the next updates when the phone will be rebooted in safe mode.
For now the only thing to do is to flash the custom boot image from tulsadiver that enable core mode only.
I heard about another alternative, from didgeridoohan magisk wiki, but never tried if it works in this case:
Since Magisk v19.4, there's an adb command that can be used to uninstall all modules on your device.
If the device is bootlooping or simply haning on the boot animation you have a good chance that you can use this command to get up and running again.
Hook your device up to a computer (or other device you can run adb from) and execute the following command:
adb wait-for-device shell magisk --remove-modules
After that you can start your device and as soon as adb is available the command will activate, the modules will be removed and the device will reboot. There's of course a chance that the troublesome module has done something that the command can't remove...
Click to expand...
Click to collapse

Just checked out both of those contributors. Good stuff, appreciated.

Help! Need to Uninstall Magisk Modules. Stuck in a Bootloop When Magisk is Activated.

I've flashed the new Lineage 18 on my Samsung Galaxy S10E Exynos and had trouble installing Magisk. I managed to get it installed somehow and tried adding a bunch of Magisk modules, some of which failed.
After rebooting, it booted up and stayed alive for a while before cutting to the bootanim and getting stuck in a loop. Disabling Magisk by flashing the old recovery.img solved it for me, but everytime I try to get Magisk to work again, it gets stuck in a loop after booting up the first time.
Help! Will uninstalling all the modules solve this issue and if it will, how do I go about doing it.
Any/all solutions much appreciated.
Thanks!

To delete a magisk module causing bootloop. Boot to TWRP, then go to advanced/file manager/data/adb/modules. U will see all magisk modules there. Delete the one that you think is causing the bootloop.
This is for my s10, I'm not sure if it's the exactly the same for s10e.

XTrail02 said:
To delete a magisk module causing bootloop. Boot to TWRP, then go to advanced/file manager/data/adb/modules. U will see all magisk modules there. Delete the one that you think is causing the bootloop.
This is for my s10, I'm not sure if it's the exactly the same for s10e.
Click to expand...
Click to collapse
Worked like a charm! Thank you

XTrail02 said:
To delete a magisk module causing bootloop. Boot to TWRP, then go to advanced/file manager/data/adb/modules. U will see all magisk modules there. Delete the one that you think is causing the bootloop.
This is for my s10, I'm not sure if it's the exactly the same for s10e.
Click to expand...
Click to collapse
is it possible somehow to do this with the stock recovery. I can boot with out magisk just fine, but if i enabled it stuck at booting forever. I like to avoid reflashing / Factory resetting.

playfsx said:
is it possible somehow to do this with the stock recovery. I can boot with out magisk just fine, but if i enabled it stuck at booting forever. I like to avoid reflashing / Factory resetting.
Click to expand...
Click to collapse
figure it out.
turn off the phone
open a shell and type: adb wait-for-device shell magisk --remove-modules
boot with magisk enabled.
your phone should reboot and in the next boot you should have a clean magisk with out modules.

playfsx said:
figure it out.
turn off the phone
open a shell and type: adb wait-for-device shell magisk --remove-modules
boot with magisk enabled.
your phone should reboot and in the next boot you should have a clean magisk with out modules.
Click to expand...
Click to collapse
You just saved me an evening reflashing and setting up all **** again.

Question Magisk 24.3 Bootloop

Anyone else the latest Magisk update causes Bootloop when installing modules?

use 24.1, is perfect

OK THANKS, I HOPE FUTURE UPDATES WILL WORK CORRECTLY ON THE DEVICE

a question: do u have repatched boot.img with new magisk version? you must do it

wetito said:
use 24.1, is perfect
Click to expand...
Click to collapse
I'm still using v23 .. just to be sure lol ! but now i know 24.1 is good thank you!

PonchoNz said:
Anyone else the latest Magisk update causes Bootloop when installing modules?
Click to expand...
Click to collapse
Use Magisk 24.3 and patch the boot file -> Flash the boot file in fastbootd
Done.

i have flashed 24.1 using fastboot. for 24.3 fastbiitd is necessary? i ask just i case in the future i will decide update to latest version

wetito said:
a question: do u have repatched boot.img with new magisk version? you must do it
Click to expand...
Click to collapse
Yep but update it by TWRP

nguadien said:
Use Magisk 24.3 and patch the boot file -> Flash the boot file in fastbootd
Click to expand...
Click to collapse
Done I did it too but when I install a Module called NFS Injector or Magnetar when I restart the device it gives bootloop

PonchoNz said:
Done I did it too but when I install a Module called NFS Injector or Magnetar when I restart the device it gives bootloop
Click to expand...
Click to collapse
Then the problem is the modules you installed, not "latest Magisk update" like you stated.
Not all modules work for all devices, each device reacts to modules very differently, so boot loop caused by modules should not be mistaken for the whole Magisk.