I was trying to write to my T5577 using lf t5 dump & lf t5 restore -f filehere.
I noticed I would dump it, and the values wouldn’t be the same as what I read off the original keyfob, so I tried it multiple times and it kept happening so I decided to try and write it line by line rather than a restore.
So I tried this guys instructions and started with t5 det, and proceeded to use “lf t5 write -b 0 -d 00105080” and this is where the problem began. I haven’t been able to get a good read since, or write to it or anything.
This is what it looks like if I try to dump multiple times.
writing block 0 means reconfiguring the analog frontend settings of the chip, which is basically telling the chip how to communicate over RFID. Changing this changes the way the chip “talks” over the shared magnetic field coupling.
So that is the result every time you dump it? It doesn’t change?
What if you just start with lf search (post outcome) and then lf t5 detect (post outcome)?
Now mind you, I have ran through the troubleshooting guide and tried to write it as an EM as well.
The only thing I can think of is to try and change the modulation of block0 in the config to match what I set it as, but I’m not sure how to do that after running 'lf t55xx config'
edit: The dump does change. I’m not sure if I am just not getting a good connection, but my implant is really close to my skin and I’m not moving after running
huh odd… expected more data… ok well whatever… basically your stuff is compiled for the wrong hardware. the iceman branch defaults to the RDV4 hardware platform, and this red text is telling you the hardware does not match the firmware / client you’ve got… this will cause a kind of proxmark dementia when it comes to operation.
this must be fixed before you can rely on your proxmark to work properly.
since you’re on mac… eh i need someone else familiar with mac to cover how to fix this.
What product is it? A 
]
