Proxmark3 community

Ghost

Contributor

Registered: 2017-07-11

Posts: 7

[solved] Trouble with chk

I read wiki but i didnt find any information about my trouble. I use command

hf mf chk *1 ? t

Answer:

No key specified, trying default keys
key[ 0] ffffffffffff
key[ 1] 000000000000
key[ 2] a0a1a2a3a4a5
key[ 3] b0b1b2b3b4b5
key[ 4] aabbccddeeff
key[ 5] 4d3a99c351dd
key[ 6] 1a982c7e459a
key[ 7] d3f7d3f7d3f7
key[ 8] 714c5c886e97
key[ 9] 587ee5f9350f
key[10] a0478cc39091
key[11] 533cb6c723f6
key[12] 8fd0a4f256e9

Time in checkkeys: 1600 ticks 2 seconds

testing to read key B...
|---|----------------|---|----------------|---|
|sec|key A           |res|key B           |res|
|---|----------------|---|----------------|---|
|000|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|001|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|002|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|003|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|004|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|005|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|006|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|007|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|008|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|009|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|010|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|011|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|012|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|013|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|014|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|015|  ffffffffffff  | 0 |  ffffffffffff  | 0 |
|---|----------------|---|----------------|---|
Found keys have been transferred to the emulator memory

But i know that my card has key a0a1a2a3a4a5 in 0 block as key A. So why do i see this result?
p.s. Which argument should me use if i want to write key after checking into .dic file?

Last edited by Ghost (2017-07-17 10:47:22)

dontlook

Contributor

Registered: 2017-01-28

Posts: 57

Email

Re: [solved] Trouble with chk

Can you post the output of

hf mf rdbl 0 A a0a1a2a3a4a5

Copy the default_keys.dic which is in the client dir to a different file name and see if specifying that file helps after t

iceman

Administrator

Registered: 2013-04-25

Posts: 9,468

Website

Re: [solved] Trouble with chk

if topic was solved,   I suggest to @OP that you edit your first post and add prefix  [solved] to your subject line.  And post what your solution was.

Ghost

Contributor

Registered: 2017-07-11

Posts: 7

Re: [solved] Trouble with chk

The problem was with the conflict between new os and old fpga image. When fpga was updated problem was solved.
How it works now:

proxmark3> hf mf chk *1 ? t
No key specified, trying default keys          
chk default key[ 0] ffffffffffff          
chk default key[ 1] 000000000000          
chk default key[ 2] a0a1a2a3a4a5          
chk default key[ 3] b0b1b2b3b4b5          
chk default key[ 4] aabbccddeeff          
chk default key[ 5] 4d3a99c351dd          
chk default key[ 6] 1a982c7e459a          
chk default key[ 7] d3f7d3f7d3f7          
chk default key[ 8] 714c5c886e97          
chk default key[ 9] 587ee5f9350f          
chk default key[10] a0478cc39091          
chk default key[11] 533cb6c723f6          
chk default key[12] 8fd0a4f256e9          
--sector: 0, block:  3, key type:A, key count:13           
Found valid key:[a0a1a2a3a4a5]          
--sector: 1, block:  7, key type:A, key count:13           
--sector: 2, block: 11, key type:A, key count:13           
Found valid key:[ffffffffffff]          
--sector: 3, block: 15, key type:A, key count:13           
--sector: 4, block: 19, key type:A, key count:13           
Found valid key:[a0a1a2a3a4a5]          
--sector: 5, block: 23, key type:A, key count:13           
--sector: 6, block: 27, key type:A, key count:13           
--sector: 7, block: 31, key type:A, key count:13           
Found valid key:[ffffffffffff]          
--sector: 8, block: 35, key type:A, key count:13           
--sector: 9, block: 39, key type:A, key count:13           
--sector:10, block: 43, key type:A, key count:13           
Found valid key:[ffffffffffff]          
--sector:11, block: 47, key type:A, key count:13           
--sector:12, block: 51, key type:A, key count:13           
--sector:13, block: 55, key type:A, key count:13           
--sector:14, block: 59, key type:A, key count:13           
--sector:15, block: 63, key type:A, key count:13           
Found valid key:[a0a1a2a3a4a5]          
--sector: 0, block:  3, key type:B, key count:13           
--sector: 1, block:  7, key type:B, key count:13           
--sector: 2, block: 11, key type:B, key count:13           
Found valid key:[ffffffffffff]          
--sector: 3, block: 15, key type:B, key count:13           
--sector: 4, block: 19, key type:B, key count:13           
--sector: 5, block: 23, key type:B, key count:13           
--sector: 6, block: 27, key type:B, key count:13           
--sector: 7, block: 31, key type:B, key count:13           
Found valid key:[ffffffffffff]          
--sector: 8, block: 35, key type:B, key count:13           
--sector: 9, block: 39, key type:B, key count:13           
--sector:10, block: 43, key type:B, key count:13           
Found valid key:[ffffffffffff]          
--sector:11, block: 47, key type:B, key count:13           
--sector:12, block: 51, key type:B, key count:13           
--sector:13, block: 55, key type:B, key count:13           
--sector:14, block: 59, key type:B, key count:13           
--sector:15, block: 63, key type:B, key count:13           
Found keys have been transferred to the emulator memory  

Last edited by Ghost (2017-07-17 10:56:08)