empiredud Posted January 24, 2016 Share Posted January 24, 2016 I got my new void headset at Christmas and I love it. Sadly, today I updated the Corsair Utility Engine to 1.14.43, and my device just completely stopped working. No lights are lighting up, it doesnt turn on even when I hold the power button, I doesnt charge (no light when I plug it in). Im not sure what happened but my headset has gone obsolete. I am on windows 10 64x. I checked the logs and I think I found something odd: [2016-01-24T00:03:46]: UserSessionInfo: locked changed to 0. [2016-01-24T00:03:47]: UserSessionInfo: connected changed to 1. [2016-01-24T00:03:47]: UserSessionInfo: local changed to 1. [2016-01-24T00:03:51]: UserSessionInfo: locked changed to 0. [2016-01-24T00:03:51]: UserSessionInfo: connected changed to 1. [2016-01-24T00:03:51]: UserSessionInfo: local changed to 1. [2016-01-24T00:03:55]: UserSessionInfo: locked changed to 0. [2016-01-24T00:03:55]: UserSessionInfo: connected changed to 1. [2016-01-24T00:03:55]: UserSessionInfo: local changed to 1. [2016-01-24T00:03:55]: Device profile (meta) for device vid=738 pid=1705 not found. [2016-01-24T00:03:55]: Device profile (meta) for device vid=1770 pid=ff00 not found. [2016-01-24T00:03:55]: Device profile (meta) for device vid=1038 pid=1000 not found. [2016-01-24T00:03:55]: Device profile (meta) for device vid=1038 pid=1000 not found. [2016-01-24T00:03:55]: Device profile (meta) for device vid=1038 pid=1000 not found. [2016-01-24T00:04:26]: Device vid=1b1c pid=1b27 is marked 'slow startup'. [2016-01-24T00:04:26]: Device vid=1b1c pid=1b27 is marked 'slow startup'. [2016-01-24T00:04:26]: Device vid=1b1c pid=1b27 is marked 'slow startup'. [2016-01-24T00:04:32]: Created new device object: VOID Wireless; ready: 0 [2016-01-24T00:04:32]: Attached to device object VOID Wireless: b=1 a=1 [2016-01-24T00:04:32]: Attached to device object VOID Wireless: b=1 a=5 [2016-01-24T00:04:32]: Initializing VOID Wireless... [2016-01-24T00:04:32]: Initialized (st=1) VOID Wireless. [2016-01-24T00:04:32]: Device insertion processing complete for VOID Wireless. [2016-01-24T00:05:00]: Firmware Download: Aborting idle process not supported. [2016-01-24T00:05:57]: SdkController. Requesting working state leave because of transition to Suspended or Shutdown state. [2016-01-24T00:05:57]: Requesting working state leave because of transition to Suspended or Shutdown state. [2016-01-24T00:05:57]: Leaving working state. Something got aborted, or I don't know. During the update, something went wrong and it killed my headset. When I plug it in with the cable, it says the USB device i connected malfunctionned. It is not the USB drivers that are the problem since they work fine with my other things. I need help. ========================================================== Solution (worked for me): I sent a ticket to support and received my answer. "Created By: Justin G. (1/25/2016 9:21 AM) Let's focus on the transceiver (dongle) first - what happens when you insert the dongle into a USB port in your system? Is it detected/listed under Devices and Printers? If so, please view the article below and let us know of any further questions. https://corsair.secure.force.com/kA140000000Cmgi?popup=true&caseId=5004000000tFHIX " Turns out this worked for me. My dongle (usb) was detected in Devices when I plugged it in and all I had to do is follow the steps from the link above. I basically force updated it and everything went fine. My headset is now working well and charging :) . Hope it works for you guys, thanks for the comments! Link to comment Share on other sites More sharing options...
Jefro3uk Posted January 24, 2016 Share Posted January 24, 2016 I have exact same problem. It failed with the firmware update saying it could not complete, now my headset will not charge, turn on or register as plugged in via usb. I have even tried on another machine as well to no avail. It has been an awesome headset up to this point which is such a shame. Link to comment Share on other sites More sharing options...
Toasted Posted January 24, 2016 Share Posted January 24, 2016 Have you tried putting the headset into bootloader mode? Press the volume rocker switch down while plugging the USB cable in. Does Windows detect the headset as Avnera AV6302? If so, open CUE then force flash the firmware. Link to comment Share on other sites More sharing options...
empiredud Posted January 24, 2016 Author Share Posted January 24, 2016 Have you tried putting the headset into bootloader mode? Press the volume rocker switch down while plugging the USB cable in. Does Windows detect the headset as Avnera AV6302? If so, open CUE then force flash the firmware. I tried this, and it still says the USB device malfunctionned. The device is still in some sort of shutdown state and wont respond to anything. I have the same problem as Jefro3uk. Link to comment Share on other sites More sharing options...
Sharkateer Posted January 24, 2016 Share Posted January 24, 2016 I have exact same problem. It failed with the firmware update saying it could not complete, now my headset will not charge, turn on or register in CUE as plugged in via usb. I have even tried on another machine as well to no avail. It has been an awesome headset up to this point which is such a shame. Exact same problem. I am running CUE 1.13.36, but upon updating my VOID headset today, it will not power on, does not seem to be in bootloader mode (does not detect as Avera or anything similar in Windows). When plugged in to Windows 7 64 bit OS, it registers as an unknown USB device in Devices and Printers. CUE won't see it at all though, and doesn't detect that I plugged it when it says 'connect USB to headset' during firmware update steps. Please advise! EDIT:: I've got 2 VOIDs on 2 different computers. The one that updated wont work on either machine now. Also, I've had lots of trouble with VOIDs in the past, so I'm no stranger to troubleshooting them... Really wondering why I bought the second one lol Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.