-
-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for Datel PowerTags #30
Comments
If I knew what FFFF... represents then I could write it, same issue |
Update I changed the values of the FFFF... still wont work, in Botw it just makes a beep. |
Is there a good description, what this PowerTag is made for and how it works? I can't find a good one. |
I believe this tool has recently added some Powertag support which could lead to clues about its functionality. |
As far as I understood that article if you have the program called "power save" (and the nfc card reader) and a power tag you can create amiibos out of it. Could you try to do it the legitimate way and tell me if that worked? |
Why wouldn't the legitimate way work? I do not have the Powersave NFC base and proprietary software, so I cannot confirm. |
Ok,so we need to investigate in an other way. Please wipe you power tag using this app: https://play.google.com/store/apps/details?id=com.nxp.nfc.tagwriter Then try to write a Amiibo to the Power Tag with the newest version of TagMo. Then use: https://play.google.com/store/apps/details?id=com.nxp.taginfolite to see if the Powertag is identified as a NTag215 Please post your results. (Edit1: added links) |
So I still need you to do the steps mentioned about. After further invetigation on my own, i found out that where is no UID written to the PowerTag. Please send me your results afterwards. :) |
@daleriechert 01D5-01DB represent the UID of the tag which is supposed to be unique to each NFC tag. as @Bombastisch mentioned could you give the output of the nxp tag info app? It might be that we could simply write to those pages (not possible for legitimate tags). If i made a custom app would you be willing to try? |
@Bombastisch @HiddenRambler The tags are not identified as NTAG215, but NTAG203(F). Erasing my written tag using the first app is not at all effective. TagMo still identifies it as the Zelda Guardian Amiibo, so I guess my last Mario write to it was ineffective. Thus because it is already identified as an Amiibo TagMo will not write to it again. This is while unchecking NTAG215 validation of course. Here is the dump of this Guardian tag using the second app: https://pastebin.com/raw/DAR7sRam As I had two additional blank tags (all FF's), I wrote Mario to one using TagMo. Here is the dump of it, similar results: https://pastebin.com/raw/ciXdFC2w Thus I have one more blank tag, and these two written ones. I'm happy to help however I can. |
Do you by any chance have a samsung phone? The NTAG203 identification is most likely an unrelated phone issue. Would it be possible to get the dump from a different phone (of a friends perhaps)? |
I have a OnePlus 3 running Lineage OS. I have access to a fairly wide variety of devices if necessary. |
Thanks. Please post a dump from a different phone. We've had NTAG203 identification issue which was mostly due to phone hardware. |
I'm getting the same results scanning from a Nexus 6 and Google Pixel. |
Popped open the plastic housing and the tag PCB is entirely unmarked. |
I get the feeling that the device does not implement the tag identification method. leading the app to believe its ntag 203. I think a modified version of tagmo might work unless it needs special commands. I've ordered a powertag. will see if anything can be done when I get it. I didn't buy a writer though so it might end up being a waste. |
Any progress on the powertag? @HiddenRambler ? :) If U can implement support for it I'd would be a great improvement I think! |
This is what i have been working on for two weeks now. I just got an idea about how to make it work last night. It will have limitations but i think we can make it work. |
New version released. A wiki page has been created with the basic usage. https://github.com/HiddenRamblings/TagMo/wiki/PowerSaves-Support |
On attempting to write to my two already written tags from above I get the error "No available key for P10_ID". I don't have the PowerSaves base, so will I not be able to wipe them? If PowerTag support is not enabled by default I could see others running into the same issue. Regardless, I am able to successfully write and rewrite the same and different Amiibo interchangeably to the third tag I have without issue. I can't thank you enough for taking additional time to add this support! |
@daleriechert I'll add support for this scenario (and your two tags) very soon. |
@daleriechert please check the latest release (2.6.1) |
I checked and it works great on all the tags, thanks again! |
So can I confirm Tagmo works fine on power tags with latest Update |
I'd like to request investigation into the support of Datel's rewritable NFC PowerTags. This would circumvent the need for single-use tags, and support from this app would also circumvent Datel's proprietary PowerSaves USB NFC writer and software. A single tag is bundled with new packages of the PowerSaves writer, or separately in 3 and 10 packs here:
http://www.ebay.com/itm/252829545695
http://www.ebay.com/itm/252828341082
The tags seem to arrive blank, all FF bytes. I attempted to write SSB Mario to one, and data is written to the tag, but it is not valid in-game. Notably bytes 01D5-01DB remain FF after the tag has been written to.
The text was updated successfully, but these errors were encountered: