Kitchen r9 ROM non-a2sd/+, S-OFF using Data++ img, 146M Free on /data, steps I took.

[Guest castroak]

Just wanted to share this with everybody just in case anybody is interested. I have been hunting around few days now how to get this accomplished and finally put it all together. Might seem simple for some but I had to do some digging around, also bunch post here and XDM and as well answer from Paul, Thanks Paul.

I baked custom ROM and left out stuff I didn't really need or use, post where I listed what I had. The /system came to be about 165M.

I S-OFFed my phone, flashed the AlphaRev Bravo Sense image, then installed the Custom baked r9 ROM. Booted it up few times, it all worked good.

Then rebooted into recovery and deleted the /system/etc/init.d/02cachedalvikcache of the phone, Paul pointed me in the right direction, also there is post that I missed on that here. Basically deleting that script makes the phone use only /data for davlik-cache, vs splitting up the dalvik-cache between /cache and /data. While booted into recovery also, then using the adb I deleted all the files from /cache/dalvik-cahce/ and /data/davlik/cache/ folders, they'll get rebuilt on the next boot BUT only in /data. Booted it back up and sure enough /cache was not used any more and all of the dalvik-cache files got created in the /data/dalvlik-cache/ directory, /cache was about 2M now without any dalvik-cache files. Phone worked good when booted back up.

Rebooted into recovery mode and did a nandroid backup of the ROM.

Then I rebooted into fastboot/hbbot, flashed the AlphaRev Bravo Data++ image to the phone. This basically made my partitions /system - 180M, /cache 10M, and /data 261M.

Formatted my /boot, /data, /system, and /cache partitions from the recovery mode. Then did a nadroid recovery of the previously backup ROM, the one that has all of the dalvik-cache files moved over to the /data partition.

Booted it backup and yeah !!!! Everything running of the internal flash, with 146M Free on the /data partition, which is plenty for my apps I install.

For grins, I booted into recovery again and deleted all of the files from /data/dalvik-cache/ directory again and then rebooted just to make sure it was all good, and sure enough it was good.

From gathering next time I want to flash a new MoDaCo ROM, make sure that the /system in the zip is under 180MB (for me not a problem), delete the /system/etc/init.d/02cachedalvikcache from the ROM zip before flashing, and it's all good, all of the dalvik-cache files go into /data/dalvik-cahce/ directory and life is great with plenty of room on /data !!!! The ONLY draw back to this, you have to flash the radio though the fastboot interface, can't do it through the recovery due to the small /cache partition, but that really is not a big deal either to do, very simple.

Not sure if anybody wanted all these details or to know this much but here it is. Thanks everybody who answered few other posts that I had made here and XDA and Paul.

[Guest byt123]

Not sure if anybody wanted all these details or to know this much but here it is. Thanks everybody who answered few other posts that I had made here and XDA and Paul.

Nice post !

I've been looking at ways to increase space recently, especially when I hit the 15mb remaining mark on data.. I've gone the alpharev and a2sd+ route though, with a 1gb partition on my sd card for the data.. some people have commented on downsides for this but I haven't hit on them myself. If there are downsides that turn up I'll have a look at implementing your option.

Cheers.

EDIT:

Can't do it - my system partition is greater than the 180mb for some reason.

df -h

Filesystem				Size	  Used Available Use% Mounted on

tmpfs				   207.6M		 0	207.6M   0% /dev

tmpfs				   207.6M		 0	207.6M   0% /mnt/asec

/dev/block/mtdblock3	250.0M	182.8M	 67.2M  73% /system

/dev/block/mtdblock5	147.6M	 14.2M	133.4M  10% /data

/dev/block/mtdblock4	 40.0M	 34.1M	  5.9M  85% /cache

tmpfs					 8.0M		 0	  8.0M   0% /app-cache

/dev/block/mmcblk0p2	915.1M	194.3M	672.0M  22% /system/sd

/dev/block/mmcblk0p2	915.1M	194.3M	672.0M  22% /data/data

Edited December 29, 2010 by byt123

[Guest bpivk]

Can't do it - my system partition is greater than the 180mb for some reason.

It depends on the rom. The more system apps it holds the less free system memory and if you're using Sense HD you use more system memory than in normal Sense.

I hope that makes sense. :(

[Guest castroak]

Nice post !

I've been looking at ways to increase space recently, especially when I hit the 15mb remaining mark on data.. I've gone the alpharev and a2sd+ route though, with a 1gb partition on my sd card for the data.. some people have commented on downsides for this but I haven't hit on them myself. If there are downsides that turn up I'll have a look at implementing your option.

Cheers.

EDIT:

Can't do it - my system partition is greater than the 180mb for some reason.

df -h

Filesystem				Size	  Used Available Use% Mounted on

tmpfs				   207.6M		 0	207.6M   0% /dev

tmpfs				   207.6M		 0	207.6M   0% /mnt/asec

/dev/block/mtdblock3	250.0M	182.8M	 67.2M  73% /system

/dev/block/mtdblock5	147.6M	 14.2M	133.4M  10% /data

/dev/block/mtdblock4	 40.0M	 34.1M	  5.9M  85% /cache

tmpfs					 8.0M		 0	  8.0M   0% /app-cache

/dev/block/mmcblk0p2	915.1M	194.3M	672.0M  22% /system/sd

/dev/block/mmcblk0p2	915.1M	194.3M	672.0M  22% /data/data

yeah It's going to matter what apps you have selected when you cook the ROM. Now if you download a pre-cooked one, you can remove any apps that you don't want from the /system or the /apps folder in the zip before flashing it. Also you are able to move apps from /system to /data and the other way around, link talking about that. you can move then prior to the install or after, BUT if you move them after you install you probably have to do it via adb in recovery mode.