Hacking Extracting private header manually

[TheShadowRunner]

I need expert help to extract my private header manually.
I dumped a brand new Zelda ocarina with GW and now have the rom on my PC (536 870 912 bytes).

The .NET 4.0 layer of this temp PC is completely screwed and id like to extract the private header with a hexeditor (can't use Gateway ROM patcher)

Could anyone tell me the beginning and end offsets of the priv header and the expected file size of the dumped binary?

Thx in advance.

 

[tekwarfare]

I don't know the answer to your question, but why not reinstall .NET, or if it's completely hopeless then Windows itself? A lot of programs use the .NET framework so fix it.

 

[macearl]

I would also be interested in this, i would be interested in a native linux way to do this, i dont really like running the Gateway Tool through wine

 

[TheShadowRunner]

I don't know the answer to your question but

sadly.

 

[rfire90]

I can tell you that it starts at 0x00001200 in the ROM and the the .bins GW Rom Patcher produces are 11,766 bytes.

This post should also be helpful: https://gbatemp.net/threads/how-to-use-scene-dumps-with-gw-2-2-online.365829/page-4#post-4991676

And if I am correct you don't even need that big of a file that it produces. I think you can just edit a scene ROM and change the 2 rows explained above.

 

[cearp]

just use a hex editor compare your dump with a scene dump.
or use the offset the guy says above.

 

[TheShadowRunner]

I can tell you that it starts at 0x00001200 in the ROM and the the .bins GW Rom Patcher produces are 11,766 bytes.

This post should also be helpful: https://gbatemp.net/threads/how-to-use-scene-dumps-with-gw-2-2-online.365829/page-4#post-4991676

And if I am correct you don't even need that big of a file that it produces. I think you can just edit a scene ROM and change the 2 rows explained above.

Thanks. Are you sure its 11,766 bytes and not 11,776 bytes..?

Edit: if 11.776 is correct as I believe, the offsets are 1200 hex to 3FFF hex.

 

[rfire90]

Thanks. Are you sure its 11,766 bytes and not 11,776 bytes..?

Edit: if 11.776 is correct as I believe, the offsets are 1200 hex to 3FFF hex.

Oops you are right, it is 11,776, my bad!