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.
One restart is documented
The 0.6.5.1 release note says a patched app may crash on first launch and that restarting it can be enough. That does not mean repeated crashes should be ignored.
If the crash repeats
- Confirm permissions were granted.
- Allow a full first-boot attempt.
- Remove third-party mods temporarily.
- Check the file log directory and
Latest.log. - Compare the app with the documented IL2CPP/arm64-v8a scope.
Do not erase evidence too early
Repeatedly reinstalling before reading logs can erase the context needed to diagnose a problem. Capture the failure first.
App-specific limitations
The project FAQ warns that game compatibility is unstable. A persistent crash may be an app-specific incompatibility rather than a broken global installation.
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.