xEM no longer readable after first commands

When it comes to writing data to the T5577 chip inside the xEM, it doesn’t matter what the device you use is… it’s still possible to tear the configuration bytes. Read this post;

https://forum.dangerousthings.com/t/quirks-of-the-t5577-cloning-tags-to-the-xem/

Now that you’re all caught up on tearing issues, I can say these things;

  1. the response you’re getting trying to read the xEM is the exact response you will get if one of the following is going on: A) you are reading a perfectly configured xEM chip but the coupling is bad due to placement, antenna geometry mis-match, etc. or B) your coupling is good but the configuration bytes on the T5577 have been configured due to invalid data being written, or a tear event occurring.

  2. recovery is possible https://forum.dangerousthings.com/t/xem-cloning-emulation-modes-and-the-perils-of-chinese-cloners

  3. we need a proxmark3 manufactured with antennas designed to work with x-series chips.

Thanks,
Amal