Compiled Windows Client - Download

joe · 2014-09-17 19:11:23

iceman wrote:

If you look in the file "FLASH bootrom.bat", the there should be a "flasher.exe com3 -b ..\firmware_win\bootrom.elf" in the older versionens I think the "-b" parameter was missing.

Thanks iceman for your remind , I found I did not change the com port . Now are ok ! Careless mistake.

Armadillo · 2014-09-18 04:41:24

Dear Experts;

Please advise;

Just got the proxmark3 board from Gezhi and flashed with the latest bootrom, firmwares, fpga from "pm3-bin-756 (cdc+lua).rar". The CDC problem seems to give results of 00000000000 using nested attack on known keys card (mifare 1k Philip) and the darkside terminates the com port. I am running windows 7 Pro.

Now I would like to revert to the old goggle compile and I think the latest is "pm3-bin-848".

I would like to know how to revert back to the HID from CDC installation. thanks guys.

iceman · 2014-09-18 06:01:31

Sorry, but your version "pm3-bin-756 (cdc+lua).rar" is not the latest at all. There has been some major changes since then. Lots of bugfixes and functionality sorted out.

Go for Aspers "0.0.4" release (which is based on the current github) Downloadable from page 1 in this thread.

Armadillo · 2014-09-18 07:07:35

Thanks iceman;

The release of "pm3-bin-756 (cdc+lua).rar" was dated Aug 2013 on this following page;

"http://code.google.com/p/proxmark3/downloads/list"

Dearest Asper latest stand alone windows compile on the first page was dated Mar 2013.

So I had thought Aug version was the latest latest version. LOL.

I will ignore the google downloads altogether from now, it has proven "not usable".

I will download 0.0.4 and have a go at it. But RadioWar web page also advises against using CDC, if I have not read wrongly. GeZhi relies on r651 version.

For curiosity sake, any thoughts on how a "safe" revert can be done from CDC to HID version. Anyone has tried it. I have not tried, any mistake here means I have to send the board back to GeZhi. I don't have the Segger J-LINK, but I have the ST-Link/V2.

I don't see the 64Kb/sec interface speed has any impact on my general usage by using HID, but getting the reliable right answer being the key!

Thanks iceman, again.

iceman · 2014-09-18 08:14:27

I see, you have been misslead by the date of Aspers first message. The thing is that Asper updates that message (but the date remains the same) and links in the latest versions for the windows environment. So the "0.0.4" release is about two weeks old.

The PM community switch from GoogleCode -> GitHub last spring, so the old repositories are not maintained anymore. Code obselete.
Only look at GitHub for latest sourcecode.
and only look in this thread (since it is Sticky) for Aspers latest windows-releases.

You will find that 0.0.4 version solves a lot of earlier problems. No reason at all to stay with old firmware/r651/r756/ anymore.

asper · 2014-09-20 13:00:01

Added r0.0.5 to the 1st post.

Last edited by asper (2014-09-20 13:00:12)

nfc_comm1 · 2014-09-22 23:55:59

suspect I just killed a pm3. maybe there's a way to recover? Here's the situation...
I managed to get some info out of it, pre-flash: hw version...
Prox/RFID mark3 RFID instrument
bootrom: svn 215 2010-01-14 21:43:26
os: svn 215 2010-01-14 21:43:26
FPGA image built on 2009/ 8/28 at 23:49:10

with this bootloader it was showing up in windows under "Human Interface Devices" as a "USB Input Device" (bus reported device desciption identified it as the proxmark). Post old driver install, it would appear under a section called "libusb-win32 device" (or something close to that).

I was able to flash it using the instructions in "pm3-bin-0.0.5" -> UpdateBootloader.pdf

However. Now, when plugging it into a usb port, the red and yellow lights stay on solid, and every 17-18 second they go off, the green light briefly comes on and a switch noise is heard. Seems like it's resetting every 17-18 seconds. Nothing appears in windows USB. Took it to a linux box and lsusb shows nothing for the proxmark. looks like it's not booting at all.

