it did when I had it on there yes, so the data I write to it is intact, but it just fails to erase and there is all this extra garbled shit in the ndef readout that I have no clue why its there
I know you said you didn’t like NFCTools, but have you tried the erase tag option there?
Yea, it works there, and I can write to it in NFC tools as well, but if I write something to it with tagwriter, it does not appear when scanned in nfc tools, it shows the device as empty, no record, no used space, nothing, but it is definitely there
I’m not certain what would cause that disconnect unfortunately, I just tried writing to a tag with tagwriter and then checking with NFCTools and it shows a record for me, the best I can recommend at the moment is to retry after the ndef fix pilgrimsmaster posted
Hopefully it works, or I’m sure someone else will be here with an idea
Edit: Tagwriter erase also works for me
ok will do, thank you
I have retried the above possible solution 4 times now, and it is still producing that long garbled stuff in the ndef record and not letting me actually erase it in tagwriter , and in nfc tools, if I erase it works, but afterwards if I got back to taginfo it still has the dangerousthings link in the ndef from the above reset commands.
I am really stumped and bummed. I appreciate all of your help here, and I suppose i will sleep on it for tonight and come back to see if anyone might have been able to find a solution to help me out.
Just to clarify, it’s Tagwriter creating the jumble?
You may try writing to the tag once with NFCTools and then seeing if that formats the ndef section properly
Beyond that, what I would probably personally try is zeroing out a chunk of the user data manually with nfc shell before retrying the fix and writing an ndef record
I honestly don’t know what is making that jumble, all I know is it shows up in the FULL section of taginfo, but otherwise other apps all think its empty.
I will try writing with nfc tools, will post results, then I have to turn in for the night.
Ok so I wrote a YT link to it in NFC tools, after eraseing it with same app, Then, tested to make sure the record link worked, which it did, and then went into taginfo and did a FULL scan, now the jumbled data is still present in the full ndef read out, but it appears that when I write something new to it, using NFC tools, if overwrites just the space that the new record uses, which means that YT link is then followed by whatever cut off part of the assumedly trashed remaining ndef record data.
Should I attempt to overwrite it all? I don’t know with what but if it would mean I could get rid of all that junk written in there would it be worth it to try?
If you’d like, I can DM you a whole bunch of lines for NFC Shell to 0 out the entire NDEF record except for the fix section, that will definitely get rid of the jumble
Or, if you have a different method for getting rid of the jumble, that should work too.
It also probably wouldn’t harm anything to leave it there, but I would want it removed personally for no real reason
Oh, yes please do send me that shell info!
Ill give it a shot as soon as I can and get back to ya. Thank you!
I was going to DM it to avoid sending a few hundred lines of code into the forum, but just in case anyone else with an XSIID wants a completely clean NDEF section:
Copy and paste the text into NFCShell, and then overwrite the Dangerous Things link with your record of choice
Tested on my implant, and it takes a few seconds, so hold your phone there until NFCShell finishes
This should work on the 1k versions of the XSIID as well, the addresses look the same on the datasheet, but I only have the 2k version to actually test on
Oh Christ please don’t use NFC Shell if you don’t know what you’re doing. There wasn’t much risk of bricking the implant with NFC Tools or TagWriter because of the way the chip is configured from DT, but if you start sending raw commands without knowing what every single line is doing you seriously can brick the thing.
What happened with all the garbled nonsense at the end is that you were writing new links to your tag, and it was adding them as new “records” at the end of the NFC “message”. Unless you factory reset or manually overwrite, the empty space will remain messy.
TagWriter has been throwing up that error because a true “factory reset” would change the configuration protection settings that DT loaded, and it can’t do it because there’s a non-default password set. I’ll take a look and see what I can do
Ok so this is what you were seeing. It’s because TagWriter sucks
Here’s my NExT (similar memory structure) with a multi record NDEF message written to it.
You can use the “Format Memory” option in NFC Tools to clear the empty space without password authentication.
And here’s the NExT after being cleared.
Now that you know about NFC Shell please do be careful and ask before you write.
I can’t do the format memory option in nfc tools, it says my device does not support that
Okay, well you can use NFC Shell for this if you want. The A2 is the Write command byte, the 04,05…E1 is the page number byte, and the 00000000 are the four empty bytes you want in each page
A20400000000 A20500000000 A20600000000 A20700000000 A20800000000 A20900000000 A20A00000000 A20B00000000 A20C00000000 A20D00000000 A20E00000000 A20F00000000 A21000000000 A21100000000 A21200000000 A21300000000 A21400000000 A21500000000 A21600000000 A21700000000 A21800000000 A21900000000 A21A00000000 A21B00000000 A21C00000000 A21D00000000 A21E00000000 A21F00000000 A22000000000 A22100000000 A22200000000 A22300000000 A22400000000 A22500000000 A22600000000 A22700000000 A22800000000 A22900000000 A22A00000000 A22B00000000 A22C00000000 A22D00000000 A22E00000000 A22F00000000 A23000000000 A23100000000 A23200000000 A23300000000 A23400000000 A23500000000 A23600000000 A23700000000 A23800000000 A23900000000 A23A00000000 A23B00000000 A23C00000000 A23D00000000 A23E00000000 A23F00000000 A24000000000 A24100000000 A24200000000 A24300000000 A24400000000 A24500000000 A24600000000 A24700000000 A24800000000 A24900000000 A24A00000000 A24B00000000 A24C00000000 A24D00000000 A24E00000000 A24F00000000 A25000000000 A25100000000 A25200000000 A25300000000 A25400000000 A25500000000 A25600000000 A25700000000 A25800000000 A25900000000 A25A00000000 A25B00000000 A25C00000000 A25D00000000 A25E00000000 A25F00000000 A26000000000 A26100000000 A26200000000 A26300000000 A26400000000 A26500000000 A26600000000 A26700000000 A26800000000 A26900000000 A26A00000000 A26B00000000 A26C00000000 A26D00000000 A26E00000000 A26F00000000 A27000000000 A27100000000 A27200000000 A27300000000 A27400000000 A27500000000 A27600000000 A27700000000 A27800000000 A27900000000 A27A00000000 A27B00000000 A27C00000000 A27D00000000 A27E00000000 A27F00000000 A28000000000 A28100000000 A28200000000 A28300000000 A28400000000 A28500000000 A28600000000 A28700000000 A28800000000 A28900000000 A28A00000000 A28B00000000 A28C00000000 A28D00000000 A28E00000000 A28F00000000 A29000000000 A29100000000 A29200000000 A29300000000 A29400000000 A29500000000 A29600000000 A29700000000 A29800000000 A29900000000 A29A00000000 A29B00000000 A29C00000000 A29D00000000 A29E00000000 A29F00000000 A2A000000000 A2A100000000 A2A200000000 A2A300000000 A2A400000000 A2A500000000 A2A600000000 A2A700000000 A2A800000000 A2A900000000 A2AA00000000 A2AB00000000 A2AC00000000 A2AD00000000 A2AE00000000 A2AF00000000 A2B000000000 A2B100000000 A2B200000000 A2B300000000 A2B400000000 A2B500000000 A2B600000000 A2B700000000 A2B800000000 A2B900000000 A2BA00000000 A2BB00000000 A2BC00000000 A2BD00000000 A2BE00000000 A2BF00000000 A2C000000000 A2C100000000 A2C200000000 A2C300000000 A2C400000000 A2C500000000 A2C600000000 A2C700000000 A2C800000000 A2C900000000 A2CA00000000 A2CB00000000 A2CC00000000 A2CD00000000 A2CE00000000 A2CF00000000 A2D000000000 A2D100000000 A2D200000000 A2D300000000 A2D400000000 A2D500000000 A2D600000000 A2D700000000 A2D800000000 A2D900000000 A2DA00000000 A2DB00000000 A2DC00000000 A2DD00000000 A2DE00000000 A2DF00000000 A2E000000000 A2E100000000
I tried to make it comma separated so it would work on NFC Tools but fuck editing csv files, it’s a nightmare. Every editor assumes you want it converted to view as newline separated. No, I fucking wanted the commas, that’s why I converted to csv!
Ok so I gave that a go, and I copy pasted it directly so made sure it didn’t get messed up before writing to it, it worked, I think, but there is still a line in the FULL readout of taginfo, that says 0E2 00 00 FF C9
and the one below it named 0E3 says 00 00 00 E2
Do I need to worry about those? Every other line is 00 00 00 00.
E2 is the beginning of the config pages for sector 0. Don’t worry about those.
Ok awesome, thank you so much for your help!
Sometimes the XSIID misbehaves with NFCTools if you zero out the NDEF space entirely, thus the earlier fix
If you use the code I linked to earlier, it does the same thing, but also puts the Dangerous Things link NDEF record in, to give NFCTools a properly formatted NDEF section to overwrite all in one step
If you just zero out the NDEF you may have to go back and manually enter a record anyways, so keep that in mind