When it comes to utilizing the open-source ecosystem to its full potential, tech enthusiasts have a number of options to choose from. In addition, users can flash customized and modified Android ROMs or gain access to the system partition, as well as replace the device’s stock recovery with one such a TWRP. But, sometimes, users get stuck while flashing ROM on their smartphones as they get an error “flashing is not allowed in lock state.” Well, that’s the reason why we are here. In this article, we have mentioned every possible fix that will help you resolve this problem. So, let’s get started with the guide.
How to Fix Flashing is Not Allowed in Lock State Error
It is important to note that the below process will wipe all of your device’s data, so take a full backup before continuing. It may also result in your device’s warranty being void (once the bootloader? partition has been unlocked). Getdroidtips members aren’t responsible if anything happens to your device or data as a result of following the steps below:
Fix 1: Flash File in FastbootD Mode
Fastboot/Bootloader Mode is the biggest culprit here, even though FastbootD Mode is intended for flashing a file. You will no longer receive the Failed (remote: Flashing is not allowed for Critical Partitions) error if you boot your device to FastobootD using the shorter instruction below:
error:FAILED ( remote: Flashing is not allowed in Lock State )
I have a REDMI NOTE 7S which I can only get fastboot
I have tried to flash with the latest MiFlash and the 18/08/2024 Miflash
Miflash can see the device – it goes through the flash and everything seems to be doing fine until after 30 seconds it says
error:FAILED ( remote: Flashing is not allowed in Lock State )
I had this device unlocked before , but when I flashed TWRP originally I left the default selection of clean all and lock on MiFlash ( sad default )
any ideas ?