Develop Bugs

[Experience sharing] Recovery data from sd card

Help please. All my data get lost!
I know the data on the card, but just cannot see them.
From checking the property of datacard, i know that all the data still on it. however, after open the card, just 2 files which i never know, all the others gone.
Don't know what my trinity did on my datacard wile i using the bluetooth internet sharing with my pc. After that, this happened.
All 1.4GB data disappeared!
Please, anyone can help?
Solution on #3

Would you care to let us know what the problem was? You might help others...

oVan said:
Would you care to let us know what the problem was? You might help others...
Click to expand...
Click to collapse
sure, it's my pleasure to help others here.
I use wm6 with a 4GB MINI SDHC(Karmba 4.0). After i use bluetooth internet sharing with my laptop, i found that all 1.4GB data disapeared from my sd card. Instead of them, i saw 3 files which have strage name on them and cannot be opened. All these files are 0byte. Then i insert sd into my laptop, right click sd to check property, i knew all data still on sd card, because the property of sd card shows "1.4GB used". After that, i enable my laptop to see hiden files, not see anything from sd card again.
Finnally, i found a tool called "Final recovery". This tool bring the most of files back to me, not all of them.
I suppose, the internet sharing write all the internet temp files into my sd card, then all my data had been overwrited. So, even when i use recovery tool, cannot recover all of them.
Karmba 4.0 set internet cache and temp folder in the sd card by default(Karmba 4.1 maybe does the same thing). Thus, i think maybe this is where the problem comes from.
By the way, i really appreciate what Karmba did for all the user here. His rom is quite good, But i think 1.2 is the best one. The others really need debug.
Hope this information can help other people who have the same problem. Cheers.

It's nice for you to share about your experience regarding recovery.
However, I think it's worthy to point out that SD corruption could be caused by almost any program that access the card. It has been discussed many times in the forum.
It's actually a HTC bug, which goes unfixed. Artemis got a fix to its SD driver long time ago.... Anyway, prevention in my opinion is far better than recovery. Look for a program called "sdsentry" and it will notify you when the corruption occurs and allows you to reboot the machine to prevent the corrupted FAT image got written to the card itself. It will save your day. Try it.

[Q] Unable to see storage card when running on Android

Hi all,
I am trying to get android to work on my old Tilt2 for my fiance so we can play games together. I've gone through all the steps by adding the correct files to the root of the storage card and running Haret. Every thing seems to work "fine" other than the fact that I can't see a storage card while in Android. I tried to partition my SD card to see if that would help but I am unable to determine the proper way to do that. Any help would be appreciated

Do you have some type of file manager installed on Android? I know that I could always see it, with the exception of the Android folder on my card.

Demonic240 said:
Hi all,
I am trying to get android to work on my old Tilt2 for my fiance so we can play games together. I've gone through all the steps by adding the correct files to the root of the storage card and running Haret. Every thing seems to work "fine" other than the fact that I can't see a storage card while in Android. I tried to partition my SD card to see if that would help but I am unable to determine the proper way to do that. Any help would be appreciated
Click to expand...
Click to collapse
I've said this 100x, not sure why it never shows up on people's searches...
But backup all the data on the card. Format the card (full format, FAT32) using the HP Tool. Restore all the data on the card after the format, or start over fresh doesn't really matter. Apps should now be able to see the card, etc.

I'm not concerned about apps seeing the storage card. I don't have a "My Files" app that will let me navigate the card. Do I need to download a file manager in order for it to work?

I fixed it.. I had to download a file management app I feel dumb now.

Which App?

lotusfrontera said:
Which App?
Click to expand...
Click to collapse
Astro is pretty good, and is included in AndroidApps folder IIRC.

arrrghhh said:
Astro is pretty good, and is included in AndroidApps folder IIRC.
Click to expand...
Click to collapse
Amusingly, I use multiple file storage apps. Super Manager for making system files r/w, and file expert for the look and feel. I have astro too, on my other phone, but only really use it for enabling all file type downloads from the web.
Sent from my SGH-I897 using XDA App

[Q] Data recovery on Xperia S (rooted)

