Hacking SNEEK+DI quick guide

[anickname]

@anickname.

You really should start with a sneek setup (without DI) and work further from there.

I used the backup of my real nand (the bootmii backup) and extracted it with showmiinand / showmiiwad.
In between the lines I read that priiloader can cause issues. In my case, it's running, but only with minimal
hacks enabled. (No online update, no game update and auto press A upon health screen.)
I did install the HBC 1.07 as the 1.08 is not working in sneek/uneek and the installer isn't working either.

If you get sneek running that way, you know 2 things:

1. Your sd card is compatible and working fine.
2. Your emulated nand is working fine as well, so it can be copied to the harddrive for uneek tests.

I would suggest a test with sneek +di afterwards. If you see a game animation in the disc channel, you know your harddisc is compatible.

This will ensure that you have a proper extracted game on the correct location.

You can use the Crediar sneek installer to create your armboot.bin, kernel.bin and di.bin. If you don't have a usb gecko, turning on verbose output is useless.

I know such a step by step approach can be fustrating, but as I explained already before, without the usb gecko output from the starting sneek, it's difficult to find the issue.

If sneek and sneek+di are running, you can proceed with uneek/di.

Do you have bootmii as boot2 or only as ios?

Thank you for your answer.

The NAND that I'm using is generated with ModMii. Is a clean NAND, no priiloader, no red theme, no channel (Weather, News ....).
Sneek is running ok on this NAND.
Sneek + DI on this NAND is running ok first time, after that I get a black screen.
Uneek and Uneek + DI are not running ok, I get continuous flashes (see the movies).

In order to test Sneek / Uneek I always used clean generated NAND and like you said I should try to move
the NAND that worked with Sneek to the hdd and try Uneek.

Bootmii is installed as IOS.

 

[XFlak]

Sneek + DI on this NAND is running ok first time, after that I get a black screen.

Try deleting the cache\config files saved to the SNEEK folder

 

[obcd]

And also see if deleting channelcache.bin and diconfig.bin in the sneek folder makes it work again?

 

[anickname]

After 2 more retries with a clean NAND generated by ModMii, SNEEK + DI worked.
I haven't done anything special ....

The NAND that worked for SNEEK / SNEEK + DI I copied on both USB HDDs (40 GB and 500 GB),
and I got the same problem (dvd drive continuous flashes).

Note :
It seems that SNEEK+DI works well both with games in sd:/games and usb:/games.
That means that SNEEK+DI sees the USB HDD after boot.

 

[obcd]

So,

if you have a sneek folder on your usb drive and
the kernel.bin in that folder (the uneek kernel which is not the same as the sneek kernel)
the di.bin in that folder
the font file in that folder. (can't remember it's exact name..)

and you also have the same kernel.bin in the sneek folder of your sd card. (Again the uneek kernel.bin)

and you are sure that you copied all your nand subfolders to the root of your harddisk,

than, if it doesn't work, it almost has to be a harddisk issue.

There is not much more I can think off.

 

[anickname]

It seems that SNEEK+DI works well both with games in sd:/games and usb:/games.
That means that SNEEK+DI sees the USB HDD after boot.

 

[anickname]

So,

if you have a sneek folder on your usb drive and
the kernel.bin in that folder (the uneek kernel which is not the same as the sneek kernel)
the di.bin in that folder
the font file in that folder. (can't remember it's exact name..)

and you also have the same kernel.bin in the sneek folder of your sd card. (Again the uneek kernel.bin)

and you are sure that you copied all your nand subfolders to the root of your harddisk,

than, if it doesn't work, it almost has to be a harddisk issue.

There is not much more I can think off.

The files for UNEEK+DI are exactly like those described by you.

 

[obcd]

And you are 100% positive you didn't forgot a nand folder... I know it sounds stupid, but it's the only thing I can think right now.

 

[anickname]

And you are 100% positive you didn't forgot a nand folder... I know it sounds stupid, but it's the only thing I can think right now.

What do you mean by "nand folder" ?
All my nand folders are in sd:/ or usb:/.
Should they be in /nand ?

 

[obcd]

nope, the subfolders from the nand should be in the root of the sd and usb disc.
The subfolders are used by the switch2uneek program. It copies them to the root if you select a specific nand from one of the nand subfolders.

