So I’m trying to read and clone a Paradox Fob (C704 I believe by physical appearence, but my numbers on the back are “5021435” and “'APJN14”) but I keep getting an “Error Manchester at [number]” and all the data read from the fob keeps changing everytime I read it.
What’s wrong?
Using Proxmark3 Easy Generic 256kb
Want to clone to NExT chip implant
# If you want to use it, copy this file as Makefile.platform and adjust it to your needs
# Run 'make PLATFORM=' to get an exhaustive list of possible parameters for this file.
#PLATFORM=PM3RDV4
#PLATFORM=PM3GENERIC
# If you want more than one PLATFORM_EXTRAS option, separate them by spaces:
#PLATFORM_EXTRAS=BTADDON
#PLATFORM_EXTRAS=FLASH
#PLATFORM_EXTRAS=BTADDON FLASH
#STANDALONE=LF_SAMYRUN
# Uncomment the lines below in order to make a 256KB image
# and comment out the lines above
PLATFORM=PM3GENERIC
PLATFORM_SIZE=256
STANDALONE=
SKIP_HITAG=1
SKIP_FELICA=1
SKIP_HFPLOT=1
SKIP_NFCBARCODE=1
SKIP_ZX8211=1
#SKIP_LF=1
SKIP_HF=1
SKIP_ISO14443a=1
# To accelerate repetitive compilations:
# Install package "ccache" -> Debian/Ubuntu: /usr/lib/ccache, Fedora/CentOS/RHEL: /usr/lib64/ccache
# And uncomment the following line
#export PATH := /usr/lib64/ccache:/usr/lib/ccache:${PATH}
# To install with sudo:
INSTALLSUDO=sudo
Yeahh I know, if I knew earlier it was a 256 I wouldn’t have gotten it xd
Yes I did successfully clone my condo key(T5577 if I remember well) to my chip.
Not sure to get what you mean by your last line?
I do know this Paradox fob is LF because the lf tune responds very well to the fob (-10v difference)
And what do you mean by try Mifare Classic with a few blocks of data? Writing the data to the fob? Reading a few blocks?
I can’t find a description of that Manchester error, nor see why or where it comes from. If I was able to I could debug that maybe?
I’m kinda thinking, your build looks fine, but I do wonder if the lack of free space is causing you the issue you are having.
Forget about your Manchester for now, I was wondering, if you were to do a new build, but rather that the LF build, try a HF build.
And try to copy and write a Mifare classic (if you have one)
If you get a similar error, It may indicate that space is your issue.
If it works, it may be an error with something specifically on the LF side.
I’m clutching at straws, but the elephant in the room is the 256…
So, I did try an HF build and I wrote on my chip my website URL. I didn’t try with a chip but I’m pretty confident the process would be the same and succeed.
So now what can we look into since the problem does seem to come from the LF side specifically…
I forgot to mention a really important thing
I was able in the past and even currently to read and clone LF chips with all this very same system.
After seeing this Manchester error, I tried to read another LF chip I have and this one reads without any problem.
I think all of this makes the problem even more of a mystery…
So, I have to be honest and say I don’t really get what’s Manchester. I think I found out it’s a protocol? And I was also not able to find out if this Paradox fob is Manchester protocol (but probably is because of the error).
Nevertheless, the other fob I read from was a basic T5577, yes.
Don’t have access to my computer atm, but if I remember well it just didn’t do anything at all, don’t find nothing.
However there was also an error that prevented me from launching “lf read” on its own (or within the lf search command, as I think lf search does incorporate lf read), saying something like “command unknown”.
Also, I was however before able to launch all these commands without any problem (but without testing with Paradox fobs)
That being said, I don’t think this “lf read, command unknown” error has anything to do with Paradox fobs because it also shows when I scan other fobs.
