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.
Start with the official warnings
Many “installation failures” are actually predictable points in the documented flow: permissions not granted, app data removed during on-device patching, device not authorized for ADB, or a slow first boot.
Checklist
- Confirm you downloaded from the LemonLoader GitHub release.
- On Android, grant the installer permissions it requests.
- On Windows, confirm USB debugging and the RSA fingerprint authorization.
- Keep the device powered during patching.
- Allow extra time for first boot.
- Restart Quest if the OS UI reports a confusing install state.
When to use logs
If the patch reports success but the app crashes repeatedly, use the documented file logs under the MelonLoader directory rather than guessing.
When to stop
If the target app is outside the documented runtime/architecture scope or important data is at risk, do not keep patching blindly.
Use evidence before reinstalling
A good troubleshooting sequence is: reproduce once, capture the relevant message/log, reduce optional mods, verify release and environment, then change one thing. Reinstalling immediately can remove useful logs and can make the next failure look different without explaining why.
Classify the failure stage
- Installer cannot see device/app: focus on ADB authorization, device selection, detection, or package structure.
- Patch fails: focus on installer output, storage, split APK handling, and current release fixes.
- Patch succeeds but app fails: focus on first-run permissions, runtime compatibility, and LemonLoader logs.
- App works until a mod is added: focus on that mod, its runtime assumptions, AssetBundles, and platform differences.
This classification prevents unrelated fixes from being applied to the wrong layer.
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.