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

[Cyan]

if you followed what I told repeatedly, the sneek folder on SD is needed only if you choose to launch neek without using USBloaderGX.
you also need the armboot.bin in sd:/bootmii/ folder
bootmii (launch from boot2 or from nswitch homebrew, or nswitch channel) loads armboot.bin, which loads sd:/sneek/kernel.bin which contains the path to where the other files are located. (hint : on usb:/sneek/)

on the contrary, if you use USBLoaderGX, then it directly loads the kernel.bin from the correct partition.
if you use Uneek, it loads usb:/sneek/kernel.bin

well, I feel like I repeating myself. just read what I said the past few posts!



SysNAND or emuNAND menu version don't matter at all. (look, I'm still using 3.2E !)
cIOS don't matter for neek (they are never used), that's the main purpose of neek don't use cIOS at all !

SysNAND relation to emuNAND content is also irelevant, the purpose of neek is to trick the console into NOT seeing it's not using the real internal memory content, but a redirected one instead. it doesn't care what the real NAND contains, it's not seen at all, and acts as if it never been there. you could have a bricked, or deleted Wii memory for all you cared, and neek would still work by just accessing "internal file system" from external device instead of internal chipset.




sd:/bootmii/armboot.bin
sd:/sneek/kernel.bin

usb:/sneek/kernel.bin
usb:/sneek/ DO NOT PLACE di.bin FILE HERE !!! DO NOT KEEP IT !
usb:/sneek/font.bin

usb:/nands/pl_us/


