# MC7455 stops working after qmi firmware update

**URL:** <https://forum.sierrawireless.com/t/mc7455-stops-working-after-qmi-firmware-update/14336>\
**Category:** MC/EM Series\
**Created:** [October 31, 2018, 7:56pm UTC](https://forum.sierrawireless.com/t/mc7455-stops-working-after-qmi-firmware-update/14336 "2018-10-31T19:56:09Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![knguyen1](https://avatars.discourse-cdn.com/v4/letter/k/e9bcb4/32.png) [@knguyen1](https://forum.sierrawireless.com/u/knguyen1)\
**Post date:** [October 31, 2018, 7:56pm UTC](https://forum.sierrawireless.com/t/mc7455-stops-working-after-qmi-firmware-update/14336/1 "2018-10-31T19:56:09Z")

</div>

Hi,

I follow the qmi update procedure as posted by experts here, but after I finished the firmware upgrade, I could no longer access LTE or send qmicli command to MC7455.  
Whenever I sent qmicli command to MC7455, I received this weild error: “ **couldn’t create client for the ‘dms’ service: CID allocation failed in the CTL client: Transaction timed out** ”.  
Then I have to reload the firmware by windows exe method. And the module is back to normally working.  
Only after I upgrade the firmware by qmi-firmware-update, the module stopped working.

Please anyone can give me a hint.  
Thank you.  
Tony.

---

<div class="post-metadata">

**Author:** ![mlw](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/mlw/32/3706_2.png) [@mlw](https://forum.sierrawireless.com/u/mlw)\
**Post date:** [November 1, 2018, 7:39am UTC](https://forum.sierrawireless.com/t/mc7455-stops-working-after-qmi-firmware-update/14336/2 "2018-11-01T07:39:58Z")

</div>

Tony,

After you have updated it can you send the below AT commands to it?

at!gstatus?  
at!pcinfo?

I suspect you are only loading the signalling firmware (.cwe) and not the corresponding carier PRI file (.nvu) i.e. generic, Verizon, AT&T, etc. Which causes a mismatch and forces the unit into low power mode. The one click updater will load both.

Regards

Matt

---

<div class="post-metadata">

**Author:** ![knguyen1](https://avatars.discourse-cdn.com/v4/letter/k/e9bcb4/32.png) [@knguyen1](https://forum.sierrawireless.com/u/knguyen1)\
**Post date:** [November 2, 2018, 1:46pm UTC](https://forum.sierrawireless.com/t/mc7455-stops-working-after-qmi-firmware-update/14336/3 "2018-11-02T13:46:27Z")

</div>

Hi Matt,

I always use 2 files CWE and PRI to upgrade the firmware.

For example, 2 firmwares I used were:

1. SWI9X30C\_ 02.24.05.06.cwe
2. SWI9X30C\_ 02.24.05.06\_BELL\_001.005\_000.nvu

And all the command I used were:  
qmicli -d /dev/cdc-wdm0 --dms-set-firmware-preference=“02.24.05.06,001.005\_000,Bell”  
qmicli -d /dev/cdc-wdm0 --dms-set-operating-mode=offline  
qmicli -d /dev/cdc-wdm0 --dms-set-operating-mode=reset  
qmi-firmware-update -t /dev/ttyUSB0 --update-qdl SWI9X30C\_ 02.24.05.06.cwe SWI9X30C\_ 02.24.05.06\_BELL\_001.005\_000.nvu

The the results of AT commands were:  
AT!GSTATUS: ERROR  
AT!PCINFO?: Low Power Mode.

Please help me out of this,  
Thank you,  
Tony.

---

<div class="post-metadata">

**Author:** ![mlw](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/mlw/32/3706_2.png) [@mlw](https://forum.sierrawireless.com/u/mlw)\
**Post date:** [November 2, 2018, 3:54pm UTC](https://forum.sierrawireless.com/t/mc7455-stops-working-after-qmi-firmware-update/14336/4 "2018-11-02T15:54:16Z")

</div>

@knguyen1,

Can you send the below commands to the unit?

```
ati    
at!pcinfo?
at!priid?
at!entercnd="A710"
at!priid?
at!gobiimpref?

```

Regards

Matt

---

<div class="post-metadata">

**Author:** ![knguyen1](https://avatars.discourse-cdn.com/v4/letter/k/e9bcb4/32.png) [@knguyen1](https://forum.sierrawireless.com/u/knguyen1)\
**Post date:** [November 5, 2018, 5:42pm UTC](https://forum.sierrawireless.com/t/mc7455-stops-working-after-qmi-firmware-update/14336/5 "2018-11-05T17:42:44Z")

</div>

Hi Matt,

When I queried list of stored firmwares in my module, this is what I have received:

qmicli -d /dev/cdc-wdm0 --dms-list-stored-images  
[/dev/cdc-wdm0] Device list of stored images retrieved:

```
[0] Type: 'modem'
    Maximum: '4'

	[modem0]
	Unique ID: '?_?'
	Build ID: '02.20.03.00_?'
	Storage index: '1'
	Failure count: '0'

	[modem1]
	Unique ID: '?_?'
	Build ID: '02.20.03.22_?'
	Storage index: '2'
	Failure count: '0'

	[modem2]
	Unique ID: '?_?'
	Build ID: '02.24.05.06_?'
	Storage index: '3'
	Failure count: '0'

	>>>>>>>>>> [CURRENT] <<<<<<<<<<
	[modem3]
	Unique ID: '?_?'
	Build ID: '02.30.03.00_?'
	Storage index: '4'
	Failure count: '0'

[1] Type: 'pri'
    Maximum: '50'

	[pri0]
	Unique ID: '002.020_000'
	Build ID: '02.20.03.00_ATT'

	[pri1]
	Unique ID: '001.005_000'
	Build ID: '02.24.05.06_BELL'

	[pri2]
	Unique ID: '002.046_001'
	Build ID: '02.30.03.00_GENERIC'

	[pri3]
	Unique ID: '002.020_000'
	Build ID: '02.20.03.22_SPRINT'

	[pri4]
	Unique ID: '001.000_000'
	Build ID: '00.00.00.00_OEMPRI918'

	[pri5]
	Unique ID: '002.034_000'
	Build ID: '02.24.05.06_VERIZON'

```

Is it normal or abnormal the displayed list of firmwares.

I can send AT!PCINFO?

at!pcinfo?

State: Low Power Mode

LPM voters - Temp:0, Volt:0, User:0, W\_DISABLE:0, IMSWITCH:1, BIOS:0, LWM2M:0, OMADM:0, FOTA:0

LPM persistence - None

at!priid?

PRI Part Number: 9906491

Revision: 001.002

Customer: Generic-M2M

Carrier PRI: 9999999\_9905153\_SWI9X30C\_02.24.05.06\_00\_BELL\_001.005\_000

I can’t send at command at!gobiimpref?

Please help me out,  
Thank you ,  
Tony

---

<div class="post-metadata">

**Author:** ![knguyen1](https://avatars.discourse-cdn.com/v4/letter/k/e9bcb4/32.png) [@knguyen1](https://forum.sierrawireless.com/u/knguyen1)\
**Post date:** [November 9, 2018, 2:29pm UTC](https://forum.sierrawireless.com/t/mc7455-stops-working-after-qmi-firmware-update/14336/6 "2018-11-09T14:29:07Z")

</div>

Hi Matt,

Please help me out,

Thank you,  
Tony

---

<div class="post-metadata">

**Author:** ![mlw](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/mlw/32/3706_2.png) [@mlw](https://forum.sierrawireless.com/u/mlw)\
**Post date:** [November 9, 2018, 2:42pm UTC](https://forum.sierrawireless.com/t/mc7455-stops-working-after-qmi-firmware-update/14336/7 "2018-11-09T14:42:43Z")

</div>

@knguyen1,

The IMSWITCH indication above tells me it is related to having the wrong PRI file active. You need to send the commands I specified above in the order I give them and they will execute properly but the order is important. Without these responses I cannot tell you the commands to send to get it working again.

Regards

Matt

---

<div class="post-metadata">

**Author:** ![knguyen1](https://avatars.discourse-cdn.com/v4/letter/k/e9bcb4/32.png) [@knguyen1](https://forum.sierrawireless.com/u/knguyen1)\
**Post date:** [November 28, 2018, 2:28pm UTC](https://forum.sierrawireless.com/t/mc7455-stops-working-after-qmi-firmware-update/14336/8 "2018-11-28T14:28:42Z")

</div>

Hi Matt,

It is the result of

!GOBIIMPREF:  
preferred fw version: 05.05.58.00  
preferred carrier name: Generic  
preferred config name: Generic\_005.025\_002  
current fw version: 05.05.58.00  
current carrier name: ATT  
current config name: ATT\_005.010\_001

carrier name mismatch  
config name mismatch

I see it is carrier mismatch, please tell me how to fix this issue.

Thank you,  
Tony,

---

<div class="post-metadata">

**Author:** ![mlw](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/mlw/32/3706_2.png) [@mlw](https://forum.sierrawireless.com/u/mlw)\
**Post date:** [November 28, 2018, 4:09pm UTC](https://forum.sierrawireless.com/t/mc7455-stops-working-after-qmi-firmware-update/14336/9 "2018-11-28T16:09:56Z")

</div>

@knguyen1,

Try sending it the below

```
at!entercnd="A710"
at!gobiimpref="GENERIC"
at!reset

```

Regards

Matt

---

<div class="post-metadata">

**Author:** ![aleksander0m](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/aleksander0m/32/1774_2.png) [@aleksander0m](https://forum.sierrawireless.com/u/aleksander0m)\
**Post date:** [November 28, 2018, 5:51pm UTC](https://forum.sierrawireless.com/t/mc7455-stops-working-after-qmi-firmware-update/14336/10 "2018-11-28T17:51:16Z")

</div>

@knguyen1 please note you can use (unless you’ve built libqmi without udev support) just a single command to do the full firmware upgrade process, which should be much safer and less error-prone than manually doing the --dms-set-firmware-preference, as it validates that the cwe and nvu images match and also send the correct details to the modem.

`$ sudo qmi-firmware-update --update --cdc-wdm /dev/cdc-wdm0 SWI9X30C_ 02.24.05.06_BELL_001.005_000.nvu SWI9X30C_02.24.05.06.cwe`