problem with proxmark3.exe

Mariana · 2014-03-24 12:45:41

Hi everyone,

I'm struggling with proxmark. I've downloaded the files from http://code.google.com/p/proxmark3/downloads/list and I'm following the instructions from this list. firstly I had some difficulties with proxmark driver for win7 64 bit but now it seems fine. Now the new problem is with running ./client/proxmark3.exe. while running this command the result is No suck file or directory which is correct! I've checked the client folder and there is not ant .exe file there!
I thought maybe there is something wrong with the package that I've downloaded but I don't have any other source to download! I've tried an old package but It's got it's own problems!

Any help would be greatly appreciated.

Thanks,
Mary

iceman · 2014-03-24 13:00:36

Don't know if this applies to you but have you change directory to client before executing the client?

Ie:
cd client
./proxmark3.exe com3 (well, which com-port you have)

Mariana · 2014-03-24 13:31:34

Yes and the result is the same: No such file or directory. even I checked the client folder but I couldn't find any .exe file.

Cex · 2014-03-24 13:35:04

The source code does not cointain the binaries for either the proxmark hardware or the windows client.
You can either:

1 - Download the Proxspace compilation environment from the download section in googlecode
2 - Download the pre-built binaries from the Windows client section

Regards.

asper · 2014-03-24 13:45:13

proxmark3.exe is not a command, is a file that MUST be present; CEX is probably right, you are trying to run source code (impossible) while you need to run the compiled .exe; unfortunately proxmark is not for total newbies...

iceman · 2014-03-24 14:05:04

Missed that one.
The proxspace environment is not easy to use so I recommend the Cex option 2 where you download the pre-compiled binaries.

Mariana · 2014-03-24 14:26:11

Based on the "GETTING STARTED GUIDE FOR WINDOWS 7 USERS" file , I tried to run the Proxmark software by “./client/proxmark3.exe” command but the result is what I've mentioned above.

asper · 2014-03-24 14:32:21

Do you have the file "proxmark.exe" in /client folder ? If not you are missing something. In particular (again) "./client/proxmark3.exe” is not a command, is a file located in /client folder.

Last edited by asper (2014-03-24 14:33:01)

Mariana · 2014-03-24 14:38:55

I know that it is not a command. that's why I think there is something wrong with the package that I've downloaded from google code. there isn't any .exe file in the client folder. I've also downloaded the file 2,3 times as a coincidence of bad downloading. seeing the msg like " No such file or directory"is obvious when that specific file or directory is not available!
except google code do you guys know any other sources to download the package?

Mariana · 2014-03-24 14:42:32

I wish I could send you a picture of files available in the client folder.

asper · 2014-03-24 14:50:04

http://proxmark.org/forum/viewtopic.php?id=1562

Mariana · 2014-03-24 15:11:15

Thank you ! I will try the new source. hope it works this time!

Mariana · 2014-03-24 23:59:19

Hi, below are my recent results:
1.I've downloaded recent package from google code. Even by SVN updating this package, the command "make clean && make all" cannot be run and without running this command the proxmark3.exe cannot be created under client folder.
2. I've downloaded an older package and did SVN update on that. the command "make clean && make all" runs and the proxmark3.exe is created under client folder. again while trying to run "./client/proxmark3.exe" error " Attempted to write bootloader but bootloader writes are not enabled "is appeared. Error while loading bootrom/obj/bootrom.elf. I checked that the bootrom.elf is available under obj folder.
3. I thought maybe I should do UPDATE PROXMARK3 BOOTLOADER. But while holding the pm3 button , at the first pm3 is recognized by windows and then it sais windows cannot recognize the usb device! and in cmd windows the msg "waiitng for the USB" remains!

I might be a newbie but I really need to make this device works...

asper · 2014-03-25 08:45:08

To make proxmark to work you DO NOT NEED the source code (svn, make, etc); you can use the pre-compiled windows version. To correctly use the pre-compiled version you need to install proxmark drivers. If you bought proxmark3 and you have an older firmware version (ask the seller which one) you need to upgrade it (from r650 proxmark uses CDC serial communication insted of libusb).

With proxmark3.exe you CANNOT write bootloader so the sentence:

"while trying to run "./client/proxmark3.exe" error " Attempted to write bootloader but bootloader writes are not enabled ""

seems to be fake because proxmark3.exe DOES NOT WRITE to bootloader; maybe you used flasher.exe.

To correctly update an older firmware (if you have an older firmware) read the .pdf document attached to the compiled windows release and follow the instructions (you can use the batch files provided there.

The "bootloader writes are not enabled" usually is dued to the missing -b parameter with flasher.exe:
flasher -b bootrom.elf
bootrom.elf need to be in the same flasher.exe folder if you do not use provided batch files but for what I remember batch files included alerady use the -b option.

EDIT: holding the proxmark3 button makes the proxmark to enter a "special mode" that need its driver; use one of the provided driver in the compiled archive.

Last edited by asper (2014-03-25 08:50:19)

Mariana · 2014-03-29 10:45:58

Hi everyone,
It seems I'm getting some where (I'm not sure yet!). I've updated the package by "pm3-bin-756 - lua branch.zip" pack and seems proxmark3.exe can be run.Actually the GNU terminal window closes quickly and I can't read a word of the result!

btw Could you please tell me why when I want to run "hw version" command, it says " command not found"?

Thanks,
Mariana

asper · 2014-03-29 12:07:30

