This is driving me crazy. I want to copy the TitaniumBackup folder from my GNEX to my Win7 PC.
Looking at the folder through Root Explorer on the GNEX all appears normal. When I look at the folder through my computer the folder is showing but the contents are backups that are almost a month older than are on the GNEX. If I delete everything in that folder FROM THE PC it still exists on the GNEX.
It is like it is looking at a different folder entirely however looking and searching through ROOT EXPLORER there are no other TITANIUM BACKUP folders.
This happens with a lot of apps. Example: I created a ZIP file using ROOT EXPLORER. The zip, viewing through ROOT EXPLORER is located in the /SDCARD/SPEEDSOFTWARE/ZIP folder however when I look at the SPEEDSOFTWARE folder via my PC the folder is empty.
I have tried both MTP and PHOTO mode. This happens with a lot of folders when trying to view them from my PC connection. Some stuff is there and a lot is not.
Hmmm, there is a /MNT/SDCARD and a /SDCARD folder (I don't know much about Linux) and the files I am NOT seeing on my PC are in /MNT/SDCARD and the files I am seeing are in /SDCARD. Why are there 2 different "SDCARD" folders? I changed the TitaniumBackup to save to /SDCARD instead of /MNT/SDCARD but the backups are still not viewable (or copyable) from my computer. I just don't get it.
So the question is, how do you "backup" the contents of the "SDCARD" directory if you can't see the files when plugged into the PC?
Well, after comparing all the "visible" files on my computer when I access the GNEX via MTP vs what I see using ROOT EXPLORER the ONLY 2 folders NOT visible from my PC are TITANIUMBACKUP and SPEEDSOFTWARE (thus is the ROOTEXPLORER app data). Why would they be hidden?
It's due to how the Android MTP service works. It hasn't scanned your internal storage for the new files/directory to present to your PC yet.
Download and run an app called SDrecan from the Market. This will force the media services on your phone to rescan the device.
Sent from my Galaxy Nexus using XDA App
Absolutely amazing! Thank you so much! I have been pulling out my hair for days!
thank you! I had the same problem!worked flawlessly!
silow said:
Download and run an app called SDrecan from the Market. This will force the media services on your phone to rescan the device.
Click to expand...
Click to collapse
Thanks! This was really driving me crazy...
is there one for phones on android kitkat 4.4 and up
silow said:
It's due to how the Android MTP service works. It hasn't scanned your internal storage for the new files/directory to present to your PC yet.
Download and run an app called SDrecan from the Market. This will force the media services on your phone to rescan the device.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
this app is force closing. i cant even run it . do you have any idea? just today was working fine , i installed a custom rom and now when i try to put another roms on my sd card , i get this message that it's empty
trickster mod also has a media rescan option in bottom of tools section if this is helpful to you, I have to use it after using the "a better camera app" in order for pics to show in gallery without reboot
How the hell can i delete a folder that can't be seen via PC connection but i can see it using es file explorer?
I can't delete it using ES even with root enabled....
zerozoneice said:
How the hell can i delete a folder that can't be seen via PC connection but i can see it using es file explorer?
I can't delete it using ES even with root enabled....
Click to expand...
Click to collapse
Depending on where it is you need to mount it first. Which folder are you trying to delete?
Sent from my Galaxy Nexus
I had a folder that became corrupted (repeatedly interrupted game data downloads, I think). I was unable to delete it (even as root) and received an Access Denied error. I was able to rename the folder (so it wouldn't conflict anymore) and delete the majority of its contents (still received the Access Denied error on a file or two). I eventually had to do a full wipe via fastboot -w to get rid of the corrupted files.
had the same problem. had to reflash su.zip and it worked. can't explain it though. just reaching at straws
matt30 said:
Depending on where it is you need to mount it first. Which folder are you trying to delete?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
it's the folder created by the Photaf application.
i uninstalled the app and the folder is still there...permissions are writable, not hidden...
i can rename it, but can't delete it....and the subfolder within it as well...
i remember it happened once before and the only way to get rid of it was to reinstall the ROM (AOKP). Once installed, i could delete the folder.....
Try reinstalling the game and using settings/application/name of game clear data
Sent from my Galaxy Nexus
bwcorvus said:
Try reinstalling the game and using settings/application/name of game clear data
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
no effect, still can't be removed
LE: WTF, i just plugged in the phone into USB for charging and i saw the folder?! It deleted just fine?
Damn weird didn't do anything different than yesterday when i couldn't even see the folder via PC...
Thank you!
My Asus Transformer (TF101) hasn't been able to download anything to the Download folder for months now. Even Opera (which I installed just to try and fix this) could only download to a different folder. I did what you said, plugged it into the computer and first renamed the folder with ADB but couldn't create a new Download folder. "File already exists." Lies. Windows Explorer said it was still there as Download so I deleted it in Explorer and created a new folder named Download. The create failed but Android said it was there and Voila! I can download again. Very weird, but not ready yet to reformat in fastboot. Thanks guys!
If you're rooted you may be able to delete the files from /data/media, which is the true location, instead of the visual SD that you are seeing.
Could also be a file ownership issue.
Using a terminal emulator, use the following command to list ownership and permissions:
ls -l
(Lower case letter L, not i or 1)
Most of the files and folders should show up as media_rw, but the problematic ones may show up as numbers. To fix them, boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
I just unlocked, rooted and restored all files in my nexus. I went into root Explorer to delete unwanted files and am getting a delete failed error every time I try to delete a file. Also my screen shots are no longer saving it says storage is in use. Anybody experience anything like this after rooting?
Sent from my Galaxy Nexus
Marcg23 said:
I just unlocked, rooted and restored all files in my nexus. I went into root Explorer to delete unwanted files and am getting a delete failed error every time I try to delete a file. Also my screen shots are no longer saving it says storage is in use. Anybody experience anything like this after rooting?
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Are you trying to delete system files? Do you have SU installed? Are you clicking the R/W option. More details please.....
Several people have reported the issue with screen shot, to fix it they've had to rename the pictures folder(Seems like the folder is read only).
Swiftkey'ed on my CM9 Galaxy Nexus
No system files just old pictures, music files and other misc. It is set as r/w, also I am getting a few apps saying I need storage available that is writable. Something has to be up with the internal storage not allowing me to access or write to it.
Sent from my Galaxy Nexus
Well I am able to take screen shots by renaming he folder. However, I am still unable to write anything to my sdcard or modify files through root Explorer or any other file manager app.
Sent from my Galaxy Nexus
Root explorer - How to text edit
Hi All,
I have a problem with my root explorer. I am not able to open a file to edit. If i long press on a file , i dont get any option to open/edit the file.
i was supposed to edit gps.conf file under /system/etc but unable to do so from root explorer.
PS: i mount r/w from the root explorer every time i try..
Please help.
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
root explorer delete failed
danger-rat said:
If you have any directories/files that you can't modify or delete, then boot into CWM recovery, plug in the USB cable, go into adb shell. Also make sure that /data is mounted in the CWM mounts menu. Then:
cd /data/media
chown -R media_rw.media_rw *
Click to expand...
Click to collapse
i'm having this crazy "delete failed" error every time i try to delete any file in sdcart, external, and root directory (copy-paste, root, permissions works fine )
i tried to delete any remains of root explorer with es file explorer ((which works fine btw so its not a problem of partitions i think), re installed the program again but its the same . Flashed the rom from the beginning with a full wipe but its the same
this error happened first when i updated from blackmart alpha to some rootexplorer v.99. I uninstalled that but it left this error
Any idea what is causing that
I'm very curious and would appreciate it
thanks
I found a way to delete the files you suggest using Root Explorer. Go into /data/media/<navigate to the directory that you want to delete files>.. make sure the folder is mounted as r/w and delete the files you want to delete. This is how I bypassed the delete failed issue in Root Explorer...
rester555 said:
I found a way to delete the files you suggest using Root Explorer. Go into /data/media/<navigate to the directory that you want to delete files>.. make sure the folder is mounted as r/w and delete the files you want to delete. This is how I bypassed the delete failed issue in Root Explorer...
Click to expand...
Click to collapse
^^^^ this
Thank you rester, this worked for me too. Was pulling my hair out.
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
warlock257 said:
Hi
I recently restored my Nexus with the toolkit but when it put the files back, I think a permissions problem has occurred. I can rename folders, but I can't delete them. I have a rather large folder that I can't get rid of. When I try in various programs, it says delete failed, or no permissions, etc.
I am rooted, and have installed Terminal emulator, but am not terribly familiar with how to use it.
Any tips would be helpful.
Thanks
Click to expand...
Click to collapse
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
JoeSyr said:
Simple solution might just be that your file explorer app doesn't have root access. Force stop it in apps->settings, check your superuser app and clear any saved entries for it, and launch the app again. It should request root privileges.
Where are the files/folders in question located? If they're in a secure place like /system/ then it's more likely to be the above scenario. If they're just in your sdcard folder, are they user made, or at all special?
Edit: Also in the future, this sort of thing is what the Q&A forum is for.
Click to expand...
Click to collapse
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
warlock257 said:
I was using Root explorer, and have granted it root access
It is in /SDcard, so it shouldn't be anything that's protected
Click to expand...
Click to collapse
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
JoeSyr said:
Did you check the permissions for what you're trying to delete? They're displayed right in the normal view in root explorer, and you can edit them from the long press menu.
Anything unusual about the files/folders themselves? Were they created on the phone? By you? By apps? Copied and pasted over USB from a computer? You could try deleting from your computer over USB.
As for command line options, you can try 'rm -r [path]' for a folder and just 'rm [path]' for a file. rm is the delete(remove) command, -r is the recursive flag to apply the action to all items in the directory if a directory is the target. Pretty sure that you can do that straight from terminal emulator on your phone, and from a command prompt over usb you'd need to use 'adb shell' first.
Click to expand...
Click to collapse
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
warlock257 said:
In root explorer the info under the folder says
rwxrwxr -x
I'm pretty sure that the problem started when I restored from the nexus toolkit on pc. I had a similar problem with my camera in that it couldn't save pictures to a folder, but all I did was rename the folder, and the camera app created a new one.
rm -r [path] in terminal emulator says "permission denied"
EDIT
upon further googleing, the 'chmod' command might be what I want, but I'm not sure which syntax is right.
Click to expand...
Click to collapse
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
simms22 said:
at the top of root explorer, theres a button that says mount r/w. press it, now it should say mount r/o. go ahead and delete that file now
Click to expand...
Click to collapse
Found the button, but didn't work
JoeSyr said:
For chmod you want 'chmod [number] [path]', where number is a string that's a bit complicated to explain. You can learn about it by googling chmod probably better than I could type it out here on the fly. But if you use 777, it should assign full permissions, which would display as rwxrwxrwx in root explorer.
You can achieve the exact same effect in root explorer though, long press and choose permissions and you'll get a 3x3 grid. All boxes checked= full permissions, same as chmod 777. The three lower boxes for special permissions should be unchecked (fyi, they would turn chmod's numeric component into a 4 digit number, and as far as I know, android doesn't really use them at all).
Also, did you type su in terminal first? It doesn't innately have root (just like any app) so you need to do that and confirm the popup first. You'll need to do this before using chmod, and if you didn't do it before using rm, try it again.
Worth a try but just for reference, rwxrwxr-x is the normal permissions set for folders on the sdcard, so that's not immediately looking like a problem.
Click to expand...
Click to collapse
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
warlock257 said:
Found the button, but didn't work
it might be the files within the folder, rather than the folder itself. going into it, some of the files have a shield on them
When I go into its permissions, some of them were unchecked. I checked the 9 at the top, and it says:
"permissions change was not successful. Please note that some files systems (e.g. SD card) do now allow permission changes."
Click to expand...
Click to collapse
Well under normal circumstances, individual files on your sdcard should have permissions rw-rw-r--, and folders have rwxrwxr-x. (For reference, this is read as read, write, execute for Root, System, and Other, with dashes indicating that a permission is denied. So rwxrwxr-x means all permissions are granted to all three groups except for write to Other). This ties into larger aspects of the OS that basically exist to stop individual apps from reading or writing whatever they want without being included in groups.
The fact that you can't do something that shouldn't require elevated permissions, and you're getting that kind of error when you try to execute commands with higher permissions, suggests to me that your sdcard partition is using the wrong filesystem. Sort of sounds like a program tried to treat it like a real sdcard and formatted it to something else, in which case I have a hunch you're going to need to back up your data and do a full reset.
You might get a simpler solution if you ask in the thread for the toolkit you used. It's not something I have any experience with so good luck.
Out of curiosity, are you on Jellybean now? Jellybean changed the address for the sdcard partition, so if the toolkit wasn't updated to reflect this, it seems like the likely place things may have gone wrong.
---------- Post added at 07:04 PM ---------- Previous post was at 06:53 PM ----------
Actually if you want to check if it's using the right filesystem, run the command 'mount' from terminal. It'll give you a bunch of information, probably towards the bottom will be a line that mentions sdcard. Mine reads as
/dev/fuse /storage/sdcard0 fuse [more info about how it's currently mounted]
Yours -should- say that if you're on JB. If you're not, it should say something instead of /storage/sdcard0 (maybe /mnt/sdcard? I forget how it was on ICS). If it says something in place of fuse that may be the problem.
..I actually think mount used to say that the sdcard block was formatted as yaffs2, while everything else was formatted as ext4. Or maybe I just looked up that it was yaffs2 online, not from terminal on my phone? I wonder if this whole thing is the reason why some people seem bootloop-prone when flashing JB roms, if the changes have cut out access to important information about the filesystem, it may be triggering a really long error scan if their sdcard partition is large.
yes, backed up in ICS, and went to Jellybean.
doing a 'mount', I believe the line reads
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,realtime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
The files that have the shield icon have permissions:
rw-rw-r--
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
JoeSyr said:
Yeah so everything that I can think of for you to check seems to be displaying as though normal. Although I don't know what aspect of these files root explorer is reading to mark them as protected and put the little shield on them.
You've tried these methods (rm, chmod) on individual files within the folder too, right? I guess this comes more from experience deleting protected files in windows, but I've found that sometimes a folder will deny deletion as long as it contains protected files, but it's relatively easy to give yourself permission to delete the individual files one by one, after which the folder goes down too. Possibly time consuming without a batch function, but easy.
My understanding of the fuse filesystem, by the way, is that it's just a virtual layer that allows the sdcard block to be treated differently than everything else on the phone, which is important for what happens when you plug it into a computer and the device is read. And I believe that the sdcard is supposed to be formatted as yaffs2 (everything else is ext4). Not sure how to check that directly, but it's possible that it has been changed to something else. But unless you can't delete -anything- on the sdcard, this seems unlikely.
Click to expand...
Click to collapse
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
warlock257 said:
yeah, I tried deleting files individually on the phone, and in windows. Wont let me do anything.
I guess the only sure fire method of clearing these files at the moment is to do a factory reset.
I can back up my stuff with titanium, so not that big a deal.
Your assistance has been much appreciated
:good:
Click to expand...
Click to collapse
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
warlock257 said:
That worked :laugh:
It's gone from all those folders.
Thanks very much!!!!!
Click to expand...
Click to collapse
+1 This worked for me as well. Thanks for posting...:good:
Had the same problem. Deleting through the /media path worked.
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
+4 You Sir are a genius! Thanks given!
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Sorry to necro this thread almost 4 years later, but I had the exact same issue with deleting a folder on internal storage (Android Lollipop). Regardless if you're still here on XDA or not: thanks for this solution.
So.. Not really a I9250, but I guess my problem on i9100 is the same.
For some weird reason this just happened to WhatsApp directory.. But whatever.
After digging deeper and deeper in recovery, it seems like the folder wasn't own by media_rw group, but root
I just had to run
Code:
chown -R 1023:1023 <folder-path>
For some weird reason neither chown nor ls -l were correctly working when booted on normal system
Cilraaz said:
Try deleting them directly from /data/media instead. If you're able to delete them there, reboot afterwards to ensure /storage/sdcard0, /sdcard, and /mnt/sdcard are updated properly.
Click to expand...
Click to collapse
@Cilraaz, I have no idea if you're still on XDA but after at least a week of intense searching I found your advice which solved my problem! Thank you.
My problem was on i9500 (still) running stock Lollipop. I've been preparing to install a custom recovery, and did a TWRP (2.8.7.0) nandroid backup. Problem was I then couldn't find the TWRP backup folder. It would only show in TWRP's file manager. Root Browser didn't show it with SU privileges, nor ES File Browser and connecting it to the PC didn't help either. It's only after looking in /data/media/0 that I could find the TWRP folder.
Hi all,
I bought my GN off a guy back in March of this year. He told me it was rooted and all that, and I just recently found out it's running a version of the open KANG project or whatever.
Anyway, I want to use a different ROM, and my buddy gave me a bunch of instructions but I'm having a problem.
He told me to put the ROM and the gapps in the /sdcard folder, or /mnt/sdcard folder - But I don't seem to have either one of those folders.
He advised I get TitaniumBackup to backup some of my apps, which I have done, and I found the TitaniumBackup folder just sitting there in the main part of the phone, or the root I guess you'd say.
Also, when I did a backup from the Recovery screen as directed by him, it just saved the backup to a clockworkmod/backup folder, again in the root directory of the phone.
When I go into My Computer I see the "Galaxy Nexus" there. When I click on it, I get another icon which says "internal storage" then when I open that I have all these folders.
Other things like DCIM, Download, android, music, movies folders are all in this root folder.
What am I missing here? Why can't I see any /sdcard folder or /mnt/sdcard folder?
The folder you are in when you connect to your computer IS /sdcard.
Sent from my Galaxy Nexus using Tapatalk 2
Pirateghost said:
The folder you are in when you connect to your computer IS /sdcard.
Click to expand...
Click to collapse
Ding ding ding.
AHHHH ok
I didn't realize that, as I couldn't find anything telling me that!
Thank you!