How to Encrypt an SD Card on Android Using Adoptable Storage (No Root)

Many Android users keep photos, videos, and sensitive documents on an external microSD card because the phone’s internal storage is limited. Unfortunately, a regular SD card is just a portable storage medium – anyone who gets hold of it can read the files. Android offers a built‑in feature called adoptable storage that encrypts the card and integrates it with the internal storage, turning the card into a secure extension of the device.

Before you start

• Backup any data on the SD card. Formatting will erase everything.
• Use a high‑quality, Class 10 or higher card. Adoptable storage encrypts the whole card, so a slow card can noticeably affect app performance.
• Charge your phone to at least 50 % or keep it plugged in. The formatting process can take several minutes.
• Make sure your device runs Android 6.0 or newer. The steps below work on stock Android and on most OEM skins (Pixel, OnePlus, Nokia, etc.).
• If you plan to use the ADB method, install the Android SDK Platform‑Tools on a PC and enable Developer options → USB debugging on the phone.

Method 1 – Using the built‑in UI (OEMs that expose the option)

Some manufacturers keep the adoptable‑storage toggle visible in Settings. If you see it, this is the simplest and safest way.

After the conversion, any app you install can be moved to the SD card, and the data stored there is encrypted automatically. To verify encryption, go to Settings → Security → Encryption & credentials. You should see a line stating that “Device encryption is on” and “SD card is encrypted.”

Moving apps and media to the new adoptable storage

1. Open Settings → Apps & notifications → See all apps.
2. Select an app, tap Storage, then tap Change → SD card (or “Internal shared storage”).
3. Repeat for any apps you want to keep on the card. For media, open the Files app, select files, and use Move to → Internal shared storage (the card is now part of that storage).

Method 2 – Using ADB on devices that hide the UI option

Many OEMs (e.g., Samsung, LG) hide the adoptable‑storage toggle in the Settings UI, but the underlying sm (storage manager) commands are still available via ADB. This method works on any Android 6.0+ device with USB debugging enabled.

Step 1 – Prepare your PC

1. Download the Android SDK Platform‑Tools zip for your OS and extract it.
2. Open a command prompt (Windows) or terminal (macOS/Linux) and navigate to the extracted folder.

   cd path/to/platform-tools

Step 2 – Enable USB debugging on the phone

1. Go to Settings → About phone → tap Build number seven times to enable Developer options.
2. Return to Settings → System → Developer options → toggle USB debugging on.
3. Connect the phone to the PC with a USB cable. When prompted on the phone, allow the PC’s RSA key.

Step 3 – Identify the SD‑card disk ID

adb devices

If your device shows up, run:

adb shell sm list-disks

The command returns something like 179,0 – that is the disk identifier for the inserted SD card.

Step 4 – Partition the disk as private (adoptable) storage

adb shell sm partition 179,0 private

Replace 179,0 with the identifier you obtained. The output will confirm the operation, e.g., “Created private partition on disk 179,0.” The phone will now format and encrypt the card. This step may take a few minutes; you can watch progress in the notification shade.

Step 5 – Verify the adoption

adb shell sm list-volumes

You should see a line similar to:

private:179,0 mounted /storage/XXXX-XXXX

The private label confirms the card is now encrypted and treated as internal storage.

Step 6 – (Optional) Move apps to the SD card

Because the card is now part of internal storage, Android’s normal “Move to SD card” UI appears for compatible apps. Follow the same steps described in Method 1, section “Moving apps and media”.

adb shell sm partition 179,0 public

Understanding what adoptable storage actually does

When you format an SD card as private, Android creates a dm-crypt block device backed by the card. A unique encryption key is generated and stored in the device’s Trusted Execution Environment (TEE). The key never leaves the phone, which means the encrypted data cannot be read on another device or by plugging the card into a PC.

Because the encrypted block device is presented as part of the internal storage pool, the system can move apps, cache files, and media across the two physical media transparently. This is why you’ll notice the total “Internal storage” figure increase after adoption.

Common troubleshooting scenarios

1. The SD card is not detected

• Make sure the card is properly seated. Power‑cycle the phone after insertion.
• Test the card in another device (camera, PC) to rule out a faulty card.
• Check for a “Read‑only” lock switch on the card’s adapter – it must be unlocked.

2. Formatting fails with “Unable to format”

• Some low‑capacity cards (< 4 GB) are not supported for adoptable storage. Use a card of at least 8 GB.
• Ensure the card is not already encrypted by another device (e.g., iOS). Reformat it first using the phone’s “Erase & format” option.
• If you’re using the ADB method, try the command with the force flag:

  adb shell sm partition 179,0 private force

3. Apps refuse to move to the SD card

• Only apps that support moving will show the option. System apps and widgets are excluded.
• If the card is still listed as “Portable” in Settings > Storage, the adoption step didn’t complete. Verify with adb shell sm list-volumes.
• Some OEMs impose a minimum free internal‑storage threshold before allowing moves. Free up a few hundred MB and try again.

4. Performance feels slower after adoption

• Adoptable storage encrypts and decrypts data on‑the‑fly, which adds CPU overhead. On older devices this can be noticeable.
• Use a high‑speed UHS‑I or UHS‑II card to mitigate the slowdown.
• If performance is unacceptable, you can revert the card to portable mode (see the ADB public command) and keep only less‑frequent data on it.

5. The phone won’t boot after removing the SD card

• This happens when the system has stored part of an app’s data on the adopted card and the card is suddenly missing.
• Power off the device, re‑insert the card, and boot again.
• If the phone still fails, boot into Safe mode (press and hold the power‑off option) and uninstall or move the offending app.

Best‑practice checklist

• Always back up the SD card before formatting.
• Prefer Class 10 or UHS‑I cards for acceptable performance.
• Keep the card inserted at all times – treat it as part of the phone’s internal storage.
• Regularly check Settings > Storage to monitor free space on both internal and adopted partitions.
• If you plan to sell or recycle the phone, remember that the encrypted card cannot be read elsewhere. Wipe it by re‑formatting as public (portable) or using a PC’s full‑disk erase.

What happens if you lose the phone?

Because the encryption key is stored only in the device’s secure hardware, a stolen phone cannot decrypt the adopted SD card without the unlock PIN/pattern/password. Conversely, if you lose the phone but retain the SD card, the data remains inaccessible – a useful side‑effect for privacy‑conscious users.

By following the steps above you can turn any compatible SD card into a secure, encrypted extension of your Android phone, protect personal files from prying eyes, and free up valuable internal space for the apps you use most.