Proxmark developers community

Research, development and trades concerning the powerful Proxmark3 device!

You are not logged in.

#1 Re: Proxmark Board Innovations » Latest PM3 from China » Today 00:11:21

THe jtag connector is no more present; is there a way to connect jtag to it ?

#2 Re: iClass » iClass is coming... » Today 00:07:31

All the good people here do what they do for passion not for money/fraud.
I ask the moderators to remove such posts and preferably perma-ban people posting/requesting those kind of stuff without any warning.

#3 Re: MIFARE Classic » A popular toy, Disney Infinity » 2015-04-22 22:04:07

And this (i think he is the same guy):

#4 Re: MIFARE Classic » A popular toy, Disney Infinity » 2015-04-22 21:58:22

Another very interesting link:

#5 Re: MIFARE Classic » A popular toy, Disney Infinity » 2015-04-22 21:50:22

It is a Logic3 device [VID:0E6F], it should work for what forum users say.
Try to contact the producer here:

#6 Re: Questions and Requests » Skidata tickets (iso 15693) » 2015-04-21 22:50:57

For what i know the feature you are looking for is not implemented yet in pm3.

#7 Re: MIFARE Classic » About U-key ... » 2015-04-21 08:42:37

Do not help people to fraud.

#8 Questions and Requests » Playing with JTAG » 2015-04-18 11:17:10

Replies: 0

Just received a JTAG (probably clone); used SEGGER J-Flash ARM V4.50 version.

I followed the following steps:

01 - Plugged the Proxmark and the Segger J-LINK in to the computer
02 - Attached the J-LINK to the Proxmark JTAG port
03 - Opened J-Flash ARM V4.50 software
04 - Created a new project by selecting File > New project
05 - Changed the project settings by going to Options > Project settings
06 - Clicked on the Target Interface tab
07 - Changed the "JTAG speed before init" to 200 kHz
08 - Clicked on the CPU tab
09 - Selected the "Device" radio button and selected "Atmel AT91SAM7S256" from the drop-down list
10 - Changed the Clock speed to "Auto detection"
11 - Applyed the changes -> OK
12 - Tested connectivity to the Proxmark by selecting Target > Connect
13 - Target -> Read back -> Entire chip

I got the same dump as proxmark3_recovery.bin until offset 0x00032047 (in the SEGGER software interface the address is 0x132047)... what are the following dumped bytes (~56Kb) ? EEPROM bytes ?

#10 Re: MIFARE DESFire » Desfire uid magic card? » 2015-04-16 07:50:54

Icode2 is a generic definitio; it would be good to know the exact command set supported.

#11 Re: Questions and Requests » unknown hf tag » 2015-04-14 22:06:46

try to cut the chip out and insert it in a working card (soldering the 2 tips of the antenna): maybe the tag coil is damaged; if this is the case it will work again;

also try to put the surely-good chip in the bad-tag antenna and see if it is still working; if so you will be sure the bad-tag chip is  damaged.

To eliminate the plastic part of the card you can dissolve it in aceton - submerge it  and cover it to avoid evaporation - only the metal parts will remain [chip+antenna]

#12 Re: Questions and Requests » unknown hf tag » 2015-04-14 17:55:43

Or use this simple script to see if it is "magic" and if it writes block0:

hf 14a raw -p -a -b 7 40
hf 14a raw -p -a 43
hf 14a raw -c -p -a A000
hf 14a raw -c -p -a 01 02 03 04 04 98 02 00 00 00 00 00 00 00 10 01

#14 Re: MIFARE Classic » About U-key ... » 2015-04-13 14:05:13

Usually it is as you mentioned but this can change according to vendors; some vendors may have different keys in different locations. For that reason please do not public any key.

#15 Re: MIFARE Classic » A popular toy, Disney Infinity » 2015-04-13 14:03:30

The only different portal seems to be the xbox portal (different vid/pid).

#16 Re: MIFARE Classic » About U-key ... » 2015-04-13 13:46:48

The keys are usually vendor-specific (same keys for the same vendor).

#18 Re: Trade Parts » group buy for proxmark3 » 2015-04-13 12:50:02

This group buy ended; if a new one will appear it will be in another thread.

#19 Re: MIFARE Classic » About U-key ... » 2015-04-13 09:31:08

The pre-built antennas you can buy are far bigger than the u-key slot hole so the answer is no.
You need to build&tune a very small antenna yourself (maybe re-using the u-key pre-built one?) and adapt it for pm3.

#20 Re: MIFARE Classic » idea: identify "weak" mifare classic tags. » 2015-04-12 14:54:25

I agree with iceman! This will be a good feature feasible reusing existing code!!

#21 Re: MIFARE Classic » A popular toy, Disney Infinity » 2015-04-10 15:07:39

Can you test a sniff key decoding attack and see if it works?

#22 Re: Questions and Requests » ATS proximity cards » 2015-04-09 08:32:41

You have to look at a 125kHz tag with 4bytes password feature and a ROM-programmed UID of "4-billion combinations" (it should be a 32bit UID). The possibilities, to my knowlwdge, are very limited and they point out to T55x7 or AT88RF256 chips (I am inclined to think about the T55x7 because of the limited user area available bytes [the unknownk tag above tech specs says "4 user memory areas"] and the because they are more common).

#23 Re: 125 kHz - ISO 11784 / 11785 » new lf commands summary » 2015-04-09 08:15:26

So "biphaserawdecode" command will become "biphrawdecode" ?

#24 Re: 125 kHz - ISO 11784 / 11785 » PCF Modulation » 2015-04-08 13:07:40

iZsh wrote:

I rewrote this code long time ago and actually implemented the programming mode. Unfortunately I never got the time to actually commit it (this is the blog post part3 I said I was going to write long time ago on f0f's blog). Maybe this summer, hopefully ;-)

BTW, as a side comment, the programming mode for the PCF IC doesn't actually really work properly/reliably with the proxmark because the antenna signal is weak, and the pulse length is limited by the hardware design. It is therefore near impossible to have short sharp pulses as required by the programming mode for the PCF.

I'll let you know once I have time to commit the code and write this damn blog post part3

Thank you for your previous work iZsh ! It will be great to have your code updated !!

Board footer

Powered by FluxBB