Download and install latest Magisk v15.0 official Root & Universal Systemless Interface Android 5.0+to 8.1 Oreo

Update: Magisk 16.7 Beta, and Magisk v17.0 Stable are now available for download with major improvements to support Project Treble GSIs and A/B devices, officially supports Samsung Galaxy S9/S9+, random Root loss issue fixed, and misc bugs fixes. See the full changelog from below. Also, download the latest Magisk 16.7, Magisk stable 16.0, and Magisk Manager APK from below.

Latest Magisk zip and Magisk Manager can be useful in gaining root access on most of the Android devices running Android P 9.0, Android 8.0/8.1 Oreo, 7.0/7.1.1 Nougat, or previous versions. It will enable you to root Android phones from manufacturers including Google Pixel and Nexus series, Samsung Galaxy series, OnePlus, Xioami, Sony, and from many more. Magisk is popular tool to root latest Android 8.1 Oreo.

Magisk is being updated to Beta version 16.7. This is great news for more and more Android phones can be rooted using the most popular rooting tool called Magisk followed by SuperSU. The latest version of Magisk brings many improvements to the Super User libraries, the manager app, and brings support to latest Android versions. Apart for being a rooting tool, it also brings several new features and functionalities like seamless OTA update installation even on a rooted device, Magisk hide, root hide, bypass Google’s Safety Net, install various modules, etc.

Recently, all the major developers are rolling out newer versions of their software, tools,  apps, or packages in order to bring about support for the latest Android 8.1 Oreo and the latest smartphones in the market. Developers of Xposed Framework, Lineage OS 15.1, Resurrection Remix 6.1.0, Paranoid Android 8.0, and many others are currently working on the Oreo platform.

Download Latest Magisk v16.7+ Beta

The latest version of Magisk is v16.6 Beta. You can also download the previous Magisk stable 16.0 if you face any issues. See the changelog and choose the best possible version for your device. Download Magisk installer zip and Magisk Manager.

Previous Magisk v16.6 Beta

Previous Magisk v16.4 Beta

Download Magisk installer zip for the latest beta version. See the changelog from below.

Stable Magisk 17.0

The Magisk 17.0 is the latest stable version for rooting Android phone. Whereas, the Magisk 16.7 is the latest beta version. So Magisk v18 will be the next stable version. Also, installing Magisk Manager APK is mandatory, listed below.

Magisk Uninstaller

Flash the Magisk Uninstaller if you would like to delete or remove Magisk completely.

Download latest Magisk Manager 5.8.2+ APK

Installing the latest Magisk Manager version is must for better experience. This is a companion application for running Magisk. Magisk Manager APK will basically manage or or grant root access to various Android devices. This is a must have app for managing Magisk.

Previous versions of Magisk Manager:

Magisk v16.7 Changelog

Magisk v16.7 update log:

Bug Fixes:

  • EMUI’s logcat permission bug fixes.
  • Support for new Treble devices (e.g. OnePlus 5/5T).
  • Some custom Treble devices (many Xiaomi devices) modifies the device tree to redirect vendor to an unused partition, and this is now fully supported!

Legacy Support:

Starting from v16.7, the native part of Magisk is compiled against SDK 16 (Android 4.1 JellyBean), which is the beginning of legacy support. This doesn’t mean you can flash Magisk on your obsolete devices now, as there are tons of stuffs needed to be done: Magisk Manager does not install on anything lower than Android 5.0; most features are not even tested yet. Proper legacy support won’t happen until the next release is pushed to the stable channel though, v17 is my top priority now and I want it to be as bug free as possible!

