So, long story short, about 12 months ago the proxmark I bought from dangerousthings was working fine, all functional. fast forward to this morning, when starting the proxmark3 software, it does not connect, and using sudo dmesg | grep -i "usb" does not show any connection, nor does any serial port get opened on a windows device.
This puzzles me as all it has done for the last 12 months is sit inside of the box it came with, and now it is not working. I’m using the cable that was given to me with it, and have tried on 3 major operating systems (Arch linux, macos, and windows) all to no success.
What can i do at this point? The LED’s flash all colors, then stay red for a second, and the LED on the FPGA side simply stays white. Holding down the button while powering on the device leads to it having orange and green LED’s lit, alongside the white one, but still displays nothing in dmesg.
Hi, many thanks for the swift reply, but unfortunately, that does not solve my issue, as it still does not show up in dmesg nor does the proxmark3 utility automatically detect it and connect. If I hold down the button on the side, however, it does show up in dmesg, but still refuses to connect automatically with the proxmark utility. From here, should I simply build and flash a new version of the proxmark firmware onto it as per here?
I’d get new firmware, compile, plug pm3 in with button to get connection… then run pm3-flash-bootrom and let that finish successfully. Wait 5 seconds. Remove power. Plug in again with button down. Get connection. Run pm3-flash-fullimage. Wait 5 seconds. Unplug. Plug in normally. You should have connection. Run pm3 client.
Upon running the pm3-flash-bootrom tool, despite the fact that a dmesg event is generated confirming the connection, the tool is left at [=] Waiting for Proxmark3 to appear..., what now? (This occurs running it as su, and --list displays [!!] No port found)
I had the same issue and turns out my USB cable was power only with no data lines. Try to validate the cable does have data with another device. I got stuck on the issue for hours…