NXP TagWriter: Unable to write NTAG213 tags -url with interaction counter and uid mirror

[peku]

Hi,

I am experiencing problems with writing NTAG213 tags. I am trying to write a URL with the interaction counter and UID mirroring active, but the app always says "Store failed." When I turn off those options, the URL is stored successfully.

I think the problem started with the last update of NXP TagWriter or maybe with an Android update. I'm not sure, but it was working for many years before December 24/January 25.

My colleagues managed to downgrade the app back to version 5.0.0, and it works on their older Android phones. However, even version 5.0.0 does not work on my Galaxy S25 with Android 15.

Can you help me troubleshoot the issue? Thanks.

[Daniel_Gutierrez]

Hello @peku, Good Day!

Thank you very much for your interest in our products.

Regarding following the procedure described in section 4 of the TagWriter User Manual to enable mirroring features on an NTAG213, I was able to successfully perform this operation using a Galaxy S25 phone and version 6.1.0 of the TagWriter app, please ensure the procedure referenced above is being followed.

However, if you still cannot enable the mirroring features and write the NDEF to the tag, I would like to ask if you could please perform a "FULL SCAN" of the tag using the NFC TagInfo App by NXP, and please share a screenshot of the information read, including the bytes read from the memory which will appear at the bottom of the page under the "FULL SCAN" tab.

My best regards,
Daniel.

[peku]

Hi. I am sending fullscan report. Thank you for your help.

<scan>
<version>6.0.0</version>
<date>2025-05-12 09:21:47</date>
<title>Unknown Shanghai Fudan Microelectronics Co. Ltd. NfcA tag</title>
<uid nxp="false">1D:74:BD:E9:09:10:80</uid>
<hasndef>false</hasndef>
<section>
<subsection title="IC Manufacturer">
<block type="text">
<content>Shanghai Fudan Microelectronics Co. Ltd.</content>
</block>
</subsection>
<subsection title="IC Type">
<block type="text">
<content>Unknown IC</content>
</block>
</subsection>
</section>
<section>
<subsection title="No NDEF Message present">
<block type="text">
<content/>
</block>
</subsection>
</section>
<section>
<subsection title="TagInfo Version">
<block type="text">
<content>Version :6.0.0</content>
</block>
</subsection>
<subsection title="Device Info">
<block type="text">
<content>Device Model :samsung ( SM-S938B ) Android OS Version :15</content>
</block>
</subsection>
</section>
<section>
<subsection title="Technologies Supported">
<block type="text">
<content>ISO/IEC 14443-3 (Type A) compatible NOT ISO/IEC 14443-2 (Type A) compatible</content>
</block>
</subsection>
<subsection title="Android Technology Information">
<block type="text">
<content>
Tag description: ‣ TAG: Tech [android.nfc.tech.NfcA, android.nfc.tech.Ndef] ‣ Maximum transceive length: 253 bytes ‣ Default maximum transceive time-out: 618 ms
<hexoutput>MIFARE Classic support present in Android</hexoutput>
</content>
</block>
</subsection>
<subsection title="Detailed Protocol Information">
<block type="text">
<content>ID: 1D:74:BD:E9:09:10:80 ATQA: 0x4400 SAK: 0x00</content>
</block>
</subsection>
<subsection title="Memory Content">
<block>
<address>0</address>
<data>1D 74 BD 5C</data>
</block>
<block>
<address>1</address>
<data>E9 09 10 80</data>
</block>
<block>
<address>2</address>
<data>70 C0 00 00</data>
</block>
<block>
<address>3</address>
<data>E1 10 12 00</data>
</block>
<block>
<address>4</address>
<data>01 03 A0 0C</data>
</block>
<block>
<address>5</address>
<data>34 03 00 FE</data>
</block>
<block>
<address>6</address>
<data>00 00 00 00</data>
</block>
<block>
<address>7</address>
<data>00 00 00 00</data>
</block>
<block>
<address>8</address>
<data>00 00 00 00</data>
</block>
<block>
<address>9</address>
<data>00 00 00 00</data>
</block>
<block>
<address>10</address>
<data>00 00 00 00</data>
</block>
<block>
<address>11</address>
<data>00 00 00 00</data>
</block>
<block>
<address>12</address>
<data>00 00 00 00</data>
</block>
<block>
<address>13</address>
<data>00 00 00 00</data>
</block>
<block>
<address>14</address>
<data>00 00 00 00</data>
</block>
<block>
<address>15</address>
<data>00 00 00 00</data>
</block>
<block>
<address>16</address>
<data>00 00 00 00</data>
</block>
<block>
<address>17</address>
<data>00 00 00 00</data>
</block>
<block>
<address>18</address>
<data>00 00 00 00</data>
</block>
<block>
<address>19</address>
<data>00 00 00 00</data>
</block>
<block>
<address>20</address>
<data>00 00 00 00</data>
</block>
<block>
<address>21</address>
<data>00 00 00 00</data>
</block>
<block>
<address>22</address>
<data>00 00 00 00</data>
</block>
<block>
<address>23</address>
<data>00 00 00 00</data>
</block>
<block>
<address>24</address>
<data>00 00 00 00</data>
</block>
<block>
<address>25</address>
<data>00 00 00 00</data>
</block>
<block>
<address>26</address>
<data>00 00 00 00</data>
</block>
<block>
<address>27</address>
<data>00 00 00 00</data>
</block>
<block>
<address>28</address>
<data>00 00 00 00</data>
</block>
<block>
<address>29</address>
<data>00 00 00 00</data>
</block>
<block>
<address>30</address>
<data>00 00 00 00</data>
</block>
<block>
<address>31</address>
<data>00 00 00 00</data>
</block>
<block>
<address>32</address>
<data>00 00 00 00</data>
</block>
<block>
<address>33</address>
<data>00 00 00 00</data>
</block>
<block>
<address>34</address>
<data>00 00 00 00</data>
</block>
<block>
<address>35</address>
<data>00 00 00 00</data>
</block>
<block>
<address>36</address>
<data>00 00 00 00</data>
</block>
<block>
<address>37</address>
<data>00 00 00 00</data>
</block>
<block>
<address>38</address>
<data>00 00 00 00</data>
</block>
<block>
<address>39</address>
<data>00 00 00 00</data>
</block>
<block>
<address>40</address>
<data>00 00 00 BD</data>
</block>
<block>
<address>41</address>
<data>00 00 00 FF</data>
</block>
<block>
<address>42</address>
<data>00 00 00 00</data>
</block>
<block>
<address>43</address>
<data>00 00 00 00</data>
</block>
</subsection>
</section>
</scan>

[Daniel_Gutierrez]

Hello @peku, Good Day!

As I can see on the log you shared, the scanned tag is not an NXP device. Please consider that our support scope is limited to products by NXP.

For further help regarding this topic, please contact the manufacturer of the tag.

My best regards,
Daniel.