Magisk General Support / Discussion

[rodken]

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)

There were instances where I suffered the same fate [twice] and simply reflashing a previously patched image would solve the dreaded 'stuck on splash screen' conundrum.

 

[DiamondJohn]

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].

You forgot Plan Z. Make backups before doing anything that may trash your setup, and have a restore plan.

...snip...

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

Id be careful with using MiX. Although I use MiX, editing dB's can have issues. It was a while back, but what I think I saw happen, is that MiX makes a copy of the database, makes the change to its own copy, and then copies back over the original. That can fail if there is another app using the dB or has the same plans.

Another option is to use SQLite directly from the command line, or use the app I built TeMeFI, which also edits the dB in-situ; its literally has a GUI to SQLite command line. MiX is closed source so its hard to know, but it failed to update a major db in android (I think the MediaDB), where the other options worked.

But the 1st option is without question the best option. ie have Magisk mess with its own database. Database concurrency is a hard taskmaster.

 

[ipdev]

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

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

Looks like vvb2060 is against adding zygisk to the CLI.

Would be nice if we could check zygisk status just like we can the denylist.

Check the Zygisk status when you are installing a Zygisk module.​

magisk --denylist status 2> /dev/null
if [ $? -ne 0 ]; then
  ui_print " "
  ui_print " The Denylist is not enforced."
fi

'Denylist is not enforced' returns as error (1).​

'Denylist is enforced' returns as success (0).​

This would be nice.

magisk --zygisk status 2> /dev/null
if [ $? -ne 0 ]; then
  ui_print " "
  ui_print " Magisk Zygisk is not enabled."
fi

Assuming zygisk status returns the same as denylist status.​

'Zygisk is not enabled' returns as error (1).​

'Zygisk is enabled' returns as success (0).​

Guess we can work with the sql method.

if [[ $(magisk --sqlite "SELECT value FROM settings WHERE key = 'zygisk'" | cut -d '=' -f2) -ne 1 ]]; then
  ui_print " "
  ui_print " Magisk Zygisk is not enabled."
fi

Thank you for nudging me in the direction of the command to check Zygisk.

Cheers.

 

[rodken]

Make backups before doing anything that may trash your setup, and have a restore plan.

+1

 

[dl200010]

Then I don't understand "Maybe the failed install was caused by 25.0 not 25.1"...

and AFAIK, Pixel always used Delta...

Are you talking about need for full data wipe needed in order to install Magisk after an OTA?... IIRC, late Pixels had this issue for a long while... If you're still facing this to boot w/ Magisk 25.1+ after OTA, please say...

Restore images, take incremental OTA, download full ROM matching OTA, extract boot image, patch/flash boot image should work without data wipes generally... PW

I just did the update. I disabled the only module I have, which is the "Systemless Hosts" from Magisk itself. I downloaded the OTA incremental from Oxygen Updater. Restored Images in Magisk (25.1). Installed the update with the System Update APK that OnePlus had out for the A12 betas (because you cannot do local updates anymore in settings). I than went into Magisk and installed to inactive and rebooted from Magisk. It came up just fine. I think there must have been an error in 24.3 or I have to disable even "Systemless Hosts" module. I am now fully up to date. Thanks @pndwal

 

[Fif_]

I have a OnePlus 9 on OxygenOS 12 C.48. C.61 is now being pushed out. Oxygen Updater no longer offers the full updates and is telling me to use incremental.

That is more than annoying. That means you have to boot once into Android with Magisk off after an OTA . If you have debloated apps, you can end up with the debloated apps reappearing when Magisk is not installed, getting updated, then having the system package pulled under the updated debloated apps. I've had instances where if I then remove the updated app, the system will refuse to boot again because expected libraries are missing. I was able to recover by editing /data/system/packages.xml, which I do not recommend for the faint of heart or noobs.
Anyways, you should do that magisk-less reboot in Airplane mode anyways, that prevents the problem from occurring in the first place, and saves you from losing certified status.

 

[dl200010]

That is more than annoying. That means you have to boot once into Android with Magisk off after an OTA . If you have debloated apps, you can end up with the debloated apps reappearing when Magisk is not installed, getting updated, then having the system package pulled under the updated debloated apps. I've had instances where if I then remove the updated app, the system will refuse to boot again because expected libraries are missing. I was able to recover by editing /data/system/packages.xml, which I do not recommend for the faint of heart or noobs.
Anyways, you should do that magisk-less reboot in Airplane mode anyways, that prevents the problem from occurring in the first place, and saves you from losing certified status.

