Jump to content

CFW- How to increase the C drive size ?


vizhigal

Recommended Posts

For RM-356 CFW the C drive allotted space is 93061120 Bytes =  88 Mb . The ROFS2 maximum size is 113 Mb . If the ROFS2 size is reduced from 113 Mb to 83 Mb then  the unused space in the Z drive is 30 Mb. Whether this 30 Mb can be added to C drive capacity to make it as 118 Mb from the existing capacity of 88Mb. ( ROFS2 size can be reduced to 83 Mb by deleting unwanted language files and certain applications )

Link to comment
Share on other sites

For RM-356 CFW the C drive allotted space is 93061120 Bytes =  88 Mb .

The ROFS2 maximum size is 113 Mb .

If the ROFS2 size is reduced from 113 Mb to 83 Mb then  the unused space in the Z drive is 30 Mb.

Whether this 30 Mb can be added to C drive capacity to make it as 118 Mb from the existing capacity of 88Mb.

( ROFS2 size can be reduced to 83 Mb by deleting unwanted language files and certain applications )

Are you sure we could achieve this ?

And I get maximum of 79MB+ free memory in C:/ drive

Link to comment
Share on other sites

For RM-356 CFW the C drive allotted space is 93061120 Bytes =  88 Mb .

The ROFS2 maximum size is 113 Mb .

If the ROFS2 size is reduced from 113 Mb to 83 Mb then  the unused space in the Z drive is 30 Mb.

Whether this 30 Mb can be added to C drive capacity to make it as 118 Mb from the existing capacity of 88Mb.

( ROFS2 size can be reduced to 83 Mb by deleting unwanted language files and certain applications )

Ultra impossible I asked it about 7 or 8 months ago on pnht and even upakul,they all said tht it was alloted by Nokia and itz fixed-ROM,No one can change it :)

Link to comment
Share on other sites

Probably they might not have come across the below details. Check the RM-356  .C00 files for the below values OFFSET = 2CDF19 58C85F02122B000300 00040000 00082FFF      262144    536575          00083400 003FFFFF      537600    4194303 00400000 007FFFFF      4194304  8388607 00800000 00D5FFFF      8388608  14024703 00D60000 09E5FFFF      14024704  166068223 192F Leave the first and last line .( Just for identifications ) The first and the second are hexa decimal addresses of teh CMT blocks. The third and fourth are the sizes in bytes This talks about CMT blocks. Below is the CFW flash log file for comparison. CFW RM356 - FLASH LOG 25:07:2011  20:27 -> CMT blocks: 568, APE blocks: 0 25:07:2011  20:27 -> Erasing cmt... 25:07:2011  20:27 -> Processing C:\Program Files\Nokia\phoenix\products\RM-356\RM-356_52.0.101_prd.core.C0r... 25:07:2011  20:27 -> Erasing cmt zone 00040000 - 00082FFF ...  262144 -    536575 = 25:07:2011  20:27 -> Erasing cmt zone 00083400 - 003FFFFF ...  537600 -  4194303 25:07:2011  20:27 -> Erasing cmt zone 00400000 - 007FFFFF ...  4194304 -  8388607 25:07:2011  20:27 -> Erasing cmt zone 00800000 - 00D5FFFF ...  8388608 -  14024703 25:07:2011  20:27 -> Erasing cmt zone 00D60000 - 09E5FFFF ... 14024704 - 160068223 25:07:2011  20:27 -> Partition result: 0014 25:07:2011  20:27 -> Processing C:\Program Files\Nokia\phoenix\products\RM-356\RM-356_52.0.101_prd.rofs2.V01... 25:07:2011  20:27 -> Erasing cmt zone 02C60000 - 09D5FFFF ... 46530560 - 165019647  = 158489087 25:07:2011  20:27 -> Processing C:\Program Files\Nokia\phoenix\products\RM-356\RM-356_52.0.101_026_000_U01.uda.fpsx... 25:07:2011  20:27 -> Erasing cmt zone 09E60000 - 0F71FFFF ... 160068224 - 259129343  = 99061119 25:07:2011  20:27 -> Send CMT CFG... ----------------------------------------------------- The UDA erasing starts from 160068224 and ends at 259129343. It is because of the CMT blocks size mentioned in the .C00 file. If the 160068224 changed to a lesser value because of smaller ROFS2 naturally UDA size will increase.

