How To Root Phone Magisk

[Arridano Tillo]

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:

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.

There are a few different ways to install Magisk. If you're already rooted and you just want access to Magisk modules, you can use Magisk Manager to install the Magisk framework. Or, if you want to pass SafetyNet on a rooted device, you can switch from SuperSU to Magisk SU. But the best way to do it is to start fresh by installing Magisk on a non-rooted phone using TWRP.

The main reason we prefer this method is because it's the cleanest. No need to remove old root binaries, just flash the Magisk ZIP and you'll be good to go. In doing so, you'll actually root your phone and install Magisk in one shot, plus you're far more likely to pass SafetyNet's CTS Profile check this way.

This method works by flashing the Magisk ZIP in TWRP, so you'll need to install the custom recovery before you begin. Much like Magisk itself, there are multiple ways to install TWRP. If you're rooted, you can use this method, but note that you'll have to do a full unroot in SuperSU after you're done.

If your phone does not have a Fastboot interface, the instructions for installing TWRP will vary. We've covered many of these methods in separate tutorials that are linked out in the following guide, so this is a perfect place to start:

Once you've got TWRP installed successfully, boot into Android and install the Magisk Manager app. This isn't the Magisk framework, which provides root access and the ability to install Magisk modules. It's simply an app for downloading and updating the Magisk framework and managing modules.

The Magisk Manager app is no longer available on the Play Store, so you'll need to have "Unknown Sources" enabled to install it. Other than that, just head to the following link, which will show you all available versions of the Magisk Manager app. Download the newest version, then when that's finished, tap the Download complete notification to launch the APK. Finally, press "Install" when prompted.

Next, open the Magisk Manager app. You'll get a popup asking if you'd like to install the Magisk framework. Tap "Install" here, then hit "Download Zip Only" on the subsequent popup. Wait until you see a message at the bottom of the app's main menu stating that the file has been downloaded.

Next, boot your phone into recovery mode, then tap the "Install" button in TWRP's main menu. From there, navigate to your device's Download folder, then select the Magisk ZIP. After that, just swipe the slider at the bottom of the screen to install Magisk, then tap "Reboot System."

Next, go ahead and open the Magisk Manager app. If everything went off without a hitch, you'll see a message towards the top of the screen that says "MAGISKSU (topjohnwu)" with a green check mark next to it. This means your phone is now officially rooted, and since it was done with Magisk, it's a systemless root.

Aside from that, the main advantage of Magisk is that you can have root without tripping SafetyNet. To verify that your phone still passes Google's SafetyNet check, press the corresponding button towards the top of the screen. If you see two extra green check marks after this test is run, you're all set to go!

When I unroot with supersu, I am unable to then boot into twrp (just get the andoid bot with red triangle). Probably because it needs root to boot. I'm stuck......Was able to flash Supersu and twrp from adb and get root back. If you unroot though now, how to you get to twrp recovery?

I'm guessing after I flash TWRP with adb I need to boot to TWRP right away (and flash Magisk) where in this instruction it said to reboot phone. It did not work when I went to boot to TWRP to flash magisk, it did not boot to recovery (darn bot with red triangle). We'll see.

This sounds like you're having problems with permanently installing TWRP. Some new devices require you to temporarily boot off of a TWRP image file (IMG), then use the booted TWRP to permanently flash a separate TWRP ZIP file. You can see if that's required by looking at the install instructions for your device on its TWRP download page (at twrp.me). After doing that, make sure to swipe the slider to allow modifications (make TWRP your permanent recovery... otherwise the stock recovery with the red triangle will take back over after a reboot).

How can this method be used to root the Honor View 10. There was no mention above of having to unlock the Bootloader first?? (surely a prerequisite of any root) And mine is locked, with Huawei not providing codes anymore.. Any ideas please? Tnx

It doesn't look like there's a TWRP release for that model. So you'd have to get a copy of your stock boot image, then patch it in the Magisk Manager app. Then you could flash it in Download Mode with Odin. But definitely look into it some more, that's just the super short version.

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

One of the side effects of switching to LineageOS 17.1 is that a different method for rooting the phone is required. The OS stores its updates at \data\lineageos_updates in the root directory. Since each update is of the order of 0.5 GB, these will eventually take up all of the available free space on the internal storage of the Moto G3. However, the amount of free space can be managed by deleting old updates or moving these onto the micro-SDcard. But, the file cleanup can only take place if the user has root access.reviously, the LineageOS development team released the addonsu software package for rooting the phone. However, in developing LineageOS 17.1, the programmers were unable to port PrivacyGuard to the Android 10 code that forms the basis of the new software. PrivacyGuard had been used by the addonsu software package and its unavailability resulted in addonsu being discontinued. SuperSU, another rooting package I used previously, has not been recommended for use with LineageOS for some time. Consequently, the rooting software of choice at present appears to Magisk.

3a8082e126