Can't get my Modem out of Low Power Mode

[michael.bachinger]

I accidentally flashed a new firmware onto the Modem and now i can’t get it out of low power mode or flash to another firmware.

AT!IMPREF?
!IMPREF: 
 preferred fw version:    02.24.05.06
 preferred carrier name:  GENERIC
 preferred config name:   GENERIC_002.026_000
 preferred subpri index:  000
 current fw version:      02.33.03.00
 current carrier name:    GENERIC
 current config name:     GENERIC_002.026_000
 current subpri index:    000

 fw version mismatch

OK

This is the version mismatch i have, but everytime i try to flash another firmware onto it, i get

FDT version: 1.0.1806.0
Awaiting adapter ...
Enabling selective suspend ...
Firmware download failed.
Primary error code: 82 - Failed in checking modem mode.
Secondary error code: 0 - Not applicable.
Device error code: 0x0 - Unknown device error code.

Preexisting images information:
        Current:
                Firmware:
                        ImageId:
                        BuildId:
                Configuration:
                        ImageId:
                        BuildId:
Final images information:
        Current:
                Firmware:
                        ImageId:
                        BuildId:
                Configuration:
                        ImageId:
                        BuildId:

OEM PRI:

IMEI:

Total time elapsed: 172 ms.


Images downloaded:


Press Enter to continue ...

i need a link for the old firmware (since i only have newer one) and a way to flash it to the modem, but i simply don’t know how to do anymore.

if you can help me i will be very grateful, thank you.

[jyijyi]

Does this help to find old firmware?

Looking for old MC7455 Firmware 02.20.03.22

Hi, SWI9X30C_02.20.03.22 not available with Generic. Pkg can be dnload from below link. Any reason a build from 2016 is needed ? https://source.sierrawireless.com/resources/#sthash.KA0j4tdO.dpbs=&tags=SWI9X30C_02.20.03.22|Firmwares+%26+drivers

Btw, did you install the latest usb driver?

https://source.sierrawireless.com/resources/airprime/software/airprime-em_mc-series-windows-drivers-qmi-build-5087/#sthash.vx480rmN.dpbs

[michael.bachinger]

Thank you for the Firmware link!

Yes, i installed both Qualcomm-HS-USB-QDLoader-9008-Driver and Qualcomm USB Driver v1.0.10061.1.

I still get

FDT version: 1.0.1702.1
Awaiting adapter ...
Enabling selective suspend ...
Firmware download failed.
Primary error code: 82 - Failed in checking modem mode.
Secondary error code: 0 - Not applicable.
Device error code: 0x0 - Unknown device error code.

Preexisting images information:
        Current:
                Firmware:
                        ImageId:
                        BuildId:
                Configuration:
                        ImageId:
                        BuildId:
Final images information:
        Current:
                Firmware:
                        ImageId:
                        BuildId:
                Configuration:
                        ImageId:
                        BuildId:

OEM PRI:

IMEI:

Total time elapsed: 125 ms.


Images downloaded:


Press Enter to continue ...

when trying to run FDT.

While using QFIL, it says no port available

which i guess is because the modem doesn’t show up as a COM Port, but as a Network Adapter

My guess is that this whole trouble is over once i flash the old correct firmware, but i dont know how to that with all the errors i am encoutering.

[jyijyi]

did you install the latest usb driver?

https://source.sierrawireless.com/resources/airprime/software/airprime-em_mc-series-windows-drivers-qmi-build-5087/#sthash.vx480rmN.dpbs

did you use the FW upgrade exe tool?

[michael.bachinger]

Yes, i have this driver installed and i used the FW Upgrade exe tool (9999999_9904609_SWI9X30C_02.24.05.06_00_GENERIC_002.026_000.exe).
When executing it, i get

FDT version: 1.0.1702.1
Awaiting adapter ...
Enabling selective suspend ...
Firmware download failed.
Primary error code: 82 - Failed in checking modem mode.
Secondary error code: 0 - Not applicable.
Device error code: 0x0 - Unknown device error code.

