Confirmed Working: How to Write Skylanders NFC Cards on Android Step by Step

Secondary market prices for toys-to-life figures have climbed to absurd levels. Out-of-print figures like Ro-Bow and Wildstorm from Skylanders Imaginators, along with high-tier Trap Team crystals, routinely fetch between $250 and $400 on secondhand marketplaces. While emulator communities have found virtual bypasses, highlighted in recent community discussions like the YouTube (Bacon and Legs) Report, players running original console discs face physical hardware barriers. If you do not place a compatible chip on the Portal of Power, the game does not load the character.

Over the past two years, hardware enthusiasts within the retro console community verified a reliable workaround. You do not need an external Proxmark3 or an expensive ACR122U desktop writer. An ordinary Android smartphone equipped with an integrated NFC controller can write functional, rewritable Skylanders cards in seconds. The catch lies entirely in the underlying silicon: buying the wrong tag standard leaves you with an unusable plastic rectangle.

📌 Key Takeaways:

• The Hardware Hurdle: Skylanders portals reject standard NTAG215 cards (Amiibo tags); they require Mifare Classic 1K chips with an accessible, rewritable manufacturer sector.
• The Crucial Tag Type: Android smartphones cannot send backdoor commands, meaning you must buy Gen2 CUID blank tags rather than standard "Gen1 magic" cards to overwrite Block 0.
• The Software Stack: The free Android app Mifare Classic Tool (MCT), paired with proper key dumps and character bin dumps, writes fully interactive figures in under 30 seconds.

Why Amiibo Cards Fail on the Portal of Power

Most players entering the RFID hobby start with Nintendo Amiibos. Those figures use standard NTAG215 chips running on the ISO/IEC 14443 Type A protocol. You can buy 100 blank NTAG215 stickers for twenty dollars and write them with nearly any modern phone using simple apps like TagMo.

Skylanders operates on an entirely different architecture. Toys for Bob built their franchise on the Mifare Classic 1K standard. A Mifare Classic chip splits its 1,024 bytes of memory into 16 distinct sectors, each protected by two cryptographic keys: Key A and Key B.

When you place a figure onto the portal, the peripheral reads Sector 0, Block 0. This manufacturer block holds the chip's hardcoded 4-byte Unique Identifier (UID). The portal immediately executes a proprietary encryption algorithm that runs the UID through an internal mathematical cipher to calculate the sector keys. If the card cannot authenticate Sector 1 through Sector 15 using those derived keys, the portal rejects it.

Standard factory-produced Mifare Classic tags lock Block 0 permanently during manufacturing. If you cannot align the physical UID on the tag with the UID encoded inside the character data dump, the portal's validation routine fails instantly.

The Silicon Trap: Understanding Gen1 Magic vs. Gen2 CUID Tags

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.

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.

Phone Compatibility: The Hardware Check

Not every Android device can read or write Mifare Classic architecture. NXP Semiconductors developed the Mifare protocol, and phones using official NXP NFC transceivers handle these tags without friction.

Many modern smartphones use Broadcom or alternate NFC controllers. While these chips read basic NFC Forum tags, some cannot authenticate the proprietary encryption routines in Mifare Classic cards.

• Samsung Galaxy devices (S10 through S25 series), OnePlus devices, and older Xiaomi hardware consistently read and write Mifare Classic sectors.
• Recent Google Pixel generations (Pixel 6 through Pixel 9) often drop Mifare Classic driver support at the kernel level, returning an "Unsupported Tag Type" or "Tag Lost" error during operations.

To check your phone, install the free app NFC Tools or Mifare Classic Tool (MCT) from GitHub or Google Play. Tap any standard hotel keycard or transit pass against the back of your phone. If the app displays the tag type as `MifareClassic` with 16 sectors visible, your phone's hardware transceiver is ready.

Writing Skylanders Bin Dumps via Mifare Classic Tool

Writing a working card requires three core elements: your verified Android device, blank Gen2 CUID cards, and the backup data files.

Backup files circulate among preservationists as 1,024-byte `.bin` files containing the raw hex image of the original figure, alongside key files containing the calculated sector keys.

Step 1: Install Mifare Classic Tool (MCT)

Download the latest open-source build of Mifare Classic Tool from F-Droid or GitHub.

