Native Android Proxmark3 client (no root required)
git clone -b v2.0.5 --recurse-submodules https://github.com/AndProx/AndProx.git
Changes:
snoop
operations.Changes:
printf
should now come through correctly.Release notes:
Mainline firmware 3.1.0 or later is required to use this build.
INTERNET
permission was added to support connecting to PM3 over TCP.
While TCP support is now available, the manifest blocks installation on devices without support for USB Host. This is to avoid confusion on devices without USB Host that have no easy way to set up a serial-over-TCP proxy (ie: everything that isn't ChromeOS or the Android Emulator).
ChromeOS support is still untested, and until I have a good way to allow use on ChromeOS but not every other Android device, this will continue to be blocked.
With a little socat
command, this allows you to easily debug on the Android
Emulator.
Changes:
ENTER
with a hardware keyboard on some devices would crash AndProx.The APK attached to this release uses Proxmark3 v3.0.1.
Corresponding firmware ELF for this version (android-hacks/v3.0.1-137-g9d8b41bd
) has been attached to this release -- it is what commit is referenced in the third_party/proxmark3
submodule. You'll need to flash that with a PC.
Post-release note (2018-05-26): Some devices made by Blackberry, Huawei, Samsung and Sony have a bug where they do not properly recognise the PM3. If you get a USB permission prompt only when you disconnect the PM3, then you may be impacted by this issue.
The firmware attached to this release still has this issue. In dmesg
, lsusb
or similar tools on a computer, impacted firmware will report Product: PM3
, fixed firmware will report Product: proxmark3
.
If your phone has this issue, you will need to flash with a PM3 firmware of f3dc6d5 or later as a work-around. Future versions of AndProx (with pre-compiled firmware) will include this patch.
This is the initial version of AndProx.
Many LF commands appear to work.
LF graphs are not available yet.
Scripting doesn't work properly, but most of the ground work is there.
Most HF card functions don't work properly yet (likely to be a firmware issue).
hf mf hardnested
commands use a lot of memory. In the event of running out of memory, it will
close the application without warning.
Anything output from printf
won't be displayed. PrintAndLog
will be displayed, but will not
be written to disk.
Probably doesn't exit or sleep cleanly, causing high battery use. Swipe the app away from the App Switcher when done, and unplug the PM3.