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.

#101 2018-07-27 19:42:23

HighPressure
Contributor
Registered: 2016-07-17
Posts: 56

Re: Compiled Windows clients - always up to date

hey gator smile long time not seen!

just tried your latest build from google drive.
I have a brand new fresh prox from kickstarter funding.
I recognized that the device first appears as COM3 and after flashing it aligns with your batch files on COM5.
just in case you want to have an extra error routine checking if it failed smile

very good work smile thanks a lot!

Offline

#102 2018-07-30 02:08:15

gator96100
Contributor
From: Austria
Registered: 2016-03-25
Posts: 131

Re: Compiled Windows clients - always up to date

I did update the ProxSpace environment to msys2 and need someone to test it. https://github.com/Gator96100/ProxSpace … /msys2.zip
With msys2 comes a package manager and the ability to easily update all installed packages.
The initial download size will be smaller than before, but after the automatic install of all required packages the size will be about 9GB.


modhex(hligicighgidilhkfchihtijduhbif)

Offline

#103 2018-07-30 17:33:45

gator96100
Contributor
From: Austria
Registered: 2016-03-25
Posts: 131

Re: Compiled Windows clients - always up to date

I pushed some fixes to the msys2 branch and added support for x86-64 compilation. When compiling with x86-64 gcc 8.2 is required, because of a bug with avx instructions under Windows. I did compile gcc 8.2 and uploaded the packages to https://github.com/Gator96100/ProxSpace-Repo. When ProxSpace is started in x86-64 mode for the first time it will automatic install gcc 8.2. I am pretty sure gcc 8.2 is not officially supported for compilation of the proxmark client, therefore ProxSpace x86-64 is highly experimental.

Last edited by gator96100 (2018-07-30 17:39:04)


modhex(hligicighgidilhkfchihtijduhbif)

Offline

#104 2018-07-31 00:23:16

gator96100
Contributor
From: Austria
Registered: 2016-03-25
Posts: 131

Re: Compiled Windows clients - always up to date

The new msys2 ProxSpace is almost finished, which means I can create x86-64 builds(hardnested can reach the memory limit for 32 bit applications). Should I separate the uploads for x86-64 and i686 or combine them in one zip and does anyone still need i686 at all?


modhex(hligicighgidilhkfchihtijduhbif)

Offline

#105 2018-08-04 01:44:22

gator96100
Contributor
From: Austria
Registered: 2016-03-25
Posts: 131

Re: Compiled Windows clients - always up to date

All precompiled builds from now on will use the new ProxSpace environment. I did add the Proxmark3 RDV40 dedicated fork to the precompiled builds. The universal GUI by burma(still in testing) is included in all builds.


modhex(hligicighgidilhkfchihtijduhbif)

Offline

#106 2018-08-04 04:54:13

iceman
Administrator
Registered: 2013-04-25
Posts: 5,604
Website

Re: Compiled Windows clients - always up to date

Awesome!


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

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#107 2018-10-30 16:05:07

zhuminggang
Contributor
Registered: 2017-09-06
Posts: 36

Re: Compiled Windows clients - always up to date

gator96100 wrote:

All precompiled builds from now on will use the new ProxSpace environment. I did add the Proxmark3 RDV40 dedicated fork to the precompiled builds. The universal GUI by burma(still in testing) is included in all builds.

In all precompiled builds,FLASH - All.bat,FLASH - Bootrom.bat,FLASH - fullimage.bat. This three batch files missing 0x0d,Can not run in windows OS,it ought to be 0x0d,0x0a. please check carriage return and line feed, for your OS is Linux.

Offline

#108 2018-10-30 21:31:03

gator96100
Contributor
From: Austria
Registered: 2016-03-25
Posts: 131

Re: Compiled Windows clients - always up to date

zhuminggang wrote:
gator96100 wrote:

All precompiled builds from now on will use the new ProxSpace environment. I did add the Proxmark3 RDV40 dedicated fork to the precompiled builds. The universal GUI by burma(still in testing) is included in all builds.

