Access to external SD card - Stock ROM (Rooted) - Galaxy S III Q&A, Help & Troubleshooting

I've encountered problems trying to access the external SD card on my rooted Samsung Galaxy S3.
There are entries in /mnt/ for both internal and external storage, namely the following mount points:
/mnt/sdcard/ - internal
/mnt/extSdCard/ - external
The former is mounted onto the filesystem as /sdcard/. Ideally I'd like to mount the external card instead. Based on information elsewhere on the site, I checked the /etc/void.fstab file with the intention of making changes. However I didn't find what I was expecting. Here's the relevant part of the file:
Code:
{
supported_exfat = yes
}
dev_mount sdcard /mnt/extSdCard auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1/
Based on this config I would have expected the external SD card to be mounted as /sdcard/. But clearly it isn't, and I don't understand why.
For the time being I am using Directory Bind to access external storage via /sdcard/external_sd/ but it would be easier to simply mount external storage as /sdcard/.
Anyone have any suggestions?

Related

[Q] Incorrect mounting sd card [CyanogenMod7.1.0.1 REPACK]

Incorrectly mounts the external sdcard in CyanogenMod7.1.0.1 REPACK.
The external card is connected as primary, and the internal sdcard as an extra.
After editing Vold.fstab, the situation changes slightly for the better. Now, the internal memory to get sdcard, and the external is not mounted at all.
P.S: Search the forums gave only what you need to edit Vold.fstab.
Here is the content of my Vold.fstab file:
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.3/mmc_host/mmc2
dev_mount sdcard2 /mnt/sdcard2 auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
dev_mount usbdisk /mnt/usbdisk auto /devices/platform/tegra-ehci
CM 7 by default mounts a "real" SDCard as /sdcard and any other storage (internal) as /emmc.
I believe it first became an option in CM7.1 that you can change this mounting (switch it so the internal storage is mounted as /sdcard ) in CyanogenMod Settings.
You no longer need to edit/modify the vold.fstab file.

[Q] How to restore mount point of internal sdcard

Hello! I've installed the XXLSJ 4.1.2 leak over CM10 (with Odin, 3+1 files, reparted with the 16GB pit)
Now everything is fine, except that my internal sdcard is mounted at
Code:
/dev/block/vold/259:3 [B]/storage/sdcard0[/B]
I would like to ask; what is the best way to restore the mounting point of the internal sd to
Code:
[B]/mnt/sdcard[/B]
Now the original 3e recovery can't mount my internal storage, because it tries to mount mnt/sdcard or /sdcard.
Also should I care the address of the block? (Which is originally something like /dev/block/mmcblk0p...)
Thanks for the answers!
Edit: My system/etc/vold.fstab:
Code:
# internal sdcard
{
ums_sys_path = /sys/class/android_usb/f_mass_storage/lun0/file
secure_format = enable
discard = enable
supported_exfat = disable
}
dev_mount sdcard /storage/sdcard0 11 /devices/platform/dw_mmc/mmc_host/mmc0/mmc0 encryptable_nonremovable
Fw:Sdcard mount problem
After upgrading to 4.1, the sdcards mount directory changed.
Not only internal sdcard but also external one face the same problem.
the external sd mount dir changed from:
4.0:
/mnt/sdcard/external_sd or /sdcard/external_sd
Click to expand...
Click to collapse
to
4.1:
/storage/sdcard1 or /extSdCard
Click to expand...
Click to collapse
which is bad.
Anyone knows how to fix/change it?
Thanks for answers!

[Q] Serious problem with Android's built-in encryption?

