Hoping someone can help with my basic understanding as I am still learning how to correctly identify the correct source and destination card and then clone it to another tag.
I have a jablotron card where I have used the command: lf jablotron reader.
This returns Card: 78e08, RAW: FFFF000049511296, Printed: number which matches the text on the card.
If i try to run the command lf jablotron clone --cn 78e08 --em
The card ID is too short. I can’t see any other options with this command set to get the card number, any ideas?
I can also run this command which provides some additional info, but not sure if i should be using this instead of the jablotron specific command, and/or if this helps me at all as i don’t see the card number still. Running the lf em 4x05 chk command will find a valid password. Help would be appreciated, can i use these commands instead and just write to a new card?
[usb] pm3 → lf em 4x05 info
[=] — Tag Information ---------------------------
[+] Block0: 00040072
[+] Chip Type: 9 | EM4305
[+] Cap Type: 3 | 330pF
[+] Cust Code: 0x200 | Default
[+] Serial #: 34D0B099
[=] — Config Information ------------------------
[=] ConfigWord: 0001809F ( JABLOTRON / NEDAP 64 )
[=] Data Rate: 31 | RF/64
[=] Encoder: 2 | Biphase
[=] Delay: 0 | no delay
[=] LastWordR: 06 | Address of last word for default read - meaning 2 blocks are output
[=] ReadLogin: 0 | Read login is not required
[=] WriteLogin: 0 | Write login is not required
[=] Disable: 0 | Disable command is not accepted
[=] R.T.F.: 0 | Reader talk first is disabled
[=] Pigeon: 0 | Pigeon mode is disabled
can you drop an lf search on the jablotron card plz
and are you writing to another em3405 you’ve bought specially for this? if you’re trying to clone to another jablotron it wont work they come write locked.
So the line 6 is the number from the original card, but the numbers from the HEX output
Is this just a case of writing the HEX code directly to the sectors that match the original card
My cards have turned up and I did the steps as above and the card isn’t read on the reader. It will beep twice, but the access light will stay red and the door won’t open.
Possibly the cards i have are incorrect?
I used the lf Jablotron clone --cn HEX Card ID–em command to see if that helped, and that takes line 2 from the card, has the same issue.
I used the commands that Equipter posted about, i also used the Jablotron specific command as above with the clone option which wrote IDs 2 4 and 5 ( if i recall).
Oh sorry I didn’t read haha. The devil is always in the details… something isn’t adding up here and the best way to figure it out is to be extremely verbose and walk through all testing and actions step by step.
When using the card on the reader using the above commands, i don’t get any ACK from the reader.
Using the original commands for the 4x05 as above, i get a denied beep and a red light.
ok thanks for the screenshots, but please edit your post to put titles and chronology together for your screenshots. think back to school when you had to write a report… make it clean and easy to read for the people trying to help you.
Scan of source card (lf search)
Scan of target fob before writing (lf search)
Confirm target fob chip type (lf t5 detect)
Attempt write to target (lf jablontron clone --cn 34D0B099)
Scan target after write (lf search)
Take the above bulletpoints and put the appropriate screenshots under each of them. That will make it very clear the order of things and what’s happening… and importantly it will be clear if you are missing any information… which i kinda think you might be.
Ultimately I think the target fobs/chips you got are T5577 but the instructions above are for writing to EM4x05 … which is a different chip… but really the primary concern is that the fobs you got are not actually writable at all… the url you gave for where you bought them seems to indicate they are T5577 but your screenshots indicate they might not be… that or the screenshots are out of order and confusing me.
I reordered the previous post to make it a bit clearer. It does feel like the details either aren’t being written correctly, or i am missing something.
Ok great! Now all we need to do is figure out why the correct ID is not being written. I can’t do that now because I’m mobile at the moment… but I’ll check it out later if nobody else can pop in on this before then.
