Lock won't accept implant or other tags

I’m not sure if this is the right place, but I have this really weird problem that I got stuck on currently:

I bought two NFC lock cylinders, same model, same website. I tested and installed the first one without any issues. Works like a charm, just presenting my implant and it lets me in.

Here’s the weird part: the second lock doesn’t accept any chip that was not included in the original package. I tried all tags and implants available - nada. But the ones included work every single time without fail.

It’s really weird to me, since the other one works flawlessly. I somehow doubt the lock is faulty, it might be more of a DRM kind of thing perhaps? The lock is compatible with the Tuya app, which is where I put it into the mode where it stores the tags.

And idea what’s going on here? I’ve read the tags with my flipper (phone doesn’t work). The one with the :white_check_mark: is the one included by the manufacturer, the one with the :cross_mark: is one I ordered on Amazon which doesn’t work with the lock, but works with the first one.

Also this is a listing for the included tags, they look identical: https://de.aliexpress.com/item/1005005655146323.html?gatewayAdapt=glo2deu

And this is the one that works with one lock but not the other: YARONGTECH (pack of 10) waterproof ABS 13.56MHz ISO14443A MIFARE Classic 1k nfc rfid token,rfid keyfob,rfid tag : Amazon.de: DIY & Tools

1 Like

Including clones/emulation of the original tags, or just enrolling new tags?

Does it reject them, or just ignore them?

Would you be willing to share the dump files?

3 Likes

Sure, I’ve attached them here.

So the first lock takes every card, but the second one does not even react to any of the non-included tags.

Neither does it beep nor does it give an “unknown card” error. It’s just as if it wasn’t there. Same goes for emulating it with the flipper. It just doesn’t even indicate that there is a card at all.

But it reads all included chips just fine and complains if they are not registered. But also it does the same for the ones from the first lock.

Cylinder_ordered.zip (1.0 KB)

Cylinder_included.zip (1.0 KB)

2 Likes

Looking at the dumps I don’t see anything super special or obvious different between them

The lack of any beeps or rejection makes me think hardware/coupling issue, which I realize is completely unhelpful to solving the mystery :classic_tongue:

Have you tried any non Mifare Classic tags with it?

4 Likes

Good question

These locks are pretty much compatiable with most HF chips.
See my reviews on “similar” locks using Tuya/ TTLock.

3 Likes

Yes, I haven’t heard of anything like that before. I was under the impression that most of them will read whatever you throw at them. It’s a fairly cheap one too, so I don’t think there is anything advanced built into it.

Since both of the locks I have look identical and one does it, but the other one doesn’t, I start to wonder if this is some kind of DRM thing that resellers can activate so they can upsell their customers with expensive tags.

I have tried it with an NTAG I2C Plus, Mifare ultralight and some random Tags I had lying around. None of them are recognised unfortunately.

3 Likes

I don’t see how they’d prevent the Flipper’s emulation that way though, it shouldn’t really be able to tell the difference between that and a genuine OEM tag

the flippers emulation of mifare classic sucks with timings which could be why.

1 Like