{"action":"opened","issue":{"url":"https://api.github.com/repos/ikarus23/MifareClassicTool/issues/66","labels_url":"https://api.github.com/repos/ikarus23/MifareClassicTool/issues/66/labels{/name}","comments_url":"https://api.github.com/repos/ikarus23/MifareClassicTool/issues/66/comments","events_url":"https://api.github.com/repos/ikarus23/MifareClassicTool/issues/66/events","html_url":"https://github.com/ikarus23/MifareClassicTool/issues/66","id":93810690,"number":66,"title":"Key 000000000000","user":{"login":"alfs","id":1869479,"avatar_url":"https://avatars.githubusercontent.com/u/1869479?v=3","gravatar_id":"","url":"https://api.github.com/users/alfs","html_url":"https://github.com/alfs","followers_url":"https://api.github.com/users/alfs/followers","following_url":"https://api.github.com/users/alfs/following{/other_user}","gists_url":"https://api.github.com/users/alfs/gists{/gist_id}","starred_url":"https://api.github.com/users/alfs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alfs/subscriptions","organizations_url":"https://api.github.com/users/alfs/orgs","repos_url":"https://api.github.com/users/alfs/repos","events_url":"https://api.github.com/users/alfs/events{/privacy}","received_events_url":"https://api.github.com/users/alfs/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-07-08T14:55:59Z","updated_at":"2015-07-08T14:55:59Z","closed_at":null,"body":"There's something strange with key 000000000000, probably in relation to specific phone models (I'm using a Z3 Compact, which works fine otherwise with regards to mifare operations).\r\n\r\nI have a factory new, standard mifare 1k tag, with default access conditions (all F's.).\r\nIt can be read with a keyfile consisting of two keys:\r\nFFFFFFFFFFFF\r\n000000000000\r\n\r\nHowever if I reverse the keys:\r\n000000000000\r\nFFFFFFFFFFFF\r\n\r\nthen MCT now reports the key as being 0s, not Fs.\r\nIf swap the last digit from a 0 to a 1, then the F key is found correctly.\r\n\r\nEven more strange:\r\n\r\nI saved a dump of a reading with 0 keys, and write it back to the card, i.e., access key is 000000000000 for A and B for all sectors. Now I cannot read it back (no valid keys found). So I try changing the order in the keyfile (first F, then 0), some other variants, no luck, card cannot be read.\r\n\r\nUsing another phone, same MCT version, the card can be read using key 0, then reprogrammed using key F, and then read by the first phone again.\r\n\r\nMCT version 2.0.4, first phone is Xperia Z3 Compact, Android 5.0.2 (21.1.A.1.28) which had problems.\r\n\r\nWorking phone was MCT 2.0.4, Samsung Galaxy S3 (i9300), Android 4.4.4 (CM11-M12) which worked OK.\r\n\r\nIt would be interesting to hear if other Z3/Z3C users experience the same. Simple test is to just use a keyfile with 0's, and try reading a card programmed with F-keys.\r\n"}}