HELP! RM502QAE firmware upgrade failed

IoT Modules 5G Module
1

i got the following error and now the modem is not detected by wg1608. Is there anyway to revive it or it’s now toast?

QFirehose -f /mnt/sda1
[000.000]: Version: QFirehose_Linux_Android_V1.4.8
[000.000]: Builded: Nov 7 2021 18:21:40
[000.000]: Find md5 check file </mnt/sda1/md5.txt>
[000.002]: md5 checking: /mnt/sda1/contents.xml pass
[000.010]: md5 checking: /mnt/sda1/update/abl.elf pass
[000.023]: md5 checking: /mnt/sda1/update/aop.mbn pass
[000.024]: md5 checking: /mnt/sda1/update/apdp.mbn pass
[000.026]: md5 checking: /mnt/sda1/update/devcfg.mbn pass
[000.027]: md5 checking: /mnt/sda1/update/firehose/partition_complete_p4K_b256K.mbn pass
[000.030]: md5 checking: /mnt/sda1/update/firehose/patch_p4K_b256K.xml pass
[000.042]: md5 checking: /mnt/sda1/update/firehose/prog_firehose_sdx55.mbn pass
[000.043]: md5 checking: /mnt/sda1/update/firehose/rawprogram_nand_p4K_b256K_update.xml pass
[000.047]: md5 checking: /mnt/sda1/update/hyp.mbn pass
[000.053]: md5 checking: /mnt/sda1/update/ipa_fws.elf pass
[000.054]: md5 checking: /mnt/sda1/update/multi_image.mbn pass
[003.551]: md5 checking: /mnt/sda1/update/NON-HLOS.ubi pass
[003.908]: md5 checking: /mnt/sda1/update/oemdata.ubi pass
[003.910]: md5 checking: /mnt/sda1/update/partition.mbn pass
[003.911]: md5 checking: /mnt/sda1/update/partition_nand.xml pass
[003.963]: md5 checking: /mnt/sda1/update/sbl1.mbn pass
[004.440]: md5 checking: /mnt/sda1/update/sdxprairie-boot.img pass
[005.077]: md5 checking: /mnt/sda1/update/sdxprairie-recoveryfs.ubi pass
[010.827]: md5 checking: /mnt/sda1/update/sdxprairie-sysfs.ubi pass
[010.828]: md5 checking: /mnt/sda1/update/sec.dat pass
[010.861]: md5 checking: /mnt/sda1/update/tools.fv pass
[010.941]: md5 checking: /mnt/sda1/update/tz.mbn pass
[011.045]: md5 checking: /mnt/sda1/update/uefi.elf pass
[011.219]: md5 checking: /mnt/sda1/update/usrdata.ubi pass
[011.225]: md5 checking: /mnt/sda1/update/xbl_cfg.elf pass
[011.226]: Totals checking 26 files md5 value, 0 file fail!
[011.227]: [1] /sys/bus/usb/devices/1-1.2 5c6/9008/0
[011.228]: P: /dev/bus/usb/001/004 idVendor=05c6 idProduct=9008
[011.228]: C: /dev/bus/usb/001/004 bNumInterfaces: 1
[011.228]: I: If#= 0 Alt= 0 #EPs= 2 Cls=ff Sub=ff Prot=11
[011.228]: E: Ad=81 Atr=02 MxPS= 512 Ivl=0ms
[011.228]: E: Ad=01 Atr=02 MxPS= 512 Ivl=0ms
[011.229]: tmp=/sys/bus/usb/devices/usb1/…/driver, driver=…/…/…/bus/platform/drivers/xhci-mtk
[011.229]: usbfs_is_kernel_driver_alive find interface 0 has match the driver usbfs
[011.229]: usbfs_detach_kernel_driver detach kernel driver success
[011.230]: dir=/mnt/sda1/update/firehose
[011.292]: d_name=prog_firehose_sdx55.mbn
[011.292]: prog_nand_firehose_filename = prog_firehose_sdx55.mbn
[011.292]: STATE ← SAHARA_WAIT_HELLO
[016.473]: inf[0] ep_in -1/4096, errno = 145 (Operation timed out), timeout=5000
[016.473]: qusb_noblock_read read=0, errno: 145 (Operation timed out)
[016.473]: qusb_noblock_read cur=0, min_size=1
[016.476]: RECEIVED ← SAHARA_CMD_UNKONOW_1836597052
[016.476]: Sahara protocol error
[016.476]: Upgrade module failed.

2

How did you upgrade the modem’s firmware? Did you do it while it was installed in the 1608 or did you put it in a simple USB sled, connect it to your computer, and use QFlash ?

3

I use a simple sled and QFlash method. I had one fail for me once… although it “acted” like it was working for a while, then just quit. My 1608 wouldn’t read the modem, etc…

I ended up flashing to an older firmware, which fixed my modem… i used it for a couple months, then flashed it back to the newer firmware that failed me. It has worked great since, going on ~8 months.

4

Thanks for replying. I’m using QFirehose in ROOter directly on wg1608. I did a couple of times before and it was fine, but i guess the modem hates going from R11A02.002 directly R11A04.003

5

You could be right. Hopefully a Quectel moderator will shed some light on this for you.

6

I havent even see any support person in the English forum for weeks.