Hacking Neek2o for vWii?

  • Thread starter Thread starter Hephaestus
  • Start date Start date
  • Views Views 3,218
  • Replies Replies 12

Hephaestus

Well-Known Member
Member
Joined
Sep 29, 2017
Messages
335
Reaction score
151
Trophies
0
Age
38
XP
1,340
Country
Korea, North
I was trying to set up neek2o on my Wii U via the vWii.
Cant seem to find the right version.

Could anyone help me out?
 
The guide also shows you to get devkitpro and how to start the compilation.
The source code can still be obtained so there is no problem.
If it still compiles after the various changes to devkitpro in the meantime there should be no problem for you to accomplish it.
 
  • Like
Reactions: Hephaestus
The guide also shows you to get devkitpro and how to start the compilation.
The source code can still be obtained so there is no problem.
If it still compiles after the various changes to devkitpro in the meantime there should be no problem for you to accomplish it.
Alright, thank you!
Will give it a go.
 
@Hephaestus Ok the normal devkitPro installation lacks the arm-eabi-gcc tools and only offers the arm-none-eabi tools.
Maybe you need to install an older version that still includes those as I get errors when using the none-eabi ones.
 
  • Like
Reactions: Hephaestus
@Hephaestus Ok the normal devkitPro installation lacks the arm-eabi-gcc tools and only offers the arm-none-eabi tools.
Maybe you need to install an older version that still includes those as I get errors when using the none-eabi ones.
Just installed the devkit pro i found online.
Think i am in over my head here.
 
@Hephaestus
Oh sorry, I didn't read an instruction and made a mistake.
Until Compiling SNEEK everything works when following the guide.
As handling the commands that appear on Powershell/CMD is a pain, devkitpro ships with msys2 that has all devkitpro paths set up already.
So start the msys2 shell in C:\devkitPro\msys2\msys2_shell.cmd when the compilation step comes up.

As it is intended for linux, you need to change the IOSKpatch, elfins and efix occurences in build_boot2.sh to IOSKpatch.exe, elfins.exe and efix.exe .
As the default python in the msys2 shell is python3, you need to change "MAKEBIN = python makebin.py" in line 9 of the Makefile in mini-tree-mod to "MAKEBIN = python2 makebin.py" and if there is still an error when compiling with command not found or something, install it with "pacman -S python2".
Then change the working directory to the path you downloaded the svn code to, paths now use "/" instead of "\" so if the downloaded code is on your desktop you get to the path with "cd /c/Users/yourname/Desktop/sneek-read-only"
Then use the bash script build_boot2.sh via the command "./build_boot2.sh".

Then everything compiles and as the next steps involve no compiling, the rest should work without problems.
 
Last edited by Wuigi,
  • Like
Reactions: Hephaestus
@Hephaestus
Oh sorry, I didn't read an instruction and made a mistake.
Until Compiling SNEEK everything works when following the guide.
As handling the commands that appear on Powershell/CMD is a pain, devkitpro ships with msys2 that has all devkitpro paths set up already.
So start the msys2 shell in C:\devkitPro\msys2\msys2_shell.cmd when the compilation step comes up.

As it is intended for linux, you need to change the IOSKpatch, elfins and efix occurences in build_boot2.sh to IOSKpatch.exe, elfins.exe and efix.exe .
As the default python in the msys2 shell is python3, you need to change "MAKEBIN = python makebin.py" in line 9 of the Makefile in mini-tree-mod to "MAKEBIN = python2 makebin.py" and if there is still an error when compiling with command not found or something, install it with "pacman -S python2".
Then change the working directory to the path you downloaded the svn code to, paths now use "/" instead of "\" so if the downloaded code is on your desktop you get to the path with "cd /c/Users/yourname/Desktop/sneek-read-only"
Then use the bash script build_boot2.sh via the command "./build_boot2.sh".

Then everything compiles and as the next steps involve no compiling, the rest should work without problems.
I built the files before your edit. Only edited the python-part.
Should i built it again with your proposed changes?
 
@Hephaestus If there were no errors and you got the .bin files it's not necessary.
I guess I must have deleted the devkitpro path from my system environment variables someday so you didn't need to do it and could just use the build_boot2.cmd instead.
 
Last edited by Wuigi,
  • Like
Reactions: Hephaestus
@Hephaestus If there were no errors and you got the .bin files it's not necessary.
I guess I must have deleted the devkitpro path from my system environment variables someday so you didn't need to do it.
Yeah, i got all the bin files!
The guide says to use "kernel_sd.bin".
what are the "_di" bins?
Could i possibly do this from USB as well, or would that mean i could not access my USB HDD in my neek-nand?
 

Site & Scene News

Popular threads in this forum