FM350-GL (installed in ThinkPad P1 Gen 5)

[Aleksander Morgado]

On Wed, Sep 13, 2023 at 12:54 PM Thilo-Alexander Ginkel
<thilo at ginkel.com> wrote:
>
> On Tue, Sep 12, 2023 at 1:31 PM Bjørn Mork <bjorn at mork.no> wrote:
>>
>> > Turns out the challenge needs to be requested via --set-fcc-lock=0,0.
>>
>> Right.  Makes sense.
>>
>> > Still, I can't get a valid unlock.
>>
>> And those challenge input values are correct?  The firware isn't
>> expecting something other than 0,0?
>
>
> I patched the Linux kernel's WWAN driver to add logging of the data sent to/from the modem and as it turns out the MBIM code path isn't even used by the official tool (although both the firmware and the unlock tool implement it). Instead AT commands are being used.
>
> Will this work for ModemManeger's firmware unlock? So far all scripts I have seen seem to rely on the MBIM device.
>

We can make this work if needed, yes. The main issue is that we don't
have an "AT proxy" as we do with QMI or MBIM, so it would require some
sync with MM to ensure we're not touching the AT port at the same
time.


-- 
Aleksander