Hacking Newer Super Mario Bros. Wii is out now.

Treeki · Jun 10, 2013

There's two riivolution folders. The one in /apps/ contains the boot.elf and HBC info stuff. The one in the root contains the Newer XML (along with others, if you have any other mods installed) and a "config" folder with Riivolution settings.

Feel free to put it on the same card as your other stuff, Newer's files live solely in /NewerSMBW so as long as you have enough space that'll work fine.

the_randomizer · Jun 10, 2013

WiiUBricker said:
No they don't. It's just that the riivolution devs aren't interested in making RV work on the Wii U. You can complain to them.

Because complaining to the developers will make them more motivated. True story.

Treeki · Jun 10, 2013

FWIW, apparently dev versions of Riivolution are working on Wii U as from today. Someone testing it in the Newer dev channel got Newer to boot successfully. Hopefully it'll be released soon ....

The Frenchman · Jun 10, 2013

Great, my birthday is on the 12! what a nice gift this is!

Hanafuda · Jun 10, 2013

Treeki said:
There's two riivolution folders. The one in /apps/ contains the boot.elf and HBC info stuff. The one in the root contains the Newer XML (along with others, if you have any other mods installed) and a "config" folder with Riivolution settings.

Feel free to put it on the same card as your other stuff, Newer's files live solely in /NewerSMBW so as long as you have enough space that'll work fine.

Thanks. I hadn't finished d'ling the newer packet when I asked that, so I didn't know where the second riivolution folder was coming from. Got pretty obvious when I opened the newersmb zip and it was right there.

VashTS · Jun 10, 2013

well im going to give it a shot, not sure if my nsmbw disc will even work. its scratched beyond belief.

JoostinOnline · Jun 10, 2013

the_randomizer said:
Because complaining to the developers will make them more motivated. True story.

It does with newbie devs like me who just love the attention.

htoxad · Jun 10, 2013

I tried to load NSMB Wii and discovered my disc drive was shot.
Mod looks fun though.

the_randomizer · Jun 10, 2013

htoxad said:
I tried to load NSMB Wii and discovered my disc drive was shot.
Mod looks fun though.

Don't worry, it won't be disc only for long...

AshuraZro · Jun 10, 2013

Rydian said:
Hey AS, USB loaders dump discs as well.

Just so you know.

You know, FYI.

Fully aware of that. In fact I've done that myself just so you know, FYI, extra sass added to a fringe scenario for argument sake but it comes with an easy solution. Put the legit game you own in the DVD drive you used to make that backup. Problem solved. I did it and wouldn't you know that the game played perfectly. If you insist on using the USB loader, see the part where I suggest it is an inconvenience or alternatively figure out how to make it work instead of being grumpy that someone else won't do it for you.

damysteryman · Jun 10, 2013

Treeki said:
Did you apply the memory patches in the XML, and Loader.bin? All of that stuff is necessary, there's a reason why we added it

Yeah, adding loader.bin to the main.dol was the first thing I did actually. I added it to the end of the file, then added data for an extra Text section in the dol header (extra file offset, section size, memory offset).

Before building the iso with this, I tried loading the modified main.dol (with added loader.bin and xml patches applied) using original disc with a loader's Alt. Dol method without adding Newer files, just to see if Newer's "Error screen" embedded into the Loader.bin would be displayed, and sure enough, it did display

So that must mean that the Loader.bin is at least being run...

Then after trying to repack the iso with added Newer files, everything seemed to work, controller screeen, creating save screen, custom title screens (different one each time I load game), and file select all work fine, as does loading the "intro level" ("up to Mario to save world again" intro), but then going to world map hangs

Ray Lewis · Jun 10, 2013

"Meh", lol. What has happened to devs since 360 scene? Open, sharing, releases. Other than some withholding of information to sell xecuter devices. While this type of project seems cool I am too disgusted by 3ds story and likely Wii U also. Nsmb was good but I won't be messing with DRM for non-licensed content. Last few posts were about trying to get around DRM so I hardly consider this off topic.

RedCoreZero · Jun 10, 2013

I just found out about this!So you should know how glad I am that I didn't have to wait!

*dances*

Treeki · Jun 10, 2013

damysteryman said:
Yeah, adding loader.bin to the main.dol was the first thing I did actually. I added it to the end of the file, then added data for an extra Text section in the dol header (extra file offset, section size, memory offset).
[...]

Huh, I wouldn't have expected the loader to work after being moved (unless you fixed up the pointers and just didn't mention that in the post). Nevertheless, I'm 99% sure that the problem there is that when you expand the .dol, the .rel files are all moved up in memory and this breaks the addresses the Newer code is pointing to.

A bit of backstory here, not sure how much you've delved into this game, but there's four rel files (d_bases, d_profile, d_en_boss, d_enemies) which are all loaded when the game starts, during the wrist strap screen. These contain significant portions of the game code, and of course, we've got to modify it.

