Xsiid wont read or write

[amal]

@mfries18

@Az_F

I don’t think you can brick it by doing that

I soft bricked mine doing just that, Android really really didn’t like the tag. Had to use some random 3rd party(non the usual) NFC app to get it to work.

I prefer “borked” for this term over “bricked” haha You can unbork some things… you can’t unbrick it.

@Az_F

Sure android would be confused but apps like tag info which just dump the entire content should at least be able to read the first blocks and even dump the rest wether it makes sense or not.

Android has its way with your saucy little NFC tags well before any NFC apps get a shot at it… think of it like digital droit du seigneur. If the Android NFC stack shits the bed, your app never gets a chance. This is talked about somewhat in the long-winded post here;

So what happened with the 2k memory on the xSIID?

TL;DR - The first batch of xSIID made December 2019 were formatted to try to use all 2k of memory across two 1k memory sectors for NFC applications, but the NFC stacks built into Android and iOS phones don’t know how to properly read multiple memory sectors in NFC Type 2 chips. Future batches are formatted to only use the first memory sector which is 1k for NFC applications. The remaining 1k is still readable and writable by phones, but only with a custom smartphone app that can directly address…

In most cases though, Android should not have a problem with a broken NDEF record… but in some instances it friggen borks hard.