# How to Run Metal Gear Solid 2 HD and Other NVIDIA SHIELD Ports on Android > AI Release · @ai_release1 · https://ai-release.org/guides/kak-zapustit-metal-gear-solid-2-hd-i-drugie-porty-nvidi_en.html ## TL;DR - Time to complete: 25–30 minutes - Difficulty: Intermediate - You will need: a PC with Android Platform Tools (`adb`), a USB cable or working Wi-Fi debugging, a SHIELD-class Android device, the port's `.apk` file and its `.obb` data file, and free storage equal to at least twice the size of the data file. ## Requirements and setup ![Illustration: Requirements and setup](https://ai-release.org/guides/img/kak-zapustit-metal-gear-solid-2-hd-i-drugie-porty-nvidi-en-1.jpg) - **PC**: Windows, macOS or Linux with Android Platform Tools installed and `adb` on your `PATH`. Verify with `adb version`. - **Device**: an NVIDIA SHIELD-class Android device (TV box or tablet). The SHIELD ports are built for this hardware family — confirm your exact model against the documentation before downloading anything. - **Files**: the game's `.apk` plus its `.obb` data file. The exact file names, package name and version code must come from the documentation of the port you are installing. This guide uses `` and `` as placeholders — replace them with the real values, e.g. a package name looks like `com.vendor.gametitle`. - **Storage**: free space at least twice the size of the `.obb` file (one copy for the download, one for the copy on the device). - **Permissions**: USB debugging enabled on the device; no root required. - **Optional**: a USB flash drive if you prefer to copy files without a PC. If you have never installed an app outside the Play Store, the sideloading basics are covered in [How to Run an AI Model Locally on Android: Apps and Setup](https://ai-release.org/guides/kak-zapustit-ii-model-lokalno-na-android-prilozheniya-i.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide). Pre-flight checklist: - [ ] `adb version` prints a version string - [ ] USB debugging is ON - [ ] `adb devices` lists the device as `device`, not `unauthorized` - [ ] `.apk` and `.obb` files are on the PC - [ ] free space on `/sdcard` is larger than the `.obb` size ## Step 1. Connect the device and confirm free space **What to do:** enable Developer options, switch on USB debugging, authorise the PC, and check the free space on the internal storage. On the device: **Settings → Device Preferences → About → Build** (tap it seven times to unlock Developer options), then **Settings → Device Preferences → Developer options → USB debugging → On**. Connect the cable and accept the "Allow USB debugging?" prompt on screen. ```bash adb devices ``` Expected output — the device must be listed with the state `device`: ``` List of devices attached 192.168.1.50:5555 device ``` If you have no cable, connect over the network instead (the IP is shown under **Settings → Device Preferences → About → Status**): ```bash adb connect 192.168.1.50:5555 adb devices ``` Now measure storage: ```bash adb shell df -h /sdcard ``` **Why:** `adb` (Android Debug Bridge) is the standard command-line channel to the device. It installs packages and copies files with the same permissions the system uses, which is exactly what a manual file copy from a file manager often gets wrong. No root is needed — this is the supported path. If you have no PC at all, an on-device shell via Termux works as a fallback; see [How to Run Linux on Android Without Root: Termux, PRoot, and AI Tools](https://ai-release.org/guides/kak-zapustit-linux-na-android-bez-root-termux-proot-i-i.html?utm_source=tg&utm_medium=channel&utm_campaign=guide_inline&utm_content=guide_to_guide). **How to check:** `adb devices` shows `device` and `df -h /sdcard` shows an `Avail` column larger than your `.obb` file size. Example: if `Avail` reads `12G`, a 2 GB data file fits with room to spare. ## Step 2. Install the APK and place the OBB data ![Illustration: Step 2. Install the APK and place the OBB data](https://ai-release.org/guides/img/kak-zapustit-metal-gear-solid-2-hd-i-drugie-porty-nvidi-en-2.jpg) **What to do:** install the package, then push the data file into the exact folder Android expects. ```bash adb install -r -g game.apk ``` `-r` reinstalls over an existing copy, `-g` grants all runtime permissions at install time. Expected output: ``` Performing Streamed Install Success ``` Then create the data folder and push the file: ```bash adb shell mkdir -p /sdcard/Android/obb/ adb push main...obb /sdcard/Android/obb// ``` Expected output ends with a transfer line such as `1 file pushed ... bytes in s`. Where each file goes: | File type | Destination | Command example | |---|---|---| | `.apk` | Installed by `adb`, not copied manually | `adb install -r -g game.apk` | | Main data | `/sdcard/Android/obb//main...obb` | `adb push main.obb /sdcard/Android/obb//` | | Patch data | Same folder, `patch...obb` | `adb push patch.obb /sdcard/Android/obb//` | **Why:** large Android games ship as a thin APK plus an OBB — an "Opaque Binary Blob", i.e. a compressed asset archive the engine reads at runtime. The engine looks it up by package name and version code, so a file in the wrong folder or with a mismatched version name is simply invisible to the game, and it either re-downloads or crashes. Confirm the exact expected file name in the documentation for your port. **How to check:** list the folder and confirm the size matches the source file: ```bash adb shell ls -l /sdcard/Android/obb// ``` Expected output — a line with `-rw-rw----` permissions and a byte count close to your local file: ``` -rw-rw---- 1 u0_a123 sdcard_rw 2147483648 2024-01-01 12:00 main...obb ``` ## Step 3. Launch the game and verify it starts cleanly ![Illustration: Step 3. Launch the game and verify it starts cleanly](https://ai-release.org/guides/img/kak-zapustit-metal-gear-solid-2-hd-i-drugie-porty-nvidi-en-3.jpg) **What to do:** start the app by package name and watch the log for crashes. ```bash adb logcat -c adb shell monkey -p -c android.intent.category.LAUNCHER 1 ``` Expected output: ``` Events injected: 1 ``` Then stream the log: ```bash adb logcat | grep -iE "AndroidRuntime|" ``` **Why:** `monkey` with the LAUNCHER category sends the same intent the home screen does, so it proves the package is registered and its main activity is resolvable. Logcat then tells you whether the process died on startup or is running — a black screen with a clean log usually means the data file is missing, not that the install failed. **How to check:** the game reaches its title screen, and the log contains no `FATAL EXCEPTION`. Success looks like this: `Events injected: 1`, the splash screen appears within a few seconds, and `adb shell pidof ` returns a process ID. ```bash adb shell pidof ``` Example output: `12345` — a number means the process is live. ## Troubleshooting **Problem. The install aborts immediately with an ABI error** - Error: `Failure [INSTALL_FAILED_NO_MATCHING_ABIS: Failed to extract native libraries, res=-113]` - Cause: the APK contains native `.so` libraries for a CPU architecture your device does not have — typically an `armeabi-v7a` or `arm64-v8a` build installed on a device with a different ABI. SHIELD ports are built for SHIELD hardware. - Solution: check the target device in the port's documentation, then confirm the device's own ABI and compare: ```bash adb shell getprop ro.product.cpu.abi adb shell getprop ro.product.model ``` If the output does not match the build you downloaded, you have the wrong package for that device. **Problem. The push fails with a permission error** - Error: `adb: error: failed to copy 'main.obb' to '/sdcard/Android/obb//main.obb': remote Permission denied` - Cause: `/sdcard/Android/obb/` does not exist yet, or the shell user cannot write into a folder owned by another app. - Solution: create the folder through the shell first, then push, and confirm ownership: ```bash adb shell mkdir -p /sdcard/Android/obb/ adb shell ls -ld /sdcard/Android/obb/ adb push main.obb /sdcard/Android/obb// ``` **Problem. Game launches but shows a black screen or asks to download data again** - Error: the log repeats `E/AndroidRuntime: FATAL EXCEPTION: main` or the in-game prompt "Download failed" / "Additional data required". - Cause: the OBB is missing, sits in `/sdcard/Android/data/` instead of `/sdcard/Android/obb/`, or its name does not match the installed version code. - Solution: read the installed version code and rename the file to match, then relaunch: ```bash adb shell dumpsys package | grep versionCode ``` Use that number as `` in `main...obb`, re-push the file, and clear the app's stale state with `adb shell pm clear `. ## Summary and next steps Installing a SHIELD port is three commands — `adb install`, `adb push` into `/sdcard/Android/obb//`, and a launch verified through `adb logcat`. Once the pattern works for one title, repeat it for the rest of the ports in the collection and keep a note of each package name and version code. ## FAQ **Do I need root to install these ports?** No. Enabling USB debugging is enough; `adb install` and `adb push` run with normal shell permissions. Root is only relevant for modifying system partitions, which this procedure never touches. **Will the APK run on a regular Android phone instead of a SHIELD device?** Usually not without issues. The ports ship native libraries compiled for SHIELD hardware, so a different chipset typically fails at install with `INSTALL_FAILED_NO_MATCHING_ABIS`. Check the documentation for the list of supported devices. **Where exactly does the OBB file go?** Into `/sdcard/Android/obb//`, not into `/sdcard/Android/data/`. The file name must follow `main...obb`, where `` is the installed version code reported by `adb shell dumpsys package | grep versionCode`. **The game downloaded its data again on first launch — did I do something wrong?** Yes, most likely the OBB name or location was wrong, so the engine ignored your copy and fetched its own. Re-check the folder listing with `adb shell ls -l /sdcard/Android/obb//` and compare the version code before relaunching.