Modem update on Cirrus AP-1300 (EP06-E)

Hi,
I'm trying to update the firmware of the LTE Module because on two routers (Cirrus) it periodically get stuck, expecially during the night. This modem is used to give internet connection to remote houses, so that I can control their IoT devices. For me it's a problem, because I cannot always go there to reset the modem.

First of all, let me say that there's not enought space in the 3.x firmware to proceed, so I had to upgrade to 4.x (but I need mesh to connect with other routers - Connexa-b) so I will have to move back once done.

The only way to do this is to download the firmware in root (/) and inflate it in /tmp, otherwise there's not enough space on it.

I've followed your procedure in Upgrade Quectel Module Software - GL.iNet Router Docs 4 but none of the QFirehose that are there are working for this device. They both escape with errors.
So I've tried the one that is present by default in the router firmware, but it's not able to get the modem into download mode, as you can see from the stamps below:

root@GL-AP1300:/tmp/firm# QFirehose-ar9531-sha256-7383f4 -f /tmp/firm/
/usr/bin/QFirehose-ar9531-sha256-7383f4: line 1: syntax error: unexpected word (expecting ")")

root@GL-AP1300:/tmp/firm# QFirehose-mtk7981a-sha256-c0b944 -f /tmp/firm/
/usr/bin/QFirehose-mtk7981a-sha256-c0b944: line 2: syntax error: unterminated quoted string

root@GL-AP1300:/tmp/firm# QFirehose -f /tmp/firm/
[000.000]: Version: QFirehose_Linux_Android_V1.4.13
[000.001]: Builded: Feb 16 2022 20:29:10
[000.001]: Find md5 check file </tmp/firm/md5.txt>
[000.001]: md5 checking: /tmp/firm/contents.xml pass
[000.012]: md5 checking: /tmp/firm/update/appsboot.mbn pass
[000.014]: md5 checking: /tmp/firm/update/ENPRG9x45.mbn pass
[000.015]: md5 checking: /tmp/firm/update/firehose/partition_complete_p4K_b256K.mbn pass
[000.015]: md5 checking: /tmp/firm/update/firehose/patch_p4K_b256K.xml pass
[000.018]: md5 checking: /tmp/firm/update/firehose/prog_nand_firehose_9x45.mbn pass
[000.019]: md5 checking: /tmp/firm/update/firehose/rawprogram_nand_p4K_b256K_update.xml pass
[000.162]: md5 checking: /tmp/firm/update/mdm9640-perf-boot.img pass
[001.236]: md5 checking: /tmp/firm/update/mdm9640-perf-sysfs.ubi pass
[001.469]: md5 checking: /tmp/firm/update/mdm-perf-recovery-image-mdm9640-perf.ubi pass
[002.500]: md5 checking: /tmp/firm/update/NON-HLOS.ubi pass
[002.502]: md5 checking: /tmp/firm/update/NPRG9x45.mbn pass
[002.503]: md5 checking: /tmp/firm/update/partition.mbn pass
[002.503]: md5 checking: /tmp/firm/update/partition_nand.xml pass
[002.507]: md5 checking: /tmp/firm/update/rpm.mbn pass
[002.512]: md5 checking: /tmp/firm/update/sbl1.mbn pass
[002.522]: md5 checking: /tmp/firm/update/tz.mbn pass
[002.522]: Totals checking 17 files md5 value, 0 file fail!
[002.522]: find 'prog_nand_firehose_9x45.mbn'
[002.523]: find_firehose_mbn prog_nand_firehose_9x45.mbn
[002.524]: [1] /sys/bus/usb/devices/1-1 2c7c/306/310
[002.525]: qusb_read_speed_atime speed: 480, st_atime: 20240831_11:14:41
[002.526]: P: /dev/bus/usb/001/002 idVendor=2c7c idProduct=0306
[002.526]: C: /dev/bus/usb/001/002 bNumInterfaces: 5
[002.526]: I: If#= 0 Alt= 0 #EPs= 2 Cls=ff Sub=ff Prot=ff
[002.526]: E: Ad=81 Atr=02 MxPS= 512 Ivl=0ms
[002.526]: E: Ad=01 Atr=02 MxPS= 512 Ivl=0ms
[002.526]: I: If#= 1 Alt= 0 #EPs= 3 Cls=ff Sub=00 Prot=00
[002.526]: E: Ad=83 Atr=03 MxPS= 10 Ivl=9ms
[002.526]: E: Ad=82 Atr=02 MxPS= 512 Ivl=0ms
[002.526]: E: Ad=02 Atr=02 MxPS= 512 Ivl=0ms
[002.526]: I: If#= 2 Alt= 0 #EPs= 3 Cls=ff Sub=00 Prot=00
[002.526]: E: Ad=85 Atr=03 MxPS= 10 Ivl=9ms
[002.526]: E: Ad=84 Atr=02 MxPS= 512 Ivl=0ms
[002.526]: E: Ad=03 Atr=02 MxPS= 512 Ivl=0ms
[002.526]: I: If#= 3 Alt= 0 #EPs= 3 Cls=ff Sub=00 Prot=00
[002.526]: E: Ad=87 Atr=03 MxPS= 10 Ivl=9ms
[002.526]: E: Ad=86 Atr=02 MxPS= 512 Ivl=0ms
[002.526]: E: Ad=04 Atr=02 MxPS= 512 Ivl=0ms
[002.526]: I: If#= 4 Alt= 0 #EPs= 3 Cls=ff Sub=ff Prot=ff
[002.527]: tmp=/sys/bus/usb/devices/usb1/../driver, driver=../../../../../../bus/platform/drivers/xhci-hcd
[002.527]: qusb_noblock_open port_name = /dev/ttyUSB1
[002.529]: old software version: EP06ELAR03A08M4G
[003.530]: poll_wait events=POLLIN msec=1000 timeout

[003.530]: switch to 'Emergency download mode'
[003.532]: successful, wait module reboot

[004.534]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[005.534]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[006.536]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[007.536]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[008.536]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[009.537]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[010.537]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[011.537]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[012.538]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[013.544]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[014.545]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[015.546]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[016.546]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[017.547]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[018.548]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[019.549]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[020.551]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[021.552]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[022.552]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[023.554]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[024.555]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[025.556]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[026.558]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[027.560]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[028.562]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory
[029.563]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[030.564]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[031.566]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[032.568]: fail to fopen /sys/bus/usb/devices/1-1/uevent, errno: 2 (No such file or directory)
[033.569]: gl-sdk4-modem-git-2024.206.33161-f3b52de/quec_UPGRADE/qfirehose.c main 407 fail

Can you help me in getting the right QFirehose ?

Thanks a lot,
Gianluca

I was able to update the firmware, outside the router.
Thanks again for no support.

Since your post was made on a Saturday, please note that the support team typically addresses requests starting on Monday during regular business hours. As the topic is more complex than other questions, it might take a bit longer to get support - since this forum is mostly community-driven.

It's great to hear that you were able to resolve the issue on your own.

1 Like

I'm sorry, this is a long pending story of an unresolved issue through months... here and with official support on site, that frustrated me...
Started here:

And it looks like I shouldnt buy qualcomm based routers and modems (although I worked for them for 5 years)... since the cannot really move to 4.x without loosing the main feature which is the reason for what I bought them. Mesh....
Mango2 and Creta are still fantastic after years... MT3000 is still messing if more than 5 IoT devices are running routines all together.... :frowning:

When something goes wrong, you can send a log
Or can I take a look at it remotely?
Technical Support via GoodCloud.tar (192 KB)