NFC microchip Read only unlock

[ThexTallxDude]

@my18666

If checked, can I unlock?

No, that’s why the warning is telling you you can’t unlock the tag if that is checked. You may be able to recover it with a Proxmark, but I can’t confirm that, you’d have to wait for someone else to chime in.

How did you get your tag readout that you posted here?
The readout you posted has an error at the bottom, which may be contributing to the issue. There’s Dynamic lock bytes stored in the last page or so of the chip that I’m not seeing in your dump.

Here’s a quote from one of Amal’s posts explaining this:

@amal

The NTAG216 chip has two sets of lock bytes. The first set are called the “static lock bytes” and are the last two bytes of page 02. The second set are called “dynamic lock bytes” and are the last three bytes of page E2. Each bit all of these lock bytes represent user programmable memory pages. If the lock bit is 0 then the page is writable, if it is 1 then that page is forever locked. These bytes are very powerful and in the case of an implant, server no real purpose since there is no conceivable situation anyone could think of where lock bytes would want to be used… except two places. The first is the CC - page 03 - which, if programmed correctly for use as an NFC Type 2 tag, should never be changed. So, we set a bit in the static lock bytes in page 02 to forever lock page 03 and secure the CC from ever being changed. The second thing that could benefit from being locked, are the lock bytes themselves. Fortunately there are bits within both the static and dynamic lock bytes that can lock the lock bytes themselves… effectively locking the lock bytes. So, after locking page 03 and securing the CC, the dynamic and static lock bytes are then locked, blocking any further user memory pages from being locked.