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.
Hello,
1. Initialy my PM3 was running the following firmware:
Prox/RFID mark3 RFID instrument
bootrom: master/v2.3 2016-09-19 20:28:38
os: master/v2.3 2016-09-19 20:28:38
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at 9: 8: 8
uC: AT91SAM7S512 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 512K bytes. Used: 183707 bytes
581 bytes (65%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
2. Then I build the iceman fork from: git clone https://github.com/iceman1001/proxmark3.git
3. At first managed to flash the bootrom, but fails to flash the fullimage. The firmware on my PM3 is now:
Prox/RFID mark3 RFID instrument
bootrom: iceman/master/v1.1.0-2275-g72e53b09-dirty-unclean 2017-09-20 18:21:02
os: master/v2.3 2016-09-19 20:28:38
LF FPGA image built for 2s30vq100 on 2015/03/06 at 07:38:04
HF FPGA image built for 2s30vq100 on 2015/11/ 2 at 9: 8: 8
uC: AT91SAM7S512 Rev B
Embedded Processor: ARM7TDMI
Nonvolatile Program Memory Size: 512K bytes. Used: 183707 bytes (35%). Free: 340
581 bytes (65%).
Second Nonvolatile Program Memory Size: None
Internal SRAM Size: 64K bytes
Architecture Identifier: AT91SAM7Sxx Series
Nonvolatile Program Memory Type: Embedded Flash Memory
3. Now I can not seem to flash any bootrom or fullimage to the PM3.
3.1.
Trying to flash Bootrom, i get this:
$ client/flasher.exe com19 -b bootrom/obj/bootrom.elf
Loading ELF file 'bootrom/obj/bootrom.elf'...
Loading usable ELF segments:
0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
1: V 0x00200000 P 0x00100200 (0x00000c78->0x00000c78) [R X] @0x298
Waiting for Proxmark to appear on com19....................................
....... Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on com19........................... Found.
Note: Your bootloader does not understand the new START_FLASH command
It is recommended that you update your bootloader
Flashing...
Writing segments for file: bootrom/obj/bootrom.elf
0x00100000..0x001001ff [0x200 / 1 blocks]
The PM3 dissappears from COM19 and appears under libusb-win32 devices. The red and yellow leds on the PM3 are on.
3.2.
Trying to flash the fullimage, i get this:
$ client/flasher.exe com19 -b armsrc/obj/fullimage.elf
Loading ELF file 'armsrc/obj/fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0002bfa0->0x0002bfa0) [R X] @0x94
1: V 0x00200000 P 0x0012dfa0 (0x00001914->0x00001914) [RW ] @0x2c034
Note: Extending previous segment from 0x2bfa0 to 0x2d8b4 bytes
Waiting for Proxmark to appear on com19.......... Found.
Entering bootloader...
(Press and release the button only to abort)
Waiting for Proxmark to reappear on com19.................
The PM3 dissappears from COM19 and appears under libusb-win32 devices. The red and yellow leds on the PM3 are on.
4. Did i just damage my PM3 or what is wrong with my PM3?
Please help!!!!!!
Last edited by CoolLink (2017-12-12 10:59:57)
Offline
Any input on this problem, please!!!
Can not seem to update any bootloader or fullimage. I even ordered a Bus Pirate V3.6a in case I bricked my PM3.
Please assist anyone with what might be the problem.
Offline
force the windows device to load the correct CDC driver and check for com port changes during a flash.
Also use the latest official github code not iceman's if you don't know exactly what you are doing.
Offline
Hi @marshmellow
me same, until mid of last month, no problem. These days, downloded recent version of iceman fork, then tried to update firmware, com port not recognized. downloaded github old version (Aug version) , same result.
when flashing, at first sw found com port, then srarting boot loader, failed, waiting for com port...
tried it several times, unplug then plug pm3, used this and that version, maybe mixed something, now pm3 showed not working well result.
Is there any command or sw to flush all then upload stable version?
About driver, no problem from the beginning, this week suddenly usb problem how can I make Windows get correct driver, not for pm3 driver (not one in Window Driver)?
Offline
Did you read http://www.proxmark.org/forum/viewtopic.php?id=4904 ?
Offline
Hi, i have the same problem after flash bootloader from iceman.....
Offline
I did test the latest iceman fork and it seems the bootloader does really brick the pm3 (or at least prevent it from flashing new firmware). When entering flash mode, Windows does not recognise it as pm3, instead it is a unknown device with code 43(no pid or vid values so pm3 driver won't load).
Last edited by gator96100 (2017-10-07 10:56:06)
Offline
Yes gaor96100, any solution ?
Offline
Don't use Iceman's fork unless you follow closely his changes and are capable of JTAG recovery of your device.
Offline
I did manage to flash a new bootloader without using my Bus Pirate. This error only exists on Windows, use Linux to flash the official bootloader.
Last edited by gator96100 (2017-10-07 14:11:07)
Offline
Yes, I'm sorry to state that the windows part is quite unstable. The linux part should be untouched.
I'm using jtag as it is right now.
Offline
Hi with linux, same problem.... flash is impossible....
Last edited by kevin2008 (2017-10-07 20:46:17)
Offline
Hi guys, any update on this issue? Im stuck too,.
@Gator, How did you manage to flash it under linux? Can you please advice?
Offline
force the windows device to load the correct CDC driver and check for com port changes during a flash.
Also use the latest official github code not iceman's if you don't know exactly what you are doing.
Thanks marshmellow--- it worked. Sorry for replying late. As marshmellow advised above, the solution is to force the PM3 to load the correct CDC driver.
1. clone the latest official github code (https://github.com/Proxmark/proxmark3)
2. connect the PM3, under device manager the com# port should appear
3. Flash the bootrom from the compiled official github code.
4. The PM3 will switch from com# port to the unknown device (both led's will be on)
5. Windows will start searching for the drivers of the PM3.
6. Install the drivers from the official github code repository folder
7. PM3 will appear again as com# port under device manager (unplug & plug PM3)
8. Restart the bootrom flash, it will go through
9. Repeat the same steps for flashing the fullimage (if the PM3 appears as unknown device again)
I tried this steps on a separate computer and it worked.
Thanks.
Offline
hello,everyone,I think that my pm3 just got bricked,after updating firmware from precompiled Iceman,s
firmware,after that pm3's four light led on,whether I press and hold the button or not,also on device manager,not detecting pm3 at all,I've searching all the forum,but until now no luck,I need help to debrick my pm3 back to life,any help will be much appreciated...
Offline
Please Start a new topic.
Offline
Hi,marshmellow,I don't now how to start a new topic,can you show me how to start a new topic.
Offline
Just click on the proper section and look for the post new topic link (usually on the right.)
Offline
Thanks I will try..
Offline