From 305b259fbe8e582ba0f55d6237d45ad580264e42 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E6=AD=90=E6=AD=AA?= Date: Tue, 22 Sep 2026 22:51:14 +0800 Subject: [PATCH] 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 --- doc/magic_cards_notes.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/magic_cards_notes.md b/doc/magic_cards_notes.md index 584d73dba..09a9ee771 100644 --- a/doc/magic_cards_notes.md +++ b/doc/magic_cards_notes.md @@ -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