Don’t suppose anyone would have any insight into the firmware issue or with the antenna that I could try?
There is one small possibility… the rdv4 proxmark3 was not initialized for timings … a few early ones escaped and they need a init config change to make the tuning and timings work. It’s a one time command… but for the life of me I can’t find it right now … @TomHarkness knows it but he’s been out of the game a while…
I went and had a look on the antenna itself, in case there was a batch number or something on the antenna it self or the packaging it came in. No batch number or anything but it does say it’s a version 1.1
Would that be after the issue you said was found after the initial run or would it still possibly be the issue?
I DID NOT KNOW THAT
I got an early RDV4 I also, and an Early DT LF antenna.
I can use it but the efficacy is not as great as I hear others say.
Don’t worry @Aemun, if that is also your issue also when I am at a computer
I’m going to hunt that bitch down
Tried running flashing using ProxSpace_Master but was getting and error when running
Reran again in a different location with v3.8. No errors, flashed without issues but still fw mismatch and same problem with the antenna.
might try to look for my old laptop that had ubuntu on it and try using that tomorrow. If it doesnt work i might just have a pretty bit of copper in some nice plastic
If you are sure it doesn’t work, click the orange floaty help button on dangerousthings.com and I am sure Michelle will sort you out
can you send a screenshot of the launch of the pm3 client from within proxspace? It should give exact client and firmware versions.
Oh! Did you use our tutorial to set your RDV4 up?
If so you might be configuring the wrong build.
I didn’t get it direct from DT, I ordered it from Lab401 since I’m in the EU. I’d like to make sure its not something I did before I ask someone to send me a replacement.
I did follow the instructions that @amal posted on the forum, but I didn’t change the
Makefile.Platform to PM3OTHER and left it as RDV4. Is that what you mean?
If you’d like, I have a handle little remote support tool for popping onto your screen… if you’d like to set up a Skype call or Google meet I could see if I could help sort this out.
If you’re willing to spend a bit of your time that would be much appreciated
Hey @amal, don’t suppose Iceman gave any insight regarding the issue you were helping with yesterday?
I’m just going to send an email to Lab401 to start the support process if I need to have it sent back and replaced.
I know you took a screenshot, I have a copy of the terminal in a text file I can send you as well if Iceman wants it that I can send.
Ah I sent you a Skype message… he wanted a pic of the back side pcb of the rdv4
Aha, sorry. I don’t usually have skype running in the background.
I’ll take a few picks of it and send them on to you
Looks like the signatures need to be updated on the hardware…
echo “1C3134A9DC63C18318A1DE95653A695201777B385531B96240F1BBA53DED10B567707EB4BD20B467C28769008F4B9CEF83344A759AC40772F888336EA7E9894B1883200825D50122B7A88E67D80B479457CDD4D35807F985AB873777FCF8833E4E3B94BD60B7A97A620EC569BD6D1CA35EB2F40A897E0F04FFF027327CB541B9” | xxd -r -p > mysign.bin
[usb/cdc] pm3 → mem load -f mysign.bin -o 262015
[usb/cdc] pm3 → mem info
[-] RSA private key validation... ( fail ) shows as fail. However…
It certainly sorted the fw issue
The LF antenna still has the same issue though. I think I was just hit with a double wammy of unfortunate luck.
Massive props to yourself and Iceman though for even helping with this stuff.
Thanks to both Amal and Iceman for their assistance.
Just to confirm, we will DOA the device and reship immediately.
Thanks to everyone for their collaboration and patience.