A severe software bug has been discovered in the latest HyperOS 4.0 Beta release for the Redmi K80 series, effectively locking users out of their devices. Following immediate reports of the issue, the development team has officially pulled the OTA update from the servers to prevent further installations.
The Lock Screen Glitch
The core of the issue lies in a fatal flaw within the system’s lock screen authentication mechanism. Users who installed the affected HyperOS 4.0 Beta build are finding that the system rejects their correct lock screen password or PIN. Instead of unlocking the UI, the system returns a “Phone has been locked” error, leaving the device completely inaccessible and soft-bricked at the lock screen.
Crucial Warning: Do Not Wipe Data
For users currently facing this lock-out, the immediate instinct might be to reboot into Recovery Mode and perform a factory reset (Wipe Data) to bypass the lock. This is highly discouraged.
Attempting to clear data will force the device into the Out-of-Box Experience (OOBE) setup phase upon reboot. Due to the nature of this specific beta bug, the firmware fails to properly communicate with Google’s servers during the setup process. Users who have wiped their data are getting permanently stuck at the Google Account Verification (FRP) step during OOBE. A factory reset essentially transforms a temporary lock screen bug into a much more complicated setup loop.
Next Steps for Affected Users
Xiaomi has entirely halted the rollout of this specific beta build. If your Redmi K80 is currently stuck on the lock screen:
-
Wait for the Hotfix: Do not attempt to bypass the lock screen via recovery tools or third-party ADB scripts. The development team is actively working on a subsequent version fix.
-
Keep the Device Powered: Ensure your device has sufficient battery life to receive an automated background patch or a safe Fastboot/Recovery flash package once the hotfix is officially deployed.
The update servers are being closely monitored, and the patched firmware details will be shared as soon as the development team pushes the corrected build.
