-
Notifications
You must be signed in to change notification settings - Fork 443
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nfc-mfclassic sucess but not wriring... #684
Comments
Hello, |
No, I haven't resolved this clue .. |
+1 |
I have the same problem but found a workaround that worked for me. I prepared a package of libnfc-1.7.1 with the driver patch for acr122 ( I only took the acr122_usb.c file from libnfc-1.8.0 version 1.8.0 and replaced it for the libnfc-1.7.1/libnfc/drivers/acr122_usb.c file) If you want you can download it from the link below or from the attachment #Now we need to unzip the file #Just to make sure that you have all the libraries to be able to compile the package #Now we compile & build it #If you don't receive any error try to open a terminal and do: You need to see: "nfc-list uses libnfc 1.7.1" (With the version that works) #If is all correct now you are able to write the file with nfc-mfclassic I hope that this guide can help you |
Thank you very much for your solution, it works very well for me. |
Unfortunately, my problem of trying to write to a card is not resolved with switching to 1.7.1. Even though I can easily read from cards, I cannot write to it:
When trying to write it with When trying with a highter LOG-Level and Or when running Any ideas what could be wrong? |
I read "unlock failure!" and this is because you use nfc-mfclassic with W Uppercase without using a Chiese Magic Card with Sector 0 (uid) editable |
That's true, thank you Cioci89 – but look at the version where I use «w» (and I think I should be using w, because I'm simply trying to overwrite a card using a dump that I received from that very card). In the log text after issuing What could that be related to? |
Good morning |
I have tried using two different files – it makes no difference for the writing-process. |
Hello, i have an issue with nfc-mfclassic. I try to copy a card to an other, the result of nfc-mfclassic is success, the data inside the nfc key is exactly the same as before the run of the command.
nfc-mfclassic output :
I tried with an other nfc key, it's the same...
Some of you has any idea ?
The text was updated successfully, but these errors were encountered: