Proxmark3 developers 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.

#301 2014-12-20 23:22:13

teve00
Member
Registered: 2014-12-13
Posts: 3

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

@ikarus: I'm sorry to hear that. :-(

@marshmellow: Thank you for the list. I found a manufacturer's site with the chips that are still produced (http://www.zotei.com/price/smart_card-IC_card_white_card_price.html). I did a bunch of Google searches but none of them (except the FM1108) are sold anywhere as UID rewritable.

Offline

#302 2014-12-24 08:35:57

pavlik1
Contributor
Registered: 2013-08-22
Posts: 15

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

ikarus wrote:

@pavlik1:
I don't know. Is it a Mifare Classic tag? What does MCT tool say? What do apps like NFC Taginfo say?

Hi ikarus

the taginfo is:1419406158_screenshot_2014-12-24-08-17-35.png

and the fideo is:

http://youtu.be/tclUq0MhZyo

to me seems the card resets due to not receiving specific answer from the reader.
any idea?

Offline

#303 2014-12-24 08:51:02

pavlik1
Contributor
Registered: 2013-08-22
Posts: 15

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

video is here https://mega.co.nz/#!1oUVjAaA!xflHmjEbHk6il4-DRIq-BkjBmw1dxxw-xZ_VTrQ0tdM

Offline

#304 2014-12-24 13:33:02

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

Hi pavlik1,

there is definitively something weird going on with your tag (and/or your readers). wink

Regarding the screenshot: in the group "Android technology information" you can only see
"android.nfc.tech.NfcA". If both, device and tag, support Mifare Classic this should be
"android.nfc.techMifareClassic". By implications this means your tag or your Android device
does not support Mifare Classic. What device do you own?

Regarding the video: I'm not sure what is causing the tag to reconnect all the time. I have some
Chinese Mifare Classic tags that sometimes behave the same way due to their really bad antennas.
But I'm pretty sure this is not what's causing the issues in your case.
Do you own a proxmark3? If so, you can sniff the traffic between the reader and the tag to see what is going on.

Have a nice Christmas eve!

Offline

#305 2014-12-25 08:25:42

pavlik1
Contributor
Registered: 2013-08-22
Posts: 15

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

hi ikarus,

The phone is S3 and it is reading and writing other tags just perfect. The reader is also ok, reading and writing under linux. It is something with the badge. at the places it supposed to work it is ok.
unfortunately no proxmark here. any idea can i sniff the good comunication? and then compare with the ACR122

Merry Christmas

Offline

#306 2014-12-29 08:16:18

result
Member
Registered: 2014-12-29
Posts: 9

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

big_smile Hi, ikarus

I found something strange today on my OnePlus One with android 4.4.2.
1: some cards with Keys of "FFFFFFFFFFFF" were read/saved as "000000000000"

I confirm its real keys of sector 0 ~ 9 are "FFFFFFFFFFFF" because I wrote a dump with this key of sector 0 ~ 9 using MCT, and it could be read and shown as "FFFFFFFFFFFF" using acr122u and mfoc.
I wrote the dump with keys "FFFFFFFFFFFF" of sector 0 ~ 9 using MCT and then read it immediately, it showed "000000000000" to me.
1419837233_qq20141229150050.jpg
1419837259_qq20141229150103.jpg
1419837296_screenshot_2014-12-29-15-08-24-76.jpg
1419837326_screenshot_2014-12-29-15-08-29-289.jpg
1419837094_screenshot_2014-12-29-15-08-37-260.jpg

Offline

#307 2014-12-29 08:31:49

result
Member
Registered: 2014-12-29
Posts: 9

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

result wrote:

big_smile Hi, ikarus

I found something strange today on my OnePlus One with android 4.4.2.
1: some cards with Keys of "FFFFFFFFFFFF" were read/saved as "000000000000"

