Magisk General Support / Discussion

[Riyad_]

After installing or removing a module in magisk 22.1 when click the reboot option there is a message that show formatting data instead of rebooting. and also after that the system boot itself into recovery. i can't say its a boot loop because if reboot the device by using power key it works . Also after booted into recovery ,reboot to system also works fine. anyione facing this issue ???

 

[Didgeridoohan]

i been traumatized with 22.0 so can i just directly install the update without extra preparation and not expecting any issue or bootloop?

You should always expect and prepare for issues and bootloops, but the most of the problems we saw with the v22.0 update should have been fixed in v22.1. This entry from the changelog is my best bet on what was causing the broken boot images we saw in the last release:

• [App] Prevent multiple installation sessions running in parallel

I say go for it (as long as you have all your important data backed up, of course).

 

[jhedfors]

This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
All information, including troubleshoot guides and notes, are in the Announcement Thread

Is there a replacement for the announcement thread? It hasn't been updated for a long time and I cannot find any reference to it being discontinued.

 

[Didgeridoohan]

Is there a replacement for the announcement thread? It hasn't been updated for a long time and I cannot find any reference to it being discontinued.

From the announcement thread:

For all up-to-date info and links, please directly check Magisk's GitHub Page.

 

[ashrr]

I got a notification to update to 22.1 today, pressed it and nothing happened. Tried to open the manager app and it wouldn't open so I waited 5 minutes then rebooted to see if it would fix it but bootlooped instead. I was on the latest version before updating which I think was 22.0. I've just tried flashing 22.1 again in recovery but I'm still bootlooping. Any ideas how I can fix this?

 

[ineedroot69]

I got a notification to update to 22.1 today, pressed it and nothing happened. Tried to open the manager app and it wouldn't open so I waited 5 minutes then rebooted to see if it would fix it but bootlooped instead. I was on the latest version before updating which I think was 22.0. I've just tried flashing 22.1 again in recovery but I'm still bootlooping. Any ideas how I can fix this?

what do you mean by flashing? i thought only the app receive update(which is apk and can be directly installed like any other apk)

did you just decided to download the new magisk apk and flash it instead of installing the update directly from magisk app... ohh nooo

