Magisk notes

Last updated : 4/10/2026 (initial commit)

Introduction

Since my little re‐encounter with Magisk (after mostly abandoning >25.2 for APatch and/or KernelSU, depending on device) in 16/8/2026, I thought it was a matter of time before I had to put up my own thoughts on it. Before that, I only bothered with 25.2 because I don't have to fuck around with overlayfs modules for something like replacing hosts file (and before that we didn't bother because most of what we did didn't really deserve mentioning). But then a fisherman friend of mine got himself an OnePlus 9 (or more like had to complete the device ASAP) and needed some help with rooting (at least getting things to work like how they used to be, but in Magisk 30.7 because Jaguar ROM), causing me to go down the rabbit hole once again.

App anecdotes and installation notes are already previously covered, so read there if you haven't read it.

Usecases

• As previously mentioned, replacing hosts file to block unwanted things (using AdAway or root‐capable file manager depending on internet availability). Requires rw access to /system. This can easily be replaced by NetGuard (which also comes with firewall and network monitor), but it takes up Android's VPN slot. Alternatively, I can replace hosts file using adb or TWRP‐based recovery (especially if I don't want root on my system) but I prefer to not overcomplicate (and sometimes TWRP‐based recoveries aren't reliably present for a device).
• Network monitoring with PCAPDroid root mode. It does have a VPN mode, but aside from the VPN slot (which blocks me from NetGuard, among other stuff), it doesn't catch all of the system‐made connections.
• These mentions of NetGuard reminds me I used to block connections with AFWall+. Though it quickly became irrelevant with per‐app data restriction and/or user‐accessible network permission toggle (and the system being mitigated so its automatic connections either goes where I want them to go or disabled). That said, I'd install NetGuard (or InviZible if I figured it out) on systems I can't fuck up to my absolute preference (which does involve unlocking bootloader and rooting) and take the VPN loss.
• Hiding root access used to be a thing for me back in the FGO days (at least back when MagiskHide is all that's there). Nowadays, Magisk's DenyList & Zygisk (or APatch/KernelSU root whitelist) is enough for me, though I readily list certain additional modules that should help.
• Preferably as little modules installed as reasonably possible. While more modules can be fun to play with, the added complexities will not. Especially if you require reliability out of them.

rw access to /system (among others)

Not to be confused with and/or related to mountrw in TWRP.

Modules :

• agreenbhm's magic‐overlayfs : Brings back rw access to /system in userspace. Works on non‐erofs devices (like OnePlus 5T).
• Kakathic's OverlayFS (1.7.0, hide_root) : Intended for erofs devices.
• Mountify : OverlayFS with tmpfs/ext4 sparse support for reduced detection. Tested on OP9, AdAway worked the way we needed it to. Also applicable to other root methods like APatch and KernelSU, though I am yet to need them there for now. Currently our preferred OverlayFS (or rw access to /system) solution.

Root hiding

For when Magisk DenyList (or APatch/KernelSU app whitelists) was no longer enough. Will require Magisk to disable its own Zygisk (toggle in Settings > Zygisk) and not enforce its own DenyList (toggle in Settings > Enforce DenyList). If on KernelSU, disable Umount modules.

• ReZygisk : Standalone Zygisk written in C (performance‐focused). Also applicable to other root methods like APatch and KernelSU.
• ReZygisk Treat Wheel : Essentially ReZygisk's root hider; but was advertised as World's most advanced and simplest general purpose root module. and The wheel to reinvent the new light., confusing us of what Treat Wheel's real functions were. Also applicable to KernelSU, as Awesome Android Root reported.

More stuff

Read Awesome Android Root (awesome‐android‐root.zhoe.org is cuckflared and Codeberg hates "outdated" browsers (though they are at least aware of Basilisk & Pale Moon) so we linked the GitHub mirror). They'll have way more than I would ever consider touching (let alone bother doccumenting).

Pointless bloat that I won't install

• GPS spoofing (by far the most egregiously pointless)
• Goolag mitigations (TrickyStore, Play Integrity, Anti SafetyCore, etc.)
These Goolag shenanigans has gotten far too complex for me to process, let alone sustainably maintain. Then again, the systems I tend to use invariably lacked GApps so I am not that interested in researching.


• Performance thingies
We'll leave the device to manage its performance, and support if necessary.


• Audio enhancements
Same shit as performance, but then the infinite variability of audio equipment adds to the complexity. (spoken by someone known to abuse at least 10 different headphones)


• Smart charging thingies (just have battery alarm and manually unplug at target percent, we don't need to add more power management issues)
• Xposed / LSPosed / Vector (and Xposed modules)
Somewhat surprisingly, my use case does not require Xposed‐level access to clear. However, if it does, I can immediately imagine myself using HMA‐OSS (not the best example as it also works as a Zygisk module but it was the only thing I would reliably imagine).

Main Page