Preexisting images information:
        Current:
                Firmware:
                        ImageId:
                        BuildId:
                Configuration:
                        ImageId:
                        BuildId:
Final images information:
        Current:
                Firmware:
                        ImageId:
                        BuildId:
                Configuration:
                        ImageId:
                        BuildId:

OEM PRI:

IMEI:

Total time elapsed: 125 ms.


Images downloaded:


Press Enter to continue ...```

[jyijyi]

how about other exe like upgrading to SWI9X30C_02.38.00.00?

[michael.bachinger]

Always the same, no matter with one i used.

[jyijyi]

what is the response of the following?

ati3
at!impref?
at!entercnd="A710"
at!usbcomp?
at!usbcomp=?

BTW, you can see here on other user update the DELL DW5819 driver: (From your screenshot, you are using DW5818)

MC7430 firmware update

Why Dell, it’s Sierra?

[michael.bachinger]

i installed the driver and now it shows up as a COM-Port
but the exe is still not working properly. Should i use QFIL?

here are the responses.

ati3
Manufacturer: Sierra Wireless, Incorporated
Model: MC7455B
Revision: SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30
MEID: 35907206696228
IMEI: 359072066962289
IMEI SV: 20
FSN: LQ835688730410
+GCAP: +CGSM


OK
at!impref?
!IMPREF: 
 preferred fw version:    02.24.05.06
 preferred carrier name:  GENERIC
 preferred config name:   GENERIC_002.026_000
 preferred subpri index:  000
 current fw version:      02.33.03.00
 current carrier name:    GENERIC
 current config name:     GENERIC_002.026_000
 current subpri index:    000

 fw version mismatch

OK
AT!entercnd="A710"
OK
AT!usbcomp?
Config Index: 1
Config Type:  1 (Generic)
Interface bitmask: 0000100D (diag,nmea,modem,mbim) 

OK
AT!usbcomp=?
!USBCOMP: 
AT!USBCOMP=<Config Index>,<Config Type>,<Interface bitmask>
  <Config Index>      - configuration index to which the composition applies, should be 1

  <Config Type>       - 1:Generic, 2:USBIF-MBIM, 3:RNDIS
                        config type 2/3 should only be used for specific Sierra PIDs: 68B1, 9068
                        customized VID/PID should use config type 1

  <Interface bitmask> - DIAG     - 0x00000001,
                        NMEA     - 0x00000004,
                        MODEM    - 0x00000008,
                        RMNET0   - 0x00000100,
                        RMNET1   - 0x00000400,
                        MBIM     - 0x00001000,
  e.g.
  10D  - diag, nmea, modem, rmnet interfaces enabled
  1009 - diag, modem, mbim interfaces enabled

  The default configuration is:
  at!usbcomp=1,1,10F

OK

[jyijyi]

how about using RMNET in AT!USBCOMP?

AT!ENTERCND="A710"
AT!USBCOMP=1,1,10d
AT!RESET

[michael.bachinger]

i now have 3 COM Ports, but either 2 of them are active, or the other one

my AT Commands only work on COM6.
This is another thing that is happening. When i connect it, i have a small time windows in which com5&com6 are there and then it disconnects and only com3 is there.

on my linux VW, it behaves likes this:
i have ttyUSB0, ttyUSB1 and ttyUSB2 at first and i can type my commands with screen/dev/ttyUSB2/.

but then, it kicks me and only ttyUSB0 is there. when i open screen/ttyUSB0/, every character i enter is displayed as ‘0’, with now way to press enter (pressing enter will just add another ‘0’).

AT Commands work for a brieve moment on COM6/ttyUSB2
after that, only COM3/ttyUSB0 is available with only zeroes

i did enter your AT Commands.

AT
OK
AT!ENTERCND="A710"
OK
AT!USBCOMP=1,1,10D
OK
AT!RESET
OK

[jyijyi]

if you use AT!USBCOMP=1,1,100D as previous case, will the module kick you out from AT command mode?