check and verify ALL the path I just gave you.
go to usbgx, set "usb1:/nands/pl_us/" as "emuNAND channel folder" in your custom path menu.
go to features menu and select "launch neek"
waiiiiiiiit few minutes on the black screen, as long as it doesn't flash led quickly it means it's working. (it could flash led slowly, it means it's working too)
you'll then be granted to the initialize console : wiimote sync (red button on wiimote, red button on console!), date, time, nickname, Mii, etc.
then, the (clean, new) system menu will appear. you are now in an NTSC-U neek environment until you shutdown the console, or (if pre-installed) launch the neek channel located on neek's system menu to reboot the console.

from here : DO NOT TRY ANYTHING. just confirm that launching neek worked. that's all. don't install games, don't change settings, don't try di.bin, etc.
I want to do things steps by steps with proper reports after each step.


something you should remember : NEEK DOES NOT HAVE 100% COMPATIBILITY !
games are still NOT WORKING on neek. don't expect all games to work !
if you want a game to work, install it to real NAND, it'll be soooo much easier

 

[codyjo]

Why don't you just install the WAD's that aren't working to the system menu.... Like, why the huge fuckaround???

 

[NJBoss]

*** Read the following if you're bored:
I almost DON'T want to tell you about my latest trial on this. Because the testing was done before your latest advice, @Cyan That being said...
• Successfully assigned emuNAND path to clean US NAND generated by ModMii; on the USB HDD.
• Using UGX Features, launch Neek System Menu.
• There was NOT an extended period of black screen at this point.
• Prompted to press A to continue. Sync'd Wii remote and off we go.
• Set date, time... TV aspect... I dont remember anything about the Mii setting. Anyway... still no long black screen.
• Neek System Menu is launched! The Disc Channel is there and two other channels too. Can't remember which... maybe post loader and Neek2o ?
• Here's where things went awry, as usual. And particularly because, AGAIN, I didn't have your latest response available yet.
• Installed some WADs.
• Bounced into Launch Neek System Menu from UGX Features.
• Attempt to launch game from channel and... black screen. I let it go 10 minutes, nothing.
• Reboot Wii.
• UGX, game settings set to global configuration of UGX.
• The emuNAND is already assigned to the path of the clean NAND
• Attempt to launch game and... corrupt system error message. Clearly, the system files weren't generated.

You may read more relevant response now. **************************************


First, thank you for all your help. I realize this is frustrating; I appreciate your time and assistance.

if you followed what I told repeatedly, the sneek folder on SD is needed only if you choose to launch neek without using USBloaderGX.

I don't see a reason to boot neek outside of UGX so, I will REMOVE the sneek folder from SD.

SysNAND relation to emuNAND content is also irelevant

Got it, thanks.

sd:/bootmii/armboot.bin
sd:/sneek/kernel.bin

usb:/sneek/kernel.bin
usb:/sneek/ DO NOT PLACE di.bin FILE HERE !!! DO NOT KEEP IT !
usb:/sneek/font.bin

usb:/nands/pl_us/

Regarding sd:/bootmii/armboot.bin ...
ModMii has generated a folder named "bootmiineek" It contains the arm boot.bin file
Currently, I turn the power to console on and am presented with the BootMii screen. When I change the name of this folder to "bootmii", will that affect my current power on behavior... in a way that we don't want it to?

Regarding sd:/sneek/kernel.bin ...
I thought I was deleting this folder from SD altogether since I will only be launching Neek via UGX.

I will delete di.bin from usb:/sneek/ folder

go to usbgx, set "usb1:/nands/pl_us/" as "emuNAND channel folder" in your custom path menu.
go to features menu and select "launch neek"
waiiiiiiiit few minutes on the black screen, as long as it doesn't flash led quickly it means it's working. (it could flash led slowly, it means it's working too)

Stellar advice re: the disc tray light.
I feel compelled to mention that...
• the USB HDD is connected to the INNER USB port on rear of Wii. A USB flash drive is in the OUTER port (the port closest to the edge)
• In this configuration, I have successfully launched Wii disc-based games from UGX. And some WW / VC titles (100-in-1, Double Dragon, Double Dragon 2)
• UGX is told to use both USB ports.
• So what's my point? Whenever I go to custom paths, cycling between USB1 and USB2 shows exactly the same files. In other words, the USB flash drive's data is not being shown when I browse the paths for USB 1 and USB 2. I DO NOT CARE ABOUT THE USB FLASH DRIVE DATA. What I'm asking is...
• Should I connect the USB HDD to the outer port and follow your above steps? Is the outer port USB 1 / is it absolutely necessary to connect the USB HDD to that port?

from here : DO NOT TRY ANYTHING. just confirm that launching neek worked. that's all. don't install games, don't change settings, don't try di.bin, etc.
I want to do things steps by steps with proper reports after each step.

Now we're talking. Got it.
Thanks!

 

[NJBoss]

Update - UGX Features Boot Neek System Menu is working. More below.

Regarding sd:/bootmii/armboot.bin ...
ModMii has generated a folder named "bootmiineek" It contains the arm boot.bin file
Currently, I turn the power to console on and am presented with the BootMii screen. When I change the name of this folder to "bootmii", will that affect my current power on behavior... in a way that we don't want it to?

Regarding sd:/sneek/kernel.bin ...
I thought I was deleting this folder from SD altogether since I will only be launching Neek via UGX.

I will delete di.bin from usb:/sneek/ folder

• The sneek folder is NOT on the SD card.
• The di.bin has been removed from the USB sneek folder.
• On launch of Neek, again, there was not a long black screen.
• Once launched, Disc Channel, Mii Channel, Neek2o, and post loader channels are available.
• Home button, Wii Menu restarts the Wii... to the Neek system menu. Good.

Miscellaneous notes:

• The BootMiiNeek folder that ModMii generated to be placed on SD card containing armboot.bin... was renamed to "bootmii". On power up, drive tray light flashes quickly 4 times. Black screen. Waited a few minutes and nothing happened so, force power down. Replaced the bootmii folder with previous data, power up Wii and BootMii appears as usual.
• Swapping USB ports did exactly what I thought it would. UGX doesn't see the Wii games on the USB HDD when that is connected to the OUTSIDE USB port (the one closest to edge of Wii)

What should I do next? Thank you!

 

[Cyan]

Regarding sd:/bootmii/armboot.bin ...
ModMii has generated a folder named "bootmiineek" It contains the arm boot.bin file
Currently, I turn the power to console on and am presented with the BootMii screen. When I change the name of this folder to "bootmii", will that affect my current power on behavior... in a way that we don't want it to?

if you rename "bootmiineek" into "bootmii", it will launch neek at console boot.
boot2 always launches "armboot.bin" from the SD card if present.

if you use bootmii's real "armboot.bin", then it launches bootmii application which let you either boot into bootmii interface, or autoboot HBC or sysmenu.
if you use neek's armboot.bin, then you'll lose your current autoboot setting and neek will launch automatically at console's boot. if you want that, you'll need to keep "sd:/sneek/kernel.bin" too.

On launch of Neek, again, there was not a long black screen.

heyy, good for you
some users had to wait longer, probably a device access speed issue.

• the USB HDD is connected to the INNER USB port on rear of Wii. A USB flash drive is in the OUTER port (the port closest to the edge)
• In this configuration, I have successfully launched Wii disc-based games from UGX. And some WW / VC titles (100-in-1, Double Dragon, Double Dragon 2)
• UGX is told to use both USB ports.
• So what's my point? Whenever I go to custom paths, cycling between USB1 and USB2 shows exactly the same files. In other words, the USB flash drive's data is not being shown when I browse the paths for USB 1 and USB 2. I DO NOT CARE ABOUT THE USB FLASH DRIVE DATA. What I'm asking is...
• Should I connect the USB HDD to the outer port and follow your above steps? Is the outer port USB 1 / is it absolutely necessary to connect the USB HDD to that port?

ahhh, new information from you !
I wish I knew this before.

you are using flashdrives?
is neek located on the flashdrive? if answer is yes, there is a lot of chance the corruption is because of that. flashdrives have LOT of issues in write mode, and trying to write files (neek writes lot of things while being active) could result to corruption. be sure to use HDD for neek, not flashdrive.


if you want to use both USB Port, I'm not sure why you don't put everything on a single HDD ?
using 2 USB Port is a lot of pain, and issues.


If you are using multiple USB Port, but are using IOS58 in the loader, it works DIFFERENTLY than if you are using d2x cIOS in the loader.
IOS58 treats all USB ports as single port, and loads them in reversed order (port1 > port0)
cIOS reads only ONE port at a time, and loads them in incremental order (port0 > port1)

note that port0 is the bottom port on Wii (close to the edge).
You should always use port0 for wii games.
you should prevent using port1 at all. it's only adding problems. you can use problematic setup once you know things are working fine with good setup. but trying to make things working on a wrong setup is only confusing and making it hard to find the solution, because we don't know if there is a problem in what you do, or if there's just an incompatibility in the folkloric setup.


please, do all your test with only 1 HDD, non flashdrive, using USB Port 0 (bottom). disable multi ports.
try launching neek at least twice from usbgx to see if launching>rebooting>launching is working, or corrupts your neek file system. DO NOT ADD WAD !
I would even think it's best to first test with Sneek (instead of Uneek), to be sure USB is not the problem.

doing step by step controls is how you debug things. doing LOT of burn steps is useless and make debugging harder if not impossible.
key to debug anything : single hardware, single software, step one by one, report and wait.

 

[NJBoss]

if you rename "bootmiineek" into "bootmii", it will launch neek at console boot.
boot2 always launches "armboot.bin" from the SD card if present.

if you use bootmii's real "armboot.bin", then it launches bootmii application which let you either boot into bootmii interface, or autoboot HBC or sysmenu.
if you use neek's armboot.bin, then you'll lose your current autoboot setting and neek will launch automatically at console's boot. if you want that, you'll need to keep "sd:/sneek/kernel.bin" too.

That explains it. No, I DON'T want to boot straight to Neek. But, clearly because the kernel.bin file was missing from SD card is why this didn't boot to Neek as expected.
Anyway, the current behavior (the behavior I've had all along and am satisfied with) is...
• boot console
• BootMii screen
• Using buttons on face of console to select to boot to sysNAND System Menu OR Homebrew Channel. I go to HBC to do the "work".

ahhh, new information from you !
I wish I knew this before.

you are using flashdrives?
is neek located on the flashdrive? if answer is yes, there is a lot of chance the corruption is because of that. flashdrives have LOT of issues in write mode, and trying to write files (neek writes lot of things while being active) could result to corruption. be sure to use HDD for neek, not flashdrive.


if you want to use both USB Port, I'm not sure why you don't put everything on a single HDD ?
using 2 USB Port is a lot of pain, and issues.

Let me clear this up before it gets out of control.
THE FLASH DRIVE IS NOT BEING USED FOR ANY OF MY TESTING. IT DOES NOT HOLD ANY RELEVANT FILES. ONLY THE USB HDD AND SD CARD ARE BEING UTILIZED FOR TESTING.
That said, the flash drive holds some ROMs for other emulators. I am going to take the drive out from the inner USB port and continue testing.

*** Now, the one important note I made in my last post is that when I moved the USB HDD to port 0 (the port closest to the edge of the console), UGX is no longer detecting the Wii games (WBFS) stored on that device. That COULD be because the goofy flash drive was in the inner USB port... More on this in a moment. ***

If you are using multiple USB Port, but are using IOS58 in the loader, it works DIFFERENTLY than if you are using d2x cIOS in the loader.
IOS58 treats all USB ports as single port, and loads them in reversed order (port1 > port0)
cIOS reads only ONE port at a time, and loads them in incremental order (port0 > port1)

1) I don't know which iOS I am using in UGX.
2) Which one should I use / how do I change that setting?
3) I installed d2x cIOS a few weeks ago... I don't remember why. What I DO remember is that I used the most current NON-BETA / NON-EXPERIMENTAL version of it.

