Hacking SNEEK+DI quick guide

[obcd]

When I used my real nand for uneek, it had priiloader 0.7 installed on it.
It worked.
I don't know about hacks_hash.ini, and there is the freezing issue if you go into setup which is instantly if I remember well.

 

[Etheboss]

Yep, i had a nand where i had priiloader 0.7 installed...worked except for the ten second freeze, that is still there...

NOTE: i manually copied priiloader 0.7 from a dump of my real nand to the emunand build by modmii.

When i have time, i will check if the hacks_hash.ini can be used...

 

[XFlak]

if it works, it'd be awesome if u could also show me a pic of the folder structure of nand:\title00000010000002\data\ after settings some system menu hacks using hacks_hash.ini? I can't remember what priiloader renames hacks_hash.ini when copied over to the nand. And if hacks_hash.ini don't doesn't work, u can always copy it the file to the emunand manually and see if that makes a difference. But I'm pretty sure when I did my testing with priiloader v0.7 running off uneek+di it didn't work for me using hacks_hash, I had to change the settings to use the classic hacks.ini for it to work... that being said, I can't remember where I had hacks_hash saved so I could have made a mistake, it may have been on the root of the sd card (not in the sd:\apps\priiloader\ folder like the latest priiloader expects), but I'm pretty sure I also copied the the hacks_hash file directly to the emunand... I definitely did with hacks.ini on v0.4 and that worked like a charm, but I can't recall v0.7

 

[Etheboss]

@XFlak, i can remember there was a discussion about the ten sec. freeze (when you enter the priiloader menu in Sneek), there was a way to stop the freeze, i also can remember you were in the discussion as well. Can you remember it, and if so, can you remember how it is done?

BTW. how is your dutch, if i take a screenshot of my windows explorer it will be partly dutch..

 

[XFlak]

ppl have claimed that launching the priiloader magicword.dol either via the HBC or a forwarder channel (ie. my Priiloader Forwarder Channel) while running the emulated nand will allow you to access priiloader on your emulated nand without freezing ONLY IF BOOTMII IS INSTALLED TO BOOT2. If bootmii is only installed as IOS, when the magicword.dol resets the Wii, it will boot into the priiloader that's installed on the real nand (if its installed, otherwise it'll boot the the real nand's system menu)

 

[obcd]

i found a method by launching the priiloader boot.dol. I changed the sources a little so that the magic word Daco is set. This makes it go to it's setup screen.
If you change some settings for that booted dol, those of the real priiloader are changed as well. So it basically acts as an editor for the priiloader setting file.
It worked fine for my priiloader 0.7 that was on the uneek backup of my real nand (4.2 menu). It gives problems on my modmii build 4.3 nand. For the moment,
I have no clue what the problem might be. The priiloader 0.7 on the modmii nand doesn't launch programs well either. After a while, they freeze when they are launched that way.
When I tested on my real 4.2 nand, everything was working fine. Maybe it's because I just copied the 0.7 app file to the nand folder, while on the real nand it was installed before I took the nand dump.

 

[skx7]

is uneek+di able to boot from ntfs usb hdd?

 

[bazamuffin]

See page 1 and setting up SD/USB

 

[skx7]

i know the past... im just wondering whether it now already supports ntfs as usb loaders all seem to support ntfs nowadays.

i have uneek+di working but would like to format my usb drive as ntfs. only uneek+di is blocking me right now...

 

[scooby74029]

sneek/uneek only work with FAT32 formatted drive and 32kb cluster size

THATS IT

 

[dracula]

I checked the troubleshooting section in the opening post, but it doesn't mention the case "Wii disc light keeps flashing slowly and continuously".

I'm currently using a self-made full NAND dump on my USB HD (FAT32 as first and active partition). That NAND dump works fine with Mighty Channels. I've also tried creating a fresh NAND with the SNEEK setup in ModMii. Either way, it always takes about 1 minute (without TV signal) before the disc light starts flashing non-stop.

Where do I begin checking what is wrong?

 

[obcd]

Start to try to get sneek running first. It will prove that your nand image is working as expected.
After that, you can replace the sneek kernel.bin with the uneek kernel.bin, and copy the nand over to your usb drive.
You will also need a sneek folder on your usb drive with the same kernel.bin in it. If that also works, you can add the di module and font.bin to the sneek folder of your usb drive.

Some say you need at least one game on your usb drive with uneek + di, others say it's not needed. As your goal is probably to play backup's, you might as well put a game on your drive.

I have seen harddisks that work fine with usb loaders and not with uneek. Uneek couldn't recognise the drive altough it was partitionned and formatted as expected.

 

[SanGor]

when using DI, the system menu WON'T boot without a game!!!

 

[zizer]

http://code.google.com/p/sneek/wiki/FAQDI

 

[OverjoY]

UNEEK+DI boots fine without a game

 

[kylster]

sneek/uneek only work with FAT32 formatted drive and 32kb cluster size

THATS IT

Sorry Scoob but cluster size needs to be either 16kb or 32kb both are supported. I'm using a 16kb cluster size atm.

 

[zizer]

The FAT lib used doesn't seem to work with 64K cluster size, assure that you use a smaller size

http://code.google.com/p/sneek/wiki/FAQ

 

[dracula]

Start to try to get sneek running first. It will prove that your nand image is working as expected.
After that, you can replace the sneek kernel.bin with the uneek kernel.bin, and copy the nand over to your usb drive.
You will also need a sneek folder on your usb drive with the same kernel.bin in it. If that also works, you can add the di module and font.bin to the sneek folder of your usb drive.

