So I got my PM3 Easy up and running with some persistence. I decided to just scan some things, get used to the commands, what to look for and how to make sense of all the info it spits out.
Problem is my apartment key fob now no longer works? I ran a few commands on it;
lf search, told me it was a t55xx so run that…
lf t55xx detect
read through some more commands in the wiki;
lf t55 p1detect
lf t55 read
left it on there for a bit while reading some other things, looking for what needed to be duplicated… came back and ran another ‘lf search’ and it came back with nothing.
It’s reading other tags fine… went downstairs and presented the fob to the reader and… nothing. It’s not a huge issue, will just cost me $10 to replace it with a new one… but… any idea what the hell happened?
This will wipe the tag for sure. More and more I am seeing fobs and cards actually use the T5577 instead of like an EM chip or something… this is because the T5577 is way better for a fob or card maker to keep in stock as a single source chip… they can make a shitton of inventory with one chip and program it with whatever they need… be it EM or HID or Indala or AWiD or whatever… so now these fobs are shipping out with T5577s and no protection… nothing… you can easily wipe it and put whatever you want on it.
I accidentally wiped a guy’s frickin government ID badge by accident… couldn’t believe it… he had to wade through a bunch of shit to get a new one too… they were like “what the fuck were you doing that got this wiped?” … really not happy… so as a PSA to anyone wanting to clone a thing to your implant, treat that thing with kid gloves… because chances are it’s an unprotected T5577.
Hmmmm, just had a THUNK
Check your log, you may have a copy of your log results, therefore you should be able to find it in the .txt , use the info, wipe and then write
PROBABLY in a folder like
GitHub/Proxspace/pm3/proxmark3
log_20200317.txt or similar maybe log_20200317.txt (log_yearmonthday.txt)
Good luck mate,hope it works, let us know if it works…Might as well write to you NExT- xNT
Problem is I was just using a command window. My issue with the pm3 was I had requested they flash it with the latest iceman repo but it came with some unknown firmware from 2018 with a bunch of weird ascii characters for the name.
So I was following the instructions regarding proxspace and pm3 compile/flashing and told me to flash the bootloader first, but attempting to do so started the “cannot communicate with proxmark” thing. I ended up flashing with precompiled official firmware from Gator(insert numbers) from the proxmark.org forums, and that worked. So I had to use command instead of the MING64 whatsit so no log was generated.
The fob doesn’t work though, so I don’t think I could even wipe it and rewrite the info. Won’t get picked up by the pm3 or the reader at the building entrance, so… I’ll work on reflashing the pm3 and getting that working smoothly, get a new fob and then try cloning that.
Does anyone happen to know if the AWID specific commands still work? still need to reflash my pm3 but back in 2017 it seems they added AWID commands (lf awid clone etc.)
Oh this is just plain strange! I would check the logs to see what possibly happened during that time. Maybe it was just a dodgy chip and now was it’s time to go. Seen this once before.
