Hello again everybody.
Here is a little tutorial to get rid of the crap thats shipped with the phone
and get it on a sweet diet of slimfast.
If you think to yourself "HEY! that shouldn't be removed!"
I most likely removed it because there is a Market alternative.
*Always be careful when modifying /system*
First we need to remount our phone and make /system/app - R/w
adb remount
then type:
adb shell
*In Shell ($)
su (IMPORTANT)
cd /system/app/
ls
Now you can start removing the bloat.
rm Launcher.* (ONLY IF YOU HAVE AN ALTERNATIVE LAUNCHER INSTALLED!)
rm Maps.*
rm SystemTutorial.*
rm LatinIME.* (MAKE SURE YOU HAVE ANOTHER KEYBOARD INSTALLED)
rm Email.*
rm Calculator.*
rm EmotionWeather.*
rm EmotionPhotoWidget.*
rm EmotionCalendar.*
rm EmotionPhotoAlbumWidget.*
rm EmotionBookmarksWidget.*
rm EmotionEvents.*
rm Twidroid.*
rm EmotionMemo.*
rm EmotionRSSReader.*
rm EmotionVideoWidget.*
rm EmotionClockWidget.*
rm HwIME.*
as always, reboot.
and, as with most things in the filesystem, this can also be done
with Root Explorer
If you messed something up, it probably wasn't meant to be
removed and most likely wasn't listed above. Start over from scratch...
unless you made back-up of course
If i missed anything, shoot me a message!
You honestly consider Calculator, Maps and Email "bloatware"?
raduque said:
You honestly consider Calculator, Maps and Email "bloatware"?
Click to expand...
Click to collapse
if they can be downloaded (and be more up to date from the market) then yeah.
You don't need to delete them to download the updated versions. My tablet prompted me to update them as soon as I connected to wifi and logged into my google account.
Updates take more space
When you update a Android app that is part of the rom it takes up 1.5 to 2x the storage than if you just simply download the newest version.
crispien said:
When you update a Android app that is part of the rom it takes up 1.5 to 2x the storage than if you just simply download the newest version.
Click to expand...
Click to collapse
That honestly means nothing to me. I don't load 500 apps on my devices.
raduque said:
That honestly means nothing to me. I don't load 500 apps on my devices.
Click to expand...
Click to collapse
look, when you delete /system files obviously it doesn't touch the /data... obviously... now your /system is on your INTERNAL partition so removing these files frees up space on your INTERNAL memory, and as for obviously downloading the updated apps from the market does update them YES AND INSTALLS THEM INTO /data, but it does not delete the OLD outdated version which still reside in /system which need to be updated and is taking up space, i hope this helps you understand whats going on... hopefully.
joenilan said:
look, when you delete /system files obviously it doesn't touch the /data... obviously... now your /system is on your INTERNAL partition so removing these files frees up space on your INTERNAL memory, and as for obviously downloading the updated apps from the market does update them YES AND INSTALLS THEM INTO /data, but it does not delete the OLD outdated version which still reside in /system which need to be updated and is taking up space, i hope this helps you understand whats going on... hopefully.
Click to expand...
Click to collapse
Yes, I understand this. But, they are two separate partitions. The S7 does not dynamically resize partitions. /system and /data are completely self-contained, and the size of either does not effect the other.
Space on /system, does not effect space on /data. I don't know how much plainer I can say this. All you're doing is freeing space on /system, but nothing goes there except pre-installed *system* files!
The bolded, underlined, italicized is the part that doesn't make any sense. It's taking up space in /system, which has no bearing on space in /data. Period, end of sentence, full stop. I'm not saying anything more on this matter, because I don't think you're going to get it.
raduque said:
Yes, I understand this. But, they are two separate partitions. The S7 does not dynamically resize partitions. /system and /data are completely self-contained, and the size of either does not effect the other.
Space on /system, does not effect space on /data. I don't know how much plainer I can say this. All you're doing is freeing space on /system, but nothing goes there except pre-installed *system* files!
The bolded, underlined, italicized is the part that doesn't make any sense. It's taking up space in /system, which has no bearing on space in /data. Period, end of sentence, full stop. I'm not saying anything more on this matter, because I don't think you're going to get it.
Click to expand...
Click to collapse
probably not, i can't get through the fog of cocky responses. instead of being a helpful person.
joenilan said:
probably not, i can't get through the fog of cocky responses. instead of being a helpful person.
Click to expand...
Click to collapse
Well, that's an interesting way of saying that you don't understand what I'm saying.
http://forum.xda-developers.com/showpost.php?p=11476068&postcount=9
Repeat after me:
"/system space is completely separate from /data space. One has no bearing on the other"
Once you have saved some room on /system/app, you can then move some of the apps that you have in /data/app to that directory. I have done this for swype, adw, facebook, google apps, documents to go for example, this is saving me an extra precious 40M.
dear joenilan..
pls help..i have remove the home launcher .replace with vtl.
i do factory reset and forgot restore with Titanium before
now face boot loop ..what should i do now.
dont have cwm in my ideos
thx big for advice
rgds
sasmitadani :
Flash a new room,
http://forum.xda-developers.com/showthread.php?t=1043349
http://phonedock.net/huawei-ideos-s7-froyo-2-2-2-update.html
http://www.androidtablets.net/forum...uawei-ideos-s7-official-firmware-2-2-2-a.html
I would also request that the OP's post be removed, or huge big letters of warnings or better described procedures be added, this can be very harmful and really makes no sense.
Related
I dont want to use app2sd as I feel it a bit unnecessary and I really don't need too much more space. I saw WES incorporated moving dalvik cache to the cache partition (cache part is 80 megs that will never get fully used on the slide). I asked in his thread twice but it seems it'll never be seen. Any way, I did some searching and found a script that does exactly what I want. This would also be useful for those like me that just want a few more mb's of internal storage and dont want to use apps2sd. I'm not a developer so I just want to put this here for our devs to mod or give the okay on if this will work on the slide.
I got the script attached from this thread. You can also read in more detail on what exactly it is I'm wanting to do here http://forum.samdroid.net/f9/relocate-dalvik-cache-free-up-space-1117/
I just want to know what has to be done if anything to get this working on the Slide. Thanks
I was able to get dalvik-cache to /cache by going into clockworkmod recovery and accessing from adb:
mv /data/dalvik-cache /cache/dc
ln -s /cache/dc /data/dalvik-cache
After the files are moved and the symlink is created, you should have no problems when rebooting.
However, I came across a problem when I flashed the radio, since it wiped the cache partition. If you are missing all your installed apps in android, it might be that the cache partition was wiped. You need to recreate the /cache/dc folder and reboot.
Thanks for the input. finally someone! ..thats good to know Im going to try it now, I didnt think it would be as simple as a move command.. any reason the radio wipes the cache partition? did dalvik recreate itself after the wipe in /data? and were ALL the apps gone or just the few that took up the memory?
turboyo said:
I didnt think it would be as simple as a move command..
Click to expand...
Click to collapse
Don't forget to make the symbolic link. That is the important command, not the move one.
turboyo said:
Thanks for the input. finally someone! ..thats good to know Im going to try it now, I didnt think it would be as simple as a move command.. any reason the radio wipes the cache partition?
Click to expand...
Click to collapse
I realize I wasn't completely clear. I don't know why the OTA radio update wiped my cache partition. Perhaps someone familiar with the update process (ChiefzReloaded) can explain this.
turboyo said:
did dalvik recreate itself after the wipe in /data?
Click to expand...
Click to collapse
If you wipe only the cache partition, you will need to recreate the dir /cache/dc but not the symlink. If you wipe only the data partition, you will need to recreate the symlink, but not the dir. If you want to clear the dalvik-cache, just delete all the files in /cache/dc (they should be recreated on next boot). If you are accustomed to 'rm -R /data/dalvik-cache' to clear the dalvik-cache, you'll have to re-setup the symlink (and possibly the /cache/dc dir as well).
turboyo said:
and were ALL the apps gone or just the few that took up the memory?
Click to expand...
Click to collapse
None of the apps are 'gone' per se, but since the /data/dalvik-cache dir is just a symlink to a non-existant dir (/cache/dc), the system can't create a dir that already exists (/data/dalvik-cache) and can't write anything to a dir that doesn't exist (/cache/dc), so it won't show any of the apps. It is an easy fix to just recreate the /cache/dc dir and reboot. None of your apps need to be reinstalled, since they are still in the /data/app dir.
reukiodo said:
None of the apps are 'gone' per se, but since the /data/dalvik-cache dir is just a symlink to a non-existant dir (/cache/dc), the system can't create a dir that already exists (/data/dalvik-cache) and can't write anything to a dir that doesn't exist (/cache/dc), so it won't show any of the apps. It is an easy fix to just recreate the /cache/dc dir and reboot. None of your apps need to be reinstalled, since they are still in the /data/app dir.
Click to expand...
Click to collapse
Awesome, that cleared it up. Will be doing this now.
alright bringing this back up, works great but .. Just in case how do we move dalvik back to data with out loosing apps or anything?
turboyo said:
alright bringing this back up, works great but .. Just in case how do we move dalvik back to data with out loosing apps or anything?
Click to expand...
Click to collapse
I'm guessing you can do these in recovery:
rm /data/dalvik-cache
mv /cache/dc /data/dalvik-cache
rm -rf /cache/dc
But I haven't tested it. In theory it should work. The first command removes the symlink, the second moves the existing cache to the original location of dalvik-cache, and the last removes the copy of dalvik-cache on the cache partition.
I have tried this process, but shouldn't I see an increase in internal memory if you go to sdcard / phone storage?
Please advise, I am not totally clear of tthe process.
Can someone help?
I am very interested on this
UnkzDomain said:
I'm guessing you can do these in recovery:
rm /data/dalvik-cache
mv /cache/dc /data/dalvik-cache
rm -rf /cache/dc
But I haven't tested it. In theory it should work. The first command removes the symlink, the second moves the existing cache to the original location of dalvik-cache, and the last removes the copy of dalvik-cache on the cache partition.
Click to expand...
Click to collapse
It's up to you, but I would suggest just letting Android regenerate the cache...
rm /data/dalvik-cache
rm -R /cache/dc
riverajuan said:
I have tried this process, but shouldn't I see an increase in internal memory if you go to sdcard / phone storage?
Please advise, I am not totally clear of the process.
Can someone help?
I am very interested on this
Click to expand...
Click to collapse
It depends on how many applications you have installed, but you should see at least some kind of increase if you move the dalvik-cache off of /data and onto the /cache partition.
reukiodo said:
I was able to get dalvik-cache to /cache by going into clockworkmod recovery and accessing from adb:
mv /data/dalvik-cache /cache/dc
ln -s /cache/dc /data/dalvik-cache
After the files are moved and the symlink is created, you should have no problems when rebooting.
However, I came across a problem when I flashed the radio, since it wiped the cache partition. If you are missing all your installed apps in android, it might be that the cache partition was wiped. You need to recreate the /cache/dc folder and reboot.
Click to expand...
Click to collapse
I've moved dalvik-cache to /cache with a symlink. However, everytime i booted, /cache was 770 and not 771.
To solve this, I just add a little script in /system/etc/init.d
#!/system/bin/sh
#
# Change 770 to 771 /cache to enable dalvik-cache
/system/bin/chmod 0771 /cache
echo "*** cache updated ***"
exit
Name it for ex. 02cache and chmod 755 it.
reboot and the /cache should be 771 now and dalvik-cache should work fine without patching anything (I have a stock rooted froyo rom)
sibere said:
I've moved dalvik-cache to /cache with a symlink. However, everytime i booted, /cache was 770 and not 771.
To solve this, I just add a little script in /system/etc/init.d
#!/system/bin/sh
#
# Change 770 to 771 /cache to enable dalvik-cache
/system/bin/chmod 0771 /cache
echo "*** cache updated ***"
exit
Name it for ex. 02cache and chmod 755 it.
reboot and the /cache should be 771 now and dalvik-cache should work fine without patching anything (I have a stock rooted froyo rom)
Click to expand...
Click to collapse
forgive the newbness but to make that a script file do you just make that script into a .txt file and add it to system/etc/init.d? what exactly are you naming the file?
turboyo said:
forgive the newbness but to make that a script file do you just make that script into a .txt file and add it to system/etc/init.d? what exactly are you naming the file?
Click to expand...
Click to collapse
the init.d is a script. open it up and add those lines to it. then just save (do not change the file name when you save it)
turboyo said:
forgive the newbness but to make that a script file do you just make that script into a .txt file and add it to system/etc/init.d? what exactly are you naming the file?
Click to expand...
Click to collapse
I did it with "vi", a linux text editor.
You can name it whatever you like. the 2 first numbers are for the order of execution if you have more than 1 script in /etc/init.d/
sibere said:
I've moved dalvik-cache to /cache with a symlink. However, everytime i booted, /cache was 770 and not 771.
To solve this, I just add a little script in /system/etc/init.d
#!/system/bin/sh
#
# Change 770 to 771 /cache to enable dalvik-cache
/system/bin/chmod 0771 /cache
echo "*** cache updated ***"
exit
Name it for ex. 02cache and chmod 755 it.
reboot and the /cache should be 771 now and dalvik-cache should work fine without patching anything (I have a stock rooted froyo rom)
Click to expand...
Click to collapse
I have a Motorola Droid running froyo 2.2 FRG83 rooted. I don't have a /system/etc/init.d file, what's the correct permissions for it? And shouldn't the 771 actually be on /cache/dc instead of /cache as all the 771 does vs the 770 is add the execute bit for others so basically it changes from rwxrwx--- to rwxrwx--x.
Also, I am curious what happened before you added the script to change the permissions, were you able to still use the terminal app to get into the shell after booting?
To get /system/etc, you must boot into recovery mode
And I DO confirm to set 771 to /cache because the system rests it to 770 on each boot. For children folders, you can set 777, this will be kept even after a reboot.
Beleive me, that's how it works
Sent from my HTC Desire using XDA App
sibere said:
To get /system/etc, you must boot into recovery mode
And I DO confirm to set 771 to /cache because the system rests it to 770 on each boot. For children folders, you can set 777, this will be kept even after a reboot.
Beleive me, that's how it works
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
There is no need to boot into recovery mode to get to /system/etc which is the same as /etc. All you need to do is use either root explorer app or get the terminal shell prompt and then get into the directory after you mount it as read+write. Besides, how do you get into the /system/etc directory with recovery mode?
I know /cache is set to 770 after boot but since /cache/dc is the directory that you're dealing with and the only difference between 770 and 771 is the 1 adds the execution by others to the permissions so it doesn't give others read+write anyways as that requires another 6 so why wouldn't just setting 771 on /cache/dc work. Before you did the 771 on /cache, are you still able to boot and use the phone and the apps?
Almighty1 said:
There is no need to boot into recovery mode to get to /system/etc which is the same as /etc. All you need to do is use either root explorer app or get the terminal shell prompt and then get into the directory after you mount it as read+write. Besides, how do you get into the /system/etc directory with recovery mode?
I know /cache is set to 770 after boot but since /cache/dc is the directory that you're dealing with and the only difference between 770 and 771 is the 1 adds the execution by others to the permissions so it doesn't give others read+write anyways as that requires another 6 so why wouldn't just setting 771 on /cache/dc work. Before you did the 771 on /cache, are you still able to boot and use the phone and the apps?
Click to expand...
Click to collapse
This would normally be the case, however the slide doesn't have S-off like other phones, so we can't mount with r/w like you would.
Ace42 said:
This would normally be the case, however the slide doesn't have S-off like other phones, so we can't mount with r/w like you would.
Click to expand...
Click to collapse
Interesting. I guess what I'm trying to figure out is what happens if /cache is at 770, will the phone just force close on everything making it a brick at that point?
To get to /system/esltc in recovery, connect your phone to your PC and use adb
If you leave 770 to /cache, dalvik VM will not get access to the directory and will rebuild dalvik-cache in /data.
But man, if you don't trust me, you can always try yourself and make your own experiments
Sent from my HTC Desire using XDA App
Guys any idea how to change the default appdata storage...
\data\data\com.google.android.apps.currents
to
sdcard\Android\data\com.google.android.apps.currents
coz currents stores both cache and data to internal mem...which takes a whopping 100-150mb itself
can i change some vaules to make it store in the sdcard instead.....
I dont know why Google does some stupid stuff it does...
and pl dont suggest s2e app2sd, link2sd etc etc...
i already use s2e...w/o data moved ...
i want data on internal only
bump
Just download 1Tap Cache Cleaner and clear your app caches once in a while. All apps accumulate some cached data so you can free space by clearing them. It's much easier this way.
Sent from my Desire HD using xda premium
sashank said:
Just download 1Tap Cache Cleaner and clear your app caches once in a while. All apps accumulate some cached data so you can free space by clearing them. It's much easier this way.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
what a douche ...
what a fool you are...
:rofl:
how im i suppose to read the content after clearing the cache...
so what then waste my mobile data again and again to re sync the same content which was cached earlier...
the caches are not create so that you can have fun deleting them...
and be proud of your achievement
bump
Remap Cache folder to SD card
So the combined size of Currents cache and content is more free than your internal memory? Not a for sure fix, but looks like folks were able to use terminal commands to remap their market cache to SD card, could try modifying the instructions found here, but substituting the folders that apply to your problem with Google Currents.
Check it out here...
http://forum.xda-developers.com/showpost.php?p=19042043&postcount=4
Quoted for anyone else with the problem.
rxwookie said:
That one I think I understand... but, unfortunately the answer is that the Dalvik cache partition (where the market APK's are downloaded to) on many original Samsung devices (i.e. Fascinate) is only about 35 MB in size. Anything larger will get rejected as being too big. Most of the newest devices have a larger download partition.
I've seen a few posts on different forums on remapping the download cache to a different, larger partition... but nothing specific to our devices. I've tried following other posts just to see if it works, but suceeded only in either having no effect or messing it up worse and having to reinstall the ROM (not a big deal, but frustrating).
Until one of the smart people here tells us how to remap **our** cache to a larger partition... I'd do a Google search for the APK of the app you are trying to install. That worked for me to install an app about 40 MB in size.
** edit **
I see that you were able to download the app after deleting everything in the cache folder. I guess your device is lucky enough to have a larger download partition than mine does
Glad to see you got it to work!
** 2nd edit - How to remap your market cache to the SD card **
-- UPDATE -- (Thanks to grickson here at XDA)
Problem: Insufficient Storage Space Available (Android Market)
Possible Solution: Remap cache folder to your SD card
** WARNING **
I am not responsible if you mess up your device doing the following. It manually remaps your market cache to your SD card to give you extra space. The only caveat is that if you remove your SD card (or while the SD card is unmounted) the market will not work. If you are worried about losing market functionality, DON'T try this. If you mistype (or the world suddenly tips over or some other unforeseen consequence), you can ruin your ability to run the Android Market at all. Please remember, you can repeatedly clear your Dalvik cache as often as needed to continue downloading apps. you can also get most larger APK's if you spend a few minutes browsing for them. You have been warned!
** END WARNING **
1.) Download and install a terminal emulator
2.) Open the terminal emulator and type su
3.) Allow the app to always have root access and exit
4.) Restart the terminal emulator and type su, the prompt should change to a #
5.) Type the following commands:
# cd /data/data/com.android.vending
# rm -R cache
# mkdir /sdcard/cache/
# mkdir /sdcard/cache/marketCache
# ln -s /sdcard/cache/marketCache cache
- What these commands do are (in order): change directory to your cache folder, delete the entire cache folder, create a directory on your SD card named cache, create a subdirectory in that one called marketCache, link the phone's market cache to the newly created folder on your SD card
To reverse this process (hopefully):
1.) Open the terminal emulator and type su
2.) Type the following commands:
# cd /sdcard/cache/
# rm -R marketCache
# mkdir /data/data/com.android.vending/cache
# ln -s /data/data/com.android.vending/cache cache
Alternately, (from what I understand) you can just repartition your device and reinstall your ROM of choice using ODIN and your market should be back to the way it was.
Click to expand...
Click to collapse
any more suggestions guys...
vNa5h said:
Guys any idea how to change the default appdata storage...
\data\data\com.google.android.apps.currents
to
sdcard\Android\data\com.google.android.apps.currents
coz currents stores both cache and data to internal mem...which takes a whopping 100-150mb itself
can i change some vaules to make it store in the sdcard instead.....
I dont know why Google does some stupid stuff it does...
Click to expand...
Click to collapse
Hello,
regarding ur following post :
http://forum.xda-developers.com/showthread.php?t=2123131
Have u found any solutions yet ?? if so please share as i'm facing the same problem. The App "New Scientist" stores about 2GB data in /data/data/com.newscientist.blabla folder,, and it takes up almost all of phone's memory.
I want to change this directory to sdcard.,, and as you already mentioned in ur post,, link2sd, foldermount etc are waste of time but don't know why people keep quoting them whenever i ask this.
As you've raised this issue about an year ago,, hopefully you might've fount out a solution/ work around. If so please help. Thank you,
coolvipcandy said:
Hello,
regarding ur following post :
http://forum.xda-developers.com/showthread.php?t=2123131
Have u found any solutions yet ?? if so please share as i'm facing the same problem. The App "New Scientist" stores about 2GB data in /data/data/com.newscientist.blabla folder,, and it takes up almost all of phone's memory.
I want to change this directory to sdcard.,, and as you already mentioned in ur post,, link2sd, foldermount etc are waste of time but don't know why people keep quoting them whenever i ask this.
As you've raised this issue about an year ago,, hopefully you might've fount out a solution/ work around. If so please help. Thank you,
Click to expand...
Click to collapse
I have the same issue. Since this was posted 2 years ago I hope you have solved it. I want app data which gets download internally to be saved in my internal storage.
I have edited the apk so that it gets installed in my internal storage but I can't find a way for app data.
Thanks in advance.
Karandeep Padam said:
I have the same issue. Since this was posted 2 years ago I hope you have solved it. I want app data which gets download internally to be saved in my internal storage.
I have edited the apk so that it gets installed in my internal storage but I can't find a way for app data.
Thanks in advance.
Click to expand...
Click to collapse
sorry for late reply, i didn't find any promising solution and finally got myself a phone with bigger space.
Its 2020 , has anyone found a way to change apps data path ? I thought could fix problem when trying Kali linux on phone even though moved it to sd card . I installed VMOS and moved it but same problem .
Hi, I'm using an LG Optimus L9 and running 4.3 bassed PAC-man rom.
The internal memory is 4GB and after installing a few apps, I started getting "Not enough storage space" warnings.
So, I checked the /data folder and found that there's directory called lost+found which is taking up a lot of space (Above 1.5GB).
I tried deleting files using ES Explorer with the data folder mounted as R+W, but it says "error deleting files"
Is it safe to delete the lost+found folder?
And if yes, how can I delete it since I'm unable to delete it with a file explorer app.
It would be really great if could recover thelost internal memory
void00 said:
Hi, I'm using an LG Optimus L9 and running 4.3 bassed PAC-man rom.
The internal memory is 4GB and after installing a few apps, I started getting "Not enough storage space" warnings.
So, I checked the /data folder and found that there's directory called lost+found which is taking up a lot of space (Above 1.5GB).
I tried deleting files using ES Explorer with the data folder mounted as R+W, but it says "error deleting files"
Is it safe to delete the lost+found folder?
And if yes, how can I delete it since I'm unable to delete it with a file explorer app.
It would be really great if could recover thelost internal memory
Click to expand...
Click to collapse
I don't think there is a problem doing that and change the permission to rwx-rwx-r try and report
sangalaxy said:
I don't think there is a problem doing that and change the permission to rwx-rwx-r try and report
Click to expand...
Click to collapse
I tried deleting the folder through adb shell.
Issued following commands:
adb shell
su
# cd /data
# rm -r lost+found
Click to expand...
Click to collapse
The output was "rm failed for lost+found. Operation not permitted"
Also tried this mounting /data as rw but no luck.
Tried chmod 775 on lost+found but no luck either.
Always getting operation not permitted message.
void00 said:
I tried deleting the folder through adb shell.
Issued following commands:
The output was "rm failed for lost+found. Operation not permitted"
Also tried this mounting /data as rw but no luck.
Tried chmod 775 on lost+found but no luck either.
Always getting operation not permitted message.
Click to expand...
Click to collapse
try r+w+x
sangalaxy said:
try r+w+x
Click to expand...
Click to collapse
Still getting the same error. Operation not permitted.
void00 said:
Still getting the same error. Operation not permitted.
Click to expand...
Click to collapse
may be something preventing it
try a reset and simply format the data in cwm do backup first
sangalaxy said:
may be something preventing it
try a reset and simply format the data in cwm do backup first
Click to expand...
Click to collapse
Using TWRP.
If I backup first, it will also back up the lost+found data
And restoring data will bring it back.
I did format data and system before flashing the rom. So I don't know why the lost+found has so large size.
What should I do?
void00 said:
Using TWRP.
If I backup first, it will also back up the lost+found data
And restoring data will bring it back.
I did format data and system before flashing the rom. So I don't know why the lost+found has so large size.
What should I do?
Click to expand...
Click to collapse
ok so don't backup
if anything goes wrong you can still flash the stock right??
sangalaxy said:
ok so don't backup
if anything goes wrong you can still flash the stock right??
Click to expand...
Click to collapse
hmm, i'll try flashing CWM and then do a format of every partition and freshly flash the rom.
Will report back if there's the same problem.
UPDATE:
Formatted all the partitions including /data/media using CWM
Did a fresh install of rom.
I've got my internal memory back
Thanks!
my 2 cents...
my 2 cents... I've opened the lost+found folder with the file manager (this https://play.google.com/store/apps/details?id=com.rhmsoft.fm), after enabling the root explorer functionality, and deleted a bunch of the biggest files, just checking they were at least 2-3 months old. Rebooted to make sure everything is fine and dandy, and now I've got enough free space, sun is chirping, birds are shining, life is beautiful :silly: :victory:
fabiosirigu said:
my 2 cents... I've opened the lost+found folder with the file manager (this *edited original link*), after enabling the root explorer functionality, and deleted a bunch of the biggest files, just checking they were at least 2-3 months old. Rebooted to make sure everything is fine and dandy, and now I've got enough free space, sun is chirping, birds are shining, life is beautiful :silly: :victory:
Click to expand...
Click to collapse
I was having the same problem. My phone is Samsung Galaxy S2 (GT-i9100). I was on stock Jellybean. But it was starting to feel sluggish and slow. So, having heard about the new Android Kitkat's lower memory requirements and smoother performance, i decided to install Cyanogenmod 11 on it.
Installation was not without problems. At first i flashed Clockworkmod Recovery 6.0.2.9. The phone bricked into a bootloop with a yellow triangle on it. Flashing the Cyanogenmod 11 resulted an error of "Status 7". So i searched for the latest Clockworkmod Recovery, which was at 6.0.4.5. After flashing the 6.0.4.5, Cyanogenmod 11 installed successfully. Performance was really smooth. No lags, no jitter, and everything worked like a charm.
The problem started when i re-installed my applications. Suddenly i got a message of "insufficient storage". This has never happened before. Note, that i previously had large games on my phone like Real Racing 3 and Bard's Tale. This time, i haven't even installed those large games. So i looked at my Storage, and found out that i only had 141mb of free space. But the weird thing is, my reported Apps was only 353mb, from 1.97GB internal storage. So there was over 1GB of storage just vanished.
I browsed for a solution to this problem, and landed on this thread. After reading reply from fabiosirigu, i decided to brave myself, and deleted the content of the lost+found folder (but not the folder itself). I accessed the folder with the built-in File Manager from Cyanogenmod, and set it to "Root Access Mode", and select all folder in the folder, and deleted it. The deletion took quite a few minutes, which felt like ages. Just sat on my bed, crossed my fingers, hoped that nothing will go wrong.
After the deletion, i rebooted my phone. the cyanogenmod logo appeared, and the system booted as usual. I just exhaled a massive sigh of relieve. I went straight to the internal storage, and now it is showing the correct report, 1.67GB of free space.
Thank you for your reply fabiosirigu. Really solved my problem.
lost+found genesis
Let somebody correct me if I'am wrong.
lost+found directory is standard for some unix/linux filesystems. All ext(s) 2, 3 and 4 contains it by default.
The operating system collects unidentified, broken files and its parts inside of l+f dir.
No one of these junks is used by running system.
So - you can look in l+f for some lost, missing files. If you don't miss for any (who knows it better?) then you don't need l+f content.
This is a mystery. I have a Verizon Samsung Galaxy Note 2, running 4.1.1, rooted. A few days ago I ran out of space on the internal storage so I wanted to move /data/media/Download to /mnt/extSdCard/ and then symlink to it. But I screwed up and accidentally moved all of /data/media to the external SD card. I realized I did that and immediately moved it back to /data/. I did this using the Move command in RootExplorer.
Now I find I can no longer write to /storage/sdcard0/. For example, my S-Note files go there but when I try to save a note it says "Unable to save file". I have another app that also keeps data there and it too complains that it can't write to its own directory on /storage/sdcard0/. I also find there are files on sdcard0 I can't delete myself either with RootExplorer or from a terminal window, even with a "#" prompt.
/sstorage/sdcard0 has perms of 775, owned by root in group sdcard_rw. /storage has perms 775, owned by system in group sdcard_r.
I'm really stumped here. What the heck did I do to my phone? Any help would be *greatly* appreciated. Thanks!
Michele31415 said:
This is a mystery. I have a Verizon Samsung Galaxy Note 2, running 4.1.1, rooted. A few days ago I ran out of space on the internal storage so I wanted to move /data/media/Download to /mnt/extSdCard/ and then symlink to it. But I screwed up and accidentally moved all of /data/media to the external SD card. I realized I did that and immediately moved it back to /data/. I did this using the Move command in RootExplorer.
Now I find I can no longer write to /storage/sdcard0/. For example, my S-Note files go there but when I try to save a note it says "Unable to save file". I have another app that also keeps data there and it too complains that it can't write to its own directory on /storage/sdcard0/. I also find there are files on sdcard0 I can't delete myself either with RootExplorer or from a terminal window, even with a "#" prompt.
/sstorage/sdcard0 has perms of 775, owned by root in group sdcard_rw. /storage has perms 775, owned by system in group sdcard_r.
I'm really stumped here. What the heck did I do to my phone? Any help would be *greatly* appreciated. Thanks!
Click to expand...
Click to collapse
Do you have a nandroid backup? extsdcard and sdcard0 will stay untouched but maybe all you need its the system and data back to working order. I figure that's the first idea. I couldn't say what's happened though.
MunkinDrunky said:
Do you have a nandroid backup? extsdcard and sdcard0 will stay untouched but maybe all you need its the system and data back to working order. I figure that's the first idea. I couldn't say what's happened though.
Click to expand...
Click to collapse
That would be nice but unfortunately I don't have nandroid. I just back up my files to the external SD card with Titanium Backup and then store a copy on my PC. To be honest, I was afraid of screwing up something by running nandroid so I never got it.
In the meantime, none of my apps that are parked on /storage/sdcard0 run anymore, all claiming they can't create files there. The only thing I've been able to do there is chmod and chown but it doesn't seem to help. If I delete a file with Root Explorer, it says it's deleted but when I refresh the directory, it's still there.
I don't see how the two could be related, but I keep coming back to /data/media. I also have a Galaxy S3 that's working. /data/media on the S3 is 775, whereas it was 770 on the Note 2. I changed it to 775 and rebooted - didn't help. I changed the group of /storage from sdcard_r to sdcard_rw - didn't help either.
Could you tell me what the properties are on your Note 2 of /data, /data/media, /storage, and /storage/sdcard0? I'm thinking that Root Explorer munged up something when I moved /data/media/ to the extSdCard and then back again. The subdirectories and files are all there but sdcard0 isn't happy now.
Thanks very much for the reply.
Michele31415 said:
That would be nice but unfortunately I don't have nandroid. I just back up my files to the external SD card with Titanium Backup and then store a copy on my PC. To be honest, I was afraid of screwing up something by running nandroid so I never got it.
In the meantime, none of my apps that are parked on /storage/sdcard0 run anymore, all claiming they can't create files there. The only thing I've been able to do there is chmod and chown but it doesn't seem to help. If I delete a file with Root Explorer, it says it's deleted but when I refresh the directory, it's still there.
I don't see how the two could be related, but I keep coming back to /data/media. I also have a Galaxy S3 that's working. /data/media on the S3 is 775, whereas it was 770 on the Note 2. I changed it to 775 and rebooted - didn't help. I changed the group of /storage from sdcard_r to sdcard_rw - didn't help either.
Could you tell me what the properties are on your Note 2 of /data, /data/media, /storage, and /storage/sdcard0? I'm thinking that Root Explorer munged up something when I moved /data/media/ to the extSdCard and then back again. The subdirectories and files are all there but sdcard0 isn't happy now.
Thanks very much for the reply.
Click to expand...
Click to collapse
Did you want to know what permissions those directories have?
/data rwx rwx --x
/data/media rwx rwx ---
MunkinDrunky said:
Did you want to know what permissions those directories have?
/data rwx rwx --x
/data/media rwx rwx ---
Click to expand...
Click to collapse
Yes, thanks. That's the same I have on the Note 2, so that's not the problem (though oddly enough, on the S3, /data/media is rwxrwxr-x).
Still, it has to be *some* permission somewhere that's wrong and is preventing apps from writing or deleting files they have in sdcard0. What about /storage? I've got:
/storage r-xr-x--- owner=system, group = sdcard_r
/storage/sdcard0 rwxrwxr-x, owner = root, group = sdcard_rw
/storage in particular doesn't seem correct. ???
FWIW, here's someone else with the exact same problem - unfortuntely he didn't get a resolution: http://androidforums.com/android-lounge/716573-unable-delete-move-files-directories-sdcard0.html
And this one too: http://android.stackexchange.com/questions/30113/cant-delete-any-files-in-my-download-folder I tried the same things suggested there and they didn't work for me either.
I dont know enough about the permission system. You said you tried terminal. Maybe try another root enabled file explorer. I've only used es and root browser. Maybe your binaries need to be updated.
You might consider starting fresh if you can't find a solution. From here on out I'd take care to be meticulous and read up on the how to threads for rooting and unlocking bootloader just so you have an idea of where what your going to do fits in with everything else. It sounds like you've just beet rooted and left your phone stock.
Perhaps the internal memory need to be reformatted and everything taken back to a stock working order? If your bootloader is unlocked and you have a custom recovery (like twrp or cw) you could back up all contents of your ext and internal sd to a computer, do a nandroid backup(just in case), and back up your apps with titanium, then wipe everything, system data cache dalvick through recovery then reformat internal sd and re flash the stock rooted image of 4.1.1 or 4.1.2.
If your bootloader is locked up still you could use Odin to get back to stock factory image. You would no longer be rooted but you can then reroot. This is always the end of the line and one can run into some bigger problems here.
MunkinDrunky said:
I dont know enough about the permission system. You said you tried terminal. Maybe try another root enabled file explorer. I've only used es and root browser. Maybe your binaries need to be updated.
Click to expand...
Click to collapse
Yup - I've tried Root Explorer, File Expert, Terminal Emulator, and adb USB from the PC. Same result from all of them. Oddly enough, Root Explorer and FE both claim that files I select on /storage/sdcard0 have been deleted, but when I refresh the file list, they're baaaack...
MunkinDrunky said:
You might consider starting fresh if you can't find a solution. From here on out I'd take care to be meticulous and read up on the how to threads for rooting and unlocking bootloader just so you have an idea of where what your going to do fits in with everything else. It sounds like you've just beet rooted and left your phone stock.
Click to expand...
Click to collapse
Yes, I only flashed the Verizon rooted stock ROM because that's all I needed. I just want to be able to use apps like Titanium Backup, get rid of that stupid clicking sound the camera makes, and other things you need root for. I'm happy with the other features of the standard ROM. I never bothered unlocking the boot loader.
MunkinDrunky said:
Perhaps the internal memory need to be reformatted and everything taken back to a stock working order? If your bootloader is unlocked and you have a custom recovery (like twrp or cw) you could back up all contents of your ext and internal sd to a computer, do a nandroid backup(just in case), and back up your apps with titanium, then wipe everything, system data cache dalvick through recovery then reformat internal sd and re flash the stock rooted image of 4.1.1 or 4.1.2.
Click to expand...
Click to collapse
Yes, I've considered that, and it may come to that. But it's not a very intellectually appealing solution. It's sort of like burning down your house because you've got termites. I'm still hoping there's a less drastic solution. In the meantime, this may be locking the barn door after the horse is gone, but I downloaded a nandroid app and took a nandroid backup. Don't know if wiping and then restoring that will also restore the problem.
MunkinDrunky said:
If your bootloader is locked up still you could use Odin to get back to stock factory image. You would no longer be rooted but you can then reroot. This is always the end of the line and one can run into some bigger problems here.
Click to expand...
Click to collapse
Yup, if that doesn't do it, it's time for a new phone
UPDATE:
I started looking at /data/media and comparing permissions there to what my S3 was showing. It seems /data/media was owned by media_rw in group media_rw on the Note2, but owned by root in group root on the S3. So in adb on the Note 2 I did #chown root:root /data/media. To my surprise, that worked. I then changed the permission from 770 to 775 to match what the S3 has. I then tried saving an S-Note - didn't work. So I went into /data/media/S Note and changed *its* owner/group to root, and permissions to 777 also. I tried saving a note and ... success! It saved it OK.
I'm starting to think that when I copied /data/media back to /data from /mnt/extSdCard/data/media, Root Explorer bollixed up the owner/group/permissions. I'm going to try some other directories there and see if that helps too. And see if this survives a reboot. So that's some progress at least...
That is indeed good news. At least the permission will work through terminal on a subdirectory basis in the media dir. You could recursively change permission for all subdirectory in media. I belive -R probably best to Google that.
MunkinDrunky said:
That is indeed good news. At least the permission will work through terminal on a subdirectory basis in the media dir. You could recursively change permission for all subdirectory in media. I belive -R probably best to Google that.
Click to expand...
Click to collapse
Well that seems to have done it. Everything is working once again. In the final analysis, it appears that you just can't change permissions or delete files from /storage/sdcard0/. However, this is apparently just a mount point (I may be wrong here) for /data/media/ and you *can* change permissions/owners/etc. there. Once I did that, the apps I had that had installed themselves on sdcard0/ started working again. Go figure.
And as a bonus, I got the motivation I needed to start doing nandroid backups and learned a little about the storage hierarchy of Android. So big thumbs up for taking the time to read all this and help me out.
Michele31415 said:
Well that seems to have done it. Everything is working once again. In the final analysis, it appears that you just can't change permissions or delete files from /storage/sdcard0/. However, this is apparently just a mount point (I may be wrong here) for /data/media/ and you *can* change permissions/owners/etc. there. Once I did that, the apps I had that had installed themselves on sdcard0/ started working again. Go figure.
And as a bonus, I got the motivation I needed to start doing nandroid backups and learned a little about the storage hierarchy of Android. So big thumbs up for taking the time to read all this and help me out.
Click to expand...
Click to collapse
Yeah I leaned more bout this too. As an after thought, I have only ever moved items from sdcard0 to extsdcard by going to /storage then copying items from one to another. I too believe this is just a mount point. Nevertheless, probably most items in /data/media you were trying to move to extsdcard are found in sdcard0 and accessible through the mounting folder: /storage, well at least /downloads are there in /storage/sdcard0/ and i have always navigated to /storage first then to /sdcard0/ to grab /downloads or /android/data/ to copy to external whatever.
I know the thread is more than a year old, but I have the same issue here on the Xperia T.
Can't write on /storage/sdcard0
However, I have no idea what to do to fix it. I found a step by step actionplan here:
http://forum.cyanogenmod.org/topic/104879-cm12-issue-with-sd-card-and-wifi-network-detection/
is this what you did?
Move dalvik-cache to /cache
import /disclaimer.md
Code:
I am not responsible for any damage done to your device/SD card/OTG cable/washing machine etc.
You are responsible for what you do.
If something brakes, it's on you!
This has only been tested on a CM13-based ROM. I have no idea how it will function on other ROMs because of the size of the dalvik-cache directory.
I have found that, on CM13-based ROMs, the dalvik-cache directory is small enough to fit in the /cache partition, giving us several MBs on /data
Current state: Beta
Reason: Not fully tested (on all ROMs)
Comment: Stable enough for daily use
Installation:
Busybox required!
Download the attached zip and flash it in recovery.
Or extract the script from the zip, put it in /system/etc/init.d/ , set the permissions to 755 (rwxr-xr-x) and ownership to 0, 2000 (root, shell).
Uninstallation:
Delete /system/etc/init.d/10dc-linker and /cache/dalvik-cache
To-Do:
Add a size checker
Make suggestions
Bugs:
Found one? Let me know!
Changelog:
v1.0:
First release
Reserved
Didn't work for me on CM13 Xperia SP.
kkumar326 said:
Didn't work for me on CM13 Xperia SP.
Click to expand...
Click to collapse
How much space do you have on /cache?
Also, what exactly is not working?
What is the state of SELinux?
Complete Data
This is what I did:
1) Extracted zip and pasted 10dc-linker in init.d
2) Rebooted phone with twrp recovery
3) Cleared dalvik-cache
4) Rebooted
Result: Nothing happened
Probable cause: Access problem to move/create folders as I couldn't change permissions for /cache , /data and /data/dalvik-cache folders manually using root explorer. It gets reverted back to original. My access was also restricted to root, there was no shell.
Probable fix: Adding script to gain permission to modify/ create in these folders. Plus adding access to both root and shell. I also read somewhere about superuser access to get permission but I couldn't understand.
My cache folder has about 600 MB space and it's completely empty. There is no issue with the space.
Please let me know about your step by step process and probable fixes. Maybe it works.
kkumar326 said:
This is what I did:
1) Extracted zip and pasted 10dc-linker in init.d
2) Rebooted phone with twrp recovery
3) Cleared dalvik-cache
4) Rebooted
Result: Nothing happened
Probable cause: Access problem to move/create folders as I couldn't change permissions for /cache , /data and /data/dalvik-cache folders manually using root explorer. It gets reverted back to original. My access was also restricted to root, there was no shell.
Probable fix: Adding script to gain permission to modify/ create in these folders. Plus adding access to both root and shell. I also read somewhere about superuser access to get permission but I couldn't understand.
My cache folder has about 600 MB space and it's completely empty. There is no issue with the space.
Please let me know about your step by step process and probable fixes. Maybe it works.
Click to expand...
Click to collapse
The script must have 755 or 777 permissions or it won't work.
Also, the zip is flashable. Just flash it in recovery and it will setup everything by itself.
When I flashed it, google-play-services fc like crazy until I restore a backup
Miasaya said:
When I flashed it, google-play-services fc like crazy until I restore a backup
Click to expand...
Click to collapse
What happens if you flash the zip and wipe dalvik-cache?
Does it still fc?
Didn't work with flash
Vagelis1608 said:
The script must have 755 or 777 permissions or it won't work.
Also, the zip is flashable. Just flash it in recovery and it will setup everything by itself.
Click to expand...
Click to collapse
I flashed zip too but nothing happened. No folder was created or moved.
Man use this utility http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664
But choose "optimal" partition layout.
kkumar326 said:
I flashed zip too but nothing happened. No folder was created or moved.
Click to expand...
Click to collapse
Did you wipe dalvik-cache and /cache after flashing?
Lion_Smith said:
Man use this utility http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664
But choose "optimal" partition layout.
Click to expand...
Click to collapse
Sure, go on dev threads and advertise other people's work. That's highly appreciated.
That's why we can't have nice things...
Found the Reason
Vagelis1608 said:
Did you wipe dalvik-cache and /cache after flashing?
Sure, go on dev threads and advertise other people's work. That's highly appreciated.
That's why we can't have nice things...
Click to expand...
Click to collapse
My dalvik-cache is shooting up to 400+ MB, that's why it's not working. I moved /data/dalvik-cache to /cache/dalvik-cache. Then, I used terminal command after su command to link them
Code:
ln -s /cache/dalvik-cache /data/dalvik-cache
It worked but my phone started showing errors with low memory notifications.
1) Is there a way to limit dalvik-cache size?
2) Another approach can be to increase /cache size with with some additional memory e.g. 100 MB, and then following this might work. There will still be a gain of 300+ MB of memory.
Please let me know what's possible.
kkumar326 said:
My dalvik-cache is shooting up to 400+ MB, that's why it's not working. I moved /data/dalvik-cache to /cache/dalvik-cache. Then, I used terminal command after su command to link them
It worked but my phone started showing errors with low memory notifications.
1) Is there a way to limit dalvik-cache size?
2) Another approach can be to increase /cache size with with some additional memory e.g. 100 MB, and then following this might work. There will still be a gain of 300+ MB of memory.
Please let me know what's possible.
Click to expand...
Click to collapse
You can't limit dalvik-cache size, sadly.
If there is enough space for dalvik-cache on /cache, then the script should work.
Also, could you give me the output of this command on a rooted shell?
Code:
ls -l /data/dalvik-cache
It's a small L.
Vagelis1608 said:
You can't limit dalvik-cache size, sadly.
If there is enough space for dalvik-cache on /cache, then the script should work.
Also, could you give me the output of this command on a rooted shell?
Code:
ls -l /data/dalvik-cache
It's a small L.
Click to expand...
Click to collapse
rwxrwxrwx 1 root root [date] [time] /data/dalvik-cache -> /cache/dalvik-cache
kkumar326 said:
rwxrwxrwx 1 root root [date] [time] /data/dalvik-cache -> /cache/dalvik-cache
Click to expand...
Click to collapse
My bad.
I forgot to mention with and without the script installed.
What's the output without the script installed?
Script not working
Vagelis1608 said:
My bad.
I forgot to mention with and without the script installed.
What's the output without the script installed?
Click to expand...
Click to collapse
Script is not doing anything at all as I told earlier. That's why I did it manually.
Lion_Smith said:
Man use this utility http://forum.xda-developers.com/g2-mini/development/d620-partition-table-tool-t3107664
But choose "optimal" partition layout.
Click to expand...
Click to collapse
This is intended to work on a LG G2 Mini, not any other phone.
kkumar326 said:
Script is not doing anything at all as I told earlier. That's why I did it manually.
Click to expand...
Click to collapse
I want the output without it linked.