Hacking WAD Scholar Needed... Online to Offline

[lowbred]

I made a forwarder for UNEEK using CustomizeMii. The base wad is Wii U Transfer Tool (Channel) and new dol from the OG neek2o NK2O_1.wad. Initially I was using a 4.1U NAND with Dolphin and when I tested the new wad it worked as expected. Next, installed it on real Wii (4.3U) via USB Loader GX EMUNAND WAD Manager and booted up UNEEK. UNEEK boots fine, the channel opens, I click 'Start' and a "An internet connection is required..." pop-up pop-ups. That sucks... After unpacking the wad... /00000000.app/banner.bin... banner.bin is the culprit. Injecting this banner.bin into a known working forwarder produces the same result. I went a little deeper 'benzin .brlan to. xmlan' and 'benzin .brlyt to .xmlyt' but found no reference to an internet connection. I'm no programmer but would really like to know if I'm on the road to nowhere. Is it possible to remove this pop-up with out scripting/building a new dol?

 

[Cyan]

please explain what you want to achieve first.
Because if you install any WAD using USBLoaderGX, then the WAD is installed on emuNAND.
launching Uneek(which is an emunand) from emuNAND is an endless loop.

You want to go to uneek from sysNAND? or want to launch the installed channels located on emuNAND?
There are already existing "neek" channels forwarder to install on emuNAND, which are used to exit neek to sysNAND, or launch neek from sysNAND. but you can't launch emuNAND from EmuNAND, what's the point??

You first need to already be in a neek environment to be able to see/use that channel, which is therefore useless. no need to boot uneek if you already are in uneek.
Maybe I don't understand what you explained by "UNEEK Boots fine, the channel opens", I click start".

because if you are still in USBLoaderGX interface, then "UNEEK Boots fine" probably refer to you clicking on the interface? before you "click start", then the channel is NOT booting. it's just a visual of the animated banner inside the channel.

If you are already in Uneek sysMenu interface, what's the point in launching another instance of Uneek from a channel? neekception.

Then, if you want to install a channel on Wii, why use a WiiU base wad and tool ?


finally, if what you want is to actually go into uneek from USBLoaderGX interface, why make a channel to launch neek, when usbloadergx does it automatically and silently by launching a game?

so maybe your question about the banner is legit, but I don't understand the reason you did all the steps before you found that internet issue. what do you want to achieve? learn about banners, or make a working channel? to what purpose?

 

[lowbred]

I'm in the UNEEK sysMenu interface booted from USB Loader GX > Features > Boot Sneek... My understanding the original neek2o NK2O_1.wad boots into UNEEK from real NAND and reboots the system from the UNEEK sysMenu (EMUNAND). That's how it's working for me. So, the "forwarder" I made to boot to UNEEK from real system menu works both ways, with this same wad I can reboot to the real system menu from the UNEEK sysMenu. The one in question uses the Wii U Transfer Tool.wad a totally different base wad for strictly UI reasons. I thought this wad was an original Wii wad, I downloaded it from a trusted source and it was included in the original Wii wad section. Maybe it's not... I can install it to the EMUNAND fine... IDK?
What I'd like to achieve is to use the Wii U Transfer Tool wad as a base to reboot the system from the UNEEK sysMenu. I hope I explained myself better. I really like the way it looks

 

[Cyan]

Ah, ok.

What you want is have the animated banner "Wii Transfer tool" channel inside your nSwitch channel, both on sysNAND and Neek?
There are therefore two option :
1. use WTT as base, and replace the dol.
2. use Nswitch as base, and replace the banner.

Personally, I would go with the second option, as it already contains the proper channel's TitleID to properly exit back to sysNAND when exiting a game.
On Wii it'll look fine.
On WiiU the issue will be that you'll have 2 identical channels on your sysmenu (you can delete the real WTT from emuNAND and keep only the nswitch one), but on sysNAND I don't recommend deleting system channels.


The first option will (should) work but on vWii you'll replace the official system channel with a patched dol (which is what's the WUP installer does) (is that the correct name? replacing Mii channel's app with hackmii launcher)
On Wii that's fine, you'll just add a new channel on sysmenu.



What I understand you did:

The "neek" channel is actually a homebrew (Nswitch) which detects whether you already are in neek environment or not.

If you are on sysNAND, it reboots the console with patched kernel (neek).
if you are on neek, it reboots the console (going back to sysNAND).


What I understand is that you made a new wad, and installed it using USBLoaderGX's emuNAND manager. it means the channel is installed on your emuNAND, and not sysNAND.

If you installed the wad using USBGX only to get that channel installed and available when you are in neek environment, in order to "exit" neek, then that's good ! that's how you need to use that (exit neek) channel.
If you installed the wad using USBGX and try to launch it from USBGX interface in order to boot into neek, that's NOT where you should install it ! that channel should be installed on sysNAND, usbgx has the ability to list channels from sysNAND too and nswitch will detect sysNAND and rebot into neek.

if you launch the channel by listing emuNAND channels from USBGX, it'll only create issues.
because USBGX will first set the console in "emuNAND", then launch the channel (nswitch) and you'll be in "emuNAND" mode when nswitch checks if you are on sysNAND or not....if you are on emuNAND, it will detects and interpret that you already are on neek (while you are not) and will try to reboot the console to return to sysNAND.
I'm not sure this is the expected result.


If your network issue is from neek, then I don't know. it's strange that the banner animation would try to check internet (eve though it's possible, as Vote channel or weather channel did).
But what I remember is that the network had issues on Neek. some games (all?) network don't work on neek. I tried only "Uno" card game, but it never worked, even if the SYSCONF and network was from the same console/network/setup.
I guess if the banner checks if the network is init, it'll fail before launching the app.

 

[lowbred]

Oh my goodness... Option 2... Reverse the process..? It worked! I feel a little du... du,du,du... dumb. That's why us newbs need you Cyan. I love how when you help us out you come at it from every angle. Very detailed but easy to understand. What I wanted to accomplish was making two new "neek" channels, one for the sysNAND and one for the emuNAND. One different from the other, two different banners/icons/sound. I do not have a vWii or a Wii-U, only a couple of original Wiis. Now, if anyone else comes across the same problem they will get a heads-up from your detailed response. Cool! I'm very grateful for your help. Love the way they both turned out. Thank you! P.S. I started the process about two weeks ago updating my soft-mods (from 2012) which lead me to your two threads/tutorials on the SNEEK/UNEEK process' which taught me everything I needed to know. Also, grateful for that. Thanks again!