Database Develop

How to check if Compcache is enabled?

I am running Cyanogen 4.0.4 and would like to know if compcache is enabled. Can someone confirm if my settings are alright?
I have the following details:
Code:
# free
total used free shared buffers
Mem: 97880 95340 2540 0 504
Swap: 24464 17408 7056
Total: 122344 112748 9596
Code:
# df
/dev: 48940K total, 0K used, 48940K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/system: 92160K total, 73844K used, 18316K available (block size 4096)
/system/modules: 640K total, 640K used, 0K available (block size 131072)
/system/xbin: 3328K total, 3328K used, 0K available (block size 131072)
/data: 91904K total, 17680K used, 74224K available (block size 4096)
/cache: 30720K total, 1552K used, 29168K available (block size 4096)
/system/sd: 409986K total, 58588K used, 351398K available (block size 1024)
/data/dalvik-cache: 409986K total, 58588K used, 351398K available (block size 1024)
/sdcard: 15121920K total, 147688K used, 14974232K available (block size 8192)
Code:
# mount
rootfs on / type rootfs (ro)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
none on /dev/cpuctl type cgroup (rw,cpu)
/dev/block/mtdblock3 on /system type yaffs2 (ro)
/dev/block/loop0 on /system/modules type squashfs (ro)
/dev/block/loop1 on /system/xbin type squashfs (ro)
/dev/block/mtdblock5 on /data type yaffs2 (rw,nodev)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nosuid,nodev)
/dev/block/mmcblk0p2 on /system/sd type ext3 (rw,noatime,nodiratime,errors=continue,data=ordered)
/dev/block/mmcblk0p2 on /data/dalvik-cache type ext3 (rw,noatime,nodiratime,errors=continue,data=ordered)
/dev/block//vold/179:1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)

if the only thing you have is compache and no linux-swap then compache is working because of the output from the free command

else you should be able to run the following with superuser access through terminal:
sh /system/bin/swap -s
It will show you the pre and post compression data size, as well as the compression rate under compcache.

Or simply use
Code:
# cat /proc/ramzswap
This file only exists when compcache is currently active. You will see its current settings and status:
Code:
DiskSize: 87040 kB
NumReads: 9509
NumWrites: 12188
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
NotifyFree: 1300
ZeroPages: 410
GoodCompress: 78 %
NoCompress: 3 %
PagesStored: 10471
PagesUsed: 3598
OrigDataSize: 41884 kB
ComprDataSize: 13755 kB
MemUsedTotal: 14392 kB

[q] sd interal/external

when i go to the shell of my devices, i put mount; and show me this:
rootfs / rootfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
proc /proc proc rw,relatime 0 0
sys /sys sysfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,relatime 0 0
/dev/block/stl6 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/r
wx,iocharset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,noatime,vfat,llw,check=no,gid/uid/rw
x,iocharset=utf8 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 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/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe
c,noatime,nodiratime,uid=1000,gid=1015,fmask=0002, dmask=0002,allow_utime=0020,co
depage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:9 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noati
me,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0 002,allow_utime=0020,codepage=
cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
what is mi internal and external memory?
thank you for you answers!!!

damn thats confusing lol
what exactly are you looking for ?? What do you want to know about your internal / external memory
im a little confused

Second column is usually the mountpoint, so, your external SD card is most likely:
Code:
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe...
so, it's mounted at /mnt/sdcard/external_sd, and the device file is /dev/block/vold/179:9
Interestingly it's also mounted as /mnt/secure/asec
Not sure about the internal one... not finding anything that sounds right :O

i have the two memorys bricked, internal and external, and when i run the command try to find /dev/block/mmcblk0 to execute the parted /dev/block/mmcblk0 , no exist...
i find the external sd in /dev/block/vold/179:9, but i could find the internal memory! to fixit

blubxd said:
Second column is usually the mountpoint, so, your external SD card is most likely:
Code:
/dev/block/vold/179:9 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexe...
so, it's mounted at /mnt/sdcard/external_sd, and the device file is /dev/block/vold/179:9
Interestingly it's also mounted as /mnt/secure/asec
Not sure about the internal one... not finding anything that sounds right :O
Click to expand...
Click to collapse
okey the external is /dev/block/vold/179:9
but the internal?!

