Database Info

[Q] Hboot vs. /Cache size

Hi all.
I am curious about the differences in the Engineering bootloaders that we have for our devices (0.98.xxxx, 6.xx.xxxx, 2.00.2002) in terms of partitioning.
So I would like to gather some statistics from the you (users in this forum) about the size of your /cache partition and the bootloader (hboot) that you are using to see is there a difference.
For the hboot version you just have to reboot to bootloader from the power menu
for the size of the /cache partition use the Android Terminal Emulator (free from the Market) and type:
Code:
df
then look at the row that is written /dev/block/mmcblk0p27 - the size is next to it (under the 1K-blocks column)
Thank you in advance!

/cashe is 302356K total
My hboot is stock (0.98.0002)

my cache is 138mb using new ENG HBOOT 2.00.2002

HBOOT 2.00.2002 (The leaked one from about a month ago).
150mb/138mb free.

i have the same cache as u but cannot see the lib partition anywhere after updating to the new hboot. can u?

Eclipse_Droid said:
i have the same cache as u but cannot see the lib partition anywhere after updating to the new hboot. can u?
Click to expand...
Click to collapse
I think this works only with the leaked Deseire S Sense 2.0 [2.3.5], ported by proxuser and its kernel. Because this bootloader appeared in the forum for the new kernel users. I am not aware whether any of the custom ROMs supports that kernel, so maybe this hboot 2.00.2002 is useful only for the leaked stock roms (proxuser's and the new OTA one). Just my assumption...
P.S.: Thank for the posted so far!. Looks fro your posts that the stock bootloader offers the most cache space. Looking for other inputs

I'm running the new HBOOT 2.xx.xxxx and I'd like a decent in lay-mans terms explanation of where the 150Mb that CACHE has lost has gone to, I believe LIB but I can't see a LIB partition? So is it being used or will it be used....someone please explain? I've read some attempted explainations but I'm afraid to say that I'm still not happy that I completely understand - I also believe that this is a particular question that many other users would appreciate an answer to.
Code:
$su
# df
/dev: 313160K total, 64K used, 313096K available (block size 4096)
/system: 562404K total, 493304K used, 69100K available (block size 4096)
/data: 1184268K total, 417700K used, 766568K available (block size 4096)
/cache: 146124K total, 4252K used, 141872K available (block size 4096)
/mnt/asec: 313160K total, 0K used, 313160K available (block size 4096)
/mnt/obb: 313160K total, 0K used, 313160K available (block size 4096)
/app-cache: 8192K total, 0K used, 8192K available (block size 4096)
/data/DxDrm/fuse: Permission denied
/mnt/sdcard: 31322160K total, 7923328K used, 23398832K available (block size 16384)
/mnt/secure/asec: 31322160K total, 7923328K used, 23398832K available (block size 16384)
/system/etc/virtuous_oc: 313160K total, 24K used, 313136K available (block size 4096)
#
EDIT: changed CACHE back to ext4 so altered numbers for CACHE to reflect this!
Swyped from my Desire S using XDA Premium

Eclipse_Droid said:
i have the same cache as u but cannot see the lib partition anywhere after updating to the new hboot. can u?
Click to expand...
Click to collapse
Btw have you flashed the PG88IMG that is attached in the hboot 2.002.002 guide?? This is your lib partition, but it works only on Sense based ROMs or even only Sense Stock ROMs (like the one from proxuser)?.
@ben_pyett
+1. This was the main reason for starting this thread. Because in my desire to be up to date I flashed all the new stuff that came around, but now I start to question myself is this really necessary...

amidabuddha said:
Btw have you flashed the PG88IMG that is attached in the hboot 2.002.002 guide?? This is your lib partition, but it works only on Sense based ROMs or even only Sense Stock ROMs (like the one from proxuser)?.
@ben_pyett
+1. This was the main reason for starting this thread. Because in my desire to be up to date I flashed all the new stuff that came around, but now I start to question myself is this really necessary...
Click to expand...
Click to collapse
Just released the somehow my CACHE had become ext3? no idea when or how this happened so convered to to ext4 using 4EXT recovery and reformatted.
So I altered the numbers in the above post to reflect changes this made.
I used a different method as I was S-OFF via XTC Clip! [GUIDE] XTC-Clip users guide to new HBOOT 2.00.2002

Its depends on the rom and the install script.
Proxusers OTA is compatible with the old HBOOT, so it doesnt use the new lib partition.
If you flash the untouched version you have the lib partition.

caravanquello said:
Its depends on the rom and the install script.
Proxusers OTA is compatible with the old HBOOT, so it doesnt use the new lib partition.
If you flash the untouched version you have the lib partition.
Click to expand...
Click to collapse
Yep, you are right. I meant the early proxuser's versions that I was happy to use up to v8 (IMO very good work). But then I gave up on Sense and not regretting a bit. Anyway according to your explanation my logic is right and this 2.00.2002 hboot is only useful for HTC ROMs, although modified by the devs here, but is pointless to use with ROM's that are not supporting it i.e. most of them.
@ben_pyett
I think that the new radio installation is messing with the cache partition, because I had the "cache_log" error after flashing it, also I am reading a lot of feedbacks from users that had to restore/reformat this partition after flashing the radio due to "not enough space" error when installing apps from the Market.

amidabuddha said:
@ben_pyett
I think that the new radio installation is messing with the cache partition, because I had the "cache_log" error after flashing it, also I am reading a lot of feedbacks from users that had to restore/reformat this partition after flashing the radio due to "not enough space" error when installing apps from the Market.
Click to expand...
Click to collapse
I possibly can agree with that as I also encountered that problem with the market after installing both the latest radio and being on latest HBOOT.
Although market space error was simply resolved by a CACHE wipe, although I'm still unsure what particular process or step put my CACHE to ext3?

ben_pyett said:
I possibly can agree with that as I also encountered that problem with the market after installing both the latest radio and being on latest HBOOT.
Although market space error was simply resolved by a CACHE wipe, although I'm still unsure what particular process or step put my CACHE to ext3?
Click to expand...
Click to collapse
exactly same thing happened to me too. just formatted back to ext4. byy the way i am now back on old ENG HBOOT and i have got my full 300mb cache partition back

Eclipse_Droid said:
exactly same thing happened to me too. just formatted back to ext4. byy the way i am now back on old ENG HBOOT and i have got my full 300mb cache partition back
Click to expand...
Click to collapse
Can you please explain how you did this, because I am also on the old bootloader but my /cache is still halved (150 MB)??
EDIT: when I reboot in the Recovery my /cache is exactly 300 MB, but the "df" command in the Terminal is showing 150 MB?? Is this the same in your case?
EDIT2: I have wiped the cache and now it shows 300 MB in the terminal. Hooray!
Just to confirm my assumption that the radio is the reason for this mess. What I did to the current state was:
1) I think I was the first one that flashed it over 2.00.2002 (almost immediately after it was posted, even before the ben_pyett's first question on the OTA radio thread, and I stuck with the famous "cache_log" error. I was scared that my eMMC is gone. So I reflashed RUU with the intention to go to the repair center with the stock hboot, etc.
2) then I saw that my system is fine (oh how happy I was) I used the revolutionary tool
3) then I flashed the old ENG HBOOT 0.98.2000
4) then I flashed the new OTA radio again
5) then I flashed the CM7 Nightly, Tiamat kernel and the GApps
6) after booting the ROM I installed the 4EXT recovery
7) after that I rebooted in the Recovery and had again the "cache_log" error, but I was calm this time and just formatted it as ext4
8) then I have noticed that my /cache is 150 MB???
so only thing that I have made extra than prevously was the new radio. CM has no customized partitioning and for me the only cause of the can be this Radio...

amidabuddha said:
Can you please explain how you did this, because I am also on the old bootloader but my /cache is still halved (150 MB)??
EDIT: when I reboot in the Recovery my /cache is exactly 300 MB, but the "df" command in the Terminal is showing 150 MB?? Is this the same in your case?
EDIT2: I have wiped the cache and now it shows 300 MB in the terminal. Hooray!
Just to confirm my assumption that the radio is the reason for this mess. What I did to the current state was:
1) because I was stuck with the famous "cache_log" error and I think I was the first to flash it over 2.00.2002 (almost immediately after it was posted, even before the ben_pyett's first question on the OTA radio thread, I was scared that my eMMC is gone. So I reflashed RUU with the intention to go to the repair center with the stock hboot, etc.
2) then I saw that my system is fine (oh how happy I was) I used the revolutionary tool
3) then I flashed the old ENG HBOOT 0.98.2000
4) then I flashed the new OTA radio again
5) after that I had again the "cache_log" error in the recovery, but I was calm this time and just formatted it as Ext4
5) then I flashed the CM7 Nightly, Tiamat kernel and the GApps
6) then I have noticed that my /cache is 150 MB???
so only thing that I have made extra than prevously was the new radio. CM has no customized partitioning and for me the only cause of the can be this Radio...
Click to expand...
Click to collapse
interesting!
everything you experienced with the cant mount errors after flashing the new radio happened to me too! i too feared i had fried the emmc chip! I am still on new radio now and everything is fine after reformatting the cache partition.
In answer to your question i believe it MUST be the new radio trying to alter partition of the cache. This would explain why it is giving you the same "cant mount cache" error as it gives when flashing new HBOOT. Something in the installation of the radio package must be trying to split the partition.
Anyway, im happy now! and by the sounds of it u are too, and have pretty much the same base setup as i do
OLD ENG HBOOT ALL THE WAY!!

