How to tell if xEM is bricked

Thanks for that post, I will check it out.

Funnily enough I may have a very cheap but out of date xEM still in the syringe on its way to me soon - probably not one to inject but maybe one to experiment with.

I was just reading Tom’s great post here lots of good information, but under the White Cloner and the 2. Newer than 2015 sub-heading I read this:
c. The input button is useless as the device does some crazy conversion that as stated above is nonsensical and so far, impossible to figure out. So really this device is only good for cloning.

Based on my experiences this evening I would have to disagree with that. I’ve written to 125khz tags that came with it using the input button and my xEM. Now as mentioned in my post above, yes after a subsequent read it seemingly spat back an incorrect code to me, but in actual fact what it had written to my xEM was the correct code I inputted, so it did in effect work for me.

The paragraph I take issue with sounds like someone who has read a xEM with the white-cloner and seen a unexpected code, even possibly read, written and re-read to check and saw a different code to what they wrote/expected but then failed to check the xEM on another reader, because when I do I get the correct UID I was expecting and had programmed in.

Perhaps I’m missing something (probably!)

2 Likes