Hi everyone,
I'm posting this because I believe this may not be an isolated issue, and I'd like to know if anyone else has experienced the same problem with the Basilisk V2 and others devices.
My Razer Basilisk V2 was working perfectly normally until I changed its profile in Razer Synapse. Immediately afterwards, the mouse started repeatedly connecting and disconnecting around 5–6 times. Then it completely stopped working.
Now:
- The mouse does not turn on.
- The RGB lights are completely off.
- Windows no longer detects it as a mouse.
- When I connect it to the PC, it appears as a removable device showing "CRP DISABLED".
- Inside it there is a firmware.bin file.
- I have tested it on multiple computers and the behavior is exactly the same.
- Reinstalling the mouse drivers does nothing.
What is particularly frustrating is that this happened immediately after using Razer Synapse to change the mouse profile. This is not a mouse that gradually developed a hardware problem — it was working normally until the Synapse operation, followed by the repeated disconnect/reconnect cycle.
I have already contacted Razer Support . Their support agent told me that the issue appears to be hardware-related and that they do not have a factory firmware file available for me to attempt a recovery.
However, I have found other reports from users experiencing the same CRP DISABLED / firmware.bin situation with Razer devices, including other Basilisk V2 users.
This makes me concerned that there may be an issue involving Synapse, firmware handling, or profile switching that can leave the mouse in a non-functional bootloader/recovery state.
I am not asking for an unofficial firmware or a risky procedure. I would simply like Razer to investigate this properly and provide an official recovery solution, or take responsibility for repairing/replacing the affected device if no recovery method exists.
If anyone else has experienced this exact problem with a Basilisk V2, especially after using Synapse or changing profiles, please comment below. It would be useful to know how widespread this issue is and whether Razer has provided a solution in other cases.
Razer: I would really appreciate it if this could be escalated to the team responsible for Synapse/firmware rather than being treated solely as a normal out-of-warranty hardware failure. The timing and circumstances of the failure strongly suggest that the software/firmware deserves to be investigated.
Thank you.
