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.
Pages: 1
Hi all,
I have a very old proxmark bought in 2011 which is running firmware version r216. I want to upgrade it to the newest version but I'm not able to do so in Ubuntu (neither in windows).
I have compiled the code from github following the instructions on the wiki.
dmesg reports:
[ 136.296248] usb 3-2: new full-speed USB device number 2 using uhci_hcd
[ 136.416191] usb 3-2: device descriptor read/64, error -71
[ 136.640237] usb 3-2: device descriptor read/64, error -71
[ 136.856200] usb 3-2: new full-speed USB device number 3 using uhci_hcd
[ 136.976211] usb 3-2: device descriptor read/64, error -71
[ 137.200240] usb 3-2: device descriptor read/64, error -71
[ 137.416207] usb 3-2: new full-speed USB device number 4 using uhci_hcd
[ 137.828161] usb 3-2: device not accepting address 4, error -71
[ 137.884239] hub 3-0:1.0: unable to enumerate USB device on port 2
[ 138.528224] usb 3-2: new full-speed USB device number 6 using uhci_hcd
[ 143.816809] generic-usb 0003:9AC4:4B8F.0001: hiddev0,hidraw0: USB HID v1.00 Device [J. Westhues ProxMark-3 RFID Instrument] on usb-0000:00:1d.1-2/input0
Then after compiling the flasher I run:
$ cd hid-flasher
$ sudo ./flasher -b ../../bootrom/obj/bootrom.elf
(and it was correctly flashed)
Then I run:
$ sudo ./flasher ../../armsrc/obj/fullimage.elf
(and file not found) --> Don't know why it is not appearing after succesfull compilation.
Then I release the PM3_button I downloaded the elf file from the windows firmware and run
$ sudo ./flasher ../../armsrc/obj/fullimage.elf
But no answer. I have tried pressing the PM3_button and not pressing it, pluging, unpluging, etc.
The problem is that currently the proxmark has the red and orange/yellow led always on, and after 5/10 secs it seems to reboot, the red led that is alone i switched on and the off and back to the same state with the two leds.
Any help is more than wellcome to come back to live my proxmark. I really need it know
Offline
More information to see if it is not bricked.
When I plugged the proxmarx with the PM3_button pressed to my USB I get the follwoing in dmesg:
[ 192.840215] usb 3-2: new full-speed USB device number 4 using uhci_hcd
[ 193.013932] cdc_acm 3-2:1.0: This device cannot do calls on its own. It is not a modem.
[ 193.013975] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
When I plugged the proxmarx with the PM3_button not pressed to my USB I get the follwoing in dmesg:
[ 204.836251] hub 1-0:1.0: unable to enumerate USB device on port 4
Offline
did you edit the blacklist?
Offline
What for should I blacklist?
I've include: "blacklist cdc_acm" in the /etc/modprobe.d/blacklist.conf an then reboot my system. After that I've run again pressing the button when plugin:
$ sudo ./flasher ../../armsrc/obj/fullimage.elf
Nothing happens... I only see dots after the waiting for proxmark.
I have also followed what is in this link (https://code.google.com/p/proxmark3/wiki/Linux) about the udev rules, and still getting the same behaviour, dots appearing and the device is not recognized.
No idea. The two leds are ok but then nothing works. What I think is the reboot of the device is after 15 seconds.
What should I do? Should I run the flasher first, should I keep always the button pressed?
Thanks
Offline
Normally you need to specify the port.
linux: flasher.exe /dev/ttyACM0 armsrc/obj/fullimage.elf
Regarding the blacklisting:
you need to blacklist proxmark for modem-manager - see wiki for more details:
http://code.google.com/p/proxmark3/wiki/Linux
Offline
According to linux flahser help there is no option to include the port.
Concerning the blacklisting, as I said on my previous replay I have already tried the info in this link.
Any other idea?
Offline
I've done it!!!! The problem was there are two flashers: the hid-flasher and the new flasher. I installed the bootroom with the old and then I was trying to update also with the old, while it has to be the new one
now I'm able to connect to proxmark console and hw info returns os: master/v2.2.0-52-g5d01f50-suspect 2015-08-27 so it seems it is the new one.
Thank you for your help.
Offline
did you ever figure out the solution to this, i have the exact problem with a newer model.
Offline
I'm having the same problem, the red and orange led just stay on, if I run the arm the dots just keep going. If you can let me know exactly what you did to solve your problem that would be greatly appreciated.
Offline
In my last post I introduced the solution, at least mine.
The problem was that I tried to use the hid-flasher to flash both the bootroom and the firmware. However, I then realized that after flashing the bootroom the proxmark is no longer behaving as before, but as a USB ACM device. Then you have to use the normal flasher (just in the directory above the hid-flasher) to flash the latest firmware (not the bootroom, the fullimage one).
This was my problem, hope it helps you. BTW do not forget to press the PM3 button and release it.
Offline
Pages: 1