MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

mercutio · 2013-11-22 13:49:21

Here is the dump of the sector 0 of my tag :
+Sector: 0
9848044094080400B946B92011051984
00000000000000000000000000000000
00000000000000000000000000000000
FFFFFFFFFFFFFF078069FFFFFFFFFFFF

This is what I did :
-I edited the dump like this
+Sector: 0
5B07000094080400B946B92011051984
00000000000000000000000000000000
00000000000000000000000000000000
FFFFFFFFFFFFFF078069FFFFFFFFFFFF
-saved the dump
-write dump with option : enable writing to manufacturer block.
Not working.

I tried to write only block0 sector 0, not working too.

I contact the seller and here is his answer :
"What's the writer you use? the writer need can write UID card,thanks"

ikarus · 2013-11-22 17:27:40

What you did was right. No mistakes there.
The description of this app states

Block 0 writable Cards seem to be buggy. If the card uses the default key (FFFFFFFFFFFF)
in Block 0 and an error is thrown, try again until it works (it might take more than 5 tries).

I don't know if this is right, but you can at least try it...

The statement of the seller is strange. The description of the cards clearly say
"normal mifare read-write device modification" and "don't need special equipment".
If this is the case the card should work. I own such a card and I'm able to write block 0.
Maybe the seller sold you a card of a differed kind (UID changeable with special commands)
and messed up the description?! Or the card is that buggy that it only works for some readers?!

I hope you will find out what is causing this issue, but unfortunately I can't tell you.
Do you own another (USB) reader? Or a Proxmark3? You could try if these devices will work and
you could try if the "special UID change command" will work...

mercutio · 2013-11-23 11:13:57

Unfortunately I don't own a usb writer, (but I'm starting to think about buying one since I spent allmost 50$ of not working UID writable tags).

Here is what I said to the seller and his answer :

ME :
"I m using my smartphone with a nxp nfc chip in it.
With an android app (mifare classic tool) that is able to write block0 sector 0.
I choose your card because the app developers told me taht it was this kind card ( with no speciak command needed) that his app was able to write uid."

Seller :
"Good day!
NFC phone can not write UID card, you need professional writer,thanks!
If you need the writer,pls tell me,thanks!
Best regards"

asper · 2013-11-23 14:30:08

The answer he gave you is true only if it is a special changeable uid card (special commands needed); in that case the card description is not correct; ikarus app makes an nfc capable phone (with nxp chip inside, not broadcom ones) behaving just like a "professional" reader/writer. In my opinion you should ask your money back!

Last edited by asper (2013-11-23 14:32:09)

ikarus · 2013-11-24 13:59:30

I'm 100% with asper on this. A NFC enabled mobile phone is a "professional" reader.
And I think too that you should ask your money back.

Last edited by ikarus (2013-11-24 13:59:48)

ikarus · 2013-12-24 12:55:23

New release! (Version 1.7.0: APK-file, Google Play)
(See: original post, updated)

