Mifare-Windows-Tool

Mifare-Windows-Tool copied to clipboard

Wanted to write a new card today, and got the following errors:

I tried both copying an existing nfc card, and writing a previous dump. Reading seems to work (however, it was unable to find the keys itself).

Is this a user error?

When you wrote previous dump, the copy was working ? You need to erase the target card at first or at least read it (the target card) because to copy a dump you always need source AND TARGET (destination) tag keys

I"ve used that dump before on my Linux box, so it should work fine. I also tried making a new dump just to make sure and got the same error. The cards should be magic, but I also tried without writing the uid. And I tried using both A and B key. I"m going to download an earlier build just to make sure.

Ok, so I uninstalled all drivers and such, just to test. I get a prompt upon starting the application saying the following:

I installed the native driver with the reader unplugged, then installed libusbK-3.1.0.0-setup.exe. After this, I still get the message above. Not sure why the application wants to reinstall, but unless I do it it says it access the reader. The light on the reader stays red, but I'm allowed to read the card I put on. No errors. If I try to write to it, it'll say the card is known and wants to know if I still want to read it. I select yes, it reads, but nothing happens. Same thing happens if I go back to try and write to it again. If I select "no", I get to the "write tag" dialog. I select "Write Dump (Clone)", "Use these access...", "Use Key A", select a source dump I just made and click "Start Cloning". This time it worked, but it's failed at least 10 times. Doing it again with the same card makes it fail. Trying to format cards just make the app force close.

Any idea as to what I should do?

1 - the driver to use : https://www.acs.com.hk/en/driver/3/acr122u-usb-nfc-reader/ 2 - then did you install libusbk with CLIENT installer ? after installing, you need to install the client as I explained here: http://legacy.averbouch.biz/fr/libnfc-and-nfc-utils-binaries-on-windows-10/#howtouse 3 - you should not have the red light still on, with libusbk properly installed 4 - are the tags/cards you are writing on: new, never used cards ? 5 - you say "got errors with the new version"--> which version before did you try with no error ?

Using your link, I don't get the same steps as in the doc. Could it be another executable?

Changed the usb port (again), and it's now green. It used to be green before...This is from device manager:

Now, factory format makes the application crash...

I've just tried the new driver: the red led should stay off after unpluging and repluging the ACR-122U below is what I did to install the new libusbk 3.1.0.0 (full procedure)

this next step is optional (answer YES if this window appears) import step : plug your ACR122U to display it in the list below: then, unplug your acr-122U and re-plug it

@Tiwas did you try to reinstall libusbk as mentioned above ?

@xavave Yes, only minimal effect. The application no longer installs the driver on every restart, which I guess is a step in the right direction. I seem to have damaged three RFID cards before I got to write to one, but the reader to my building doesn't recognize it. I'm going to run the applications manually to see if there's any difference, but there shouldn't be.

@Tiwas - you say "got errors with the new version"--> which version before did you try with no error ?

The last one I had was a preview you sent me. I didn't have any issues before yesterday, when I downloaded the latest version after the program prompted me to. I could, of course, be extremely unlucky with the last cards in my batch, though.

@Tiwas you can still download and install a previous version if you want to test: https://github.com/xavave/Mifare-Windows-Tool/releases

I think I found the issue, which is probably the executables you're running (the nfc executables).

This is the command I issued on my windows computer:

I booted my ubuntu laptop with a PN533 NFC stick, and issued the same command - and it succeeded. I can now write to these cards again.

Good news. You wanted to erase the card, right? So maybe I should try to recompile nfc-mfcclassic on windows

As far as I understand, erasing doesn't work on non-"magic" cards, only on fobs that allow changing UID. I suspect it might be the way it was formatted left them in a non-functional state, but the recent nfc build I had on ubuntu managed to write to them.

I see two potential problems here:

1. If normal cards cannot be formatted (only overwritten with a blank copy), then there should be an option to just write a blank copy with FFFFFFFF as both A and B key. That would probably solve that issue. If electing to not use the blank image and insisting on actually formatting them, a warning should be given (but please double check if my understanding is correct).
2. Rebuilding the binaries (please make sure to include the hardnested fork) might make it possible to rewrite cards that have been left inoperable after misuse.

Thanks for helping out with the wrapper issue, and for actively listening to feedback :)

You are welcome :) I already put a "blank card" file in the software that you can write on a card to simulate erase : https://github.com/xavave/Mifare-Windows-Tool/tree/master/MifareWindowsTool/dumps

have same issued here, but wasn't able to make one work... Keep saying

NFC reader: ACS / ACR122U PICC Interface opened Found MIFARE Classic card: ISO/IEC 14443A (106 kbps) target: ATQA (SENS_RES): 00 04
UID (NFCID1): bc 83 de cd
SAK (SEL_RES): 08
RATS support: no Guessing size: seems to be a 1024-byte card Sent bits: 50 00 57 cd
Sent bits: 40 (7 bits) Warning: Unlock command [1/2]: failed / not acknowledged. Writing 64 blocks |xxxfailed to write trailer block 3 x! Error: tag was removed

when using chinese magic unlocked/gen1 (W)

when using not 0 writable (w)... write 63 on 63 blocks.

Can you help.

I'm already at my 10th cards no longer workable. When trying to Factory Format the card. Application on windows 10 keep crashing. Thanks

this is when using 0 writable... sorry.

NFC reader: ACS / ACR122U PICC Interface opened Found MIFARE Classic card: ISO/IEC 14443A (106 kbps) target: ATQA (SENS_RES): 00 04
UID (NFCID1): bc 83 de cd
SAK (SEL_RES): 08
RATS support: no Guessing size: seems to be a 1024-byte card Writing 64 blocks |xxfailed to write trailer block 3 xxxxfailed to write trailer block 7 xxxxfailed to write trailer block 11 xxxxfailed to write trailer block 15 xxxxfailed to write trailer block 19 xxxxfailed to write trailer block 23 xxxxfailed to write trailer block 27 xxxxfailed to write trailer block 31 xxxxfailed to write trailer block 35 xxxxfailed to write trailer block 39 xxxxfailed to write trailer block 43 xxxxfailed to write trailer block 47 xxxxfailed to write trailer block 51 xxxxfailed to write trailer block 55 xxxxfailed to write trailer block 59 xxxxfailed to write trailer block 63 x| nfc_initiator_transceive_bytes: Mifare Authentication Failed Done, 0 of 64 blocks written. nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed nfc_initiator_transceive_bytes: Mifare Authentication Failed

hi @billw815 you tried with 10 cards , but I always see the same uid in your paste : UID (NFCID1): bc 83 de cd which steps did you proceed to write these cards ?

@billw815 : Are you sure these are in fact UID unlocked? As far as I've heard only fobs can be unlocked, while cards for some reason cannot. Keep in mind, this is only something I read while looking for a solution to the problem I had.

Also, are you using the latest version of the software?

@xavave Did you recompile the binaries for the latest release? If so, maybe he should try it from the command line?

@Tiwas i did not recompile executables for the latest version. Just some changes on my wrapper. But definitely it could be a good solution to test directly from command line