Related
Im having some serious trouble with loading a recovery image (recovery-RA-heroc-v1.5.2.img) onto my Hero. The device successfully roots but I just cant push the recovery image.
I know you are supposed to enable debugging after you mount the sd card, however, whenever i try to enable debugging with the sd card mounted it automatically ejects the drive. Anyone know how I can fix this? Ive tried a factory reset and I've erased and reformatted my sd card multiple times, but nothing fixes this. Ive rooted a Hero before which is why this is so frustrating, i just cant figure it out.
Here is the terminal error:
Eric-Highleys-MBP:tools erichighley$ ./adb push recovery-RA-heroc-v1.5.2.img /sdcard/
failed to copy 'recovery-RA-heroc-v1.5.2.img' to '/sdcard//recovery-RA-heroc-v1.5.2.img': Permission denied
Eric-Highleys-MBP:tools erichighley$
Eric-Highleys-MBP:tools erichighley$ ./adb shell
$
booyakasha said:
Im having some serious trouble with loading a recovery image (recovery-RA-heroc-v1.5.2.img) onto my Hero. The device successfully roots but I just cant push the recovery image.
I know you are supposed to enable debugging after you mount the sd card, however, whenever i try to enable debugging with the sd card mounted it automatically ejects the drive. Anyone know how I can fix this? Ive tried a factory reset and I've erased and reformatted my sd card multiple times, but nothing fixes this. Ive rooted a Hero before which is why this is so frustrating, i just cant figure it out.
Here is the terminal error:
Eric-Highleys-MBP:tools erichighley$ ./adb push recovery-RA-heroc-v1.5.2.img /sdcard/
failed to copy 'recovery-RA-heroc-v1.5.2.img' to '/sdcard//recovery-RA-heroc-v1.5.2.img': Permission denied
Eric-Highleys-MBP:tools erichighley$
Eric-Highleys-MBP:tools erichighley$ ./adb shell
$
Click to expand...
Click to collapse
you cant have the card mounted and have it debugging at the same time once you mount the card it treats it just like any other removable storage device.
wtphoto said:
you cant have the card mounted and have it debugging at the same time once you mount the card it treats it just like any other removable storage device.
Click to expand...
Click to collapse
so when i go to push the recovery i dont mount the sd card (i.e. no drive visibile on the desktop), just enable debugging?
wtphoto said:
you cant have the card mounted and have it debugging at the same time once you mount the card it treats it just like any other removable storage device.
Click to expand...
Click to collapse
shiiiiit i think that worked....ive only been trying to figure this out for 4+ hours. thanks a lot man
booyakasha said:
shiiiiit i think that worked....ive only been trying to figure this out for 4+ hours. thanks a lot man
Click to expand...
Click to collapse
lol no problem I made the same mistake the first coiple times I re-rooted my phone.
Hey guys I am new just got the tablet yesterday. My question is how can I save things like kernels and things to my SD card? It saves yo internal storage and then from there I try n use astro file manager to move it to external from the mnt section but it lets my see the external card it just wont allow me paste it there I had to put SD in my Atrix and then do it and then have to out it back in the a500. Thank u I am rooted using the minimalist rom
Sent from my Motorola Atrix 4G MB860 using XDA Premium App
I have same issue.
i Just re-bought my Iconia last night. I rooted this unit for the first time soon after (MinimalistRom). I see the same thing your seeing. Internal memory is seen as sdcard and my added MicroSD is read as external1. External2 I have to assume would be storage connected to usb connection. Yes i cant copy files over to microsd (external1) from internal (so called SDCard). I'm going to try giving permissions to that xternal1 mnt folder using es explorer like i read in other earlier topic. Ill try to post what i find out.
make sure your tab is rooted then either use es file explorer or root explorer and it will work just fine. I don't think astro can manage it.
I couldnt figure it out. Got to the point of instaling superuser, busybox, super manager and ghost commander. Got every thing, i guess, somewhat hooked up. But in super manager's file explorer, i could get it to chmod rwe on owner --- and other r-e. Group had everything checked rwe. I guess there is something else i'm missing here to change this directories permission. So I'm stumped at the moment and re-image with another rom to see if it correct the mounting of this microsd card external1. Sure would like to figure this out to have app manager send app2sd to my microsd class 10 card on external1.
Sauyai1 said:
I couldnt figure it out. Got to the point of instaling superuser, busybox, super manager and ghost commander. Got every thing, i guess, somewhat hooked up. But in super manager's file explorer, i could get it to chmod rwe on owner --- and other r-e. Group had everything checked rwe. I guess there is something else i'm missing here to change this directories permission. So I'm stumped at the moment and re-image with another rom to see if it correct the mounting of this microsd card external1. Sure would like to figure this out to have app manager send app2sd to my microsd class 10 card on external1.
Click to expand...
Click to collapse
"I could get it to chmod rwe on owner.." ....couldn't get it to chmod rwe...
That's why we need the DEVs to tear this script apart and make it works with custom roms
http://forum.xda-developers.com/showthread.php?t=1175342
so far, no taker
bump it to the top once in awhile if you can
~~~
Hi,
Just Got the 7.7 3g - so far so good. Screen is as good as they say
The extra resolution defn. helps with web browsing.
Not finding any lag really.
7.7 is just about the limit for my two handed use but i would say the original 7" was a wee bit easier to handle but something with time should become more intuitive.
Just a few issues - external sd card is somewhat limited. Might be deliberate by Samsung but does not make sense.
Normal user apps cant access to the external sdcard. Using connect bot, i checked permissions and it seems that it is mounted by the os with system permissions, where as the internal sdcard is mounted as sd_rw.
This can't be correct? The only way to copy stuff to it is to use the samsung system file explorer as it has system permissions So copy to internal first then to external - this sounds like a bug?
I have not rooted this yet - might then chown to sd_rw get rid of this ?? There is a lot of entries in the vold.fstab to make sense of. Not a hacker so just looking around. A bit too early to start soft-bricking
But I take these don't have protected bootloaders so thats why we can root ?
Video playback is v.good but I am not able to throw on a bluray m2ts file (obviously with the sd card issue) and play smoothly. I found Dice player can handle m2ts by renaming it to a ts file. It then can use hardware decoding. Still drops frames but still watchable to a certain degree. For all other files mx player is still best. I have lossy transcoded some "native" blurays clips and seems that it handle high profile h264 1080p at high bitrates very well. Hoping, formatting sd card ext3/ext4 will improve things.
On the whole very impressive device - plus more ics goodies to come soon hopefully.
I've noticed some issues with the external SD card as well. Only the stock file manager can copy files from the internal storage to the external storage. I was able to transfer files to the ext. SD via Dooblou's Wifi Explorer, though. Although that would crap out a few times.
I'm hoping that we see some new ROMs with a different file system at any rate. The 4GB limit is so 1998.
Fix for external sd write issue
I've already posted a fix for this in our original thread?
davp said:
There is a fix for the write to external storage in this thread:
Samsung Galaxy Tab Plus->Galaxy Tab Plus General->unable to write files to external sd card
post #7
Requires root to apply fix.
There is a new permission that older file managers aren't asking for yet. The stock file manager knows to ask for it.
Fix worked for my P6810 wifi.
Click to expand...
Click to collapse
thaloneus said:
I can't post a link to the original post on another forum that worked for me so I will quote it:
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
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 your tablet.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Click to expand...
Click to collapse
Rooted and then applied this change.
Can write to ext sdcard !!!!
Cheers
Will apply as soon as i get tad, should be getting it today, cant wait
Sent from my GT-P1000 using XDA App
I think you have to format the sd card in the tab. I been able to transfer files no problem. Maybe its due to the mtp for the internal sd.
Sent from my GT-P6800 using xda premium
will6316 said:
I think you have to format the sd card in the tab. I been able to transfer files no problem. Maybe its due to the mtp for the internal sd.
Sent from my GT-P6800 using xda premium
Click to expand...
Click to collapse
Using downloaded apps or the stock File Manager app? Because I formatted the SD card in the Tab and nothing else can write to it. Now, I can drag and drop stuff from my computer via MTP, but that's not the same issue.
Ok, I'm trying to add the permission and it doesn't seem to save after a reboot. I'm rooted and made sure to mount that directory as R/W. After I edit platform.xml and reboot it simply reverts. Can anyone offer a more granular description to this n00b?
Thanks.
Edit: Nevermind. I edited the file on my computer and copied it over the original and am good to go.
burhanistan said:
Ok, I'm trying to add the permission and it doesn't seem to save after a reboot. I'm rooted and made sure to mount that directory as R/W. After I edit platform.xml and reboot it simply reverts. Can anyone offer a more granular description to this n00b?
Thanks.
Edit: Nevermind. I edited the file on my computer and copied it over the original and am good to go.
Click to expand...
Click to collapse
Thanks Burhanistan. I had this problem too and did what you did to get around it. Now I can read/write to the external SD with any file explorer.
Hello,
I can access the external SD with no problem, only issue is Titanium backup showing 440Mb capacity on the external SD (32Gb card).
Anyone with the same issue? Any fix?
Thanks.
No problem for me
davp said:
I've already posted a fix for this in our original thread?
Click to expand...
Click to collapse
Things must have changed as i got my P6800 recently did the upgrade from samsung and tried to copy to external sd and no problem for me. I never tried to do it pre upgrade but maybe the upgrade fixed that. Re i can copy and paste to device from my pc when its connected - to both device and sd. I can also copy using the the stock file manager from device to sd card.
No Issues here also
I recieved the tap a week ago. Now my 32GB Sandisk SD is here.
The Tap did at the first startup and using the described 12 MB Android update via internet conn.
Until now there is no issue between writing from/to SD over PC/MTP, copying between internal and external SD. Used preinstalled Filemanager and ES File Ex.
I tried it unrooted and rooted but not before the Android update.
davp said:
Simple solution for external sdcard write access on Android 3.2...if you're rooted
I've found a simple solution for gaining write access to the external sdcard (/mnt/sdcard2) on Android 3.2. The sdcard is mounted r/w, but the owning group is media_rw which is linked to the WRITE_MEDIA_STORAGE permission. Unfortunately, this permission was not required for access to the external sdcard prior to 3.2 so most file management utilities do not request it when they run...meaning they only have read access to the card.
The simple solution, if you're rooted, is as follows:
1. Using a root-enabled file manager, navigate to /system/etc/permissions and make sure you have mounted the file system r/w.
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 your tablet.
After this change, any apps that request the WRITE_EXTERNAL_STORAGE permission (which includes almost anything that access either of the sdcards) will gain group membership in both sdcard_rw AND media_rw, giving them r/w access to both sdcard filesystems.
Click to expand...
Click to collapse
Some people are reporting the above procedure is no more needed, however, with several apps (like Titanium backup, and a SAMBA explorer), writing to the sdcard (extstorage/.../sdcard) is still impossible (GT6800 updated to latest samsung firmware).
I have used this procedure and can state that Titanium backup works now with the SD card.
Thanks to many reading within the XDA forum, I have found this simpler procedure :
- download / install the "Root Browser Lite" app from the android market
- add write access to group and other to the following directory: /system, /system/etc, /system/etc/permissions (with root browser Lite, press on the directory name during 3 seconds to get a contextual menu allowing to change the permissions)
- add write access to group and other to the file platform.xml in /system/etc/permissions
- use the editor of "Root Browser Lite" to modify the file platform.xml as described above (you should have two <group gid= ...> lines within the WRITE_EXTERNAL_STORAGE xml block.)
- save the file. Verify that a .bak file has been created and that the date of platform.xml changed.
- remove the write access.
- Turn off the GTAB, then turn it ON.
NB: Titanium backup still reports a erronous free size on the SD card (401MB), but backups on the sdcard work.
can't save the xlm doc
davp said:
I've already posted a fix for this in our original thread?
Click to expand...
Click to collapse
Hi, I edit the file but when I try to save it I fail because it says original saved as .....xlm.bak, but I can't find that file and the one I find is unchanged, any ideas?
There is an automated installer for the fix here:
http://forum.xda-developers.com/showthread.php?p=21670802
Is for the plus but worked fine for me
Sent from my SCH-I815 using Tapatalk
damm, must forget something, just followed exacty all the steps
still no writing on sd card
the automatic installer failed also
IS there a way to go into the (forgive the incorrect term) "registry" or similar, and have Android re-interpret/understand that instead of looking in "/sdcard"... it should instead look/point programs to "/mnt/sdcard/extstorages/sdcard"...
i heard that it might be called something like a "simlink" or "symbolic link"... maybe this could resolve the application installation issue to the sdcard as well as backups, transfers, etc... right now, not only do i run out of space too fast, can't install apps to the sd card, but as well, if i should run a hard reset... all my data erases! (yes, the internal "SD card" is erased in a hard reset)...
so, for all practical senses, when it says it will erase data, unless you KNOW you have copied ALL you user data to your "Real" SD Card, you will kill your data without even knowing it when you do a hard reset, even if you "thought" you were protected because "I saved my info to the SD card!"
(and yes, this was my experience today, so it's a fact.)
backup programs won't point to the sd card, (app manager, titanium, app list backup, etc)...
so unless you actively move files individually to the card (and know where to look)...
Bottom line... is there a hack/workaround on this that's not just "open up for file transfers" or is someone working on a ROM that might kill the partitioning and allow the /sdcard to actually point to a real external card?
Edited: Nevermind...
acess-rights-hell
hi forum
i would like to use the EzyKernel v1 - 23/02/2012 as in post http://forum.xda-developers.com/showthread.php?t=1513413&highlight=ezykernel
one of the prerequisites is a stock ZSKL firmware.
on the tab is/was XXKL4 AUT/CH
i successfully flashed the ZSKL2 - but that's where the nightmare started: i could not write to sdcard, busybox/superuser don't work properly, as i can't get root via su - which means to me, that there are messed up accessrights also in other places, not just the SD. the funny thing is, that i finally got the overclocking EzyKernel working, but not busybox + superuser.
does that sound familiar to anyone ?
i would really appreciate any ideas about this.
thank you
with best regards from switzerland
roland
could you please explain what "make sure you have mounted the file system r/w" means. And sorry for my noob question, but does this fix allow to install apps on the external sd card or I'm missing something.
After having formatted my internal sdcard, I'm unable to flash any rom. I've installed cwm revorery and would like to push a rom to the sdcard in order to be able to flash it, because right now theres nothing on my card (its totally formatted without any system on it).
When i try to push a file via toolkit to the internal sdcard there appears the following error message:
- exec ' /system/bin/sh' failed: No such file or directory (2) -
Can anybody help me out with this issue?
It looks like the error is saying it is missing a file in /system/bin/, which makes sense since internal storage is completely wiped.
Just start a command prompt in Windows and change directory to where adb.exe is in the android sdk. Then copy the ROM you want to install into the same directory as adb. Use the command "adb push blahblahblah.zip" to push the ROM from your PC to the internal storage. Obviously replacing blahblahblah.zip with whatever the ROM filename is.
Toolkit's can be handy, but before you use one you need to know how to unlock your phone and copy files to/from your device without a toolkit. So that way when problems arise you know what probably went wrong and how to fix it.
Probably not really helpful, but I was able to push files to /sdcard when I wiped all options and formatted Data with TWRP.
Same problem here
Please help us. I accidentally did the same. Now I can't copy file to the device. CWM is still functioning but there is nothing left to flash.
kimezra said:
Please help us. I accidentally did the same. Now I can't copy file to the device. CWM is still functioning but there is nothing left to flash.
Click to expand...
Click to collapse
Just flash TWRP recovery via Fastboot then mount the SD card as USB storage. Once you have done this you can copy a new Rom over and flash it.
Thanks for your quick reply!
EniGmA1987 said:
It looks like the error is saying it is missing a file in /system/bin/, which makes sense since internal storage is completely wiped.
Just start a command prompt and change directory to where adb.exe is in the android sdk. Then copy the ROM you want to install into the same directory as adb. Use the command "adb push blahblachblah.zip" to push the ROM from your PC to the internal storage. Obviously replacing blahblahblah.zip with whatever the ROM filename is.
Toolkit's can be handy, but before you use one you need tokn ow how to unlock your phone and copy files to/from your device without a toolkit. So that way when problems arise you know what probably went wrong and how to fix it.
Click to expand...
Click to collapse
You're right! I've learned that by wasting hours..
How do I change directory to where adb.exe is? what is android sdk? I'd be very happy if you could explain me some of the steps to achieve that or lead me to a tutorial where I can learn it.
Thanks again!
dr9722 said:
Just flash TWRP recovery via Fastboot then mount the SD card as USB storage. Once you have done this you can copy a new Rom over and flash it.
Click to expand...
Click to collapse
Thanks a lot for your reply!!
Would you mind telling me how to flash twrp recovery via fastboot?
Thx in advance!
http://forum.xda-developers.com/showpost.php?p=37019359&postcount=10
Also:
Once you are in a ROM again, download GooManager and look on Google for the easy steps to flashing TeamWinRecoveryProject.
Thank you so much EniGmA1987!! This is awesome!
It finally worked out for me! BIG THANKS!
Your welcome
Was it easy enough even without the use of a toolkit?
Your tutorial is very clear and easy to understand. I followed all the steps, but still couldn't find the pushed ROM on my SD card (after having waited for about 5 minutes). So I mounted all you can with cwm and used the toolkit - and it worked! Probably it was the directory that was set right after having followed your tutorial. Thanks again!!
T-Mo S2, took the nougat update, and even using "MyFiles" all attempts to write to the external sdcard fail. I can't even enable permissions for root explorer or es-filemanager pro. I'm frustrated enough to use this tablet as a weapon in a road rage incident. Anyone else seeing this or is there something I've missed along the way?
scottricketts said:
T-Mo S2, took the nougat update, and even using "MyFiles" all attempts to write to the external sdcard fail. I can't even enable permissions for root explorer or es-filemanager pro. I'm frustrated enough to use this tablet as a weapon in a road rage incident. Anyone else seeing this or is there something I've missed along the way?
Click to expand...
Click to collapse
Don't use supersu 2.82 SR1
I'm not rooted. It's totally stock
Something's not right because I have no problems on my T713. Bone stock. I just finished copying some pix from a USB-OTG to the micro SD. Went without a hitch.
scottricketts said:
I'm not rooted. It's totally stock
Click to expand...
Click to collapse
I have difficulty to write on SD card for some of the apps (such as GPS) after update. But, the file explorer and some other apps are ok. I believe the problem is caused by app permissions and needs to be solve as per app level.
scottricketts said:
T-Mo S2, took the nougat update, and even using "MyFiles" all attempts to write to the external sdcard fail. I can't even enable permissions for root explorer or es-filemanager pro. I'm frustrated enough to use this tablet as a weapon in a road rage incident. Anyone else seeing this or is there something I've missed along the way?
Click to expand...
Click to collapse
It just a permission. It will pop up with permission request then you choose internal or external at root of storage. My can read/write from internal, microsd card, and even 1tb WD hard drive (without power) all no problem.
I'm having the same problem. I was running stock to this happened and have since rooted and tried two, (at the end of the day not very) different ROMs. Resurrection remix and Lineage OS both running nougat and neither have worked. I've tried using adb partition without success and root essentials asks me to flash ASPlugin.zip which I have tried with the flasher and through twrp. Neither works as it asks me to flash it again when I retry root essentials. No errors get thrown while flashing ASPlugin.zip.
I'm also at the point of wanting to throw my tab against the wall.
The permissions window pops up but it does not seem to effect the external SD card.
this link shows how to fix it:
https://www.youtube.com/watch?v=VJRKuQf0puE
ES File Explorer Pro permits root permission, but it's not very obvious as to how it works. Execute a copy or move, you'll be prompted to go to the root of the card, click on the card link, then bottom right hand corner, click the select button and it's done.
Hi everyone.
I found this thread while searching for an answer to the same problem, which drove me almost crazy, too.
I decided to post my solution here, so that it might help others in the future.
As I said: I had the said problem, too.
No writing to ext. SD card, also no writing to my USB-stick via USB-OTG (On The Go), after updating my Tab S2 (SM-T815) to Nougat (Android 7.0) with a stock ROM and then rooting it with magisk (which btw went surprisingly well!).
I am using FX File Explorer, bought it even to be able to use it as root explorer, imho it's one of the best ones out there.
Connected to my PC I could pull or write files to my internal storage as well as to my external SD card via MTP, though.
Strange, but to those of us with just enough know-how to not brick the phone when flashing "stuff" the higher functions seem to be magical anyway, so I didn't take too much time to wonder.
I tried unmounting and mounting both SD card and USB stick, but that would not help.
Also disabeling writing acces in FX explorer and enabeling it again showe no effect. All I got was an error message "Internal Error".
The post above gave me the hint about permissions. (I couldn't watch the linked Youtube video, because my PC has no speakers atm, and I also had no headphones. Also, it looks like the video solves an intirely different problem anyways, not sure why tensux posted this here!?)
So I checked the permissions by using FX.
I went to /root then checked the permissions for /root/sdcard which were set to rwx,rwx,rwx.
Then I checked the SD card (and the USB, while I was at it anyways) via root/storage/[technical name of my SD card like 5555-2843] and /root/storage/[technical name of my USB-stick like 2234-1289] and found that both had their permissions set to rwx,rx,rx.
I marked the respective folders, went to security through the context menu, and changed the permissions to rwx,rwx,rwx in each of them. It would not stick in the grafics, meaning afterwards the permissions still showed no change, even when I restarted the Tablet, but...
I went back to the regular FX explorer and unmounted and mounted both SD card and USB-stick again. I still got the error message, only this time I tried to copy, move or delete a file there was no problem anymore, neither from or to the SD card nor the USB-stick.
After several restarts I still can write to my SD card as well as to my USB-stick, so I must have done something right.
.
Thank you XDA for being a place of knowledge, maybe I could give back a little and maybe this report helps someone else out there.
McFex said:
Hi everyone.
I found this thread while searching for an answer to the same problem, which drove me almost crazy, too.
I decided to post my solution here, so that it might help others in the future.
As I said: I had the said problem, too.
No writing to ext. SD card, also no writing to my USB-stick via USB-OTG (On The Go), after updating my Tab S2 (SM-T815) to Nougat (Android 7.0) with a stock ROM and then rooting it with magisk (which btw went surprisingly well!).
I am using FX File Explorer, bought it even to be able to use it as root explorer, imho it's one of the best ones out there.
Connected to my PC I could pull or write files to my internal storage as well as to my external SD card via MTP, though.
Strange, but to those of us with just enough know-how to not brick the phone when flashing "stuff" the higher functions seem to be magical anyway, so I didn't take too much time to wonder.
I tried unmounting and mounting both SD card and USB stick, but that would not help.
Also disabeling writing acces in FX explorer and enabeling it again showe no effect. All I got was an error message "Internal Error".
The post above gave me the hint about permissions. (I couldn't watch the linked Youtube video, because my PC has no speakers atm, and I also had no headphones. Also, it looks like the video solves an intirely different problem anyways, not sure why tensux posted this here!?)
So I checked the permissions by using FX.
I went to /root then checked the permissions for /root/sdcard which were set to rwx,rwx,rwx.
Then I checked the SD card (and the USB, while I was at it anyways) via root/storage/[technical name of my SD card like 5555-2843] and /root/storage/[technical name of my USB-stick like 2234-1289] and found that both had their permissions set to rwx,rx,rx.
I marked the respective folders, went to security through the context menu, and changed the permissions to rwx,rwx,rwx in each of them. It would not stick in the grafics, meaning afterwards the permissions still showed no change, even when I restarted the Tablet, but...
I went back to the regular FX explorer and unmounted and mounted both SD card and USB-stick again. I still got the error message, only this time I tried to copy, move or delete a file there was no problem anymore, neither from or to the SD card nor the USB-stick.
After several restarts I still can write to my SD card as well as to my USB-stick, so I must have done something right.
.
Thank you XDA for being a place of knowledge, maybe I could give back a little and maybe this report helps someone else out there.
Click to expand...
Click to collapse
All external storage write permissions are granted on a per app basis as per Google's security specs.
If an app has issues with writing to external storage then it is the app at fault.
The developer needs to update the app with the new permissions.
I have many Android devices and for all of these devices I use Root Explorer.
This is and has always been the best Root file explorer since day one. It does what it needs to do without any silly unnecessary bells and whistles.
Any serious developer will use this app as it's proved to be the most reliable and the dev is on the ball with this app.
Never have I had an issue with it.