I confirm its real keys of sector 0 ~ 9 are "FFFFFFFFFFFF" because I wrote a dump with this key of sector 0 ~ 9 using MCT, and it could be read and shown as "FFFFFFFFFFFF" using acr122u and mfoc.
I wrote the dump with keys "FFFFFFFFFFFF" of sector 0 ~ 9 using MCT and then read it immediately, it showed "000000000000" to me.
http://www.proxmark.org/forum/img/6460/1419837233_qq20141229150050.jpg
http://www.proxmark.org/forum/img/6460/1419837259_qq20141229150103.jpg
http://www.proxmark.org/forum/img/6460/1419837296_screenshot_2014-12-29-15-08-24-76.jpg
http://www.proxmark.org/forum/img/6460/1419837326_screenshot_2014-12-29-15-08-29-289.jpg
http://www.proxmark.org/forum/img/6460/1419837094_screenshot_2014-12-29-15-08-37-260.jpg


2: I wrote a MCT dump witch keys of sector 0 ~ 9 are "000000000000" to a card and then read it immediately, MCT told me sector 0 ~ 9  "No keys found (or dead sector)".
1419838189_screenshot_2014-12-29-15-41-10-543.jpg

Then I read it with acr122u and mfoc, keys of sector 0 ~ 9 could be read and shown as "000000000000"

Offline

#308 2014-12-29 08:40:55

result
Member
Registered: 2014-12-29
Posts: 9

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

What's more, do you think an optional function that automatically save dumps after a "read" operation is meaningful?

Offline

#309 2014-12-29 08:46:30

result
Member
Registered: 2014-12-29
Posts: 9

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

result wrote:

big_smile Hi, ikarus

I found something strange today on my OnePlus One with android 4.4.2.
1: some cards with Keys of "FFFFFFFFFFFF" were read/saved as "000000000000"

I confirm its real keys of sector 0 ~ 9 are "FFFFFFFFFFFF" because I wrote a dump with this key of sector 0 ~ 9 using MCT, and it could be read and shown as "FFFFFFFFFFFF" using acr122u and mfoc.
I wrote the dump with keys "FFFFFFFFFFFF" of sector 0 ~ 9 using MCT and then read it immediately, it showed "000000000000" to me.
http://www.proxmark.org/forum/img/6460/1419837233_qq20141229150050.jpg
http://www.proxmark.org/forum/img/6460/1419837259_qq20141229150103.jpg
http://www.proxmark.org/forum/img/6460/1419837296_screenshot_2014-12-29-15-08-24-76.jpg
http://www.proxmark.org/forum/img/6460/1419837326_screenshot_2014-12-29-15-08-29-289.jpg
http://www.proxmark.org/forum/img/6460/1419837094_screenshot_2014-12-29-15-08-37-260.jpg


I'm using 1.8.1  big_smile

Offline

#310 2014-12-29 21:04:48

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

Hi result,

This is really weird. Unfortunately I don't think there is much I can do about it. It's most likely
an issue with OnePlus One (or its image). I heard there are a lot of problems with Mifare Classic
and the OnePlus One. Two of my friends have one and they can't even detect Mifare Classic tag
(but other tags like Mifare Ultralight, ICode SLI, etc. are working fine).


result wrote:

What's more, do you think an optional function that automatically save dumps after a "read" operation is meaningful?

This is part of the "quick dump" feature I'm planing to implement. But not to soon. It's a lot of work and I don't have the time now.

Greetings from the 31c3

Offline

#311 2014-12-30 04:45:29

result
Member
Registered: 2014-12-29
Posts: 9

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

ikarus wrote:

Hi result,

This is really weird. Unfortunately I don't think there is much I can do about it. It's most likely
an issue with OnePlus One (or its image). I heard there are a lot of problems with Mifare Classic
and the OnePlus One. Two of my friends have one and they can't even detect Mifare Classic tag
(but other tags like Mifare Ultralight, ICode SLI, etc. are working fine).


result wrote:

What's more, do you think an optional function that automatically save dumps after a "read" operation is meaningful?

This is part of the quick dump feature I'm planing to implement. But not to soon. It's a lot of work and I don't have the time now.

Greetings from the 31c3


Great!

I'll do some tests on other devices and send you the feedbacks.

Offline

#312 2014-12-30 13:44:48

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

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

* Improved Mifare Classic support check. Thanks to "domints".
* Show a dialog if there are unsaved changes (dump and key editor).
* File name suggestion for dumps.
* Reduced presses for comparing a dump via editor.
   Thanks to "systemcrash".
* Fixed false positive results of the MF Classic support detection.
   Thanks to "domints".
