Windows one-click bootloader (BL) unlock assistant for Xiaomi devices with Snapdragon 8s Gen 4
Mi8sG4_BootLoader_Unlocker is a Windows fully-automatic bootloader (BL) unlock assistant for Xiaomi devices based on the Snapdragon 8s Gen 4 platform.
This project provides an automated workflow via the toUnlock.bat script. It bundles an ADB / Fastboot environment, device-specific resources, status-checking tools, and debug entry points to complete the BL unlock process under HyperOS.
Users only need to fully extract the package on Windows, connect their device, and run toUnlock.bat; follow the script prompts to complete the automated flow.
For help or discussion, join the channel:
https://fb.com/being.as.hasib
-
One-click Windows run
RuntoUnlock.batto start the automated workflow. -
Targeting Snapdragon 8s Gen 4 platform
Adapted specifically for Xiaomi devices on the new 8s Gen 4 platform. -
Multi-model precise matching
The script selects model-specific resources from the corresponding directories. -
Built-in ADB / Fastboot
No need to separately install Android Platform Tools β just extract and use. -
BL status detection
Includescheck-unlock.batto check bootloader lock and engineering ABL status. -
Integrated debug tools
Includesadb-tool.batfor convenient ADB / Fastboot debugging commands. -
Lightweight resource package
Bundles only necessary ABL / GPT resources to reduce unnecessary file size.
The following three Snapdragon 8s Gen 4 devices are currently supported:
- Redmi Turbo 4 Pro
- Xiaomi Civi 5 Pro
- Xiaomi Pad 8
Please confirm your device meets the following requirements before use.
| Item | Requirement |
|---|---|
| PC OS | Windows 10 / Windows 11 |
| Phone OS | HyperOS 2.0 or later |
| Android Security Patch | February 2026 or older |
| Device platform | Snapdragon 8s Gen 4 |
| Connection | USB data cable |
| Debug status | USB debugging enabled |
Supported:
HyperOS 2.0 and above
Not supported:
HyperOS 1.0 and earlier
HyperOS 1.0 and earlier lack necessary low-level system components, so this tool's flow will not work correctly on those older versions.
Mi8sG4_BootLoader_Unlocker.zip
βββ 8735-Ennea.img
βββ 8sg4-unlock.bat
βββ toUnlock.bat
βββ check-unlock.bat
βββ adb-tool.bat
βββ adb.exe
βββ fastboot.exe
βββ AdbWinApi.dll
βββ AdbWinUsbApi.dll
βββ unlockFolder/
βββ factoryImages/
β βββ Redmiturbo4pro/
β β βββ images/
β β βββ abl.elf
β β βββ gpt_both4.bin
β βββ Xiaomicivi5pro/
β β βββ images/
β β βββ abl.elf
β β βββ gpt_both4.bin
β βββ Xiaomipad8/
β βββ images/
β βββ abl.elf
β βββ gpt_both4.bin
βββ unlockGPT/
βββ Redmiturbo4pro/
β βββ unlockgpt_both4.bin
βββ Xiaomicivi5pro/
β βββ unlockgpt_both4.bin
βββ Xiaomipad8/
βββ unlockgpt_both4.bin
| File / Directory | Description |
|---|---|
toUnlock.bat |
One-click entry script |
8sg4-unlock.bat |
Main unlock process script |
check-unlock.bat |
Script to check BL lock / engineering ABL status |
adb-tool.bat |
ADB / Fastboot debugging tool |
8735-Ennea.img |
Image used in the unlock flow |
adb.exe |
ADB tool |
fastboot.exe |
Fastboot tool |
AdbWinApi.dll |
Windows ADB runtime library |
AdbWinUsbApi.dll |
Windows ADB USB runtime library |
unlockFolder/factoryImages/ |
ABL / GPT resources per model |
unlockFolder/unlockGPT/ |
GPT unlock resources |
Download the latest version from the Releases page:
Mi8sG4_BootLoader_Unlocker.zip
Fully extract to a local directory.
It is recommended to use an English path, for example:
D:\Mi8sG4_Unlocker\
Do not run scripts directly from inside the ZIP archive.
On the phone:
Settings β About phone β tap the build number repeatedly to enable Developer options
Settings β More settings β Developer options β USB debugging
After connecting to the PC, allow the USB debugging authorization prompt on the phone.
Double-click to run:
toUnlock.bat
Choose the corresponding model when prompted by the script and continue.
After the unlock process completes, you can run:
check-unlock.bat
This script checks:
- Bootloader (BL) lock status
- Engineering ABL status
- Current device connection status
- Possible exceptions or errors
If you need to run ADB / Fastboot commands manually, run:
adb-tool.bat
- Unlocking the bootloader will erase all user data β be sure to back up beforehand.
- Use the original or a reliable quality data cable.
- It is recommended to connect to a USB 2.0 port on the computer.
- Fully extract the package before running scripts.
- Do not delete, move, or rename files inside the package.
- Not recommended to run in virtual machines, remote desktop, or unstable USB environments.
- If the device is not recognized, check USB debugging authorization, drivers, and the data cable.
- There is no guarantee the tool will work for all system versions, region variants, or device states.
Check:
- Whether USB debugging is enabled
- Whether the phone showed a USB debugging authorization prompt
- Whether you tapped Allow for debugging
- Whether the data cable supports data transfer
- Whether Windows drivers are installed correctly
- Whether another phone management tool is occupying ADB
- Whether the package was fully extracted
No.
This tool requires HyperOS 2.0 or later.
Yes.
BL unlock will erase user data β please back up first.
Some batch scripts and ADB / Fastboot tools may behave unexpectedly when run from Chinese or special-character paths.
Recommended path:
D:\Mi8sG4_Unlocker\
If you encounter any of the following issues on supported models:
- Device not recognized
- Script errors
- Status check abnormal
- Model matching errors
- ADB / Fastboot communication issues
- Process interrupted or failed
Please open an Issue and include as much of the following as possible:
- Device model
- System version
- Screenshot of the script
- Error messages
- Which step failed
- Current device mode: System / Fastboot
Thanks to @Kernix for scripts support.
![]() Kernix π‘ Scripts / π» 8sg4_Unlocker.bat |
Thanks to @Littlenine for core technical support.
![]() Littlenine π‘ Core technology / π» Unlocking boot.img |
This project is provided for technical exchange, maintenance of personal devices, and authorized testing only.
Using this tool may result in:
- User data deletion
- Device malfunction
- System failure to boot
- Warranty status changes
- Need for reflashing to recover
- Other unforeseen issues
Users must ensure they own the device or have authorization to use it and accept full responsibility for any risks.
The developer is not liable for device failures, data loss, warranty voiding, or other direct/indirect losses resulting from use of this project.
Do not use this project on unauthorized devices, for illegal activities, or to infringe others' rights.