Some say you need at least one game on your usb drive with uneek + di, others say it's not needed. As your goal is probably to play backup's, you might as well put a game on your drive.

I have seen harddisks that work fine with usb loaders and not with uneek. Uneek couldn't recognise the drive altough it was partitionned and formatted as expected.

Thanks, that's indeed a smart approach.

I started with sneek and a fresh NAND, and that works perfectly.

I copied that NAND to the USB partition (FAT32, first, active), and made sure both usb and sd were uneek-ready (no DI). Now after turning on the Wii, it takes about 20 seconds before the USB drive is powered on, and then another 40 seconds before the Wii disc light starts flashing non-stop. I'm using a Western Digital My Passport Essential 500 Gb (USB 3.0), which seemed to score pretty good in compatibility overall.

Can I now draw the conclusion that uneek will simply not work with this hard disk? Is there any way to get more debug info, or info about the disc light flashing?

 

[obcd]

Those Western Digital passport drives are junk. The problem with WD is that they changed the drive electronics to be usb 3.0 compatible and they kept the name of the drive.
So, the drives that are listed as being compatible are the older not usb 3.0 compatible ones. I bought 2 of them as well as they are good priced, and I ended up using none of them on my wii. The usb interface is integrated in the drive electronics and the housing is sealed, so you can't even use those drives as a normal laptop drive.

My advice is, stop wasting your time and find yourself another drive. I was pretty pi**ed myself when I realised that my WD's I had carefully selected from the list of being compatible didn't work.

I remember they did sometimes work, either with usbloader_gx or with the HBC, but never reliable. One time it worked, the next run it didn't anymore.

So I bought an external usb enclosure and a normal laptop drive. The enclosure was only 16 euro, and I could return the drive if it didn't work, or use it for something else. The drives power consumption was 0.55 amps which is a little over the maximum usb allowed 0.5 amps, but it wrks without problem. I also hear about people having good results with Seagate (Freeagent series I think). This system is also based on a standard harddisk. The usb interface is detachable, and you can choose to use both an usb 3.0 for your pc and an usb 2.0 for your wii. It's a bit more expensive than my el chepo external housing solution, but you wil have the guarantee that it works.

If you really want more information about what is going wrong, an usb gecko is what you need. Your flashing pattern seems to be the one flash... The delay is probably caused by the several retries in an attempt to get the disc running.

 

[shortz1994]

Start to try to get sneek running first. It will prove that your nand image is working as expected.
After that, you can replace the sneek kernel.bin with the uneek kernel.bin, and copy the nand over to your usb drive.
You will also need a sneek folder on your usb drive with the same kernel.bin in it. If that also works, you can add the di module and font.bin to the sneek folder of your usb drive.

Some say you need at least one game on your usb drive with uneek + di, others say it's not needed. As your goal is probably to play backup's, you might as well put a game on your drive.

I have seen harddisks that work fine with usb loaders and not with uneek. Uneek couldn't recognise the drive altough it was partitionned and formatted as expected.

Thanks, that's indeed a smart approach.

I started with sneek and a fresh NAND, and that works perfectly.

I copied that NAND to the USB partition (FAT32, first, active), and made sure both usb and sd were uneek-ready (no DI). Now after turning on the Wii, it takes about 20 seconds before the USB drive is powered on, and then another 40 seconds before the Wii disc light starts flashing non-stop. I'm using a Western Digital My Passport Essential 500 Gb (USB 3.0), which seemed to score pretty good in compatibility overall.

Can I now draw the conclusion that uneek will simply not work with this hard disk? Is there any way to get more debug info, or info about the disc light flashing?



QUOTE(obcd @ Jun 15 2011, 02:20 AM)

Those Western Digital passport drives are junk. The problem with WD is that they changed the drive electronics to be usb 3.0 compatible and they kept the name of the drive.
So, the drives that are listed as being compatible are the older not usb 3.0 compatible ones. I bought 2 of them as well as they are good priced, and I ended up using none of them on my wii. The usb interface is integrated in the drive electronics and the housing is sealed, so you can't even use those drives as a normal laptop drive.

My advice is, stop wasting your time and find yourself another drive. I was pretty pi**ed myself when I realised that my WD's I had carefully selected from the list of being compatible didn't work.

I remember they did sometimes work, either with usbloader_gx or with the HBC, but never reliable. One time it worked, the next run it didn't anymore.

So I bought an external usb enclosure and a normal laptop drive. The enclosure was only 16 euro, and I could return the drive if it didn't work, or use it for something else. The drives power consumption was 0.55 amps which is a little over the maximum usb allowed 0.5 amps, but it wrks without problem. I also hear about people having good results with Seagate (Freeagent series I think). This system is also based on a standard harddisk. The usb interface is detachable, and you can choose to use both an usb 3.0 for your pc and an usb 2.0 for your wii. It's a bit more expensive than my el chepo external housing solution, but you wil have the guarantee that it works.

If you really want more information about what is going wrong, an usb gecko is what you need. Your flashing pattern seems to be the one flash... The delay is probably caused by the several retries in an attempt to get the disc running.

that's all i have two western digital hardrives an neither one has given me any problems, one is 500gb an the other is a 300gb.. the 500 gb has all my nand, homebrew an uneek on it, boots every time with out a problem, same with the smaller one. 300gb. never a problem.. to me seagates are the worst. so not sure whats going on.. by the way both are 3.0- 2.0 compatible.. they are the passport. smaller then a pack of smokes..