Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Hi, I have problems reading a T5557 card I recently bought on the the proxmark3.
None of the commands work, however a lf search u does detect the card.
Would appreciate any help I can get. Below is a quote of the output. Thanks in advance!
proxmark3> lf search u
#db# Sampling config:
#db# [q] divisor: 95
#db# bps: 8
#db# [d] decimation: 1
#db# [a] averaging: 1
#db# [t] trigger threshold: 0
#db# Done, saved 40000 out of 40000 seen samples at 8 bits/sample#db# buffer samples: ff ff ff ff ff e5 9f 5d ...
Reading 20000 bytes from device memoryData fetched
Samples @ 8 bits/smpl, decimation 1:1
NOTE: some demods output possible binary
if it finds something that looks like a tag
False Positives ARE possibleChecking for known tags:
No Known Tags Found!
Checking for Unknown tags:
Possible Auto Correlation of 32 repeating samples
Unknown ASK Modulated and Manchester encoded Tag Found!
if it does not look right it could instead be ASK/Biphase - try 'data rawdemod a
b'
010101770101010771
010101770101010771
010101770101010771
01010177010101111
010101770101010771
010101770101010771
010101770101010771
010101770101010771
010101770101010771
010101770101010771
010101770101010771
010101770101010771
010101770101010770
110101770101010771
010101770101010771
010101770101010771
010101770101010771
010101770101010771
010101770101010771
010101770101010771
010101770101010771
Offline
If you have written corrupted block 0 data to a t5557 card, is it possible to recover the card?
i.e
lf t55xx write 0 11111111
It does not respond to any read/write commands now.
Offline
Did you do a "lf t55xx detect" before trying to read/dump/info?
Offline
Yes I did, but I could not find the modulation.
I realise this occurs after I run the
em410xwrite <UID> 1
command. This command seems to corrupts the card.
After running this command I can no long read or write to the card.
Offline
The thing is I cannot write to the card at all.
Running
lf tm55xx write 0 <8 hex characters>
seems to do nothing to the card. Is the card damaged?
Offline
bummer, if it is a t55xx tag you can always write a new config block to the tag. That usually make the tag alive again.
Offline
lf t55xx write 0 00008040
lf t55xx detect
lf t55xx info
Offline
Yea I suspected so. That's weird.
Are there any sample config blocks I can try? The operation of the write command is independent of the modulation right?
Offline
I tried that but it still does not work. I cannot write to block 0. If I write a corrupted block 0 value to the card, etc.
11110001
, will the card still accept write commands?
Offline
Also, does OTP affect the writing of block0?
Offline
t55xx is very nice, it listens to the write command regardless what you wrote to the config block 0.
However, if its in password mode, you kind of need to add a password
how does the graph look like after you try a "lf read/data samples 2000"?
and after a "lf t55xx read 0"?
Offline
This is the graph. Could you help me identify if its in password mode? Thanks in advance!
Offline
Also, what is the default data and config in blocks 0 - 7 in a new blank t5557 card?
Offline
A ask default config block 0, would be as I wrote earlier: "00008040"
the rest of the blocks is only interesting if you want the tag to emulate another tagtype.. (ie config yr t55x7 to be a em410x)
However, there is two different reads I want you to show and you didn't say which one you are showing.
Offline
The tag does not allow me to write to block 0. I tried to write "00008040" to the tag, but nothing seems to happen to the tag.
Here are the data from the different reads! Thanks so much from your help!
lf t55xx read 0
lf read samples 2000
Offline
hmmm that isn't possible. it looks like you must not have sent the lf read - data samples 2000 correctly. (the plot still has 11996 samples in it)...
(they are separate commands - lf read - then - data samples 2000)
Offline
Oh I see! Here is the updated data samples data. Thanks marshmellow for pointing out the error! I was wondering why both graphs look the same.
Offline
it looks like the sequence terminator is turned on. the t5xx commands do not yet work with this config. (write commands should though.)
Offline
What is the sequence terminator?
The write commands don't work as well
Offline
are you sending the write command correctly? from the output above it looks like you likely have a valid t55xx tag (as it seems to respond to the read command if you notice the unmodulated starting point in your first plot image and the fact that the data shown isn't the same as the data in just a lf read.). meaning there is no reason the write command shouldn't work.
unless you have a t5555 or a Q5. there is a bug in the write of that tag in recent code (or at least i hear)
Offline
I'm quite sure I am. Below is the screenshot of the commands.
Offline
Try holding the tag a little off the antenna?
Offline
Tried that. It still does not work Are there any possible causes of such a scenario? Is there a one-time pad on T55xx cards?
Offline
the signal is strong, should be able to get a "lf t55xx info" out of it.. but it can't detect a clock..
how about you do it manually. use the "lf t55xx config" to set the ask, maybe a clock of 64 or 32...
and use the offset.. to skip until after the sequence marker... that should give you a good read...
Offline
it shouldn't affect the write command, as that always works. (as long as password isn't set, and yours isn't)
try the write command a few times in a row, sometimes the tag misses the start of command from the reader.
Offline
*edited*
or change the timings in lfops.c ... (and flash )
Last edited by iceman (2015-06-02 20:44:21)
Offline
iso14443a.c ??? you mean lfops.c
Offline
yes, yes, yes.. that was excatly what I meant.. ..
Offline
Hmm, what offset value should I use in this case?
I asked the supplier of the card. He informed me that it is not preconfigured with a password. The default configuration of block0 is "00 08 80 E8".
Does "lf em4x em410xwrite" write a password to the card?
Offline
Please understand the difference when you are dealing with a t55x7 tag.
A t55x7 tag can be configured to emulate different LF tags via modulation, bitrates, etc
When you want to read / write / configure the t55x7 you need to use the specific t55xx commands.
when you want to test if your t55x7 tag has been programmed correct, ie to emulate for instance a em410x tag, you can use the "LF SEARCH" or in this case "LF EM4X" commands to see if it behavies correct. It behaves correct when you can get a good read and value out of it.
CONFUSION: the "lf em4x write" command doesnt write to a em4x tag (since they are readonly) , it tries to configure a t55x7 tag to emulate a em4x tag. However this command doesn't use a password. SO if your t55x7 tag is in password mode, you need to use the t55xx commands to re-configure it to not use password. Then you can use the "lf em4x write" command..
ok?
Offline
I see.
But is there a way to tell if the t55xx is in password mode (e.g. analyzing the graph) besides trying to tag write failure?
What is the best offset value to use and how to calculate it?
Thanks so much for your help iceman!
Last edited by DingYao (2015-06-03 16:13:08)
Offline
yes, look at the config block there is a nice "lf t55xx info" command too
Offline
... The config block is not readable when it is in password mode unless you use the password with the read command
Offline
To see if a tag is in password mode (without having the password), on my t55x7 tags the data plot looks like "static noise"
If you can't sniff the tag / reader and figuring out the password, you might have to test default pwds like
0x00000000
0xFFFFFFFFF
There is these two known passwords.
Known cloner passwords:
0x51243648
0x000D8787
Last edited by iceman (2015-06-03 17:32:11)
Offline
I have experimented with the tag. From the looks of the data plot it isn't static noise, nor did I write it with a password hence it is unlikely to be password protected. However, the tag still does not respond to write commands.
I've tried setting the config to ASK modulation and played around with the bit rates but to no avail. I get erronous data from the tag (all 7 blocks are the same).
Is it possible that the tag has been permenantly locked? If not, perhaps this is a Q5 tag and not a t5557 tag..
Offline
Make sure there is little around the pm3 and antenna/tag while sending the write. I've noticed the t5xxx is very sensitive to electromagnetic interference.
Offline
The t5557 is very old and wasn't tested with the new t55xx commands. It is possible it suffers from the same issues the q5 is right now. I am working to fix the q5 issue.
Offline
actually, I just call my tags for t55x7, but I don't know exactly which model they are.
I usually need some space between my tag and lf antenna. 1cm?
but when I have the right config settings for the tag, it works perfect. (with my timings, )
Offline