You do know a ntag216 is not interchangeable with a ntag215?
And you do know how many useable bytes are available in a ntag215?
So the answer should be obvious.
And you do know how many useable bytes are available in a ntag215?
So the answer should be obvious.
To be honest I do not know that information... Could you share so that I can file a claim with amazon and try to cancel my order then?
You MAY get a ntag215 BUT it will NOT have "888 useable bytes".To be honest I do not know that information... Could you share so that I can file a claim with amazon and try to cancel my order then?
http://www.nxp.com/products/identif...144-504-888-bytes-user-memory:NTAG213_215_216
EEPROM
- 180, 540 or 924 bytes organized in 45, 135 or 231 pages with 4 bytes per page
- 144, 504 or 888 bytes freely available user Read/Write area (36, 126 or 222 pages)
- 4 bytes initialized capability container with one time programmable access bits
- Field programmable read-only locking function per page for the first 16 pages
- Field programmable read-only locking function above the first 16 pages per double page for NTAG213 or per 16 pages for NTAG215 and NTAG216
- Configurable password protection with optional limit of unsuccessful attempts
- Anti-tearing support for capability container (CC) and lock bits
- ECC supported originality check
- Data retention time of 10 years
- Write endurance 100,000 cycles
Last edited by Bug_Checker_,
Will it work for these amiibos thing tho? I dont know the size of the amiibo data
I am not this company so I do not know if they will send you a ntag215 or a ntag216.
If they send you a ntag215 it should work(but you will not have "888 useable bytes").
If they honor the claim of "888 useable bytes" then they must send you a ntag216(which will not (currently)work with amiibos).
Thank you a lot for the information, I have contacted the seller regarding this query. I will update back when possible in case anyone else wants to get these. Thank you again for the info.
- Joined
- Jul 7, 2010
- Messages
- 3,882
- Trophies
- 2
- Location
- /dev/random
- Website
- www.gudenau.net
- XP
- 5,542
- Country
Don't see why not, I was thinking of trying that myself.
...that is brilliant . that would be perfect omg. no need for me to ask to borrow a phone w/ nfc jeje
@gudenaurock Like I said, we'll have to use either NTAG.rpl or NFC.rpl. NTAG doesn't seem to have as low level access as NFC has, so I think I'll go for NFC if I can get that to initialize by just using IDA to find out how it works.
Excuse me for my noob question: can't Amiiqo write onto the NTAG215? Isn't its device a NFC tag?
The blank tags need to have a special sector written to the first bit so that it actually identifies as an Amiibo, which is what people are having an issue with right now
I updated the layout on the Wikitemp Amiibo page to document the entire layout. I'll add descriptions for each byte when I have some time. There is really only two things I haven't figured out. The first is what the data on page 23 is used for. This is the page immediately after the character data pages, and as far as I can tell it isn't really used for anything currently. This means that if we are doing something wrong on this page (which is locked) it is possible that this could be used to detect a fake. If people could post UIDs along with pages 21 through 23, that would be great. The second thing is exactly how the 0x20 byte block at page 24 is generated. You can use whatever values you want here and the tag seems to work fine, so my assumption is that it is random (which makes sense as it is essentially used as salt for the DRBG used to generate per amiibo keys). However, if it is a hash of something, this could again be used to detect a fake. In fact, generating a valid (but corrupt) Amiibo dump is super easy, you can just set every byte to random, and then write the 2 pages with the character data.
Those are actually the tags I used, and the ones I got were definitely NTAG215s (the description was of course wrong).
Not entirely true. The hardware is actually capable of emulating NFC Type 2 Tags, and CM 9.1 through 10 something actually supported this on devices with NXP NFC chipsets. The problem is that the hardware doesn't allow you to set an arbitrary UID; the first byte is locked to a specific value (0x08) in order to differentiate the emulator from an actual tag. You can actually work around this by manually overriding the handling of the anti-collision commands, but this will almost certainly mess up the timings, and I'm not certain that the CM implementation would even allow you to do this. Furthermore, this would only work on devices with a very specific very old version of CM and a specific NFC chipset. It's possible that somebody could create VERY custom firmware for exactly this purpose, but it would be an exceedingly high amount of effort.
Last edited by Supercool330,
If I own an amiibo can I "edit" it so the wii u will consider it something else ?
for exemple , I have a Link amiibo is there a program that can change it to be like a ganondorf amiibo ?
btw did anyone try it ?
http://www.ebay.com/itm/NFC-Smart-T...126595?hash=item54135d2e03:g:IC8AAOSwLa9UVy4u
will this do ?
for exemple , I have a Link amiibo is there a program that can change it to be like a ganondorf amiibo ?
btw did anyone try it ?
http://www.ebay.com/itm/NFC-Smart-T...126595?hash=item54135d2e03:g:IC8AAOSwLa9UVy4u
will this do ?
anybody used it ?
sounds extremely good and cheap
just ordered myself 10 NTAG215 tag stickers
http:// http://de.aliexpress.com/it...32315909847.html?spm=2114.47010308.4.2.4lzkcp
They are cheaper, aren't they? (100x = 35,50$ offer)
Last edited by oldsk00l,
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
-
-
@
BigOnYa:
We all knew once Panda joined chat, after the response OMG, she/they be back everyday, much love!+1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
