Blackshark V2 Pro Firmware Updater stuck | Razer Insider

Blackshark V2 Pro Firmware Updater stuck

  • 2 December 2020
  • 2 replies
  • 108 views

Gentlefolks,

I have a brand spanking new headset with a Chroma V2 stand, and as any aspiring geek, I went for software and firmware updates.

Upon execution of the BlackShark V2 Pro_FirmwareUpdater_v1.00.11_r2 file from the Razer support site, everything followed the script until 50%, at which it just stopped. The application did not per say hang, stop responding (per the TM), it simply stopped progressing.

There is also this lovely green "do not power off or unplug' warning as is typical of any form of firmware updater I have seen in the past.

The expected update was from firmware 1.00.09 to 1.00.11... but alas, I have no idea what is going on.

And of course, Razer is not allowing for phone tech directly, so this has to go to the forums with my machine in limbo, and non-working headset with the updater still on screen awaiting help.

Any good input here with this firmware updater would be appreciated!

IVORYdailyMintCream343

Edit:

Update 1... an off-script portion, where the PDF did not state anything about the power to the headset needing to be turned on (even though the updater detects the headset and indicates to proceed when the headset is corded in on USB).

A pop up window, without a task bar preview, was under the updater now indicating that it could not find the headset (again, the updater itself did show if found, and proceeded to the 50% mark).

Now it stops at 100%, and never gets to the last screen with a close button. Oh come on...

This topic has been closed for comments

2 Replies

Hey. This guy had the same issue and was able to make it work. Maybe try what he did and if it works for you.
Userlevel 7
Is the dongle for the headset plugged directly into your PC or to the USB hub on the headset stand? Please send me the serial number of the headset and screenshots of the stuck firmware update. You can upload the images on GDrive or Dropbox and send me a shareable link. Do check out the link shared by @saffronfs7, that could do the trick for you.

*Locking the thread to curb the conversation to PMs.