Update [September 01, 2018]: Within a few hours of the launch of 17.0, the developer team has updated it to Magisk 17.1. The Magisk Manager app has also been revised to v5.9.1. Latest versions of both the packages available below, while original version (Magisk 17.0 and Manager app 5.9.0) have been removed because of the issues associated with them.

In order to customize an Android smartphone’s software and do other geeky stuff like flashing custom ROMs, changing system settings and so on, you need root access to the phone. A while back, SuperSU was the go-to option for gaining root access, but since the launch of Magisk, it has become the best alternative, or maybe even the best option there is.

Related: Download Magisk for Project Treble ROMS

With the help of Magisk Manager, you can easily manage your Android phone’s root access and implement plenty of tweaks thanks to the many Magisk modules available. And today, there are new versions of Magisk and Magisk Manager that bring versions 17.0 and 5.9, respectively.

Downloads

Magisk 17.1 full changelog:
  • Bring back install to inactive slot for OTAs on A/B devices
  • Remove system based root in addon.d
  • Add proper addon.d-v2 for preserving Magisk on custom ROMs on A/B devices
  • Enable KEEPVERITY when the device is using system_root_image
  • Add hexpatch to remove Samsung defex in new Oreo kernels
  • Support non ext4 filesystems for mirrors (system/vendor)
  • Make pts sockets always run in dev_pts secontext, providing all terminal emulator root shell the same power as adb shells
  • Kill all processes with same UID of the target to workaround OOS embryo optimization
  • Move all sepolicy patches pre-init to prevent Pixel 2 (XL) boot service breakdown
Magisk Manager 5.9.1 full changelog:
  • No more on boot notifications
  • Support new mechanism for installing to inactive slot for OTAs on A/B devices
  • Fix restore Magisk Manager settings on Android Pie
  • Verify existing file checksums to prevent unnecessary re-downloads
  • Update SNET extension to use new Google API, fix “Invalid Response” errors
  • Move fingerprint settings to magisk database to prevent the settings to be easily removed
  • Fingerprint settings are now guarded with fingerprint authentications before it can get changed
  • Prevent any files to be downloaded to /sdcard/MagiskManager