In all precompiled builds,FLASH - All.bat,FLASH - Bootrom.bat,FLASH - fullimage.bat. This three batch files missing 0x0d,Can not run in windows OS,it ought to be 0x0d,0x0a. please check carriage return and line feed, for your OS is Linux.

I don't get it what you are trying to say. Are saying that the .bat files are missing a carriage return at the line end? On Windows a carriage return is not needed. You would be the first one to have problems with the .bat files.


modhex(hligicighgidilhkfchihtijduhbif)

Offline

#109 2018-10-31 04:30:00

zhuminggang
Contributor
Registered: 2017-09-06
Posts: 36

Re: Compiled Windows clients - always up to date

gator96100 wrote:
zhuminggang wrote:
gator96100 wrote:

All precompiled builds from now on will use the new ProxSpace environment. I did add the Proxmark3 RDV40 dedicated fork to the precompiled builds. The universal GUI by burma(still in testing) is included in all builds.

In all precompiled builds,FLASH - All.bat,FLASH - Bootrom.bat,FLASH - fullimage.bat. This three batch files missing 0x0d,Can not run in windows OS,it ought to be 0x0d,0x0a. please check carriage return and line feed, for your OS is Linux.

I don't get it what you are trying to say. Are saying that the .bat files are missing a carriage return at the line end? On Windows a carriage return is not needed. You would be the first one to have problems with the .bat files.

My laptop OS is windows 10(Version 10.0.17763.55),when i run FLASH - All.bat,many error message appear. Edit the batch files and add 0x0d each line, all is ok. Please test!

'0' is not recognized as an internal or external command,
operable program or batch file.
'ho.' is not recognized as an internal or external command,
operable program or batch file.
'!!!!!!!!!!!!!!!!!' is not recognized as an internal or external command,
operable program or batch file.
'│' is not recognized as an internal or external command,
operable program or batch file.
'ULLIMAGE' is not recognized as an internal or external command,
operable program or batch file.
'│' is not recognized as an internal or external command,
operable program or batch file.
'l' is not recognized as an internal or external command,
operable program or batch file.
'ill' is not recognized as an internal or external command,
operable program or batch file.
'will' is not recognized as an internal or external command,
operable program or batch file.
'ou' is not recognized as an internal or external command,
operable program or batch file.
'?' is not recognized as an internal or external command,
operable program or batch file.
'│' is not recognized as an internal or external command,
operable program or batch file.
'│IF' is not recognized as an internal or external command,
operable program or batch file.
'ho' is not recognized as an internal or external command,
operable program or batch file.
  ==========================================================================
Press any key to continue . . .

.

Last edited by zhuminggang (2018-10-31 04:32:52)

Offline

#110 2018-11-04 23:45:22

gator96100
Contributor
From: Austria
Registered: 2016-03-25
Posts: 131

Re: Compiled Windows clients - always up to date

I have tested multiple Windows 10 and Windows 7 installations and all are working. Windows does not care about carriage returns are you using a other than default terminal?


modhex(hligicighgidilhkfchihtijduhbif)

Offline

#111 2018-11-05 09:34:34

iceman
Administrator
Registered: 2013-04-25
Posts: 5,604
Website

Re: Compiled Windows clients - always up to date

looks like it didn't run the intial first run, where it downloaded / installed everything,   and it that case I doubt he has compiled...


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

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#112 2018-11-05 12:16:00

gator96100
Contributor
From: Austria
Registered: 2016-03-25
Posts: 131

Re: Compiled Windows clients - always up to date

iceman wrote:

looks like it didn't run the intial first run, where it downloaded / installed everything,   and it that case I doubt he has compiled...

It is about the precompiled builds and not ProxSpace, there is not initial setup. The .bat files are not working for zhuminggang because a missing carriage returns, but on Windows there is no need for it. The only reason I can think of what causes this isse is an other than default terminal.


modhex(hligicighgidilhkfchihtijduhbif)

Offline

#113 2018-11-05 13:56:17

