Hacking How do I compile everything that's needed for apps to work with UStealth?

[wiimanofthenorth]

I've been talking to a few friends online, and we'd really like for some old homebrew to be updated. I'm asking of course for Wii apps to be updated for vWii use.

Over the mist of time, and most coders going on to try and program for the Wii U, or even leaving the scene behind. I'd like to know what is I needed to recompile homebrew stuff that came out on the Wii to work on a Wii U with an UStealth enabled HDD? I'm sure the info in hidden in lots of old threads, but since there doesn't seem to be a tut, and far too many threads to be reading from scratch. I it would be nice to have some pointers.

I know of Maxtrernal's updated libfat library. https://gbatemp.net/threads/ustealth-wii-u-format-disk-nag-workaround.352786/

Apart from that though, what is really needed?

Which compiler would be best to use, apart from the source code for apps, and the updated libfat library, is there anything else I'd need?

I haven't done any real coding before. So I just need pointing in the right direction, so I can sit and recompile a load of homebrew, I'd like to see working with on the Wii U, while a "hidden" HDD is being used.

It's mostly emulators, my friends and I would like to be updated.

Thank you for any help!

 

[Kafluke]

I've been talking to a few friends online, and we'd really like for some old homebrew to be updated.

Over the mist of time, and most coders going on to try and program for the Wii U, or even leaving the scene behind - I'd like to know what is I needed to recompile homebrew stuff that came out on the Wii to work on a Wii U with an UStealth enabled HDD?

I know of Maxtrernal's updated libfat library. https://gbatemp.net/threads/ustealth-wii-u-format-disk-nag-workaround.352786/

Apart from that though, what is really needed? I haven't done any real coding before. So I just need pointing in the right direction, so I can sit and recompile a load of homebrew, I'd like to see working with on the Wii U, while a "hidden" HDD is being used.

It's mostly emulators, my friends and I would like to be updated.

Thank you for any help!

USB hdd is not supported on wii u homebrew right now. Only SD

Ustealth is done with a PC and it's just to avoid the nag. No Wii U homebrew will work right now on external HD

 

[wiimanofthenorth]

USB hdd is not supported on wii u homebrew right now. Only SD

Ustealth is done with a PC and it's just to avoid the nag. No Wii U homebrew will work right now on external HD

Yeah, I didn't make myself clear at first. This is of course for Wii homebrew to be used under vWii. Though, I've no idea why else you'd want to hide a drive from the Wii U?

 

[Kafluke]

Yeah, I didn't make myself clear at first. This is of course for Wii homebrew to be used under vWii. Though, I've no idea why else you'd want to hide a drive from the Wii U?

Good point.

 

[wiimanofthenorth]

I'm still looking for help on this...?

 

[Deleted User]

Hmmmm this is a good thread. Would compiling the homebrew be as easy as putting the files in a folder and running a .bat file (like injecting Sm4sh textures in a .nut file). I have been wondering how to compile C games into a playable homebrew game. Because I have some that I can compile. Just need to know how.

 

[wiimanofthenorth]

Can anybody help with this at all?

 

[cjizzle]

Man, by far I'm no expert at this but I see what you are trying to do and it sounds pretty cool. Years ago I recompiled a bunch of apps for use with hbc when the new motion plus controllers came out. You need to install devkitppc and libogc if I recall correctly. Tuts I believe are on wiibrew. Once you read up on it and put the correct files in the correct places, compiling is simple as can be (that's why I don't remember how exactly I did it..it was a "set up once and done" kind of thing). I just selected the source folder of the app I was recompiling, clicked a few buttons and that was it.

Anyways, the apps you want to recompile obviously would have to be open source. And the fix for ustealth would have to be a change in the source code of each individual app. Iirc, I remember seeing something about that in one of the usb loader source pages...I think it was GX or wiiflow... It seems like it was a relatively simple change, but it's been so long ago I can't remember nor have the time to go back and start fishing for it at current moment. Another way may be to look at the change logs of different apps that have been recompiled for ustealth and get your hands on a pre and post change source folder and see what specifically was changed.

Sorry can't help more, and I apologize for being a complete novice at this, but I saw no one had responded with much so figured might as well throw in the little I do know about it...

 

[Cyan]

There's an official thread about UStealth, and it contains multiple "do it yourself" tutorial (look at the end of the first post).
There are two methods :

the easiest is editing the sources responsible to the partition table check (some homebrew don't even check it, so there's no fix needed, it already works).
Once you find the sources with the partition table check, it should be something like "if(signature != 55AA) Then don't continue"
you need to add "55AB" as possible signature too "if (signature != 55AA && signature != 55AB) then don't continue"


The second method might be harder if the homebrew depend on LibFAT itself to check the partition table signature. in that case, you'll have to edit the libFAT and recompile it, then replace the library inside libogc libraries folder.
but if you look in UStealth thread, I'm pretty sure the recompiled libFAT is already done and provided to make your own homebrew compatible with UStealth signature.
So, the second method could be even easier than the first, just replace a file, don't edit sources, and recompile.
the provided libFAT is probably old (<v10) but it works too.

 

[OriginalHamster]

nvm, some recompiled apps are on my sig

 

[wiimanofthenorth]

...