I came across a problem with Android's built-in encryption function and typical sdcard data. I searched everywhere on the internet and this is what I could collect so far:
Also, from my research, while I cannot confirm this, I have read that prior to 4.2, external (public) storage in Android was /mnt/sdcard/ (if you are not familiar with the Android file system, "sdcard" refers to public storage that is internal...not necessarily an external sdcard), but this was just a symbolic link from the protected /data/ directory. At the time, Android only encrypted /data/, which was fine because the symbolic link would also encrypt any personal files in the public directory.
After 4.2, due to multiple profiles, the public storage was moved to /storage/emulated/legacy. That means if Android's "full disk encryption" only encrypted /data...then any sensitive data in the public directories is not encrypted (this could be downloads from work, private photos, etc).
Click to expand...
Click to collapse
Source and full topic: https://productforum...xus/Lzsje-4QfTQ
This can be OEM dependent indeed, but /mnt/sdcard is now just a symlink to
a 'virtual' SD card that lives under /data. So downloaded documents, media
etc. are encrypted along with private data, etc. From the boot script:
# create virtual SD card at /storage/sdcard0, based on the /data/media directory
# daemon will drop to user/group system/media_rw after initializing
# underlying files in /data/media will be created with user and group
media_rw (1023)
If one some device /mnt/sdcard (external storage) is independent from /data,
it might not get encrypted. But then again they may modify the
firmware to encrypt it.
Click to expand...
Click to collapse
Source and full topic: https://groups.googl...uss/-mE-XTot0Gg (This is also only referring to Android versions =< 4.0)
1.) I checked a CM 11 installation on a Huawei Ascend Y300 and I could find the same internal SD card data in
/internal_sd -> /storage/sdcard0 (fuse)
/mnt/internal_sd -> /storage/sdcard0 (fuse)
/mnt/media_rw/sdcard0 -> /mnt/media_rw/sdcard (vfat)
2.) /data/media does not contain the files as the others in 1.).
3.) /internal_sd is the only partition visible via TWRP file manager, which could mean that the others are created during the start of Android itself.
2012
So the actual physical storage place is still /data/media. /storage/sdcard0 is a "virtual" SD card. /sdcard and /mnt/sdcard are symbolic links of /storage/sdcard0.
Click to expand...
Click to collapse
I'd guess that the virtual sdcard exists because /data/media is part of an ext# partition, so they use fuse filesystem and virtual sdcard to make it look like fat to apps, many of which don't understand ext# filesystems.
Click to expand...
Click to collapse
2013
http://forum.xda-developers.com/galaxy-s3/general/info-flashed-4-2-sdcard-data-t2274218
Click to expand...
Click to collapse
I'd assume the actual physical storage place is /storage/sdcard0 now, but I'm not sure.
Conclusion: To make the encryption include typical "sdcard data" again, we would have to somehow change it back to this:
So the actual physical storage place is still /data/media. /storage/sdcard0 is a "virtual" SD card. /sdcard and /mnt/sdcard are symbolic links of /storage/sdcard0.
Click to expand...
Click to collapse
Are my thoughts on this correct so far or does anyone have an idea?
Does this mean older Android versions (pre-4.2) did not actually have this problem?

[Q] HTC Desire 310 emulated and ext sd card data problems