Link to comment
Share on other sites

Probably they might not have come across the below details.

Check the RM-356  .C00 files for the below values

OFFSET = 2CDF19

58C85F02122B000300

00040000 00082FFF      262144    536575         

00083400 003FFFFF      537600    4194303

00400000 007FFFFF      4194304  8388607

00800000 00D5FFFF      8388608  14024703

00D60000 09E5FFFF      14024704  166068223

192F

Leave the first and last line .( Just for identifications )

The first and the second are hexa decimal addresses of teh CMT blocks.

The third and fourth are the sizes in bytes

This talks about CMT blocks.

Below is the CFW flash log file for comparison.

CFW RM356 - FLASH LOG

25:07:2011  20:27 -> CMT blocks: 568, APE blocks: 0

25:07:2011  20:27 -> Erasing cmt...

25:07:2011  20:27 -> Processing C:\Program Files\Nokia\phoenix\products\RM-356\RM-356_52.0.101_prd.core.C0r...

25:07:2011  20:27 -> Erasing cmt zone 00040000 - 00082FFF ...  262144 -    536575 =

25:07:2011  20:27 -> Erasing cmt zone 00083400 - 003FFFFF ...  537600 -  4194303

25:07:2011  20:27 -> Erasing cmt zone 00400000 - 007FFFFF ...  4194304 -  8388607

25:07:2011  20:27 -> Erasing cmt zone 00800000 - 00D5FFFF ...  8388608 -  14024703

25:07:2011  20:27 -> Erasing cmt zone 00D60000 - 09E5FFFF ... 14024704 - 160068223

25:07:2011  20:27 -> Partition result: 0014

25:07:2011  20:27 -> Processing C:\Program Files\Nokia\phoenix\products\RM-356\RM-356_52.0.101_prd.rofs2.V01...

25:07:2011  20:27 -> Erasing cmt zone 02C60000 - 09D5FFFF ... 46530560 - 165019647  = 158489087

25:07:2011  20:27 -> Processing C:\Program Files\Nokia\phoenix\products\RM-356\RM-356_52.0.101_026_000_U01.uda.fpsx...

25:07:2011  20:27 -> Erasing cmt zone 09E60000 - 0F71FFFF ... 160068224 - 259129343  = 99061119

25:07:2011  20:27 -> Send CMT CFG...

-----------------------------------------------------

The UDA erasing starts from 160068224 and ends at 259129343.

It is because of the CMT blocks size mentioned in the .C00 file.

If the 160068224 changed to a lesser value because of smaller ROFS2 naturally UDA size will increase.

welll welll quite interesting!!! so u wish to squeeze out more space!!!

Based on data u provided i would have obviously tried if i had my 5230!!

Nice!!! So U changed nything???got something????I am very excited :)

Link to comment
Share on other sites

The details i have given are less known because no one venture in to analysis of various files. I just collected the details and analysed and just sharing my thoughts. Unless i get more contributions from the fellow members this will also see a natural death. I am starting the threads for more interactions and the response was very poor. The CFW making thread only Nitesh and arya was got involved . I know every one was anxious to know the results but before that i wish to have some participation from the members. My question now is this Why it can not be possible?

Link to comment
Share on other sites

  • 1 month later...

hmmm to be honest you must understand that physically it's impossible to do this because of nature of Rom and nand flash memories. The speed of Rom compensates for less flexibility that is changing data. Approx 2000 times is total capacity and you won't want your phone to be killed guys, it's time to throw your phones gradually and get new one's that's all. I won't be interested in corrupting my Rom just for bit of free c memory. What do you guys do with this memory?

Link to comment
Share on other sites

Guest prayaas1998

it may sound stupid but if you can use rom as read/write partition then simply remove that write protection from rom Z and free everyone from this cooking hassle :(

isnt read only  rom physically different from read write rom ?

But see, the phone can access it. JAF can (technically not) access it. There can't be a physical difference.

Link to comment
Share on other sites

yup noicable but my understanding still is that we can partition whats on one media like a single hdd core rofs rofs2 rofs3 all go to one media (just my understanding) so we can repartition them but is uda written on same chip or physically there are two memory chips ? if there are 2 its impossible we cannot repartition whats not on same media

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...