Related
Firstly, I am running Valhalla Final 2.3.6 ("Happy Holidays") and using the KI3 Kernel. I'm almost Positive my issue is not related to the ROM or kernel.
A couple of weeks ago I was attempting to get Link2SD app to work properly (it never has but I kept trying every few weeks thinking Link2SD app would get updated and it would work) on my EXTERNAL Sdcard's 2nd EXT4 patition. I ended up with a soft bricked phone.
And my Sdcard appeared to be wiped. I restored the backup of my EXTERNAL Sdcard to my Sdcard (Internal).
Prior to restoring the backup of my EXTERNAL to Internal I used to have a "Long" menu list in Recovery. That List included options like
external
external/sd
tapatalk
tapatalk/download
They aren't listed anymore.
This is what my Menu looks like in Recovery (CWM Voodoo Lagfix Recovery v3.0.2.8.) now;
Android/
CameraZOOM/
DCMI/
LOST.DIR/
Removable Disk/ Removable Disk/ Was NEVER an option for me.
SpeedSoftware/
SupertaskManager/
TunnyBrowser/
Voodoo/
albumthumbs/
bluetooth/
bugreports/
clockworkmod/
data/
gameloft/
handcent/iTagCache/
launcherpro_backup/
music/
openfeint/
tapatalkxdapre_download/
and then my ROMS and Kernels Boot Anamation ect.
My Sdcard NEVER looked like this before my restoring of EXTERNAL to internal.
HOW do I fix this?? I've been searching for 2 weeks and haven't found anyone with a problem like this or solution... my phone works properly but I know this is not the way it should be.. I NEVER had a Removable Disk option before.
Any Help/Insight on this issue will be Greatly Appreciated and Thanked.
Jerry D said:
Firstly, I am running Valhalla Final 2.3.6 ("Happy Holidays") and using the KI3 Kernel. I'm almost Positive my issue is not related to the ROM or kernel.
A couple of weeks ago I was attempting to get Link2SD app to work properly (it never has but I kept trying every few weeks thinking Link2SD app would get updated and it would work) on my EXTERNAL Sdcard's 2nd EXT4 patition. I ended up with a soft bricked phone.
And my Sdcard appeared to be wiped. I restored the backup of my EXTERNAL Sdcard to my Sdcard (Internal).
Prior to restoring the backup of my EXTERNAL to Internal I used to have a "Long" menu list in Recovery. That List included options like
external
external/sd
tapatalk
tapatalk/download
They aren't listed anymore.
This is what my Menu looks like in Recovery (CWM Voodoo Lagfix Recovery v3.0.2.8.) now;
Android/
CameraZOOM/
DCMI/
LOST.DIR/
Removable Disk/ Removable Disk/ Was NEVER an option for me.
SpeedSoftware/
SupertaskManager/
TunnyBrowser/
Voodoo/
albumthumbs/
bluetooth/
bugreports/
clockworkmod/
data/
gameloft/
handcent/iTagCache/
launcherpro_backup/
music/
openfeint/
tapatalkxdapre_download/
and then my ROMS and Kernels Boot Anamation ect.
My Sdcard NEVER looked like this before my restoring of EXTERNAL to internal.
HOW do I fix this?? I've been searching for 2 weeks and haven't found anyone with a problem like this or solution... my phone works properly but I know this is not the way it should be.. I NEVER had a Removable Disk option before.
Any Help/Insight on this issue will be Greatly Appreciated and Thanked.
Click to expand...
Click to collapse
I see nobody has responded to you... but I do not see a problem. Maybe more explanation of your concerns.
The after restore list looks similar to mine. It is showing you the contents of your sdcard (folders & files).
EDIT: Not sure if you are aware of this thread: [GUIDE] Link2sd setup and installation
Did you set both partitions to primary? Don't format to Ext4, just use FAT 32.
lumin30 said:
I see nobody has responded to you... but I do not see a problem. Maybe more explanation of your concerns.
The after restore list looks similar to mine. It is showing you the contents of your sdcard (folders & files).
EDIT: Not sure if you are aware of this thread: [GUIDE] Link2sd setup and installation
Click to expand...
Click to collapse
Thanks for your reply..
My major concern was that after I dragged, dropped and restored my sdcard backup my menu list in Voodoo Recovery looked much different than it had ever looked before.
Specifically The Removable Disk option (I had NEVER had that option before).
Also. I no longer had external/ or external sdcard/ in my options list.
I thought I had dropped my EXTERNAL SD backup into my INTERNAL sdcard. But you say mine looks similar to your's so I guess I'm ok.. it was very disconcerting to see a much different Recovery Menu than the one I had been seeing for a year.
I had used an Excellent Guide by desexton to get an EXT4 partition on my External sdcard and it worked Flawlessly on Froyo and was hoping to have it work the same way on Gingerbread.. Other members have also been having issues with an EXT4 Partition (External sdcard) on Gingerbread.
The Guide you posted says to make the Partition EXT3. I am going to look into the Guide you posted tonight after work.
Thank you for your reply. I feel much better now that someone has replied that their menu looks like mine.
Have a Great Day!
Tested by me on the Samsung Galaxy Exhibit only. (I'm told it works on the Galaxy W). If your device's /system/etc/vold.fstab file matches the attached original Galaxy Exhibit fstab file, it may work for you as well. Note: This app is not compatible with CyanogenMod. Root is required.
A common complaint about some Samsung Gingerbread phones is the fact that they mount the relatively small internal sd memory as /mnt/sdcard and this memory is treated as the phone's primary removable storage by some apps, ignoring the "real" removable sd card that Samsung refers to as "/mnt/sdcard/external_sd".
This simple gui allows you to swap the two so your larger "external sd" is mounted as "/mnt/sdcard/" and the smaller sd internal memory is mounted as "/mnt/sdcard/external_sd".
This is done by changing a file called vold.fstab in your phone's /etc folder. The original device vold.fstab file is backed up to /etc/vold.fstab.backup when this app first runs. Your data on /mnt/sdcard and /mnt/sdcard/external_sd is not touched in any way whatsoever. Root is required. Easy install: copy the apk file to your SD card and open with a file manager.
Please nandroid backup before testing!
If you get "Unknown Error, Contact Developer" you are more than likely not properly rooted! This app requires Superuser and Busybox to properly function!
Please note that if you've already moved existing apps to SD or existing apps have placed support files on SD, swapping mount points is not a good idea. Uninstall these apps, then reinstall after swapping.
jocala said:
Tested on the Samsung Galaxy Exhibit only. If your device's /system/etc/vold.fstab file matches the attached fstab file, it may work for you as well.
Please nandroid backup before testing!
Click to expand...
Click to collapse
So has anyone had success using this on the Exhibit II/4G or is it really just for the older Exhibit or am I just mis-reading the title?
I'd like to make the switch since the "internal" sd situation is rather silly and I just picked up a new SDHC card for my phone.
so the app is for swapping
and wt abt the txt ??? is it the original or the custom for swapping ??????
Works on any rom?
Sent from my GT-I8150 using xda premium
willynatedgreat said:
So has anyone had success using this on the Exhibit II/4G or is it really just for the older Exhibit or am I just mis-reading the title?
I'd like to make the switch since the "internal" sd situation is rather silly and I just picked up a new SDHC card for my phone.
Click to expand...
Click to collapse
The Galaxy Exhibit 4G was formerly known as the Exhibit II 4G
mosta_9741 said:
so the app is for swapping
and wt abt the txt ??? is it the original or the custom for swapping ??????
Click to expand...
Click to collapse
The fstab.txt is the original from the Galaxy Exhibit. It's attached so you can compare it to the /system/etc/vold.fstab on your phone. If the two match, this app may work for you.
Karmalot said:
Works on any rom?
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
So far.
Ok, a question as I learn more and more about the Galaxy Exhibit.
I am testing one, have some time to return if the coverage is not what I need, so I have installed my apps from my other phone, and just moved the SD card over, since it had some zips and apks that I wanted.
Since some of the directories exist already and are used by apps, while others have been recreated on the internal sd of the phone. My thought was to install the swapsd apk, immediately physically move all files from the internal sd to the actual sd card by activating the USB connection. Then disable USB, the swap is active, the media scanner will run, and the phone should see everything on /sdcard and the /ext_sdcard will be clean, except for what I left in the /usb_storage directory.
I tried mounting in recovery under mounts, mount usb storage, but it can only see one virtual drive and not both, whereas activating from the phone, both show.
Is that correct, or am I missing something? And obviously, in recovery, the partitions stay they same since the script is not running.
Pkt_Lnt said:
Ok, a question as I learn more and more about the Galaxy Exhibit.
I am testing one, have some time to return if the coverage is not what I need, so I have installed my apps from my other phone, and just moved the SD card over, since it had some zips and apks that I wanted.
Since some of the directories exist already and are used by apps, while others have been recreated on the internal sd of the phone. My thought was to install the swapsd apk, immediately physically move all files from the internal sd to the actual sd card by activating the USB connection. Then disable USB, the swap is active, the media scanner will run, and the phone should see everything on /sdcard and the /ext_sdcard will be clean, except for what I left in the /usb_storage directory.
I tried mounting in recovery under mounts, mount usb storage, but it can only see one virtual drive and not both, whereas activating from the phone, both show.
Is that correct, or am I missing something? And obviously, in recovery, the partitions stay they same since the script is not running.
Click to expand...
Click to collapse
Samsung's stock recovery only sees the internal storage, not removable. ClockworkMod sees both. You can get cwm here.
jocala said:
Samsung's stock recovery only sees the internal storage, not removable. ClockworkMod sees both. You can get cwm here.
Click to expand...
Click to collapse
That is from within CWM from that link, maybe my old XP laptop is playing games. Is that implying that I should move files in recovery?
I also find a swapsd01.zip and a swapsd.apk, same, just different application method?
sd/swap beta
hi jocala ,was wondering if you could fully explain how to do the swpp sd in full ?
thanks
sean
Pkt_Lnt said:
That is from within CWM from that link, maybe my old XP laptop is playing games. Is that implying that I should move files in recovery?
I also find a swapsd01.zip and a swapsd.apk, same, just different application method?
Click to expand...
Click to collapse
The swapsd.apk in this thread is the app. Disregard any links to zips, they are outdated.
roto rooter said:
hi jocala ,was wondering if you could fully explain how to do the swpp sd in full ?
thanks
sean
Click to expand...
Click to collapse
I've attached a screenshot to the OP, hopefully that will help. It's pretty simple:
Root is required. Run the app, you'll see four buttons, Help, Default, Swap, Reboot.
To swap sd and external_sd press Swap.
To return to default, press Default.
Once you press either of the buttons above, press Reboot.
For instructions, press Help.
Pkt_Lnt said:
That is from within CWM from that link, maybe my old XP laptop is playing games. Is that implying that I should move files in recovery?
Click to expand...
Click to collapse
No. I misunderstood your post. To mount your /sdcard (internal) in cwm mount /sdcard. To mount your removable sd do mount /emmc.
jocala said:
No. I misunderstood your post. To mount your /sdcard (internal) in cwm mount /sdcard. To mount your removable sd do mount /emmc.
Click to expand...
Click to collapse
Well, I got it done. I had to do it a little different, more lengthy, more secure. Backed up both partitions to my computer. Activated swapsd, rebooted to recovery, but could not mount both simultaneously. So I mounted the new /sdcard that is removable and moved what was backed up on the computer from the previous internal card to it. Rebooted and then cleaned up everything for duplicates. Thanks for the help again.
Pkt_Lnt said:
Well, I got it done. I had to do it a little different, more lengthy, more secure. Backed up both partitions to my computer. Activated swapsd, rebooted to recovery, but could not mount both simultaneously. So I mounted the new /sdcard that is removable and moved what was backed up on the computer from the previous internal card to it. Rebooted and then cleaned up everything for duplicates. Thanks for the help again.
Click to expand...
Click to collapse
Glad it worked out for you. Good luck with your Galaxy Exhibit
jocala said:
Tested by me on the Samsung Galaxy Exhibit only. (I'm told it works on the Galaxy W). If your device's /system/etc/vold.fstab file matches the attached original Galaxy Exhibit fstab file, it may work for you as well.
A common complaint about some Samsung Gingerbread phones is the fact that they mount the relatively small internal sd memory as /mnt/sdcard and this memory is treated as the phone's primary removable storage by some apps, ignoring the "real" removable sd card that Samsung refers to as "/mnt/sdcard/external_sd".
This simple gui allows you to swap the two so your larger "external sd" is mounted as "/mnt/sdcard/" and the smaller sd internal memory is mounted as "/mnt/sdcard/external_sd".
This is done by changing a file called vold.fstab in your phone's /etc folder. The original device vold.fstab file is backed up to /etc/vold.fstab.backup when this app first runs. Your data on /mnt/sdcard and /mnt/sdcard/external_sd is not touched in any way whatsoever. Root is required.
Please nandroid backup before testing!
Click to expand...
Click to collapse
How to change the file?
Many thanks
NOLAchick said:
How to change the file?
Many thanks
Click to expand...
Click to collapse
Install the apk in the OP, and choose the swap button, then the reboot button. Sorry to be so technical..........
Pkt_Lnt said:
Install the apk in the OP, and choose the swap button, then the reboot button. Sorry to be so technical..........
Click to expand...
Click to collapse
That's the big question....for us noobies
Tanks though...
NOLAchick said:
That's the big question....for us noobies
Tanks though...
Click to expand...
Click to collapse
Copy the file to your SD card. Open it in your file manager.
Problem when I reboot my phone the internal SD is not available only the external micro-SD. I remove the micro-SD and then I can see my internal SD. I am beginning to think my Infuse is on it's last leg. Good thing I can upgrade on 1st January.
I have tried Wipe Cache Partition and Advanced/Wipe Dalvik Cache. No help. This is the second time, thought I had it fixed by returning to stock then back to CM10 4.2 all was well then I saw a post about the new camera that I didn't have yet so I flashed it. Now I am back to SD problem.
If anyone has an idea what is causing this, other than me. I would greatly appreciate it.
Does anyone have a suggestion on how to fix or advise on new phone to get?
Thank you!
swub1
Here is my boot.log contents.
Wed Dec 5 00:35:21 GMT 2012
umount: can't umount /sdcard: Invalid argument
cpio: dev not created: newer or same age file exists
cpio: proc not created: newer or same age file exists
cpio: sys not created: newer or same age file exists
cpio: system not created: newer or same age file exists
1263 blocks
Wed Dec 5 00:35:21 GMT 2012
Also I noticed that the date time stamp on microSD says 31 Dec 69
The above is the same with it working or with it not so thats not the problem and it doesn't help to solve it.
I have found that as long as I don't have to restart my phone when it is working it will remain working. If I think I have a reason to reboot I must make sure I really want to do this.
As the work to get it straight involves remove micro-SD, wipe/format reinstall of ROM and GApps and then restore enough to edit build.prop for tweaking lockscreen powerdown install micro-SD then powerup to restore rest of the apps.
If anyone knows what might be causing this I would really appreciate it. Even if you could point me to the log file to look at that might give me a clue that would be very nice.
swub1
If it works with out microsd just don't use one. 14 gigs is plenty. Otherwise maybe format the microsd? Or try a full stock wipe and see if it all comes back.
Sent from my SGH-I997 using xda app-developers app
cpio I believe means copy in and out.
Since phone works without micro-sd and fails with it try a new micro sd or a different rom.
As for the date you mentioned, it is not unusual to find files with dates that are years in the past. Upgrade? If you are staying with AT&T pick 3-5 phones from their website that based on specs and price meet you needs and spend some hands on time with each. No one can make a better decision as to your next phone than you. Well, maybe bigjoe could...
USB Storage unmounts?
swub1 said:
Problem when I reboot my phone the internal SD is not available only the external micro-SD. I remove the micro-SD and then I can see my internal SD. I am beginning to think my Infuse is on it's last leg. Good thing I can upgrade on 1st January.
I have tried Wipe Cache Partition and Advanced/Wipe Dalvik Cache. No help. This is the second time, thought I had it fixed by returning to stock then back to CM10 4.2 all was well then I saw a post about the new camera that I didn't have yet so I flashed it. Now I am back to SD problem.
If anyone has an idea what is causing this, other than me. I would greatly appreciate it.
Does anyone have a suggestion on how to fix or advise on new phone to get?
Thank you!
swub1
Click to expand...
Click to collapse
your post is the closest example to the SAME problem i am having so i will see if we are experiencing the same thing.
Im running Scott's 4.2.1 Unofficial CM10 - 12/02 build and ever since the 11/30 build, my internal ~14GB sdcard (called USB Storage when i look under system settings / storage) will not mount. the 2GB "internal" Storage and my 64GB External are always visible.
whats strange, is that when i reboot into recovery, i can still get all the data in this "sdcard" partition, it just will not mount when booted.
When i 1st boot from a new flash, its there, but after a reboot (and every reboot after that) it shows for a split-second, then disappears.
I come into this thread and seen it may have something to do with my External SD, i tried it removing the External SD, rebooted, and sure enough, it brought back my internal SD.
i shut down, re-inserted my External SD and powered up, and the USB Storage did NOT disappear but i cant leave well enough alone, so I rebooted 1 more time... POOF... USB Storage GONE....
How could the External SD have such an impact on the mounting of the Internal SD?
In Scott's thread he mentions that external (micro) sd should be removed before flashing the rom... don't know if that is the case, just sayin'.
Pony Express said:
In Scott's thread he mentions that external (micro) sd should be removed before flashing the rom... don't know if that is the case, just sayin'.
Click to expand...
Click to collapse
I have flashed & reflashed with and without, no change. I have reformatted the External SD, no change.
I think i have isolated the issue to the physical presense if the External SD, but this is not an issue with the 11/4 build. I just go back to 4.1.2 till the next release
Downgrading back to 11/04 now
I am downgrading to see if that fixes it will let you know. Did it work for you?
Some one had a point. How is it not available? No media can be seen. Or is it non existent in root explorer. PR under system settings> storage.
If its the first it might be a .nomedia file in the root directory.
Sent from my SGH-I997 using xda app-developers app
swub1 said:
I am downgrading to see if that fixes it will let you know. Did it work for you?
Click to expand...
Click to collapse
After downgrading back to 4.1.2 of CM10 my problem goes away. Another thing that I noticed is that the default APN's are now editable and I can delete them as well. While on 4.2 the only thing I could do was create a new one and set it to be the one in use. I guess part of the system is read only. Trying to save us from messing something up.
swub1
Pony Express said:
In Scott's thread he mentions that external (micro) sd should be removed before flashing the rom... don't know if that is the case, just sayin'.
Click to expand...
Click to collapse
When first told to remove external micro sd prior to flash I did just that. Later I supposed that I had nothing to loose so I tried leaving it in. Didn't see anything go wrong so I thought it was just a cover my a$$ thing.
Skwerl23 said:
Some one had a point. How is it not available? No media can be seen. Or is it non existent in root explorer. PR under system settings> storage.
If its the first it might be a .nomedia file in the root directory.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
Well for me, not available means not mounted & unmounable, the sdcard directory can be seen, but it empty through root explorer.
the "other way in" through Storage/Sdcard0 shows the dame, nothing, REMOVE the external SD, the internal SD (called USB Storage in settings/storage) Mounts in reboot. .nomedia is not the issue as when the External SD is present, i can play media (from the External SD, but the camera and other apps that rely on the internal SD for storage, can not function.
When i reboot into recovery, i can see and access all the files (typically where the flashable files reside when i drag them over from my PC) both internal and external, and when i reboot, the MOMENT the unlock screen appears i dash over to settings/storage and the internal drive appears, but collapses in a less then a second. (as unmounted)
swub1 said:
I am downgrading to see if that fixes it will let you know. Did it work for you?
Click to expand...
Click to collapse
yes, returning to the 11/4 (4.1.2) ROM I do not experience this issue.
I tried scott.hart.bti 4.2.1 12/11
Went up to try 4.2.1 12/11 - No difference - The only thing I was able to do in this one was delete unused APN and edit save new one.
Wish I knew how to program and spot the differences in the code somewhere. I'd really like to stay on 4.2.1 but without my micro-SD it seems like a waste.
I have not had issues with 12/12, thought I'd share my process: wipe data/factory, wipe cache, wipe dalvik (advanced), format system (mounts and storage), install ROM, wipe dalvik, install Scott's gapps, reboot. I also don't auto restore apps. There are still compatibility issues with some apps and 4.2
I am a programmer with experience working on Linux, brand new to Android. Recently I got my first Android phone, a Moto G 4G (XT1045) and installed CM11-20141009-NIGHTLY-peregrine on it. Today I bought a 32GB SDCard and formatted it to ext4 filesystem with AParted.
So it seems like cyanogenmod kernel should have SDCard fix for kitkat built in. Now I have a specific problem. I am trying to switch Titanium Backup to use sdcard1 as backup the location. So I have to browse to that folder.
My sdcard seems to be mounted in two places:
/mnt/media_rw/sdcard1
/storage/sdcard1
but both of them have problems. /storage/sdcard1 is a fuse mount and is read-only, even to root. I can browse there with TitaniumBackup, but then TitaniumBackup can't write any backups. /mnt/media_rw/sdcard1 is writable, and I can make directories on it from adb. But TitaniumBackup cannot browse inside of it, because media_rw is only accessible to user 1023(AID_MEDIA_RW). So I can't point TitaniumBackup to my sdcard!
How to fix this?
colinw1 said:
I am a programmer with experience working on Linux, brand new to Android. Recently I got my first Android phone, a Moto G 4G (XT1045) and installed CM11-20141009-NIGHTLY-peregrine on it. Today I bought a 32GB SDCard and formatted it to ext4 filesystem with AParted.
So it seems like cyanogenmod kernel should have SDCard fix for kitkat built in. Now I have a specific problem. I am trying to switch Titanium Backup to use sdcard1 as backup the location. So I have to browse to that folder.
My sdcard seems to be mounted in two places:
/mnt/media_rw/sdcard1
/storage/sdcard1
but both of them have problems. /storage/sdcard1 is a fuse mount and is read-only, even to root. I can browse there with TitaniumBackup, but then TitaniumBackup can't write any backups. /mnt/media_rw/sdcard1 is writable, and I can make directories on it from adb. But TitaniumBackup cannot browse inside of it, because media_rw is only accessible to user 1023(AID_MEDIA_RW). So I can't point TitaniumBackup to my sdcard!
How to fix this?
Click to expand...
Click to collapse
Hmmm. There have been problems with ext sd cards in cyanogenmod nightlies in the past and it is bound to happen. Not sure.
But try a CM11 snapshot instead of the nightlies as it is more stable with fewer bugs or wait for nightly updates which are very frequent.
Oh and make sure you do a nandroid backup before trying the CM11 Snapshot just in case.
https://download.cyanogenmod.org/?device=falcon&type=snapshot
Cheers!
CuckinFunt said:
Hmmm. There have been problems with ext sd cards in cyanogenmod nightlies in the past and it is bound to happen. Not sure.
But try a CM11 snapshot instead of the nightlies as it is more stable with fewer bugs or wait for nightly updates which are very frequent.
Oh and make sure you do a nandroid backup before trying the CM11 Snapshot just in case.
Cheers!
Click to expand...
Click to collapse
Thanks for the response - it seems it was not a problem with the ROM.
I've been working on this for about 8 hrs since the last post(!!), and I've made a lot of progress. I guess I'll just post it here in case someone comes across this question, though maybe not in scope of my original question.
It turns out my custom rom cyanogenmod (CM) has a fix for the KitKat modification built in. From the command line, as root, as long as I use /mnt/media_rw/sdcard1 to access the external secondary storage (my sdcard), everything works fine. Apps don't seem to mind that /storage/sdcard1 is mostly readonly.
I tested several non-rooted apps (e.g. doubleTwist), and noticed that they were able to write to various locations on my sdcard, always as user:group 1023:1023, ie MEDIA_RW. So the CM fix works. Note that you DO NOT have to install SDFix Apps or anything like that, or modify /etc/permissions/platform.xml. My original goal had been to get TitaniumBackup to start using my sdcard1. What I had to do was, as root, creat /mnt/media_rw/sdcard1/Backup/TitaniumBackup, set the owner and permissions correctly, and then I was able to switch to that directory in Titanium Backup (note, you have to use the Android system back button to go up a level when navigating the directories in Titanium Backup).
Also, It's important if you are using ext4 file system for your sdcard1, that it actually be ext4, not ext2, or CM doesn't recognize it. I used AParted to format it to ext4.
Finally, seems like FolderMount is great app for actually USING your sdcard1, once it's writable. I used FolderMount to redirect sdcard0/DCIM to sdcard1/DCIM, and now my camera is saving to the sdcard.
Sorry for maybe stating so much obvious info, but thought it might help some newcomer like myself - also seems like there's not a really good guide out there for users on how to work with the KitKat restrictions. Seems like with a Mod'd ROM like CM11, maybe nothing has changed(??) I am too new to Android to know the answer.
I have just bought an S7 (SM-G930F) after years and years with my trusty S3 9-9300...
I have rooted it and installed TWRP. Otherwise stock. Added most of my trusty apps and 64Gb SD Card.
I have an odd senario. I can access the card and I can andd and make changes to content, BUT there are some things I can not do, such as change ownership and permissions, but more importantly, I can not back up using Titanium Backup. TB says the card is fuill, but further investigation it won't allow it to store to the card. It says it is read only.
How do I fix this very annoying delema, any one, please?
jonners59 said:
I have just bought an S7 (SM-G930F) after years and years with my trusty S3 9-9300...
I have rooted it and installed TWRP. Otherwise stock. Added most of my trusty apps and 64Gb SD Card.
I have an odd senario. I can access the card and I can andd and make changes to content, BUT there are some things I can not do, such as change ownership and permissions, but more importantly, I can not back up using Titanium Backup. TB says the card is fuill, but further investigation it won't allow it to store to the card. It says it is read only.
How do I fix this very annoying delema, any one, please?
Click to expand...
Click to collapse
Hi
did you do all the steps posted in the TWRP page , specially Wipe Data?
Well I didn't follow those steps, but I did wipe the data partition just by chance.
What do you think ithe problem is and do you think it can be fixed without yet another rebuild - I have done so many to get the phone working.
jonners59 said:
Well I didn't follow those steps, but I did wipe the data partition just by chance.
What do you think ithe problem is and do you think it can be fixed without yet another rebuild - I have done so many to get the phone working.
Click to expand...
Click to collapse
Hi
I think that the data partition is still encrypted or not totally decripted that is why you do not have full access
TWRP Op step 10
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
You need to format data ( no just wipe) to get full access
I would try to install again TWRP ( all steps) but of course the problem is your data will be gone
OK, but how does that help the SDCard?????
I ask as I want to make absolutly sure as I now have no backup as I had deleted all the TB files.
jonners59 said:
OK, but how does that help the SDCard?????
I ask as I want to make absolutly sure as I now have no backup as I had deleted all the TB files.
Click to expand...
Click to collapse
Hi
I think I misunderstood you , you are talking about your external SD card not the internal,right ? if so , sorry my bad .
Maybe you had already but did you try to format it again or a different root explorer?
Not yet..... Odd thing is I am sure it worked for a while, but you know how these things are...
jonners59 said:
Not yet..... Odd thing is I am sure it worked for a while, but you know how these things are...
Click to expand...
Click to collapse
Check this
http://androidforums.com/threads/titanium-backup-pro-wont-use-external-sd.936278/
This app may help out
https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
* This app is likely only useful if you have a stock ROM. If you're running an aftermarket ROM like Cyanogenmod, then there is no reason to install this app (good aftermarket ROMs don't suffer from the problem that this app corrects).
Maybe....
---------- Post added at 02:55 PM ---------- Previous post was at 02:34 PM ----------
check also this
---------- Post added at 03:02 PM ---------- Previous post was at 02:55 PM ----------
And this
No, did not work. Wouldn't even recognise I had a card. So reformatted it and then wiped the phone, data, etc and factory reset. And just rebooted and installing, but still same problem. Also learnt how crap the Google and Samsung backups are. Just install the apps not anything useful. Hac'd with this crap phone.
jonners59 said:
No, did not work. Wouldn't even recognise I had a card. So reformatted it and then wiped the phone, data, etc and factory reset. And just rebooted and installing, but still same problem. Also learnt how crap the Google and Samsung backups are. Just install the apps not anything useful. Hac'd with this crap phone.
Click to expand...
Click to collapse
Sorry to hear that, did you formatted the card in FAT32 or exFat ?
MAX 404 said:
Sorry to hear that, did you formatted the card in FAT32 or exFat ?
Click to expand...
Click to collapse
FAT, which I assumed to be FAT32
jonners59 said:
FAT, which I assumed to be FAT32
Click to expand...
Click to collapse
Nope, FAT and FAT32 are different
http://portableapps.com/node/2149
jonners59 said:
FAT, which I assumed to be FAT32
Click to expand...
Click to collapse
Different card , formatted and still nothing......definitely odd , I am of ideas for now.......
The only option via TWRP were Fat and exFat. I went FAT. WIll it make a difference in this case?
Thanks Max 404
jonners59 said:
The only option via TWRP were Fat and exFat. I went FAT. WIll it make a difference in this case?
Thanks Max 404
Click to expand...
Click to collapse
Hi
Did you see @*Detection* comments , FAT is not the same as FAT32 , format the sd card in your PC and make sure you select FAT32
SO using my rooted file explorers, the issue seems to be that SDcard is owned by root and is rwxr-xr-x and I can't change it...
jonners59 said:
SO using my rooted file explorers, the issue seems to be that SDcard is owned by root and is rwxr-xr-x and I can't change it...
Click to expand...
Click to collapse
Take the card out of the phone, put it in a reader and connect to PC USB
Use something like minitool partition wizard free to delete all the partitions on the card, create a new primary partition, format to FAT32
Put it back in the phone and see how you get on
jonners59 said:
SO using my rooted file explorers, the issue seems to be that SDcard is owned by root and is rwxr-xr-x and I can't change it...
Click to expand...
Click to collapse
*Detection* said:
Take the card out of the phone, put it in a reader and connect to PC USB
Use something like minitool partition wizard free to delete all the partitions on the card, create a new primary partition, format to FAT32
Put it back in the phone and see how you get on
Click to expand...
Click to collapse
Hi
+1 @*Detection*
Also you are 100% you are root ? check with something like Root Checker to make sure
I had using gParted - I use Linux machines, still the same and I re rooted several times. and via other rooted S3s. Same.
I think that this is an ownership/group issue. The mount directory is "storage" owned by root, and it is interesting the two of my root file managers see it and the card as rwx-rwx-rwx and others as rwx-r_x-r__
and I suspect that apps like TB, parted (partition manager), Apps to SD, etc. are seeing the same. However, even with the file manager apps that see full access I can not change ownership or rw privileges..... REALLY ODD!!!!!!
SOLVED!!!! Hope this helps others.
In TWRP, Advanced, File Manager.... Find the SD Card, the change the permisions to 0015 This is the SDCard Group/ownership. It all works great now.
To tidy up I need to create a new mount point in / or storage and then a line in fstab. Know how to do that in Linux/Ubuntu, but not in Android even though it is one the same.
Any helps Please?????