[FIXED] Can't remove remaining facebook files - G3 Q&A, Help & Troubleshooting

Hello guys,
I have 2 remaining .cnt files in /data/data/com.facebook.katana/cache/image/v2.ols100.1/44 and /data/data/com.facebook.katana/cache/image/v2.ols100.1/45
The thing is that they can't be removed in any way. I am rooted and tried with TWRP's file manager, ES file explorer and adb shell. All I get is:
Code:
rm: com.facebook.katana/cache/image/v2.ols100.1/45/OiSR12MweCzGONMN1iX7RFU4zN4.cnt: I/O error
rm: com.facebook.katana/cache/image/v2.ols100.1/45: Directory not empty
rm: com.facebook.katana/cache/image/v2.ols100.1/44/5F38tB3DUq0HT5gzyfpNDbnOAwY.cnt: I/O error
rm: com.facebook.katana/cache/image/v2.ols100.1/44: Directory not empty
rm: com.facebook.katana/cache/image/v2.ols100.1: Directory not empty
rm: com.facebook.katana/cache/image: Directory not empty
rm: com.facebook.katana/cache: Directory not empty
rm: com.facebook.katana: Directory not empty

Related

[Q] android problem

trying to run android on top of windows mobile 6.1 on a o2 xda stellar. but the instructions on http://www.androidonhtc.com/ says put androidinstall.tar on the memory card, but none of the builds come with androidinstall.tar, they come with androidinstall.tgz
I re-named it but when installing on the phone using haret it says unable to open androidinstal.tar. so then when trying to boot it has no system files as it hasn't installed them. so i get error no:2 when trying to boot.
any help?
try opening the .tgz see if there is an androidinstall.tar inside of it. If not then place it in the install directory instead.
aceoyame said:
try opening the .tgz see if there is an androidinstall.tar inside of it. If not then place it in the install directory instead.
Click to expand...
Click to collapse
no there isnt an androidinstall.tar inside of it.
r.lepecha said:
no there isnt an androidinstall.tar inside of it.
Click to expand...
Click to collapse
then rename it androidinstall.tgz and install it like you would a .tar file
thoughtlesskyle said:
then rename it androidinstall.tgz and install it like you would a .tar file
Click to expand...
Click to collapse
tried it, it still says unreadable file because it makes it into a .tar file with the the .tgz as another file inside
Why not try just not renaming it and keeping the .tgz extension? If all else fails the build i have, my bare bones one inside the rar file sits an androidinstall.tar
i extracted it, and i have re-compressed to .tar, going to try that
failed to extract. can some one give me a printscreen of what is in each folder because im confused now.
I think it would be nice if all the releaser make the same compression for the rom rls, if it would be .tar inside zip or just .tgz
It would make you guys not have to answer this question too many times.
Edit : If you can't extract it, does that mean your file corrupted?
vellowax said:
I think it would be nice if all the releaser make the same compression for the rom rls, if it would be .tar inside zip or just .tgz
It would make you guys not have to answer this question too many times.
Click to expand...
Click to collapse
i have now got the .tgz to install but i get many IO errors. and then when it goes to boot all it does is go blank? any help on that?
Android Installed
Fixing Permissions on files
chown: /data/app_s: No such file or directory
chmod: /data/app_s: No such file or directory
chown: /system/bin/su: No such file or directory
chmod: /system/bin/su: No such file or directory
chown: /system/init: No such file or directory
chmod: /system/init: No such file or directory
sh: 2: unknown operand
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop1 is mounted
/dev/block/loop1: clean, 544/65536 files, 83557/262144 blocks
e2fsck 1.38 (30-Jun-2005)
e2fsck: while determining whether /dev/block/loop0 is mounted
/dev/block/loop0: clean, 272/65536 files, 25007/262144 blocks
mount: mounting /data/sysfiles/su on /system/bin/su failed: No such file or directory
my file setup is
\root\default.txt
\root\haret.exe
\root\intrd.gz
\root\KAISimg.nbh
\root\rootfs.img
\root\zimage
\root\andboot\androidinstall.tgz
\root\conf\with lots of .conf files inside
\root\media\audio\....etc etc
\root\media\resource\with images inside.
i now managed to get it to boot into android. but it didnt extract the androidinstall.tgz so the system files aren't there. can some one please send me a link to download the androidinstall.tar because no matter what I do with the .tgz it doesn't work.
http://www.mediafire.com/?5ioe4z80db9e7dm that is my barebones android. Basically you just use market and configure it the way you want. I linked you my De-odex'd release 3 which is more configurable.
thanks a lot.
going to try it now.
edit : still doesn't work.
i dont know what else to try

Error While Restoring /data! - Please help

