I'm sorry man, but I'm a complete newbie, so it's kind of difficult, and I'm trying my best to comprehend. But I followed your guide https://gbatemp.net/posts/6592730,what you did wrong? you didn't follow the guide.
Where in my guide did it tell to launch neek using nswitch? (I listed it as possible method only, but told that USBLoaderGX does things differently)
here is the launch part in the guide:
to launch neek, use USBLoaderGX.
unless you don't want to use that loader and really want to launch neek independently from any loaders, then you need to install bootmii as IOS to use nswitch, as it relies on it.
if it freezes on "reloading bootmii IOS" and you don't have bootmii IOS installed, then it can't load it...
then set up neek (skip step 1 & 2 as said above) and then up until step 6 and got that black screen. Isn't that the guide?Neek(2o) setup
I already wrote few neek and neek2o compiling and setup tutorial, so I will give links instead of writing the same thing again.
Neek/Neek2o Wii file creation using modmii (skip step 1 and 2)
NEEK INSTALLATION GUIDE6. Install complete
- plug USB and SD to Wii.
- Launch nswitch homebrew and wait until the console reboots.
Ok thanks @Cyan Ima give a try when I'm home, but it's ok I should have read that part, but I'm always doing the guides like exactly as they're written, so got confused. But, hey, thanks for the guides, I mean those are the only guides out there related to the neek2o & usb loader gx. It would be great if they were finished, although it's ok they're a WIP I suppose!well, my guide is in fact 3 different guides written at different dates for different reasons with conflicting instructions. I never took time to write a full, real guide, not based on multiple sources.
the link to these guides were only used for the "file creation" either from modmii or from the installer. not the be followed to launch it, as it's done in the main guide.
File creation is "step 3" only.
but okay, sorry that it's confusing.
once you created the files (with modmii or the installer), then continue reading the main guide to launch neek from usbloadergx.
important thing :
when following a guide, read it at least 3 time BEFORE attempting to follow it.
be sure to understand all the steps and that everything is coherent and make sense to you.
that's not only for neek, but a general guide and tutorial for anything.
note that it's not something I tell against you, I'm not criticizing. I'm just explaining and wanting to help.
Oh, glad you could compile it with r27 (and we all wonder why wintermute force deletion of old toolchain from internet when it's still the easiest to just use old ones to compile old projects)With my r27 I was able to build r1263. Now I just have to verify it boots and works and then I can start, thanks.
No, I think it'll have to be done directly in code. But, unless I make a stupid mistake with the patch, an update will not be necessary. The point of this change is that the patch itself is relatively small, and the actual code changes are downloaded from the server on each connect, so there shouldn't be the need to ever update this patcher.if you succeed, do you think it could be done by loading an external patch file?
Also, if I had other nands, how would I know it load one or the other nand? Is there a config file for setting that up?Different methods to launch/exit neek:
- If you use Bootmii@boot2, it launches sd:/bootmii/armboot.bin at launch (bypassing ALL splash screens and animations), which is a program replaced (not bootmii anymore) with a neek(2o) launcher, which loads SD:/sneek/kernel.bin.
- When you are on realNAND, nSwitch launches bootmii IOS. BootMii IOS launches sd:/bootmii/armboot.bin on SD card, which is replaced with a program to launch neek(2o) located on SD:/sneek/kernel.bin.
- Nswitch on vWii (not Wii) work the same way than USBLoaderGX, it doesn't use armboot.bin file at all, it loads sd:/sneek/kernel.bin directly
- USBLoaderGX uses the same method than nSwitch vWii, but improves it a little : it launches kernel.bin (not sd:/bootmii/armboot.bin), but loads from either SD OR USB based on your emuNAND path setting ! (no need to put bootmii and sneek files on both SD and USB)
- when you are on Neek, nSwitch reboot the console to go back to realNAND.
Ok thanks man I finally got it work for uneek+di and it loads pretty well, although it takes some time but that's ok.to launch neek from boot2, you need bootmii installed in boot2.
if your console is not vulnerable and you can only install bootmii as IOS (see in hackmii installer if you can or not) then you need priiloader to launch nswitch channel.
if you have bootmii, it's working by actually replacing the bootmii's armboot.bin with the from from neek.
When you generate sneek or uneek, you have a "copy to SD" folder. this contain a bootmii/armboot.bin file, this is what's used to boot the console at boot2 time.
if you have that file, and the console does not automatically boot, then it means you don't have bootmii installed into boot2, or else it would load that file from SD without the need of nswitch.
nSwitch is manually launching bootmii (as IOS) because the console couldn't load it (as boot2), which in both cases result in loading armboot.bin file.
I just have a folder that's called nand on my SD and my USB root. It's loading good from there too. So if I want to change it, I just rename it to nands and then put my "nand" folder on inside /nands/ that's how it should be right?if you have neek (not neek2o) you can have only one emuNAND, located on partition's root.
if you have neek2o, you can store the emuNAND into subfolders of /nands/ folder
example :
/nands/nand1/
nands/pal3.2E/
nands/ntsc4.3U/
nands/ntsc4.3J/
etc.
You mean to access the menu by pressing 1 right on the emunand? Then to go where it says like nands or something to change path?to choose the default folder to boot, there's a binary file in sneek folder which contains the path to the default path to use.
once in neek2o, access the hidden menu to switch the folder to use. it will auto-edit the file (don't edit it manually, it's not a text file, it's a binary). You can also use USBLoaderGX to set the path you want to use and boot a game, it will generate the binary config file too.
That's what I did but I only got a black screen at boot (since I'm loading it via boot2) and then the wii starts to blink on and off blue light.if you want sneek, regenerate neek from modmii, and copy the "copy to sd" content to your SD card. then put the /nands/ folder on SD.
yes, but remember to delete the emunand config file (as it'll have the old path stored in it. It'll be recreated automatically on next launch when it'll try to load the folder it finds)So if I want to change it, I just rename it to nands and then put my "nand" folder on inside /nands/ that's how it should be right?
yes.You mean to access the menu by pressing 1 right on the emunand? Then to go where it says like nands or something to change path?
I think blinking LED means it didn't find the nand path, or doesn't find what to load.That's what I did but I only got a black screen at boot (since I'm loading it via boot2) and then the wii starts to blink on and off blue light.
Hey @Cyan while you're here, figured I'd finally ask the question I've had for years now.yes, but remember to delete the emunand config file (as it'll have the old path stored in it. It'll be recreated automatically on next launch when it'll try to load the folder it finds)
yes.
I think blinking LED means it didn't find the nand path, or doesn't find what to load.
Sorry, meant to be a little more clear. Say I launch USB loader, play some MKWII, then go to the wii system menu, remove SD card, put it back in, then go launch USB loader, it gets stuck on initialize.it's a very bad thing to eject a mounted device without using "safe eject".
on windows, there's the option to safely eject, but on USBLoaderGX there is not.
if you launch USBLoaderGX with the SD card inserted, it create a virtual link to the mounted partition. this reference to that partition is different after every eject/reinsert, and you can corrupt the content of your SD card by doing that because the loader will still try to read/write data to the known mounting point stored in memory, while the card is not properly remounted. it can have many effect, from memory corruption, to console freeze or crash.
There's a "SD Remount" button you need to click if you ever insert an SD card AFTER launching the loader. but it shouldn't be used lightly for eject/reinsert purpose as currently opened transmitted flow will break and ends nowhere in memory.
Gotcha! Like I said, it's not an issue at all, just a weird thing I've noticed over the years. Thank you for your responseyeah, I edited my message
you saw it too soon ahaha.
So the config.bin is on the /nand folder right? I delete it. Ok.yes, but remember to delete the emunand config file (as it'll have the old path stored in it. It'll be recreated automatically on next launch when it'll try to load the folder it finds)
Made an account just to post this, I've run into a problem with Metal Slug Complete (NTSC-J). The game will run just fine but if I turn on a second Wii remote, a message that I'm assuming is supposed to be in Japanese but is in gibberish will pop up and I have to restart my Wii (only english word in the message is "OFF"). Anyone have a similar problem with the game and/or know how to fix it?
Are you making sure the extra remotes are already synced from the system menu? If you're using emuNAND for saves you also need to recopy the sysconf file in the loader's Features menu. The option is near the bottom of the list.
--------------------- MERGED ---------------------------
I cloned r1268 to here:
I'll get it compiling with the latest devkitPPC as soon as I can and post the changes there. I've been a bit busy lately.
I'll probably release 1269 as it is right now (I wanted to fix, change the boot sequence for hdd init issue and clean up the code style), but if you fix for pacman, and soon there'll be a fix for wiimmfi, I should release it to be up to date to apply your changes.I cloned r1268 to here: https://github.com/GreyWolfSC/UNEO
I'll get it compiling with the latest devkitPPC as soon as I can and post the changes there. I've been a bit busy lately.