My implant stopped accepting writing and I never tried to lock it or add any password



Yes, I did use the delay as well:

pm3 --> msleep -t 3000; hf search
[!] No known/supported 13.56 MHz tags found

When a use the card test, it works fine. My implant seems unresponsive to the antenna of the Proxmark.

OK, THESE positions below are the ones you want to be trying, NONE of the others

Ideally, where you see the Antenna trace on the bottom board, you want to place that perpendicular to your implant, making a “+” with antenna and implant.

Try an hf tune , and record the higest voltage with your implant away from the antenna, then place your antenna on the implant, and move it around until you get the lowest possible Voltage ( record this voltage also). This SHOULD be your best coupling and therefore your best chance of reading / writing to your implant.
once you have the LOWEST voltage, DO NOT MOVE, send an hf search in that position and orientation, if it doesn’t work Keep pressing firmly, and move VERY small increments after each command until you get a read
let us know how this goes.

It may also hep to draw an outline around your xSIID

Since your phone makes your blinky blink? :blinky_green:
the hf tune should also make your LED blinky blink :blinky_blue: and at its brightest, is also likely where you should be able to get a read.

From reading your posts above, it sounds like there is some reconfiguring to do, but we need to get a read before we can tackle that issue

Basically it looks almost like the implant is going to be sitting near the center of the bottom PCB and that’s not where it should be. The trace of the hf antenna runs under half the bottom PCB (the half on the other side from the USB cable connector). The very end of the PCB have HF traces across it, so the very end of the proxmark should be sitting across your xSIID so half the xSIID is peaking out from under the bottom PCB of the proxmark… if that makes sense.

With your tips, I was able to make it blink. However, the hf search command still gives me the same answer: No known/supported 13.56 MHz tags found.

Can you get a read with your phone?

No, my phone cannot read it either.

Hmm… did your experiment at all with the kill code by chance?

No, I didn´t. Should I?
Anyway, since nothing can read it, I guess I cannot do anything :frowning:
Do you know places I could replace or implant another chip? I live in Stockholm, Sweden.
I tried with Chipster and they have stopped their chipping business.

1 Like

There is one studio registered at the map

Have you ensured that your PM3 and client are on the same version? If not, strange things can happen.
Run hw version and post the output.

1 Like

The primary reason this is odd is that the LED is lighting. That means the chip is getting power from the antenna and the chip is performing. The only thing I can think of is that it might be getting enough power to light the LED but not activate the NFC functions of the chip. That would be a problem with coupling quality… But it would be really rare for that kind of thing to happen.

Sure

pm3 --> hw version

 [ Proxmark3 RFID instrument ]

 [ CLIENT ]
  Iceman/master/v4.14831-963-gba1def240-dirty-unclean 2022-09-23 22:54:27 180bffbf5
  compiled with............. MinGW-w64 12.2.0
  platform.................. Windows (64b) / x86_64
  Readline support.......... present
  QT GUI support............ present
  native BT support......... absent
  Python script support..... present
  Lua SWIG support.......... present
  Python SWIG support....... present

 [ PROXMARK3 ]
  firmware.................. PM3 GENERIC

 [ ARM ]
  bootrom: Iceman/master/v4.14831-963-gba1def240-dirty-unclean 2022-09-23 22:56:05 180bffbf5
       os: Iceman/master/v4.14831-963-gba1def240-dirty-unclean 2022-09-23 22:56:39 180bffbf5
  compiled with GCC 10.1.0

 [ FPGA ]
  LF image 2s30vq100 2022-03-23 17:21:05
  HF image 2s30vq100 2022-03-23 17:21:16
  HF FeliCa image 2s30vq100 2022-03-23 17:21:27
  HF 15 image 2s30vq100 2022-03-23 17:21:38

 [ Hardware ]
  --= uC: AT91SAM7S512 Rev B
  --= Embedded Processor: ARM7TDMI
  --= Internal SRAM size: 64K bytes
  --= Architecture identifier: AT91SAM7Sxx Series
  --= Embedded flash memory 512K bytes ( 59% used )

Weird indeed :slightly_frowning_face:
What do you suggest I shall do in this case? Would be better to get another NFC reader?

This is an xsiid right, do we know what happens with the pm3 if the “header” (can’t remember the proper name) is screwed up. I know most phones won’t read it maybe try that to recover see if it helps?

How to recovery the “header”?

You will need an android phone for starters (maybe possible in other ways but this was the way we originally did it)

Get that app

Copy the below into the app and hold the phone so thats its illuminating the xsiid. And send the commands.

A20400000000
A20500000000
A2060000031F
A207D1011B55
A20803666F72
A209756D2E64
A20A616E6765
A20B726F7573
A20C7468696E
A20D67732E63
A20E6F6D2FFE
1 Like

I tried, but it does not recognize it :frowning:
It keeps waiting and waiting even though I can see it has the light on

1 Like

Do you have a silicone case on your phone?
I’ve found it kinda scrambled nfc for mine… it’ll light up but not read

I took the phone case out to prevent the signal from being weak

Just making sure