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.
Reset the variables
Reinstallation is most useful when you return to a known clean app state first. Mixing an unknown patched APK, old installer, old mods, and a new release makes troubleshooting harder.
Checklist
- Back up data you can safely preserve.
- Restore the unpatched APK through the installer if that backup exists; otherwise reinstall a clean app.
- Get the current installer from the project release page.
- Patch using the documented flow.
- Test first launch before adding mods.
- Add mods back gradually.
Why add mods later
Testing the patched app before adding mods separates a LemonLoader installation problem from a specific mod problem.
If the clean patch still fails
Collect LemonLoader logs and compare your environment with the documented IL2CPP and arm64-v8a scope. Then search existing GitHub issues for the exact app/version.
Maintenance is about returning to a known state
Uninstalling or reinstalling is most useful when it reduces uncertainty. The goal is not merely to remove files; it is to restore a clean, testable app state, then reintroduce LemonLoader and mods in a controlled order if needed.
Keep data and software rollback separate
A clean APK restoration does not automatically mean all app data has been restored. Treat the application package, local data, OBB/additional files, and mod files as separate pieces. Document which piece your backup actually contains.
After restoration, launch the clean app before patching again. That verifies the base installation independently and prevents a broken underlying app install from being blamed on LemonLoader.
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.