OhMyKeymint: Custom Android Keystore Spoofer

Welcome to this comprehensive guide on OhMyKeymint. If you customize Android devices, pass hardware attestation checks, or bypass root detection mechanisms, you have likely encountered tools like TrickyStore or TEESimulator. OhMyKeymint represents the next evolutionary step in Android key attestation spoofing.

In this blog post, you will learn what OhMyKeymint is, how it functions under the hood, its standout features, system requirements, step-by-step installation instructions, configuration methods, troubleshooting tips, and answers to common questions.

Table of Contents

What is OhMyKeymint?

OhMyKeymint (often abbreviated as OMK) is an advanced open-source module created by developer James Clef (qwq233). It provides a full custom keystore implementation for Android devices by implementing the native Android Open Source Project (AOSP) Android Interface Definition Language (AIDL) framework.

When applications want to check whether an Android device is modified or unlocked, they query the system Keystore service. Traditional spoofing tools intercept or patch specific responses on the fly. OhMyKeymint takes a deeper approach by serving as a full implementation that closely references official AOSP code. Because its responses conform to expected AOSP behavior, security detection tools find it significantly harder to detect anomalies.

Features of OhMyKeymint

OhMyKeymint brings several powerful capabilities to power users and custom ROM enthusiasts:

Complete AOSP AIDL Implementation: Implements official AOSP Keystore interfaces to ensure high compatibility and stealth against detection routines.
Private RPC Architecture: Uses private rsbinder Remote Procedure Calls (RPC) instead of standard public service managers, creating an isolated operational environment.
Selective App Target List (scoop): Allows you to specify exactly which apps receive spoofed attestation responses (such as Google Play Services, banking apps, or detection tools) while leaving other system apps untouched.
Dual Background Daemons: Runs dedicated daemons for both the keymint service and the injector process, allowing modular management.
Hot-Reloadable Settings: Allows security patch levels and active configurations to update on the fly without requiring a full device reboot in most scenarios.
Custom Keybox Integration: Fully supports custom keybox.xml certificates with both EC (Elliptic Curve) and RSA key chains.
Automatic Configuration Safeguards: If a configuration file breaks due to syntax errors, OhMyKeymint backs up the bad file and restores a valid default config automatically.

Requirements

Before installing OhMyKeymint, verify that your device meets the following prerequisites:

Android Operating System: Android 12 or higher (Android 12, 13, 14, or 15+).
Root Environment: Root access configured through Magisk, KernelSU, or APatch.
Custom Keybox File (Optional but Recommended): A valid keybox.xml containing clean EC and RSA certificate chains without watermarks or hidden characters if you want to pass hardware-backed key attestation.
Root File Explorer or Terminal App: An application like MT Manager, Mixplorer, or Termux to inspect and edit TOML configuration files under system directories.

Download

You can obtain the latest source code, CI builds, and release archives directly from official developer resources:

Official GitHub Repository: qwq233 OhMyKeymint on GitHub

Always download module zip packages from verified developer links to ensure code integrity and safety.

Install

Installing OhMyKeymint follows standard root module installation steps:

Download the latest OhMyKeymint flashable zip file to your phone’s internal storage.
Open your preferred root manager application (Magisk App, KernelSU WebUI, or APatch).
Select the Modules tab.
Tap Install from storage and choose the downloaded OhMyKeymint zip file.
Allow the installation script to complete.
Reboot your device to start the system daemons.

How to Use

Once installed, OhMyKeymint operates automatically in the background, but you can customize its operation through configuration files and terminal commands.

1. Replacing the Keybox File

If you have a clean keybox.xml certificate file:

Place your valid keybox.xml file into the module folder directory or replace the template keybox located in /data/misc/keystore/omk/.
Ensure the file contains both valid EC and RSA chains and contains no extra text or hidden characters.

2. Customizing Configuration Files

OhMyKeymint relies on two main configuration files located at /data/misc/keystore/omk/:

config.toml: Controls primary backend behavior, cryptographic seeds (root_kek_seed and kak_seed), and system property overrides.
injector.toml: Controls app interception. Edit the scoop list to declare which package names are targeted:

Ini, TOML

scoop = [
  "io.github.vvb2060.keyattestation",
  "com.google.android.gsf",
  "com.google.android.gms",
  "com.android.vending",
  "com.eltavine.duckdetector"
]

[main]
enabled = true
log_level = "debug"

3. Restarting Services Without Rebooting

When you modify settings inside injector.toml or config.toml, you do not always need to restart your phone. You can restart individual daemons via root terminal commands:

Restart Keymint Daemon:
resetprop persist.sys.omk.restart.keymint 1
(or run touch /data/adb/omk/restart.keymint as root)
Restart Injector Daemon:
resetprop persist.sys.omk.restart.injector 1
(or run touch /data/adb/omk/restart.injector as root)
Restart Both Services Simultaneously:
resetprop persist.sys.omk.restart.all 1
(or run touch /data/adb/omk/restart.all as root)

Credits

OhMyKeymint is made possible thanks to open-source contributions and official reference code:

Primary Developer: James Clef (qwq233) for designing and maintaining the OhMyKeymint project.
Android Open Source Project (AOSP): Source code components derived under the Apache-2.0 License copyright by Google LLC.

Troubleshooting

If you encounter issues while using OhMyKeymint, consider the following troubleshooting solutions:

Invalid Configuration File: If you accidentally make a syntax error while editing .toml files, OhMyKeymint renames the broken file to config.toml.bak with error details appended and regenerates a valid standard config file automatically.
Keybox Parsing Failures: Verify that your keybox.xml contains valid XML syntax. Ensure no hidden characters or invisible watermarks were added during file transfer.
Target App Bypassing Interception: Double-check that the application’s exact package name is listed inside the scoop array in injector.toml.
System Property Changes Not Updating: If you change vb_key or vb_hash settings from random back to auto, a simple daemon restart is insufficient. You must reboot your device completely so boot properties resolve correctly.

FAQs

What makes OhMyKeymint different from TrickyStore?

TrickyStore hooks specific keystore functions or certificate generation routines. OhMyKeymint implements the full AOSP AIDL Keystore interface, offering higher fidelity and stealth against advanced security detection algorithms.

Does OhMyKeymint work on Android 11 or older?

No. OhMyKeymint requires Android 12 or newer because it relies on AIDL Keystore architecture introduced in modern Android versions.

Can I run OhMyKeymint alongside other root hiding modules?

Yes, OhMyKeymint works well alongside standard root concealment solutions like Zygisk modules or Play Integrity fixes. Ensure you do not run multiple active keystore spoofers simultaneously to avoid conflicts.

Conclusion

OhMyKeymint provides a robust, modern solution for Android key attestation spoofing by building directly on top of AOSP specifications. Its dual-daemon structure, dynamic hot-reloading capabilities, and flexible targeting make it an exceptional choice for advanced Android users seeking maximum system stealth.

Do you have questions about setting up your configuration file or working with keybox certificates? Please leave a comment below and share your thoughts.