Ok power off and on again and leave normal running (don’t press the button)… in proxspace run
./pm3 --list
Don’t run this until you confirm the com port is visible in device manager
1 Like
It won’t let me enter any commands while it says waiting for proxmark to appear so I have to just close out proxspace and when I do that, I have to start the whole setup over again
1 Like
Try Ctrl+c, see if that drops you back into the terminal
You shouldn’t have to do anything other than open proxspace again if it closes…
Could be a permissions issue.
Windows only allows one program to access a com port at a time. Make sure that if you’re using the terminal to flash, you don’t have any other programs running trying to connect to it.
If that doesn’t work, have you tried running from an elevated command prompt?
1 Like
Also, not sure if I’m missing something, it’s running iceman already, but you’re trying to reflash it?
1 Like
This makes sense… the hardware is what tells windows it is a com port device, it’s got nothing to do with proxspace.
When you say always… is it there when you don’t have the proxmark plugged in? Or does it disappear when you unplug the proxmark?
1 Like
It’s brand new just first time install
1 Like
It disappears when proxmark is unplugged and reappears when I plug it back in.
2 Likes
It looks like its working as it should. Make sure you try the things I suggested above. Though you should be able to use it as is without installing iceman on it, Amal did that for you.
1 Like
It’s possible the firmware push failed … you know how when you’re doing the same thing 100+ times in a row you can just zone out … I might have missed some or missed an error. It definitely should be “seen” by the flashing utility.
We may have to explore a replacement if it doesn’t get sorted… but the next step I think might be to set up a call like google meet or something with screenshare
2 Likes
Yet again, service above and beyond.
DT sets the example for all companies to aspire to.
Thanks Amal.
6 Likes
Yeah, really appreciate it what day and time works best for you. My work schedule is kind of weird. And what time zone are you on?
1 Like
He’s on the West Coast of the United States.
You can tip on his profile and it will show you his current time
He’s 3 Hours behind you
3 Likes
I’ll DM you a calendar scheduling link
2 Likes
Ok, so this is the oddest thing I’ve ever seen. After an hour long Google Meet with screen sharing, we got things working… sort of.
- ProxSpace was removed and re-deployed from scratch to ensure no funny business was going on.
- The latest iceman branch was cloned and compiled.
- Within ProxSpace, the /dev listing showed the ttyS0 port which was confirmed to appear and disappear when the Proxmark3 was plugged in and unplugged.
- The
~/proxmark3/pm3script was simply unable to detect the port. - Using
~/proxmark3/client/proxmark3.exe -p COM1 --flash [etc]we were able to update the bootloader and fullimage on the hardware. - Even after updating the bootloader and image to current, the pm3 script could not detect / find the proxmark, and
pm3 --listreturned “No ports detected”. - Launching the client directly via ~/proxmark3/client/proxmark3.exe COM1``` did work though, and the client ran as expected.
No idea wtf is going on… but it seems like a potential issue with the pm3 port detection script? We even tried running proxspace as administrator to no avail.
3 Likes
That was going to be the route i was going to go, specifying port specifically to launch. I ran into that before i found your guide last year and had to specifically call the port each time i ran it.
I am willing to bet it is specific to some software restrictions on his computer, not necessarily the scripts.
Did you have him run everything as administrator?
I can’t thank you enough for you taking the time out to help me with this issue. Dangerous things has the best customer service out of any company I’ve ever dealt with.
4 Likes
yep ran the whole cmd dos box as admin, then launched proxspace within that and still.
we even disabled all windows exec and memory protections, windows defender, etc. the computer was also basically new with nothing funky on it that i could tell. the only thing was there was a flipper driver installed, but i don’t see how that could cause the issue.
the only reason i didn’t think so was that proxspace was seeing the com device as /dev/ttyS0 … if there was a restriction, that port should not be visible.
1 Like
In the residential consumer grade PC’s i have seen some of the most ridiculous stuff.
I am imagining something that is allowing you to see the device, but not allowing the device to interact with the CMD layer.
Did you only uise CMD or did you try with powershell as well?
1 Like