Installation

LemonLoader Installation Guide for On-Device Patching

A concise, source-based walkthrough of the on-device installer flow, including the documented data-loss warning.

Illustration for LemonLoader Installation Guide for On-Device Patching

Source note: LemonLoader is independent. Project-specific facts below are limited to information published by the LemonLoader repository, releases, or wiki; general troubleshooting advice is identified by context.

Important data-loss warning

Official wiki warning: on-device patching removes app data. Apps that depend on files such as OBBs may become unusable if required data is not backed up.

On-device flow

  1. Get the installer APK from the project Releases page.
  2. Install and open the MelonLoader Installer on the device.
  3. Grant the permissions requested by the installer.
  4. Select the target app and choose Patch.
  5. Keep the device powered while patching completes.
  6. Follow the prompts to uninstall the original app and install the patched app.
  7. Launch the patched app and allow extra time for first boot.

Quest-specific prompts

The wiki notes that Quest/Oculus may show modified-app prompts after installation and may temporarily report the app as missing. A headset restart is the documented recovery when the UI gets confused.

Do not add undocumented steps

This site does not add root requirements, Android-version claims, or game-specific compatibility promises because the cited installation page does not establish them as universal requirements.

Installation checkpoints

Think of patching as a sequence of checkpoints rather than one button press. Before patching, verify source and backup. During patching, keep the device connected/powered and avoid interrupting the installer. After patching, confirm the installer reports success before introducing mods or changing preferences.

If the app fails after patching, preserve the simplest possible test state. A clean patched app with no optional mods provides much better diagnostic evidence than an installation where the loader, target app, several mods, and configuration files were all changed together.

What a successful patch does not prove

An installer reporting “patched” only tells you the patch operation completed. It does not establish that every game feature, network service, or third-party mod is compatible. First launch, runtime initialization, and mod loading are separate stages and should be tested separately.

Recommended next step

For a clean path through the project, use the verified download page, follow the installation guide, and keep the logging guide available for troubleshooting.

Primary project references
Main repository ↗ · Releases ↗ · Wiki ↗