FOSS fw problem - PinePhonePro, EG25 modem

[dukla2000]

OK, so I have had an older PinePhonePro (mini SIM rather than micro SIM) for a while. I had flashed Biktorg's fw to it and used to be able to chat to the modem fine. A while back I had a problem 1 night setting a wakeup call (can't remember, power fail, think trying to flash 0.8.0) and since then I cant SMS the modem. I have tried everything I can think of, flashing back to stock, trying fwupd to flash, pmOS, arch, mobian, 30.006, 01.003 ADSP firmware, ...

So as I write this I have my PPP which has a "Frankenstein" firmware (it seems half FOSS but with stock artefacts) and my old PP in front of me which is FOSS and behaves like I expect.

The basic problem that is the subject of this thread - I can't send SMS to the modem:

Code:

$ cat sms.txt | sxmo_modemsendsms.sh +223344556677 -
12:41:25 sxmo_modemsendsms.sh: Couldn't send text message (error: couldn't send the SMS: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Connected: No AT port available to run command')
Couldn't send text message (error: couldn't send the SMS: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Connected: No AT port available to run command')

The system log during boot - note the serial number is "community_fw":

Code:

[   34.237819] usb 1-1: new high-speed USB device number 3 using ehci-platform
[   34.368702] usb 1-1: New USB device found, idVendor=2c7c, idProduct=0125, bcdDevice= 3.18
[   34.368737] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   34.368747] usb 1-1: Product: LTE Module
[   34.368755] usb 1-1: Manufacturer: Quectel, Incorporated
[   34.368764] usb 1-1: SerialNumber: community_fw
[   34.441830] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
[   34.442645] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB1
[   34.443151] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB2
[   34.443494] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB3

For cross reference on my PP the system log has the same info:

Code:

[   52.475036] usb 2-1: new high-speed USB device number 3 using ehci-platform
[   52.636611] usb 2-1: New USB device found, idVendor=2c7c, idProduct=0125, bcdDevice= 3.18
[   52.640986] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   52.641138] usb 2-1: Product: LTE Module
[   52.641198] usb 2-1: Manufacturer: Quectel, Incorporated
[   52.641232] usb 2-1: SerialNumber: community_fw
[   52.717965] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB0
[   52.723460] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB1
[   52.737674] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB2
[   52.742115] usb 2-1: GSM modem (1-port) converter now attached to ttyUSB3

The reason for my "Frankenstein" use is that the differences start showing in the journal - my PPP has

Code:

[Jan 31 12:27:05] daemon eg25-manager: ** Message: 12:27:05.087: Successfully sent command: AT+QGMR
...
[Jan 31 12:27:05] daemon eg25-manager: ** Message: 12:27:05.113: Response: [EG25GGBR07A08M2G_01.003.00.000\r\n\r\nOK]

Whereas the PP has

Code:

[Jan 01 01:01:30] daemon eg25-manager: ** Message: 01:01:30.626: Successfully sent command: AT+QGMR
...
[Jan 01 01:01:30] daemon eg25-manager: ** Message: 01:01:30.645: Response: [0.7.4\r\n\r\nOK]

So it appears my most recent attempt to flash the modem failed, but the log is (flashing 0.7.4 FWIW):

Code:

# ./flashall
Sending AT+QFASTBOOT...
OKAY [  0.002s]
Finished. Total time: 0.002s
Warning: skip copying aboot image avb footer (aboot partition size: 0, aboot image size: 286476).
Sending 'aboot' (279 KB)                           OKAY [  0.013s]
Writing 'aboot'                                    OKAY [  0.131s]
Finished. Total time: 0.166s
Rebooting                                          OKAY [  0.004s]
Finished. Total time: 0.055s
< waiting for any device >
OKAY [  0.002s]
Finished. Total time: 0.002s
Sending 'boot' (4600 KB)                           OKAY [  0.149s]
Writing 'boot'                                     OKAY [  1.793s]
Finished. Total time: 1.955s
Sending 'recovery' (4600 KB)                       OKAY [  0.148s]
Writing 'recovery'                                 OKAY [  1.795s]
Finished. Total time: 1.963s
Warning: skip copying system image avb footer (system partition size: 0, system image size: 28311552).
Sending 'system' (27648 KB)                        OKAY [  0.879s]
Writing 'system'                                   OKAY [ 11.942s]
Finished. Total time: 12.844s
Warning: skip copying recoveryfs image avb footer (recoveryfs partition size: 0, recoveryfs image size: 13369344).
Sending 'recoveryfs' (13056 KB)                    OKAY [  0.417s]
Writing 'recoveryfs'                               OKAY [  4.949s]
Finished. Total time: 5.391s
Rebooting                                          OKAY [  0.004s]
Finished. Total time: 0.055s
Done!

Any thoughts welcome - my only hope is to keep trying to flash 0.7.4 and hope it works!

[zetabeta]

may not be your case totally, but look it anyway.

https://forum.pine64.org/showthread.php?...+partition

[dukla2000]

may not be your case totally, but look it anyway.

https://forum.pine64.org/showthread.php?...+partition

Thanks - some similarities but not completely.

I should have added in my first post that in fact I could not send or receive any SMS, couldn't make or receive any call and although the data APN would attach I couldn't get any data via LTE.

I do have some good progress though:

• I deleted all the downloaded stuff I had and started with a fresh download of the FOSS firmware and checked all the sha512sums. I also downloaded a fresh copy of the 30.200 ADSP. I could flash them happily and it made no difference. I even tried ./flashall twice in a row followed by the HLOS twice, nada.
  
