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
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.
I am setting up my Proxmark3 RDV V2 from Elechouse on Windows 10.
The installation appeared to run fine with no errors but when attempting to flash the bootrom I received an error to say:
bash: /client/flasher: No such file or directory
I reviewed the file structure and the directory and file are present.
I assume it's not a driver issue or port issue as the Human Interface Device appears in Device Manager as does the Serial Com port on Com4.
I typed the command as I read it from the instructions:
/client/flasher com4 -b /bootrom/obj/bootrom.elf
Any guidance greatly appreciated.
Thanks
I guess you are using ProxSpace on Windows 10, right?
Of cause /client/flasher does not exist, ist is./client/flasher com4 -b /bootrom/obj/bootrom.elf
There is no folder /client
Thanks for the reply.
You are correct, it is ProxSpace on Windows 10.
Not sure I follow you though. I just checked the directory structure again and there is a client folder under
\ProxSpace-Master\pm3\client
and the file flasher.exe resides within it.
Am I missing something?
/client is not a relative directory if you want to run the flasher that is in the client folder of your current directory you need a dot =>"./client/flasher com4 -b ./bootrom/obj/bootrom.elf"
On Windows /client would be equal to C:/client whereas ./client would be equal to <current dir>/cient
Last edited by gator96100 (2018-10-10 08:06:42)
Sorry for the delay in my reply. Too much work and not enough free time. Thank you to both of you. I sorted it.
I haven't used Linux previously and my QNX is a little rusty and dated.
It's all up and running now so it's time to start experimenting!