Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MC145026 Bruteforce #81

Open
zigad opened this issue Jan 20, 2025 · 2 comments
Open

MC145026 Bruteforce #81

zigad opened this issue Jan 20, 2025 · 2 comments
Labels
feature New feature request

Comments

@zigad
Copy link

zigad commented Jan 20, 2025

I discovered that a local manufacturer of parking ramp barriers uses these MC145026 chips in remotes to open parking barriers, and they are quite popular in Slovenia. As a result, I started studying the MC145026 protocol used in remote controllers. Since the system relies on a fixed "code," I believe it might be possible to brute-force it.

I'm eager to dive deeper into the protocol and would appreciate any help or guidance. So far, I’ve managed to decode little part of the data sent by the remote, but I haven't yet pinpointed where the code itself is transmitted. I will try to re-solder the address pins on my remote and try to see where is the difference in transmission. Based on my decoding, the remote seems to send the following sequence:

0, OPEN, OPEN, OPEN, OPEN, 1, 0, 1, 1
(one small part, there appears to be a lot of data sent)

I’m wondering if the last 4 digits could represent the address, though that’s just a guess for now. There’s a fair amount of data in the full reading, so I'm still working on figuring it all out.

SubGHz_2025-01-15_18,30,20.sub.zip
SubGHz_2025-01-15_19,33,46.sub.zip
SubGHz_2025-01-15_19,41,48.sub.zip

I saw that HackRF already has this encoder implemented in protocols so maybe this can help: https://github.com/portapack-mayhem/mayhem-firmware/blob/next/firmware/application/protocols/encoders.hpp

@derskythe derskythe added the feature New feature request label Jan 20, 2025
@derskythe
Copy link
Member

Hello @zigad, I will analyze your files in the next two weeks and I'll come back with the result.

@zigad
Copy link
Author

zigad commented Jan 27, 2025

Adding few more ReadRAW dumps. Flipper managed to read a signal only 1 time and recognized it as BET 18Bit (freq: 309,25 MHz)

Flipper found this:
Image
Bett_18bit.sub.zip

RAW Dumps
Archive.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

2 participants