In this guide, we will show you the steps to fix the FAILED (remote: ‘Partition should be flashed in fastbootd’). There are quite a few under the hood changes going on in recent years that might escape from the general users. A few years ago, we got to welcome the A/B dual partition slots and Seamless Android upgrades. This was a major change in the Android ecosystem as the recovery partition was no longer there and was replaced by the boot partition. As a result, the flashing of TWRP was never the same again.
Then recently we got to know about the fastbootd. Beginning with Android 10, there is now support for resizable partitions. Since the userspace fastboot and recovery are near about similar, there stands a possibility of merging them into one partition. But what would be the benefit of the same? Well, it will lead to lowering the partition count on your device which in turn would save storage space as well. Apart from that, both the recovery and fastboot could now share the same kernel and libraries.
To make your device support the same, the bootloader on your device should (or rather must) implement a new boot control block. This BCB should be related to the command of boot-fastboot. All in all, there’s quite a lot of perks associated with these new changes. But on the other hand, there seem to be a few issues as well. Many users have complained about the FAILED (remote: ‘Partition should be flashed in fastbootd’) error. If you are also facing it, then this guide is here to help you out. Follow along.
- How to Execute Android ADB Fastboot Commands Wirelessly
- Run ADB Fastboot Commands directly on Android without Root
- Use ADB and Fastboot Commands on Android Without PC
- How to Flash Custom ROMs in Android using Web Browser
Fix FAILED (remote: ‘Partition should be flashed in fastbootd’)
Given below are three methods to rectify this issue. There isn’t any universal fix as such, you will have to try out each of the below-mentioned workarounds until you are able to fix this issue. So on that note, let’s get started.
Fix 1: Use the latest ADB Fastboot Binaires
The two biggest reasons for this error are attributed to using an older build of ADB binaries or using third-party ADB tools. In this regard, you should always use the Android SDK Platform Tools provided by Google. This comes bundled with all the required ADB and Fastboot binary files.
- So download the latest version of Android SDK Platform Tools.
- Then extract it to any convenient location on your PC.
- Upon extraction, you should get the platform-tools folder.
- So head over to this folder’s address bar, type in CMD in the address bar, and hit Enter. This will launch the Command Prompt window.
You may now execute the desired command and the FAILED (remote: ‘Partition should be flashed in fastbootd’) error would be fixed. If not, then here are a couple of other methods to try out.
Do keep in mind that while executing Fix 2 or Fix 3, you will still have to respect the steps given in this Fix 1. This is because both the below methods requires executing Fastboot Commands, which should alwasy be done via the latest Android SDK Platform Tools.
- How to fix FAILED (status read failed (Too many links))
- How to Fix FAILED (remote: unknown command) Error
- Guide to Fix FAILED (remote: Command not allowed)
- How to Fix Bootloop in A/B Partition Android Devices
Fix 2: Boot to Fastbootd via Fastboot Command
- A lot could change with just a missing hyphen! Here’s how. If you are currently booted to Bootloader/Fastboot mode and wish to reboot to this mode, then you use the following command:
fastboot reboot bootloader
- However, that is now things work inside the Fastbootd environment. When you are getting the FAILED (remote: ‘Partition should be flashed in fastbootd’) error, then you need to reboot your device to Fastbootd mode and not the normal Fastboot mode.
- And this could be achieved by adding a hyphen to the aforementioned command. In other words, you should use the following command:
- Do so and your device shall be booted to Fastbootd Mode. Similarly, it should also fix the FAILED (remote: ‘Partition should be flashed in fastbootd’) error. However, if your answer is in a negative tone, then here’s another method that you should try out.
Fix 3: Reboot from Fastboot to Fastbootd
- This is similar to the above fix but the commands are slightly different. There exists another command through which you could boot the device to Fastbootd mode from Fastboot. So if the above fastboot reboot-bootloader didn’t work out in your favor, then try the following command:
fastboot reboot fastboot
- Your device will now boot to the Fastbootd mode, thereby fixing the error as well.
With this, we conclude the guide on how to fix the FAILED (remote: ‘Partition should be flashed in fastbootd’) error. We have shared three different methods for the same. Do let us know in the comments which one spelled out success in your case. Furthermore, we will be regularly updating this guide with more fixes as and when we get hold of them.
- How to Fix fastboot: error: Couldn’t parse partition size ‘0x’
- How to Fix Android Device stuck in Fastboot Mode
- Fix error boot prepare- device stuck in fastboot (Pixel devices)
- Fix FAILED (remote: Slot Change is not allowed in Lock State)