# If you want more than one PLATFORM_EXTRAS option, separate them by spaces: Here's a sample file I made, for turning on bluetooth, PLATFORM=PM3RDV4 Now, in that atform, we need to make a couple of changes, If you want to see all possible changes to the atform file, you can do it like this make PLATFORM= we need to rename it to atform cp atform Now, in that sourcecode, there's a file called. Next, let's get some sourcecode git clone For a Kali, Debian, Ubuntu, that would be apt-get install -no-install-recommends git ca-certificates build-essential pkg-config libreadline-dev gcc-arm-none-eabi libnewlib-dev qtbase5-dev libbz2-dev libbluetooth-dev Okay, now that's done, time to install some dependencies.

The reason for this is that IF it's enabled when we flash the firmware, ModemManager can begin transmitting to the PM3, thus destroying the firmware files, so kill it, disable it, or simply remove it. Loaded: loaded (/lib/systemd/system/rvice disabled vendor> So, this is a short article about building the firmware, and flashing the Proxmark3-REV4, for those inclined to do so :)įirst, we have to check that ModemManager is disabled in our OS, before we flash the PM3 firmware, so let's do that. BUT, a laptop can use the PM3 over serial bluetooth without any problem, how strange that may be. So, when I began to dig into it, I found out that the bluetooth firmware module is NOT built in, that you have to do yourself. Because I wanted to test out the RFID-Tools app for android, and found that the app did some strange things, and threw up some strange errors. Note that it requires the Proxmark3 Revision 4 hardware from lab410, and the bluetooth addon hardware. This is a short article about recompiling the Proxmark3-Rev4 firmware and adding Bluetooth support.

Proxmark 4