Mifare classic tool скачать для windows

• v1.6.8424.42463 fixes

1. converting dump into flipper dump was crashing for 4K dumps
2. nfc-mfsetuid.exe was wrong when setting 7 bytes UID (beta testers welcome) —>
   nfc-tools/libnfc#582 and xavave/libnfc_with_extra_tools@5061094 (if someone here has knowledge in C/C++ and knows if a 7 bytes UID should be converted to a 4 bytes FNUID or not, please comment)
3. Set UID window : couldn’t set uid because check on UID before write was wrong
4. Set UID window: new: verify UID after setting the new UID on the tag
5. Dump Window: fix on tag size display
6. Main Window better exception catching

Full Changelog: 1.6.8424.20701…1.6.8424.42463

• fixed dll (libusb was not compiled in release mode before) in nfctools_pcsc folder

• small fix on exception catching in UI

• you can now use libnfc.conf in nfctools_pcsc folder to customize libnfc settings

• if your windows antivirus complains, you can add «C:Program Files (x86)AVXTECMWTnfctools_pcsc» folder to your anitivirus exclusion list

• if your antivirus blocks a mandatory executable or dll, you could get a 0x0000007b error:

** associated libnfc version: xavave/libnfc_with_extra_tools@e757f7c

** ACR122 removed from pcsc_driver accepted devices because it’s already in its own driver acr122_pcsc

** new branch created for this source code: pcsc_libnfc
** On next versions, I will try to implement PCSC Sharp

Full Changelog: 1.6.8422.36014…1.6.8424.20701

** 0abcbce

• nugets updated: cliwrap + wixsharp
• added new option to select which start and end block to write

• possibility to change default Access control bits (warning: not fully tested)

• libnfc compiled with PN532_UART driver (not tested)
  discussion 47

• you can use libnfc config (config file (.conf) needs to be in nfctools_pcsc directory)

• possiblity to write 7 bytes UID (warning: not fully tested yet, it could brick your tag if it’s not a 7 bytes UID tag)

• missing dll added ( discussion 63 and issue 64)

• you can also watch my changes on libnfc on my nfctools fork: https://github.com/xavave/libnfc_with_extra_tools

Full Changelog: 1.6.8421.33645…1.6.8422.36014

In this version: UI improvments, this version should be more stable, and tag cloning should work again

more dll included in pcsc folder MifareWindowsToolnfctools_pcsc: (lib nfc compiled in Install/Release mode (x64) so all mandatory dll should be there to run on other computers)

• auto detect if your target tag is block 0 writable («chinese magic tag»)
  if the tag on your reader is block 0 writable, this checkbox will be automaticaly checked:
  

• You don’t need to use libusbK anymore (and you need to uninstall driver filter that you had installed previously for your ACR122U)

• (By the way this will make you recover your ACR 122U green LED and bip sound)

Some fixes on utils and examples executables on my libnfc fork (included in this MWT version)
you can get more details on my libnfc changes here: xavave/libnfc_with_extra_tools@44145f4

drivers included/not included in this libnfc cross compilation:

you can change dump selection manually for source and target tag, by cliking on

Q

• changes on:
  usbbusc.c
  acr122_usb.c
  nfc.c
• libusb 1.0

mfoc-hardnested is compiled on VS2022 (Clang) with this libnfc version (and also libusb 1.0)

this is a PCSC driver version: you will need to uninstall LibUsbK driver if you want to use this one

• added: automatic libusbk uninstall attempt
• method to toggle ACR device status (to not have to unplug and replug it by hand after libusbk uninstalling)

Full Changelog: 1.6.8409.43095…1.6.8410.22153

this is a PCSC driver version: you will need to uninstall LibUsbK driver if you want to use this one

• all libnfc tools +mfoc-hardnested have been recompiled (and also in release mode to have a smaller size) from libnfc with visual studio 2022 on Windows 11 64 to be able to work with pcsc drivers
  (this because most of the libnfc tools where only trying to get first or default reader but were not looking for other available pcsc drivers configured in libnfc)

• libusbk driver and option button to uninstall it have been removed, as they are not needed in this version anymore

Full Changelog: 1.6.8408.42890…1.6.8409.43095

Prerelease version: PCSC

WARNING: With this new PCSC version (and ONLY for PCSC VERSION), you need to uninstall LIBUSBK driver wrapped on ACR122
If you dont uninstall libusbK driver with this version, MWT will not detect the tag reader on your PC

To do so, go to device manager (Windows Key +X ) —> Device Manager

then click on uninstall driver and tick checkbox «try to delete driver»

Then ,[Optional] reinstall ACR 122 PCSC driver (you can find it here: http://www.acs.com.hk/en/products/3/acr122u-usb-nfc-reader/)

Then , unplug, and replug your ACR 122 (and now the green light and beep sound of ACR should work again — It was not supported in libusbK)

As these drivers are PCSC, MWT may be more compatible with other tag readers supporting PCSC (not only ACR122U),
So please give us some feedbacks to let us know if it works with newer ACR 122 tag readers like ACR122U-A9 or even other brands)

• switched to pcsc driver and libnfc 1.8.0: all nfc tools recompiled with libnfc with ACR122 PCSC driver
• removed: mifare-classic-format.exe, replaced with nfc-mfsetuid.exe with option -f to format
• fixed: a small bug in change UID window
• added: when starting app, if a new stable version or new pre-release version exist, you can go on github page to download them (it was no implemented for pre release before)

• added: when starting app, if a new stable version or new pre-release version exist, you can go on github page to download them (it was no implemented for pre release before)
• fixed: a small bug in change UID window that made change uid button not enabled

added: mandatory files check
Without these files, MWT cannot work. if so, you will see a message box like this one:

In that case, maybe that your antivirus has blocked some of the mandatory files.
Please check in your antivirus and you can add folder: C:Program Files (x86)AVXTECMWTnfctools in your antivirus trusted folders list

• switched back to nfc-mfclassic.exe and nfc-mfsetuid.exe from v1.0.8225.472
• added: option to write full block 0 in tools/Options —> change UID (this should allow to set 7 bytes UID — but you need to write full block 0 — 16 bytes)

• fixed: write tag window was not opening after clicking on write tag and decrypting target tag
• fixed exception when copying text from MWT to clipboard