I'm having mount issues with my TF700. Its unlocked and rooted, installed busybox. Stock ROM and Stock Recovery. It mounts the internal OK, mounts microSD OK, mounts SD OK. But if I plug in my external Bluray reader (with DVD inserted) It mounts USBDisk001, but is linked to my SD card which is already mounted! So now I have 2 mount links to my SDcard! I've rebooted and tried other things, but couldnt get it to work properly. So I removed the SD card. Plug in the Bluray drive and it does nothing (as expected). I open a terminal, become superuser, and mkdir /Removable/Bluray, then mount -t iso9660 /dev/block/sr0 /Removable/Bluray. It claims to have mounted Read-Only (as it should), but I enter the folder and ITS EMPTY! Whats wrong here?! I type blkid and it shows the disc Label. So it IS reading the disc. I try to unmount the disc and try again. umount /Removable/Bluray . It claims Invalid Argument as if nothing is mounted! WTF?!
Any help would be greatly appreciated. FYI, Same disc on linux and windows Machine shows files fine on same external drive.
Edit: Oh, and installing busybox didn't overwrite the original mount files. I used smart install from stericson's installer and mount is still symlinked to the original /system/bin/toolbox .
Sent from my ASUS Transformer Pad TF700T using xda premium
Related
Hello folks,
I am trying to move my google music cache to the external 32GB SD card so that it won't fill up my internal storage but somehow I fail.
Here is what I did so far:
format sdcard as ext2
manually mount sdcard since it won't automatically when ext:
Code:
mkdir /Removable/MicroSD
mount -r -w -t ext2 /dev/block/vold/179\:9 /Removable/MicroSD
mkdir /Removable/MicroSD/GoogleMusicData
Then move all data from /sdcard/Android/data/com.google.android.music/cache to /Removable/MicroSD/GoogleMusicData/cache
I did this with root explorer since I'm not too much of a terminal h4xx0r.
Delete the folder /sdcard/Android/data/com.google.android.music/
Link the new Folder on external MicroSD Card to the original location via this terminal command:
Code:
ln -s /Removable/MicroSD/GoogleMusicData /data/media/Android/data/com.google.android.music
Since /sdcard is already a link like the one I am setting up here, it is not possible to link to this linked location (/sdcard/Android/data/com.google.android.music).
Instead I had to link to the origninal destination of /sdcard which is /data/media.
Now the microSD card is accessible for root explorer. It shows read and write access.
But google music won't find it. It says that it doesn't have enough space to stream music so I figure that it somehow doesn't have access to the sd card.
What could be the issue here?
Also instead of 28GB free memory root explorer shows me only 364,44MB free memory. the command "df" in terminal however confirms 28GB of free memory.
I thought that a reboot might do it. But it doesn't. Instead it gets rid of all the hacking I've done in terminal. So I guess I would have to place a script in /etc/init.d for the link to be set everytime I reboot, right?
Help please?
We don't know how gmusic checks that, but I would suggest checking the perms on the mount, perhaps even mounting somewhere else.
Never done it and don't have the resources but I'm sure with root, making /mnt/sdcard a real microsd is possible.
Sent from my Transformer Prime TF201 using Tapatalk
Maybe this thread will help ?
Thanks for your response!
What do you mean by "checking the perms on the mount"?
I don't want to mount my microsd to /sdcard since then I would have 16 gigs of unused space on my internal memory.
I would rather just link this music folder to my external card and maybe some others later (e.g. DCIM and so on).
I have also tried the mount -o bind command instead of ln but that didn't do the job either. the folder com.google.android.music then only appeared under /data/media/Android/data/ but not under /sdcard/Android/data/ which I totally don't understand how that can happen.
I have root of course.
Does anybody maybe have a script by hand of a similar undertaking so that I can look into that and try to understand how this whole mounting and binding thing works?
I just installed Dosbox Turbo and it sees my Transformer TF700 internal storage as /sdcard/
I knew that was normal, but can't figure out how to mount my dock's sdcard.
I tried
"mount d /removable/sd" and got "Directory /removable/sd doesn't exist."
I also tried every other path I could think of. Does anybody have any insight that could help me?
I might just copy the game folders onto internal storage, but it bugs me that I can't get this reading the card.
By the way, I'm running stock JB 4.1.1, not rooted, not unlocked.
AnakiMana said:
can't figure out how to mount my dock's sdcard.
Click to expand...
Click to collapse
The tablet should mount it itself, and show an SD card icon at the bottom of your screen, if it is recognized.
What is the format of the card (FAT32, exFAT, NTFS, etc)? Using an unsupported format or unformatted card is usually the reason for it not to be recognized and mounted.
Total Commander shows all SD cards (and USB drives) at the top of it's main browse screen, including their path.
My MicroSD card is mounted as /Removable/MicroSD. Please note that Linux, thus Android is case sensitive. Meaning that upper and lowercase letters are not treated the same as in Windows for example. So /removable/sd is not the same as /Removable/SD.
If you are using Android Terminal Emulator, use the tab key to activate the auto complete feature. Type /R, then press tab and it will complete it if there is only one match (in this case /Removable/). When there is more than one match, it will show you a list of matches. This way it is easier to not make a typo when using long paths.
Thanks for your reply.
The card was always visible from File Manager (Asus app), I just hadn't been able to use the mount command successfully in Dosbox.
I got it working by using proper capitalization, as you suggested! Thanks!
The answer, for anyone else with this issue, is: /Removable/SD
So, the command from Dosbox is "mount d /Removable/SD", to make the sdcard your D:\ drive.
I wanted to convert my external sdcard to ext4 so I can create a symbolic link. Mainly because one of the apps I use won't see the sdcard (devs tell me it's because the tf700 isn't using mass storage drives apparently) and I thought this might solve the problem if I could put a link on the internal card that pointed to the external. I'm aware that symbolic links cannot work with FAT32 partitions but will between ext4/3/2 partitions.
I formatted the card with minitool partition and the TF700 wouldn't mount it. It shows up in settings > storage as a MicroSD with a Mount option but this simply does nothing. Having trawled through some thread someone provided this script to mount an ext4 card.
Code:
mkdir /Removable/MicroSD
mount -o noatime,nodiratime -t ext4 /dev/block/mmcblk1p1 /Removable/MicroSD
chmod -R 777 /Removable/MicroSD
Which should be done at each boot. This seemed to work as I got to the card and was able to manually copy something to it but it seems to be flakey and unreliable. eg. a picture copied to it would fail to load. I managed to get it to after a while (not sure what I did). Then I tried an .apk file and it wouldn't install, giving an error. I also used Rom toolbox to specify Apps2SD destination to the external but trying to install anything will give "not enough space" error.
So I am stumped.
As I am rooted but NOT unlocked I can't install a rom which might be the solution but I'd like to know if what I'm trying to do is possible without that.
I find it odd that the TF700 can't deal with an ext4 partition since it can happily deal with them on the internal. I'm confused so any clear explanation of the situation would be welcome.
louiscar said:
and I thought this might solve the problem if I could put a link on the internal card that pointed to the external. I'm aware that symbolic links cannot work with FAT32 partitions but will between ext4/3/2 partitions.
Click to expand...
Click to collapse
The internal "sdcard" is not an ext4 partition, it's a FUSE filesystem that emulates some properties of FAT (no case sensitivity, no permissions) on top of ext4. It also does not support symlinks.
louiscar said:
I formatted the card with minitool partition and the TF700 wouldn't mount it.
Click to expand...
Click to collapse
Many users of the Data2SD mod had problems with Minitool - use gparted to create ext4 partitions.
louiscar said:
This seemed to work as I got to the card and was able to manually copy something to it but it seems to be flakey and unreliable. eg. a picture copied to it would fail to load. I managed to get it to after a while (not sure what I did).
Click to expand...
Click to collapse
Are you on the latest 10.4.4.25 firmware? Because that fixed something with microSD cards, and it's the only kernel so far that reliably works with my Sandisk "Mobile Ultra" microSD card, even with ext4.
_that said:
The internal "sdcard" is not an ext4 partition, it's a FUSE filesystem that emulates some properties of FAT (no case sensitivity, no permissions) on top of ext4. It also does not support symlinks.
Click to expand...
Click to collapse
Ok although I don't understand the Fuse fs (still trying to get to grips with basic unix stuff), I did think that symlinks were used internally.
_that said:
Many users of the Data2SD mod had problems with Minitool - use gparted to create ext4 partitions.
Click to expand...
Click to collapse
Ok I'll give that a go.
_that said:
Are you on the latest 10.4.4.25 firmware? Because that fixed something with microSD cards, and it's the only kernel so far that reliably works with my Sandisk "Mobile Ultra" microSD card, even with ext4.
Click to expand...
Click to collapse
Yes, I've just done the OTA to .25 a few days ago.
So basically what you are saying is that there's no reason why an external MicroSD formatted as Ext4 shouldn't work with the TF700?
Many thanks for the quick reply. I'm going to get gparted and give this a go.
My device is a BLU Studio 5.0S (GSM Arena link in my sig for the exact phone, model D570a
My ROM is a modified variant of the stock from BLU, that I made myself
The SD card in question is a 8GB SDHC Class 4 card.
When I physically take the card out of the phone, put it in an SD adapter, and put it in my laptop (running Ubuntu 13.10 64bit), it is just fine, and I can read, write, execute, etc. with no problems whatsoever.
When I hook the phone up to the computer via USB, I can get into the phone's memory (1.4GB) just fine, but when I try to mount the 8GB SD card, I just get this message:
Code:
Error mounting /dev/sr1 at /media/k2trf/8GB C4: Command-line `mount -t "vfat" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,shortname=mixed,dmask=0077,utf8=1,showexec,flush" "/dev/sr1" "/media/k2trf/8GB C4"' exited with non-zero exit status 32: mount: block device /dev/sr1 is write-protected, mounting read-only
mount: /dev/sr1: can't read superblock
The only difference betwen the arguments on the internal storage and the SD is the GID -- for the internal storage it is 1023 (which doesn't coorespond to anything), but for the 8GB SD card it is 1015 (which is sdcard_rw).
Mounting it shows GID 1000 (which would be the group id for my account, 'k2trf' on the computer.
That's the only difference between the two I can see on the device. Since there are both entries for /dev/sr0 and /dev/sr1 in my /dev/, I can safely assume that sr0 is the internal memory (which is working perfectly), and sr1 is the SD card (which seems to have a bad superblock?).
This confuses me, because physically putting the SD card in the laptop, it's completely fine, and there's no super block issues that I've been able to find, so I have to assume that it's the superblock controlling the sdcard in the phone that's bad (/dev/block/void/179:33) -- is there a way I can go about rewriting the superblock somehow for just that partition?
I've already tried doing it like I would on the laptop for other flash memory (using mke2fs and e2fsck), but I guess busybox doesn't include those commands (which would make a bit of sense, I can't imagine those are simple or small functions).
i want my 360 qiku n5 cellphone to use the tf card as an internalSD card, and also link to the /data/data diretory,so that I can make the storage more sufficient.
i have so many app to install, and the app use much space consuming up the internal space,leaving the tf card empty.
i'd tried making tf card ext4 and mounted to /mnt/sdcard-ext,and maked a link "ln -s /mnt/sdcard-ext/data /data/data",but the apps just crashed as soon as they started.then i deleted the link and cellphone return normal.
after try i found using the "su, mount" script to mount tf card on any directory,the nornal apps which do not use "su" can't read the mount point,I think that's why i link the tf card to /data/data but apps could not start. So how can i solve this problem?I use the supersu as the root and have allready turn off the "Mount namespace separation" option.
And how can i make a startup autorun script on the android6 phone?
Anybody help me please?
This will not work how you want. Apps on SD cards only work with Googles new feature to make the sdcard as internal storage. But even that is buggy due to the sdcard code that has never been made to work for apps on sdcard.