iceman
Administrator
Registered: 2013-04-25
Posts: 5,604
Website

Re: Compiled Windows clients - always up to date

aha,  ok,  then I stand corrected


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

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#114 2019-01-22 06:56:32

Kieths
Contributor
Registered: 2015-04-21
Posts: 18

Re: Compiled Windows clients - always up to date

Hi gator,

First, I appreciate your taking time to compile official releases for Windows, as I've run into problems trying to do so.
I recently pulled down the precompiled official-64-20190117, and it appears to be based on v3.01.

Will there be a Windows 64 precompiled based on the newer v3.10 released on October 27, 2018, or has that had problems compiling on Windows? 
I ask, as the newest AndProx app specifies this version (though it may accept the prior release).

Offline

#115 2019-01-25 17:58:09

gator96100
Contributor
From: Austria
Registered: 2016-03-25
Posts: 131

Re: Compiled Windows clients - always up to date

Kieths wrote:

Hi gator,

First, I appreciate your taking time to compile official releases for Windows, as I've run into problems trying to do so.
I recently pulled down the precompiled official-64-20190117, and it appears to be based on v3.01.

Will there be a Windows 64 precompiled based on the newer v3.10 released on October 27, 2018, or has that had problems compiling on Windows? 
I ask, as the newest AndProx app specifies this version (though it may accept the prior release).

There was a bug with my git repository, only the version string was affected. Although is said v3.01 it was v3.10.
I did fix the problem, thanks for reporting that bug.

Last edited by gator96100 (2019-01-25 17:58:58)


modhex(hligicighgidilhkfchihtijduhbif)

Offline

#116 2019-01-26 06:02:24

Kieths
Contributor
Registered: 2015-04-21
Posts: 18

Re: Compiled Windows clients - always up to date

Thanks so much! 
Looking forward to checking the PM3 with updated firmware on my Android device.

Offline

#117 2019-01-26 07:44:32

Kieths
Contributor
Registered: 2015-04-21
Posts: 18

Re: Compiled Windows clients - always up to date

Issue: One of more commands under PM3UniversalGUI fail to respond / provide expected output.

Steps to reproduce (example 1):
    a) Select current COM port
    b) Select PM3\lf\read    (results: Top panel: "Sending bytes to proxmark failed - offline", other panels blank)
    c) Click Run (button on right, center)  (results: No change to display.  Attempted to scan a card, PM3 device timed out, auto-reset after 35 seconds).

Steps to reproduce (example 2):
    a) Select current COM port
    b) Select PM3\lf\read    (results: Top panel: "Sending bytes to proxmark failed - offline", other panels blank)
    c) Click Run (button on right, center)  (results: No change to display.  Attempted to scan a card, then:
        i) Press PM3 device button to reset/stop read. (note: No change to display)
        ii) Select PM3\hw\ver, and click Run (button on right, center)  (results: Item #2 below, output of "hw ver").

Conclusion: Based on the above results, it appears that:
    A) PM3UniversalGUI does not display output directly following the "lf hid read" command, though it does appear to trigger and perform the operation with output to buffers
    B) Issuing the "lf hid read" command without manually stopping/resetting the PM3 device after a short period (>20 sec) appears to result in a time out and auto reset of the PM3 device at approx. 35 seconds (note: this behavior is not observed under the proxmark3.exe terminal, which appears not to have any such timeout limitation)



PM3 System Configuration:
=========================
1) Release: official-64-20190125-1511ea28a8cc647a6fc462e9c182622a43df1318

2) Output of "hw ver" (after issuing the command, "lf hid read", scanning several swipes with no output, then pressing button to reset; TAG ID has been obscured):

