i tried hijacking the other 1.4.0 thread but got ignored and didnt want to keep a something stale that was off-topic alive.
so, i have flashed 1.4.0, verified that the kernel is in fact running. i wiped before the update to get rid of other issues i was having with some apps.
now, with 1.4.0 running, it appears that the external sdcard is not mounting while the system is booted. in recovery, it shows up as it should with all of the files. i have an /mnt/sdcard/sdcard2 and i have an an external directory under /sdcard
ive tried with card in before boot and after. i can say that dmesg is in fact seeing the card being removed and pushed in; however it doesnt seem to 'automount' from vold.fstab properly, or something else is jacked.
that being said, i dont seem to have a /devices which is where these things are suppose to be mounting from, is it not?
/sys/devices/platform/sdhci-tegra.2/mmc_host/mmc1
should i add the prefix /sys to both the usbOTG and sdcard to fix this?
or is there something else that is missing? presumably i could also create a symbolic link /devices -> /sys/devices, or does the kernel chroot to /sys at some point so none of this is needed, and i am having a different problem?
thanks for the help,
~marion
ya i noticed mine sd card is doing the same thing wont mount but works in recovery and i know it did work bc i had sdcard access through root explorer on v1.4.0 and now it does not work like it died over night
mine has not worked since moving to 1.4.0.
i originally went from 1.3.2 to 1.4.0 but the update didnt work well through the clockworkmod steps was having problems mounting e: so i went back to 1.3.1 then -> 1.4.0 [after wiping cache/data, and readding an sdcard2] using kernelmanager.
the update worked well, i rebooted to recovery and say that i could mount e:, and files where on the sdcard as expected. when booting to OS external has no files and sdcard2 has no files. also using connectbot for a shell, df shows nothing mounted.
is this because vold.fstab isnt mounting from /sys as described in my earlier post?
still unable to mount external sdcard while xoom is boote in 1.4.0.
Am able to pc-mount, and back up to it via recovery... no one else is seeing anything similar?
In 1.4.0 the sdcard should be in /sdcard/external not sdcard2. The card has to be in before turning it on. They are not hot-swappable.
Sent from my Xoom
Guys this is why Mass Storage has been removed in 1.4.1. Here's basically what's going on. When the device boots, the Sdcard is mounted to data/media/external which is the same as Sdcard/external. The Sdcard mounts before data/media is "fused" to create a virtual internal Sdcard. This is the only reason why you can actually see the external Sdcard inside the internal Sdcard. And this is why gallery can see the external Sdcard. However, in order for the Sdcard to mount as mass storage, Vold.fstab MUST mount the Sdcard at mnt/Sdcard so that Vold service can see it. But, this is the same mount point the internal storage is "fused" to. So when mass storage is done, it attempts to remount the sdcard where it was previously mounted, sdcard/external. But because of the way "fuse" works, it does not let any devices be mounted inside it. This is why I need source to do it right. I can then tell Vold to look some other place for the sdcard mount point. Until then, it's borked and that's why I pulled it.
@bwcorvus: in my first post i said that it wasnt showing up in sdcard2 or external... maybe i wasnt clear enough but its there.
@bigrush: thats exactly what i was seeing, and what i was presuming. i figured the lack of response meant either people werent seeing the issue or noticing it.
that being said... dmesg shows the device showing up if inserted/removed while running. but its showing out of /sys/devices... instead of /devices... changing that in vold.fstab didnt do anything for me as im not sure i have a great grasp on the boot sequence.
~marion
That's odd, mine mounts to external with no issue with 1.4.0
Related
This just popped up yesterday as before I had no issues. I can see the card, I can see the data, I can mount the card. The phone is rooted and I cannot change the permissions with root explorer, or any other Root file manager. If I put the SDcard in my Vibrant then it is R/W and no issues, I even ran fix permissions while in the Vibrant. I can even mount it on my PC, but I can't delete anything, even though Windows thinks it deleted it. I put the SDcard from my vibrant in my G2x no issues, R/W as it should be. And yes I did run fix permissions from recovery, no luck. sidenote, reseated card, pulled battery prayed, and then cursed... Also, I can copy data to my SDcard from Windows, such as a .zip, but while in recovery (Nflash vol up + power) I don;t see any of the added files, even zips for that matter. I do see the existing files. I know this is FAT32, but clearly something is amiss. I can't even format the card in my phone. Don;t have a card reader for the PC. I'm sure there has to be some simple command to set the correct permisions. I did search this fourm but didn;t find anything. I'd appreciate any insight and thank you in advance
Yeah I could format it in Windows via disk management, but was really hoping for a less painful method. Thank you for the suggestion phburks
Okay so windows says it's formatted, I put it back in all the data is still there. Put it in the Vibrant, formatted it, yet data still there and no errors...
and Camera now says "sdcard no exist" and reverts to phone memory....
Dunno about permissions but I'd just backup everything from the card and then format it.
G2X CM7
Yea that was a no go in the end. Anyone have any suggestions? I cannot make any changes to the data on the card add/delete/format...
I was using XXKPQ Gingerbread. Soon my phone started restarting and giving errors.
When I use ODIN I can put new files in to system folders. I installed XXKPE and clockworkmod, then I used adb remount, adb shell to delete everything under data/data, data/app, sdcard, sd-ext. When I do ls it said folders were empty but after restart everything came back!
Is there a way to mount a file system as a volatile memory? It accepts all the changes I say but it reverts back when unmounted and remounted. I thought it might be permission problem but fix_permissions script does not solve it. Also I heard 0 available memory bugs in the forums but my case is not that either.
On recovery menu, I used clockworkmod options to mount the data folder, I erased everything in it via adb shell, and without restarting I unmounted and mounted again using CWM, the files were there again in adb shell!
Since there are files under data/data and data/app folders, I get crashes of those applications all the time when I try to use the phone. If I install the same application from market it works fine but after restart it reverts back to crashing.
snlzkn said:
I was using XXKPQ Gingerbread. Soon my phone started restarting and giving errors.
When I use ODIN I can put new files in to system folders. I installed XXKPE and clockworkmod, then I used adb remount, adb shell to delete everything under data/data, data/app, sdcard, sd-ext. When I do ls it said folders were empty but after restart everything came back!
Is there a way to mount a file system as a volatile memory? It accepts all the changes I say but it reverts back when unmounted and remounted. I thought it might be permission problem but fix_permissions script does not solve it. Also I heard 0 available memory bugs in the forums but my case is not that either.
On recovery menu, I used clockworkmod options to mount the data folder, I erased everything in it via adb shell, and without restarting I unmounted and mounted again using CWM, the files were there again in adb shell!
Since there are files under data/data and data/app folders, I get crashes of those applications all the time when I try to use the phone. If I install the same application from market it works fine but after restart it reverts back to crashing.
Click to expand...
Click to collapse
Exists even after xxkpe + pit flash?
Try converting to ext4 and formatting and then flash xxkpe + pit.
Having read many such issues now, it seems its MoBo issue. Search around a bit. From what i have read, probably service center's the only one who would be able to help you now.
Try VurrutRom , when you install it the rom exchange the internal sd with the external sd.
you will see that your /data folder is now in the external sd. I hope this fix your problem.
@ggclanlord: This phone had motherboard issues before but this looks more like a protection to me. No matter which rom I install the applications and their settings just stay there. I might try ext4 later as well.
reivaj20 said:
Try VurrutRom , when you install it the rom exchange the internal sd with the external sd.
you will see that your /data folder is now in the external sd. I hope this fix your problem.
Click to expand...
Click to collapse
How do I change the internal sd with external sd? I have found this but it does not say it needs to be Vurrut. Is it somehow easier with Vurrut?
http://forum.xda-developers.com/showthread.php?t=1088474
First of all, why are you trying to clear any partition manually ?
Second, /data is a separate partition altogether neither on internal sd nor external.
Flash a full xxkpe with pit and re-partitioned checked. Then flash CF-root. Your phone should return to normal.
Generally you should not need to manually format partition ever but in case you need there are options under Advanced in CWM.
Hope it helps!
Good luck !
Not sure how this happened. In the root directory the folder for sdcard is now a file. This is also true in the /mnt dir. In the storage directory, i can access my sdcard files through sdcard0. Also now my signature says epad instead of whatever it said before. Ive tried to restore and reflash. No joy. Every app that needs the sd crashes including checking storage in the settings.
Any ideas?
Sent from my EPAD using xda premium
This has happened to me also. I installed rayman33's JB build #2, and i should have looked at the zip before i did as it seems theres a kernelblob in there, and while digging it seems that only /storage/sdcard0/ is mounted now instead of /sdcard/. I went back to a revolver nandroid after i tried out the JB rom and now twrp sees /sdcard/ but theres nothing in it. I have a feeling that whatever was in the blob changed the mount point for /data/media to /storage/sdcard0, and i can not for the life of me remember how to change it back.
Looking at /sdcard/ in root explorer shows that it has a link to /storage/sdcard0/, but it does us no good when its not mounted.
Seems like the easiest way is to push an old kernelblob that resembles what our original configs were, but its been so long since i've done that on my transformer that i've forgotten how.
HM, i used superwipe lite to preserve /data/media/, which is where the content was anyway, and reflashed revolver and it seems to have worked.
I've looked through the big development thread and haven't found a clear answer but has anyone found an app to sd solution that works?
This stupid SdCard / ExtSdCard arrangement is making me pull my hair out. I just realized my titanium backups weren't really backups since they were being stored on my internal memory.
I managed to change my backup folder and free up some space by moving all my backups to the SD card, but for some reason I cannot move apps to SD through Titanium or any other app I've tried.
Does anyone know how to do this? Is there a setting in titanium I need to change or is this just something we have to deal with forever short of flashing a custom rom?
SDCARD binary
Galahad_Knight said:
I've looked through the big development thread and haven't found a clear answer but has anyone found an app to sd solution that works?
This stupid SdCard / ExtSdCard arrangement is making me pull my hair out. I just realized my titanium backups weren't really backups since they were being stored on my internal memory.
I managed to change my backup folder and free up some space by moving all my backups to the SD card, but for some reason I cannot move apps to SD through Titanium or any other app I've tried.
Does anyone know how to do this? Is there a setting in titanium I need to change or is this just something we have to deal with forever short of flashing a custom rom?
Click to expand...
Click to collapse
I've found the real problem, but not the solution.
My Relay runs ICS. It is rooted, and you have to root to even touch any of this. The phone has a binary, /system/bin/sdcard that controls the internal memory and your SDcard. now, I have found that if you are rooted, you can chmod this binary (or use rooted ES File explorer to remove all executable properties) so that it can no longer run, then reboot. then you can run, as superuser "mount -o rw,bind /mnt/extSdCard /mnt/sdcard"
Seems great... Except vfat doesn't like to be bound in such a fashion, and you quickly lose write access and it starts mangling your files.
vfat just doesn't seem to work for us in this case. I've changed mine back, and reformatted my SDcard to be NTFS and mounted with paragon NTFS/HFS, which has completely stabilized my filesystem. only problem is, I can't get this to mount -o bind worth a damn.
I'm toying with the idea of reformatting my SDCard part vfat and either part NTFS or EXT4. maybe I get get the phone to natively recognize ext4 for the sdcard (even if I have to create a script myself)
keypoints I've found in this process:
1. the sdcard binary only allows access to 1023 files at once on either the SDcard, or the memory block it is using as the SDcard. too many pictures in your gallery? so sorry... can't load them all.
2. the physical device for your sdcard is /dev/block/mmcblk1. the partitions are mmcblk1p* (starting with 1)
3. the phone will not allow the sdcard binary to be killed manually. removing the executable permission and then rebooting the phone seems to be the only way to get it to stop.
4. vfat is prone to errors, and android seems to love screwing with the card. getting off vfat seems to be crucial to this process.
As you've gotten no other replies, and this is a gigantic concern for me as well, I'm going to keep working on this myself, in the hopes that I can get the phone to actually use the SDcard the way we hope it can be used.
I've been searching both this forum and the net generally and not found an answer to my specific problem so I'm hoping someone can help.
I'm trying to swap out my ROM, I'm currently running CM 11 nightly but I'm getting endless FCs with apps so thought I'd try something different.
When I try to run the nandroid backup with TWRP v2.7.0.1 the backup fails every time with the error E: unable to mount '/sd-ext'
Can anyone advise? Thanks
tht looks like external sd card.
Try changing location for your backup to internal memory or make sure you got SD card plugged in to SD slot.
you may also try command on terminal emulator (or via adb shell):
ln -s /storage/emulated/0/ /sd-ext/
it will create symbolic link named sd-ext in root of your system and it will point to internal storage (if I am not mistaken, from now on it should not matter if you select internal or external storage as target for your backup - it will end up as internal anyways)
Sent from my TF300T using XDA Free mobile app
Thanks, the backup was to be created on the internal SD card, but you are right it is almost certainly a problem with the external card. I'm unable to mount either the dock SD or micro SD cards in TWRP - the options are just greyed out and can't be selected.
I can't get either card to mount when I boot to system ether I have noticed. I've tried formatting them as FAT32, EXFAT and NTFS and no dice so I'm wondering if this is a KK issue - they both worked flawlessly when I was running PA and Omnirom JB ROMs.
I've managed to find a workaround - I've flashed CWM and have been able to do a nandroid backup with that - but I still can't mount either the micro SD or dock SD cards with CWM or in system when I flashed KatKISS ROM - and of course now I can't use any old TWRP nandroids I have from JB ROMs without reflashing TWRP. I'd also rather be running TWRP ultimately if I can so it would be good to get to the bottom of what is causing this issue.
Not quite sure what the command line you suggested does, but I'm guessing it won't be useful with the problem as it stands now?
sorry for late reply as I was out of internet lately.
that command creates /sd-ext/ folder that acts similar to shortcut to intertnal sdcard
any call for /sd-ext (for example: cd /sd-ext) will end up on internal sdcard.
That wont help with accessing your external sdcard (as this was main issue here) - it would merely fool installer to 'think' it is working on external sd while it was still on internal.
Sent from my TF300T using XDA Free mobile app
Thanks for your help. I've had endless troubles which ultimately ended in a hard brick during a failed flash of the stock ROM. I'm waiting for a replacement motherboard - something wasn't right with the old board anyway, it doesn't seem that it was just ROM issue. Hopefully when it comes I'll find that it wasn't a hardware issue associated with the SD cards as well.