Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
You are not logged in.
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Sorry to bother hard-working developers but I don't see a troubleshooting forum.
I'm not even a user. I just want this off my plate.
I have, or rather my boss has, a Proxmark 3 that he wanted updated to the latest firmware
last year. His Win7 box was having trouble seeing the device or running the software. I
don't remember.
I grabbed a .pdf on updating the firmware and set about it. The current version was 672. I
got as far as the bootrom and then I couldn't get the flasher to work anymore.
The crisis passed before I could figure it out and so it sat in my desk till now.
Now, he needs it again and I'm looking into how to fix it. Remember, I touched it last.
The last version of the proxmark3 utility that works is r486 (Win & Linux).
The "hw version" command gives me this information.
Connected units:
1. SN: ? [bus-0/\\.\libusb0-0001--0x9ac4-0x4b8f]
proxmark3> hw version
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: svn 671 2013-03-07 17:12:17
#db# os: svn 215 2010-01-14 21:43:26
#db# FPGA image built on 2009/ 8/28 at 23:49:10
The "hw tune" command gives me an "unrecognized command 00000401" error.
So, I probably need to get all of the firmware on the same page.
The one Linux version of the flasher that I've got (r486) does not see the device unless I
let go of the button. Then it finds the device; recommends that I update the bootloader;
starts flashing; errors (expecting ACK) on writing block 0.
Doesn't matter if I try to write bootrom, whole image, FPGA, or OS.
Under Windows, the device is never found by the flasher with the button pressed. The driver
won't upgrade to anything with the button pressed. Just looks like an unsupported COM4 in
device manager.
Is there a way out of this mess? Or am I in the market for a JTAG programmer?
Thank you for your time.
Offline
These are my two go-to threads when I need to install drivers on a new machine or update the PM3 firmware.
http://www.proxmark.org/forum/viewtopic … 4581#p4581
http://www.proxmark.org/forum/viewtopic.php?id=1562
Hope they help
Last edited by gbhuk (2014-10-16 04:35:16)
Offline
http://www.proxmark.org/forum/viewtopic.php?id=1561
Rules reply in this thread should sort you out, it looks like you have a CDC based bootloader, and HID firmware, hold the button down when plugging in to force it to enter the bootloader, install the driver.inf for this comport, then use the new flasher to flash the firmware.
You can get precompiled firmware/old and new flasher/etc here:
http://www.proxmark.org/forum/viewtopic.php?id=1562
Offline
Thank you both for responding so quickly.
I think I've searched this forum on every keyword that I've seen come back from this device - so I've seen (and tried) those threads before.
The proxmark shows up in my Device Manager under:
>libusb-win32 devices
.....ProxMark-3 RFID Instrument
Which, I believe, is correct until the rest of the firmware can be updated.
With the button pressed; the proxmark comes up under:
>Other Devices
.....Unknown Device
And then I can install any driver I want but Win7 tells me there's "The folder you specified doesn't contain a compatible software driver..." on every driver I've tried (r486, r651, 672, 756, 0.0.5, flip-libusb-signed-driver)
I've also tried all of the corresponding flashers and scripts for those releases. The device never shows up in USB to be flashed - except in Linux, but that has other errors (above).
I've tried the driver that "rule" linked to. It's the same as what's in the "master" release on github, though, isn't it? Both drivers (button pushed in and not) give the same "The folder you specified doesn't contain..."
I think I've tried every combination of driver/flasher/button pressing that's ever worked. Halfway hoping that this thing would brick so I could quit trying.
I do appreciate the help, though. And your timeliness. I'm afraid I really will brick this thing and then get THE ANSWER the next day.
Offline
And so it took a Bus Pirate with v6.1 of the firmware to re-write the Proxmark firmware.
And then I was left with the same problem - No Windows drivers would install.
It took another Windows box that hadn't connected to the Proxmark before to install the correct drivers and verify that the Bus Pirate flash was successful.
At lease we can use the Proxmark now. Thank you everyone that gave this thread a look.
Offline
mobill76, if you're in the Netherlands, would you be able with assisting me to unbrick my PM3? thanks a lot!
Offline