Hi all,
Just wanted to start by saying, big thanks to DooMLoRD and the rest of the xda-developers forum for providing me the tools to get root access to a friends phone, who has recently accidentally deleted all their photos and videos. If we are successful, I'll definitely be suggesting that they make a donation to Doom for his epic contributions
I'm trying to help them recover the lost media. I know that typically performing data recovery on a phone requires root access, so I have gone ahead and done this. On with...
My question:
I've got an Xperia S running Jellybean (4.1.2) which is rooted. However attempting to use my data recovery tools on the phone, the device is not shown as a storage device. As you may well be aware, the S does not come with external storage. The S also has the 'mass storage mode' removed. Nice one Sony, give professionals another reason to avoid your products in the future...
I don't want to Flash the phone since any added files will start destroying the potentially recoverable data (plus I'd simply rather not format the phone if possible).
Is it possible to mount the internal storage of the Sony Xperia S as a drive so that I can run my PC based data recovery tools on it?
I imagine App Store apps are too lightweight to handle a file-based undeletion. If I could just see the device in my recovery apps I'm sure I'd be in business! I've attempted Recuva and R-Studio.

Doing some more research (like a good little n00b) I imagine I'm going to need SD Mounter.
I'm a little thrown off because 'SD' usually describes SD cards (of which the Xperia S has none). Also, the screenshots (for SD mounter) seem to indicate it's for ICS so I'm not sure if there's going to be a compatibility issue there.
Am I barking up the wrong tree by making this assumption? Should JellyBean have access to the mass storage and the option is simply not showing for some reason? Anyway, I'll continue working under my assumptions until someone suggests otherwise...
To get SD Mounter running, I'm going to need BusyBox. The problem is, I'm trying to read the BusyBox installation FAQ, and I'm finding it very vague. Like...
and save it under the name "busybox"
Click to expand...
Click to collapse
but it does not specify WHERE. Make a folder called 'busybox' on the root folder of the phone? Somewhere on my PC (the page suggests its for the PC rather than the phone)? Also I'm seeing Linux-looking command lines, but I'm on a PC... can I run this via the command prompt in Windows? I downloaded the 'binaries' like it said, but there aren't any executables in here...
Can anyone shed some light?

There's an app called BusyBox Installer, that installs it correctly on my Xperia S. That SD Mounter app works perfectly on 4.1.2, though. I use time to time. It just messes up a bit with Media Scanner, requiring me to do a reboot on the phone to make it work again.
I wish you lot of luck trying to recover your files. I once tried something like that, but came unsuccessful. There were some media I wish I had saved, but it wasn't THAT important, so I just gave up.
Suggest to your friend, though, to get an account on Mega, Box.net or Dropbox. All of them has auto backup of camera media to the server. All of them has options to backup only on WiFi, and even when charging only. The first two has 50 Gb of free storage for life (Box, you just need to sign with your Xperia device), and the later only 2 Gb, but you can get more and more with promotions.
Alternatively, he can enable the Google+ Auto Backup. There is 15 Gb (shared with Gmail and Google Drive) for pictures on original resolution or unlimited on 2048px, compressed. On Google+, though, you have the Auto Awesome, which make some awesome images.
Hope it helped. If I can help any further, just tag me
Sent from my LT26i using Tapatalk

Hey Felimenta97, thanks for your swift response!
Felimenta97 said:
There's an app called BusyBox Installer...
Click to expand...
Click to collapse
I see 'BusyBox Installer' in the Play Store, is that the one? Seems strange that the Play Store would add an app that requires rooting. Just wanna make sure I shouldn't be looking for it somewhere else (plus I'm away from that phone at the moment)
Felimenta97 said:
It just messes up a bit with Media Scanner, requiring me to do a reboot on the phone to make it work again.
Click to expand...
Click to collapse
That's okay. I've warned them this process might even brick their entire phone. They are prepared (I hope) for complete loss/compromised apps
Felimenta97 said:
...I wish you lot of luck trying to recover your files. I once tried something like that, but came unsuccessful...
Click to expand...
Click to collapse
*touches wood*. Gah I'm suddenly 10 times less confident this file recovery is gonna work. Wish me luck! They'll be crushed if I can't get their media back...
Felimenta97 said:
...get an account on Mega, Box.net or Dropbox...
Click to expand...
Click to collapse
Oh trust me, I've already given them the lecture
Thanks for your help!

