So... I've been messing around with framework-res.apk. To migrate the file onto the i9000 i rm the original, then cp the new version in. It looks like everytime I do this though, the filesystem never releases free space.
"du -ks /system/*" totals to 260552k, but "df -k /system" shows:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/stl9 282432 281316 1116 100% /system
So it appears like the last 3 or so framework-res.apk's haven't had their space released. I've had to move out some apps from /system/apps to copy in the last couple of framework-res.apk's.
Any suggestions as to how to release the free space?
(My guess is that I remount as rw before copying the file, but there are many processes with handles on the old file so the filesystem cant release the space until reboot, and with the reboot the filesystem is mounted as ro so it can't release the free space?)
** SOLVED **
followed bilboa1's advice on RFS errors in this thread : forum.xda-developers.com/showthread.php?t=797650&highlight=mount+%2Fsystem , fsck_msdos'd the /system partition, did a reboot and regained the free space:
/dev/block/stl9 275.8M 273.7M 2.2M 99% /system
# /system/bin/fsck_msdos -p -f /dev/block/stl9
# reboot
/dev/block/stl9 275.8M 267.2M 8.7M 97% /system
*** solution bump ***
Related
I have a bit of a problem.
I have dangerspl, latest radio & cyanogen recovery 1.4 +jf.
I've tried to install numerous roms on my G1:
Both modaco v2 hero roms from http://android.modaco.com/content/h...m-is-here-2-versions-based-on-the-new-update/
also, cyanogen's 4.0.4 from http://forum.xda-developers.com/showthread.php?t=537204
and JAC;s xrom v1.4r3 from http://forum.xda-developers.com/showthread.php?t=543621
The process I'm following is
Code:
alt+w wipe in recovery then,
adb shell mount /sdcard
push the zip over with adp push whatever.zip /sdcard/whatever.zip
and finally apply any zip from sd.
Installation gets to 'copying files' then I get some errors:
Code:
E: Can't chown/mod /system/xbin/busybox (No such file or directory)
E: Failure at line 41:: set_perm 0 0 04755 SYSTEM:xbin/busybox.
Installation aborted.
I've sniffed around and found /system is full via df -h.
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 47.8M 0 47.8M 0% /dev
/dev/block/mmcblk0p1 1.3G 105.3M 1.2G 8% /sdcard
/dev/block/mtdblock3 90.0M 90.0M 4.0K 100% /system
/dev/block/mtdblock4 30.0M 1.1M 28.9M 4% /cache
Is it safe to rm -rf /system or will it turn my g1 into a shiny black paperweight?
Thanks,
Ruint.
edit: seems /system/app is full of apk/odex files, is it safe to remove them?
edi2: looks like after wiping, /data is never remounted, even if I mount it, it looks like it's unused in the install procsess. :/
repartition ur card to give urself more space. u can pull ur apps off of the partition. or write down what u have and reinstall all of them. also make sure u have the right spl, radio image, and if u haven't grab cyanogen's 1.4 recovery to help with the partitioning. of u can partition with ubuntu or paragon. if u need help check my sig and get back to me on gmail, or gtalk
EDIT: i see that u already have the radio, spl and recovery lol
same problem as yours.......
I can install some roms (CM 3.x, CM 4.x, zeroXd and even some hero ones), but while flashing others (JAC, MoDaCo, ecc.) I receive errors like the one you said and sometime line 88 copy_dir error.
Tried repairing the sdcard filesystem but it didn't help.....maybe it's a space related problem, as you suggested?
ps latest radio, recovery, and spl for me, too.......
I've had these errors and usually what it means is the rom.zip file is corrupt. Are you guys downloading the zip files from your phone? If so try downloading from a computer and then putting it on your phone. Don't use ADB just use windows. This solved my problem.
I'm downloading from the pc. Tried re-downloading and a different microsd card but the situation hasn't improved much....... sigh
any one found a fix for this issue...i cant seem to load newer ROMS..i keep gettin this error...pls help
I'm fairly certain it has nothing to do with the SD. The /system folder is stored on the phone's memory, not on the SD card. I'm looking into modifying the install script to use the busybox that is in /system/bin
EDIT: oh and "rm -r"ing anything is scary. I'm pretty sure that the whole system folder gets overwritten by most ROM install scripts, but why delete it?
EDIT: So I tried removing the copy commands from the install script and then copying the stuff manually and this happened: I first "rm -r"ing the system folder which removes all but the lost+found, then I tried copying the system folder from the ROM manually using "cp -r * /system". Then I got a very tell-tale error: not enough room on device. doing a quick "df -h" shows that my system folder is only allowed 67.5M of space, which is less than what ruin posted as his. anyone know of a way to resize?
i can install any rom on my x1..i try to but the screen just hang... pLLLLLSSSSS help
ruin said:
I have a bit of a problem.
I have dangerspl, latest radio & cyanogen recovery 1.4 +jf.
I've tried to install numerous roms on my G1:
Both modaco v2 hero roms from http://android.modaco.com/content/h...m-is-here-2-versions-based-on-the-new-update/
also, cyanogen's 4.0.4 from http://forum.xda-developers.com/showthread.php?t=537204
and JAC;s xrom v1.4r3 from http://forum.xda-developers.com/showthread.php?t=543621
The process I'm following is
Code:
alt+w wipe in recovery then,
adb shell mount /sdcard
push the zip over with adp push whatever.zip /sdcard/whatever.zip
and finally apply any zip from sd.
Installation gets to 'copying files' then I get some errors:
Code:
E: Can't chown/mod /system/xbin/busybox (No such file or directory)
E: Failure at line 41:: set_perm 0 0 04755 SYSTEM:xbin/busybox.
Installation aborted.
I've sniffed around and found /system is full via df -h.
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 47.8M 0 47.8M 0% /dev
/dev/block/mmcblk0p1 1.3G 105.3M 1.2G 8% /sdcard
/dev/block/mtdblock3 90.0M 90.0M 4.0K 100% /system
/dev/block/mtdblock4 30.0M 1.1M 28.9M 4% /cache
Is it safe to rm -rf /system or will it turn my g1 into a shiny black paperweight?
Thanks,
Ruint.
edit: seems /system/app is full of apk/odex files, is it safe to remove them?
edi2: looks like after wiping, /data is never remounted, even if I mount it, it looks like it's unused in the install procsess. :/
Click to expand...
Click to collapse
Where the hell is your /system/sd partition?
If your trying to install a Hero rom it needs an ext partition.
According to this:
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 47.8M 0 47.8M 0% /dev
/dev/block/mmcblk0p1 1.3G 105.3M 1.2G 8% /sdcard
/dev/block/mtdblock3 90.0M 90.0M 4.0K 100% /system
/dev/block/mtdblock4 30.0M 1.1M 28.9M 4% /cache
Where is mmcblk0p2 (system/sd) at?
Is there a way to make all applications store their data in a folder other than /sdcard (root folder on the sd card) ?
I'm planning on rooting and thought that this time round I can keep my sdcard nice and organized by creating an "ApplicationData" folder in the root of the sdcard and somehow configuring android to use that.
On a similar note, can I move the DCIM (camera photos) to a different location too?
Will the below change-mount-point idea work?
Maybe as root we can
1) un-define /sdcard (in /etc/fstab) //or wherever its defined
2) define /sdcard as /dev/<hdb0>/ApplicationData //change hdb0 to the appropriate device/partition
thanks.
Yeah, I see your point... but quite frankly, I believe it's upto the app developers [my knowledge of the Android world is still from the stone-age!!]... if the app specifies that it's data will be stored in /sdcard/AppName, there's not much you can do, unless you can modify the app...
I was thinking that maybe as root we can
1) un-define /sdcard (in /etc/fstab) //or wherever its defined
2) define /sdcard as /dev/<hdb0>/ApplicationData
edit: added to post#1
britoso said:
I was thinking that maybe as root we can
1) un-define /sdcard (in /etc/fstab) //or wherever its defined
2) define /sdcard as /dev/<hdb0>/ApplicationData
edit: added to post#1
Click to expand...
Click to collapse
I did think of this too...
/sdcard --> /sd/AppData
rest of sd card --> /sd
but I think it would mean some other changes as well... for example... the mount usb functionality would have to be modified to mount/unmount a different volume...
So heres the contents of my fstab file:
Code:
C:\>adb shell cat /system/etc/fstab
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mtdblock5 /data yaffs2 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/dev/block/mmcblk0p2 /system/sd auto rw
/system/modules/modules.sqf /system/modules squashfs ro,loop
/system/xbin/xbin.sqf /system/xbin squashfs ro,loop
I'll try changing line 4 (/sdcard), I'm guessing /system/sd is for when I apps2sd is enabled.
Question: How do I escape from INSERT/EDIT mode in VI? Tried pressing trackball+1, trackball+1+2...didnt work
Hey britoso!
Keep us updated with your accomplishments. I, personally, am very interested in being able to achieve this.
Good luck!
update: that didnt work.
Note: the way to get the ESCAPE character is CONTROL + [ (hold the trackball then press [ ). The control key is configurable and defaults to the Jogball/TrackBall
here are the contents of my fstab file, the camera app is still writing to the root of the sdcard (/sdcard/DCIM)
Code:
C:\>adb shell cat /system/etc/fstab
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mtdblock5 /data yaffs2 rw
/dev/block/mmcblk0p1 /sdcard/AppData vfat rw
/dev/block/mmcblk0p2 /system/sd auto rw
/system/modules/modules.sqf /system/modules squashfs ro,loop
/system/xbin/xbin.sqf /system/xbin squashfs ro,loop
Heres the output of "df"
Code:
C:\>adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 197600 0 197600 0% /dev
tmpfs 4096 0 4096 0% /sqlite_stmt_journals
/dev/block/mtdblock3 148480 100088 48392 67% /system
/dev/block/mtdblock5 200960 63752 137208 32% /data
/dev/block/mtdblock4 97280 39628 57652 41% /cache
/dev/block//vold/179:1
15643712 6843256 8800456 44% /sdcard
@britoso
This is what I found out about mounts in Android...
The init program directly mounts all filesystems and devices using either hard-coded file names or device names generated by probing the sysfs filesystem (thereby eliminating the need for a /etc/fstab file in Android).
And from what I see in your df output, it didn't mount /sdcard/AppData...
Have a few ideas in mind... gonna try 'em out now...
craigacgomez said:
gonna try 'em out now...
Click to expand...
Click to collapse
thanks for the info. Let us know how it works out.
Here's what I reached finally...
To achieve this, I have 2 ideas...
1. We gotta modify the init and change the SD mount point to AppData and add another for the rest of the SD... this however would require a rebuilt ROM (I can't edit init on the phone, need to edit init.c from the source)
2. We push some startup scripts to achieve this, but so far, I haven't been able to mount anything else on /sdcard (operation failed), but I think I'm doing something wrong...
Didn't get much time to experiment... and it mite be a busy end of week for me... but I'll try to squeeze in so time to get this...
Why not ask Cyanogen to do this for us in his next ROM?
Or your next favorite modder?
I'm sure they'll like this idea!?
theres a setting in /init.rc that may help
Code:
export EXTERNAL_STORAGE /sdcard
However / is mounted read-only
mount
rootfs on / type rootfs (ro,relatime)
Click to expand...
Click to collapse
i used amon ra v1,5,2 because it is stable but i checked my internal mem and it says 32mb which is still regular phone mem
do i need ap2sd to get my 96mb or do i need to convert ex3 to ex4 or is there something im missing
What spl are you using?
Also, type
Code:
busybox df -h
in terminal and let us know the output.
I don't know how to tell which spl
But this is the output
My busy box kmoo sd Details $ su# busybox df -h Filesystem*************** Size***** Used Available Use% Mounted on tmpfs******************* 47.8M**** 12.0K**** 47.8M** 0% /dev tmpfs******************** 4.0M******** 0***** 4.0M** 0% /sqlite_stmt_journals/dev/block/mtdblock3 AO
So what do I do next
DroidFreek said:
I don't know how to tell which spl
But this is the output
My busy box kmoo sd Details $ su# busybox df -h Filesystem*************** Size***** Used Available Use% Mounted on tmpfs******************* 47.8M**** 12.0K**** 47.8M** 0% /dev tmpfs******************** 4.0M******** 0***** 4.0M** 0% /sqlite_stmt_journals/dev/block/mtdblock3 AO
So what do I do next
Click to expand...
Click to collapse
Doesn't look right . Your df -h output should look something like this
Code:
Filesystem Size Used Available Use% Mounted on
tmpfs 47.9M 12.0K 47.8M 0% /dev
tmpfs 4.0M 0 4.0M 0% /sqlite_st
/dev/block/mtdblock3 90.0M 66.4M 23.6M 74% /system
/dev/block/loop0 512.0K 512.0K 0 100% /system/modules
/dev/block/loop1 2.8M 2.8M 0 100% /system/xb
/dev/block/mtdblock5 89.8M 27.4M 62.4M 30% /data
/dev/block/mtdblock4 30.0M 24.1M 5.9M 80% /cache
/dev/block/mmcblk0p2 457.3M 33.0M 400.0M 8% /system/sd
/dev/block/mmcblk0p2 457.3M 33.0M 400.0M 8% /data/dalv
/dev/block//vold/179:1
6.9G 6.3G 670.3M 91% /sdcard
where /system/sd is your apps2sd partition (if you have it) and /data is your internal storage.
I have 62megs free in my data, I'm not sure where you hear 96 megs but its complete unnecessary to have that much space free. I've yet to experience any slowdowns or low mem warnings. Also remember.... some devs put parts of their rom on /data partition and that will decrease your available space.
Also, there's absolutely NO WAY you should be getting low mem warning with 34 megs free. That only happens when you have less then 10 megs available. Apps2sd is the obvious choice if you want to have as much phone mem available as possible.
Your a real geniuos ty I got it to work but what is the secondary sd for what does it store and how can I access it I am currently using estrongs explorer
Don't know about estrongs... never used it. Rule of thumb, if it asks for SU access the first time you run it - then it will be able to access it.
I'll break it down for ya
Internal memory:
/system - your rom
/system/app - system files (google apps, dialer, contacts etc)
/system/**** - extra stuff that our devs include (thanks to them)
/data/app - non-protected apps
/data/app-private - protected apps
/data/dalvik-cache - working files for all apps
/data/data - your settings
/system/sd - aka your secondary partition, aka apps2sd is a part of your sdcard. Only accessible in Linux or in terminal. When you have apps2sd set up, your phone will bypass /data/app, data/app-private and /data/dalvik-cache and forward those files to /system/sd/app, /system/sd/app-private and /system/sd/dalvik-cache. It will still use /data/data for all of your settings. I know it's a lot of slashes there but it will start making sense as you progress with Android hacking.
If you want to see what's on secondary sd just type this in terminal
Code:
ls /system/sd
This will give you a print-out of the apps that are on your sd.
Anything else I'm forgeting?
Ok this is the new output
$ su# busybox df -h Filesystem*************** Size***** Used Available Use% Mounted on tmpfs******************* 47.8M**** 12.0K**** 47.8M** 0% /dev tmpfs******************** 4.0M******** 0***** 4.0M** 0% /sqlite_stmt_journals/dev/block/mtdblock3**** 67.5M**** 61.8M***** 5.7M* 92% /system/dev/block/loop0
Is it possible you can give me a list of all the commands for terminal
http://www.droidforums.net/forum/droid-hacks/26036-linux-commands-android.html
Try this, some basics.
want to make exact image of my whole os and all apps in it
Is it possible to make an exact image of of my whole os including the apps web bookmarks and etc
sort of like the program iamgeburn does for pc
yea a nandroid back up. check your recovery for a back up option
So i just head to recovery and choose nanodroid then choose backup right
after soing so where does it save to and how can i retrieve it after a complete wipe of sd and system
saved on your sdcard under nandroid.
To use it, in recovery select restore and choose the nadroid that you want to recover. Your now back to exactly where you were when you created it.
easy peasy.
Been searching tons of forums for answer, seems like no ones problem is quite like mine though, so...Time to ask you guys
I'm running newest RA-Amon Recovery
I'm running Damage Control 2.09.01
I have been TRYING to get A2SD working correctly for a few days now with no luck....
I've formatted my card, wiped my phone, partitioned SD as follows:
Swap 32mb
Ext 2 512mb (Changed to Ext 3)
Fat32 Remainder
Not sure if it matters, but I have a 32GB SD card...
When I run busybox df -h this is what I get:
C:\AndroidSDK\tools>adb shell
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.5M 0 95.5M 0% /dev
tmpfs 4.0M 4.0K 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 141.6M 28.4M 83% /system
/dev/block/mtdblock5 159.5M 67.1M 92.4M 42% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 457.4M 5.0K 433.0M 0% /system/sd
/dev/block//vold/179:1
30.7G 31.5M 30.7G 0% /sdcard
Also, if I try to install a program from Market, it downloads fine, but Fails to Install due to Insufficient Storage
If anyone has any ideas or would like me to try something else, I'm all ears. Phone starting to frustrate me
Don't know if this will work, but try this:
Go into an adb shell. Type this:
cd /data/data/com.android.vending/cache
rm -f *
reboot
This will clear the market cache and reboot your phone.
Let me know if that works.
kronik03 said:
Been searching tons of forums for answer, seems like no ones problem is quite like mine though, so...Time to ask you guys
I'm running newest RA-Amon Recovery
I'm running Damage Control 2.09.01
I have been TRYING to get A2SD working correctly for a few days now with no luck....
I've formatted my card, wiped my phone, partitioned SD as follows:
Swap 32mb
Ext 2 512mb (Changed to Ext 3)
Fat32 Remainder
Not sure if it matters, but I have a 32GB SD card...
When I run busybox df -h this is what I get:
C:\AndroidSDK\tools>adb shell
# busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 95.5M 0 95.5M 0% /dev
tmpfs 4.0M 4.0K 4.0M 0% /sqlite_stmt_journals
/dev/block/mtdblock3 170.0M 141.6M 28.4M 83% /system
/dev/block/mtdblock5 159.5M 67.1M 92.4M 42% /data
/dev/block/mtdblock4 130.0M 1.1M 128.9M 1% /cache
/dev/block/mmcblk0p2 457.4M 5.0K 433.0M 0% /system/sd
/dev/block//vold/179:1
30.7G 31.5M 30.7G 0% /sdcard
Also, if I try to install a program from Market, it downloads fine, but Fails to Install due to Insufficient Storage
If anyone has any ideas or would like me to try something else, I'm all ears. Phone starting to frustrate me
Click to expand...
Click to collapse
Just a little question going around. is mine normal? 108mb free.
http://dl.dropbox.com/u/14612246/CAP201109101129.png
Code:
/ # df /system
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/block/system 327922 318477 9445 97% /system
5.6.890; Mildly molested filesystem...