proxmark3> hw ver
#db# TAG ID: 211cxxxxxx (xxxxx)         
#db# TAG ID: 211cxxxxxx (xxxxx)
#db# TAG ID: 211cxxxxxx (xxxxx)
#db# TAG ID: 211cxxxxxx (xxxxx)         
#db# Stopped         
Prox/RFID mark3 RFID instrument         
bootrom: master/v2.2.0-271-g910ad54-dirty-suspect 2016-12-19 18:01:16
os: master/v3.1.0-52-g1511ea2-suspect 2019-01-25 16:37:01
fpga_lf.bit built for 2s30vq100 on 2015/03/06 at 07:38:04
fpga_hf.bit built for 2s30vq100 on 2018/11/28 at 08:33:11
SmartCard Slot: not available
         
uC: AT91SAM7S256 Rev B         
Embedded Processor: ARM7TDMI         
Nonvolatile Program Memory Size: 256K bytes. Used: 202541 bytes (77%). Free: 59603 bytes (23%).         
Second Nonvolatile Program Memory Size: None         
Internal SRAM Size: 64K bytes         
Architecture Identifier: AT91SAM7Sxx Series         
Nonvolatile Program Memory Type: Embedded Flash Memory         

3) Proxmark3 (Original), LF Antenna (GeZhi)

4) Windows 10 Pro x64

Last edited by Kieths (2019-01-26 07:58:31)

Offline

#118 2019-01-26 07:57:45

iceman
Administrator
Registered: 2013-04-25
Posts: 5,604
Website

Re: Compiled Windows clients - always up to date

Please don't hijack threads.   This thread is about the compiled pm3 client,  create a new thread instead.


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

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#119 2019-01-26 08:14:08

Kieths
Contributor
Registered: 2015-04-21
Posts: 18

Re: Compiled Windows clients - always up to date

I apologize for misinterpreting.

I was providing a report for an error found in use of the precompiled build, which included PM3UniversalGUI, based upon the first post in this thread.  I am uncertain where the error rests, in the compilation, or in the included PM3UniversalGUI utility

gator96100 wrote:

If you ran into an error during the usage of a precompiled build please post following information...

I will create a new thread.  Thank you.
Feel free to remove the report, and our responses thereafter, as appropriate.

Last edited by Kieths (2019-01-26 08:17:08)

Offline

#120 2019-01-26 08:30:39

iceman
Administrator
Registered: 2013-04-25
Posts: 5,604
Website

Re: Compiled Windows clients - always up to date

Don't worry.  Just trying to keep the forum clean and easy to follow. Usually many subjects overbridges eachother.


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

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#121 2019-01-27 04:12:44

Kieths
Contributor
Registered: 2015-04-21
Posts: 18

Re: Compiled Windows clients - always up to date

Hi Gator,

