never tried powershell… never considered it… might try in the future though.
you might not be wrong about there being some kind of permission / restriction issue but if that was the case, then running the client directly specifying COM1 should not have worked for flashing or client interop
Had a similar problem but not with a fresh install. factory reset my laptop and reinstalled everything but I’m also stuck on waiting for proxmark. used the commands posted here and i can get it to work via your direct launch instructions but now it doesn’t bump files into a mifare1k fob that i was using previously without issue. i did manage to update it also using the flash command you posted but still says i don’t have up to date firmware
What happens when you try to flash all? Screenshot?
That’s kind of a strange way to approach the flashing… from the proxmark3 folder just run the script ./pm3-flash-all and it should flash the bootloader and the firmware.
Hmm ok what about holding the button down, plugging in the USB, keep holding while you run the script… then release once the firmware starts loading?
doesn’t do anything. Held it until i got a popup from windows saying it no longer recognizes the device. still stuck on waiting for proxmark
i can use the proxmark and copy the schlage 9691t keyfob but with some extra info that didn’t pop up before. I can’t dump the files into another fob even though it says it does.
You might try setting the port manually with the flashing script like:
./pm3-flash-fullimage -p <PORT>
You can’t do anything reliably with the proxmark until the bootloader, firmware, and client all match. You will get random and unreliable results until this is solved.
I have a slightly different approach to most others, but your choice if you want to follow it.
Rather than fucking around and backwards and forwards. (I personally find a fresh build faster than a fault find)
and yes, I know you’ve just done this but I suggest you delete EVERYTHING including folders and I start Fresh.
Follow the guide through I will link shortly.
Go through step-by-step and stop when you get an error. If you do (you shouldn’t) then reply to this post.
It is easier to diagnose as you work through.
As long as you followed the guide exactly everything should work
Here’s my abridged guide, Stolen from, but linked to Amals very thorough guide.
I have used my own guide a few times and never had an issue.
Follow it to the letter, and you SHOULD be fine.
FYI
The Button Trick
First error when running runme64.bat but still got green pm3
Was still stuck waiting on proxmark to appear but managed to flash bootrom and fullimage using the command [Aoxhwjfoavdlhsvfpzha] posted ./pm3-flash-fullimage -p COM1 after flashing bootrom it reverted to COM3
pm3 didn’t work after so had to use the command amal posted ~/proxmark3/client/proxmark3.exe COM3
but this is how i ended.
update. got it to work with the previous version 3.10 instead of the latest one. its stuck on waiting for proxmark3 to appear even with the button trick. what did work is just adding the -p COM it appears under device manager when flashing and launching the client directly via ~/proxmark3/client/proxmark3.exe COM1. Managed to autopwn Schlage 9691t fob and dump it into a mifare1k fob
New PC so tried to install there. I’m also getting stuck on attempting to flash . On Windows 11, rather vanilla <haven’t installed any extra security software that isn’t bundled with the OS>. When I specify the COM I can get things reading, but I do get the incorrect version red warning.
I’ve run out of troubleshooting time for the day, so I’ll need to pick it up next week. Will clear everything and try the Pilgrimsmaster walkthrough instead of the DT video walk through.
Update:
Completed the steps again via the walkthrough with the same-ish results.
Note: On Pilgrimsmaster’s steps it’s missing the copy of the make sample file to the make file.
Using:
./pm3-flash-fullimage -p COM3
I was able to successfully flash the image.
Using:
~/proxmark3/client/proxmark3.exe COM3
I can launch pm3.
Without specifying the port I get stuck with the waiting message. It was working on my previous PC, which was Windows 10. This one is Windows 11 pro, a fresh install with only a brother printer, Office, chrome, 7zip, and dupeGuru installed prior to starting this.
Alright, so I started taking things apart.
./pm3 was getting stuck in this function:
function get_pm3_list_Windows {
N=$1
PM3LIST=()
echo "In Windows"
# Normal SERIAL PORTS (COM)
for DEV in $(wmic /locale:ms_409 path Win32_SerialPort Where "PNPDeviceID LIKE '%VID_9AC4&PID_4B8F%' Or PNPDeviceID LIKE '%VID_2D2D&PID_504D%'" Get DeviceID 2>/dev/null | awk -b '/^COM/{print $1}'); do
DEV=${DEV/ */}
#prevent soft bricking when using pm3-flash-all on an outdated bootloader
if [ $(basename -- "$0") = "pm3-flash-all" ]; then
line=$(wmic /locale:ms_409 path Win32_SerialPort Where "DeviceID='$DEV'" Get PNPDeviceID 2>/dev/null | awk -b '/^USB/{print $1}');
if [[ ! $line =~ ^"USB\VID_9AC4&PID_4B8F\ICEMAN" ]]; then
echo -e "\033[0;31m[!] Using pm3-flash-all on an oudated bootloader, use pm3-flash-bootrom first!"
exit 1
fi
fi
PM3LIST+=("$DEV")
if [ ${#PM3LIST[*]} -ge "$N" ]; then
return
fi
done
The command that is failing is in the for DEV in statement attempting to use wmic to get the com port. WMIC is no longer natively installed with windows 11 24H2, and the error stream is getting sent to dev null so you don’t even get the info on where things are failing.
So I installed wmic.
Add-WindowsCapability -Online -Name WMIC~~~~
Statement now gets the correct COM port and I no longer get an error. Not sure where we want to add a check for WMIC, not my project, but it should be done either in there or at least a note added to the install steps. This is likely going to occur many more times as folks are upgrading.
Wow great work!
@Iceman … something to consider
Indeed good find. I heard some rumour that WMIC isn’t installed default.
Making our com port enumeration a bit more complicated.
Will need to figure out what a Win11 24H2 and later edition has installed by default so we can use it. Preferably something that is also default on older versions of Windows.
A quick check in the changelog and I find my own first change for WMIC to powershell. Seems like the “pure” windows part, like for proxspace etc didn’t get that fix…
inside “pm3” shell script,
would you mind testing one thing?
line 499: elif [[ "$HOSTOS" =~ MINGW(32|64)_NT* ]]; then
line 500: GETPM3LIST=get_pm3_list_Windows
change line 500 to,
GETPM3LIST=get_pm3_list_WSL
That would exclude the WMIC path to be executed and only use the Powershell path.
I’ll try tomorrow.
Should I uninstall wmic prior?
I pushed a proper fix,
if you uninstall the WMIC and we can see if it works.