Develop Bugs

[MOD] MicroSD 2 Internal Memory Swap w/ICS support

***Warning Dragons Ahead!!***
Do this at your own risk, it will not void your warrantee but it may make your device unresponsive and cause other issues that I haven't discovered yet! Also, DO NOT at any point attempt to use the unmount sdcard found in your storage settings and DO NOT take your micro sdcard out while your tablet is on, doing these things will cause your apps to fc and potentially loose data. This has been tested only for the Iconia A100 and other devices will probably have different mount points.
It's working great for me but your results may vary, I am not responsible for any damage or problems you might encounter by using this mod (very unlikely that you'll have problems though).
What this mod does:
Since this particular tablet only has 5.4gb of internal storage, I thought it would be great to use my external sd (which is much larger) to install app data and everything else on. So this mod will dirty swap your External micro sd card with your internal memory and vice versa. By dirty swap I mean that the original mount points are untouched and I've just re-bound the mount points to different locations in the tablet. Not the ideal way of doing it, but it works and since we can't touch our init its just about our only option.
It will also speed up your sdcard's read and possibly write speeds by increasing the sdcard's cache.
Requirments: (things you'll need before doing this mod)
You'll need to be rooted, have root explorer installed and of course a micro sd card in your tab:
Instructions:
- Download and unzip the attached file and put it in the root of your internal sdcard (/mnt/sdcard)
- Open root explorer and navigate to /mnt/sdcard (if its not already there) tap and hold on the file install_recovery.sh and pick the copy option
- Now navigate to the /etc folder tap the Mount r/w button
- Find the install_recovery.sh file tap and hold it, then select the option rename. Change the name to install_recovery.bak and then tap paste to copy over the new file.
Now look just under the file, you'll see the date and permissions, it should say something like rwxrwxrwx if it does not you'll need to tap and hold the file tap permissions and check all three boxes for read and execute.
Once you've done the above steps reboot and wait about a minute after your tab comes up, goto settings and look at your storage space to see if the internal space size has changed.
To reverse just delete the install_recovery.sh file, rename the backed up one and reboot. If you decide to keep this mod, you'll want to copy the contents of /mnt/external_sd to /mnt/sdcard so you dont loose any of your app data. Also, you'll no longer need GL 2 SD or any other mod to fetch data from your micro sdcard.
Note: if you have problems deleting or writing to /mnt/external_sd after doing this mod, in root explorer goto /mnt press Mount R/W tap and hold on external_sd and choose permissions. Make sure that all boxes for read and write are checked.
You can use this in conjunction with ICS, its been tested and works great (actually improved my bench scores in antutu benchmark). You can merge the system r/w mod with this one to keep your system read /writable (in ICS) just add the system r/w commands to the end of this install-recovery.sh file.

Thank you! This Mod is greatly appreciated. I'll give it a go once my hangover settles down
Sent from my SPH-D700 using xda premium

Works like a champ. Awesome.

crossix,
...thanks a bunch for this mod, it works great, I've tested a number of apps and scenarios and so far so good.
I reviewed the original install_recovery.sh and noticed that it's there for some sort of firmware / recovery updates. ...so since we replaced the script I'm wondering if it will prevent future firmware upgrades, or more importantly could it prevent an emergency restore / recovery.
Perhaps merging your script with the original would be beneficial?
...any thoughts on this?
Thanks again for your effort on this, FredT

I don't forsee any issues, unless you get an ota update, then you'll need to redo this mod.
The system runs /system/etc/install-recovery.sh on boot and would normally check the recovery partition for files changed outside of an ota update (ie viruses or cwm). If a file gets changed this script would run at boot and restore it's origional recovery.
Normally in order to get cwm or any other custom recovery to "stick" you would need to delete this file (or delete it's contents) so that your modded recovery wouldn't be overwritten on the next boot.
An OTA update will overwrite the install-recovery.sh file and you may have to follow the above instructions again (or it may even break my mod). I'm still running the origional stock rom (3.2) and haven't tested this mod on the newer versions.
Sent from my MB860 using XDA App

cool thanks.... btw I am on the latest 3.2.1 ota update and this is working great for me so far....
Sent from my A100 using Tapatalk

thanks buddy

what format for the SDCARD
so I got a new large SDCard to use for this setup... I bought it off a buddy and it is formated as EXT4 already. I'm going to reformat it, what is the best format to use with HC ? EXT4 or something else?
Thanks FredT

Unfortunatly only fat32 will work, I've tried formatting & mounting the sdcard as ext2, 3 and 4, but couldnt get the tab to mount it automatically.

Thank you a million times can finally put all my gameloft games on the sd card without having to delete others.

I don't have install_recovery.sh I have a init_goldfish.sh
And the etc folder you are talking about, is it the one in system or the one just under the main root of the device (/etc or /system/etc)? I only bring that up because I thought it odd I had two "almost" identical etc folders!?! One in /system and one under /.
Either way, I don't have a install_recovery.sh file. only the init_goldfish.sh file. Any thoughts on this?

/etc is actually a symlink to /system/etc so they are one in the same.
What Build is your tab running? (find out by tapping the time in the bottom right corner of the screen and then push the little lines on the right and tap system, scroll down to about tablet and look for build number.
Sent from my MB860 using XDA App

It worked like a charm!!!!
I just have one question, what happens to the files/apps on internal memory? So basically it just swapped it witb external sd?
Sent from my A100 using xda premium

Yup, you can just copy all of the contents from /mnt/external_sd back to /mnt/sdcard and everything should be good.

Awesome mod, this is a life saver. Just the other day found myself having to delete apps to dload GTAIII now I can use my 32GB Sd Card.
Thanks a ton!

crossix said:
/etc is actually a symlink to /system/etc so they are one in the same.
What Build is your tab running? (find out by tapping the time in the bottom right corner of the screen and then push the little lines on the right and tap system, scroll down to about tablet and look for build number.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I don't have the file under /etc or /system/etc either
Kernel version 2.6.36.3
Build number Acer_A100_1.018.05_COM_GEN2
Edit: I followed the instructions and it WORKED!!!!
Sent from my HTC EVO 3D using xda premium

apparently they are having some success getting this to work with the a500 so assuming you can find a working root method for the a101, this should work with it as well.
Sent from my MB860 using XDA App

Thank you for this
One problem - I needed to move to a larger drive due to Audible - but now that I'm moved over, Audible is complaining "Please insert SD Card" and then exiting!
Looks to be more of a Audible thing vs. storage, but if anyone has any thoughts on working around this, that'd be great

OK... Weird thing. I have about 3gb free space in my micro SD card, 2.5gb of real internal memory, but only 880mb free for application space. Is it just me?

This did not work for me, I follow all your instruction but still nothing, can it be because I have the build.prop mod act, any help.
Sent from my A500 using xda premium

App data to external card

Hi everyone,
I was just wondering if there still is no way of moving the app data to the external sd card?
I am especially interested in the games data, because i've got tons of games, and obviously cannot play all of them because of the storage issue.
I know about the gl to sd app, but I was wondering if there is another way of doing this, as after using this app, you need to launch the game from the app.
Also is there a beta version of some sort of the app2sd app that might work on the S3?
Thanks!

yeah
dont have any way to move app to external card?

Here you go: [TOOL] DirectoryBind - move data to external_sd (GameLoft, Shadowgun etc.) ROOT req.
Runs very well with my S3 and the 64GB sd-card. You are able to move every directory you want to the external sd-card and mount it to the internal sd-card.
- I just do not use the "Transfer files from target to data" and have moved the files manual by myself before I make a directory bind.
- At second I have to activate "Alternate dbase mgmt" and "Persistent service" (under preferences) to have the bindings after a reboot.
- you can make a backup of your bindings e.g. if you want to flash a new rom (under "options" - "backup database")
I use the version 0.2.0o

hurray said:
Here you go: [TOOL] DirectoryBind - move data to external_sd (GameLoft, Shadowgun etc.) ROOT req.
Runs very well with my S3 and the 64GB sd-card. You are able to move every directory you want to the external sd-card and mount it to the internal sd-card.
- I just do not use the "Transfer files from target to data" and have moved the files manual by myself before I make a directory bind.
- At second I have to activate "Alternate dbase mgmt" and "Persistent service" (under preferences) to have the bindings after a reboot.
- you can make a backup of your bindings e.g. if you want to flash a new rom (under "options" - "backup database")
I use the version 0.2.0o
Click to expand...
Click to collapse
I'm trying to make this thing work, but not really succeeding; here's what I did:
> First time I tried one game by using the "Transfer files from target to data":
- I long tapped the first field, the source, and selected an empty folder on the external sd card
- I then long pressed the second field, the target, and selected the folder on the sdcard containing the game data
- Then ticked the "Transfer files from target to data" option and taped the Add button; then waited for the operation to complete
- Afterwards, runed the game, but it prompted me to download the data.
> After this method failing, I tried to transfer the files manually, with another game:
- Created a new folder on the external card and moved the game data manually there
- In the app, I selected the target and the source directory respectively, left the "Transfer files from target to data" option un-ticked and taped the Add button; waited for the operation to complete again
- Then I runed the other game and the same problem.
Please note that I ticked the "Bind on boot", "Alternate dbase mgmt" and the "Persistent service" options in the app preferences and tried restarting the phone and checked the games again, with no luck.
Could someone please point the mistake in what I did?
Thanks!
EDIT: nevermind, I did not taped the icon before the bind so it will turn green.
Now it works!
weepeey!
Thanks for that!

this program can do that too without root, but it's only for gameloft games
http://www.filestube.com/6osJgxhiKD...ch-APK-for-Samsung-by-Duero-include-Java.html

b0gd4n said:
Hi everyone,
I was just wondering if there still is no way of moving the app data to the external sd card?
I am especially interested in the games data, because i've got tons of games, and obviously cannot play all of them because of the storage issue.
I know about the gl to sd app, but I was wondering if there is another way of doing this, as after using this app, you need to launch the game from the app.
Also is there a beta version of some sort of the app2sd app that might work on the S3?
Thanks!
Click to expand...
Click to collapse
If u r rooted then i highly recommend using "gl to sd" from play store n thr great thing is that it is free. I myself use this n this works for all games... provided that u r rooted... worth having a go
Sent from my GT-I9300 using Tapatalk 2

aneeqkhan said:
If u r rooted then i highly recommend using "gl to sd" from play store n thr great thing is that it is free. I myself use this n this works for all games... provided that u r rooted... worth having a go
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I used that, but it is really annoying that you have to launch the game from within gl to sd.
The Directory Bind app works very well, and you can set the bind at boot so no worries about having to set everything up every time.
Thanks anyway!

Try "super mount" from lidroid.u can find it in market.

zodiaxe66 said:
Try "super mount" from lidroid.u can find it in market.
Click to expand...
Click to collapse
Could you tell me how to use it ?
On google play it says that i9300 is supported.
I created a new dir on extSd: "lidroid". After starting app, and hitting "mount SD card" it says Mount error
Does it require root ?

i tried using app2sd pro to transfer some to my external sd, but when i used it, the transfer button is no where to be found. any idea??? btw, my s3 is already rooted

reyes_todd22 said:
i tried using app2sd pro to transfer some to my external sd, but when i used it, the transfer button is no where to be found. any idea??? btw, my s3 is already rooted
Click to expand...
Click to collapse
Rooting does not bring back the apps 2 sd function. I recommend directory bind, mentioned earlier
Sent from my GT-I9300 using Tapatalk 2

https://play.google.com/store/apps/...SwxLDIxMiwiaXQuY3JvY2Npby5zd2l0Y2htZW1vcnkiXQ..
Sent from my GT-I9300 using xda premium

I have just installed and tested DirectoryBind on my S3, I actually transferred GTA3 data files from the internal to my external SD, works fine, rebooted my mobile and tested the game again, worked fine too. Very happy with this app...

I think that it is a little bit uncomfortable to launch apps from GL to SD(root), however, the developer is working very hard on the app which is great for our SGS3, recently we got an update for 64 SD cards and misc, i wil put my prayers on this man for having a completely app that resolves the anoying emulated storage for our loved SGS3 :fingers-crossed:
for me, this is the best.

[Root] NookManager - graphical rooter for 1.2.x and beyond

This is a graphical, interactive rooting system with the ability to create/restore backups and factory settings.
This has been tested on systems 1.1.5, 1.2.0 (US/UK), and 1.2.1. It will probably work on earlier versions and should be safe to use on future versions. For best results, however, you should be on 1.2.1 before using this tool.
If you've tried rooting your nook unsuccessfully with another utility, it's best to do a factory restore (from NookManager, choose the "Rescue" option and then "Restore factory.zip") and, if your nook came with older firmware, upgrade to the latest 1.2.1 firmware.
Features:
Root your Nook
Backup/Restore
Restore to factory settings
Disable B&N Apps
Custom plugins
How to root:
1. Download NookManager.
2. Unzip the file you downloaded and write the NookManager.img file to an empty SD card. On Windows, you can use disk imager. Linux and mac users can use dd.
Use a real SD card adapter when writing the image, DO NOT USE YOUR NOOK AS THE SDCARD ADAPTER.
If possible, you should use a dedicated SD card for the NookManager image (so you can easily restore from a backup should you ever screw up your Nook). A 512Mb card is big enough for the NookManager image plus a backup of your Nook.​
3. Power off your Nook, insert the SD card and power on.
You should see the NookManager boot screen followed within 15 seconds by the welcome screen.​
4. Choose "No, continue without wireless"
the wireless option is for advanced users looking to connect directly to their device​
5. Make a backup using NookManager! Choose "Rescue" then "Backup" then "Format remaining space on SD card" and finally "Create backup"
Because NookManager cleans the empty space on the Nooks' internal partitions and compresses the backup, it will take at least 15 minutes (and up to 45 minutes) for the backup to complete. Be patient. The final backup file can be as small as only be a few hundred megabytes, depending on the number of downloaded or sideloaded books you have.​
6. Copy the backup image to your computer. Connect your Nook to your computer using the USB cable. Copy the 'backup.full.tgz' and 'backup.full.md5' files from the NookBackup drive to your computer.
This is your backup in case anything happens to your SD card. This backup is tied to your individual Nook so keep it safe. It's important to copy this file while your Nook is still booted from the SD card because Windows will normally hide the NookBackup partition on the SD card. If you ever need access to the NookBackup partition again, just boot your Nook using the NookManager SD card and connect the Nook to your computer with the USB cable.​
7. Root! After your backup, press "Back" and "Back" to return to the Main Menu. Press "Root" and then "Root my device"
8. That's it! After rooting, pres "Back" and then "Exit". Remove the SD card and put it someplace safe, in case you need to restore to your backup later.
After rooting, you can install Google Apps using straygecko's excellent NTGAppsAttack package if you want to use Google Market/Gmail/Calendar/etc.
[/LIST]
Technical stuff:
The actual rooting function is minimal and as non-invasive as possible:
uRamdisk is patched to enable ADB
the internal database setting is changed to allow installation of non-market apps
the DroidSansFallback font is replaced with the updated font from jellybean to add support for extended characters
the su/Superuser binary/package is installed
Relaunch is installed
ADB Konnect is installed for enabling/disabling ADB over wireless
on systems running firmware 1.2+, the ModManager jars and package are installed
on 1.2+ systems, the PackageInstaller.apk from the 1.1.2 firmware is installed to resolve issues with package installers
and, finally, the Amazon appstore is installed just to have some easy way of downloading new apps. You can uninstall it using ReLaunch if you don't use it.
The uRamdisk patching is done with scripts rather than copying pre-compiled binaries, so this should be safe for all existing versions of the Nook firmware and (hopefully) will be forward compatible with any new releases.
The rooting procedure is non-destructive and can be run multiple times without causing problems.
Under the hood, this is a minimal linux environment with the nook drivers/binaries and a few core android binaries. The display is generated with imagemagick and written directly to the framebuffer.
If you're connecting to NookManager wirelessly over SSH, the username/password is root/root
Wherever possible, the parts of this system are compiled from source including the Linux kernel, uBoot, and all of the buildroot utilities. The hardware drivers and associated binaries are extracted from the 1.2.0 upgrade package.
The source for the project, including an automated buildscript is available at GitHub.
Support for custom menu items and scripts is documented here.

https://github.com/doozan/NookManager/downloads
NookManager.zip
17.9MB · Uploaded 14 hours ago
File was not found.
Click to expand...
Click to collapse
??

Weird. I deleted/re-upped the file and the download link seems to be working now.

ok..now it works. Thanks

Will this work with NoRefresh?

Thanks for the work on this - it was easy and worked great. And if you're planning to update, maybe add ES File Explorer or Titanium Backup in the pre-installed apps; that would make it easier to install apks directly from your SD card instead of having to do it over wireless adb. But thanks regardless.

Can confirm no refresh works great. Installed FBReader, Opera Mobile, ES File Explorer and Kindle app. Great
I just came from a firmware that had the ability to change the hardware buttons for page turning, any chance of this being added?

Thanks for this! Giving it a try.
Just curious though... I'm trying to create the backup of the device and it seems to take forever to format the free space. It also took forever to find the wireless network and I eventually just rebooted it. How long does it usually take?
I'm using a NST on 1.2.0 and have tried a 2GB Sandisk and a 8GB Dane-elec microsd card.
Gonna try redownloading and re-installing the image.

Install apk
Hi, i successfully root my NGL(1.2.0) but, if i try to install apk (Cool Reader) i got an error window "Out of space" and i'm almost sure it must be enough space to install, may someone can help with this ?

mobamoba said:
maybe add ES File Explorer or Titanium Backup in the pre-installed apps
Click to expand...
Click to collapse
Good suggestion, I've added ES File Explorer
Gvr4-330 said:
it seems to take forever to format the free space..and wifi
Click to expand...
Click to collapse
Thanks for reporting this. There was a glitch with the script that formats the SD card and with the wifi loading. Both issues have been fixed in the latest release.
asprin said:
if i try to install apk (Cool Reader) i got an error window "Out of space"
Click to expand...
Click to collapse
How are you trying to install the apk? I'm also using Cool Reader it installed with "adb install" and runs just fine. For best Nook compatibility, use coolreader 3.1.2-27 (12/11/2012 build) or later.

Originally Posted by asprin
if i try to install apk (Cool Reader) i got an error window "Out of space"
Click to expand...
Click to collapse
You get this error when you try to install application from an .apk file on sdcard or when you try to update application via it's built in updater.
ADB install works fine.
Good suggestion, I've added ES File Explorer
Click to expand...
Click to collapse
I use
Rhythm Software - File Manager
http://rhmsoft.com/?p=96

osowiecki said:
You get this error when you try to install application from an .apk file on sdcard or when you try to update
Click to expand...
Click to collapse
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
mobamoba said:
maybe add ES File Explorer
Click to expand...
Click to collapse
osowiecki said:
I use Rhythm Software - File Manager
Click to expand...
Click to collapse
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.

jeff_kz said:
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
Click to expand...
Click to collapse
Thx for respond, mate, I tried install with file browser in ReLaunch from sd card, and i cant imagine that can be space issue cause i just start procedure after factory reset and rooting, anyway, thanks for tip, will try tomorrow install new build, and adb install. In general great work you did :good:

jeff_kz said:
I'm not able to replicate this: I can copy coolreader to my sd card, and install it from there with no problems using ES File Explorer or ReLaunch. Maybe you really do have a disk space issue. Try openinng an adb shell and run "df -h" to see disk usage on your mounted partitions.
It turns out you can install apks using the file browser in ReLaunch, so I'll be removing ES File Explorer in any future versions.
Click to expand...
Click to collapse
df :
/dev: 116452K total, 0K used, 116452K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/rom: 16116K total, 227K used, 15888K available (block size 512)
/system: 285583K total, 210922K used, 74661K available (block size 1024)
/data: 824424K total, 304344K used, 520080K available (block size 4096)
/cache: 237987K total, 4179K used, 233808K available (block size 1024)
/media: 245484K total, 40K used, 245444K available (block size 4096)
/sdcard: 31149680K total, 6924320K used, 24225360K available (block size 16384)
Are you using UK or US Nook?
I'm on US Nook FW 1.2 + v176 kernel

I'm able to reproduce the apk install problems now. The "Not enough free space" error is what android throws when the internal PackageManager can't create the temporary apk file. In this case, it turns out that it's a permissions-related read error from the sdcard. I don't know if this is a matter of the internal PackageManager not running with elevated permissions, or if it's that the sdcard is mounted too restrictively.
If I re-mount the sdcard without the restrictive permissions, I can install apks from the sdcard without any errors:
Code:
umount /sdcard
mount -t vfat /dev/block//vold/179:17 /sdcard
If anyone else has any ideas for making this work, I'm open to any suggestions. In the meantime, "adb install" works just fine for installing packages.

I really suggest grabbing Android Commander if you're new to adb to graphically install apps.

jeff_kz said:
Thanks for reporting this. There was a glitch with the script that formats the SD card and with the wifi loading. Both issues have been fixed in the latest release.
Click to expand...
Click to collapse
Thanks for the quick update. I'm going to try it out now and will report back. I'm very excited
It works! Thanks so much for this! Very easy way to root and backup.

With your tool now I use this to read comics, RSS and books. First I need to say thank you.
I installed "D7 Google Reader" and "Google Drive" which requires Google Login. How could I use this software? Thanks
Also I installed version 0.2, I saw 0.3 comes out. Can I just update 0.2 to 0.3 directly? Thanks

so glad I decided to check the nook thread. Finally BN apps gone . Thank You

hi all, anyone have test factory reset on nstg US ? my backup is corrupt.
Envoyé depuis mon GT-N7100 avec Tapatalk

[Q] TItanium Backup SD card not writable after Lollipop Upgrade

I have the T-Mobile Galaxy Note 3. I was on stock and just took the OTA upgrade to Lollipop (N900TUVUFOB6). After doing this, I rooted the phone with CF Auto Root and installed TWRP 2.8.5.0. I have root access fine. I keep my apps backed up from Titanium Backup on my SD card. When I open up Titanium Backup it tells me the directory isn't writable. I am on the latest su binary / supersu and I have tried changing the mount namespace setting with no luck. Is there anything else I could try to fix it?

Did you install the SD card fix app?

I think there is an option on lollipop to authorize other apps to access directories that are not there own. That might be the problem.

I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!

sjancura said:
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
Click to expand...
Click to collapse
Thanks so much! I had to pick the option DocumentProvider storage and then select the directory through there. Working fine now.

Sorry. Meant Document provider not Directory provider. ?

Has anyone found a reason why TiBu now thinks the entire directory of dalvik cache is unnecessary when you run the clean up option?

Changing that to DocumentProvider storage solved my problem too sjancura, thanks!

Hi,
I spoke too soon... I am still having problem with using external SD card with titanium backup.
I changed the storage provider to DocumentProvider but I cannot 'save' that selection as it's grayed out - please see the screenshot.
I have tried changing name of ex SD card. At first I used SDFix apps which were able to help with similar problem in KitKat but haven't fixed the issue now in lollipop.

I had the same problem (Running Lollipop and TB) and I got it fixed by using one of the KitKat fixes. The one I used was "SDFix" by "NextApp, Inc." in the google play store.

dajomas said:
I had the same problem (Running Lollipop and TB) and I got it fixed by using one of the KitKat fixes. The one I used was "SDFix" by "NextApp, Inc." in the google play store.
Click to expand...
Click to collapse
Thanks...that worked for me too.

sjancura said:
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
Click to expand...
Click to collapse
Hours of frustration brought to an end by that advice ... thanks mate ... you're a legend!

Hi,
I tried running SDFix, having run it in tbe past, prior to finding out this morsel of info on changing DP. However I still can't get it to save that location. Same greyed out directory like previous user posted.

Yeah I found that as well, changed it but could not "save" to that folder location (greyed out). Tried SDFix app, no change. Tried creating a new folder in TB, AND then using ESFile Explorer & neither would allow me to write to the extSD card. Rooted, stock Sprint Lollipop ROM.

I had that issue, worked it out. When you're browsing for a folder with the DocumentProvider select the root of the SD card, then it should close and return to the browser in Titanium Backup. Browse to the sub folder you want, you should be able to click the save button now.

Hi Ghosthree3,
Thanks so much for this. I'm going to give it a shot. My extSD card was used in the past on an earlier version of Android OS, whereby I could write to the extSD card just fine. Consequently there are prior backups on there. As such, I'm wondering if i should mount the phone, copy that folder off, delete that folder on the extSD card and then via TB create a "new" Titanium Backup folder and see if it then allows me to write. Note: I tried mounting the phone to my PC in an effort to create a folder on the extSD card and that method too, prevented me from creating a folder, hence my thought on getting what I have off of the device, and attempting writing a new folder per your directions. I wonder if my PC will allow me to erase that folder.....

Dopamin3 said:
I have the T-Mobile Galaxy Note 3. I was on stock and just took the OTA upgrade to Lollipop (N900TUVUFOB6). After doing this, I rooted the phone with CF Auto Root and installed TWRP 2.8.5.0. I have root access fine. I keep my apps backed up from Titanium Backup on my SD card. When I open up Titanium Backup it tells me the directory isn't writable. I am on the latest su binary / supersu and I have tried changing the mount namespace setting with no luck. Is there anything else I could try to fix it?
Click to expand...
Click to collapse
Install xposed and then use xinternalsd then configure it as u wish. This will fix the problem
Sent from my iris_X8 using XDA Free mobile app

sjancura said:
I searched and found you need to change a setting in Preferences - Backup folder location. Near the top is Storage Provider. Click and change to Directory provider. Fixed it for me. Never knew that was a setting before!
Click to expand...
Click to collapse
Thank you!

Hi s j a n cu r a,
Thank you very much. Someone else posted that, but maybe i'm not selecting it properly. When I select Document Provider, I browse to "Open from SD card", scroll down to the "Titanium Backup" folder, hit "Select" the "Titanium Backups" that are there [at one time I had no issues writing to my EXT SD card], it then says, "Detect!" [External storage] and I select "Everywhere in External Storage". It finds 41 backups there, I select that "External Storage' radio button. That's where I seem to hit a wall. The "Use the current folder" appears to be greyed out. I'm left only with "Cancel". I think there is some deeper issue writing to ExtSD because with File Explorer I can't copy picture files from one folder to the other. That's what is giving me this feeling that something else is going on with write permission. Frustrating to say the least. My only recourse at this point is to use the internal SD, which does work.

Google lollipop external sdcard fix. There's an app in the play store.
Sent from my SM-N900T using Tapatalk

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.