These builds are compiled with the newest version of ProxSpace and are always up to date. Here I will post the latest compiled Windows versions from the official Proxmark repository and some forks. If you want me to add a fork please contact me.
Having problems? Please look at the Known issues first.
Warning Proxmark3 Easy users: make sure your Proxmark does have 512KB of flash otherwise these builds might not work!
This is only a short instruction to getting your Proxmark3 up and running. There are many resources for the Proxmark, if you want to know more about the Proxmark here is a short list:
There many different hardware variations of the Proxmark3 and some builds are only working for a specific hardware variation. For a more detailed collection of the different hardware variations, I recommend to take a look at proxmark.com
Original: This is the original Proxmark3, with the green PCB. If you bought a Proxmark3 within the last years it is highly unlikely, that you bought an original Proxmark3.
RDV2: This version was designed by Elechouse and usually has a blue PCB. The Antennas on the RDV2 are extern and are connected with coax cables.
RDV3/Proxmark Easy: The RDV3, mostly referred as Proxmark Easy was designed by Elechouse as a lower cost variant. Many different clones with hardware differences of the Proxmark Easy exists. Most Proxmark3 Easy devices have a lowered flash size, that makes them unusable for some builds. Some Proxmark3 Easy devices have 512KB flash memory available and are able to run those builds. To check how much memory your Proxmark3 has available, check the microcontroller. If it is an AT91SAM7S256 you have only 256KB and if it is an AT91SAM7S512 you have 512KB of memory available.
RDV4: This is the latest version of the Proxmark3 and has many additional features that the previous versions do not have. That is why there are builds that are specific for the RDV4. The RDV4 has support for a Bluetooth module (blueshark addon). In order to use this module, it has to be enabled during compilation, that is why there are builds for it.
For more information about the Firmware differences look below. Download the build you wish to use. After downloading you need to extract the 7zip archive. For extracting choose a folder without spaces.
On Windows version prior to Windows 10 you have to manually install the driver, it is included in the .7z file. Open the Device Manager > navigate to Other devices > right click on proxmark3 > click Update Driver Software > Browse my computer for driver software > click on the Browse button > navigate to your Windows Driver folder > when prompted click on Install this driver software anyway. Your Proxmark3 should now appear.
Open the Device Manager on your PC and go to the Ports section. You should see COMX, where X is the port number. Make sure this port is your Proxmark3 by unplugging your Proxmark3 from your PC, now the port should be gone.
For the official build you need to adjust the COM port in Go.bat, FLASH - All.bat, FLASH - Bootrom.bat and FLASH - fullimage.bat. For all other builds there is no need to edit files, only if you need to force a COM port, e.g.: you are using two Proxmark3 devices. This can be done in pm3*.bat files.
If you do not like to change the COM port in the .bat files, you can force the proxmark3 to be on com5. This is done by: open Device Manager > right click on your Proxmark3 com port > Properties > Port configuration > Advanced > select COM5 as port.
If you are switching between the official repository and the RRG repository or you don’t know what firmware is running on your Proxmark3, flash the bootloader first followed by the fullimage. Otherwise, you can flash all at once.
Now your Proxmark3 should be updated, if there are any errors during the updating look at the Known issues.
To start the Proxmark3 client run Go.bat or pm3.bat, depending on your chosen build. Congratulation you now have a running Proxmark3. Now is a great time to have a look at the Proxmark Wiki for what to do next.
There are currently builds for two different Proxmark3 repositories. The official Proxmark repository and the RRG / Iceman repository, with the latter having multiple configurations.
This is the most stable firmware for your Proxmark3. It does work on all Proxmark3 devices and is a great starting point, but might lack some features.
The RRG / Iceman repository is bleeding edge with many new features, but it might not be the most stable. It is designed to take advantage of the Proxmark3 RDV4 hardware. This firmware requires 512KB of memory, if your Proxmark3 has less than that and you still want to use it, follow 256kb versions.
Please refer to the Differences section.
Open the Device Manager on your PC and go to the Ports section. You should see COMX, where X is the port number. Make sure this port is your Proxmark3 by unplugging your Proxmark3 from your PC, now the port should be gone.
There were community efforts to creating a GUI, but no available GUI does support all features of the Proxmark3 client.
All binaries are created using ProxSpace and the corresponding Proxmark repository. If you don’t trust the binaries and want to compile the Proxmark firmware yourself look at the Proxmark repository for more information.
Many users have no interest in compiling the Proxmark firmware themselves, especially when they only want to use their proxmark3 without modifying the source code.
This usually does happen when switching between the official repository and the RRG repository, it is nothing to worry about. Run FLASH - Bootrom.bat or pm3-flash-bootrom.bat first and then FLASH - fullimage.bat or pm3-flash-fullimage.bat
Your Proxmark has only 256KB of flash and the firmware you are trying to flash exceeds this size. You need do disable some features and compile the firmware yourself. See 256kb versions.
This usually happens when trying to flash the RDV4 firmware on a Proxmark3 that is not a RDV4.
When coming from an unknown firmware you might need to force the COM port, open pm3-flash-bootrom.bat and pm3-flash-fullimage.bat in the editor. Change the line that contains the bash command to bash pm3-flash-bootrom COM3 and bash pm3-flash-fullimage COM3, COM3 needs to be replaced with your acctual COM port. Additional information is found in the pm3*.bat files.
Please note that It does not work is not a valid error to report.
If you ran into an error during the usage of a precompiled build please contact me with following information:
Please use the forum thread.
The RFID HACKING BY ICEMAN Discord server.
Or contact me through Discord: Gator96100#2719