Hacking Does anyone have an ips patch of the Wii U version of MMBN5?

[Bryon15]

Look at this:

http://forums.therockmanexezone.com/topic/8947437/1/

I was able to patch those megaman battle network games and then convert them to cia format and install them in my 3ds. They work great. Unfortunately they don't have battle network 5, because nintendo fixed the exploit that was used to obtain these in the newest Wii U system software, so it's no longer possible to do this yourself unless you have a Wii U on version 5.3.2 or lower. Does anyone here have it?

 

[Gadorach]

Should be possible with NNU-Patcher and some firmware spoofing.

 

[Bryon15]

I would if I could. But my Wii U is on 5.5.1

 

[VinsCool]

How much is it on eshop?

--------------------- MERGED ---------------------------

There is two versions of it too. I guess you would need both?

 

[Bryon15]

How much is it on eshop?

--------------------- MERGED ---------------------------

There is two versions of it too. I guess you would need both?

It's $8. And no I don't need both. I'd prefer the team colonel version. But it doesn't really matter.

 

[VinsCool]

It's $8. And no I don't need both. I'd prefer the team colonel version. But it doesn't really matter.

I'll get it, unless someone else do it before me.

Let's wait for tomowwor though.

 

[Bryon15]

I'll get it, unless someone else do it before me.

Let's wait for tomowwor though.

Wow, thanks a lot. I appreciate this.

 

[VinsCool]

I bought it.

I'll try to get the patch as soon as possible

 

[Bryon15]

I bought it.

I'll try to get the patch as soon as possible

Thank you very much.

 

[VinsCool]

Ok, I got the rom.

It seems like some change made it not working as is.

By reverting some of the bytes from the original GBA version, I got the rom to boot. but that's to be investigated. I have no idea if it works or not that way, I have little to no GBA hacking knowledge.
The four bytes at 0x6084 seem to be the key to making it boot


so, I'll just post the IPS patch out of the raw GBA rom dump from my WiiU.

https://mega.nz/#!ep9SQRQR!OT5qUhtaD8cG4v_qtTvfKOomKDU0R2FUQY0DBOSTcT4

Apply over "2032 - Megaman Battle Network 5 Team Colonel (U).gba"

Please note: It'll not work as is.

 

[Bryon15]

Awesome job man. Thank you. I'll try it out in a little bit.

 

[VinsCool]

Awesome job man. Thank you. I'll try it out in a little bit.

Please note that something is making the rom non working. It needs a bit of patching it seems. I hope that a gba hacker could tell what it is.

 

[Bryon15]

Please note that something is making the rom non working. It needs a bit of patching it seems. I hope that a gba hacker could tell what it is.

Oh I see. Hmm. Guess I could ask over on the gba board?

 

[VinsCool]

Oh I see. Hmm. Guess I could ask over on the gba board?

Sure thing. Someone with good gba knowledge might have an explanation

 

[Bryon15]

Sure thing. Someone with good gba knowledge might have an explanation

Did it.

https://gbatemp.net/threads/need-help-with-ips-patching-megaman-battle-network-5.419262/

Now we wait. Might take a while. The gba boards aren't as active as they used to be.

 

[Prof. 9]

I can probably answer this one.

Here's what the four bytes they changed at 6084 do:

08006084    F1C1F8BC    bl    81C7200h

This instruction hooks into a function that is called on every screen transition to do... something. If we follow it to its destination we find the following function that was added to the ROM at 1C7200:

081C7200    4650        mov    r0,r10
081C7202    213C        mov    r1,3Ch
081C7204    B430        push    r4,r5
081C7206    4C06        ldr    r4,=2002944h
081C7208    8824        ldrh    r4,[r4]
081C720A    2C00        cmp    r4,0h
081C720C    D003        beq    81C7216h
081C720E    2400        mov    r4,0h
081C7210    2500        mov    r5,0h
081C7212    E825        ????
081C7214    E002        b    81C721Ch
081C7216    2400        mov    r4,0h
081C7218    2501        mov    r5,1h
081C721A    E825        ????
081C721C    BC30        pop    r4,r5
081C721E    46F7        mov    r15,r14
081C7220    02002944

The first two lines just perform the same function as the instructions that were originally at 6084. After that, the game loads a halfword from 02002944 -- which appears to be the values for the current area and sub area -- and compares them to 0x0000, which happens to be the ACDC Town overworld map. It then loads 0 into r4 and either 0 or 1 into r5 depending on whether you are in the ACDC Town map, and executes the instruction encoded as 0xE825. However, this is actually an invalid CPU instruction (hence the ????) so the emulator doesn't know what to do with it and crashes.

