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.
Pages: 1
Happy new year!
I recently cloned an awid tag on a " Dual Chip Frequency RFID 13.56Mhz 1K UID and EM4305 or t5577 125 kHz ID key tag". I am trying to rewrite the lf data on the tag. I am using data I got from a HID tag.
I ran the proxmark command to wipe the tag and then ran the hid clone command. The data on the tag is not saving the new hid tag info. It still has the awid tag info.
Any idea as to why I can't overwrite the tag with new info? are there certain tags that can only be written to once?
I am using the proxmark easy 3
Last edited by addy (2017-01-06 18:44:06)
Offline
Which commands did you run when you wiped it?
What is your output from these cmds?
lf search
lf t55 detect
lf t55 info
lf t55 dump
Offline
What did you use to clone the tag originally? The pm3 or another device?
Offline
Hi Iceman,
Here are my results
proxmark3> lf search
Reading 30000 bytes from device memory
Data 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 possible
Checking for known tags:
AWID Found - BitLength: 50 -unknown BitLength- (13790) - Wiegand: 1f4000506xxx, Raw: 0128817e4111124174xxxxxx
Valid AWID ID Found!
proxmark3> lf t55 detect
Could not detect modulation automatically. Try setting it manually with 'lf t55xx config'
proxmark3> lf t55xx config
Chip Type : T55x7
Modulation : ASK
Bit Rate : 0 - RF/8
Inverted : No
Offset : 0
Seq. Term. : No
Block0 : 0x00000000
proxmark3> lf t55xx info
proxmark3> lf t55xx dump
Reading Page 0:
blk | hex data | binary
----+----------+---------------------------------
Reading Page 1:
blk | hex data | binary
----+----------+---------------------------------
proxmark3>
Offline
What did you use to clone the tag originally? The pm3 or another device?
Used the same device proxmark 3 easy
Offline
Other strange behavior:
- When I clone a HID card to either the keyring tags or a card tag I can erase and rewrite it.
- When I clone an ioprox or awid tag to a keyring tag or a card tag I can not erase or overwrite it.
What am I doing wrong? Seems so strange to me.
Offline
solved...
I downgraded the flash and used the pm3-bin-2.5.0 version of proxmark. Everything worked out fine. This was the version I used originally to clone the tag.
The version I was using, with the errors wiping the previously written tags, was 20161219-910ad5470d913baeaf9d882a22fc1b853318a5da . zip
Prox/RFID mark3 RFID instrument
bootrom: /-suspect 2015-11-19 10:08:02
os: /-suspect 2015-11-19 10:08:09
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at 9: 8: 8
uC: AT91SAM7S256 Rev C
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes. Used: 169916 bytes (65%). Free: 92228 bytes (35%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
Offline
Great that you solved yr issue. Still raises the Q if something is fishy in current PM3 master with Awid/t55x7 imp.
I suggest you edit yr first post and add "[solved]" at the beginning of yr subject.
Offline
Having this same issue trying to rewrite a t55xx bracelet that i had previously written an hid copy to.
Even after multiple wipes (t55xx likes to take a few tries) running lf search still shows it as an hid.
All the screenshots from OP are exactly what i'm getting.
Using PM3 latest releases from iceman and regular, updated device manager with driver from each package and flashed bootrom and fullimage. The t55xx tags are the black wristband t5577 from yarongtech off of amazon.
Downloading the old pm3bin2.5.0 to try it out.
p.s. wanted to do a new post, but the issue is too similiar to what i'm getting and while it was solved for the OP there wasn't much of a solution provided for others.
Last edited by a2d (2018-06-28 16:40:39)
Offline
Pages: 1