NFC microchip Read only unlock

[Pilgrimsmaster]

OK, I think all the info you need is in the post, I have tried to break it down and make it A LITTLE more easy to understand
I have Broken it into 2 Parts ( I COULD STILL HAVE MISSED SOMETHING, THIS IS MY BEST GUESS )

Part one, your Lock Bits
Part two, Your Simply NFC locking

Part one, your Lock Bits

@my18666

<aborted: read error on page 156>

@ThexTallxDude

The readout you posted has an error at the bottom, which may be contributing to the issue.

@amal

The only way to tell for sure is another scan from TagInfo (dngr.us/taginfo )… try to get the full scan (no aborted error).

@my18666

[02] . 54 48 00 00 (BCC1, INT, LOCK0-LOCK1)
[03] . E1:10:6D:0F (OTP0-OTP3)

@my18666

[E2] . 00 00 00 BD (LOCK2-LOCK4, CHK)
[E3] . 04 00 00 FF (CFG, MIRROR, AUTH0)
[E4] . 00 05 – – (ACCESS)
[E5] +P FF FF FF FF (PWD0-PWD3)
[E6] +P 00 00 – – (PACK0-PACK1)

@Satur9

So you were not able to use “Erase & format as NDEF”? That’s the solution he suggested.

It looks like both times you used Erase to factory default

You SHOULD be using

Please try that and let us know if that works!

also could you download and run THIS DT NFC App and let us know what result you get, I expect it should be something like this

Part two, Your Simply NFC

IF THE ABOVE DOESN’T WORK, I ( OR SOMEBODY ELSE) WILL EXPAND FURTHER ON BELOW

@my18666

If checked, can I unlock?

@ThexTallxDude

You may be able to recover it with a Proxmark

@my18666

Unlock by using Proxmark?

@my18666

If checked, can I unlock?

I may have checked

Sale Replacement

[my18666]

ありがとう！
Dangerous NFCをダウンロードしました。
パスワードを求められました。
パワスワードを数字4桁で打ち込んだのですが、エラーになりました

[Satur9]

That’s not good. The default capability container values are
E1 10 6D 00

Those are “One Time Programmable” bytes, so they can’t be changed back. Here’s a snippet from the datasheet.

This is why the Product Page for the xNT says to download the Dangerous NFC and protect your tag.

The xNT is an older implant, which allowed customers to have complete control over all the configuration. This problem kept occurring, so the newer NExT implant has this configuration done for you before delivery.

@my18666
Where did you purchase your xNT? On the Dangerous Things website, or from a reseller?

[anon2520759]

Not to hijack, but this just made me wonder which chips are still recommended to use the DT app for protection/configuration?

[my18666]

リセラーで入れてもらいました。
いれたチップは

です。

[Pilgrimsmaster]

Mate sorry, the google translate plugin is not working very well, and your message didn’t translate very well anyway.

This is how it translates

We had you put in reseller.
The tip I put is.

You are clearly more capable than google at translating, could you ask again in english?

[my18666]

It is true that this was scanned.

I forgot which app. It indicated that the chip was not protected.

I downloaded Dangerous NFC.
I was asked for a password.
I entered the power word with 4 digits, but I got an error

I have never set a password, but I was asked for one.

[Pilgrimsmaster]

incorrect DON’T DO THIS

@my18666

It is true that this was scanned.

correct DO THIS

[my18666]

読み込みをしてみました！

このようになりました。

[Satur9]

That is not good. It should not say “0 bytes”

Here is what my chip says on the same screen

I am sorry my18666, but you may need to get a replacement implant. The capability container cannot be fixed once it is changed.

If you get a new implant, use the Dangerous NFC (BETA) app to protect it so that this will not happen again

play.google.com

Dangerous NFC (BETA)

This is the beta version of our Dangerous NFC app for Android. It will ensure your xNT has been protected against accidental locking or malicious attack. It does this by doing the following; 1) Analyze the tag to ensure it is set up in a standard configuration and assess risks 2) Conform the capability container to latest NFC standard (E1 12 6D 00) 3) Lock the capability container against accidental or malicious modification 4) Freeze static and dynamic lock bytes on the tag, locking user me...

Free

@mdanger
Just looping you in. my18666 may need a replacement xNT because the write protection was never applied, and some app made their whole tag read only