# EM7565 problem after firmware update failure **URL:** \ **Category:** MC/EM Series\ **Created:** [April 29, 2019, 11:40pm UTC](https://forum.sierrawireless.com/t/em7565-problem-after-firmware-update-failure/16236 "2019-04-29T23:40:43Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![mhizem](https://avatars.discourse-cdn.com/v4/letter/m/5f9b8f/32.png) [@mhizem](https://forum.sierrawireless.com/u/mhizem)\ **Post date:** [April 29, 2019, 11:40pm UTC](https://forum.sierrawireless.com/t/em7565-problem-after-firmware-update-failure/16236/1 "2019-04-29T23:40:44Z")
Hello, It looks like I bricked this EM7565 card after a failed attempt to update the firmware, now only one USB interface is present and it’s not an AT interface: dmesg: [55.262614] usb 1-4.2: new high-speed USB device number 8 using xhci\_hcd [55.349384] usb 1-4.2: New USB device found, idVendor=1199, idProduct=9090 [55.349389] usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [55.349392] usb 1-4.2: Product: QUSB\_\_BULK [55.349395] usb 1-4.2: Manufacturer: Sierra Wireless, Incorporated [55.349398] usb 1-4.2: SerialNumber: UF80168511030634 [55.393491] usbcore: registered new interface driver qcserial [55.393571] usbserial: USB Serial support registered for Qualcomm USB modem [55.393627] qcserial 1-4.2:1.0: Qualcomm USB modem converter detected [55.394343] usb 1-4.2: Qualcomm USB modem converter now attached to ttyUSB0 lsusb Bus 002 Device 003: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub Bus 002 Device 002: ID 0451:8140 Texas Instruments, Inc. TUSB8041 4-Port Hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 008: ID 1199:9090 Sierra Wireless, Inc. Bus 001 Device 005: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub Bus 001 Device 007: ID 1976:1307 Chipsbrand Microelectronics (HK) Co., Ltd. Bus 001 Device 006: ID 045e:0745 Microsoft Corp. Nano Transceiver v1.0 for Bluetooth Bus 001 Device 003: ID 0451:8142 Texas Instruments, Inc. TUSB8041 4-Port Hub Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd Bus 001 Device 002: ID 0557:7000 ATEN International Co., Ltd Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub lsusb -t /: Bus 02.Port 1: Dev 1, Class=root\_hub, Driver=xhci\_hcd/4p, 5000M |\_\_ Port 3: Dev 2, If 0, Class=Hub, Driver=hub/4p, 5000M |\_\_ Port 4: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M /: Bus 01.Port 1: Dev 1, Class=root\_hub, Driver=xhci\_hcd/4p, 480M |\_\_ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |\_\_ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |\_\_ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M |\_\_ Port 3: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M |\_\_ Port 1: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 12M |\_\_ Port 1: Dev 6, If 1, Class=Human Interface Device, Driver=usbhid, 12M |\_\_ Port 1: Dev 6, If 2, Class=Human Interface Device, Driver=usbhid, 12M |\_\_ Port 2: Dev 7, If 0, Class=Mass Storage, Driver=usb-storage, 480M |\_\_ Port 4: Dev 5, If 0, Class=Hub, Driver=hub/4p, 480M |\_\_ Port 2: Dev 8, If 0, Class=Vendor Specific Class, Driver=qcserial, 480M ls /dev | grep USB ttyUSB0 Has anyone encountered this problem?, how do we recover from this? Thank you ---
**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:** [April 30, 2019, 6:44am UTC](https://forum.sierrawireless.com/t/em7565-problem-after-firmware-update-failure/16236/2 "2019-04-30T06:44:26Z")
> [@mhizem](#): > > [55.349384] usb 1-4.2: New USB device found, idVendor=1199, idProduct=9090 > [55.349389] usb 1-4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 > [55.349392] usb 1-4.2: Product: QUSB\_\_BULK This is the bootloader. You should be able to fix the issue by rerunning the firmware upgrade. Possibly with another firmware version, depending on why it failed initially. But I would have tried the same version first. ---
**Author:** ![mhizem](https://avatars.discourse-cdn.com/v4/letter/m/5f9b8f/32.png) [@mhizem](https://forum.sierrawireless.com/u/mhizem)\ **Post date:** [May 3, 2019, 1:22am UTC](https://forum.sierrawireless.com/t/em7565-problem-after-firmware-update-failure/16236/3 "2019-05-03T01:22:15Z")
Thank you dl5162, the firmware downloading software is finding the device in an unexpected state and stops immediately: [1953.218582] usb 5-1.2: new full-speed USB device number 4 using uhci\_hcd [1953.401637] usb 5-1.2: New USB device found, idVendor=1199, idProduct=9090 [1953.401640] usb 5-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [1953.401642] usb 5-1.2: Product: QUSB\_\_BULK [1953.401644] usb 5-1.2: Manufacturer: Sierra Wireless, Incorporated [1953.401646] usb 5-1.2: SerialNumber: UF80168511030634 [1953.407672] GobiSerial 5-1.2:1.0: GobiSerial converter detected [1953.407761] usb 5-1.2: GobiSerial converter now attached to ttyUSB0 ./fwdwl-litehostx86\_64 -d /dev/ttyUSB0 --fwpath /home/Downloads/SWI9X50C\_01.07.02.00\_ATT\_002.008\_004 litefw version :lite-fwSLQS04.00.19 INFO: QDL Port : /dev/ttyUSB0 INFO: Device Path: /dev/qcqmi0 INFO: FW Path : /home/mhizem/Downloads/SWI9X50C\_01.07.02.00\_ATT\_002.008\_004 Package Info: Carrier :ATT FW Version :01.07.02.00 Model ID :SWI9X50C Package ID :004 PRI Version:002.008 SKU :9999999 GetDeviceMode: ERROR! Unknown modem state Modem not in correct state Exiting Application!!! Tried -i -1 & -u -1 options with the same result (also with any other possible option) I’m using Gobi package S2.36N2.56, It could be failing because of /dev/qcqmi0 not being mapped. Any other ideas of potentially another package that could work only on /dev/ttyUSBx? Thank you ---
**Author:** ![shvedv.egr](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@shvedv.egr](https://forum.sierrawireless.com/u/shvedv.egr)\ **Post date:** [February 27, 2023, 2:56pm UTC](https://forum.sierrawireless.com/t/em7565-problem-after-firmware-update-failure/16236/4 "2023-02-27T14:56:39Z")
Hello there! Do you have a solution of this problem? I have EM7565 that stuck at QALoder port too :C ---
**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:** [February 27, 2023, 4:22pm UTC](https://forum.sierrawireless.com/t/em7565-problem-after-firmware-update-failure/16236/5 "2023-02-27T16:22:44Z")
you need to use MBPL version upper than R27 to run the lite-fw-download to upgrade module in boot and hold mode `sudo ./bin/fwdwl-litehostx86_64 -c QMI -m 4 -d /dev/ttyUSB0 -f /home/jordan/Downloads/FW_EM74x1/SWI9X50C_01.14.03.00_GENERIC_002.036_010/` ---
**Author:** ![shvedv.egr](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@shvedv.egr](https://forum.sierrawireless.com/u/shvedv.egr)\ **Post date:** [February 27, 2023, 5:35pm UTC](https://forum.sierrawireless.com/t/em7565-problem-after-firmware-update-failure/16236/6 "2023-02-27T17:35:09Z")
I’m using that command: ```auto ubuntu-mate@ubuntu-mate:~$ ./fwdwl-litehostx86_64 -d /dev/$devpath --modelfamily 4 --logfile "fwdwl-lite-$devpath.log" -e 1 --fwpath "./swi_fw0105/" litefw version :lite-fwSLQS04.00.15 INFO: QDL Port : /dev/ INFO: Device Path: /dev/qcqmi0 INFO: FW Path : ./swi_fw0105/ Package Info: Carrier :GENERIC FW Version :01.05.01.00 Model ID :SWI9X50C Package ID :000 PRI Version:001.028 SKU :9999999 GetDeviceMode: ERROR! Unknown modem state Modem not in correct state Exiting Application!!! ``` From this post: > I’m not Linux user (Windows 99,9% time), how i need to edit this command? My modem starts with QDLoader port vid 1199:9090 VID/PID ---
**Author:** ![shvedv.egr](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@shvedv.egr](https://forum.sierrawireless.com/u/shvedv.egr)\ **Post date:** [February 27, 2023, 5:40pm UTC](https://forum.sierrawireless.com/t/em7565-problem-after-firmware-update-failure/16236/7 "2023-02-27T17:40:44Z")
> [@jyijyi](#): > > MBPL version upper than R27 How to check what is my version is and how to install the new one? ---
**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:** [February 27, 2023, 5:43pm UTC](https://forum.sierrawireless.com/t/em7565-problem-after-firmware-update-failure/16236/8 "2023-02-27T17:43:06Z")
you are using the old Gobi SDK. To download new MBPL SDK, you can go to here: [https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/#sthash.qzsmPuwe.dpbs](https://source.sierrawireless.com/resources/airprime/software/mbpl/mbpl-software-latest/#sthash.qzsmPuwe.dpbs)