Hi, have a Galaxy Nexus running Modacco 10. this morning Google+ updated and finished successfully, i went to browse chrome and suddenly my phone restarted and bootlooped.
Out came the battery, back in, nothing
Tried to restore but failed on Restoring /DATA!
Formatted all partitions NO ERRORS!
tried to do an advance restore to Data and got the following - Error While Restoring /data!
I have tried to flash basic rom on which is on the SD Card and still nothing. It hangs!
Can any one help please?
The log i get is:
Error While Restoring /data!
rm: can't remove 'tombstones/tombstone_3'; Read only file system
rm: can't remove 'tombstones/tombstone_4'; Read only file system
rm: can't remove 'tombstones/tombstone_5'; Read only file system
rm: can't remove 'tombstones/tombstone_6'; Read only file system
rm: can't remove 'tombstones/tombstone_7'; Read only file system
rm: can't remove 'tombstones/tombstone_8'; Read only file system
rm: can't remove 'tombstones/tombstone_9'; Read only file system
rm: can't remove 'tombstones; Read only file system
rm: can't remove 'user/0'; Read only file system
rm: can't remove 'user'; Read only file system
tar; cant remove old file data/radio/nv_data.bin read only file system nv_data.binError while restoring /data!
Any help i would be very grateful!
Thanks
Fastboot fixed it
nick w said:
Fastboot fixed it
Click to expand...
Click to collapse
what did you do in fastboot?
4569294 said:
what did you do in fastboot?
Click to expand...
Click to collapse
Some people only care about seeing their own problems solved.
Restore crash
HI. I have the same probl with my Galaxy Nexus. I flash custom rom CM9...but in one day the phone reboot and start to loop. I reinstalled again CM9 from zip. I made a backup from ClockworkMod(pressing power and volume buttons) and after i tried to put back the stock restore. This crash. Adter i tried to restore the previous backup of CM9. Both crash and give this error: error while restoring /data. Pls help me because now i cannot restore nothing. Also the install again of CM9 from zip don't want to work.

Maguro 4.0.3 stuck in boot loop

Yesterday I restarted my Galaxy Nexus after it had problems with GMaps locations.
The following then happened.
1. Vibrate.
2. Google Logo (unlocked)
3. Restart
I've tried reflashing AOKP, wiped cache/data and I'm still getting the same issue. I can open recovery fine.
Any tips?
The following shows up when I try to restore:
Code:
"Error while restoring /data!"
rm: can't remove 'tombstones/tombstone_03': Read-only file system.
rm: can't remove 'tombstones/tombstone_04': Read-only file system.
rm: can't remove 'tombstones/tombstone_05': Read-only file system.
rm: can't remove 'tombstones/tombstone_06': Read-only file system.
rm: can't remove 'tombstones/tombstone_07': Read-only file system.
rm: can't remove 'tombstones/tombstone_08': Read-only file system.
rm: can't remove 'tombstones/tombstone_09': Read-only file system.
rm: can't remove 'tombstones': Read-only file system.
rm: can't remove 'user/0': Read-only file system.
rm: can't remove 'user': Read-only file system.
tar: can't remove old file data/radio/nv_data.bin: Read-only file system
nv_data.binError while restoring /data!
I tried [fix permissions], and while it fixed a few permissions, when I tried to restore, I get the same Errors while restoring /data. A reflash of AOKP+full wipe still leave me in a boot loop.

[Q] Need help deleting a directory

