Razer BlackShark V2 Pro (2023)  | Razer Insider
Skip to main content
Question

Razer BlackShark V2 Pro (2023) 


Hi,

I'm hoping someone here can help because I've exhausted most of the usual troubleshooting options, and I'm struggling to find any information about performing a proper hardware reset on this headset.

Device: Razer BlackShark V2 Pro (2023), PC version.

How the issue started

Everything was working normally until I connected the headset to my iPhone via Bluetooth. I had also temporarily removed the detachable microphone.

After reconnecting the microphone and using SmartSwitch to return to 2.4 GHz wireless mode on my PC, the headset continued playing audio normally, but the microphone initially stopped working.

I opened Razer Synapse 4 to investigate and discovered that it was reporting the headset as disconnected or powered off, despite the headset being powered on and actively playing audio through the USB wireless dongle.

The microphone eventually started working again, but the other issues remain.

Current symptoms

1. Abnormal power-button behaviour

When the headset is disconnected from USB-C power, it immediately shuts down.

Attempting to turn it back on results in the headset repeatedly announcing "Power off" instead of "Power on".

This is particularly strange because, when the headset previously ran out of battery normally, it would simply stop powering on. It wouldn't repeatedly play the shutdown announcement. Also there is no audible "Battery low".

2. Battery percentage stuck / apparent charging failure

Before this issue, the headset worked for approximately 2–3 days between charges, with no signs of battery degradation or charging problems.

Since the issue began, my iphone has displayed a battery percentage stuck at approximately 10%, without increasing or decreasing. And synapse shows as charging but stays on 0%.

Even after leaving the headset charging overnight, it still immediately shuts down when USB-C is disconnected.

3. Synapse fails to detect the headset

Synapse reports:

"Device is switched off or needs to be connected via 2.4 GHz."

However, the headset can still play audio and transmit microphone input through the 2.4 GHz dongle when connected to USB-C power.

4. SmartSwitch / Bluetooth switching behaves abnormally

The SmartSwitch button no longer reliably switches between Bluetooth and 2.4 GHz mode when double-pressed.

Given that the problem started immediately after switching between my phone and PC, I'm wondering whether the headset's internal controller has entered some kind of incorrect connection or power state.

Troubleshooting already attempted

  • Disconnected and reconnected the 2.4 GHz USB dongle.

  • Switched between Bluetooth and 2.4 GHz modes.

  • Tested with the microphone both attached and removed.

  • Used a separate USB wall charger with the PC completely shut down. The power-off problem persists independently of Windows and Synapse.

  • Left the headset charging overnight.

  • Successfully updated the headset using the correct official BlackShark V2 Pro (2023) firmware updater.

  • Restarted the headset and Synapse multiple times.

None of these steps has resolved the remaining problems.

Previous occurrences

This is not the first time something similar has happened.

I've experienced Synapse detection and connection issues with this headset before, going back to when I first got it. On previous occasions, repeatedly reconnecting the headset and switching between Bluetooth and 2.4 GHz eventually restored normal functionality.

However, this is the most severe occurrence so far, particularly the inability to operate without USB-C power.

Does anyone know whether the BlackShark V2 Pro (2023) has a way to perform a complete internal controller reset or hardware power cycle, rather than just resetting EQ profiles through Synapse?

Is there a documented firmware recovery procedure, or has anyone encountered and successfully resolved these particular symptoms?

I've found several threads describing very similar issues, but unfortunately, the troubleshooting was moved into private messages.

Any technical advice or information from someone who has experienced this would be greatly appreciated.