Any hope for reviving the device or do we just need to buy a new one?

asper · 2014-09-23 13:53:00

Have a look here: http://www.proxmark.org/forum/viewtopic.php?id=2119

nfc_comm1 · 2014-09-24 17:10:25

was able to get it working, held button down while plugging it in and was able to install new driver, then flash the os and fpga. It's now working fine!

Although, hw version shows...
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: /-suspect 2014-09-19 10:31:37
#db# os: /-suspect 2014-09-13 11:21:04
#db# HF FPGA image built on 2014/ 6/19 at 21:26: 2
uC: AT91SAM7S256 Rev A
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 256K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory

The "/-suspect " bit is a bit concerning

iceman · 2014-09-24 17:19:03

Good!
U shouldn't worry about that. It is just the "version.c" which is generated during the compilation. Nothing that you should be concerned about, your PM3 will work nevertheless.

nfc_comm1 · 2014-09-24 20:38:53

thanks for the help folks!

no6mis · 2014-12-12 19:23:54

Hi,

Proxmark Tool.exe has been identified as TR, any explanation why?

https://www.virustotal.com/de/file/7b9dfc5b19d7bb8d056b37e07b82d5c794cd59e75319aa3034c94fa1f0a9fd00/analysis/1418408815/

asper · 2014-12-13 08:01:36

False positive. We should ask gaucho why.

iceman · 2014-12-13 11:02:07

Could be a packer used? I read on the antivirus companies pages and the classification is used for programs (indepentently developers and small distributions) where the antivirus software thinks it is a new strange software not seen before and tags it as "here might be dragons"..

gaucho · 2014-12-15 20:50:31

hi guys,
i uploaded on this forum also the sources,
you can check by yourself that there is no virus inside it.
anyway there are many reasons why a exe is identified as virus.

i should check the code cause actually i can't remember anything causing the issue.

in example few years ago i created a executable that modifies itself in order to store inside the exe some data. also this fact is identified as virus. anyway our tool for proxmark has nothing special inside it.

anyway i'm glad to know that one of my tools is on a global virus database.

dk1206 · 2014-12-23 12:50:29

Hey guys, is there any possible Guide also on How To use this Tool ?
With a good description of what each option does (e.g. DARKSIDE ATTACK, NESTED ATTACK, etc.) ?

Thanks.

iceman · 2014-12-23 19:14:59

You can start with reading the old wiki and on the forum and the help texts from the pm3 client.

After that I suggest an trial and error approach.

asper · 2014-12-24 12:56:00

The tool is only a gui for proxmark exe file, you should know how to use proxmark before using the GUI; anyway inside the gui you can find many useful hints/tips that are not present in the .exe.

asper · 2015-01-01 18:09:12

Added r0.0.6 to the 1st post.

renko · 2015-01-30 02:17:50

I am new to this so please forgive the dumb question.

I have a new proxmark an went to the Github site and downloaded the latest build by downloading and unpacking the zip file that I found on the right hand side of the page. There were no elf files and I knew that I had to compile this package to make them.

As well I did download the proxspace file with QT and the rest of the packages to compile the Github file in Win7. I am just stuck on what steps I should take next to produce the elf files.

Thanks for the help.

marshmellow · 2015-01-30 04:11:39

In the proxspace folder find the readme and look for guides in there. I'm not at my PC ATM or I'd be more specific

marshmellow · 2015-01-30 04:12:40

Also have a look at the wiki on github

marshmellow · 2015-01-30 04:35:10

https://github.com/Proxmark/proxmark3/wiki/Windows for the windows wiki

renko · 2015-01-31 19:32:34

Thank you marshmellow for taking the time to respond, much appreciated. I will have a look at this page and the wiki and work my way through it. Maybe someday I can actually contribute something useful to this forum.

asper · 2015-02-01 10:58:49

Added r.0.0.7 to the 1st post.

Please do not use this thread for feedbacks or bugs, search the forum for the appropriate section. Thank you !

gaucho · 2015-02-01 15:50:12

