I don't have access to my internal storage anymore. I don't know why. Yesterday I went from Lollipop back to Stock. I think, that's the reason. But I can write to my external MicroSD. And if I want to open a folder with FX, it shows "Access denied". Help pls.
I fixed permission with SELinux changer ,changed to permissive.
My SELinux-Status was already on permissive.
But thanks. I solved the problem with formatting the data partition. I have lost all my data but now the permissions are working again.
Related
Hello, I have tried the app fixes, next app and sd fixer. Both say all is fixed. I have verified that the correct changes have been made to the platform.xml file. I have mounted r/w the system. ES File Explorer still has SuperSu permissions, verified root with root checker. No matter how hard I try, I can't seem to get this to work. Anyone have any suggestions on what I could try to regain the ability to transfer files from Internal Storage to External SD Card?
jerdoggmckoy said:
Hello, I have tried the app fixes, next app and sd fixer. Both say all is fixed. I have verified that the correct changes have been made to the platform.xml file. I have mounted r/w the system. ES File Explorer still has SuperSu permissions, verified root with root checker. No matter how hard I try, I can't seem to get this to work. Anyone have any suggestions on what I could try to regain the ability to transfer files from Internal Storage to External SD Card?
Click to expand...
Click to collapse
Try installing SDFix: KitKat Writable MicroSD it also works on lollipop that should fix your problem
I am trying to install TWRP on an xt1963 -- did this once already with another one, with no problems. On this one it doesn't seem to let me access the System partition. MTP doesn't work, and the Internal Storage says 0MB.
When I get into TWRP I am given the option of swiping to allow modifications and I swipe it, but it doesn't seem to do anything. Anyone have any tips?
EDIT: using v4 now, seems to be OK.
Edit: Title should read "SD Card" (how to edit that?)
I have root and I am trying to get Link2SD to work. I have created the FAT32 (primary) and EXT4 (primary) partitions but I keep getting a mount script error ("unable to mount") (Also tried EXT2)
I am doing the same thing as I have done on several other devices and it is not working on the samsung.
Also, I am having issues with getting Titanium Backup to wrtie to the SD card too. I tried the Kitkit SD card patch but it failed.
I know the SD card works so I am thinking it is a wonky Samsung thing?
Thoughts or advice
Edit: Pulling SD card, re-inserting and rebooting and then Link2SD reports that the 2nd partition is not accessible during boot (and suggests quick boot to fix which it does not). Samsung says the FAT32 is fine but the EXT is "corrupt" but I have confirmed on two other devices it is fine.
So this seems to be some sort of access thing. Maybe related to the removal of encryption patch as part of the TWRP install?
Edit2: cat /sys/block/mmcblk2/device/type gives back "no such file or directory"; (whereas mmcblk1 gives SD)
Total commander shows sd-card (which is internal /storage/emulated/0), sd-card(2) "/data/sdext2"), and USB (SD FAT32 as /storage/BDB2-8960)
Got TB fixed anyway. Backup one file (on device internal location), move the directory to external SD card, then TB decided it is was OK to include that location under settings so select new location.
Now need Link2SD. Could this be a mount script write issue? Encryption issue (I removed it from internal via a scripted)?
Runings Mounts2SD, installed scripts, reboot but it says External is "not mounted". Link2SD still fails with those scripts installed.
chemie99 said:
Got TB fixed anyway. Backup one file (on device internal location), move the directory to external SD card, then TB decided it is was OK to include that location under settings so select new location.
Now need Link2SD. Could this be a mount script write issue? Encryption issue (I removed it from internal via a scripted)?
Runings Mounts2SD, installed scripts, reboot but it says External is "not mounted". Link2SD still fails with those scripts installed.
Click to expand...
Click to collapse
Link2SD never worked for me either no matter what I did. Apps2SD works flawlessly. Links data, apk, obb files and everything without any issues on ext4 format.
moxalis said:
Link2SD never worked for me either no matter what I did. Apps2SD works flawlessly. Links data, apk, obb files and everything without any issues on ext4 format.
Click to expand...
Click to collapse
I tried installed Apps2SD but it never asked for root and decided half the apps could not be moved. I figured it was just offering the usual stock "move apps" which moves marginal amount.
Samsung says that the EXT partition is corrupt but Aparted says it is fine. EXT2, and EXT4 created in either Minitool or Aparted are simply not read.
Mount2SD adds scripts to mount but the partition remains unmounted after reboots.
What format does Samsung want?
chemie99 said:
I tried installed Apps2SD but it never asked for root and decided half the apps could not be moved. I figured it was just offering the usual stock "move apps" which moves marginal amount.
Samsung says that the EXT partition is corrupt but Aparted says it is fine. EXT2, and EXT4 created in either Minitool or Aparted are simply not read.
Mount2SD adds scripts to mount but the partition remains unmounted after reboots.
What format does Samsung want?
Click to expand...
Click to collapse
Samsung reads the partition as corrupt but Apps2SD is using it just fine. You should delete any mount scripts and re-create them through the Apps2SD application.
moxalis said:
Samsung reads the partition as corrupt but Apps2SD is using it just fine. You should delete any mount scripts and re-create them through the Apps2SD application.
Click to expand...
Click to collapse
How do I manually delete the mount scripts?
chemie99 said:
How do I manually delete the mount scripts?
Click to expand...
Click to collapse
There is the option "Delete mount scripts" in the Apps2SD app. Check their FAQ page for any questions, it's pretty helpful.
Hello! I was having just the exact same problem with my T580.
I just loged in to say how I fixed it:
Open SuperSU app -> Settings.
Check "Enable su during boot"
Uncheck "Mount namespace separation".
After a reboot, Link2SD detected the 2nd partition!
EDIT: Now I fin another issue. If I try to link Obb, it says my device is using "sdcardfs". It offers to install fuse insted to fix it, but after rebooting I still getting the same message.
What could I do?
otamaglimmer said:
Hello! I was having just the exact same problem with my T580.
I just loged in to say how I fixed it:
Open SuperSU app -> Settings.
Check "Enable su during boot"
Uncheck "Mount namespace separation".
After a reboot, Link2SD detected the 2nd partition!
EDIT: Now I fin another issue. If I try to link Obb, it says my device is using "sdcardfs". It offers to install fuse insted to fix it, but after rebooting I still getting the same message.
What could I do?
Click to expand...
Click to collapse
Seems Link2SD does not like Marshmallow so I switched to Apps2SD (which also suggests what you did). It would not create the partition itself but took windows EXT4 and after a bunch of config, worked. The issue I now have is that Samsung still thinks the card is corrupt (which it isnt); any EXT partition and it says that. So on any reboot it greets me with a system notification of a corrupt card (which I want to get rid of but so far can't)..
I did try adoptable using a scripts from this site (didn't work) and the Apps2SD option. Seem to work on device but windows only saw the device memory so would not copy anything when it reported full.
took another kick at the cat today; installed Apps2SD, created mount scripts, but now, for reasons unknown, it no longer reports the SD as corrupt on boot (although it does say that partition is corrupt from the storage setting menu. Weird. No idea why it is no longer doing this. I will say the reinstall was funny. I had to delete and recreate the mount scripts several times (all said it worked) to actually get apps to move without disappearing. perhpas I ended up with a different mount script method in all the trying
My s7 edge has been restarted and this message is came:
I dont spek Italien but I think this message about the system memory. If I restart my system comes always this. My phone is rooted and if I open Teamwin recovery and mount the system I can't see my files.
My some files are really important for me? What do you suggest me to access them?
http://imgur.com/0ndjunk
Have u tried mounting your twrp into MTP? Where is your files located? SD or internal? I that was internal, sorry bro but your files will be deleted to fix that. (Flashing stock rom)
JohnLouise said:
Have u tried mounting your twrp into MTP? Where is your files located? SD or internal? I that was internal, sorry bro but your files will be deleted to fix that. (Flashing stock rom)
Click to expand...
Click to collapse
yes but MTP doesnt show any file. I tried also the internal file browser of twrp still same. The files located under internal.
Hi,
I suddenly have a very strange problem. My internal memory changed for some reason to read-only. The built-in file browser can't modify files anymore, nor can any app. With Root explorer (root access) I can still modify files. I could just use Root explorer, but some apps actually crash because they can't access the internal memory, so that's no solution.
Here's the situation:
I have the SM-N9005, on Android Kitkat (4.4.2). I was rooted with CF Auto Root. I wanted to try Magisk (not realising that you needed at least Android 5.0 for it). I uninstalled Busybox, Xposed, and then did a full unroot via the SU app. Then I installed TWRP recovery, tried installing Magisk. Of course that didn't work. So then, with Odin, I reinstalled CF Auto Root. After that I reactivated Busybox and Xposed. TWRP seemed to have disappeared, so installed that again as well. Everything was back to the way it was, except for that internal memory issue.
Does anyone has any idea how to fix this?
I made nandroid backup, so I could just revert to that backup but I'd prefer to find a solution and know why it happened.
Thanks!
After installing and running twrp, did it ask to make changes to internal storage?
audit13 said:
After installing and running twrp, did it ask to make changes to internal storage?
Click to expand...
Click to collapse
It did not. And I've just found out that everything on the SD card can't be opened via the built in file explorer. I can create new folders and such, I just cannot open any files.
I says: "Not able access to external SD card. Try again if SD card is successfully mounted"
It's been a while since I used twrp but I recall being asked if I want to allow modifications to the file system.
Maybe it's time to flash back to stock using Odin and then restore your backup?
audit13 said:
It's been a while since I used twrp but I recall being asked if I want to allow modifications to the file system.
Maybe it's time to flash back to stock using Odin and then restore your backup?
Click to expand...
Click to collapse
Weird, I don't think it asked.
Yeah I guess is if no one comes up with a solution I won't have another choice.