As you can see i tried changing uid (which failed because it is no magic tag) and also wiping it. Wiping it does repeatedly not work, also in the 2nd slower mode.
Is this normal? are there any locks on it?
ISO15693 (NFC type 15) is a very broad standard, not every card can be rewritten or wiped, it appears this one may not be compatible with that command at this time
to explain: im creating a wearable that contains a tag used to grant its authenticity. Now i received this sample from my supplier but it the tag is not fitting at all. I want to change it (not possible because its not a magic tag) or disable it and replace with my own magic tag to try out different idâs.
I still donât understand so Iâm just going to throw this out there. Take a lighter and burn the chip. Those thing burn well. Fire kills everything.
I would do that but like i said i can not physically reach the tag right now, it is embedded in the wearable. Burning it would mean burning the whole wearable, i can not do that
Maybe Iâve missed something, but what makes you say it isnât being wiped? I donât see any mention of the memory contents (other than the UID which is read-only) remaining after running the wipe command. You seem to have decided that âwipeâ actually means âpermanently disableâ rather than âerase the user memoryâ. I understand it would be frustrating when the device doesnât work the way you expected, but it doesnât really seem like a shortcoming of the PM3.
Have you read the datasheet for the ICS2602? Specifically section 9.5.3.8 where it tells you how to use the DESTROY command? I donât think the pm3 has that as a built-in function, but you should be able to send it using the âhf 15 rawâ command.