Well, I am now up to date. It might have been a bug in Magisk that was fixed in 25.1, or because I never disabled the one module I have in Magisk. I was able to use "Install to inactive" in Magisk after the incremental OTA just fine. I don't do anything special with bloat, just disable it in settings, and Neo Backup can disable those that settings tries to prevent you from doing. Even if I flash stock boot the bloat stays disabled.

 

[pndwal]

Apparently Magisk 'repository owner' doesn't want GitHub members to offer any help / clarity after issues are closed without proper resolutions...

https://github.com/topjohnwu/Magisk/issues/6072

This already closed issue was effectively killed within minutes of my comments. PW

 

[dl200010]

Apparently Magisk 'repository owner' doesn't want GitHub members to offer any help / clarity after issues are closed without proper resolutions...
View attachment 5654997
https://github.com/topjohnwu/Magisk/issues/6072

This already closed issue was effectively killed within minutes of my comments. PW

Unfortunately, many many devs are like that, not just these. Don't know why, but they are.... This seems to be completely vvb2060 doing it because they didn't like being wrong.

 

[pndwal]

Unfortunately, many many devs are like that, not just these. Don't know why, but they are.... This seems to be completely vvb2060 doing it because they didn't like being wrong.

Not saying she's wrong... It's a fair response to a misleading issue description...

But I would like to see Devs (especially more than one LSP Dev) being more respectful of others' time / efforts, and also of users who battle w/ magiskbot & submit the same issue 5 times before getting it right and it's accepted... Bit frustrating for all involved, and has alienated a few...

And we do have some good l o n g s u f f e r i n g role models... Perhaps @osm0sis could make a pull request for a an internationally acceptable magisk-manners code for dev / modding community relations... PW

 

[73sydney]

Not saying she's wrong... It's a fair response to a misleading issue description...

But I would like to see Devs (especially more than one LSP Dev) being more respectful of others' time / efforts, and also of users who battle w/ magiskbot & submit the same issue 5 times before getting it right and it's accepted... Bit frustrating for all involved, and has alienated a few...

And we do have some good l o n g s u f f e r i n g role models... Perhaps @osm0sis could make a pull request for a an internationally acceptable magisk-manners code for dev / modding community relations... PW

Sadly not the 1st time the dev has gotten "spicy"

Really responses like "ignore it" to an issue are beyond less than helpful

And yes @osm0sis is a good egg, went to bat for me to get my feature request for magisk manager to stay on Install tab after local module install, upsold that one twice if my memory serves....

 

[dl200010]

Sadly not the 1st time the dev has gotten "spicy"

Really responses like "ignore it" to an issue are beyond less than helpful

And yes @osm0sis is a good egg, went to bat for me to get my feature request for magisk manager to stay on Install tab after local module install, upsold that one twice if my memory serves....

My opinion is "ignore it" should be banned as a response, especially from a dev.

 

[J.Michael]

I interpreted "ignore it" as advice to the original poster to ignore the error messages. I couldn't follow the process well enough to tell if/where files were being copied, but I think the error message occurs when a copy is done with the "preserve permissions, time, owner" flag, and the destination filesystem does not support one or more of those attributes.

I was more annoyed when the "response" to @pndwal's request for clarification was just a repeat of a section of the log.

 

[dl200010]

I interpreted "ignore it" as advice to the original poster to ignore the error messages. I couldn't follow the process well enough to tell if/where files were being copied, but I think the error message occurs when a copy is done with the "preserve permissions, time, owner" flag, and the destination filesystem does not support one or more of those attributes.

I was more annoyed when the "response" to @pndwal's request for clarification was just a repeat of a section of the log.

The response should have been more of "this message can be safely ignored" instead. I also take issue with how they closed down the issue and locked it, because @pndwal was trying to help. Also take issue with how they hid his last comment.

 

[BlueMan_86]

Is it possible that Magisk v25 bricked my device? I updated to latest miui rom Mi10T Pro, before that I used v24.. BUT, when I intalled v25, phone caused to bootloop, that is not strange at all, most weird thing is when I back my original boot.img, phone stuck in bootloop and that was it... My phone have "vbmeta" so I selected that option on install... What is going on there... How is posible that original boot.img want work and phone bricked...
Any ideas whats happened and what was causing that? Also I deleted magisk modules folder over TWRP, but nothing.. just dead bootloop... Thanks..

 

