In this guide, we will make you aware whether you need to use the boot or the init boot file when it comes to rooting via Magisk, KernelSU, and APatch. Gaining administrative access by rooting the device has forever been the tech enthusiast’s favorite tweak. And why not? After all, when it gives you the ability to flash modules, customize the firmware, flash a custom kernel, and welcome abode a plentitude of tweaks, then what else can one ask for?
Moreover, when it comes to rooting, there are quite a few ways through which you can get this job done, with Magisk being the most popular among all of them. However, that isn’t the only one out there as there have been a few newcomers in this domain as well, namely KernelSU and APatch. On the one hand, it translates to the fact that you now have multiple options at hand, however, at the same time, it is resulting in some confusion among the newcomers.
In this regard, one of the most common queries is whether one has to patch the boot or the init boot file while rooting the device via Magisk, kernelSU, and APatch. If you are also scratching your hands searching for an answer to this query, then this guide will help you out. Follow along on this journey.
Table of Contents
Rooting via Magisk/KernelSU/APatch: Boot or Init Boot?
Let’s break down this guide into three separate sections, one for each app, for ease of understanding.
Magisk: Boot or Init Boot?
If your device came with Android 12 or older versions out of the box, then you have to use the boot.img file for rooting. On the other hand, if it comes with Android 13 or higher versions, then you’ll have to use the init boot file.
NOTE: There are a few exceptions to this rule, with the likes of Poco F5 and Nothing Phone 2 being launched with Android 13 but still using the boot.img for rooting.
KernelSU: Boot or Init Boot?
KernelSU provides two methods of rooting an Android Device: via Generic Kernel Image and using a Loadable Kernel Module. It is highly recommended that you opt for the LKM method. The LKM method follows the same rule as Magisk- use boot.img for devices launched with Android 12 or older OS versions and init boot for devices with Android 13 or higher versions [with Poco F5 and Phone2 being the two exceptions as before]. On the other hand, if you plan to root via GKI, then you’ll have to use the boot.img file for rooting.
APatch: Boot or Init Boot?
In the case of APatch, you’ll have to use the boot.img for rooting, irrespective of the OS build your device initially came with.
That’s it. This was all from this guide on whether you need to use boot or init boot while rooting your device. If you have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution as soon as possible.
