Proxmark3 community
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.
Announcement
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.
Pages: 1
#1 2013-08-26 14:40:12
- john67
- Member
- Registered: 2013-07-18
- Posts: 9
Problem wrbl #db# Cmd Error 4
If I try to write a block I get the following error:
http://www.4shared.com/photo/6XgCmOWj/Img_r_w_2.html
#db# Cmd Error 4
Can you help me?
Offline
#2 2013-08-26 16:33:10
- piwi
- Contributor
- Registered: 2013-06-04
- Posts: 704
Re: Problem wrbl #db# Cmd Error 4
Access conditions don't allow write access to this block?
Offline
#3 2013-08-26 20:50:06
- john67
- Member
- Registered: 2013-07-18
- Posts: 9
Re: Problem wrbl #db# Cmd Error 4
I possess the key to read the block, but when I write it generates the error:#db# Cmd ERROR 4.
What generates the "Cmd Error 4"?
Offline
#4 2013-08-27 16:11:39
- ikarus
- Contributor
- Registered: 2012-09-20
- Posts: 249
- Website
Re: Problem wrbl #db# Cmd Error 4
I don't know what error 4 is, but I think piwi might be right.
The read-key is often different from the key with the write privileges.
Try to read block 11 and use this tool to check what key has what privileges.
But if you really need to know what error 4 is, I think you have to take a look into the code...
Offline
#5 2014-08-03 04:12:17
- ale88
- Contributor
- Registered: 2014-04-13
- Posts: 10
Re: Problem wrbl #db# Cmd Error 4
Hello, I have the same problem. How did you solve this???
Regards...
Offline
#6 2014-08-03 09:16:41
- piwi
- Contributor
- Registered: 2013-06-04
- Posts: 704
Re: Problem wrbl #db# Cmd Error 4
Cmd Error: 04 means that the card has responded with 0x04 to the writeblock command. 0x04 is "NACK" (Not Acknowledged), i.e. the card didn't accept the writeblock command. Most probable reason are Access Conditions which don't allow writing to the specified block with the (successfully authenticated) key.
Offline
#7 2014-08-03 17:35:22
- ale88
- Contributor
- Registered: 2014-04-13
- Posts: 10
Re: Problem wrbl #db# Cmd Error 4
Cmd Error: 04 means that the card has responded with 0x04 to the writeblock command. 0x04 is "NACK" (Not Acknowledged), i.e. the card didn't accept the writeblock command. Most probable reason are Access Conditions which don't allow writing to the specified block with the (successfully authenticated) key.
Thanks piwi!
I tried to write several blocks of different sectors and the error says:
proxmark3> hf mf wrbl 1 A 7b296f353c6b 43FFFF7FBD00008042FFFF7F00FF00FF
--block no:01 key type:00 key:7b 29 6f 35 3c 6b
--data: 43 ff ff 7f bd 00 00 80 42 ff ff 7f 00 ff 00 ff
#db# Cmd Error: 04
#db# Write block error
#db# WRITE BLOCK FINISHED
-------------------------------------
hf mf wrbl 5 A 668737F0EB0A 08ACDEC8984107EDDC8210F24D1914A9
--block no:05 key type:00 key:66 87 37 f0 eb 0a
--data: 08 ac de c8 98 41 07 ed dc 82 10 f2 4d 19 14 a9
#db# Cmd Error: 04
#db# Write block error
#db# WRITE BLOCK FINISHED
--------------------------------------
The key is correct!
The card is a NXP MIFARE CLASSIC 1k | 2k Plus SL1. The card isn't empty and I want to modify some bocks.
Access conditions don't allow write access to all blocks. What can I do?
Sorry for my English.
Regards...
Offline
Pages: 1