Proxmark3 failing to clone Awid fob

Support
1

Hello! Trying to clone an AWID fob for my condo
this is what I get
[+] AWID - len: 37 FC: 2578 Card: 87096 - Wiegand: 5092a871d, Raw: 01224482224b1787b1111111.

I have a cloned fob I can read as above and is identified as the t55x chipset. However, if I try to read the ORIGINAL fob provided by the condo, it shows the above AWID info, but says CHIPSET DATA UNAVAILABLE.

When I try to clone the AWID to a t557 125 khz sticker or the provided blue tag with the cloner, I type

lf awid clone --fmt 37 --fc 2578 --cn 87096

All the cards I try to clone this way are not able to be read by lf awid reader or auto.
What am I doing wrong?

1 Like
2

Is your PM3 client up to date?

When you lf search one of those cards that doesn’t read, does it detect the T5577 chipset still?

It may just be a coupling issue, play around with moving the card on/under/around the PM3 and re-run the clone command a couple of times

1 Like
3

its very strange that the cloned fob is a t55xx chipset but only is discoverable as AWID? I have also managed to accidentally wipe the original however I have the AWID info thankfully

1 Like
4

I am concerned I am not addressing the Wiegand

1 Like
5

What do you mean?

…What do you mean?

6

i used a different chip and it did copy over.
however the source chip reads:
AWID - len: 37 FC: 2578 Card: 87096 - Wiegand: 5092a871d, Raw: 01224482224b1787b1111111

and my copied chip reads:
AWID - len: 37 FC: 2578 Card: 87096 - Wiegand: 15092a8710, Raw: 01227482224b178411111111
this is what I mean that I am concerned the Wiegand is not addressed

1 Like
7

Can you just use the awid clone command and supply the raw data vs the fc and cn data?

1 Like
8

That doesn’t seem to be an option for awid clone, unfortunately

9

it appears the Wiegand is off by 1 bit somehow? does this help?

1 Like
10

Screenshot_20240820_190917
It’s actually off by 4 bits

Have you tried the cloned card on the actual awid reader, not just the PM3?

11

Yes, no response

1 Like
12

i fixed the issue using a solution in another post. I have to manually code the 4 blocks from the raw data since it seems the AWID clone feature is off by 1 in parity

1 Like
13

Could you link to that post, please?

Glad you got it working!

2 Likes
14

Can anyone help me with this AWID fob? - Support - Dangerous Things Forum
repsonse by Dangerousenti

4 Likes
15

Hi jlatz,

Very grateful for your post and you finding the other article link!..I am still kind of a newbie… I had the same issue for the past couple weeks…the Weigand and Raw data was coming out wrong in the cloning process (also for the same AWID 37 bit fob you encountered).
My Wiegand was changing from 1516b0065d to 1516b00650 (in the copy)…
incidentally lf t5 dump wasn’t working for the original fob…thankfully the raw data was present in addition to the Wiegand in lf search.

Much obliged!
Nauman

2 Likes