[Q] user-storage paths vary? (Android, TWRP, CWMR) - Android Q&A, Help & Troubleshooting

Cheers all,
I'm in the process of documenting some android file system stuff, and I noticed that Android, CWM, and TWRP are somewhat inconsistent when it comes to the paths of user-storage.
Comparing their mount stats leads me to believe that
1) the storage destination is a device-block mapped to a path-name, which occurs during boot.
2) the path-name is defined by the author of the firmware?
^^ are these assumptions anywhere near correct?
booted into android
internal & external user-storage are located at /storage/sdcard0 & /storage/sdcard1
Code:
mount
/dev/block/vold/179:9 /mnt/media_rw/sdcard1 fuseblk rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/fuse /storage/sdcard1 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/259:3 /mnt/media_rw/sdcard0 fuseblk rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/block/vold/259:3 /mnt/secure/asec fuseblk rw,dirsync,context=u:object_r:sdcard_external:s0,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[email protected]:/ #
booted into CWMR
internal & external user-storage are located at /storage/sdcard0 & /storage/sdcard1
Code:
mount
/dev/block/vold/259:3 on /storage/sdcard0 type fuseblk (rw,dirsync,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/block/vold/179:9 on /storage/sdcard1 type fuseblk (rw,dirsync,nosuid,nodev,noexec,noatime,user_id=0,group_id=0,allow_other,blksize=4096)
~ #
booted into TWRP
internal & external user-storage are located at /emmc & /sdcard
Code:
mount
/dev/block/mmcblk0p11 on /emmc type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=131072,blksize=4096)
/dev/block/mmcblk0p11 on /and-sec type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=131072,blksize=4096)
/dev/block/mmcblk1p1 on /sdcard type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,max_read=131072,blksize=4096)

Related

[Q] vold.fstab swapping internal with external sd card

After recently acquiring and rooting a RK3066 based DoPo td-1010 tablet, I quickly ran out of room for my apps, as I only have 500mb of internal storage. What I want to do now is swap the mounting point of my external SD card with the mounting point of my internal storage.
Listed under settings>storage in ICS are 3 mounted areas:
Internal - 504 mb
NAND Flash - 5.81Gb (I believe this to be a glorified internal SD card)
SD CARD - 7.39 Gb (my external card)
a quick look through vold.fstab reveals that the mount point for Internal appears no to be listed:
Code:
## Vold 2.0 Generic fstab
## - San Mehat ([email protected])
##
#######################
## Regular device mount
##
## Format: dev_mount <label> <mount_point> <part> <sysfs_path1...>
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## <sysfs_path> - List of sysfs paths to source devices
######################
## Example of a standard sdcard mount for the emulator / Dream
# Mounts the first usable partition of the specified device
#dev_mount sdcard /mnt/sdcard auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
dev_mount flash /mnt/sdcard auto /devices/virtual/mtd/mtd9/mtdblock9
dev_mount sdcard /mnt/external_sd auto /devices/platform/rk29_sdmmc.0/mmc_host/mmc0
dev_mount udisk /mnt/usb_storage auto /devices/platform/usb20_host/usb
## Example of a dual card setup
# dev_mount left_sdcard /sdcard1 auto /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
# dev_mount right_sdcard /sdcard2 auto /devices/platform/goldfish_mmc.1 /devices/platform/msm_sdcc.3/mmc_host/mmc1
## Example of specifying a specific partition for mounts
# dev_mount sdcard /sdcard 2 /devices/platform/goldfish_mmc.0 /devices/platform/msm_sdcc.2/mmc_host/mmc1
Dev_mount flash links to the NAND Flash partition. this is the area apps which support movement to the SD card are moved to. Again, the Internal storage partition appears on to be listed.
After installing busybox on my tablet, and installing a terminal emulator, an output of cat /proc/mounts reveals this:
Code:
[email protected]:/ $ cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock8 /system ext4 ro,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mtdblock6 /data ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mtdblock5 /cache ext4 rw,nosuid,nodev,noatime,nodiratime,barrier=1,data=ordered,noauto_da_alloc 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/vold/31:9 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/31:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:1 /mnt/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-0 /mnt/asec/com.halfbrick.jetpackjoyride-1 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.amazon.kindle-1 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/com.agilesoftresource-2 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.pandora.android-1 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-4 /mnt/asec/com.skype.raider-2 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-5 /mnt/asec/com.aideronrobotics.android.aura-2 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-6 /mnt/asec/org.zwanoo.android.speedtest-1 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-7 /mnt/asec/com.noinnion.android.greader.reader-2 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-8 /mnt/asec/com.eamobile.life_na_wf-1 vfat ro,dirsync,nosuid,nodev,noatime,nodiratime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $
As I am unfamiliar with Android mounting points, I am unsure what I am looking for/which partition is the one Internal is using.
Any help?

link2sd: /data/sdext2 and /mnt/sdcard identically mounted

