This guide will walk you through the steps to resolve boot loops after flashing the Magisk patched init_boot file. The way we used to root our devices has changed dramatically since Android 13. You had to patch and flash the boot. img to the boot partition until the twelfth iteration. However, init_boot has since taken its place. As a result, you must now patch and flash the init_boot to its init_boot slot. However, there is a catch, or rather two catches.
To begin with, some devices still ship with Android 13 but use the boot.img rather than the init_boot. To make matters worse, some users have reported having to flash the file in FastbootD Mode rather than Fastboot/Bootloader Mode. Overall, things appear to be quite complicated in this domain. But don’t worry, if your device gets stuck in a bootloop, you can easily fix it by flashing the Magisk patched init_boot file.
Fix Bootloop after Flashing Magisk Patched init_boot
It is recommended that you try each of the workarounds listed below and see which one works best for you. So, with that in mind, let us begin.
1: Force Restart
While rooting, it is always recommended that you boot your device through a patched init_boot before flashing it. This is because, in the cases we are currently dealing with, a simple reboot will resolve the bootloop issue. Because you used the fastboot boot command, your device will only boot temporarily with a patched init_boot. The patched init_boot will be replaced by the stock init_boot the next time you reboot it, and the problem will be resolved.
Long-press the power icon to perform a hard reboot, and then examine the results. Or, as soon as your device shuts down [which may take 1-2 seconds if it’s in a bootloop], press and hold the hardware key combination for your device to enter Fastboot Mode, and then use the fastboot reboot command to boot to the operating system.
2: If you Flashed the Magisk Patched Boot
If you had previously irrevocably flashed the modified init_boot using the fastboot flash command, you must now flash the original init_boot.img file. Here’s how it could be accomplished:
- You can get the stock init_boot.img file from the stock software for your device.
- Then, get the Android SDK Platform Tools and extract them to your PC.
- Then, put the stock boot.img file inside the platform tools folder.
Now, use a hardware key combination to force your device to restart into Fastboot Mode.
- Next, open the platform-tools folder’s Command Prompt.
Now, update both slots with the original init_boot.img file:
fastboot flash init_boot_a boot.img fastboot flash init_boot_b boot.img
- Finally, type the following command to begin the OS boot process:
- After flashing the Magisk patched init_boot file, you should check to see if it cures the bootloop.
3: Flash Stock Firmware
In certain circumstances, an improper root process may also corrupt the remainder of the partitions, with the exception of the init_boot partition. However, because it could take a very long time to determine which partition was damaged, your best choice is to use the Fastboot commands to reinstall the whole original firmware on your device. This will flash all of the files to the partitions where they belong, which should, in turn, fix the bootloop issue. You might find it helpful to consult one of the guides mentioned below, depending on the type of device you have:
- Download MSM Download Tool: Unbrick any OnePlus Device
- How to Unbrick any Xiaomi/Redmi/Poco via Mi Flash Tool
- How to Flash Firmware on Pixel via Android Flash Tool
- Samsung Firmware Flash Guide –
- Motorola Stock Firmware With RSD Lite Tool
- Motorola Phones Firmware Using mFastboot
- Stock ROM With QcomDloader Tool
- SPreadtrum Smart Phones Flashing
- Stock Rom QPST 2.7.422 With QFIL
- MediaTek Stock ROMs Flash Using SP Flash Tool