Hacking SNEEK+DI quick guide

[longtom1]

I think hard drive compatibility is broken on uneek/uneek_di cause I can get it to boot on 1 hard drive out of 6 all have fat32 32k clusters and active primary partitions and work for games in sneek_di

 

[sk0ld]

There's a bug that was thought to have been killed off in r110, and seems to affect UNEEK only.
To successfully boot the latest revision of UNEEK using the kernel from IOS80, (which you should be using) you must patch your system menu executable for verbose PPC output. So for example, the dol for 4.3U is usb:\title0000100002\content00098.app (3.68MB)
IOSkpatch 00000098.app patched.app -p

 

[NReale3370]

There's a bug that was thought to have been killed off in r110, and seems to affect UNEEK only.
To successfully boot the latest revision of UNEEK using the kernel from IOS80, (which you should be using) you must patch your system menu executable for verbose PPC output. So for example, the dol for 4.3U is usb:\title0000100002\content00098.app (3.68MB)
IOSkpatch 00000098.app patched.app -p

would/could this also affect sneek-di with a usb flash drive? I haven't heard of this before and I haven't been able to get sneek-di or uneek to work with my flash drive in the latest revision (or any revision for uneek)

 

[sk0ld]

Nope. SNEEK(+DI) works just fine. As I stated, the problem seems specific to UNEEK.

 

[longtom1]

There's a bug that was thought to have been killed off in r110, and seems to affect UNEEK only.
To successfully boot the latest revision of UNEEK using the kernel from IOS80, (which you should be using) you must patch your system menu executable for verbose PPC output. So for example, the dol for 4.3U is usb:\title0000100002\content00098.app (3.68MB)
IOSkpatch 00000098.app patched.app -p

thanks for the info thought something needed patching but wasn't sure

 

[NReale3370]

Yeah that didn't help me any

 

[koiulpoi]

Maybe somebody can help me. I'm trying to run Uneek, and have had a couple different issues.

1) Using the r110 pack uploaded by Mddy, I can get a NAND to boot once, and never again. Doesn't matter if it's my own or a virgin one. (edit: just tried the "patch the system menu" trick earlier in this thread; like the others, did nothing. still get a nice black screen)

So, I downloaded PUneek.

It runs the NAND just fine, but it has an interesting issue: any time I try to launch a channel, it freezes with a black screen. The next time I launch it, it loads into the channel I was trying to load earlier, instead of the system menu. The homebrew channel is unable to actually load anything, as far as I can tell.

Anyone have any ideas?

 

[longtom1]

nope same here patching the 0000009b.app for 4.3E 3.778kb didn't work

Edit Scratch what I just said it does work just not with the first hard drive I tried

 

[twig123]

So, I downloaded PUneek.

It runs the NAND just fine, but it has an interesting issue: any time I try to launch a channel, it freezes with a black screen. The next time I launch it, it loads into the channel I was trying to load earlier, instead of the system menu. The homebrew channel is unable to actually load anything, as far as I can tell.

I have this same issue with SNEEK+DI...

 

[ChokeD]

Please just use the latest revision with 0000000e.app from IOS80 and 00000001.app IOS60, even if other (IOS) versions seem to work all tools have been adjusted for those certain versions and certain patches might not work or things crash!

If I had space in my signature for this it would be there.

 

[longtom1]

is there going to be a fix for the next revision on the svn???

 

[retrohead]

nope same here patching the 0000009b.app for 4.3E 3.778kb didn't work

Edit Scratch what I just said it does work just not with the first hard drive I tried

Would this be the same for 4.2E do you know?

 

[ricerobo]

QUOTE(SanGor @ Jul 28 2010, 04:30 AM) Please just use the latest revision with 0000000e.app from IOS80 and 00000001.app IOS60, even if other (IOS) versions seem to work all tools have been adjusted for those certain versions and certain patches might not work or things crash!

This time, I compiled SNEEK r110 according to the guide of this forum, using IOS80-64-v6943 0000000e.app and IOS60-v6174 00000001.app.
Then I have confirmed that SNEEK r110 works properly.
Honestly I don't know which combination of 0000000e.app and 00000001.app is proper.

 

[ChokeD]

QUOTE(SanGor @ Jul 28 2010, 04:30 AM) Please just use the latest revision with 0000000e.app from IOS80 and 00000001.app IOS60, even if other (IOS) versions seem to work all tools have been adjusted for those certain versions and certain patches might not work or things crash!

This time, I compiled SNEEK r110 according to the guide of this forum, using IOS80-64-v6943 0000000e.app and IOS60-v6174 00000001.app.
Then I have confirmed that SNEEK r110 works properly.
Honestly I don't know which combination of 0000000e.app and 00000001.app is proper.

The quote above is correct, the guide was right until this past week when a lot of things have and still are changing within SNEEK. I am just waiting to re/write the guide to a proper format until crediar commits a new rev because as of now you have to change this and change that and rename this and add this code and crap just to get a working version of sneek and then it only works for some and not for others.

 

[twig123]

