How to properly give access to storage to an Android application: all the methods and nuances

Providing access to device storage is one of the most common tasks when working with Android applications. Without this permission, apps will not be able to save files, download media, or sync data. However, with the release of new versions of Android (especially Android 10+), the rights management mechanism has become significantly more complicated. Now users have to understand the runtime permissions, scoped storage and restrictions for different file types.

In this article we will take a detailed look at all the current ways to provide access to storage - from standard settings to hidden features for advanced users. You will learn how permissions differ for Android 13, Android 12 and older versions, what to do if the application does not see files, and how to bypass common restrictions without root access. We will pay special attention to security: we will explain what risks wide permissions bring and how to minimize them.

Why applications need access to storage

Modern Android applications request access to storage for several key reasons:

• 📁 Saving user data: from documents and photos to cache and settings. Without this permission, applications would have to store everything in an isolated sandbox, which would limit functionality.
• 🔄 Import/export files: messengers (for example, Telegram or WhatsApp) will not be able to upload media to chats, and file managers will not be able to copy data between folders.
• ☁️ Synchronization with clouds: Google Drive, Dropbox and analogues require access to automatically upload/download files.
• 🎮 Modifications and user content: games (for example, Minecraft or GTA San Andreas) will not be able to download maps, skins or saves.

However, with the release of Android 11 (API 30) Google has tightened its permission policy, dividing access into:

• 📂 Partial access — only to selected files/folders (via Storage Access Framework).
• 🔓 Full access — to the entire storage (requires special permission MANAGE_EXTERNAL_STORAGE, which is issued only to system and some privileged applications).

⚠️ Attention: Starting from Android 14even applications with full access to the storage will not be able to see files of other apps without explicit user permission via MediaStore or DocumentsUI.

Standard method: granting permission via settings

The simplest method is to grant access directly to the application menu. The instructions are valid for all versions of Android from 6.0 Marshmallow to 14:

1. Open Settings → Applications (or Settings → All applications on some firmware).
2. Find the desired application in the list and tap on it.
3. Go to the section Permissions (or Rights).
4. Find the item Storage (may be called Files and media) and move the switch to the position Allow.

On Android 11+ the interface may differ:

• 🔹 If the application requests limited access, the system will offer to select specific files/folders through a standard file manager.
• 🔹 For Full access (for example, for Total Commander or FX File Explorer) You will need to manually activate the option Manage all files in the application settings.

If the item Storage is not in the list of permissions, this means:

• 📌 The application does not request access to files (for example, a simple calculator).
• 📌 Permission has already been granted earlier.
• 📌 The device has custom firmware with non-standard rights settings.

Features for different versions of Android

The storage management policy has changed dramatically with the release of new OS versions. Below are the key differences:

Android version	Default access type	Restrictions	How to bypass
Android 5.1 Lollipop and below	Full access to the entire storage during installation	No division into "internal" and "external" memory	Not relevant
Android 6.0–9.0	Permissions are requested upon first launch	Applications see all files, but cannot modify system folders	Use adb for forced granting of rights
Android 10 (API 29)	Scoped Storage: access only to your files and selected media	Prohibition of writing to /sdcard/DCIM, /sdcard/Download without explicit user selection	Request access via Storage Access Framework
Android 11 (API 30)	Complete ban on access to files of other applications	Permission required MANAGE_EXTERNAL_STORAGE for general access	Use MediaStore API or request an exception from Google
Android 13+	Granular permissions for photos, video, music and documents	Applications do not see the path to the files, only the URI	Integrate Photo Picker to select files

For example, on Android 13 application WhatsApp When you try to save a photo to the gallery, it will request separate permissions for:

• 📷 Access to photos and videos.
• 🎵 Access to audio files (if you need to save a voice message).
• 📄 Access to documents (for PDF or APK).

⚠️ Attention: On devices Samsung, Xiaomi and Huawei additional restrictions may apply due to proprietary shells (One UI, MIUI, EMUI). For example, in MIUI 14 You need to separately activate the "Show hidden files" option in the security settings.

How to give access to storage via ADB (for advanced users)

If the application cannot obtain permissions through the standard interface (for example, without Android 11+ without permission), you can use MANAGE_EXTERNAL_STORAGE), can be used Android Debug Bridge (ADB). This method works on all versions of the OS, but requires a connection to a computer.

Step-by-step guide:

1. Enable Developer mode on your phone: go to Settings → About phone and tap on the item 7 times Build number.
2. Go back to Settings → System → For developers and activate USB debugging.
3. Connect the phone to the PC, install drivers ADB (for example, via Platform Tools from Google) and run the command:

   adb devices

   to ensure success connection.

4. Give permission with the command:

   adb shell pm grant com.example.app android.permission.READ_EXTERNAL_STORAGE
   adb shell pm grant com.example.app android.permission.WRITE_EXTERNAL_STORAGE

   (replace com.example.app with the actual application package).

For Android 11+ an additional command may be required for full access:

adb shell appops set com.example.app MANAGE_EXTERNAL_STORAGE allow

Method limitations:

• ⚠️ After reinstalling the application, permissions are reset.
• ⚠️ On some firmware (for example, ColorOS from Oppo) ADB commands may be blocked.
• ⚠️ Google Play Protect may regard forced granting of permissions as suspicious activity.

Problem solving: the application does not see files or requests access again

If after granting permissions the application still does not work with files, check the following points:

• 🔍 Cache and application data: sometimes the crash occurs due to damaged temporary files. Try clearing the cache in Settings → Applications → [Application name] → Storage → Clear cache.
• 📱 Power saving mode: on Xiaomi, Huawei i Samsung background application activity may be blocked. Add the app to battery exceptions.
• 🔒 Proprietary restrictions: for example, MIUI you need to disable the "Privacy Protection" option for the file manager.
• 🔄 Permission conflict: if the application requests access via Storage Access Framework, but at the same time tries to use outdated APIs, errors may occur.

Typical errors and their solutions:

Error	Cause	Solution
"No access to folder"	The application does not have permission to write to /sdcard/Download	Save the file to another folder or use SAF to select the target directory
"Permission denied"	The user clicked "Deny" and checked the "Don't ask again" checkbox	Reset permissions in Settings → Applications → [Name] → Permissions → Reset
"File not found"	The application looks for the file in the absolute path, but because Scoped Storage does not see it	Use MediaStore or ContentResolver to work with files

Why do applications lose access after updating Android?

Updating the system (for example, from Android 12 to 13) resets some storage-related permissions. This is due to the tightening of Google's privacy policies. To restore access, you need to manually reassign permissions or reinstall the application.

If the problem persists, check the application logs via adb logcat. Look for lines with tags StorageManager, MediaProvider or PackageManager —they will indicate a specific error.

Alternative methods: bypassing restrictions without root access

If standard methods do not work, you can use legal workarounds:

• 📂 Using Storage Access Framework (SAF): many applications (for example, Solid Explorer) support opening files through the system selection dialog. This allows you to bypass restrictions Scoped Storagesince the user explicitly selects a folder.
• ☁️ Cloud storage: syncing files via Google Drive, Dropbox or Nextcloud does not require local permissions.
• 🔗 FUSE-mounting: applications like Mixplorer can mount clouds as local folders via rclone or WebDAV.
• 📱 Work Profile: on some devices (for example, c Android for Work) you can give the application extended rights in the work profile.

For technically savvy users, the method with Shizuku is suitable - a tool that allows you to execute ADB commands without USB debugging. Install Shizuku from GitHub, connect to the server through the app and run the same commands as through adb shell.

⚠️ Warning: Using alternative methods may violate Google Play policies. Some applications (for example, banking) block work on devices with activated debugging or non-standard permissions.

Security: risks and how to minimize them

Providing access to storage is associated with potential threats:

• 🕵️ Data leak: attackers can steal photos, documents or passwords from files.
• 💣 Encryptors: viruses (for example, Android/Simplocker) encrypt files and demand ransom.
• 📊 Collection of analytics: some applications scan the storage for targeted advertising.
• 🔄 Modification of system files: careless actions can lead to OS failure.

How to protect yourself:

• 🛡️ Install applications only from Google Play or trusted sources (for example, APKMirror).
• 🔍 Check permissions before installation: if the flashlight is asking for storage access, this is suspicious.
• 📁 Use separate folders for sensitive data and limit access to them via SAF.
• 🔄 Regularly revoke unnecessary permissions in Settings → Privacy → Permission Manager.

On Android 13+ Google entered Photo Picker —a safe way to choose photo/video without providing full access to the gallery. Recommend developers to integrate this mechanism instead of legacy permissions.

FAQ: Frequently asked questions about access. to storage

🔹 Why did the application stop seeing files after updating Android?

Most likely, permissions were reset due to changes in the privacy policy in the new version of the OS. Go to the application settings and manually grant access to the storage again. If this does not help, try reinstalling the app.

🔹 Is it possible to give access to only one folder and not the entire storage?

Yes, on Android 11+ this is possible via Storage Access Framework. The application must support folder selection through the system dialog. For example, in FX File Explorer you can create a “bookmark” for a specific directory and provide access only to it.

🔹 How to check which applications have access to my files?

Open Settings → Privacy → Permission manager → Storage. A list of all apps with access to files is displayed here. On Android 13+ you can filter by data type (photos, videos, documents).

🔹 Why do some applications ask for permission to “manage all files”?

This is a special permission MANAGE_EXTERNAL_STORAGErequired for file managers, antiviruses and backup utilities. Google limits its issuance: the application must either be systemic or receive approval through Google Play Console. On user devices, it can be issued manually via ADB.

🔹 Is it possible to revoke access to the storage for system applications?

Partially. System applications (for example Google Photos or Galaxy Gallery) have built-in permissions that cannot be revoked through the standard interface. However, you can limit their access through ADB or disable the application completely (if this is not critical for the operation of the OS).