Jump to content

Recommended Posts

Posted

Is it possible to re partition the OFW core ?

Posted Image

OFW  size details

CORE  43.909

ROFS1  71.704

ROFS2  33.423

ROFS3  13.631

USER    93.061

Posted Image

CFW  size details

CORE  43.909

ROFS1  1.31

ROFS2  118.489

ROFS3  1.048

USER    93.061

The core size remains same in OFW and CFW.

1.Basics of core partitioning

OFW core size              =  110,674 Kb

OFW ROFS1 image size =    70,020 KB

OFW ROFS3  Size          =    1,258 Kb

OFW ROFS3 image size  =    1,240 Kb

CFW Size                        =  41,897 Kb

ROFS1 portion ( 70,034 Kb ) removed  from the core and  ROFS3 portion (1257 KB )  added to the core.

Calculation = 110674-70034+1257 = 41,897.

ROFS3 image was not added and ROFS3 full file is also not added.

A 1257 Kb size file only selected from ROFS3 SIZE OF 1258 kB.

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

Core file contains a partition table .

It defines the size of the files allocated to each sector.

The sectors details in Hex values is  below for the OFW Core files.

5401170E000300D3  8A010000  04000008  00006C00  00000000001C00000000000000000000000000 TABLE

5357424C00000000  00000000  00040000  00260000  000000000000000000000000 SWBL

4144410000000000  00000000  002A0000  00060000  000000000000000000000000 ADA

4B45595300000000  00000000  00300000  00040000    000000000000000000000000 KEYS

5226440000000000  00000000  00340000  8C070000  000000000000000000000000 R&D

5052494D41505000  00000000  00400000  00C00100  000000000000000000000000 PRIMAPP

524150334E414E44  00000000  00000200  60250100  000000000000000000401C08 RAPNAND

5041535542544F43  00000000  00F00300  00100000    000000000000000000301E08 PASUBTAC

50415055424B4559  53000000 00000400 525E1300 000000000000000000F08F08 PAPUBKEYS

534F532A55504441  50500000 0004FAFF 00080000 000000000000000000101C08 SOS*UPDAP

4E50430000000000  00000000 000CFAFF 00040000 000000000000000000201C08 NPC

4343430000000000  00000000 0010FAFF 00040000 000000000000000000301C08 CCC

4857430000000000 00000000 0000FCFF 00000200 000000000000000000000000 HWC

5355534431000000 00000000 0000FEFF 00000200 000000000000000000000000 SUSD1

5355534432000000 00000000 00003800 179D2D00 000000000000000000F08F08 SUSD2

534F532A454E4F00 00000000 00007800 00002600 000000000000000000002008 SOS*ENO    2.989335  2187264

534F532A44535030 00000000 00009E00 00003000 000000000000000000004808 SOS*DSPO  10.354688  3.145728

534F532A49534153 57000000 0000CE00 A830CC01 000000000000000000F08F08 SOS*ISASW 13.500416  30.159016 

 

534F532B434F5245 00000000 00009E02 BC1D4604  000000000000000000000000  SOS+CORE  43.909120  71.703996

534F532B524F4653 31000000 00001007 0000FE01  000000000000000000000000  SOS+ROFS1 118489088  33.423360

534F532B524F4653 32000000 00000E09 0000D000  000000000000000000000000  SOS+ROFS2 151912448  136.31488

534F532B524F4653 33000000 0000DE09 00008C05  000000000000000000000000  SOS+ROFS3 165543936  93.061120

534F532D55534552 00000000 0000840F 00001600  000000000000000000000000  SOS+USER  261750784      1441792

534F532D504D4D00 00000000 00009A0F 00000200  000000000000000000000000  SOS-PMM    261750784      1311072

534F532D43524153 48000000 FFFFFFFF FFFFFFFF FFFFFFFFFFFFFFFFFFFFFFFF  SOS-CRASH

THE BELOW DETAILS WILL BE EDITED TO PARTITIONED THE CORE

BASE      MAX SIZE

00009E02 BC1D4604  SOS+CORE    43.909120  71.703996

00001007 0000FE01  SOS+ROFS1  118489088  33.423360

00000E09 0000D000  SOS+ROFS2  151912448  136.31488

0000DE09 00008C05  SOS+ROFS3  165543936  93.061120

0000840F 00001600    SOS+USER  261750784      1441792

The principle is

rofs1  rf1Base  rf1Max

rofs2  rf2Base  rf2Max

rofs3  rf3Base  rf3Max

user  userBase  userMax

rf2Base = rf1Base + rf1Max

rf3Base = rf2Base + rf2Max

userBase = rf3Base + rf3Max

Posted Image

Attached core table and cfw table.

Open them in 010 editor and compare.

You will find 4 differences.

1. The table sector difference .( A , B , C)

2.SOS+CORE

3.SOS+ROFS1

4.SOS+ROFS2

Because original core was not partitioned.

Now it should be clear what to adjust and where.

2..Attached OFW core partition table and CFW partition table .

    This files can be compared in HEX editor  to know how the partition was effected .