[zgfg]

Boot with that original boot.img but having Magisk v25 APPLICATION installed.

From Magisk app, chose Install (Magisk) - main window, on top, right; Select and Patch, navigate to the original boot img file, do not tick Recovery option; Let's go

When done, youl'll have the patched boot img (in Download folder)- from Fastboot or TWRP, flash to Boot (and do not play with vbmeta)

Reboot to Magisk

That's the way Magisk installation works on all Xiaomi devices, MIUI 10/11/12... (btw, I have two of them, and do it as above since 2019)

Try first that way. If it won't work,then bootloop could be due to the incompatible Magisk module that was not disabled (but that usually happens when you upgrade ROM, not Magisk like you). That can be also fixed, but try first as above

 

[pndwal]

Is it possible that Magisk v25 bricked my device? I updated to latest miui rom Mi10T Pro, before that I used v24.. BUT, when I intalled v25, phone caused to bootloop, that is not strange at all, most weird thing is when I back my original boot.img, phone stuck in bootloop and that was it... My phone have "vbmeta" so I selected that option on install...

I'm assuming you mean you did this:

• (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

What is going on there... How is posible that original boot.img want work and phone bricked...
Any ideas whats happened and what was causing that? Also I deleted magisk modules folder over TWRP, but nothing.. just dead bootloop... Thanks..

So likely your device needs AVB (Android verified boot) intact and you have disabled it by patching vbmeta to disable-verity & disable-verification...

Instructions don't say to do this; they simply say it's an option & you can...

I believe this method has been added for the relatively few devices, eg (perhaps only) those running custom kernels, that require disable-verity & disable-verification... My guess is that most modern stock ROMs will normally require working AVB...

Since you've patched vbmeta in addition to boot image, you'll need to restore this image from ROM package also... or can dirty flash complete ROM... PW

 

[pndwal]

Did a bit or playing with modern Magisk, and it seems we can no longer 'downgrade' the App to a version earlier than running Magisk daemon in 25100+...
Force app version not lower than daemon
vvb2060 authored and topjohnwu committed 22 days ago

So with Magisk 25101 loaded, there is no way I can downgrade the App to Stable 25100 (despite the binary being in sync), or run any earlier app (Including old Manager app) on my device.

Whether calling apk package from App by setting Channel to Stable (App not hidden), or by downloading this or earlier Apps (previous App uninstalled), all the packages will simply install the stub app which in turn prompts:

and this always fails with never ending:

until it is force-closed.

(I guess Build dynamic stub resource APK at runtime … topjohnwu and vvb2060 committed 17 days ago
or Fix app state, vvb2060 authored and topjohnwu committed 7 days ago
may fix some broken behaviour.)

At present, the only Magisk App I can seem to install successfully (w/ 25101 binaries loaded) is 25101!* ... This installs the full App (not stub) as expected.

... It seems we must at least remove root injection and do an initial re-flash again just to install synced Beta/Stable App, and that any other 'downgrade' is also precluded...

*Further, I've found I can no longer even install a CI App, even one later than my Canary build (these actually use the same last app version, ie. also 25101), from Actions (Continuous Integration test build) runs with 25101 Magisk binary installed! ... Same behaviour as above... I'm guessing this is due to app signature checks.

If anyone wants to try, or is able to downgrade the Magisk App from current Canary or Debug to Stable, or to upgrade this to a CI build w/o restoring unpatched images (removing root), please report... I'll reward you with some happy faces... PW

 

[pndwal]

The response should have been more of "this message can be safely ignored" instead. I also take issue with how they closed down the issue and locked it, because @pndwal was trying to help. Also take issue with how they hid his last comment.

@osm0sis has changed "ignore it" to "ignore the errors"...
https://github.com/topjohnwu/Magisk/issues/6072#issuecomment-1178394392

Users being met ½ way? ... PW

 

[samhhmobil]

Hi,

does somebody knows, how the german health insurance app "TK" does detect root?

My configuration:
LOS 19.1
Magisk 24.3 (app hidden),
Zygisk, Shamiko 0.5.1(115),
MagiskHidePropConfig is set,
Safetynet is passed! CTS is passed.
No TWRP folder.

What am I missing?

samhhmobil