Installing heavy mobile games on devices with limited capabilities or without direct access to Google Play often turns into a real quest. The user downloads the APK file, launches it, but instead of the treasured game world, he sees an error message or a requirement to download gigabytes of data. It is at this moment that a critical question arises: where to copy the game cacheso that the application finally starts correctly. Understanding the Android folder structure can be difficult, especially taking into account changes in the system security policy in the latest versions of the OS.
Incorrect placement of cache files is the most common cause of failures when launching “heavy” projects. The system simply cannot find the resources it needs to render graphics and load levels. In this article, we will analyze in detail the logic of the file system, the correct paths for different firmware versions, and methods for solving problems if standard instructions do not work.
First, it is important to understand what a cache is in the context of mobile entertainment. These are not temporary browser files, but full-fledged archives with textures, sounds, character models and location maps. Their volume can reach tens of gigabytes, so it is impossible to store them in the application’s internal memory (which is often limited). Developers place this data in separate directories, access to which must be provided manually during manual installation.
Folder structure and data placement logic
The Android file system is strictly regulated, and violation of this structure leads to the software not working. The main storage of user data is located in the root of the internal storage or SD card. It is here, to the root, that the paths that every advanced user needs to remember usually lead. There are two key directories here: Android/obb and Android/data.
The folder Android/obb is intended for storing the main archive files of the game. Usually these are files with the extension .obbthat contain the "body" of the game. If you downloaded the cache as a ZIP archive, you need to unpack it. Inside you will find a folder with the same name as the application's package name (for example, com.rockstargames.gtasa). This entire folder needs to be moved to the directory obb. Important: the folder itself with the package name must be inside obb, and not the files must be scattered at the root of this directory.
The second important zone is Android/data. Additional cache files, profile settings, or save files are often copied here (although saves may be located in other places). The structure here is similar: a folder is created with the name of the package, and inside it there are subfolders like files. Confusion between obb and data is a common mistake. If a game requires a cache, but you put it in data, it most likely will not start, and vice versa.
Always check the name of the cache folder. It must exactly match the package name of the APK file. You can find it through the file manager or APK installer by looking at the file properties before installation.
It is worth noting that starting from Android 11 and higher, access to the folder Android/data for third-party file managers is limited by the Scoped Storage security policy. This means that standard Explorer may not show the contents of this folder or prohibit writing to it. In such cases, you need to use specialized managers with special access rights or connect to a PC.
Step-by-step guide for installing a cache without root access
Most users do not want to obtain root access due to the risk of losing the warranty or the possibility of “bricking” the device. Fortunately, in 90% of cases, installing a cache is possible without deep intervention in the system. The algorithm of actions remains the same for all devices, only the interface of the file managers differs.
First you need to prepare the files. Download the APK game installer and archive with cache (usually a ZIP or RAR file). Install the APK, but do not start the game. If you run it before migrating the cache, it may create empty configuration files that will prevent it from working correctly later, or it may simply throw an error and close. Then unpack the archive with the cache into any convenient temporary folder.
Now let's start moving. Open a file manager (recommended to use Total Commander, FX File Explorer or MIUI File Manager). Find the unpacked cache folder. Select it and select the "Move" or "Cut" function. Go to the root of the internal storage, then to the folder Android. Depending on the cache type, go to obb or data. Paste the folder here.
☑️ Cache installation algorithm
After moving, check the access rights. In rare cases, if files were copied from external media, the system may restrict read rights. Android usually corrects this on first launch, but if the game crashes, make sure the files are not corrupted. The size of the folder in the new location must match the size of the original archive.
⚠️ Attention: On some smartphones from Xiaomi, Realme and other brands with aggressive memory optimization, the system can automatically clean the folder
Android/obbIf there is not enough space or after a reboot, if the game was not added to the Memory Cleanup exceptions. Add the game to the list of protected applications in the battery settings.
Features of working with root access and system folders
The presence of root access allows access to hidden sections of the system that a normal user cannot access. This is true for older games that were developed before the introduction of modern data storage standards, or for specific modifications. In such cases, the cache may be required not in /sdcard/Android, but directly in the system partition /data/data.
Path /data/data/[package_name]/ is the sacred storage for each application. Only the application itself and the superuser (Root) have the right to write there. If the instructions for a modified game say "copy files to /data/data", you will need a file manager with Root support, for example Root Explorer or Mixplorer. When you enter this folder, the manager will ask you to grant superuser rights - confirm the action.
Copying to the system partition requires special care. An error in permissions can result in the game not seeing files, even if they are physically located in the desired folder. After copying files, you often need to manually set permissions rw-r--r-- (644) for files and rwxr-xr-x (755) for folders. This is done through the "Access Rights" or "Permissions" menu in the file manager.
What to do if the game crashes after copying to /data/data?
Often the problem lies with the owner of the files. After copying through the Root manager, root becomes the owner of the files. Try changing the owner to "system" or "u0_a..." (application user number), although in modern versions of Android the game often picks up files independently of the owner if read permissions are open.
Using Root also allows you to transfer the applications themselves, along with their cache, to the SD card in full operation mode, and not as “external storage”. This is done through applications like Link2SD or Titanium Backup. However, remember that when you reset the settings or flash the firmware, all data in /data will be permanently deleted.
Solving access problems on Android 11, 12, 13 and later
With the release of Android 11, Google introduced strict restrictions on access to the folder Android. Third-party applications can no longer simply read and write to Android/data i Android/obb. This causes panic among users who are accustomed to the freedom of previous versions. However, workarounds exist and they are quite simple.
The most reliable way is to use a file manager ZArchiver or an updated version Total Commander with a plugin. When you try to enter a folder Android such an application will request special permission from the system. A system window will appear with a “Use this folder” button. You need to click it and confirm the action by clicking "Allow". After this, the manager will have full access to the subdirectories.
An alternative method is to connect the smartphone to the computer via USB. On PCs, Scoped Storage limitations do not fully apply when using file transfer mode (MTP). You can easily go into the phone’s memory, find the folder Android and upload the cache there using standard Windows or macOS copying. This is often faster and more convenient than fiddling with resolutions on a small screen.
| Android version | Access Android/data | Recommended method | Limitations |
|---|---|---|---|
| Android 10 and below | Full access | Any file manager | Absent |
| Android 11 | Limited | ZArchiver / PC connection | Specialist required. resolution |
| Android 12-13 | Blocked for many | Shizuku + FM / PC | System restrictions |
| Android 14+ | Strictly prohibited | Only PC or ADB | Direct access is closed |
If none of the methods helps, you can use ADB debugging. The command adb shell allows you to manage files from your computer with rights close to system ones. This is a method for advanced users, but it guarantees results where graphical interfaces are powerless.
Moving cache to an SD card: pros and cons
The internal memory of modern smartphones is often full, and microSD memory cards offer a cheap way to expand storage. There is a logical desire to transfer the heavy cache of games to the card. Technically this is possible, but it has its pitfalls, which are worth knowing in advance.
Many games categorically do not recommend or even do not support running the cache from an external memory card. The reason lies in the read/write speed. Even fast UHS-I cards can be inferior to internal UFS 3.1 flash memory in random reading of small files, which leads to long level loading times, texture stuttering, and stuttering. In some cases, the game may simply not see the cache if it is on removable media.
If you still decide to transfer data, the algorithm is the same: create a folder structure Android/obb already on the SD card itself and place the files there. In the settings of some file managers, you can make the memory card the main storage by default, but this does not guarantee that all games will work. SD card must be formatted as internal storage (Adoptable Storage) so that the system perceives it as a single whole, but this function is not available on all smartphones.
⚠️ Attention: When formatting a card as internal storage, all data on it will be deleted and it will become unreadable for other devices (cameras, PCs) without unlocking with the encryption key of a specific phone. Do not use this method for cards that you plan to frequently move between devices.
Common errors and ways to resolve them
Even after following all the instructions, users are faced with the fact that the game writes “Cache not found” or crashes on the splash screen. Most often the problem is trivial: double nesting of folders. When unpacking an archive, a structure like Cache folder/com.game.name/filesis often created. If you transfer this entire structure into Android/obb the path will become incorrect. Correct path: Android/obb/com.game.name/files.obb. The extra intermediate folder needs to be deleted.
Another common error is a mismatch between the APK and cache versions. Developers regularly update games. If you installed the latest version of the APK from the Play Market, but downloaded the cache from a third-party site a month ago, the checksums of the files will not match, and the game will require resuming or will refuse to work. Always try to download the APK and cache from the same source and release date.
Sometimes clearing the application data before trying again helps. Go to Settings → Applications → [Your Game] → Storage and click "Clear data". Then check again for files in the folders. This will reset erroneous configurations that could have been saved during previous unsuccessful launches.
The main cause of errors is a violation of the folder nesting structure. The path should look like a “matryoshka”, where the name of the cache folder corresponds to the package name of the game, without unnecessary intermediate directories.
FAQ: Answers to popular questions
Is it possible to delete the Android/obb folder after installing the game?
No, it is not possible. Unlike installation files, the folder obb contains the resources the game needs to operate during the process. If you delete it, the game will stop launching or require you to download the data again. You can delete these files only after completely deleting the game itself.
Why does the game require you to download the cache again, although I have already copied it?
Most likely, you put the files in the wrong folder (for example, in data instead of obb) or the folder name does not match with the application package name. It is also possible that the cache version does not match the version of the installed APK.
How to find the correct batch name of the game to create the folder?
The batch name is usually indicated in the name of the downloaded archive with the cache (for example, cache_com.gameloft.android.ANMP.GloftA9HM.zip -here is the name com.gameloft.android.ANMP.GloftA9HM). You can also view it on Google Play via a link to the game or through applications like App Inspector.
Does moving the cache affect the speed of the game?
Yes, it does. The internal memory of a smartphone is usually faster than a memory card. If the game is “heavy” and requires constant loading of textures (open world), storing the cache on a slow SD card can cause micro-freezes and increased loading time for locations.