# MC7455 lower power mode (config name mismatch) after latest FW **URL:** \ **Category:** MC/EM Series\ **Created:** [July 30, 2020, 9:24pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083 "2020-07-30T21:24:30Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![alex.ciarlillo](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/alex.ciarlillo/32/5456_2.png) [@alex.ciarlillo](https://forum.sierrawireless.com/u/alex.ciarlillo)\ **Post date:** [July 30, 2020, 9:24pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/1 "2020-07-30T21:24:30Z")
Title pretty much says it. I tried to flash the latest generic firmware onto my generic MC7455 and it all looked like it went fine. However, the modem now comes up stuck in “low power mode”. After some digging I believe this is due to a “config name mismatch”, but I cannot seem to fix it. Details: ATI Manufacturer: Sierra Wireless, Incorporated Model: MC7455 Revision: SWI9X30C\_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30 IMEI: REDACTED IMEI SV: 20 FSN: REDACTED +GCAP: +CGSM ``` at!priid? PRI Part Number: 9907763 Revision: 002.072 Customer: GENERIC Carrier PRI: None at!impref? !IMPREF: preferred fw version: 02.33.03.00 preferred carrier name: GENERIC preferred config name: GENERIC_002.072_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 config name mismatch at!gstatus? !GSTATUS: Current Time: 434 Temperature: 29 Reset Counter: 3 Mode: LOW POWER MODE OK ``` Tried the following with no luck: AT!ENTERCND=“A710” AT!USBPID=9071,9070 AT!USBVID=1199 AT!PRIID=“9907763”,“002.072”,“GENERIC” AT!IMAGE=0 AT!RESET (followed by re-flashing) I am dead in the water. Any help is appreciated. ---
**Author:** ![Donald](https://avatars.discourse-cdn.com/v4/letter/d/ac8455/32.png) [@Donald](https://forum.sierrawireless.com/u/Donald)\ **Post date:** [July 31, 2020, 8:13am UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/2 "2020-07-31T08:13:56Z")
Hi @alex.ciarlillo You can try to do these steps as below: 1.Clear all firmware entries and NVUs: AT!ENTERCND=“A710” AT!IMAGE=0 AT!RESET 2. Download the latest firmware (SWI9X30C\_02.33.03.00 Generic) to the module [https://source.sierrawireless.com/resources/airprime/minicard/74xx/airprime-em\_mc74xx-approved-fw-packages/#sthash.u3x3NZkA.dpbs](https://source.sierrawireless.com/resources/airprime/minicard/74xx/airprime-em_mc74xx-approved-fw-packages/#sthash.u3x3NZkA.dpbs) 3. Set image management preferences AT!ENTERCND=“A710” AT!IMPREF=“GENERIC” AT!RESET 4.Provide some information about your module using below commands ATI3 AT!ENTERCND=“A710” AT!HWID? AT!IMPREF? AT!IMAGE? AT!PRIID? AT!GSTATUS? AT!SKU? ---
**Author:** ![alex.ciarlillo](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/alex.ciarlillo/32/5456_2.png) [@alex.ciarlillo](https://forum.sierrawireless.com/u/alex.ciarlillo)\ **Post date:** [July 31, 2020, 12:01pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/3 "2020-07-31T12:01:05Z")
Hi @Donald I have run those commands and tried re-flashing a few times now, along with trying AT!RMARESET before re-flashing. Here is the output of the commands you asked for: ```auto Send:ATI3 Recieve: ATI3 Recieve: Manufacturer: Sierra Wireless, Incorporated Recieve: Model: MC7455 Recieve: Revision: SWI9X30C_02.33.03.00 r8209 CARMD-EV-FRMWR2 2019/08/28 20:59:30 Recieve: IMEI: REDACTED Recieve: IMEI SV: 20 Recieve: FSN: REDACTED Recieve: +GCAP: +CGSM Recieve: OK Send:AT!ENTERCND="A710" Recieve: AT!ENTERCND="A710" Recieve: OK Send:AT!HWID? Recieve: AT!HWID? Recieve: Revision: 1.0 Recieve: OK Send:AT!IMPREF? Recieve: AT!IMPREF? Recieve: !IMPREF: Recieve: preferred fw version: 02.33.03.00 Recieve: preferred carrier name: GENERIC Recieve: preferred config name: GENERIC_002.072_000 Recieve: preferred subpri index: 000 Recieve: current fw version: 02.33.03.00 Recieve: current carrier name: GENERIC Recieve: current config name: GENERIC_002.026_000 Recieve: current subpri index: 000 Recieve: config name mismatch Recieve: OK Send:AT!IMAGE? Recieve: AT!IMAGE? Recieve: TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID Recieve: FW 1 GOOD 1 0 0 ?_? 02.33.03.00_? Recieve: FW 2 EMPTY 0 0 0 Recieve: FW 3 EMPTY 0 0 0 Recieve: FW 4 EMPTY 0 0 0 Recieve: Max FW images: 4 Recieve: Active FW image is at slot 1 Recieve: TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID Recieve: PRI FF GOOD 0 0 0 002.072_000 02.33.03.00_GENERIC Recieve: Max PRI images: 50 Recieve: OK Send:AT!PRIID? Recieve: AT!PRIID? Recieve: PRI Part Number: 9904609 Recieve: Revision: 002.072 Recieve: Customer: Generic-Laptop Recieve: Carrier PRI: None Recieve: OK Send:AT!SKU? Recieve: AT!SKU? Recieve: SKU: 1103789 Recieve: OK Send:AT!GSTATUS? Recieve: AT!GSTATUS? Recieve: !GSTATUS: Recieve: Current Time: 96 Temperature: 27 Recieve: Reset Counter: 1 Mode: LOW POWER MODE Recieve: OK Send:AT!IMPREF? Recieve: AT!IMPREF? Recieve: !IMPREF: Recieve: preferred fw version: 02.33.03.00 Recieve: preferred carrier name: GENERIC Recieve: preferred config name: GENERIC_002.072_000 Recieve: preferred subpri index: 000 Recieve: current fw version: 02.33.03.00 Recieve: current carrier name: GENERIC Recieve: current config name: GENERIC_002.026_000 Recieve: current subpri index: 000 Recieve: config name mismatch Recieve: OK ``` ---
**Author:** ![Donald](https://avatars.discourse-cdn.com/v4/letter/d/ac8455/32.png) [@Donald](https://forum.sierrawireless.com/u/Donald)\ **Post date:** [August 3, 2020, 3:56am UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/4 "2020-08-03T03:56:19Z")
Hi @alex.ciarlillo This issue has not been reproduced with MC7455 firmware SWI9X30C\_02.33.03.00 Generic on my side. > [@alex.ciarlillo](#): > > ```auto > Recieve: AT!IMPREF? > Recieve: !IMPREF: > Recieve: preferred fw version: 02.33.03.00 > Recieve: preferred carrier name: GENERIC > Recieve: preferred config name: GENERIC_002.072_000 > Recieve: preferred subpri index: 000 > Recieve: current fw version: 02.33.03.00 > Recieve: current carrier name: GENERIC > Recieve: current config name: GENERIC_002.026_000 > Recieve: current subpri index: 000 > Recieve: config name mismatch > Recieve: OK > > ``` > [@alex.ciarlillo](#): > > ```auto > Send:AT!PRIID? > > Recieve: AT!PRIID? > Recieve: PRI Part Number: 9904609 > Recieve: Revision: 002.072 > Recieve: Customer: Generic-Laptop > Recieve: Carrier PRI: None > Recieve: OK > > ``` PRI file is not switched correctly after upgrading the firmware on your module. You can try to do these steps as below: AT!ENTERCND=“A710” AT!IMPREF=“02.33.03.00"”“GENERIC”,“GENERIC\_002.072\_000” AT!PRIID=“9904609”,“002.072”,“GENERIC” AT!RESET AT!IMPREF? AT!IMAGE? AT!PRIID? AT!GSTATUS? ---
**Author:** ![perrysteger](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@perrysteger](https://forum.sierrawireless.com/u/perrysteger)\ **Post date:** [October 4, 2020, 10:01pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/5 "2020-10-04T22:01:25Z")
@Donald @alex.ciarlillo I am experiencing the same problem. For some reason, the modem is selecting the generic PRI from original firmware: `Carrier PRI: 9999999_9904609_SWI9X30C_02.24.05.06_00_GENERIC_002.026_000` Even though I’ve run `AT!IMAGE=0` and downloaded the latest Verizon firmware/PRI. The Verizon PRI is the only one listed by `AT!IMAGE?` and yet the modem chooses Generic 002.026. I’ve set `AT!PRIID="9904780","002.079","hi"` and `AT!RESET`. Doesn’t matter. I still get: ```auto at!impref? !IMPREF: preferred fw version: 02.33.03.00 preferred carrier name: VERIZON preferred config name: VERIZON_002.079_001 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 carrier name mismatch config name mismatch OK ``` I’d love to hear thoughts or ideas that anyone has on this. ---
**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:** [October 5, 2020, 6:39am UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/6 "2020-10-05T06:39:05Z")
@perrysteger So if you include the response to at!image? then we can see everything that is on the unit. I would try the below command at!impref=“GENERIC” at!reset Regards Matt ---
**Author:** ![perrysteger](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@perrysteger](https://forum.sierrawireless.com/u/perrysteger)\ **Post date:** [October 5, 2020, 8:58pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/7 "2020-10-05T20:58:42Z")
@mlw here’s my minicom session, right after `AT!IMAGE=0` and download latest Verizon firmware: ```auto at!image? TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID FW 1 GOOD 1 0 0 ?_? 02.33.03.00_? FW 2 EMPTY 0 0 0 FW 3 EMPTY 0 0 0 FW 4 EMPTY 0 0 0 Max FW images: 4 Active FW image is at slot 1 TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID PRI FF GOOD 0 0 0 002.079_001 02.33.03.00_VERIZON Max PRI images: 50 OK at!impref? !IMPREF: preferred fw version: 02.33.03.00 preferred carrier name: VERIZON preferred config name: VERIZON_002.079_001 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 carrier name mismatch config name mismatch OK ``` and here is the result of doing the same thing with latest Generic: ```auto at!image? TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID FW 1 GOOD 1 0 0 ?_? 02.33.03.00_? FW 2 EMPTY 0 0 0 FW 3 EMPTY 0 0 0 FW 4 EMPTY 0 0 0 Max FW images: 4 Active FW image is at slot 1 TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID PRI FF GOOD 0 0 0 002.072_000 02.33.03.00_GENERIC Max PRI images: 50 OK at!impref? !IMPREF: preferred fw version: 02.33.03.00 preferred carrier name: GENERIC preferred config name: GENERIC_002.072_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 config name mismatch OK ``` I have one MC7455 (SKU 1103789) Rev B and both of these work fine. But I have several Rev A modems, and none of these will successfully load the correct PRI unless I revert to the 02.24.05 firmware that they shipped with. Does not work with 02.30.03, 02.32.11 or latest 02.33.03. In summary: MC7455 Rev B modems are upgradeable. MC7455 Rev A modems only work with 02.24.05 firmware. We have a ton of Rev A modems deployed, and I would like the option of upgrading their firmware, so I still need a fix for this! ---
**Author:** ![perrysteger](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@perrysteger](https://forum.sierrawireless.com/u/perrysteger)\ **Post date:** [October 5, 2020, 9:57pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/8 "2020-10-05T21:57:01Z")
A little more info here. I have tried to set PRIID and this does not appear to be working: ```auto at!priid="9904780","002.079","hi-there" OK at!priid? PRI Part Number: 9904780 Revision: 002.079 Customer: hi-there Carrier PRI: None ``` I think that “Carrier PRI: None” means that it doesn’t like my PRI… ---
**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:** [October 6, 2020, 6:33am UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/9 "2020-10-06T06:33:15Z")
@perrysteger So can you send the below commands to the unit as everything looks like it should work. We have only ever had a single hardware revision that has shipped from the factory. We may have substituted like for like components but there has never been a memory change or refresh of the design which would mean that it only worked up to version X of the firmware. ``` at!hwid? at!pcinfo? ``` Also a picture of one of the ‘rev A’ units would be useful as I cannot see a rev on mine (and its pretty old) but this could have changed over time. Regards Matt ---
**Author:** ![perrysteger](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@perrysteger](https://forum.sierrawireless.com/u/perrysteger)\ **Post date:** [October 6, 2020, 12:54pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/10 "2020-10-06T12:54:21Z")
@mlw thanks so much for responding. Here’s a dump of a minicom session this morning. Just downloaded the latest Verizon firmware/PRI combo and: I’m guessing the since AT!PRIID? returning “Carrier PRI: None” may be a symptom of the problem. ```auto at!entercnd="A710" OK at!hwid? Revision: 1.0 OK 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 OK at!image? TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID FW 1 GOOD 1 0 0 ?_? 02.33.03.00_? FW 2 EMPTY 0 0 0 FW 3 EMPTY 0 0 0 FW 4 EMPTY 0 0 0 Max FW images: 4 Active FW image is at slot 1 TYPE SLOT STATUS LRU FAILURES UNIQUE_ID BUILD_ID PRI FF GOOD 0 0 0 002.079_001 02.33.03.00_VERIZON Max PRI images: 50 OK at!impref? !IMPREF: preferred fw version: 02.33.03.00 preferred carrier name: VERIZON preferred config name: VERIZON_002.079_001 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 carrier name mismatch config name mismatch OK at!priid? PRI Part Number: 9904780 Revision: 002.079 Customer: hi Carrier PRI: None OK ``` ![IMG_0355.jpg](https://us1.discourse-cdn.com/flex025/uploads/sierrawireless/original/2X/4/416ad201a6bacaae648df41c90acfed52fd449ca.jpeg) ---
**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:** [October 6, 2020, 2:47pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/11 "2020-10-06T14:47:53Z")
@perrysteger So I have a HW 1.0 unit as well and have no issues so I do not think it is anything do with this. In the unit above you have the preferred set to VERIZON and the current set to GENERIC which is where the mismatch comes in (which is surprising given you do not have the GENERIC PRI file loaded). If you send the below then I think it will work. at!impref=“VERIZON” at!reset That should set the current, the preferred and what is on the unit to line up. Regards Matt ---
**Author:** ![perrysteger](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@perrysteger](https://forum.sierrawireless.com/u/perrysteger)\ **Post date:** [October 6, 2020, 4:06pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/12 "2020-10-06T16:06:50Z")
@mlw Oh, I wish it were that easy. Here you go: ```auto at!impref="VERIZON" OK at!reset OK (wait for modem to reset...) ate OK at!impref? !IMPREF: preferred fw version: 02.33.03.00 preferred carrier name: VERIZON preferred config name: VERIZON_002.079_001 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 carrier name mismatch config name mismatch OK ``` Can I ship you one of these modems? I have several that behave identically. I don’t need it back – just want to figure out how to get the firmware upgraded… ---
**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:** [October 6, 2020, 5:33pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/13 "2020-10-06T17:33:57Z")
@perrysteger So last ditch attempt, try the below command, this sets it back to ground 0 as far as is possible (its not possible to completely make it factory fresh). `at!rmareset=0` Might need a reset afterwards might not. Regards Matt ---
**Author:** ![perrysteger](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@perrysteger](https://forum.sierrawireless.com/u/perrysteger)\ **Post date:** [October 6, 2020, 8:04pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/14 "2020-10-06T20:04:58Z")
@mlw I’m all for last ditch efforts! Here it is: ```auto at!rmareset=0 ERROR at!entercnd="A710" OK at!rmareset=0 ERROR at!rmareset? !RMARESET: 3 Latest OK ``` I could do `at!rmareset=3` for you, but I’ve done that already… TechShip tech support asked me to try `AT!IMPREF="AUTO-SIM"`, so here that is: ```auto at!impref="AUTO-SIM" OK ate OK at!impref? !IMPREF: preferred fw version: 00.00.00.00 preferred carrier name: AUTO-SIM preferred config name: AUTO-SIM_000.000_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 carrier name mismatch config name mismatch OK ``` And just for completeness, here’s `AT!RMARESET=3`: ```auto at!rmareset=3 !RMARESET: DEVICE REBOOT REQUIRED Items Restored: 1730 Items Deleted: 0 Items Skipped: 7 OK at!reset OK ate 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 ``` Thanks for sticking with me on this. ---
**Author:** ![anon56110884](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@anon56110884](https://forum.sierrawireless.com/u/anon56110884)\ **Post date:** [October 6, 2020, 8:52pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/15 "2020-10-06T20:52:39Z")
Have you tried on Linux? You can give it a try by using the modem on a Linux PC and setting AT!IMAGE=“carrier”, AT!RESET based on what AT!IMAGE? shows you have on the modem. ---
**Author:** ![perrysteger](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@perrysteger](https://forum.sierrawireless.com/u/perrysteger)\ **Post date:** [October 6, 2020, 9:11pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/16 "2020-10-06T21:11:54Z")
@anon56110884 yep – tried AT!IMPREF=“VERIZON” and “GENERIC”. This modem still reaches for an older unlisted generic PRI and gets carrier mismatch or version mismatch. ---
**Author:** ![anon56110884](https://avatars.discourse-cdn.com/v4/letter/a/ecb155/32.png) [@anon56110884](https://forum.sierrawireless.com/u/anon56110884)\ **Post date:** [October 6, 2020, 9:15pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/17 "2020-10-06T21:15:23Z")
Thanks for trying @perrysteger. Would you please reach out via your Sierra or distributor support channel. We’ll look deeper into this issue that you are facing via the support channel. Thanks. ---
**Author:** ![perrysteger](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@perrysteger](https://forum.sierrawireless.com/u/perrysteger)\ **Post date:** [October 6, 2020, 9:32pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/18 "2020-10-06T21:32:54Z")
@anon56110884 Could you give me some help contacting someone directly at Sierra? Thanks. ---
**Author:** ![dl5162](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/dl5162/32/2169_2.png) [@dl5162](https://forum.sierrawireless.com/u/dl5162)\ **Post date:** [October 7, 2020, 8:03am UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/19 "2020-10-07T08:03:19Z")
> [@perrysteger](#): > > ```auto > at!rmareset? > !RMARESET: > 3 Latest > > ``` I believe this proves there is something seriously wrong with that module. The “0 Factory” and “1 Provision” cannot be replaced according to the AT command manual, and I assume that means they cannot be deleted either. FWIW, `at!rmareset=0` is documented as “For information only, cannot be restored”, so you might want to try `at!rmareset=1` instead. But that list of restore points does not look promising so I guess it won’t work either. The “3 Latest” restore point is automatically backed up and restored on every firmware update, so manually restoring it is not expected to make much difference. ---
**Author:** ![perrysteger](https://avatars.discourse-cdn.com/v4/letter/p/df705f/32.png) [@perrysteger](https://forum.sierrawireless.com/u/perrysteger)\ **Post date:** [October 7, 2020, 1:25pm UTC](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083/20 "2020-10-07T13:25:42Z")
@dl5162 agree that there is something wrong with this modem, along with the five additional Rev A modems I have here on my desk, and maybe a hundred or so we have deployed in the field. My lone Rev B modem IS upgradable to the latest firmware. I was hopeful that I could find someone from Sierra who might take up this cause to figure out why some of their modems are not upgradable. The original message in this thread from @alex.ciarlillo documents identical symptoms. Thanks for responding. [Next page](https://forum.sierrawireless.com/t/mc7455-lower-power-mode-config-name-mismatch-after-latest-fw/21083.md?page=2)