Take the 2-minute tour ×
Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

*Question: I need assistance mounting an Android phone's internal data using the Android ADB Shell while the unit is connected via USB and in recovery mode. How do I form a proper mount command? See below for more detailed information.

*FYI: I have experience developing with the Android SDK using Java/XML. I have found little documentation for the Android ADB Shell for my purpose.

I have a Samsung GT-i9000 Android phone with a smashed screen. Screen is black, and unresponsive to touch. The phone does not have USB debugging enabled or USB auto mount enabled. I cannot simply plug the phone via USB to access the desired files (photos, and other internal data). I unfortunately cannot confirm the OS version. The phone has no SD Card, all the desired data is on the internal board. The phone is not rooted.

*What I've tried: Doing some research I have booted the phone into recovery mode using the three button method (VolUP + Home + Power) and managed to access the device using the "adb devices" command on my Win 7 machine. It displays as "recovery". This is the only way I have been able to make the computer recognize the device via USB. I've tried Kies, and androidscreencast with no success.

I have been able to use the "pull" command to access all the Android system files from the phone. I presume this is because recovery mode only mounts the required system files for updates/repairs and doesn't bother with the internal data. Using the mount command I can see what I consider to be the paths to the files I am looking for:

$ mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
nodev /tmp tmpfs rw,relatime 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=
utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,
iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=
utf8 0 0

All my efforts to mount fail, usually with a usage suggestion:

$ mount rootfs / /mnt/ rw 0 0
mount rootfs / /mnt/ rw 0 0
Usage: mount [-r] [-w] [-o options] [-t type] device directory
share|improve this question

migrated from stackoverflow.com Feb 14 '13 at 13:20

This question came from our site for professional and enthusiast programmers.

Is there a possibility I could turn on the USB setting through XML using the system files I have aquired? –  user1710096 Feb 11 '13 at 23:08

3 Answers 3

ls -l /dev/block/platform/dw_mmc/by-name/ 

to find the path to user data partition. Then

mount -t ext4 /dev/block/mmcblk0p10 /data

Check the correct file system type as well as mmcblkXpXX from first command.

If successful, /data should be mounted correctly

share|improve this answer
All of my mount commands result in mount: Operation not permitted. I believe I've found what you are referring to, although they (mmcblk0p2, mmcblk0p1) exist in the block directory. The platform directory does not appear to exist. –  silencecm Apr 27 '14 at 20:29

Samsung Galaxy S2 partitions with usefull data are /data and /sdcard (internal memory) or /emmc depending on the recovery.

To mount a partition, you issue the following command: mount <partition> <mount_point> or mount <mount_point> if the mount_point is already defined. For /data or /sdcard, you can try with mount /data and mount /sdcard.

If the mount_point is not already defined, you would have to use the partition: mount /dev/block/mmcblk0p10 /data. The -o parameter defines the options when calling mount, but since you only want to get all the data (read), the default options would sufice.

share|improve this answer
Thank you for the migration to the proper forum. The only proper mount command I could run was mount -t jpg /dev/block/mmcblk0p1 /sdcard -operation not permitted. I used mmcblk0p1 because your mentioned location does not exist. –  silencecm Feb 24 '13 at 21:18
Why are you using -t jpg along the mount command? –  Peter Feb 25 '13 at 9:27

Try this:

$ adb shell
$ su
# mount -o rw,remount /system
share|improve this answer
su: not found. The mount command persists to fail even using the # method. –  user1710096 Feb 11 '13 at 22:46
If the phone is not rooted, it won't be able to run su (or as root) –  Peter Feb 14 '13 at 14:17

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.