In the newest compiled collection, the GUI utility: PM3UniversalGUI.exe (no version # under Properties/Details) does not open/run under Win10 x64.
Compilation version: official-64-20190126-1511ea28a8cc647a6fc462e9c182622a43df1318

Previous compilation version "official-64-20190117-d3c606574f90881daab8585659c18223a7a3c2c3" included PM3UniversalGUI.exe (file version 1.1.1.0), which ran, but seemed to have some parsing issues.

I've downloaded the utility author's latest release bin (circa 15/Sep/2018), and it also does not run (file version 1.1.2.0).
This version also does not run, but has a very different error.  I will advise the GUI utility writer of the test results, along with my OS version.

Will advise any updates to help with future compilations.
Thanks for your efforts in providing the compilation!

Last edited by Kieths (2019-01-27 08:14:18)

Offline

#122 2019-01-29 23:19:29

Petrolhead
Contributor
Registered: 2019-01-24
Posts: 17

Re: Compiled Windows clients - always up to date

Same here as Kieths.
I have two pc's, home and a pro edition x64 version 1803 build 17134,556  intel i7 cores.
Both official and iceman's compiled collection. (latest two releases dont start on PM3UniversalGUI.exe)


*Thank you gator96100 for the fix smile*

Last edited by Petrolhead (2019-02-09 07:15:34)

Offline

#123 2019-02-08 18:04:59

gator96100
Contributor
From: Austria
Registered: 2016-03-25
Posts: 131

Re: Compiled Windows clients - always up to date

The autobuild script did download the PM3UniversalGUI.exe in some sort of HTML format, I did fix it.
I also had to upgrade my google drive account, because I ran out of space and the latest builds could not be uploaded.


modhex(hligicighgidilhkfchihtijduhbif)

Offline

#124 2019-02-08 20:55:51

Kieths
Contributor
Registered: 2015-04-21
Posts: 18

Re: Compiled Windows clients - always up to date

I look forward to testing tonight, thank you!

Offline

#125 2019-05-01 16:48:03

Petrolhead
Contributor
Registered: 2019-01-24
Posts: 17

Re: Compiled Windows clients - always up to date

Tried the few of the latest (rdv40-64-2019****) but getting variuos problem with each version.
after version rdv40-64-20190302 it happens
Some of them the window dont start (getting a cmd and window) other it just shut down direct after start.
rdv40-64-20190501 I cant check version or ping the proxmark and tune check (gets loop problem) but reading mifare does work (strange)

Im sorry that Im not giving you exakt the fault (but each version has it own problem)

Im back on rdv40-64-20190302 and it works great, all others after dont.
Sorry for my poor troubleshooting. (on win10 1809 and got panic that I did brick my pm3)

Last edited by Petrolhead (2019-05-01 16:56:48)

Offline

#126 2019-05-01 19:31:50

gator96100
Contributor
From: Austria
Registered: 2016-03-25
Posts: 131

Re: Compiled Windows clients - always up to date

I am sorry, but I do not understand the problem.
Please describe the exact step you have done.
Adding the line "pause" in Go.bat should prevent instant closing of the cmd and maybe there is an error message.


modhex(hligicighgidilhkfchihtijduhbif)

Offline

#127 2019-05-01 21:21:39

Petrolhead
Contributor
Registered: 2019-01-24
Posts: 17

Re: Compiled Windows clients - always up to date

Appreciate that you read and answerd smile

After rdv40-64-20190302 non of the versions works correct here for me. (diffrent problems in every version)

Ill just run that version untill a bigger upgrade is avaible (so never mind my problem) maybe anyone else wanna try it? I cant be the only one.


Im a lossy explainer, sorry smile

Offline

#128 2019-08-10 20:29:04

gator96100
Contributor
From: Austria
Registered: 2016-03-25
Posts: 131

Re: Compiled Windows clients - always up to date

After the first delivery attempt for my Blue Shark Add-on failed and the package was send back to China, I finally received it.

I did add precompiled builds with the Bluetooth Add-on for x86/x64. During testing, I did have some issues related to the Bluetooth driver for my cheap USB Bluetooth dongle. If you have problems connecting to the Bluetooth COM port you might need another dongle.


modhex(hligicighgidilhkfchihtijduhbif)

Offline

#129 2019-08-12 19:54:41

iceman
Administrator
Registered: 2013-04-25
Posts: 5,604
Website

Re: Compiled Windows clients - always up to date

Nice!  Precompiled BTADDON for RDV4 platform.  Ppl will be happy.

ps
Send mail an email about what your blue shark did ?


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

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

#130 2019-08-12 21:44:20

gator96100
Contributor
From: Austria
Registered: 2016-03-25
Posts: 131

Re: Compiled Windows clients - always up to date

iceman wrote:

Nice!  Precompiled BTADDON for RDV4 platform.  Ppl will be happy.

ps
Send mail an email about what your blue shark did ?

Blue Shark did everything right and did not make any problem. My problem was Windows/Bluetooth driver related. By the way, is there supposed to be two COM ports for the Blue Shark Add-on? I have an incoming COM port and an outgoing COM port and just one of them seems to work.


modhex(hligicighgidilhkfchihtijduhbif)

Offline

#131 2019-08-12 21:54:10

iceman
Administrator
Registered: 2013-04-25
Posts: 5,604
Website

Re: Compiled Windows clients - always up to date

yeah.  i noticed that aswell.  the B one works for me.  strange but client sends first.  ie outgoing.


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

modhex(hkhehghthbhudcfcdchkigiehgduiehg)

Offline

Board footer

Powered by FluxBB