How to Patch boot.img Using Magisk: The Complete Step by Step Guide for 2026
The most thorough guide available for patching your boot.img with Magisk in 2026. Every step is explained clearly, including what each step actually does under the hood, the exact files you need, and the most common errors people never talk about along with how to fix them.
What Is boot.img and Why Does Magisk Need It
boot.img is the partition image on your Android device that contains the Linux kernel and the ramdisk. Magisk patches this image to inject its own init process into the boot sequence, allowing it to gain root access at the very start of the system startup without permanently altering the system partition. This is what makes Magisk so powerful and what sets it apart from older rooting methods.
Every Android device ships with a boot partition. This partition is loaded by the bootloader before Android itself starts. When Magisk patches your boot.img, it inserts a small set of files into the ramdisk and modifies the init startup sequence so that Magisk launches before the rest of Android. By the time your home screen appears, Magisk has already set up its environment and is ready to grant root access to apps that request it.
The reason Magisk patches boot.img rather than modifying system files directly is called systemless root. System partitions on modern Android devices are mounted read only, verified by Android Verified Boot, and protected by SafetyNet and its successor Play Integrity. Magisk sidesteps all of this by working entirely within the boot partition and never touching /system at all. This is the technical foundation behind why Magisk can pass integrity checks that older root methods could never survive.
Understanding this process before you begin will make every subsequent step much clearer. You are not blindly running commands. You are modifying a specific partition image, flashing it back to the correct slot on your device, and letting Magisk take care of everything else from there.
What You Need Before You Start
Getting the right tools and files in place before you begin is one of the most important things this guide can tell you. Attempting to patch boot.img without the correct prerequisites is the single biggest reason people end up with a bricked device or a failed root attempt.
- An unlocked bootloader on your Android device. Magisk cannot be flashed to a locked bootloader. If yours is still locked, unlock it first through your device manufacturer’s official process before doing anything else in this guide
- The exact stock firmware package for your specific device model and region. This is where you will extract the correct boot.img. Using a firmware from the wrong region or wrong build number will produce a patched image that does not match your device and will fail to boot
- The latest version of the Magisk APK downloaded directly from the official Magisk GitHub releases page. Install it on your device before proceeding
- ADB and Fastboot installed and working on your computer. Test them by connecting your device and running adb devices to confirm your device is recognized before you need them for flashing
- A USB cable that reliably transfers data. Charge only cables will cause fastboot to fail silently in ways that are very confusing to diagnose
- At least 70 percent battery charge on your device. The patching and flashing process should not be interrupted by a shutdown
Important: Back up everything on your device before you begin. An unlocked bootloader means fastboot wipe commands will work without confirmation. A single typo in a fastboot command can erase your data. This is not meant to scare you away from the process. It is meant to make sure you start with a backup so that even a worst case scenario is recoverable.
How to Get the Correct boot.img for Your Device
This step is where most guides give vague advice that leaves people confused. Here is exactly what you need to do to get the correct boot.img file every time.
Finding Your Exact Firmware Build
Go to your device settings, navigate to About Phone, and note your exact build number. It will look something like a string of letters, numbers, and dots that identifies the precise software version running on your device. This exact build number is what you need to match when downloading firmware.
Download the full factory image or OTA package for your device from your manufacturer’s official firmware download page, a trusted mirror such as Google’s own factory images repository for Pixel devices, or the firmware database appropriate for your brand. Never use unofficial firmware sources for this step because a modified firmware defeats the entire purpose of starting from a known good state.
Extracting boot.img from the Firmware Package
Most firmware packages are distributed as zip files. Open the zip and look inside. For Pixel devices you will find a file called image-devicename-buildnumber.zip nested inside the outer zip. Open that inner zip and you will find boot.img directly. For Samsung devices the firmware is distributed as a combination of files including one labeled with AP at the start of the filename. That AP file contains the boot image inside it and needs to be extracted using a tool like 7-Zip. The file inside is often named boot.img.lz4 and needs to be decompressed before use.
| Device Brand | Firmware Format | Where to Find boot.img | Special Notes |
|---|---|---|---|
| Google Pixel | Factory image zip containing inner image zip | Directly inside the inner image zip as boot.img | Easiest extraction process. Match build number exactly |
| Samsung | Multi part AP BL CP CSC files | Inside the AP file as boot.img.lz4 | Decompress lz4 before patching. Use 7-Zip or lz4 command line tool |
| Xiaomi / Redmi | Fastboot ROM zip | Inside images folder as boot.img | Use Fastboot ROM not Recovery ROM for this process |
| OnePlus | OxygenOS zip or payload.bin | Extract from payload.bin using payload dumper tool | payload.bin extraction adds one extra step but is straightforward |
| Motorola | Factory zip with images folder | Directly inside the images subfolder | Verify correct boot.img for your slot if device uses A/B partitions |
Step by Step: Patching boot.img Using the Magisk App
This is the core of the entire process. The Magisk app handles the actual patching. Your job is to give it the correct file and transfer the result back to your computer.
-
1Transfer boot.img to Your Device Copy the boot.img file you extracted in the previous section to your device’s internal storage. The Downloads folder is a reliable choice because it is easy to navigate to from within the Magisk app file picker. Use a USB cable and MTP mode or any file transfer method you prefer. Confirm the file is present on your device before continuing.
-
2Open the Magisk App and Select Install Launch the Magisk app on your device. You will see a card at the top labeled Magisk with an Install button. Tap that Install button. A dialog will appear with several options. Select the option labeled “Select and Patch a File” rather than the direct install options. This is the correct path for patching a stock boot.img file.
-
3Navigate to Your boot.img File The app will open a file picker. Navigate to the Downloads folder or wherever you saved your boot.img file. Tap the file to select it. The Magisk app will display the file name in its interface confirming your selection. Double check that the filename matches exactly what you extracted from your firmware package.
-
4Run the Patching Process Tap the “Let’s Go” button. The Magisk app will begin patching your boot.img. You will see a log appear in the app showing each step of the patching process as it happens. This typically takes between 30 seconds and two minutes depending on your device’s processing speed. Do not navigate away from the app or lock your screen during this process.
-
5Confirm the Output File When patching is complete the Magisk app will display a message indicating success and show you the path to the output file. The patched file will be saved in your Downloads folder with a name like magisk_patched_XXXXX.img where XXXXX is a random string of characters. Make a note of this exact filename.
-
6Transfer the Patched File Back to Your Computer Connect your device to your computer via USB. Copy the magisk_patched file from your device’s Downloads folder to a convenient location on your computer such as your desktop. This is the file you will flash in the next section. Keep the original unpatched boot.img as well in case you need to restore it.
What Magisk Actually Does During Patching
When you tap Let’s Go the Magisk app unpacks your boot.img, decompresses the ramdisk, injects the magiskinit binary and its configuration, adds the Magisk overlay directory structure, and rebuilds and recompresses the ramdisk. It then reassembles the boot image with the modified ramdisk in place of the original. The result is a boot image that is byte for byte identical to your stock image in every way except for the ramdisk, which now contains everything Magisk needs to initialize itself before Android starts. This is the technical reason why Magisk root survives OTA updates that do not change the boot partition format and why it can be cleanly uninstalled by simply reflashing the original stock boot.img.
How to Flash the Patched boot.img via Fastboot
With the patched image on your computer you are ready to flash it. This section covers the exact commands needed and explains the slot system that trips up many users on A/B partition devices.
Boot Into Fastboot Mode
Power off your device completely. Hold the volume down button and the power button simultaneously until the bootloader or fastboot screen appears. The exact button combination varies slightly by manufacturer but volume down plus power works for the majority of devices. Alternatively you can reboot into fastboot from ADB by running the command below while your device is connected and ADB authorized.
adb reboot bootloader
Flash the Patched Image
Once your device is in fastboot mode and visible to your computer, navigate in your terminal or command prompt to the folder where you saved the patched image file. Run the following command, replacing the filename with your actual patched image filename.
fastboot flash boot magisk_patched_XXXXX.img
A/B Slot Devices: The Detail Most Guides Skip
If your device uses an A/B partition scheme, which includes most modern devices released after 2017, you need to understand that your device has two complete sets of partitions called slot A and slot B. When you flash with the command above it flashes to the currently active slot. After flashing, reboot and check which slot is now active. In some cases you may want to flash to both slots to ensure that your patched boot image is present regardless of which slot the system switches to during an OTA update.
fastboot flash boot_a magisk_patched_XXXXX.img
fastboot flash boot_b magisk_patched_XXXXX.img
After flashing, reboot your device using the command below or by selecting the restart option from the bootloader menu.
fastboot reboot
How to Verify Root Access After Flashing
Your device should boot normally after flashing the patched image. The first boot after a Magisk flash typically takes slightly longer than normal because Magisk is completing its setup process in the background. This is expected and not a sign of a problem.
Check the Magisk App
Open the Magisk app after your device finishes booting. If the installation was successful the app will display the installed Magisk version and the current Magisk version as matching numbers. A mismatch here usually means the app needs to update itself, which it will prompt you to do automatically.
Test with a Root App
Install an app that requests root access such as a terminal emulator or a root checker application. Grant the root request when it appears. If root access is granted successfully you will see confirmation in the app. This is the clearest real world confirmation that Magisk is working correctly.
Check Play Integrity
Open the Magisk app and run the Safety Net or Play Integrity check from within the app’s settings. A properly configured Magisk installation on a device without other modifications will typically pass at least the basic integrity check. Advanced passing requires additional Magisk configuration but basic passing confirms the core installation is clean.
Advanced: Patching boot.img Without a Working Device
There is a scenario that most guides never address. What if your device does not boot, or you want to prepare a patched boot image before you even set up a new device? Magisk supports this through a command line patching method that runs entirely on your computer.
This method requires a Linux environment, either a native Linux install, WSL on Windows, or a Linux virtual machine. You also need the Magisk zip file downloaded from the GitHub releases page, not the APK but the zip version which contains the patching scripts and binaries directly.
unzip Magisk-v27.0.zip -d magisk-tools
Inside the extracted folder you will find architecture specific binaries. For most modern 64 bit Android devices you want the arm64 v8a version of magiskboot. This binary is the same tool the Magisk app uses internally when you patch through the app interface. Running it directly gives you complete control over the patching process and allows you to patch boot images for devices you do not have in front of you.
KEEPFORCEENCRYPT=true KEEPVERITY=true ./magiskboot patch boot.img
The KEEPVERITY and KEEPFORCEENCRYPT flags tell magiskboot to preserve dm-verity and forced encryption settings from the original image. For most devices you want both set to true so that the patched image does not disable features your device depends on for its security model. The output will be a file named new-boot.img in the same directory which you then flash exactly as described in the fastboot section above.
Common Errors and How to Fix Them
These are the errors that actually appear during the boot.img patching process and that are rarely covered in detail anywhere else.
| Error or Symptom | What Is Actually Happening | How to Fix It |
|---|---|---|
| Device stuck on boot animation after flashing | The patched image does not match the running firmware. Build number mismatch between the firmware you extracted boot.img from and what is installed on your device | Reboot to fastboot and reflash the original stock boot.img to recover. Then redownload firmware matching your exact build number and repeat the process |
| Fastboot says “FAILED (remote: ‘partition not found’)” | You are using the wrong partition name for your device. Some devices use “boot” and others use “boot_a” or a vendor specific name | Run fastboot getvar all and look for partition information in the output. Use the correct partition name for your specific device |
| Magisk app shows version as N/A after reboot | The flash completed but Magisk did not initialize correctly. This often happens when the patched image was built for a different architecture than what your device uses | Confirm you are running Magisk version 26 or higher. Older versions have known initialization failures on newer devices. Download the latest release and repeat patching |
| Patching log shows “unsupported magic” error | The boot.img you gave Magisk is compressed in a format magiskboot does not recognize, or it is not actually a boot image at all | For Samsung devices decompress the lz4 file first. For devices with payload.bin make sure you have extracted correctly using payload-dumper-go before attempting to patch |
| Device boots but root requests are all denied | The Magisk app is installed but the boot image is not actually patched or flashed correctly. Root app and daemon are not running | Open Magisk and check if it shows an installed version. If not, repeat the flash process and ensure fastboot output showed OKAY rather than FAILED during the flash command |
| Fastboot command not found on computer | Platform tools are not installed or not added to your system PATH | Download the latest platform tools from the Android developer website and either run fastboot directly from that folder or add the folder to your system PATH variable |
Frequently Asked Questions
These are the real questions people ask after going through the patching process for the first time.
You Now Have Everything You Need to Patch boot.img with Magisk
This guide has walked you through every stage of the process: understanding what boot.img is, extracting the correct file, patching it with the Magisk app, flashing it via fastboot, verifying root, and handling any errors that appear along the way. Visit magisk.com.co for more Magisk guides, module recommendations, and the latest updates on Android rooting in 2026.