You need to specify the proxmark3 com port using the following command under a shell:
proxmark3 comX
where X is the com port number assigned by you system to the proxmark3.

Please have a look at the new windows wiki page for more information.

Last edited by asper (2014-03-29 13:07:37)

Mariana · 2014-03-29 12:09:21

Thank you asper

Mariana · 2014-03-29 13:54:27

Dear asper,
Thank you for the windows wiki page . this is really awesome that all steps are sorted like this.

I tried to specify the com port doing UPDATE PROXMARK TO THE NEW CDC Serial INTERFACE step. I can see see "ProxMark-3 RFID Instrument" under the "LibUSB-Win32 Devices" node but when I'm doing the flashing step ( holding the button, connection, hearing the USB port sound, and waiting for...) after a while it says that windows can not recognized the usb device and then there is no "ProxMark-3 RFID Instrument" under the "LibUSB-Win32 Devices"! I can only see unknown device!

I had the same problem while doing the next step, "WINDOWS PROBLEMS IN RECOGNIZING COM PORT". Could you please tell me why it happens?!

Regards,
Mariana

Mariana · 2014-03-29 14:14:58

I don't know if it's important or nit but I'm using win 7 32- bit.

asper · 2014-03-29 15:05:06

Are you using the old flasher and not the newer one?

Mariana · 2014-03-29 23:33:23

I'm using FLASH NEW Bootrom (uses old flasher exe with -b option).bat

asper · 2014-03-29 23:43:14

Try to use the old flasher to update fpga and os (you need to do it manually) while holding the button.

Mariana · 2014-03-29 23:52:47

Sorry asper but I'm not sure if I've got you correctly. you mean I should use FLASH - OS.bat AND FLASH - FPGA fullimage.bat ? could you please explain more.
I really appreciate your help.

Mariana · 2014-03-30 00:53:41

in the flasher screen it says that "you will need to have <bootrom-only.bat> file in \win32 folder but there is not such a file in that folder! could it be a reason?!

asper · 2014-03-30 07:43:31

You need to flash the new cdc/serial bootloader. If windows finds pm3 under libusb that means you have to the old bootloader. Old bootloader needs old flasher to flash anything (even new serial .elf files). You cannot specify a com port when using old bootloader because libusb is not serial. Batch files are there to help but you can also use manual commands under windows shell (if you don't find a batch file for example - you are correct, the file name reported in the flash screen is wrong but the batch commands inside are correct - anyway i will fix this). Again, pm3 needs practice, you have all you need to solve your problem, if i will spoon-feed you, you will never learn how pm3 works. Try to do the procedure from the beginning.

Anyway if you have windows recognizing proxmark3 under libusb you can open a dos shell in the proxmark3.exe client folder and simply run proxmark3.exe (but you need an old proxmark.exe version to make this command to work); after connecting to pm3 execute hw version and post here the result.

A final word: you are finding problems because you mixed up recent releases with old releases. Old client (proxmark3.exe) does not respond to new firmwares and new client does not respond to old firmwares. You MUST use .exe files and firmwares from the same release to make it to work properly.

Last edited by asper (2014-03-30 08:42:39)

Mariana · 2014-04-03 01:46:12

Hi asper and others who tried to help me
Just wanted to let you know that my dear pm3 works perfectly.

Thank you

asper · 2014-04-03 07:13:51

Good job man!

Proxmark3 community

Announcement

#1 2014-03-24 12:45:41

problem with proxmark3.exe

#2 2014-03-24 13:00:36

Re: problem with proxmark3.exe

#3 2014-03-24 13:31:34

Re: problem with proxmark3.exe

#4 2014-03-24 13:35:04

Re: problem with proxmark3.exe

#5 2014-03-24 13:45:13

Re: problem with proxmark3.exe

#6 2014-03-24 14:05:04

Re: problem with proxmark3.exe

#7 2014-03-24 14:26:11

Re: problem with proxmark3.exe

#8 2014-03-24 14:32:21

Re: problem with proxmark3.exe

#9 2014-03-24 14:38:55

Re: problem with proxmark3.exe

#10 2014-03-24 14:42:32

Re: problem with proxmark3.exe

#11 2014-03-24 14:50:04

Re: problem with proxmark3.exe

#12 2014-03-24 15:11:15

Re: problem with proxmark3.exe

#13 2014-03-24 23:59:19

Re: problem with proxmark3.exe

#14 2014-03-25 08:45:08

Re: problem with proxmark3.exe

#15 2014-03-29 10:45:58

Re: problem with proxmark3.exe

#16 2014-03-29 12:07:30

Re: problem with proxmark3.exe

#17 2014-03-29 12:09:21

Re: problem with proxmark3.exe

#18 2014-03-29 13:54:27

Re: problem with proxmark3.exe

#19 2014-03-29 14:14:58

Re: problem with proxmark3.exe

#20 2014-03-29 15:05:06

Re: problem with proxmark3.exe

#21 2014-03-29 23:33:23

Re: problem with proxmark3.exe

#22 2014-03-29 23:43:14

Re: problem with proxmark3.exe

#23 2014-03-29 23:52:47

Re: problem with proxmark3.exe

#24 2014-03-30 00:53:41

Re: problem with proxmark3.exe

#25 2014-03-30 07:43:31

Re: problem with proxmark3.exe

#26 2014-04-03 01:46:12

Re: problem with proxmark3.exe

#27 2014-04-03 07:13:51

Re: problem with proxmark3.exe

Board footer