I missed something.
If you choose "Write Block" and go for sector 0 and block 0, MCT asks you whether you know what you are doing and if you want to proceed.
In this case the data on the card is updated.
However, I tried to copy a whole card and went for the "Write Dump (Clone)" option. In this case, it does not update sector 0, block 0 unless you explicitly go to options and choose "Advanced: Enable writing to manufacturer block". Without choosing this option, MCT still tells you that it succeeded but just did not mess with sector 0, block 0.
Happy end.
Frustrating at first but it made me update my Proxmark3 to the new firmware and it made me learn more about its options and especially the sniffing function.
Thanks iceman and IKARUS for the tools and the support!
ImSchatten360
]]>proxmark3> hf mf rdbl 0 a ffffffffffff
--block no:0, key type:A, key:ff ff ff ff ff ff
#db# READ BLOCK FINISHED
isOk:01 data:11 22 33 44 44 88 04 00 00 00 00 00 00 00 00 00
It is also recognized by MCT.
What I observed is that sometimes the proxmark3 has trouble communicating with the tag(s). Then I need to repeat the operation until I do not obtain any errors ("#db# Cmd CRC response error.", "#db# Can't select card", "#db# Auth error ", ...).
Example:
proxmark3> hf mf rdbl 0 a ffffffffffff
--block no:0, key type:A, key:ff ff ff ff ff ff
#db# READ BLOCK FINISHED
isOk:01 data:11 22 33 44 44 88 04 00 00 00 00 00 00 00 00 00
proxmark3> hf mf rdbl 0 a ffffffffffff
--block no:0, key type:A, key:ff ff ff ff ff ff
#db# Authentication failed. Card timeout.
#db# Auth error
#db# READ BLOCK FINISHED
isOk:00
proxmark3> hf mf rdbl 0 a ffffffffffff
--block no:0, key type:A, key:ff ff ff ff ff ff
#db# Can't select card
#db# READ BLOCK FINISHED
isOk:00
proxmark3> hf mf rdbl 0 a ffffffffffff
--block no:0, key type:A, key:ff ff ff ff ff ff
#db# Multiple tags detected. Collision after Bit 1
#db# Can't select card
#db# READ BLOCK FINISHED
isOk:00
proxmark3> hf mf rdbl 0 a ffffffffffff
--block no:0, key type:A, key:ff ff ff ff ff ff
#db# Can't select card
#db# READ BLOCK FINISHED
isOk:00
proxmark3> hf mf rdbl 0 a ffffffffffff
--block no:0, key type:A, key:ff ff ff ff ff ff
#db# Auth error
#db# READ BLOCK FINISHED
isOk:00
proxmark3> hf mf rdbl 0 a ffffffffffff
--block no:0, key type:A, key:ff ff ff ff ff ff
#db# Auth error
#db# READ BLOCK FINISHED
isOk:00
proxmark3> hf mf rdbl 0 a ffffffffffff
--block no:0, key type:A, key:ff ff ff ff ff ff
#db# READ BLOCK FINISHED
isOk:01 data:11 22 33 44 44 88 04 00 00 00 00 00 00 00 00 00
Maybe the tags in general are not performing well?
However, MCT always seems to be able to easily handle them, except for the writing to block 0 part.
It is a little unfortunate that MCT confirms the writing attempt as successful without reading the content of the tag again. At least this seems to happen.
In addition, I am still not sure why a "hf mf wrbl" is successful and an attempt with MCT is not. I would like to understand how both procedures differ. I am really not yet familiar with how the procedures are implemented.
An invite for you https://discord.gg/cfNvV5
]]>I have bunch of tags that are identified by the proxmark3 as following:
proxmark3> hf search
UID : 11 22 33 44
ATQA : 00 04
SAK : 03 [2]
proprietary non iso14443-4 card found, RATS not supported
No chinese magic backdoor command detected
Prng detection: WEAK
Valid ISO14443A Tag Found - Quiting Search
As far as I am aware, these are Gen2 tags. They used to have some "random" UID and I changed it with the following command:
hf mf wrbl 0 A FFFFFFFFFFFF 11223344448804000000000000000000
However, if I try to change block 0 or just the UID + BCC with MCT on my Android Sony Xperia XZ1 Compact, it tells me, that the writing was successful but the block content does not change. Nevertheless, I can write information to all other blocks and sectors.
Does anyone know why this is the case?
Shouldn't I be able to use MCT if I can write to the cards via "hf mf wrbl"?
Are there additional requirements to use cards with MCT?
Regards,
ImSchatten360
]]>