How to Switch from Magisk to KernelSU

In this guide, we will show you the steps to make a switch from Magisk to KernelSU. Initially, we had the SuperUser app for gaining administrative privileges which has its glory days for quite a length time frame before being ultimately replaced by Magisk. People chose the latter over the former due to the fact that it carried out all the tweaks systemlessly [and only due to its slew of additional goodies such as the modules repository, Magisk Hide, etc].

But now, the landscape is slowly changing once again, this time mainly due to the caveats associated with rooting. Confused? let me explain. The thing is nowadays when you root your device, there are a slew of drawbacks that you have to face, with the Play Integrity failure being the top-most problem.

New A13+ Play Integrity Check - 1

The direct consequence of the same is the inability of the banking and payment app to function along the expected lines. Making matters worse is the fact that in some cases, even passing this test does no good for these apps. This is because most of these apps now do extensive and stringent Magisk checks on your device. But that’s just about it.

They only check for Magisk and not for any other rooting alternative apps like KernelSU or APatch! Therefore, to make the most of this opportunity, many users are now making a switch from Magisk over to KernelSU. If you are also planning to do the same, then this guide will help you out. Follow along for the steps.

How to Switch from Magisk to KernelSU

YouTube video - 2

Before starting, please take a backup of all the data on your device, just to be on the safer side. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps. NOTE: We are opting for the LKM rooting method for KernelSU as it will be universally applicable across all Android devices. If you instead wish to go with the GKI approach, then do have a look at our detailed guide on the said topic.

  1. First off, launch Magisk, and remove all the modules.
  2. Then tap on Uninstall Magisk > Complete Uninstall.
  3. Next up download the stock firmware for your device. Make sure to download the same version which is installed on your device. You can verify the same by having a look at Build Number/Version Number.
  4. Then extract the firmware and get the boot/init_boot . Use boot.img if your device came with Android 12 or older version out of the box, else use init_boot.img. For extracting Xiaomi’s Fastboot ROM and Pixel’s Factory Image, use 7ZIP, for OnePlus- use the Fastboot Enhance Tool .
  5. Next up, transfer the boot/init_boot file to the device.
  6. Once done, now download & install the KernelSU app .
  7. Then launch it and tap on Not Installed > Select a file.
  8. Choose the boot/init_boot > Next > it will be patched.
  9. The patched file will be placed in the Downloads folder.
  10. Now download & extract Android SDK Platform Tools .
  11. Next up, transfer this patched file to the platform tools.
  12. Now enable USB Debugging & connect the device to PC.
  13. Open CMD inside the platform-tools folder and type in: adb reboot bootloader
  14. Your device will now boot to the Fastboot Mode [drivers].
  15. Now type the below command to flash the boot/init_boot fastboot flash boot patched_boot.img fastboot flash init_boot patched_init_boot.img Reference Image
  16. Then use the below command to boot to the OS fastboot reboot
  17. Now launch the KernelSU app and verify the result.

That’s it. You have now successfully made a switch from Magisk to KernelSU. With that said, there are just a couple of things worth keeping in mind:

  • As opposed to Magisk, there’s no built-in Zygisk in KernelSU. So you’ll have to flash the ZygiskNext module to enable it in KernelSU.

  • Likewise, when you are rooted vi Magisk and launch a root-supported app, you get the SuperUser request, taping on Grant will give the app the required root access. However, things work a little bit differently here. In the case of KernelSU, you won’t get any SuperUser prompt, instead, you’ll have to grant root access to the required apps from within the KernelSU’s SuperUser tab [select the app and enable SuperUser].

  • How to Hide Root via KernelSU on Rooted Android

  • Rooting via Magisk/KernelSU/APatch: Boot or Init Boot

  • How to Enable Zygisk in KernelSU and APatch

  • How to Give SuperUser Root Access to Apps via KernelSU

Google preferred - 3 Google preferred - 4

(Cancel Reply)

Δ

How to Enable Zygisk in KernelSU and APatch

