Where to unpack the game cache on Android: a complete guide with paths and errors

Unpacking the cache (OBB files) is a mandatory step for launching many mobile games on Android, especially if you downloaded the APK from third-party sources. Even experienced users sometimes encounter problems: the game does not see files, displays an error Error 2 or does not start at all. Most often there is only one reason - the cache is unpacked into the wrong folder.

In this article we will examine all possible ways to place the OBB cache on different versions of Android, including features for devices with root access and without it. You will also learn how to avoid common mistakes when transferring files, why some games require additional rights, and what to do if standard folders do not work. We will separately consider the nuances for emulators (BlueStacks, LDPlayer) and devices with custom firmware.

If you have already tried to unpack the cache, but the game still does not work, there is one at the end of the article FAQ with solutions for 90% of cases. And for those who are just starting out, we have prepared step-by-step guide with visual examples of paths.

What is OBB cache and why it needs to be unpacked

Files with the extension .obb (or .zip in some games) are additional datathat do not fit in the APK due to restrictions Google Play (maximum 100 MB for free applications). They store:

• 🎨 High-resolution graphics (textures, 3D models)
• 🎵 Sound tracks and music
• 🗺️ Level maps, locations, scripts
• 📄 Localizations in different languages

When you install the game from Google Play, the cache is downloaded automatically. But if the APK is downloaded from a site like APKMirror or TapTap, the files .obb will have to be placed manually. And here the problems begin: Android does not allow you to simply write data to system folders, and the paths to the cache differ depending on the OS version and device manufacturer.

For example, on Samsung Galaxy s Android 13 the path will be one, but on Xiaomi Redmi s Android 12 — to others. And if you mix up the folders, the game either won’t launch or will start downloading the cache again, taking up traffic.

Standard paths for unpacking the cache on Android

In 95% of cases, OBB files should be placed in one of three paths. The choice depends on whether where the game is installed: in the internal memory or on the SD card.

Where to get game package (for example, com.gameloft.android.ANMP.GloftA8HM)? It can be found:

• 🔍 In the name of the APK file (usually listed after the game name)
• 📱 In the application settings on the phone: Settings → Applications → [Game] → Information
• 🌐 On the website APKMirror or in the game description on Google Play

Important! The folder with the name of the game package is needed create manually. For example, if the package com.rockstargames.gtasa, the path will be:

/sdcard/Android/obb/com.rockstargames.gtasa/

Features for different versions of Android

With the release Android 11 Google has introduced Scoped Storage a system of limited access to storage. This has affected the way applications (and users) interact with files. Let's look at the key differences:

Android 10 and older

Before Android 10 users could freely write files to any folders through the file manager. The ways were simple:

• 📁 Internal memory: /sdcard/Android/obb/
• 📁 SD card: /storage/extSdCard/Android/obb/ (on some devices)

Android 11, 12, 13 and later

C Android 11 direct access to folders is limited. Now:

• 🔒 File managers see the "virtual" path /storage/emulated/0/, but physically the files are stored in an encrypted partition.
• 📎 To write to Android/obb/ may require permission to manage files (configured in the parameters developer).
• 🚫 Some applications (for example, ES Explorer) have lost access to system folders.

If your file manager cannot write files in obb/, try:

1. Use Total Commander or FX File Explorer (they support Scoped Storage).
2. Connect the phone to the PC and transfer files via MTP (transfer mode data).
3. Temporarily grant rights to the manager root (if the device is rooted).

adb shell mkdir /sdcard/Android/obb/com.example.game

How to unpack the cache on devices with root access

If your smartphone rooted, you have two advantages:

1. You can write files to any folders, including system ones.
2. You can change access rights (chmod) for OBB files if the game does not see them.

Instructions for root users:

1. Open Root Explorer or Solid Explorer (with root support)

2. Go to /sdcard/Android/obb/ (or create a folder if it doesn’t exist)

3. Create a folder with the name of the game package (for example, com.gameloft.android.ANMP.GloftA8HM)

