Daily Mobile Forum
20 April 2014, 05:20 *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Read the FORUM RULES - Ignoring the rules will end up with a ban so do NOT ask for registrations keys or share warez links / cracked applications. You have been warned!
 
   Home   Help Search Login Register  
Pages: 1 ... 8 9 10 11 12 [13]   Go Down
  Print  
Author Topic: The Nokia Firmware File-Format  (Read 24244 times)
0 Members and 2 Guests are viewing this topic.
writz
Forum Addicted
***
Thanks: 61
Offline Offline

Location:


Posts: 284



Activity
0%

NOPE! NOPE! NOPE!


« Reply #180 on: 24 April 2012, 13:09 »

if you want to know the exact meaning of these fields and their purpose you have to take the readimage sources and look there...

About iAtt,
I used only the Directory signature as 0x10 and all the other signatures will be extracted as files.
iAttExtra, Mostly I found it to be 0xFF so I did not considered about it in my lib, but i believe that N8 Rofs Extra Attribute is contained by this field.
And, I did not used the iSubDir in TRofsDir which is working smoothly!
I'm not wikipedia, I don't remember all the possible values for all the possible fields Cheesy when I need them, I take the sources and look there.

LOL... Grin
Just forget it... don't waste your time

Forgot about "Genstubs.exe"... Cheesy..What was it?? Grin Cheesy
I don't study the ROFS/ROFX differences since long time, I don't remember the details about the offset differences.
If I remember well, NC rebuilds a ROFX like it was a ROFS and eventually patches the iFileAddress fields and the signature.

Actually I was looking for the ROFX Repack...and found out that there was a rofxname or something like that in the oby file syntax..I am still unsure about that...NC's process of repack gave me some idea of of repacking the rofx files...Thanx Wink
Congratulations for your FirmwareExplorer project and it would be better if you open a new thread for it Smiley


Thanx! Smiley But I think i should not open a new thread for this project but complete my open-src classlib and then open a new thread here... Cool
Logged


writz
Forum Addicted
***
Thanks: 61
Offline Offline

Location:


Posts: 284



Activity
0%

NOPE! NOPE! NOPE!


« Reply #181 on: 25 April 2012, 19:59 »

@Il.Socio,
Have you ever tried building a rofs from your own??
I am trying to build the ClassLib to support viewing of Rofs without Extracting them and also Editing..
So I need your answer...
Logged
Il.Socio
DailyMobile Developer
Hero Member
****
Thanks: 551
Offline Offline

Posts: 634



Activity
1%

http://www.guardian-mobile.com/


WWW
« Reply #182 on: 26 April 2012, 11:35 »

No I never tried.
the rofsbuild command does the job quite well, so imho, it doesn't worth the effort.
Logged
writz
Forum Addicted
***
Thanks: 61
Offline Offline

Location:


Posts: 284



Activity
0%

NOPE! NOPE! NOPE!


« Reply #183 on: 26 April 2012, 14:24 »

No I never tried.
the rofsbuild command does the job quite well, so imho, it doesn't worth the effort.



But I will code it! Wink
Logged
mr_gourav2000
DailyMobile Contributor
Forum Master
****
Thanks: 1187
Offline Offline

Current Phone:
Xolo Q500

Posts: 4541



Activity
0%

Hit thanks for ME.


« Reply #184 on: 30 April 2012, 12:55 »

my one question-
when i open core in hexeditor and search ROFS then i see-
ROFS1
ROFS2
ROFS3
ROFS4
ROFS5
ROFS6

We have rofs1/2/3 but what mean rofs4/5/6 and what there purpose?

And if it is possible to use that then what is there partition size?
Logged


writz
Forum Addicted
***
Thanks: 61
Offline Offline

Location:


Posts: 284



Activity
0%

NOPE! NOPE! NOPE!


« Reply #185 on: 30 April 2012, 14:05 »

my one question-
when i open core in hexeditor and search ROFS then i see-
ROFS1
ROFS2
ROFS3
ROFS4
ROFS5
ROFS6

We have rofs1/2/3 but what mean rofs4/5/6 and what there purpose?

And if it is possible to use that then what is there partition size?


