parisisal Posted October 30, 2020 Share Posted October 30, 2020 Hi, the Corsair support sent to me a zip file with a firmware (zip format). If I try to update the keyboard using this file I obtain this error in the logs: 2020-10-28T22:17:11 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image" 2020-10-28T22:17:11 I cue.firmware.index: "K55 RGB" firmware update, expected version: 30.8 same version found, on device: bootloader: 3.0 firmware: 30.8 2020-10-28T22:17:24 W Model size of -49 is less than 0 [b][color="Red"]2020-10-28T22:19:08 C cue.devices.nxp: Bad firmware.[/color][/b] 2020-10-28T22:19:08 I cue.firmware.update.controller: "K55 RGB" FW update has been failed. From "" to "Fw type: Firmware FW: 30.08 ; " Is this an hardware issue ? Or a corrupted firmware ? If I try to force the update from the online repository the Update works without issues: 2020-10-28T22:36:16 I cue.firmware.update.controller: "K55 RGB" FW update has been started. From "Primary FW: 30.08; Secondary FW: 30.08; Bootloader FW: 3.00" to "Secondary: Application: 30.8" 2020-10-28T22:36:16 I cue.hid_report_worker: Stopping report worker "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col03#8&28800968&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" 2020-10-28T22:36:16 I cue.hid_report_worker: Waiting for report worker stop "\\\\?\\hid#vid_1b1c&pid_1b3d&mi_00&col03#8&28800968&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" 2020-10-28T22:36:17 W cue.firmware.update.process.proto_n: "0" stderr: DD: tryOpen: Failed to open \\?\hid#vid_1b1c&pid_1b3d&mi_00&col02#8&28800968&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}: 32 2020-10-28T22:36:17 W cue.firmware.update.process.proto_n: "0" stderr: DD: tryOpne: Device was already opened, closing \\?\hid#vid_1b1c&pid_1b3d&mi_00&col03#8&28800968&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030} 2020-10-28T22:36:17 W cue.firmware.update.process.proto_n: "0" stderr: Adding device: \\?\hid#vid_1b1c&pid_1b3d&mi_01#8&155b9f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} 2020-10-28T22:36:17 W cue.firmware.update.process.proto_n: "0" stderr: Protocol version received: 5 2020-10-28T22:36:17 W cue.firmware.update.process.proto_n: "0" stderr: No device found for report: 0 2020-10-28T22:36:17 W cue.firmware.update.process.proto_n: "0" stderr: testDevices: device handle not found 2020-10-28T22:36:17 W cue.firmware.update.process.proto_n: "0" stderr: Adding device: \\?\hid#vid_1b1c&pid_1b3d&mi_00&col04#8&28800968&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030} 2020-10-28T22:36:17 W cue.firmware.update.process.proto_n: "0" stderr: 0 started NXP pid=1b3d; delays: short 5ms, medium 10ms, long 750ms 2020-10-28T22:36:17 I cue.firmware.update.controller: "K55 RGB" progress: 3 2020-10-28T22:36:21 I cue.firmware.update.controller: "K55 RGB" progress: 5 2020-10-28T22:36:22 I cue.firmware.update.controller: "K55 RGB" progress: 10 2020-10-28T22:36:22 I cue.firmware.update.controller: "K55 RGB" progress: 11 2020-10-28T22:36:23 I cue.firmware.update.controller: "K55 RGB" progress: 12 2020-10-28T22:36:23 I cue.firmware.update.controller: "K55 RGB" progress: 13 2020-10-28T22:36:23 I cue.firmware.update.controller: "K55 RGB" progress: 14 2020-10-28T22:36:23 I cue.firmware.update.controller: "K55 RGB" progress: 15 ... ... ... 2020-10-28T22:36:42 I cue.firmware.update.controller: "K55 RGB" progress: 90 2020-10-28T22:36:42 I cue.firmware.update.controller: "K55 RGB" progress: 95 2020-10-28T22:36:42 I cue.firmware.update.controller: "K55 RGB" progress: 100 2020-10-28T22:36:42 I cue.firmware.update.process.proto_n: "0" exit code: 0 exit status: 0 Reported: true true 2020-10-28T22:36:42 I cue.firmware.update.process.proto_n: All FW update tools finished: true 2020-10-28T22:36:42 I cue.firmware.update.controller: "K55 RGB" FW update has been finished. From "Primary FW: 30.08; Secondary FW: 30.08; Bootloader FW: 3.00" to "Secondary: Application: 30.8" Can someone help me to understand this error ? I've a damage keyboard or i'm trying to use a bad file ? Thank you Link to comment Share on other sites More sharing options...
parisisal Posted November 17, 2020 Author Share Posted November 17, 2020 I still have this issue, could someone help me? Link to comment Share on other sites More sharing options...
xMacias Posted November 17, 2020 Share Posted November 17, 2020 Ignoring issues with the logs, you said the update through iCUE works. Is your keyboard working fine? Link to comment Share on other sites More sharing options...
Recommended Posts