please, do all your test with only 1 HDD, non flashdrive, using USB Port 0 (bottom). disable multi ports.
try launching neek at least twice from usbgx to see if launching>rebooting>launching is working, or corrupts your neek file system. DO NOT ADD WAD !

Will do. I will launch the neek menu from UGX Features... then reboot from neek sys menu to confirm still working. I won't launch any of the pre-installed channels from Neek sys menu. I will not attempt to launch any of the pre-installed channels on Neek sys menu.

doing step by step controls is how you debug things. doing LOT of burn steps is useless and make debugging harder if not impossible.
key to debug anything : single hardware, single software, step one by one, report and wait.

Of course! We're getting closer to solution. I'll wait for responses to above thoughts then test again tonight. Thanks for all your help!

 

[Cyan]

Anyway, the current behavior (the behavior I've had all along and am satisfied with) is...
• boot console
• BootMii screen
• Using buttons on face of console to select to boot to sysNAND System Menu OR Homebrew Channel. I go to HBC to do the "work".

I find it annoying to see bootmii screen and have to go to the console to press buttons.
you know you can set a timer of 1-2 seconds to autoboot sysmenu for example, if you want to stay in bootmii then you press a button, if not it'll autoboot sysmenu.
You can also set the timer to 0 for autoboot without seeing bootmii screen at all. you can autoboot into sysmenu or hbc.
personnaly, I always autoboot HBC, I don't need sysmenu ever, I only use my Wii for homebrew or launch games from loaders.
if you can't to change your bootmii behavior, there's a bootmii configurator.


Having the flashdrive connected can be an issue, even if neek is on the other port, because like I said when using IOS58 the devices are mounted in reversed order.
if you choose "partition 1" (usb1:/path/path/ etc.) when using cIOS, it loads the path on port0. but the SAME PATH (usb1:/path/path/ etc.) when using IOS58 mounts the first partition on port1 !
the same path are accessing different partition based on your setup.
having 2 devices plugged at the same time is prone to mistake you didn't expected, just because a specific path is not always pointing to the same device. it can lead to "emuNAND not found" (flashing led) for example. or file written to wrong partition etc.



please, follow the syscheck guide in my signature and post the result here.
I suppose you installed d2x v8 final, but I have (and you don't have) no idea which base or slot you installed. this tool will tell us.

 

[NJBoss]

I must be brief for the moment, sorry.

Yes, I want to return to adjusting the BootMii behavior, Excellent tip - I'm not thrilled with having to press buttons on the console either. Ideally, HBC autoboot... or UGX autoboot.

EDIT - removing misinformation to save future confusion.

Here is my SysCheck

Spoiler: My God, what does this all mean...

SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6175).

Region: NTSC-U
System Menu 4.1U (v449)

Drive date: 09.07.2006
Homebrew Channel 1.1.0 running on IOS58

Hollywood v0x11
Console ID: 37236654
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v2
Found 117 titles.
Found 42 IOS on this console. 1 of them are stubs.

IOS4 (rev 3): Stub
IOS9 (rev 54321): Trucha Bug
IOS11 (rev 54321): Trucha Bug
IOS12 (rev 6): Flash Access
IOS13 (rev 10): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS14 (rev 257): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS15 (rev 523): No Patches
IOS16 (rev 54321): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS17 (rev 512): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS20 (rev 54321): Trucha Bug
IOS21 (rev 517): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS22 (rev 772): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS28 (rev 1288): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS30 (rev 54321): Trucha Bug
IOS31 (rev 2576): ES Identify, Flash Access
IOS33 (rev 1040): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS34 (rev 1039): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS35 (rev 1040): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS36 (rev 54321): Trucha Bug, ES Identify, NAND Access
IOS37 (rev 3869): Trucha Bug
IOS38 (rev 3867): Trucha Bug
IOS50 (rev 54321): Trucha Bug
IOS53 (rev 5406): Trucha Bug
IOS55 (rev 5406): Trucha Bug
IOS58 (rev 6175): USB 2.0
IOS60 (rev 54321): Trucha Bug
IOS70 (rev 54321): Trucha Bug
IOS80 (rev 54321): Trucha Bug
IOS90 (rev 54321): Trucha Bug
IOS202[60] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS222[38] (rev 4, Info: hermes-v4): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[38+37] (rev 4, Info: hermes-v4): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS224[57] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS236 (rev 54321): Trucha Bug, ES Identify, NAND Access, Beer Ticket
IOS245[37] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS246[38] (rev 21008, Info: d2x-v8final): Trucha Bug, ES Identify, NAND Access
IOS247[53] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS248[55] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS249[56] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS251[58] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v4
MIOS v8
Report generated on 03/16/2019.

I hope this sheds some light on what the next course of action should be, thank you for your help!

 

[NJBoss]

es, I want to return to adjusting the BootMii behavior, Excellent tip - I'm not thrilled with having to press buttons on the console either. Ideally, HBC autoboot

No further support needed on this - used that configurator to autoboot HBC. Thanks for the tip!

 

[NJBoss]

My stupidity is limitless... The following info is incorrect. Ignore it.

• my Wii is vertical. I have moved the USB HDD to the port that is closest to the edge of the Wii. Looking at the console from the front, the USB port would be the right most. Looking directly at the rear of console, that port would be the left most.
• Launch UGX and... it does not mount the USB HDD. It tried for 20 seconds at launch before giving the message "Mounting USB port to 1"
• In UGX, it is reporting that the HDD is not initialized, switching to channel mode. Or something like that.
• Go to Hard Drive Settings, change ports from Both to Port 0. No success. Then changed settings from use port 0 to Port 1. No success. The top most setting reports Not Initialized. When the USB HDD was connected to the "wrong port", I remember that setting reported something to the effect of FAT32... I can't remember for sure, sorry.

All along I thought the "working / outside port" was the one the HDD was plugged in to. I turned the console to go flat / horizontal. The USB HDD was not in the bottom port in this configuration.

The USB HDD has been placed into the correct port. UGX launches without issue (as before). Wii games are showing up in the available titles. Hard Drive Settings is not showing uninitialized drive. USB is set to Port 0 only. And...

Used Features to successfully launch Neek System Menu. I used Home button on Wii remote then Wii Menu to "reset" the console. Need System Menu appears as expected.

At this point, not installing any WW / VC games. Sys Check report is posted and I will wait for guidance on next steps, cheers.

 

[Cyan]

All along I thought the "working / outside port" was the one the HDD was plugged in to. I turned the console to go flat / horizontal. The USB HDD was not in the bottom port in this configuration.
The USB HDD has been placed into the correct port. UGX launches without issue (as before). Wii games are showing up in the available titles. Hard Drive Settings is not showing uninitialized drive. USB is set to Port 0 only. And...
Used Features to successfully launch Neek System Menu. I used Home button on Wii remote then Wii Menu to "reset" the console. Need System Menu appears as expected.

Ahh, some good news

Here is my SysCheck

Spoiler: My God, what does this all mean...

SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6175).

