Related
Im running Quantum V3, 4.4.1 KitKat on AT&T Samsung Galaxy S3. Last night I played around with phone, unmounted SD card cuz I needed to check my battery drainage. After I remounted it, ESfile explorer says that sdcard1 has "Invalid path". Even tho in settings > storage, it shows that there is sd card and how much space there's left on it...
I did a clean flash of the ROM before if that matters. I don't wanna reflash it and arrange all the apps all over again...
Also when I check the sd card through the app folders, aka in storage/sdcard1, it shows files and everything. What could be the issue that I cant get it to work?
Matt_GT said:
Im running Quantum V3, 4.4.1 KitKay on AT&T Samsung Galaxy S3. Last night I played around with phone, unmounted SD card cuz I needed to check my battery drainage. After I remounted it, ESfile explorer says that sdcard1 has "Invalid path". Even tho in settings > storage, it shows that there is sd card and how much space there's left on it...
I did a clean flash of the ROM before if that matters. I don't wanna reflash it and arrange all the apps all over again...
Also when I check the sd card through the app folders, aka in storage/sdcard1, it shows files and everything. What could be the issue that I cant get it to work?
Click to expand...
Click to collapse
Probably one of the bugs with the latest update by PwnCakes. Maybe you didn't unmount properly, or try formatting the sd card and plug it in again?
I have the same exact thing.
Sigh, at least I'm not alone xD
And I didn't try formatting, got 27 gig stuff on my SD card and unfortunately no space on HDD to copy all the stuff :/
Shame I ain't got enough posts to reply in PwnCakes thread...
I think it might actually be a bug within the rom itself OR ES file explorer. I had this bug since I think a few releases ago
I have the exact same problem. Under "device", i have two copies of extSDcard. I also get the "invalid path" when i tap on sdcard1. I guess i'll wait for a fix, as i don't want to uninstall ES File Explorer, and reinstall, just to lose everything.
grunt0300 said:
I have the exact same problem. Under "device", i have two copies of extSDcard. I also get the "invalid path" when i tap on sdcard1. I guess i'll wait for a fix, as i don't want to uninstall ES File Explorer, and reinstall, just to lose everything.
Click to expand...
Click to collapse
I will post my workaround for ES when I get to my computer. It will basically circumvent the error to make it usable. Just keep and eye on this post, I'll edit it in.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
xXshur1kenXx said:
I will post my workaround for ES when I get to my computer. It will basically circumvent the error to make it usable. Just keep and eye on this post, I'll edit it in.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Click to expand...
Click to collapse
Aight, nice to hear someone wants to help till it's solved!:victory:
Temporary ES File Explorer Workaround for SD Card and Ext SD Card
Sorry it took so long. Just got done finals and had to get the bus. Below is the settings that you guys can use to make it almost as if nothing was wrong with ES.
Set your directory settings for Home to the External SD Card
Change the default window settings to the following: Sdcard, Home, whatever else you want loaded AFTER these
This will make it so that the first loaded 'window' of ES is the device's internal memory. Then it will load the external SD card as the second 'window'. As long as you check it in the proper order, it will load just fine.
xXshur1kenXx said:
Sorry it took so long. Just got done finals and had to get the bus. Below is the settings that you guys can use to make it almost as if nothing was wrong with ES.
Set your directory settings for Home to the External SD Card
Change the default window settings to the following: Sdcard, Home, whatever else you want loaded AFTER these
This will make it so that the first loaded 'window' of ES is the device's internal memory. Then it will load the external SD card as the second 'window'. As long as you check it in the proper order, it will load just fine.
Click to expand...
Click to collapse
That does work indeed... Thanks!
Followed directions, and i get LAN with a blank page, then i still have to tap on the top of the app, and go into the directory to find sd card, and ext sd card(which used to be sd card1. What would happen if i wiped data on ES File Explorer, deleted the app, and then reinstalled it? Thanks for any help.
grunt0300 said:
Followed directions, and i get LAN with a blank page, then i still have to tap on the top of the app, and go into the directory to find sd card, and ext sd card(which used to be sd card1. What would happen if i wiped data on ES File Explorer, deleted the app, and then reinstalled it? Thanks for any help.
Click to expand...
Click to collapse
Idk how you got LAN. Uncheck all of the windows then select them in the order I provided. Also make sure home directory is set to your external SD card at whatever path it is. Also can you provide a screenshot?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
xXshur1kenXx said:
Idk how you got LAN. Uncheck all of the windows then select them in the order I provided. Also make sure home directory is set to your external SD card at whatever path it is. Also can you provide a screenshot?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Click to expand...
Click to collapse
O.K.,now. LAN was checked, in windows settings, but i didn't see it. If the problem is ES File Explorer, will it be fixed in the next upgrade? I've never had this problem with my other roms. Thanks for the help.:good:
grunt0300 said:
O.K.,now. LAN was checked, in windows settings, but i didn't see it. If the problem is ES File Explorer, will it be fixed in the next upgrade? I've never had this problem with my other roms. Thanks for the help.:good:
Click to expand...
Click to collapse
I'll be honest with you. I check play d store almost daily to see if there is anything new with ES. I don't know. It might be a problem with the selinux transition from 4.3 to 4.4. It could be a million things but I think its just some back end code for the file system. :/
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
xXshur1kenXx said:
I'll be honest with you. I check play d store almost daily to see if there is anything new with ES. I don't know. It might be a problem with the selinux transition from 4.3 to 4.4. It could be a million things but I think its just some back end code for the file system. :/
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Click to expand...
Click to collapse
Right, so in your opinion, wiping & uninstalling, then reinstalling would just bring back the same problem?
grunt0300 said:
Right, so in your opinion, wiping & uninstalling, then reinstalling would just bring back the same problem?
Click to expand...
Click to collapse
Yep, because I've done that many times
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
xXshur1kenXx said:
Yep, because I've done that many times
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Click to expand...
Click to collapse
Just found FX File Explorer. It works perfectly, and also has a "dark theme", which i like. There's a root access add-on with it, also for free, but it's telling me to grant it root access using my installed "SuperUser" app. How do i do that with that app? Thanks, again for all your help.:good:
grunt0300 said:
Just found FX File Explorer. It works perfectly, and also has a "dark theme", which i like. There's a root access add-on with it, also for free, but it's telling me to grant it root access using my installed "SuperUser" app. How do i do that with that app? Thanks, again for all your help.:good:
Click to expand...
Click to collapse
Super user should pop up a prompt if you're rooted. Also, I know the error that breaks ES but idk how to fix it myself. Is a problem with permissions.xml
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
xXshur1kenXx said:
Super user should pop up a prompt if you're rooted. Also, I know the error that breaks ES but idk how to fix it myself. Is a problem with permissions.xml
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
Click to expand...
Click to collapse
I get the prompt, but it keeps being denied by SU, however, it goes into Titanium Backup. I'm wondering if i really need root access. I don't think that i have it with ES File Explorer.
grunt0300 said:
I get the prompt, but it keeps being denied by SU, however, it goes into Titanium Backup. I'm wondering if i really need root access. I don't think that i have it with ES File Explorer.
Click to expand...
Click to collapse
You don't need it but you might want it lol.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
---------- Post added at 01:15 AM ---------- Previous post was at 01:09 AM ----------
@grunt0300 if you really want, I can take a look into the permission.xml. however, no way I am making the commits to my device at the moment. All I know (without looking up the exact wording) is that in permissions.xml is a line for read external storage and that line is set to media/mnt/sdcard instead of storage/sdcard1.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 4
I have rooted and have disabled most of the recommendations listed here: http://forum.xda-developers.com/galaxy-tab-s/help/debloating-t2805503
I now find myself unable to create a folder (using ES or ASTRO) in any directory?
Very confused
Did you try and search first before posting a new thread ?????
This is one of a number of similar posts with solution.
http://forum.xda-developers.com/showthread.php?t=2815237
Sent from my SM-N9005 using XDA Premium 4 mobile app
UpInTheAir said:
Did you try and search first before posting a new thread ?????
This is one of a number of similar posts with solution.
http://forum.xda-developers.com/showthread.php?t=2815237
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I don't think I was clear. This is not to my external sd card but to the actual storage on my device (or maybe that did happen for others)? I checked out that thread, downloaded the "SDFix: KitKat Writable MicroSD", rebooted and still does not work. I am attempting the wanam xposed fix but whenever I attempt to use the xposed installer, it can't extract (due too inability to write to disk). Is there a way to install xposed via odin?
Thank you for the response. I am new to rooting and Android in general, but I am trying!
lordnorth4 said:
Sorry I don't think I was clear. This is not to my external sd card but to the actual storage on my device (or maybe that did happen for others)?
Click to expand...
Click to collapse
Not sure on what your issue might be, but I just tried using ES File Explorer, and I could create a new folder in the SD0 (internal) directory, without issues. So perhaps try with another file manager like ES.
Freakstyler said:
Not sure on what your issue might be, but I just tried using ES File Explorer, and I could create a new folder in the SD0 (internal) directory, without issues. So perhaps try with another file manager like ES.
Click to expand...
Click to collapse
Okay update time. I attempted both Root Browser and ES File Explorer.. Root browser did the same thing as ASTRO, which was that after I attempted to create a folder/file clicked ok, the screen refreshed and viola- nothing. ES File Explorer did have the added benefit of apologizing saying: "Sorry, operation failed".
I attempted more drastic measures, as I am sure I was able to do this earlier on my device (through ASTRO). I backed up my current setup, and then restored the one I made directly after rooting. This had no apps disabled. Problem persisted. Restored to my current and problem still persisted.
I then attempted to use Samsung's "My Files" app, which was surprisingly capable of performing these operations. I don't know what options this leaves me. This is not just a problem with file browsers, as I was using AIDE and was incapable of creating a new project, so this is drastically affecting the use of my device. Does anyone have any suggestions?
EDIT
I have made sure ES File explorer has root permission, and yet it still will not create folder's/files. I have put in an sd card, and am able to write folders to that. A quick and uninformed internet search has lead me to believe that it is because the file system is inproperly mounted, but I have absolutely no idea if that is correct or how I caused that issue. I am further lost on how to go about fixing it.
Would a reflash using the original root method work?
Or perhaps a factory reset?
I just don't know enough.
END EDIT
Thanks for your replies and time, I really appreciate it.
same issue
lordnorth4 said:
Okay update time. I attempted both Root Browser and ES File Explorer.. Root browser did the same thing as ASTRO, which was that after I attempted to create a folder/file clicked ok, the screen refreshed and viola- nothing. ES File Explorer did have the added benefit of apologizing saying: "Sorry, operation failed".
I attempted more drastic measures, as I am sure I was able to do this earlier on my device (through ASTRO). I backed up my current setup, and then restored the one I made directly after rooting. This had no apps disabled. Problem persisted. Restored to my current and problem still persisted.
I then attempted to use Samsung's "My Files" app, which was surprisingly capable of performing these operations. I don't know what options this leaves me. This is not just a problem with file browsers, as I was using AIDE and was incapable of creating a new project, so this is drastically affecting the use of my device. Does anyone have any suggestions?
EDIT
I have made sure ES File explorer has root permission, and yet it still will not create folder's/files. I have put in an sd card, and am able to write folders to that. A quick and uninformed internet search has lead me to believe that it is because the file system is inproperly mounted, but I have absolutely no idea if that is correct or how I caused that issue. I am further lost on how to go about fixing it.
Would a reflash using the original root method work?
Or perhaps a factory reset?
I just don't know enough.
END EDIT
Thanks for your replies and time, I really appreciate it.
Click to expand...
Click to collapse
I have the same exact issue. I can add folders through the Samsung My Files; the ES File explorer gives me 'Sorry, operation failed' also. I have reformatted, and re-rooted, but same issue.
Im no expert mind you, but i had this exact same issue, pretty sure its a kernel issue, specifically i think selinux and its two modes passive and enforce.........first i tried an app on the store thats suppose to change this mode upon reboot, before i realised newly installed apps were now also having issue with internal storage........anyways, long story short, i checked out the lone kernel in the dev thread, paraphrasing, selinux disabled, or some such, and bingo bango, everythings back the way it was
If you have recovery, might be worth backing up and flashing kernel, see if that works, report if it does for the benifit of others that might find themselves with internal storage issues
Edit
T700/T705 version
http://forum.xda-developers.com/galaxy-tab-s/orig-development/kernel-skyhigh-tw-kernel-t2806563
"SELinux PERMISSIVE" - turns out kernel is permissive by default, not disabled
T800/T805 version
http://forum.xda-developers.com/gal...ent/kernel-skyhigh-tw-kernel-synapse-t2854933
Hopefully thats usefull
Yep. Just did a first TWRP backup and restored with my latest kernel flashed. No internal storage write issue. If you really want to know if it's SELinux or how I mount let me know and I can repack a stock kernel for private test. I do set the last line of my /sbin/SkyHigh.sh script as data rw, so probably that's it.
UpInTheAir said:
Yep. Just did a first TWRP backup and restored with my latest kernel flashed. No internal storage write issue. If you really want to know if it's SELinux or how I mount let me know and I can repack a stock kernel for private test. I do set the last line of my /sbin/SkyHigh.sh script as data rw, so probably that's it.
Click to expand...
Click to collapse
Did you have the internal issue aswell?
So we have two probable culprits, selinux or a line in a script
Can you flash kernel one ontop of the other without negatives, so lets say you put two test versions here, one with the script change but selinux enforce, and your latest kernel at the moment, anyone in the future with this issue, who is willing to help could flash the first one and confirm if fixed and thus hopefully identify the issue specifically as the data r/w or not
On another note
Although i was having internal issues in android itself at the time, my twrp recovery file manager had no problems deleting/moving files.....maybe that might narrow down the issue, i dont know
banderos101 said:
Did you have the internal issue aswell?
So we have two probable culprits, selinux or a line in a script
Can you flash kernel one ontop of the other without negatives, so lets say you put two test versions here, one with the script change but selinux enforce, and your latest kernel at the moment, anyone in the future with this issue, who is willing to help could flash the first one and confirm if fixed and thus hopefully identify the issue specifically as the data r/w or not
On another note
Although i was having internal issues in android itself at the time, my twrp recovery file manager had no problems deleting/moving files.....maybe that might narrow down the issue, i dont know
Click to expand...
Click to collapse
No, I've never had the issue as I've used my own kernel from just about day one Hence restoring with TWRP hadn't been a problem the one time I just used it.
I have posted a couple of times asking if someone wants to do the flashing, I don't have the motivation and time to do it.
I will however respond to a PM if someone wishes to flash a modified re-packed stock kernel to test. They'll need to supply the stock boot.img from the firmware version they are currently using. If all is good, we can then post the results.
Or in the meantime, user SkyHigh kernel
UpInTheAir said:
No, I've never had the issue as I've used my own kernel from just about day one Hence restoring with TWRP hadn't been a problem the one time I just used it.
I have posted a couple of times asking if someone wants to do the flashing, I don't have the motivation and time to do it.
I will however respond to a PM if someone wishes to flash a modified re-packed stock kernel to test. They'll need to supply the stock boot.img from the firmware version they are currently using. If all is good, we can then post the results.
Or in the meantime, user SkyHigh kernel
Click to expand...
Click to collapse
Thanks by the way, for your kernel, and its rescue of my device .........and not least of all, the work you've done with our devices:highfive:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
flhthemi said:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
Click to expand...
Click to collapse
No. You'll need to re-read the entire thread. Easy mistake.
The thread is about an issue with INTERNAL sdcard after TWRP recovery restore and a "solution".
flhthemi said:
So is this actually a bug or by design? Is it KK or Samsung's problem? Kinda stupid to lock us out of our own SD card but still allow us to install apps from unknown sources???
WTF?
Click to expand...
Click to collapse
Worked fine until i started rooting and flashing the recovery, pretty sure during that process something triggered this issue
UpInTheAir said:
No. You'll need to re-read the entire thread. Easy mistake.
The thread is about an issue with INTERNAL sdcard after TWRP recovery restore and a "solution".
Click to expand...
Click to collapse
Yup, first post in the Samsung threads and I messed up. Now I have to find a proper thread to get an answer....
Just for future reference
This issue affects both internal AND external storage, if you just have an external issue and no internal, its likely you have a different issue, likely the changes brought about by kitkat, where there are other solutions elsewhere.......thats not to say you cant try a kernal thats known to have selinux as permissive and r/w script change though, might actually be another solution to the kitkat/external card issue?i dont know
So to clarify, this issue involves the INTERNAL storage too, which the other issue doesnt
banderos101 said:
Just for future reference
This issue affects both internal AND external storage, if you just have an external issue and no internal, its likely you have a different issue, likely the changes brought about by kitkat, where there are other solutions elsewhere.......thats not to say you cant try a kernal thats known to have selinux as permissive and r/w script change though, might actually be another solution to the kitkat/external card issue?i dont know
So to clarify, this issue involves the INTERNAL storage too, which the other issue doesnt
Click to expand...
Click to collapse
This thread is about INTERNAL sdcard write issue after restoring TWRP backup. Current known solution: flash my kernel.
The EXTERNAL sdcard issue is brought about with the introduction of Android 4.4.2 (There are other dedicated threads on this). Current known solutions: flash a patched custom ROM, use one of the Play Store apps (root), or mod the relevant system folder yourself (root).
UpInTheAir said:
This thread is about INTERNAL sdcard write issue after restoring TWRP backup. Current known solution: flash my kernel.
The EXTERNAL sdcard issue is brought about with the introduction of Android 4.4.2 (There are other dedicated threads on this). Current known solutions: flash a patched custom ROM, use one of the Play Store apps (root), or mod the relevant system folder yourself (root).
Click to expand...
Click to collapse
Okay, i could have sworn that i was experiencing the same issue on the external, aswell as the internal, infact im certain, i remember trying the external fixes first, assuming i had the kitkat external storage issue, untill i noticed it was also happening to the internal storage.......this was the first and only thread i found concerning internal issues, maybe i had both issues, but then again, the kitkat fixes didnt fix the external issues, your kernel seemed to fix both, at least in my specific situation
Edit
Okay, i see maybe you were answering my question from a more knowledgeble perpective, it just seemed that whatever affected the internal, was also affecting the external, otherwise, wouldnt the sdfix and/or root file managers like es file explorer with a kitkat/sd workaround, worked, both of which i tried.......seems like whatever was affecting my internal was also affecting external..........one way to find out is if folks who find themselves with the internal issues could confirm if they also have external issues, and whether the external fixes work or not
Edit
Ive just come to realise the fact that i was having internal storage permission issues might have caused the external storage fixes not to function properly, and that maybe i did indeed have two seperate issues, and that whatever was affecting my internal storage was a different issue to the kitkat/external sd card issue, so maybe you are right in saying that this only fixes the internal storage issue, which in turn allowed the external storage fixes to work.........hopefully time will tell, and hopefully, some of that makes sense
Hey guys
Im running low on space in my phone so i decided to move my titanium backup folder to the external sd card. However, its says the folder is not writable. Any way I can solve this ? Im running 5.0 and have xposed installed
Solved: I flashed the ex sd card fix zip and it worked like a charm
Think you have to use the stock File Manager as Android doesn't allow direct writing to an external memory source
EddyOS said:
Think you have to use the stock File Manager as Android doesn't allow direct writing to an external memory source
Click to expand...
Click to collapse
Yes I am aware but I was wondering are there any root solutions currently available to fix this ?
Just root then apply the sd card fix. Job done.
Sent from my SM-T805 using XDA Free mobile app
It says that the system partition on stockhtc kernel is protected and hence the method will not work
You likely need S-OFF in that case?
Wait... Did you actually root the phone yet?
Darth said:
Wait... Did you actually root the phone yet?
Click to expand...
Click to collapse
Yup phones rooted. Its been checked with root checker and I am running titanium backup, xposed alpha, and automagic premium with it
Then I'm not sure, sorry.
Darth said:
Then I'm not sure, sorry.
Click to expand...
Click to collapse
Is there a way to manually remove the protection for the system partition and make it writable ? I have twrp recovery
xdaaccount123 said:
Is there a way to manually remove the protection for the system partition and make it writable ? I have twrp recovery
Click to expand...
Click to collapse
You're already rooted... That's not the issue.
But I'm not sure what is unfortunately.
Darth said:
You're already rooted... That's not the issue.
But I'm not sure what is unfortunately.
Click to expand...
Click to collapse
should I maybe run through the root process again ? Like reflash supersu ?
Sounds like you have root.
I think you're barking up the wrong tree here. Lol
Here's some things to try,
http://forum.xda-developers.com/htc-one-m8/help/lollipop-titanium-backup-extsd-error-t3009584
http://forum.xda-developers.com/htc-one-m8/help/lollipop-grant-access-to-sdcard-t3015672 (same as above I think)
http://forum.xda-developers.com/htc-one-m8/help/lollipop-blocking-writes-to-external-t2969254
See if anything there helps.
Darth said:
Here's some things to try,
http://forum.xda-developers.com/htc-one-m8/help/lollipop-titanium-backup-extsd-error-t3009584
http://forum.xda-developers.com/htc-one-m8/help/lollipop-grant-access-to-sdcard-t3015672 (same as above I think)
http://forum.xda-developers.com/htc-one-m8/help/lollipop-blocking-writes-to-external-t2969254
See if anything there helps.
Click to expand...
Click to collapse
Unfortunately ive already tried all of those :S
Ive found a really interesting thing though I dont know if its pertinent. When I edit the xml file, it doesnt save after reboot
EddyOS said:
Think you have to use the stock File Manager as Android doesn't allow direct writing to an external memory source
Click to expand...
Click to collapse
Sorry for the noob question, but could you explain that? With the stock File manager I can copy/move files to the external memory card. So is that file manager not part of Android or do you mean that apps are not allowed to write to the sd card? But the the stock camera can - all my photos are on sd card ...
xdaaccount123 said:
Ive found a really interesting thing though I dont know if its pertinent. When I edit the xml file, it doesnt save after reboot
Click to expand...
Click to collapse
try a custom kernel; stock kernel usually has /system write protection enabled so it won't allow changes to stick to the system partition
EDIT: or change the file while booted into custom recovery (ie pull the file, edit it, push it back, make sure permissions are correct)
---------- Post added at 06:51 PM ---------- Previous post was at 06:42 PM ----------
unifex_ said:
Sorry for the noob question, but could you explain that? With the stock File manager I can copy/move files to the external memory card. So is that file manager not part of Android or do you mean that apps are not allowed to write to the sd card? But the the stock camera can - all my photos are on sd card ...
Click to expand...
Click to collapse
IF (yes big if) i remember correctly, only system apps have [full] access to the sdcard, all user apps only have access to their respective directories.
feel free to correct me, havent been keeping up to date :angel:
nkk71 said:
try a custom kernel; stock kernel usually has /system write protection enabled so it won't allow changes to stick to the system partition
EDIT: or change the file while booted into custom recovery (ie pull the file, edit it, push it back, make sure permissions are correct)
Click to expand...
Click to collapse
I think I am going to do that. Can you recommend a custom kernel for flashing ? And I have no idea how to change the file while booted into custom recovery, could you please walk me through it if its not too much trouble ?
xdaaccount123 said:
I think I am going to do that. Can you recommend a custom kernel for flashing ? And I have no idea how to change the file while booted into custom recovery, could you please walk me through it if its not too much trouble ?
Click to expand...
Click to collapse
i'm still on KK, but have always used ElementalX (both on M7 and M8), but if you rather do it through TWRP, can you upload the xml for me, i'll change it and post instructions back on how to push it back in TWRP
Hi,
my H815 is freshly and happily rooted, and i wonder if i have to install SdFix or not.
Do we have to do this on Lillipop?
on Google Play, SdFix says "for kitkat" and don't mention Lollipop.
What do you think?
Thanx for answers
I had to use it for some apps, so I say YES. Lollipop has the same regulations for the external SD like KitKat, so the apps have the same problems.
misteurz said:
Hi,
my H815 is freshly and happily rooted, and i wonder if i have to install SdFix or not.
Do we have to do this on Lillipop?
on Google Play, SdFix says "for kitkat" and don't mention Lollipop.
What do you think?
Thanx for answers
Click to expand...
Click to collapse
I use it as well and it works - I can now save TB backup directly on my external SD :good:
clandes said:
I use it as well and it works - I can now save TB backup directly on my external SD :good:
Click to expand...
Click to collapse
+1
there was this thread some time ago by @TecknoFreak that explained how to fix that by editing the /system/etc/permissions/platform.xml file by hand, no need for an app http://forum.xda-developers.com/showthread.php?t=2524277. he posted this in another thread but i cant remember now where i saw it
having said that, i cant remember if i used TB saving my backups to external before or after i made the change to my xml using the steps from the thread but i am pretty sure it was before. also the LG camera can write to ext_sd so dont know for sure this is needed. plus i just did a reflash of @MicroMod777 xTreme rom so it reset that file and i can still write to my ext_sd with TB and camera
oops...i take back part of this, i just now noticed the notification i got from TB that said my backup failed cause i did not have enough space to write the backup to, but the camera still saves to external
so i must have done the xml edit before i did TB, either way, i dont think you need an app for this. sure it might make it easier, but editing the file is not too bad to tackle either
I downloaded SDFix from Google Play (pretty sure it's the same one I used when KitKat first came out) and it reported that the app wasn't necessary.
EU H815 rooted with the recently released Low Effort Exploit (and not by unlocking the bootloader via LG's Dev site).
TiBu was one of the first apps I installed after rooting earlier this week, and it never had a problem backing up to my ext. SD card.
Midnight_Rider said:
there was this thread some time ago by @TecknoFreak that explained how to fix that by editing the /system/etc/permissions/platform.xml file by hand, no need for an app http://forum.xda-developers.com/showthread.php?t=2524277. he posted this in another thread but i cant remember now where i saw it
having said that, i cant remember if i used TB saving my backups to external before or after i made the change to my xml using the steps from the thread but i am pretty sure it was before. also the LG camera can write to ext_sd so dont know for sure this is needed. plus i just did a reflash of @MicroMod777 xTreme rom so it reset that file and i can still write to my ext_sd with TB and camera
oops...i take back part of this, i just now noticed the notification i got from TB that said my backup failed cause i did not have enough space to write the backup to, but the camera still saves to external
so i must have done the xml edit before i did TB, either way, i dont think you need an app for this. sure it might make it easier, but editing the file is not too bad to tackle either
Click to expand...
Click to collapse
My edits should work just fine for TB backing up on external. I did the same edits to my H811 and works great. I was getting the same error as well and it got fixed after those edits that is just one line missing.
I rather change a line or 2 before installing an app to my phone but that is just me.
Specifically for TitaniumBackup, you just need to go to preferences and when selecting your backup folder, change the storage provider to DocumentProvider storage (Click above the DETECT button) and then navigate to your folder.
Works fine without any fixes.
Charsher47 said:
Specifically for TitaniumBackup, you just need to go to preferences and when selecting your backup folder, change the storage provider to DocumentProvider storage (Click above the DETECT button) and then navigate to your folder.
Works fine without any fixes.
Click to expand...
Click to collapse
Don't get the option to 'protect' backups though if you go this route. Only if you use the default setting with edited platform.xml file.
TecknoFreak said:
My edits should work just fine for TB backing up on external. I did the same edits to my H811 and works great. I was getting the same error as well and it got fixed after those edits that is just one line missing.
I rather change a line or 2 before installing an app to my phone but that is just me.
Click to expand...
Click to collapse
Same here, and this worked perfectly fine on my H815 (SEA version). Now I can actually let GoneMadMusicPlayer edit tags in my music collection.
Thanks :good:
I seem to have been at this for hours now. I finally got Xposed framework on my Tab S and Note 4 and decided to try Marshmallow SD fix
https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263/page29
and then EXT SD fix
https://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
In each case going to Titanium backup it just doesn't work - I get the same old "Folder is not writable" message for anything on the SD card.
Since many people are having success - I'm assuming this is because of the Samsung version of Xposed framework ?
I don't know but nothing I do seems to work.
Any suggestions / advice - has anyone got this to work on their tab s or note 4?
louiscar said:
I seem to have been at this for hours now. I finally got Xposed framework on my Tab S and Note 4 and decided to try Marshmallow SD fix
https://forum.xda-developers.com/xposed/modules/xposed-marshmallow-sd-fix-write-t3403263/page29
and then EXT SD fix
https://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
In each case going to Titanium backup it just doesn't work - I get the same old "Folder is not writable" message for anything on the SD card.
Since many people are having success - I'm assuming this is because of the Samsung version of Xposed framework ?
I don't know but nothing I do seems to work.
Any suggestions / advice - has anyone got this to work on their tab s or note 4?
Click to expand...
Click to collapse
If it's lollipop you need the sdcard fix. If it's mm you just need to allow write permissions to the app.
ashyx said:
If it's lollipop you need the sdcard fix. If it's mm you just need to allow write permissions to the app.
Click to expand...
Click to collapse
I'm not sure I understand that. Are you talking about extsd or marshmallow fix ? Also there are no permissions to set other than the ones shown. For Titanium those are all set to on. Ie. Storage.
Is there a specific 'write' permission elsewhere that I've missed?
louiscar said:
I'm not sure I understand that. Are you talking about extsd or marshmallow fix ? Also there are no permissions to set other than the ones shown. For Titanium those are all set to on. Ie. Storage.
Is there a specific 'write' permission elsewhere that I've missed?
Click to expand...
Click to collapse
Any app that wishes to write to the external storage should show a dialog requesting permission to the ext sd after that it will have full write access.
Any app that doesn't isn't mm compatible.
Which folder path are you trying to use?
ashyx said:
Any app that wishes to write to the external storage should show a dialog requesting permission to the ext sd after that it will have full write access.
Any app that doesn't isn't mm compatible.
Which folder path are you trying to use?
Click to expand...
Click to collapse
The Titanium problem is fairly common. if all apps need to be was mm compatible then we wouldn't need a fix for the SD cards I would have thought.
But coming to Titanium itself I can select the old folder with is exsdcard/titaniumbackup but Titanium will tell me this has no write access but I can use it to read from and restore.
There is no location that Titanium will use or see on the extsdcard. What one has to do to is to copy the contents of your backup folder to the internal card then select that as the backup folder in Tba. Then you have elect to change the backup folder but choosing DocumentProvider storage. At this point you then have to create a folder - an existing folder is no good. Once created it will copy the contents of the internal folder to the extsdcard. Apart from the fact that this 'workaround' is much slower it is also inconvenient and any kind of change for whatever reason in the backup folder means that you can't just switch to the old one you have to go through the whole creation process.
As far as I am concerned this is why I wanted an SD card fix but I also understand to some point your view and it does make some sense. However it is confusing. When this nightmare started with Kitkat I understood that apps were allowed their own folder but couldn't affect or write to other folders. Also they were media folders only. This as I remember also affected file managers which then couldn't do their intended job.
With MM and without any fix Solid explorer can and does have full access to the sd card and can write in any folder from what I can see. Other apps seem to possibly access with documentprovider permissions - I'm not sure but many appear to have no problems but the pop up is very much like the documentprovider - choose a folder. So I am confused why Titanium has these problems and can understand a point of view that they haven't adapted as they should have perhaps but then I find it hard to believe that they wouldn't have done what they can with the features /tools they have for one of the most popular backup programs..
Either way, at the end of the day I was really hoping I could have got a fix which worked much like sdcard fix on Kitkat which stopped the nonsense and Google's insistence that they know best how we can and should use our SD cards.
And indeed for many people Marshmallow fix and or EXTSD appear to work for a lot of people in the way I was hoping - hence the creation of this thread because
1) it certainly doesn't for both my Samsung devices and
2) Many people with Samsungs (and some other devices) appear to be having the same difficulty.
I don't understand what has been done on MM to make it so difficult to overcome the problem but obviously it appears Google is just plain bloody minded and trying to make it more foolproof.
louiscar said:
The Titanium problem is fairly common. if all apps need to be was mm compatible then we wouldn't need a fix for the SD cards I would have thought.
But coming to Titanium itself I can select the old folder with is exsdcard/titaniumbackup but Titanium will tell me this has no write access but I can use it to read from and restore.
There is no location that Titanium will use or see on the extsdcard. What one has to do to is to copy the contents of your backup folder to the internal card then select that as the backup folder in Tba. Then you have elect to change the backup folder but choosing DocumentProvider storage. At this point you then have to create a folder - an existing folder is no good. Once created it will copy the contents of the internal folder to the extsdcard. Apart from the fact that this 'workaround' is much slower it is also inconvenient and any kind of change for whatever reason in the backup folder means that you can't just switch to the old one you have to go through the whole creation process.
As far as I am concerned this is why I wanted an SD card fix but I also understand to some point your view and it does make some sense. However it is confusing. When this nightmare started with Kitkat I understood that apps were allowed their own folder but couldn't affect or write to other folders. Also they were media folders only. This as I remember also affected file managers which then couldn't do their intended job.
With MM and without any fix Solid explorer can and does have full access to the sd card and can write in any folder from what I can see. Other apps seem to possibly access with documentprovider permissions - I'm not sure but many appear to have no problems but the pop up is very much like the documentprovider - choose a folder. So I am confused why Titanium has these problems and can understand a point of view that they haven't adapted as they should have perhaps but then I find it hard to believe that they wouldn't have done what they can with the features /tools they have for one of the most popular backup programs..
Either way, at the end of the day I was really hoping I could have got a fix which worked much like sdcard fix on Kitkat which stopped the nonsense and Google's insistence that they know best how we can and should use our SD cards.
And indeed for many people Marshmallow fix and or EXTSD appear to work for a lot of people in the way I was hoping - hence the creation of this thread because
1) it certainly doesn't for both my Samsung devices and
2) Many people with Samsungs (and some other devices) appear to be having the same difficulty.
I don't understand what has been done on MM to make it so difficult to overcome the problem but obviously it appears Google is just plain bloody minded and trying to make it more foolproof.
Click to expand...
Click to collapse
The fix for KitKat and lollipop isn't needed for MM because Google did in fact listen to people griping about the ext card restrictions.
MM will give full access to properly coded apps.
I have many different devices running MM and all gave write access to the ext sdcard including TB, which I use regularly.
However that doesn't mean to say I haven't had the issue you speak of. I may have even had it with TB.
The folder path I use in this case is mnt/media_rw/
This path is almost always accessible by apps and is the path I'm using right now for TB.
If that doesn't work try disabling 'mount namespace separation' in SuperSU settings then reboot also make sure your TB is up to date.
ashyx said:
The fix for KitKat and lollipop isn't needed for MM because Google did in fact listen to people griping about the ext card restrictions.
MM will give full access to properly coded apps.
Click to expand...
Click to collapse
Ok understood.
I'm guessing then that the so called Marshmallow fix via xposed is to get older apps which may not be updated to work
ashyx said:
I have many different devices running MM and all gave write access to the ext sdcard including TB, which I use regularly.
However that doesn't mean to say I haven't had the issue you speak of. I may have even had it with TB.
The folder path I use in this case is mnt/media_rw/
This path is almost always accessible by apps and is the path I'm using right now for TB.
Click to expand...
Click to collapse
Ok so now the plot thickens and I've no idea what is going on here. Tba says when I navigate to this folder [and I'm assuming that the choice when asked is "filesystem storage" and not "Filesystem storage - Media" (which only offers internal memory anyway)]
"This folder cannot be accessed"
and that is before getting to the external sd card which would be the number (F91E-D472) in my case. ie. mnt/media-rw
Needless to say - Solid explorer can see this and navigate to the sd card no problem.
This happens on both Note 4 and TAB s and I'm really curious now because something on my systems are different.
ashyx said:
If that doesn't work try disabling 'mount namespace separation' in SuperSU settings then reboot also make sure your TB is up to date.
Click to expand...
Click to collapse
Sure, namespace is unchecked - did that on both devices some time ago, and Tba is up to date.
Pretty damn confused now
louiscar said:
Ok understood.
I'm guessing then that the so called Marshmallow fix via xposed is to get older apps which may not be updated to work
Ok so now the plot thickens and I've no idea what is going on here. Tba says when I navigate to this folder [and I'm assuming that the choice when asked is "filesystem storage" and not "Filesystem storage - Media" (which only offers internal memory anyway)]
"This folder cannot be accessed"
and that is before getting to the external sd card which would be the number (F91E-D472) in my case. ie. mnt/media-rw
Needless to say - Solid explorer can see this and navigate to the sd card no problem.
This happens on both Note 4 and TAB s and I'm really curious now because something on my systems are different.
Sure, namespace is unchecked - did that on both devices some time ago, and Tba is up to date.
Pretty damn confused now
Click to expand...
Click to collapse
Have you tried placing the TB folder on your ext sdcard then used the detect button (whole device) in preferences to detect the folder and then select it under mnt/media_rw?
ashyx said:
Have you tried placing the TB folder on your ext sdcard then used the detect button (whole device) in preferences to detect the folder and then select it under mnt/media_rw?
Click to expand...
Click to collapse
This was the method I used as soon as I updated to MM and didn't notice the "this folder is not writable" message.
However, the option to choose mnt/media_rw isn't available. If I use Detect > whole device I'll be offered :
/storage/F91E-D472/Titaniumbackup
perhaps I'd see the other option under normal circumstances but Tba is not able to access that path so wouldn't find it in a search ... I guess
Aha! could this be the problem?
see post #15
https://forums.geforce.com/default/topic/917126/write-to-external-sd-restriction-in-marshmallow/
What is your sd card formatted as - mine is FAT32 so perhaps I need to go exfat?
..but then such links show that I'm certainly not alone - this one actually confirms that tb has this write problems and leads to the Documentprovider solution:
https://www.youtube.com/watch?v=GATqU1_xzqA
louiscar said:
Aha! could this be the problem?
see post #15
https://forums.geforce.com/default/topic/917126/write-to-external-sd-restriction-in-marshmallow/
What is your sd card formatted as - mine is FAT32 so perhaps I need to go exfat?
..but then such links show that I'm certainly not alone - this one actually confirms that tb has this write problems and leads to the Documentprovider solution:
Click to expand...
Click to collapse
ExFAT. Anything above 4gb should be ExFAT.
ashyx said:
ExFAT. Anything above 4gb should be ExFAT.
Click to expand...
Click to collapse
curiously I set permissions to 777 for the mnt/media_rw and titanium can go there but any further (even though I've done the same for the sdcard folder - nada!
and sadly after converting to exfat - mnt/media_rw .... "this folder cannot be accessed"
Not sure what else I can do.