* New Feature: Write only the sectors you want to be written
(when using the Write Dump functionality).
* Added a new standard key file (extended-std.keys).
Most of its keys were taken from SLURP by Anders Sundman
(https://github.com/4ZM/slurp).
* Fixed broken sector status (Write Dump).
A sector status is either "no keys found" or "dead".
* Fixed the MCT dump to proxmark3 emulator tool.
* Some code improvements & cleanup.
* Some minor bug fixes.
* Fixed some spelling (thanks to 'systemcrash').
* Updated support list.
Googles Nexus 5 does not support Mifare Classic.

Regarding the new feature: this is what it looks like.

Marry Christmas
ikarus

ikarus · 2014-01-07 13:43:33

New release! (Version 1.7.1: APK-file, Google Play)
(See: original post, updated)

Version 1.7.1:
* Tried to fix the strange crash which occurs sometimes when starting
the key mapper. I don't know why

If you are one of these unlucky people who encounter this strange crash/error, please say so.
I would like to hunt this bug down, but I can't find a way to reproduce it on my phone.

Kind regards,
ikarus

Last edited by ikarus (2014-01-07 13:44:07)

slb · 2014-01-08 10:01:04

Hi ikarus,

I read some web pages talking about the emulation of Mifare Classic support for Nexus 5 ( or other device with a non built in compatible nfc chip ). Based on a modified rom or a pure app emulation ( but requiring rooted device ) . Maybe it's interesting to check it out.

Also it's interesting my nexus 5 with no Mifare Classic support can read a Mifare Classic 1K partially, so app emulation support can be interesting imo.

ikarus · 2014-01-08 13:00:36

Hi slb,

that sounds indeed really interesting!
Can you provide me with some links?

Your Nexus 5 can partially "read" Mifare Classic because the
tag selection phase (anti collision, UID, etc.) is ISO 14443 compliant
(ISO 14443 tags are supported by Android).
The rest however (authenticating/reading/writing), is proprietary.

xtay004 · 2014-01-10 06:21:24

hi~
when i read nxp smartMX card ( P5CT072 ) key mapping cannot continue！taginfo can do it
maybe you can find why crash occurs
MifareClassicTool 1.7.1

xtay004 · 2014-01-10 06:43:50

part of P5CT072 pdf：
In confguration B1 the contactless MIFARE Classic OS provided by Philips is implemented on the P5CT072. 1 Kbyte of the EEPROM can be accessed by the MIFARE Classic OS offering the same command set and functionality as a MIFARE 1K hardwired logic chip. The access conditions for the user OS to the MIFARE memory area can be confgured via the so called ACM (Access condition matrix). The MIFARE Classic OS offers a backward compatibility to support existing infrastructure based on the MIFARE Classic functionality.

xtay004 · 2014-01-13 08:27:05

I found out that use the right key mifare classic can read/wirte this tag sectors one by one
maybe security mechanism cause this happen

ikarus · 2014-01-19 21:21:26

Just for the record:
With xtray004s help I was able to develop a fix.

The next version will have a preference view to turn on/off this fix.
(I don't want to make this behaviour the default because it might lead to
unexpected behaviour on non emulated Mifare Classic tags.)

For the full discussion see: https://github.com/ikarus23/MifareClassicTool/issues/11

Last edited by ikarus (2014-01-19 21:21:50)

ikarus · 2014-01-26 14:14:48

New release! (Version 1.7.2: APK-file, Google Play, F-Droid)
(See: original post, updated)

* New Feature: Display the date of manufacture.
* Added preference system.
* Added a preference for auto reconnection if tag gets lost during the
key mapping process. (Maybe useful if you encounter issues during
this phase. Thanks to xtay004.)
* Added a "about" dialog (including useful links).
* Show error message if tag gets lost during key mapping.
* Some minor bug fixes.

Regarding the new feature: this is what it looks like.
Thanks to asper for pointing out that the last two bytes of block 0 are most likely the date of manufacture.

And I almost forgot to mention: MCT is now available via F-Droid.

Kind regards,
ikarus

asper · 2014-01-26 16:00:12

Great work (as always!) man !

I have a problem reading Magic Chinese Changeable UID mifare cards (1st generation = special commands needed to write block0);
when I try to read the card automatically using standard+extended key files the app try to read blocks grater than 15, that obviously are not present in the card, until block 39:

I don't know what can be the problem... maybe the app recognize the tag other than mifare 1k ?

Topic change: together with the date, another thing you can do to identify counterfait cards, is to verify byte4 of sector0block0 that must be the xor result of byte0+byte1+byte2+byte3 of the same block; if it is not it means the card is 99% counterfait.

EDIT:

So the app consider it a 4k...

Last edited by asper (2014-01-26 16:54:43)

ikarus · 2014-01-26 23:31:16

First of all: Thank you!

The problem you encounter is new to me. I never saw a 1k tag that was mistaken for a 4k tag. Unfortunately there is nothing
I can do (at least I think so). MCT uses the getSectorCount() (and getSize()) of the Android Mifare Classic API.
I can't tell whether it is Androids or your tags fault.

asper wrote:

together with the date, another thing you can do to identify counterfait cards, is to verify byte4 of sector0block0 that
must be the xor result of byte0+byte1+byte2+byte3 of the same block; if it is not it means the card is 99% counterfait.

Interesting. Is this still the case if the UID is 7 or 10 bytes long?

{0x776F6F74333332} · 2014-01-27 01:41:09

Nope 7 and 10 byte long uid byte 0 is to identify ic manufacturer 04h is NXP.
4 byte uid does not have manufacturer id but I think SAK and ATQA can be used.
Now cheking the bcc byte to dectect counterfeit cards should work, but from
what I understand bcc is recalculated when using csetuid right?.

ic list:
http://www.kartenbezogene-identifier.de/de/chiphersteller-kennungen.html

asper · 2014-01-27 09:29:53

{0x776F6F74333332} wrote:

Nope 7 and 10 byte long uid byte 0 is to identify ic manufacturer 04h is NXP.
4 byte uid does not have manufacturer id but I think SAK and ATQA can be used.
.....
ic list:
http://www.kartenbezogene-identifier.de/de/chiphersteller-kennungen.html

Yes woot332, it is stated here at page 6. And yes, ATQA+SAK can be used but it is not always correct.

On the contrary, in single sized UID tags byte0 is always used to detect what kind of tag it is:
08 = RID: UID1, UID2 and UID3 are dynamically generated during or after each Power-On-Reset (POR) --> random UID.
x0... x7 = Proprietary use (i.e. used for MIFARE)
18…78, 98…E8 = Proprietary use (i.e. used for MIFARE)
x9...xE = Proprietary use (i.e. used for MIFARE)
xF = Fixed number, non-unique
88 = Cascade Tag (more-than-4-bytes-UID)
F8 = RFU

This can be the problem of the "wrong recognizing" by your app, I will investigate this further !

Now cheking the bcc byte to dectect counterfeit cards should work, but from what I understand bcc is recalculated when using csetuid right?.

Never verified that because I don't have a MCT supported changeable UID tag; Ikarus can you confirm that your app will recalculate bcc in supported changeable UID tags ?

EDIT:
Here a good reading about single/double size UIDs.

Last edited by asper (2014-01-27 11:26:40)

ikarus · 2014-01-27 10:36:03

asper wrote:

Ikarus can you confirm that your app will recalculate bcc in supported changeable UID tags ?

No, MCT does not recalculate the bcc. But this is because of the tag type and the Android API:
- "2nd gen" tags (no special commands) are block 0 writable rather than UID changeable. You can writhe the whole
manufacturer block (including UID, bbc, date of manufacture, etc.).
- The Android API only offers a command to write block-wise. If I want to have a special "change UID" function
the app must first read block 0, replace the UID, recalculate and replace the bcc and write the whole block
back to the tag.
Until now you can only write block 0 like any other block (if you have a "2nd gen" tag).

Last edited by ikarus (2014-01-27 10:37:57)

asper · 2014-01-27 11:00:05

Thanks for the answer. Maybe you can add the option "automatic reaclculate bcc (byte4)" in "2nd gen" tags when writing UID in block0 so users are still free to change bytes as they want

About my previous problem I think that the problem is the UID0 byte; I don't have a Mifare 4k but reading dumps from google, 4k UID0s seem to be "x0... x7" while original 1ks seem to be "18…78, 98…E8" or "x9...xE"; can anyone with a 4k verify this please ? Anyway I will check when I will come back home.

{0x776F6F74333332} · 2014-01-27 14:32:43

asper wrote:

Thanks for the answer. Maybe you can add the option "automatic reaclculate bcc (byte4)" in "2nd gen" tags when writing UID in block0 so users are still free to change bytes as they want
About my previous problem I think that the problem is the UID0 byte; I don't have a Mifare 4k but reading dumps from google, 4k UID0s seem to be "x0... x7" while original 1ks seem to be "18…78, 98…E8" or "x9...xE"; can anyone with a 4k verify this please ? Anyway I will check when I will come back home.

Here you go UID0 byte 82h and B2h from original 1K, interesting but what about x9...xE, xF, 08
are these found in 1k cards?.

{0x776F6F74333332} · 2014-01-27 15:12:41

Also this has UID0 byte 14h and sak 88h maybe its 1k Infineon dump?.
I dont see any reference to UID0 14h in AN10927.pdf.

http://nfc-tools.org/images/9/9a/Empty_mfd_example.zip

asper · 2014-01-27 17:35:13

Well, the problem is not the UID0 but is ATQA+SAK because changing it to 08 04 00 or 88 04 00 makes the tag to be recognized as a mifare 1k; so MPCOS Gemplus is wrongly recognized as a Mifare 4k; I have a 0Eaabbccxx980200zzzzzzzz49603108 tag and it is a mifare 1k so there is a "bug" in Android.

EDIT:
Android also checks the bcc to be correct, if it is wrong the card is totally not recognzied (the same happens if you set ATQA+SAK to 00) so I think is a good idea to add an automatic bcc calculation in MCT

Anyway I was not able to find any datasheet about Gemplus MPCOS 1k...

Last edited by asper (2014-02-22 19:39:43)

{0x776F6F74333332} · 2014-01-27 21:02:02

Nevermind I got the rest of the documentation I was looking for.

epsilonandreas · 2014-02-22 16:38:01

In regards to writing to the manufacturer block, the documentation states I'll need a card that supports a simple write command.

Does "hf mf wrbl 0 a ..." count as a simple write command for this purpose?
I apologise for my lack of knowledge in this field.

asper · 2014-02-22 18:41:11

It should (anyway you cannot be 100% sure until you test it because there are tags that need special commands to be written in block0; blame the seller if this will be the case).

Last edited by asper (2014-02-22 19:39:09)

epsilonandreas · 2014-02-22 18:59:31

Alright. Thanks for the info.

ikarus · 2014-02-26 14:58:28

New release! (Version 1.7.3: APK-file, Google Play, F-Droid)
(See: original post, updated)

* Last used key files will be remembered.
(This behaviour can be switched off in the preference dialog.)
* Some minor bug fixes.

Kind regards,
ikarus

nn · 2014-03-05 00:17:08

Hi ikarus, I've got a question.
I accidentally factory formatted my Mifare Classic 1k tag using MCT. I created a dump of tag before formatting it and managed to restore sectors 1-15, but I can't restore sector 0. It has default FFFFFFFFFFFF keys now. Is there any way to restore previous keys for this sector using MCT? My tag without first sector is useless now...

ikarus · 2014-03-05 20:26:00

Hi nn,

can you post the original sector 0 (backup) and the sector 0 as it is now?
Have you checked the Access Conditions (in dump editor select "Decode Access Conditions" from the menu)?

nn · 2014-03-05 21:59:46

I finally did it by writing every block manually. Writing a clone of whole sector didn't work. I left block 0 (UID & Manufacturer info) unchanged and write blocks 1,2 and 3 (keys & access conditions) separately by "write block" option in MCT. Tag works like new

ikarus · 2014-03-05 23:26:09

Hmmm... this sounds mysterious...
If you could write the data of sector 0 block by block, then the write dump function should also work.
Maybe MCT has a bug there...

Can you provide me the data I asked for (see last post)?
You can anonymize/change the keys and content of blocks if you wish.

Also, can you tell me if there was any error message (using the write dump method)?
Did you enable the write to manufacturer block setting?

wous · 2014-03-07 14:33:06

Hi,

Is it possible to export a dump in a *.dump format so I can use it on my pc with Mifare offline cracker?

ikarus · 2014-03-07 21:38:00

Hi wous,

I think there is a misunderstanding. If you want to use "mfoc" the *.dump file you provide using the "-O" option
is not a file that gets read by mfoc, it is the file that gets written. After mfoc cracked the keys the whole card content
will be dumped in that file. mfoc can not crack keys using a dump. You need a reader connected to your PC.
And concerning the "-i" option of "mfcuk": As far as I know this will only load the dump for viewing/verification
reasons, not for cracking.

(And regarding MCT: you first need the keys, than you can create a dump of the card's content.
You can not create a dump without knowing at least one valid key.)

wous · 2014-03-08 14:18:40

Ah thanks, that clears a lot! I'm just trying to read what is on my card. And I saw some option in mfoc GUI to open a existing dump file.

MCT is a nice app by the way !

wous · 2014-03-13 16:16:14

I've just got my uid changeable mifare classic card.
http://www.ebay.com/itm/UID-Card-Changeable-Writable-Mifare-Classic-1k-S50-Compatible-/161219337827?pt=LH_DefaultDomain_0&hash=item25896bde63

I've read in the description "Proxmark3 "backdoor" (csetuid)" as UID Modification Method. Is this possible in MCT? My galaxy S3 gives an error when I try to write a dump from another card.

ikarus · 2014-03-14 13:11:23

Sorry to say so, but the "csetuid" backdoored are the wrong ones. They will not work.
You have to buy a tag that allow you to write to block 0 with a normal Mifare Classic command (no fancy csetuid).

Last edited by ikarus (2014-03-14 13:12:14)

asper · 2014-03-14 13:16:42

MCT does not support "backdoor" feature, only common mifare write commands;
there are 2 kind of UID rewritable tags:

- backdoored ones (old)
and
- "normal commands" ones (new)

no UID rewritable tags support both (backdoor+normal command = THOSE TAGS DO NOT EXISTs) so you have to choose/find/buy the "normal commands" one in order for it to work with MCT; if you have the backdoor one you need hardware like proxmark3 to change UID as it is CLEARLY stated in the product specifications:

Last edited by asper (2014-03-14 13:19:32)

ikarus · 2014-03-14 13:41:27

@asper: Thanks for the clarification. People continuously mix up this two versions.

@all:
Note that descriptions to such tags are not always that clear.
For example http://www.aliexpress.com/item/Free-Shi … 44863.html
In the description you can read

block 0 directly with normal IC read-write device modification, don't need special equipment.

which contradicts with

Note:Common IC reader writer cannot write UID card!!

(from the same description).

So take your time, read everything, compare descriptions, read feedback (e.g. this), etc.

asper · 2014-03-14 14:08:55

You are welcome ikarus... I think you should write a kind of "disclaimer" about those changeable UID cards in the 1st post...

wous · 2014-03-14 21:34:09

Excuse me for the question. Im still new in the RFID tech. I've read that description you posted and that's why my question came. I had a little hope of being able to use Proxmark software on an Android phone. Thanks for the explanation though!

I'm about to buy a NFC reader I guess

asper · 2014-03-14 21:50:26

Proxmark software for Android (proxdroid) works ONLY with a proxmark3 hardware connected to the Android phone!

TheJuice · 2014-03-20 11:07:09

Hi,
I understand that your program can only use MIFARE Classic 1K.
I have cards that are Infineon MIFARE Classic 1K (00 04 88), and they are not recognized as being compatible with the program...

What are the differences between Infineon type and the other one ?
Any chance compatibility could be added ? After all, this is still a MIFARE Classic 1K...

Thanks and keep up the good work.

asper · 2014-03-20 11:59:54

NXP and Infineon mifare are the same product manufactured by different producers so if your mobile phone has the NXP chip inside (not the broadcom one) it will be able to read both of them. Unfortunately there is no way to know which NFC chip you have inside except to try to read a mifare card ! (or to dismantle your mobile phone!!) UID can be always retreived by NXP or broadcom chips because it is part of the ISO14443A standard but auth command ncessary to read/write mifare are not part of the ISO14443A standard so you can't read/write those tags if you don't have an NXP chip inside. Summing it up you porbably have a mobile phone with boradcom chip inside (ex. Samsung Galaxy S4, while Galaxy S3 has NXP).

TheJuice · 2014-03-20 12:27:30

Thanks for your reply.
I bought a phone (LG G2), looking for a compatible chip with the help of following page : http://www.nfc-phones.org/summary-list-of-all-available-nfc-phones/
And I just went back to the page while writing this post... Just to see that I have wrongly thought all along that my mobile had an NXP chip :-(((
The lack of compatibility was one of the reasons I did not buy the Nexus 5, and in the end I bought another phone with the same chip.

So my mistake, now I understand why it is not working and that there's nothing I can do about it :-(

asper · 2014-03-20 12:52:16

I am sorry man; maybe this other link will help someone else looking for a mifare-capable nfc mobile phone.

ikarus · 2014-03-20 14:26:17

TheJuice wrote:

keep up the good work

Thanks!

And I'm sorry too for your mispurchase!

I updated the device compatibility list and blacklisted the devices from the article in Google Play (thx asper).
(Maybe this is why I get more 1-star ratings on Google Play lately...)
I did not know that there are that much NFC enabled devices without Mifare Classic support.

Last edited by ikarus (2014-03-20 14:28:33)

asper · 2014-03-20 17:56:02

You are welcome ikarus; it seems to be that new nfc mobile phones adopted broadcom chipset to support nfc android new wallet system/feature so i think that mifare will not be supported anymore except for a maybe-new-broadcom-product chip that will support them both (like the one inside the new WiiU Game Pad but not confirmed yet because no official datasheet available).

Last edited by asper (2014-03-20 17:57:37)

asper · 2014-03-20 22:07:45

Please have also a look at here.

wous · 2014-03-26 13:32:19

Hi,
I've bought the ACR122u and succesfully changed the UID of the card with libnfc. The card I want to clone is broken but I dumped it to my phone with MCT.
When I try to write the dump to the UID changed card, the keys don't change. They stay at FFFFFFFF as a default value. Can MCT clone, together with changing the keys? Or is there an alternative way to do this?

Proxmark3 community

Announcement

#151 2013-11-22 13:49:21

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#152 2013-11-22 17:27:40

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#153 2013-11-23 11:13:57

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#154 2013-11-23 14:30:08

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#155 2013-11-24 13:59:30

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#156 2013-12-24 12:55:23

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#157 2014-01-07 13:43:33

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#158 2014-01-08 10:01:04

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#159 2014-01-08 13:00:36

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#160 2014-01-10 06:21:24

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#161 2014-01-10 06:43:50

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#162 2014-01-13 08:27:05

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#163 2014-01-19 21:21:26

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#164 2014-01-26 14:14:48

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#165 2014-01-26 16:00:12

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#166 2014-01-26 23:31:16

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#167 2014-01-27 01:41:09

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#168 2014-01-27 09:29:53

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#169 2014-01-27 10:36:03

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#170 2014-01-27 11:00:05

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#171 2014-01-27 14:32:43

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#172 2014-01-27 15:12:41

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#173 2014-01-27 17:35:13

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#174 2014-01-27 21:02:02

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#175 2014-02-22 16:38:01

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#176 2014-02-22 18:41:11

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#177 2014-02-22 18:59:31

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#178 2014-02-26 14:58:28

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#179 2014-03-05 00:17:08

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#180 2014-03-05 20:26:00

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#181 2014-03-05 21:59:46

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#182 2014-03-05 23:26:09

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#183 2014-03-07 14:33:06

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#184 2014-03-07 21:38:00

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#185 2014-03-08 14:18:40

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#186 2014-03-13 16:16:14

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#187 2014-03-14 13:11:23

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#188 2014-03-14 13:16:42

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic

#189 2014-03-14 13:41:27

Re: MCT - An Android NFC-App for reading/writing/analysing/etc. MF Classic