Hi all. So, to explain my problem the best I can I'll start from the thing that bugs me the most, the apk's won't detect obb's on the ext sd card. If you don't know this phone comes with phone storage (/sdcard), emulated storage (/storage/emulated/legacy OR /storage/emulated/0) and the 3rd is my ext sd card. Now i know this can be done because i made it work a few days ago but since then i changed some stuff around and now it won't work anymore. My main goal was to completely switch the internal phone memory with the ext sd card (because of the obb problem) but that posed even more problems.
Here's my specs:
Model: HTC Desire 310
Android ver: 4.2.2
Baseband ver: MOLY.WR8.W1315.MD.WG.MP.V19.F5.P1
Kernel ver: 3.4.5 [email protected] #1
Build num: 1.00.401.14
ROOTed with Root Genius, replaced the chinese Kinguser with SuperSU, supposedly there aren't any ROMs for this device yet and it can't be S-Off'ed (yet) according to google/forums.
Here's what I've done/tried doing so far:
- Link2SD: partitioned the 16gb card to 12gb FAT32 / 3gb ext2, configured Link2SD and linked the game (Galaxy on Fire 2 for example)
obb is on /storage/sdcard1/Android/obb but i guess Link2SD doesn't link obb files
- FolderMount: is supposed to link games with their obb, didn't seem to do a thing
- External2Internal: spent a whole day messing with it, didn't seem to change anything
- Universal Init.d + SMenager: basically i tried running .sh scripts that are supposed to mount the partitions/sd cards, and yes i edited the scripts to match my mount points ( http://forum.xda-developers.com/showthread.php?t=1886091 )
- Edited the "vold.fstab": tried ~20 different combinations of mount points and paths, and it actually changes them but not the way i want (I don't know unix that well).
>> [mount_point] (label)
- The original vold.fstab gives me (in that order): internal storage [/sdcard] (sdcard), emulated internal storage [/storage/emulated/legacy] (sdcard), ext sd card [/storage/sdcard1] (sdcard2):
Code:
dev_mount sdcard /storage/sdcard0 [email protected] /devices/platform/goldfish_mmc.0 /devices/platform/mtk-msdc.0/mmc_host
dev_mount sdcard2 /storage/sdcard1 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-msdc.1/mmc_host
- #1 vold.fstab that gives me (in that order): internal storage [/sdcard] (sdcard), ext sd card [/storage/sdcard1] (sdcard), emulated internal storage [/storage/emulated/legacy] (sdcard2):
Code:
dev_mount sdcard /storage/sdcard1 auto /devices/platform/goldfish_mmc.0 /devices/platform/mtk-msdc.1/mmc_host
dev_mount sdcard2 /storage/sdcard0 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-msdc.0/mmc_host
- #2 vold.fstab that gives me (in that order): internal storage [/sdcard] (sdcard), ext sd card [/storage/sdcard1] (sdcard):
Code:
dev_mount sdcard /storage/sdcard1 auto /devices/platform/goldfish_mmc.1 /devices/platform/mtk-msdc.1/mmc_host
BUT i can't make it completely replace the internal storage with the ext sd card.
Here's what I THINK worked: used #2 vold.fstab, linked Galaxy on Fire 2 in Link2SD, used External2Internal to swap sdcard0 and sdcard1 (tho it didn't seem to change a thing) and the game worked fine, but since then i changed vold.fstab several times and installed/uninstall mentioned apps and now i don't know why it won't work.
I tried to include as much info as I could but feel free to ask for more and if someone can modify my vold.fstab or have some other solution for me please share.
Desire 310
Hi, Zim
Any luck on swaping memories? I am looking on all the forums about this and could not figure out any working option for our phone. Did you?

Swapping mount points

I have a cheapo DragonTouch Y88X. I'm not looking for a custom ROM or anything - its for the kids and honestly it does everything they need, with one exception: Disney Movies Anywhere can't download videos to the external SD card.
As near as I can tell, this is an application problem - hardwired looking for /mnt/sdcard instead of using the Google API to find where the SD card is mounted, and DragonTouch was brain dead and mounted part of the internal storage to /mnt/sdcard (the actual SD card gets mounted to /mnt/extsd).
OK, so I'm not going to get Disney to change the app (and there's no setting to change where it downloads to other than "Save To/Play From SD Card"), so I started poking around how to change the mount points. I'm reasonably familiar with linux, sys admin duties and the like. But the format and options on the fstab file are a bit unfamiliar to me... All I really want to do is make the external SD card be mounted at /mnt/sdcard (and maybe mount the internal partition to something useful - maybe app cache space or something?)
I managed to get root and installed ES File Explorer, and the fstab file (/fstab.sun8i to be specific) has the following lines that I think are relevant...:
Code:
...
/devices/virtual/block/nandk auto vfat defaults wait,check,noemulatedsd,voldmanaged=sdcard:auto
/devices/platform/sunxi-mmc.2/mmc_host auto vfat defaults wait,check,noemulatedsd,voldmanagedsd=sdcard:auto
/devices/platform/sunxi-mmc.0/mmc_host /mnt/extsd vfat rw,realtime,fmask=0000,dmask=0000,wait,check,voldm anaged=extsd:auto
/devices/platform/sunxi-mmc.1/mmc_host /mnt/extsd vfat rw,realtime,fmask=0000,dmask=0000,wait,check,voldm anaged=extsd:auto
...
I don't know quite enough about either fstab or Android/DragonTouch's variant of it to know why both sdcard and extsd have two entries each... Or exactly how to swap them. I could try to change the voldmanaged=[name] entry on each - would that be safe?
Is what I'm trying to do crazy, or should this work?
Thanks

Categories

Resources