In this guide, we will show you various methods to fix the fastboot: error: boot partition is smaller than boot image. Once you unlock the device’s bootloader and step into the custom development, there are a plethora of tweaks to try out. From flashing custom ROMs to installing a custom recovery like TWRP, there’s a lot to try out. Along the same lines, you could also gain administrative privileges by rooting your device via Magisk.
This will then make it possible for you to flash tons of mods including the likes of Magisk Modules, Xposed Framework, Substratum Themes, etc. However, when users are trying to root their device by flashing the Magisk patched boot.img or simply trying to flash the stock boot.img to fix the corrupt boot partition, they aren’t able to do so. This is because the boot partition is simply refusing to accept that boot.img file.
In hindsight, it might look due to the size of the file being larger than the partition itself. But as strange as it may sound, in most instances, that is not the reason for this issue. Rather it has to do with the incorrect commands used for flashing the boot.img file. So with that said, this guide shall make you aware of various methods to fix the fastboot: error: boot partition is smaller than boot image error. Follow along.
How to Fix fastboot: error: boot partition is smaller than boot image
There isn’t any universal fix as such. You will have to try out each of the below-mentioned workarounds and then see which one gives out the best result. So keeping that in mind, let’s get started. 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.
- To begin with, download the Android SDK Platform Tools and extract it to any convenient location on your PC.
- Then head over to this platform-tools folder address bar, type in CMD, and hit Enter. This shall launch the Command Prompt window. So all the commands that we have listed in this guide should be entered inside this CMD window only.
- Moreover, whatever boot.img file you need to flash, transfer it to this platform-tools folder. Likewise, rename it to boot so that the complete name becomes boot.img.
- Finally, your device should be booted to Fastboot Mode and connected to the PC via USB cable. If you haven’t done so, then enable USB Debugging and then use the adb reboot bootloader command to boot to Fastboot Mode.
That’s it. These were all the requirements. You may now proceed ahead with the steps to fix the fastboot: error: boot partition is smaller than boot image error.
FIX 1: Manually Flash Boot.img to Both Slots
- For flashing the boot.img file, you might be using the following generic command:
fastboot flash boot boot.img
- While it works out in most cases, sometimes, it could spell out trouble as well. To rectify it, you should manually specify the slots to which the boot files are being flashed.
- So, use the below two commands to flash the boot.img to Slot A and Slot B:
fastboot flash boot_a boot.img fastboot flash boot_b boot.img
- Once that is done, reboot your device via the below command:
- Now verify whether it is able to fix the fastboot: error: boot partition is smaller than boot image error.
FIX 2: Flash Boot.img to Active Partition
Rather than flashing the boot.img to both the partitions (A and B), you could take an alternate route. This involves checking the current active slot and then flashing the file only to that partition. So follow along for the instructions:
- To begin with, use the following command to check the current active slot
fastboot getvar all
- This shall bring a long list of results. You need to refer to the value of ‘(bootloader) current-slot’.
- If it is the one that we have listed below, then A is your current active slot
- Hence you should use the following command to flash the boot.img file to your active slot A:
fastboot flash boot_a boot.img
- On the other hand, if you get the below value then you are on Slot B:
- In that case, you should use the following command to flash the boot.img file to your active slot B:
fastboot flash boot_b boot.img
- Once you have successfully flashed the file to your active slot, use the below command to reboot the device to the OS:
- Now check if the fastboot: error: boot partition is smaller than boot image has been fixed or not.
FIX 3: For Mac Users
Since Apple is no longer using the Intel chipset, there have been a few instances of flashing commands not being executed successfully. Along the same lines, even Google’s Android Flash Tool is causing a lot of issues on Mac setup. Unfortunately, there’s currently no way to fix this issue. The only way out is to arrange a Windows PC and then try out the flashing process in it.
So with this, we round off the guide on how you could fix fastboot: error: boot partition is smaller than boot image. We have listed three different methods for the same. Well, there does exist a fourth method that involves re-partitioning the boot partition on your device. But we have not listed it because there are quite a lot of technicalities involved in it.
And just a slight error could spell out disaster for your device. Anyways, if you have any queries with the three methods that we have listed above, then do let us know in the comments section below. We will get back to you with a solution at the earliest.
- How to Check and Change Current Active Slot on Android
- Fix Bootloop in A/B Partition Android Devices
- How to Fix No Bootable A/B Slot Error on Android
- How to Fix Slot Unbootable Load Error on Pixel Devices