@ben_pyett
Just an addition to my previous assumption.
I doubt that the Stock ROM natively supports ext4. So if the radio is altering somehow the /cache partition it of course is designed to search and manipulate an ext3 type partition (most probably this is the cause of the error). When you have reformatted, it was restored as it was labeled by the radio script - as an ext3. So the restoration solved your Market problem, you just noticed the ext3 type later.
Sent from my HTC Desire S using XDA App

amidabuddha said:
@ben_pyett
Just an addition to my previous assumption.
I doubt that the Stock ROM natively supports ext4. So if the radio is altering somehow the /cache partition it of course is designed to search and manipulate an ext3 type partition (most probably this is the cause of the error). When you have reformatted, it was restored as it was labeled by the radio script - as an ext3. So the restoration solved your Market problem, you just noticed the ext3 type later.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
this is a very good point! but why is it only changing the cache partition and not the rest?

Eclipse_Droid said:
this is a very good point! but why is it only changing the cache partition and not the rest?
Click to expand...
Click to collapse
I think that at this point already some of the devs has to clarify further
Edit: now a conversation with Nexx in his CM7 thread comes to me. He said that the new partition (lib) is taking up space from the /cache not from /system (which fact is verified by the results in this thread). So maybe the script is checking for the "properly" mounted partitions and when is not finding the lib.img is trying to remount or to force reformat/rebuild that is causing the corruption. Just a theory of mine but linux is working quite straightforward as far as I know
Sent from my HTC Desire S using XDA App

amidabuddha said:
I think that at this point already some of the devs has to clarify further
Edit: now a conversation with Nexx in his CM7 thread comes to me. He said that the new partition (lib) is taking up space from the /cache not from /system (which fact is verified by the results in this thread). So maybe the script is checking for the "properly" mounted partitions and when is not finding the lib.img is trying to remount or to force reformat/rebuild that is causing the corruption. Just a theory of mine but linux is working quite straightforward as far as I know
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
i guess this could be true! either way, we are both running new radio now without any issues
just a bit annoying having to go through this process before you have it working

Well done gentlemen!
It's good to at least get to the bottom of why the file system ext3->ext4 conversion occurred.

[Q] How to resize/recreate /system and /data partitions?

With all the lighter custom ROMs we have today, the default huge /system partition we have in the O3D is a waste of space. Same with the /data partition. For those who don´t know, both /system and /data (and other smaller ones) are actual internal SD Card space!
That´s why we have LG specs saying we have 8GB of internal flash storage, when in fact we have just 5.5GB available.
So my question is: is there a (safe) way to wipe all internal SD partitions and then recreate them with more appropriate sizes, earning back all the wasted space?
Thanks a lot!