TheWaste said:
Hey Felimenta97, thanks for your swift response!
I see 'BusyBox Installer' in the Play Store, is that the one? Seems strange that the Play Store would add an app that requires rooting. Just wanna make sure I shouldn't be looking for it somewhere else (plus I'm away from that phone at the moment)
That's okay. I've warned them this process might even brick their entire phone. They are prepared (I hope) for complete loss/compromised apps
*touches wood*. Gah I'm suddenly 10 times less confident this file recovery is gonna work. Wish me luck! They'll be crushed if I can't get their media back...
Oh trust me, I've already given them the lecture
Thanks for your help!
Click to expand...
Click to collapse
As I'm a lazy person, who can't find a way to break quotes into multiple parts (serious, how do you Do that, without having to write the quote code every time? It is not much, but I'm really lazy, so yeah.
Yep, that's the app. There's no reason for Google to block root apps. It's a function of the OS itself, just hidden from users. It's one of the easiest things to do on a Nexus device, after all. It's hidden because, if used without caution, can soft brick your device. But, don't worry, that shouldn't do any harm. At it least it hasn't with my device until now haha
As I said, I had already lost lots of stuff, and I didn't bothered much to go any further to recover it. It was a simply Install Recuva, run on the SD card and see if I could restore anything. Nothing? OK, no worries. As you already mentioned in your first post, avoid at all costs writing new files to the SD Card partition.
About the lecture, yeah, I imagined you had already told them, but it doesn't hurt to tell anyway.
About the SD Card on the Xperia S, another technical info you might or might not know, and also doesn't hurt to tell. Until Android 2.3, devices with a big internal storage required a partition for cache, one for data (apps and their own data), one for system, and one SD Card. The last one in Fat32 (plus others, but those are just too small and insignificant, for most, anyway) Think of a normal hard drive with plenty of partitions. Since Xperia S was developed (and launched) with 2.3 (one of Sony's biggest mistakes with this phone), it had to follow those "guidelines".
With Android 4.0 and beyond, the above mentioned data and SD Card turned into one partition, in Ext4 format. That data partition stores both apps and their data, and also other types of media, like media, documents, and etc. That storage goes into a mounted folder.
Anyway, again, wish you good luck. If they aren't very close friends/relatives, you should charge some money for all the hassle if you recover haha
Sent from my SGP311 using Tapatalk

Felimenta97 said:
how do you Do that, without having to write the quote code every time?
Click to expand...
Click to collapse
Haha, actually I still kinda do. #hen I hit 'reply' I empty the quote block, copy the empty quote block a few times, then copy-paste the parts of the text I'm replying to as I go
Felimenta97 said:
avoid at all costs writing new files to the SD Card partition.
Click to expand...
Click to collapse
Yeah absolutely.
Felimenta97 said:
Until Android 2.3, devices with a big internal storage required a partition for cache, one for data (apps and their own data), one for system, and one SD Card
Click to expand...
Click to collapse
Jeaz. Thank god I don't have to eff around with that!
Felimenta97 said:
With Android 4.0 and beyond, the above mentioned data and SD Card turned into one partition, in Ext4 format. That data partition stores both apps and their data, and also other types of media, like media, documents, and etc. That storage goes into a mounted folder.
Click to expand...
Click to collapse
I don't need to re-format the internal storage of the phone to attempt recovery do I?
Thanks again Felimenta!

TheWaste said:
Haha, actually I still kinda do. #hen I hit 'reply' I empty the quote block, copy the empty quote block a few times, then copy-paste the parts of the text I'm replying to as I go
Yeah absolutely.
Jeaz. Thank god I don't have to eff around with that!
I don't need to re-format the internal storage of the phone to attempt recovery do I?
Thanks again Felimenta!
Click to expand...
Click to collapse
Not in Xperia S case. As I said, it is on Fat32, so it is easily mount-able on Windows.
On any phone with Android 4.0 or more, you'd need a Linux to do the recovery. You can't format it, or else you will turn the device into a really expensive paperweight.
Sent from my SGP311 using Tapatalk

[Q] Can only create folder through "My Files"?

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

Is there any way to get write permissions to SD card - xposed Fix EXTSD dont work

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.