* Improved editor only mode.
* Some code cleanup. Thanks to "systemcrash".
* Some minor bug fixes.
* LG G2 mini, G3 S and F60 are not supported.


Happy new year!
ikarus

Offline

#313 2014-12-30 14:52:47

iceman
Administrator
Registered: 2013-04-25
Posts: 6,277
Website

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

If you can send seven bit shortcommands with your tool,  then you might add some simple checks to see if a tag responses to the chinese magic commands  ie detect s50 gen1 cards.


If you feel the love,  https://www.patreon.com/iceman1001

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#314 2014-12-31 00:02:26

asper
Contributor
Registered: 2008-08-24
Posts: 1,409

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

Unfrtunately It is not possible to send 7bits commands (nfc chip firmware forced limitation) if so even devices not compatible with mifare will be compatible.

Offline

#315 2014-12-31 01:09:33

iceman
Administrator
Registered: 2013-04-25
Posts: 6,277
Website

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

That's a bummer.


If you feel the love,  https://www.patreon.com/iceman1001

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#316 2014-12-31 03:29:30

result
Member
Registered: 2014-12-29
Posts: 9

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

Hi ikarus,
   I did some tests on Huawei X4 and found the same issue 1. But I don't know whether Huawei X4 uses the same NFC chip as OnePlus One's NXP nsd404x or not.
   Then I turned back to my One and found the root cause of this issue. MCT (or nsd404x) can read data of sectors with keyA/B of "FFFFFFFFFFFF" using the key "000000000000"!
   1. If a key file contains both "FFFFFFFFFFFF" and "000000000000", the issue will arise randomly. But I haven't start to read the code of MCT so I don't know what's your procedure of mapping a key. I guess it's because MCT read the data using "FFFFFFFFFFFF" and  "000000000000" randomly and both of them were succeeded. There's no difference after I seperated the two keys to two files and chose both of them to read a card.
   2. The issue does not exist any more after I deleted "000000000000" from the key file, or just do not choose the key file which contains "000000000000".
   3. I use a key file contains just one key - "000000000000" to read cards. It can really read the data of sectors using "FFFFFFFFFFFF" for keyA/B WITH NO ERROR!
   4. All sectors use FF078069 for access controls.
   
   For issue 2, I don't know whether the mis-read dumps causing by issue 1 affects it or not. I don't have any cards using "000000000000" for keys to make a real dump. But I wrote a modified dump which contains "000000000000" sectors with a key file containing only "000000000000", it shows "No keys found (or dead sector)" again for "00000000000" sectors.
  So, why all-0 key can read all-F sectors but not read its own all-0 sectors?
  Could you please do the same tests on your devices?

  Many thanks! tongue
  Sorry for my poor English. yikes

Offline

#317 2014-12-31 03:33:14

result
Member
Registered: 2014-12-29
Posts: 9

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

result wrote:

Hi ikarus,
   I did some tests on Huawei X4 and found the same issue 1. But I don't know whether Huawei X4 uses the same NFC chip as OnePlus One's NXP nsd404x or not.
   Then I turned back to my One and found the root cause of this issue. MCT (or nsd404x) can read data of sectors with keyA/B of "FFFFFFFFFFFF" using the key "000000000000"!
   1. If a key file contains both "FFFFFFFFFFFF" and "000000000000", the issue will arise randomly. But I haven't start to read the code of MCT so I don't know what's your procedure of mapping a key. I guess it's because MCT read the data using "FFFFFFFFFFFF" and  "000000000000" randomly and both of them were succeeded. There's no difference after I seperated the two keys to two files and chose both of them to read a card.
   2. The issue does not exist any more after I deleted "000000000000" from the key file, or just do not choose the key file which contains "000000000000".
   3. I use a key file contains just one key - "000000000000" to read cards. It can really read the data of sectors using "FFFFFFFFFFFF" for keyA/B WITH NO ERROR!
   4. All sectors use FF078069 for access controls.
   
   For issue 2, I don't know whether the mis-read dumps causing by issue 1 affects it or not. I don't have any cards using "000000000000" for keys to make a real dump. But I wrote a modified dump which contains "000000000000" sectors with a key file containing only "000000000000", it shows "No keys found (or dead sector)" again for "00000000000" sectors.
  So, why all-0 key can read all-F sectors but not read its own all-0 sectors?
  Could you please do the same tests on your devices?

  Many thanks! tongue
  Sorry for my poor English. yikes


