To make a custom card work, you must change Block 0 to match the exact UID of the figure backup. This is where most DIY attempts collapse.
Online storefronts sell hundreds of blank tags labeled "UID Changeable" or "Magic Mifare." Almost all of these are Gen1 "Magic" tags. Gen1 cards unlock Block 0 using specialized backdoor commands (such as unlocking with a 0x40/0x43 transmission). Desktop writers like the ACR122U handle these commands easily. Android phones do not. Android’s native NFC software stack (NfcA / libnfc) restricts low-level frame commands. Your phone will throw a "Block 0 write failed" error every time you try to modify a Gen1 tag.
You must source Gen2 CUID (Changeable UID) tags.
Gen2 silicon responds to regular Mifare write commands (`0xA0`) rather than backdoor commands. Because a Gen2 card treats Block 0 like any normal data sector, a stock Android NFC reader-writer can write the new UID directly through the operating system's standard permissions.
| Tag Standard | Phone Writable (Android) | Portal Compatibility | Average Cost Per Unit |
|---|---|---|---|
| NTAG215 (Amiibo Tag) | Yes (Native) | Zero (Rejected) | $0.20, $0.35 |
| Standard Mifare Classic 1K | Data only (Block 0 Locked) | Zero (UID Mismatch) | $0.30, $0.50 |
| Gen1 "Magic" UID Tag | No (Requires Desktop APDU) | Full (If written via PC) | $0.60, $1.10 |
| Gen2 CUID Tag | Yes (Direct Write) | 100% Working | $0.75, $1.40 |
Check the listing specifications carefully before ordering blanks. Search specifically for "CUID 13.56MHz Android Writable" in PVC card, key fob, or coin sticker formats. Standard "UID" labels indicate Gen1 chips that will stall your workflow.
