Hacking Wii NAND-Backup help

XFlak

Wiitired but still kicking
Member
Joined
Sep 12, 2009
Messages
13,799
Trophies
3
Age
38
Location
Cyprus, originally from Toronto
Website
modmii.github.io
XP
9,782
Country
Cyprus
This might also help, someone else asked the same Q in another thread
Modmii by default creates a copy to sd folder and a copy to USB folder. You want to copy the contents of those folders to the root of those devices. Or you can tell ModMii where your SD card is and where your hard drive is and it will put the files directly on the drives without you having to do anything extra. You would have seen screens prompting you to browse for your sd card, or continue using copy to sd and doing the transfer later.

I will have to run it to be sure, but as I said I think there are instructions or tips displayed on screen at the end of a neek installation. In any case, if you run nswitch, it will rename bootmiineek to bootmii, then it will launch "bootmii" which is really launching neek.

Alternatively you could manually rename bootmiineek to bootmii (on the SD card) and then launch "bootmii" (really neek) from the HBC or boot2.
 

Davve_DP

Member
OP
Newcomer
Joined
Mar 29, 2019
Messages
24
Trophies
0
Age
22
XP
138
Country
Sweden
So if I've gone ahead and done these things:

Installed bootmii as IOS (apparently I hadn't done that) and made a backup of my NAND.

*I'm not using this nand copy as my emuNAND, It's saved safely on my PC*

Then I went ahead and installed the sneek-wad file that came un my modmii bundle.

I then ran the sneek channel and managed to boot into my emuNAND. I went through the setup process and arrived at the system menu. Then I booted back to the system menu using the modmii-installed sneek channel in my emuNAND.

This is about as far I got without trouble. Now I want to install wads to my emuNAND through USBLoader GX. But when I choose to boot into neek (from the features-list) It just shows me a black screen and the blue LED lights up every 3 seconds.

I then looked at my nand directory, it looks like this:

USB/nands/nand1/import, shared etc.

I'm wondering if USBLoader GX is expecting the emuNAND in another location or if it's expecting the neek files in another location.

Can you understand this?

Installed:

UNEEK + DI (neek2o rev96) ---> USB/sneek/di.bin
USB/sneek/diconfig.bin
USB/sneek/font.bin
USB/sneek/kernel.bin
USB/sneek/nadncfg.bin

Bootmii ---> USB/bootmii/armboot.bin


Btw, multimodmanager doesn't seem to work when run from usb either.

EDIT: Now no matter what I do I can't get back into my emuNAND using the channel on my system menu. I'm really stuck rn
 
Last edited by Davve_DP,

XFlak

Wiitired but still kicking
Member
Joined
Sep 12, 2009
Messages
13,799
Trophies
3
Age
38
Location
Cyprus, originally from Toronto
Website
modmii.github.io
XP
9,782
Country
Cyprus
What's your sd card folder structure look like? You can try manually renaming bootmineek to bootmii on the SD and launch "bootmii" (actually neek) from the HBC menu.

In terms of where gx expects the emunand @Cyan is a good resource to ask, I'm actually not sure. I know it detects my emunand which is *I think* in a similar structure to yours, but I'd have to double check to be certain.

Note you can also install wads to your emunand with a PC using ModMii or showmiiwads /showmiinand
 

Davve_DP

Member
OP
Newcomer
Joined
Mar 29, 2019
Messages
24
Trophies
0
Age
22
XP
138
Country
Sweden
So I've been at it at it a few hours and concluded this:

---> modmii (the real modmii) has no effect on either neek whatsoever (as expected)
---> Without changing the files at all I can boot into emuNAND using the neek2o channel and then fail to launch it in USBLoader GX. Then after that fail the channel stops working too.

I'm assuming that USBLoader GX messes with the files somehow so that the neek2o channel gets confused.

all within neek works fine, tried some wbfs titles which also worked.

I'm currently debating between moving the neek2o files to the USB drive to try that.

My question: Does the neek channel expect to find its files from SD or can it be run only from USB? I'm suspecting that using both SD and USB is confusing some peice of software.

here's my SD structure

apps
bootmiineek
ploader (not using this at all so will delete it)
sneek
---> sneek/kernel.bin
WAD
boot.elf (no idea what it does)
bootmini.elf (no idea what it does)
historii.txt
mmmconfig.txt (could this be why it mmm didn't work on USB?)
neek20booter.app (no idea what it does)
neek2obooter.dol (no idea what it does)
readmii.txt

My USB structure:

/apps
/controllers (for nintendont)
/games (gc games)
/nands

---> nands/pl_us (my USA NAND)

/saves (gc memory cards)
/sneek
---> sneek/di.bin
---> sneek/diconfig.bin
---> sneek/font.bin
---> sneek/kernel.bin
---> sneek/nandcfg.bin

/wad
/wbfs (wbfs games)
 

Davve_DP

Member
OP
Newcomer
Joined
Mar 29, 2019
Messages
24
Trophies
0
Age
22
XP
138
Country
Sweden
Welp. I think that's game-over for me. I managed to figure out what the problem was. US loader GX expected:
usb/nands/01
My nand was called nand1 not 01.
What I later did was I added some wads using the USBLoader GX was manager. These were ofc games.
I then saw them show up amongst my other games in the loader. I also saw the neek2o channel as well.

I then set the global settings:
nand channel emulation ----> neek
Return to ------> neek2o
Then I tried launching the games with no success.

My thought process then was that I'd try launching the channels from the emuNAND system menu instead. So I launched the neek2o channel from the system menu and it did half the process before giving me a black screen and then returning me to the Wii menu. Only problem is that the video is frozen on the first frame of the system menu load-in screen.

Is this a soft brick? I'm assuming what happened is that the neek2o channel got run unlimited times because USBLoader had told it (since it counts as a game in usbloader) to return to itself after running.

What do I do from here?
 

Cyan

GBATemp's lurking knight
Former Staff
Joined
Oct 27, 2002
Messages
23,749
Trophies
4
Age
45
Location
Engine room, learning
XP
15,648
Country
France
USBLoaderGX uses the path set in the settings. it doesn't assume or use any hardcoded path.
by default, it used to be "sd:/nand/"
but I heard and got report that neek2o expected 2 subfolders instead of only one, for example to look like "sd:/nands/pl_us" for Post Loader.
so I renamed the default emuNAND path to "sd:/nands/01/"

you can of course change that path to be anything else, for example "USB:/nands/nand1/" so it uses the same path than the one you used when launched from nswitch.
when you run neek from USBLoaderGX (there are 2 ways to do it, I'll cover that later), it put that path into "nandcfg.bin" file in sneek folder.
if your nandcfg.bin is messed up, you can just delete that file so it is generated again on next launch.


Sorry, I didn't read the full thread yet, but I don't recommend keeping di.bin in the sneek folder until after you confirmed neek is working.
so if neek doesn't boot at all, for now just move/delete that file from sneek.
I'll read your thread better in few mins and edit here if I have more to tell.


edit:
Ok, I see you could boot into Neek2o just fine, and with di.bin file, so don't bother deleting it now. it works fine.
in order to manage the emuNAND content within USBLoaderGX, you need to set your folder in the settings.
settings > custom path > emuNAND channel folder : usb1:/nands/nand1/
main window > top menu > 4th icon : enable "emuNAND channels"
now you can see the content of that emuNAND inside the loader's interface.

if you run a game listed here, it'll use "cIOS emuNAND Full" mode. that mode doesn't reboot the console into neek mode, and it works fine for 80% (or more) of games.
for the few games (wiiware and N64VC) not working, you'll need the "neek emuNAND" mode.
Select the game (from USBGX interface) that is not working/booting when launched with default "cIOS EmuNAND Full" mode, go to option > Game option > Change the emuNAND option from "Full" to "neek".
it will set the NEEK mode only for THIS game. not all other games.
this is the individual game setting.

only set neek mode for non working games.
all other games should keep using the normal cIOS mode, as it's easier/faster, and reboots right into the loader when you exit a game.

When you play a game using neek mode, if you want to automatically exit neek when you exit the game, and having the console reboot into "non neek" mode, then you need :
- Neek (nswitch) channel installed on emuNAND
- USBLoaderGX's setting "return to" enabled in the individual game setting.

if you want to exit a game launched in neek mode and return to the "neek" system menu (no console reboot, for example if you plan to launch another N64 VC channel directly from neek) then just disable "return to" setting in the individual game setting.
if you disable it in the global settings, it'll affect ALL games (not only neek) : wii games will also stop returning to USBLoaderGX automatically, so I don't recommend doing it in global mode.


Does the neek channel expect to find its files from SD or can it be run only from USB? I'm suspecting that using both SD and USB is confusing some peice of software.
the neek channel is not really one.
it's only a bootmii launcher if you are on real NAND, and a console rebooter if you are on emuNAND (already in neek).

Bootmii is ALWAYS booted from SD.

Sneek : bootmii -> SD -> Sneek
Uneek : Bootmii -> SD -> USB -> Uneek


Sneek : sd:/sneek/kernel.bin (sneek kernel.bin)
Uneek : sd:/sneek/kernel.bin (uneek kernel.bin) + usb:/sneek/kernel.bin (uneek kernel.bin too)
Even if you place your emuNAND on USB, you need to ALSO place the "uneek" kernel.bin on SD:/sneek/


if you use USBLoaderGX :
the loader loads the kernel.bin from the same partition than you emuNAND folder :
if your emuNAND is on USB, it loads usb:/sneek/kernel.bin (uneek kernel.bin)
if your emuNAND is on SD, it loads sd:/sneek/kernel.bin (sneek kernel.bin)
this is useful in case you have multiple emuNANDS and switch them often : you just boot the game, and it'll use the kernel.bin corresponding to the location.

Attention : if you have sneek kernel.bin on SD, it will NOT launch Uneek if you use nswitch/bootmii.


I then set the global settings:
nand channel emulation ----> neek
Return to ------> neek2o
Never do that !
you misunderstood that option !

the "return to" is meant for real NAND, not EmuNAND !
this one is the channel to "return to" when you exit a Wii game (wbfs), it's used to return to "UNEO" forwarder in order to return into the loader automatically when exiting a game, instead of returning to system menu.

If you want to return to "NK2O" channel on neek when exiting a neek's launched game... you don't need to specify it, it's already hardcoded to return to THAT nswitch channel located on EmuNAND. You just need to have the channel installed on emuNAND to load it when exiting a game autobooted from USBGX, and the effect is : reboot the console ! (which effectively exit neek)


You didn't create a loop, as it's NOT launching nswitch channel on real NAND. it's launching it when you are in neek, to reboot the console, and only when exiting a game.


also, like explained above : DO NOT SET NEEK AS GLOBAL SETTING ! it should work, but neek is not meant to be used as default/daily/main interface. it's slow, has issues and is not necessarily a miracle solution for non working games.
this is bad practice.
please, always use "FULL" as global emuNAND Channel mode. only use neek individually for non working games.





setup is really easy :
- generate uneek with modmii, put on USB. (don't care about "copy_to_sd")
- generate sneek with modmii, put on SD.
- launch USBGX, set emuNAND Channel folder path like you want, and dump NAND to that folder. (or generate one with modmii and point usbgx settings to that folder)
- launch neek (from features menu) at least once to init/verify it works.
- shutdown the console, return to usbgx, add wads (don't forget to add NK2O (nswitch, neek) channel manually if you didn't generate/add that option from modmii)

- play channels using the default "full" mode.
- only for channels not working, set "neek" mode.

all settings are already set correctly by default, with all "return to" set as you'd want them to be.
 
Last edited by Cyan,

XFlak

Wiitired but still kicking
Member
Joined
Sep 12, 2009
Messages
13,799
Trophies
3
Age
38
Location
Cyprus, originally from Toronto
Website
modmii.github.io
XP
9,782
Country
Cyprus
Anything u did with neek should not have had an impact on the real nand. Can you explain the problem you're having in greater detail?

If having issues booting to real nand, try removing the SD card and other peripherals. If u have bootmii installed as boot2 and an SD card with neek in the bootmii folder it will try to launch immediately upon boot which could mislead you into believing you have issues impacting your real nand
 
Last edited by XFlak,

Davve_DP

Member
OP
Newcomer
Joined
Mar 29, 2019
Messages
24
Trophies
0
Age
22
XP
138
Country
Sweden
EYYYY!! I'TS ALIVE!!

I don't know how, but when I started it now a few hours later it worked. Maybe the graphics chip was too hot or something. But anyway I did as you said cyan and made sure to change my global nand channel emulation setting to "full" instead of "neek". I also turned return to "off" for the time being. In the n64 games I turned on neek as my emulation mode.

But the games aren't working!

Maybe my wads are bad...

could you maybe point me in the o so legal direction of where I vould find some working wads ;)

I have no experience in wad injections but I would love to learn!

thanks for the amazing feedback. You really wrote-up on that one mate.

Have a fantastic evening!

I love GBAtemp!

--------------------- MERGED ---------------------------

Actually the games aren't bad at all. They work when they're launched from emuNAND as channels. Some setting must be wrong in USBLoader GX.

Does USBGX look for kernel.bin in SD?
I currently don't have my SD card inserted, but I copied all the contents from COPY_TO_SD to my usb drive instead and I can run games from my emuNAND. So nswitch can read the kernel.bin file on my usb drive but USBGX can't?
Have I understood that correctly?
 
Last edited by Davve_DP,

Cyan

GBATemp's lurking knight
Former Staff
Joined
Oct 27, 2002
Messages
23,749
Trophies
4
Age
45
Location
Engine room, learning
XP
15,648
Country
France
sorry if I gave lot of info at once, I tend to write a lot :P

if the N64 game is not working when using neek mode with autoboot, try to launch neek sysmenu (from the features menu, so it doesn't boot any game), and from the neek system menu try launching the game normally.
if it's the same region, it should work. if it's a channel from another region than the emuNAND region you created, you need to enable neek region free in the neek's hidden menu.

if still not working let us know, we will search more possibilities from there.


edit:
oh I see you did what I said. I guess when you said "launch as channel" you mean inside neek. or maybe you think you are inside neek but installed the channel on realNAND?

Does USBGX look for kernel.bin in SD?
Like I said in my previous message, USBGX only loads the kernel bin from the same partition than the emuNAND folder.

<partition>:/nands/nand1/
<partition>:/sneek/kernel.bin

if your nand1 is on USB, it doesn't look at kernel.bin on SD.

I copied all the contents from COPY_TO_SD to my usb drive instead and I can run games from my emuNAND. So nswitch can read the kernel.bin file on my usb drive but USBGX can't?
Have I understood that correctly?
Hmmm, okay that one is really weird.
if you don't have SD card inserted, nswitch shouldn't be able to boot neek (because it actually boot Bootmii, which loads bootmii/armboot.bin, which loads sd:/sneek/kernel.bin, which loads <partition>:/path/to/emuNAND/ based on "S" or "U" neek you generated in modmii)
I don't think there were any nswitch updated to never use bootmii on Wii (and work like vWii, and like usbgx)
maybe I'm wrong if it works without SD card, and it has been updated to work by loading kernel.bin directly instead of bootmii?


And it's probably working only because you copied the "copy to SD" from a Uneek (not Sneek) generated by modmii, which is actually uneek's kernel.bin in both "copy to SD" and "copy to USB" folders (both used to load nand path on USB).
if it was a "copy to SD" from a sneek (not Uneek) then it would try to mount the SD card.
that's one of the misconception, people think the "copy to SD" is needed only if they have the emuNAND on SD, and "copy to usb" only if they use it, but that's not how it works. you need both SD+USB if your emuNAND is on USB. they think the "copy to SD" contains Sneek, while it contains Uneek kernel.bin if they generated uneek!


as for your "it looks like it's semi bricked" when you boot the console with the SD card, it's probably because you replaced bootmii/armboot.bin with neek's booter.
delete the bootmii folder, and it'll work again.
even better, replace the original bootmii folder here, and it'll launch bootmii at console's boot, which lets you autoboot HBC if you want.
 
Last edited by Cyan,
  • Like
Reactions: XFlak

Davve_DP

Member
OP
Newcomer
Joined
Mar 29, 2019
Messages
24
Trophies
0
Age
22
XP
138
Country
Sweden
Thanks a lot Cyan. You really are a legend here at Gbatemp!

I'll keep cracking tomorrow and fiddle around a little to make sure the games load from USBGX and get back to this thread.

Thanks a ton to Xflak ofc too because without modmii I never would've figured this out.
 
  • Like
Reactions: XFlak

XFlak

Wiitired but still kicking
Member
Joined
Sep 12, 2009
Messages
13,799
Trophies
3
Age
38
Location
Cyprus, originally from Toronto
Website
modmii.github.io
XP
9,782
Country
Cyprus
@Cyan, can you confirm if usbloader gx can boot games off a USB emunand in "full" mode even without an SD card? And that an SD card with a neek bootmii folder is only needed if loading a USB emunand in "neek" mode. Is that all accurate? Just trying to fine tune my knowledge on the subject. Cheers m8
 
Last edited by XFlak,

Cyan

GBATemp's lurking knight
Former Staff
Joined
Oct 27, 2002
Messages
23,749
Trophies
4
Age
45
Location
Engine room, learning
XP
15,648
Country
France
yes, it can boot anything without SD card, wii games, gamecube, EmuNAND Full, EmuNAND neek.

Full mode is done in sysNAND mode, using the cIOS to rewrite path in real time (when a game asks for NAND file, the IOS serves the file from emuNAND folder instead (like layeredFS on 3DS/Switch), whether it's SD or USB has no impact, it's using the path set in USBGX's settings)
Neek mode doesn't rely on cIOS and reboot the full console, it can also use only the USB, the SD card is not required.

SD card with the neek bootmii folder is only needed if you want to launch neek using either bootmii or nswitch (which also uses bootmii).
USBLoaderGX does not rely on armboot.bin at all to load kernel.bin, it loads the proper kernel.bin directly based on where is located the emuNAND folder.

if you have emuNAND on USB1, it'll load usb1:/sneek/kernel.bin (SD is not accessed or needed at all)
if you have emuNAND on SD, it'll load sd:/sneek/kernel.bin

My best setup is this :
usb1:/sneek/kernel.bin <--- uneek kernel.bin
sd:/sneek/kernel.bin <--- sneek kernel.bin
usbgx will use the one based on the emuNAND folder, if emuNAND is on Sd it'll use Sneek, if the emuNAND is on USB it'll use Uneek.
 
Last edited by Cyan,

XFlak

Wiitired but still kicking
Member
Joined
Sep 12, 2009
Messages
13,799
Trophies
3
Age
38
Location
Cyprus, originally from Toronto
Website
modmii.github.io
XP
9,782
Country
Cyprus
Interesting. I honestly had no idea you could boot uneek without an SD card. I'm assuming you could do so even with a fresh emunand created by ModMii and it will expand files upon first launch the same as if it were launched using the traditional bootmii method
 

Davve_DP

Member
OP
Newcomer
Joined
Mar 29, 2019
Messages
24
Trophies
0
Age
22
XP
138
Country
Sweden
Hi again guys!

So I've cleaned up my usb drive, but I'm still not using an SD card. I'm able to use the nswitch channel by putting the "bootmineek" folder on my drive. Also I'm able to boot into neek through USBLoader GX.

I'm also able to see my installed emuNAND titles and I've set "neek" as the individual "game load" setting. While keeping the emuNAND path to "global". If I can boot into neek from USBGX then my global setting should be the right one.

I can also play my emuNAND n64 games from the neek emuNAND menu by launching the channel. But I can't get the game to work when I launch it from USBLoader GX.

Could it be the case that USBGX can't initiate emulation because of some path that is not set?

I'm not really sure whats wrong.

Here's my drive structure:

/apps
/bootmiineek ---> armboot.bin
/controllers
/games
/nands ---> 01 (my emuNAND)
/saves
/sneek --->

/sneek/di.bin
/sneek/diconfig.bin
/sneek/font.bin
/sneek/kernel.bin
/sneek/nandcfg.bin

/wad
/wbfs

Thanks again for all your support!
 
Last edited by Davve_DP,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    K3Nv2 @ K3Nv2: https://youtu.be/K-Gqyv0gkHc?si=nGlIcg7Lr7OPfc4a