Accidentally bricked my Next v2 HF side with hf mfu wipe — any hope?

Support
1

Hey guys,

So I did something really dumb. I ran hf mfu wipe on my Next v2 implant using Proxmark3 and now the HF side doesn’t respond to anything at all. Tried everything I could find, different commands, different apps, different phones, nothing detects it.

LF side still works fine.

Is there any way to recover from this or is it just dead?

Thanks

1 Like
2

Huh, that shouldn’t break anything. But I suppose that is a lot of consecutive writes and the likelihood of a tear is higher than normal. What all have you tried? It’s always nice to start with an hw tune --mix to make sure the implant is coupling with proxmark before you try to send a command.

Also, how long have you had the implant installed? Had anything been written to it before?

1 Like
3

Hey tac0s, thanks for getting back to me! I implanted it last November, and since then it was working, I recorded some things with NFC Tools. It still blinks with color when I run hf 14a reader -@, however its UID doesn’t show up, as if it’s not responding, and when I read a another card it reads normally.

1 Like
4

Can you try doing a sniff of an interaction with your phone? Hmmmm I forgot they are Ntagi2c not a 216… I’ll check the pm3 source in the morning if no one beats me to it to verify the mapping.

2 Likes
5

When you did the wipe did you use the key flag? Because I had assumed you hadn’t.

2 Likes
6

So, there is a map for ntagi2c memory so the device is aware of that specific transponder and even when it touches the config to reset it the only thing that comes to mind that could cause this (assuming the trace is empty) would be disabling the nfc interface but even if you were authed, that gets a default zero written to it. That means the nfc interface would still be on. If NDEF just isn’t working, it could be a compatibility container issue, I suppose, but it skips that block. :man_shrugging:

1 Like