Hacking SNEEK+DI quick guide

[ChokeD]

no it's not, but I would add it if it gets explained.

 

[SanGor]

it's in the options tab called "Video mode patch", Press B after opening the SNEEK menu.

 

[ChokeD]

ah, I wondered what that did, thanks SanGor.

 

[Cyan]

It's working

Thank you !

 

[ChokeD]

Yes thanks much and added to the op.

NOTE2: To access the SNEEK configuration press "2" on the Wiimote.
in the SNEEK configuration,
Use the Video Patch Mode, referred to as the VI, To patch the region of a game that does not match the region of the SNEEK NAND being used.

 

[SanGor]

Yes thanks much and added to the op.

NOTE2: To access the SNEEK configuration press "2" on the Wiimote.
in the SNEEK configuration,
Use the Video Patch Mode, referred to as the VI, To patch the region of a game that does not match the region of the SNEEK NAND being used.

not 2, B!

 

[ChokeD]

my bad it is B isn't it !!!

 

[Cyan]

And you need to be in the game menu first.

1 -> game list -> B to open it. Pressing B again to close it.
B only on the system menu doesn't work.

 

[scooby74029]

hey guys

heres stuff
sysmenu4.2
ios80
uneek_di r114
verbitum 250gig hd 104 games

i love uneek+di so far tested 40 of the games and they all work so far. Ill post if any of them dont

 

[ChokeD]

NOTE2: To access the SNEEK configuration,
press "1" -> in the SNEEK game menu -> press "B" to open it. Pressing "B" again closes the configuration box.
Video Patch Mode, referred to as the VI, patches the region of a game that does not match the region of the SNEEK NAND being used.




Thanks for the help guys.

 

[ChokeD]

I have recently made A LOT of changes to the guide.

1.) updated some pix to reflect new versions of apps being used
2.) re-worded a lot of things to explain more thoroughly
3.) added code boxes in places to pinpoint command prompt typing illustrations
4.) added a USB for SNEEK preparation section
5.) changed the order of the Spoilers to emphasize procedures
6.) combined 2 spoilers that were based on NAND building
7.) deleted a how to for installing HBC that was not needed.
8.) placed the 4.3 spoiler at the bottom until more info is given or useful to the guide
9.) still organizing downloads, steps and anything else, to reflect necessity
10.) a lot of spelling corrections from other users "HOW TO's"

I hope everything is satisfactory to everyone's needs and wants. Take a look, if you feel changes need to be made, let me know and I'll see what I can do.

 

[Cyan]

7) about the HBC install, I followed the one saying "What I did to install mine"
But, I had difficulties because I didn't find the correct menu/option.

It says "extract HBC.wad from Bootmii nand using ShowmiiWad"

But, I didn't find where to load the bootmii nand to show its content, only an option to fully extract the nand to FS dump files.
Then I mounted the FS dump directory, to access the content of the nand.


So either I missed a step (because the guide ask to extract bootmii nand later), or you should modify a little the guide, something like that :

Have HBC(JODI) installed on real nand 3.2 or 4.2x
dump real nand using bootmii
Open showmiiwads, go to "tools/extract Bootmii nand" and select your nand.bin
when extraction is complete, go to "option/change NAND backup path" and select the new created folder named "nand-extracteda" where your nand.bin is located.
Go to "View/ShowmiiNand"
Right click on your HBC(JODI) and select "Pack Wad" and save it, ex. HBC(JODI).wad
Go back to your VIRGIN Sneek nand, by selecting your sneek drive letter in "Options/Change NAND backup path"
Right click and choose "Install/file", select your HBC(JODI).wad, and once installed close ShowmiiWads.
Then manually copy and replace your original Bootmii NAND/ticket/00010001/4a4f4449.tik to Sneek NAND/ticket/00010001/4a4f4449.tik
your done. Test it.


Maybe that's longer and not well explained (Someone told me my english was poorly worded >.>), but there's more step by step.

 

[ChokeD]

Your point is valid, thanks for noticing. I am in the process of making pix and re-doing this process right now. It may take me 15 minutes but I will get it fixed properly. Thanks again for proofing my work.

 

[twig123]

Bootmii NAND/ticket/00010001/4a4f4449.tik

fk! Thats why my HBC was lame (had scam warning)! I grabbed mine from 'title' instead of 'ticket'. DOH!

 

[twig123]

This info was added as of R112. It would be nice to have in the Troubleshooting/Error section:

-added slot blinking on fatal errors
1 short flash : The TMD of the requested title is missing
2 short flashes: The TMD of the IOS the current title uses is missing
3 short flashes: The kernel.bin is not found on sd and or usb
4 short flashes: Failed to load the requested IOS (missing IOS, missing
TMD/Ticket/content)

 

[Digital1980]

This info was added as of R112. It would be nice to have in the Troubleshooting/Error section:

-added slot blinking on fatal errors
1 short flash : The TMD of the requested title is missing
2 short flashes: The TMD of the IOS the current title uses is missing
3 short flashes: The kernel.bin is not found on sd and or usb
4 short flashes: Failed to load the requested IOS (missing IOS, missing
TMD/Ticket/content)

how about "hang at a black screen"

Is there a troubleshooting explanation for that?

 

[NReale3370]

This info was added as of R112. It would be nice to have in the Troubleshooting/Error section:

-added slot blinking on fatal errors
1 short flash : The TMD of the requested title is missing
2 short flashes: The TMD of the IOS the current title uses is missing
3 short flashes: The kernel.bin is not found on sd and or usb
4 short flashes: Failed to load the requested IOS (missing IOS, missing
TMD/Ticket/content)

how about "hang at a black screen"

Is there a troubleshooting explanation for that?

I'm voting a cross between armboot.bin problems and/or usb drive incompatibilities (since I'm getting that on any usb related sneek)

 

[Digital1980]

I'm voting a cross between armboot.bin problems and/or usb drive incompatibilities (since I'm getting that on any usb related sneek)

I should also add that I updated to HBC 1.0.7 today, could that be also be part of the problem?

I've been swapping out different SD cards (just trying to get SNEEK and SNEEK+DI working for now).

the armboot.bin creates itself with a size of 44kb which I think is correct. I'm on 4.2

 

[ChokeD]

This info was added as of R112. It would be nice to have in the Troubleshooting/Error section:

-added slot blinking on fatal errors
1 short flash : The TMD of the requested title is missing
2 short flashes: The TMD of the IOS the current title uses is missing
3 short flashes: The kernel.bin is not found on sd and or usb
4 short flashes: Failed to load the requested IOS (missing IOS, missing
TMD/Ticket/content)

Adding this now, Thank you.


Adjustments just made and finished:

How to install HBC to SNEEK NAND

Spoiler

This is how I installed my HBC To SNEEK NAND

Spoiler

:
1.) Have HBC(JODI) installed on real nand 3.2x-4.2x
2.) dump real nand using bootmii
3.) Open showmiiwads, go to "tools/extract Bootmii nand" and select your nand.bin

4.) when extraction is complete, go to "option/change NAND backup path" and select the new created folder named "nand-extracteda" where your extracted NAND is located.

5.) Go to "View/ShowmiiNand"

6.) Right click on your HBC(JODI) and select "Pack Wad" and save it, ex. HBC(JODI).wad

7.) Go back to your VIRGIN Sneek nand, by selecting your sneek drive letter in "Options/Change NAND backup path"
8.) Right click and choose "Install/file", select your HBC(JODI).wad, and once installed close ShowmiiWads.

9.) Then manually copy and replace your original Bootmii NAND/ticket/00010001/4a4f4449.tik to Sneek NAND/ticket/00010001/4a4f4449.tik

10.) your done. Test it.

 

[ChokeD]

I'm voting a cross between armboot.bin problems and/or usb drive incompatibilities (since I'm getting that on any usb related sneek)

I should also add that I updated to HBC 1.0.7 today, could that be also be part of the problem?

I've been swapping out different SD cards (just trying to get SNEEK and SNEEK+DI working for now).

the armboot.bin creates itself with a size of 44kb which I think is correct. I'm on 4.2

My di.bin was 44kb on 111 and now that I'm on 114 it has changed to 33kb. Both tested and worked.

EDIT: I might add my 111 di.bin was patch, 114 di.bin is not.