# EM9190 . EM9191 fw problem **URL:** \ **Category:** MC/EM Series\ **Created:** [June 16, 2023, 8:45am UTC](https://forum.sierrawireless.com/t/em9190-em9191-fw-problem/30006 "2023-06-16T08:45:15Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![filemoon](https://avatars.discourse-cdn.com/v4/letter/f/ce7236/32.png) [@filemoon](https://forum.sierrawireless.com/u/filemoon)\ **Post date:** [June 16, 2023, 8:45am UTC](https://forum.sierrawireless.com/t/em9190-em9191-fw-problem/30006/1 "2023-06-16T08:45:15Z")
Hi, I do have non working EM9190 - it is on Sierra Warranty but they told me it is “child device” (it is extracted from Cradlepoint R1900) and they refuse to generate RMA. Module stops working when carrier firmware was upgraded. I do belie module rejects firmware (no AT command is possible). I’ve noticed module was shipped with EM9190\_01.07.13.00.cwe version of firmware and I would like to download it and reload into the module. It is not possible to find anymore except Cisco webpage (I do not have contract with Cisco to download it): EM9190\_01.07.13.00.cwe EM9190\_01.07.13.00\_GENERIC\_016.006\_004.nvu Can anyone share firmware 01.07.13 generic with me please? Regards Chris ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [June 16, 2023, 8:51am UTC](https://forum.sierrawireless.com/t/em9190-em9191-fw-problem/30006/2 "2023-06-16T08:51:26Z")
only have this one 01.07.19.00, see if it helps: > [@Upgrade of old EM9191 firmware and band N40 support](https://forum.sierrawireless.com/t/upgrade-of-old-em9191-firmware-and-band-n40-support/27231/2): > > I have a backup file in my PC: ---
**Author:** ![filemoon](https://avatars.discourse-cdn.com/v4/letter/f/ce7236/32.png) [@filemoon](https://forum.sierrawireless.com/u/filemoon)\ **Post date:** [June 16, 2023, 8:54am UTC](https://forum.sierrawireless.com/t/em9190-em9191-fw-problem/30006/3 "2023-06-16T08:54:58Z")
Hi, I do have 01.07.19.00 - I would like to try the one with was delivered with module 01.07.13. This is my last hope for the EM9190. Regards Chris ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [June 16, 2023, 10:40am UTC](https://forum.sierrawireless.com/t/em9190-em9191-fw-problem/30006/4 "2023-06-16T10:40:34Z")
I don’t think you can downgrade the version as it might have different partition size ---
**Author:** ![filemoon](https://avatars.discourse-cdn.com/v4/letter/f/ce7236/32.png) [@filemoon](https://forum.sierrawireless.com/u/filemoon)\ **Post date:** [June 16, 2023, 11:58am UTC](https://forum.sierrawireless.com/t/em9190-em9191-fw-problem/30006/5 "2023-06-16T11:58:08Z")
Hi, I was able to locate the firmware - firmware was loaded, but result is very same - modem is starting, it will present: - EM9190-CP - Sierra Wireless DM Port (Com3) - Sierra Wireless WWAN Modem in Windows (in linux it will present ttyUSB0 and ttyUSB1) the problem I have: no AT connection possible to any port (same in Windows as in Linux). After that the module will reload several times and finish in QDL load mode where is ready for firmware upload. When module is in QDL mode I can connect to corresponding USB or ttyUSB port but per every button I press “0” is displayed on terminal - nothing else. So FW downgrade (same as upgrade) did NOT resolve the problem I have - is there any way I can reset module to factory state (when no access to AT command is possible) w/o developer board - what is functionality of reset button on dev board -if reset button resets modem to factory state can I force the modem reset w/o having the dev board by shorting the/some connectors or by software (remember no At possible)? I do have two usb-\>m2 boards - they are working with my other EM9190 module … but they do not have full functionality of official dev board. ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [June 16, 2023, 12:17pm UTC](https://forum.sierrawireless.com/t/em9190-em9191-fw-problem/30006/6 "2023-06-16T12:17:37Z")
How about at!rmareset command? > [@EM9191 remains in WCDMA and does not latch to LTE](https://forum.sierrawireless.com/t/em9191-remains-in-wcdma-and-does-not-latch-to-lte/29697/2): > > does upgrading FW help? does “AT!RMARESET” help? ---
**Author:** ![filemoon](https://avatars.discourse-cdn.com/v4/letter/f/ce7236/32.png) [@filemoon](https://forum.sierrawireless.com/u/filemoon)\ **Post date:** [June 16, 2023, 12:45pm UTC](https://forum.sierrawireless.com/t/em9190-em9191-fw-problem/30006/7 "2023-06-16T12:45:37Z")
“the problem I have: no AT connection possible to any port (same in Windows as in Linux).” “So FW downgrade (same as upgrade) did NOT resolve the problem I have” ---
**Author:** ![jyijyi](https://sea1.discourse-cdn.com/flex025/user_avatar/forum.sierrawireless.com/jyijyi/32/4766_2.png) [@jyijyi](https://forum.sierrawireless.com/u/jyijyi)\ **Post date:** [June 16, 2023, 2:06pm UTC](https://forum.sierrawireless.com/t/em9190-em9191-fw-problem/30006/8 "2023-06-16T14:06:29Z")
How about using qmicli? > [@Reset AT!ENTERCND password](https://forum.sierrawireless.com/t/reset-at-entercnd-password/15098): > > AT!ENTERCND=“A710” ERROR I’ve tried qmicli -d /dev/cdc-wdm0 --dms-restore-factory-defaults=“000000” hoping that would restore the default creds, but no luck. Please, how do I reset the nvram/force back to factory 1199:9013 Sierra Wireless, Inc. Sierra Wireless Gobi 3000 Modem device (MC8355) ---
**Author:** ![filemoon](https://avatars.discourse-cdn.com/v4/letter/f/ce7236/32.png) [@filemoon](https://forum.sierrawireless.com/u/filemoon)\ **Post date:** [June 16, 2023, 4:16pm UTC](https://forum.sierrawireless.com/t/em9190-em9191-fw-problem/30006/9 "2023-06-16T16:16:34Z")
sudo qmicli -d /dev/cdc-wdm0 --dms-restore-factory-defaults=“000000” error: couldn’t open the QmiDevice: Operation fimed out: device is closed it looks like is not working too … - Every single qmicli command against /dev/cdc-wdm0 result is same /dev/cdc-wdm0 is “visible” under /dev/ folder - until device is back in qdl mode If any reset is possible it is hardware reset - via the button, but I think module is “dead duck”