Fix TWRP Unable to Mount Storage 0MB

If your TWRP recovery shows “Unable to mount storage� or “Internal Storage (0MB)�, you can’t flash ROMs, make backups, or restore files. This usually happens after a failed encryption, a corrupted data partition, or a bad flash. The fix involves wiping the data partition, changing the file system, or removing encryption flags—all doable from TWRP itself.

What You’ll Need

• A device with TWRP already installed (or a way to boot it, e.g., fastboot boot twrp.img)
• A USB cable and a computer (optional but helpful for file transfers)
• Your device’s stock firmware or a known-good ROM zip (if you need to reflash after fixing)
• Patience—this process wipes all data on the device

Step-by-Step

1. Boot into TWRP. Power off the device, then press and hold the volume-up + power buttons (or the key combo for your device) until the TWRP logo appears. If you don’t have TWRP installed, connect the device to a PC and run fastboot boot twrp.img.
2. Check the current storage state. Go to Wipe → Advanced Wipe. Look at the list—if “Data� shows 0MB or “Unable to mount /data� appears, you’re in the right place.
3. Wipe the Data partition. In Advanced Wipe, tick Data (and also Cache and Dalvik/ART Cache if you want a clean slate). Swipe to wipe. This removes encryption and most corruption. After wiping, go back to the main menu and check if storage now shows the correct size.
4. Change the file system (if still 0MB). If the wipe didn’t help, go to Wipe → Advanced Wipe, select Data, then tap Repair or Change File System. Choose Change File System → EXT4 (or F2FS if your device originally used it). Confirm the conversion. This formats the partition from scratch.
5. Format Data (if still broken). Go to Wipe → Format Data. Type “yes� when prompted. This is a full format that removes all encryption and resets the partition. It will wipe everything, including internal storage.
6. Reboot recovery. After formatting, go to Reboot → Recovery. This reloads TWRP and re-reads the partition table. Check storage again—it should now show the full capacity.
7. Transfer files (if needed). If you need to flash a ROM, connect the device to a PC via USB. In TWRP, go to Mount and ensure MTP is enabled. Your device should appear as a drive on the computer. Copy the ROM zip to the internal storage.
8. Flash your ROM (optional). If you had to wipe everything, you’ll need to flash a ROM and a kernel (if separate). Go to Install, select the zip, and swipe to flash. After that, reboot to system.

Common Mistakes

• Wiping only cache or dalvik. These don’t affect the data partition, so the 0MB issue persists.
• Using the wrong file system. Some devices require F2FS for data, but TWRP defaults to EXT4. Check your device’s original file system (often listed in the TWRP wipe screen).
• Not rebooting recovery after a format. TWRP may still show stale info until you reboot.
• Forgetting to reflash a ROM after formatting. Formatting data removes the OS, so you must flash a ROM before rebooting to system.
• Skipping the “Format Dataâ€� step. A simple wipe may not remove encryption flags; only Format Data does that.

Tips

• Always back up your data before attempting any fix—though if you’re already stuck, the data may be unrecoverable.
• If you have a microSD card, use it to store ROMs so you don’t need USB transfer.
• After formatting, set up your device fresh before restoring backups—this avoids re-encryption issues.
• Use the latest TWRP version for your device. Older builds may have bugs with storage mounting.
• If you’re on a device with Dynamic Partitions (most Android 10+), avoid changing the file system of “Systemâ€� or “Vendorâ€�—only touch Data.

Troubleshooting

If the steps above didn’t fix it, try these in order:

• Reinstall TWRP. Flash the TWRP installer zip again or reflash via fastboot. A corrupted recovery can cause mount issues.
• Use a different TWRP version. Sometimes a beta or older version works where the latest doesn’t. Check your device’s XDA forum for known-good versions.
• Check for hardware issues. If the storage still shows 0MB after all wipes and formats, the internal memory chip may be failing. This is rare but possible.
• Restore stock firmware. Use your device’s official flashing tool (e.g., Odin for Samsung, Fastboot for Pixel) to reflash the stock ROM. This repartitions the storage and often fixes mount errors.
• Try a different recovery. If TWRP is completely broken, try OrangeFox or PitchBlack Recovery (if available for your device).
• Check the partition table. In TWRP, go to Advanced → Terminal and type ls /dev/block/bootdevice/by-name to see if the data partition exists. If it’s missing, you may need to restore the partition table via fastboot.

Frequently Asked Questions

Will this wipe my photos and apps?

Yes, formatting data wipes everything on internal storage, including photos, downloads, and app data. Back up anything you want to keep before proceeding.

Why does TWRP show 0MB even after I wiped Cache?

Cache is separate from Data. The 0MB issue is specifically about the Data partition—you must wipe or format Data itself.

Can I fix this without losing data?

Sometimes, if the issue is just an encryption flag, a simple “Wipe Data� (not Format) may preserve files. But if the partition is corrupted, data loss is unavoidable. Try wiping first, then check if storage appears.

What is the difference between “Wipe� and “Format Data�?

Wipe deletes the contents but keeps the file system and encryption flag. Format Data removes the file system entirely and recreates it, which clears encryption and often fixes mount errors.

Do I need to flash a ROM after fixing storage?

If you only wiped data, you can reboot to system and it will boot to the setup wizard. If you formatted data, the system is still there, but your data is gone—so you can boot and set up fresh. If you also wiped system, you must flash a ROM.

Why does my device still show 0MB in TWRP after formatting?

This could indicate a hardware failure or a corrupted partition table. Try flashing stock firmware with your PC—if that doesn’t restore storage, the internal memory may be dead.

Related

• External Hard Drive Formats: Pros & Cons
• Install Plex Media Server on CentOS: Step-by-Step
• Vector Images: What They Are & How to Make One