doc: 15693 V3 finalize moves user data instead of erasing it

Corrects the claim that every block reads back as 00000000 after finalize.
On the tag tested, block 0x38 held 11223344 before finalize and block 0x20
held it afterwards, a shift of 0x18, while blocks 0x10/0x11 and 0x14/0x15
were cleared.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
歐歪andClaude Opus 5 committed 2026-09-22 22:51:14 +08:00
1 parent 12b0143f46
commit 305b259fbe
1 file changed
+4 -2
+4 -2
View File
@@ -2765,8 +2765,10 @@ hf 15 raw -acw -d 02211077665544
hf 15 raw -acw -d 022111332211E0
```
Finalize locks the UID for good and can't be undone. It also erases the whole tag
memory, every block reads back as `00000000` afterwards:
Finalize locks the UID for good and can't be undone. It clears the configuration
blocks and changes the block numbering: on the tag tested, data written to block
`0x38` before finalize read back at block `0x20` afterwards, a shift of `0x18`.
User data is moved, not erased. Note down what is where before finalizing:
```
hf 15 raw -acw -d 022114A52B442C