Edited on 7th 1745 hrs.

411_.rar

412_.rar

  • Replies 56
  • Created
  • Last Reply

Top Posters In This Topic

Posted

Is it possible to re partition the OFW core ?

i think there is no need to repartition ofw core. . .we make cfw for ofw by jst modifying rofs2 and rofs3 files. . .core file is as it is frm the navifirm
Posted

I have changed the topic to make it more clear. How to make a CFW core from the OFW core. We can not use the  Navifirm ROFS2 and ROFS3 with the CFW core  . It too need to be modified to use with a CFW core.

Posted

i think there is no need to repartition ofw core. . .we make cfw for ofw by jst modifying rofs2 and rofs3 files. . .core file is as it is frm the navifirm

Well,repartioning iz not required though,The problem comes when we want to delete some app :P

We need to delete from rofs2 and rofs otherwize the leftover's r too much :)

Posted

I have changed the topic to make it more clear.

How to make a CFW core from the OFW core.

We can not use the  Navifirm ROFS2 and ROFS3 with the CFW core  .

It too need to be modified to use with a CFW core.

using the doctorly core editor, we can separate the rofs1,rofs2 and rofs3. . .though i never testd. .many said so.

And for core, wont d hex editing method work as u said before? Sos + rofs1 ,etc

Posted

Shifting of ROFS1 to ROFS2 will not do the magic. For example Let me shift the ROFS1 to ROFS2 to make ROFS2 as 100 MB. If we flash this 100 Mb  ROFS2 with OFW core the phone will brick.

Posted

Shifting of ROFS1 to ROFS2 will not do the magic.

For example

Let me shift the ROFS1 to ROFS2 to make ROFS2 as 100 MB.

If we flash this 100 Mb  ROFS2 with OFW core the phone will brick.

yeah, i jst said abt minimizing the c00 size

we actualy shud modify the c00 using hex editor to match wid our phone model. . .then only it wud work

Posted

yeah, i jst said abt minimizing the c00 size

we actualy shud modify the c00 using hex editor to match wid our phone model. . .then only it wud work

Nooo Last time i edited my OFW core!!!

I deleted some apps and more and reduced itz size to 94 Mb!!

It worked!!

The problem was I was not able to make a big rofs2 so couldnt add rofs and rofs2

Posted

WTf?? Both r the same dude from what I see :P

nope, it isnt

u r simply talking abt adding stufs to rof2 and then flashing wid it

u cant use the ofw c00 file wid cfw rofs file

and vizi is asking 4 repartitioning the core

Posted

@Arya What you have done is that you have edited ROFS1 size and flashed with OFW ROFS2 certainly it will work. My question was Using OFW .C00 file of 110 Mb and flash ROFS2 of 1100Mb ( Die idea) will brick. Just check the sizes of OFW and CFW you will understand.

Posted

nope, it isnt

u r simply talking abt adding stufs to rof2 and then flashing wid it

u cant use the ofw c00 file wid cfw rofs file

and vizi is asking 4 repartitioning the core

K I get it he wnts to know how to repartition the Nokia Cooker has the option to repartition I suppose :P

And the good thing is not working on my OS

Posted

@Arya

What you have done is that you have edited ROFS1 size and flashed with OFW ROFS2 certainly it will work.

My question was

Using OFW .C00 file of 110 Mb and flash ROFS2 of 1100Mb ( Die idea) will brick.

Just check the sizes of OFW and CFW you will understand.

K u can delete everything from the rofs but It must have a single file in rofs otherwise the phone will brick :P

But if i do tht and make a rofs2 then with rofs1 and rofs2 summed up then NFE says "plz dont flash":(

Posted

@Arya

What you have done is that you have edited ROFS1 size and flashed with OFW ROFS2 certainly it will work.

My question was

Using OFW .C00 file of 110 Mb and flash ROFS2 of 1100Mb ( Die idea) will brick.

Just check the sizes of OFW and CFW you will understand.

hmm. . .nt actualy

when we shift the contents of rofs1 (which is present inside C00) to rofs2. .naturally, the c00 file size wud decrease. . .to 40mb i suppose (as per d calculations frm the size chart u mentioned)

bt i dnt knw whethr the c00 file wud succesfuly flash or not. .i need to try it today

Posted

hmm. . .nt actualy

when we shift the contents of rofs1 (which is present inside C00) to rofs2. .naturally, the c00 file size wud decrease. . .to 40mb i suppose (as per d calculations frm the size chart u mentioned)

bt i dnt knw whethr the c00 file wud succesfuly flash or not. .i need to try it today

Dude it worked for me I deleted the annyoing leftovers of about,welcome and Maps :P it decreased to some extent,

Ithink it should work on further deletion

Posted

K u can delete everything from the rofs but It must have a single file in rofs otherwise the phone will brick :P

But if i do tht and make a rofs2 then with rofs1 and rofs2 summed up then NFE says "plz dont flash":(

Because the size of your ROFS2 is exceeding the size of ROFS2 given in the core .

Refer my first size details

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...