# After power problem, new ID USB on 05C6:9008. Why?

**URL:** <https://forum.sierrawireless.com/t/after-power-problem-new-id-usb-on-05c6-9008-why/31270>\
**Category:** IoT Modules\
**Created:** [December 15, 2023, 3:28pm UTC](https://forum.sierrawireless.com/t/after-power-problem-new-id-usb-on-05c6-9008-why/31270 "2023-12-15T15:28:53Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![JFTWIT](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@JFTWIT](https://forum.sierrawireless.com/u/JFTWIT)\
**Post date:** [December 15, 2023, 3:28pm UTC](https://forum.sierrawireless.com/t/after-power-problem-new-id-usb-on-05c6-9008-why/31270/1 "2023-12-15T15:28:53Z")

</div>

Hello,  
Due to power supply problems, an RC7620-1 modem no longer appears as a USB device. To be able to reload its firmware, I set the Boot Pin to 0.  
But the modem now has the USB ID 05C6:9008 which is different from the usual 1199:68C0.  
With the fwdwl-litearm tool I can’t download it.  
Here is the result of the log.

**IMPORTANT:** The drivers are in the kernel

_[04:25:15.249][1]System date/time: 01/01/2018 4:25:15_  
_[04:25:15.250][1]1.0.2303.0_  
_[04:25:15.272][1]Kernel: Linux REDY 4.14.281-1.1.0 #1 PREEMPT Wed Jun 8 10:32:05 CEST 2022 armv7l GNU/Linux_

_[04:25:15.273][1]File not found: /sys/module/qcserial/version_

_[04:25:15.273][1]Unable to get qcserial driver’s version from file ‘/sys/module/qcserial/version’ trying using modinfo_

_[04:25:15.286][1]Unable to log qcserial version info. Drivers from MBPL R17 or newer are required._  
_[04:25:15.287][1]File not found: /sys/module/usb\_wwan/version_

_[04:25:15.287][1]Unable to get usb\_wwan driver’s version from file ‘/sys/module/usb\_wwan/version’ trying using modinfo_

_[04:25:15.300][1]Unable to log usb\_wwan version info. Drivers from MBPL R17 or newer are required._  
_[04:25:15.301][1]File not found: /sys/module/cdc\_mbim/version_

_[04:25:15.301][1]Unable to get cdc\_mbim driver’s version from file ‘/sys/module/cdc\_mbim/version’ trying using modinfo_

_[04:25:15.314][1]Unable to log cdc\_mbim version info. Drivers from MBPL R17 or newer are required._  
_[04:25:15.314][1]File not found: /sys/module/qmi\_wwan/version_

_[04:25:15.314][1]Unable to get qmi\_wwan driver’s version from file ‘/sys/module/qmi\_wwan/version’ trying using modinfo_

_[04:25:15.327][1]Unable to log qmi\_wwan version info. Drivers from MBPL R17 or newer are required._  
_[04:25:15.328][1]File not found: /sys/module/mhictrl/version_

_[04:25:15.328][1]Unable to get mhictrl driver’s version from file ‘/sys/module/mhictrl/version’ trying using modinfo_

_[04:25:15.341][1]Unable to log mhictrl version info. Drivers from MBPL R17 or newer are required._  
_[04:25:15.341][1]File not found: /sys/module/mhinet/version_

_[04:25:15.342][1]Unable to get mhinet driver’s version from file ‘/sys/module/mhinet/version’ trying using modinfo_

_[04:25:15.354][1]Unable to log mhinet version info. Drivers from MBPL R17 or newer are required._  
_[04:25:15.355][1]File not found: /sys/module/mhitty/version_

_[04:25:15.355][1]Unable to get mhitty driver’s version from file ‘/sys/module/mhitty/version’ trying using modinfo_

_[04:25:15.368][1]Unable to log mhitty version info. Drivers from MBPL R17 or newer are required._  
_[04:25:15.369][1]/usr/sbin/fwdwl-litearm_  
_[04:25:15.369][1]-c_  
_[04:25:15.369][1]QMI_  
_[04:25:15.369][1]-d_  
_[04:25:15.369][1]/dev/ttyUSB0_  
_[04:25:15.369][1]-p_  
_[04:25:15.369][1]/dev/cdc-wdm0_  
_[04:25:15.369][1]-m4_  
_[04:25:15.369][1]-f_  
_[04:25:15.369][1]/var/_  
_[04:25:15.369][1]-l_  
_[04:25:15.369][1]testsr.log_  
_[04:25:15.437][7]User specified read block size: 0 bytes_  
_[04:25:15.438][7]_\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
_[04:25:15.438][7]Copyright: Â© 2015-2017 Sierra Wireless, Inc. all rights reserved_  
_[04:25:15.438][7]lite-fw is only permitted to be used with Sierra Wireless Modems_  
_[04:25:15.438][7]lite-fw version lite-fwMBPL\_SDK\_R32\_ENG2_  
_[04:25:15.438][7]_\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
_[04:25:15.438][6]Device is in BOOT&HOLD mode._  
_[04:25:15.439][6]Images list:_  
_[04:25:15.439][6]Image[0]: /var//RC76xx\_Release9.6.1\_GENERIC\_7620.spk_  
_[04:25:15.462][7]find\_dev\_ss\_loc: Do not found any USB devices with VID(0x1199)_  
_[04:25:15.462][3]disable\_ss: Failed to find device SS path. SS stays unchanged._  
_[04:25:15.462][6]litefw\_download: Adjust download\_type from 0 to REG\_DWLD as device is already in B&H mode._  
_[04:25:15.462][7]Waiting for modem to come up in B&H mode …_  
_[04:25:16.465][7]Modem is in B&H mode. Downloading firmware …_  
_[04:25:16.498][7]find\_dev\_ss\_loc: Do not found any USB devices with VID(0x1199)_  
_[04:25:16.499][3]disable\_ss: Failed to find device SS path. SS stays unchanged._  
_[04:25:16.499][7]QDL Port :/dev/ttyUSB0_  
_[04:25:22.000][7]read timeout_  
_[04:25:22.000][7]Read payload [0]_  
_[04:25:22.000][1]Read 0 bytes_  
\*[04:25:22.001][1]\<- \*  
_[04:25:22.001][7]Sahara HELLO message might be missed. Resending Sahara HELLO response._  
_[04:25:22.001][7]Current mode: 0, previous max\_reads\_allowed: 29_  
_[04:25:22.001][1]Send 48 bytes_  
_[04:25:22.001][1]-\> 02 00 00 00 30 00 00 00 02 00 00 00 02 00 00 00 00 00 00 00 03 00 00 00 01 00 00 00 02 00 00 00 …0…_  
_[04:25:22.002][1]-\> 03 00 00 00 04 00 00 00 05 00 00 00 06 00 00 00 …_  
_[04:25:22.002][7]Sahara Hello Rsp sent successfully, max\_reads\_allowed reset to 30_  
_[04:25:22.503][7]read timeout_  
_[04:25:22.503][7]Read payload [0]_  
_[04:25:22.503][1]Read 0 bytes_  
\*[04:25:22.503][1]\<- \*  
_[04:25:22.503][3]Device not responsive to SAHARA HELLO RESPONSE, need a power cycle._

**Do you have any idea how to recover the modem?**  
Thanks for your help

---

<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 15, 2023, 3:44pm UTC](https://forum.sierrawireless.com/t/after-power-problem-new-id-usb-on-05c6-9008-why/31270/2 "2023-12-15T15:44:10Z")

</div>

VID/PID “05c6:9008” is the Qualcomm VID/PID.  
There is some boot up problem and makes to such enumeration.

Currently i don’t see any method to recover this.

---

<div class="post-metadata">

**Author:** ![JFTWIT](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@JFTWIT](https://forum.sierrawireless.com/u/JFTWIT)\
**Post date:** [December 15, 2023, 4:03pm UTC](https://forum.sierrawireless.com/t/after-power-problem-new-id-usb-on-05c6-9008-why/31270/3 "2023-12-15T16:03:24Z")

</div>

Thank you for your reply, even if it’s not satisfactory.

**So you’re saying that I can throw my modem in the bin?**

That’s not a tenable situation at a time when everything has to be recycled.  
I’m still convinced that there’s a way of recovering this modem.  
I’m waiting for you to be more specific, even if it must be complicated.

Thank you for your help.

---

<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 16, 2023, 2:44am UTC](https://forum.sierrawireless.com/t/after-power-problem-new-id-usb-on-05c6-9008-why/31270/4 "2023-12-16T02:44:23Z")

</div>

Have you contacted distributor?  
Have you tried fdt tool in windows?

---

<div class="post-metadata">

**Author:** ![JFTWIT](https://avatars.discourse-cdn.com/v4/letter/j/d2c977/32.png) [@JFTWIT](https://forum.sierrawireless.com/u/JFTWIT)\
**Post date:** [December 18, 2023, 8:41am UTC](https://forum.sierrawireless.com/t/after-power-problem-new-id-usb-on-05c6-9008-why/31270/5 "2023-12-18T08:41:28Z")

</div>

Hello,  
No, I haven’t contacted the distributor yet. But what could they do for us?  
can you tell me more about the windows fdt 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 18, 2023, 8:54am UTC](https://forum.sierrawireless.com/t/after-power-problem-new-id-usb-on-05c6-9008-why/31270/6 "2023-12-18T08:54:44Z")

</div>

you contact distributor with business case, then you should get the official support to have deeper investigation for you.

fdt tool:  
[https://source.sierrawireless.com/resources/airprime/software/fdt/](https://source.sierrawireless.com/resources/airprime/software/fdt/)