It just so happens that the Virtual Console version of MMBN5 applies a motion blur/frame blending effect to the screen when you are in the ACDC Town map. I have no idea why they did that, my best guess would be because of the flickering helicopter shadow sprite that shows up near the end of the game. Virtual Console versions of games tend to patch out certain effects that could possibly be seizure inducing.

In any case, since 0xE825 is not a valid instruction I'd wager a guess that it actually tells the Virtual Console emulator how to apply the motion blur effect (with r4 and r5 being the parameters). Ideally I suppose the GBA emulator would replicate this effect or simply ignore the instruction, but either way we can simply patch it out.

So to make the game function correctly in conventional emulators, write two bytes 00 00 to 1C7212 as well as to 1C721A.

Now if you don't mind, I'll go ahead and add this patch to the topic that was linked in the first post. :)

 

[VinsCool]

I can probably answer this one.

Here's what the four bytes they changed at 6084 do:

08006084    F1C1F8BC    bl    81C7200h

This instruction hooks into a function that is called on every screen transition to do... something. If we follow it to its destination we find the following function that was added to the ROM at 1C7200:

081C7200    4650        mov    r0,r10
081C7202    213C        mov    r1,3Ch
081C7204    B430        push    r4,r5
081C7206    4C06        ldr    r4,=2002944h
081C7208    8824        ldrh    r4,[r4]
081C720A    2C00        cmp    r4,0h
081C720C    D003        beq    81C7216h
081C720E    2400        mov    r4,0h
081C7210    2500        mov    r5,0h
081C7212    E825        ????
081C7214    E002        b    81C721Ch
081C7216    2400        mov    r4,0h
081C7218    2501        mov    r5,1h
081C721A    E825        ????
081C721C    BC30        pop    r4,r5
081C721E    46F7        mov    r15,r14
081C7220    02002944

The first two lines just perform the same function as the instructions that were originally at 6084. After that, the game loads a halfword from 02002944 -- which appears to be the values for the current area and sub area -- and compares them to 0x0000, which happens to be the ACDC Town overworld map. It then loads 0 into r4 and either 0 or 1 into r5 depending on whether you are in the ACDC Town map, and executes the instruction encoded as 0xE825. However, this is actually an invalid CPU instruction (hence the ????) so the emulator doesn't know what to do with it and crashes.

It just so happens that the Virtual Console version of MMBN5 applies a motion blur/frame blending effect to the screen when you are in the ACDC Town map. I have no idea why they did that, my best guess would be because of the flickering helicopter shadow sprite that shows up near the end of the game. Virtual Console versions of games tend to patch out certain effects that could possibly be seizure inducing.

In any case, since 0xE825 is not a valid instruction I'd wager a guess that it actually tells the Virtual Console emulator how to apply the motion blur effect (with r4 and r5 being the parameters). Ideally I suppose the GBA emulator would replicate this effect or simply ignore the instruction, but either way we can simply patch it out.

So to make the game function correctly in conventional emulators, write two bytes 00 00 to 1C7212 as well as to 1C721A.

Now if you don't mind, I'll go ahead and add this patch to the topic that was linked in the first post.

Glad to know that I and @daxtsu weren't too far from your explanation

In my end, reverting those bytes to their gba release counterpart made the rom booting in my end, so I guess I was in the right path xD

Thank you for the explanation, this is greatly appreaciated

 

[daxtsu]

In any case, since 0xE825 is not a valid instruction I'd wager a guess that it actually tells the Virtual Console emulator how to apply the motion blur effect (with r4 and r5 being the parameters).

That's what I suspected, but I don't know ARM assembly, so I could only speculate as well. Thanks for clearing that up.

 

[Bryon15]

Fantastic. Thank you very much professor 9. I really appreciate this.

 

[VinsCool]

Bumping this thread, I made more patches

Megaman Battle Network 3 White: Apply over "1080 - Megaman Battle Network 3 White (U).gba"
Megaman Battle Network 4 Red Sun: Apply over "1554 - Megaman Battle Network 4 Red Sun (U).gba"
Megaman Battle Network 6 Gregar: Apply over "2427 - Megaman Battle Network 6 Cybeast Gregar (U).gba"
Megaman Battle Network 6 Falzar: Apply over "2436 - Megaman Battle Network 6 Cybeast Falzar (U).gba"


Also;
Megaman Battle Network 5 Team Protoman is still missing, but I'll get this one eventually too

Have fun!

@Prof. 9 @Hiccup @Bryon15 @Bjnido35