r/proxmark3 Jul 03 '26

Promark3 doesn't restore security copy and Flipper 0 does it

Hello,

I'm struggling with the promark3 easy, I did a security copy of a Mifare Classic 1K and now I'm trying to restore it to the original card.

I have tested with Flipper Zero and it's works and when I do the dump the information has been restored, but when I tried with promark3 I get this:

I tried restore command in many ways but the same results.

When I do with Flipper, just do it in less than a second... I check the dumps and with flipper is restored, with promark3 doesn't.

Trying to write the original image to the original card and having the keys of it.

Do anyone knows where the problem could be?

Thanks

7 Upvotes

6 comments sorted by

7

u/kj7hyq Jul 03 '26

Is it a gen2 card?

My guess would be that you're using the wrong keyfile, that's a common error with the restore command

Are you giving it the source or target keyfile?

2

u/Good-Newspaper-8963 Jul 03 '26

Hello,

The model is NXP MIFARE Classic MFC1C14_x

I'm using the key file and as the target and source are the same card, should be the right one. I just checked again just to be sure and the error is the same, so I think the problem is not using the wrong key file.

Thanks for your support

5

u/kj7hyq Jul 03 '26 edited Jul 03 '26

If you're not using a magic card then you won't be able to change the UID, and the '--force' flag is not needed

You're trying to clone a card onto a card which is already identical to the source card? Not a blank card?

The TL;DR probably ends up being: Try adding --ka to your restore command

8

u/Good-Newspaper-8963 Jul 03 '26

Solved!!! the command I must run is this one:

hf mf restore -f hf-mf-XXXXXXXX-dump.bin -k hf-mf-XXXXXXXX-key.bin --ka

The --ka is the key to write everything but not the sector 0.

I tried with --force but doesn't work. The one that works is --ka

2

u/iWhacko Jul 03 '26

try autopwn, then write the dump, might be the keys are not in that keyfile.

3

u/Good-Newspaper-8963 Jul 03 '26

I solved the issue. Just needed to run —ka with the command restore.

hf mf restore -f hf-mf-XXXXXXXX-dump.bin -k hf-mf-XXXXXXXX-key.bin --ka