Hello @leon.bao,
I appretiate you going the extra mile of digging up these older tools for me. Not many support people would put into it this much effort. I am really impressed and happy at the same time about it.
On the other hand, sorry to keep you waiting for so long, but I finally found the time to attempt the upgrade.
I used a Kubuntu 24.04 live system for the upgrade.
The upgrade tool compiled successfully, though with some compiler warnings.
When attempting the upgrade, the outputs suggested that some steps were executing successfully, but in the end I encountered the following problem:
root@kubuntu:~/eeee/updater# ./QFlash -f fffff/
EC20_QFlash_Linux&Android_V3.1.0
***********************
The CPU is little endian
***********************
firmware path: /root/eeee/updater/fffff/
Module upgrade tool, Wed Jun 11 12:31:31 2025
unknow file EC20_A20150923.qcn in firmware path
Detect yaffs_head.aa file
Detect yaffs_head.ab file
module status detection
/root/eeee/updater/QFlash fastboot devices
MDM9615 fastboot
/root/eeee/updater/QFlash fastboot erase aboot
erasing 'aboot'...
OKAY [ 0.019s]
finished. total time: 0.019s
/root/eeee/updater/QFlash fastboot reboot
rebooting...
finished. total time: 0.001s
in download mode
in PRG Status
send /root/eeee/updater/fffff//NPRG9x15.hex
progress : 100% finished
tx:7e 05 41 70 00 00 f7 63 7e
tx:7e 06 4e 95 7e
rx:7e 0e 49 6e 76 61 6c 69 64 20 43 6f 6d 6d 61 6e 64 0a 58 bd 7e 7e 0d 05 00 00 00 49 6e 76 61 6c 69 64 20 43 6f 6d 6d 61 6e 64 bf c3 7e
in go mode
start to download firmware
tx:7e 17 01 57 c6 7e
rx:7e
rx:18
rx:b1
rx:6c
rx:7e
tx:7e 19 00 9a 1b 7d 5d aa bc 48 7d 5d 1f 03 00 00 00 10 00 00 00 30 3a 4d 49 42 49 42 00 00 00 00 00 00 00 00 00 06 00 00 00 04 00 00 00 ff ff ff
handle_parti_tbl command = 1a, status = 00
flash 0:SBL1 /root/eeee/updater/fffff//sbl1.mbn
sending '0:SBL1' (115KB)
progress : 100% finished
OKAY
flash 0:SBL2 sbl2_tmp.mbn
progress : 100% finished
OKAY
flash 0:RPM /root/eeee/updater/fffff//rpm.mbn
sending '0:RPM' (102KB)
progress : 100% finished
OKAY
flash 0:APPSBL appsboot_tmp.mbn
progress : 100% finished
OKAY
tx:7e 0b ab 4e 7e
rx:7e
rx:0c
rx:14
rx:3a
rx:7e
/root/eeee/updater/QFlash fastboot devices
MDM9615 fastboot
/root/eeee/updater/QFlash fastboot flash sbl2 "/root/eeee/updater/fffff//sbl2.mbn"
error: cannot open device
Upgrade module unsuccessfully, Wed Jun 11 12:31:48 2025
This was what I saw in the Linux systems kernel log:
[Wed Jun 11 12:35:50 2025] usb 3-4: new high-speed USB device number 8 using xhci_hcd
[Wed Jun 11 12:35:50 2025] usb 3-4: New USB device found, idVendor=05c6, idProduct=9215, bcdDevice= 0.00
[Wed Jun 11 12:35:50 2025] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[Wed Jun 11 12:35:50 2025] usb 3-4: Product: QHSUSB_DLOAD
[Wed Jun 11 12:35:50 2025] usb 3-4: Manufacturer: Qualcomm CDMA Technologies MSM
[Wed Jun 11 12:35:50 2025] qcserial 3-4:1.0: Qualcomm USB modem converter detected
[Wed Jun 11 12:35:50 2025] usb 3-4: Qualcomm USB modem converter now attached to ttyUSB0
[Wed Jun 11 12:36:03 2025] usb 3-4: USB disconnect, device number 8
[Wed Jun 11 12:36:03 2025] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[Wed Jun 11 12:36:03 2025] qcserial 3-4:1.0: device disconnected
[Wed Jun 11 12:36:04 2025] usb 3-4: new high-speed USB device number 9 using xhci_hcd
[Wed Jun 11 12:36:04 2025] usb 3-4: New USB device found, idVendor=18d1, idProduct=d00d, bcdDevice= 1.00
[Wed Jun 11 12:36:04 2025] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Wed Jun 11 12:36:04 2025] usb 3-4: Product: Android
[Wed Jun 11 12:36:04 2025] usb 3-4: Manufacturer: Google
[Wed Jun 11 12:36:04 2025] usb 3-4: SerialNumber: MDM9615
[Wed Jun 11 12:38:12 2025] usb 2-1.2: USB disconnect, device number 5
Currently the device doesn’t offer any virtual serial ports, but shows up as the following USB device:
Bus 003 Device 009: ID 18d1:d00d Google Inc. Xiaomi Mi/Redmi 2 (fastboot)
Do you perhaps have any further suggestions, that I might try?