Dear Forum,
I'm new here (however I've been following for some time) and I really hope you can help me with a problem I ran into today. I am using a Base Varia (which is an Alcatel 918d). I have link2sd installed and two partitions, both FAT32.
As with link2sd, normally one partition is mounted to /data/sdext2 (app files), and the other one is in /mnt/sdcard (everything else). This worked perfectly up to now. Today I realized strange behavior of the phone and after some research, I noticed that the app file partition was mounted in both directories:
Code:
/dev/block/vold/179:2 /data/sdext2 vfat rw,relatime,uid=1000,gid=1000,fmask=0133,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/vold/179:2 /mnt/sdcard vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1000,fmask=0133,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
So basically I've lost my sdcard partition for user files (Gallery, Music, osmand maps, ...). I CAN manually mount /dev/block/vold/179:1, which is the device that should be mounted in /mnt/sdcard. I do not know if it helps, but /data/link2sd-install-recovery.log shows the following (note 2nd line)
Code:
Tue Nov 19 18:56:14 CET 2013 mounting...
mount: Device or resource busy
rootfs / rootfs ro,relatime 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
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mtdblock12 /system yaffs2 ro,relatime 0 0
/dev/block/mtdblock13 /custpack yaffs2 rw,relatime 0 0
/dev/block/mtdblock15 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock14 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
tmpfs /data/local/sqlite_stmt_journals tmpfs rw,relatime,size=4096k 0 0
/dev/block/mtdblock8 /data/nvram/md/s yaffs2 ro,relatime 0 0
/dev/block/vold/179:2 /data/sdext2 vfat rw,relatime,uid=1000,gid=1000,fmask=0133,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
Tue Nov 19 18:56:15 CET 2013 mount finished
If you have any idea on how to help me, that would be greatly appreciated. I really would not like to reinstall everything!
Thanks a lot in advance,
-mauli-
Just a quick update:
it turned out the SD card was broken, the /mnt/sdcard partition not readable anymore. Also partitioning with gparted was not possible.
So I replaced it with a working card and everything's back to normal.
Puh!

[Q] External SDCard mounted as /storage/sdcard0

Hi!
In my current phone the External SDCard is mounted as /storage/sdcard0.
Some info about my system:
vold.fstab
Code:
dev_mount sdcard /storage/sdcard0 [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-msdc.0/mmc_host
dev_mount sdcard2 /storage/sdcard1 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-msdc.1/mmc_host
[email protected]:/ # mount
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,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
tmpfs /mnt/secure tmpfs rw,relatime,mode=700 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/[email protected] /system ext4 ro,relatime,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected] /data ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected] /cache ext4 rw,nosuid,nodev,noatime,discard,noauto_da_alloc,data=ordered 0 0
/[email protected]_f /protect_f ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/[email protected]_s /protect_s ext4 rw,nosuid,nodev,noatime,nodelalloc,noauto_da_alloc,commit=1,data=ordered 0 0
/dev/block/loop0 /mnt/cd-rom iso9660 ro,relatime 0 0
/dev/block/vold/179:7 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
I don't untherstand why is /storage/sdcard0 and not /storage/sdcard1
I don't have any script at /etc/init.d/
Any idea about why my SDCard is at /storage/sdcard0 ?
me too
I'm having the same problem with my Star N9599T which has a MediaTek MT6589T chipset
I'm finding it really annoying - I put the SDcard in for more space but I've had to duplicate lots of stuff across both drives. Plus, it's upset some of my apps.
It looks to me that if [email protected] were to remain as the internal drive there would be no problem. I'm tempted to reformat the card to ext2 to see if that fixes it
dodgy automount?
from the following I'm thinking that there's an automount script somewhere that's weirdly written - you can see that /dev/block/vold/179:8 (internal sdcard) is mounted as external storage (sdcard1)
Code:
# mount | grep sdcard
/dev/block/vold/179:8 /storage/sdcard1 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:97 /storage/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /storage/sdcard0/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
Code:
# grep -v '^#' /system/etc/vold.fstab
dev_mount sdcard /storage/sdcard0 [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-msdc.0/mmc_host
dev_mount sdcard2 /storage/sdcard1 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-msdc.1/mmc_host
dev_mount usbotg /mnt/usbotg auto /devices/platform/mt_usb /devices/platform/musbfsh_hdrc

Swap /data partition with sdcard HTC Legend

Hi, I am trying to swap mount points to increase internal memory on my device - HTC Legend.
I know that there is script for this purpose.
http://forum.xda-developers.com/showthread.php?t=902395 .
As I can guess here we just use /sd-ext partition to swap it with /data. But in my case I have no /sd-ext partition at all, only /sdcard.
Of course I have no device /dev/block/mmcblk0p2.
About installed firmware - Android 2.3.7 ExtremeLegendFuse_2 based on CM7.
Output of mount command.
Code:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro,relatime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev,relatime)
/dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,relatime,size=0k,mode=000)
#
And df -h
Code:
# df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 145.7M 32.0K 145.7M 0% /dev
tmpfs 145.7M 0 145.7M 0% /mnt/asec
tmpfs 145.7M 0 145.7M 0% /mnt/obb
/dev/block/mtdblock3 240.0M 160.7M 79.3M 67% /system
/dev/block/mtdblock5 185.1M 18.9M 166.3M 10% /data
/dev/block/mtdblock4 40.0M 6.6M 33.4M 16% /cache
/dev/block/vold/179:1
967.6M 194.8M 772.8M 20% /mnt/sdcard
/dev/block/vold/179:1
967.6M 194.8M 772.8M 20% /mnt/secure/asec
#
Content of /system/etc/vold.fstab
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/usb_mass_storage/lun0 /devices/platform/msm_sdcc.2/mmc_host/mmc0
I have some basic knowledge, but I need help in this case.
Please help to swap storage to increase internal storage.
Thanks everyone in advance.
The problem has been solved.
My fault was that I have partitioned my sd card incorrectly.
You can do this easily from recovery. Go to Advanced - > Partition SD card Than you can select desired amount of space and choose Swap 0M.
After that you are ready to use this script.
Just reboot your device, it will take some time to boot, because your data is been moved from internal storage to the external.

