I have very similar designs (based on the same box art template perhaps?)
(Note: Mine are credit card-sized, which is different than the AC cards)
View attachment 41215 View attachment 41216 View attachment 41217
I tried to look into this issue. However I am new to making android apk's, the apk always generate errors ('Unfortunately app has stopped') when I trigger the NFC functions in my custom tagmo app (signed with self-generated key). The error exists even with compling the original code. I do not know what's wrong with my android studio :\
I hypothesized earlier on the NTAG215 thread for replacing with NTAG216:
Took a brief look at the datasheet. The difference between the 2 chips are the location of 'dynamic lock bytes' and 'configuration pages' as well as the value in CC.
[Also, the response in GET_VERSION will be different too] So in order to use NTAG216 in place of NTAG215, the data for 'dynamic lock bytes' and 'configuration pages' need to be written to the correct location. CC bits could be set to FF (refer to Amiibo article on 3dbrew) so the difference in default value does not matter.
[Those data may need to be written into both NTAG215 and '216 locations. However, for the PASS and PACK they are write-only, so the NTAG215 location needs to be 0's]
The problem is with GET_VERSION which is fixed. Byte 6 (storage size) is different between NTAG215 and '216. If ninty really checks the response, I do not think there is a way to get around it. However I could not get my working android compiler to play with it