Help with sd card as portable media - Verizon Galaxy S 5 Q&A, Help & Troubleshooting

Ok so ive finally upgraded my s4 to a s5 unlocked bootloader, rooted and resurrection rom. I understand the whole adaptable media and encryption. I want my sd card as portable so i can use it in my pc and other phones if needed. Also to use titanium backup to restore apps if i wipe and install a fresh rom.
My problem is es file explorer, root explorer, and any archiving apps are all jacked up and wont write as they used to. I am able to write to the sd card but i want to have full control like i used to on older roms on my s4.
Any help?

maniac2k said:
Ok so ive finally upgraded my s4 to a s5 unlocked bootloader, rooted and resurrection rom. I understand the whole adaptable media and encryption. I want my sd card as portable so i can use it in my pc and other phones if needed. Also to use titanium backup to restore apps if i wipe and install a fresh rom.
My problem is es file explorer, root explorer, and any archiving apps are all jacked up and wont write as they used to. I am able to write to the sd card but i want to have full control like i used to on older roms on my s4.
Any help?
Click to expand...
Click to collapse
I'm using Ressurection too. Marshmallow can be a pain with the sdcard. Apps have to ask for write permission when it first needs it and you have make sure to grant it.
Titanium Backup works with the external sdcard but you have to go to "Preferences", then to "Backup Folder Location", click where it says "Storage provider:", select " Document provider storage", go to the external sdcard (not a directory in it) and press "select", and then go to the TB backup directory and select "Use the current folder".
If you're using a multi partitioned sdcard, Link2SD doesn't work but Apps2SD appears to work fine. Either way, you'll probably get a notification about a corrupted sdcard for each extra partition. You can safely ignore them. Long press on the notification and select the crossed bell icon to prevent it from popping up again.
Some apps have trouble if they are opened from another app. Rar wouldn't work for me in ES File Explorer until I opened it from the app drawer. Then the correct permission dialog popped up and it was fine ever since.
I would also strongly suggest setting selinux mode to permissive. I suggest using SELinuxModeChanger.

Thanks. I changed the selinux mode but es is still wonky when working with zips. I also tried zarchiver opened directly and it has problems too. Oh well.
I did get tibu working previously as you stated.
I hate when enhancements are downgrades!!
Thank you for the information.

Related

[Q] External SD not working after custom ROM install...

I'm relatively new to this but up until now I've had no problems so far... So I just upgraded to the latest version of Jamal's 4.4.2, following the proper install method, clearing data and caches in CWM.
I DL'd Titanium Backup and tried to change my backup location to where I store my apps which is on my SD however upon selecting /extsdcard it says that 'this folder is not writable'. Using a file manager and attempting to access external just displays an empty folder. However, going into settings-storage shows that the SD card is mounted and displays the correct size/available space.
If I unmount then mount the card it seems to function again, I am able to access the files in a file manager. That is until I go back into Titanium Backup. Now it does something different here if I press 'DETECT!', it finds my backups and displays the correct amount and path on the external however upon selecting them it takes me to the appropriate folder and says 'This folder is not writable' and 'this folder is empty.' and Use the current folder' is greyed out. The external sd is then back to displaying nothing in the file managers again.
I've tried wiping and re-installing the ROM, but it still carries on doing the same thing. I've searched in the ROM's thread and other places and I haven't been able to come up with any solution so I'd be grateful if you could shed some light into this issue and possibly offer a potential fix?
this issue is hard.Im not a developer,but I think you need change an another firmware or change a new TF card.so you can know what's the problem.But I have a damaged TF card have the similar problem.but due to I have no important file in it ,I throw it out
hope I can help you

Micro SD card issue in 4.4.2

Hi Guys,
since i have updated my note 3 to 4.4.2 its giving problem with micro SD card, developers did find the solution which works in most of the applications specially in Titanium backup. I use GoBackup Pro to backup my messages, wifi access points, call log, launcher layout etc. gobackup do not read memory card straight away. i have to use root explorer and and change permissions of /mnt/media_rw folder to rwxrwxrwx. I have to do it every full restart because permissions go back to rwxr--x--
any comment or help?
glimpsofreality said:
Hi Guys,
since i have updated my note 3 to 4.4.2 its giving problem with micro SD card, developers did find the solution which works in most of the applications specially in Titanium backup. I use GoBackup Pro to backup my messages, wifi access points, call log, launcher layout etc. gobackup do not read memory card straight away. i have to use root explorer and and change permissions of /mnt/media_rw folder to rwxrwxrwx. I have to do it every full restart because permissions go back to rwxr--x--
any comment or help?
Click to expand...
Click to collapse
I have the same prob, although I'm not rooted also after updating the phone to the latest Russian ROM N900XXUDNB2 still the same issue
you can root again if you lost root and write an init.d script that sets the permissions on every reboot (in case that your kenrnel has init.d support).
If not try pimp my rom and try the universal init.d support

Factory reset device, cant access storage/emulated/0