Region: NTSC-U
System Menu 4.1U (v449)

Drive date: 09.07.2006
Homebrew Channel 1.1.0 running on IOS58

Hollywood v0x11
Console ID: 37236654
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v2
Found 117 titles.
Found 42 IOS on this console. 1 of them are stubs.

IOS4 (rev 3): Stub
IOS9 (rev 54321): Trucha Bug
IOS11 (rev 54321): Trucha Bug
IOS12 (rev 6): Flash Access
IOS13 (rev 10): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS14 (rev 257): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS15 (rev 523): No Patches
IOS16 (rev 54321): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS17 (rev 512): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS20 (rev 54321): Trucha Bug
IOS21 (rev 517): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS22 (rev 772): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS28 (rev 1288): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS30 (rev 54321): Trucha Bug
IOS31 (rev 2576): ES Identify, Flash Access
IOS33 (rev 1040): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS34 (rev 1039): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS35 (rev 1040): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS36 (rev 54321): Trucha Bug, ES Identify, NAND Access
IOS37 (rev 3869): Trucha Bug
IOS38 (rev 3867): Trucha Bug
IOS50 (rev 54321): Trucha Bug
IOS53 (rev 5406): Trucha Bug
IOS55 (rev 5406): Trucha Bug
IOS58 (rev 6175): USB 2.0
IOS60 (rev 54321): Trucha Bug
IOS70 (rev 54321): Trucha Bug
IOS80 (rev 54321): Trucha Bug
IOS90 (rev 54321): Trucha Bug
IOS202[60] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS222[38] (rev 4, Info: hermes-v4): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[38+37] (rev 4, Info: hermes-v4): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS224[57] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS236 (rev 54321): Trucha Bug, ES Identify, NAND Access, Beer Ticket
IOS245[37] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS246[38] (rev 21008, Info: d2x-v8final): Trucha Bug, ES Identify, NAND Access
IOS247[53] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS248[55] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS249[56] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS250[57] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS251[58] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v4
MIOS v8
Report generated on 03/16/2019.

