Redmi 12 5G (23077RABDC) stuck in Fastboot after MiFlash — locked bootloader / possible EDL recovery

[noorul ameen]

Hi everyone,

I’m working on a Redmi 12 5G China variant, model 23077RABDC, which is currently stuck in Fastboot after a failed MiFlash operation.

I’m a phone technician, so I’m looking for a technical recovery path rather than basic Fastboot troubleshooting.

Device information​

• Model: 23077RABDC
• Product reported by Fastboot: river
• Variant: SM_ UFS
• Bootloader: locked
• Secure boot: yes
• Current slot: a
• Slot count: 2
• Android/A-B layout with dynamic super
• snapshot-update-status: none

Current slot state​

Fastboot reports:

current-slot: a
slot-count: 2

slot-unbootable:a: yes
slot-successful:a: no
slot-retry-count:a: 0

slot-unbootable:b: no
slot-successful:b: no
slot-retry-count:b: 0
I tried:

fastboot set_active b
but received:

remote: 'Slot Change is not allowed in Lock State'
fastboot oem device-info reports:

Verity mode: true
Device unlocked: false
Device critical unlocked: false
The phone is still detected normally by Fastboot.

What happened​

The phone was working normally before the MiFlash operation.

I used:

miui_SKY_V14.0.8.0.TMWCNXM_e2ba72d422_13.0.zip
After the MiFlash operation, the phone ended up in Fastboot.

I don't remember whether MiFlash was set to:

• clean all
• save user data
• clean all and lock

The bootloader is now locked.

I have never logged a Mi/Xiaomi account into this phone, so I don't believe this is a normal Mi Account activation-lock situation.
>>> MI FLASH TOOL SAYS UNLOCK NOT POSSIBLE IN LOCK STATE

Fastboot capabilities​

I'm using:

fastboot version 36.0.2-14143358
The phone does not expose an obvious EDL command:

fastboot help | findstr /i "edl reboot emergency"

reboot [bootloader] Reboot device.
--set-active[=SLOT] Sets the active slot before rebooting.
--skip-reboot Don't reboot device after flashing.
And:

fastboot oem help
returns:

FAILED (remote: 'unknown command')
fastboot: error: Command failed
I also tested the newer fastboot fetch functionality, but the device reports that it does not support fetch.

Partition layout​

The device has A/B copies of the important boot-chain partitions, including:

boot_a / boot_b
vendor_boot_a / vendor_boot_b
dtbo_a / dtbo_b
vbmeta_a / vbmeta_b
abl_a / abl_b
xbl_a / xbl_b
recovery_a / recovery_b
It also has:

super
userdata
with dynamic partitions.

What I want to determine​

At this point I'm considering:

Fastboot → Qualcomm 9008/EDL → authorized programmer → restore the correct firmware/boot chain → Android → official bootloader recovery/unlock

I would like advice from anyone who has specifically worked on the 23077RABDC / Redmi 12 5G China / river platform.

In particular:

1. Is there a known legitimate EDL/test-point recovery procedure for this exact board?
2. Does this model require an authorized Xiaomi programmer/account for EDL flashing?
3. Is there a known reason why the locked bootloader prevents switching to slot B in this situation?
4. Is miui_SKY_V14.0.8.0.TMWCNXM...zip the correct package type for MiFlash, or should the corresponding Fastboot TGZ be used?
5. If the phone is still fully responsive in Fastboot, is there a safe way to restore the boot chain without wiping/erasing userdata?
6. Are there known partition dependencies on this platform that should be restored together rather than flashing individual boot, vendor_boot, vbmeta, etc.?

I am not looking for Mi Account bypasses, unauthorized authentication bypasses, or random Firehose/programmer files. I am specifically interested in the correct technical recovery procedure for this model.

I can provide additional non-sensitive Fastboot output if needed.

I will not post IMEI, serial number, authentication tokens, or other device credentials publicly.

 

[rasul khan]

I am in ditto same condition , same mobile , same code name , same model , same china . These details reported by CLI Tool Fastboot. I locked bootloader then phone gone into bootloop. I live in india. Phone bought in UAE by my relative. Please help me.

I tried mi unlock app in windows 10 but it is showing 20045 error which is sold and registered location is not same.

I tried mi assistant but not able to find recovery file for river codename of realme 12 5G with this model number.

What shall I do?

 

[rasul khan]

Did you find any solution?