For issue 2, I don't know whether the mis-read dumps causing by issue 1 affects it or not. I don't have any cards using "000000000000" for keys to make a real dump. But I wrote a modified dump which contains "000000000000" sectors with a key file containing only "000000000000", it shows "No keys found (or dead sector)" again for "00000000000" sectors.

  I mean it shows "No keys found (or dead sector)" again for "00000000000" sectors when reading it after writing.

Offline

#318 2014-12-31 04:01:57

result
Member
Registered: 2014-12-29
Posts: 9

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

ikarus,
    I never succeeded to use the "writting to manufacturee block" feature. I'm using a UID writable card that made in China. Actually all bits of this card can be written like no access control. I often use it to clone M1 cards using ACR122u and below app.
1419994566_qq20141231110307.jpg

   But when I try to write sector 0 of any dump to it, it just fails with this.
1419994820_screenshot_2014-12-31-11-14-59-868.jpg1419994837_screenshot_2014-12-31-11-15-11-658.jpg1419994867_screenshot_2014-12-31-11-15-29-804.jpg

Offline

#319 2014-12-31 13:32:51

pavlik1
Contributor
Registered: 2013-08-22
Posts: 15

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

teve00 wrote:

@stickymarm: Unfortunately, the type of the card can't be determined from the block 0 data. Could you read the card with the app that I linked? It's free, doesn't require strange permissions and takes only a minute.

Does anyone actually has a direct writable card and is willing to share the type of the IC (or a cheap source)?

Thanks

624639160@qq.com
Daniel li
Fudan S50 1K

received summer 2013 and working just fine

Offline

#320 2014-12-31 14:37:45

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

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

* Bugfix: Show the "unsaved changes" dialog only if the user
   edited a dump and not just looked at it. Thanks to "systemcrash".



Happy new year!
ikarus

Offline

#321 2015-01-01 03:15:41

result
Member
Registered: 2014-12-29
Posts: 9

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

Happy new year!

Offline

#322 2015-01-03 04:56:28

kevin84
Contributor
Registered: 2014-12-06
Posts: 8

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

great job ikarus...working well on my phone...Do u know any idea of implementing bruteforce in future?..I know its very slow but maybe u can give an option like bruteforce only last two keys "11 22 33 44 55 XX" or custom option for bruteforce.

Thanks.

Offline

#323 2015-01-03 13:47:59

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

@result
I really can't reproduce the behavior you got there. I can read factory formatted tags (key A/B FFFFFFFFFFFF)
only with key FFFFFFFFFFFF and not with 000000000000. Is there something wrong with your tag?
Have you tried to read it with 000000000000 with your ACR122? Also there should not be "random" behavior
within the MCT key mapping process. I should be reproducible.

Regarding your attempt to write the manufacturer block: Are you sure you got the right type of tag?
Remember: There are special Mifare Classic tags that support writing to the manufacturer block with
a simple write command. This App is able to write to such tags and can therefore create fully correct clones.
However, some special tags require a special command sequence to put them into the state where writing
to the manufacturer block is possible. These tags will not work.


@kevin84
Thanks!
In the readme it states "There will be no "brute-force" attack capability in this application. It is way too slow due to the protocol.",
but I never thought of partial bruteforcing.. Is this really useful? How often is it the case you know parts of the key? Isn't it easier to
just buy an ACR122u for about $50 and crack the keys?

Offline

#324 2015-01-08 14:28:33

pavlik1
Contributor
Registered: 2013-08-22
Posts: 15

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

Hi Ikarus,

the card that made the reader "crazy" is probably Legic or desfire. Any suggestion about reader/software.

So far all apk i have are reading only the UID

Offline

#325 2015-01-08 15:34:10

asper
Contributor
Registered: 2008-08-24
Posts: 1,409

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

https://play.google.com/store/apps/details?id=com.legic.nfc.p2p.p2p_example

https://play.google.com/store/apps/details?id=com.skjolberg.mifare.desfiretool

Offline

#326 2015-01-09 11:41:08

