Hacking WiiWare / VC, having trouble launching with USB Loader GX and neek2o

[NJBoss]

EDIT, FOR TL;DR THREAD. In an effort to save time for others with similar problem, I provide my tips and observations here:

Goal - launch WW / VC games with UGX. Some games are not working directly under UGX.

Misconception - NEEK is the "cure-all" for problematic games.

No, neek is not a universal solution, nor a miracle solution to get all games working. Again, I repeated it many times (in many threads) : Need DOES NOT HAVE 100% COMPATIBILITY !
Neek is not recommended, neek is slow and hard to setup and requires specific specs, neek is not supposed to be used as main console daily usage, and not all games are compatible

Misconception - all N64 VC games need NEEK to run. WRONG.
Quick tests proved that UGX can directly load N64 VC games.

My main problems that were preventing the successful launch of WW / VC games:

• Using outdated CIOS.
• Making assumptions.
• Trying too much at once.

Ultimately, my solution was a combination of factors.

• update my Wii's softmod.
• in UGX, dump realNAND to emuNAND. I had problems launching games when using a clean NAND generated by ModMii.
• Install only the games I want to play... not every single game that is available.
• Is a particular game causing too much trouble? Write it off as a bad dump and move on. If you really want to play it, keep trying and / or find a different dump.

For games that DO require NEEK to launch, UGX's autoboot NEEK feature is wonderful. A simple way to define NEEK as boot option without bouncing into the NEEK System Menu (which takes longer).

Disclaimer - of course, I have not extensively tested all games. Take that for what it's worth.

Hope that helps, many thanks to @Cyan Original post follows.

**************************************************************

Hello,

After successfully launching the Neek system menu from USB Loader GX, I am having trouble launching WW / VC titles. Of note, 101-in-1 Explosive Megamix successfully launches from USB Loader GX directly but will not launch from the Neek system menu. When I try to launch it, the grey Wii loading animation occurs then dumps me back to the system menu. My point? I must have something set incorrectly for Neek. Separate point - 1080 Snowboarding (VC title; as I understand these require the most attention to successfully launch) yields a black screen.

Basic details / rambling

• North American Wii console
• Soft-modded many years ago. I forgot the process I followed. ***
• BootMii is first screen after powering on the console. I use the physical buttons on the console to launch the Homebrew Channel
• From here, I launch USB Loader Gx.
• I have dumped the NAND to USB HDD. FAT32, one partition. I am sorry that I don't know how to determine cluster size. However, Wii games that are stored on this same HDD are launched successfully with USBLGX. Mario Kart, Wii Sports, etc. They are WBFS files.
• I can't remember which port the HDD is connected to. I THINK the inner USB port, NOT the port closest to the side of the Wii. The other port has a flash drive in it - there's some ROMs on there for other emulators. I think I tried reversing the ports but USBLGX then was not displaying the Wii titles stored on the HDD. Anyway...
• Neek2o didn't work for me via USBLGX at first. My success was to take the UNEEK + DI files generated by ModMii and load to the appropriate devices. Fine. In USBLGX settings, I had to make the custom path point to USB - the default was SD. I forget the exact directory. This part probably doesn't matter but whatever. ModMii is run under Windows XP via Parallels from MacOS.
• As an attempt to fix, in USBLGX settings, I enabled region path and Sneek video patch. It did not resolve the issue.

*** Because I am so rusty at this, there are clearly some relevant details I should share that I have missed. Your guidance on what info you need to help troubleshoot and your patience is MOST APPRECIATED!

 

[NJBoss]

I also have d2x cIOS installed. Not in front of the machine now so I can't say what version. Not sure if this was obvious info based on fact that:

• USBLGX launches
• I can successfully play WBFS rips of disc-based games
• I can successfully play some WW / VC games (I didn't already mention that Double Dragon works)

Anyway, any help is appreciated.

 

[Cyan]

not all games are working in neek (it's not a 100% compatibility environment).

what I understood :
you don't really have neek, but neek2o, right?

neek2o allows you to auto-boot a game right after neek system is launched, by patching the console to loads a game's titleID instead of the Menu's TitleID.
so, when you launch a game from USBLoaderGX with autoboot option it works, but if you launch neek system menu and manually launch the same game it doesn't work?


USBLoaderGX is doing nothing different and is not affecting neek at all.
it only write the TitleID to autoboot in a file for neek2o to read it later, and launches neek. that's all. it either write a titleid or not into a file. neek is always launched the same way.
I don't understand why it wouldn't be able to launch the game manually, but autobooting works.

 

[NJBoss]

Thank you @Cyan for responding!

what I understood :
you don't really have neek, but neek2o, right?

Correct.

neek2o allows you to auto-boot a game right after neek system is launched, by patching the console to loads a game's titleID instead of the Menu's TitleID.
so, when you launch a game from USBLoaderGX with autoboot option it works, but if you launch neek system menu and manually launch the same game it doesn't work?

What a shame. I had a detailed response written up then computer crashed. Too bad the forum's auto save function isn't more frequent. Oh well! Here's the brief version:
Using 100-in-1 Explosive Megamix as an example, I have game options for this set to default (Use Global is the setting on most configurable options, IOS 249). Neek is NOT selected as the game loader. The game successfully launches this way. If I boot to Neek System Menu, I see the game (and other installed WADs)) available as Channels. If I choose that game's channel and attempt to Start, gray animated Wii loading screen before getting kicked back to System Menu.
Before you ask "Why do you care to do this if the game launches from USBLGX without Neek turned on?" I am trying to figure out the right settings for games that WON'T launch under USBLGX. Assumption was to use Neek in those cases.

USBLoaderGX is doing nothing different and is not affecting neek at all.
it only write the TitleID to autoboot in a file for neek2o to read it later, and launches neek. that's all. it either write a titleid or not into a file. neek is always launched the same way.
I don't understand why it wouldn't be able to launch the game manually, but autobooting works.

I hope that I have clarified this with my remarks above. I am not in front of the system now but I would be glad to try any advice you have later when I have access to the machine. As I said, I soft modded many years ago. I am not opposed to "starting over" using a more current guide, if I must. Thank you very much!

 

[Cyan]

did you try the neek2o autoboot feature?
I guess it won't work either, like I explained it's neek2o which is actually launching the game, but just curious to see if it would work differently when using autoboot than when launching it from its channel manually.

in usbgx, go to the individual game option and enable neek. try to boot it, it should launch neek, and skip the system menu.


I don't know why neek is not working with this game.
is it the same region ?
sometime you need a new NAND matching the region of the game you want to launch because neek's "region free" option is not working perfectly.
usbgx let you manage multiple neek emuNAND at the same time, and auto-boot games using the correct region.
it's a little weird to setup but works like this :

make 3 NAND :
sd:/nands/pal/
sd:/nands/us/
sd:/nands/jp/
(kr too if you want korean games, but I don't know if they work with neek)

choose the "main" nand that you will see in the loader, and install ALL your games to it. for example ALL games from all region in "us" emuNAND.
install again european games in EU folder, and jp games in jp folder.
go to individual game setting and edit the nand path to match the region of the game.

the loader will display all games from US folder, but at launches will select the individually set path so neek will match the region of the game.




then, like you said, it's better to just use the working cIOS emuNAND mode instead of neek. it's faster and easier, and returns to loader at game exit.
I recommend to use neek only for games not working with cIOS mode. some games can seem to not work with cIOS, but they usually require a specific version/base. so it can be hard work to make an ultimate setup with all games working.

 

[NJBoss]

did you try the neek2o autoboot feature?
I guess it won't work either, like I explained it's neek2o which is actually launching the game, but just curious to see if it would work differently when using autoboot than when launching it from its channel manually.

That's part of the problem. I don't know HOW to enable that autoboot feature. Plus, I don't have a dedicated Channel for neek2o. Errr... I mean, if I go to Wii System Menu (not the neek version of this), I don't have a channel for neek2o there.

in usbgx, go to the individual game option and enable neek. try to boot it, it should launch neek, and skip the system menu.

I've tried this. Changing game loader to neek in the game settings, that is. Clarification:

• USBGX launched.
• Select a problematic WW or VC title.
• Adjust game settings for this game specifically.
• Change game loader to neek.
• When I choose to start the game, black screen. OH, I SHOULD HAVE MENTIONED EARLIER THAT THIS IS ACCOMPANIED BY FLASHING DISC DRIVE TRAY. I think. I gotta check that when I'm in front of the Wii.

I don't know why neek is not working with this game.
is it the same region ?
sometime you need a new NAND matching the region of the game you want to launch because neek's "region free" option is not working perfectly.
usbgx let you manage multiple neek emuNAND at the same time, and auto-boot games using the correct region.

I'm not sure how to determine the region of the problematic WADs. I have only US emuNAND. Used USBGX to dump my Wii's real nand. I would need to figure out a way to acquire EU and JP NANDs too.

then, like you said, it's better to just use the working cIOS emuNAND mode instead of neek. it's faster and easier, and returns to loader at game exit.

That is an entirely separate problem. Return to is set to USBGX but... no success when trying to use the pause screen / Wii Menu option. I even set that to Clear but still, no success. I MUST have installed something incorrectly for this to not even work. I had a channel for USBGX on the real Wii System Menu, an old one. Then I installed latest USBGX and a new channel by the same name was added to the System Menu. So, I used an app from Home-brew Launcher to delete the old channel. I don't know if this is relevant information but, figured I'd share.

I recommend to use neek only for games not working with cIOS mode. some games can seem to not work with cIOS, but they usually require a specific version/base. so it can be hard work to make an ultimate setup with all games working.

Yes, cIOS mode much preferred. Simple. Encountering these "problem" games (specifically WW / VC titles) is the purpose of this thread. Thank you for your help!

 

[tswntk]

That's part of the problem. I don't know HOW to enable that autoboot feature. Plus, I don't have a dedicated Channel for neek2o. Errr... I mean, if I go to Wii System Menu (not the neek version of this), I don't have a channel for neek2o there.

If you don't have the channel, then you probably haven't installed neek2o properly. I guess modmii have a guide for that (haven't need to touch that for ages). Simply making a nand dump is not enough for neek20 to work. Cyan would be better at that.

I'm not sure how to determine the region of the problematic WADs. I have only US emuNAND. Used USBGX to dump my Wii's real nand. I would need to figure out a way to acquire EU and JP NANDs too.

You can use showmiiwads, it can tell info about your wads.
Don't dump your own nand for neek, it contains cios which makes some games (though rare) not working. Use modmii to build clean nands

That is an entirely separate problem. Return to is set to USBGX but... no success when trying to use the pause screen / Wii Menu option. I even set that to Clear but still, no success. I MUST have installed something incorrectly for this to not even work. I had a channel for USBGX on the real Wii System Menu, an old one. Then I installed latest USBGX and a new channel by the same name was added to the System Menu. So, I used an app from Home-brew Launcher to delete the old channel. I don't know if this is relevant information but, figured I'd share.

You need the latest forwarder channel for USBLGX and point the "return to" setting to that forwarder channel. Download them from the official sourceforge page, not random websites. Again Cyan would be better at that.

 

[Cyan]

there's no channel required to launch neek or neek2o, USBLoaderGX is the one launching it.
if USBLoaderGX's "launch neek system menu" works, it should also work for the games with "neek" option.
if it doesn't boot, I guess it's because the game doesn't work with neek ? you said yourself, when inside neek that game doesn't work either. try with a working game.

The blinking LED means the Nand path is not found.
be sure to put the path in a double subfolder (seems to be a bug of neek2o)
sd:/nand/ <-- doesn't work well
sd:/nands/nand name/ <-- good

since 1271, I changed the default path (for new loader's install, or when reseting the settings) to sd:/nands/01/


the channel you should install is not on sysmenu, but on your emuNAND (use the wad manager in usbgx features menu). It allows you to exit neek2o automatically when exiting an auto-booted game by rebooting the console instead of loading neek's system menu.
to return to the loader after a reboot you need to do a special setup with priiloader or bootmii.

you don't know how to do the autoboot? you just did!
set "neek" in the individual game settings. that's all.


like said, to "return to" the loader when you exit a game (not from neek mode), you need to install the forwarder channel and go to usbloadergx settings, set that channel as "return to" option.
now when you choose "exit" from a game home screen, it'll load the forwarder instead of the system menu.

 

[NJBoss]

Thank you @tswntk and @Cyan for your help!

You can use showmiiwads, it can tell info about your wads.
Don't dump your own nand for neek, it contains cios which makes some games (though rare) not working. Use modmii to build clean nands

Good tip! Now must figure out how to do on Mac... The machine that hosts all my d... Not even worth explaining, NM.
That bit about the NAND dump though... Didn't realize that I should generate the NAND with ModMii. Sorry to go off topic - when I replace the emuNAND(s) with the new one(s) from ModMii, how will my game save files be affected? Ex. using USBGX, I have launched Mario Kart. I have made progress in the game. If I replace the emuNAND and attempt to play that game again, will my save file from before be there?

You need the latest forwarder channel for USBLGX and point the "return to" setting to that forwarder channel. Download them from the official sourceforge page, not random websites. Again Cyan would be better at that.

I have USB Loader GX-UNEO_Forwarder_5_1_AHBPROT.wad I had same with the word "fix" in the file name. Not sure what I did wrong when installing. I think Cyan addressed this below:

• install that as a channel to emuNAND, not real NAND

Should I use the one with "fix" in file name instead?

if USBLoaderGX's "launch neek system menu" works, it should also work for the games with "neek" option.
if it doesn't boot, I guess it's because the game doesn't work with neek ? you said yourself, when inside neek that game doesn't work either. try with a working game.

I apologize if I wasn't clear enough about this. I HAVE tried to do just that - a game that works under USBGX directly won't launch via Neek sys menu.
I am going to try to take a known working game (as described above) and set to autoboot neek.

The blinking LED means the Nand path is not found.
be sure to put the path in a double subfolder (seems to be a bug of neek2o)
sd:/nand/ <-- doesn't work well
sd:/nands/nand name/ <-- good

since 1271, I changed the default path (for new loader's install, or when reseting the settings) to sd:/nands/01/

AHHH!! So THAT'S what that means! I need to double check to see if / when I am still getting that flashing tray.
Anyway, FWIW, my emuNAND is now on USB HDD, not SD. And yes, it's following those same paths you describe. My real NAND was dumped to USB:/nands/01 That's NTSC / USA NAND in there. Before when I had no success, the emuNAND was on the SD card.

the channel you should install is not on sysmenu, but on your emuNAND (use the wad manager in usbgx features menu). It allows you to exit neek2o automatically when exiting an auto-booted game by rebooting the console instead of loading neek's system menu.

Yup. Got it now. Going to give it a shot. I want the same behavior though for exiting a game... launched with USBGX / cIOS... BACK TO USBGX. Pretty sure doing the exit function from the game's Home screen dumps me back to real NAND sys menu. Anyway, I'll try that forwarded advice mentioned above (install channel to emuNAND).

you don't know how to do the autoboot? you just did!
set "neek" in the individual game settings. that's all.

DERP, whoops!
I realize a lot of what I'm saying here portrays me as hopeless. I appreciate your help, I'll get there eventually!

 

[tswntk]

Good tip! Now must figure out how to do on Mac... The machine that hosts all my d... Not even worth explaining, NM.
That bit about the NAND dump though... Didn't realize that I should generate the NAND with ModMii. Sorry to go off topic - when I replace the emuNAND(s) with the new one(s) from ModMii, how will my game save files be affected? Ex. using USBGX, I have launched Mario Kart. I have made progress in the game. If I replace the emuNAND and attempt to play that game again, will my save file from before be there?

You will need a VM like wine to run windows app on Mac.,
neek is slow, so you should use it for games that are not compatible with real or cios emunands. And for that purpose, you should use clean nands to ensure best compatibility. The nands should be place inside subfolders like \nand\us,\nand\eu,\nand\01 etc. You can keep your old nand as is and run Mario Kart from that nand as is (especially if it is a cios emunand).
You can also use savegame manager gx to transfer saves among real nand, and different emunands, or you can copy directly the \nand\xx\title\00010000 folder to another nand (each subfolder inside the that folder is the data for an individual game but it maybe difficult for noobs to figure out which is which).

I have USB Loader GX-UNEO_Forwarder_5_1_AHBPROT.wad I had same with the word "fix" in the file name. Not sure what I did wrong when installing. I think Cyan addressed this below:

• install that as a channel to emuNAND, not real NAND

Should I use the one with "fix" in file name instead?

You need the fix version and install it to real nand for USBLGX to return to inside games running in real nand or cios emunand.
If you want to return to USBLGX from neek, that is impossible unless you use bootmii or priiloader as exiting neek will always reboot the console.
I guess you mixed up cios emunand and neek? neek is not designed to run homebrews inside it without modification and up till now, i guess USBLGX is not designed to run inside neek. USBLGX can launch neek but then neek will take over and neek is not designed to return to anything when exiting but reboots.
What Cyan (and I) means is the neek2o switch channel which allows you to switch between real nand and neek

AHHH!! So THAT'S what that means! I need to double check to see if / when I am still getting that flashing tray.
Anyway, FWIW, my emuNAND is now on USB HDD, not SD. And yes, it's following those same paths you describe. My real NAND was dumped to USB:/nands/01 That's NTSC / USA NAND in there. Before when I had no success, the emuNAND was on the SD card.

You will need different versions of neek/neek2o for SD and USB. sneek for SD and uneek for HDD

PS: maybe I myself am also mixing up neek and neek2o? I guess USBLGX is using nee2o for neek emulation and I have never really used neek but neek2o. Cyan comes to the rescue

 

[Cyan]

That bit about the NAND dump though... Didn't realize that I should generate the NAND with ModMii.

you don't "should"
you can either dump your own NAND, or generate a clean empty one (with modmii or other tools. modmii is just the easiest).

when I replace the emuNAND(s) with the new one(s) from ModMii, how will my game save files be affected?

if it's wii games, or WiiWare/VC on NAND, the savegames are read from internal memory.
if it's WiiWare/VC on emuNAND, then using a clean emuNAND means clean state, no savegame on emuNAND ! it's what clean means.


You seem to mix what NAND and EmuNAND are.
NAND is your console's system.
emuNAND is a copy of a wii system, located on external device (sd or usb), and WiiWare/VC game access "can" be redirected to that folder if you select to do it.
Wii games are NOT redirected to emuNAND. why would it do it? EmuNAND is used to install MORE than 48 channels at the same time, and break the 512MB limit.
Wii games are not installed to NAND, so there's no reason to use a bigger place to play them. emuNAND is not for Wii or gamecube games.

I have USB Loader GX-UNEO_Forwarder_5_1_AHBPROT.wad I had same with the word "fix" in the file name. Not sure what I did wrong when installing. I think Cyan addressed this below:
• install that as a channel to emuNAND, not real NAND
Should I use the one with "fix" in file name instead?

Don't!!
stop what you are thinking.

again, you clearly misunderstand and mix both NAND and EmuNAND purpose.

you need to understand what neek is, and that your console can either run its core (kernel) on the console itself (sysNAND), or the one on the SD/USB (emuNAND).
emu doesn't mean "emulated". it's a bad word choice.
it's a redirected NAND access. (redNAND)

re-read again your messages before mine, you talked about "neek channel" and I said you have to install it in emuNAND.
I never said you had to install USBLoaderGX forwarder channel on emuNAND.

the forwarder goes on sysNAND
the neek channel goes on emuNAND

DO NOT MIX the Wii forwarder and the vWii FIX forwarder !
DO NOT install the "fix" version on Wii. this is the vWii version !

it's not because it's called "fix" that it's better for everything or that it fix a bug on old version.
the fix is a fix for vWii.

I apologize if I wasn't clear enough about this. I HAVE tried to do just that - a game that works under USBGX directly won't launch via Neek sys menu.

and why are you using a complicated non working setup, if it works on an easier setup?
just launch the game without neek.
don't boot neek AT ALL.
why would you want neek in the first time?

You will need different versions of neek/neek2o for SD and USB. sneek for SD and uneek for HDD
PS: maybe I myself am also mixing up neek and neek2o? I guess USBLGX is using nee2o for neek emulation and I have never really used neek but neek2o. Cyan comes to the rescue

neek is the name of the program.
S means it redirect NAND calls to SD
U means it redirect NAND calles to USB
+di means it adds disc interface support (Disc channel is also redirected to external device, not only NAND)
2o means "version 2.0", it's an update of neek. it adds features such as wbfs support, subfolder to store the NAND dump into, autoboot and return to TitleIDs through arguments.
It also had an attempt at fixing support for 4k drives, but seems it failed (some users report it works, some it doesn't). That's probably a matter of real4k, 512e, etc. I think it's fixed on vWii neek2o, but it has more bugs and is not stable. unfortunately, there's no sources to compile the latest version for Wii.


if you use neek (not 2o), it will work fine but there are more restriction :
- the NAND dump need to be on root of the device, not in a subfolder.
- if you use +di (if di.bin file is present in /sneek/ folder), then you need at least one extracted game on your device or neek will not boot.
- if you launch a game by selecting it in USBGX, it'll not autoboot it. it'll just run the patched kernel and your console will reload into neek's sysmenu. you'll have to launch your game manually from there (or from the hidden menu if you have more than 48 channels).


if you use neek2o
- the loader can launch neek sysmenu (from the features menu) without autobooting a game
- the loader send the TitleID of the game to launch if you launch the game with "neek" emuNAND mode. and if present on emuNAND, it'll send "NK2O" titleID as "return to" argument on Wii, or "return to WiiU" titleID on vWii. you don't need to install Neek channel on vWii neek, there's already a channel to reboot the console provided by nintendo.



USBLoaderGX can support for Sneek and Uneek installed at the same time.
generate uneek files, put them on USB first partition
generate sneek files, put them on SD
based on where your emuNAND path is located, it'll load the correct kernel.bin from the same partition.


if you don't use USBLoaderGX to boot neek, but instead uses either bootmii@boot2 or bootmii@IOS (nswitch) you can't have both at the same time.
SD:/sneek/kernel.bin is ALWAYS booted first.

if you want USB, you need to put the USB version on SD too ! meaning you lose the Sneek version and only have Uneek on both SD and USB.
Sneek : bootmii (from boot2 or nswitch) -> sd:/bootmii/armboot.bin -> sd:/sneek/kernel.bin (sd version) -> uses files into sd:/sneek/ and read emuNAND on SD.
Uneek : bootmii (from boot2 or nswitch) -> sd:/bootmii/armboot.bin -> sd:/sneek/kernel.bin (usb version) -> uses files into usb:/sneek/ -> read emuNAND on USB.

 

[NJBoss]

Thank you friends! Will be back in a few days with better response.

Quick notes - generated clean NANDs in ModMij. Pointed UGX to location of new, clean NAND. Previously working WW title reports some corrupt system file message. My quick assessment - it worked before with my dumped real NAND with cIOS. Clean NAND not "hacked" so, probably the culprit.

Will follow all thoughts above on my next round of troubleshooting. Thank you!

 

[Cyan]

clean NAND does not need to be "hacked".
it needs to be initialized. it's missing a LOT of files used by the console.
Clean NAND are not meant to be used right away, as is.
clean NAND are specifically made for neek, and you need to launch neek at least once before installing anything to it in order to initialize the NAND (set the date/time, sync wiimote, generate a Mii, etc.). like if your console was new !
you can't install games and play them directly after generating a clean (empty) NAND. it's missing requires system files, and you'll get "corrupt system" message.


DO NOT try to use neek if you don't need to, or don't understand why you need it or how to use it!
why people are looking for problems when they can just use working setup instead?

dump your own NAND. use it for WiiWare/VC with cIOS mode. no neek required ! no time wasted by us to explain how to setup and use neek while you don't even need it. why learn something you don't need? If I take the bus I don't learn mechanics to repair cars...

 

[tswntk]

DO NOT try to use neek if you don't need to, or don't understand why you need it or how to use it!

This^
Neek is slow and complicated. Only use it for those rare games that are not compatible with cios loading. (That's why its best to be "clean")

You have used Modmii to create clean nands and probably installed neek2o? Does it come with a guide? if so, read it and read
https://gbatemp.net/threads/neek2o.313314/

 

[NJBoss]

*** NOTE - before reading below, I have not done new / extensive testing as of this writing.

Wii games are NOT redirected to emuNAND. why would it do it? EmuNAND is used to install MORE than 48 channels at the same time, and break the 512MB limit.
Wii games are not installed to NAND, so there's no reason to use a bigger place to play them. emuNAND is not for Wii or gamecube games.

OHHHHHHHHHHHHHHHHhhhhhhhhhhh.......! Well, that would explain how disc-based Wii games (as WBFS files in USBGX) have not given me any problems.

you need to understand what neek is, and that your console can either run its core (kernel) on the console itself (sysNAND), or the one on the SD/USB (emuNAND).
emu doesn't mean "emulated". it's a bad word choice.
it's a redirected NAND access. (redNAND)

OHHHHHHHHHHH...!

and why are you using a complicated non working setup, if it works on an easier setup?

I understand why this seems frustrating. But, to make my point again... I am referring to games that ARE NOT WORKING in the easy USBGX / cIOS environment! Hence, trying neek2o to launch those problem titles.
FWIW @tswntk I checked the problem WW title with ShowMiiWads and confirmed USA region flag. But please see my point at the top ***

if you want USB, you need to put the USB version on SD too ! meaning you lose the Sneek version and only have Uneek on both SD and USB.

I think that's what I've got! Both the USB HDD and SD have a sneek folder. Each contains kernel.bin and some other files. From ModMii, I did exactly what folder name instructed "COPY TO USB" and "COPY TO SD". The files in the "COPY TO SD" folder were NOT copied to the USB and vice versa. So, I think I didn't screw that part up.

You can also use savegame manager gx to transfer saves among real nand, and different emunands,

I will remember this as an option. But I think you've already cleared it up. I might not need it at all. Wii disc-based games via USBGX are saving to sysNAND. emuNAND saves are saving to their respective NAND folders. If I'm not going to be launching those games from a different NAND, is there even a reason to transfer save files around? Besides backing up data, of course.

clean NAND does not need to be "hacked".
it needs to be initialized. it's missing a LOT of files used by the console.
Clean NAND are not meant to be used right away, as is.
clean NAND are specifically made for neek, and you need to launch neek at least once before installing anything to it in order to initialize the NAND (set the date/time, sync wiimote, generate a Mii, etc.). like if your console was new !

OHHHHHHHhhhhh...!

dump your own NAND. use it for WiiWare/VC with cIOS mode. no neek required ! no time wasted by us to explain how to setup and use neek while you don't even need it. why learn something you don't need?

But... it DOESN'T work for certain WW / VC titles...
• In USGX, I will reassign the path from the clean NAND generated by ModMii to my dumped NAND.
• I will try to launch the problem WW / VC titles again.
I have done EXACTLY this already though. Not sure what I am missing in order to get those problem titles to launch? Maybe some more settings in USBGX (like the IOS choice) need to be adjusted? Please see my note at the top though ***

If I take the bus I don't learn mechanics to repair cars...

LMAO

You have used Modmii to create clean nands and probably installed neek2o? Does it come with a guide? if so, read it and read
https://gbatemp.net/threads/neek2o.313314/

I did the NAND generation from ModMii without the wizard / guide mode. I suppose I will be re-generating NANDs now... lol
The post you linked to is informative, thanks!

 

[tswntk]

I did the NAND generation from ModMii without the wizard / guide mode. I suppose I will be re-generating NANDs now... lol
The post you linked to is informative, thanks!

after you installed neek2o successfully, you should have neek2o switch channel on real nand's system menu. Run it to let the clean nand initialize, (may back screen for a few minutes, be patient), you will need to sync your Wiimote to the new nand and then you can install your WW games using ULGX or showmiiwads. Test your WW games from the neek's system menu to eliminate ULGX config problems or other complications.
If that still doesn't work, then your WW games many be bad. Tell us what games are you testing. IIRC, Cyan has a WW compatibility list somewhere.

 

[Cyan]

I'll tell almost the same thing.

he doesn't really need the neek channel on sysNAND, he only need a way to launch neek in order to initialize it.
either from bootmii@boot2
either from nswitch homebrew
either from nswitch channel (it's the neek channel, it's just a channel injected with nswitch homebrew)
either from USBLoaderGX "launch neek" option from the features menu.

like said, it should black screen few minutes, that's totally normal. it's generating missing files.

You said you want to use neek for games not working "normaly", but previously you said the contrary. you said launching from neek doesn't work while launching with standard method from the loader did.
Can you tell us which game you are trying to launch and fix which requires neek ? is it a channel or a disc based game?

setting up and using neek needs to follow proper steps in correct order.
wanting to burn steps is what makes neek complicated and seems hard to understand or make it work.
like trying to install games on uninitialized emuNAND, or trying to autoboot games from neek2o without testing if neek works first, etc.

neek is not that hard to use, setup or understand, but I always feel people burn steps and want to go directly to the end and expect it to work the way they think it works, instead of learning how it works and adapt its use around it.

 

[tswntk]

The only reason i recommend to init neek nand with nswitch channel is because its simple and if he doesn't have the channel, then he probably didn't installed neek2o properly.

I also wanted to take ULGX out of the way for the beginning to keep things simple. Although using ULGX is simple enough, it does add an extra layer of uncertainty (neek nand is not created properly and extra settings etc).

 

[Cyan]

I feel usbgx is easier because you don't need to install a channel, and you don't need to have SD files if you want Uneek, you can boot uneek directly from USB, unlike nswitch which requires SD files even for uneek.
but the result is the same. all boot method are mostly similar.
nswitch wii or bootmii loads armboot.bin which loads kernel.bin
nswitch vWii or usbgx (wii/vWii) loads kernel.bin directly

 

[NJBoss]

But... it DOESN'T work for certain WW / VC titles...
• In USGX, I will reassign the path from the clean NAND generated by ModMii to my dumped NAND.
• I will try to launch the problem WW / VC titles again.
I have done EXACTLY this already though. Not sure what I am missing in order to get those problem titles to launch? Maybe some more settings in USBGX (like the IOS choice) need to be adjusted?

I tried again last night.
• Redumped the sysNAND to emuNAND within UGX.
• Installed WADs to test with.
• These are now accessible on the UGX game selection screen. I have to set filter to show emuNAND channels.

*** You know, I think this might be where I'm going wrong. ***

Most settings in UGX are left as default. The iOS being used is 249.
The Wii games (disc-based) work fine. We've already established that.
The WW / VC games are spotty.

Tell us what games are you testing. IIRC, Cyan has a WW compatibility list somewhere.

You said you want to use neek for games not working "normaly", but previously you said the contrary. you said launching from neek doesn't work while launching with standard method from the loader did.
Can you tell us which game you are trying to launch and fix which requires neek ? is it a channel or a disc based game?

I want to use WHATEVER I NEED TO for games that are not working. My ASSUMPTION was that neek was the solution for games that aren't launching from UGX directly.

• 101-in-1 Explosive Megamix works directly launched from UGX.
• 2 Fast 4 Gnomz doesn't.

Why do I think this is the point where I'm going wrong? Maybe UGX's use of redNAND (the dump of my cIOS modded sysNAND) is the culprit. Based on this:

You seem to mix what NAND and EmuNAND are.
NAND is your console's system.
emuNAND is a copy of a wii system, located on external device (sd or usb), and WiiWare/VC game access "can" be redirected to that folder if you select to do it.
Wii games are NOT redirected to emuNAND. why would it do it? EmuNAND is used to install MORE than 48 channels at the same time, and break the 512MB limit.
Wii games are not installed to NAND, so there's no reason to use a bigger place to play them. emuNAND is not for Wii or gamecube games.

Thus, I need to figure out how to ask these titles, specifically, to redirect to redNAND / emuNAND. (The CLEAN one generated by ModMii). Am I on the right track now?
The problem (frustration / annoyance) is how to set that up to be far-reaching. Otherwise, this will involve setting each game's Game Settings manually to use emuNAND and point to the folder of the clean NAND. A bit annoying to do with the Wii remote but, if that's what it takes... I'm all ears on a better solution... assuming I got this figured out now.

after you installed neek2o successfully, you should have neek2o switch channel on real nand's system menu. Run it to let the clean nand initialize, (may back screen for a few minutes, be patient), you will need to sync your Wiimote to the new nand and then you can install your WW games using ULGX

That channel isn't on sysNAND System Menu. HOWEVER, I hadn't finished setting up (initializing) the clean NAND as of last testing. The Wii remote syncing was my point of failure. I couldn't remember how to sync the damn thing when the "Press A to continue" screen showed up. I was also drunk at the time WHOOPS. lol Back at it tonight.

he doesn't really need the neek channel on sysNAND, he only need a way to launch neek in order to initialize it.
either from bootmii@boot2
either from nswitch homebrew
either from nswitch channel (it's the neek channel, it's just a channel injected with nswitch homebrew)
either from USBLoaderGX "launch neek" option from the features menu.

Oh, sorry. Yes, the way I arrived at that screen was the launch NEEK from UGX Features menu.

feel usbgx is easier because you don't need to install a channel, and you don't need to have SD files if you want Uneek, you can boot uneek directly from USB, unlike nswitch which requires SD files even for uneek.

Again, I am confused by what ModMii has provided me with. Among many other things that were generated, the COPY TO SD folder includes:

• sneak folder. Containing kernel.bin

The COPY TO USB folder includes:

• nands folder. Containing pl_us folder, the cleanly generated NAND.
• SNEEK folder. Each time I make these experiments, I change the folder to lower case. Based on prior tip from Cyan in some other thread.
• This SNEEK folder contains dl.bin, font.bin, and kernel.bin

So, this begs the question... Do I need that sneek folder on the SD card or do I not?
Lastly, I generated these with System Menu 4.3 I am not in front of my Wii now so I can't confirm which sys menu sysNAND is using but... does the clean NAND sys menu version matter with respect to the sysNAND sys menu version?

Thank you!