Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Pages: 1
I can’t for the life of me get my Proxmark with Blue Shark to work with the new Android app. RDV4 git cloned the newest RRG/Iceman release. Compiled using Makefile.platform with BT Addon enabled and then firmware flashed to the RDV4.
Device pairs with BT on my Android device. However, it never asks me to select a port. When I open the app, in the discovery window, it shows no devices found. Blue light always flashes and never goes solid.
What am I doing wrong here? My android device is an older one. Is there a minimum supported device level or Android level?
Last edited by vrocco (2019-09-08 03:26:19)
Offline
Nop, you need to download a special pm3 firmware (based on 12th Aug source from RRG/Iceman) from proxgrinds site.
One of these days the repo will be able to compile with the needed android changes until then you need to this.
Here is a direct link
https://www.dropbox.com/s/416lsrqpr2lfe … 2.rar?dl=0
And you download the RRG RFID app from playstore.
Offline
Ahhh gotcha. I had assumed those changes had already been integrated into the repo. I’ll try this today. Thanks!
Offline
OK I just flashed that firmware and I get the same behavior. Looks like it flashed correctly. When I run the 3rd bat file, I get:
======. ===. ===. ====. ...iceman fork
==...==.====. ====. ..=. ...dedicated to RDV40
======..==.====.==. ====..
==..... ==..==..==. ..=. iceman@icesql.net
==. ==. ... ==. ====.. https://github.com/rfidresearchgroup/proxmark3/
... ... ... ..... pre-release v4.0
Support iceman on patreon, https://www.patreon.com/iceman1001/
[=] Using UART port /com4
[=] Communicating with PM3 over USB-CDC
[ Proxmark3 RFID instrument ]
[ CLIENT ]
client: RRG/Iceman
compiled with GCC 4.9.2
[ PROXMARK RDV4 ]
external flash: present
smartcard reader: present
[ PROXMARK RDV4 Extras ]
FPC USART for BT add-on support: present
[ ARM ]
bootrom: RRG/Iceman// 2019-08-12 23:21:45
os: RRG/Iceman// 2019-08-12 23:23:25
compiled with GCC 5.3.0
[ FPGA ]
LF image built for 2s30vq100 on 2019/ 7/31 at 15:57:16
HF image built for 2s30vq100 on 2018/ 9/ 3 at 21:40:23
[ Hardware ]
--= uC: AT91SAM7S512 Rev B
--= Embedded Processor: ARM7TDMI
--= Nonvolatile Program Memory Size: 512K bytes, Used: 272266 bytes (52%) Free: 252022 bytes (48%)
--= Second Nonvolatile Program Memory Size: None
--= Internal SRAM Size: 64K bytes
--= Architecture Identifier: AT91SAM7Sxx Series
--= Nonvolatile Program Memory Type: Embedded Flash Memory
However, it still does the same thing on android device. Bluetooth asks me for pin and pairs. says it is paired, but never asks me to specify com port. When I open the app, it still just says "No Devices Found". Anything else I can try??
Offline
looks like you got the special fw in place. Did you download the app from playstore? so you have the latest there aswell. I think you will need to accept giving it rights for using bluetooth.
You will need to email android@rfidresearchgroup.com , I have not insight to what might get wrong with the app, make some screenshots from the app and lets see what happens.
Offline
Yes latest version from play store. I’ll shoot an email to that address and see if they have any insights. Thanks
Offline
Be Careful !!!
The app still requires (and I don't know why) an active internet connection at start.
Are you sure to be connected when app displays 'RRG' logo ?
Offline
Yes I am connected to the internet when it runs.
Offline
Yes I am connected to the internet when it runs.
Yeah I also had the same problem. I only use the android specifically for testing so it doesn't have a SIM. When I am in the field I'm not usually connected to WiFi. I was getting pissed because it was connecting to Walrus app but not RRG and then I would get back to my place which has WiFi it auto connects to and it works. I would connect to WiFi in the field to re-download and install the app and then it works again. So yeah I run a hotspot with my phone connected to the android every time.
Offline
Thanks for the tip!
After flashing the firmware you provided, I finally manage to connect to the RRG app via Bluetooth.
However, the connexion is a bit buggy for me. It tells me sometimes that there may be some voltage issues.
Anyway, it works, and thank you for that !!
But now, I face another issue: I can no longer connect via the linux client because it's newer than the firmware
└──╼ $./proxmark3 /dev/ttyACM0
[=] Session log /home/mac/.proxmark3/log_20200212.txt
[=] Using UART port /dev/ttyACM0
[!!] Capabilities structure version sent by Proxmark3 is not the same as the one used by the client!
[!!] Please flash the Proxmark with the same version as the client.
[!!] ERROR: cannot communicate with the Proxmark
Should I downgrade the client? How?
Or is there another way?
Thanks for your help
PS: I found à not so great workaround.
Thanks to this post http://www.proxmark.org/forum/viewtopic.php?id=3975
That contains always up to date Windows client, I was able to retriever the Windows client from 2019/08/12 that match the firmware provided here.
Last edited by MrNonoss (2020-02-14 09:00:14)
Offline
Nop, you need to download a special pm3 firmware (based on 12th Aug source from RRG/Iceman) from proxgrinds site.
One of these days the repo will be able to compile with the needed android changes until then you need to this
Out of curiosity, what are those Android-specific changes in the special firmware? Are there proprietary software bits in it perhaps?
Offline
No really, it all is open sourced and now it builds proxmark3 binaries from RRG/Iceman repo via the android cmake, so all is well.
Offline
No really, it all is open sourced and now it builds proxmark3 binaries from RRG/Iceman repo via the android cmake, so all is well.
Hmm, I'm not sure I understand. In the page you link to, it still says one has to download and flash a special firmware from a RAR file from Dropbox to use the PM3 with the Android app. Either the documentation is out of date and I can use the firmware I built on my Linux box from the git repo head yesterday, or I need to use the Dropbox file with whatever magic it contains.
I guess my questions were: which is it? And if I need the Dropbox file, what's the magic in it?
Or am I a bit thick? That's entirely possible
Offline
The documentation is out of date. If that makes you a bit thick, I don't know.
The original problem is that Proxmark3 fw is strongly connected with same built client sw.
If you wanted to use the latest fw from RRG/Iceman repo, your client on the android app wasn't the same.
Now there has been added the android cmake, you can build the needed Proxmark3 client / lib to be used with the android app.
So building the android app, now can pull latest from RRG/Iceman repo to make fw and client to be used with it.
Not forgetting to flash fw.
No more precompiled unknown pm3 client lib with unknown fw to flash.
However you can not build latest fw/client from RRG/Iceman, flash your device and think it works perfect on the android app that you download. The one used in the app should be the release version v4.9237 if I understood it correct. That documentation isn't as clear as one might wish for.
Offline
Right, now I get it. Thanks for the explanation!
Offline
np
Offline
Hi, can I somehow expand the parameter list for LF reading via RFID Tolls. Updating the application did not help. For example, is it an LF continuous reading with the @ parameter? Thanks
Offline
Pages: 1