4. Copy the .obbfile to the created folder

5. Click on the file, select Permissions and set the rights rw-r--r-- (644)

6. Reboot the device (sometimes required to apply rights)

-->

If the game still does not see the cache, check:

• 🔄 Is it specified correctly path (sometimes games look for files in /data/data/[package]/files/).
• 🔐 Are the files blocked SELinux (checked by command ls -Z v Terminal Emulator).
• 📦 Does it match cache version with the APK version (for example, the cache for GTA San Andreas 2.00 is not suitable for the version 2.10).

Unpacking the cache in emulators (BlueStacks, LDPlayer, MuMu)

Emulators Android on PC have their own file system, and the paths to the cache differ from real devices. Let's consider popular emulators:

Action algorithm for emulators:

1. Download the OBB file to your PC and do not extract it it (if it is an archive).
2. Open the emulator folder (see table above) and find Android/obb/.
3. Create a folder named game package (for example, com.epicgames.fortnite).
4. Move the .obbfile to the created folder.
5. Run the game from the emulator (not through the desktop shortcut!).

Attention! In BlueStacks 4 and older, the path is different from BlueStacks 5. If you have an old version, look for the folder at:

C:\ProgramData\BlueStacks\Engine\UserData\SharedFolder\

Typical errors and how to fix them

Even if you unpacked the cache correctly, the game may not start. Here are top 5 errors and their solutions:

1. Error "File not found" or "Error 2"

Causes:

• 📌 Incorrect folder name (for example, an extra space or an error in the package).
• 📌 File .obb renamed (must match the original name).
• 📌 The cache was downloaded for another version of the game (for example, for GTA SA 1.08, but for you 2.00).

Solution: check file integrity (compare hash sums with the original) and reinstall the game.

2. The game starts downloading the cache again

Reasons:

• 🔄 The files .obb are in the wrong folder (for example, in Download instead obb).
• 🔄 File permissions are incorrect (should be 644).
• 🔄 The cache is damaged (try downloading again).

Solution: delete the game folder in /data/data/[package]/ (requires root) or reinstall the APK.

3. The game crashes at startup

Reasons:

• 💥 Incompatibility of the cache version and APK.
• 💥 Conflict with mods (if patches have been installed).
• 💥 Not enough memory on device.

Solution: check the game requirements on Google Play and free up space.

4. The obb folder is not created

Reasons:

• 📂 The file manager does not have write permissions.
• 📂 The device has encryption enabled (for example, on Samsung Knox).

Solution: use ADB to create a folder:

adb shell mkdir -p /sdcard/Android/obb/com.example.game

5. The game asks to update the cache

Reason:

• 🔄 You have an outdated version OBB files.
• 🔄 The developers changed the cache structure (for example, after a major update).

Solution: download the current cache from the official source.

Additional tips and lifehacks

A few advanced tricksthat will help avoid problems:

• 🔧 Backup the cache: before updating the game, copy folder obb on the PC. If the cache disappears after the update, you can restore it.
• 🔧 Usage symlinks: if the game looks for the cache in a non-standard folder, create a symbolic link (requires root):

  ln -s /sdcard/Android/obb/com.game /data/data/com.game/files/obb

• 🔧 Checking hash sums: compare MD5 or SHA-1 downloaded cache with the original (you can via 7-Zip or HashMyFiles).
• 🔧 Clearing the Dalvik cache: if the game lags after installing the cache, clear Dalvik/Cache via Recovery (for rooted devices).

Critical! Some games (for example, PUBG Mobile or Call of Duty: Mobile) use Additional configuration files in the folder /Android/data/[package]/files/. If you are transferring the cache to a new device, copy this folder too, otherwise the settings will be reset.

Useful for emulators know:

• 🖥️ B BlueStacks you can increase the FPS limit for games by editing the file BlueStacks.conf (find through disk search C:).
• 🖥️ B LDPlayer for better turn on performance VT virtualization in the settings.

FAQ: Frequently asked questions about unpacking the cache