How to Update Kenji-NX Without Losing Saves
Updating Kenji-NX is easy — losing a 60-hour save file is not. Follow this order and your games, saves, and settings survive every update: back up first, install second, verify third.
Step 1 — Back up your saves (2 minutes)
Kenji-NX ships a built-in Save Manager (added in 2.1.0-pr.1). Open it, select your games, and export saves as .zip. Copy that .zip somewhere off the phone — cloud storage, a PC, anywhere that survives an app reinstall. This is the step everyone skips and later regrets.
Step 2 — Download the new APK
Grab the latest build from our download page. If you’re unsure which variant to pick, Standard is the safe default; check the changelog to see what’s new first. Verify the SHA-256 hash after downloading, as described on the download page.
Step 3 — Install over the old version
Install the APK normally — Android updates the app in place and your data stays. One exception: the Optimized variant installs as a separate package, so it appears as a second app rather than replacing Standard. That’s intentional (it’s meant for side-by-side testing), but it means saves don’t carry over automatically — which is exactly why Step 1 exists.
Step 4 — Verify, then restore if needed
Launch the updated app and boot a game. If your saves are there, you’re done — delete the backup .zip whenever you like. If anything is missing, use the Save Manager’s import function to bring the .zip back in.
If something breaks after updating
- One game crashes, others fine: try toggling Threaded Rendering off for that title (2.1.0-pr.1 added this switch precisely for crash-prone games).
- Everything was fine before: keep the old APK file. You can reinstall the previous version over the new one to roll back, then report the regression.
- Driver weirdness: re-check your Turnip driver — see our Turnip driver guide. Major version jumps sometimes want a fresh driver.
Frequently asked questions
Will updating delete my games or saves?
Installing a new APK over the old one preserves app data. The risk is reinstalling from scratch or switching to the separately-packaged Optimized variant — export a .zip backup first and the risk disappears.
Do I need to re-enter my keys and firmware after updating?
No. Keys and firmware live in app data, which survives an in-place update. Only a full uninstall wipes them.
Should I update to every pre-release?
Pre-releases like pr.2 are where the fixes land, and the developer asks users to test them. If your setup is stable and you’re mid-playthrough, it’s reasonable to wait — just read the changelog first.
The new version runs worse. What now?
Roll back by reinstalling your saved older APK, keep your .zip save backup handy, and check whether a setting (e.g. threaded rendering) or your Turnip driver needs adjusting for the new build.