Related
> > > TMO N900TUVUCNB4 External SD Card Write FIX: < < <
tekhd.com/downloads/tmo_kk_extsd_fix.zip
I just ask for a simple thanks...
This will make Titanium, Root Explorer or any app be able to write to external SD Card...
-> Just flash this zip file via TWRP or CWM...
TEKHD said:
TMO N900TUVUCNB4 External SD Card Write FIX: (TMO OFFICIAL 4.4.2 KK)
tekhd.com/downloads/tmo_kk_extsd_fix.zip
I just ask for a simple thanks...
This will make Titanium, Root Explorer or any app be able to write to external SD Card...
Click to expand...
Click to collapse
FIRST!
Damn, well that was fast. Thank you!
Also, I don't think this should be in "Themes and Apps." This isn't a theme nor an app.
Looks like only 1 line was changed in the following if I am correct. I just edited/compared. I only saw the one change though.
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
NMonster69 said:
Looks like only 1 line was changed in the following if I am correct. I just edited/compared. I only saw the one change though.
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Click to expand...
Click to collapse
Yes... correct...
TEKHD said:
TMO N900TUVUCNB4 External SD Card Write FIX: (TMO OFFICIAL 4.4.2 KK)
tekhd.com/downloads/tmo_kk_extsd_fix.zip
I just ask for a simple thanks...
This will make Titanium, Root Explorer or any app be able to write to external SD Card...
Click to expand...
Click to collapse
This is awesome... can this be applied using a stock bootloader?
(Basically, install instructions for us newbs would be greatly appreciated)
Thanks!
Store on External Card and install via TWRP?
sacky73 said:
Store on External Card and install via TWRP?
Click to expand...
Click to collapse
yes
Defenestratus said:
This is awesome... can this be applied using a stock bootloader?
(Basically, install instructions for us newbs would be greatly appreciated)
Thanks!
Click to expand...
Click to collapse
Only through custom recovery. If you don't have a custom recovery, but are rooted, you can add the missing line. Use a root file explorer, go to: ~/system/etc/permissions, then edit the platforms.xml with the root file explorer's text editor, and add the missing line <group gid="media_rw" /> (as in post #3). Reboot, and test if apps now have access to external storage (Don't quote me on these steps. Maybe Google them to make sure how to do it). The details to do it manually are more involved, and you need to know exactly what you are doing. That's why the OP has posted the awesome zip. Flash, and done.
bobbyphoenix said:
Only through custom recovery. If you don't have a custom recovery, but are rooted, you can add the missing line. Use a root file explorer, go to: ~/system/etc/permissions, then edit the platforms.xml with the root file explorer's text editor, and add the missing line <group gid="media_rw" /> (as in post #3). Reboot, and test if apps now have access to external storage (Don't quote me on these steps. Maybe Google them to make sure how to do it). The details to do it manually are more involved, and you need to know exactly what you are doing. That's why the OP has posted the awesome zip. Flash, and done.
Click to expand...
Click to collapse
This worked great. Thank You!
(I need to find a recovery that will flash to the new 4.4 N900T - CWM wont)
Defenestratus said:
This worked great. Thank You!
(I need to find a recovery that will flash to the new 4.4 N900T - CWM wont)
Click to expand...
Click to collapse
This is the only recovery that works with 4.4 as of now. Download the tar, and ODIN it to your phone:
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte
Anyone else having problems with this? I installed, i see the lines of code, but apps like swiftkey cannot access to write. Any ideas?
Sent from my SM-N900T using Tapatalk
aerichards1977 said:
Anyone else having problems with this? I installed, i see the lines of code, but apps like swiftkey cannot access to write. Any ideas?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
yup, i see the lines but the phone doesnt recognize the card.
edit: turns out my card was bad, got a new one and its working great!!!!
Works Great!:good::good::good:
Could be my card is bad, but after using this fix for a few days my card became read-only. Like, period. I can't format it on my PC or my phone. I can access all files, but I can't delete or modify them. Any clues? I've asked around on XDA and there's one other person with this issue, but no fixes. I will try to get my card replaced through warranty in the meantime.
I have an lg gpad and a note 3 this works on the note 3 but gpad I havent tried this yet.I flashed a rom based on stock and card doesnt write to apps only lg apps the rom claims it has the sd card fix but doesnt work like my note 3 my queation is if I flash this on the gpad will it mess anything up.The devs dont seem to be making any roms so Im stuck looking elsewhere
Sent from my SM-N900T using Tapatalk
Nice!
Sent from my SM-G900W8 using XDA Premium 4 mobile app
Thanks!
I'm still unrooted (damn Knox!) but rapidly coming to the conclusion that I just can't work on an unrooted phone any more, warranty or not.
Is there a non-root fix for this issue (as I know that apps like ES Explorer manage to bypass it on stock phones).
Andre
Thank for help to bring back ownership of my Memory Card to me
I'm again owner of my 64GB card- not Google ! My PlayerPro no more were updating ratings for songs ( end developer of PP was to lazy to try created designed folder on the card for the music ?) This was one of the reasons why I rooted the phone;so after I added this line (<group gid=”media_rw” />) everything is working again like was before update 4.4.2 on my Note 3- N900T.
Another thing what I looking for- is increase volume of my Bluetooth stereo headset. I successfully increased volume for wired headset and speaker (speaker- mono- is not strong side of this phone) with edited: mixer-paths.xml, but I can't find line or solution for the bluetooth, maybe someone can help me with it ?
Note: all changes I did using Root Explorer; could be done also with ES File Explorer
Changed permissions for media write and still does not work
TEKHD said:
Yes... correct...
Click to expand...
Click to collapse
I changed the permissions for the WRITE_EXTERNAL_STORAGE. I used different apps that automate this task and Xposed installers HandleExternalStorage. The permissions are changed and everything works for a little while as it use to. I delete files I no longer need and they are gone only to show back up in their old directories again as if I never deleted them. I can't save my music or delete old music from the external storage either. When I delete old photos or the entire DCIM directory on the external storage is goes away only to return about 40 minutes later. I have been dealing with this for several days and am getting a bit ticked off. Now I have a new Note 3 with 32gb internal storage and 32gb external storage except the external storage is not writable, I could have had that with an iPhone. The reason I went with an android was the flexability of storage but that looks like it is gone.
Anyone else have this problems? As I said the file permissions were changed and look good.
Thanks
Hi,
I hope someone has suggestions on the following issue. I've searched threads, but haven't found this specifically.
I need the ability to R/W with multiple programs to my SD card. Due to work and also teaching concerns, I need to access directories of ebooks, articles and databases that are large and in the past were synced from the cloud to my device. Obviously KitKat makes an issue of this.
I recently obtained a Samsung Galaxy Note 10.1 2014 P600. Refurbished by the manufacturer. This has only a one-month warranty so rooting wasn't a concern.
1. I rooted the device using CF Autoroot. Rooting was confirmed by Root Checker.
2. I ran SDFix. No joy. Access to the SD card was sporadic - for example - music on the card would only play 2 seconds of each song.
3. Using Titanium Backup, I froze all Knox-related programs (this was more than the list of 6 I think. I can provide a list later.) Later, I also backed-up and deleted the programs.
Access to the SD card was still sporadic. After a reboot, I might have access for a few minutes, and then restricted access again.
4. I then tried Xposed Framework and the "Handle External Storage" module (see the 3rd method in this article http://technofaq.org/posts/2014/04/fixing-external-sd-card-write-issue-on-android-kitkat/). This worked but still had issues - I had drive access but from time to time it would disappear - it would seem to randomly unmount.
5. But, I decide to keep trying and in the process went to create a folder with File Explorer. FX gave me a message about KitKat - and asked if I wanted to configure it to try to write to the SD card under KitKat. I said yes - and suddenly I cannot access the drive at all.
Android Version 4.4.2
Kernel Version 3.4.39-1462259
Build Number: KOT49H.P600UECNK1
SE for Android Status Enforcing SEPF_SM-P600_4.4.2_0032
The SD card is a Sandisk 128GB.
I haven't tried flashing another ROM because I also need S-Pen and Chromecast functionality - so I just didn't want to fool with it.
1. Does anyone have any suggestions to get SD card RW access?
2. If "No" to the above, what is a good stock ROM with S-Pen and Chromecast functionality that has already addressed the SD issue that I can flash (and where is it located)?
Thank you all for your help.
Have you tried manually editing /system/etc/permissions/platform.xml?
Find this section:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
And change it to this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
[B][COLOR=Blue]<group gid="media_rw" />[/COLOR][/B]
</permission>
Check permissions on platform.xml after editing and fix if needed. Reboot.
blindmanpb said:
Have you tried manually editing /system/etc/permissions/platform.xml?
Click to expand...
Click to collapse
[SNIP]
Yes - I checked SDFix after running it, and platform.xml had already been correctly edited. Thanks for the suggestion though.
Have you tested this SD card in other devices, and other SD cards in this device?
Caveman6 said:
Hi,
I hope someone has suggestions on the following issue. I've searched threads, but haven't found this specifically.
I need the ability to R/W with multiple programs to my SD card. Due to work and also teaching concerns, I need to access directories of ebooks, articles and databases that are large and in the past were synced from the cloud to my device. Obviously KitKat makes an issue of this.
I recently obtained a Samsung Galaxy Note 10.1 2014 P600. Refurbished by the manufacturer. This has only a one-month warranty so rooting wasn't a concern.
1. I rooted the device using CF Autoroot. Rooting was confirmed by Root Checker.
2. I ran SDFix. No joy. Access to the SD card was sporadic - for example - music on the card would only play 2 seconds of each song.
Edit: This ROM would be a good fit for you it has all of the stock features plus some also the ability to read and write to the SD card. http://forum.xda-developers.com/showthread.php?t=2793898
3. Using Titanium Backup, I froze all Knox-related programs (this was more than the list of 6 I think. I can provide a list later.) Later, I also backed-up and deleted the programs.
Access to the SD card was still sporadic. After a reboot, I might have access for a few minutes, and then restricted access again.
4. I then tried Xposed Framework and the "Handle External Storage" module (see the 3rd method in this article http://technofaq.org/posts/2014/04/fixing-external-sd-card-write-issue-on-android-kitkat/). This worked but still had issues - I had drive access but from time to time it would disappear - it would seem to randomly unmount.
5. But, I decide to keep trying and in the process went to create a folder with File Explorer. FX gave me a message about KitKat - and asked if I wanted to configure it to try to write to the SD card under KitKat. I said yes - and suddenly I cannot access the drive at all.
Android Version 4.4.2
Kernel Version 3.4.39-1462259
Build Number: KOT49H.P600UECNK1
SE for Android Status Enforcing SEPF_SM-P600_4.4.2_0032
The SD card is a Sandisk 128GB.
I haven't tried flashing another ROM because I also need S-Pen and Chromecast functionality - so I just didn't want to fool with it.
1. Does anyone have any suggestions to get SD card RW access?
2. If "No" to the above, what is a good stock ROM with S-Pen and Chromecast functionality that has already addressed the SD issue that I can flash (and where is it located)?
Thank you all for your help.
Click to expand...
Click to collapse
Take a look at this thread http://forum.xda-developers.com/showthread.php?t=2741914. It looks like 128Gb SD card only works with 4.3
Edit: Try this ROM it should have RW to SD card. Along with S-Pen and Chromecast ability because it is stock based.
http://forum.xda-developers.com/showthread.php?t=2793898
Sent from my SM-P600 using XDA Free mobile app
Thank you for the prior comments. Due to work and the holidays I wasn't able to reply prior to now.
It turns out the issue was my attempt at using a 128GB card- the Samsung Note 10.1 2014 can apparently only handle up to a 64GB card.
Out of curiosity, has anyone found a way to root and reset KNOX to 0?
Orion116 said:
Take a look at this thread http://forum.xda-developers.com/showthread.php?t=2741914. It looks like 128Gb SD card only works with 4.3
Edit: Try this ROM it should have RW to SD card. Along with S-Pen and Chromecast ability because it is stock based.
http://forum.xda-developers.com/showthread.php?t=2793898
Sent from my SM-P600 using XDA Free mobile app
Click to expand...
Click to collapse
128GB cards do not work with 4.3. I have 4.3 and have tested four different Sandisk 128gb cards in fat32 and Exfat and no luck. Only 64gb works with 4.3 and this was confirmed with Best Buy demo units as well (pre 4.4 update of the demos course).
Caveman6 said:
Thank you for the prior comments. Due to work and the holidays I wasn't able to reply prior to now.
It turns out the issue was my attempt at using a 128GB card- the Samsung Note 10.1 2014 can apparently only handle up to a 64GB card.
Out of curiosity, has anyone found a way to root and reset KNOX to 0?
Click to expand...
Click to collapse
from what I know and read once knox is tripped you cant reset it. I think you can root without tripping it but just cant reset it.
It's a one-way trip!
mikep2323 said:
from what I know and read once knox is tripped you cant reset it. I think you can root without tripping it but just cant reset it.
Click to expand...
Click to collapse
Right! The problem is that "tripping" knox actually changes the hardware. It burns out a fusible link which, of course, can't be un-burnt.
Caveman6 said:
Thank you for the prior comments. Due to work and the holidays I wasn't able to reply prior to now.
It turns out the issue was my attempt at using a 128GB card- the Samsung Note 10.1 2014 can apparently only handle up to a 64GB card.
Out of curiosity, has anyone found a way to root and reset KNOX to 0?
Click to expand...
Click to collapse
Good news! The issue I was having was with the SPECIFIC 128 GB card. I tried a PNY 128GB card instead, and it is working perfectly.
I've had this issue for a while since installing NB4 rooted on my phone. Can't seem to get downloads from Chrome (or any other browser) to save to my device.
Also having a weird and possibly related issue with my camera apps (Google Camera and Camera Zoom FX), neither is saving any image captures. Camera Zoom is returning "Error Code 2" pertaining to my SD card.
I fear this may be a SD card permissions bug that I triggered when trying to troubleshoot a nandroid restore issue via doing a "Fix SD Card Permissions".
I've tried the platform.xml fix for <group gid="media_rw" />.
Trying to avoid starting fresh...help please?
Thank you in advance for your feedback.
Bump.
Has anyone come across this issue?
Hope I'm not repeating a question here. I couldn't find anything in this forum. I just finished updating my international m8 to lollipop ota. After installing titanium backup from the market, I noticed my previous backup on ext_sd are reported as not writable by titanium. I was under the impression that the new android L would rectify this Kitkat issue. Is there any work around for this issue yet? Thanks.
So I found a test version of titanium backup for Lollipop http://bit.ly/1v0njNa. Unfortunately I'm getting Documents crashes when I selected the extsd after switching to documentprovider storage. So I'm still unable to assign the backup directory to my external sd. Any input would be appreciated. Thanks!
mateenf said:
Hello All,
Since kitkat 4.4.2 was released on the Galaxy Note 3, many users were unable to write files to the External SD Card. Below is a simple fix for rooted users on the Galaxy Note 3 N9005 ( International Snapdragon Variant).
**Please be advised that I have only tested this on my personal N9005. However, you are free to test it on your own devices at your own risk!! **
1. Using a root-enabled file manager, navigate to /system/etc/permissions
2. Edit platform.xml and find the WRITE_EXTERNAL_STORAGE permission.
3. Add an additional group definition for this permission...<group gid="media_rw" />
4. Save the changes to the file.
5. Restart.
Attached is a copy of my platform.xml.
Click to expand...
Click to collapse
Thread link forum.xda-developers.com/showthread.php?t=2617921
Working ok.
Thanks for the reply. I did use that solution when I was on 4.4 but lollipop has a different documentprovider solution now. I finally figured out what was happening. The issue isn't with titanium backup up but with how documentprovider was accessing my ext_sd. For some reason the documents will crash if I left ext_sd unnamed. I ended resolving the issue by naming my sdcard and it's been working as expected. Weird little bug in lollipop... In addition to the DNS issue.
Thanks for that solution. I had the same issue.
After naming the SD card using my laptop, the HTC Documents application no longer crashed and I can allow write access to the application (ES fileexplorer in my case.).
I guess it is an HTC bug, the documentsprovider shows the label/name of the ext SD card on the button to be pressed to allow access, and apparently it can't handle an empty SD card name.
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