How To Root Android Phone With Magisk

[Nayme Cutforth]

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.

The Pixel 3a came out of nowhere and flexed its muscles to show the industry that you can have a great phone without a hefty price tag. Since Pixel smartphones are first-party devices straight from Google, you can be sure you'll have root access one way or another. For right now the method used to get your Pixel 3a rooted will take a few steps, but they go by real quick.

Rooting your phone with Magisk opens up the world of mods like never before with a variety of benefits. One of the best things to come from Magisk is the ability to keep Google's SafetyNet flag from being tripped, which could stop you from using certain apps. With the platform continually evolving and getting better all the time, now's the perfect time to get started.

Of course, before you can get started with modding your Pixel 3a or rooting with Magisk, you'll need to unlock your bootloader. If you haven't done so yet, visit the guide below and get your bootloader taken care of before moving on with this guide.

There are two methods for rooting your Pixel 3a, and you can pick whichever one works better for you. The easiest and most beneficial of the two is done through the custom recovery environment via TWRP, which is the one most people will use for ease of access. The manual method is for when a device doesn't have TWRP support or for someone who prefers the old fashioned install process.

Using TWRP is the method that works best since it was created to make our lives easier in the first place by reducing the overall steps required for gaining root access. If you'd rather not waste any extra time with unnecessary manual steps, using a custom recovery to gain full root access is the way for you without a doubt. It doesn't get any easier than this!

Once your bootloader is unlocked, you need to grab the image file required to boot your Pixel 3a into TWRP. As mentioned previously, the benefits of installing Magisk on your system via TWRP provides the quickest route for gaining full root access. Having a custom recovery also means you can then install any ZIP file you want without having to rely on a computer when installed permanently.

The next thing you need to do is install the Magisk framework and the Magisk Manager app onto your system via a single ZIP file. This file will be installed within TWRP, and will patch your system to grant you full root access while passing Google's SafetyNet checks. Download the file below and place it in the "Download" folder on your phone's storage.

Now you need to boot your phone into Fastboot Mode so that you can access the TWRP recovery menu. There are other ways of booting into TWRP, but the universal method will always be to boot into your device's native Fastboot Mode via the power down method. If you're unfamiliar with the process or need a refresher, you can hit the link below and complete the step real quick before moving on.

Once you're in Fastboot Mode, navigate the menu with the up and down volume keys to make your selection. After you highlight "Recovery Mode" tap the power button to confirm the action. The device will immediately boot right into the TWRP main menu if all went well.

At this point, you should be sitting at the main screen of TWRP and ready to install Magisk onto your phone. From the main menu, tap "Install" then navigate to the "Download" folder where you stored the Magisk ZIP file. Once you have located the Magisk file, tap it once, then initiate the "Swipe to confirm Flash" slider to begin installing it.

The Magisk framework will automatically start doing its thing and will patch the boot image on your system partition. This means your phone will have full root access and still pass Google's SafetyNet, as mentioned previously. Once Magisk is finished installing on your system, tap the "Reboot System" option to boot back into Android.

Last but not least, after your phone reboots, head back into the Magisk Manager app. You'll want to then make sure you have both green check marks for "Latest Version" and "Installed Version." You'd also want to tap the arrow next to "Tap to start SafetyNet check" to ensure you pass Google's SafetyNet check. All set! Enjoy root access on your Pixel 3a.

Once you have your bootloader unlocked and ready to go, you'll then need to download the factory image for your specific device model. Head to a computer for this part to keep things simple. Click the download link below for the newest version for either your Pixel 3a or 3a XL. You'll have to scroll down past the flashing instructions section to find where the downloads section starts.

After the entire factory firmware package has been downloaded onto your computer, extract the folder to any location of your choosing. Once extracted the first time, look for the only ZIP file in the folder that starts with "image" and then extract that file within the current folder to reveal all the system files.

The file is not very large, so the download should be rather quick, but when it's finished, tap the "OK" button followed by "Open." If you are prompted to do so, you'll need to grant Chrome the proper permissions to sideload the Magisk Manager app. Simply tap "Settings," then enable the switch for the "Allow from this source" option. Tap the back button once, and then you can tap "Install."

From the main menu of the Magisk Manager app, tap "Install" then tap "Install" again to bring up a new set of options. Choose the "Select and Patch a File" option and then allow the media permissions when prompted to do so by tapping "Allow."

From the file manager that pops up, tap the menu icon in the upper left of the screen, then select "Downloads." Select the "boot.img" file, then Magisk will begin patching it within about a minute or so. Once it finishes patching the file, go ahead and tap the back arrow to complete the process.

Now that you've got the patched "boot.img" file that you need to gain root access, you'll need to use a quick command to send the file over to your phone on a system level. You'll need to download Google's SDK Platform-Tools standalone package, which will give you everything you need without complicating things.

Now you'll need to transfer the patched boot image that you got from Magisk in Step 5 to the platform-tools folder on your computer. It should be named "magisk_patched.img" and will be located within the same "Download" folder that your original file was in. Transfer that file and the original "boot.img" file to your platform-tools folder for safekeeping in case you should need it again.

3a8082e126