topic Re: DESFire EV3 Formatting Issue in NFC

DESFire EV3 Formatting Issue

Riowang-Akuvox — Wed, 13 Nov 2024 02:15:15 GMT

The issue we are encountering is as follows: When using a DESFire EV3 8K card, after sending the 0xFC format command to format the card, the card enters a "frozen" state and does not respond to any further commands. Even removing the card from the field, re-scanning it, or re-running the code does not resolve the problem. However, we found that when the card is read by a smartphone's NFC function, it recovers and can execute other commands normally. The problem reoccurs as soon as the card is formatted again.

Additionally, we tested several other DESFire cards. Three of the EV1 cards exhibited similar issues, while the three EV2 cards and two EV3 cards worked normally after formatting.

This situation suggests that after the card is formatted, it does not return to its normal operating state. However, when the card is read by a smartphone's NFC function, it seems to reactivate and return to normal operation. The strange thing is that only certain DESFire cards exhibit this behavior.

Re: DESFire EV3 Formatting Issue

KaiLi — Wed, 13 Nov 2024 08:17:07 GMT

Hello @Riowang-Akuvox

From your description, formatting failed. At PICC level, all applications and files are deleted by Format(0xFC) command,but before that, you must authenticate the card, and successed, and then you can format the application and files.

Re: DESFire EV3 Formatting Issue

Riowang-Akuvox — Wed, 13 Nov 2024 08:29:40 GMT

Yes, as you mentioned, I’ve already authenticated the PICC before formatting, and based on the read results, the formatting has indeed been completed (all created applications are deleted). However, the issue I’m encountering now is that after formatting, the card cannot execute other commands. For example, commands like selecting an application, authentication, and getting the version all fail. But after reading the card with a phone’s NFC function, when I put the card back on the reader, it works normally.

This issue seems like the card isn’t restored to the correct state after formatting, while reading it with a phone’s NFC function somehow reactivates it to a normal state. What’s odd is that this issue only occurs with one EV3 card and a few EV1 cards I have, while other cards (EV1, EV2, or EV3) work fine with formatting, application creation, or file creation.

Re: DESFire EV3 Formatting Issue

KaiLi — Wed, 13 Nov 2024 12:24:31 GMT

Hello @Riowang-Akuvox

After formatting, you need to reset your reader and then re-active layer3/4 ,and then create the new application and file, please try.

Re: DESFire EV3 Formatting Issue

Riowang-Akuvox — Wed, 13 Nov 2024 15:15:09 GMT

Thank you for your response. As you mentioned, after formatting, I have reset the card reader and re-executed the anti-collision card selection process that complies with the 14443A standard. At this point, reading the 7-byte UID from the Desfire card works normally, but executing Desfire-related commands still fails. I think it’s worth noting that, among the Desfire cards I currently have, only some cards exhibit this issue while others work fine. If there were flaws in our formatting process or workflow, it would likely result in all cards malfunctioning rather than only some. This problem might be due to unknown differences between various Desfire cards. When this issue occurs with one card in my possession, it can also be reproduced with other cards from the same batch. I hope you can provide more information for reference, and I look forward to your reply.

Re: DESFire EV3 Formatting Issue

KaiLi — Fri, 15 Nov 2024 03:21:29 GMT

Hello @Riowang-Akuvox

Your situation is strange, I have not reproduced your situation, your card is a clone card?

Re: DESFire EV3 Formatting Issue

Riowang-Akuvox — Fri, 15 Nov 2024 03:28:43 GMT

Actually, the Desfire cards I have are physical cards that we purchased from a card manufacturing supplier.

Re: DESFire EV3 Formatting Issue

KaiLi — Sun, 17 Nov 2024 13:32:39 GMT

Hello @Riowang-Akuvox

As the final way, it is recommended to try the NXP Reader CLRD730 (PEGODA Contactless Smart Card Reader | NXP Semiconductors).

Re: DESFire EV3 Formatting Issue

NeatCar — Tue, 07 Jan 2025 19:01:13 GMT

I'm having the same problem with EV3 cards after command 0xFC. I'm using a custom NFC reader with custom firmware. It works perfectly for all EV2/EV3 commands so far, except for this one.

Steps to reproduce:

Bring card into RF field.
Card is discovered.
Send GetVersion command (0x60). Response is good.
Select application 0x000000.
Authenticate with PICCMasterKey. Success.
Send command 0xFC. NO RESPONSE.
Remove card from RF field.
Bring card back into the RF field.
Card is discovered.
Send GetVersion command (0x60). NO RESPONSE.
Repeating steps 7-10 always has the same result.
Reading the card with an Android NFC phone "fixes" the card. Now it responds to GetVersion.