One among them is the inability of the command to be executed properly. In this regard, many users are experiencing issues while trying to erase the system partition on their device via a Fastboot Command. But why is there a need to wipe the system partition? Well, it is mostly needed when you are trying to flash a custom ROM via Fastboot Commands (without using TWRP), or more importantly when you are trying to flash the GSI image. In most cases, either the Command Window is either stuck on the erasing system or it straightaway shows the FAILED (remote: unknown command) message. While TWRP could have easily wiped this partition, the thing most users going through this issue doesn’t have this custom recovery installed in the first place. So if you are also on the same page, then this guide shall help you out. Given here are the detailed instructions to fix the fastboot erase system command not working issue.
How to Fix fastboot erase system command not working
Do keep in mind that carrying out this task is extremely risky. Upon successfully wiping the system, you will lose the installed OS, thereby make sure you have the required stock firmware or custom ROM by your side beforehand. 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.
Use the Latest Google ADB Fastboot Binaries
Use Official USB cable | USB 2.0 Port
While it may sound like a pretty simple fix, but trust us, many users were able to fix the fastboot erase system command not working issue via this trick. So make sure that you are using the official USB cable that came shipped with your device. If that is not possible, then you could also use the official cable of any other device. But it shouldn’t be a standalone USB cable as they only support charging and MTP.
These cables aren’t able to carry out any of the advanced functionalities such as execution of ADB and Fastboot Commands. Along the same lines, it is highly recommended that you use the USB 2.0 Port on your PC or laptop. USB 3.0, though provide higher speed, is known to conflicts with these commands. Try out these tweaks and then see if it fixes the issue.
Manually Install Android USB Drivers
Most Android devices automatically install the USB drivers as soon as you connect them to the PC via USB cable. However, if that is not the case, then you would have to manually install two such drivers: android_winusb.inf and Android Bootloader Interface Drivers. Please refer to our comprehensive guides on both these drivers for the download links as well as the installation steps:
Download and Install Android USB Drivers (android_winusb.inf)How to Install Google Android Bootloader Interface Drivers
Try out a Different Fastboot Erase Command
Well, if the native fastboot erase system doesn’t work out, then there is an alternative way out. However, it is extremely risky and could potentially brick the device. While some users were able to achieve success with this command, it doesn’t mean that it would work for all of you. So what exactly is this command? Well, the command is: You will have to execute this command inside the CMD window that is opened in the platform-tools folder. While adding “-u” will not erase the system partition, it will only overwrite the partition. So in a nutshell, you are flashing a new system image (ROM) over the already installed stock one. This overriding of the system files might work out or even lead to disastrous consequences. So try ahead at your own risk.
Fix for Ryzen PC
ADB/Fastboot Commands and Ryzen don’t usually go hand in hand. There are a plethora of complaints lined up by users who have this processor. To fix this, you could refer to our standalone guide, written specifically for Ryzen: How to Fix Android ADB and Fastboot Issues on Ryzen based PCs.
Fix Check device console Error
While trying to wipe the system partition, some users were greeted with the FAILED (remote: Check device console) error. If you also getting bugged with this error, then you may refer to our separate guide that focuses on just this issue: How to Fix FAILED (remote: Check device console). So these were some of the methods through which you could fix the fastboot erase system command not working issue. We have shared six different fixed for the same, do let us know in the comments which one spelled out success for you. Moreover, if you were able to fix this issue using any other workaround, do let us know in the comments section.
Fix Root not working after flashing Magisk patched boot.imgHow to Fix All ADB and Fastboot ErrorsHow to Fix (FAILED (Write to device failed (Invalid argument))Fix writing ‘system’ FAILED (remote: ‘Partition not found’)
About Chief Editor
