Develop Bugs

What files can be safely deleted in the HTC Desire Root folder?

I've been looking at the root folder using Astro and there are several files/folders. Can any be deleted, without causing any problem? I'm running out of space and am hoping some are just temporary files etc...
For example I've spotted the APK files are in \system\app. I never use the Peep or Teeter apps. Can I safely delete their APK files?
Thanks
p.s - I am using an unrooted HTC Desire.

bradavon said:
I've been looking at the root folder using Astro and there are several files/folders. Can any be deleted, without causing any problem? I'm running out of space and am hoping some are just temporary files etc...
For example I've spotted the APK files are in \system\app. I never use the Peep or Teeter apps. Can I safely delete their APK files?
Thanks
p.s - I am using an unrooted HTC Desire.
Click to expand...
Click to collapse
you cant delete them using astro, we only have write access to /system in recovery, use adb in recovery to delete them
edit, without root you cant delete anything lol

bradavon said:
For example I've spotted the APK files are in \system\app. I never use the Peep or Teeter apps. Can I safely delete their APK files?
Click to expand...
Click to collapse
In addition, deleting anything from /system won't actually gain you any more space for applications anyway due to the way that the filesystems are partitioned.
Regards,
Dave

Thanks guys. I take it you mean we've got write but not modify access to the \system folder? So we can write to existing files but not delete them.
I wasn't just asking about \system though but any files/folders in the Root folder. Are there any at all, that can be safely deleted? Or are you saying you cannot delete a thing without rooting?
Not that it sounds like it will make any difference, due to partitioning.
Thanks

Ok to put it as simple as possible:
- no you cant pretty much delete a thing apart from sd without root
- we cant do anything in the system partition while the system is booted due to the nand protection
- we can modify /system while in recovery (using adb)
- when you are running out of space it is on the /data partition, which have a fixed size so deleting from /system or anything else won't help
And at last my advice to you is to go root and install a2sd easy as pie and i've never had space problems since.

Thanks for the informative reply mortenmhp

I have just rooted my 2.1 Desire, trying to remove two of the mms.apk and one other mms file in the /system folder so I can install a different mms.apk, however when I try to do it, it says I dont have the proper permissions. Its rooted, I see the Super User icon in applications.
Any suggestions?

Please read a little before asking questions. It is commonly known, that we dont have full root access on the desire yet.
Due to the nand protection you cant edit the system partition while the system is bootet. You have to use a custom recovery image either via fakeflash or installed by unrevoked. Then you can edit the system partition by using adb commands.
Edit: which i also stated quite clearly 2 posts above yours several months ago

Is A2SD better than the Android 2.2 implementation? Which as far as I can tell just moves the APK (not apps/data) to the SD Card.
Thanks.

Well it is kinda off topic here but in my opinion yes it is better. I'm running a2sd+ atm. and you can make it move /data/data as well.
In froyo there have been some complications though when remountingSD after using it as mass storage. But you can read more about that elsewhere(i would provide a link but I'm writing from my phone)
So the conclusion must be that it is down to personal preferences

Thanks because the official implementation is something of a cop out. On WM you could run the entire App/Data etc... on an SD card.

Does it matter what is used to remove crap apps?

I previously made the mistake of deleting crap apps without backing up the apk's and have since recovered them (that was pre-OTA), so I want to do it right this time. I know I can just move the apk's out of /system/app instead of deleting them completely, but does it matter how I do it? Would it mess up permissions or anything if I moved them with something like Root Explorer instead of using ADB?
Sent from my ADR6300 using XDA App

Unless you're desperate to recover storage space, it's generally better to simply rename the file rather than delete it. Just append ".disabled" or something to the end of the file names. This makes it a breeze to restore the system, as you can simply fix the names to get everything back to where it was before.

How to change permissions in the main system folder

Ok, here's the issue I want to copy over and ringtones and have them live in the same area as my current ringtones now I have root and tried to change permissions and u for an error message saying that some system folders and folders on sd cards cannot be changed. Ok......so now what
Sent from my SGH-T989 using xda app-developers app

I think extension of your ringtones have to be .ogg and then change permissions as usual with a root explorer app..
XX
X
X
like that. BUT I'm not quite sure if that's all that is needed.
And, I have tried putting them in as just .mp3 or .wav but they dont show up. SO, Im guessing it has to be .ogg

rastlin said:
Ok, here's the issue I want to copy over and ringtones and have them live in the same area as my current ringtones now I have root and tried to change permissions and u for an error message saying that some system folders and folders on sd cards cannot be changed. Ok......so now what
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
You need to set r/w with a file manager that has root access.
Sent from my SGH-T989 using xda premium

If you mean copy your ringtones to your system file ( so they work even with USB storage connected ), I actually did that recently; here's some things that might help:
1. For some reason, some apps have trouble making the system R/W, so if one doesn't work, try another one. Root Explorer and FX Explorer always seem to work flawlessly for me, but YMMV. Also, like it's been said, make sure you have system mounted as R/W; some apps might make it seem like it's mounted R/W when it's not.
2. MP3s should be fine, and I believe WAV files worked for me too.
3. This one took me a while to figure out; after copying the files, you have to reboot for them to show up when you're selecting tones.
Anyways, hope that helps.

cannot change frikin permissions
i have used both root explorer and FX explorer (and i prefer the latter of the two) but when i try to change the permissions it basically say "FFFFFFFFFFFFFFUUUUUUUUUUUUUUUUU" even though i do have root i am not too sure why i cannot change the permissions of subdirectories? I know in windows you can make the subdirectories inherent the atributes of the parent directory but unfortunately my lack of linux/unix experience is abundantly apparent. Is there away to force the subdirectories to inherent the attributes of the parent directory, or am i just a dumbass barking up the wrong tree.. OH!, and yes just to state the obvious yes i am rooted....
DIMENSIONAL said:
If you mean copy your ringtones to your system file ( so they work even with USB storage connected ), I actually did that recently; here's some things that might help:
1. For some reason, some apps have trouble making the system R/W, so if one doesn't work, try another one. Root Explorer and FX Explorer always seem to work flawlessly for me, but YMMV. Also, like it's been said, make sure you have system mounted as R/W; some apps might make it seem like it's mounted R/W when it's not.
2. MP3s should be fine, and I believe WAV files worked for me too.
3. This one took me a while to figure out; after copying the files, you have to reboot for them to show up when you're selecting tones.
Anyways, hope that helps.
Click to expand...
Click to collapse

Unfortunately, I'm not sure how much more I can help then. Here's a few things though:
I know that you need to download some kind of additional app from the developer to enable root features in FX Explorer, and I think you might have to enable something in the settings.
When I'm using the app, system R/W seems to apply to the entire /system directory, so it affects the parent directories of the sub-directories that I trigger R/W in.
From what I've read, some people have issues with SuperUser functions working, even when they're rooted, so maybe it's your SU that's causing the issues? I'm not sure what the solution is, but I know people have posted various methods that might work in the forums.

File move error or bug?

I installed Slim rom and it moved all of my previous sdcard files to a different location. I tried to use ES File Explorer to move all the data (2.85gb) to the new sdcard location. Once the process completed there's a message saying low storage space when I should have 3.25gb avail.
*
I checked the location where it was supposed to move the previous sdcard files to the new location and instead it created many duplicates of the current roms sdcard location (inception style) and repeated until there was no space left.
*
I found the previous sdcard location under mnt/shell/emulated/. I selected to move the emulated folder. I don't know if this "emulated" is some sort of special android folder that I'm not supposed to mess with or not and maybe that caused this issue.
*
But then, when I went to the folder where the previous files were located and browsed it, all of the files are listed as having a file size of 0.00 and clicking on properties for any folder shows 0 folder size. So I can see the files there but its as if they have been overwritten or made inaccessible. So I'm a bit pissed at this point because I can't find where the files were moved to and the old files seem to have no file size. Yet, after deleting the repeated copied info it only freed up the 3.25gb of space. So it's as if my old files are still taking up space somewhere but I can't get to them or open them.
*
Next, I decided to move those old files again and this time I placed them on my extsdcard. When I moved the files again they were completely viewable and accessible, from the extsdcard, even though they can't be accessed at my old location. I also used multiple root browsers and none could access the old files at the old location.
*
Any ideas what could have gone wrong?

AngelsNecropolis said:
I installed Slim rom and it moved all of my previous sdcard files to a different location. I tried to use ES File Explorer to move all the data (2.85gb) to the new sdcard location. Once the process completed there's a message saying low storage space when I should have 3.25gb avail.
*
I checked the location where it was supposed to move the previous sdcard files to the new location and instead it created many duplicates of the current roms sdcard location (inception style) and repeated until there was no space left.
*
I found the previous sdcard location under mnt/shell/emulated/. I selected to move the emulated folder. I don't know if this "emulated" is some sort of special android folder that I'm not supposed to mess with or not and maybe that caused this issue.
*
But then, when I went to the folder where the previous files were located and browsed it, all of the files are listed as having a file size of 0.00 and clicking on properties for any folder shows 0 folder size. So I can see the files there but its as if they have been overwritten or made inaccessible. So I'm a bit pissed at this point because I can't find where the files were moved to and the old files seem to have no file size. Yet, after deleting the repeated copied info it only freed up the 3.25gb of space. So it's as if my old files are still taking up space somewhere but I can't get to them or open them.
*
Next, I decided to move those old files again and this time I placed them on my extsdcard. When I moved the files again they were completely viewable and accessible, from the extsdcard, even though they can't be accessed at my old location. I also used multiple root browsers and none could access the old files at the old location.
*
Any ideas what could have gone wrong?
Click to expand...
Click to collapse
It appears you are running a recovery that is not supported by Android 4.2.
Since android 4.2 modified the directory layout to make way for multi user support, recoveries had to be updated to flash properly.
You will need to more than likely move your data files to your computer by hand, delete all of the extra and then reimplement your data to the appropriate folder.
Make sure you update your recovery as well so you don't see this on future 4.2 flashes.
When 4.2 first released this was a common issue with recoveries. Once you get your data and apps backed up appropriately, you may need to wipe your data/internal storage to free up the "used" space. I put used in quotes because it may appear its not taking any space at all when in all actuality it is.
Sent from my SGH-I747 using xda app-developers app

I'm using the latest TWRP 2.3.3.1 I think is the version. Is that not a compatible recovery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

AngelsNecropolis said:
I'm using the latest TWRP 2.3.3.1 I think is the version. Is that not a compatible recovery?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Hmm... latest is 2.4.1.0 but 2.3.3.1 was definitely compatible... sounds like there's a different underlying issue out of my realm of expertise. We'll have to wait for someone else to come along. Sorry man =/
Sent from my SGH-I747 using xda app-developers app

I'll update my recovery anyways. I've fixed the problem by moving everything again but in smaller sections. I may take up your advice to connect to a pc and back up everything, format it, then move the files back though. I just don't want to duplicate the issue again. It was a huge inconvenience. Thanks for posting.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

AngelsNecropolis said:
I'll update my recovery anyways. I've fixed the problem by moving everything again but in smaller sections. I may take up your advice to connect to a pc and back up everything, format it, then move the files back though. I just don't want to duplicate the issue again. It was a huge inconvenience. Thanks for posting.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
no problem man, sorry I couldn't help more. good luck with it! may have just been a fluke bad flash.
Sent from my SGH-I747 using xda app-developers app

Limited access to file system?

I was side loading an app from my phone to my tablet, incompatible in market. Well when I tried to copy the obb into the obb folder on my tablet it said access restricted... can't get it to copy even with root explorer.
Sent from my Nexus 7 using xda premium

whoamanwtf said:
I was side loading an app from my phone to my tablet, incompatible in market. Well when I tried to copy the obb into the obb folder on my tablet it said access restricted... can't get it to copy even with root explorer.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Are you rooted...?

I noticed something similar to this as well. I used TiBu to restore the SwiftKey app and settings from my 1st Gen N7. After restoring it, the English language pack wouldn't download. After Googling around, they recommended deleting languagepacks.json from the sdcard/Android/files/com.whatever directory and even with root access and Root Explorer I wasn't able to delete the file. I had to do it through TWRP and even that didn't solve the issue. I had to format internal storage to solve my issue. Needless to say, I've been much more careful about using TiBu since then.
Sent from my SGH-T999 using xda premium

alicarbovader said:
Are you rooted...?
Click to expand...
Click to collapse
Yes, yes I am. But you should not need root for these folders anyways.
Sent from my Optimus G using xda premium

I got it working with a different file manager, but I am still unable to copy the Titanium backup folder to my computer via usb, or airdroid. Weird thing is I cannot even use a zip app to zip it up then move the zip.

whoamanwtf said:
I got it working with a different file manager, but I am still unable to copy the Titanium backup folder to my computer via usb, or airdroid. Weird thing is I cannot even use a zip app to zip it up then move the zip.
Click to expand...
Click to collapse
I actually ran into a similar issue on my N7v1 last night. I wanted to copy over all my apps and settings, so I attempted to copy the various files in my Titanium Backup backup folder. I tried using adb pull, but it failed to copy over any of the apks. The other files (properties, etc.) copied, but not the applications. This seemed very weird. Then things got weirder.
I looked at the ownership/permissions/etc. and they were all identical. I had read/write access to everything. So I tried tar'ing them all up on the device, as root, to copy over one big archive. No dice. Even tar couldn't read the files. I tried coping them to another directory, but that failed too. I could only move or delete them - not copy/read/etc.
I assumed maybe something was wrong with the backups, so I deleted them all and redid the TiBu backup. Problem persisted even on these new files I just made.
It reminded me of an issue I had with TWRP when Android changed around the file system location of the sdcard. When that happened, I couldn't access my nandroid backups either, or even delete them. I actually had to make a flashable zip to get rid of them.
So I had an idea. My current TiBu backup location was "/sdcard/TitaniumBackup". The /sdcard directory points to "/storage/emulated/0/". So I deleted all the backup files again, changed the TiBu backup location to the latter and ran the backup process again.
Voila. I could now read/copy/everything all the files in that same directory, albeit with a different path.
Anyway, I thought I would share this because it sounds like a similar issue. Try using the full path and not the /sdcard shortcut and see if that works.