NExT xEM stopped working

Yeah I have the xEM Access controller and it was enrolled and working but just stopped one day that’s what prompted me to get a proxmark and investigate. Clearing the Access controller and trying to renrole gives no result also it still works with fobs. I have a feeling that the xEM silicone has died. I build an antenna to use with the proxmark and is tuned to 125khz. I dont think this is an coupling issue with the proxmark

Sounds like you have done all the correct things to fault find.
It might be time to contact DT support


Ticket received… taking this internal. Thanks guys.

Amal

1 Like

would love to know the outcome of this, I have the same problem

EXACT same?
Both LF and HF?
Can you share some more details?
Hopefully we can help you figure out a solution…
What diagnostic tools do you have?
When did it stop working? HF / LF

What have you done so far to fault find?

1 Like

I know that was November 2019, but in case anyone else sees this, that antenna works with the Proxmark3 RDV4, not the Proxmark3 Easy that Dangerous Things sell.

There are instructions for making a home brew ferrite core antenna for the Proxmark3 Easy on this site, in particular this thread.

1 Like

Just the lf has stopped working, it was 2 days I think, I was playing with it with the proxmark and it got less and less reliable untill I couldn’t find anything with an ‘lf search’

How long ago was your NExT installed?

The 25th if June

So it totally could be swelling related.

When you first install, there is a little trauma but your body has fully fought back, slowly your body starts to blood pool and swell (even though it is not always obvious from the outside)

Think of the swelling and of reduction of readability like a bell curve.

image

At the peak and either side you may get intermittent on no reads at all.
(BLUE ZONE from the graph above)

This forum is full of people experiencing the same issue as you, and more often than not, this is the “issue”, It is just your body working correctly

We normally say give it around 2 weeks to be reliable and properly healed

I would still give it another week before you start getting too concerned.

I hope this helps

OR what Amal says down there

what-he-said

this is sorta the key i think… chances are it’s left in a misconfigured state and LF SEARCH will not find anything if it’s not configured perfectly. I would try this;

or… as I like to do… just write an EM410x ID to it a few times and then try LF SEARCH… that can also work to clear a simple misconfig…

1 Like

ok, so I’m not getting nothing anymore, but I can’t write to it, and it doesn’t turn up on an lf search or lf t55 detect

