sodcalculator

10 Tech How-To

How to Recover Android Data After Rooting

Guide 10-34066 · Updated · Step by step

Rooting your Android phone gives you deeper system access, but it also carries a real risk of data loss—whether from a failed boot, a bad flash, or a factory reset gone wrong. This guide walks you through the practical steps to recover your photos, messages, and app data after rooting, using tools that work with a rooted device. You’ll need a computer, a USB cable, and a bit of patience, but no special hardware beyond that.

What You’ll Need

  • A rooted Android phone (bootloader unlocked, Magisk or SuperSU installed)
  • A Windows, Mac, or Linux computer
  • A USB cable that supports data transfer
  • USB debugging enabled on the phone (Settings > Developer Options > USB Debugging)
  • ADB and Fastboot tools installed on your computer (download from the official Android developer site)
  • Optional but helpful: a microSD card or USB OTG drive for storing recovered files

Step-by-Step

  1. Stop using the phone immediately. If you deleted files or performed a factory reset, avoid writing new data to the internal storage. Every new photo, app install, or even a boot can overwrite the deleted data, making recovery harder or impossible.
  2. Enable USB debugging. Go to Settings > About Phone and tap “Build Number” seven times to unlock Developer Options. Then go to Settings > Developer Options and toggle on USB Debugging. If the phone won’t boot, skip this step—you’ll use recovery mode instead.
  3. Install ADB and Fastboot on your computer. Download the platform-tools zip from the Android developer website, extract it to a folder, and open a terminal/command prompt in that folder. Verify the installation by running adb version.
  4. Connect your phone and authorize the computer. Plug the phone into the computer with the USB cable. On the phone, a dialog will appear asking to allow USB debugging—check “Always allow” and tap OK. Then run adb devices to confirm your phone is listed as “device”.
  5. Create a full backup of the current state (if possible). If your phone still boots, run adb backup -apk -shared -all -f backup.ab to create a full backup. This won’t recover deleted files, but it preserves what’s still there so you don’t lose more data while attempting recovery.
  6. Check if the phone boots into Android. If it does, skip to step 8. If it’s stuck in a boot loop or on the logo, boot into recovery mode (usually hold Power + Volume Down, or Power + Volume Up depending on the model). From recovery, try “Reboot system now” first—sometimes a simple reboot fixes a temporary glitch.
  7. If the phone won’t boot, use recovery mode to mount storage. In TWRP or a similar custom recovery, go to Mount and check “Data” and “Internal Storage”. Then on your computer, run adb shell to access the phone’s filesystem. You can copy files out using adb pull /sdcard/DCIM /path/on/computer to save your photos and videos.
  8. Use a data recovery app that works with root. Install a root-enabled recovery app like DiskDigger (root mode) or Dr.Fone – Data Recovery (root mode). These apps can scan the raw internal storage for deleted files, even after a factory reset, because they bypass the normal file system restrictions.
  9. Run the recovery scan. Open the app, grant root permissions when prompted, and select the storage area to scan (internal storage or SD card). Choose the file types you want to recover (photos, videos, messages, etc.) and start the scan. This can take anywhere from a few minutes to an hour depending on storage size.
  10. Preview and recover the files. After the scan, the app will list recoverable files. Preview them to confirm they’re intact, then select the ones you want and save them to an external location—preferably a microSD card or USB OTG drive, not the phone’s internal storage, to avoid overwriting.
  11. If app data (like WhatsApp chats) is lost, restore from a cloud backup. If you had Google Drive or a manufacturer backup enabled, reinstall the app and follow the restore prompt. For WhatsApp, the backup is stored in Google Drive; for other apps, check if they have their own backup feature.
  12. If you have a Nandroid backup (TWRP backup) from before the data loss, restore it. Boot into TWRP, go to Restore, select the backup file, and swipe to restore. This will bring back the entire system and data as it was at the time of the backup—but it will overwrite any new data, so use it only if you’re okay with that.
  13. After recovery, re-root carefully. If you had to restore a backup or reflash the ROM, you may need to reinstall Magisk. Flash the Magisk zip via TWRP or patch the boot image with Magisk Manager. This won’t affect your recovered data.