Hi guys, i had the time to investigate about the gui revealed as virus.
i scanned the exe and it was revealed as virus.
then i commented the part of the code that i suspect it is causing the issue, i recompiled and scanned again with antivirus and it is no more revealed as virus.
so i uncommented the code, restoring it in it's original state and i recompiled
then i rescanned it with antivirus (and virustotal website) but it is no more revelaed as virus.

i suspect that antivirus was using hash of the exe but the exe after recompile is no more identified as virus.

i upload here the exe that it is exactly the same as before (talking about code), it is just recompiled.

i suspect that the exe will be soon reidentified as virus, and i suspect that the resposible part for this, is the following part of the code that calls the command prompt exe in a sort of subclassing:

 Public Sub ProxmarkProcess()


        p = New Process



        Dim pi As ProcessStartInfo = New ProcessStartInfo()
        pi.Arguments = "COM" & comPortNumberVar
        pi.FileName = Application.StartupPath & "\proxmark3.exe"
        
        pi.UseShellExecute = False
        pi.CreateNoWindow = True
        pi.RedirectStandardInput = True
        pi.RedirectStandardOutput = True

        p.StartInfo = pi
        p.Start()



        While True
            Try
                If p.StandardOutput.EndOfStream Then Continue While
                Dim tmpStr As String = p.StandardOutput.ReadLine
                If Trim(tmpStr) <> "" Then SetText(tmpStr)


            Catch ex As Exception

            End Try

        End While
        p.WaitForExit()
        p.Close()

    End Sub

this is the recompiled exe: https://www.sendspace.com/file/j0cxkm

i can't do more than report it as a false positive. you can do the same.

marshmellow · 2015-02-01 16:02:13

I've found that other projects with p.Start were also falsely identified...

Last edited by marshmellow (2015-02-01 16:03:44)

joe · 2015-02-03 14:34:44

Just updated to bin-007, but the LF SEARCH, can't work with windows 32 bits XP. anyone can tell me the reason ??

but it works well with windows 7.

proxmark3> lf search
#db# buffer samples: 9a 98 93 8e 8a 8b 8e 8b ...
Reading 20000 samples from device memory
NOTE: some demods output possible binary
if it finds something that looks like a tag
Checking for known tags:
No Known Tags Found!
proxmark3>
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: /-suspect 2015-01-31 07:13:30
#db# os: /-suspect 2015-01-31 07:13:36
#db# LF FPGA image built on 2015/01/15 at 12:18:56
uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3>
proxmark3> hw tune
Measuring antenna characteristics, please wait.......
# LF antenna: 5.50 V @ 125.00 kHz
# LF antenna: 5.50 V @ 134.00 kHz
# LF optimal: 11.28 V @ 166.67 kHz
# HF antenna: 0.06 V @ 13.56 MHz
# Your HF antenna is unusable.
Done! Divisor 89 is 134khz, 95 is 125khz.
proxmark3>

joe · 2015-02-03 14:44:53

now, This are the output from windows 7...

proxmark3> lf search
#db# buffer samples: 00 00 00 00 00 03 08 0b ...
Reading 20000 samples from device memory
NOTE: some demods output possible binary
if it finds something that looks like a tag
Checking for known tags:
Using Clock: 40 - Invert: 0 - Bits Found: 400
ASK/Manchester decoded bitstream:
0000000000000000
0000111111111001
1000000000000000
1000010001100101
0001011011001010
1100000101100111
0000000000000000
0000111111111001
1000000000000000
1000010001100101
0001011011001010
1100000101100111
0000000000000000
0000111111111001
1000000000000000
1000010001100101
0001011011001010
1100000101100111
0000000000000000
0000111111111001
1000000000000000
1000010001100101
0001011011001010
1100000101100111
0000000000000000
No Known Tags Found!
proxmark3>
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: /-suspect 2015-01-31 07:13:30
#db# os: /-suspect 2015-01-31 07:13:36
#db# LF FPGA image built on 2015/01/15 at 12:18:56
uC: AT91SAM7S256 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 256K bytes
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3>
proxmark3> hw tune
Measuring antenna characteristics, please wait.........
# LF antenna: 6.98 V @ 125.00 kHz
# LF antenna: 9.00 V @ 134.00 kHz
# LF optimal: 10.74 V @ 139.53 kHz
# HF antenna: 0.39 V @ 13.56 MHz
# Your HF antenna is unusable.
Done! Divisor 89 is 134khz, 95 is 125khz.
proxmark3>

