MT-EN Applier
2.7.0 · GitHub
More about this app
One-tap installer for the unofficial English patch of the Mushoku Tensei mobile game, copying files via Shizuku with no root or PC.
MT-EN Applier
Unofficial English patch for Mushoku Tensei: Chronicle of Echoes, on Android, iPhone / iPad and Windows (DMM).
New here? The plain-language walkthrough covers every platform with pictures:
Last patch: 2026-11-12 (v22). See patch-latest for the current build.
Get the patch
| Platform | How | Guide |
|---|---|---|
| Android phone (no root) | The MT-EN Applier app + Shizuku | below |
| iPhone / iPad (no cable, no jailbreak) | A Windows PC on the same Wi-Fi + the free WireGuard app | below · docs/INSTALL-iOS.md |
| Windows PC (DMM GAME PLAYER) | One PowerShell command, or a zip | below · tools/pc/README.md |
| Android emulator / rooted / Google Play Games PC | adb script | tools/reapply-en-patch.ps1 |
Every platform installs the same translation, from the rolling
patch-latest release.
Load twice for full translation. Some screens fetch their text on first load and cache it, so a few lines can stay Japanese the very first time. Go back to the title menu and re-enter; the second load is fully English. This applies to every platform. On PC it can be removed entirely with the optional
-WithAssetsstep in the Windows section below.
Android phone
You need Android 11 or newer and Shizuku (free; it lets the app write into the game's folder without root).
- Start Shizuku via wireless debugging (it stays on until you reboot).
- Open the game once to the title screen so it downloads its data, then close it.
- Install
MT-EN-Applier.apkfrom the latest release and allow the Shizuku permission when asked. - Tap Install English, then launch the game.
INSTALL.md on the release page walks through each step, including Shizuku's pairing.
- Updating from v2.2.2 or older: uninstall the app once, then install the new APK. v2.4.0 moved to a permanent signing key, so Android can't install it over the old one. Your game and patch aren't affected, and later versions install over the top. The app now shows a Get update banner when a new version is out.
- After a game update: open the app and tap Install again. If no patch for the new game version is out yet, Install builds the translation on the phone in a few seconds instead (Auto-patch; only brand-new text stays Japanese). The ? next to Install explains this in the app.
- Translated menus (on by default): Install also translates the text built into the game's screens (menus, buttons, windows: about 7,000 labels), in the chosen language (about 35 MB). Turn the Translated menus switch off and Install puts the Japanese ones back.
- Translated images (opt-in): turn on the Translated images switch and the next Install also replaces the buttons, banners and logos that have Japanese lettering, in the chosen language (about 17 MB).
- Advanced: Rebuild on this phone (Auto-patch) forces the on-phone build, and Install a __data file… installs a patch file you picked.
- Back to Japanese: Delete all language packs (reset) for the text and Remove translated images for the images; the game re-downloads the Japanese files at next launch.
- Shizuku keeps stopping? See the troubleshooting section of
INSTALL.md, and tap the status card at the top of the app for Diagnostics.
iPhone / iPad
Free, no cable, no jailbreak: a Windows PC on the same Wi-Fi hands the game English copies of its text and image downloads, and the game keeps them. The PC is only needed while the game downloads.
- On the PC, download
MT-EN-iOS.zip, extract it and double-click Installer-iOS.bat. A page opens with the steps. - On the iPhone, install the free WireGuard app and scan the page's QR code; then scan the second code and trust the certificate (once).
- Open the game, title menu › Delete local data (account and progress stay). The game downloads its files again, in English. Then switch the tunnel off and close the PC window.
docs/INSTALL-iOS.md walks through every tap. The title-screen menu
and first-load tips live inside the app, which iOS doesn't let anyone change: load twice.
Maintainers: tools/ios/README.md.
Windows PC (DMM)
Launch the game once to the title screen, close it, then open PowerShell and paste:
irm https://github.com/Aikiooo/mt-en-applier/releases/download/patch-latest/install.ps1 | iex
Then click Play in DMM GAME PLAYER. Re-run the same command after a game update.
- Fully English on the first load (default, PC only). The text the game itself
ships — the cached UI prefabs and the in-app bundle behind the first-load title
screen — installs without asking; that's what the patch has always done, just
more of it. The redrawn images (logos, banners, buttons, badges, tutorial
captions) are the one thing it asks about, because they change the art:
yes is the default, and so is 60 seconds of silence. They arrive inside the same
a separate 23.2 MB download, fetched only if they say yes, so answering no saves it.
-WithAssetsanswers yes up front,-NoImagesand-LanguageOnlysay no. Because the in-app half can't stay installed (DMM verifies that file before launching), a small watcher swaps it in per session: start the game withPlay-in-English.cmd(Play-in-French.cmd, ... in another language), then click Play. Every published language ships all of it, not only its text.tools/pc/README.mdhas the details. - No terminal? Download the zip from the PC English Patch release,
extract it and double-click
Install-EnPatch.bat.START-HERE.txtinside is the whole guide. - Back to Japanese:
Restore-Japanese.batin the zip, or the command above with-Restore. - Link your account first: the PC client has no in-game account recovery.
tools/pc/README.mdexplains, along with every option (-Check,-Language,-GameDir).
Languages
English is the only published language today. A French translation is complete
and ready to publish (PC, everything English has: Publish-Locale.ps1 -Locale fr -BuildPcPatch -PcPrefabDir … -PcInappBuild …); a
Spanish one is in progress. The translation lives in translations/ as readable,
one-line-per-entry files, so anyone can suggest a fix or translate into another
language with a normal pull request. translations/README.md
explains how.
Once a second language is published, the Android app shows a Patch language picker and the PC installer asks which language to install. Until then, both behave exactly as they do now.
For developers and maintainers
What the app does
MainActivity reaches a shell (ADB uid) through Shizuku: a bound UserService, or a
one-shot Shizuku.newProcess fallback for phones whose task killer blocks the
service. It force-stops the game, finds every live language bundle (__data) under
/sdcard/Android/data/jp.gree_ent.mushoku/files/…/UnityCache/Shared/ (the asset-hash
folder changes with updates, and a mirror lives under files/il2cpp/), copies the
patch over each, and checks the size on the device.
- Install reads
version.jsononpatch-latest, downloads the selected language's patch and verifies its size and md5, checks it against the game (below) and copies it. With no patch published for the language, or none that fits, it runs Auto-patch. - Auto-patch takes the AES keys from the game's own
global-metadata.dat(offsets fromversion.json), decrypts the new bundle, overlays the translation cache and rebuilds it on the phone (core/AutoPatcher). The status card shows its progress. Details below. - Translated menus (on by default) and translated images (opt-in) overwrite the game's cached UI bundles with the release's per-language build. Details below.
The shell can overwrite the game's cache files but not delete them. The cache
folders are drwxr-s--- (owner: the game, group ext_data_rw) and the files
rw-rw----, so the shell uid (in ext_data_rw) can write a file but not unlink it.
To make the game download a bundle again, the app empties that entry's __info
(Unity's cache record, -1 / timestamp / 1 / __data): Unity then treats the entry
as not cached and downloads it at next launch. Reset, Remove translated images and
Auto-patch's "open the game once" fallback all work this way.
Auto-patch always translates from Japanese. The translation cache matches
Japanese text, so patching an already patched bundle changes almost nothing. Before
patching, it counts the Japanese text cells of the source (AutoPatcher.Result .sourceIsJapanese(): the stock bundle is ~99% Japanese, a patched one ~0%):
- It keeps a copy of the Japanese bundle whenever it sees one (
original_ja.__datain the app's files, also taken by Install before it overwrites the stock bundle). - When the game holds a patch (this app's or another), it starts from that copy if
the copy holds the same table rows as the game's pack, i.e. the same game version
(
AutoPatcher.rowIds; row ids don't depend on the language). - Otherwise it empties the language entries'
__infoand asks the player to open the game once (it downloads its Japanese pack), close it and tap Install again. The app never opens the game by itself.
Install falls back to Auto-patch after a game update. Before copying, Install
decrypts the patch and the game's live language pack and compares the row ids of
every table (AutoPatcher.rowIds, about a second on a phone). Row ids are the same
in every language, so they differ only when the game data changed: then the game
has updated since the patch was published, and Install runs Auto-patch instead of
installing a patch that lacks the new rows. File sizes can't tell this: a patch
doesn't have to keep the stock size.
When a translated table is too long for its ciphertext, rows go back to Japanese, longest first. The patcher sizes that by arithmetic (the plaintext length is the sum of its rows) and encrypts once, so the whole patch takes about half a second on a PC.
Translated menus and images. The game caches its UI bundles like the language
pack, at UnityCache/Shared/<name folder>/<version folder>/__data. The name folder is
the same as on PC; only the version folder differs. Two zips per language on the
release, each holding the patched bundles under their name folder plus a manifest with
the stock (src_md5) and patched (out_md5) md5:
android-prefabs-<code>.zip: the text built into 243 UI prefabs (TextMeshProm_text), the same ~7,270 strings as the PC patch. Installed unless the player turns Translated menus off.android-images-<code>.zip: 113 bundles with redrawn textures (ASTC 6×6). The 3 of them that also carry menu text have the text too, so the image copy replaces the text copy instead of undoing it. Installed when Translated images is on.
The app installs menus first, then images. It overwrites a cached copy only when it is
stock or a bundle it wrote itself (either kind, any language), so switching languages
works and a bundle the game updated stays Japanese. Switching to a language without a
kind, or turning menus off, takes the previous copy away rather than mixing languages.
Remove translated images puts the text-only copy back on the 3 shared bundles.
Both zips are built from the game's Android CDN stock by
tools/prefab-patch/build_android_prefabs.py;
see tools/prefab-patch/README.md.
- Update check looks for the highest
vX.Y.ZGitHub release carryingMT-EN-Applier.apk.
The APK contains no game data and no encryption keys.
Build
gradlew.bat assembleDebug :: app\build\outputs\apk\debug\app-debug.apk
gradlew.bat assembleRelease :: app\build\outputs\apk\release\app-release.apk (signed)
AGP 9.3.0 / Gradle 9.5.1, Java 17 bytecode, compileSdk 37, minSdk 26. The UI is
plain Java with no UI libraries. Dependencies: the vendored Shizuku API client
(rikka.shizuku.*, moe.shizuku.* AIDL; MIT, © RikkaApps), hiddenapibypass for
hidden-API access on Android 9+, and lz4-java plus org.tukaani:xz (LZMA blocks)
for the auto-patcher.
Release builds are signed with the project key, which lives outside the repo
(~/.android/mt-en-applier-release.properties, or -PmtReleaseProps=<path>).
Without it, release builds are unsigned. Every published APK must use that same key,
or users can't update over their installed copy.
Releasing
- App: tag
vX.Y.Zand attach the release build asMT-EN-Applier.apk(plusINSTALL.md). The in-app update check depends on both the tag format and the file name. Don't do it by hand: bumpversionName/versionCodeinapp/build.gradle, commit and pushmain, then runtools/Release-App.ps1(stages and verifies; add-Notes <file> -Publishto release). It refuses a dirty/unpushed tree, an existing tag, a version mismatch, or any signing key other than the project's.INSTALL.mdis versioned atdocs/INSTALL.md; the script fills in the size/MD5 in the attached copy. - Patch: the English patch (
__data,version.json,translation_cache.json, PC bundles) is published topatch-latestby the maintainer pipeline;tools/pc/maintainer/Publish-PcPatch.ps1adds the PC block — the language bundle, the in-app bundle with the stock metadata the swap watcher needs, andprefab-patch.zip(it verifies that build against the local game cache before uploading). - PC installer:
tools/pc/maintainer/Build-PcZip.ps1-Publishuploads the zip and the one-line installer together, so both always run the same scripts. - Other languages:
tools/translations/Publish-Locale.ps1(seetranslations/README.md). Re-run it after each English release, which rewritesversion.json. - Android menus and images:
tools/prefab-patch/publish_android_images.py--locale <code> --kind prefabs images --publish(English included). Re-run it after each English release too. - After a game update: the maintainer's automation builds and publishes the English
pack, adds the update's new lines to
translations/en/, translates them for each published language (French today), commits them here, and re-runs the two steps above plus thecache_md5stamp below. It then rebuilds the iOS patch and the Android menus and images from the new CDN stock and publishes them. The PC UI prefabs and images still need a manual rebuild. - English cache:
version.jsonmust carry a top-levelcache_md5(the md5 oftranslation_cache.json). The app re-downloads its cache only when that stamp changes, so a cache uploaded without it never reaches the phones that have one.
Roadmap
- Ready-made Spanish bundles for Android and PC (exact-size builds, like the English one).
- Keep the
localesblock ofversion.jsonwhen the English release is republished. - Server-side auto-build on game updates (GitHub Actions / watcher), so
patch-latestrefreshes without a manual run. - Textures for events newer than the redrawn set (e.g. the current pickup banners), and the title logo on Android, which lives inside the game's APK.
- Android first-load fix: the in-app bundle there lives inside the APK, so the PC approach (swap the StreamingAssets copy at launch) doesn't transfer.
Legal / disclaimer
Unofficial fan project, not affiliated with GREE, Beaglee or the rights holders. The patch is a fan-made translation layered onto the game's own data; game text © its respective owners. Use at your own risk.
How Shizuku is used
Can install the Mushoku Tensei English patch, rebuild it on-device, manage translated menus and images and reset packs via `sh` shell commands through Shizuku.
This is an AI-assisted analysis of Shizuku-related usages in the app's public source code. It is best effort, so it may not catch every single usage.
How this app uses Shizuku
Shizuku is used to run shell commands with shell privileges so the app can read and replace the game language, menu and image files it otherwise cannot access.
- Apply English patch: stops the game, copies the downloaded or user chosen translation file over every live language copy found in the game cache, fixes permissions and checks file size to confirm success.
- Rebuild patch on-device: stops the game, copies the current game bundle and decryption metadata into app storage for local patching, then writes the rebuilt translation back over every live copy found.
- Manage translated menus and images: downloads the translated menu or image set, copies it over cached game bundles and repairs their metadata, or clears the translated images and menus so the game fetches the originals again.
- Reset language packs: stops the game and blanks the metadata of every cached language pack so the next game launch downloads the original Japanese files again, while also clearing the staged patch copy.
- Check game data: lists cached language bundles, reads their sizes and checksums, locates game metadata and checks shell identity and system settings to diagnose install or reset problems.
Android APIs or commands used
am force-stopcpchmodstatwclsheadmd5sumfindsettings getidsh -c
Notable details
Game updates re-download the original Japanese bundle, so the patch must be applied again after each update. Reset clears the patched files and lets the game fetch clean originals on next launch.
Changelog
What's new for version 2.7.0
What's new
- Translated menus. Install now also translates the text built into the game's screens: menus, buttons, windows, the sign-in and data-transfer screens, purchase warnings (about 7,000 labels, English and French, about 35 MB). It's on by default; turn Translated menus off and tap Install to get the Japanese ones back.
- Translated images were rebuilt for the current game version and keep the translated menus on the screens that have both.
After a game update, open the app and tap Install again.
Install over v2.4.0 or newer. From v2.2.2 or older, uninstall the old app first (one time only, see INSTALL.md).
Permissions
3 permissions requested
Sources
2 sources
Sources
2 sources