Kiisu-MNTM

Momentum firmware fork for Kiisu v4b/v4br - with U2F and rolling code support

Note: Kiisu-MNTM is not an official Momentum branch. It is a separate community fork of Momentum FW for Kiisu.

Why choose this over other forks?

• Up-to-date - Actively maintained and always in sync with upstream Momentum, plus the latest tweaks and apps from upstream Kiisu FW.

• Rolling code & U2F support - Includes rolling code and U2F support for Kiisu. The firmware covers most rolling code manufacturers from upstream Momentum, but not all. If you find a missing manufacturer key, please contribute here.

• Kiisu assets - Replaces all Flipper assets with Kiisu branding, unlike the Momentum Kiisu branch or stock Kiisu FW. The original Kiisu assets had minor visual issues (noise, low-res images); this firmware ships with fixed assets redrawn by hand. Found something missing? Open an issue.

How to install

Option #1: Using web installer (recommended)

1. Visit kiisu-web-updater.pages.dev
2. Choose Momentum (Kiisu-MNTM)
3. Select INSTALL (or UPDATE)

Option #2: Using Flipper Lab/qFlipper

1. Download kiisu-mntm_XXXXXXXX_dd-MM-yyyy.tgz from Releases
2. Open qFlipper or visit lab.flipper.net
3. Select Install from file and choose the downloaded file

How to build

Clone the repository:

git clone --recursive --jobs 8 https://github.com/HiennNek/kiisu-mntm.git
cd kiisu-mntm/

Flash directly to Kiisu (device must be connected via USB with qFlipper closed):

./fbt flash_usb_full

Compile a TGZ package:

./fbt updater_package

Build and launch a single app:

./fbt launch APPSRC=your_appid

FAQ

Don't see your question answered here? Open an issue.

Common issues

Screen glitching after installation

Just restart your Kiisu.

Things broke after switching from other firmware (e.g., qFlipper/Flipper Lab shows it as incompatible, etc.)

Delete all files from your SD card (you can still keep captured files/downloaded DB files), then reinstall the firmware.

If you can't flash the firmware using the normal way, try flashing it in DFU mode. (Turn off Kiisu, then hold the OK button and plug your Kiisu into your PC. qFlipper and lab.flipper.net will recognize it as DFU mode.)

You can find the DFU file in the latest releases.

qFlipper can't install the firmware (Unknown error occurred, timeout error, etc.)

Use lab.flipper.net. If it does not work, try putting it in DFU mode and flashing the DFU file.

How to enter DFU mode: Unplug your Kiisu, then hold the OK button while connecting through USB. Flipper Lab/qFlipper will recognize it as being in DFU mode.

Why doesn't U2F work?

Try deleting all files in SD Card/u2f/. It will regenerate all cert files. If it still doesn't work, then you're using an older version of Kiisu that doesn't ship with Kiisu's secret keys.

Why can't Sub-GHz copy my remote?

The upstream firmware might not support your remote. If you believe your remote is supported by upstream, check non-flipper-rolling-code-support. Or open an issue.

Windows Defender flags the firmware as a virus

Use Linux

Windows Defender uses AI to scan and detect malware, which might create a false positive.

Try using VirusTotal if you don't trust it.

General

What is Kiisu-MNTM?

Kiisu-MNTM is a community-maintained fork of Momentum Firmware built specifically for the Kiisu device. It adds rolling code and U2F support that aren't available in the official Momentum firmware on Kiisu hardware, ships hand-redrawn Kiisu-branded assets, and stays continuously synced with upstream Momentum plus the latest Kiisu-specific tweaks and apps.

Is this an official Momentum or Kiisu firmware?

No. Kiisu-MNTM is not an official Momentum branch, and it isn't the stock Kiisu firmware either - it's a separate, independently maintained community fork.

Installation & Updates

How do I install Kiisu-MNTM?

See above

Can I switch back to stock firmware or another fork later?

Yes - switching is just a matter of flashing a different firmware file the same way, via qFlipper or lab.flipper.net.

How often is it updated?

Weekly. Check the Releases page for the latest build.

Features

What is rolling code support, and why does it matter for Kiisu?

Rolling code is the security scheme used by many garage door openers, gate remotes, and car key fobs, where each transmission uses a new code instead of a static one. Official Flipper firmware needs factory-provisioned keys to handle certain rolling-code protocols - and since Kiisu hardware isn't produced by Flipper Devices Inc., it doesn't ship with those keys. Kiisu-MNTM implements its own support so these protocols work on Kiisu anyway.

Which rolling code manufacturers are supported?

Most of the manufacturers covered by upstream Momentum Firmware, though not all of them.

What if my remote/manufacturer isn't supported?

You can contribute the missing manufacturer key at the companion repo: non-flipper-rolling-code-support.

What is U2F, and why didn't it work before?

U2F (Universal 2nd Factor) is a hardware authentication standard used for two-factor login. Like rolling code, U2F functionality needs certification that other firmware doesn't ship with - Kiisu-MNTM adds its own support (certificate generation, pulled from official Kiisu FW), so U2F works on Kiisu.

What's different about the Kiisu-themed assets in this fork?

All visuals are Kiisu-branded rather than Flipper-branded, and the original Kiisu asset set - which had some noise and low-resolution artifacts - has been redrawn by hand to fix those issues.

Kiisu-MNTM vs. Other Firmware

How is this different from stock Kiisu firmware?

Kiisu-MNTM brings Momentum's broader feature set on top of Kiisu, stays actively synced with upstream, and includes the hand-corrected assets - none of which are part of stock Kiisu firmware.

How is this different from the official Momentum Kiisu branch?

The official Momentum Kiisu branch doesn't include the hand-redrawn Kiisu assets that Kiisu-MNTM ships with - it still has the original assets' minor visual issues (noise, low-res). Kiisu-MNTM also tracks upstream Momentum closely to stay current.