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
Hello,
I successfully flashed and used the r651 firmware revision (mifare cloning etc. I love this awesome RFID tool), I wanted to test the new 672 firmware and now I'm locked with this version :
Connected units:
1. SN: ChangeMe [bus-0/\\.\libusb0-0001--0x9ac4-0x4b8f]
proxmark3> hw ver
#db# Prox/RFID mark3 RFID instrument
#db# bootrom: svn 671 2013-03-07 17:12:17
#db# os: svn 651-suspect 2013-01-25 15:52:19
#db# FPGA image built on 2012/ 1/ 6 at 15:27:56
proxmark3>
I can't flash anymore:( New flasher / Old flasher... I never show the virtual com port - WINDOWS 7 64bits.
C:\>D:\A\RFID\pm3-bin-r651\client\flasher.exe -b D:\A\RFID\pm3-bin-r651\arm\boot
rom.elf
Loading ELF file 'D:\A\RFID\pm3-bin-r651\arm\bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x000017b0->0x000017b0) [R X] @0x294
Waiting for Proxmark to appear on USB...
Connected units:
1. SN: ChangeMe [bus-0/\\.\libusb0-0001--0x9ac4-0x4b8f]
Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on USB.........................................................................................(for ever)
I'm bricked:( - Proxmark3 OS functions are now inconsistent and I can't rollback my bootloader:(
Please help
Pascal
Offline
If you have the new (CDC) bootrom
First, hold the button and plug in your proxmark. Now, keep holding the button and go to the device manager.
If it shows a "unknown device", please install using this driver.inf file.
You should see now the proxmark in the list of the (com)ports
-> start the new flasher:
windows
flasher COM* -b bootrom.elf (replace * with port number)
flasher COM* fullimage.elf (replace * with port number)
unix
flasher /dev/tty* -b bootrom.elf (replace * with port name)
flasher /dev/tty* fullimage.elf (replace * with port name)
If you have the old (HID) bootrom
First, hold the button and plug in your proxmark. Now, keep holding the button and go to the device manager.
You should see the proxmark in the list of HID devices.
-> start the old flasher:
flasher -b bootrom.elf
flasher fullimage.elf
Offline
Thanks a lot roel, this is exactly what I need, the INF file for bootloader com port:D
I flashed succefuly all
the automatic reboot/flash and com port are awesome feature:)
======================================
FLASHING fpgaimage.elf, please wait...
======================================
Loading ELF file '..\firmware_win\fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0000a4bc->0x0000a4bc) [R ] @0xb4
1: V 0x00110000 P 0x00110000 (0x00012656->0x00012656) [R X] @0xa570
2: V 0x00200000 P 0x00122658 (0x000029b8->0x000029b8) [RWX] @0x1cbc8
Note: Extending previous segment from 0x12656 to 0x15010 bytes
Note: 0x2-byte hole created
Waiting for Proxmark to appear on USB... Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on USB........ Found.
Flashing...
Writing segments for file: ..\firmware_win\fullimage.elf
0x00102000..0x0010c4bb [0xa4bc / 83 blocks]....................................
............................................... OK
0x00110000..0x0012500f [0x15010 / 169 blocks]..................................
................................................................................
....................................................... OK
Resetting hardware...
All done.
Have a nice day!
Appuyez sur une touche pour continuer...
Offline
Outch I get some inconsistent result with this version
A csave on my magic chinese 1k, there is no 44444444 on this card (and a nested give me a error like "0 keys returned by proxmark" !
I check more tomorrow
44444444b288040047ba141551301210
44444444000000000000000000000000
44444444000009380938093809380938
44444444a4a561e789c1b0b1b2b3b4b5
44444444000000000000000000000000
44444444000000000000000000000000
44444444000000000000000000000000
44444444a4a578778869b0b1b2b3b4b5
44444444000000000000000000000000
44444444000000000000000000000000
44444444000000000000000000000000
44444444a4a578778869b0b1b2b3b4b5
44444444000000000000000000000000
44444444000000000000000000000000
44444444000000000000000000000000
44444444a4a578778869b0b1b2b3b4b5
44444444000000000000000000000000
44444444000000000000000000000000
44444444000000000000000000000000
44444444a4a578778869b0b1b2b3b4b5
44444444000000000000000000000000
44444444000000000000000000000000
44444444000000000000000000000000
44444444a4a578778869b0b1b2b3b4b5
44444444000000000000000000000000
44444444000000000000000000000000
44444444000000000000000000000000
44444444a4a578778869b0b1b2b3b4b5
44444444000000000000000000000000
44444444000000000000000000000000
44444444000000000000000000000000
44444444a4a578778869b0b1b2b3b4b5
44444444000000000000000000000000
44444444000000000000000000000000
44444444000000000000000000000000
44444444a4a578778869b0b1b2b3b4b5
44444444000000000000000000000000
44444444000000000000000000000000
44444444000000000000000000000000
44444444a4a578778869b0b1b2b3b4b5
44444444000000000000000000000000
44444444000000000000000000000000
44444444000000000000000000000000
44444444a4a578778869b0b1b2b3b4b5
444444440005791500002100040045a3
444444440208eeee0000000000000000
444444443b6300010000000000000000
44444444a4a51e11ee5a285a454785ec
44444444000000000008000000000000
4444444400000000dddddddddddddddd
44444444dddddddddddddddddddddddd
44444444a4a50f00ff868346470f0708
44444444dddddddddddddddddddddddd
44444444dddddddddddddddddddddddd
44444444dddddddddddddddddddddddd
44444444a4a50f00ffea82a6dc40f1bc
44444444dddddddddddddddddddddddd
44444444dddddddddddddddddddddddd
44444444dddddddddddddddddddddddd
44444444a4a50f00ff5ad4bd89adec74
44444444dddddddddddddddddddddddd
44444444dddddddddddddddddddddddd
44444444016ce400000000004d494300
44444444a4a54b44bb5a702e78333960
(corrupted read inside an EML)
Offline
Yes revision 672 can't do a Nested on my old classic 1k, the revision 651 work prefectly... But I want the com port also in OS, I must install development environment for last updates...
Offline
Please try to locate the code/lines that is generating problems, then I could try to fix it.
Offline
If you have the new (CDC) bootrom
First, hold the button and plug in your proxmark. Now, keep holding the button and go to the device manager.
If it shows a "unknown device", please install using this driver.inf file.You should see now the proxmark in the list of the (com)ports
-> start the new flasher:
windows
flasher COM* -b bootrom.elf (replace * with port number)
flasher COM* fullimage.elf (replace * with port number)
unix
flasher /dev/tty* -b bootrom.elf (replace * with port name)
flasher /dev/tty* fullimage.elf (replace * with port name)If you have the old (HID) bootrom
First, hold the button and plug in your proxmark. Now, keep holding the button and go to the device manager.You should see the proxmark in the list of HID devices.
-> start the old flasher:
flasher -b bootrom.elf
flasher fullimage.elf
Been gone for a while and today I updated my proxmark to the latest revision unaware that there was a new USB bootloader.
Flashed with the fpgaimage and osimage.elf and later when I tried to flash the bootrom neither the old or the new flasher were able to do it. It just said "Waiting for proxmark to reappear on USB". After some experimenting it somehow wrote 2 blocks to the bootloader and then the Waiting-message appeared again. Nothing happened so I disconnected it. Now all LEDs light up when I plug it in and Windows says unrecognized device. Do I need to JTAG it now?
Offline
Pages: 1