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
Hello Everyone,
Yesterday I received my Proxmark III (Woo Hoo!). I assembled a 125kHz, 134kHz and 13.56MHz antenna. All of them appear to function as expected.
Tune
# LF antenna: 3.49 V @ 125.00 kHz
# LF antenna: 3.49 V @ 134.00 kHz
# LF optimal: 14.50 V @ 69.77 kHz
# HF antenna: 7.28 V @ 13.56 MHz
Due to my lack of experience with the PM3, I decided to follow the PM3 User Guide before I start jumping in to the deep end...
Equipment used:
* Windows 7 x64 machine
* OmniKey5321
* PM3
* ISO14443A (MiFare 1K Standard) card UID: E1 2C 9E 25
I have attempted to snoop one of the MiFare cards I have using the OK diagnostic tool. Here is what I got:
> hi14snoop
#db# in done pt
#db# 0000008c, 00000000, 00000000
#db# 00000064, 000003eb, 00000023
> hi14list
recorded activity:
time :rssi: who bytes
---------+----+----+-----------
+ 0: 32: TAG (SHORT)
+1652162: 53: TAG b7 38 (SHORT)
+ 198494: 13: TAG (SHORT)
+1657780: 36: TAG (SHORT)
+ 192936: 49: TAG b7 38 (SHORT)
+ 198724: 51: TAG (SHORT)
+2048782: 55: TAG b7 38 (SHORT)
+2049216: 47: TAG (SHORT)
+2049382: 13: TAG (SHORT)
+ 925262: 51: TAG b7 18 (SHORT)
+3371270: 52: TAG b7 38 (SHORT)
+1322076: 34: TAG (SHORT)
+1123758: 54: TAG b7 38 (SHORT)
+2445820: 55: TAG b7 38 (SHORT)
+1520564: 13: TAG (SHORT)
+ 925686: 51: TAG b7 38 (SHORT)
+ 197888: 46: TAG (SHORT)
+2049206: 49: TAG b7 18 (SHORT)
+1123762: 49: TAG (SHORT)
+1123748: 36: TAG (SHORT)
+2247512: 50: TAG b7 18 (SHORT)
+1123764: 52: TAG b7 18 (SHORT)
+1123760: 53: TAG b7 38 (SHORT)
+2445824: 52: TAG b7 38 (SHORT)
+ 198304: 39: TAG (SHORT)
+1322072: 52: TAG b7 18 (SHORT)
+1123754: 44: TAG (SHORT)
+1850904: 52: TAG b7 18 (SHORT)
+1123754: 46: TAG (SHORT)
+ 925450: 43: TAG (SHORT)
+1652590: 55: TAG b7 38 (SHORT)
+3106852: 54: TAG b7 38 (SHORT)
+1652580: 55: TAG (SHORT)
+1454278: 52: TAG (SHORT)
+2710246: 55: TAG b7 38 (SHORT)
+ 727132: 50: TAG b7 18 (SHORT)
+1916998: 58: TAG (SHORT)
+1718690: 49: TAG (SHORT)
+2247936: 30: TAG (SHORT)
+1387746: 35: TAG (SHORT)
+1195248: 50: TAG (SHORT)
+1052280: 52: TAG (SHORT)
+1916992: 43: TAG (SHORT)
+1724066: 32: TAG (SHORT)
+ 192938: 55: TAG (SHORT)
+1388162: 35: TAG (SHORT)
+ 335908: 53: TAG (SHORT)
+1052266: 57: TAG (SHORT)
+1718880: 13: TAG (SHORT)
+1718496: 58: TAG (SHORT)
+ 859354: 58: TAG (SHORT)
+ 859332: 54: TAG (SHORT)
+ 859350: 44: TAG (SHORT)
+ 859342: 49: TAG b7 38 (SHORT)
+2776344: 51: TAG (SHORT)
+1388166: 51: TAG (SHORT)
+1388170: 57: TAG (SHORT)
+2776342: 49: TAG (SHORT)
+8131564: 52: TAG (SHORT)
+3040760: 58: TAG (SHORT)
+1063034: 53: TAG (SHORT)
+ 192934: 44: TAG (SHORT)
+3239062: 55: TAG (SHORT)
+ 712028: 28: TAG (SHORT)
+3188072: 45: TAG (SHORT)
+ 335900: 41: TAG (SHORT)
+ 193540: 13: TAG (SHORT)
+ 335286: 54: TAG (SHORT)
+1057650: 53: TAG (SHORT)
+ 193124: 12: TAG (SHORT)
+ 335710: 52: TAG (SHORT)
+ 193108: 13: TAG (SHORT)
+ 335718: 52: TAG (SHORT)
+1058066: 50: TAG (SHORT)
+ 192510: 47: TAG (SHORT)
+2298514: 5: TAG (SHORT)
+4245908: 12: TAG (SHORT)
+ 335714: 47: TAG (SHORT)
+ 192930: 50: TAG (SHORT)
+ 529250: 41: TAG (SHORT)
+1057242: 54: TAG (SHORT)
+ 727132: 44: TAG (SHORT)
+ 528826: 26: TAG (SHORT)
+1255972: 44: TAG (SHORT)
+ 132242: 8: TAG (SHORT)
+4700072: 94: TAG (SHORT)
+ 528834: 68: TAG (SHORT)
+ 528822: 47: TAG (SHORT)
+ 844220: 18: TAG (SHORT)
+ 411748: 71: TAG (SHORT)
+ 528830: 36: TAG (SHORT)
+ 727136: 55: TAG (SHORT)
+1209768: 46: TAG (SHORT)
+3641074: 50: TAG (SHORT)
+1448894: 51: TAG (SHORT)
+ 727140: 38: TAG (SHORT)
when executing hi14snoop on the r52 build, prox.exe crashes. So I moved to r216.
hi14snoop takes what seems to be about 5 mins to complete, returning "in done pt". I'm not sure what this is indicating but the results from hi14list look disappointing.
Can anyone tell me where I have gone wrong and how to correct this?
I have not upgraded my unit since receiving it from proxmark3.com. I'm assuming it's using r52 (according to the documentation). Should I upgrade it to r216 or higher?
I apologize in advance if my question has already been answered elsewhere in the forum.
Regards,
-0xFFFF
Offline
I have not upgraded my unit since receiving it from proxmark3.com. I'm assuming it's using r52 (according to the documentation). Should I upgrade it to r216 or higher?
yes.
Offline
Thanks merlok,
I figured that would be the response I'd get. I just wasn't expecting the result I got from following the procedure to the letter.
I'm back at step 9.
Regards,
-0xFFFF
Offline
Pages: 1