Step 2: Prepare the Key Files

MCT must authenticate all 16 sectors before it can overwrite them.

1. Open MCT and enter "Tools" -> "Edit/Add Key File".
2. Create a new key list or append to "extended-std.keys".
3. Skylanders uses derived keys for each sector. Add the global master keys

and known static sector keys used across character dumps.

Save the key file.

Step 3: Convert Character Dumps

MCT reads human-readable `.mct` or `.dump` files containing ASCII hex text,

whereas raw backups are usually binary `.bin` files.

1. Use an online or mobile file converter (like a hex editor or Skylanders MCT converter)

to translate your 1KB `.bin` character file into an MCT-readable text format.

1. Place the resulting file into the internal storage directory:

`mifareclassictool/dump-files/`.

Step 4: Execute the Block 0 Write

1. In MCT, tap "Write Tag".
2. Select "Write Dump (Clone)".
3. Check the box labeled "Show Options" and ensure "Write Block 0" is enabled.
4. Select the dump file of the character you want to flash.
5. Select the key file you configured in Step 2.
6. Hold your Gen2 CUID card flat against the back of your phone near the NFC antenna.
7. Tap "Start Mapping and Write Dump".

Keep the card steady for the entire three-second process. MCT maps the sectors, authenticates blocks 0 through 63, and writes the manufacturer block alongside the encrypted gameplay data. Once the screen confirms 64 blocks written successfully, the card is ready for gameplay.

Portal Compatibility Across the Full Game Catalog

Field tests show that Gen2 CUID clones written through this method behave identically to original retail figures across all six main franchise releases:

• Spyro’s Adventure & Giants: Simple character reading and local level saving work without restriction.
• Swap Force figures physically split the top and bottom halves across two distinct chips. To recreate these on cards, write the top half to one CUID card and the bottom half to a second card. Placing both cards side-by-side on the portal registers the custom combination in the engine.
• Trap Team Elements & Villains: Writing villain traps to CUID cards provides instant access to rare Traptanium elements like Light and Dark traps, bypassing the high prices common on collector platforms. The portal reads them as authentic physical crystals.
• SuperChargers & Imaginators: Vehicles, Senseis, and Creation Crystals function cleanly. Once written, Creation Crystals behave like factory-fresh items; their element is locked to the specific bin file flashed onto the chip.

Upgrades, gold counts, and nickname edits write back to the CUID card during gameplay. When the portal pulses its read/write light during saving, it updates the card's sector data. You can rewrite a Gen2 CUID card with a completely different character file later by repeating the MCT flash sequence.

Frequently Asked Questions (FAQ)

Q1: Can I use an iPhone to make Skylanders cards?

No. While iOS supports reading standard NFC chips and writing basic NTAG URLs, Apple restricts third-party apps from sending raw write commands to Mifare Classic chips. You must use an Android device with an NXP-compatible transceiver or an external desktop programmer like the ACR122U connected to a PC.

Q2: Will my written cards get banned or corrupt game consoles?

No. Consoles interact strictly with the Portal of Power over a standard USB connection. The console receives game data from the portal rather than reading the raw RFID chip directly. The portal sees a valid UID and properly encrypted sectors, identifying the card as an authentic physical figure.

Q3: Why does Mifare Classic Tool display "Error: No blocks written"?

This error points to one of two issues: you bought Gen1 magic cards instead of Gen2 CUID tags, or your phone's NFC controller cannot write to Mifare chips. If MCT cannot unlock Sector 0 with standard write commands, the write routine aborts immediately.

Q4: Can I write multiple characters onto a single CUID card?

No. Each standard Mifare Classic 1K card holds only one 1,024-byte character image at a time. To switch figures, rewrite the card using your phone or use separate cards for each character in your collection.

Preserving Physical Game History

Commercial support for the toys-to-life genre ended years ago, stranding late-era characters behind artificial scarcity and brittle plastic tags. Silicon components inside original figures will inevitably face bit-rot and antenna fatigue as the decades advance.

Custom Gen2 CUID cards offer practical preservation. Sourcing the right tags and utilizing Android’s native NFC architecture lets you run the full breadth of the series on original hardware without spending hundreds of dollars on collector markets. By verifying the hardware type before buying blanks, you transform an ordinary phone into a capable archiving station.