From what I can tell you are trying use the proxmark on Windows and using WSL (Windows Subsystem for Linux). This is how I also mainly use my proxmark also.
You still need to install the drivers in Device Manager then it should be detected in WSL. I have had to uninstall the drivers/device completely in device manager before and reinstall the drivers.
Since you have a PM3 Easy, you need to specify before compiling the firmware that its for the Easy. By default its expecting an RDV4 and could cause problems later.
Did you ever get the PM3 Easy working (be it on stock or Iceman fork)?
Are you in the DT Discord? I would be able to provide some more instant feedback and guidance
Currently we are using Proxspace which I think is different. I am just following a forum post I had seen a while back for the config. Is WSL the preferred way?
I personally prefer WSL since its Linux based and I have some Linux knowledge. I feel like it also removes any of the common issues with running a proxmark on Windows.
I originally tried it under native Windows and had nothing but headaches. I eventually got it working but would also run into more issues as I tried to do more.
Decided to give WSL a shot since I already have it installed and use it for other things. Got everything setup and it worked 1st try. Since then Ive had minor errors and easily corrected them.
The guide you linked is the official guide for the Iceman fork, which I have used several times. It does have install/compilation instructions for WSL further down.
Its up to yourself what you’re happy to use for the proxmark for the foreseeable future. Didnt mean to muddy the waters with mentioning WSL.
Still wondering why you haven’t just specified a COM port yet.
If they are using WSL then COM ports wont work since the ports are translated into ttySx.
If they are using Proxspace then a COM port should be specified.
From the screenshot in the original post it looks like WSL thus specifying a COM port wouldn’t work.
Yes, but if they are trying to use Proxspace via WSL then a specifying a COM port still wont work. Even since they can see /dev and ttySx ports suggests they are using WSL.
If they were to use Proxspace on a Windows shell, then a COM port should be specified but this doesn’t look to be the case.
Try the easy flashing guide I posted above, I had a lot of issues with ProxSpace communicating with the PM3E. This method is a simple unzip and batch file.
One other question - which USB port do you have it plugged into? A few folks have accidentally plugged it in the side port, but you’ll wanna use the bottom port.
I have, also as mentioned in one of my earlier posts I even tried the PM3-FLASH-ALL which should attempt to do any device on any COM if I am reading what that command does correctly.
I will try the easy guide and see if I have any luck. If not maybe I can get in the discord this afternoon or over the weekend with @Jirvin and whoever else wants to help out and see if we can get it squared away. I appreciate everyone helping out so far.
SUCCESS!! Used the one on the Discord and it worked right away. Now to figure out why the other method I was using did not work, because I am not letting it win
Glad you got it working!
The main reason I was mentioning WSL is that some PM3 Easy’s have less memory and dont support the Iceman fork too well. On WSL/Linux you can specify that, while compiling, to do it for an Easy (specifically a more “generic” device).
I am on the discord (same username) if you want to switch/try WSL just let me know. Also happy to help with some cloning queries (I mostly know Mifare stuff).
