Version: 2.0.4

Prototype / work-in-progress native Android client for Proxmark 3, which doesn't require root, permission changes or other messing about with kernel modules.

This is intended to become a replacement for Proxdroid and other "root required" Android forks.

This uses the Android USB Host API and mik3y's USB Serial for Android driver in order to access the Proxmark's USB ACM interface from user-space Java code.

Opt-in to the beta on Google Play | Direct APK download also available

See COMPATIBILITY.md.

• Cross compiles to armeabi, armeabi-v7a, arm64-v8a, x86 and x86_64. Only really tested on ARM.

• Many LF commands appear to work. Some devices need a Y cable and external power source for HF commands. See COMPATIBILITY.md for details.

• LF graphs are not available yet. (Issue #1, Issue #2)

• Scripting doesn't work properly, but most of the ground work is there. (Issue #3)

• 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. (Issue #5)

• Flasher has not been implemented.

• 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.

1. Install the APK, or side-load the APK from GitHub.

2. Plug your Proxmark3 into your Android device.

3. Run AndProx, and accept the permissions bump.

4. Press "Connect"

5. Try hw version, hw status and hw tune to test out the device!

AndProx will write files to Internal Storage, in the proxmark3 directory.

Use the System Info to show what USB devices AndProx can see. You should see:

• USB Host: yes

  (If it says "no", your device doesn't support USB Host.)

• Found >1 USB Devices; (9ac4:4b8f; name = null)

  (If it shows 2d2d : 504d -- you have an old firmware and should upgrade.)

  (If it shows some other ID -- you may have a third-party firmware and should switch to mainline.)

  (Some devices have WiFi/Bluetooth radios connected over USB, you can ignore those.)

  (If it shows nothing, then your device isn't exposing USB devices properly, or may have the cdc_acm kernel module loaded when it shouldn't.)

• Found 1 suitable drivers; CdcAcmSerialPort

  (If it shows no suitable drivers, but the correct IDs are showing, then this is probably a firmware issue.)

See HACKING.md.

Do not download the ZIP file from GitHub -- it will not work!

Copyright 2016-2018 Michael Farrell.

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.

Under section 7 of the GNU General Public License v3, the following additional terms apply to this program:

• (b) You must preserve reasonable legal notices and author attributions in the program.

• (c) You must not misrepresent the origin of this program, and need to mark modified versions in reasonable ways as different from the original version (such as changing the name and logos).

• (d) You may not use the names of licensors or authors for publicity purposes, without explicit written permission.

AndProx includes several third-party components under other licenses. More detail of these components is shown in third_party/README.md.