After backing up the EMMC, baseband and Qualcomm blobs, I tried installing the Debian image on the openstick repository
Once done flashing the appropriate boot image and transplanting the blobs, everything works just fine, and the SIM APN gets recognized automatically.
Hello @reefbrallis , can you elaborate on this ?
How did you backup blobs and put them back ?
Regards,
Fabien
In the meantime I found the answer to my question in the comments.
To dump the whole flash using this edl tool(https://github.com/bkerler/edl). In case you brick it.
$ adb reboot edl
$ edl rl dumps --skip=userdata --genxml
or
$ edl rf flash.bin
To flash back on the openstick
$ edl qfil rawprogram0.xml patch0.xml .
I have also an UFI001C and replayed as indicated here:
Modem is well detected
root@openstick:/# nmcli c
NAME UUID TYPE DEVICE
USB 89be98d0-f5e6-4432-ae40-caf8693164de ethernet usb0
Wired connection 1 e07c048d-9efa-30fa-9b3a-ed744eb30e34 ethernet --
modem ead26b9f-2b9e-44dd-87d0-3e9cb826bf88 gsm --
also
root@openstick:/# mmcli -L
/org/freedesktop/ModemManager1/Modem/0 [1] 0
However it seems the SIM card is not powered up:
root@openstick:/# mmcli -m 0
-----------------------------------
General | path: /org/freedesktop/ModemManager1/Modem/0
| device id: 6e2290d10230978b4ab0ad4aeb613c54d70f3f2d
-----------------------------------
Hardware | manufacturer: 1
| model: 0
| firmware revision: MPSS.DPM.2.0.2.c1-00178-M8936FAAAANUZM-1D 1 [Nov 04 2016 02:00:00]
| carrier config: Commercial-CSFB-SS-CMCC
| carrier config revision: 02011866
| h/w revision: 10000
| supported: gsm-umts, lte
| current: gsm-umts, lte
| equipment id: 000000000000000
-----------------------------------
System | device: qcom-soc
| drivers: qcom-q6v5-mss, bam-dmux
| plugin: qcom-soc
| primary port: wwan0qmi0
| ports: wwan0 (net), wwan0at0 (at), wwan0qmi0 (qmi), wwan1 (net),
| wwan2 (net), wwan3 (net), wwan4 (net), wwan5 (net), wwan6 (net),
| wwan7 (net)
-----------------------------------
Status | state: failed
| failed reason: sim-missing
| **power state: off**
| signal quality: 0% (cached)
-----------------------------------
Modes | supported: allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 3g, 4g; preferred: 4g
| allowed: 3g, 4g; preferred: 3g
| current: allowed: any; preferred: none
-----------------------------------
Bands | supported: utran-1, utran-5, utran-8, eutran-1, eutran-3, eutran-5,
| eutran-8, eutran-38, eutran-39, eutran-40, eutran-41
-----------------------------------
IP | supported: ipv4, ipv6, ipv4v6
I have found @sorine was mentioning a potential swap of GPIO here: UF896 - Qualcomm MSM8916 LTE router ~384MiB RAM/2.4GiB flash, Android: OpenWrt? - #128 by sorine but this was for the other openstick UF896.
Moreover this is for the Openwrt build that was never able to detect my modem when built.
So I have 2 tracks, one finding the Debian source tree and try to swap GPIO to make the SIM powered up, or second one more complex (at least it seems) to fix the modem detection issue and hoping that the GPIO are in the right order or trying to solve it.
Do some experts here have other advises ?
EDIT1: In fact the modem is well detecting a few seconds after booting.
It then stop working after this error seen in syslog:
[ 38.833175] qcom-q6v5-mss 4080000.remoteproc: fatal error received: sys_m.c:603:THIS IS INTENTIONAL RESET, NO RAMDUMP EXPECTED, smp2p write ret =
[ 38.833314] remoteproc remoteproc1: crash detected in 4080000.remoteproc: type fatal error
[ 38.847751] remoteproc remoteproc1: handling crash #1 in 4080000.remoteproc
[ 40.636760] qcom-wcnss-pil a204000.remoteproc: unexpected response to sysmon event
[ 40.636799] remoteproc remoteproc1: stopped remote processor 4080000.remoteproc
[ 40.645836] qcom-wcnss-pil a204000.remoteproc: unexpected response to sysmon event
[ 40.697259] qcom-q6v5-mss 4080000.remoteproc: MBA booted without debug policy, loading mpss
[ 41.332011] remoteproc remoteproc1: remote processor 4080000.remoteproc is now up
however the last line seems to indicate it is up again.
Maybe the modem driver qcom-q6v5 embedded into https://github.com/OpenStick/OpenStick is buggy ?
any update, my board is UZ801,
My UZ801 still in fastboot mode, how can I reboot to normal. I unplug and replug to PC but it still in fastboot mode. Please help!
Hello !
have you tried?
fastboot reboot
Thank you! I try and work fine, I install openwrt but I can get back to stock rom.
Good to know !
How did you managed to install openwrt ?
On my new devices UZ801 I am unable to launch ADB, nor FASTBOOT, and so not able to flash openwrt.
adb devices return nothing, only EDL is working by connecting USB pin 1 and 2 to enter this mode.
I recommend do not install openwrt, only 3G work when install openwrt on UZ801, 4G not work. If you really want install Openwrt on UZ801, use adb connect with port 7628 not default port.
Can someone make another dump of the stock firmware of the UF896 v1.1 using EDL
edl rl dumps --skip=userdata --genxml
Screwed up, and it won't boot any more. The dump from @Capt.Insano doesn't seem to work and is missing the patch0.xml
Thanks !
Hi,
You should go there :
Once up and running, please tell whether the LTE is working as expected
for you.
I have not managed to get something workable yet.
Thanks
Thanks so much.
That worked. I have a functioning stick again. Now back to breaking it again 
lte connection drops after approximatly five minutes
does anybody have a hint? This happens regardless whether I configure the connection using /etc/config/network or by invoking mmcli -m 0 --simple-connect=..... It is also annoying that ifconfig always shows zero transferred bytes even if something has been downloaded. The last messages from logread with "mmcli -G DEBUG" are
Tue Mar 21 07:27:15 2023 daemon.debug [2789]: [/dev/rpmsg0] Received generic indication (translated)... <<<<<< QMUX: <<<<<< length = 16 <<<<<< flags = 0x80 <<<<<< service = "wds" <<<<<< client = 2 <<<<<< QMI: <<<<<< flags = "indication" <<<<<< transaction = 40 <<<<<< tlv_length = 4 <<<<<< message = "Event Report" (0x0001) <<<<<< TLV: <<<<<< type = "Dormancy Status" (0x18) <<<<<< length = 1 <<<<<< value = 01 <<<<<< translated = traffic-channel-dormant
Tue Mar 21 07:27:15 2023 daemon.debug [2789]: <debug> [modem0/bearer1] got QMI WDS event report
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received message... <<<<<< RAW: <<<<<< length = 29 <<<<<< data = 01:1C:00:80:01:02:04:29:00:01:00:10:00:28:04:00:04:00:00:00:22:02:00:01:00:1F:01:00:02
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received generic indication (translated)... <<<<<< QMUX: <<<<<< length = 28 <<<<<< flags = 0x80 <<<<<< service = "wds" <<<<<< client = 2 <<<<<< QMI: <<<<<< flags = "indication" <<<<<< transaction = 41 <<<<<< tlv_length = 16 <<<<<< message = "Event Report" (0x0001) <<<<<< TLV: <<<<<< type = "Data Call Address Family" (0x28) <<<<<< length = 4 <<<<<< value = 04:00:00:00 <<<<<< translated = ipv4 <<<<<< TLV: <<<<<< type = "Data Call Type" (0x22) <<<<<< length = 2 <<<<<< value = 01:00 <<<<<< translated = [ data_call_type = 'embedded' tethered_call_type = 'non-tethered' ] <<<<<< TLV: <<<<<< type = "Data Call Status" (0x1f) <<<<<< length = 1 <<<<<< value = 02 <<<<<< translated = terminated
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received message... <<<<<< RAW: <<<<<< length = 34 <<<<<< data = 01:21:00:80:01:02:04:2A:00:22:00:15:00:01:02:00:01:00:10:02:00:01:00:11:04:00:00:00:00:00:12:01:00:04
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received generic indication (translated)... <<<<<< QMUX: <<<<<< length = 33 <<<<<< flags = 0x80 <<<<<< service = "wds" <<<<<< client = 2 <<<<<< QMI: <<<<<< flags = "indication" <<<<<< transaction = 42 <<<<<< tlv_length = 21 <<<<<< message = "Packet Service Status" (0x0022) <<<<<< TLV: <<<<<< type = "Connection Status" (0x01) <<<<<< length = 2 <<<<<< value = 01:00 <<<<<< translated = [ status = 'disconnected' reconfiguration_required = 'no' ] <<<<<< TLV: <<<<<< type = "Call End Reason" (0x10) <<<<<< length = 2 <<<<<< value = 01:00 <<<<<< translated = generic-unspecified <<<<<< TLV: <<<<<< type = "Verbose Call End Reason" (0x11) <<<<<< length = 4 <<<<<< value = 00:00:00:00 <<<<<< translated = [ type = '(null)' reason = '0' ] <<<<<< TLV: <<<<<< type = "IP Family" (0x12) <<<<<< length = 1 <<<<<< value = 04 <<<<<< translated = ipv4
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received message... <<<<<< RAW: <<<<<< length = 34 <<<<<< data = 01:21:00:80:01:01:04:04:00:22:00:15:00:01:02:00:01:00:10:02:00:01:00:11:04:00:00:00:00:00:12:01:00:04
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received generic indication (translated)... <<<<<< QMUX: <<<<<< length = 33 <<<<<< flags = 0x80 <<<<<< service = "wds" <<<<<< client = 1 <<<<<< QMI: <<<<<< flags = "indication" <<<<<< transaction = 4 <<<<<< tlv_length = 21 <<<<<< message = "Packet Service Status" (0x0022) <<<<<< TLV: <<<<<< type = "Connection Status" (0x01) <<<<<< length = 2 <<<<<< value = 01:00 <<<<<< translated = [ status = 'disconnected' reconfiguration_required = 'no' ] <<<<<< TLV: <<<<<< type = "Call End Reason" (0x10) <<<<<< length = 2 <<<<<< value = 01:00 <<<<<< translated = generic-unspecified <<<<<< TLV: <<<<<< type = "Verbose Call End Reason" (0x11) <<<<<< length = 4 <<<<<< value = 00:00:00:00 <<<<<< translated = [ type = '(null)' reason = '0' ] <<<<<< TLV: <<<<<< type = "IP Family" (0x12) <<<<<< length = 1 <<<<<< value = 04 <<<<<< translated = ipv4
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: <debug> [modem0/bearer1] got QMI WDS event report
Tue Mar 21 07:27:24 2023 daemon.info [2789]: <info> [modem0/bearer1] verbose call end reason (0,0): [(null)] (null)
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Sent message... <<<<<< RAW: <<<<<< length = 61 <<<<<< data = 01:3C:00:00:01:02:00:0E:00:01:00:30:00:1E:01:00:00:1C:01:00:00:1B:01:00:00:1A:01:00:00:19:01:00:00:18:01:00:00:17:01:00:00:15:01:00:00:14:01:00:00:13:01:00:00:12:01:00:00:10:01:00:00
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Sent generic request (translated)... <<<<<< QMUX: <<<<<< length = 60 <<<<<< flags = 0x00 <<<<<< service = "wds" <<<<<< client = 2 <<<<<< QMI: <<<<<< flags = "none" <<<<<< transaction = 14 <<<<<< tlv_length = 48 <<<<<< message = "Set Event Report" (0x0001) <<<<<< TLV: <<<<<< type = "Extended Data Bearer Technology" (0x1e) <<<<<< length = 1 <<<<<< value = 00 <<<<<< translated = no <<<<<< TLV: <<<<<< type = "Limited Data System Status" (0x1c) <<<<<< length = 1 <<<<<< value = 00 <<<<<< translated = no <<<<<< TLV: <<<<<< type = "Uplink Flow Control" (0x1b) <<<<<< length = 1 <<<<<< value = 00 <<<<<< translated = no <<<<<< TLV: <<<<<< type = "Data Systems" (0x1a) <<<<<< length = 1 <<<<<< value = 00 <<<<<< translated = no <<<<<< TLV: <<<<<< type = "EVDO PM Change" (0x19) <<<<<< length = 1 <<<<<< value = 00 <<<<<< translated = no <<
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: <debug> [modem0/wwan0/net] port now disconnected
Tue Mar 21 07:27:24 2023 daemon.info [2789]: <info> [modem0] state changed (connected -> registered)
Tue Mar 21 07:27:24 2023 daemon.info [2789]: <info> [modem0/bearer1] connection #1 finished: duration 266s, tx: 4916 bytes, rx: 700 bytes
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received message... <<<<<< RAW: <<<<<< length = 36 <<<<<< data = 01:23:00:80:01:02:04:2B:00:01:00:17:00:24:14:00:00:02:00:00:80:00:00:00:00:00:00:01:00:00:00:00:00:00:00:00
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received generic indication (translated)... <<<<<< QMUX: <<<<<< length = 35 <<<<<< flags = 0x80 <<<<<< service = "wds" <<<<<< client = 2 <<<<<< QMI: <<<<<< flags = "indication" <<<<<< transaction = 43 <<<<<< tlv_length = 23 <<<<<< message = "Event Report" (0x0001) <<<<<< TLV: <<<<<< type = "Data Systems" (0x24) <<<<<< length = 20 <<<<<< value = 00:02:00:00:80:00:00:00:00:00:00:01:00:00:00:00:00:00:00:00 <<<<<< translated = [ preferred_network_type = '3gpp' networks = '{ [0] = '[ network_type = '3gpp' rat_mask = '32768' so_mask = '0' ] ' [1] = '[ network_type = '3gpp2' rat_mask = '0' so_mask = '0' ] '}' ]
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received message... <<<<<< RAW: <<<<<< length = 20 <<<<<< data = 01:13:00:80:01:02:04:2C:00:01:00:07:00:20:04:00:00:00:00:00
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received generic indication (translated)... <<<<<< QMUX: <<<<<< length = 19 <<<<<< flags = 0x80 <<<<<< service = "wds" <<<<<< client = 2 <<<<<< QMI: <<<<<< flags = "indication" <<<<<< transaction = 44 <<<<<< tlv_length = 7 <<<<<< message = "Event Report" (0x0001) <<<<<< TLV: <<<<<< type = "Preferred Data System" (0x20) <<<<<< length = 4 <<<<<< value = 00:00:00:00 <<<<<< translated = unknown
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received message... <<<<<< RAW: <<<<<< length = 36 <<<<<< data = 01:23:00:80:01:01:04:05:00:01:00:17:00:24:14:00:00:02:00:00:80:00:00:00:00:00:00:01:00:00:00:00:00:00:00:00
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received generic indication (translated)... <<<<<< QMUX: <<<<<< length = 35 <<<<<< flags = 0x80 <<<<<< service = "wds" <<<<<< client = 1 <<<<<< QMI: <<<<<< flags = "indication" <<<<<< transaction = 5 <<<<<< tlv_length = 23 <<<<<< message = "Event Report" (0x0001) <<<<<< TLV: <<<<<< type = "Data Systems" (0x24) <<<<<< length = 20 <<<<<< value = 00:02:00:00:80:00:00:00:00:00:00:01:00:00:00:00:00:00:00:00 <<<<<< translated = [ preferred_network_type = '3gpp' networks = '{ [0] = '[ network_type = '3gpp' rat_mask = '32768' so_mask = '0' ] ' [1] = '[ network_type = '3gpp2' rat_mask = '0' so_mask = '0' ] '}' ]
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received message... <<<<<< RAW: <<<<<< length = 20 <<<<<< data = 01:13:00:80:01:02:02:0E:00:01:00:07:00:02:04:00:00:00:00:00
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received generic response (translated)... <<<<<< QMUX: <<<<<< length = 19 <<<<<< flags = 0x80 <<<<<< service = "wds" <<<<<< client = 2 <<<<<< QMI: <<<<<< flags = "response" <<<<<< transaction = 14 <<<<<< tlv_length = 7 <<<<<< message = "Set Event Report" (0x0001) <<<<<< TLV: <<<<<< type = "Result" (0x02) <<<<<< length = 4 <<<<<< value = 00:00:00:00 <<<<<< translated = SUCCESS
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: <debug> [modem0] data systems update, preferred network: 3gpp
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Sent message... <<<<<< RAW: <<<<<< length = 13 <<<<<< data = 01:0C:00:00:01:01:00:0A:00:85:00:00:00
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Sent generic request (translated)... <<<<<< QMUX: <<<<<< length = 12 <<<<<< flags = 0x00 <<<<<< service = "wds" <<<<<< client = 1 <<<<<< QMI: <<<<<< flags = "none" <<<<<< transaction = 10 <<<<<< tlv_length = 0 <<<<<< message = "Get LTE Attach Parameters" (0x0085)
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received message... <<<<<< RAW: <<<<<< length = 20 <<<<<< data = 01:13:00:80:01:01:02:0A:00:85:00:07:00:02:04:00:01:00:4A:00
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: [/dev/rpmsg0] Received generic response (translated)... <<<<<< QMUX: <<<<<< length = 19 <<<<<< flags = 0x80 <<<<<< service = "wds" <<<<<< client = 1 <<<<<< QMI: <<<<<< flags = "response" <<<<<< transaction = 10 <<<<<< tlv_length = 7 <<<<<< message = "Get LTE Attach Parameters" (0x0085) <<<<<< TLV: <<<<<< type = "Result" (0x02) <<<<<< length = 4 <<<<<< value = 01:00:4A:00 <<<<<< translated = FAILURE: InformationUnavailable
Tue Mar 21 07:27:24 2023 daemon.debug [2789]: <debug> [modem0] couldn't load initial default bearer properties: Couldn't get LTE attach parameters: QMI protocol error (74): 'InformationUnavailable'
Tue Mar 21 07:27:40 2023 daemon.debug [2789]: [/dev/rpmsg0] Received message... <<<<<< RAW: <<<<<< length = 34 <<<<<< data = 01:21:00:80:03:01:04:08:00:24:00:15:00:01:06:00:00:02:01:00:01:00:11:01:00:00:22:05:00:00:02:00:00:00
Tue Mar 21 07:27:40 2023 daemon.debug [2789]: [/dev/rpmsg0] Received generic indication (translated)... <<<<<< QMUX: <<<<<< length = 33 <<<<<< flags = 0x80 <<<<<< service = "nas" <<<<<< client = 1 <<<<<< QMI: <<<<<< flags = "indication" <<<<<< transaction = 8 <<<<<< tlv_length = 21 <<<<<< message = "Serving System" (0x0024) <<<<<< TLV: <<<<<< type = "Serving System" (0x01) <<<<<< length = 6 <<<<<< value = 00:02:01:00:01:00 <<<<<< translated = [ registration_state = 'not-registered' cs_attach_state = 'detached' ps_attach_state = 'attached' selected_network = 'unknown' radio_interfaces = '{ [0] = 'none '}' ] <<<<<< TLV: <<<<<< type = "Data Service Capability" (0x11) <<<<<< length = 1 <<<<<< value = 00 <<<<<< translated = {} <<<<<< TLV: <<<<<< type = "Detailed Service Status" (0x22) <<<<<< length = 5 <<<<<< value = 00:02:00:00:00 <<<<<< translated = [ status = 'none' capability = 'ps' hdr_status = 'none' hdr_hybrid = 'no' forbidde
Tue Mar 21 07:27:40 2023 daemon.debug [2789]: <debug> [modem0] no 3GPP info given...
Tue Mar 21 07:27:40 2023 daemon.info [2789]: <info> [modem0] 3GPP registration state changed (home -> unknown)
Tue Mar 21 07:27:40 2023 daemon.debug [2789]: <debug> [modem0] consolidated registration state: cs 'unknown', ps 'unknown', eps 'unknown', 5gs 'unknown' --> 'unknown'
Tue Mar 21 07:27:40 2023 daemon.debug [2789]: <debug> [modem0] 3GPP location updated (MCCMNC: '<none>', location area code: 'FFFE', tracking area code: '008CE8', cell ID: '00EE2E1B')
Tue Mar 21 07:27:40 2023 daemon.debug [2789]: <debug> [modem0/bearer0] bearer not allowed to connect, not registered in 3GPP network
Tue Mar 21 07:27:40 2023 daemon.debug [2789]: <debug> [modem0/bearer1] bearer not allowed to connect, not registered in 3GPP network
Tue Mar 21 07:27:40 2023 daemon.info [2789]: <info> [modem0] state changed (registered -> enabled)
Tue Mar 21 07:27:40 2023 daemon.debug [2789]: <debug> [modem0] access technology changed (lte -> unknown)
Tue Mar 21 07:27:40 2023 daemon.debug [2789]: <debug> [modem0] 3GPP location updated (MCCMNC: '<none>', location area code: '0000', tracking area code: '000000', cell ID: '00000000')
Tue Mar 21 07:27:40 2023 daemon.warn [2789]: <warn> [modem0] couldn't load operator code: Current operator MCC/MNC is still unknown
Tue Mar 21 07:27:40 2023 daemon.warn [2789]: <warn> [modem0] couldn't load operator name: Current operator id is still unknown
Did you find out what to do with that?
I've got debian running and networkmanager shows the modem but ModemManager does not... I'm stuck at the moment. I'm wondering whether I need to flash the baseband, but I'm not even sure how to do that. I would assume that modemst1 and modemst2 are the basebands... and those are backed up in the base/flash.sh script and then flashed back again... so then baseband should be unchanged from oem.
I would actually prefer using OpenWRT on the stick but from what I've gathered from this thread is that modem is not working but is on Debian. So I guess it's not a driver issue but a matter of tinkering?
With OpenStick-debian I had to extract the firmware according to https://github.com/OpenStick/OpenStick/issues/33#issuecomment-1309835024 and copy the files to /lib/firmware. This changed state=sim card missing to connected.
If you select the correct model in openwrt the firmware files are already included.
But both variants have the problem, that lte gets disconnected after five minutes. The original firmware was more stable (1 week).
Thanks for the reply. I have extracted the firmware from the edl backup but modemmanager doesn't even recognize my modem:
# nmcli c
NAME UUID TYPE DEVICE
USB 024ae1c4-35d3-48ea-b543-79b220de0102 ethernet usb0
modem 50adff5d-c0b9-4330-ab41-de9b888b0397 gsm --
root@openstick:/# mmcli -L
No modems were found
root@openstick:/# mmcli -m 0
error: couldn't find modem
root@openstick:/# ls -l /lib/firmware
total 43128
-rw-r--r-- 1 root root 230272 Mar 21 2023 mba.mbn
-rw-r--r-- 1 root root 1012 Mar 21 2023 modem.b00
-rw-r--r-- 1 root root 7400 Mar 21 2023 modem.b01
-rw-r--r-- 1 root root 4212 Mar 21 2023 modem.b02
-rw-r--r-- 1 root root 5376 Mar 21 2023 modem.b03
-rw-r--r-- 1 root root 205152 Mar 21 2023 modem.b04
-rw-r--r-- 1 root root 3398848 Mar 21 2023 modem.b05
-rw-r--r-- 1 root root 3099238 Mar 21 2023 modem.b06
-rw-r--r-- 1 root root 342860 Mar 21 2023 modem.b07
-rw-r--r-- 1 root root 175904 Mar 21 2023 modem.b08
-rw-r--r-- 1 root root 44864 Mar 21 2023 modem.b10
-rw-r--r-- 1 root root 130024 Mar 21 2023 modem.b15
-rw-r--r-- 1 root root 765160 Mar 21 2023 modem.b16
-rw-r--r-- 1 root root 12823120 Mar 21 2023 modem.b17
-rw-r--r-- 1 root root 663520 Mar 21 2023 modem.b18
-rw-r--r-- 1 root root 6174048 Mar 21 2023 modem.b19
-rw-r--r-- 1 root root 2738780 Mar 21 2023 modem.b20
-rw-r--r-- 1 root root 76784 Mar 21 2023 modem.b23
-rw-r--r-- 1 root root 395612 Mar 21 2023 modem.b24
-rw-r--r-- 1 root root 7983104 Mar 21 2023 modem.b25
-rw-r--r-- 1 root root 128288 Mar 21 2023 modem.b27
-rw-r--r-- 1 root root 1048576 Mar 21 2023 modem.b28
-rw-r--r-- 1 root root 8412 Mar 21 2023 modem.mdt
drwxr-xr-x 3 root root 4096 Mar 21 2023 qcom
-rw-r--r-- 1 root root 436 Mar 21 2023 wcnss.b00
-rw-r--r-- 1 root root 6824 Mar 21 2023 wcnss.b01
-rw-r--r-- 1 root root 13064 Mar 21 2023 wcnss.b02
-rw-r--r-- 1 root root 61440 Mar 21 2023 wcnss.b04
-rw-r--r-- 1 root root 2860948 Mar 21 2023 wcnss.b06
-rw-r--r-- 1 root root 52 Mar 21 2023 wcnss.b09
-rw-r--r-- 1 root root 655360 Mar 21 2023 wcnss.b10
-rw-r--r-- 1 root root 43304 Mar 21 2023 wcnss.b11
-rw-r--r-- 1 root root 7260 Mar 21 2023 wcnss.mdt
drwxr-xr-x 3 root root 4096 Mar 21 2023 wlan
On first try I copied the files into the firmware directory and noticed that my firmware had fewer files and was missing a few of the .b##, so some of the files were not overwritten... So on my second attempt I cleared the directory and started clean, except I left the two directories qcom and wlan intact. That had no effect.
Am I missing a driver?
This firmware and driver magic is over my head. But your result is interesting. I also had some missing files in my first dump. A second dump was identical to https://github.com/kirdesde/qcom-firmware/blob/main/uf896-modem.bin and containes more files.
Got a few other firmware archives and pushed to the stick... No change... tried upgrading debian to bookworm since mobian has no repo for bullseye and that bricked the stick... my second stick. 
I think I'll call it for now... Hopefully we will get information on how to reset it into EDL mode when we get a totally unresponsive device, like I have.
I assume you already tried to shorten the pins shown here while plugging. My device sometimes woke up in edl or fastboot mode.
Yeah I tried shorting them with a paper clip and plugging in. Does nothing. The pins seem to be covered with a thin film, I scraped that off... still no go. The SoC warms up but there is no response through the USB... Doesn't show up in lsusb, no messages in dmesg, EDL doesn't find it.