Common Mistakes

  • Continuing to use the phone before recovery. Every new app install, photo, or even a system update can overwrite deleted data. The golden rule: stop using the phone as soon as you realize data is missing.
  • Recovering files back to the same storage. Saving recovered files to the internal storage where the deleted data was can overwrite other lost files. Always save to an external SD card or computer.
  • Ignoring USB debugging. Many recovery tools require USB debugging. If you skip enabling it, ADB commands won’t work and you’ll be stuck.
  • Using a non-root recovery app. Non-root apps can only scan for media files and often miss app data or messages. Root access is essential for deep scanning.
  • Restoring a Nandroid backup without backing up current data. A Nandroid restore wipes everything after the backup point. If you have any new data you want to keep, back it up first.

Tips

  • Enable automatic backups before rooting. Google’s backup service (Settings > System > Backup) can save app data, call history, and settings to the cloud. If you have this enabled, you can restore most data after a reset.
  • Make a Nandroid backup immediately after rooting. Before you start modifying the system, boot into TWRP and create a full backup. This is your safety net—if anything goes wrong, you can restore everything.
  • Use a quality microSD card. If you’re saving recovered files to an SD card, use a reputable brand and format it as portable storage to avoid compatibility issues.
  • Keep the phone charged. A dead battery mid-recovery can cause more problems. Keep it plugged in during scans.
  • Know your phone’s recovery key combo. Write it down before you need it. For Samsung, it’s usually Power + Volume Up + Home; for Pixel, Power + Volume Down.

Troubleshooting

  • ADB says “device not found”. Make sure USB debugging is enabled and the phone is unlocked. Try a different USB port or cable, and reinstall the ADB drivers. If the phone is in recovery, ADB may not work unless you’re in TWRP with MTP enabled.
  • The recovery app doesn’t see root access. Open Magisk Manager and check if the app appears in the “Superuser” section. If not, you may need to reflash Magisk. Also, some apps require you to grant root permission the first time you open them.
  • The scan finds no deleted files. This can happen if the data was overwritten already, or if the app’s scan depth is limited. Try a different app or use the ADB pull method to manually browse the filesystem for remnants.
  • The phone is stuck in a boot loop after rooting. Boot into recovery and wipe cache/dalvik cache first. If that doesn’t work, restore your Nandroid backup or reflash the original ROM. Your data should remain intact if you didn’t wipe data.
  • Recovered files are corrupted. Some files may be partially overwritten. Try a deeper scan or use a file repair tool specific to the file type (e.g., for photos, try a JPEG repair app).
  • USB debugging is not available because the phone won’t boot. In TWRP, you can enable ADB by going to Advanced > ADB Sideload, but this only works for flashing. For file recovery, you’ll need to mount storage in TWRP and use MTP to copy files out.

Frequently Asked Questions

Q: Can I recover data after a factory reset on a rooted phone?
A: Yes, but only if the data hasn’t been overwritten. A factory reset marks the storage as empty, but the actual data remains until new data is written. Root access allows deep scanning that can find these remnants.

Q: Does rooting itself cause data loss?
A: Rooting usually doesn’t erase data, but the process often involves unlocking the bootloader, which performs a factory reset. Always back up before unlocking the bootloader.

Q: What’s the best recovery app for rooted phones?
A: DiskDigger is popular for photos and videos, while Dr.Fone offers a broader range including messages. Both require root for deep scanning. No single app is perfect—try one, and if it fails, try another.

Q: Can I recover WhatsApp messages after rooting?
A: Yes, if you have a Google Drive backup, you can restore them by reinstalling WhatsApp and logging in. If not, you can try recovering the SQLite database file from the phone’s internal storage using a root file explorer, but it may be encrypted.

Q: Is it safe to use a Nandroid backup to recover data?
A: Yes, it’s the most reliable method. It restores the entire system and data exactly as it was at backup time. However, it will overwrite any changes made after that point, so back up current data first.

Q: How long does a deep scan take?
A: It depends on the storage size and the app. A 64GB phone can take 30–60 minutes. Larger storage or a slow SD card may take longer. Patience is key—don’t interrupt the scan.

Related

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →