This is a peculiar thing. Some apps that have an internal file browser (MD5 Checker, for example) have started defaulting to the root folder, and I can't navigate to the sdcard, because /sdcard as well as /mnt/sdcard don't exist (or can't be seen). I'm denied access to /storage. But file explorer programs (FX, ES) see them no problem.
Does anyone have any ideas? I'm running the latest Cataclysm 4.3.
Edit: problem solved by doing a factory reset and clean install.
Sent from my Nexus 4 using Tapatalk 2
Related
I'm on stock rooted MDL and I can't seem to put my filesystem into read/write. I have tried ES explorer, Solid explorer, and even tried the remount rw command in Terminal Emulator. No joy.
Anyone come across this our have an idea? Haven't tried adb copy yet.
Sent from my SPH-L720 using xda app-developers app
I am also having a similar problem, I just rooted my S4(SPH-L720) running 4.3 MK2(Stock Recovery and ROM) with CF-Auto-Root and when i try to use "SystemApp Remover" it shows system as not mounted. If I use Root File Manager I can change it to R/W and do whatever. But other then that I can not get /system mounted with R/W.
BlackoutX90 said:
I am also having a similar problem, I just rooted my S4(SPH-L720) running 4.3 MK2(Stock Recovery and ROM) with CF-Auto-Root and when i try to use "SystemApp Remover" it shows system as not mounted. If I use Root File Manager I can change it to R/W and do whatever. But other then that I can not get /system mounted with R/W.
Click to expand...
Click to collapse
Meh, I couldn't figure it out and never found anything on it. Ended up flashing (Odin) a rooted Stock ROM (4.3 MK2) with philz recovery.
I wanted to keep my phone as close to stock as possible and just have root but inevitably I always go to a custom ROM. So my middle ground was the rooted stock ROM and I've had no issues so far.
I upgraded to motorola's 5.02 lollipop last week. Beautiful - no problems worth mentioning.
Then I wanted to try xposed, so I went into TWRP and made a backup. No problems with xposed. It is working fine.
But, I noticed a disk space inconsistency and a problem with the /sdcard/TWRP directory. Here are the symptoms:
Under settings->storage, it did not show my TWRP backups under "misc", but it counted the space as used in the numeric free space.
I tried to look at /sdcard/TWRP/ in es file explorer, but TWRP showed up as a file and not a directory.
At the command line, I got permission denied when I tried to cd into or ls the /sdcard/TWRP directory.
I could not see the /TWRP directory using my PC via USB/MTP while in android.
I could not delete /sdcard/TWRP within es file explorer or at the command line.
The TWRP directory was available and seemed fine at /data/media/0/TWRP.
Within TWRP recovery (v2.8.5.0), I had no problem viewing or deleting the TWRP directory, but when I made a new backup, the problem came back.
I googled and found a number of people with the same problem. (ie http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749)
This fixes half of the problem. After running this, the TWRP ?file? was a directory again and the space was seen in storage under "misc":
Code:
su
restorecon -FR /data/media/0
But, I still did not access to read TWRP as either root in the terminal or from es file explorer. I noticed the owners were not the same as other directories. This fixed that problem:
Code:
su
chown -R media_rw:media_rw /data/media/0/TWRP
Now, I seem to finally have control over the /sdcard/TWRP directory. Whew!
I did not try a restore, and read where others were having trouble restoring lollipop (bootloops or /data missing) with older versions of TWRP. I would be interested to hear if anyone had successfully restored lollipop /data/ using TWRP.
edit: I was forced to restore system and data.. It worked....
Ctrl-Freak said:
I did not try a restore, and read where others were having trouble restoring lollipop (bootloops or /data missing) with older versions of TWRP. I would be interested to hear if anyone had successfully restored lollipop /data/ using TWRP.
Click to expand...
Click to collapse
About 2 weeks ago I had restored the Motorola 5.0.2 backup posted here on XDA [Link Removed by Mods due to Moto Policies]. I had the SELinux storage access problem. Then I restored the CM12 nandroid i had then.
No problem occurred. All of my data in /data is still intact.
Ctrl-Freak said:
I upgraded to motorola's 5.02 lollipop last week. Beautiful - no problems worth mentioning.
Then I wanted to try xposed, so I went into TWRP and made a backup. No problems with xposed. It is working fine.
But, I noticed a disk space inconsistency and a problem with the /sdcard/TWRP directory. Here are the symptoms:
Under settings->storage, it did not show my TWRP backups under "misc", but it counted the space as used in the numeric free space.
I tried to look at /sdcard/TWRP/ in es file explorer, but TWRP showed up as a file and not a directory.
At the command line, I got permission denied when I tried to cd into or ls the /sdcard/TWRP directory.
I could not see the /TWRP directory using my PC via USB/MTP while in android.
I could not delete /sdcard/TWRP within es file explorer or at the command line.
The TWRP directory was available and seemed fine at /data/media/0/TWRP.
Within TWRP recovery (v2.8.5.0), I had no problem viewing or deleting the TWRP directory, but when I made a new backup, the problem came back.
I googled and found a number of people with the same problem. (ie http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749)
This fixes half of the problem. After running this, the TWRP ?file? was a directory again and the space was seen in storage under "misc":
Code:
su
restorecon -FR /data/media/0
But, I still did not access to read TWRP as either root in the terminal or from es file explorer. I noticed the owners were not the same as other directories. This fixed that problem:
Code:
su
chown -R media_rw:media_rw /data/media/0/TWRP
Now, I seem to finally have control over the /sdcard/TWRP directory. Whew!
I did not try a restore, and read where others were having trouble restoring lollipop (bootloops or /data missing) with older versions of TWRP. I would be interested to hear if anyone had successfully restored lollipop /data/ using TWRP.
edit: I was forced to restore system and data.. It worked....
Click to expand...
Click to collapse
hi, im having the same problem as you. I was on cm12, reverted to 4.4.4 and took the OTA, i then flashed TWRP and did a backup of the stock rom, but I cant see the file on ES Explorer and its taking space like you said. The problem is I didnt understand how you fixed it. Could you explain please? Whats the code you mention on the solution? where do you enter it?
Edit: I managed to flash a backup of the rom i was running prior to KitKat via OTG cable. TWRP recognized the backup when i made a couple of folders: TWRP/BACKUPS/TA000021JN and i flashed. As soon as the phone booted up I was able to see the TWRP folder on ES Explorer again so i think it 's probably fixed?
Cristian314 said:
hi, im having the same problem as you. I was on cm12, reverted to 4.4.4 and took the OTA, i then flashed TWRP and did a backup of the stock rom, but I cant see the file on ES Explorer and its taking space like you said. The problem is I didnt understand how you fixed it. Could you explain please? Whats the code you mention on the solution? where do you enter it?
Click to expand...
Click to collapse
Terminal emulator (app), I just tried it, works [emoji2]
Enviado desde mi XT1058 mediante Tapatalk
My Razr M is running BlissPop-v3.4-moto_msm8960_jbbl-Official-20150531-0035. It's been solid for a few weeks now. My external SD card is 16GB.
My external SD card (sdcard1) now has an errant file with empty date, time, and permissions. Unfortunately, it appears to be an important file, as it's called ".android_secure". Ghost Commander no longer will read sdcard1, even in root mode, as it fails on that file. Total Commander will read sdcard1 just fine, but not that file. I've tried to rename this file and change it's date/time/permissions with no success. Even in root mode, Total Commander won't touch it. I also fired up the Terminal Emulator and tried chown and chmod; both gave me a "permission denied" error even after "su".
The built-in file manager (Cyanogenmod) sees sdcard1 just fine, but doesn't show this file.
My best guess is that ".android_secure" used to be a folder, but something messed it up. I'm not sure what caused this problem as I've done nothing unusual that I've not done before. I got an error during an SFTP transfer this morning when I was copying my latest set of backup files from TiBu, but I think that has happened before. I restarted the SFTP transfer and it worked just fine. I was using Ghost Commander to do the transfer.
I have never moved any apps to sdcard1. Everything else seems to be working fine.
What I think I'll need to do at this point is unmount sdcard1, remove it, then use my desktop to delete that file. I can't do anything to it with any program on the phone. I'll do a "fsck.vfat" on it while it's plugged into my desktop (which runs Linux) and see if that shows anything.
Does anyone have any other suggestions? Thanks!
----
Update:
I played with it a bit more just now and things seem to be working, though it's confusing. I will blame whomever invented the VFAT format and Google for creating such an ugly kluge to get around its limitations.
I'm using Ghost Commander for all the following:
- In root mode, I can't look at /storage/sdcard1 without getting an error: "lstat /storage/sdcard1//.android_secure failed: permission denied"
- In root mode, I can look at /mnt/media_rw/sdcard1 just fine. .android_secure shows up as a folder "drwxrwx---" from Apr 30 23:54, and it's empty
- Not in root mode, I can again look at /storage/sdcard1 just fine. .android_secure shows up as an empty file with no date
Anyway, probably nothing was wrong, but because of this ugly kluge, somehow I ended up in the wrong place even though they all look the same.
Please give a try a new beta version of the application.
So Hello everyone, i got interesting problem...
I bricked my phone
Phone: SM-9005
OS: Android 4.4.2
Firmware: N9005XXUGNG1
Recovery: TWRP 3.0 installed.
Root software installed which may be interesting "Xposed Additions, Lucky Patcher, SuperSu, Greenify"
Step by step.
// maybe helpful - cache / dalvik cache wiped and after reboot i started playing stuff
I used Root Browser (com.jrummy.root.browserfree) to copy 2 directories from my /downloads to /system.
There were /lib & /bin which contained unique libs and one executable so this would not affect system if everything went ok, but i didn't
After i started coping, root explorer asked me that "File already exist, overwrite or make a copy"? i pressed overwrite, in same second all apps in android started to generate "unexpected error", i tried to reboot and got boot into recovery
after i watched /system i found that what i tried to copy actually copied not to /system/lib & /system/app but to /system/system/lib & /system/system/app.
So i think there was some folder or file called system in /system directory which was overwritten. Or any kind of problem with dir / file permissions.
Any ideas of how to fix this / what was in /system/system / where to get bootlog to find after what "kernel panic" takes place or any other help?
Thanks.
// maybe somebody with same model version, same os version can upload zip file of own /system folder without /apps, /priv-apps and build.prop so i can compare whats lost compared to my data?
Fixed myself, root browser set wrong permissions to /system while was coping files... set back to 755 and it works
I am on android 7 and have an issue with the emulated folder. by default it is not readable or writable. the problem that i am facing is that when I am in an app and going back threw folders to access a removable flash drive, I cant get out of the emulated folder and into the parent folder (storage).
In a file explorer if i view /storage/emulated permissions, it is not readable or writable by anything other than root. If i try to change permissions, I get an error access denied.
I havent tried it through shell yet. What would that look like?
anyways, anyone got a fix for this? I want to make the folder rrw or fully rw
Hmmm what apps are you using. Name your file explorer and it's version.
What did you use to root, what package from what source?.
Personally i flashed supersu from supersu.com/download which is systemless root.
Some apps and file explorers may not be compatible with systemless root.
For example i use es file explorer v3.2.5.5 and i had to copy paste the content of /su/bin to /system/xbin in order to recognize root and enable rw permissions.
Enviado desde mi Moto X via Tapatalk!
I will look into that. I think I have system root though and using esfileexplorer pro.
Emulator apps are my issue though. I try to navigate to my flash drive to set up sons and save. Storage is fine but storage/emulated though is tricky.. Some apps will just recognize that it don't have access but still let it up folder to /storage/ where I can then select flash drive...
Other apps will get hung on the emulated folder.. Not letting me folder up further.
Its a pain.. And to solve, I would just like full access to emulated
adam_ky said:
I will look into that. I think I have system root though and using esfileexplorer pro.
Emulator apps are my issue though. I try to navigate to my flash drive to set up sons and save. Storage is fine but storage/emulated though is tricky.. Some apps will just recognize that it don't have access but still let it up folder to /storage/ where I can then select flash drive...
Other apps will get hung on the emulated folder.. Not letting me folder up further.
Its a pain.. And to solve, I would just like full access to emulated
Click to expand...
Click to collapse
Thing is that you need to get a popup to grant permissions to the root of the extrrnal storage you want to use, then a windows will open where you can select your device and then hit select button.
You're not getting that.
So i suggest to change to systemless root which is proven to work and test by yourself.
I do not have AndroidTV installed but full Android Nougat yet that basic feature if i remember correctly is available even without rooting because i backup my stuff to my external USB flash drive before flashing custom firmware and i never rooted while in AndroidTV.
Now, i use Hyperspin with Retroarch and all my hyperspin folder with system,roms,etc is in my external USB 3.0 flash drive and works great no issues with those apps recognizing the external storage. Same goes for writing to my microsd with other apps
Enviado desde mi Moto X via Tapatalk!