How To Root Android Phone Using Magisk

[Katrine Freggiaro]

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 am using Fiddler, and I have to insert a CA Cert to decrypt the SSL certificate coming out of my device. My device running Android 13 is rooted, and when I installed my cert, it went into the user's section (as expected).

There are ways to get around this though - I've written a detail write-up of how Android HTTPS works generally and how to modify this using root here, and the details of some notable very recent related changes in Android 14 here.

If that doesn't work, check if you have a /apex/com.android.conscrypt/cacerts directory. If so, you have the Android 14 version of Conscrypt installed, and there's some extra steps. See the 2nd article above for full details, but in short: you need to use nsenter to add a bind mount for that /system/etc/security/cacerts path into the APEX path for every single running app process on the machine, including the Zygote/Zygote64 processes (which launch new processes in future, who will inherit this setting). That looks like this:

Alternatively, if that's too fiddly to do manually, you can use HTTP Toolkit which is a modern version of Fiddler I've built, that does HTTPS interception too but automates all the setup down to one click. That's all open-source, so if you want to see the full details of how this works so you can automate it yourself just follow the code from here.

Android users have been rooting their phones since the beginning of the operating system, but in recent years it has gotten much more complicated. More recently, a new method for handling root management has emerged, and it's called Magisk.

But starting with Marshmallow, Google essentially blocked the most popular root methods of previous versions---dropping the "su" daemon into the /system partition and running it with the required permissions at startup. This resulted in a new sort of root access, called "systemeless" root, named such because it doesn't modify the /system partition in any way.

As part of this increased security, things like Google SafetyNet have been put in place to keep services like Android Pay secure, which leaves users having to choose between root access and valuable services. It's a bummer.

But that's where Magisk comes in. This is a basically the evolution of root access and management on Android. It leaves SafetyNet untouched, so users are still able to access Android Pay and Netflix, but still allows for powerful root tools like Xposed to continue working. It's truly the best of both worlds.

It's completely open source, under constant development, and getting better every day. Now may be the time to make the switch to this new root solution if you've been concerned about losing things like Android Pay.

First, you're going to need the Magisk file. You can read about all the benefits of Magisk and grab the download by heading over to this thread on XDA. Go ahead and grab the Magisk Manager while you're at it---you'll need it later. Copy both to your phone's internal storage or SD card.

Once the phone boots back up, you'll need to install the Magisk Manager, which you should've downloaded from the above XDA thread. You'll need to have Unknown Sources enabled before you can install this app---jump into Settings > Security > Unknown Sources, click the toggle and accept the warning.

Once installed, fire that bad boy up. It should start up on the status page, where you'll see that you're running the current version and it's properly rooted. You can also perform a SafetyNet check here if you'd like, which I encourage.

The app is very straightforward and easy to understand, especially if you've used a rooted phone before. Here's a quick breakdown of the menu, which you can access by swiping in from the left-hand side of the app:

Most of these are passively enabled (meaning they work in the background), with the exception of Magisk Hide. Once enabled, a new option will show up in the menu---Magisk Hide. This is where you'll tell Magisk which apps to hide its presence (and status) from. Android Pay is selected by default, but you can also choose any other that won't work on a rooted device---like Netflix and Pokmon Go, for example.

If your device doesn't pass the SafetyNet check (as mine didn't at first), apps like Android Pay won't work until you fix this---regardless of Magisk Hide status. If you're using a device with June security patches, you'll need to enable Magisk Core Only mode in Settings (and then reboot) before it will pass SafetyNet. This will disable all Magisk Modules, but all root functionality and BusyBox will still work. If that doesn't fix the issue, check this thread for troubleshooting.

Overall, Magisk is the answer to many of the root questions that users have had since Marshmallow. It's the solution to most (if not all) of the issues rooted users have with modern handsets and services. When set up correctly, Magisk should provide the perfect balance between using Android with all the services you love without sacrificing the root tools you've become accustomed to using.

In this tutorial, we are going to show how one can root an android device by patching the stock boot.img using Magisk Manager. This comes in particularly handy for those on Lollipop and above where one-click-root apks like Kingroot don't work and would therefore require a custom recovery to root. With this method, you won't be needing a one-click-root apk or custom recovery (e.g Philz, CWM, TWRP etc) to root your device.

Stock boot.img for your phone model (its best its for your Build Number / Variant ) . You can extract from the stock rom / firmware of your device (you may check our collection at -89.html ) OR backup from your device using a hardware box e.g Miracle Box, CM2, Nck Box Pro etc

Install MagiskManager apk on your android device Copy the stock boot.img of your device to your phone's internal storage or SD card Launch Magisk Manager app If you're not using the latest version, you'll have to update the app first before proceeding If you intend to patch recovery.img then manually tick "Recovery Mode" in Advanced Settings Select Install > Install > Select and Patch a File > Navigate to the location of the stock boot.img you copied earlier on, then Select it. Note that if you are using a samsung device then you should select the firmware of your device in .tar format instead of boot.img Magisk Manager should begin downloading the magisk zip file used for patching Once download is complete, MagiskManager will automatically patch the file and store it under SDcard/Download/magisk_patched.img[.tar]

You have a variety of options to flash the patched boot.img depending on your chipset (e.g Mediatek MTK, Spreadtrum SPD, Qualcomm QLM etc ), the resources you have and your skills. Note that some flashing methods might require you to rename the file to boot.img For those using MTK devices and have the specific scatter file for their device, you can flash the patched boot.img using SP flash tool or Miracle Box For those using SPD devices and have the PAC file for their device, you can flash the patched boot.img using Research download tool by replacing the stock boot.img with your patched boot.img For those using Qualcomm devices, you can flash patched boot.img using Miracle box custom flasher; see -26213.html For those using Samsung devices and wish to flash patched boot.img.tar using Odin see Generally speaking, you could also use Fastboot to flash the patched_boot.img or boot.img (if you've renamed then the command must reflect the file name) as outlined below

3a8082e126