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!
The “Dragon Ball Z: Kakarot – Update v1.031 CODEX Portable” is a enabling free, offline play of the Bardock DLC patch. It is useful for preservation or offline testing but is illegal, unsupported, and insecure for regular use. Official purchase and updates are strongly recommended for the full, safe, and legal experience.
Extract to your preferred drive (SSD recommended for faster loading). as Administrator. Power up your Ki and enjoy!
If you have obtained the DBZKakarot.v1.031.Codex.Portable archive (usually a 7z or RAR file split into 20+ parts), follow this checklist:
If you have specific issues with the or are trying to find system requirements for this version, let me know, and I can provide those details! dragon ball z kakarot update v1031codex portable
This is the headliner. Unlike the previous DLCs (Beerus & Golden Frieza), which focused on Super Saiyan God forms, Warrior of Hope is a grim, narrative-driven episode.
Even portable games need runtimes. The v1.031 Codex floppy includes a _Redist folder. Install VC_redist.x64.exe (no reboot required). Because the game is portable, you do not need to install this system-wide; you can place the DLLs in the game root.
: Typically found at C:\Users\Public\Documents\Steam\CODEX\851850\remote or C:\Users\[YourUsername]\AppData\Local\AT\Saved\SaveGames . The “Dragon Ball Z: Kakarot – Update v1
The v1.03.1 update and Codex Portable version of Dragon Ball Z: Kakarot have generated significant excitement among fans and gamers. The update addresses long-standing issues and adds new content, demonstrating the developer's commitment to the game's community.
Even a perfect release has quirks. Here are the three most common issues with this specific build.
The v1.031 update serves as a critical maintenance patch for the PC version of Dragon Ball Z: Kakarot. Released shortly after the game's initial launch, its primary purpose was to address early performance bugs, crash loops, and asset loading errors. Extract to your preferred drive (SSD recommended for
Significantly improved transitions when traveling between different world map areas.
: v1.031 improves native support for various gamepads, ensuring better compatibility for the "portable" style play often sought for Steam Deck or similar handheld setups. Pros and Cons Pros :
v1.031 included a shader pre-caching mechanism that Codex successfully ported without requiring an online validation. The portable version also strips out the Epic Games overlay, which was a notorious resource hog in the original release.
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