Sorry can't help more, and I apologize for being a complete novice at this, but I saw no one had responded with much so figured might as well throw in the little I do know about it...

No, no, you've taught me stuff that I had no clue about. With your help, I can actually start in the right direction. Thank you

There's an official thread about UStealth, and it contains multiple "do it yourself" tutorial (look at the end of the first post).
...

I fully understand that to you, that the end of the first post explains everything, because you know already how and what is needed to compile.
Sadly, I don't. So yes, it explains you need to drop this and that, and edit that, but sadly, it doesn't say a thing about devkitppc. (Which cjizzle has now pointed me in the right direction it seems.)

As stated in my first post, I've no clue which compiler was needed.

Thank you for the reply though!

nvm, some recompiled apps are on my sig

Why the nvm? Unless one falls across your posts, and bothers to read them, it's not like it's screaming Wii U Stealth apps. Just as, I posted about this back in April, and you've not replied before. So, I'll assume it was because you never saw my post, rather than couldn't be bothered to reply.

Why not make a nice post, mentioning everything in your sig? (And fix you dead links?) So one can search and find them in the forums?

Of everyone who's posted, you could have helped me out the most. But tell me to nvm?

Just because you've got a few things, doesn't mean that their aren't other things I'd like to work with UStealth.

 

[Cyan]

you need devkitpro, libogc and devkitPPC (both are installed automatically when installing devkitpro).
But some homebrew might have more dependencies and libraries required to compile them.
a lot of homebrew are using the same libraries "ported" to wii.
These ported libraries are located in portlib folder inside devkitpro, but that folder doesn't exists and is not created by the installer.

You can find some "ready to use" packs.
For example, this one :
https://sourceforge.net/projects/usbloadergx/files/Libraries/
download the one which is 16MB, and extract it in your devkitpro folder. it contains libogc and the portlib used with DevkitPPC r27. It should work with r28 too but I haven't tested yet.

you should have something like that:
c:/devkitpro/devkitPPC/
c:/devkitpro/devkitARM/
c:/devkitpro/libogc/
c:/devkitpro/portlibs/

Most homebrew should be able to compile now.
there will be some who will require additional libraries (like WiiMC). if you encounter such homebrew who can't be compiled, it will be harder to find all the requirement.


After you have all these devkit installed, browse to your homebrew folder and open a command line windows.
Type "make" and it will compile.
If you have a multi-core CPU, you can specify how many core to use and it will speed up the compilation time :
"make -j4" will use quadcore.

 

[OriginalHamster]

Why the nvm? Unless one falls across your posts, and bothers to read them, it's not like it's screaming Wii U Stealth apps. Just as, I posted about this back in April, and you've not replied before. So, I'll assume it was because you never saw my post, rather than couldn't be bothered to reply.

Why not make a nice post, mentioning everything in your sig? (And fix you dead links?) So one can search and find them in the forums?

Of everyone who's posted, you could have helped me out the most. But tell me to nvm?

Just because you've got a few things, doesn't mean that their aren't other things I'd like to work with UStealth.

Because cyan already answer you, all that you need is in the UStealth thread. Also I won't bother trying to help someone that make a big deal over nothing.

 

[Cyan]

Well, even to me he responded like if I didn't understood his question. But I still chose to reply after his answer and added more information about compiling, putting his reply aside. I hope this time it's what he expected.

It wasn't the reply he expected, saying "at least cjizzle told me", but why would I say the same thing that had already been told to you ? I added information on the procedure and what you had to do (replace 55AA to 55AB)

My reply wasn't an attack to say "You shouldn't ask because it's already explained in the first post" but an additional information that the first post had some examples you could use to learn how to do it and I explained what the method consisted of (replacing the signature).


wiimanofthenorth : Your question wasn't very clear. You asked what you needed to recompile to add Ustealth to homebrew. So I replied to your question the way I understood it. You asked what compiler you needed, and like you said, cjizzle told you.
If you need help installing SDK environment and compiling homebrew from scratch, then ask about that first.
Be sure you can compile the clean homebrew (without ustealth) and that it launches correctly. Then once you know how to do that you can move to editing the sources and adding Ustealth compatibility.

And if someone edit his post, it's not an attack to you. It doesn't mean he doesn't want to help you!
it could be a bad suggestion and he removed it, it could be because he posted in the wrong thread, etc.
don't take things personally. We are all here to help each others.

 

[wiimanofthenorth]

First off, there may be a little bit of misunderstanding in translation of cultural habits. And it's not just me, but @OriginalHamster's post with the "nvm", comes across to the English ear as, *Middle finger*, "I can do it, you can't, and here they are, HA!". There's no mention of, "Oh, the people before me, beat me to it." I'm sorry, but that's just the way it reads to me and many other native English speakers from the UK. A sentence that starts with nvw, is very often seen as being rude or being sharp with someone. The editing of a post, had nothing to do with it. Quite frankly, I hadn't even noticed the post had been edited.

@Cyan, Thank you for being as helpful as you have been. I'm sorry for misunderstanding the way you were trying to pass on your knowledge. And thank you for even more informative posts.

Hopefully, we can all ignore any misunderstandings that have arisen.

 

[Cyan]

Thank you.

If you need more help, let us know what you did so far and where you have issues.