[ See edit at bottom - Likely just another case of bad reads. Even using the booster board though. Suppose the main thing to do is use hf tune to keep looking for better angles to read from. ]
After some time of not using it, I pulled out my Proxmark3 easy I bought from DT, and it doesn’t seem to be working to do things I’ve done successfully in the past. Don’t know if it’s user error from forgetting how to use it or if something’s gone wrong with my equipment. (Did that really bright white PW light always stay on?)
For my NExT, which I’ve written to and read from in the past:
[usb] pm3 --> hf mf rdbl --b 2
[#] Can't select card
And then for the exact same command on the same chip I would also get:
[#] Auth error
I tried it with several different blocks, getting the same results.
For my DESFire the only command that worked was getuid, but after the first couple times I can’t get it working again either. Also, when getuid did work, a couple digits were misread. Most were correct though. (Note that my KBR1 still reads the IDs just fine.)
[usb] pm3 --> hf mfdes getuid
[!!] 🚨 Desfire AID select error.
[-] ⛔ Select or authentication AID 000000 failed. Result [202] Can't
select application by ISO ID.
I added @Hamspiced’s Proxmark Booster Board (the backplane), but am still getting the same results. Actually, I’m now getting a voltage increase of about 1000 mV when I place the Proxmark3 against my skin (anywhere, not just over an implant). I installed it as in this picture. (Only difference is I put the screws back in.)
Huh. And just now, this happened:
[usb] pm3 --> hf tune
corrupted size vs. prev_size
/usr/local/bin/pm3: line 253: 3859 Aborted $CLIENT "$@"
And then pm3 crashed back to my shell. The line referenced in the error message seems to be the second line of:
if [ "$SCRIPT" = "pm3" ]; then
CMD() { eval "$EVALENV"; $CLIENT "$@"; }
HELP() {
cat << EOF
I haven’t touched the pm3 software on my PC or the firmware on the device since I last used it. Maybe I’ll need to re-flash it but I’d rather try other things first.
I don’t know if the “suspect” in the below means anything. Based on my logs, that’s always been there, even when I was using the device successfully, so I guess not.
MCU....... AT91SAM7S512 Rev B
Memory.... 512 KB ( 60% used )
Client.... Iceman/master/v4.17140-73-g512e7aa94 2023-10-05 15:44:56
Bootrom... Iceman/master/v4.17140-73-g512e7aa94-suspect 2023-10-05 15:44:23
OS........ Iceman/master/v4.17140-73-g512e7aa94-suspect 2023-10-05 15:46:00
Target.... PM3 GENERIC
Looking through my logs, I realise before I was using the mfu rather than mf command. Trying it, I mostly get no return value at all, except once I got it to work except that’s not the correct data that should be on that block. (Should be 57 68 61 74.)
[usb] pm3 --> hf mfu rdbl --b 7
[usb] pm3 --> hf mfu rdbl --b 7
[usb] pm3 --> hf mfu rdbl --b 7
[=] Block# | Data | Ascii
[=] -----------------------------
[=] 07/0x07 | 75 73 2F 73 | us/s
[usb] pm3 --> hf mfu rdbl --b 7
[usb] pm3 --> hf mfu rdbl --b 7
[usb] pm3 -->
EDIT:
Should’ve tested this previously. It seems to be working on tags outside of my body, which suggests I’m simply not getting a good read. (Also the mfu data block I thought was wrong because it didn’t match with my logs I found on one of my cheap paper NTAGs where I tested it before writing, so maybe I’ve forgotten which block of my implant I wrote the same message to.) Indeed I’m getting voltage drops instead of increases when scanning the external tags. Will keep fiddling.
EDIT2:
Well, it did work once. Now even on the external tag I’m getting weird results. There are no other tags nearby. But, if I position it right it still works, so I’m still thinking it’s an issue with getting a good read. I do get voltage increases with the external tags as well in some positions.
[usb] pm3 --> hf mfu rdbl --b 7
[#] Warning: HF field is off, ignoring TransmitFor14443a command
[#] Multiple tags detected. Collision after Bit 1
[#] Can't select card (RC:00)
[!] ⚠️ Failed reading block: ( 00 )
[usb] pm3 --> hf mfu rdbl --b 7
[#] Multiple tags detected. Collision after Bit 3
[#] Warning: HF field is off, ignoring TransmitFor14443a command
[#] Multiple tags detected. Collision after Bit 3
[#] Warning: HF field is off, ignoring TransmitFor14443a command
[#] Warning: HF field is off, ignoring TransmitFor14443a command
[usb] pm3 --> hf mfu rdbl --b 7
[#] Can't select card (RC:00)
[!] ⚠️ Failed reading block: ( 00 )
[usb] pm3 --> hf mfu rdbl --b 7
[usb] pm3 --> hf mfu rdbl --b 7
[usb] pm3 --> hf mfu rdbl --b 7
[#] Warning: HF field is off, ignoring TransmitFor14443a command
[=] Block# | Data | Ascii
[=] -----------------------------
[=] 07/0x07 | 57 68 61 74 | What
Okay, as I position it particular ways I am able to get mostly consistent reads on my external tags. Guess I just need to fiddle with the positioning for reading my implants through the booster board.
repeater board from what I’ve heard.
