Magisk General Support / Discussion

[Néocray]

Hey there.
I have a Samsung S9 under Alexis Rom (based on OneUI 2.5).
When trying to update to Magisk 25.1, the direct install method leads to an error "unsupported boot image extra".
So I tried the patch images method. However, there was no “Patch vbmeta in boot image” option as described. So I let Magisk patch the original boot.img and flashed it.
It ended up to boot on a locked screen saying that the device is encrypted, which is not true. Moreover, the /data partition is readable in TWRP.

What have I done wrong?

EDIT: solved the issue with a backup of /data, then formatting it, then restoring the backup.
However, flashing again the 25.1 patched boot image resulted in bootloop: back to 24.3.

 

[rodken]

I'm stuck in a bootloop due to a module I installed (foxyboot?). I can boot normally with the stock boot.img and another boot image that gives me ADB root access.

I tried

adb wait-for-device shell magisk --remove-modules

but the device never established an ADB connection. So then I used the boot image that gives me ADB root, and I deleted /data/ADB/modules and modules_update. That didn't help. I tried data/ADB/magisk/ ./magisk32 --remove-modules, but that just caused the device to reboot, and didn't change the bootloop.

I can't install zips via TWRP currently.

Is it possible for me to just remove all the ADB files on the device eMMC and reinstall magisk manager? Where else is magisk storing files other than /data/ADB ?

For future reference:
-- Always take a working version of the latest Magisk and patch your boot.img
-- This ensures that you can flash and resort back in the event of a catastrophic event
-- Consider investing in installation of the Bootloop Saver.
-- Look into what the 'Magisk Manager for Recovery Mode' can do for you [if you have a working version of TWRP installed].

​

 

[sharpknight]

I just installed Magisk v25.1 on my LG V20 H990DS with stock oreo, and success without having kernel issues. But i can't opened the app itself (stuck on logo), but when downgrading the app to v23.0. It can be opened.

I am experiencing the same issue on my LG G7 ThinQ. I am able to install the Magisk v25.1 app but after the app install, the Magisk v25.1 app does not open. I just see the Magisk mask/face logo. I upgraded from v24.3. I'm able to downgrade back to Magisk v24.3 without problems.

 

[rodken]

I am experiencing the same issue on my LG G7 ThinQ. I am able to install the Magisk v25.1 app but after the app install, the Magisk v25.1 app does not open. I just see the Magisk mask/face logo. I upgraded from v24.3. I'm able to downgrade back to Magisk v24.3 without problems.

If Magisk is stuck on the splash screen:
-- Uninstall Magisk app and repatch your boot image.
-- If that doesn't work - Reflash your boot image and then patch the new boot image.

 

[zgfg]

If Magisk is stuck on the splash screen:
-- Uninstall Magisk app and repatch your boot image.
-- If that doesn't work - Reflash your boot image and then patch the new boot image.

It's absolutely strange that Magisk APP is stuck, but do you have any ground that reinstalling Magisk (patch and flash the image) would help to the Magisk app?!

(It could be that something is wrong with Magisk db or so, and repatching and reflashing Magisk would not fix at all)

 

[zgfg]

I am experiencing the same issue on my LG G7 ThinQ. I am able to install the Magisk v25.1 app but after the app install, the Magisk v25.1 app does not open. I just see the Magisk mask/face logo. I upgraded from v24.3. I'm able to downgrade back to Magisk v24.3 without problems.

