The github explanation says that some T55 clones can have that data changed, but in that case, the likelihood that a T55 clone has accurate data to begin with is low.
And this brings up the question of why that data would change if the “lf t55 wipe” command was run. Does that command include targeting the tracability data knowing that “real” T55’s can’t have that data changed?
And this brings me back to questioning why that would be important to have accurate data in an implant.
Amal, do we know for sure whether the T5577’s in the xEM (and other implants for that matter) are “real” (not that I really care, just curious).
Edit: I’ll have to look into this and see what I get when I “trace” my two T55 implants when I get home.
It’d be the xEM and we are pretty sure they are legit t5577 but we did not source these our factory engineering staff did. Honestly if they are clones with writeable traceability data, I kind of think that’s better.
don’t know what this is about with iceman firmware not doing t5577s properly but it ain’t true. it’s fine. if you need help writing something with iceman fw lmk. you shouldn’t have any other firmware on your proxmark. they’re all otherwise depreciated.
iceman fw doesn’t mess with init timings it has standard block configurations for all its listed formats.
I couldn’t reply to my original topic because of a limit on replies by new users on their first day, so here’s my reply to @amal from the original post.
This. It gives the manufacture date, lot no, wafer no, etc, of the chip. I’m sure it’s probably trivial, I just like keeping things as close to original as possible.
The “sibling” xEM is likely to give you something close to original. If the data was truly wiped on your xEM, it is gone unless you have a copy of it somewhere.
i can assure you it is trivial and unnecessary to keep, in some very limited circumstances, you need to overwrite traceability data in order to produce a functioning credential (usually for encoders with enrolling not readers themselves)
After doing some digging I realized just how trivial it really is, I’m not worried about it anymore. He has been using a Flipper Zero to program his, which overwrote his original traceability data with that of his work fob, and I have since done the same with mine as well.
Now I need to save up and get the XSIID NFC + LED implant for my other hand. I travel frequently for work and almost always end up with a stack of hotel key cards because I’m constantly forgetting them in my room and having to get replacements from the front desk, so being able to clone those to my other hand and never having to worry about locking myself out of my room will make it just as useful as my xEM is.
The stack I’ve been messing around with tonight seem to be almost exclusively MiFare Classic 1k. My Proxmark3 came with four cards and one fob, all HF, and I was able to clone the card for the hotel room I’m currently in onto them. I must have had my implants confused, it looks like the xM1 is the chip I need for that. I’ll still get the xSIID in my right hand cause I really want the LED and it will work with the door locks I’m putting on my house, so I’ll eventually end up getting them both.
I just got one less than a week ago, and already planning on two more. I didn’t realize just how slippery this slope would be.
On a related note, now that I got my chip working again I went and flashed Iceman fw back into my Proxmark and haven’t had any issues. Not sure what the deal was there…maybe a bad flash when I first updated it from the half broken version it came with from the factory?
xMagic is my new favourite and I wish I had done it instead of the NExT to be honest. I like the NExT but I am mainly doing access control so the xMagic is better for my scenarios.