I hope this sheds some light on what the next course of action should be, thank you for your help!

OHHHHH my god.
I spoke too soon !

Here is a little information :
Neek purpose is to hack the console and do all sort of things (such as launching backup) while the console doesn't see it's been hacked.
it means : no custom or patched IOS are required to play games, unlike USB Loaders which rely on cIOS.
the purpose of neek is to launch backups without cIOS ! all games are expected to use their official, original, untouched respective IOS.

now your setup :
ALL your sysNAND is wrong and ALL your IOS are patched to replace them to cIOS. ALL of them, not only the IOS used by usbloaders (249/250), no no no, all of your IOS used by retail games too !
which means that when you dump your real NAND to use it as base for neek, all the IOS expected to look clean for neek are in fact altered and not clean at all.
if you try to play your legally bought retail game disc with anti-piracy detection on your console (without usbloaders), it wouldn't work either.

I don't say that it's the reason neek didn't work correctly, but it's just a paradox to want to use neek to play incompatible games with anti-piracy detection but launching them with patched IOS anyway, which triggers the antipiracy code.
neek is therefore useless here, and non working games in USBLoaderGX will also be non working on neek !


what I recommend:
you made a clean emuNAND NTSC-U, so you don't have to worry about your sysNAND being patched because you don't rely on your real NAND dump anymore.
but I still recommend you clean your sysNAND for any future usage.
Your IOS are also outdated, so updating them is also recommended.

