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;
[002] * 44 00 0F 00 (CFG0-CFG1, LOCK0-LOCK1)
[0E2] . 00 00 FF 00 (LOCK2-LOCK4, CHK)
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…
RawNFC command library - Projects - Dangerous Things Forum
Scroll down to the second post “Tag Fixes”