Feature request: Oh My Keymint compatibility

[UIRAN23]

Problem

Tricky Addon WebUI only works with Tricky Store. Oh My Keymint (OMK) uses different config format (TOML) and file paths, so the WebUI doesn't support it.

What's needed

1. Engine detection

Detect which engine is installed at startup:

• Check /data/adb/modules/oh_my_keymint/module.prop → OMK
• Check /data/adb/modules/tricky_store/module.prop → Tricky Store
• OMK takes priority if both are installed

2. Config management

OMK uses two TOML files:

• injector.toml — target apps list in [scoop] section
• config.toml — policy in [trust], [device], [crypto] sections

Need to read/write both files, preserving all sections.

3. Policy dialog

When OMK is active, show all OMK fields in the default policy dialog:

• Trust: os_version, security_patch, vb_key, vb_hash
• Device: brand, device, manufacturer, model, product, serial
• Crypto: root_kek_seed, kak_seed, shared_secret_seed, shared_secret_nonce
• Injector: log_level

4. Keybox

OMK keybox path: /data/misc/keystore/omk/keybox.xml
Requires ownership keystore:keystore (uid 1017) and permissions 0600.
Since WebUI runs in app context, need to use su -c for writing.

5. Daemon restart

After saving config, restart OMK daemons by creating marker file at /data/adb/omk/restart.all.

6. Module scripts

• service.sh: Skip prop handler for OMK, symlink to correct engine
• uninstall.sh: Clean up symlinks and restore keybox for both engines

UI requirements

• When OMK is active: show small "Oh My Keymint" label next to title
• When Tricky Store or unknown: UI looks exactly like original (no changes)
• No extra badges, status indicators, or visual clutter

Constraints

• Zero changes for Tricky Store users
• No background services or polling
• WebUI only runs when opened in root manager

[KOWX712]

A partial support has been done in #140 , test latest canary build first https://github.com/KOWX712/Tricky-Addon-Update-Target-List/actions/runs/27203000047/artifacts/7506250329

[KOWX712]

Partial support means what TrickyStore support is supported like scoop (target management), security patch (policy), keybox management, if you want some frequent used feature that not yet implemented you can suggest it.

[UIRAN23]

A partial support has been done in #140 , test latest canary build first https://github.com/KOWX712/Tricky-Addon-Update-Target-List/actions/runs/27203000047/artifacts/7506250329

I tested it. It doesn't add the keybox to the OMK folder. The keybox.xml file's modification date changes, but there's no text inside.
OMK keybox path: /data/misc/keystore/omk/keybox.xml
Requires ownership keystore:keystore (uid 1017) and permissions 0600.
Since WebUI runs in app context, need to use su -c for writing.

[KOWX712]

Nope, webui runs in root context, webui use root shell for exec and spawn

[UIRAN23]

Nope, webui runs in root context, webui use root shell for exec and spawn

I don't know, but with my method the keybox is recorded well. However, in your Canary, the keybox is not written to the OMK folder.

[KOWX712]

It is working well on current canary, what do you mean not written

lv_0_20260611233629.mp4

[UIRAN23]

VID_20260611_205305.mp4

It doesn't work for me. Maybe it's my root. I'm using folkpatch(fork Apatch). What root method do you use? And can you adapt it for folkpatch?

[KOWX712]

Added a working mode tag in about dialog, you can check which setup it is working with.
TS -> TrickyStore
OMK -> OhMyKeymint

https://github.com/KOWX712/Tricky-Addon-Update-Target-List/actions/runs/27361805848/artifacts/7570505534

[UIRAN23]

He showed OMK

[alitajelsir]

I have the same issue.

No matter which keybox I apply through Tricky Addon; a backup keybox is created and OMK stock keybox is restored. I have to copy the keybox manually.

Tricky Addon canary 721
KSU v3.2.4-68-gb0bc817b (32525-2)
OMK 1.2.0-3414522

[KOWX712]

try https://github.com/KOWX712/Tricky-Addon-Update-Target-List/actions/runs/28037716243/artifacts/7825715663

[alitajelsir]

Working fine with 722

[alitajelsir]

Also regrading compatibility, in the [scoop] section in injector.toml, having each app in a separate line would be better for readability if the need arise to edit the file manually.

I didn't open a new issue because i thought the suggestion falls within the same topic.