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.

Moving from EXT4 ROM to an EXT3 one

I recently installed WCX Illuminati [3.5 Sense Based on 1.22.461.2 (Quicksall Rcmix kernel v12 )overclocked to 1536 by default.].
While the ROM is not advertised to be (as far as I can tell) an EXT4 ROM, I noticed during the install the system was formatted as EXT4.
I'll like to experiment with some other ROMs that are EXT3. Do I have to go through any special steps to go back to an EXT3 ROM after running an EXT4 ROM, I can I just flash the new ROM though CM Recovery?
Thanks.

Four-Fifty-X said:
I recently installed WCX Illuminati [3.5 Sense Based on 1.22.461.2 (Quicksall Rcmix kernel v12 )overclocked to 1536 by default.].
While the ROM is not advertised to be (as far as I can tell) an EXT4 ROM, I noticed during the install the system was formatted as EXT4.
I'll like to experiment with some other ROMs that are EXT3. Do I have to go through any special steps to go back to an EXT3 ROM after running an EXT4 ROM, I can I just flash the new ROM though CM Recovery?
Thanks.
Click to expand...
Click to collapse
There are no steps for that, just flash the new Rom. But make sure to flash CWM recovery first as the illuminati Rom uses stock recovery. Go to Rom manager and flash recovery. Once you have done that flash the Rom you want.
Sent from my Inspire 4G using XDA App

glevitan said:
There are no steps for that, just flash the new Rom. But make sure to flash CWM recovery first as the illuminati Rom uses stock recovery. Go to Rom manager and flash recovery. Once you have done that flash the Rom you want.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Good. Thanks.
Sent from my HTC Inspire 4G using XDA App

I was wondering this myself also. But I want to ask a little deeper question.
Say I have 2 ROMS. One that is ext3 and the other that is ext4. Each one formats the system appropriately when installed fresh. But say I have a NAND backup of the ext3 ROM on my card and I have the ext4 ROM installed on the phone at the present. Can I restore the ext3 ROM without doing anything other than the normal wiping using clockwork? Or would I have to reinstall the ext3 ROM fresh to get the proper format and then restore the backup?
And would it be the same going the other direction too?

Agoattamer said:
I was wondering this myself also. But I want to ask a little deeper question.
Say I have 2 ROMS. One that is ext3 and the other that is ext4. Each one formats the system appropriately when installed fresh. But say I have a NAND backup of the ext3 ROM on my card and I have the ext4 ROM installed on the phone at the present. Can I restore the ext3 ROM without doing anything other than the normal wiping using clockwork? Or would I have to reinstall the ext3 ROM fresh to get the proper format and then restore the backup?
And would it be the same going the other direction too?
Click to expand...
Click to collapse
I guess but not sure that when you do a wipe to install a new Rom your partitions are formatted and ifvyo don't use an ext4 Rom then you will have just ext3.
Sent from my Inspire 4G using XDA App

Agoattamer said:
I was wondering this myself also. But I want to ask a little deeper question.
Say I have 2 ROMS. One that is ext3 and the other that is ext4. Each one formats the system appropriately when installed fresh. But say I have a NAND backup of the ext3 ROM on my card and I have the ext4 ROM installed on the phone at the present. Can I restore the ext3 ROM without doing anything other than the normal wiping using clockwork? Or would I have to reinstall the ext3 ROM fresh to get the proper format and then restore the backup?
And would it be the same going the other direction too?
Click to expand...
Click to collapse
I'm not sure how ClockworkMod handles this but I've been using 4EXT Recovery for a few months and it will automatically determine which format the ROM you're flashing uses and convert if necessary. Works for both fresh ROM flashes or backups.
I've been running ARHD and wanted to pull something off of the stock ROM backup I had. When I restored the stock nandroid, 4EXT formatted the existing ext4 partitions to ext3 and restored the backup. Then when I restored ARHD it automatically switched 'em back to ext4.

Thanks for the responses guys. Still looking for someone to answer positively on this last question. I don't want to be the someone asking about how to get my phone to boot when it is stuck on the white screen. lol.

Agoattamer said:
Thanks for the responses guys. Still looking for someone to answer positively on this last question. I don't want to be the someone asking about how to get my phone to boot when it is stuck on the white screen. lol.
Click to expand...
Click to collapse
i'm with the other guy, i use 4EXT. but when making a backup it says "writing ext4 data" (or something along those lines) for each partition that uses ext4. it does the same for ext3.
i would be inclined to believe that CWM does the same thing and changes the file system accordingly. one way to check if it records the file system type would be to look at the tar files. go to sdcard/clockworkmod/backup/whatever-you-named-your-backup that folder should contain, at a minimum, the following files: system.xxxx.tar, data.xxxx.tar, boot.img, and an md5 file. the xxxx should be the file system that particular backup uses.
EDIT: that is assuming that CWM uses tar backups and not yaffs2. not sure how those backups are structured. either way the filesystem should still get recorded some how.
i think you'd be fine just restoring. there would have been massive amounts of new threads popping up saying "OMGIDIDARESTOREANDMYPHONEISFUX0RED!!!!" if anyone had any problems once ext4 showed its face. know what i mean?
as an alternative. why not just flash 4EXT Recovery? since you KNOW it does what you're asking? kinda takes the guess work out... lol

