Cloning fdxb to xEM

[jop]

Trying to clone animal tag # to xEM
using
lf fdx clone -c 840 -n XXXXXXXXXXXX
goes through all the motions as it should
when I read the xEM with my chip reader it reads:
ID64
2018070749

[amal]

-n XXXXXXXXXXXX looks like too many X … 840 is the “c” code and there should only be a few more digits for the -n section…

[amal]

also… it’s possible you are not actually writing anything… or at least not successfully. The write process just spews bits into the ether… there is no validation done…

Check this video at 12:25 about that…

Cloning common 125kHZ chips to the T5577

My point here is that you might not be properly coupling to the chip to complete a successful write. Doing so with a proxmark3 on an implant can be a challenge because you have to hold it while trying to press enter on the keyboard. To help with that, you can add a delay to the command!

How to add a delay to Proxmark3 commands for implantees

Having an implant in your body and trying to use the Proxmark3 can be a tricky balancing act of trying to hold the Proxmark3 antenna just so over your implant and then trying to hit Enter to initiate the command. But, there is a way to solve this by using the msleep command along with command chaining to add a delay between pressing enter and the command you want to execute against your implant is actually run. For example, to perform an lf search with a 3 second delay before actually performing…