Can you help mw please??? I send this mesg from my i9000 but i cant use the sd internal and external. Any solution to this?

Which blocks are present in our SGA`s FW?

Does anyone have information about which blocks are present in our SGA?
For example: bml5 - it's core(?), stl12 - this system, stl13 - data and so on.
I would like to know them all.

I could be wrong, from size analysis of "cat /proc/partitions" and "cat /proc/mounts" info:
bml1: mibib (APBOOT)
bml2: qcsbl (APBOOT)
bml3: oemsbl (APBOOT)
bml4: amss (MODEM) - confirmed
bml5: efs - confirmed very dangerous, don't touch it
bml6:
bml7: arm11boot (APBOOT)
bml8: boot.img (CODE) - confirmed
bml9: recovery.img (CODE) - confirmed
bml10: param partition - info from init.rc
bml11: fota partition - info from init.rc
stl12: /system (CODE) - confirmed
stl13: /data (CODE) - confirmed
stl14: /cache (CSC) - confirmed

Does anyone have information about which blocks are present in gt-s5830i?

problem partitions
I have a problem with these corrupt partitions I have them and I can not restore a backup

ketut.kumajaya said:
I could be wrong, from size analysis of "cat /proc/partitions" and "cat /proc/mounts" info:
bml1: mibib (APBOOT)
bml2: qcsbl (APBOOT)
bml3: oemsbl (APBOOT)
bml4: amss (MODEM) - confirmed
bml5: efs - confirmed very dangerous, don't touch it
bml6:
bml7: arm11boot (APBOOT)
bml8: boot.img (CODE) - confirmed
bml9: recovery.img (CODE) - confirmed
bml10: param partition - info from init.rc
bml11: fota partition - info from init.rc
stl12: /system (CODE) - confirmed
stl13: /data (CODE) - confirmed
stl14: /cache (CSC) - confirmed
Click to expand...
Click to collapse
how to get information like you? I used the two commands cat /proc/partitions" and "cat /proc/mounts
results
Code:
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
179 0 1954816 mmcblk0
179 1 1954751 mmcblk0p1
137 0 513024 bml0/c
137 1 1536 bml1
137 2 512 bml2
137 3 768 bml3
137 4 25600 bml4
137 5 9216 bml5
137 6 5120 bml6
137 7 2048 bml7
137 8 8192 bml8
137 9 8192 bml9
137 10 768 bml10
137 11 6144 bml11
137 12 222464 bml12
137 13 186624 bml13
137 14 29696 bml14
137 15 6144 bml15
138 12 214784 stl12
138 13 179968 stl13
138 14 25856 stl14
138 15 2304 stl15
254 0 2110 dm-0
#
Code:
# cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw,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
/dev/stl14 /cache rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/stl13 /data rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,ioch
arset=utf8 0 0
/dev/stl12 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8
0 0
/dev/stl15 /secure rfs rw,nosuid,nodev,relatime,vfat,llw,check=no,gid/uid/rwx,io
charset=utf8 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=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/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioch
arset=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/dm-0 /mnt/asec/com.speedsoftware.rootexplorer-1 vfat ro,dirsync,nosui
d,nodev,noexec,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=
iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
#
please help me to get the information you thankssssss:good:

please help me .................................................

Try running this:
ls -al /dev/block/platform/msm_sdcc.1/by-name
That works on my GS3, on AT&T....
~Ibrahim~

Trying to help devs

I'm new here and have no rights to post in dev section.
I have tried many possible tools and tips for getting root on o4x... No success yet..
But I found out that SupeOneClick tool could write on some sections on /data.
The main problem remains that we couldn't get WRITE access to /system section.
I'm not expert on Linux but I let run some scripts on /system/bin and /root... Till now unfortunately no success.
I found interesting scripts for FOTA like lgdms.fota_update.rc.
As I see our system path is /dev/block/Platform/sdhci-tegra.3/by-name/APP /system
can someone of devs confirm that?
That would mean all other tools trying to gain access with "mount -o remount,rw -t ext4 /dev/block/mmcblk0p33 /system"
will not help us anyway.. Or I'm wrong?
cat /proc/mounts cmd brings me no other /system path...
Here what I get on "cat /proc/mounts":
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ cat /proc/mounts
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
debugfs /sys/kernel/debug debugfs 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/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime,resuid=1000,errors=continue,user_xattr,acl,barrier=1,nodelalloc,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAL /cal ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/MLT /mpt ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/DRM /persist-lg ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:17 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $
P.S. Excuse for my bad English.

Androgenic said:
I'm new here and have no rights to post in dev section.
I have tried many possible tools and tips for getting root on o4x... No success yet..
But I found out that SupeOneClick tool could write on some sections on /data.
The main problem remains that we couldn't get WRITE access to /system section.
I'm not expert on Linux but I let run some scripts on /system/bin and /root... Till now unfortunately no success.
I found interesting scripts for FOTA like lgdms.fota_update.rc.
As I see our system path is /dev/block/Platform/sdhci-tegra.3/by-name/APP /system
can someone of devs confirm that?
That would mean all other tools trying to gain access with "mount -o remount,rw -t ext4 /dev/block/mmcblk0p33 /system"
will not help us anyway.. Or I'm wrong?
cat /proc/mounts cmd brings me no other /system path...
Here what I get on "cat /proc/mounts":
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ cat /proc/mounts
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
debugfs /sys/kernel/debug debugfs 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/platform/sdhci-tegra.3/by-name/APP /system ext4 ro,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw,nosuid,nodev,noatime,resuid=1000,errors=continue,user_xattr,acl,barrier=1,nodelalloc,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/CAL /cal ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/MLT /mpt ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/platform/sdhci-tegra.3/by-name/DRM /persist-lg ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/vold/179:17 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
[email protected]:/ $
P.S. Excuse for my bad English.
Click to expand...
Click to collapse
Thanks for posting
I also have two files that might be worth having a look at.
http://db.tt/dPOQmB5H
Sent from my LG-P880 using xda premium

WOW!
Thanks... Thats interesting to look at...
Can you tell me how you dump sys files? I would take a look on some other too..
ianford10 said:
Thanks for posting
I also have two files that might be worth having a look at.
Sent from my LG-P880 using xda premium
Click to expand...
Click to collapse

So I found a complete dump of /system... Thats fine.
Maybe there would be something that would help to gain write access to /system.

[HoWTO] [FINDING MOUNT POINTS] [SAMSUNG] [NAUTILUS]

Hello buddies..
From the concept SHARING IS CARING, I am going to share with you how to get the mount points of a samsung device.
So let's start!!
Needed tools:
1)Any Linux distro that supports Nautilus scripts
2)Willing of learning and some patience and cold nerves!
First off Download This : CLICK ME!
Set-Up:
Now Open Your Home Folder.
1) Copy The Downloaded File then Press Ctrl+H .
2) Now open .gnome2 . Now open nautilus-scripts.
3) Paste the downloaded File There.
4) Open Terminal Using Ctrl+Alt+T
5) Paste This Into Terminal And Hit Enter.
Code:
chmod a+x ~/.gnome2/nautilus-scripts/Mount-Points
Now To Use This Script to find the mount points.
1) Ensure You Have ADB Working
2) Connect Your Phone with USB Debugging On
3) Now Open HOME Folder
4) Right-Click And Scroll To Scripts.
5) Now Select "Mount-Points"
6) Check in You Home Dir To See mounts.txt
Thats It!! Have Fun Making ROMS!!

Wtf
Isnt it easier to just tell em to adb shell cat /proc/mounts and adb shell cat /proc/partitions :silly:
This way some will learn a bit since this is xda university section and not the i want likes for every post section ^^

Hi mate.
I can get some Mount points later if you still need them, what Linux distro is recommended? And how easy is to to use a n7100 ROM after the mount points have been found??
Sent from my GT-N7105 using Tapatalk 2

Robbie Hood said:
Wtf
Isnt it easier to just tell em to adb shell cat /proc/mounts and adb shell cat /proc/partitions :silly:
This way some will learn a bit since this is xda university section and not the i want likes for every post section ^^
Click to expand...
Click to collapse
Hmm...but those commands don't show me the logical location (aka mount points):
Code:
C:\Users\hehehehehe\AppData\Local\Android\android-sdk\platform-tools>adb shell cat /proc/mounts
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/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/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.urbandroid.sleep.full.key-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.quoord.tapatalkpro.activity-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.boatbrowser.license.key-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.vito.lux-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/com.distractionware.superhexagon-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/com.asksven.betterbatterystats-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/gov.whitehouse-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/com.tyenee.android.googlecontactformatter-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/org.mots.haxsync-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/vold/179:97 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
C:\Users\hehehehehe\AppData\Local\Android\android-sdk\platform-tools>adb shell cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
7 1 9387 loop1
7 2 2111 loop2
7 3 3150 loop3
7 4 66591 loop4
7 6 5229 loop6
7 7 3150 loop7
179 0 15388672 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 13952 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 1536000 mmcblk0p14
179 15 12832768 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 860160 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 8 mmcblk0p22
179 23 5120 mmcblk0p23
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15558144 mmcblk1
179 97 15557120 mmcblk1p1
254 0 2110 dm-0
254 1 9387 dm-1
254 2 2110 dm-2
254 3 3150 dm-3
254 4 66591 dm-4
254 6 5229 dm-6
254 7 3150 dm-7
7 8 2111 loop8
254 8 2110 dm-8
7 9 3150 loop9
254 9 3150 dm-9
I know mmcblk0p18 is recovery from another guide I read, but how did they figure that out? Are these Nautilus scripts the easiest way, then?
EDIT: this command works! ls -al /dev/block/platform/msm_sdcc.1/by-name

ikjadoon said:
Hmm...but those commands don't show me the logical location (aka mount points):
Code:
C:\Users\hehehehehe\AppData\Local\Android\android-sdk\platform-tools>adb shell cat /proc/mounts
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/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/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/block/dm-0 /mnt/asec/com.urbandroid.sleep.full.key-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-1 /mnt/asec/com.quoord.tapatalkpro.activity-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.boatbrowser.license.key-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.vito.lux-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/com.distractionware.superhexagon-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/com.asksven.betterbatterystats-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/gov.whitehouse-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/com.tyenee.android.googlecontactformatter-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/org.mots.haxsync-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,barrier=1 0 0
/dev/block/vold/179:97 /storage/extSdCard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
C:\Users\hehehehehe\AppData\Local\Android\android-sdk\platform-tools>adb shell cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
7 1 9387 loop1
7 2 2111 loop2
7 3 3150 loop3
7 4 66591 loop4
7 6 5229 loop6
7 7 3150 loop7
179 0 15388672 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 10240 mmcblk0p7
179 8 512 mmcblk0p8
179 9 512 mmcblk0p9
179 10 10240 mmcblk0p10
179 11 13952 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 3072 mmcblk0p13
179 14 1536000 mmcblk0p14
179 15 12832768 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 860160 mmcblk0p17
179 18 10240 mmcblk0p18
179 19 10240 mmcblk0p19
179 20 6144 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 8 mmcblk0p22
179 23 5120 mmcblk0p23
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15558144 mmcblk1
179 97 15557120 mmcblk1p1
254 0 2110 dm-0
254 1 9387 dm-1
254 2 2110 dm-2
254 3 3150 dm-3
254 4 66591 dm-4
254 6 5229 dm-6
254 7 3150 dm-7
7 8 2111 loop8
254 8 2110 dm-8
7 9 3150 loop9
254 9 3150 dm-9
I know mmcblk0p18 is recovery from another guide I read, but how did they figure that out? Are these Nautilus scripts the easiest way, then?
EDIT: this command works! ls -al /dev/block/platform/msm_sdcc.1/by-name
Click to expand...
Click to collapse
Actually, the first command - cat /proc/mounts gives you the mount points. The first column is the device, the second column is the mount point, the third column is the file system type, the fourth column is how it is mounted, i.e. ro (read-only) or rw (read-write) and so on. The second command gives the partition table. You may be able to look at other files, like fstab or recovery.fstab to see where other things are.

sidneyk said:
Actually, the first command - cat /proc/mounts gives you the mount points. The first column is the device, the second column is the mount point, the third column is the file system type, the fourth column is how it is mounted, i.e. ro (read-only) or rw (read-write) and so on. The second command gives the partition table. You may be able to look at other files, like fstab or recovery.fstab to see where other things are.
Click to expand...
Click to collapse
Do a adb pull yourphone/proc/mounts
Sent from my GT-P7300 using xda premium

mithun46 said:
Do a adb pull yourphone/proc/mounts
Sent from my GT-P7300 using xda premium
Click to expand...
Click to collapse
OK, here is from my SGH-T769 under Android:
Code:
[email protected]:~$ adb shell cat /proc/mounts
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/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/mmcblk0p24 /system ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p26 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p13 /system/etc/firmware/misc vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p27 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/vold/179:33 /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:28 /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:28 /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
/dev/block/dm-1 /mnt/asec/com.gsn.android.casino-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.phantomefx.standalone.mermaidspearl-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.phantomefx.standalone.robinhood-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/com.chartcross.gpstest-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/com.androidwasabi.livewallpaper.raindrop-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/air.com.slotgalaxy-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.farproc.wifi.analyzer-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/air.com.playtika.slotomania-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/com.iudesk.android.photo.editor-2 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-10 /mnt/asec/com.eamobile.life_na_wf-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-11 /mnt/asec/com.google.android.apps.plus-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-12 /mnt/asec/org.zwanoo.android.speedtest-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-13 /mnt/asec/com.phantomefx.standalone.theheist-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-14 /mnt/asec/com.joeykrim.rootcheckp-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-15 /mnt/asec/com.androidwasabi.livewallpaper.dandelion-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-16 /mnt/asec/com.phantomefx.indianspirit_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-17 /mnt/asec/com.zumobi.msnbc-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-18 /mnt/asec/com.slots-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-19 /mnt/asec/com.anddoes.launcher.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-20 /mnt/asec/com.bvalosek.cpuspy.realgpp-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-21 /mnt/asec/com.pokiemagic.KalahariSunFree-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-22 /mnt/asec/com.mw.slotsroyale-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-23 /mnt/asec/com.phantomefx.leprecoin_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-24 /mnt/asec/air.com.Slot-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-25 /mnt/asec/com.audioaddict.sky-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-26 /mnt/asec/com.fishsticksgames.SlotsJourney-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-27 /mnt/asec/com.quoord.tapatalkxda.activity-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-28 /mnt/asec/com.mxtech.videoplayer.ad-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-29 /mnt/asec/mobi.mgeek.TunnyBrowser-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-30 /mnt/asec/com.phantomefx.aztecsun_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-31 /mnt/asec/com.natenai.virtualhorseracing3d-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-32 /mnt/asec/com.eamobile.monopoly_full_azn-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-33 /mnt/asec/com.phantomefx.balloonblitz-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-34 /mnt/asec/com.jrummy.liberty.toolboxpro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-35 /mnt/asec/com.ziplinegames.slotstycoon-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-36 /mnt/asec/com.google.zxing.client.android-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-37 /mnt/asec/com.phantomefx.bovinebling_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-38 /mnt/asec/com.koushikdutta.rommanager-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-39 /mnt/asec/com.phantomefx.tunzamunny-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-40 /mnt/asec/com.hotrod.reference.spiritofseventysix-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-41 /mnt/asec/com.phantomefx.standalone.spiritwolf-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
And here is the contents of /etc/recovery.fstab from the CWM recovery ramdisk:
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p8
/recovery emmc /dev/block/mmcblk0p22
/efs ext4 /dev/block/mmcblk0p21
/data ext4 /dev/block/mmcblk0p25
/system ext4 /dev/block/mmcblk0p24
/cache ext4 /dev/block/mmcblk0p26
/emmc vfat /dev/block/mmcblk0p28
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2
And here is the contents of /fstab.qcom back in the normal Android OS:
Code:
[email protected]:/ # cat /fstab.qcom
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p24 /system ext4 ro,barrier=1 wait
/dev/block/mmcblk0p26 /cache ext4 nosuid,nodev,barrier=1 wait,check
/dev/block/mmcblk0p21 /efs ext4 nosuid,nodev,barrier=1 wait.check
/dev/block/mmcblk0p25 /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,check
This, of course, applies to my phone, Samsung Galaxy S Blaze 4G SGH-T769 with custom CWM recovery and custom PACman JB 4.1.2 ROM. You should be able to see the same things on your phone, especially if rooted, and can see where the friendly names of the familiar mount points are at and how it was figured out. There are also other mounts being executed in some of the other startup files. One thing of note, is that the recovery system and Android system may, and probably do, use different mount points and even different mount names for internal storage and external sdcard. For example, in recovery, the internal storage is /emmc and /sdcard and /sd-ext are the external sdcard. Under Android, /sdcard can refer to at least a part of internal storage. Under Android 4.1+ the external card is /storage/sdcard1 and the internal is also /storage/sdcard0. Some of the devices are given multiple mount points (or at least symlinks) with different names pointing to the same device. Confusing as hell, but that's the way it is.

sidneyk said:
OK, here is from my SGH-T769 under Android:
Code:
[email protected]:~$ adb shell cat /proc/mounts
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/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/mmcblk0p24 /system ext4 ro,relatime,user_xattr,acl,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p26 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p21 /efs ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p25 /data ext4 rw,nosuid,nodev,noatime,user_xattr,acl,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p13 /system/etc/firmware/misc vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0133,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p27 /tombstones ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/dm-0 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/vold/179:33 /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:28 /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:28 /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
/dev/block/dm-1 /mnt/asec/com.gsn.android.casino-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-2 /mnt/asec/com.phantomefx.standalone.mermaidspearl-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.phantomefx.standalone.robinhood-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/com.chartcross.gpstest-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/com.androidwasabi.livewallpaper.raindrop-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/air.com.slotgalaxy-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.farproc.wifi.analyzer-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-8 /mnt/asec/air.com.playtika.slotomania-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-9 /mnt/asec/com.iudesk.android.photo.editor-2 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-10 /mnt/asec/com.eamobile.life_na_wf-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-11 /mnt/asec/com.google.android.apps.plus-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-12 /mnt/asec/org.zwanoo.android.speedtest-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-13 /mnt/asec/com.phantomefx.standalone.theheist-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-14 /mnt/asec/com.joeykrim.rootcheckp-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-15 /mnt/asec/com.androidwasabi.livewallpaper.dandelion-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-16 /mnt/asec/com.phantomefx.indianspirit_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-17 /mnt/asec/com.zumobi.msnbc-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-18 /mnt/asec/com.slots-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-19 /mnt/asec/com.anddoes.launcher.pro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-20 /mnt/asec/com.bvalosek.cpuspy.realgpp-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-21 /mnt/asec/com.pokiemagic.KalahariSunFree-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-22 /mnt/asec/com.mw.slotsroyale-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-23 /mnt/asec/com.phantomefx.leprecoin_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-24 /mnt/asec/air.com.Slot-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-25 /mnt/asec/com.audioaddict.sky-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-26 /mnt/asec/com.fishsticksgames.SlotsJourney-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-27 /mnt/asec/com.quoord.tapatalkxda.activity-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-28 /mnt/asec/com.mxtech.videoplayer.ad-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-29 /mnt/asec/mobi.mgeek.TunnyBrowser-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-30 /mnt/asec/com.phantomefx.aztecsun_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-31 /mnt/asec/com.natenai.virtualhorseracing3d-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-32 /mnt/asec/com.eamobile.monopoly_full_azn-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-33 /mnt/asec/com.phantomefx.balloonblitz-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-34 /mnt/asec/com.jrummy.liberty.toolboxpro-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-35 /mnt/asec/com.ziplinegames.slotstycoon-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-36 /mnt/asec/com.google.zxing.client.android-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-37 /mnt/asec/com.phantomefx.bovinebling_x-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-38 /mnt/asec/com.koushikdutta.rommanager-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-39 /mnt/asec/com.phantomefx.tunzamunny-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-40 /mnt/asec/com.hotrod.reference.spiritofseventysix-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
/dev/block/dm-41 /mnt/asec/com.phantomefx.standalone.spiritwolf-1 ext4 ro,dirsync,nosuid,nodev,noatime,user_xattr,acl,barrier=1 0 0
And here is the contents of /etc/recovery.fstab from the CWM recovery ramdisk:
Code:
# mount point fstype device [device2]
/boot emmc /dev/block/mmcblk0p8
/recovery emmc /dev/block/mmcblk0p22
/efs ext4 /dev/block/mmcblk0p21
/data ext4 /dev/block/mmcblk0p25
/system ext4 /dev/block/mmcblk0p24
/cache ext4 /dev/block/mmcblk0p26
/emmc vfat /dev/block/mmcblk0p28
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
/sd-ext ext4 /dev/block/mmcblk1p2
And here is the contents of /fstab.qcom back in the normal Android OS:
Code:
[email protected]:/ # cat /fstab.qcom
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p24 /system ext4 ro,barrier=1 wait
/dev/block/mmcblk0p26 /cache ext4 nosuid,nodev,barrier=1 wait,check
/dev/block/mmcblk0p21 /efs ext4 nosuid,nodev,barrier=1 wait.check
/dev/block/mmcblk0p25 /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc wait,check
This, of course, applies to my phone, Samsung Galaxy S Blaze 4G SGH-T769 with custom CWM recovery and custom PACman JB 4.1.2 ROM. You should be able to see the same things on your phone, especially if rooted, and can see where the friendly names of the familiar mount points are at and how it was figured out. There are also other mounts being executed in some of the other startup files. One thing of note, is that the recovery system and Android system may, and probably do, use different mount points and even different mount names for internal storage and external sdcard. For example, in recovery, the internal storage is /emmc and /sdcard and /sd-ext are the external sdcard. Under Android, /sdcard can refer to at least a part of internal storage. Under Android 4.1+ the external card is /storage/sdcard1 and the internal is also /storage/sdcard0. Some of the devices are given multiple mount points (or at least symlinks) with different names pointing to the same device. Confusing as hell, but that's the way it is.
Click to expand...
Click to collapse
U r right
Sent from my GT-P7300 using xda premium

Since this is xda university to share info with new xda members, here is a summary on how to get mounting points without rooting or extracting recovery.img.
The different procedures only needs to have adb shell or terminal emulator.. I will explain using adb shell through pc.
After establishing adb connection to your device, you can choose any of the following procedures to get your mounting points:
#1
Code:
adb shell
cat /proc/mounts
This will give you info about device, the mount point, the file system type, and how it is mounted. (see post #4)
Limitation: This method, however, will not give you all mounting points.!!!
#2
Code:
adb shell
cat /proc/partitions
This is more neat, it will give you info about ALL dev blocks and their names (not the familiar name!), and block size
Limitation: Needs from you to figure out which block belong to which partition name.!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#3
Code:
adb shell
ls -al /dev/block/platform/[B][COLOR="Blue"]dw_mmc[/COLOR][/B]/by-name
This one is the command that I like on non-rooted device..! It will give you info about the dev block names WITH their familiar names (i.e, boot, recovery, system... etc) :laugh:
This command is not universal between devices, and you will need to gather its pieces (/dev/block/platform/dw_mmc/by-name).
How?
- In your device, use any explorer that can get you to the device root (personally I use ES Explorer, by pressing on "/" on navigation bar).
- Go to "/dev/block/platform/" folder
- Here you will see some files and folders, we need to open folders and search for the folder called "by-name" inside one of them; in my situation it was "dw_mmc" folder which has the folder "by-name" inside it.
N.B: If you check post #4, it was "msm_sdcc.1", so it depends totally on which device you have.!
- At the end, my targeted piece info will be (/dev/block/platform/dw_mmc/by-name)
- Now open adb shell and put the command..
If anyone knows any other method for NON-ROOTED devices, please share.
Cheers

Why not use adb shell,then just type mount > /sdcard/mounts.txt and use adb pull to get it?
通过我的 SM-N9200 上的 Tapatalk发言