pavlik1
Contributor
Registered: 2013-08-22
Posts: 15

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

asper wrote:

https://play.google.com/store/apps/details?id=com.legic.nfc.p2p.p2p_example

https://play.google.com/store/apps/details?id=com.skjolberg.mifare.desfiretool

thank you

any soft for RDR-80582AKU ?

Offline

#327 2015-01-09 13:26:00

asper
Contributor
Registered: 2008-08-24
Posts: 1,409

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

Ask the reseller.

Offline

#328 2015-01-12 22:02:29

asper
Contributor
Registered: 2008-08-24
Posts: 1,409

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

http://proxmark.org/forum/viewtopic.php?id=2238 ikarus, can you have a look to the bottom of this thread about SAK? It seems that MCT shows it in decimal and not in hex:

Last edited by asper (2015-01-12 22:03:21)

Offline

#329 2015-01-12 23:36:25

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

Hmm... It should be HEX.
...unless my byte2HexString method is broken.
But until now I never had any issues/complaints.

Offline

#330 2015-01-13 00:35:04

asper
Contributor
Registered: 2008-08-24
Posts: 1,409

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

Thanks for looking. SAK is reported in hex in every paper. Maybe he is using an old MCT version... unfortunately i don't have cards wit SAK >= A anymore to test.

Last edited by asper (2015-01-13 01:16:08)

Offline

#331 2015-01-13 20:50:29

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

The SAK was always hexadecimal in MCT.
...But you may have discovered another bug! MCT always displays a one byte long SAK value.
As I just found out, the SAK is two byte long for tags with a 7 byte UID!

The issue will be fixed within the next release!

Offline

#332 2015-01-13 21:40:16

asper
Contributor
Registered: 2008-08-24
Posts: 1,409

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

Well, not exactly 2 bytes: you receive a 1st SAK and if it has a specific bit set to 1 (bit3 start counting from 0) it asks for the next part of the UID and after this the reader receive another SAK, if also this shows there is a 3rd part of UID (triple size uid) another sequence will start and you will receive the last SAK. Here is an example with a double size UID.

So you can have 3 SAK bytes, one after each 9x 20 -> 9x 70 sequence, but not all at the same time.

93 20 --> 93 70 --> SAK-bit3 = 1 --> --> 95 20 --> 95 70 --> SAK-bit3 = 1 --> --> 97 20 --> 97 70 --> SAK bit3 = 0 --> END

93 70 = Select of cascade level1
95 70 = Select of cascade level2
97 70 = Select of cascade level3

Last edited by asper (2015-01-13 21:48:57)

Offline

#333 2015-01-13 22:03:39

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

Android returns the SAK"in one peace"  (after the whole anti collision and card selection process).
Therefor it can have more than one byte. Although, really interesting is that it can have two bytes at max.
I'm not sure why. Maybe Android cant handle CL3 tag?! Are there any CL3 tags out in the field?
(I never saw one.)

Offline

#334 2015-01-13 22:26:05

asper
Contributor
Registered: 2008-08-24
Posts: 1,409

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

Never saw one me too.

Offline

#335 2015-01-28 18:02:36

iStefano
Member
Registered: 2015-01-28
Posts: 3

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

Hi, at first congratulations for the app, it works properly on lg g3.
Please can you help me, I own an u-key like this http://www.nurissa.ch/uploads/content/clae_u-key.jpg and which I use in the vending machine and I want to change the credit value.
Now can I do this with your app? If yes how I can interpretate the values?
This is the code
Thank you very much

