Writing tag data to Amiibolink results in a corrupted tag

[LRFLEW]

I reported HiddenRamblings/TagMo#730, tested this project as well (as that implementation seemed to have been based on this one), and saw this exhibits the same behavior. This project doesn't seem terribly active, but I figured I'd report the issue here as well.

Connecting to my Amiibolink and using "upload tag data" results in a corrupted tag on the Amiibolink. It shows up as the correct type of amiibo, but trying to use it with the switch where it tries to read the registration or game data results in a corruption error being shown. (Using the Switch's option to reset amiibo does get it working, though.) Reading it with TagMo shows that the data sent when scanned does not match the tag data sent.

There's also the possibility that it's just my device, but it seems to be behaving reliably other than the occasional random read errors. There did seem to be issue with the other actions (such as the "write blank tag" putting it into a seemingly unusable state), but that's a less pressing issue, and I suspect it's all the same issue.

[Bibasyoy]

I reported HiddenRamblings/TagMo#730, tested this project as well (as that implementation seemed to have been based on this one), and saw this exhibits the same behavior. This project doesn't seem terribly active, but I figured I'd report the issue here as well.

Connecting to my Amiibolink and using "upload tag data" results in a corrupted tag on the Amiibolink. It shows up as the correct type of amiibo, but trying to use it with the switch where it tries to read the registration or game data results in a corruption error being shown. (Using the Switch's option to reset amiibo does get it working, though.) Reading it with TagMo shows that the data sent when scanned does not match the tag data sent.

There's also the possibility that it's just my device, but it seems to be behaving reliably other than the occasional random read errors. There did seem to be issue with the other actions (such as the "write blank tag" putting it into a seemingly unusable state), but that's a less pressing issue, and I suspect it's all the same issue.

I have same issue with Amiloop. Clearing the data and cache of browser sometimes helps. Sometimes it works sometimes doesn't. Have you found the source of issue and solution?

[DanTheMan827]

@LRFLEW in regards to the different modes, the app for the amiiloop has the option to change modes between static, change the ID on button, and change in scan. Perhaps that’s messing it up?

It could also be a difference in the firmware version flashed.

Writing a blank tag uses the same code as writing a dump, it just writes a blank ntag215 dump.

I can’t recall where, but there are firmware updates for these devices. Maybe one of those would help?