Try uninstalling TagMo and instead install the version found in post #45 of the TagMo thread. Here's a direct link to the post: https://gbatemp.net/threads/release...ng-editing-amiibos.431670/page-3#post-6530204
This worked for me and a bunch of other people with the exact same issue.
This one linked in another post worked for me.The link on that page no longer works it looks like the file was removed from dropbox. Does any one have a mirror or any other link to get that version of tagmo.
Falseso i have a bunch of ntag216 lying around and i heard a rumor of using these instead of the 215 is this true
Thanks for letting me know.The link on that page no longer works it looks like the file was removed from dropbox. Does any one have a mirror or any other link to get that version of tagmo.
They all worked for me... they were 572 bytes to be exact. Even the guardian worked
Do you have to use a certain version or alter the files in anyway to get the BOW ones to work?
I used a 570 byte amiibo (all the botw ones) with tagmo 2.3.2. It worked fine.
one comment above the one you quoted:
As I stated in the post you quoted I did use the 572 byte bin files even though I said 570 there.
Then where are the other 32 bytes coming from, if not the Amiibo as explained below?Amiibos are 540 Bytes. Always. Cause the Tags are exactly 540 Bytes too.
I can explain the 572B thing. Without getting into to much detail, basically, someone out there figured out that amiibo NTAGs have some extra visible data on them at the end of the tag that might be of use eventually, so Amiibitz now dumps that, and handles that somewhat properly.-snip-
Yes, that's why I was trying to bring them to your attention. I haven't checked Amiibitz, but they should be the vendor ECC. (from read_sig) If that's the case, those bytes are there and readable.I dont know where the other Bytes are supposed to come from
Correct. The Amiibo's NTAG215 (if it verifies as such) would have had only 540 bytes of "space". That doesn't mean that they only have 540 bytes of important information.Cause amiibos itself only have 540 Bytes space.
The signature bytes aren't of use to someone writing an NTAG215 because that area isn't writable. That doesn't make them not exist. They would be useful (critical) for someone emulating a tag if Nintendo decided to start verifying the signature. My point is that those bytes don't make the dump invalid. If your writing program doesn't ignore them, just chop them off with a hex editor.but it wouldnt be of any use
A Datel powertag isn't an NTAG215, but it is recognizable as an Amiibo. (However, it doesn't pass the sig verification as an NTAG215, so Nintendo could put those out of commission.) And, of course, the N2 Elite isn't a tag at all.because only written ntag215's are recognized as amiibos. And they have only 540 Bytes.
Yes, that's why I was trying to bring them to your attention. I haven't checked Amiibitz, but they should be the vendor ECC. (from read_sig) If that's the case, those bytes are there and readable.Correct. The Amiibo's NTAG215 (if it verifies as such) would have had only 540 bytes of "space". That doesn't mean that they only have 540 bytes of important information.The signature bytes aren't of use to someone writing an NTAG215 because that area isn't writable. That doesn't make them not exist. They would be useful (critical) for someone emulating a tag if Nintendo decided to start verifying the signature. My point is that those bytes don't make the dump invalid. If your writing program doesn't ignore them, just chop them off with a hex editor.A Datel powertag isn't an NTAG215, but it is recognizable as an Amiibo. (However, it doesn't pass the sig verification as an NTAG215, so Nintendo could put those out of commission.) And, of course, the N2 Elite isn't a tag at all.