Help - Search - Members - Calendar
Full Version: Offset Finding~!
SE-NSE Forums > SE Firmware > Newbie Forum
SnZ
Hello,

At first I am total newbie in patching nad want to find offset from patch.

As ex. I got:

CODE
;c510 SW-R1FA035
;Whitelist to blacklist
;(c) SiNgle
;(p) Xamid
;pAtChFiLe=/boot/phone_app.cxc
14F23806: 00D1 00D0


I opened phone_app.cxc with hex editor , and tryed searching offset 14F23806, but it says 'The file does not contain offset 14F23806.'

What I am doing wrong ;( ?

Please answer!
Jinx13
Minus by the base address or something lol.gif
SnZ
Right, but look :

14F23806 - 14000000 = F23806

I go to: F23806

PIC:



And where I can find 00D1 ?? I don't see this really. Please explain!

14F23806: 00D1 00D0

//EDIT--

I found, when I do base - 13FFEFFF (but why that, I searched forums google and doesn't seen sth like this)....
pakraider
The correct base offset is 13FFF000. So in the case of 14F23806, you need to look at offset F24806 in Winhex (142F23806 - 13FFF000 = F24806)
blacklizard
QUOTE (pakraider @ 2009-10-27 02:02) *
The correct base offset is 13FFF000. So in the case of 14F23806, you need to look at offset F24806 in Winhex (142F23806 - 13FFF000 = F24806)


WRONG
Boysie
QUOTE (blacklizard @ 2009-10-27 05:08) *
WRONG

Would be better to explain why he's wrong as well, so it helps the topic starter. smile.gif
blacklizard
QUOTE (Boysie @ 2009-10-27 08:26) *
Would be better to explain why he's wrong as well, so it helps the topic starter. smile.gif


There is only ONE base adress for each platform.

14000000 for DB3210
10000000 for DB3150

in db3210 you need to minus 0x1000 from base adress because 0x1000 is the cxc header size(im very sure on this)

and for db3150 cxc header size is 0x2000
SnZ
Umm I als think that is wrong because i compared clean phone_app.cxc and patched. And offset was 142F23806 - 13FFEFFF = F24807 or something like that.
Boysie
QUOTE (buggy @ 2009-10-27 07:33) *
Umm I als think that is wrong because i compared clean phone_app.cxc and patched. And offset was 142F23806 - 13FFEFFF = F24807 or something like that.

Blacklizard is a patch porter so I think he knows what he's talking about. wink.gif
blacklizard
QUOTE (buggy @ 2009-10-27 08:33) *
Umm I als think that is wrong because i compared clean phone_app.cxc and patched. And offset was 142F23806 - 13FFEFFF = F24807 or something like that.


I see you are trying to open .cxc file in WinHex. So you should minus 14000000, not 13FFF000

Only use 13FFF000 when using smelter

and oboviousy 13FFEFFF is wrong
SnZ
But why, when I 142F23806 - 14000000 = F23806 .... but ehn 1 was patched with ;c510 SW-R1FA035 ;Whitelist to blacklist , then it wasn't F23806 , that was F24807
Jinx13
The base address is different for different patches I think it depends on what base was used by the original porter smile.gif
SnZ
very weird wink.gif but thanks to all for fast answers.
Cheers
blacklizard
SnZ

You using what to patch your phone_app.cxc?
SnZ
QUOTE (blacklizard @ 2009-10-27 15:49) *
SnZ

You using what to patch your phone_app.cxc?


cxcpatcher (FAR plugin).
jock
Blacklizard is almost correct smile.gif

CXC RAW Format (Extracted from mbn file with readdb3150) = 0x14000000

CXC (Extracted from A2 Uploader) = 0x14000000 - 0x1000 = 0x13FFF000

DB3150 = 0x10000000
With a DB3150 cxc file you'll need some more work to find your base, browse down until you find following bytes:

18F09FE5 18F09FE5

they are at either 0x1000 or 0x2000 then lets say you find them at 0x1000 then do

0x10000000 - 0x1000 = 0xFFFF000


Regards
Jinx13
Thanks for the info Jock this can come in useful smile.gif
pakraider
thanks for the mature answer Jock. smile.gif
blacklizard
QUOTE (jock @ 2009-10-27 20:20) *
...
CXC RAW Format (Extracted from mbn file with readdb3150) = 0x14000000

CXC (Extracted from A2 Uploader) = 0x14000000 - 0x1000 = 0x13FFF000
...


One more info for DB3210, when using .cxc with smelter,

cxc from A2 uploader, loading base is 13FFF000

cxc from read3150, loading base is 13FFE000
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.