also perhaps youre wifi connection is slow (since it's downloading the update) should've have waited longer instead of rebooting your device

 

[ashrr]

what do you mean by flashing? i thought only the app receive update(which is apk and can be directly installed like any other apk)

did you just decided to download the new magisk apk and flash it instead of installing the update directly from magisk app... ohh nooo

also perhaps youre wifi connection is slow (since it's downloading the update) should've have waited longer instead of rebooting your device

Installation

The Magic Mask for Android

topjohnwu.github.io

Yh renamed the apk to zip and flashed that after the normal method failed.
I doubt it was due to a slow connection, I get about 200mb down from the room I was in. Yh I probably should've waited a bit longer but 5+ minutes is usually more than enough.

 

[ineedroot69]

Installation

The Magic Mask for Android

topjohnwu.github.io

Yh renamed the apk to zip and flashed that after the normal method failed.
I doubt it was due to a slow connection, I get about 200mb down from the room I was in. Yh I probably should've waited a bit longer but 5+ minutes is usually more than enough.

you have TWRP? just grab the partition Magisk backup and fastboot flash it

 

[ashrr]

you have TWRP? just grab the partition Magisk backup and fastboot flash it

Yh I do. Where can I find magisk backup partition? I used to flash custom roms and kernels back when I had my Nexus 4 but these days it's just stock with magisk so I'm pretty much new to this whole thing.

 

[kevk60]

Have updated to Magisk 22.0 on oneplus 6t and 8t and had no problems. Updated to Magisk 22.1 on both and have had no problems.

 

[aryanhington]

what are you doing? why you manually changing them?

anyway here's what they does from the god himself John Wu

preserve avb 2.0/dm-verity
View attachment 5274989

Preserve force encryptionView attachment 5274991​

anyone know if verity can be disabled by editing /sbin/.magisk/config as can't see the option of verity within magisk manager app?

 

[JimSmith94]

I'm not 100% sure what bricked my Pixel 5 but after installing the April Security update and patching boot.img, it was stuck on the fastboot screen with no boot image on slot b. I believe it happened because I patched boot. img without checking and installing the new Magisk Manager first. UbreakIFix was unable to force flash so now I'm waiting for them to get in a new motherboard. As I said, I'm not positive this caused it, but perhaps this warning will keep someone else from doing something stupid like I did.

I won't get my phone back until sometime next week. Before I build up the courage to root it again, can someone confirm that my patching the boot image after installing the April Security update but without checking for a Magisk Manager update first was what bricked my Pixel 5?

 

[ashrr]

Yh I do. Where can I find magisk backup partition? I used to flash custom roms and kernels back when I had my Nexus 4 but these days it's just stock with magisk so I'm pretty much new to this whole thing.

Ok I'm getting nowhere. I got the backup boot.img which I extracted from /data/magisk_backup_sha1/boot.img.gz and flashed it using the command fastboot flash boot boot.img and my OP 5T just shows a white led and ends up in some diagnostic mode. I've also tried flashing the stock boot.img then flashing magisk but that didn't work either. Does anyone want to help me with some instructions a 5 year old could follow?
I have a twrp backup from a while ago which is for the same android version but an older magisk version and I also have one with the broken boot after the failed update from 22.0 and before attempting to flash 22.1 again in twrp.

Edit: I've gotten back into android by restoring my system backup from late 2019. I then uninstalled the broken magisk app installed 22.1 again and all is working fine. I've tried restoring the broken system image but it bootlooped again. What could be causing this? The only thing I can think of is substratum.

 

[ineedroot69]

Ok I'm getting nowhere. I got the backup boot.img which I extracted from /data/magisk_backup_sha1/boot.img.gz and flashed it using the command fastboot flash boot boot.img and my OP 5T just shows a white led and ends up in some diagnostic mode. I've also tried flashing the stock boot.img then flashing magisk but that didn't work either. Does anyone want to help me with some instructions a 5 year old could follow?
I have a twrp backup from a while ago which is for the same android version but an older magisk version and I also have one with the broken boot after the failed update from 22.0 and before attempting to flash 22.1 again in twrp.

Edit: I've gotten back into android by restoring my system backup from late 2019. I then uninstalled the broken magisk app installed 22.1 again and all is working fine. I've tried restoring the broken system image but it bootlooped again. What could be causing this? The only thing I can think of is substratum.

i previously asked that too "why is magisk called systemless when it's capable corrupting system partition" but nobody answered me i guess it's one of those question like

Which Came First, the Chicken or the Egg?​

nobody know thou it's better left unanswered

 

[DiamondJohn]

i previously asked that too "why is magisk called systemless when it's capable corrupting system partition" but nobody answered me i guess it's one of those question like

Which Came First, the Chicken or the Egg?​

nobody know thou it's better left unanswered

Magisk itself is not Systemlesss, in that it modifies the BOOT partition, which some would cal a "system" modification. However, technically NOT touching the SYSTEM partition.

The "magic" of Magisk is that after that, all modifications that appear to be to the SYSTEM partition are actual achieved by systemless mods; the mods are in the DATA partition.

Its the differentiation between BOOT and SYSTEM, and that the changes made by Magisk are systemless. Magisk is not ...errr.. "bootlesss"

 

[ineedroot69]

Magisk itself is not Systemlesss, in that it modifies the BOOT partition, which some would cal a "system" modification. However, technically NOT touching the SYSTEM partition.

The "magic" of Magisk is that after that, all modifications that appear to be to the SYSTEM partition are actual achieved by systemless mods; the mods are in the DATA partition.

Irs the differentiation between BOOT and SYSTEM, and that the changes made by Magisk are systemless. Magisk is not ...errr.. "bootlesss"

that make sense so if magisk installation got corrupted then system partion would appear to be corrupted to since magisk is symlinking or like emulating system partition

 

[DiamondJohn]

that make sense so if magisk installation got corrupted then system partion would appear to be corrupted to since magisk is symlinking or like emulating system partition

That could be the case, but if yur boot partition is corrupted (ie not working) then there would be no chance for your phone to work exactly; booot gets loaded before system). But also (as you stated), if the Magisk install starts making "bad" changes to tour system, then the system wont boot / operate correctly. The first step to recover from such a situation is commonly to flash back the original boot image (doing so is built into magisk), and hence remove the system changes and hopefully that will give you a working system. Or remove all your modules (ie systemless changes)

PS: in case you haven't already, simply report your own double post to get it removed.

 

[J.Michael]

@ineedroot69 If you think you can't boot because of a Magisk module, try booting to Safe Mode. I think when you boot to Safe Mode, Magisk does not run. Then, the next time you boot, Magisk runs but does not activate any modules. At that point, you have root, so you should be able to delete or disable the modules.

 

[Iron_Overheat]

On clean flashed (fully wiped) LineageOS 18.1, Xiaomi Mi A1, v22.1, the app didn't work initially after flashing the apk renamed as .zip (it threw an error message trying to download and install the full app after tapping it in the app drawer). I then manually installed the app by using the normal apk. Everything works fine su wise but attempting to install a module crashes the app, event though notifs say it's downloading (but doesn't install).

 

[op3tguy]

First time here and I hope I'm asking this question in the right place.
Oneplus 3T running OOS 9.0.6 since about Jan. 2020 with Magisk installed a long time ago.
TWRP 3.5.2_9

This morning there was a download for Magisk which I ignored. (Little download arrow at the top of the screen.)
I was using the phone fine for a few hours until I got out of the car and put it in my pocket.
10 minutes later I noticed it was hot, took it out and found it stuck at the prompt for start/recovery/bootloader etc.

It will not complete its boot.
I can get to TWRP, I've tried flashing v22.1 but it fails in the same way.

! Unsupported/Unknown image format
- Unmounting partitions
Updater process ended with ERROR: 1

I've attached the dmesg.log and recovery.log if that helps.

I have Nandroid backups from the last time (after) I upgraded to OOS 9.0.6.

Any help would be appreciated.