Home > Root

Signature verification failed: How to Sideload Magisk & Root [Video]

In this guide, we will show you the steps to fix the Signature verification failed error when sideloading Magisk and rooting your device. Most custom ROMs nowadays come with their own built-in recovery as well. However, as opposed to TWRP, these recoveries don’t have the option to install/flash any file, instead, you’ll have to perform an ADB Sideload.

So for example, if you want to root your custom ROM, then you just need to sideload the Magisk ZIP. But since Magisk hasn’t been officially signed by that ROM developer, you might get the Signature Verification Failed message. Alongside that, you’ll have the option to proceed ahead and install that file or skip it. However, this option isn’t present across all the custom recoveries, some of them will blatantly refuse to flash the file.

It will straightaway give out the aforementioned error message but wouldn’t give you any option to proceed ahead with the installation. So what could be done in such instances? Well, even if you are getting a Signature verification failed error when sideloading Magisk, you could still root your device via two nifty methods. And in this guide, we will make you aware of both these methods. Follow along.

Signature verification failed: How to Sideload Magisk & Root?

You could take two different approaches to get this job done. First off, you could temporarily boot to TWRP for one-time usage and flash the Magisk ZIP. This is the shorter of the methods and is quite easy to carry out. Unfortunately, TWRP might not be available for every device. In such cases, you will then have to opt for the longer route of extracting ROM’s payload.bin, getting the boot.img, patching it via Magisk, and flashing it via Fastboot.

We have explained both these methods below. You may refer to the one that is in sync with your requirement. 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.

Method 1: Via TWRP

  1. To begin with, download TWRP Recovery for your device.
  2. After that, download the latest Magisk.apk on your device.
  3. Then download and extract Android SDK Platform Tools.Fix OnePlus Fingerprint issues without Persist
  4. Now place the twrp.img file inside this platform-tools folder.
  5. Then enable USB Debugging and connect your device to your PC.magisk Signature verification failed
  6. Now launch CMD inside this folder and execute the below command
    adb reboot bootloader

    magisk Signature verification failed

  7. Your device will now boot to Fastboot Mode. So type in the below command:
    fastboot boot twrp.img

    magisk Signature verification failed

  8. Your device will boot to TWRP. Go to Install, select the Magisk APK and flash it.magisk Signature verification failed
  9. Once done, go to Reboot and select System. Your device will now boot to the OS.
  10. Now install the Magisk APK. Then launch it and tap OK in the additional setup prompt.magisk Signature verification failed
  11. Now select Direct Install > Let Go. Magisk will be flashed. Once done, tap Reboot.magisk Signature verification failed
  12. Your device will now boot to the rooted OS and your task stands complete. That’s it.

These were the steps to fix the Signature verification failed error when sideloading Magisk and rooting your device. Let’s now make you aware of the second method to get this job done.

Method 2: Via Payload Extraction

In this method, you’ll have to extract the payload.bin fil via Fastboot Enhance, get the stock boot.img, patch it via Magisk, then temporarily boot your device via this patched boot, and finally select Direct Install for permanent root. We have explained all this in detail in the linked guide below, do check it out:

How to Root any Custom ROM via Magisk [Video]

That’s it. These were the two different methods that should help you fix the Signature verification failed error when sideloading Magisk and 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 at the earliest.


Share: