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.
I flashed bootloader successfully.
./flasher /dev/ttyACM0 -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 (0x00000c84->0x00000c84) [R X] @0x298
Waiting for Proxmark to appear on /dev/ttyACM0 ..........................
Found.
Flashing...
Writing segments for file: ../bootrom/obj/bootrom.elf
0x00100000..0x001001ff [0x200 / 1 blocks]. OK
0x00100200..0x00100e83 [0xc84 / 7 blocks]....... OK
Resetting hardware...
All done.
Have a nice day!
Now whenever I plug it in, red and green lights, A and C are on. Normal behavior is just power light is on when you plug it in.
It doesn't show up as a USB device.
However, if I plug it in while holding down the button, and hold the button for 10s after plugging it in, it goes into the mode where it would normally have lights A and C stay on. For a few seconds, it's discoverable as a USB device.
I can't/couldn't update the OS.
In the flashing guide, I've completed "Upgrade the Proxmark bootrom by executing the following command: ./client/flasher /dev/ttyACM0 -b bootrom/obj/bootrom.elf" successfully, and can't run ./client/flasher /dev/ttyACM0 armsrc/obj/fullimage.elf, because the device will never be detected. If I force it to show up by plugging it in with the button held down, and keep it held down for 10s, then wait ~5s for it to go into discoverable mode it will find it, but then lose it again when it goes back to invisible.
Loading ELF file '../armsrc/obj/fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0002ea28->0x0002ea28) [R X] @0x94
1: V 0x00200000 P 0x00130a28 (0x00001940->0x00001940) [RW ] @0x2eabc
Note: Extending previous segment from 0x2ea28 to 0x30368 bytes
Waiting for Proxmark to appear on /dev/ttyACM0 ................................................
Found.
Waiting for a response from the proxmark...
You can cancel this operation by pressing the pm3 button
or
./flasher /dev/ttyACM0 ../armsrc/obj/fullimage.elf
Loading ELF file '../armsrc/obj/fullimage.elf'...
Loading usable ELF segments:
0: V 0x00102000 P 0x00102000 (0x0002ea28->0x0002ea28) [R X] @0x94
1: V 0x00200000 P 0x00130a28 (0x00001940->0x00001940) [RW ] @0x2eabc
Note: Extending previous segment from 0x2ea28 to 0x30368 bytes
Waiting for Proxmark to appear on /dev/ttyACM0 ...........
Found.
Flashing...
Writing segments for file: ../armsrc/obj/fullimage.elf
0x00102000..0x00132367 [0x30368 / 386 blocks].........Waiting for a response from the proxmark...
You can cancel this operation by pressing the pm3 button
You can see it tries to write, but then loses the USB connected status, and defaults to "waiting for a response from the proxmark". Trying to re-plug with button depressed doesn't recover.
If I try to run the client like normal, then, say, hw status, I get
Sending bytes to proxmark failed
SOLVED.
The key was
sudo apt purge modemmanager
Now I can run the image no problem!
Last edited by theguy (2019-05-17 07:54:04)
Offline
When I first go my proxmark3 easy I think I had the some issue.
What I found worked for me was to hold the button while plugging in, and keep holding the button.
When the devices is found, keep holding the button and try to flash the os (fullimage.elf)
and only let the button go once the os has completed updating.
Offline