So based on what I have read so far, KitKat has protections for apps writing to the external microSD card. An example of how you might "fix" this:
http://forum.xda-developers.com/showthread.php?t=2617921
However, the M8 also protects the system directory, so we cannot write to it. Kind of a catch-22, no?
So, my questions are:
1) Do we think we will be able to remove the system protection?
2) Will that then allow us to let apps write to the microSD card?
gjlowe said:
So based on what I have read so far, KitKat has protections for apps writing to the external microSD card. An example of how you might "fix" this:
http://forum.xda-developers.com/showthread.php?t=2617921
However, the M8 also protects the system directory, so we cannot write to it. Kind of a catch-22, no?
So, my questions are:
1) Do we think we will be able to remove the system protection?
2) Will that then allow us to let apps write to the microSD card?
Click to expand...
Click to collapse
You will have to root and edit the system permissions file as shown in that link. I did it with my GS4, and it worked perfectly! It allows any app to write to external SD.
SolarTrans said:
You will have to root and edit the system permissions file as shown in that link. I did it with my GS4, and it worked perfectly! It allows any app to write to external SD.
Click to expand...
Click to collapse
I have used ES File Explorer with root enabled, but it won't let me write to system due to the other issue I mentioned.
I used it too. You have to enable root access for the app (within its settings), then for the specific permissions folder itself (also within the app). You've gotta make sure it has permission to write in both of those settings as well.
Sent from my iPad using Tapatalk
I am not following...I did set root Explorer for the app, but I cannot modify anything, including permissions for the folder because I cannot modify the contents of /system
Sent from my HTC One_M8 using Tapatalk
U can bypass system write protection by using adb from within custom recovery (TWRP) and issue this command
adb shell
mount /system/
djkinetic said:
U can bypass system write protection by using adb from within custom recovery (TWRP) and issue this command
adb shell
mount /system/
Click to expand...
Click to collapse
Perfect! Thank you sir! So to continue this thought, if it can be done in recovery, are we just waiting for a method to do this live in a fully booted system?
gjlowe said:
Perfect! Thank you sir! So to continue this thought, if it can be done in recovery, are we just waiting for a method to do this live in a fully booted system?
Click to expand...
Click to collapse
basically we need an insecure kernel/module/boot.img as far as i know there is one out but only for dev/testing purposes, i think in order to get a proper one we first need kernel source to drop, i'm no dev so I could be wrong.
gjlowe said:
So based on what I have read so far, KitKat has protections for apps writing to the external microSD card. An example of how you might "fix" this:
http://forum.xda-developers.com/showthread.php?t=2617921
However, the M8 also protects the system directory, so we cannot write to it. Kind of a catch-22, no?
So, my questions are:
1) Do we think we will be able to remove the system protection?
2) Will that then allow us to let apps write to the microSD card?
Click to expand...
Click to collapse
I applied this fix on my LG GPad GPe which had 4.4 stock and didn't support RW to the external sdcard. Yes it does require root in order to access and edit that file to change permissions, but its ridiculous how editing one line of code will fix this problem, now I can read/write and even write data directly to my extsd card and save TWRP backups to ext memory no problem.
I plan to do the same once I get and root my GPe M8
Sent from my LG-V510 using Tapatalk
gjlowe said:
I am not following...I did set root Explorer for the app, but I cannot modify anything, including permissions for the folder because I cannot modify the contents of /system
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I may be able to help further once I get my M8 this Friday, but as of now I don't have an Android device to use and guide you through with. It took me a lot of messing around, and there was some menu in the app past the general root access one that changed permissions of a few folders (/system and a couple others). It looks like the ADB method above helped though so hope you're up and going!
Sent from my iPhone 5s using Tapatalk
Here's how i managed to apply the "fix" to platform.xml, this will require root at the very least.
I navigated to /system/etc/permissions/ and copied platform.xml from there to the internal SD, then i opened it with solid explorer's built in text editor, though i think any editor will do, and changed it like this:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.WRITE_MEDIA_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Saved the file, and rebooted in to TWRP.
Once in TWRP i mounted the system partition, then used the file manager under advanced. Navigated to /system/etc/permissions/ again and renamed permissions.xml to permissions.xml.bak so that i'd have a backup right there in the same directory. Next I used the file manager and copied the permissions.xml that i modified and saved earlier to the internal SD back in to /system/etc/permissions/. Finally i used the chmod functionality in the file manager and did a chmod 644 to it. Booted in to android and tried to copy a file from the internal SD to the external SD and everything seems to have worked fine.
While i was in there i moved some of the bloatware off the priv-app folder in /system so it wouldn't keep trying to reinstall lumen and it's bushel of crap every time i reboot. I think its also possible to get rid of or change the boot sound via TWRP file manager but i haven't tried yet.
Sorry if all that was a jumble and hard to understand, i can reword it if necessary.
lacrossev said:
Here's how i managed to apply the "fix" to platform.xml, this will require root at the very least.
I navigated to /system/etc/permissions/ and copied platform.xml from there to the internal SD, then i opened it with solid explorer's built in text editor, though i think any editor will do, and changed it like this:
Saved the file, and rebooted in to TWRP.
Once in TWRP i mounted the system partition, then used the file manager under advanced. Navigated to /system/etc/permissions/ again and renamed permissions.xml to permissions.xml.bak so that i'd have a backup right there in the same directory. Next I used the file manager and copied the permissions.xml that i modified and saved earlier to the internal SD back in to /system/etc/permissions/. Finally i used the chmod functionality in the file manager and did a chmod 644 to it. Booted in to android and tried to copy a file from the internal SD to the external SD and everything seems to have worked fine.
While i was in there i moved some of the bloatware off the priv-app folder in /system so it wouldn't keep trying to reinstall lumen and it's bushel of crap every time i reboot. I think its also possible to get rid of or change the boot sound via TWRP file manager but i haven't tried yet.
Sorry if all that was a jumble and hard to understand, i can reword it if necessary.
Click to expand...
Click to collapse
You can, I removed the boot up sound by using the file manager in recovery mode. It's found here: system/customize/resource/HTC_Sense5_Boot.mp3
Edit:
I followed your steps and now I am able to write to my SD card with no problem. Thanks!
Hello.
Thank you lacrossev for the steps you have provided, but unfortunately they don't seem to work for me.
I have the international, carrier-free One M8. Perm-rooted it today and installed TWRP, but I am still on the stock ROM. The problem seems to be that the platform.xml file is restored to the original version on every reboot. I even tried to chmod 0444 it, so that nobody can overwrite it, but it didn't do the trick. I cannot figure out where the file is being restore from.
Any clues? Thanks in advance to anybody who will help.
Also thank you Bachatu, I replaced the startup sound with Windows 2000's startup sound.
I have followed them carefully, but the file keeps being reverted
I change my permison.xml file like this
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
[B]<group gid="media_rw" />[/B]
</permission>
<permission name="android.permission.WRITE_MEDIA_STORAGE" >
[B]<group gid="sdcard_rw" />[/B]
<group gid="media_rw" />
</permission>
give a permision to file 644 like in instructions but nothing. Still phone crash when I try move a file to system directory from internal_sd.
I have cid_032 and 1.54.401.10 version
I have write access to the ex sd without making modifications to the xml file. Also have apps writing to the ex sd card too.
I don't have <group gid="media_rw" /> under WRITE-EXTERNAL_STORAGE nor do I have <group gid="sdcard_rw" /> under WRITE_MEDIA_STORAGE.
ashyx said:
I have write access to the ex sd without making modifications to the xml file. Also have apps writing to the ex sd card too.
I don't have <group gid="media_rw" /> under WRITE-EXTERNAL_STORAGE nor do I have <group gid="sdcard_rw" /> under WRITE_MEDIA_STORAGE.
Click to expand...
Click to collapse
I try two version from other post with add to WRITE-EXTERNAL_STORAGE <group gid="sdcard_rw" /> and without and still nothing.
Thank you so much.
I spent a long time trying this out... and found where I was going wrong in reading the description.
To everyone else who's trying to do this...
Please note the following...
You need to COPY partition.xml from M8's internal sd to the external micro sd card then modify it there.
Then when you go into TWRP, you then rename the M8's internal sd copy of "partition.xml" to "partition.xml.bak"... only then, you copy the modified file for "partition.xml" from the external micro sd card back into M8's internal sd at /system/etc/permissions....
They key here is to note that when the author refers to internal sd..... he really means the external micro sd card.
Good luck everyone, I can get back to using quickpic.
lacrossev said:
Here's how i managed to apply the "fix" to platform.xml, this will require root at the very least.
I navigated to /system/etc/permissions/ and copied platform.xml from there to the internal SD, then i opened it with solid explorer's built in text editor, though i think any editor will do, and changed it like this:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
<permission name="android.permission.WRITE_MEDIA_STORAGE" >
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Saved the file, and rebooted in to TWRP.
Once in TWRP i mounted the system partition, then used the file manager under advanced. Navigated to /system/etc/permissions/ again and renamed permissions.xml to permissions.xml.bak so that i'd have a backup right there in the same directory. Next I used the file manager and copied the permissions.xml that i modified and saved earlier to the internal SD back in to /system/etc/permissions/. Finally i used the chmod functionality in the file manager and did a chmod 644 to it. Booted in to android and tried to copy a file from the internal SD to the external SD and everything seems to have worked fine.
While i was in there i moved some of the bloatware off the priv-app folder in /system so it wouldn't keep trying to reinstall lumen and it's bushel of crap every time i reboot. I think its also possible to get rid of or change the boot sound via TWRP file manager but i haven't tried yet.
Sorry if all that was a jumble and hard to understand, i can reword it if necessary.
Click to expand...
Click to collapse
htc 816
hi, my phone is htc desire 816 dual sim
i change the platform.xml file but in reboot its change to original file. even i deleted platform.xml file and my phone restart at the time and when start again every thing come back!!
please help me, i want to use gl to sd and other app on my device, its so bad google! u downgrade ur OS!!!!
sina_alone said:
hi, my phone is htc desire 816 dual sim
i change the platform.xml file but in reboot its change to original file. even i deleted platform.xml file and my phone restart at the time and when start again every thing come back!!
in TWRC file manager replaced platform.xml and its work!!!!! I do it!!!!
Click to expand...
Click to collapse
Related
I'm on rooted stock ND8. As I expected there are a few apps that don't want to write to the ext card because of the new permissions required by KitKat. One deveoper (rerware...MyBackup Pro) suggests that if I want to use the ext card for backups I edit the permissions for the ext card. They were even kind enough to send me instructions, which I've posted below.
Their argument was that because of the sandboxed nature of the data on the ext card, if they allowed ext card storage using the standard KitKat permissions it would be to easy for the system to delete the data if the app is uninstalled or an upgrade fails. I see their point.
My question is...Is this a good idea? Am I opening up the ext card to easy hacking? Is this just setting the permissions to where they were in Jellybean?
Thanks
Instructions:
1- Using a root-enabled file manager, navigate to /system/etc/permissions
2- Edit platform.xml
3- <permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
< group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
4- save and restart
Here's a good read on it: http://m.androidcentral.com/kitkat-sdcard-changes
I will personally be doing it as I don't keep any sensitive information anywhere near my phone to begin with.
This is absolutely the best info on this issue! I was getting pretty frustrated with how 4.4 handles the ext sdcard but now all is well. :thumbup::beer:
poit said:
I'm on rooted stock ND8. As I expected there are a few apps that don't want to write to the ext card because of the new permissions required by KitKat. One deveoper (rerware...MyBackup Pro) suggests that if I want to use the ext card for backups I edit the permissions for the ext card. They were even kind enough to send me instructions, which I've posted below.
Their argument was that because of the sandboxed nature of the data on the ext card, if they allowed ext card storage using the standard KitKat permissions it would be to easy for the system to delete the data if the app is uninstalled or an upgrade fails. I see their point.
My question is...Is this a good idea? Am I opening up the ext card to easy hacking? Is this just setting the permissions to where they were in Jellybean?
Thanks
Instructions:
1- Using a root-enabled file manager, navigate to /system/etc/permissions
2- Edit platform.xml
3- <permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
< group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
4- save and restart
Click to expand...
Click to collapse
And yes, this'll just put the SD card back where it was before KitKat.
Sent from my Sprint Samsung Galaxy SIII with M.O.A.R. v9.0, dkp kernel dated 3/20/2014 and TWRP v2.7.0.0.
I have a N7100 Galaxy Note 2 with the latest official firmware 4.4.2 stock.
I followed these two guides to root and enable screen mirroring.
Everything worked perfectly!
Later, with ES File Explorer I edit "platform.xml" to fix writing permissions on the microsd and I added "<group /> gid="media_rw" />" under "WRITE_EXTERNAL_STORAGE"
After reboot problems begin, all apps are unusable, inaccessible internal and external memory.
With ES File Explorer I restore "platform.xml" as the original file but problems persist.
Now, only sms and phone work.
Why? How can I fix this problem?
Has Knox locked my smartphone?
campotino said:
I have a N7100 Galaxy Note 2 with the latest official firmware 4.4.2 stock.
I followed these two guides to root and enable screen mirroring.
Everything worked perfectly!
Later, with ES File Explorer I edit "platform.xml" to fix writing permissions on the microsd and I added "<group /> gid="media_rw" />" under "WRITE_EXTERNAL_STORAGE"
After reboot problems begin, all apps are unusable, inaccessible internal and external memory.
With ES File Explorer I restore "platform.xml" as the original file but problems persist.
Now, only sms and phone work.
Why? How can I fix this problem?
Has Knox locked my smartphone?
Click to expand...
Click to collapse
I am not at my PC to look into my platform.xml so I can only suspect that your command is wrong and it should be: <group gid=”media_rw” />
Androidwizzard said:
I am not at my PC to look into my platform.xml so I can only suspect that your command is wrong and it should be: <group gid=”media_rw” />
Click to expand...
Click to collapse
I agree. If in fact you entered <group /> gid="media_rw" /> in system/etc/permissions/platform.xml, that is most likely your problem. All the posts I have read concur with Androidwizzard. I have also read that the permissions for that file should be 0644 or rw-r--r--. These can be set in Root Explorer.
Not that this has solved the problem with my Note II, but you at least have a clear error in your string. My platform.xml file is correct and non-rooted apps still can't access my extSdCard. TiBU and Root Explorer can access it without issue.
On a side note, this platform.xml file is found in 2 places: system/etc/permissions/platform.xml AND /etc/permissions/platform.xml. Is this just a mirroring thing that Android does? It appears that changes made to one appear in the other...
Some people in this thread are reporting success using FolderMount from the Play store. When you launch this app it will detect errors in your file system and make changes to /system/bin/sdcard. This change alone is supposedly enough to enable your apps to access the SD card. But it did not work for me.
I sure am hoping we can find a good solution!
any fix for this ?? what is the owner file of platform.xml actually ? is it root or system ?
another thing about the /system/etc/permission is it same with /etc/permission ??
never know this small 7kb file can messed up phone quite bad.
I solved problem with Wipe facrtory reset!
After this, I repeat root on android 4.4.2 and with SD fix, downloaded to playstore, i fix write permission on external sd card.
Now my Note 2 work fine
thanks for the reply. it seems factory default is the last resort. lesson learned. never messed with platform.xml. hahah.
I am trying to change the permissions under platform.xml so I can access the sd card with TitaniumBackup.
I installed the SDFix app and it seemed to have worked, I can delete files and stuff from the SD Card, however TitaniumBackup still couldn't backup directly into the SD Card.
I found that under the platform.xml I only had <group gid="sdcard_r" /> and <group gid="sdcard_rw" /> but not <group gid="media_rw" /> so I tried to add the media part into the file.
I am rooted and I do successfully change the file (tried with Root Explorer and Total Commander), but every time after I reboot the file changes back to the original.
I tried searching online for this but couldn't seem to find any information on this.
Thanks in advance!
Your device needs to be rooted
1. Open any files manager of your choice and make sure it runs with superSU/superuser permissions.
2. Mount your system partition as R/W to perform any changes.
3. Navigate to the /system/etc/permissions/ folder and look for the platform.xml.
4. Make backup of platform.xml.
5. Open the platform.xml file with any text editor on your device and search for the following line:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
6. And change it to this:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
[COLOR="Red"]<group gid="media_rw" />[/COLOR]
</permission>
7. Save it and set permission rw-r-r
8. Reboot
Note: If any problems occur just delete platform.xml and restore the backup file.
rer3 said:
Your device needs to be rooted
1. Open any files manager of your choice and make sure it runs with superSU/superuser permissions.
2. Mount your system partition as R/W to perform any changes.
3. Navigate to the /system/etc/permissions/ folder and look for the platform.xml.
4. Make backup of platform.xml.
5. Open the platform.xml file with any text editor on your device and search for the following line:
Note: If any problems occur just delete platform.xml and restore the backup file.
Click to expand...
Click to collapse
thanks for the tuts , i did this using sdfix kitkat app from playstore
Hi, I tried Foldermount, the first time I opened aplied the fix, rebooted, a thats all
I did this process, however not correct this error, when I copy some damp pc for external memory of my Z3c, the unit not play the file.
If I copy the internal memory to the outside also does not work.
How to solve?
iedafarha said:
thanks for the tuts , i did this using sdfix kitkat app from playstore
Click to expand...
Click to collapse
Dany MID Zero said:
Hi, I tried Foldermount, the first time I opened aplied the fix, rebooted, a thats all
Click to expand...
Click to collapse
well, there's always an alternative.
pedro5148 said:
I did this process, however not correct this error, when I copy some damp pc for external memory of my Z3c, the unit not play the file.
If I copy the internal memory to the outside also does not work.
How to solve?
Click to expand...
Click to collapse
to be honest I don't really understand what you're saying.
I did all the steps and now all the 3rd party apps (eg: titanium backup, airdroid) on my LP Z3 could write on ext sd card.
Sent from my D6603 using XDA Free mobile app
I can also write to the SD card, but music and videos are corrupted.
pedro5148 said:
I can also write to the SD card, but music and videos are corrupted.
Click to expand...
Click to collapse
well let me put it clear what this this tutorial will do.
If you try to copy songs or videos from your PC via airdroid (which is 3rd party app) to ext sd card, kitkat rom or above will prevent it to happen. After you did this tutorial, kitkat rom or above won't prevent it. If your songs or videos get corrupted the problem are (might be) the files. I've tested it myself and nothing get corrupted.
thanks bro for the tut.
i used sdfix in kitkat, and in lollipop too when update, but everytime i restore app from TB (i make backup folder location in sd card) always got bootloop.
i don't know if sdfix isn't compatible yet with lollipop or not, so i don't instal it again.
now i use your tutorial, and everything works like a charm :good:, but maybe for now i wont make backup folder location in sd card, at least now i can use xposed obb on sd card :laugh:
------
btw, si agan orang bandung? :laugh:
gundam_warlock said:
thanks bro for the tut.
i used sdfix in kitkat, and in lollipop too when update, but everytime i restore app from TB (i make backup folder location in sd card) always got bootloop.
i don't know if sdfix isn't compatible yet with lollipop or not, so i don't instal it again.
now i use your tutorial, and everything works like a charm :good:, but maybe for now i wont make backup folder location in sd card, at least now i can use xposed obb on sd card :laugh:
------
btw, si agan orang bandung? :laugh:
Click to expand...
Click to collapse
Well life is getting so much easier with this fix, lol.
------
yoi gan
after editing i can't save it. dont know what happens, sony E3 rooted with lock bootloader .
Great work
anhtu_1990 said:
after editing i can't save it. dont know what happens, sony E3 rooted with lock bootloader .
Click to expand...
Click to collapse
you could try editting it in notepad++ and then push it back inside system.
Sent from my D6653 using XDA Free mobile app
I used NEXTAPP SDFIX app from the Google Play store. It took about 5 seconds. Must have root. No issues.
Im on a Z3 D6616 with OEM 4.4.4 locked bootloader.
Man, this is awesome. I don't like installing apps to do this kind of things.
THANK YOU
Edit: I'll keep testing the apps, if any trouble show up I'll tell you.
Doesn't work on my xperia z3 stock rom 4.4.4.
Followed the instructions succesfully but after rebooting i still cant move apps to sd.
That button isn't there under app info in settings
Nagaeh said:
Doesn't work on my xperia z3 stock rom 4.4.4.
Followed the instructions succesfully but after rebooting i still cant move apps to sd.
That button isn't there under app info in settings
Click to expand...
Click to collapse
Have you already made a check on platform.xml after the reboot, if the changes you made (see startpost no. 5. and 6.) are really saved? Did you already check the permissions of platform.xml as per description (rw-r-r)? If yes, reboot your device again and give it another try!
Just install this application, it makes this whole process.
Obviously, you must have root access.
https://play.google.com/store/apps/details?id=nextapp.sdfix
Thanks.
Nice work.
I tried doing it with the SD fix app as well as doing it manually with a root explorer.
Neither works.
I can see that the file is succesfully saved and the permission is set to rw-r-r- but nothing happens
Worked for me, thx for the tutorial
HTC One M9+ plus Android 5.0.2 Sense 7.0 Stock ROM 1.88.707.1
I want to write and modify files to my external 128gb SD Card I installed, I noticed that ES File Explorer cant write or modify it. Its not the card a 64GB card I tried had the same problem
Both work fine for read but no modify/write possible
My phone is not rooted and I dont want to root it as I use it for sky go, mobile banking etc and these will stop if I root it
HTC own file manager can modify / write to the external SD
ES File explorer askes me to get to root directory to give it permission but but it doesnt show up there
Only the Internal SD shows so I cant do that
When I go back to using ES File explorer the external SD shows up as normal but again no write or modify access
What can I do?
Help much appreciated
Thanks
Update - Tried many different file managers all with same result - no access to modify or write
Only HTC own file manager has permissions. Maybe this is something in Sense 7 as I have a M9+.
I have the same problem with the same phone
dachat said:
Update - Tried many different file managers all with same result - no access to modify or write
Only HTC own file manager has permissions. Maybe this is something in Sense 7 as I have a M9+.
Click to expand...
Click to collapse
I have the same problem with the same phone / HTC M9 PLUS
icincan said:
I have the same problem with the same phone / HTC M9 PLUS
Click to expand...
Click to collapse
If your phone is rooted you need to modify platform.xml to add permissions to allow apps to write to external SD.
/system/etc/permissions/platform.xml
look this section it should look like below
<permission
name="android.permission.WRITE_EXTERNAL_STORAGE"
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permision>
Make sure to backup the file before editing.
http://forum.xda-developers.com/showpost.php?p=20869996&postcount=7
You could try to temproot your phone by using kingroot and then you could make the modification dratsablive suggested you.
Check this guide out.
THX for responding!
But I understood that with Android 5 you could write to sd without need it to root.!
I have a halfway issue with the m9. I can read, write, edit on ext_sd card just fine but apps cannot directly save to ext_sd.
Another crap htc feature.
I wish I stole my HTC M9.
It may be the rom. I've never had an issues writing to my sdcard. I have TiBu set up to use it for backups and never had to change any permissions to do it.
There are apps that will fix this issue if you're rooted. I had to do it on my LG G-Pad to allow app access to ext_sd.
iElvis said:
It may be the rom. I've never had an issues writing to my sdcard. I have TiBu set up to use it for backups and never had to change any permissions to do it.
There are apps that will fix this issue if you're rooted. I had to do it on my LG G-Pad to allow app access to ext_sd.
Click to expand...
Click to collapse
I'm sure that the real problem is the rom but its frustrating because it is the original stock rom and the phone is neverlocked. The only file manager usable is the original HTC file manager. No es file explorer and no Astro. I had many HTC.s but this new one , HTC M9+, is the first that I remarked that includes his own file manager. Maybe is valable only for the HTC M9+ and not for M9.
Crap !
dratsablive said:
If your phone is rooted you need to modify platform.xml to add permissions to allow apps to write to external SD.
/system/etc/permissions/platform.xml
look this section it should look like below
<permission
name="android.permission.WRITE_EXTERNAL_STORAGE"
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permision>
Make sure to backup the file before editing.
http://forum.xda-developers.com/showpost.php?p=20869996&postcount=7
Click to expand...
Click to collapse
I have the same problem on the HTC M9+. Using Cleanslate Europe 1.2.3, Rooted.
Tried this approach, but apps still can't write to SD Card.
File Manager (incorporated in ROM) is the only one that has access to SD.
Litronius said:
I have the same problem on the HTC M9+. Using Cleanslate Europe 1.2.3, Rooted.
Tried this approach, but apps still can't write to SD Card.
File Manager (incorporated in ROM) is the only one that has access to SD.
Click to expand...
Click to collapse
I remember ages ago being prompted for es file explorer to read and write to external. I had to manually point to the card and hit "open" via the system file browser. Es file Explorer has been able to read and write the external card without problems ever since.
If you swap cards often you might have issues..
Beamed in by telepathy.
shivadow said:
I remember ages ago being prompted for es file explorer to read and write to external. I had to manually point to the card and hit "open" via the system file browser. Es file Explorer has been able to read and write the external card without problems ever since.
If you swap cards often you might have issues..
Beamed in by telepathy.
Click to expand...
Click to collapse
Yes, this is how it supposed to work, but for some reason, the SD card doesn't appear on Es Explorer. It seems more a problem of permissions. Maybe a ROM bug?