Homebrew make a custom Wii U forwarder to launch a homebrew app from wii u menu?

[nazoparadox]

Ok I've been spending my entire day trying to figure this out.

first off im not asking how to make a vwii forwader

everywhere i looked just lead to a dead end

trying to figure out how to make a custom Wii U forwarder (with tiramisu installed) to launch a wii u homebrew app from the Wii U menu (in my case each retroarch core (ex. snes9x_libretro) so my menu looks nice (yes i know its dumb))

tried Trudes "How to create a custom Wii U forwarder for ANY vWii Homebrew + gamepad support" but it seems its only for vwii wont work with .rpx

tried hbl2hbc but im already using it for usbloadergx, so installing it again would overwrite my setup.
I looked into "cloning the hbl2hbc" and having the .txt file redirect to wiiu/apps/(app i want to launch)/ .rpx but cant find anything about how to do that or if it would work

tried looking for another possible solution and found mikadubbz post "How to make .rpx homebrew forwarder channels?" and found tehtemp post about using the base of V10lator's Ship of Harkinian forwarder. I went ahead and edit the sd card path from the base but cant find anything else about compiling the base at all, just the same old "use docker to compile" and thats it, no instructions or anything else past that. (also im on windows 8 so i have to use docker toolbox if that makes a difference)

tried nuspacker to see if i could get it to launch a forwarder but another dead end, unable to find anything about using .rpx file with it

I cant find a definitive answer anywhere and i honestly don't know what else to do or what im doing wrong its driving me crazy, any help would be much appreciated

 

[Deleted member 571007]

Just to clarify, these 6 people you know that it happened to, occurred only because they have .elf homebrew forwarders in a Tiramisu envirorment?

One of them, actually yes. The others were because they were making their own apps which included IOSU exploits on top of Tiramisu, which would cause the same problem as using Haxchi on top of Tiramisu.

 

[MikaDubbz]

One of them, actually yes.

Then this is the only example I'm interested in. Can I know more about their situation, are we certain that the only supposed no-no they did with their Wii U was putting .elf forwarders in a Tiramisu environment? There isn't anything else they might have also led to a brick? How many .elf forwarders did they have and how often did they use them before it bricked? Cuz I must have 10 or 15 .elf forwarders and I use 2 of them like every day, going on years at this point (in Tiramisu and CBHC, most were grandfathered in from CBHC, but a couple were new installs to the Tiramisu environment).

 

[Deleted member 571007]

They were a generally basic user, but used a forwarder for basically every homebrew app they ever had- which I honestly never understood but whatever. Anyways, the thing is they didn't do anything else (that I know of at least) that would cause a brick, because they were the type of person to think that if they changed a game texture wrong that it would brick their console, so you can see how they would stray from the majority of system-related modifications.

I'm not sure at how many they had, but I know it was going on daily use for a few (around 6-ish) months, and at random when they turned on their console, it just did nothing. I assumed it was due to a dumb mistake or something so I referred them to UDPIH, and lo and behold- it didn't even load the USB Stack.

The problem is, while it may not happen super often for everyone it is COMPLETELY random hence the name Undefined Behavior. It's the result of things either clashing or interfering with each-others logic which won't always cause issues, but it once again is random. Take the Wii U pen-drive example, you know that they wear out fast, right? Two users could both use the exact same drive- User One could use it steady with daily use for 3 years, but User Two could have it in use for maybe a week and it would break. It's the same logic with Undefined Behavior.

Gonna use another system for another example, one which actually happened to me about a week ago. I was editing the processing logic of a device, and accidentally included a NULL terminator in a place where it shouldn't be. This wouldn't normally cause an issue, but it caused the logic of two different functions to clash. It ran fine for about 2 weeks before I noticed anything, but it almost at random started to procedurally corrupt the entire operating system to the point that it wasn't recoverable.

Even if it is a 1 in 1000 chance, it's still random. So you could by chance land that 1 in 1000 chance- which at least in my opinion? Isn't really that worth it. But like I said before, it's your choice. It's not my job to dictate what people do with their own property.

 

[MikaDubbz]

They were a generally basic user, but used a forwarder for basically every homebrew app they ever had- which I honestly never understood but whatever. Anyways, the thing is they didn't do anything else (that I know of at least) that would cause a brick, because they were the type of person to think that if they changed a game texture wrong that it would brick their console, so you can see how they would stray from the majority of system-related modifications.

I'm not sure at how many they had, but I know it was going on daily use for a few (around 6-ish) months, and at random when they turned on their console, it just did nothing. I assumed it was due to a dumb mistake or something so I referred them to UDPIH, and lo and behold- it didn't even load the USB Stack.

The problem is, while it may not happen super often for everyone it is COMPLETELY random hence the name Undefined Behavior. It's the result of things either clashing or interfering with each-others logic which won't always cause issues, but it once again is random. Take the Wii U pen-drive example, you know that they wear out fast, right? Two users could both use the exact same drive- User One could use it steady with daily use for 3 years, but User Two could have it in use for maybe a week and it would break. It's the same logic with Undefined Behavior.

Gonna use another system for another example, one which actually happened to me about a week ago. I was editing the processing logic of a device, and accidentally included a NULL terminator in a place where it shouldn't be. This wouldn't normally cause an issue, but it caused the logic of two different functions to clash. It ran fine for about 2 weeks before I noticed anything, but it almost at random started to procedurally corrupt the entire operating system to the point that it wasn't recoverable.

Even if it is a 1 in 1000 chance, it's still random, so you could by chance land that 1 in 1000 chance.

Ah, well a basic user alone worries me. I'd lend their example more credence if they were more experienced. Seems very possible that user error elsewhere could have been the cause for the brick. I'll keep your example in mind though, but it's not a great one for me, not one that makes me worry, especially considering how well my Wii U continues to hold up without issue, and there is no way I've missed that 1 in 1000 chance at this rate. I'll update if I ever do randomly brick, but at this point, I wouldn't hold your breath on that day ever coming.

 

[V10lator]

then it sure as hell should have added up substantially for me considering how many I have and how often I use them, yet nothing has gone remotely wrong with my Wii U

You still don't get what "random", "unpredictable" or "settings dependant" means... Really, talking to you about this topic is like talking to a wall - and trying to explain that wall why a wall can break even if this wall stands strong for 100 years now.

 

[nazoparadox]

It's actually wayyyy more common than you would initially think. To put it in perspective, even if nothing happens to you, people often use the HBC / HBL daily, and multiple times a day. Each time it runs its own IOSU exploits, and in addition to that, other applications that a user launches can screw up more in tandem. Put that on top of crashes, heap corruptions, data-stack errors, etc- You basically have a ton of small factors coming together to make what would by itself be a non-issue into something much more concerning.

You say it happens to no one, but I happen to know around 6 people that this happened to, as well as it happening to myself on my old console I used for dev-testing, and lemme tell you- you cannot fix it. It's like being cautious about not installing literally everything in existence to the NAND. Because yes, while the chances of something happening initially are low, it adds up pretty quickly, and in addition to that it can also be completely random; so a mint-condition console could get an IOSU or full-NAND Corruption within the day of modding it.

Just because it never happened to you, doesn't allow you the credibility to immediately dismiss the information, especially since it was being generally provided to ensure at least some sembelence of safety. But as stated earlier in the thread, what you do to your console is your choice.

ok going into this undefined behavior topic, this is only applying to the haxchi method of making unofficial forwarders? or also applies to all unofficial forwaders like nuspacker and the uwuwcvi aio (one i just discovered, pretty much the same as nuspacker compiling) even installing it to a external hard drive? I did a few test forwarders and installed through NAND (yes dumb i know) but now im installing all through my external hard drive. I should be good now be deleting all mods in nand and installing everything through external hard drive?

 

[MikaDubbz]

You still don't get what "random", "unpredictable" or "settings dependant" means... Really, talking to you about this topic is like talking to a wall - and trying to explain that wall why a wall can break even if this wall stands strong for 100 years now.

I said I'll caveat my explanation in the future that you believe such behavior can lead to a brick, not really sure what more you want from me.

 

[Deleted member 571007]

@nazoparadox the main problem was talking about using Haxchi or the Legacy HBC on top of Tiramisu because they have conflicting IOSU Exploits. Do it if you want, I just wouldn't recommend it.

Also, it's fine to have things on NAND, just don't excessively download / install large things to it or else you'll cause it to corrupt.

 

[V10lator]

I said I'll caveat my explanation in the future that you believe such behavior can lead to a brick

Might be language barrier but for me it looked like you called all lies. Got told that real live examples exist, still didn't believe. Got 8 examples from Korozin, still neglected them as "user error".
So yea, for me it seems you still act like this problem doesn't exist, refusing to listen to basic knowledge of computer science.

@nazoparadox What you did is fine, don't worry.

 

[Deleted member 571007]

@V10lator You speak German, right? If so, a language barrier is completely understandable. Put simply what they said was that they would take what you said into mind, and possibly relay it to others. But they're also not going to be too concerned about it in their own case.

Hopefully that helped at least a bit.

 

[MikaDubbz]

Might be language barrier but for me it looked like you called all lies. Got told that real live examples exist, still didn't believe. Got 8 examples from Korozin, still neglected them as "user error".
So yea, for me it seems you still act like this problem doesn't exist, refusing to listen to basic knowledge of computer science.

@nazoparadox What you did is fine, don't worry.

I'm not saying lies, I'm saying examples aren't really here of bricks, and the one we might have is a second hand account of someone who is a basic user. I've said I will continue to recommend the Haxchi method for .elf forwarders, but I will also mention that you believe this might lead to bricks when I do. I feel like that's all completely fair.

 

[nazoparadox]

Might be language barrier but for me it looked like you called all lies. Got told that real live examples exist, still didn't believe. Got 8 examples from Korozin, still neglected them as "user error".
So yea, for me it seems you still act like this problem doesn't exist, refusing to listen to basic knowledge of computer science.

@nazoparadox What you did is fine, don't worry.

ah ok awesome, i'll continue to use the uwuvci aio forwarder method since its more easier for me.

 

[Bidu]

Hello

WiiU2HBC MOD (Wiiflow)
Tested on Tiramisu (latest version)​

I'm struggling to make a forwarder for the Wii U from Wiiflow (hbl2hbc)
Failed to create a forwarder that reads sd:/wiiu/hbl2hbc/hblhbc.elf and starts Wiiflow
What I managed to do was a Forwarder Mod WiiU 2 HBC
Where I changed the meta and made an installation file
I used the .elf Wiiflow file which doesn't need hbl2hbc.txt

The problem is that there is no way to install the official WiiU 2 HBC (hbl2hbc) and the Mod I made at the same time.

The solution I found to use hbl2hbc was through Wii U HBL, where I just changed the folder name to hbl2vWii and kept the official files, booting from sd:/hbl2hbc.txt normally.

With Aroma all this is useless, but it's there for anyone who wants to try it.

Thanks

 

[loggedtxt]

.

 

[chris2009]

i got one here

Post automatically merged: Sep 8, 2024

i got one here