marshmellow · 2015-02-03 14:48:51

asper wrote:

Please do not use this thread for feedbacks or bugs, search the forum for the appropriate section. Thank you !

joe · 2015-02-03 14:54:49

ok, noted. sorry ...

asper · 2015-04-02 17:50:44

Updated the 1st post with the new rev 2.0.0 !
Many changes since last compiled 0.0.7, mainly in the LF front but not only !

Many kudos to Piwi, Holiman, Iceman and Marshmellow for the new code !

Last edited by asper (2015-04-02 17:51:11)

Earman · 2015-04-02 21:05:55

Thanks Asper, Piwi, Holiman, Iceman and Marshmellow!

Last edited by Earman (2015-04-02 21:07:33)

DingYao · 2015-05-23 09:41:17

pm3-2.00-bin link not working, mirror?

asper · 2015-05-23 13:09:36

DingYao wrote:

pm3-2.00-bin link not working, mirror?

Right now I only have the latest compiled build; can someone please provide a link to 2.0.0 ? I will re-upload it as soon as I get it. Dunno why sendspace deleted it.

marshmellow · 2015-05-24 05:00:46

pm3-2.0.0 https://www.sendspace.com/file/tofyqi

DingYao · 2015-05-24 05:23:33

Asper, if that is the case, could you upload the latest compiled build? Thanks in advance!

Marshmellow, do you have the compiled version of pm3-2.00?

asper · 2015-05-24 09:24:50

Link to 2.0.0 updated. Thanks marshmellow !

DingYao · 2015-05-24 10:49:52

asper wrote:

Link to 2.0.0 updated. Thanks marshmellow !

The new link is the 2.00 sources which can be found on GitHub and not the compiled Windows binaries.

asper · 2015-05-24 11:48:40

Updated with compiled code.

DingYao · 2015-05-24 13:39:15

asper wrote:

Updated with compiled code.

Thank you asper!

marshmellow · 2015-05-24 14:08:20

DingYao wrote:

asper wrote:
Link to 2.0.0 updated. Thanks marshmellow !
The new link is the 2.00 sources which can be found on GitHub and not the compiled Windows binaries.

Oops wrong zip.. Lol. Thanks asper .

iceman · 2015-06-18 14:28:29

Per request, a bin distro of iceman fork.

Please take notice that it is a highly experimental distro since the sourcecode has more changes than the PM3 unstable branch.
You will need to flash the osimage.elf.

https://www.sendspace.com/file/8kff3o

asper · 2015-06-23 17:15:26

Added the new rev 2.1.0 to the 1st post !

ntk · 2015-07-08 01:09:40

thank you all for all the hard works to bring out this new release.

I flash bootrom.elf and fullimage.elf, Does it contain all new changes or do I have to flash osimage.elf separately too?

@Marshmellow

Just remember about why I did not want to upgrade: The modification to avoid problem in AT55x7 and Q5 writing!

Do I still have to do it manually? Sh*t* Sh*t* sh*t* I overwritten the whole proxmark3 directory and have lost it

Last edited by ntk (2015-07-08 01:31:23)

ntk · 2015-07-08 03:48:49

Writing Q5 and AT55x7 seem to be OK. patch is in the src code lfops.c.

But proxmark3> hw version
uC: AT91SAM7S512 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 512K bytes
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
proxmark3>

I cleaned and rebuild all and flashed but version does not let me see when it is built anymore. Is it intended in the new SW release?

marshmellow · 2015-07-08 04:53:18

Fullimage.elf contains the is and fpga code now there shouldn't be an osimage anymore.

marshmellow · 2015-07-08 05:11:56