Magisk app is only like a UI Manager (remember it's previous name Manager?)

Magisk can work without the app - did you test if Magisk works?

Root: If you previously granted root to an app, does that app still works with root grants (it wouldn't if Magisk is not running)

Modules: Do you have any modules installed, then test if those modules still work

Command Line Interface: From terminal type magisk and read the help (man pages).
With the magisk command + options (all from Terminal), youu can investigate which version of Magisk is running, if Zygisk is active or not, etc (you can even manage DenyList and modules - not just check their status)

If you really did not make some mistake on your side, it would be more than worth to report as an issue to the Magisk GitHub. You would need Magisk Debug 25101 and its logs....

PS: When you say you install Magisk 25.1 and downgrade to 24.3, are you referring really to upgrading and downgrading Magisk (service/mask) or you only install Magisk app v25.1 and then back Magisk app v24.3?

And in that case, what is your procedure of upgrading and downgrading Magisk (I'm not asking about the app) - please describe

 

[sharpknight]

Magisk app is only like a UI Manager (remember it's previous name Manager?)

Magisk can work without the app - did you test if Magisk works?

Root: If you previously granted root to an app, does that app still works with root grants (it wouldn't if Magisk is not running)

Modules: Do you have any modules installed, then test if those modules still work

Command Line Interface: From terminal type magisk and read the help (man pages).
With the magisk command + options (all from Terminal), youu can investigate which version of Magisk is running, if Zygisk is active or not, etc (you can even manage DenyList and modules - not just check their status)

If you really did not make some mistake on your side, it would be more than worth to report as an issue to the Magisk GitHub. You would need Magisk Debug 25101 and its logs....

PS: When you say you install Magisk 25.1 and downgrade to 24.3, are you referring really to upgrading and downgrading Magisk (service/mask) or you only install Magisk app v25.1 and then back Magisk app v24.3?

And in that case, what is your procedure of upgrading and downgrading Magisk (I'm not asking about the app) - please describe

I reverted to Magisk 24.3 and it appears to work. I have root access (my other root apps work).
Yes, all my root apps that previously had been granted root access work.

with terminal command: magisk -c
i get: 24.3MAGISK (24300)

with terminal command: magisk -v
i get: 24.3MAGISK

therefore it appears that i have Magisk 24.3

When I said I installed Magisk 25.1, I downloaded and installed the Magisk Manager 25.1 app. I obtained the app via the Magisk manager, but i also tried the apk from the Github. Both yield the same result where upon opening the Magisk Manager 25.1 app, I see the Magisk mask/face logo. Nothing else. I waited several minutes. SO technically? i was unable to install Magisk 25.1.
I was going to install Magisk 25.1 via the Magisk 25.1 by clicking "Install" and selecting the "Direct Install (Recommended)" option.

 

[ipdev]

Command Line Interface: From terminal type magisk and read the help (man pages).
With the magisk command + options (all from Terminal), youu can investigate which version of Magisk is running, if Zygisk is active or not, etc (you can even manage DenyList and modules - not just check their status)

I missed the one that shows Zygisk status.
Can you nudge me in the direction of the command to check Zygisk.

Cheers.

 

[pndwal]

Hey there.
I have a Samsung S9 under Alexis Rom (based on OneUI 2.5).
When trying to update to Magisk 25.1, the direct install method leads to an error "unsupported boot image extra".
So I tried the patch images method. However, there was no “Patch vbmeta in boot image” option as described.

Sounds like your device has a separate vbmeta partition...

So I let Magisk patch the original boot.img and flashed it.
It ended up to boot on a locked screen saying that the device is encrypted, which is not true. Moreover, the /data partition is readable in TWRP.

What have I done wrong?

EDIT: solved the issue with a backup of /data, then formatting it, then restoring the backup.
However, flashing again the 25.1 patched boot image resulted in bootloop: back to 24.3.

So have you tried with the optional step to disable verity/verification?:

• (Optional) If your device has a separate vbmeta partition, you can patch the vbmeta partition with command:
  fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img

Note: pre 25.0 Magisk used to strip avb_key and avb verification flags for partitions in 2SI devices, but 25+ no longer does this since refactoring 2SI MagiskInit injection...

Configurations that rely on Magisk to strip avb_key and avb verification flags for partitions will no longer work as Magisk no longer does / needs these changes (since fstab modification is not used for magiskinit injection in 2SI any longer).

This means a number of custom ROMs / kernels, including... Kirisakura kernel by @Freak07, will bootloop on some devices if you don't disable verity/verification before booting...

PW

 

[pndwal]

I just installed Magisk v25.1 on my LG V20 H990DS with stock oreo, and success without having kernel issues. But i can't opened the app itself (stuck on logo), but when downgrading the app to v23.0. It can be opened.

I am experiencing the same issue on my LG G7 ThinQ. I am able to install the Magisk v25.1 app but after the app install, the Magisk v25.1 app does not open. I just see the Magisk mask/face logo. I upgraded from v24.3. I'm able to downgrade back to Magisk v24.3 without problems.

Could be worth trying Canary apk or Debug...

User here reports that Stable 25.1 (frozen) behaviour is different, and Debug works... That should mean Canary will work also:
https://github.com/topjohnwu/Magisk/issues/6026#issuecomment-1165267294

Issue was closed and I can't confirm anything there... Hope it provides clues

Since user also reports differences in builds file structure (anomaly?), I'm guessing it could also (possibly) relate to this issue:
www.twitter.com/topjohnwu/status/1543440351460962305

... PW

 

[zgfg]

I missed the one that shows Zygisk status.
Can you nudge me in the direction of the command to check Zygisk.

Cheers.

You're right. I missed that currently even checking the Zygisk status is not supported through CLI

Feature request: Extend CLI to show Zygisk status · Issue #6064 · topjohnwu/Magisk

CLI supports a lot, eg (partially) managing modules and DenyList but seems that even Zygisk status Yes or No cannot be checked through CLI Even better, it would be good to additionally have the opt...

github.com

 

[J.Michael]

If Magisk is stuck on the splash screen:
-- Uninstall Magisk app and repatch your boot image.
-- If that doesn't work - Reflash your boot image and then patch the new boot image.

It is going to be challenging to repatch the boot image after uninstalling the Magisk app.

 

[zgfg]

It is going to be challenging to repatch the boot image after uninstalling the Magisk app.

It was recently shown/discussed in this thread how to use:
/data/adb/magisk/boot_patch.sh

to manually patch the (given) boot.ing

 

[dohanin]

Hi, I suddenly found that while using a root explorer (Total Commander), there were only two folders and a link in /data/data, but in the past I could see all apps' data folders. Then I realised I recently had re-installed Magisk and just left the Mount Namesapce Mode as default (i.e. Inherit). After I changed it to Global, everything back to normal.

I just wanna ask, is this option only affecting the behaviour of those apps granted superuser access? Would it in any way affect root hiding?

 

[BlekBomor]

Whenever i open magisk, it just gets stuck on its logo at the start. I have tried deleting and reinstalling it and even wiped chache and dalvik but it still didnt work. Please someone help me

 

[zgfg]

Whenever i open magisk, it just gets stuck on its logo at the start. I have tried deleting and reinstalling it and even wiped chache and dalvik but it still didnt work. Please someone help me

Did you see the yesterday's post, just a single page back (an answer to the two reports like yours):
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-87114215

 

[J.Michael]

It was recently shown/discussed in this thread how to use:
/data/adb/magisk/boot_patch.sh

to manually patch the (given) boot.ing

Wouldn't boot_patch.sh produce a boot image corresponding to the version of Magisk already installed?

I thought that the original problem was: Magisk and manager app v23 installed and working; Magisk Manager app v25 won't run. Maybe problem will be resolved by replacing Magisk with v25, but how to patch boot image to v25 without being able to run manager app v25?

I thought @rodken's suggestion to reflash stock, then install manager app v25 was likely to work. I didn't see how just uninstalling the manager app could advance the situation. I still do not.

 

[zgfg]

Wouldn't boot_patch.sh produce a boot image corresponding to the version of Magisk already installed?

I thought that the original problem was: Magisk and manager app v23 installed and working; Magisk Manager app v25 won't run. Maybe problem will be resolved by replacing Magisk with v25, but how to patch boot image to v25 without being able to run manager app v25?

I thought @rodken's suggestion to reflash stock, then install manager app v25 was likely to work. I didn't see how just uninstalling the manager app could advance the situation. I still do not.

Yeah, manual procedure will reflash the currently installed Magisk and that's v24.3 in his case

But apparently the user has a problem with Magisk APP v25.1 (Stable, supposed) not launching

It should have nothing to do with patching Magisk. Pndwal yesterday responded, see also a post right before yours (already three users reporting the same here - seems they have to try installing Canary v25101 APP instead, and then proceed with updating Magisk)

 

[huskydg]

I missed the one that shows Zygisk status.
Can you nudge me in the direction of the command to check Zygisk.

Cheers.

Feature request: Extend CLI to show Zygisk status · Issue #6064 · topjohnwu/Magisk

CLI supports a lot, eg (partially) managing modules and DenyList but seems that even Zygisk status Yes or No cannot be checked through CLI Even better, it would be good to additionally have the opt...

github.com

 

[zgfg]

Feature request: Extend CLI to show Zygisk status · Issue #6064 · topjohnwu/Magisk

CLI supports a lot, eg (partially) managing modules and DenyList but seems that even Zygisk status Yes or No cannot be checked through CLI Even better, it would be good to additionally have the opt...

github.com

Thanks for your hint to use --sqlite:

Set Zygisk On:
magisk --sqlite "REPLACE INTO settings (key,value) VALUES('zygisk',1);"

Set Zygisk Off:
magisk --sqlite "REPLACE INTO settings (key,value) VALUES('zygisk',0);"

Check Zygisk status:
magisk --sqlite "SELECT value FROM settings WHERE key = 'zygisk';"

Btw, Magisk.db can be also easily managed from MiXPlorer (incl. Denylist and Root grants)