Can Some One Dump Boot.img ( Kernel) from device? Asap!
Cheers..!
eaglerazor123 said:
Can Some One Dump Boot.img ( Kernel) from device? Asap!
Cheers..!
Click to expand...
Click to collapse
https://www.dropbox.com/s/vv94z7kazvfkdig/boot.img sent link in pm also
b3ltazar said:
https://www.dropbox.com/s/vv94z7kazvfkdig/boot.img sent link in pm also
Click to expand...
Click to collapse
Firmware no?! And i need mount partitions too!
adb mount
Houston, The EAGLE has landed! :laugh:
eaglerazor123 said:
Can Some One Dump Boot.img ( Kernel) from device? Asap!
Cheers..!
Click to expand...
Click to collapse
Our first interested Dev, people, whatever he wants, give it to him, beer, sex, etc... :victory:
easyguy said:
Our first interested Dev, people, whatever he wants, give it to him, beer, sex, etc... :victory:
Click to expand...
Click to collapse
Mount partitions would be enough for me to keep going!
run this in adb
adb mount
cheers..!
eaglerazor123 said:
Mount partitions would be enough for me to keep going!
run this in adb
adb mount
cheers..!
Click to expand...
Click to collapse
Is this what your looking for:
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 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
tmpfs /mnt/usb 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=ord
ered 0 0
/dev/block/mmcblk0p26 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,acl,barrie
r=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,relatime,user_xattr,acl,barrier
=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p13 /system/etc/firmware/misc vfat ro,relatime,fmask=0133,dmas
k=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,b
arrier=1,data=ordered 0 0
/dev/block/vold/179:28 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,n
odiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp43
7,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
tmpfs /mnt/sdcard/external_sd tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodir
atime,size=0k,mode=755,gid=1000 0 0
tmpfs /mnt/sdcard/usbStorage tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodira
time,size=0k,mode=755,gid=1000 0 0
/dev/block/vold/179:33 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noex
ec,noatime,nodiratime,uid=1000,gid=1023,fmask=0002,dmask=0002,allow_utime=0020,c
odepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noat
ime,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
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000
0 0
And this one too
/proc/mtd
eaglerazor123 said:
And this one too
/proc/mtd
Click to expand...
Click to collapse
That was the entire output.
I did adb shell, mount in windows terminal.
How do I get the one you want?
[email protected]:/ $ export PATH=/data/local/bin:$PATH
[email protected]:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 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
tmpfs /mnt/usb 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,relatime,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
/dev/block/vold/179:28 /mnt/sdcard 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,discard 0 0
tmpfs /mnt/sdcard/external_sd tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000 0 0
tmpfs /mnt/sdcard/usbStorage tmpfs rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,size=0k,mode=755,gid=1000 0 0
/dev/block/vold/179:33 /mnt/sdcard/external_sd 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
/dev/block/vold/179:33 /mnt/secure/asec 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
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.mobilityflow.torrent-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]:/ $
Here ya go.
eaglerazor123 said:
Can Some One Dump Boot.img ( Kernel) from device? Asap!
Cheers..!
Click to expand...
Click to collapse
Here is the boot.img http://forum.xda-developers.com/showthread.php?t=1837907. Fourth in the list.
Hello everyone,
I am using CM10.1 on my Samsung Galaxy S i9000. I have a strange problem since I swithed to CM10 about a month ago. If I boot to revocery I can reach, read and write to all partitions including sdcard and internalsd (and data, system etc.) However, If I boot to normal system, the boot screen SGS/Cyanogen mod image lasts on the screen for too long and then system stats.
When system starts, I end up with external sd mounted but not internal sd. If I connect my phone to a computer at this time, computer only sees external sd card, and says "insert disk" when I click internal sd from Explorer. However, when I removed by sdcard from computer, my phone says "preparing sd card" and than mounts internal sd. Now, external sd is unmounted magically. This time I can use internal sd (read, write everything) but external sd card is not mounted. If I go to System -> Storage to mount external sd card, "Insert sdcard to mount" appears, and it can't be mountable.
I also ran mount command before connecting to PC (when external sd was mounted) and after disconnected from PC (this time internal sd was mounted) These are the outputs:
before connecting to pc
Code:
[email protected]:/ # mount
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
/dev/block/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock2 /datadata yaffs2 rw,relatime 0 0
/dev/lvpool/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/lvpool/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/dm-2 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.chartcross.gpstestplus-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/kr.aboy.tools-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/dk.logisoft.aircontrolfull-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/radiotime.player-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.qo.android.am3-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/vold/179:25 /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
last lines differ
after connecting to pc
Code:
[email protected]:/ # mount
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
/dev/block/mtdblock3 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock5 /radio yaffs2 rw,relatime 0 0
/dev/block/mtdblock2 /datadata yaffs2 rw,relatime 0 0
/dev/lvpool/system /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/lvpool/userdata /data ext4 rw,nosuid,nodev,noatime,errors=panic,barrier=1,nomblk_io_submit,data=ordered 0 0
/dev/block/mtdblock4 /efs yaffs2 rw,relatime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/dm-2 /mnt/asec/com.keramidas.TitaniumBackupPro-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-3 /mnt/asec/com.chartcross.gpstestplus-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-4 /mnt/asec/kr.aboy.tools-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-5 /mnt/asec/dk.logisoft.aircontrolfull-1 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-6 /mnt/asec/radiotime.player-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/dm-7 /mnt/asec/com.qo.android.am3-2 ext4 ro,dirsync,nosuid,nodev,noatime,barrier=1 0 0
/dev/block/vold/179:1 /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:1 /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
How can I fix this? Btw, I can't report this to CM10.1 page because my post count is too low.
If I could'nt write and read to internalsdcard properly on recovery or after disconnecting to pc I'd thought that it was broken on hardware level but this seems like a software issue to me? What do you think?
By using which shell command, I can try to manually mount my internal sdcard, after the phone booted?
If I run these commands manually after turning on my phone, I can mount my internal sd card to /storage/sdcard successfully. However, I can't mount sdcard to multiple locations (such as mnt/sdcard and /sdcard) so programs don't run properly.
Code:
mount -t vfat /dev/block/mmcblk0p1 /storage/sdcard0;
setprop EXTERNAL_STORAGE_STATE mounted;
am broadcast -a android.intent.action.MEDIA_MOUNTED --ez read-only false -d file:///storage/sdcard0;
However if I try to mount vold/179:0 i get the following error:
Code:
[email protected]:/ # mount -t vfat /dev/block/vold/179\:0 /storage/sdcard0;
mount: Device or resource busy
Any thoughts?
What is vold and what is the difference between mounting
/dev/block/vold/179:0 and /dev/block/mmcblk0p1 ?
If both points to internal storage, why can't I mount one, but do mount another?
Well, I found out the real reason after tremendeous testing.I have a 32GB sdcard inserted. If I have lots of music and files on that card, phone doesn't mount internal sd on boot. (don't know the reason) But if I delete the musics and empty the external sd card, then internal sd mounts properly.
Really no iade how they effect each other but this is the case.
gergefil said:
Well, I found out the real reason after tremendeous testing.I have a 32GB sdcard inserted. If I have lots of music and files on that card, phone doesn't mount internal sd on boot. (don't know the reason) But if I delete the musics and empty the external sd card, then internal sd mounts properly.
Really no iade how they effect each other but this is the case.
Click to expand...
Click to collapse
Probably, problem is "clockworkmod" folder into external SD card!
When you make backup, you must choise "tar format" instead "dup format"!!
almost there
Man!
That´s exactly my case!! SGS Vibrant T959, with CyanogenMod v10.1.2. I noticed that I was not accessing the internal sdcard. I tried to plug in the computer and enable the usb mass storage but it wouldn´t mount the internal sdcard. Then I rebooted in recovery mode (CWM recovery) and went to mount & storage -> mount sdcard. Rebooted and nothing. Went back to CWM recovery, mounted sdcard, and to browser it I went to 'install zip' just to see. I was able to see my old files.
Then I googled it and found this!
Thank you very much for your hint!
Funny thing is, this happened just after I installed this version (10.1.2). I was using v10.0 and it was just all fine (with 32 Gb external sdcard).
1) I removed it, and boot and there was my internal sdcard with all my files and backups!! ooohoooo
2) plugged my 32 gb sdcard back and it mounted .
3) reboot
4) and my internal SDcard was not mounted again .
So for now, everytime I boot I have to remove my 32gb external sdcard first, and plug it again after boot is finished.
Does anyone know how to def fix it ?!
Thanks!
gergefil said:
Well, I found out the real reason after tremendeous testing.I have a 32GB sdcard inserted. If I have lots of music and files on that card, phone doesn't mount internal sd on boot. (don't know the reason) But if I delete the musics and empty the external sd card, then internal sd mounts properly.
Really no iade how they effect each other but this is the case.
Click to expand...
Click to collapse
portisheadbr said:
Does anyone know how to def fix it ?! Thanks!
Click to expand...
Click to collapse
just a thought, Android might have issues when the SD card is not formatted using Android. Its advisable to format Sd cards in a PC and after that again in your Android Phone.
Not sure , if this would solve your problem, but worth a try, if its not too difficult to do.
Check this out!You , YES! you are an " Android ". Not your phone but U.
You Must watch this documentary concerning your privacy Terms & Conditions we had agreed to, by using a PC or Smartphone
How to say Thank you? If you find any post helpful on XDA, please click on the Thanks button
{
"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"
}
If you are using XDA App or Tapatalk, long press on the post and select :good: Thanks Its easier to give "Feedback" in this manner than make an additional post.
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发言
Hey guys, I'm having some issues trying to install spotify apk through adb. I've installed this before and it installed fine but now I keep getting no such file or directory found. I've run it in elevated PS and my phone is listed under abd devices as well. I'm sure it's probably something simple in the path that I'm overlooking but I can't figure it out. I've tried putting it in different directories in root/subfolders (/card/folder; /phone/downloads; etc.) but it can't find any path I give it.
edit: This is on a tmobile GS8+ , installing it via. local desktop works but of course it doesn't have the vendor flag
Code:
.\adb install C:/filepath/app.apk
is there a way to append the com.android.vending flag to this command?
{
"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"
}
Why not install it using "adb install" ?
Code:
adb install C:\Local_Path_to_APK\spotify.apk
I mentioned in my post that installing directly from my desktop via. adb install works fine (without vendor flag), what I can't get it to do is recognize the file path to my phone so I can also install it with the vendor flag. The thing is that I've been able to do this before so I'm not sure what happened.
corgin said:
I mentioned in my post that installing directly from my desktop via. adb install works fine (without vendor flag), what I can't get it to do is recognize the file path to my phone so I can also install it with the vendor flag. The thing is that I've been able to do this before so I'm not sure what happened.
Click to expand...
Click to collapse
The error "no such file or directory" means that you aren't using the correct path to your file on the sdcard. Do 'adb shell', and verify your sdcard's mount point with the "mount" or "df -k" command. It's probably mounted at "/sdcard", rather than "/card", regardless of what it shows up as in MTP in Windows.
Best of luck.
Rottgrub said:
The error "no such file or directory" means that you aren't using the correct path to your file on the sdcard. Do 'adb shell', and verify your sdcard's mount point with the "mount" or "df -k" command. It's probably mounted at "/sdcard", rather than "/card", regardless of what it shows up as in MTP in Windows.
Best of luck.
Click to expand...
Click to collapse
Oh, yeah I tried different phrases beforehand (sdcard, storage, card, etc.), Sdcard was the original path that worked before haha. So I tried the commands and I see /data/knox/sdcard (or tmp_sdcard) below. I'm assuming that some sort of recent security patch with knox might be preventing me from actually loading the sdcard? My sdcard is 128GB but the /media_rw path doesn't seem right either. Hmm...
mount:
Code:
rootfs on / type rootfs (ro,seclabel,size=1629824k,nr_inodes=407456)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,size=1700888k,nr_inodes=425222,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,nosuid,relatime,mode=600)
proc on /proc type proc (rw,nosuid,relatime,gid=3009,hidepid=2)
sysfs on /sys type sysfs (rw,seclabel,nosuid,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,nosuid,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,seclabel,nosuid,relatime)
none on /acct type cgroup (rw,nosuid,relatime,cpuacct)
none on /dev/stune type cgroup (rw,nosuid,relatime,schedtune)
tmpfs on /mnt type tmpfs (rw,seclabel,nosuid,relatime,size=1700888k,nr_inodes=425222,mode=755,gid=1000)
none on /config type configfs (rw,nosuid,relatime)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,nosuid,relatime,size=1700888k,nr_inodes=425222,mode=700)
tmpfs on /mnt/secure/asec type tmpfs (rw,seclabel,nosuid,relatime,size=1700888k,nr_inodes=425222,mode=700)
none on /dev/cpuctl type cgroup (rw,nosuid,relatime,cpu)
none on /dev/cpuset type cgroup (rw,nosuid,relatime,cpuset,noprefix,release_agent=/sbin/cpuset_release_agent)
pstore on /sys/fs/pstore type pstore (rw,seclabel,nosuid,relatime)
/dev/block/dm-0 on /system type ext4 (ro,seclabel,relatime)
/dev/block/sda20 on /cache type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc)
/dev/block/sda5 on /persist type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc)
/dev/block/sdd7 on /dsp type ext4 (ro,seclabel,nosuid,nodev,relatime,data=ordered)
/dev/block/sda6 on /efs type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc)
/dev/block/sda15 on /firmware type vfat (ro,context=u:object_r:firmware_file:s0,nosuid,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sda16 on /firmware-modem type vfat (ro,context=u:object_r:firmware_file:s0,nosuid,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro)
/dev/block/sda21 on /carrier type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc)
/dev/block/sda22 on /omr type ext4 (rw,seclabel,nosuid,nodev,noatime,noauto_da_alloc)
tmpfs on /storage type tmpfs (rw,seclabel,nosuid,relatime,size=1700888k,nr_inodes=425222,mode=755,gid=1000)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,seclabel,nosuid,relatime)
adb on /dev/usb-ffs/adb type functionfs (rw,nosuid,relatime)
/dev/block/dm-0 on /system/carrier type ext4 (ro,seclabel,nosuid,relatime)
/dev/block/dm-1 on /data type ext4 (rw,seclabel,nosuid,nodev,noatime,journal_checksum,noauto_da_alloc)
/data/knox/tmp_sdcard on /mnt/knox type sdcardfs (rw,nosuid,nodev,relatime,mask=0077)
/data/knox/sdcard on /mnt/knox/default/knox-emulated type sdcardfs (rw,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=1015,multi_user,mask=0006)
/data/knox/sdcard on /mnt/knox/read/knox-emulated type sdcardfs (rw,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=9997,multi_user,mask=0027)
/data/knox/sdcard on /mnt/knox/write/knox-emulated type sdcardfs (rw,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=9997,multi_user,mask=0007)
/data/knox/secure_fs/enc_media on /mnt/shell/enc_media type sdcardfs (rw,nosuid,nodev,relatime,low_uid=1000,low_gid=1000,gid=9997,multi_user,reserved=20MB)
/data/media on /mnt/runtime/default/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=1015,multi_user,mask=0006,reserved=20MB)
/data/media on /storage/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=1015,multi_user,mask=0006,reserved=20MB)
/data/media on /mnt/runtime/read/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=9997,multi_user,mask=0027,reserved=20MB)
/data/media on /mnt/runtime/write/emulated type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=9997,multi_user,mask=0007,reserved=20MB)
/data/knox/secure_fs/enc_user on /data/enc_user type ecryptfs (rw,seclabel,nosuid,nodev,relatime,ecryptfs_fnek_sig=b96b381490a68879,ecryptfs_sig=b96b381490a68879,userid=0,sdp_enabled,partition_id=0,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_enable_cc,ecryptfs_passthrough,base=,label=)
/mnt/shell/enc_media on /mnt/shell/enc_emulated type ecryptfs (rw,seclabel,nosuid,nodev,relatime,ecryptfs_fnek_sig=b96b381490a68879,ecryptfs_sig=b96b381490a68879,userid=0,sdp_enabled,partition_id=1,ecryptfs_cipher=aes,ecryptfs_key_bytes=32,ecryptfs_enable_cc,ecryptfs_passthrough,base=,label=)
/dev/block/vold/public:179,1 on /mnt/media_rw/0000-0000 type sdfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,fs=exfat,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,utf8,namecase=0,adj_req,symlink=0,bps=512,errors=remount-ro)
/dev/block/vold/public:179,1 on /mnt/secure/asec type sdfat (rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,fs=exfat,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,utf8,namecase=0,adj_req,symlink=0,bps=512,errors=remount-ro)
/mnt/media_rw/0000-0000 on /mnt/runtime/default/0000-0000 type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=1015,mask=0006)
/mnt/media_rw/0000-0000 on /storage/0000-0000 type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=1015,mask=0006)
/mnt/media_rw/0000-0000 on /mnt/runtime/read/0000-0000 type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=9997,mask=0022)
/mnt/media_rw/0000-0000 on /mnt/runtime/write/0000-0000 type sdcardfs (rw,nosuid,nodev,noexec,noatime,low_uid=1023,low_gid=1023,gid=9997,mask=0022)
df -k:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1629824 12760 1617064 1% /
tmpfs 1700888 1096 1699792 1% /dev
tmpfs 1700888 0 1700888 0% /mnt
tmpfs 1700888 0 1700888 0% /mnt/secure
/dev/block/dm-0 4578356 4376036 202320 96% /system
/dev/block/sda20 595136 10636 584500 2% /cache
/dev/block/sda5 28144 172 27972 1% /persist
/dev/block/sdd7 12016 4552 7464 38% /dsp
/dev/block/sda6 16048 936 15112 6% /efs
/dev/block/sda15 97232 45328 51904 47% /firmware
/dev/block/sda16 112576 74672 37904 67% /firmware-modem
/dev/block/sda21 41248 8 41240 1% /carrier
/dev/block/sda22 5968 8 5960 1% /omr
tmpfs 1700888 0 1700888 0% /storage
/dev/block/dm-0 4578356 4376036 202320 96% /system/carrier
/dev/block/dm-1 55885696 14479704 41378596 26% /data
/data/knox/tmp_sdcard 55885696 14479704 41378596 26% /mnt/knox
/data/knox/secure_fs/enc_media 55865216 14507100 41358116 26% /mnt/shell/enc_media
/data/media 55865216 14507100 41358116 26% /storage/emulated
/data/knox/secure_fs/enc_user 55885696 14479704 41378596 26% /data/enc_user
/mnt/shell/enc_media 55865216 14507100 41358116 26% /mnt/shell/enc_emulated
/mnt/media_rw/0000-0000 125009920 3599104 121410816 3% /storage/0000-0000
Yeah, looks like your storage is mounted at "/mnt/media_rw/0000-0000", which is interesting. An easy way to check is to just "adb shell" and then "pwd" to show your working directory. You should be in your "sdcard" by default. Otherwise, "cd /mnt/media_rw/0000-0000", and then "ls" to see the files there. If your spotify.apk is there, you know.
Best of luck.