QUOTE(SanGor @ Jul 28 2010, 04:30 AM) Please just use the latest revision with 0000000e.app from IOS80 and 00000001.app IOS60, even if other (IOS) versions seem to work all tools have been adjusted for those certain versions and certain patches might not work or things crash!

This time, I compiled SNEEK r110 according to the guide of this forum, using IOS80-64-v6943 0000000e.app and IOS60-v6174 00000001.app.
Then I have confirmed that SNEEK r110 works properly.
Honestly I don't know which combination of 0000000e.app and 00000001.app is proper.

The quote above is correct, the guide was right until this past week when a lot of things have and still are changing within SNEEK. I am just waiting to re/write the guide to a proper format until crediar commits a new rev because as of now you have to change this and change that and rename this and add this code and crap just to get a working version of sneek and then it only works for some and not for others.

Nice info to know... Strange how the SNEEK Google Code and every guide I run across still says to use IOS70 instead of IOS80...
Maybe tomorrow I'll try to compile with IOS80 to see if it works for me

Things change so often, thanks for trying to keep the guide updated

 

[ChokeD]

I've been working on new pics and adding info. I have not deleted any info yet and won't until I see it as a must.

This is basically an announcement:

CURRENTLY UNDER CONSTRUCTION, DO NOT PAY ATTENTION TO THE MAN BEHIND THE CURTAIN,
THIS GUIDE IS NOT PRACTICAL FOR ANY APPLICATION UNTIL ANOTHER REVISION IS RELEASED, USE AT YOUR OWN RISK OF LOST TIME

I'm going to bed, goodnight all,
ChokeD

 

[MaK11-12]

Hi guys,
Well first off, my sneek and uneek install did not work, it would just flash the dvd drive.
So i compiled the new 110 source myself with no errors. Now when i load UNEEK the disk drive flashes 3 times, pauses, then repeats.
What am i doing wrong?
My wii is 4.2E
The nand on USB is the one from the "How To Achieve a NAND for use with SNEEK" guide.
I have also installed ios35 with all patches.

Edit:
Nevermind, a quick search on GBAtemp and i found a rename of boot2.bin to kernel.bin and movement to to the X:\sneek\ folder on both SD and USB got it working.

 

[longtom1]

R111

mini-mod:
-mini now does three short flashes if it couldn't open or read the /sneek/kernel.bin

 

[moosehunter]

So, I downloaded PUneek.

It runs the NAND just fine, but it has an interesting issue: any time I try to launch a channel, it freezes with a black screen. The next time I launch it, it loads into the channel I was trying to load earlier, instead of the system menu. The homebrew channel is unable to actually load anything, as far as I can tell.

I have this same issue with SNEEK+DI...

Someone doesn't have kernel.bin on their usb drive

 

[ChokeD]

r111 still has a di.bin 0KB in size. I would imagine we'll see a higher revision soon.
I'm still getting a "no such directory found" error.


This has been updated in the guide to reflect the changes made in r107+


File Structure for SNEEK, SNEEK+DI, UNEEK and UNEEK+DI.

Spoiler

Filestructure for SNEEK DI:
sd:\bootmii\armboot.bin
sd:\sneek\di.bin
sd:\sneek\kernel.bin (renamed boot2_di.bin)
sd:\sneek\font.bin
NAND
sd:\import
sd:\meta
sd:\shared1
sd:\shared2
sd:\temp
sd:\title

usb:\games\a_game example: usb:\games\RMGE01
----------------------------------------------------------------
Filestructure for SNEEK:
sd:\bootmii\armboot.bin
sd:\sneek\kernel.bin (boot2_sd.bin)
NAND
sd:\import
sd:\meta
sd:\shared1
sd:\shared2
sd:\temp
sd:\title

usb:\games\a_game example: usb:\games\RMGE01
-----------------------------------------------------------------
Filestructure for UNEEK:
sd:\bootmii\armboot.bin
sd:\sneek\kernel.bin (boot2_usb.bin)

usb:\sneek\kernel.bin (boot2_usb.bin)
NAND
usb:\import
usb:\meta
usb:\shared1
usb:\shared2
usb:\temp
usb:\title
usb:\games\a_game example: usb:\games\RMGE01
-----------------------------------------------------------------
Filestructure for UNEEK+DI:
sd:/bootmii/armboot.bin
sd:/sneek/kernel.bin (renamed boot2_usb.bin)

usb:/sneek/di.bin
usb:/sneek/kernel.bin (renamed boot2_usb.bin)
usb:/sneek/font.bin
NAND
usb:\import
usb:\meta
usb:\shared1
usb:\shared2
usb:\temp
usb:\title
usb:\games\a_game example: usb:\games\RMGE01

Place files respectively and boot your wii

CURRENTLY UNDER CONSTRUCTION, DO NOT PAY ATTENTION TO THE MAN BEHIND THE CURTAIN,
THIS GUIDE IS NOT PRACTICAL FOR ANY APPLICATION UNTIL ANOTHER REVISION IS RELEASED, USE AT YOUR OWN RISK OF LOST TIME