[Q] LG L65 d280 bricked?

Hello all,
I'm afraid I've just done a STUPID THING (TM) with my phone. In adb shell (root) I wanted to reformat the second partition of the *external* sd card, and I typed mmcblk0p2 instead of mmcblk1p2. I'm not sure I have broken anything, because fdisk does not show any mmcblk0p2 partition (see below), but the mkfs command somehow succeded:
Code:
# mkfs.ext2 /dev/block/mmcblk0p2
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
128 inodes, 1024 blocks
51 blocks (5%) reserved for the super user
First data block=1
Maximum filesystem blocks=262144
1 block groups
8192 blocks per group, 8192 fragments per group
128 inodes per group
and here is fdisk output:
Code:
# fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes
256 heads, 63 sectors/track, 473 cylinders
Units = cylinders of 16128 * 512 = 8257536 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 266306 2147483647+ ee EFI GPT
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 0, 1) logical=(0, 0, 2)
Partition 1 has different physical/logical endings:
phys=(1023, 255, 63) logical=(266305, 4, 4)
and the output of the mount command:
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=469568k,nr_inodes=117392,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=469568k,nr_inodes=117392,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,size=469568k,nr_inodes=117392,mode=755,gid=1000 0 0
/dev/block/dm-0 /mnt/asec/lysesoft.andsmb-1 ext4 ro,dirsync,seclabel,nosuid,nodev,noatime 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,size=469568k,nr_inodes=117392,mode=755,gid=1000 0 0
/dev/block/platform/msm_sdcc.1/by-name/system /system ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,resuid=1000,errors=continue,data=ordered 0 0
/dev/block/vold/179:66 /data/sdext2 ext4 rw,seclabel,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,nodelalloc,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/drm /persist-lg ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/mpt /mpt ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/sns /sns ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/cust /cust ext4 ro,seclabel,nodev,relatime,noauto_da_alloc,data=ordered 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,size=469568k,nr_inodes=117392,mode=050,gid=1028 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:65 /mnt/media_rw/external_SD vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:65 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/external_SD fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy/Android/obb fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:65 /data/media/0/WhatsApp vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Now the phone is still powered on, working ok, and connected with adb shell. I'm not rebooting it until I have some confidence I've not wiped essential system stuff. The phone has the LG stock ROM. Have I wiped any system partition? Will the phone boot again?
Since there is no partition by that name, you have not done any damage to your phone
Plus as it is your external SD card, nothing will happen to the ROM on your phone, as all of that is on the Device Memory!
Cheer up mate, all's well!:thumbup:
Sent from my SM-G530H using XDA Free mobile app
I know I can't blame you, but, just to let you know, the phone is actually bricked. I turned it off after I read your reply, and it never resurrected. No power+volume down tricks. Nothing. Black screen.
Rest in peace.
Oh! I'm so sorry buddy. Your phone may still get back to life. Try a senior on XDA. He may help you.
I guess you don't have access to your recovery as well?
I still don't get it, how can your phone get bricked when you did stuff with the External SD card?
Sent from my SM-G530H using XDA Free mobile app
heinrich.himmler said:
Oh! I'm so sorry buddy. Your phone may still get back to life. Try a senior on XDA. He may help you.
I guess you don't have access to your recovery as well?
Click to expand...
Click to collapse
This story's had a happy ending. Last month I brought my phone back to the lab (the warranty period isn't over yet) and I told them that one day it suddendly died with no reason. I know, Beelzebub has a devil put aside for me...
They phone was so bricked they didn't even dare to check why. They simply replaced the system board and handed me it back fixed after a few days, for free.
heinrich.himmler said:
I still don't get it, how can your phone get bricked when you did stuff with the External SD card?
Click to expand...
Click to collapse
Please note that /dev/block/mmcblk0 is not the external SD. I should have typed /dev/block/mmcblk1 for the external SD, see my first post.

Categories

Resources