Patching the rel files themselves is a huge hassle, especially since they're compressed, so I chose to hook the boot process and load/apply code patches immediately after the rels are loaded (this is the Riiv XML memory patch that writes 0x80001800; that address is part of a list of function pointers).

We can do this because, thankfully, the four rels are all loaded at once, and never moved. The position is always the same for all runs of a specific game version- unless you resize the dol of course

I didn't bother implementing logic that searches for the rels in RAM, so the Newer hacks depend on them being at their default locations.

So yeah, that's my guess.

Try replacing something like, say... the unused Bluetooth error messages. There's a block of those big enough to fit the loader in. 803482C0 EU / 80347F80 US / 80347CE0 JP sounds like a good place

damysteryman · Jun 10, 2013

Ah, ok, that makes sense, I guess what I did would interfere with the location of the .rel files in memory.
All I did was tack the .bin to the end of the .dol file, and told it to be loaded at 0x80001800 in memoy... so I assume the loader.bin would have still been in the same location as it would normally be.

And yeah, I saw those files in the game dump, but did not look at them. And that makes sense, it does sound like a huge hassle.

And thanks for the help Treeki, I did not exactly expect that anyone would actually help give any info on this

EDIT:
UPDATE:
I moved the Loader.bin ove the top of those bluetooth error messages, edited the Loader.bin to account for the hardcoded offsets, and corrected the pointer to inject the loader from the new address.

And... same results as my original method... using Alt. Dol on original NSMBW disc loads the Loader after healthscreen, throwing Newer error screen, just as expected. Doing the same thing on my Newer .iso yeilds the same results as before, loads up fine, until trying to load world map.

Also, looks like I was incorrect about the title screen alternating, it just loads the same "default" jungle one (based on original title) every time...

So, looks like there is no difference in how I run the Loader.bin atm... I guess I would have had to packed the partition wrong?

But what I do not understand, is that, the titlescreen is actually supposed to alternate between different ones, right?

Treeki · Jun 10, 2013

The title screen changes depending on what world you last saved on.

I don't think expanding the .dol should have been an issue if you loaded stuff into 80001800-- I was thinking that you somehow expanded the existing sections, and the other method doesn't seem to have worked, so that's probably not it :x

What game version are you modifying?

btw, for anyone interested, Riivolution 1.05 with Wii U support is out now. Newer works on it.

damysteryman · Jun 10, 2013

Ah, ok, makes sense, oops

Maybe I should try copying my existing savegame to NAND and see what it shows me.

Yeah, I did not actually expand any existing sections, first time I added a new one, got it to load to 80001800, second time I manually patched it into the .dol over those bluetooth error strings.
Also, just now, I took the modified Loader.bin out of my modified .dol, and actually put it into the riivolution package, edited the xml, and launched it via riivolution just to see if my edits were correct, and Newer loaded fine with it... I guess I have to have screwed up the ISO building process, cannot think of any other reason...

I am modifying New Super Mario Bros. Wii PAL SMNP01 ver1.01 according to disc header.

Haha, just found it myself too, was about to post that myself, hit refresh, and found that you beat me to it

Thanks

EDIT: copied Newer save to Wii NAND, loaded up the ISO I have so far, and yeah, it loaded the correct title screen (world 5 one), so the issue must lie elsewhere.

GolfDude · Jun 10, 2013

NEWER MARIO CAN NOW BE PLAYED ON THE WiiU's Virtual Wii!

All you have to do is download the newest version of Riivolution at http://rvlution.net/wiki/Riivolution (version 1.0.5)

and simply overwrite the existing Riivolution folder in the sd card's app folder, with version 1.0.5, and you can now install the riivolution channel on your vWii, or access it via the HBC

markehmus · Jun 10, 2013

Finally, a reason to use my WiiU

Rydian · Jun 10, 2013

AshuraZro said:
Fully aware of that. In fact I've done that myself just so you know, FYI, extra sass added to a fringe scenario for argument sake but it comes with an easy solution. Put the legit game you own in the DVD drive you used to make that backup. Problem solved. I did it and wouldn't you know that the game played perfectly. If you insist on using the USB loader, see the part where I suggest it is an inconvenience or alternatively figure out how to make it work instead of being grumpy that someone else won't do it for you.

Your post stated that ISO = Piracy, so I was simply showing that's not true. I was responding to what was in your post, not your mind.

Hacking Newer Super Mario Bros. Wii is out now.

Well-Known Member

The Temp's official fox whisperer

Well-Known Member

Well-Known Member

Well-Known Member

Beat it, son

Certified Crash Test Dummy

Well-Known Member

The Temp's official fox whisperer

Belongs in a museum.

I am too busy IRL these days...

Banned!

Creativity is Power

Well-Known Member

I am too busy IRL these days...

Well-Known Member

I am too busy IRL these days...

Well-Known Member

Well-Known Member

Resident Furvert™

Similar threads

Popular threads in this forum