Users of Android mobile devices are often faced with the need to find hidden files, make a deep backup, or free up space by deleting “garbage” that is not visible in the standard file manager. Understanding the logical structure of a file system is key to effective device management. Unlike desktop operating systems, the Android architecture strictly distinguishes between private and public areas of information storage.
In this article we will examine in detail the physical and logical paths along which caches, databases and software installation packages are located. We'll explain the difference between internal memory and a memory card, and also touch on the changes that Google has implemented in the latest versions of Android, limiting access to folders Android/data without obtaining special rights.
Knowing the exact location of data will help you not only transfer game progress or application settings when changing smartphones, but also diagnose problems with memory overflow. It is important to approach this issue consciously, since interfering with system partitions requires caution and understanding of the consequences.
Logical structure of device memory
The Android file system is based on the Linux kernel, which implies a strict hierarchy of directories. However, for the user, this structure is abstracted into two main logical zones: the system partition, read-only (without root), and the user data partition. Internal memory The smartphone is technically an eMMC or UFS partition mounted in the root directory.
When you connect your smartphone to your computer via USB, you do not see the entire file system, but only its emulated part. This is done for security purposes to prevent accidental deletion of critical system files. Access to the true root of the file system (/) is only possible through USB debugging (ADB) or with superuser rights.
⚠️ Warning: Directly editing files in system partitions without a backup copy may cause the device to fail to boot (bootloop). Always do a full dump before making changes to root directories.
Modern versions of Android use a file system ext4 or f2fsthat support journaling. This means that the directory structure is rigidly fixed by the firmware manufacturer. Understanding this structure is necessary to work with advanced data recovery tools.
Use the "Termux" application or a terminal emulator to view the folder structure through Linux commands, even without root access you will see more than in a regular Explorer.
Public storage: /sdcard directory and its subfolders
Traditionally, users are used to searching files in the folder that appears as "Internal Memory". In fact, the path to it in the system looks like /sdcard or /storage/emulated/0. This is not a physical memory card, but an emulation of a partition in the internal memory, accessible to all applications without special permissions.
This is where media files, downloads and general application data are stored. In recent years, Google has implemented a "Scoped Storage" policy, which has changed the rules for accessing this section. Now applications can freely write only to their own subfolders, without having access to the entire disk.
Consider the main directories where user data is accumulated:
- 📂 Android/data —Cache, databases, and additional files (OBB) for games and applications are stored here. Access to this folder in Android 11 and higher is closed to third-party file managers without root.
- 📂 Android/obb — directory for large game data files that do not fit in the main APK file.
- 📂 Download — standard folder for all files downloaded from the browser or instant messengers.
- 📂 DCIM — storage location for photos and videos taken by the camera devices.
Many users mistakenly believe that cleaning a folder Android/data is safe. In fact, deleting the contents of this directory will result in resetting application settings, losing progress in offline games and having to re-download heavy resources.
Private application storage: section /data/data
The most valuable and protected information is in the section /data/data. This directory contains the private files of each installed application. Only the application itself and the user with rootrights have access to it. This is where SQLite databases, settings files SharedPreferences and temporary files are stored.
The path structure usually looks like this: /data/data/com.example.appwhere com.example.app is the app's unique batch identifier. Inside this folder there are subdirectories files, cache, code_cache and databases. It is in the folder databases that files with the history of correspondence, contacts and action logs are often located.
It is impossible to extract data from this section using standard methods. Requires the use of a utility ADB with superuser rights or specialized backup managers such as Titanium Backup or Swift Backup. These apps can archive the contents of private folders along with access rights.
adb shellsu
cd /data/data/com.whatsapp
ls -la
The above sequence of commands demonstrates how to go to the WhatsApp messenger directory through the terminal and view its contents. Without entering the command su (switch user), access will be denied by the SELinux security system.
What is symlink in Android?
A symbolic link (symlink) is a shortcut to a file or folder. On Android, the /sdcard folder is often a link to /storage/emulated/0, which allows you to maintain compatibility with older access paths.
OBB directory and heavy game data
For modern mobile games with high-quality graphics, a single APK installation file is not enough. Graphic assets, sounds and models take up gigabytes of space and are stored in the /sdcard/Android/obbdirectory. The files here have the extension .obb and are archived resources.
When deleting a game through the standard Android settings interface, the system usually offers to delete the OBB data associated with it. However, when manually deleting an APK file through a file manager, the folder in obb may remain, taking up space as dead weight. This is a common reason for lack of memory on budget smartphones.
Transferring these files to a microSD memory card in modern versions of Android is often impossible or unstable. The system mounts the card as removable storage, and applications that expect data along a strictly defined path in the internal memory simply do not see it on the external drive.
| Data type | Location | Access without Root | Impact on operation |
|---|---|---|---|
| APK installer | /data/app | Partially | Critical (application launch) |
| Application cache | /data/data/.../cache | No | Medium (boot acceleration) |
| Game resources | /sdcard/Android/obb | Yes | Critical (textures, sounds) |
| User settings | /data/data/.../shared_prefs | No | High (loss of logins, settings) |
⚠️ Attention: Interface and access options folders may differ depending on the manufacturer's shell (MIUI, OneUI, ColorOS). Always check the relevance of the paths in the documentation for your specific model.
Features of working with a memory card (External SD)
Using an external memory card to store application data in Android is associated with a number of limitations. Starting with Android 6.0, the "Adoptable Storage" feature appeared, allowing you to format the card as part of the internal memory. In this case, the data is encrypted and becomes unreadable on other devices.
If the card is used as portable storage, applications can only save media files and documents to it. Transferring the application body itself (APK) and its private data (/data/data) to a card without root access and specific manipulations with link2sd is impossible. The system deliberately limits this feature for the sake of stability, since the reading speed of memory cards is often lower than the speed of internal flash memory.
When you remove a memory card, applications whose data was stored there may crash with an error or lose some functionality. It is recommended to use the memory card primarily for storing photos, videos and music, leaving fast internal memory for system processes and active applications.
☑️ Preparing for data transfer
Tools for accessing and managing files
For effective work with the file structure, a standard explorer is not enough. You will need specialized tools. For non-root users, an excellent solution is to use a computer and command adb pull, which allows you to download files from protected partitions to your PC.
Owners of superuser rights can use powerful file managers such as Root Explorer, Mixplorer or Solid Explorer (with the root plugin). These applications allow you to change access rights (chmod, chown), edit system files and move data between partitions.
It is also worth mentioning the utility Shizuku. It allows regular apps to gain enhanced access to system APIs without completely rooting the device, using over-the-air debugging. Through Shizuku, many file managers can now see the contents of a folder Android/data even on Android 11-14.
When working with SQLite databases that are stored in private folders, it is convenient to use database viewers. They allow you to open a file .db and export tables to readable CSV or Excel format, which is useful for analyzing activity history or recovering lost information.
Without root access, you are limited to only the public part of the file system. To have full control over application data, you must obtain superuser rights or use ADB.
Frequently asked questions
Is it possible to transfer the Android/data folder to a memory card?
Directly through the system settings - no. This is only possible using third-party utilities like Link2SD with root access, creating symbolic links. However, this can lead to unstable applications because the speed of the memory card is lower.
Why can't I see the Android/data folder in File Explorer?
Starting with Android 11, Google has restricted access to this folder for all third-party file managers for privacy purposes. You can only see it through the system explorer (to a limited extent) or through file managers with root/ADB rights.
Where are WhatsApp and Telegram messages stored?
Message databases are usually located in a private directory /data/data/com.whatsapp/databases. Backups created regularly can be duplicated in a public folder /sdcard/Android/media/com.whatsapp or /sdcard/WhatsApp/Databases depending on the version of the application.
Is it safe to delete files from the obb folder?
It is safe to delete files from the obb folder only if if the corresponding application has already been removed from the device. If you delete the obb file for an installed game, it will stop launching or will require you to download resources again.
How to find the exact path to the data of a specific application?
Use the command in the terminal or ADB: pm path com.package.name. It will show all the paths associated with this package, including the location of the APK and data directories.