So the NTAG215 UID is 7 bytes, but the Amiibo UID is 8 bytes? How does that work - pad the end with 00?First decrypt Amiibo and go to offset 0x1D4 (8 bytes UID BCC0)
Last edited by fiveighteen,
So the NTAG215 UID is 7 bytes, but the Amiibo UID is 8 bytes? How does that work - pad the end with 00?First decrypt Amiibo and go to offset 0x1D4 (8 bytes UID BCC0)
The UID is the first seven bytes of the encrypted dump, so you can search it the decrypted dump and change it.Alright, so I'm equipped with everything I need to give this a shot today:
- blank NTAG215 tags
- Amiibo dump
- hex editor
- the key to encrypt it
- Android smartphone with AmiiWrite
1) I decrypted the Amiibo dump
2) I read the NTAG215 with Android app NFC TagInfo to get the 7-byte UID.
3) I opened the Amiibo dump in a hex editor...
Where is the location of the UID to change it?
Extra byte is BCC0 = 0x88 xor UID0 xor UID1 xor UID2NTAG 215 UID:
04 C3 7A 52 C2 3E 80
DUCK HUNT DUO UID:
04 FC 30 40 82 03 49 80
It concerns me that they both start with 04 and end with 80 but there's an extra byte in the middle of the Amiibo.
Should I be changing Duck Hunt Duo to:
04 C3 7A 52 C2 3E 80 80 ??
Oh, that's what you meant. I apologize for not understanding. Thanks so much for the info!Extra byte is BCC0 = 0x88 xor UID0 xor UID1 xor UID2
88 xor 04 xor C3 xor 7A = 35
04 C3 7A 35 52 C2 3E 80
For dump I use Amiiqo app in Android or PC with https://github.com/socram8888/ulread this last recommended because it works to write blank tagsDoes this work with every smartphone? I installed amiiWrite on my S3 mini (NFC version) but everytime I want to dump an amiibo it says "Woops! Please retry!"
http://www.aliexpress.com/item/100p...ll-NFC-Mobile-Phone-NFC-Card/32258165667.htmlIsn't it easier to buy these cards and put a sticker on it?
NFC Card
Well that depends upon if there's any tool for it. I'd personally just use AmiiWrite and a cheap android with NFC.And this should work as a writer? NFC Reader/Writer
The first 10 bytes of the tag are determined by the NFC type A spec.EDIT: I'm essentially asking if someone knows an easy way to calculate that extra byte.
3: BCC0 - CT ^ UID0 ^ UID1 ^ UID2 (CT is 0x88)
(example for the UID I was using)EDIT: I'm essentially asking if someone knows an easy way to calculate that extra byte.
You can use http://xor.pw/ and the same logic as my above post.My head hurts from this xD
If someone can make a way to calculate this either online or as a program, I swear I will <3 you forever
PHP (which is the worst langauge ever) actually supports xor, it is literally just "xor". It also supports hex litterals, so your code could look something like:How would you put that into something like PHP?