Proxmark3 Easy first timer problems (bricked already?)

Hey all. I was setting up the PM3 using the instructions here.

Ran the following:

pm3 ~/proxmark3$ ./pm3-flash-all
[!] Using pm3-flash-all on an oudated bootloader, use pm3-flash-bootrom first!

so I ran:

pm3 ~/proxmark3$ ./pm3-flash-bootrom
[=] Session log C:\ProxSpace\pm3/.proxmark3/logs/log_20220701.txt
[+] About to use the following file:
[+]    C:\ProxSpace\pm3\proxmark3\client\../bootrom/obj/bootrom.elf
[+] Loading ELF file C:\ProxSpace\pm3\proxmark3\client\../bootrom/obj/bootrom.elf
[+] ELF file version Iceman/master/v4.14831-706-g45ea60c92 2022-06-30 19:33:58 c48a213a1

[+] Waiting for Proxmark3 to appear on COM3
[|] 59 found
[+] Entering bootloader...
[+] (Press and release the button only to abort)
[+] Waiting for Proxmark3 to appear on COM3
[-] 47 found
[!!] ====================== OBS ! ===========================================
[!!] Note: Your bootloader does not understand the new CMD_BL_VERSION command
[!!] It is recommended that you first update your bootloader alone,
[!!] reboot the Proxmark3 then only update the main firmware


[!!] ------------- Follow these steps -------------------

[!!]  1)   ./pm3-flash-bootrom
[!!]  2)   ./pm3-flash-all
[!!]  3)   ./pm3

[=] ---------------------------------------------------

[=] Available memory on this board: UNKNOWN

[!!] ====================== OBS ! ======================================
[!!] Note: Your bootloader does not understand the new CHIP_INFO command
[=] Permitted flash range: 0x00100000-0x00140000
[+] Loading usable ELF segments:
[+]    0: V 0x00100000 P 0x00100000 (0x00000200->0x00000200) [R X] @0x94
[+]    1: V 0x00200000 P 0x00100200 (0x00000d1c->0x00000d1c) [R X] @0x298

[+] Flashing...
[+] Writing segments for file: C:\ProxSpace\pm3\proxmark3\client\../bootrom/obj/bootrom.elf
[+]  0x00100000..0x001001ff [0x200 / 1 blocks]
. ok
[+]  0x00100200..0x00100f1b [0xd1c / 7 blocks]
....... ok

[+] All done

[=] Have a nice day!

and now I have a seemingly bricked proxmark3 as it no longer detects on COM3. What are my options here? Do I have to mess with JTAG?

pm3 ~/proxmark3$ ./pm3-flash-all
[=] Waiting for Proxmark3 to appear...

I figured out how to fix this from various sources. I unplugged the Proxmark3, held the button down and plugged it back in. After about 5 seconds Windows detected it, and I was able to run ./pm3-flash-bottom. Then unplugged it again, held down the button for 5 seconds and then ./pm3-flash-all. Finally ./pm3 and all is good

ヘ( ^o^)ノ\(:slight_smile: )

1 Like

Nice save :+1: