If your steam crashes during an FW update or if you unplug/turn off the controller while updating the controller will be "bricked".

Being bricked is a state where your controller either has no firmware or the firmware installed is damaged. This means your controller will not be working at all! Don't worry, there is a manual FW update procedure that is both easy and fast that should get you back up and be running in no time!

This procedure is also useful for those who need to revert their controller to a previous version of the firmware in case they encounter a bug. Generally speaking, this should not be necessary and whatever the latest version installed by the steam client should be fine. As beta updates are made there are often firmware updates included in beta and they can have bugs or issues.

The manual process MUST be done wired. The steam controller has a mode where it will show up to your OS, in this case Windows, as a removable USB device where we can copy the firmware file right onto it.

The first step is to plug in the SC wired via a micro USB cable while holding the right trigger until it clicks. If the USB device does not show immediately, don't worry. I had to wait for the driver installation to fail, unplug my controller and plug in again. After doing this the USB device (CRP DISABLED) Showed up perfectly fine.

Okay now, this is a little confusing for the first timer. We are going to get the FW file right from Valve. There are a few things you have to do to get the latest version. The benefit of doing it this way is that you will always have the lastest version of the firmware. This will also allow you to get ahold of any version of the steam controllers firmware that has been released so for working around a specific bug, this can be very helpful.

The biggest issue here is that we don't know what the exact name of the file is so we have to go through a few steps to ensure we get the correct file.


First you need to CLICK HERE to get the firmware.vdf file. Don't worry, this is just a simple text document so you won't need anything special to open it. You can use notepad or Wordpad if you prefer, any text editor should be able to display this file perfectly.


Now that you have opened up this text file you should see a list of the available firmwares for the SC. The formatting should look something like this.

At the time I am writing this update to the guide 17 was the last version available so for the purposes of this guide, I am going to use this as the main example.


You will notice just after "firmwarebinary" that it will not only display the exact name of the file itself but will also show you the second half of the URL that you can download the file from. in this case it is "/firmware/vcf_wired_controller_d0g_56c78c01.bin"

The first half is so for this example I would type in into the address bar of any browser. After this, the file should download. These files are incredibly small and should take only a few seconds to download fully. Just remember to remove the quotation marks as they are not needed in the URL.


From here all you need to do is rename the FW file from "vcf_wired_controller_d0g_56c78c01.bin" to simply "firmware.bin" and have it copied to a place where you can find it, like the desktop.


A special thanks goes to [bli] Pila for pointing out that I should be doing this instead of having a link to Dropbox. This way anyone can get the latest version and I don't have to keep pulling the firmware files right off my controller.

Here is where you actually do the flash. If there is a firmware.bin present on the controller please delete this. From here it is just as simple as drag and dropping the NEW firmware.bin right onto the attached USB device.

It is VERY important that you wait. I would wait at least 1-2 full minutes to make sure IO operations to this USB device finished before you attempt to remove the USB device.

Make 100% SURE you eject the USB device and don't just unplug it! Sometimes Windows will tell you the device is busy. If this is the case you can wait another minute and try again. If this continues, we can be more or less positive the process is done and Windows is just being Windows. If this happens, shutdown your computer and unplug the SC when it is off.

Here is the command line to give the steam controllers USB device permissions to be seen in Linux. I don't use Linux so I assume anyone who does is familiar with the command line and how to use it. You need to make sure the udev rules are set properly or the controller won't function correctly. Normally you will have done this already and it is automatic in SteamOS for out of the box functionality.


WARNING: A direct copy to the CRP DISABLED USB device that is, the steam controller, will not work under Linux. This is the command to do the copy via the command line.

First, set your active directory to the steam controller CRP DISABLED

Then, the flash itself.

WARNING: A direct copy to the CRP DISABLED USB device that is, the steam controller, will not work under OSX. This is the command to do the copy via the terminal.

First, set your active directory to the steam controller CRP DISABLED


Second, you need to use the CAT command to do the transfer the firmware.bin over to the SC itself. As I do not personally use OSX my understanding of this command over the CP command is limited but this command does not copy some garbage data that the SC simply can not use and is too large to fit on the SCs internal flash.


After this you should be all good!


Special thanks go out to DTM and also his dad for both figuring this out and filling me in on how it is done so I could add this to the guide.

That's it! Your SC will have been unbricked! From here, you should plug the controller back in and attempt to update the FW through steam big picture mode while opted into beta to make sure the FW is the latest version available. Using a wired connection for the update should mitigate the possibility of encountering connection issues during an update and possible bricking the controller again.

OPT INTO BETA! (Optional)
In BPM go to settings (the gear icon on the top right) > System > Participate in beta checkbox
WAIT for steam to restart and install the beta client. Just remember the steam beta client is recommended for steam controller users as it includes the latest features and fixes. Just remember this is still a beta and is not a full stable version. If you experience any issues you should first try reverting to the stable branch by opting out of beta to confirm your issue as a bug. Beta client may also include beta FW updates as well.

FORCE UPDATE CHECK (Recommended)
In the same System menu check for updates and it will also update the FW if needed. FW will only update from in BPM!