Related
So apparently I have to use my computer or root explorer to write to my SD card since the 3.2 update. Does anyone know how this might be fixed to allow general file managers or applications to take advantage of?
same here....
f'ing moto fail here....this is NOT sd support to me
i have been using file manager HD and it will copy files to & from the sd card and delete from the sd card. it just wont "move" to the sd card.
EDIT- was using root explorer...not the other one.
Did you do anything special since upgrading to #Version three point two? I use the same program and it won't move, copy, or delete.
jase33 said:
i have been using file manager HD and it will copy files to & from the sd card and delete from the sd card. it just wont "move" to the sd card.
Click to expand...
Click to collapse
I can copy from the SD card but not paste to using the same software...this mean its read only
To be clear, I updated using update.zip and now running tiamat kernel, but I'm sure it was read only before I flashed the new kernel
I updated to 3.2 with ota and manually rooted. using stock kernel. write to sd works fine. maybe the method you updated from or the kernel you use is causing an issue.
sdcard
heh i find it amusing:
Real SDCard = /mnt/external1
Same ole crap SDCard = /mnt/sdcard, /sdcard, /data/media, and i bet more if i care to look harder.
jase33 said:
I updated to 3.2 with ota and manually rooted. using stock kernel. write to sd works fine. maybe the method you updated from or the kernel you use is causing an issue.
Click to expand...
Click to collapse
Are u talking about the Sdcard folder or the external1 folder?
I updated via update.zip method
Edit: Attached screenshot of my external1 permission
jase33 said:
i have been using file manager HD and it will copy files to & from the sd card and delete from the sd card. it just wont "move" to the sd card.
Click to expand...
Click to collapse
Moving from one source to another isn't possible. It's a linux/android thing. So that's nothing to worry about.
Remount /mnt/external1 as read/write
Here's what I've done to make /mnt/external1 read/write accessible:
adb shell or any other terminal emulator to get to a shell on the xoom
su to get to the # prompt
umount /mnt/external1
mount -t vfat -o fmask=0000,dmask=0000,rw /dev/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
That remounts the sdcard without using vold, which is enforcing a mask on the perms.
Now to get this to happen at boot...
Stealyourface said:
Moving from one source to another isn't possible. It's a linux/android thing. So that's nothing to worry about.
Click to expand...
Click to collapse
Yeah I know.....I was just responding simply
Sent from my HD2
Stealyourface said:
Moving from one source to another isn't possible. It's a linux/android thing. So that's nothing to worry about.
Click to expand...
Click to collapse
I move files all the time in Linux, via both command line and file manager. I don't know where you are getting this "Linux/Android can't move files" from.
Given up and revert back to Tiamat 1.1
I reflashed stock and upgraded to 3.1 then 3.2 only to learn that the SD card was not writable within the xoom. I have full confidence that one of the devs will release a mod for 3.2 to get us all the features that we are accustomed to. Until then I've flashed back to Tiamat 1.1.
ekarelis said:
Here's what I've done to make /mnt/external1 read/write accessible:
adb shell or any other terminal emulator to get to a shell on the xoom
su to get to the # prompt
umount /mnt/external1
mount -t vfat -o fmask=0000,dmask=0000,rw /dev/block/platform/sdhci-tegra.2/mmcblk0p1 /mnt/external1
That remounts the sdcard without using vold, which is enforcing a mask on the perms.
Now to get this to happen at boot...
Click to expand...
Click to collapse
This is exactly right. It appears vold is now placing special perms above standard media_rw perms. So, apps without this level of permission can not write to external storage. We will address this in the upcoming Tiamat Rom release.
looking forward to 3.2 cusrom rom
Thanks brd. Very much looking forward to the tiamat 3.2 based rom.
mambomta said:
I move files all the time in Linux, via both command line and file manager. I don't know where you are getting this "Linux/Android can't move files" from.
Click to expand...
Click to collapse
Move a file from your xoom (if you even have one) from internal storage to external. It either won't let you, or it'll get corrupted in the process.
Stealyourface said:
Move a file from your xoom (if you even have one) from internal storage to external. It either won't let you, or it'll get corrupted in the process.
Click to expand...
Click to collapse
My Xoom should arrive tomorrow. If the Xoom is not allowing a move, it is a bug, not a limitation in Linux.
Hi.
As so many apps still don't support card locations other than /mnt/sdcard, I manually run as root the following to mount /Removable/MicroSD off /mnt/sdcard
mount -o bind /Removable/MicroSD /mnt/sdcard/MicroSD
This works great. Non /Removable aware apps then pick up files on the Transformers sdcard slot.
However, I'd like to automate this. Anyone know how I would do this? I guess a tweak to the android equivalent fstab file?
Thanks!
I have been looking for a solution for this, and found an older thread here on XDA with several methods.
I used root explorer to modify the mount point in /etc/vold.fstab
Just change the mount point from /Removable/MicroSD to /mnt/sdcard/MicroSD and reboot.
This seems to work great so far, but I have only been using this for a couple of hours. Don't forsee any problems though.
Sent from my Transformer TF101 using Tapatalk
kbrabble said:
I have been looking for a solution for this, and found an older thread here on XDA with several methods.
I used root explorer to modify the mount point in /etc/vold.fstab
Just change the mount point from /Removable/MicroSD to /mnt/sdcard/MicroSD and reboot.
This seems to work great so far, but I have only been using this for a couple of hours. Don't forsee any problems though.
Sent from my Transformer TF101 using Tapatalk
Click to expand...
Click to collapse
Thanks for that. I'll give it a go!
Hmm, this seems to cause a force close when you eject the card. It then also fails to mount the first 2-3 times when you plug the card back in.
I guess some Asus service is relying on the card being at /Removable
There must be a way to autorun a mount -bind somehow?
Have you also tried hooking up to your computer, as I know on some devices changing the mount points to nested like that would screw up the process for mounting to the computer properly.
I haven't experienced any force closes, or any problems mounting the card when reinstalled. As far as mounting on the computer, I have not tried. I agree that a -bind would be the best way, but haven't found a way to do this at boot yet.
Sent from my Transformer TF101 using Tapatalk
I just upgraded to GB 2.3.6 and then rooted by installing a new kernel via odin. I went in and tried to do a nandroid backup and it brings up an error that it can't mount the sdcard. Did i do something wrong or is my card going bad?
Sent from my SGH-T989 using xda premium
darock159 said:
I just upgraded to GB 2.3.6 and then rooted by installing a new kernel via odin. I went in and tried to do a nandroid backup and it brings up an error that it can't mount the sdcard. Did i do something wrong or is my card going bad?
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Interesting. If you use the 'Files' application when the phone is running does it show you anything? It should display the files/folders on the sdcard.
Yes I can see all my files and such just not in recovery
Sent from my SGH-T989 using xda premium
maybe do a fix permissions? I'm wondering if they somehow got hosed & prevent CWM from mounting.
Sent from my SGH-T959V using XDA App
Nope fixing permissions did nothing for it. It still brings up can't mount sdcard error. i can't install any zip files too, same error
Sent from my SGH-T989 using xda premium
What was the phone running before you upgraded? Did you have CWM, voodoo, etc?
Sent from my SGH-T959V using XDA App
Try backing up your SD card and then reformat it to see if that fixes the error
agreed back up sd card, maybe try changing voodoo, then is that doesn't work reformat and good to go
Can't format the scard on the phone since it won't mount. any other ideas. i am not sure what i am doing with voodoo so didn't mess with that.
Sent from my SGH-T989 using xda premium
darock159 said:
Can't format the scard on the phone since it won't mount. any other ideas. i am not sure what i am doing with voodoo so didn't mess with that.
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
If your computer, Wii, or whatever can mount the sdcard you could format it that way.
Have you tried shutting the phone down, removing the SD card, and putting it back?
Do you have the Android SDK installed? If so, put the phone in USB debugging mode, crank up a shell (adb shell), and type:
mount
If the filesystem is actually able to mount the phone during normal operation you will see a line similar to this (note it's all actually 1 line):
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dm
ask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
If you see that, try these commands:
cd /
ls -l sdcard
That should show you the effective permissions on the sdcard, like this:
ls -l sdcard
lrwxrwxrwx root root 2011-11-20 10:16 sdcard -> /mnt/sdcard
The 'l' means it's a symbolic link (shortcut, in essence) to another place (/mnt/sdcard)
The rwxrwxrwx are the permissions (read, write, execute). You see it three times because permissions are listed for user (rwx) group (rwx) and global (rwx).
The 'root root' is the owner and group for that directory.
If you were able to execute the command, do your permissions & ownership look the same?
I just installed a new ROM and the SDCARD and SDCard-ext are in the wrong location. They are listed under the root director ( / ) and /storage instead of under /mnt/sdcard
Does it work? You could create a symlink. If that fixed it, put it in a script on bootup.
post-mortem said:
Does it work? You could create a symlink. If that fixed it, put it in a script on bootup.
Click to expand...
Click to collapse
Does it work is a relative question. (wasn't meant to sound wise-a$$). I can access them, but apps do not see them at all. They are looking for the cards in /mnt therefor not finding them.
I changed them in /system/etc/vold.fstab but now it won't boot. The not booting is not an issue, I can fix that, but I don't know how to fix these incorrect paths/
No one else who's using this ROM is having these problems? I say either reflash, create symlinks, or choose another ROM.
post-mortem said:
No one else who's using this ROM is having these problems? I say either reflash, create symlinks, or choose another ROM.
Click to expand...
Click to collapse
Not sure if anyone else is running it. Haven't been able to find a thread on here for it. How do you do symlinks?
mikemikemikexxx said:
Not sure if anyone else is running it. Haven't been able to find a thread on here for it. How do you do symlinks?
Click to expand...
Click to collapse
ln -s target shortcut
See a bit more here.
Make a script in your /system/etc/init.d directory, so these links will be created on every boot.
post-mortem said:
ln -s target shortcut
See a bit more here.
Make a script in your /system/etc/init.d directory, so these links will be created on every boot.
Click to expand...
Click to collapse
From what I have read you cannot use them on FAT.
Why does editing this file not work? I fail to see how Android could do anything other than read the file, provided permissions are the same.
mikemikemikexxx said:
From what I have read you cannot use them on FAT.
Why does editing this file not work? I fail to see how Android could do anything other than read the file, provided permissions are the same.
Click to expand...
Click to collapse
The internal memory is not FAT; typically, only the 1st partition on the SD card is FAT, everything else should be EXT. So, executing ln -s /storage /sd-ext should work (or wherever it's currently being mounted).
post-mortem said:
The internal memory is not FAT; typically, only the 1st partition on the SD card is FAT, everything else should be EXT. So, executing ln -s /storage /sd-ext should work (or wherever it's currently being mounted).
Click to expand...
Click to collapse
I meant the card but ln is not working.
One more thing I am going to try is an ADB pull and push. If that doesn't work I really need some community support.
bump to the front.
Are my questions that complex or that dumb that I get so few replays? /bump
Sent from my XT875 using xda app-developers app
Is there a good reason that you don't want to use another ROM?
Mainly speed and compatibility. I need the offline commands only available in JB. Stock ROM is dead slow and is only ICS. Other custom ROMs were also on the slow side and/or battery hogs.
Sent from my XT875 using xda app-developers app
So, is this right?
FAT partition is currently being mounted as /storage
EXT partition is currently being mounted as /mnt/sdcard
post-mortem said:
So, is this right?
FAT partition is currently being mounted as /storage
EXT partition is currently being mounted as /mnt/sdcard
Click to expand...
Click to collapse
Well the way my phone is laid out is
System (I assume too large so they split it in two which resulted in the below SD-Card)
SD-Card
SD-Card EXT (The actual SD Card) - FAT32
I assume the System and SD-Card are standard Android partition format.
Do you use a file manager on the phone, such as ES File Explorer? Are you familiar with using adb?
Edit: Basically, I'm trying to figure out the exact path of the mounted partitions, and where they're supposed to be mounted.
post-mortem said:
Do you use a file manager on the phone, such as ES File Explorer? Are you familiar with using adb?
Edit: Basically, I'm trying to figure out the exact path of the mounted partitions, and where they're supposed to be mounted.
Click to expand...
Click to collapse
They are 100% supposed to be mounted under: /mnt/sdcard and /mnt/sdcard-ext
Right now they are mounting to: /storage/sdcard and /storage/sdcard-ext
There is also an entry in under root ( /sdcard and /sdcard-ext --- For these two I am booting into stock ROM to see if they are suppose to be directly in root as well, will post up when I know)
Check the scripts in your init.d to see if one of them is mounting the sd partitions under /storage.
I suppose you could also try booting without the sd card in place, and see if those /storage directories still exist. Not sure how much that will tell you, though.
post-mortem said:
Check the scripts in your init.d to see if one of them is mounting the sd partitions under /storage.
I suppose you could also try booting without the sd card in place, and see if those /storage directories still exist. Not sure how much that will tell you, though.
Click to expand...
Click to collapse
The init.d for sure says to load sdcards to /storage . (on this particular ROM only)
I will try without the sdcard as you suggested and let you know. Battery died on me, phone won't boot even when plugged in until at least 10%.
Which script is mounting the sd card to /storage? Is it part of the ROM, or is it something which the dev included in this ROM? I ask in case the ROM expects the sd card to be mounted there.
Regardless, try changing the script to link to /sdcard.
Hello
Finally i found a way to mount sd partition used in 4.2.2(after 2 hours ) on 4.4.2(cm11)...
So this is the way i do it:
Be sure that your checked ADB Debugging in Developer menu,your phone is recognized in ADB and you have rooted your rom.
Run ADB and tipe this:
Code:
adb root
adb shell
mount -o rw -t vfat /dev/block/mmcblk0p32 /mnt/shell/emulated/0
Symlinks will do the rest.
Then go with any android explorer to /sdcard or /storage/sdcard0 and see if all is good (ye,it will be used for internal sd) Now you have full access to your old 4gb sdcard used in 4.2. (And finally you can download asphalt 8 or any other big game )
The only bug i found is Settings>Storage dont show 4gb,but its there.
Work when connect with computer too No problems with Gplay,camera too.
This is temporary fix,so use it till @varun.chitre15 release kernel with the real fix
You need to repeat this steps after every restart
Please test and report
P.S.- Im using CM11 alpha 2 with ThunderZap 4.1 kernel
Didn't worked on PA BETA 6.
I discovered this few days ago, but I had used /sdcard2 as the new mount point to avoid conflicts with the default path.
Instead of using init.d script the correct way of doing this is replacing all references of /data/media and emulated sdcard with the new block.
I will post a new kernel tomorrow here which will fix the internal storage completely on any android 4.4 ROM
Sent from my C2105 using Tapatalk
not working
Not working on CM11 either
varun.chitre15 said:
I discovered this few days ago, but I had used /sdcard2 as the new mount point to avoid conflicts with the default path.
Instead of using init.d script the correct way of doing this is replacing all references of /data/media and emulated sdcard with the new block.
I will post a new kernel tomorrow here which will fix the internal storage completely on any android 4.4 ROM
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
Ye,I used /data/sdcard2 first,but then i try to mount it directly to sdcard0 and that was the place where it worked correct
Will wait for your kernel Good luck with it.
Navneet Suresh said:
Not working on CM11 either
Click to expand...
Click to collapse
Wait for the new kernel from varun
Shivam Kuchhal said:
Didn't worked on PA BETA 6.
Click to expand...
Click to collapse
Navneet Suresh said:
Not working on CM11 either
Click to expand...
Click to collapse
This should work for anyone
1. Create a folder in root say sdcard2
2. Open terminal or shell with root permissions
Then type
Code:
mount -t vfat /dev/block/mmcblk0p32 /sdcard2
Now you can access your true internal storage but only through terminal emulator Here is how
Code:
su
cd sdcard2
ls
This will give you root level access to your storage.
Sent from my C2105 using Tapatalk
Not working
varun.chitre15 said:
This should work for anyone
1. Create a folder in root say sdcard2
2. Open terminal or shell with root permissions
Then type
Code:
mount -t vfat /dev/block/mmcblk0p32 /sdcard2
Now you can access your true internal storage but only through terminal emulator Here is how
Code:
su
cd sdcard2
ls
This will give you root level access to your storage.
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
Not working am unable to create sdcard2 folder with Solid Explorer any other way (not even with terminal explorer)
Navneet Suresh said:
Not working am unable to create sdcard2 folder with Solid Explorer any other way (not even with terminal explorer)
Click to expand...
Click to collapse
I updated OP.Try it and be sure that you phone is recognized in ADB and of course rooted rom
Ok works now
Navneet Suresh said:
Not working am unable to create sdcard2 folder with Solid Explorer any other way (not even with terminal explorer)
Click to expand...
Click to collapse
varun.chitre15 said:
This should work for anyone
1. Create a folder in root say sdcard2
2. Open terminal or shell with root permissions
Then type
Code:
mount -t vfat /dev/block/mmcblk0p32 /sdcard2
Now you can access your true internal storage but only through terminal emulator Here is how
Code:
su
cd sdcard2
ls
This will give you root level access to your storage.
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
siankatabg said:
I updated OP.Try it and be sure that you phone is recognized in ADB
Click to expand...
Click to collapse
Ok works now but only shows in terminal I used this config as I wasn't able to use it directly :
Made a folder in emulated sdcard
Changed the mount point to it
Code:
mount -t vfat /dev/block/mmcblk0p32 /storage/emulated/legacy/sdcard2/
Then
Code:
su
cd sdcard2
ls
It shows in Terminal only as stated by Varun
Nice work :good: @varun.chitre15
EDIT : o.f.c am rooted -_- leave it it worked with a small workaround stated above.
Nice
Dont know why my method not work for you... but i can see all the files with explorer(got picture in op) and its used for internal sd (i can use it from computer too)
But lets all wait for the real fix from varun
hmm
siankatabg said:
Nice
Dont know why my method not work for you... but i can see all the files with explorer(got picture in op) and its used for internal sd (i can use it from computer too)
But lets all wait for the real fix from varun
Click to expand...
Click to collapse
Even if I use your method stated in OP it shows the emulated one it must be a CM11 bug
Navneet Suresh said:
Ok works now but only shows in terminal I used this config as I wasn't able to use it directly :
Made a folder in emulated sdcard
Changed the mount point to it
Code:
mount -t vfat /dev/block/mmcblk0p32 /storage/emulated/legacy/sdcard2/
Then
Code:
su
cd sdcard2
ls
It shows in Terminal only as stated by Varun
Nice work :good: @varun.chitre15
EDIT : o.f.c am rooted -_- leave it it worked with a small workaround stated above.
Click to expand...
Click to collapse
You need to mount the root subsystem as root and then create the folder
Code:
mount -o rw, remount /
mkdir /sdcard2
Sent from my C2105 using Tapatalk
Navneet Suresh said:
Even if I use your method stated in OP it shows the emulated one it must be a CM11 bug
Click to expand...
Click to collapse
This emulated folders are the method used from sony,I only mount the mmcblk0p32 there to use it for internal sd(not for third sd),so when i mount it there,symlinks do all the rest and you can see it in /sdcard,/storage/sdcard0 and so on
P.S.-Dont know why ,but if you mount it with ADB you will see the files with explorer not only with terminal
varun.chitre15 said:
You need to mount the root subsystem as root and then create the folder
Code:
mount -o rw, remount /
mkdir /sdcard2
Sent from my C2105 using Tapatalk
Click to expand...
Click to collapse
siankatabg said:
This emulated folders are the method used from sony,I only mount the mmcblk0p32 there to use it for internal sd(not for third sd),so when i mount it there,symlinks do all the rest and you can see it in /sdcard,/storage/sdcard0 and so on
P.S.-You can mount it with ADB and you will see the files with explorer not only with terminal
Click to expand...
Click to collapse
Ok guys it seems the issue has a temporary fix, @varun.chitre15 I forgot to remount as RW my bad :silly:
Oh man thats really great
Wow!! Finally bug is fixed!! Will be checking for your kernel tomorrow @varun.chitre15
Thank you so much
The fact is you can also access the internal storage using ddms from android sdk
varun.chitre15 said:
The fact is you can also access the internal storage using ddms from android sdk
Click to expand...
Click to collapse
Oh hmm yep. BTW for those who don't know what's DDMS
More progress ...!
Works completely fine as a separate partition. Now you have the 2GB emulated and 4GB true internal storage completely accessible. Bonus right?
Await my tomorrows release. I am also going to release updated CM with some more fixes of others in thread by @#root or a new thread maybe.
But I have got exams from Tuesday. Will try as hard as possible to release everything tomorrow. Finally got this irritating bug fixed
Cheers
varun.chitre15 said:
More progress ...!
Works completely fine as a separate partition. Now you have the 2GB emulated and 4GB true internal storage completely accessible. Bonus right?
Await my tomorrows release. I am also going to release updated CM with some more fixes of others in thread by @#root or a new thread maybe.
But I have got exams from Tuesday. Will try as hard as possible to release everything tomorrow. Finally got this irritating bug fixed
Cheers
Click to expand...
Click to collapse
Oh great i am backing up my data and waiting for you release of cm11 tomorrow