You could try the script I have here (Windows Method #2):
It’ll install ProxSpace for you mostly automated
1 Like
ill give this a try and get to you. i’ve most likely tried the first method on the pm3 wizard. going to give both methods try
1 Like
this happen
It sounds like the tar file wasn’t completely downloaded
The script should download and automatically unpack it, all you should have to do is run the bat file
Hmmm…
1 Like
still no luck! is it possible if you could do screen sharing with me
1 Like
That’s it unpacking, it’s not a particularly quick process unfortunately, it’s a lot of files…
I’ll have to take a look into speeding things up…
1 Like
Yes, after the tar file is decompressed and installed, those files are there
That’s how you re-launch the client after the initial install
1 Like
Where are you putting the proxspace files? There sometimes is a problem with proxspace being placed into a file path that has long file names and / or spaces. It is suggested dngr.us/pm3-guide to place the ProxSpace files into a simple short path off the C:\ or root of any target drive like C:\ProxSpace
2 Likes
ah so it was extracted directly to your Downloads folder, which is really a path like C:\users\youraccount\Downloads … not a good spot for this.
Start over.
Create a folder off C:\ called ProxSpace and extract the .7z file contents there, then run runme64 from in there.
To run it, instead of clicking on it, try opening a CMD window first… this is a command shell for Windows and it’s from this shell you launch ProxSpace to enter the proxspace linux pseudo-shell environment, and inside that pseudo-shell environment you run the proxspace client.
To get into the CMD shell, press the Windows key or click the Windows menu icon and type cmd and press enter. When you type cmd you should see something like this, with Command Prompt listed as the top app;
Once in there, you will need to “cd” or Change Directory to c:\ProxSpace… to do that type cd \proxspace and press enter. My proxspace folder is under a “working” folder, so you can see my process here;
Once you are in the proxspace folder, type runme64.bat and press enter. This should get you into the proxspace environment… eventually… after it’s done doing its first initial build…
Once in the proxspace environment, you will need to pull down the github repo, then compile the code pulled down using the make all command. After make finishes compiling the code, you can use pm3-flash-all to update your RDV4 to the version of firmware that you pulled from git and compiled. The client is also compiled, so after the firmware is updated on the RDV4 hardware you can run the matching client by just using the pm3 command.
Once the PM3 command is run successfully, you will now be operating in the PM3 client environment… so yes, you are wrapped in several layers here CMD>PROXSPACE>PM3.
This is a very quick overview of steps… if you want to follow the whole thing through, follow these steps;
However, because you are using the RDV4 then your Makefile changes will be different as the guide linked above is for the Proxmark3 Easy we sell. Still, all the other parts of the process are the same for the RDV4.
3 Likes
Those first two bunches of errors are just part of proxspace’s runme64.bat doing its thing, mine did that too but still resulted in a functional install
And those last two errors seem to be the same problem as before, which just means that it’s probably a real error and not due to the pre-compiled binaries you were using before
At this point you should have a usable install, I’d try the button trick again through proxspace:
Open runme64.bat
cd proxmark3
do the button trick
./pm3-flash-all
The script will warn you if you try to use a file path with spaces, I’ll have to do some testing on longer file paths, see if I can figure out when it might cause issues
1 Like
runme64.bat is a file, not a command
It’ll be in the unzipped folder, click it to run it
1 Like
(post deleted by author)