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.
Very strange behavior from my new RDV4 when working with Ultralight tags.
In standalone mode (and while connected to the console in standalone mode) it picks up the tag as soon as I bring it close, within 2 inches. Works first try every time.
When I do a <i>hf mfu info</i> or <i>hf 14a info</i> it has to have the tag actually touching the case, and even then it gives a "iso14443a card select failed" much of the time. I can run the command 5 times (without actually moving the tag a micron) and it only works once. The 14a works more than mfu but it still gives errors sometimes.
Simulation is the same thing- it works well with 4 byte UIDs but Ultralight and 7 byte UIDs fail most of the time. Often I have to keep the device in direct contact with the reader for 20 seconds or more for the simulation to finally work. Sometimes it never works. This is true for both standalone mode and tethered mode. Also, often when simulating 7 byte UIDs the UID read is incorrect.
The fact that standalone mode works so well when reading leads me to think that it is not hardware defective, however the simulation works equally poorly in both modes.
Is there a way to test the hardware to determine if it is working properly, and to determine if this is a firmware problem or not?
Thanks!
bootrom/os: master/v3.1.0-83-g1f61f19-dirty-suspect 2019-04-06 05:39:00
Last edited by cds333 (2019-04-19 02:51:35)
Offline
I suggest you pull latest code from RRG repo (compile/flash) since there was fixes for hf mf sim commited last night etc.
The hf 14a info sounds strange, I can detect tag from 0cm - 5cm distances.
hw status
hw tune
Offline
Ah yes; now it is working! Thanks very much!
They really should include this firmware before they ship. Mine came with an unknown version that <i>hw ver</i> could not recognize.
Last edited by cds333 (2019-04-18 05:13:50)
Offline
I suggest you edit your first post in this thread, and add the prefix [solved] to your title.
Proxgrind has factory flashed firmware from January 2019 I think. Since the production facility make a bunch devices at a time they don't update that often. Since you should have matching client/firmware on your device you should flash firmware once you compiled the client regardless. Like mixin' firmware and client leads to this kind of problems you experienced.
I can't stress enough repeating the advice to, read the instructions and update all what is needed to make the most of your RDV4. It isn't very hard if you follow the instructions.
Offline
Oh but I did follow the instructions- just the wrong ones!
I followed the https://github.com/Proxmark/proxmark3/wiki/Getting-Started and updated first thing. Apparently that is for the RDV2 or Easy models.
I should have been looking at https://github.com/RfidResearchGroup/proxmark3
Hopefully this will help someone else.
Offline
The official repository supports all revisions of Proxmark3 (including RDV4) for the benefit of all Proxmark3 users. Currently, the additional flash-memory of the RDV4 is not supported (until the same feature can be offered to pre RDV4 users as well).
The Wiki on https://github.com/Proxmark/proxmark3/w … ng-Started therefore should have worked for you as well. I have removed the outdated links in the "Getting Started" sections which might have led to confusion. Where exactly did you struggle?
Offline
I didn't mean to imply that the instructions were wrong, they worked.
I only had problems with the mfu features- reading and simulating ultralights specifically; I couldn't get those to work once I compiled & flashed the device. Switching to the RRG build fixed the issues for me. I assumed that this was because the RRG has been updated to work with the rdv4, but if that is not the case then I really can't tell you what went wrong.
Last edited by cds333 (2019-04-21 05:20:28)
Offline