[== Undefined ==]
+Sector: 0
FE41BF3A3A8804004885149145200111
D2000000000000000000000000000000
00000000000000000938093809380938
A0A1A2A3A4A561E789C1B0B1B2B3B4B5
+Sector: 1
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
A0A1A2A3A4A578778869B0B1B2B3B4B5
+Sector: 2
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
A0A1A2A3A4A578778869B0B1B2B3B4B5
+Sector: 3
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
A0A1A2A3A4A578778869B0B1B2B3B4B5
+Sector: 4
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
A0A1A2A3A4A578778869B0B1B2B3B4B5
+Sector: 5
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
A0A1A2A3A4A578778869B0B1B2B3B4B5
+Sector: 6
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
A0A1A2A3A4A578778869B0B1B2B3B4B5
+Sector: 7
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
A0A1A2A3A4A578778869B0B1B2B3B4B5
+Sector: 8
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
A0A1A2A3A4A578778869B0B1B2B3B4B5
+Sector: 9
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
A0A1A2A3A4A578778869B0B1B2B3B4B5
+Sector: 10
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
A0A1A2A3A4A578778869B0B1B2B3B4B5
+Sector: 11
00000000000000000000000000000000
00000000000000000000000000000000
00000000000000000000000000000000
A0A1A2A3A4A578778869B0B1B2B3B4B5
+Sector: 12
8807F8820004A50A0000270001019B19
--------------------------------
--------------------------------
A0A1A2A3A4A51E11EE5A------------
+Sector: 13
--------------------------------
--------------------------------
--------------------------------
A0A1A2A3A4A50F00FF5A------------
+Sector: 14
--------------------------------
--------------------------------
--------------------------------
A0A1A2A3A4A50F00FFF5------------
+Sector: 15
--------------------------------
--------------------------------
00005E2000F3ED00000000004D494300
A0A1A2A3A4A54B44BB5A------------

Offline

#336 2015-01-28 21:37:48

asper
Contributor
Registered: 2008-08-24
Posts: 1,409

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

No answers to fraud questions. You are not welcome in this forum.

Offline

#337 2015-01-29 00:45:11

iStefano
Member
Registered: 2015-01-28
Posts: 3

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

Ok, I'm so sorry. I didn 't read the forum rules, I will do it right now

Offline

#338 2015-01-29 00:50:48

iStefano
Member
Registered: 2015-01-28
Posts: 3

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

So talking in general, how can I interpretate the values shown in the app? I read in the info of the app that are in the Hex format but it don't seems like that...maybe the key used by the program aren t right so the result isn't readable?
Thanks in advance

Offline

#339 2015-01-30 19:24:12

pavlik1
Contributor
Registered: 2013-08-22
Posts: 15

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

hi stefano. write me a mail to explain you how the program function
lada21011 at yahoo com

Offline

#340 2015-03-05 13:23:58

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

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

