firmware-lenovo icon indicating copy to clipboard operation
firmware-lenovo copied to clipboard

Published 20 hours ago • verified publisher icon fwupd

[Qualcomm Snapdragon X55 5G] since firmware update -> not working anymore

Open j5k opened this issue 2 years ago • 19 comments

Since I made a firmware update from [1] to [2] the modem can't establish a connection anymore. For Windows exists a newer version [3]. Can you put this on LVFS and is the problem with this version solved?

[1] T99W175.F0.0.0.5.7.SC.004.076 (old) [2] T99W175.F0.1.0.0.9.SC.005.067 (current) [3] T99W175.F0.1.0.0.9.SC.005.075 (windows)

# journalctl
ModemManager[2916]: <info>  [modem0] simple connect started...
ModemManager[2916]: <info>  [modem0] simple connect state (3/8): enable
ModemManager[2916]: <info>  [modem0] state changed (disabled -> enabling)
ModemManager[2916]: <warn>  [modem0] Failure
ModemManager[2916]: <warn>  [modem0] Failure
ModemManager[2916]: <warn>  [modem0] couldn't enable interface: 'Invalid transition'
ModemManager[2916]: <info>  [modem0] state changed (enabling -> disabled)

j5k avatar Apr 26 '22 23:04 j5k

I can confirm that the update to T99W175.F0.1.0.0.9.SC.005.067 (T99W175.F0.1.0.0.9.DT.003.067 in my case) effectively soft-bricks the device as ModemManager's FCC unlock no longer works.

@j5k Are you sure that T99W175.F0.1.0.0.9.SC.005.075 will solve the issue? I previously had to downgrade to T99W175.F0.1.0.0.9.DT.003.055 to get it working, all newer versions use a modified FCC unlock approach that breaks ModemManager.

ginkel avatar Apr 27 '22 07:04 ginkel

I'm using firmware T99W175.F0.1.0.0.9_063 (thales branded) with ATT without issue. it is in a peplink balance router fwiw. Also, I have a HP t99w175 pcie and wondering if there is a easy way to re-brand this thing to a thales. I don't have access to any thales firmware, so if you have anything for it, it would be appreciated. thanks

jgsieve avatar Apr 28 '22 15:04 jgsieve

I can also confirm that the update to T99W175.F0.1.0.0.9.SC.005.067 has broken the FFC Unlock, and is now effectively soft-bricked.

error: couldn't enable the modem: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Retry: Invalid transition'

muelllu9 avatar May 03 '22 10:05 muelllu9

@mrhpearson should we pull this one back from stable?

hughsie avatar May 03 '22 12:05 hughsie

I'm checking with the WWAN team what happened here - but it's a holiday in Japan this week so won't know until next week the answer. I did ask last week and the FCC unlock mechanism wasn't supposed to have changed - but it certainly seems to have so I've been surprised by what has happened

@hughsie - I'll ping you offline for next steps. This one is potentially awkward.

mrhpearson avatar May 03 '22 13:05 mrhpearson

I'm checking with the WWAN team what happened here - but it's a holiday in Japan this week so won't know until next week the answer. I did ask last week and the FCC unlock mechanism wasn't supposed to have changed - but it certainly seems to have so I've been surprised by what has happened

My hypothesis is: The FCC unlock mechanism did not change from the (Windows) firmware published at pcsupport.lenovo.com. So the statement by the firmware team is most likely factually correct... It did, however, change from the v48 that is no longer available officially.

@mrhpearson Thanks for keeping us updated! While this is pretty frustrating from an end-user perspective, it must be even more so from your end...

ginkel avatar May 03 '22 13:05 ginkel

@ginkel No, I was not sure that T99W175.F0.1.0.0.9.SC.005.075 will solve the issue. I was asking about it.

But today I installed Windows on a second SSD to test this (newest) version. Same issue.

@mrhpearson If I can help in some way, please let me know.

j5k avatar May 04 '22 18:05 j5k

Thanks, Waiting for feedback from the WWAN team on the next steps. We have pulled the FW back to testing in the meantime. Will update ASAP

mrhpearson avatar May 04 '22 18:05 mrhpearson

Would it be possible to make the previous version available again on fwupd for an easy downgrade? Previous version: T99W175.F0.0.0.5.7.SC.004.076

muelllu9 avatar May 05 '22 15:05 muelllu9

We made some progress adding support for the new unlock mechanism to ModemManager / libqmi (thanks, Aleksander and Bjørn!).

