Identfying mystery rfid keyfob

Support
21

Yeah, I’m not getting that

[usb] pm3 --> lf em 410x
help This help
demod demodulate a EM410x tag from the GraphBuffer
reader attempt to read and extract tag data
sim simulate EM410x tag
brute reader bruteforce attack by simulating EM410x tags
watch watches for EM410x 125/134 kHz tags (option ‘h’ for 134)
spoof watches for EM410x 125/134 kHz tags, and replays them. (option ‘h’ for 134)
clone write EM410x UID to T55x7 or Q5/T5555 tag
[usb] pm3 --> lf em 410x_clone help
help This help
410x EM 4102 commands…
4x05 EM 4205 / 4305 / 4369 / 4469 commands…
4x50 EM 4350 / 4450 commands…
4x70 EM 4070 / 4170 commands…
[usb] pm3 -->

I should be on the latest Iceman.

[ CLIENT ]
client: RRG/Iceman/master/v4.9237-2844-g2646925ad 2021-01-13 17:03:54
compiled with MinGW-w64 10.2.0 OS:Windows (64b) ARCH:x86_64

[ PROXMARK3 ]
firmware… PM3OTHER

[ ARM ]
bootrom: RRG/Iceman/master/v4.9237-2844-g2646925ad 2021-01-13 17:03:39
os: RRG/Iceman/master/v4.9237-2844-g2646925ad 2021-01-13 17:03:47
compiled with GCC 8.4.0

22

Damn, that sucks. It definitely shows up when you run lf em 410x though, so at least now you know it’s clone instead of write. I’m definitely not using the very latest iceman build (I think mine is from mid December last year), so that could be the cause of it. I’ll try updating and see if I get the same issue.

23

All fixed! Nothing was wrong.

lf em 410x clone -u 12345678

Looks like the current Iceman has deprecated the syntax used in basically every googlable example.
410x_clone does not work like 410xwrite/410x_write used to.

2 Likes
24

Woohoo its fixed!!!

1 Like
25

I actually ran into this earlier today haha, got a few new proxmarks and was testing them by cloning a UID to a T5577 test card. The help text literally tells you the wrong syntax as examples…

Shouldn’t be a hard fix for him to update the help text, but it’s annoying.

26

Thats the exact number of exclamation points I said too!!!

27

So, answered my original questions-
Bodet keyfob is a T5577, not sure if its password protected but that was never a concern of mine.
I’ve rigged up a test run off the full access control board, our time attendance fobs can be read and enrolled into it with no issues.
I can clone our original fobs into a T5577, I’m taking one into work to double check it tomorrow.

I just need lockdown to lift now so I can book in to get my hand pierced…

28

updating my own firmware… i will explore the help text and ping iceman

1 Like
29

Are you saying THIS is not the latest???

██████╗ ███╗   ███╗ ████╗      ...iceman fork
██╔══██╗████╗ ████║   ══█║       ...dedicated to RDV40
██████╔╝██╔████╔██║ ████╔╝
██╔═══╝ ██║╚██╔╝██║   ══█║     iceman@icesql.net
██║     ██║ ╚═╝ ██║ ████╔╝    https://github.com/rfidresearchgroup/proxmark3/
╚═╝     ╚═╝     ╚═╝ ╚═══╝  pre-release v4.0

:rofl:

1 Like
30

well, I’m updated to today’s push… v4.9237-2866-g0e18443b0 2021-01-14 12:44:00

the LF commands look pretty straightforward, just not what one might be used to from old firmwares… Iceman has been making solid ground on standardizing the UI and command set from a adhoc group of features from disparate developers getting their PRs merged into the main codebranch. It’s not a simple undertaking, but his work is quickly putting the proxmark3 on solid ground as an actually usable piece of kit even for basic noobs.

image
image741×537 15.2 KB

so at this point I suggest going into your proxmark3 folder and issuing git pull and then make clean && make all and pushing the latest firmware.