How To Root Device With Magisk

[Shelly Takacs]

Rootingis basically giving yourself privileges to access features on your phone which either would be blocked by the carrier or the actual provider of the phone. There are a variety of apps, access to which can only be granted if your phone has root permissions. For example, you can download an advanced screen recorder.

To the people new to rooting, you are in safe hands! To the people who know rooting, how irritating was it to constantly keep rooting/unrooting your phone in order to get OTA updates! Or the inability to use banking applications on your phone? We totally feel you.

Now, to run that application, you may choose to unroot your phone, work on that app, and re-root your phone using Chainfire SuperSU. But rooting and unrooting your device is a lengthy process. You may do it once but doing it repeatedly will surely feel tedious.

If you want to grant/deny permission for any application, this can be easily done with the help of Magisk App. There are a ton of free modules available on Magisk App, from them you can download apps and games to your Android device. And the plus point is, you can add your own or custom repositories to get stuff from.

Magisk Manager is a well-developed rooting application compatible with Android smart devices and reportedly does not include any sort of malware. It does not modify the boot partitions neither does it touch the system partitions. Unlike other rooting apps, it does not install any third-party applications. Hence, you can rest assured that Magisk Manager is risk-free.

Q.6 With which Android versions is Magisk compatible?

Magisk is now completely compatible with the latest Android version. This app would function on all the versions above the Android 6.0.

Q.7 Why is Magisk not working properly on my phone?

Installing the Magisk Manager to external or adoptable storage can cause some functioning issues. We recommend reinstalling the app to internal storage.

Magisk Manager is undoubtedly a must-have application. It is a one-stop solution to all the root-related issues that usually arise later after rooting of the device. We hope you have now understood what is Magisk, what is Magisk Manager, and what is the use of Magisk Manager. While it may take some time for you to get a hang of it, you will find it totally worth your while.

Sit, thank you very much for your great work

I am using OnePlus 7T running on 10.3.8 (Indian variant) and rooted with Magisk v 22100, i am having a problem were i cant start my phone, what happen is that uninstalled two Apps (Google Duo & Cloud Services from oneplus) by using Debloat, i rebooted my device only once after i unstilled those two apps, what happened is that my phone went to boot loop animation, i have tried several ways to fix this issue by:

Magisk Manager is the official app for managing root on Android devices. After unlocking the boot loader and flashing the corresponding file to root your device, Magisk Manager allows you to manage root permissions and grant them to the applications that request it. For added security, you can enable biometric verification in Magisk Manager, so that only the super-user permission is granted via fingerprint or face detection.

Magisk Manager also allows you to install additional root-related modules. For example, you can install SafetyNet Fix, which helps you to hide certain apps that your device is rooted, as well as the boot loader is unlocked.

From Magisk Manager's settings, you can also install Magisk with Zygisk, which allows developers to create more efficient modules by preloading the resources to be used in the system's memory. You can also choose the apps in which to hide the root, so that you can use them without problems or limits. Among them, you find games and banking and payment apps, which can limit functions if your device is rooted.

Magisk Manager is the best tool for root permissions on Android. It is the most widespread, flexible, and easy-to-use option thanks to its "systemless" flashing mode, which does not modify the Android system partition. In addition, it is compatible with all devices on the market after Android 8.

It's possible to install Magisk Manager without having root permissions on the device, but you can't root your device unless you've completed the previous steps. So it will tell you if you've successfully completed the steps you need in order to enjoy root permissions.

Uptodown is a multi-platform app store specialized in Android. Our goal is to provide free and open access to a large catalog of apps without restrictions, while providing a legal distribution platform accessible from any browser, and also through its official native app.

I have an Android-based phone (2.3.6) with unlocked root privileges.Since i'd like to have access to my phone through my computer, today i've installed QtAdb and Android SDK.If i open a command prompt and i do

The problem is that, even though your phone is rooted, the 'adbd' server on the phone does not use root permissions. You can try to bypass these checks or install a different adbd on your phone or install a custom kernel/distribution that includes a patched adbd.

Or, a much easier solution is to use 'adbd insecure' from chainfire which will patch your adbd on the fly. It's not permanent, so you have to run it before starting up the adb server (or else set it to run every boot). You can get the app from the google play store for a couple bucks:

You have to grant the Superuser right to the shell app (com.anroid.shell).In my case, I use Magisk to root my phone Nexsus 6P (Oreo 8.1). So I can grant Superuser right in the Magisk Manager app, whih is in the left upper option menu.

The result of Ramdisk determines whether your device has ramdisk in the boot partition. If your device does not have boot ramdisk, read the Magisk in Recovery section before continuing.

If your device has boot ramdisk, get a copy of the boot.img (or init_boot.img if exists).

If your device does NOT have boot ramdisk, get a copy of the recovery.img.

You should be able to extract the file you need from official firmware packages or your custom ROM zip.

Warning: NEVER flash patched image shared by others or patch image on another device even if they have the same device model! You may need to do a full data wipe to recover your device. ALWAYS patch boot image on the same device where you want to install Magisk.

The easiest way to uninstall Magisk is directly through the Magisk app. If you insist on using custom recoveries, rename the Magisk APK to uninstall.zip and flash it like any other ordinary flashable zip.

In the case when your device does not have ramdisk in boot images, Magisk has no choice but to hijack the recovery partition. For these devices, you will have to reboot to recovery every time you want Magisk enabled.

When Magisk hijacks the recovery, there is a special mechanism to allow you to actually boot into recovery mode. Each device model has its own key combo to boot into recovery, as an example for Galaxy S10 it is (Power + Bixby + Volume Up). A quick search online should easily get you this info. As soon as you press the key combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. If you decide to boot into the actual recovery mode, long press volume up until you see the recovery screen.

Installing using custom recoveries is only possible if your device has boot ramdisk. Installing Magisk through custom recoveries on modern devices is no longer recommended. If you face any issues, please use the Patch Image method.

Fastboot is the recommended method by magisk developers, but fastboot does not work with samsung devices.

On a standard e/os/ installation interact with the bootloader on samsung phones is only possible using odin or heimdall.

Get the boot.img file from the zip file containing the e/os/ build for your phone.

You can grab the zip file containing the right e/os/ build for your phone from

substituting yourphonename with (obviously) the name for your phone you can find on supported devices page. For example my S8+'s name is dream2lte so the builds page is

I'd like to achieve that too. However, I keep running into issues. The problem I'm trying to solve now is that the expected mount points are not available after configuring a new connection. I can use rclone ls to list the contents of a server and that succeeds so I know the connection is working. But there are no mount points under any of these locations:

I have rclone-mount working on two different Android devices now. Both are rooted, of course, but one runs the stock Samsung firmware and the other runs LineageOS. The rclone Magisk module did not work correctly for me on either device. I used Termux:Boot to implement a nice automatic rclone-mount solution on my LineageOS device. On the other device, I had to implement my own simple script.

3a8082e126