Hi there
Im sorry if this been asked before, but I did some searches and couldnt find anything related to this
I just made a factory reset on my phone, because the battery drain was horrible and couldnt locate which app was causing this.
The device is rooted and its been working fine until now. For some reason Titanium Backup cannot access the path storage/emulated/0. This is where the backups are supposed to be stored. But it doesnt have access to any other internal path, it always says "this folder is not writable" every time I try to use internal storage. Thus cant make any backup or restore. I cant even see the list of the apps that are installed in order to freeze some of them.
Same happens to ES File Explorer. Before I could access storage/emulated/0 to transfer files from/to my MicroSD. And when I tried to copy a WhatsApp back up it says that it failed. In the memory selector I could choose between extCard and the before mentioned path. Now I can only see the extCard and a "legacy" drive, or whatever its called.
I tried fixing permisions for TB and ES File Explorer and used an App thats suppossed to fix the KitKat SDcard issue but its not working for me
It seems to me that the internal storage is somehow write protected?
Anyone can help? With links or your own knolwdge.
Thanks
Alberto5501 said:
Hi there
Im sorry if this been asked before, but I did some searches and couldnt find anything related to this
I just made a factory reset on my phone, because the battery drain was horrible and couldnt locate which app was causing this.
The device is rooted and its been working fine until now. For some reason Titanium Backup cannot access the path storage/emulated/0. This is where the backups are supposed to be stored. But it doesnt have access to any other internal path, it always says "this folder is not writable" every time I try to use internal storage. Thus cant make any backup or restore. I cant even see the list of the apps that are installed in order to freeze some of them.
Same happens to ES File Explorer. Before I could access storage/emulated/0 to transfer files from/to my MicroSD. And when I tried to copy a WhatsApp back up it says that it failed. In the memory selector I could choose between extCard and the before mentioned path. Now I can only see the extCard and a "legacy" drive, or whatever its called.
I tried fixing permisions for TB and ES File Explorer and used an App thats suppossed to fix the KitKat SDcard issue but its not working for me
It seems to me that the internal storage is somehow write protected?
Anyone can help? With links or your own knolwdge.
Thanks
Click to expand...
Click to collapse
Did you find a solution? I am stuck with the same issue and have tried all the steps you mentioned.
Sadly I didn't find any solution for this issue. I just sold the device and got a Note 3 shortly after I wrote this post. Maybe you could reflash the whole firmware via Odin? Or restoring the device via Kies.

I can't properly write on my SD

Ok, I have had many phones and this problem is a little bit weird for me.
I'm using Poweramp as my daily driver for music. I tried deleting some songs I stored on my SD and it said my files were write protected. I then used Root Browser just to see, that most of my music and photos I have on my SD card were not located in /sdcard but in /storage/57EF-B920, a directory I never created. When I put the SD card into my PC, I can see all my files normally and r/w without any issues.
I figured I could only alter files using the stock file browser and gallery app, but why? And why are my SD card stored media files showing up in /storage/57EF-B920 instead of their actual path? Is that a security feature?
My phone is 100% stock and not rooted.
Thanks for your help!
This is how it has always been on MM. The days of /sdcard, or /storage/extSDcard for your external SD card folder are long gone with LP/KK/JB I'm afraid.
The directory for external sd is unique to your SD card. Put in another SD card, and a new directory name will get generated for it, and it alone.
The ability for an app to write to SD card is down to the app's developer. It will need to have the updated methods that MM uses. Usually, if an app can write correctly, it will prompt you to browse to the root of your external sd card the first time it attempts to access it. Even then, some apps may need extra tweaking. Titanium Backup for example requires the storage type for the external SD card to be changed to Document Storage/Provider in its settings. I used to use Nandroid Manager on my rooted S4 on CM MM, and this could never update external SD card....I had to use Root Explorer to delete/rename my TWRP backups.
You can also double check specific apps for permission through Application Manager.
Go into the specific app in application manager, click on Permissions, and make sure Storage is turned on.
Even when turned on, some apps might still fail, as I've explained.
hawkerpaul said:
This is how it has always been on MM. The days of /sdcard, or /storage/extSDcard for your external SD card folder are long gone with LP/KK/JB I'm afraid.
The directory for external sd is unique to your SD card. Put in another SD card, and a new directory name will get generated for it, and it alone.
The ability for an app to write to SD card is down to the app's developer. It will need to have the updated methods that MM uses. Usually, if an app can write correctly, it will prompt you to browse to the root of your external sd card the first time it attempts to access it. Even then, some apps may need extra tweaking. Titanium Backup for example requires the storage type for the external SD card to be changed to Document Storage/Provider in its settings. I used to use Nandroid Manager on my rooted S4 on CM MM, and this could never update external SD card....I had to use Root Explorer to delete/rename my TWRP backups.
You can also double check specific apps for permission through Application Manager.
Go into the specific app in application manager, click on Permissions, and make sure Storage is turned on.
Even when turned on, some apps might still fail, as I've explained.
Click to expand...
Click to collapse
Sorry for the late reply, but thanks for the explanation! So it's because how MM works vs how Lollipop did and Poweramp not being uptodate with that? I'll try out the permission thing and even if I fail, it's good to know why it won't work. Thank for your help!

After 7.0 Update Nothing Can Write to SDCARD

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.

Categories

Resources