ROM Hack Trouble running custom .code

[JustPingo]

On the edge of my seat, care to explain?

Don't be hyped, that's why we didn't want to talk about it in the first place.
We're trying really hard to make HANS working, but if it ends up not working we will use our plan B we began before even knowing about HANS. Dirty pointer injections and stuff.

 

[MasterLel]

Dirty pointer injections and stuff.

Would this work in userland ?

 

[Mrrraou]

Would this work in userland ?

Of course, that's the main goal. However, the plan B would only be 10.1 and less.

 

[MasterLel]

Okay, my firmware is 10.2 so...

 

[Mrrraou]

Okay, my firmware is 10.2 so...

Golden rule of hacking: Never update

 

[MasterLel]

Yeah yeah I know, but it's too late now

 

[Mrrraou]

Yeah yeah I know, but it's too late now

But if you're lucky, you'll have it (I hope that you are)

 

[DatHax0r]

I'm on 10.1 on my main 3ds I use, phew

 

[noatpad]

Okay, so lemme see if I got this right. You guys are attempting to use HANS (or your plan B) to edit the eShop's code to allow the installation of any kind of CIA on >9.2 systems...

Woah, you guys are amazing to have progress so far.

 

[JustPingo]

Interesting fact: in ExHeaders, segment sizes are stored with little endian. That's why we had so much trouble with it.

 

[shutterbug2000]

Interesting fact: in ExHeaders, segment sizes are stored with little endian. That's why we had so much trouble with it.

Out of curiosity, what are the segment sizes?

 

[Mrrraou]

Out of curiosity, what are the segment sizes?

They are variable for each application/game. They represent the sizes of the .text, .rodata and .data in the .code located in the exefs.

 

[shutterbug2000]

They are variable for each application/game. They represent the sizes of the .text, .rodata and .data in the .code located in the exefs.

Ik that, but what are they for eshop?

 

[JustPingo]

base: 0x100000
.text: 0x297000
.rodata: 0x26000
.data: 0x16000
.bss: 0x62000
in bytes

 

[DatHax0r]

So, if I were to modify Eshop code now, would I need to make sure that the exheader was present in my id.code or is this so we know the bounds when modifying it??

Edit: Or both??

 

[Mrrraou]

So, if I were to modify Eshop code now, would I need to make sure that the exheader was present in my id.code or is this so we know the bounds when modifying it??

Edit: Or both??

The exheader is not in the .code file, neither it is in the romfs or the exefs.

 

[DatHax0r]

Sorry worded that question wrong, I mean is this required to be accessible by hans somewhere or is this so we know where the bounds are so if we run custom code it has to stick to those sizes?

Offtopic: Mrrraou your profile picture is awesome

 

[Mrrraou]

Sorry worded that question wrong, I mean is this required to be accessible by hans somewhere or is this so we know where the bounds are so if we run custom code it has to stick to those sizes?

Offtopic: Mrrraou your profile picture is awesome

We can't access nor patch the exheader, but it's useful to know the sections size and their bounds located in the .code file, since we can't really guess these. shinyquagsire23 said that it would be a requirement to run custom .code files.

By the way, thanks.

 

[DatHax0r]

We can't access nor patch the exheader, but it's useful to know the sections size and their bounds located in the .code file, since we can't really guess these. shinyquagsire23 said that it would be a requirement to run custom .code files.

Right, so this is implying that base is 0x0 to 0x100000?

 

[Mrrraou]

Right, so this is implying that base is 0x0 to 0x100000?

Actually, the base is not useful in anyway for the .code file, but I think that it is the location for it inside the exefs. I can't confirm that though, but we don't use it at all.
.text starts at 0x0.