Marcovecchio said:
With all the lighter custom ROMs we have today, the default huge /system partition we have in the O3D is a waste of space. Same with the /data partition. For those who don´t know, both /system and /data (and other smaller ones) are actual internal SD Card space!
That´s why we have LG specs saying we have 8GB of internal flash storage, when in fact we have just 5.5GB available.
So my question is: is there a (safe) way to wipe all internal SD partitions and then recreate them with more appropriate sizes, earning back all the wasted space?
Thanks a lot!
Click to expand...
Click to collapse
Have you read about data2ext? I think it would be a very good solution to us.
Sent from my LG-P920 using XDA App

Thanks for the reply, ThiaiZ!
However, I think I´m looking for something different: as far as I know, data2ext changes the /data partition pointer to external memory (SD Card), so the original /data partition will never be used by the OS, and it´s space will be wasted, right?
I would like to find a way to get this wasted space back! If we could repartition /system, /data, /cache, to smaller sizes, we would have more storage space for stuff on the internal SD. Does it make sense? Thanks!

Well, since I had no solutions here, I would like to post some examples of this for other phone models:
MyTouch 3G Slide - http://forum.xda-developers.com/showthread.php?t=893706
LG GT540 - http://forum.xda-developers.com/showthread.php?t=1171531
The MyTouch 3G Slide thread is particularly good because it explains in detail how to check the partition sizes, and shows how much space is wasted on the /system partition.

Marcovecchio said:
Well, since I had no solutions here, I would like to post some examples of this for other phone models:
MyTouch 3G Slide - http://forum.xda-developers.com/showthread.php?t=893706
LG GT540 - http://forum.xda-developers.com/showthread.php?t=1171531
The MyTouch 3G Slide thread is particularly good because it explains in detail how to check the partition sizes, and shows how much space is wasted on the /system partition.
Click to expand...
Click to collapse
Don't we have to be s-off to be able to resize the partitions ?
I did it a lot on my HTC Desire.
BTW do you have any idea in which block data and sd-ext are mounted on our device ?

I believe the S-OFF flag exists only in HTC devices. I read that somewhere here, at XDA. The guy seemed to know what he was talking about, and he said LG never implemented any kind of protection like S-ON / S-OFF.
About the block names, I believe you can list the blocks and the partition names they´re mounted as, with the "df" command. I know almost nothing about Linux, and even less about how Android manage it´s partitions, but that would be nice to be able to tweak their sizes...

LG GT540's partitions can easily be resized by flashing an MBN file. Don't know if this phone can get that done too
http://forum.xda-developers.com/showthread.php?t=1171531

Don't try resizing partitions.
You'll brick your phone.

[Q] Resizing active partitions

Is it possible to resize active partitions/
I am running Stock JB on sytem1 and ParanoidAndroid 4.3 on ssytem 2 (this is my primary system). Prior to ROM flashing I created (3) 1GB partitions for each system. Now my Data partition for system 2 is at 100MB even after I moved every app I could to the SD card. Every thread I looked at said 1GB was more than enough for a data partition so I cannot understand how I've run out of space. Perhaps I am not using the partition structures correctly. Anyway, I was hoping to resize an active partition the same way I have with Partition Magic when resizing a Windows drive partition. Thanks for any replies.

[Q] Problem with Link2sd after resizing ext2partition

Hi all...
Im having problem with Link2sd after resizing the second partition.
What I had done:
Before resizing the partition I copied all the files from ext partition to my desktop
I resized the partition to a smaller one, from 4.5 gb to 3.5.
The total filesize in this partition was under 2 gig.
Using minipartition tool I deleted the ext partition.
Resized my existing fat partition to 4 gb and created ext partition with rest of the space
Ext partition was created as primary.
Now I copied back all the files from desktop to sd card.
But everytime I start with my sdcard, Samsung logo keeps showing after boit sound.
I waited for 5 minutes but nothing happnd.
I started without sdcard. And tried recreating mount script.But the same problem.
How to overcome this problem. Do I need to start from the beginning? ?
My device Samsung Galaxy Fame 6812.
Running jb 4.1 Stock ROM definitely Rooted.