PM3 output
[usb] pm3 --> l t55 dump
[+] Reading Page 0:
[+] blk | hex data | binary                           | ascii
[+] ----+----------+----------------------------------+-------
[+]  00 | 00000000 | 00000000000000000000000000000000 | ....
[+]  01 | 00000000 | 00000000000000000000000000000000 | ....
[+]  02 | 00000000 | 00000000000000000000000000000000 | ....
[+]  03 | 00000000 | 00000000000000000000000000000000 | ....
[+]  04 | 00000000 | 00000000000000000000000000000000 | ....
[+]  05 | 00000000 | 00000000000000000000000000000000 | ....
[+]  06 | 00000000 | 00000000000000000000000000000000 | ....
[+]  07 | FFFFFFFC | 11111111111111111111111111111100 | ....
[+] Reading Page 1:
[+] blk | hex data | binary                           | ascii
[+] ----+----------+----------------------------------+-------
[+]  00 | 00000000 | 00000000000000000000000000000000 | ....
[+]  01 | 00000000 | 00000000000000000000000000000000 | ....
[+]  02 | 00000000 | 00000000000000000000000000000000 | ....
[+]  03 | 00000000 | 00000000000000000000000000000000 | ....
[+] saved to json file lf-t55xx-dump-4.json
[+] saved 12 blocks to text file lf-t55xx-dump-4.eml
[+] saved 48 bytes to binary file lf-t55xx-dump-4.bin
[usb] pm3 --> l t55 dump
[+] Reading Page 0:
[+] blk | hex data | binary                           | ascii
[+] ----+----------+----------------------------------+-------
[+]  00 | 0007FFFF | 00000000000001111111111111111111 | ....
[+]  01 | FFFFFFFF | 11111111111111111111111111111111 | ....
[+]  02 | 00000000 | 00000000000000000000000000000000 | ....
[+]  03 | 00000000 | 00000000000000000000000000000000 | ....
[+]  04 | FFFFFFFF | 11111111111111111111111111111111 | ....
[+]  05 | 00000000 | 00000000000000000000000000000000 | ....
[+]  06 | FFFFFFFF | 11111111111111111111111111111111 | ....
[+]  07 | 00000000 | 00000000000000000000000000000000 | ....
[+] Reading Page 1:
[+] blk | hex data | binary                           | ascii
[+] ----+----------+----------------------------------+-------
[+]  00 | 00000000 | 00000000000000000000000000000000 | ....
[+]  01 | 07FFFFFF | 00000111111111111111111111111111 | ....
[+]  02 | 00000000 | 00000000000000000000000000000000 | ....
[+]  03 | 003FFFFF | 00000000001111111111111111111111 | .?..
[+] saved to json file lf-t55xx-dump-5.json
[+] saved 12 blocks to text file lf-t55xx-dump-5.eml
[+] saved 48 bytes to binary file lf-t55xx-dump-5.bin
[usb] pm3 --> l t55 dump
[+] Reading Page 0:
[+] blk | hex data | binary                           | ascii
[+] ----+----------+----------------------------------+-------
[+]  00 | 00000000 | 00000000000000000000000000000000 | ....
[+]  01 | 00000000 | 00000000000000000000000000000000 | ....
[+]  02 | FFFFFFFF | 11111111111111111111111111111111 | ....
[+]  03 | 00000000 | 00000000000000000000000000000000 | ....
[+]  04 | 00000000 | 00000000000000000000000000000000 | ....
[+]  05 | FFFFFFFF | 11111111111111111111111111111111 | ....
[+]  06 | 00000000 | 00000000000000000000000000000000 | ....
[+]  07 | 00000000 | 00000000000000000000000000000000 | ....
[+] Reading Page 1:
[+] blk | hex data | binary                           | ascii
[+] ----+----------+----------------------------------+-------
[+]  00 | 00000000 | 00000000000000000000000000000000 | ....
[+]  01 | 0000007F | 00000000000000000000000001111111 | ....
[+]  02 | FFFFFFFF | 11111111111111111111111111111111 | ....
[+]  03 | 00000000 | 00000000000000000000000000000000 | ....
[+] saved to json file lf-t55xx-dump-6.json
[+] saved 12 blocks to text file lf-t55xx-dump-6.eml
[+] saved 48 bytes to binary file lf-t55xx-dump-6.bin
[usb] pm3 --> l t55 detect
[!] Could not detect modulation automatically. Try setting it manually with 'lf t55xx config'
[usb] pm3 --> l t55 detect
[!] Could not detect modulation automatically. Try setting it manually with 'lf t55xx config'
[usb] pm3 --> l t55 dump
[+] Reading Page 0:
[+] blk | hex data | binary                           | ascii
[+] ----+----------+----------------------------------+-------
[+]  00 | FFFFFFFC | 11111111111111111111111111111100 | ....
[+]  01 | FFFFFFFF | 11111111111111111111111111111111 | ....
[+]  02 | 00000000 | 00000000000000000000000000000000 | ....
[+]  03 | 00000000 | 00000000000000000000000000000000 | ....
[+]  04 | 00000000 | 00000000000000000000000000000000 | ....
[+]  05 | 00000000 | 00000000000000000000000000000000 | ....
[+]  06 | FFFFFFC0 | 11111111111111111111111111000000 | ....
[+]  07 | 00000000 | 00000000000000000000000000000000 | ....
[+] Reading Page 1:
[+] blk | hex data | binary                           | ascii
[+] ----+----------+----------------------------------+-------
[+]  00 | FFFFFFFF | 11111111111111111111111111111111 | ....
[+]  01 | 007FFFC0 | 00000000011111111111111111000000 | ....
[+]  02 | 00000000 | 00000000000000000000000000000000 | ....
[+]  03 | 001FFFF0 | 00000000000111111111111111110000 | ....
[+] saved to json file lf-t55xx-dump-7.json
[+] saved 12 blocks to text file lf-t55xx-dump-7.eml
[+] saved 48 bytes to binary file lf-t55xx-dump-7.bin

so it’s getting different data each time you run a dump? it looks almost like noise. how’s your antenna positioning? is someone helping you by pressing enter or are you juggling all that yourself?

PS … just asked iceman if he could add a delay to the search / clone commands…

just a small suggestion that is a serious pain in the ass for a small group of people… adding a delay to any kind of operation would be very helpful. Basically when you are trying to position a proxmark3 over your implant you are typically using one hand to hold the proxmark3 over the other… and then having to use an elbow or awkwardly extended finger to press enter… if a settable delay could be added as a parameter to allow like -d 3 to delay 3 seconds before executing… it would be super helpful. the most important commands of course are the hf/lf search and various cloning commands.

we’ll see what he says.

3 Likes

Yeah, I was juggling it myself, I should figure out a better solution :yum:

Actually he said there’s already a provision for it!

msleep -t 3000; lf search

So basically you issue the msleep command first (in milliseconds) then a semicolon to chain commands together.

2 Likes

i’ve got it in a vice now so I have a free hand, the lf t5 detect command doesn’t find anything so maybe I’ve go the wrong config for the tag?
is the config hard coded or can it be changed using block0? What should I be using?

edit:
I don’t know if this is a good reference, but I’m only getting a 3,000mV drop on the lf tune display with my implant, compared to arround 16,000mV on another tag
but now I can’t write to, or read anything meaningfull from either of my test lf tags

ok, I can’t get a read of either of my test t5577 cards either
One card turns up with an Indala ID that changes every time I run lf search, and the other can’t find a valid tag but detects the t55xx chipset.
I can’t write to either of them using lf t55 wipe, lf t55xx write b 0 d 000880E0 -t or lf em 410 clone --id 0D00072C63

Have I done something to my proxmark?

Time to dive in… what hardware do you have? What firmware? When you launch the pm3 client it spits out some info on the screen… post that too…