A Redmi Note 10 Pro completed a flash operation but continued to stop at the MI logo and restart. Fastboot reported that the bootloader and critical partitions were locked, while fastboot getvar anti returned 3. The installed build was identified as V14.0.9.0.TKFEUXM, and an old PixelOS package for the sweet device family was also available.
This is not a situation for trying random ROM archives or selecting a nearby model in a servicing tool. The safest path depends on four facts: exact hardware variant, region, bootloader state, and whether stock recovery still works. With a locked bootloader, official fastboot flashing is normally unavailable to the owner; EDL servicing may require Xiaomi-authorized credentials.
Preserve the Device Identity
Before any operation that writes partitions, record what can be read without modification:
fastboot devices
fastboot oem device-info
fastboot getvar product
fastboot getvar anti
Keep the complete output, not a transcription of only one line. Also record the model printed on the device or box, IMEI only in private service records, original sales region, and the last known MIUI build.
The suffix in TKFEUXM is significant: EU identifies the EEA software branch. A global, India, Turkey, Taiwan, or China package is not interchangeable merely because its Android version and device name look similar.
Interpret the Locked Bootloader Correctly
The observed Fastboot output included:
Device unlocked: false
Device critical unlocked: false
That means a normal owner-side fastboot flash of boot, vendor, system, or recovery should not be expected to work. Xiaomi’s official flashing guidance states that its MiFlash fastboot process requires the bootloader to be unlocked first. Its Redmi Note 10 Pro FAQ also confirms that the model uses a bootloader lock to protect user data and system integrity.
FRP and bootloader unlocking are different controls. Erasing Factory Reset Protection does not turn a locked bootloader into an unlocked one, and an unlock flow can still require the Xiaomi account previously bound to the device. Do not buy access to a tool solely because it displays FRP, EDL, or Unlock buttons.
Do Not Downgrade Based Only on the Version Number
The anti: 3 value is evidence that anti-rollback metadata exists, but it is not a complete downgrade decision. A lower MIUI number can contain an incompatible bootloader or firmware chain. Region mismatches introduce another failure mode.
Do not flash an older package unless Xiaomi documentation or an authorized service center confirms that the exact device, region, and rollback index permit it. A successful write followed by a bootloop does not prove that another older build is safer.
The clean all and lock option in MiFlash deserves particular caution. Relocking with a wrong region, custom system, or incomplete stock image can make recovery harder. Never select a relock action as a generic repair step.
PixelOS Is Not a Stock Recovery Package
A file named PixelOS_sweet-13.0-20230924-1329.zip may target the community codename sweet, but it is a third-party custom ROM from 2023. It is not an official Xiaomi recovery package and cannot be used to repair a locked stock device through ordinary fastboot.
Installing a custom ROM generally requires an unlocked bootloader and the recovery/firmware combination specified by that ROM’s maintainer. Mixing an old custom package with current stock firmware is not a safe bootloop test. Preserve the file separately and exclude it from the official recovery workflow.
Try Stock Recovery Before Service Flashing
Xiaomi’s official Redmi Note 10 Pro FAQ documents stock recovery access with the phone powered off: hold Volume Up and Power, then release Power when the Xiaomi logo appears.
If recovery opens:
- Photograph the recovery version and every displayed error.
- Try Reboot to System once.
- If the menu exposes an official update or assistant connection, use only an exact official package offered for the device and region.
- Use Wipe Data only after accepting that local data will be erased.
A factory reset can fix corrupted user data after an update, but it cannot replace missing or incompatible system partitions. Do not repeat the wipe if the first clean boot still loops.
Xiaomi’s OTA troubleshooting page says that official packages are verified for the model and recommends the latest full package when an incremental update fails. The phone must be able to enter a supported updater or recovery path for that advice to apply.
Why Mi Phone Assistant May Not Download Everything Automatically
Mi Phone Assistant builds and regional services have changed over time. The Chinese assistant may recognize a device that the old global download no longer handles, but that does not guarantee that it can retrieve an EEA recovery image for a locked phone.
If the assistant asks for a local package, do not substitute a similarly named archive. Verify:
- Recovery package versus fastboot package.
- Exact model/codename.
- EEA branch matching
EUXM. - Newer or equal permitted rollback level.
- Vendor-published checksum where available.
A 503 error from a download endpoint is a server or delivery failure, not a reason to use an unverified mirror. Retry the official channel later or move to authorized service.
When EDL Mode Is the Correct Boundary
Qualcomm 9008/EDL mode exposes a low-level service interface. Logs from third-party servicing software showed the phone on a COM port but failed while searching for a compatible loader or authenticating.
Selecting a different Xiaomi model to make the tool continue is unsafe. A mismatched programmer can write the wrong partition layout or firmware. Modern Xiaomi EDL workflows may require an authorized service account; that restriction is part of the security boundary.
Do not attempt to bypass Xiaomi account authorization, FRP, or bootloader controls. If stock recovery cannot repair the phone and the bootloader is locked, use Xiaomi’s authorized service network. Xiaomi explicitly lists software upgrade service and warns that service operations can erase data.
A Safe Decision Tree
| Device state | Next action |
|---|---|
| Boots after one forced restart | Back up immediately and inspect update status |
| Stock recovery opens | Reboot once; then consider an accepted data wipe or exact official recovery path |
| Fastboot works and bootloader is already unlocked | Use only the exact official fastboot package and documented MiFlash mode |
| Fastboot works but bootloader is locked | Do not force partition writes; use recovery or authorized service |
| Only Qualcomm 9008 is detected | Authorized EDL service with the exact model and loader |
| Hardware test or service flash still bootloops | Diagnose storage, power, or board failure |
Xiaomi’s current Fastboot support article recommends a long Power-button restart and authorized inspection when the device does not leave Fastboot. The same escalation principle applies when a locked phone cannot complete an official recovery.
What to Give the Service Center
Provide a compact incident record:
- Exact Redmi model and sales region.
- Original build
V14.0.9.0.TKFEUXMor other verified build. - Bootloader output showing locked state.
- Anti-rollback output.
- The tool and package that reported a completed flash.
- Whether stock recovery opens and whether a wipe was attempted.
- Whether the phone enumerates as Fastboot or Qualcomm 9008.
- Proof of purchase and the Xiaomi account available to the owner.
Do not publish the IMEI, serial number, account address, or paid-tool work ID in a forum post.
Conclusion
A completed progress bar does not prove that a Redmi Note 10 Pro received a compatible boot chain. In this case, the locked bootloader, EEA build, anti-rollback value, and continued MI-logo loop rule out casual experimentation with old custom ROMs and cross-region downgrades.
Start with read-only identification and stock recovery. Use only an exact official package accepted by the device. If the bootloader remains locked and EDL authentication is required, the safe next step is an authorized Xiaomi service center—not a bypass tool or a different model profile.
