Problem:
Since some time I am not able to flash a new recovery or boot image in bootloader mode.
How to produce the problem:
Method1:
adb reboot bootloader
fastboot devices (respons with device number)
fastboot flash recovery recovery.img
→ Computer does not give any respons. The command line stays empty and stays there for hours.
Method2:
adb reboot bootloader
fastboot devices (respons given)
fastboot boot recovery.img
→ Command line gives no respons (no errors, no warnings or whatsoever).
Method3:
Xiaomi flash tool (which actually uses fastboot commands I believe).
→ Flash starts, but hangs there for hours without respons (also no errors or warnings).
Did this exercise on a Linux laptop, but also on a Windows 10 laptop. Both give exact the same results.
USB debugging is switched on.
I ended up in this situation, since I wanted to test /e/OS R-release and also wanted to use the e-Rovery tool. So, I decided to enable that option. That was successful, since erecovery was indeed flashed along with the ROM (flashed the ROM via TWRP (TWRP 3.3.1-1).
By using adb sideload, decided to flash the stock ROM of Chiron (miui_MIMIX2Global_V12.0.1.0.PDEMIXM_64006b3102_9.0.zip), which also went fine. The original recovery of Xiaomi came together with the updated stock ROM.
So, now I have a complete stock version of my Mix 2 available. But cannot flash anything else anymore. What are my option to flash back the latest /e/OS release? From bootloader cannot flash nor boot to a new recovery.
Used indeed more than one cable. It made no difference.
Downloaded the unlock tool from Xiaomi and tried to re-apply. Interesting outcome.
At first it was trying to read the device info. The Serial-Number (SN) was recognized. The message from the tool: “Read failed, please refresh or reboot device”. When rebooted it could not read out the device anymore, even not the SN. After several times of re-trying, sometimes it gave back the same message. Sometimes not recognized at all.
@aibd , I am back to the stock recovery, so I guess not related to an outdated TWRP image. See also my previous reply to @smu44 . I guess something corrupt.
I do take your point, did you already use this exact MIUI already?
My experience is that increasingly newer MIUI make breaking into MIUI more difficult than 12 months ago. I am not being definite about this but perhaps worth checking out some recent posts on XDA
Moved your suggested lines into a “.bat” file and executed it as administrator. Next restarted into the bootloader and flashed the recovery. Worked at the first command! Now back to e/OS/!