So here's the thing i've been exploring the possibilities of USBHost and decided to try an usb stick so i installed Paragon https://play.google.com/store/apps/details?id=com.paragon.mounter
It took me a while to get the hang of things. At first my usbstick was formatted in fat32. I specified in paragon i would like the default mount point to be USBStorage instead of /paragonNTFS. I made a small typo at first and named the folder usbStorage
now here comes the problem.
for some reason the app created 2 subfolders called sdb1 and sdb2 and i cannot remove them
Things i've tried:
cyanogenmod file manager in root access mode
-- delete directory > "This operation needs elevated permissions. Try switching to root access mode" (translated from dutch so wording may be a bit off
-- modifying permissions of folders > denied > changing permissions failed. for security reasons some filesystems, such as on sdcards do not allow changing permissions
Same problem for Astro file manager
Same problem when attaching the tablet to computer. parent directory (and sub dirs) get "removed" in windows but when checking the file system on the tablet, the opposite is true and the directories is still present
and now it's starting to piss me off. I want that folder "usbStorage" and it's subfolders "sdb1" and "sdb2" removed. so my guess is it'll have to be done by terminal commands but my terminal experience is ZERO.
in preperation of you guys helping me installed https://play.google.com/store/apps/details?id=jackpal.androidterm the same one used in cyanogenmod roms. I tried a bit of tinkering myself but prob doing something wrong
what i've tried (in sequence, --ok behind the command means it was succesfully executed)
su --ok
cd sdcard --ok
*rm -rf /usbStorage >> *rm: not found
rm -rf /usbstorage --ok, but folder was still present
rm -rf usbstorage --rm failed for usbStorage, Directory not empty
cd usbStorage --ok
rm -rf sdb1 --ok, rm failed for sdb1, Permission denied
at that point i gave up. I hope you guys can help me out
I do have paragon configured properly now and my USBstick in NTFS is getting recognised. Upon mounting of the usbstick, it now creates a folder called "USBStorage" where the contents of the usb stick is properly displayed.
so where are those android terminal / linux masters to help me out
only thing i can add is that when opening paragon with the stick attached but unmounted i do see a line above it /dev/block/sda1 but that doesn't seem to affect mounting in the specified directory
Bump, anyone? I want and need this folder removed
Verstuurd vanaf mijn Nexus 7 met Tapatalk
From my understanding of your post.
You are rooted and using cyanogenmod?
Did you try going into the app information and clear data?
In the app drawer hold the app and then drag it to App Info
Clear data.
Did that solve it? If not continue below.
Make sure you don't have the USB stick mounted and or plugged in.
Then go into terminal and type
su
Then type.
mount
The mount command shows all listed mount points. If you don't see the usbStorage or whatever mounted.
Then type.
busybox rm -rf usbStorage
Or whatever the main directory is...
For example directory is at.
/sdcard/usbStorage
cd /sdcard
rm -rf usbStorage
Let me know how you make out.
Sent from my Galaxy Nexus using xda app-developers app
nope, my phone is running CM 10.2 (not relevant to the question) this is the nexus section and its my nexus 7 2013 running stock rom but rooted yes that needs the folders removed.
The folders i need to delete according to the Nexus 7 mount main mount path SD content
main path: /storage/emulated/0 or /storage/emulated/legacy (both are the same according according to ParagonNTFS as a folder the mount path /sdcard/USBStorage = /storage/emulated/0/USBStorage or /storage/emulated/legacy/USBStorage
important lines?
/dev/fuse /storage/emulated/0/ fuse rw,nosuid,nodev,realtime, user_id=1023, default_permissions,allow_other 0 0
/def/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatimeuser,user_id=1023, group_id=1023,default_permissions,allow_other 0 0
folders to delete are
/storage/emulated/0/usbStorage
/storage/emulated/0/usbStorage/sdb1 <= can select these just fine
/storage/emulated/0/usbStorage/sdb2
/storage/emulated/0/ParagonNTFS <= simply selecting this folder prompts CM manager "this operation needs elevated priviledges. Try switching to rootmodus, even when the CM filemanager already is in root mode
so i went
Opening terminal
su
cd sdcard (command ok)
cd usbStorage (commando ok)
busybox rm -rf sdb1
rm: can't remove 'sdb1': permission denied
Then i tried
cd /sdcard
rm -rf usbStorage
rm failed for usbStorage, Directory not empty
cd usbStorage
rm -rf sdb1
rm failed for sdb1, Permisison denied
busybox rm -rf sdb1
rm: can't remove 'sdb1': Permision denied
According to Cyanogen mod file manager:
Filesysteminfo:
Status: rw
linkpath?: /storage/emulated/0
Device: /dev/fuse
Type: fuse
Options: rw,nosuid,nodev,relatime,user_id=1023,default_permissions,allow_other
Dump / Pass: 0 / 0
even with the app ParagonNTFS uninstalled it doesnt work
hmm
try
close the app ParoganNTFS and uninstall it.
then try to delete those directories.
Also when you type
mount
does it show any of the directories you are trying to delete as mounted?
if it is try
umount /sdcard/usbStorage/sdb1
rm -rf /sdcard/usbStorage/sda1
were you able to delete the dir?
I had the same problems under very similar circumstances. Stickmount rather than paragon. The only way I could delete the dir was to boot into recovery (team win recovery project v2.7.1.1) and delete it with TWRP's terminal command. Something in the OS apparently locks on to the mount and simply will not let it go ever. It has to be done before android starts. It's very annoying. I am beginning to really be disgusted with many of the decisions google is making with regard to android. Why do they hate sdcard expansion so much? its absurd.
---------- Post added at 04:22 AM ---------- Previous post was at 04:17 AM ----------
Oh and by the way, even though the OS latched on to that folder as if its very existence depended on it, I was never able to even see the files on the USB memory stick with any file explorer. Worked just fine in kit kat and before. In some ways lollipop really sucks.

Need the file platform.xml

Hello,
I'm not sure this is the source of my problem but can someone post the content of his /etc/permissions/platform.xml file please? (on stock Android 5.02)
After trying the app "GL to SD" on my tablet, the internal memory /sdcard and equivalent folders (/storage/emulated/0, /storage/emulated/legacy, /storage/sdcard0) are not accessible.
I still see them in command line with ADB, but from the tablet the command line ls in /sdcard gives opendir failed: permission denied.
Or if you have any other idea...

Categories

Resources