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
Related
So I've installed a custom ClockworkMod recovery and ROM on my Nexus 7 tablet. Life was good. Recently, I was running out of space and decided to delete my CWM backup (after saving it to my computer). And then, I realized I couldn't.
I went into ES File Explorer to try. I couldn't do it there.
I went into the ADB shell as root to try to remove it. No luck again, just the message when I finally DID try to remove one file:
Code:
# rm boot.img
rm failed for boot.img, Operation not permitted
What am I doing wrong?
Edit: This looks like it's ClockWorkMod (5.8.??)'s fault, but besides reading that another backup won't make the current one much larger, I don't actually know how to delete the current one.
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
BillGoss said:
Try "rm -rf ddd" (where "ddd" is the directory name) on the directory containing the files.
Sent from my Nexus 7
Click to expand...
Click to collapse
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
I did this in a way not mentioned here that still deserves mentioning... First I updated to the latest version of CWM available (via the Nexus 7 Toolkit) and then booted into recovery, opened the backup option, deleted the backup that was there, then cleaned the nandroids.
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
erica_renee said:
in the development section there is a cwm flashable.zip that will delete them.. Then upgrade to latest cwm or TWRP.. its a bug from older version of cwm.. its talked about in the dev cwm thread..
good luck..
Click to expand...
Click to collapse
primetechv2 said:
I could not find the aforementioned flashable zip, and because of the new CWM I had, I wanted to attempt a proper method of removal before running another rm command via the terminal. Therefore I could not verify the other methods mentioned here, my apologies.
Click to expand...
Click to collapse
Sorry for re-opening an old thread, but I am having a problem where I have files that I cannot delete from the clockworkmods/blobs folder on my external sd card. So far, I have tried deleting them from a file explorer, deleting them as root from a file explorer, root and non-root deletes from terminal emulator, deleting through windows, adb shell deletes (with system booted).
I also wanted to try adb shell while booted into cwm, but I could not get the adb connection to work from recovery.
I also tried to find the zip file in the developer section and that's the real reason why I revived this thread...Does anyone know where the thread is with the zip file to remove these files?
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Kodiack99 said:
I think the only way to delete them is through cwm.Boot to recovery and use the menu to delete them.
Sent from my SGH-I927 using xda app-developers app
Click to expand...
Click to collapse
When I booted to recovery, I am able to delete each of the backups that I created. These all deleted correctly. I then went to Free unused backup files (to delete the files/folders in the blobs folder) and ran that and most of the files are gone. When I boot back into the phone, there are still some files/folders there and they seem to be taking up about 4-5 GB on the card. When I try to delete them through the file manager apps (either as root or not) they will not delete and the manager reports an error (before clicking delete, the manager displays a statistics report that says that the size of the files are over 2TB so obviously something is very messed up about them). I have also tried to delete them through the terminal (again as root and regular user) and they will not delete there either and they totally mess up the terminal window with unprintable characters (the only way to recover is to exit out of the current window and start a new one).
I finally fixed this problem last night by backing up all of my stuff (except the clockworkmod folder) to my computer. I then rebooted into recovery (latest version of CWM non-touch) and formatting the ext SD Card. When I rebooted there were still some folders there (including the clockworkmod folder). I did a format from within the OS and that cleared everything out. I copied all of my stuff back from my computer and I'm now good to go. Not sure how it got messed up to begin with, but the problem is fixed now. I think I'm going to stick with TWRP from now on.
Most of the files in my TiBU folder will copy. All the properties files, and ~half of the .gz files. Most of these are game backups for progress purposes.
Dragging and dropping using Windows explorer doesn't work (nothing will happen at all)
Using ES File Explorer from the phone doesn't work.
adb from the PC doesn't work (command line has entries saying something about permissions on the failed files)
Help? I'm aware I could try backing up to cloud, but that's a workaround vs actually solving the problem. Plus it takes a while.
deusfaux said:
Most of the files in my TiBU folder will copy. All the properties files, and ~half of the .gz files. Most of these are game backups for progress purposes.
Dragging and dropping using Windows explorer doesn't work (nothing will happen at all)
Using ES File Explorer from the phone doesn't work.
adb from the PC doesn't work (command line has entries saying something about permissions on the failed files)
Help? I'm aware I could try backing up to cloud, but that's a workaround vs actually solving the problem. Plus it takes a while.
Click to expand...
Click to collapse
I think TIBU needs a big update....I have same issue but my biggest problem is I can´t uninstall any system apps (there a some I don´t need) when I tap the uninstall button always same thing...."Cannot find the .apk file .....no problem whith my personally apk´s..?
Somebody same issue?
I ran into the same issue and solved (?) it by rebooting into recovery and doing an adb pull from there. It doesn't work from within Android like you said but once you're in the recovery partition things are different.
I think this not a problem with TiBu (or maybe it just needs an update like shivasrage said), because I can't copy my Nandroids to my PC either. I had to do a adb pull from recovery as well in that case. In fact, now that I remember, yesterday I tried to copy some backups I did in ES Explorer and some of them failed.
Android 4.3 is secure but that's messing with our old habits and making things more difficult.
Yeah but I had this problem before updating to 4.3
deusfaux said:
Yeah but I had this problem before updating to 4.3
Click to expand...
Click to collapse
Oh, that's weird. I never had this problem before 4.3.
I just went through this exact same problem with my TWRP backup files yesterday (Except in that case it was an issue with the latest 2.6 version of TWRP, not the Android OS). For Titanium Backup, I am going to have to go back today and count the files that I copied over to my PC using Windows Explorer and compare it to an adb pull under Recovery. There are so many files as part of the backup that I would never have noticed a couple of missing ones like I did on TWRP.
EDIT: Just checked and 427 files were copied over doing it each way with a full Titanium Backup (Windows Explorer or an adb pull), so it works fine for me. I am on Android version 4.2.2.
I solved the problem by installing BusyBox from Play Store (Normal install). Then, opened a command window (you can also do it using Terminal Emulator) from within my platform-tools folder in C and typed:
adb shell
su (grant permission in the phone)
busybox chown -R 1023.1023 /data/media/*
Click to expand...
Click to collapse
Now I can safely copy all files by drag-n-drop or adb pull from within android.
Cheers
Can someone walk me through solving this? I'm wanting to do a factory reset immediately, but I can't before copying over these Titanium Backup'd apps.
Why is this even happening?
ABD, ES File Explorer, everything is giving me a permission error. The latter said EACCES (Permission denied) Refused by system.
edit: nevermind. I narrowed down the offending files, and forced new backups by deleting the old ones and re-doing them. Something about the way TiBu wrote a handful of the backups was not allowing anything to copy the files.
EDIT: Solved. See post #5.
___________________________
I had 4.4.4 stock ROM, and installed stock 5.1.1 ROM ([ROM][Manta][5.1.1] *03.05.2015* [Factory Images]) with PhilZ Touch recovery, and it's driving me nuts.
1) All data from my 4.4.4 /sdcard is moved to /sdcard/0.
But the system continues to use /sdcard.
Can I move all content from /sdcard/0 to /sdcard to have it all in one place?
2) I use Total Commander with the ADB file system plugin to copy files to my Android devices.
But now I cannot access /sdcard/clockworkmod anymore, since it doesn't show up.
I can only see it in /data/media/0/clockworkmod and it shows owner and group "0", whereas all other folders/files have "1023" as owner/group....?
Does anybody know why?
random_n00b said:
But now I cannot access the /sdcard/clockworkmod folder anymore, since it simply doesn't show up.
I can only see it in /data/media/0/clockworkmod and it shows owner and group "0", whereas all other folders/files have "1023" as owner/group....?
Does anybody know why?
Click to expand...
Click to collapse
User 0 is root, that is superuser. Any other number means normal underprivileged user.
I use twrp, and I never faced this problem.
[email protected] said:
User 0 is root, that is superuser. Any other number means normal underprivileged user.
I use twrp, and I never faced this problem.
Click to expand...
Click to collapse
OK. I'll give TWRP a try....
Edit:
TRWP does not move data to /sdcard/0/. That's good.
But now /TRWP/ has user/group "0", so it's similar to CWM and /clockworkmod/.
You may back up your data with adb pull or the twrp file explorer and then format back
Envoyé de mon Nexus 10 en utilisant Tapatalk
Finally I found a fix for my problems here.
That solved all access issues I had with the /clockworkmod an the /TWRP folders before.
:laugh::good:
___________EDIT________________
Made a few more tests.
When I switch back to Philz Touch (CWM), alle new backups are *again* not accessible. I need to run the "restorecon" command again to make the new backup folders accessible.
With TWRP no such problems. New backup folders are accessible right away.
--> Philz Touch caused all the problems I had. Will stick with TWRP from now on.
Not sure though if Philz Touch is the root cause, or the combination of ROM + Recovery...
Hey people!
I just got a nexus 7 2012 and i am wanting to mount it in my car. So i wanted to do a few things before that.
I updated to official 5.1.1 via OTA. Everything is STOCK
First step was rooting which SEEMED to work (DID it via WUGS). It installed SU and busybox. Next step was to create my own bootanimation
This is where the issues have started. I can not change permissions or move any files to the system directory even with W/R option turned on
I can delete the files but can not copy files to the directories. I can no change permissions in ANY directory.
I have tried in root explorer mounting r/w ES file explorer R/W ... i tried to install a new busy box and it installs then immediately says "you installed but it seems there is an older version on the system" i can not uninstall busybox. I tried mounting in terminal and it says all partitions are EXT 4. I have tried rerooting. Root check says everything is fine. SU seems to be working fine (it elevates permissions for all the root apps).
But for the life of me it will not copy anything into / or /system. :crying:
Should i just forget it and install another rom, WIPE everything and start again? If ROM which one is the best at the moment (nexus 2012)
After 2-3 hours of messing about... I just TWRP and flashed a different SU and it starting working.
I've looked all over and I'm unable to find a solution or even what's stopping me from modifying the /system folder in the root directory. I can remove files from that folder and all of it's subfolders but I'm unable to add any files into that directory. I am rooted on the T-mobile OnePlus 6t that has been converted to the international ROM. I know my root works cause I can perform other root functions. I also cannot modify the /system folder from TWRP either which is really strange to me. Also, when TWRP prompts me to install the app, it just reboots recovery since it's trying to install it as a system app which I can't do for this odd reason I have yet to find out. This issue all of a sudden showed up after an OTA update and re-rooting after. I have tried reinstalling TWRP, Magisk and Oxygen OS itself but the issue persists. I have also tried running "reboot disemmcwp" as root in a terminal window AND using adb but I guess that command no longer works. Any suggestions welcome as this is the last place I can find an answer to this issue.
Edit: found out I'm unable to uninstall system apps for some reason. So the issue isn't space related.
Toilet Clauger said:
I've looked all over and I'm unable to find a solution or even what's stopping me from modifying the /system folder in the root directory. I can remove files from that folder and all of it's subfolders but I'm unable to add any files into that directory. I am rooted on the T-mobile OnePlus 6t that has been converted to the international ROM. I know my root works cause I can perform other root functions. I also cannot modify the /system folder from TWRP either which is really strange to me. Also, when TWRP prompts me to install the app, it just reboots recovery since it's trying to install it as a system app which I can't do for this odd reason I have yet to find out. This issue all of a sudden showed up after an OTA update and re-rooting after. I have tried reinstalling TWRP, Magisk and Oxygen OS itself but the issue persists. I have also tried running "reboot disemmcwp" as root in a terminal window AND using adb but I guess that command no longer works. Any suggestions welcome as this is the last place I can find an answer to this issue.
Click to expand...
Click to collapse
Known issue that in the Newer OxygenOS versions there is no free space in /system. I'd download Solid Explorer and check the Free Space in the Root Directory.
Sent from my OnePlus6T using XDA Labs
Mannan Qamar said:
Known issue that in the Newer OxygenOS versions there is no free space in /system. I'd download Solid Explorer and check the Free Space in the Root Directory.
Click to expand...
Click to collapse
I've thought about that before. I use root explorer and can see there's more space than needed for the files I want to insert. Is there some buffer space needed in there and how much?
Toilet Clauger said:
I've thought about that before. I use root explorer and can see there's more space than needed for the files I want to insert. Is there some buffer space needed in there and how much?
Click to expand...
Click to collapse
Well, if you go to magisk and select core only mode then reboot you will be able to modify system
toolhas4degrees said:
Well, if you go to magisk and select core only mode then reboot you will be able to modify system
Click to expand...
Click to collapse
I was actually able to find the issue. Space was the issue. I guess there's a space buffer needed from what a file explorer says is left and what's actually left. I uninstalled a couple system apps I disable anyway and was able to insert files/apps into system again.
I made space easy I have the new OnePlus camera apk 125mb the old one is 67mb