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.
Hey, so we just got a new RDV4.0 and reading through all the threads on here about bricking and stuff, I have two questions.
1) What's the best version to use? Like, we're familiar with the stock firmware, but also read somewhere that the RRG one is better for the 4.0? We're primarily interested in working with LF stuff right now, if that makes a difference.
2) Do you really have to flash the bootloader every time? Like that seems to be where these things keep getting bricked, so is it really necessary? Or can we just flash the fullimage.elf?
FWIW we had been using a Proxmark3 Easy, but bricked it last week, when we were flashing from the stock firmware to the RRG one to try it out.
Thanks!
Offline
1. It comes down to flavor I guess. You flash the one that works the best for you since you are going for LF there is no preference.
2. no. Once you flashed bootrom recently then its fine. However, when going between repos (official -> rrg, or rrg -> official) then you need to flash bootrom/fullimage.
Offline
Thanks iceman!
Offline
Easy to brick (pun intended) , you need to remember to target the compile for PM3EASY. You can't compile for RDV4 and flash on an easy and expect it to work.
Offline
Ah! We totally missed that, just downloaded the RRG version and did make all then tried to flash it. Didn't even think about changing target or any compile options or any of that stuff.
Will be alot more careful when we start working with the RDV4. (hoping to get started with it later today.)
Thanks again!
Offline
You should be able to un-brick it via the jtag and correct boot loader, then update the full as per normal (for the correct chips).
I think of it this way. There is a computer on the device that needs an OS installed. normally this is done via the "special" chip programmers, in this case the jtag programmer (there are a few standers in use like PIC and Atmel use, but jtag is more standard and whats used here)
So to make it easier for every day use in field updating, the developers have written a boot loader "os" for us.
So jtag is used to install the boot loader.
The boot loader then has some basic functions that will either boot into the main os/firmware, or go into firmware update mode (e.g. when you hold the button).
Offline