Regarding the hw ver, Are you using the 2.1.0 from aspers pre compiled binaries in the first post of this thread? Yet you say you cleaned and rebuilt all...?

ntk · 2015-07-08 11:03:43

yes I downloaded proxmark3-master from GIT then rebuild all, flash all with "make clean && make all flash-all", then I downloaded also the zip file bin 2.1.0 RAR extract and copy over the client folder to have new client, GUI environment.

I ran writing test on At55x7 and Q5 and tested, checked the source code lfops.c

After all that I ran version and was surprised

Last edited by ntk (2015-07-08 11:05:29)

marshmellow · 2015-07-08 12:13:08

I suggest you make and flash again as it seems you client and firmware are different versions that don't fully understand each other. The github master is past 2.1.0, so if you overwrote the proxmark3.exe in your client folder with the 2.1.0 you broke it. Make again...

Proxmark3 community

Announcement

#101 2014-09-17 19:11:23

Re: Compiled Windows Client - Download

#102 2014-09-18 04:41:24

Re: Compiled Windows Client - Download

#103 2014-09-18 06:01:31

Re: Compiled Windows Client - Download

#104 2014-09-18 07:07:35

Re: Compiled Windows Client - Download

#105 2014-09-18 08:14:27

Re: Compiled Windows Client - Download

#106 2014-09-20 13:00:01

Re: Compiled Windows Client - Download

#107 2014-09-22 23:55:59

Re: Compiled Windows Client - Download

#108 2014-09-23 13:53:00

Re: Compiled Windows Client - Download

#109 2014-09-24 17:10:25

Re: Compiled Windows Client - Download

#110 2014-09-24 17:19:03

Re: Compiled Windows Client - Download

#111 2014-09-24 20:38:53

Re: Compiled Windows Client - Download

#112 2014-12-12 19:23:54

Re: Compiled Windows Client - Download

#113 2014-12-13 08:01:36

Re: Compiled Windows Client - Download

#114 2014-12-13 11:02:07

Re: Compiled Windows Client - Download

#115 2014-12-15 20:50:31

Re: Compiled Windows Client - Download

#116 2014-12-23 12:50:29

Re: Compiled Windows Client - Download

#117 2014-12-23 19:14:59

Re: Compiled Windows Client - Download

#118 2014-12-24 12:56:00

Re: Compiled Windows Client - Download

#119 2015-01-01 18:09:12

Re: Compiled Windows Client - Download

#120 2015-01-30 02:17:50

Re: Compiled Windows Client - Download

#121 2015-01-30 04:11:39

Re: Compiled Windows Client - Download

#122 2015-01-30 04:12:40

Re: Compiled Windows Client - Download

#123 2015-01-30 04:35:10

Re: Compiled Windows Client - Download

#124 2015-01-31 19:32:34

Re: Compiled Windows Client - Download

#125 2015-02-01 10:58:49

Re: Compiled Windows Client - Download

#126 2015-02-01 15:50:12

Re: Compiled Windows Client - Download

#127 2015-02-01 16:02:13

Re: Compiled Windows Client - Download

#128 2015-02-03 14:34:44

Re: Compiled Windows Client - Download

#129 2015-02-03 14:44:53

Re: Compiled Windows Client - Download

#130 2015-02-03 14:48:51

Re: Compiled Windows Client - Download

#131 2015-02-03 14:54:49

Re: Compiled Windows Client - Download

#132 2015-04-02 17:50:44

Re: Compiled Windows Client - Download

#133 2015-04-02 21:05:55

Re: Compiled Windows Client - Download

#134 2015-05-23 09:41:17

Re: Compiled Windows Client - Download

#135 2015-05-23 13:09:36

Re: Compiled Windows Client - Download

#136 2015-05-24 05:00:46

Re: Compiled Windows Client - Download

#137 2015-05-24 05:23:33

Re: Compiled Windows Client - Download

#138 2015-05-24 09:24:50

Re: Compiled Windows Client - Download

#139 2015-05-24 10:49:52

Re: Compiled Windows Client - Download