Magisk v16.6 update log:

  • Magisk Manager will preserve the random package name when upgrading within the app. Magisk will no longer prefer the package name com.topjohnwu.magisk over repackaged (hidden) Magisk Manager to prevent malware from targeting this specific package name. If you have a repackaged Magisk Manager installed, com.topjohnwu.magisk will be forcefully denied root access. You can use Restore Magisk Manager in settings, or uninstall the repackaged Magisk Manager to unlock com.topjohnwu.magisk.
  • The logic to calculate free space in ext4 images is replaced with new extremely precise methods, hopefully no more module installation failures caused by images should happen. All modules using template 1500 will automatically benefit from the new free space calculation method on Magisk v16.6+, no additional changes are needed.
  • Support for Samsung Galaxy S9/S9+ is officially added.
  • Magisk v16.4 switched to 32-bit only binaries and caused issues in some apps. A new wrapper script is added to eliminate all possible quirks.
  • Treble GSIs (e.g. phh AOSP) sometimes require replacing adbd in ramdisk and used to conflict with Magisk. It is now fixed and ADB will fully function when using GSIs.
  • LineageOS introduced addon.d-v2 to A/B partition devices, the addon.d script is updated to be A/B aware (untested on my side)
  • Magisk v16.4
    – [Daemon] Directly check logcat command instead of detecting logd, should fix logging and MagiskHide on several Samsung devices
    – [Daemon] Fix startup Magisk Manager APK installation on Android P
    – [MagiskPolicy] Switch from AOSP u:r:su:s0 to u:r:magisk:s0 to prevent conflicts
    – [MagiskPolicy] Remove unnecessary sepolicy rules to reduce security penalty
    – [Daemon] Massive re-design /sbin tmpfs overlay and daemon start up
    – [MagiskInit] Remove magiskinit_daemon, the actual magisk daemon (magiskd) shall handle everything itself
    – [Daemon] Remove post-fs stage as it is very limited and also will not work on A/B devices; replaced with simple mount in post-fs-data, which will run ASAP even before the daemon is started
    – [General] Remove all 64-bit binaries as there is no point in using them; all binaries are now 32-bit only.
    Some weirdly implemented root apps might break (e.g. Tasker, already reported to the developer), but it is not my fault smile
    – [resetprop] Add Protobuf encode/decode to support manipulating persist properties on Android P
    – [MagiskHide] Include app sub-services as hiding targets. This might significantly increase the amount of apps that could be properly hidden
  • Magisk Manager v5.7.0
    – Add app shortcuts for Android 7.1+
    – Bump minimal module minMagisk requirement to 1500
    – Adjustments for new sepolicies on v16.4+
    – Fix crashes when refreshing the online repo

Magisk v16.3

– [General] Remove symlinks used for backwards compatibility
– [MagiskBoot] Fix a small size calculation bug

  • v16.2

– [General] Force use system binaries in handling ext4 images (fix module installation on Android P)
– [MagiskHide] Change property state to disable if logd is disabled

Magisk v16.1 (1610)

  • Update resetprop
  • Update several SELinux stuffs
  • Add workaround for missing `make_ext4fs`
  • Fix SELinux issues on Android 6.0 and lower

Magisk Manager v5.6.4

  • Remove the blacklisted apps using SafetyNet (e.g. Pokemon GO)
  • Manually disable WAL mode for SQLite as Android P is weird
  • Change paths for hiding manager as Android P added more restrictions
  • Fix hide manager on old Android versions

The latest Magisk Manager works on most of the Android phones running 5.0/5.1 Lollipop, 6.0.1 Marshmallow, 7.1 Nougat, 8.0/8.1 Oreo.

How to install Magisk?

Read: Detailed tutorial on how to install Magisk

  • Make sure your Android device has the latest TWRP recovery installed. See how to install TWRP recovery. For Samsung devices visit this tutorial.
  • Now, download the latest Magisk zip and Magisk Manager APK. You can also simply install the Magisk Manager and download the flashable zip from there.
  • Transfer Magisk installer zip, manager APK, and uninstaller to phone storage.
  • You may want to uninstall Magisk if your version is too old.
  • Reboot device into TWRP recovery. Turn off your phone then press and hold volume (down/up) + power button at the same time.
  • Take a full Nandroid backup.
  • Flash the Magisk zip by going to install option in TWRP and selecting the latest version.
  • Reboot to system.
  • You may want to install the latest Magisk Manager again.
  • Download Android P or Oreo.

That’s it reboot the device to the system and open the Magisk Manager app to start granting root access and start using various modules.

Thanks to developer topjohnwu for deploying Magisk Manager 5.8.0 APK and made the whole project as one single application. Being ambitious, the developer also updated MagiskSU to work the same as proper Linux implementation. Super User package has also been completely changed in order to bring more stability.


Sarang Avatar

One response


  1. Ashok Poolla Avatar
    Ashok Poolla

    Hello, Thanks for continually updating this post to reflect Magisk’s development.

    I have a simple question, I’m using Resurrection Remix 6.0.1 ROM (Lineage OS 15.1 Oreo) on my Xiaomi Redmi Note 4 (codenamed Mido) which happens to be a treble-supported ROM. Since Magisk v16.0 Stable version does not identify support for Treble, the ROM authors have built a custom-Magisk version (Based on v16.0 stable) to include Treble support for the said device and ROM. My question is, having noticed all the new development since v16.0 Stable all the way to v16.7 Beta (at the time of this writing), I’d like to switch to 16.7 beta after carefully removing 16.0 because of the tremendous amount of bug fixes, official treble support, etc..but I’m wondering if doing so would bring unintended consequences. Of course, I’d have to try it myself to see if the switch works reliably enough but I’d like to ask you before doing anything.

    Additional Info:
    ——————–
    Current device I’m using: https://www.gsmarena.com/xiaomi_redmi_note_4-8531.php
    The ROM I’m running on this phone right now: https://forum.xda-developers.com/redmi-note-4/xiaomi-redmi-note-4-snapdragon-roms-kernels-recoveries–other-development/rom-resurrection-remix-v6-0-0-t3748465

Leave a Reply