Magisk has been updated to version 14.5, in beta. The new build of Magisk brings a series of substantial improvements to the popular root utility.
The first notable feature of this update is the updated device support list; Magisk now supports the almost 2-month old Pixel 2 and Pixel 2 XL. While getting device support off the ground has not been easy for these devices due to a series of bootloader issues and other similar problems, Google has set out to fix this with a series of updates aiming to resolve said issues, and judging by this Magisk release, their move has been effective. Additionally, the update fixes issues that Xiaomi Mi A1 users were facing with Magisk, meaning the utility is more accessible than ever before.
Some substantial improvements to MagiskHide are included with this build.
Furthermore, this build brings some substantial improvements to MagiskHide, making it more effective at implementing systemless root than ever before. First and foremost, choosing to hide Magisk changes the package name of Magisk Manager, meaning apps that attempt to catch out Magisk by detecting package IDs will not find it installed. However, the developer, topjohnwu, does not recommended this option to users unless it is absolutely necessary.
Furthermore, the Magisk core has had a directory change; moving to the /Magisk mount point to
/sbin/.core. This means that any Magisk modules should not be using the /Magisk directory as a hard-coded access point anymore, helping further to maintain the function and integrity of MagiskHide. Additionally, the Magisk installation process is now more unified and streamlined on new devices, thanks to magiskinit. magiskinit will now detect what device it's being run on after flashing and will dynamically inject the changes necessary to optimise the Magisk experience on a specific device.
This build is not daily driver material. I repeat – this is not a daily driver.
However, this build is not perfect; far from it. While this build does introduce a lot of under-the-hood refinements, it also has a number of critical, crippling flaws that will prevent it from being your daily driver – at least for now. This beta is aimed primarily at developers, as we'll discuss further later on. Notably, changing the package name of Magisk can cause it to drop root access altogether, along with error messages in the logcat of OnePlus devices Samsung devices and others from the NDK r16 when trying to call su. Additionally, the Pixel 2 also shows a popup saying that avb-verity is off – however, this is not a severe issue. Either way, it's likely that this build is not daily driver material just yet.
This beta is aiming to solve issues with devices that use non-standard boot image formats, such as offerings from Samsung, Google and some other limited exceptions – this build should work largely as intended on near-AOSP functioning devices such as OnePlus or HTC phones. Furthermore, the build is primarily intended for developers, and the beta thread states that at least basic debugging skills are needed to run this build, according to topjohnwu. If that didn't scare you off, you can view the full changelog below, and grab the build from this thread over on the XDA Developer Forums.
- [Daemon] Moved internal path to /sbin/.core, new image mountpoint is /sbin/.core/img
- [MagiskSU] Support switching package name, used when Magisk Manager is hidden
- [MagiskHide] Add temporary /magisk removal
- [MagiskHide] All changes above contributes to hiding from nasty apps like FGO and several banking apps
- [Magiskinit] Use magiskinit for all devices (dynamic initramfs)
- [Magiskinit] Fix Xiaomi A1 support
- [Magiskinit] Add Pixel 2 (XL) support
- [Magiskboot] Add support to remove avb-verity in dtbo.img
- [Magiskboot] Fix typo in handling MTK boot image headers
- [script] Along with updates in Magisk Manager, add support to sign boot images (AVB 1.0)
- [script] Add dtbo.img backup and restore support
- [misc] Many small adjustments to properly support old platforms like Android 5.0
What do you guys think? Will you try your hand at this build? Let us know in the comments below, or post over on our forums.