Would anyone volunteer to help testing the fix before it gets merged into ModemManager? You need to compile and install the development version of libqmi from https://gitlab.freedesktop.org/mobile-broadband/libqmi and replace the fcc-unlock script in ModemManager with the version from https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/806...

ginkel avatar May 30 '22 21:05 ginkel

This week I'm very busy, but on the weekend I maybe find some time. Thanks a lot for your effort!

j5k avatar May 30 '22 21:05 j5k

Ok, my wonder has won ;-) It works!! But I can nothing say about the stability. I will test this the next few days...

Thanks!

j5k avatar May 30 '22 21:05 j5k 

May 30 23:42:34 testpc systemd[1]: Starting Modem Manager...
May 30 23:42:34 testpc ModemManager[485982]: <info>  ModemManager (version 1.18.8-1) starting in system bus...
May 30 23:42:34 testpc ModemManager[485982]: [qrtr] socket lookup from 1:0
May 30 23:42:34 testpc ModemManager[485982]: [qrtr] initial lookup finished
May 30 23:42:34 testpc systemd[1]: Started Modem Manager.
May 30 23:42:34 testpc audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ModemManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 30 23:42:34 testpc kernel: audit: type=1130 audit(1653946954.228:2231): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=ModemManager comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 30 23:42:34 testpc NetworkManager[3251]: <info>  [1653946954.2516] modem-manager: ModemManager now available
May 30 23:42:35 testpc ModemManager[485982]: opening device...
May 30 23:42:35 testpc ModemManager[485982]: cannot connect to proxy: Could not connect: Connection refused
May 30 23:42:35 testpc ModemManager[485982]: spawning new mbim-proxy (try 1)...
May 30 23:42:35 testpc ModemManager[485982]: [/dev/wwan0mbim0] Couldn't find descriptors file, possibly not using cdc_mbim
May 30 23:42:35 testpc ModemManager[485982]: [/dev/wwan0mbim0] Fallback to default max control message size: 4096
May 30 23:42:36 testpc ModemManager[485982]: <info>  [wwan0mbim0/mbim] MBIM device is not QMI capable
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] channel destroyed
May 30 23:42:36 testpc ModemManager[485982]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:0d.0/usb2/2-3/2-3.4/2-3.4.4/2-3.4.4.3': not supported by any plugin
May 30 23:42:36 testpc ModemManager[485982]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin
May 30 23:42:36 testpc ModemManager[485982]: <info>  [device /sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0] creating modem with plugin 'foxconn' and '4' ports
May 30 23:42:36 testpc ModemManager[485982]: <info>  [base-manager] modem for device '/sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0' successfully created
May 30 23:42:36 testpc ModemManager[485982]: opening device...
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] Couldn't find descriptors file, possibly not using cdc_mbim
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] Fallback to default max control message size: 4096
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] Opening device with flags 'version-info, proxy, mbim, expect-indications'...
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] created endpoint
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] creating MBIM device...
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] MBIM device created
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] opening MBIM device...
May 30 23:42:36 testpc ModemManager[485982]: opening device...
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] Couldn't find descriptors file, possibly not using cdc_mbim
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] Fallback to default max control message size: 4096
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] MBIM device open
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] Checking version info (15 retries)...
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] QMI Device supports 35 services:
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    ctl (1.5)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    wds (1.193)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    dms (1.79)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    nas (1.25)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    qos (1.18)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    wms (1.10)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    auth (1.14)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    at (1.6)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    voice (2.1)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    cat2 (2.24)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    uim (1.77)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    pbm (1.4)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    test (1.0)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    loc (2.131)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    sar (1.0)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    ims (1.91)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    ts (1.0)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    tmd (1.0)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    wda (1.24)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    csvt (1.6)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    imsa (1.44)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    coex (1.0)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    pdc (1.0)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    rfrpe (1.0)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    dsd (1.67)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    unknown [0x2d] (1.3)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    unknown [0x30] (1.12)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    unknown [0x31] (1.0)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    unknown [0x44] (1.4)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    unknown [0x49] (1.7)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    unknown [0x4a] (1.1)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    unknown [0x4b] (1.3)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    unknown [0x4c] (1.0)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    unknown [0x4d] (1.4)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0]    unknown [0x4e] (1.2)
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] Enabling QMI indications via MBIM...
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] enabled QMI indications via MBIM
May 30 23:42:36 testpc ModemManager[485982]: <info>  [modem0/wwan0mbim0/mbim] MBIM device is QMI capable
May 30 23:42:36 testpc ModemManager[485982]: [/dev/wwan0mbim0] Allocating new client ID...
May 30 23:42:37 testpc ModemManager[485982]: [/dev/wwan0mbim0] Registered 'dms' (version 1.79) client with ID '11'
May 30 23:42:37 testpc ModemManager[485982]: [/dev/wwan0mbim0] Allocating new client ID...
May 30 23:42:37 testpc ModemManager[485982]: [/dev/wwan0mbim0] Registered 'nas' (version 1.25) client with ID '4'
May 30 23:42:37 testpc ModemManager[485982]: [/dev/wwan0mbim0] Allocating new client ID...
May 30 23:42:37 testpc ModemManager[485982]: [/dev/wwan0mbim0] Registered 'loc' (version 2.131) client with ID '1'
May 30 23:42:37 testpc ModemManager[485982]: [/dev/wwan0mbim0] Allocating new client ID...
May 30 23:42:37 testpc ModemManager[485982]: [/dev/wwan0mbim0] Registered 'pdc' (version 1.0) client with ID '1'
May 30 23:42:37 testpc ModemManager[485982]: <info>  [modem0] QMI-based capability and mode switching support enabled
May 30 23:42:38 testpc ModemManager[485982]: <warn>  [modem0/sim0] couldn't load list of emergency numbers: Failed to parse CRSM query result '+CRSM: 148,8,""'
May 30 23:42:38 testpc ModemManager[485982]: <warn>  [modem0/sim0] couldn't load list of preferred networks: Operation not allowed
May 30 23:42:38 testpc ModemManager[485982]: <warn>  [modem0] couldn't setup carrier config: No such file or directory
May 30 23:42:38 testpc ModemManager[485982]: <info>  [modem0] state changed (unknown -> disabled)
May 30 23:42:41 testpc ModemManager[485982]: <info>  [modem0] state changed (disabled -> enabling)
May 30 23:42:42 testpc ModemManager[485982]: <warn>  [modem0] OperationNotAllowed
May 30 23:42:42 testpc ModemManager[485982]: <info>  [modem0] power state updated: on
May 30 23:42:42 testpc ModemManager[485982]: <info>  [modem0] 3GPP registration state changed (unknown -> searching)
May 30 23:42:42 testpc ModemManager[485982]: <info>  [modem0] state changed (enabling -> searching)
May 30 23:42:43 testpc ModemManager[485982]: <info>  [modem0] 3GPP registration state changed (searching -> registering)
May 30 23:42:43 testpc ModemManager[485982]: <info>  [modem0] 3GPP registration state changed (registering -> home)
May 30 23:42:43 testpc ModemManager[485982]: <info>  [modem0] state changed (searching -> registered)
May 30 23:42:47 testpc ModemManager[485982]: <info>  [modem0] simple connect started...
May 30 23:42:47 testpc ModemManager[485982]: <info>  [modem0] simple connect state (4/8): wait to get fully enabled
May 30 23:42:47 testpc ModemManager[485982]: <info>  [modem0] simple connect state (5/8): register
May 30 23:42:47 testpc ModemManager[485982]: <info>  [modem0] simple connect state (6/8): bearer
May 30 23:42:47 testpc ModemManager[485982]: <info>  [modem0] simple connect state (7/8): connect
May 30 23:42:47 testpc ModemManager[485982]: <info>  [modem0] state changed (registered -> connecting)
May 30 23:42:47 testpc ModemManager[485982]: <info>  [modem0] state changed (connecting -> connected)
May 30 23:42:47 testpc ModemManager[485982]: <info>  [modem0] simple connect state (8/8): all done

j5k avatar May 30 '22 21:05 j5k

Ok, my wonder has won ;-) It works!! But I can nothing say about the stability. I will test this the next few days...

Excellent, thanks for your feedback! :-)

ginkel avatar May 30 '22 21:05 ginkel

Works here! This is what windows installed

T99W175.F0.1.0.0.9.TO.006.079

cowboyrushforth avatar May 30 '22 23:05 cowboyrushforth

As a datapoint, I'm on T99W175.F0.0.0.5.7.VZ.006 on an X1 Nano with Fedora 36 and it's failing with 'Invalid transition' even after installing the latest libqmi and the fcc-unlock mentioned above.

davide125 avatar Jul 08 '22 17:07 davide125

Fedota 37 beta with x55 modem, Still failing with 'Invalid transition'

plumlis avatar Sep 20 '22 16:09 plumlis

@plumlis Please check https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/806, newer version of ModemManager is needed for "Invalid transition" fix, which is not in Fedora 37 yet

xapienz avatar Nov 07 '22 08:11 xapienz

could anyone plz confirm if this will work in my desktop? or only lenovo? thank you

murad0522 avatar Jan 27 '23 11:01 murad0522