I am currently using a modified version of the Proxmark3 software that restricts usage to their proprietary blank fobs. I’ve tried various commands, such as lf t5 dump and hf iclass dump, to explore compatibility with other RFID tags but have been unsuccessful in getting third-party fobs to work with the software.
Recently, I executed the command lf t5 chk and successfully identified the password for a T55xx tag. However, as I am new to this field, I’m unsure how to proceed from here to enable my third-party fobs to function with the modified software.
Could you please provide guidance on the following:
How to properly configure the software to accept third-party fobs?
Steps to write the identified password to another fob if it supports password functionality.
Any additional commands or techniques that might help with this process.
Why are you doing this? Is it work related? Are you trying to use cheaper fobs on an existing system? What are your goals exactly?
If that proxmark3 has a work related firmware, I’d recommend buying a new one. Dangerous Things sells a version of the PM3 Easy that has some reinforced solder joints and comes with the Iceman firmware.
On the other hand, if you have a proxmark3 that you can flash freely but came from an old proprietary system, I’d look into the Iceman firmware.
I am currently reselling Proxmark3 devices with modified software that includes a simplified interface and an Android app for ease of use. However, the software only works with blank fobs purchased from the original vendor, similar to how iCopyX locks their devices to specific fobs.
The issue I’m facing is that when trying to use third-party T55xx or iClass fobs, the software displays an error stating “unrecognized fob.” I’ve explored this by running commands like lf t5 dump and hf iclass dump using the Proxmark3’s standard ProxSpace software, and the fobs seem identical in structure to the vendor’s fobs. I suspect the vendor has embedded an ID, password, or some other protection in their fobs to enforce this lock-in.
I have made some progress by running lf t5 chk and identifying the password on the T55xx fobs, but I am not very technical and haven’t been able to figure out how to make third-party fobs work with this modified software.
What I’ve Tried:
Dumping both vendor fobs and third-party fobs, which appear to be identical.
Using lf t5 chk to find passwords and testing write commands to clone data.
Exploring Proxmark3 commands for both LF and HF fobs to better understand what protections are in place.
The Goal:
Enable third-party T55xx and iClass fobs to work with this customized Proxmark3 software.
Identify how the vendor’s fobs are locked and replicate that protection on third-party fobs.
Maintain the ease of use that my customers like about this software, as the standard Proxmark3 interface is too complex for them.
I believe the vendor may have embedded a hidden identifier, custom firmware, or a password on their fobs that restricts compatibility. Any guidance on how I can replicate this or bypass the lock-in would be greatly appreciated. Many of my customers prefer the simpler interface, and I want to give them more flexibility in fob options.
From what saw, the iCopyX has/had the potential to be a really good device, I was excited to get one, but iCOPY fucked up!!! They lost me and I assume many more potential customers.
MY OPINION
iCopyX shot themselves in the foot when they locked down their device to their proprietary cards.
They later opened this up to EU versions (I think), but not others, but even that was too little too late.
Again, still my opinion, but only some RFID fanboys got 'em, and now it’s only people that stumble on them that don’t know any better.
I still wouldn’t reccomend them, and would steer people away from them.
Most, if not all people here, are big proponents of open source.
With that business model that iCopy and you share, I can only really speak for myself, I’m out, but my guess is you already lost every other potential customer here.
MY ADVICE
To be clear,
I’m not critisizing, merely providing some constructive feedback for you to consider
This is still not open source but more palatable:-
Charge a little more for the device that gives them ease of use and a paid android app but, use THAT as the selling point and the justification for the higher price.
( Make sure you advertise you need the App and it also comes at a price, or include the app cost price in the Hardware purchase )
Don’t lock them to vendor card’s only, I think this will only serve to piss people off, also, don’t even consider a subscription model.
You might want to consider some well respected people in the community to send some to for endorsement, here’s a few for you to consider. @Iceman @amal @Equipter @Aoxhwjfoavdlhsvfpzha @doegox
There are others, but a few to consider
Whatever path you choose, I wish you luck with your business
