Firmware update only did partial upgrade?

[Agent24]

I have a PinePhone Manjaro Edition and it's working alright with PostmarketOS, but I do have some issues with SMS, particularly larger messages getting "jammed" and not receiving, until I manually delete them from the queue, wait some amount of time (sometimes even a day) and it will start working again. I thought this might be some modem firmware issue as I am running a very old version.

The original modem firmware was EG25GGBR07A08M2G_01.001.01.001

I tried updating to 01.002.01.002 with the fastboot command, but it only seems to have half worked, or something.
I used the information here: https://github.com/the-modem-distro/pine...LASHING.md

I got a message like this with a warning:

Code:

~/Downloads $ fastboot flash modem NON-HLOS.ubi && fastboot reboot Warning: skip copying modem image avb footer (modem partition size: 0, modem image size: 41025536). Sending 'modem' (40064 KB)                        OKAY [  1.281s] Writing 'modem'                                    OKAY [ 12.747s] Finished. Total time: 14.051s Rebooting                                          OKAY [  0.018s] Finished. Total time: 0.073s

When the modem rebooted, the version number was not 01.002.01.002, but 01.002.01.001 instead.
I tried upgrading to 01.003.01.003 and it's the same problem.

The given echo command to set the modem into fastboot did not work for me, I get an error that /dev/ttyUSB2 could not be created:

Code:

/bin/ash: can't create /dev/ttyUSB2: Permission denied

I used the following instead:

Code:

~ $ echo "AT+QFASTBOOT" | sudo atinout - /dev/ttyUSB2 - > ./fboot.txt doas (user@pine64-pinephone) password: EOF from modem

Does anyone know what to do? Thanks!

[Gumur]

I have a PinePhone Manjaro Edition and it's working alright with PostmarketOS, but I do have some issues with SMS, particularly larger messages getting "jammed" and not receiving, until I manually delete them from the queue, wait some amount of time (sometimes even a day) and it will start working again. I thought this might be some modem firmware issue as I am running a very old version.

The original modem firmware was EG25GGBR07A08M2G_01.001.01.001

I tried updating to 01.002.01.002 with the fastboot command, but it only seems to have half worked, or something.
I used the information here: https://github.com/the-modem-distro/pine...LASHING.md

I got a message like this with a warning:

Code:

~/Downloads $ fastboot flash modem NON-HLOS.ubi && fastboot reboot Warning: skip copying modem image avb footer (modem partition size: 0, modem image size: 41025536). Sending 'modem' (40064 KB)                        OKAY [  1.281s] Writing 'modem'                                    OKAY [ 12.747s] Finished. Total time: 14.051s Rebooting                                          OKAY [  0.018s] Finished. Total time: 0.073s

You did not need atinout for this.

It seems you did the job as normal user, but must open a root terminal (sudo su) before fastboot ....

[Agent24]

I think I've figured it out - I found the recovery script here:
https://github.com/Biktorgj/quectel_eg25...flashstock

Which shows flashing individual modules of the firmware.

Code:

#!/bin/sh echo "Sending AT+QFASTBOOT..." sudo sh -c 'echo -ne "AT+QFASTBOOT\r" > /dev/ttyUSB2' echo "Sending OEM STAY in case the custom bootloader is installed" fastboot oem stay echo "Waiting to settle..." sleep 2 echo "Start flashing!" fastboot flash aboot update/appsboot.mbn || exit "Failed to flash the bootloader" fastboot flash:raw boot update/mdm9607-boot.img || exit "Failed to flash main kernel" fastboot flash:raw recovery update/mdm9607-boot.img || exit "Failed to flash recovery kernel" fastboot flash system update/mdm9607-sysfs.ubi || exit "Failed to flash the system partition" fastboot flash recoveryfs update/mdm9607-recovery.ubi || exit "Failed to flash the recovery partition" fastboot flash modem update/NON-HLOS.ubi || exit "Failed to flash ADSP firmware" fastboot reboot echo "Done!"

Again, the command to set the modem into flashing mode didn't work, so I used the other one, and manually ran each flashing command.
The firmware version string reported by the modem is now as expected: 01.003.01.003

Time will tell if it has made any difference to the SMS receive issue...

---

You did not need atinout for this.

It seems you did the job as normal user, but must open a root terminal (sudo su) before fastboot ....

Ahh thanks, I will try it next time.
Sorry I did not notice you had replied, I didn't get a notification email...

But I think the real problem was that first command was only flashing one part/module of the firmware, not the whole thing?