After migrating back from f2fs to ext4 I found out I couldn't touch the files that I adb pushed back onto the device. The pictures I took with the stock camera app wouldn't save until I renamed the old DCIM folder, which caused it to create a new one and proceeded to work normally. How can I make my files and folders writeable again? ES shows that all the files and folders do have RW tags.
I'm running the Android L mako port with the Unleashed kernel.
Very similar problem here, after doing a restore with CWM of 4.4.4 backup, I'm unable to save files to user storage. Owner is 0 root, GID is 1028 sdcard_r, permissions drwxrwx--x.
Can save to ./Downloads though. ?:|
Did you ever resolve your issue?
Related
I am running on Team Union Rom v3. JB.
I cannot restore / backup files on Nova Launcher.
Default Location (cannot be changed) = /sdcard/data/com.teslacoisw.launcher/backup
MAIN PROBLEM
I cannot access /sdcard/data
The folder is there. And it is empty.
Cannot access or move or create file in it (even with root explorer)
In Files app. Under storage - got 2 directories:
1. sdcard0 = internal
2. sdext = external
ATTEMPTS
Try backup files within Nova Launcher to determine backup dir
Failed. Says backup successful but backup file no where to be found.
Why is my sdcard/data folder not accessible?
Can you access it through storage/sdcard0/data ?
in ics the internal space is called Sdcard in JB its called sdcard0, may be you need to fix permissions to access it as its a system folder are you rooted
Rooted via CWM method.
Root works fine. Lucky patcher, busybox, chainfire 3d all works fine.
I need to rephrase my situation.
I can access into sdcard/data/
But once I am in it. No files are in it / visible.
Cannot create file / folder
there is no sdcard its sdcard0 and on my tablet the data folder is extsdcard
anyways I am not rooted currently as just installed the new rom.
But I think its more the case of permission or may be there are no files in it
samir_a said:
there is no sdcard its sdcard0 and on my tablet the data folder is extsdcard
anyways I am not rooted currently as just installed the new rom.
But I think its more the case of permission or may be there are no files in it
Click to expand...
Click to collapse
Already check permission. Full permission. Owner root. Sdcard_write.
Anyway flashed a new rom. Redemption.
Sdcard/android/data is accessible. Nova Launcher backup dir is here.
But could not save backup to sdcard0.
Try backup failed.
I'm running stock/unrooted with my bootloader unlocked.
I wanted to try out the PA beta with the PIE navigation so I used adb fastboot to boot into TWRP 2.3.3.3 (not flashed, booted the image directly. I have no custom recovery flashed) to make a nandroid backup. This is the second one I've made with this method but this one went tits up. It reported success and I rebooted. All of my apps are in place and everything seems to be in order other than that my /sdcard folder was completely wiped. All my of pictures and everything. The only folders it contains are the ones the OS and apps are creating as they need them. I also have the /TWRP folder but it only contains .twrps and .version.
I get the same results from ES File Explorer. I went back in TWRP to use the built-in root file explorer to see if it was a permissions issue but it is not. The recovery file explorer shows the same results. The only folders under /sdcard are newly created by Android or by my apps.
Anyone have any idea what happened here and how I can prevent it from happening again?
EDIT: Oddly enough I just noticed if I go back into the TWRP backup screen it's reporting about 2GB less free space (approx backup size) than it did when I made the backup that apparently broke everything. I can't seem to find any backup actually stored though. The Restore option doesn't list any backups available to restore.
EDIT2: I found the backup. It is in /data/media/TWRP. /data/media/0 has the contents of the newly created /sdcard folder but none of my old data is anywhere to be found. Did TWRP writing this folder break my /sdcard folder somehow?
Hi,
I updated my nexus 7 to from PA 4.2 to PA 4.3, before this I did multiple backups using TWRP, TiB and copied the entire contents of my SD card to my computer using adb (adb push and adb pull) on OS X (android file transfer does not work properly and windows kept on not responding, Linux had no space and no write to my OS X partitions or Windows Drive.
After the update I restored apps from TiB, and copied the data folders for some apps (apex launcher backups etc.), my TWRP folder and TiB folder back to my SD card. (using adb again) Then, with adb, I copied some films to a Media folder on the root of my sdcard, I created the folder with adb but now, with any file manager I can't write to the contents of that folder anymore, or change anything. Then I tried to make another, updated TiB backup, but it said insufficient storage space, even for just one app with well over 5GB of free space. Then I tried to do a TWRP backup using offline nandroid backup, however the backup completed in 0 seconds and made no new file or folder in the TWRP folder on sdcard. I then tried in recovery, the backup completed, but upon further inspection no new files or folders were made.
I think the problem is that any folders I have made through adb have no write permissions, even though mounted rw(x). And I cannot change the permissions. ( in Linux would I be able to cd to the directories on my n7 then sudo chmod 755 them?), I already tried this with mobile terminal however on my N7 and had no result. What is the solution for this problem?, should I wipe sdcard and make folders using a file explorer, then use adb to copy files into the premade folders, or just find a way to use Ubuntu to copy the files?
Thanks!
Sent from my Nexus 7
I have fixed it my self by doing this:
I was originally using the link from solid explorer to view and edit my sdcard files, which uses the /sdcard directory on root. For some reason I could not edit files going through /sdcard made from adb on OS X, however, when navigating internal storage through /data/media/0/ I had full permissions and could delete the folders made through adb, making new TiBu Backups and TWRP backups.
I tried using shell through adb to change permissions and remove the directories using:
Code:
adb shell
su chmod 777 /sdcard/(TWRP/TiBu etc...)
and
Code:
adb shell
rm -rf /sdcard/(TWRP/TiBu etc...)
but had permission denied errors.
Was on rooted 4.3 with PA3.99, backed up all apps and data using Titanium. Not sure which folder, but when I copied the /sdcard folder to my computer the backup folder was in /storage/emulated/legacy and it was full of .properties files. Now I'm rooted (using SuperSU) on 4.4.2 (stock ROM) and have put the folder in /sdcard but Titanium won't recognise it. I've tried changing the backup location to /storage/emulated/legacy, 'Force system BusyBox', fixing permissions in TWRP, and lots of other stuff I've found online that fixed it for others, but nothing works. If I create a new backup of an app, it recognises that fine, but if I change the name of the 4.3 backup file to the new one, it shows up as a valid file but restoring doesn't seem to do anything.
Hi,
I've recently rooted my I9505 using Philz Touch recovery method, and I adjusted the platform.xml file to allow Titanium Backup to write direct to external SD. After rebooting, I get several "Unfortunately, xxx has stopped" for several apps. When I connect the phone via MTP the Card and Phone storage spaces both show remaining space, but are both empty, and if I open ES File Explorer and look in the /storage folder it's completely empty, which I assume is causing the problems with the apps as they can't find their stored files.
I've tried putting a backup copy of platform.xml back in /etc/permissions while in recovery, checked permissions on that file are set to 644, and even reflashed the same stock ROM back on the phone using Odin, but the errors continue.
Is there a way I can fix this without doing a wipe data/factory reset? I can get adb access as root in recovery if needed.
Thanks in advance!
B
Done a bit more testing this evening and if I do a factory reset and reflash to stock then everything works as normal. I then reflashed Philz Touch and did a custom nandroid restore of /data only, and the problem returned (the nandroid backup was taken after the issue started).
So the issue points to something in the /data rather than something in /system or elsewhere, if that helps anyone to diagnose?