PROBLEM: The current cloner sucks. It corrupts xEM tags if the coupling isn’t perfect and the only way to recover them is to use a proxmark iii and issue command;
lf t55xx write b 0 d 00148041 p 51243648
The “p 51243648” specifies the password set by the cloner. If the xEM was never properly written to by the cloner, then this password will not be set and won’t be necessary to communicate.
SOLUTION: Make our own reader/writer/cloner that doesn’t eff up your xEM tag and allows you much greater control over your ATA5577 chip based xEM tag. It can function as a standalone cloner as well as a connected reader/writer and “tag manager” device. Perhaps store multiple tag IDs and select them via pushbutton to write those IDs to the xEM at will. Emulation is not an intended goal for this project.
GITHUB: https://github.com/DangerousThings/xEM-Cloner (may rename if project scope widens later)
Initial project plan:
Scope : Reset corrupted xEM chips.
Use : Immediate DIY fixes.
Hardware : Minimal, cheap, simple EE.
Software : Minimal, one-off script.
Scope : Read/Write data to/from ATA5577 chip.
Use : Early developer access.
Hardware : Prefab, little to no EE required.
Software : Core library with one spec/device specific module.
Scope : Full data and feature management of ATA5577 chip (read/write/clone)
Use : Arduino shield design / Retail board
Hardware : Ideally MVP compatible, no EE required.
Software : Stable library + full suite of spec/device modules.