droidshan said:
Hi all...
Im having problem with Link2sd after resizing the second partition.
What I had done:
Before resizing the partition I copied all the files from ext partition to my desktop
I resized the partition to a smaller one, from 4.5 gb to 3.5.
The total filesize in this partition was under 2 gig.
Using minipartition tool I deleted the ext partition.
Resized my existing fat partition to 4 gb and created ext partition with rest of the space
Ext partition was created as primary.
Now I copied back all the files from desktop to sd card.
But everytime I start with my sdcard, Samsung logo keeps showing after boit sound.
I waited for 5 minutes but nothing happnd.
I started without sdcard. And tried recreating mount script.But the same problem.
How to overcome this problem. Do I need to start from the beginning? ?
Click to expand...
Click to collapse
Whats the phone you're talking about?

LS.xD said:
Whats the phone you're talking about?
Click to expand...
Click to collapse
Oopss. Im really sorry for not specifying device model..
My device Samsung Galaxy Fame 6812.
Running jb 4.1 Stock ROM definitely Rooted.

droidshan said:
Oopss. Im really sorry for not specifying device model..
My device Samsung Galaxy Fame 6812.
Running jb 4.1 Stock ROM definitely Rooted.
Click to expand...
Click to collapse
The operation to link storage to ext partition is scripted. Ext4 partition has to be formatted once after installing the script to work properly. Link2SD performs this when setting up. You can try formatting the SD-Ext partition using your custom recovery but i suppose you will have to set up the ext partition again usning Link2SD

LS.xD said:
The operation to link storage to ext partition is scripted. Ext4 partition has to be formatted once after installing the script to work properly. Link2SD performs this when setting up. You can try formatting the SD-Ext partition using your custom recovery but i suppose you will have to set up the ext partition again usning Link2SD
Click to expand...
Click to collapse
Yes, I copied the files back to ext partition after formatting the partition.
Do I need to start from the scratch?

Did you Format it using the custom recovery?
Sent from my beloved HTC One S using (most time buggy) Tapatalk

No custom recovery, running with stock recovery. I had no problem when I first started link2sd with no apos linked.
I formatted the ext partition from mini partition tool

droidshan said:
No custom recovery, running with stock recovery. I had no problem when I first started link2sd with no apos linked.
I formatted the ext partition from mini partition tool
Click to expand...
Click to collapse
Seems as you need to set up the partition via Link2SD again

LS.xD said:
Seems as you need to set up the partition via Link2SD again
Click to expand...
Click to collapse
Yes!! I had cleaned up the second partition from linked2sd. And rebooted.
Phone boots normally with basic apps..
Now I tapped " relink all files " frm link2sd . And copied one apk file from my backup & rebooted
Bingo!!! That app linked 2 sd .. now copying rest of the apps..
Thanks for helping me..

Resizing system and data partitions

Hello everyone, how can I resize my /system and /data partitions?
I've noticed that my system partition is 2.2GB big, but my system is using only 1G of it.
Meanwhile, my data partition, where the apps are stored, has 3.9 out of 4.5G in use.
Is it feasible to resize those?
If so, can you link me to any good how-to on how to do it? I would be very happy to have 0.7G more in my /Data partition.
Thanks in advance.
I've attached a pic of the issue.

frenchiveruti said:
Hello everyone, how can I resize my /system and /data partitions?
I've noticed that my system partition is 2.2GB big, but my system is using only 1G of it.
Meanwhile, my data partition, where the apps are stored, has 3.9 out of 4.5G in use.
Is it feasible to resize those?
If so, can you link me to any good how-to on how to do it? I would be very happy to have 0.7G more in my /Data partition.
Thanks in advance.
I've attached a pic of the issue.
Click to expand...
Click to collapse
Last time I messed with the partitions I semi-bricked my phone and had to restore stock firmware via ADB and fastboot. Won't be doing that again anytime soon. I am sure it can be done just be careful, goodluck.

Don't do it... really... this device has 20+ partitions, and messing with them almost always results in a non-bootable condition, and sometimes in hard brick state, and since we don't have the proper QDLoader files (and never will), it makes it a perma-brick. Messing with partitioning on newer device is problematic at best, because we can only access about 5-8 of the partitions out of the 20 or so on the device, but on the Moto without Qualcomm QDLoader recovery files, it is almost impossible.

Ok, good to know that I must not do it then.
Thanks for the replies!