Closed underfl0w closed 4 years ago
Your lf device timings indicate you are on a non-rdv4 device.
Your clone didn't return success, indicating client couldnt verify the written data.
Have you tried looking at your t55xx data and see if it matches the blocks that was suppose to be written?
It's a proxmark3 easy with the firmware PLATFORM=PM3OTHER set.
You're right, the writing to the chip did not succeed. It did however work when I used the example command in the documentation
lf indala clone -l -r 80000001b23523a6c2e31eba3cbee4afb3c6ad1fcf649393928c14e5
But it still fails too read the original keyfob or clone it to the t55xx.
When using the official proxmark3 firmware I was able to read the real keyfob and clone it.
lf indala clone 80000002671d756170651ef1f782af5a8b5ad63f25559fbf2a2e1b53 l
Now after reflashing RNG/Iceman it gives me this when using lf search
Like I said, can you look at the t55xx data and see what got written?
[+] Reading Page 0:
[+] blk | hex data | binary | ascii
[+] ----+----------+----------------------------------+-------
[+] 00 | 000820E0 | 00000000000010000010000011100000 | .. .
[+] 01 | 00C000C0 | 00000000110000000000000011000000 | ....
[+] 02 | 671D7561 | 01100111000111010111010101100001 | g.ua
[+] 03 | 70651EF1 | 01110000011001010001111011110001 | pe..
[+] 04 | F782AF5A | 11110111100000101010111101011010 | ...Z
[+] 05 | 8B5AD63F | 10001011010110101101011000111111 | .Z.?
[+] 06 | 25559FBF | 00100101010101011001111110111111 | %U..
[+] 07 | 2A2E1B53 | 00101010001011100001101101010011 | *..S
[+] Reading Page 1:
[+] blk | hex data | binary | ascii
[+] ----+----------+----------------------------------+-------
[+] 00 | 000820E0 | 00000000000010000010000011100000 | .. .
[+] 01 | E03900D0 | 11100000001110010000000011010000 | .9..
[+] 02 | 7920F272 | 01111001001000001111001001110010 | y .r
[+] 03 | 00A00003 | 00000000101000000000000000000011 | .... `
Screenshot :
hm, looks the same. Only thing I came come up with now is the config block.
lf indala clone on offical
lf t55xx detect
lf indala clone on iceman
lf t55xx detect
And see if the config blocks matchs.
So the difference is that
And lf t55xx detect
iceman detects the same
Things do change a lot after cloning it when on Iceman.
Official does recognize the clone that is made on Iceman.
So I did the same thing when using the raw id given in the example on lf indala clone. This seems to give similar results to the other clone but it is detected on iceman.
[usb] pm3 --> lf indala clone -l -r 80000001b23523a6c2e31eba3cbee4afb3c6ad1fcf649393928c14e5 [=] Preparing to clone Indala 224bit tag with RawID 80 00 00 01 B2 35 23 A6 C2 E3 1E BA 3C BE E4 AF B3 C6 AD 1F CF 64 93 93 92 8C 14 E5
[+] Blk | Data
[+] ----+------------
[+] 00 | 000820E0
[+] 01 | 80000001
[+] 02 | B23523A6
[+] 03 | C2E31EBA
[+] 04 | 3CBEE4AF
[+] 05 | B3C6AD1F
[+] 06 | CF649393
[+] 07 | 928C14E5[+] Success writing to tag
[usb] pm3 --> [usb] pm3 --> lf t55xx detect [+] Found [2] possible matches for modulation.
--[1]---------------
Chip Type : T55x7
Modulation : DIRECT/NRZ
Bit Rate : 2 - RF/32
Inverted : No
Offset : 59
Seq. Term. : No
Block0 : 0x00080000
Downlink Mode : default/fixed bit length
Password Set : No--[2]---------------
Chip Type : T55x7
Modulation : PSK2
Bit Rate : 2 - RF/32
Inverted : No
Offset : 45
Seq. Term. : No
Block0 : 0x000820E0
Downlink Mode : default/fixed bit length
Password Set : NoChip Type : T55x7 Modulation : PSK2 Bit Rate : 2 - RF/32 Inverted : No Offset : 45 Seq. Term. : No Block0 : 0x000820E0 Downlink Mode : long leading reference Password Set : No
[usb] pm3 --> lf search [=] NOTE: some demods output possible binary
[=] if it finds something that looks like a tag
[=] False Positives ARE possible
[=]
[=] Checking for known tags...
[=]
[+] Indala Found - bitlength 224, Raw 0x80000001b23523a6c2e31eba3cbee4afb3c6ad1fcf649393928c14e5[+] Valid Indala ID found!
Pull latest and try again. the preamble detection for 224bits is less strict now. https://github.com/RfidResearchGroup/proxmark3/commit/32fdde3d00924abf41a3620d5c85ce28e924679a
I've verified that I'm able to read the tag now! Thanks a ton for fixing this so fast.
It has made me want to dive into actually start developing instead of just using your superb software.
Describe the bug I've gotten my hands on access card of an office building which is an Indala E8 type tag. I was able to read and clone the tag using the official proxmark3 master but not with RNG/Iceman
lf indala read
does not give the expected results.To Reproduce Steps to reproduce the behavior:
lf indala clone -l -r 80000002671D7561706500F1F7F2AF5B8B5ED74F256693BF442FF350
Expected behavior I would expect to be able to read the tag similar to how "official" would read the tag
Screenshots
Desktop (please complete the following information):
`