* New Feature: Increment/Decrement Value Blocks.
* New Logo. Thanks to Beneke Traub (http://www.beneketraub.com/).
* MCT can be used in "offline" mode on devices with no NFC
* Fixed the monospace font issue of the diff tool for Android 5.0+..
* Fixed representation of SAK and ATS in the tag info tool.
* Major (cosmetic) code cleanup & typo fixes.
* Some minor bug fixes.
* Samsung Galaxy S5 900P, Huawei G620S and Xiaomi MI 3 are not supported.


Why version 2.0.0? No particular reason. It just felt right. There have been much improvements
and new features since 1.0.0. With the new logo, a new feature and a lot of fixes I thought the time
was right to move to 2.0.0.

To all Samsung Galaxy S5 and HTC One (m7/m8) users that upgraded to Android 5.x:
I'm sorry, MCT does not to work on this devices right now. Unfortunately, it seams that
this is an issue of the Android builds provided by Samsung/HTC. There is nothing I can do about it.
Please see: https://github.com/ikarus23/MifareClassicTool/issues/53 and
https://github.com/ikarus23/MifareClassicTool/issues/52.

Have a nice day!
ikarus

Last edited by ikarus (2015-04-26 13:57:09)

Offline

#341 2015-03-07 15:55:50

lolio
Member
Registered: 2015-03-07
Posts: 1

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

So long story short I'm an idiot.

I was playing with the Access Condition Encoder and set two sectors on my card to read only. In hindsight this was a stupid idea as I can no longer write to those sectors. I assume that this can't be reversed? If not would it be possible to add a warning somewhere so that idiots like myself don't accidentally break their cards? Perhaps a small check with a warning message when writing to a card or when selecting it in the encoder warning that once written it can not be undone.

So other than when confronted with my idiocy your app is great, please keep up the good work.

Offline

#342 2015-03-09 22:11:56

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

Hi lolio,
I'm sorry, but you are right. These changes can not be undone.

Regarding the warning notice. I'm not sure where to place it and what exactly its content should be.
Adding a hint that you can't change the Access Conditions once you removed the permission to change them sounds kind
of ridiculous... And already is the dialog before writing to a sector trailer

You're about to write to a sector trailer. Writing incorrect data may cause irreparable damage to the tag.

and the dialog at the first usage of MCT

This application is dedicated to users who have at least basic familiarity with the
Mifare Classic technology. Its features are basic and at a low level. Therefore nearly all data input and output will be hexadecimal.
It is also important that you understand what you are doing, e.g. if you write data to a tag. Writing the wrong data to certain
blocks may cause irreparable damage to the tag.


Maybe a warning message within the AC encoder tool is the right choice. I will consider it.
Thanks for your feedback! Have fun using MCT and exploring Mifare Classic!

Offline

#343 2015-03-23 04:51:30

Lukkasss
Member
Registered: 2015-03-23
Posts: 2

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

Hello, does it work on LG G3?

Offline

#344 2015-03-24 00:34:08

phaza
Member
Registered: 2015-03-24
Posts: 1

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

Hi, I'd like to show human-readable value of sectors on the editor. For example for

display:
test     ?test           ?test           ?Ó÷Ó÷Ó÷ˆ@ÿÿÿÿÿÿ

instead of:
7465737420202020203f7465737420202020202020202020203f7465737420202020202020202020203fd3f7d3f7d3f77f078840ffffffffffff

What should I do to convert hex value in text
DumpEditor.java file method: private void initEditor:
text = TextUtils.concat(text, blocks.get(j));
et.setText(text, BufferType.SPANNABLE)

Thank you so much in advance

Offline

#345 2015-03-24 21:04:59

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

@Lukkasss
The LG G3 should work. At least this site state it has a "NXP PN547 NFC chip".
But I can't guarantee for anything. I don't own a LG G3. wink
Edit: This user tested it and it works, even with Android 5

@phaza
Sorry I don't understand your problem. You can use the menu button in the editor to
convert hex to ASCII, if this is of any help to you...

Last edited by ikarus (2015-03-24 21:09:27)

Offline

#346 2015-03-25 01:14:22

Lukkasss
Member
Registered: 2015-03-23
Posts: 2

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

ikarus wrote:

@Lukkasss
The LG G3 should work. At least  state it has a "NXP PN547 NFC chip".
But I can't guarantee for anything. I don't own a LG G3. wink
Edit: This user tested it and it works, even with Android 5

@phaza
Sorry I don't understand your problem. You can use the menu button in the editor to
convert hex to ASCII, if this is of any help to you...


Thanks for the answer ikarus.

I'm going to buy a G3 next month and I'll play with your app. I'll need some help in the future so your answers here are incredible amazing.

Thanks for providing this for us.

Have a nice day.

Offline

#347 2015-03-31 23:21:18

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

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

* Fixed bug causing to show dashes on Samsung Galaxy S5 devices.
   Thanks to "andake".
* Samsung's Galaxy Ace 4 is not supported


Finally... thanks to andake one of the ugly bugs could be fixed. MCT should now work again on Samsung's Galaxy S5.
The error: The readBlock() method of the Android API should always return 16 bytes.
On Galaxy S5 devices it sometimes returns more or less than 16 bytes.
The fix (workaround): If less than 16 bytes --> error, if more than 16 bytes --> ignore tailing bytes.


Have a nice day!
ikarus

Last edited by ikarus (2015-03-31 23:21:40)

Offline

#348 2015-04-04 13:57:17

alaa1993
Member
Registered: 2015-04-04
Posts: 6

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

how i can change the list of key ?

Offline

#349 2015-04-05 18:50:45

ikarus
Contributor
Registered: 2012-09-20
Posts: 242
Website

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

alaa1993 wrote:

how i can change the list of key ?

You mean add another key file? or edit existing key files?

1. Create new key file:
Edit/Add Key File => Context menu (3 dots) => Create New File
2. Edit key file:
Edit/Add Key File => Select a file => Edit or add keys

Was that really so hard?  hmm

Offline

#350 2015-04-12 14:59:14

alaa1993
Member
Registered: 2015-04-04
Posts: 6

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

hhhh no is so esay ....thinks
now i need to save all of tag memoiry in STRING OR another type  to display afficher chaque information dans leur text view roll

Offline

Board footer

Powered by FluxBB