I think they are additional slots for additional rofs...
Maybe reserved by nokia for future use...
but, IMO, as all rofs will be transferred to z: the total partition size ie, ROFS1+ROFS2+ROFS3+ROFS4+ROFS5+ROFS6 will be the z: drive size [In most fw it is ROFS1+ROFS2+ROFS3 as ROFS4/5/6 are not used and no partition entry is there in the partition table]

BTW, Congrats on your 300'th thanks....
Logged
mr_gourav2000
DailyMobile Contributor
Forum Master
****
Thanks: 1187
Offline Offline

Current Phone:
Xolo Q500

Posts: 4541



Activity
0%

Hit thanks for ME.


« Reply #186 on: 30 April 2012, 19:27 »

I think they are additional slots for additional rofs...
Maybe reserved by nokia for future use...
but, IMO, as all rofs will be transferred to z: the total partition size ie, ROFS1+ROFS2+ROFS3+ROFS4+ROFS5+ROFS6 will be the z: drive size [In most fw it is ROFS1+ROFS2+ROFS3 as ROFS4/5/6 are not used and no partition entry is there in the partition table]

BTW, Congrats on your 300'th thanks....

and where i found partition table in core when i open in hexeditor?
Thanks for reply
+1 for your hard work and nice topic.
Logged
Il.Socio
DailyMobile Developer
Hero Member
****
Thanks: 551
Offline Offline

Posts: 634



Activity
1%

http://www.guardian-mobile.com/


WWW
« Reply #187 on: 30 April 2012, 21:10 »

and where i found partition table in core when i open in hexeditor?

Look here:
http://forum.dailymobile.net/index.php?topic=55242.msg732086#msg732086
Logged
mr_gourav2000
DailyMobile Contributor
Forum Master
****
Thanks: 1187
Offline Offline

Current Phone:
Xolo Q500

Posts: 4541



Activity
0%

Hit thanks for ME.


« Reply #188 on: 02 May 2012, 03:45 »


and what about romdump?

pc vs mobile.
Logged
kamy_wfa
Member
*
Thanks: 0
Offline Offline

Posts: 8



Activity
0%


« Reply #189 on: 15 September 2012, 13:39 »

@Socio

please help me explain those data blocks below (RM-697_21.0.003_prd.core.C00),

5D 01 27 2D 91 6F 75 21 7F 32081248B15C38DFC8E81B1803F26F41444100000000000000000000 03 00 66 42 00000400 000A0800 0F
(content...)
5D 01 27 2D 8E 30 9B 54 DA 1ADDE27C2A035D63AACACDCB6C003B41444100000000000000000000 03 00 01 44  00000400  000A0800 0A
(content...)

as i know the content (size of 400H) will be written into flash at address 000A0800H, one of the two data blocks will be selected to write to flashmemory,

1. could you please explain the principle  for this selection ?
2. if we make a dump file from the phone, say "we will get the content of 400H at the address 000A0800" how can we rebuild or infer the 2 data blocks including contents and headers as original ?

BRs

kamy_wfa
Logged


writz
Forum Addicted
***
Thanks: 61
Offline Offline

Location:


Posts: 284



Activity
0%

NOPE! NOPE! NOPE!


« Reply #190 on: 23 February 2013, 18:48 »

@Il.Socio

I want to know about that special  "Extra Attribute" of N8 Rofs[i guess its one of those "Protected Rofs"]...

Could you explain this??
Logged
MrKenkadze27
DailyMobile Developer
Hero Member
****
Thanks: 260
Offline Offline

Current Phone:
Nokia N95 8GB

Location:
Tbilisi, Georgia

Like KazySoft on Facebook
Add Me on Facebook
Follow Me on Twitter @MrKenkadze27

KazySoft Projects

Feeling Nice?


Posts: 955



Activity
43%

Otaku and Proud :) Development on Hold :/


WWW
« Reply #191 on: 05 July 2013, 16:40 »

it's confuseing how these work...
Logged
Pages: 1 ... 8 9 10 11 12 [13]   Go Up
  Print  
 
Jump to:  







Daily Mobile - Daily iPhone Blog - Contact us - Forum Rules - © Copyright MAS Media Inc. | Privacy
Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC