Might have bricked my modem? Tried flashing the modem sdk. It failed so I flashed the recovery and tried again. Network Manager says modem is disabled, mmcli -L shows the modem, and mmcli -m any -e gives the following
Code:
error: couldn't enable modem: 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.DeviceNotReady: Couldn't set operating mode: QMI protocol error (52): DeviceNotReady
Getting a plain "ERROR." with echo "AT+QMBNCFG=list" | sudo atinout - /dev/ttyUSB2 - # also tried /dev/EG25.AT
I'm currently on the recovery flash from the github with the same errors. Same errors in Mobian Phosh as well as PMOS Plasma-Mobile. SIM still works in an android phone so nothing wrong with my carrier afaik. Google turns up a few people who got the same error with different phones and no one got any answers. Hopefully someone here has some more troubleshooting ideas than I came up with?
(02-12-2024, 09:21 AM)nekonosuke Wrote: [ -> ]Might have bricked my modem?
I'm currently on the recovery flash from the github with the same errors. Same errors in Mobian Phosh as well as PMOS Plasma-Mobile. SIM still works in an android phone so nothing wrong with my carrier afaik. Google turns up a few people who got the same error with different phones and no one got any answers. Hopefully someone here has some more troubleshooting ideas than I came up with?
It sounds like a few newer PinePhone Pros are having issues flashing the modem.
So I pulled logs for dmesg, eg25-manager, ModemManager, and NetworkManager. Everything seems to want to work normally except this from Modem Manager. It seems the power mode is going into "factory-test" mode and can't get out of it.
Code:
Feb 13 01:38:23 mobian systemd[1]: Starting ModemManager.service - Modem Manager...
Feb 13 01:38:23 mobian ModemManager[582]: <info> ModemManager (version 1.20.4) starting in system bus...
Feb 13 01:38:24 mobian systemd[1]: Started ModemManager.service - Modem Manager.
Feb 13 01:38:26 mobian ModemManager[582]: <info> [base-manager] couldn't check support for device '/sys/devices/platform/fe310000.mmc/mmc_host/mmc0/mmc0:0001/mmc0:0001:1': not supported by any plugin
Feb 13 01:38:26 mobian ModemManager[582]: <info> [base-manager] couldn't check support for device '/sys/devices/platform/usb@fe800000/fe800000.usb': not supported by any plugin
Feb 13 01:38:42 mobian ModemManager[582]: <warn> [ttyUSB0/probe] failed to parse QCDM version info command result: -7
Feb 13 01:38:48 mobian ModemManager[582]: <info> [device /sys/devices/platform/fe3c0000.usb/usb1/1-1] creating modem with plugin 'quectel' and '6' ports
Feb 13 01:38:48 mobian ModemManager[582]: <info> [base-manager] modem for device '/sys/devices/platform/fe3c0000.usb/usb1/1-1' successfully created
Feb 13 01:38:51 mobian ModemManager[582]: <warn> [modem0] couldn't load power state: Unhandled power state: 'factory-test' (2)
Feb 13 01:38:51 mobian ModemManager[582]: <warn> [modem0/sim0] couldn't load operator identifier: Couldn't get home network: QMI protocol error (16): 'NotProvisioned'
Feb 13 01:38:51 mobian ModemManager[582]: <warn> [modem0/sim0] couldn't load operator name: Couldn't get home network: QMI protocol error (16): 'NotProvisioned'
Feb 13 01:38:51 mobian ModemManager[582]: <warn> [modem0/sim0] couldn't load list of emergency numbers: uninitialized emergency numbers list
Feb 13 01:38:51 mobian ModemManager[582]: <warn> [modem0] couldn't load list of own numbers: Couldn't get MSISDN: QMI protocol error (16): 'NotProvisioned'
Feb 13 01:38:51 mobian ModemManager[582]: <warn> [modem0] couldn't load IMEI: Device doesn't report a valid IMEI
Feb 13 01:38:52 mobian ModemManager[582]: <info> [modem0] state changed (unknown -> disabled)
Feb 13 01:38:52 mobian ModemManager[582]: <info> [modem0] state changed (disabled -> enabling)
Feb 13 01:38:57 mobian ModemManager[582]: <warn> [modem0] couldn't enable interface: 'Couldn't set operating mode: QMI protocol error (52): 'DeviceNotReady''
Feb 13 01:38:57 mobian ModemManager[582]: <info> [modem0] 3GPP registration state changed (unknown -> unknown)
Feb 13 01:38:57 mobian ModemManager[582]: <info> [modem0] state changed (enabling -> disabled)
The first time I flashed the sdk firmware it failed to go into fastboot before continuing to flash all of the files but when I reflashed it manually I did successfully get fastboot to enable before continuing. Not sure what bearing that may have on this situation but is there some way to break out of factory test mode or did something get written in a way that can't be rewritten?
(02-13-2024, 09:26 AM)nekonosuke Wrote: [ -> ]So I pulled logs for dmesg, eg25-manager, ModemManager, and NetworkManager. Everything seems to want to work normally except this from Modem Manager. It seems the power mode is going into "factory-test" mode and can't get out of it.
The first time I flashed the sdk firmware it failed to go into fastboot before continuing to flash all of the files but when I reflashed it manually I did successfully get fastboot to enable before continuing. Not sure what bearing that may have on this situation but is there some way to break out of factory test mode or did something get written in a way that can't be rewritten?
Join to matrix room.
Find the link from Pinephone modem sdk github page:
https://github.com/the-modem-distro/pinephone_modem_sdk
It is failure in Quectel firmware but Biktorgj have fix for it. There are some license/juridistic questions why he can't publish it for everyone.
Just wanted to touch base back here for future readers.
The modem got stuck in Factory Test Mode after a failed flash which made getting into fastboot mode fail with most methods. After this I was able to recover the modem and then flash to the latest 0.7.4 release.
If you have one of these newer pinephone pros then be wary when flashing. Only do it manually following the documentation on the github. Always make sure you're in fastboot with lsusb before flashing any file.
If you run into issues, join the matrix room and you'll get sorted out