Jump to content
Corsair Community

CRP disabled issue [SOLVED]


Recommended Posts

First of all: I am not a corsair support officer.

However, due to the fact that I have not received a response from support anywhere, neither on the forums, nor on the website, nor anywhere else on the Internet, I still found a solution to this problem.

Therefore, I would like to save the nerves and money of many users of corsair devices who are faced with this problem.

I duplicate the instruction I found on the Discord channel from a person who once helped people on this forum.

But now on the forum, it is impossible to find a solution to this problem. And so the instruction is as follows:

 

please the below instructions on how to do a hard firmware rest of your device. Please note THIS WILL NOT WORK FOR WIRELESS DEVICES. I will not be providing FW images for wireless devices due to the fact that there is a much higher chance of can brick the device and I do not want to be responsible for any incidents.

 

You can not use a FW image from a similar device! Please make sure your device name 100% matches the label. The firmware might load on to the keyboard and show up in iCUE but there is a good change it will damage the device over time. Eg. [K70 RAPIDFIRE] is not the same as [K70 RGB RAPIDFIRE] or [K70 RGB MK2]

 

1: Unplug your keyboard from the computer.

2: Locate the small pinhole underneath your keyboard For some, this will be located near the polling rate switch by the cable. On others, it will be located underneath on the tilt legs on the bottom of the keyboard.

3: Using a small paperclip or push-pin, press down on the button inside the pinhole.

4: Plug your keyboard/mouse back into the computer, while holding down the pinhole button.

5: Once it is plugged back in, your computer should recognize a drive called CRP_Disabled. Please open this.

6: Download the correct firmware file below. If it is compressed into a .RAR / .ZIP file, please extract this file to an easily found location on the computer.

7: Delete the file FIRMWARE.BIN from the CRP_DISABLED drive, and then place the file with ISP in it’s name to the CRP_Disabled drive.

8: Once you have performed the steps above, please unplug your keyboard and then plug it back in. The device should return to normal.

 

If your device still shows the CRP_DISABLED drive after following these steps you might have the wrong file or there could be a hardware problem with your device. Please contract Corsair Support at https://help.corsair.com/hc/en-us

 

STRAFE RGB

K70 RGB MK2

K70_RGB

K70_RAPIDFIRE

K70 RAPIDFIRE RGB

K90 RGB

K65_RGB

K65 LUX RGB

 

P.S. Appeal to the administration and moderators. If possible, place it in a fixed topic. Or at least, I ask you not to delete this message, because it is impossible to get intelligible answers from you on how to fix this error. I spent many hours trying to find a solution to this problem, and eventually I found it. Give people a solution to this problem to keep them happy. Thank!

Edited by Dmitrys
Link to comment
Share on other sites

  • Corsair Employees

As a PSA for other users regarding the post above.

 

Using the wrong firmware file with this method can potentially brick your keyboard irreversibly.

 

We do not provide a public repository of these files for exactly this reason.

 

If you require the firmware file for a hard reset; please contact Corsair Support directly, and you will be provided with the latest file that is appropriate to your board.

https://help.corsair.com/hc/en-us

 

DO NOT use files provided by anyone other than an official Corsair representative; as this will void warranty.

 

~ Mordred

Link to comment
Share on other sites

  • 1 month later...
  • 3 weeks later...
  • 2 months later...

Either the K70 RGB Mk2 file is incorrect or support gave me the wrong one... Mine is a low profile but my file from Corsair support is titled K70MK2LP_ISP_3.24.22.bin

Unfortunately in my case the keyboard is stuck in bootloader mode even after following Corsair's directions to the T. Also, I backed up my original firmware file but my mac says it cannot be copied back to the keyboard because it's 4kb too big. Which is super strange.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...