ext3 format?

So I am going to flash my phone to the ICS Debloated for the droid thunderbolt. problem? one step says
4ext Recovery
Make sure to format in ext3 format!
You need to wipe everything!!!!
There is no data wipe built in so folks can reflash at will and restore system.
First time, wipe everything!!! All partitions except SD!
Especially if coming from GB or AOSP!
Ok so i have 4ext recovery fully installed on my phone.
but how do i format to ext3 what is it, what does it do, and how do i go about perfecting this so i can flash my phone in flying colors. some one please help.

ext3 is file system used in Linux
There should be some software for windows to format partition in ext3.
Maybe some drivers could help.

mcstando said:
ext3 is file system used in Linux
There should be some software for windows to format partition in ext3.
Maybe some drivers could help.
Click to expand...
Click to collapse
wait...so how do i go about make my sd card ready so that i can flash ICS unloated on my t-bolt? I am noob to the maximum, please forgive me.

snake2243 said:
wait...so how do i go about make my sd card ready so that i can flash ICS unloated on my t-bolt? I am noob to the maximum, please forgive me.
Click to expand...
Click to collapse
here read this:
http://forum.xda-developers.com/showthread.php?p=37383522#post37383522

chromium96 said:
here read this:
http://forum.xda-developers.com/showthread.php?p=37383522#post37383522
Click to expand...
Click to collapse
why are you so awesome?

Which Recovery allows Sd-ext formatting option for ext4

Hi I am using currently TouchWiz JB V2 ROM ....
My recovery is CWM 5.0.2.6
When every i partitioned my sdcard/Wipedata/ it always formats in ext3 format
Is there a recovery that i can use which formats in ext4 format.....
Also iam unbale to use int2ext+ in my JB 4.2.2 i believe improper revocery ability to format my sd card...
Thanks any help will be appreciated..

use TWRP recovery.

Use amora 3.0.6
Sent from my LG-P500 using xda premium

allenwalker1998 said:
Use amora 3.0.6
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
+1
@OP, you made 2 identical posts...
you have to wait for answers and maybe search a little bit more before creating new topics.

uf0999 said:
+1
@OP, you made 2 identical posts...
you have to wait for answers and maybe search a little bit more before creating new topics.
Click to expand...
Click to collapse
Thanks for the answer. and as of the double posts ill keep that in mind.
Also when i checked it it looks like a flashable zip file......
So if i flash it over my existing recovery (CWM 5.0.2.0) do i need to back up before it ......
Also is a wipe data/factory reset required.

solution
maybe CWM 5.0.2.0 will be the best, it formats ext partition in ext4 format and also can take backup of ext partition also with backup of full rom , which CWM 5.0.2.6 can't... so use CWM 5.0.2.0 it is good enough.

smartyateeb said:
maybe CWM 5.0.2.0 will be the best, it formats ext partition in ext4 format and also can take backup of ext partition also with backup of full rom , which CWM 5.0.2.6 can't... so use CWM 5.0.2.0 it is good enough.
Click to expand...
Click to collapse
Oh, man... This quite a big deal. I had to learn this the hard way. Had always backed up with 5.0.2.6 and, the day I needed to restore my ext4 position, I was not able to... just stick to 5.0.2.0 and be happy. You are losing nothing with this recovery version.
Sent from my GT-P7500 using xda premium

[Q] Data On My Internal Storage?

Hi guys, this is my first post on this forum ( Actually I have benn here for a long time without account )
Alright, This is my problem, I usually flash back to stock by RUU, my Pico has over 100MB free space. A few days ago, I flashed the same RUU, but this time I have 70MB space only, I have cleaned all partitions by recovery and flash again, still.
Oh wait, I just use Disk Usage and check the storage, it's say there are some data(not system) on the internal storage, wow.
Does anyone have ideas?
My Pico cid is Taiwan(621), so I flash TW RUU.
Thanks

before flashing, did you wipe system partition too?

Affangta said:
before flashing, did you wipe system partition too?
Click to expand...
Click to collapse
yeah, I did, everything wiped before flash back by RUU, actually before this, I never wipe by myself but has no problems,

AA181891 said:
yeah, I did, everything wiped before flash back by RUU, actually before this, I never wipe by myself but has no problems,
Click to expand...
Click to collapse
why not sd-ext partition for apps?

Affangta said:
why not sd-ext partition for apps?
Click to expand...
Click to collapse
I know that and it's convenience, but this smartphone now is just my secondary phone.
And for a odd reason, I prefer not to creat a partition on my SD card, just like to keep it simple and clean.
Looks like I'm stubborn...