• I meticulously followed the Going back to stock instructions (rather than ./flashstock) and I do seem to have a fully functioning EG25GGBR07A08M2G_30.006.30.006 - SMS, calls and data are all functioning.
  
• I tried to use fwupdmgr on pmOS and it wont do any up (or down) grades
  

Next to try is to flash Biktorgj's 0.7.4 again - I want the SMS interface (for alarms etc) but am a bit nervous about why I patently failed to do it properly before! Watch this space

---

OK, so tried a FOSS flash again, have a Frankenstein setup again except SMS & calls seem to work.

First the log of my attempt to flash in the same order as the recovery instructions above (i.e. aboot last)

Code:

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 18d1:d00d Google Inc. Xiaomi Mi/Redmi 2 (fastboot)
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
...
fastboot flash system rootfs-mdm9607.ubi-mdm9607.ubi
Warning: skip copying system image avb footer (system partition size: 0, system image size: 28311552).
Sending 'system' (27648 KB)                        OKAY [  1.429s]
Writing 'system'                                   OKAY [ 10.086s]
Finished. Total time: 11.540s
[csn@PPP modem]$ fastboot flash recoveryfs recoveryfs.ubi
Warning: skip copying recoveryfs image avb footer (recoveryfs partition size: 0, recoveryfs image size: 13369344).
Sending 'recoveryfs' (13056 KB)                    OKAY [  0.682s]
Writing 'recoveryfs'                               OKAY [  4.441s]
Finished. Total time: 5.149s
[csn@PPP modem]$ fastboot flash:raw boot boot-mdm9607.img
Sending 'boot' (4600 KB)                           OKAY [  0.148s]
Writing 'boot'                                     OKAY [  1.580s]
Finished. Total time: 1.944s
[csn@PPP modem]$ fastboot flash:raw recovery boot-mdm9607.img
Sending 'recovery' (4600 KB)                       OKAY [  0.149s]
Writing 'recovery'                                 OKAY [  1.582s]
Finished. Total time: 1.746s
[csn@PPP modem]$ fastboot flash aboot appsboot.mbn
Warning: skip copying aboot image avb footer (aboot partition size: 0, aboot image size: 286476).
Sending 'aboot' (279 KB)                           OKAY [  0.028s]
Writing 'aboot'                                    OKAY [  0.136s]
Finished. Total time: 0.188s
[csn@PPP modem]$ fastboot reboot

System log says community_fw

Code:

[   37.845272] usb 1-1: new high-speed USB device number 3 using ehci-platform
[   37.992120] usb 1-1: New USB device found, idVendor=2c7c, idProduct=0125, bcdDevice= 3.18
[   37.992164] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   37.992183] usb 1-1: Product: LTE Module
[   37.992198] usb 1-1: Manufacturer: Quectel, Incorporated
[   37.992213] usb 1-1: SerialNumber: community_fw

But it still thinks it is stock and wont play nicely with the SMS interface.

Code:

$ echo 'AT+QGMR' | sudo atinout - /dev/ttyUSB2 -

EG25GGBR07A08M2G_30.006.30.006

OK
[csn@PPP ~]$ ./sendsms.sh +223344556677
20:58:48 sxmo_modemsendsms.sh: Couldn't send text message (error: couldn't send the SMS: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Message.Unknown: Unknown message error: 350')
Couldn't send text message (error: couldn't send the SMS: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Message.Unknown: Unknown message error: 350')

Guess I will flash properly back to stock and stick with that for now

[biketool]

I HAVE to make a copypasta for the PPp modem issue, someone PLEASE put this on the wikis!!!
https://themodemdistro.com/efs_recovery
now your issue is not the usual softbrick PPp modem issue but surf the Biktorg website and is has great documentation for exactly this type of stuff.
I wish it were mentioned in the main git, Pine64, or mobian wiki.
for your issue look at https://themodemdistro.com/docs SMS Interface header

[dukla2000]

I HAVE to make a copypasta for the PPp modem issue, someone PLEASE put this on the wikis!!!
https://themodemdistro.com/efs_recovery
now your issue is not the usual softbrick PPp modem issue but surf the Biktorg website and is has great documentation for exactly this type of stuff.
I wish it were mentioned in the main git, Pine64, or mobian wiki.
...

The Pine64 wiki does link to Biktorgj's github (which in turn links to themodemdistro website).

...
for your issue look at https://themodemdistro.com/docs  SMS Interface header

I think I have read most of the github issues and documentation. My issue, as per the first bit I posted in code in my first post, is I can't send an SMS to my modem. And (my conclusion) is because I am unable to properly and completely flash the FOSS firmware. ./flashall runs just fine, except I then have a mix up - it is not FOSS to the extent I can send the SMS.

[biketool]

I HAVE to make a copypasta for the PPp modem issue, someone PLEASE put this on the wikis!!!
https://themodemdistro.com/efs_recovery
now your issue is not the usual softbrick PPp modem issue but surf the Biktorg website and is has great documentation for exactly this type of stuff.
I wish it were mentioned in the main git, Pine64, or mobian wiki.
...

The Pine64 wiki does link to Biktorgj's github (which in turn links to themodemdistro website).

I found the website by digging through bug reports in the git, it is not easy to find at all, which is unfortunate as it is a well designed website full of useful modem related fixes and tweaks.  I do see that there is now a link to the website at the bottom of the git page, he claims to be terrible with documenting writes amazing documentation website for his modem firmware and