You should download modmii (a windows tool), and follow the option "I want to resoftmod", it will ask you questions and based on your answers it will generate a guide that you have to follow.
it'll download all the updated and clean WAD of all IOS/MIOS/BC slots.


post a new syscheck after doing that

 

[NJBoss]

OHHHHH my god.
I spoke too soon !

LOL

ALL your sysNAND is wrong and ALL your IOS are patched to replace them to cIOS. ALL of them, not only the IOS used by usbloaders (249/250), no no no, all of your IOS used by retail games too !
which means that when you dump your real NAND to use it as base for neek, all the IOS expected to look clean for neek are in fact altered and not clean at all.

So we're clear on this - UGX emuNAND path is pointing to the clean NAND generated by ModMii, not a dump of my realNAND.
The realNAND dump doesn't mean jack sh!t to the Wii games in UGX because, as you've pointed out, UGX is not relying on emuNAND to launch those games.

if you try to play your legally bought retail game disc with anti-piracy detection on your console (without usbloaders), it wouldn't work either.

That's where I think we have a disconnect. When I did the soft mod many years ago, the purpose was to continue using retail discs and backup discs. Both types of discs worked fine on real sys menu. Retail discs through Disc Channel, backup discs through Neo Gamma. UGX I had as channel but never really explored it (these were the days when external media was... less inexpensive). Hope that info helps!

you made a clean emuNAND NTSC-U, so you don't have to worry about your sysNAND being patched because you don't rely on your real NAND dump anymore.

Ignore my comment above re: which emuNAND UGX was pointing to. Clearly, you understand my setup.

but I still recommend you clean your sysNAND for any future usage.
Your IOS are also outdated, so updating them is also recommended.

