In this guide, we will show you the steps to fix the Patch Failed No New Boot.img Detected error in the APatch app. There exist quite a few ways through which you can gain administrative access or in other words, root your device and there are no brownie points in guessing that the most popular among them is the offering from John Wu- Magisk.
You can easily patch the boot or the init_boot.img file and then flash it via Fastboot to gain elevated-level permissions on your device. However, recently with Google tightening the screws with the likes of Play Integrity and SafetyNet, it is becoming somewhat challenging to completely hide the Magisk app and its associated binary from the device.
While there do exist options like Magisk Hide which renames the app package name and modules like Play Integrity Fix which spoofs the device’s fingerprint and lets you pass Basic and Device Integrity, however, some banking and payment apps still manage to find out that the Magisk app is installed on the device.
To circumvent that, users have started looking for alternatives and two of the most perfect ones in this regard are KernelSU and APatch. Both of them work in kernel mode and grant root privileges to user space apps directly in kernel space.
While we have already covered how this module works and all its associated functionalities in this detailed guide, however, some users are unable to checkmark even the first requirement off the list that involves patching the stock boot.img file. If you are also in the same boat, then fret not. In this guide, we will show you the steps to address this issue once and for all. So without any further ado, let’s get started.
Fix APatch Patch Failed No New Boot.img Detected
Before starting, please take a backup of all the data on your device. TheDroidwin 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.
FIX 1: Try a Different Device
As obvious as it might sound, in some cases, the issue might appear due to less RAM on a device. Therefore, switch to a more powerful device, install APatch, then try patching the boot.img, and check out the result.
FIX 2: Unpack and Repack Boot.img
Your next course of action involves a three-step process: Unpack boot.img > Patch kernel image > Repack Boot.img. Here’s how it can be carried out:
- To begin with, download
kptools-win.zip,kpimg-androidandmagiskbootfrom below.DOWNLOAD LINK
- Now extract all these three files inside the same folder.
- Then open Command Prompt inside that folder and type in the below command:
magiskboot.exe unpack boot.img
- This will unpack the
boot.imgand give you the kernel file. Rename it to kernel-b. - Now type in the below command in the CMD window to patch this kernel file:
kptools-x86_64-win.exe -p --image kernel-b --skey "YourKey" --kpimg kpimg-android --out kernel
- Finally, type in the below command to repack the boot.img:
magiskboot.exe repack boot.img
- You’ll get a new patched image named new-boot.img.
- You could now either temporarily boot your device to it or permanently flash it via Fastboot, or flash it via TWRP, as explained below
Temporary Boot: fastboot boot new-boot.img Permanent Flashing: fastboot flash boot new-boot.img TWRP: Go to Install > Tap on Install Image > Select new-boot.img > Right swipe to flash it > Reboot > System
So these were the steps to fix the Patch Failed No New Boot.img Detected error in the APatch app. If you still have any queries concerning the aforementioned steps, do let us know in the comments. We will get back to you with a solution at the earliest.
