I recently got an xSIID implanted in my hand. I was able to write to it, but now I cannot rewrite to it nor does my phone open the URL programmed in it when I scan it. I did attempt to password protect it, but when I try to remove the password, NFC Tool PRO says the NFC tag is not supported. Then how was I able to set one? Either way, I am unable to write or format the chip now but it does still light up.
What exactly did you use for this and what exact buttons did you boop? When it comes to the word “protect” … it could mean different things. We program the NFC chip to disable the lock bits because people were “protecting” their tag, not realizing it means lock it forever in an unrecoverable read-only state… so that’s not what happened… but there are other forms of “protection” including soft-lock based on TLVs you can write to the user memory pages, but that’s not what happened here. I can tell by your taginfo dump the lock bytes are ok;
We also set a default password and AUTH0 byte that protects only lower config pages (including password) so unless you authenticated using the default password first, you could not have changed the default password.
[0E3] . 00 00 00 E2 (RFU-RFU, AUTH0)
Just to be clear, you cannot remove the password from the chip because “the password” is whatever is stored in memory page E5… and since you can’t physically remove the memory page, you cannot remove the password. All you can do is set the password to a well known “factory default”, or you can make the password irrelevant by settings AUTH0 to point to a memory page lower than any existing page, like FF.
What I do see however is a broken NDEF container, starting with a zeroed out page 4
[004] + 00 00 00 00 |…|
Try using TagWriter to “format” your tag. If this fails, you might need to use RawNFC to overwrite your user memory with a blank NDEF record…
Referring to the password, I saw a feature in NFC Tools to set a password that would be required each time you want to write to the NFC tag. I thought that was the issue, but the “TagWriter” app you linked to was able to write to this NFC tag with no password and no problem. So it may have just been the NFC Tools app does not like this type of tag? Not sure but I am able to write to it no problem with this other app.
However, when I write a new URL on to the tag and then use taginfo, it says no ndef data storage populated and the link still does not open on my phone as expected.
04-42-7D-32-94-51-80_08-Jul-25 14-37-39_taginfo_scan.txt (15.7 KB)
I am able to write to it. This is with the new URL written, but the link does not open and taginfo says no NDEF data storage populated, “sector 0, page 0x00 error invalid last NDEF message page address”
That’s from your tag info dump… user memory starts at page 04 and there appears to be a blank ndef record followed by another entirely different ndef record for the dangerousthings.com URL.
Let me know if you have RawNFC loaded and I’ll write a custom link here for it that will entirely clear your tag and set a single ndef record.