Im totally new to all RFID research and im currently setting up my proxmark3 rdv4. I keep getting stuck at this step even though the proxmark3 rdv4 is connected.
pm3 ~/proxmark3$ ./pm3-flash-all
[=] Waiting for Proxmark3 to appear…
all help is appreciated, thanks!
Are you on Windows?
Did you try The Button Trick?
You may also try individually flashing the bootrom and then the fullimage
can you describe the way you’re flashing, are you on a windows system using proxspace? WSL? virtual machine?
if you’re on linux have you removed modemmanager?
given yourself accessrights to dialout?
open Device Manager on Windows to ensure the device is not appearing as an alternative COM port when it boots into the bootloader
sorry for the late reply, got busy at work. all it says is access denied
i’m on windows, i think i pressed the button too many times because the red LED light is on at the letter A
Can you tell us a bit more about what you’ve tried so far?
What set-up guide are you following?
Following this one Getting started with the proxmark3 easy and every time i type “./pm3-flash-all” it says “[=] Waiting for Proxmark3 to appear…”. I tried the button trick but i definitely messed up because there’s only one LED light on when i plug it in.
Unfortunately I don’t have too much experience with the PM3 on windows, but if I were in your shoes at this point I would remove all my PM3 files and start over from scratch following this guide:
thanks for the help
If you have any more issues, I’ll be glad to offer what little help I can 
And I’m sure others on the forum who have setup the PM3 more than me will chip in again as time permits
And if they don’t I’ll bug 'em until they do
hey I am currently using the proxmark4 rdv4. and I am having trouble connecting to windows 11. I followed all the steps correctly. and i’m still have trouble. my device doesn’t detect on the cmd on flash or image. downloaded the proxmarkbuilds.org as well. @Aoxhwjfoavdlhsvfpzha
let’s start with the basics… when you plug in your RDV4 does it show up in Device Manager as a COM port device?
If not, then try a new USB cable… you might be using a power only cable meant for charging but has no data lines.
What steps are those?
Ah interesting… ok… Well, now it’s time to try the button trick. Hold the button in as you plug it in and keep it held. The bootrom flasher should be able to find it. You may notice the com port is different as well but that’s fine for this stage
At this point you might need to reach out to the RRG group (makers of the RDV4) for support.
One last thing to consider… have you tried using the ProxSpace method to pull down the latest Iceman branch software, compiling that, and trying to flash the freshly compiled bootrom and firmware?
You could try the script I have here (Windows Method #2):
It’ll install ProxSpace for you mostly automated
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…
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…
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
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
