Revision [312]

This is an old revision of MagiskHideIssues made by didgeridoohan on 2018-07-19 09:03:09.


MagiskHide Issues

Test MagiskHide

First thing to do is to toggle MagiskHide off and on again. Sometimes MagiskHide stops working temporarily after an update of Magisk or the Manager. If it still doesn't work, make sure MagiskHide is actually working by using a root checker or a root app. Start by making sure the app can detect that your device is rooted. After that, add the app to the Hide list and see if it no longer can detect root. If that is the case, MagiskHide is working on your device. If you still can't get it to work, see "Asking for help/reporting bugs".

MagiskHide fails after an update

If MagiskHidestarts failing after an update to either Magisk, the Manager or both it's usually fixed by toggling MagiskHide off and on (see ”Test MagiskHide above”).

Android logging

Android logging has to be enabled for MagiskHide to work (see ”MagiskHide requirements”).

MagiskHide doesnt show in the Manager

Your device’s kernel probably doesn’t have support for mount namespace (see ”Mount namespace issues” below).

MagiskHide isn't working

If you can’t get MagiskHide to work, either for SafetyNet or any other app detecting root, there are a few things you can try.

Start by testing if MagiskHide actually works (see "Test MagiskHide" above).

Starting MagiskHide manually

MagiskHide is enabled by default and should start automatically on boot. If it isn’t working, try toggling MagiskHide off and on in the Manager settings. If MagiskHide just won't start when toggling it in the Magisk Manager (check the Magisk log, it might have started but the Manager doesn't reflect it), try starting it manually. This can be done in a terminal emulator (as su) by executing the following command:
magiskhide --disable
magiskhide --enable

Systemless hosts

Some users have reported issues with MagiskHide if systemless hosts is enabled in Magisk Manager settings. Try disabling it and rebooting to see if it fixes your issue. If this works, please help finding out more by providing logs and details in the support thread (also see "Asking for help/reporting bugs").

Kernel logcat support

If your device's kernel doesn't have logcat support the MagiskHide process monitor won't be able to see when a process/package is started and therefore won't unmount the necessary folders to hide Magisk and it's core features.

If you have the beta version of Magisk installed (and if you don't, install it; also see "Asking for help/reporting bugs"), you can look in the magisk_debug.log if there are entries for unmounting when MagiskHide runs. If there isn’t, it's likely you have this issue.

You can test for this by running the following command in a terminal app:
logcat -b events -v raw -t 10

If you get an error you might have a logcat issue. Ask in your kernel/ROM thread for advice or try a different kernel.

There's also a possibility that your issue can be fixed by using a kernel managing app like Kernel Adiutor. It might be enough just to install it to enable logcat support. This is untested (by me at least) and just speculation on my part from what I've seen around the forums (please confirm if you have information about this or tested it).
A huge thank you to tamer7 for teaching me about this.

Huawei devices often have logcat disabled. See here for more details.

Logger buffer size

If you have turned off Logger buffer size under Android settings - Developer Options, MagiskHide won't be able to monitor when a process/package is started and won't unmount the necessary folders to hide Magisk and it's core features.
Thank you to Chaplan for the tip.

Mount namespace issues

If you see this line in the Magisk log/magisk_debug.log (see "Asking for help/reporting bugs"): "proc_monitor: Your kernel doesn't support mount namespace", your device has a Linux kernel that is to old. The Linux kernel version have to be at least 3.8 (thank you TheCech12), or otherwise have the necessary features backported. Ask in your ROM/kernel thread or try a different ROM and/or kernel.

Apps added to the MagiskHide list disappears

If your device can't properly mount the Magisk image, you might still be able to use MagiskHide. There won't be any way for Magisk to permanently store the information about what apps you want to hide root from (apart from SafetyNet) and you will have to add them back to the list after each reboot.

The above might be because of a faulty f2fs implementation (see “Issues with f2fs”), that the Magisk image is mounted read-only (run the command “mount | grep "/sbin/.core/img” in terminal to see if it’s rw or ro. A different kernel might fix this) or that the Magisk image is corrupt (easiest way to fix this is to run the Magisk uninstaller and start from the beginning or use fsck. Google it…).
Valid XHTML :: Valid CSS: :: Powered by WikkaWiki