It could still also be an issue with the uneek kernel.bin. How did you create it? Sorry if that's already posted. I don't want to browse trough all the articles now. You could perhaps PM me a link to your bin files. I could test them in my setup to ensure they work. It would again be something we know is working.

 

[OverjoY]

@anickname: It seems it can't find the files on your USB device. Are you sure the partition you use = the first partition, primairy, active and the cluster size is 32kb or less?

Also folder structure should look like this if you're using a clean nand:

SD:/bootmii/armboot.bin
SD:/sneek/kernel.bin (boot2_usb.bin)

USB:/games/ With at least one DiscEx extracted game

USB:/sneek/kernel.bin (boot2_usb.bin)
USB:/sneek/di.bin
USB:/sneek/font.bin

USB:/shared1
USB:/ticket
USB:/title
USB:/sys/uid.sys

Nothing more nothing less

 

[Jehuty25]

When you say first parition, is it supposed to be like:
FAT32
NTFS?

Sorry for hijacking the thread, but I kinda have the same problem and I just wanted to make sure.

 

[anickname]

@obcd
The files are generated using ModMii 4.5.3.
These are my files :

URL removed from post.

Thank you for testing them.

@OverjoY
My directories structure is like that descibed by you.
Like I said the NAND is working for SNEEK/SNEEK+DI, but the same NAND is not working for UNEEK/UNEEK+DI.

@Jehuty25
I tried different partitioning schemes :

- 1 FAT32 partition
- 2 FAT32 partitions
- 1 FAT32 patition and 1 NTFS partition

All without success.
In all schemes the FAT32 partition was first, primary and active.

 

[obcd]

@anickname

I have just checked your files.
They work fine on my system.

This narrows the problem to your harddisk or your nand files.

What program do you use to check your disk partition type and cluster size?

Somehow there is something uneek doesn't like when it gets your nand from the harddisk.
The di module is not having problems with that.

As you have tried 2 different disks, the common factor between the 2 is the way they are partitionned.

 

[anickname]

@anickname

I have just checked your files.
They work fine on my system.

This narrows the problem to your harddisk or your nand files.

What program do you use to check your disk partition type and cluster size?

Somehow there is something uneek doesn't like when it gets your nand from the harddisk.
The di module is not having problems with that.

As you have tried 2 different disks, the common factor between the 2 is the way they are partitionned.

Can you tell me please, how your drive is partitioned and formated ?

 

[OverjoY]

When you say first parition, is it supposed to be like:
FAT32
NTFS?

Sorry for hijacking the thread, but I kinda have the same problem and I just wanted to make sure.
UNEEK only supports FAT32. The partition that UNEEK uses has to be the first partition, primairy, active and the cluster size has to be 32kb or less. The first partition has to be FAT32


QUOTE(anickname @ Apr 29 2011, 07:46 AM) In all schemes the FAT32 partition was first, primary and active.

And the cluster size is? Your issue has nothing to do with UNEEK, DI or the emu nand you're using. A flashing pattern like that is a problem within MINI not finding the required files for example

BTW. You're not allowed to share those files here in public as they contain copyrighted ninty stuff

 

[anickname]

When you say first parition, is it supposed to be like:
FAT32
NTFS?

Sorry for hijacking the thread, but I kinda have the same problem and I just wanted to make sure.
UNEEK only supports FAT32. The partition that UNEEK uses has to be the first partition, primairy, active and the cluster size has to be 32kb or less. The first partition has to be FAT32


QUOTE(anickname @ Apr 29 2011, 07:46 AM) In all schemes the FAT32 partition was first, primary and active.

And the cluster size is? Your issue has nothing to do with UNEEK, DI or the emu nand you're using. A flashing pattern like that is a problem within MINI not finding the required files for example

The 40 GB drive was formated using fat32format.exe with default setting which is 32KB cluster size.

http://www.ridgecrop.demon.co.uk/index.htm?fat32format.htm

I will check again.

 

[anickname]

BTW. You're not allowed to share those files here in public as they contain copyrighted ninty stuff

Sorry for that, I didn't knew.
I removed the url from post.

 

[obcd]

Which is why I asked you to PM the link...
Just edit that post and remove the link. It has furfilled it's purpose. I see you already did...

I used the same program to partition my disk.

There must be some mistake you are making over and over again. It's almost the only possibility.

 

[zizer]

try use hdd or usb flash with one partition