- Joined
- Oct 27, 2002
- Messages
- 23,749
- Trophies
- 4
- Age
- 46
- Location
- Engine room, learning
- XP
- 15,661
- Country
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
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
Last edited by Cyan,