vizhigal Posted September 14, 2011 Report Posted September 14, 2011 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 ) Quote
Die2mrw007 Posted September 14, 2011 Report Posted September 14, 2011 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 Quote
Aryacooldude Posted September 14, 2011 Report Posted September 14, 2011 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 Quote
Aryacooldude Posted September 14, 2011 Report Posted September 14, 2011 even rem-dm said it is impossible Quote
Die2mrw007 Posted September 14, 2011 Report Posted September 14, 2011 Wondering if its really possible Quote
vizhigal Posted September 14, 2011 Author Report Posted September 14, 2011 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. Quote
Guest prayaas1998 Posted September 14, 2011 Report Posted September 14, 2011 Did you succeed in doing that? Quote
Aryacooldude Posted September 14, 2011 Report Posted September 14, 2011 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 Quote
vizhigal Posted September 14, 2011 Author Report Posted September 14, 2011 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? Quote
Aryacooldude Posted September 14, 2011 Report Posted September 14, 2011 Idk but itz quite tough bcoz itz fixed by nokia nd According to what I am thinking,exceeding it will lead to dead phone!!! Only Nokia can chage it bcoz they have quite awesome programmers and they know where to change and what to change Ofcourse we can try!!!!Who knows if we succeed Quote
Die2mrw007 Posted September 14, 2011 Report Posted September 14, 2011 Let us push up this project. I will study about this thoroughly Quote
Die2mrw007 Posted September 14, 2011 Report Posted September 14, 2011 I found that its really hectic to use 010 Editor...though its comfortable more than the hex editor I was having Quote
Aryacooldude Posted September 14, 2011 Report Posted September 14, 2011 I dont even have a pc to use 010 editor :'( Quote
farazejaz Posted November 4, 2011 Report Posted November 4, 2011 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 ? Quote
vds5344 Posted November 4, 2011 Report Posted November 4, 2011 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? Quote
Guest prayaas1998 Posted November 4, 2011 Report Posted November 4, 2011 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. Quote
farazejaz Posted November 4, 2011 Report Posted November 4, 2011 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 Quote
Guest prayaas1998 Posted November 4, 2011 Report Posted November 4, 2011 Nope.. It's the same chip AFAIK. That's why we can flash something to phone memory via uda but not to memory card (it's a different chip). Quote
Die2mrw007 Posted November 4, 2011 Report Posted November 4, 2011 Nope.. It's the same chip AFAIK. That's why we can flash something to phone memory via uda but not to memory card (it's a different chip). Its the same chip. . .the left out memory frm ROM is considered as phone memory. I have studied this frm an article written at gsmareana Quote
Guest prayaas1998 Posted November 5, 2011 Report Posted November 5, 2011 But how do we actually implement it? vizhigal's info is helpful though it needs to be worked upon a bit. Quote
vds5344 Posted November 5, 2011 Report Posted November 5, 2011 not the case with x6 i think because it has 300mb phone MEMORY Quote
Guest prayaas1998 Posted November 5, 2011 Report Posted November 5, 2011 Nope.. I guess X6 has more space in the ROM Chip. Contrary to that, we should be able to increase to ROFS2 size to 300 MB leaving 100 MB as phone memory.. Quote
vds5344 Posted November 5, 2011 Report Posted November 5, 2011 different for x6 8 gb and 16 gb to ? One is 400 and 8gb is 300 something Quote
Recommended Posts
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.