In this guide, we will show you the steps to enable Zygisk in KernelSU and APatch. Back in the day, we had the ever-so-popular SuperSU by Chainfire for gaining administrative access to our device. After its demise, many shady one-click root solutions tried to fill its place and thankfully failed. This is when John Wu stepped in and revolutionized the rooting domain with its offering in the form of Magisk [ironically, he now works in Google in the Android Platform Security team, though it has no major impact on the app].

One of the biggest perks of this app is the fact that it carries out its task systemlessly, i.e. interacting with the system partition of your device, something that cannot be said with its successor. Apart from that, the entire rooting process is a breeze. Not to mention the fact that it allows a one-tap easy flashing of the modules of your choice [initially, it even used to house all the modules within the app itself, though that section has now been removed].

magisk app - 5

Magisk App in action

While Magisk is still being used by many for rooting purposes, we are also seeing the introduction of a couple of other players in this domain, with KernelSU and APatch being the two most noticeable names. But instead of taking the help of the boot partition, they tend to take the kernel route. Apart from that, there are a slew of other differences between Magisk and KernelSU & APatch, one among which is the ability to enable Zygisk.

For the unaware, Zygisk allows the developers to run their code directly in the app’s process even before it [the process] starts.

In the case of the former, you can easily enable it from its Settings menu but that is not the case with the latter two. Infact Zygisk seems to be altogether absent from both these apps. So if that is the case then how could one enable it in the first place? In this guide, we will make you aware of just that. So without any further ado, let’s check it out.

  • What is the Need to Enable Zygisk?
  • How to Enable Zygisk in Magisk, KernelSU, and APatch Magisk KernelSU APatch

What is the Need to Enable Zygisk?

While you will still be able to root your device even if you don’t enable Zygisk, however, there are many crucial tasks that will fail if this is not enabled. For instance, Play Integrity Fix is one of the most important modules for any rooted user as it allows you to pass the Basic and Device Integrity , in other words, allows you to use banking and payment apps.

why enable zygisk - 6

However, you will not be able to use any banking and payment apps [and nowadays, even the likes of MacDonalds and Uber] if you don’t enable Zygisk. So owning to these factors, it is of paramount importance that you enable it on your device. And in this guide, we will show you how to do just that. Follow along.

How to Enable Zygisk in Magisk, KernelSU, and APatch

enable zygisk apatch kernelsu - 7 enable zygisk apatch kernelsu - 8

Before starting, please take a backup of all the data on your device, just to be on the safer side. Droidwin and its members wouldn’t be held responsible in case of a thermonuclear war, your alarm doesn’t wake you up, or if anything happens to your device and data by performing the below steps.

Magisk

As already mentioned before, Magisk comes built-in with Zygisk, so you can directly enable it from within the app itself. Here’s how”

  1. Launch the Magisk app and tap on the Settings icon at the top right.
  2. Then enable the toggle next to Zygisk and restart your device once.
  3. Your device will now reboot and the Zygisk should now be enabled.
  4. To verify the same, refer to the value next to Zygisk, it should state Yes.

KernelSU

YouTube video - 9 YouTube video - 10

When it comes to KernelSU, there’s no built-in option to enable AZygisk. So you’ll have to take the help of an open-source module to get the job done. Here’s how it could be done:

  1. irst off, download the Zygisk Next module from its GitHub page.
  2. Then launch KernelSU, go to Modules, and hit the Install button.
  3. Select the Zygisk Next module and it will be flashed on your device.

APatch

Similar to KernelSU, APatch also does not have Zygisk built into its app. So, as before, you’ll have to take the help of an open-source module to enable it. Follow along with the steps:

  1. First off, download the Zygisk Next module from its GitHub page.
  2. Then launch APatch, go to Modules, and tap on the Load button.
  3. Select the Zygisk Next module and it will be flashed on your device.
  • How to Root Android Devices via KernelSU [GKI and LKM]
  • Root Android via APatch: Give SU Access Flash Module Install OTA
  • How to pass Meets Device and Basic Integrity via Play Integrity Fix
  • List of custom fingerprints/JSON/build prop that pass Play Integrity
Google preferred - 11 Google preferred - 12

(Cancel Reply)

Δ