# Firmawre Update to MC7430 EM7430 and MC7431

**URL:** <https://forum.sierrawireless.com/t/firmawre-update-to-mc7430-em7430-and-mc7431/35649>\
**Category:** MC/EM Series\
**Tags:** fw-upgrade\
**Created:** [December 3, 2025, 6:47am UTC](https://forum.sierrawireless.com/t/firmawre-update-to-mc7430-em7430-and-mc7431/35649 "2025-12-03T06:47:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![shotaro](https://avatars.discourse-cdn.com/v4/letter/s/7993a0/32.png) [@shotaro](https://forum.sierrawireless.com/u/shotaro)\
**Post date:** [December 3, 2025, 6:47am UTC](https://forum.sierrawireless.com/t/firmawre-update-to-mc7430-em7430-and-mc7431/35649/1 "2025-12-03T06:47:33Z")

</div>

I am trying to update firmwares into those modules using the FDT2.exe tool. Going through the steps shown on 2174314 FDT AppNote r1.pdf manual and others posts carefully, it still does not put two firmwares for two different carriers into the module.

> fdt2.exe -d g5k -force -f SWI9X30C\_02.36.00.00.cwe SWI9X30C\_02.36.00.00\_KDDI\_001.052\_001.nvu SWI9X30C\_02.38.00.00.cwe SWI9X30C\_02.38.00.00\_DOCOMO\_001.058\_000.nvu -log C:\FDTlogs

works, but it does not put both 02.36.00.00.cwe and 02.38.00.00.cwe software into 2 slots. Console with at!image? outputs:

> at!image?  
> TYPE SLOT STATUS LRU FAILURES UNIQUE\_ID BUILD\_ID  
> FW 1 EMPTY 0 0 0  
> FW 2 GOOD 1 0 0 ?_? 02.38.00.00_?  
> FW 3 EMPTY 0 0 0  
> FW 4 EMPTY 0 0 0  
> Max FW images: 4  
> Active FW image is at slot 255
> 
> TYPE SLOT STATUS LRU FAILURES UNIQUE\_ID BUILD\_ID  
> PRI FF GOOD 0 0 0 001.058\_000 02.38.00.00\_DOCOMO  
> PRI FF GOOD 0 0 0 001.052\_001 02.36.00.00\_KDDI  
> Max PRI images: 50

and

> fdt2.exe -d g5k -force -f SWI9X30C\_02.36.00.00.cwe SWI9X30C\_02.36.00.00\_KDDI\_001.052\_001.nvu SWI9X30C\_02.38.00.00.cwe SWI9X30C\_02.38.00.00\_DOCOMO\_001.058\_000.nvu -mi -impref SWI9X30C\_02.36.00.00\_KDDI\_001.052\_001.nvu SWI9X30C\_02.38.00.00\_DOCOMO\_001.058\_000.nvu -log C:\FDTlogs

does not work, it gives us errors:

> Primary error code: 51 - Failed to switch device to BOOT&HOLD mode. Secondary error code: 201 - Failed to switch device to QDL mode. Device error code: 0x0 - Unknown device error code.

What is the proper way to put two firmwares into two slots, 1 and 2, with FDT2.exe tool?

---

<div class="post-metadata">

**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:** [December 3, 2025, 7:11am UTC](https://forum.sierrawireless.com/t/firmawre-update-to-mc7430-em7430-and-mc7431/35649/2 "2025-12-03T07:11:48Z")

</div>

how about download two times with only one firmware each time?

BTW, you can also see here:

> [@EM9291 FW upgrade problem](https://forum.sierrawireless.com/t/em9291-fw-upgrade-problem/34292):
>
> Hi, I would like to know how to upgrade an image and multiple PRIs using FDT tool in Windows OS. Below is the command I used but it always shows error. Could anyone help with suggestions? Thanks. fdt2.exe -d g5k -ignswto -mi -impref SWIX65C\_02.17.08.00.cwe SWIX65C\_02.17.08.00\_GENERIC\_030.081\_001.nvu -f SWIX65C\_02.17.08.00.cwe SWIX65C\_02.17.08.00\_PTCRB\_030.077\_001.nvu SWIX65C\_02.17.08.00\_ATT\_030.094\_001.nvu SWIX65C\_02.17.08.00\_VERIZON\_030.092\_001.nvu SWIX65C\_02.17.08.00\_TMO\_030.042\_001.nvu S…

I saw other user can make it work in EM7565:

> [@How to batch flash multiple firmware's to more than 1 cell modem simulatiously and reliably with fdt2.exe commands for a large production run?](https://forum.sierrawireless.com/t/how-to-batch-flash-multiple-firmwares-to-more-than-1-cell-modem-simulatiously-and-reliably-with-fdt2-exe-commands-for-a-large-production-run/33006):
>
> I am absolutely banging my head against the wall trying to make a script to flash 4 firmwares to more than 1 EM7565 modems connected to the PC at the same time in order to try and speed up production. Right now I have to disable 1 of the modems USB ports and update that modem then after its finished rebooting I have to disable that port and flash the next. The fdt2.exe update utility needs some work in windows. Why does the fdt2.exe process spawn another cmd terminal??? fdt2.exe does not app…