You should download modmii (a windows tool), and follow the option "I want to resoftmod", it will ask you questions and based on your answers it will generate a guide that you have to follow.
it'll download all the updated and clean WAD of all IOS/MIOS/BC slots.


post a new syscheck after doing that

Remember early on in thread I remarked that I would have no problem re-modding from scratch? ;-)

Alas, I need to wait to get in front of my Mac with Parallels to do this next operative. I'm all about it - it's a big, 10 year old mess that needs to be sorted. Cheers!

 

[Cyan]

That's where I think we have a disconnect. When I did the soft mod many years ago, the purpose was to continue using retail discs and backup discs. Both types of discs worked fine on real sys menu.

I specifically mentioned "disc with anti-piracy detection".
so what you did was meant to play disc (retail and burned) from disc channel, but not all disc would work based on your setup. some games are detecting console modification, and that's where neek comes in action, redirecting without system modification.

Alas, I need to wait to get in front of my Mac

ah, you have a mac?
you can launch windows apps ?

 

[NJBoss]

but not all disc would work based on your setup. some games are detecting console modification, and that's where neek comes in action, redirecting without system modification.

I'm sort of interested to test a disc with this feature. Retail discs never gave me an issue after soft mod. Truly, this would be a waste of time as we are going to re-mod.

ah, you have a mac?
you can launch windows apps ?

Yes, using Parallels. At that machine now so, here goes with ModMii...
When asked if first time soft-modding, I am choosing YES... even though that is not the truth. I won't know exactly what I want to update and, as the wizard advises, select NO only if I know what I want to update.

In the guide, a few things stood out at me. How do you feel about the following?

"Do not update active IOSs (can be enabled in options)
Do not Install a cMIOS (can be enabled in options) "

Much of the rest of the guide is pretty straightforward. I might regret this but, I am going to take my existing SD card and shelf it. Will follow this guide using fresh SD.
Interestingly, ModMii did not put anything into the COPY TO USB folder. Anyway, will give it a go tonight, thanks!

 

[Cyan]

I'm sort of interested to test a disc with this feature. Retail discs never gave me an issue after soft mod. Truly, this would be a waste of time as we are going to re-mod.

Try Tintin. it's a known game to work only in neek.
but I'm not sure if it detects the cIOS or the way the game is launched (through loader, or through disc channel).


I think default settings are fine if you choose to (re)softmod.
it should download and make you reinstall all the IOS (below slot 200) used by retail games, cIOS (over slot 200) d2x v8, maybe even hermes cIOS (not sure they are still provided in default modmii settings), BC v6 and MIOS v10.

do not install cMIOS.

everything goes to "copy to SD" because all the guide uses SD card. lot of homebrew where never made to support USB, and therefore have SD path hardcoded.
it's always best to use SD to softmod/hack a console. once everything is done, you can then switch to using USB with compatible homebrew.


remember, this is only to have a cleaner Wii system. it's not affected neek, we will go back to neek after that
it's just in case you make a NAND dump to use for wiiware/VC, you'll have better IOS.

 

[NJBoss]

Try Tintin. it's a known game to work only in neek.
but I'm not sure if it detects the cIOS or the way the game is launched (through loader, or through disc channel).

Yup, good tip. Once all is clean again, I will use that one to test with.

remember, this is only to have a cleaner Wii system. it's not affected neek, we will go back to neek after that
it's just in case you make a NAND dump to use for wiiware/VC, you'll have better IOS.

Hell yeah. Gonna clean house tonight. Cheers!

 

[NJBoss]

Well, it's all updated now. Before I install the VC / WW WADs, do you need another sys check? Any other instructions?
FWIW, there are residual channels on the sysNAND that don't work - emulators. They lead to gray Wii loading screen before arriving back to real System Menu. I believe these are forwarder channels that are looking for the apps on SD card. Recall that in this latest attempt, I have started with a clean SD card. I am merged some data from the fresh SD card with the files on the previous SD card. Put previous SD card in Wii, channels are working again. I've got two USB Loader channels on there that have a different visual appearance from one another. One is asking to connect a USB drive at the hold screen - press Start and there's a different Wii controller graphic that is shown before the usual UGX loading screen. Both channels launch UGX properly. Whatever.

 

[NJBoss]

Spoiler: F it, here's the latest sys check

SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline, Double_A, R2-D2199, and Nano
...runs on IOS58 (rev 6176).

Region: NTSC-U
System Menu 4.1U (v449)
Priiloader installed
Drive date: 09.07.2006
Homebrew Channel 1.1.2 running on IOS58

Hollywood v0x11
Console ID: 37236654
Console Type: Wii
Shop Channel Country: United States (49)
Boot2 v2
Found 122 titles.
Found 44 IOS on this console. 1 of them are stubs.

IOS4 (rev 3): Stub
IOS9 (rev 54321): Trucha Bug
IOS11 (rev 16174): Trucha Bug, NAND Access
IOS12 (rev 6): Flash Access
IOS13 (rev 10): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS14 (rev 257): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS15 (rev 523): No Patches
IOS16 (rev 54321): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS17 (rev 512): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS20 (rev 16174): Trucha Bug, NAND Access
IOS21 (rev 517): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS22 (rev 772): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS28 (rev 1288): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS30 (rev 16174): Trucha Bug, NAND Access
IOS31 (rev 2576): ES Identify, Flash Access
IOS33 (rev 1040): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS34 (rev 1039): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS35 (rev 1040): Trucha Bug, ES Identify, Flash Access, NAND Access
IOS36 (rev 54321): Trucha Bug, ES Identify, NAND Access
IOS37 (rev 3869): Trucha Bug
IOS38 (rev 3867): Trucha Bug
IOS40 (rev 16174): Trucha Bug, NAND Access
IOS50 (rev 16174): Trucha Bug, NAND Access
IOS52 (rev 16174): Trucha Bug, NAND Access
IOS53 (rev 5406): Trucha Bug
IOS55 (rev 5406): Trucha Bug
IOS58 (rev 6176): USB 2.0
IOS60 (rev 16174): Trucha Bug, NAND Access
IOS70 (rev 16174): Trucha Bug, NAND Access
IOS80 (rev 16174): Trucha Bug, NAND Access
IOS90 (rev 54321): Trucha Bug
IOS202[60] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS222[38] (rev 4, Info: hermes-v4): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS223[38+37] (rev 4, Info: hermes-v4): Trucha Bug, ES Identify, NAND Access, USB 2.0
IOS224[57] (rev 65535, Info: hermesrodries-v6): Trucha Bug, NAND Access, USB 2.0
IOS236[36] (rev 65535, Info: rev 3351): Trucha Bug, ES Identify, NAND Access
IOS245[37] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS246[38] (rev 21008, Info: d2x-v8final): Trucha Bug, ES Identify, NAND Access
IOS247[53] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS248[55] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS249[57] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS250[56] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS251[58] (rev 21008, Info: d2x-v8final): Trucha Bug, NAND Access, USB 2.0
IOS254 (rev 65281): BootMii
BC v4
MIOS v8
Report generated on 03/18/2019.

Wii WBFS games launch without issue, as expected. I haven't tried Neek or installing WW / VC WADs yet. Cheers.

 

[Cyan]

Yup, good tip. Once all is clean again, I will use that one to test with.

the test has to be done BEFORE it's all clean.
if it's clean, then of course Tintin will work.

thanks for your new syscheck, allmost good.
BCv6 and MIOSv10 could be nice, but they are used for gamecube discs so don't worry too much.

I'll help you later for neek.

 

[NJBoss]

SysCheck reveals what I've got going on now. I still didn't install any WW / VC WADs to test from within UGX. Ultimately, that's how I'd like to launch everything... as much as compatibility allows. We have established that I had some outdated, possibly "bad" modding. My hope is that the newly updated mod will allow for these titles to launch from UGX without issue. Is it safe to begin testing WW / VC installation now? Or... (caution, stupidity follows!) Do I once again do a full dump of sysNAND then install the WADs? Point UGX emuNAND and emuNAND channel path to THAT NAND, not the clean one generated by ModMii?

the test has to be done BEFORE it's all clean.
if it's clean, then of course Tintin will work.

Which would require neek to point to the emuNAND path to the clean one generated by ModMii. Right?

thanks for your new syscheck, allmost good.
BCv6 and MIOSv10 could be nice, but they are used for gamecube discs so don't worry too much.

Do I need to remove any iOS? FWIW, I don't have any GC games (discs or otherwise). Those discs wouldn't fit in Wii disc tray anyway... :-D
Thanks!