Hacking SNEEK+DI quick guide

  • Thread starter Thread starter ChokeD
  • Start date Start date
  • Views Views 592,155
  • Replies Replies 3,091
  • Likes Likes 4
Wow, I feel really stupid. I figured out my error that was causing the menu not to show up. When I was testing the SDStatus change, I switched to a larger SD card... that I somehow forgot to copy font.bin to.
blush.gif


Also, anyone have any idea what _ _fwrite patch is, in practical terms?
 
I have previously questioned about the display of SNEEK+DI menu.
But I have not yet got the information about it.

I use JPN console Wii(4.2J).
I can make sure of good works on SNEEK,SNEEK+DI,UNEEK by using a 4.2J virgin NAND.
In the case of SNEEK+DI,I have recognized the game title in the disc drive channel,and I could play the game properly.
But I have not got the display of SNEEK+DI menu.
Off course,I have connected the GC controller to the port1 before booting the Wii.

I think that I cannot access the SNEEK+DI menu by using a 4.2J NAND.
Can I access the SNEEK+DI menu by using a 4.2U or 4.2E NAND?

I appreciate anyone who has good opinions.
 
I dumped my NAND again with FSDump, did the whole thing all over again, and I still get a black screen and my Wii freezes when I try to load BootMii from HBC. If I reinstall BootMii over my Sneek DI boot2 and armboot, I get the normal BootMii screen but that doesn't do me much good.
 
Luriden said:
I dumped my NAND again with FSDump, did the whole thing all over again, and I still get a black screen and my Wii freezes when I try to load BootMii from HBC. If I reinstall BootMii over my Sneek DI boot2 and armboot, I get the normal BootMii screen but that doesn't do me much good.

I think you should regulate the timing of connecting the USB drive to the Wii.
I have made sure of good works on SNEEK+DI
After booting the Wii in the condition of inserting the SD,the disc drive blinks blue and disappear. Just the timing of disappearance blinking blue,I connects the USB drive to the Wii.
 
ricerobo said:
Luriden said:
I dumped my NAND again with FSDump, did the whole thing all over again, and I still get a black screen and my Wii freezes when I try to load BootMii from HBC. If I reinstall BootMii over my Sneek DI boot2 and armboot, I get the normal BootMii screen but that doesn't do me much good.

I think you should regulate the timing of connecting the USB drive to the Wii.
I have made sure of good works on SNEEK+DI
After booting the Wii in the condition of inserting the SD,the disc drive blinks blue and disappear. Just the timing of disappearance blinking blue,I connects the USB drive to the Wii.

It's got nothing to do with the USB though, and I'm not concerned with USB at the moment anyway. I can't even get Sneek DI to run from the SD card at all. I have yet to run Sneek of any kind on this Wii.
 
I have installed bootmii as boots and IOS254.
In the case of your Wii,I think that you should after launching bootmii from HBC in the condition of inserting the SD,......
 
__fwrite() is one of the functions that's called by the OSReport debug chain.
OSReport -> vprintf -> __FileWrite -> __fwrite()

the patch makes the data that's supposed to be sent to the normal debug method be sent over EXI ( usbgecko )

edit:
before someone comes in trying to correct the chain, yes, vprintf doesn't call __FileWrite(), it passes it as an argument to another function that parses the format string and arguments into one string. that string is then passed to __FileWrite()
 
megazig said:
__fwrite() is one of the functions that's called by the OSReport debug chain.
OSReport -> vprintf -> __FileWrite -> __fwrite()

the patch makes the data that's supposed to be sent to the normal debug method be sent over EXI ( usbgecko )

Thank you, that was very helpful.
 
Luriden said:
It's got nothing to do with the USB though, and I'm not concerned with USB at the moment anyway. I can't even get Sneek DI to run from the SD card at all. I have yet to run Sneek of any kind on this Wii.
You need a hard drive connected with at least one game installed for sneek Di to boot also you need the DI.bin and font.bin on the root of the usb drive also if I don't have a drive connected I just get black screen the timing method explained a few posts earlier works for some hard drives and others will just boot without any fiddling
 
I read some posts on this topic, but still can not understand what sneek help you do.

I mean i know it emulates the nand but what can I do with that? What are the features I gain?
 
longtom1 said:
Luriden said:
It's got nothing to do with the USB though, and I'm not concerned with USB at the moment anyway. I can't even get Sneek DI to run from the SD card at all. I have yet to run Sneek of any kind on this Wii.
You need a hard drive connected with at least one game installed for sneek Di to boot also you need the DI.bin and font.bin on the root of the usb drive also if I don't have a drive connected I just get black screen the timing method explained a few posts earlier works for some hard drives and others will just boot without any fiddling


execute bootmii, wait for black screen. Let hang, then plug in uSB drive and watch disk drive flash the blue light and sneek boots up.

works for me EVERY TIME. it works on and off with other methods and until I figured out the for sure solution. the HDD or usb drive gets corrupted when you try to boot up sneek with it connected prior.
 
doesn't corrupt usb drive for me when I leave connected and do a cold boot it boots straight away a bit slow cause loading nand of sd but works every time
 
longtom1 said:
doesn't corrupt usb drive for me when I leave connected and do a cold boot it boots straight away a bit slow cause loading nand of sd but works every time

interesting, possibly my enclosure or drive then? I'm just glad there is a fix for now.
 
SanGor said:
sounds like your device doesn't quite follow the specs, I got an external USB powered drive which works everytime from cold boot.

I'm using a 3.5" HDD in an external enclosure with it's own separate power supply is where the situation differs. Sounds like you guys are cold booting to a 2.5" USB powered HDD. I have that option as well but have not tried it yet, I'm sure it will be fine.
 
Digital1980 said:
longtom1 said:
Luriden said:
It's got nothing to do with the USB though, and I'm not concerned with USB at the moment anyway. I can't even get Sneek DI to run from the SD card at all. I have yet to run Sneek of any kind on this Wii.
You need a hard drive connected with at least one game installed for sneek Di to boot also you need the DI.bin and font.bin on the root of the usb drive also if I don't have a drive connected I just get black screen the timing method explained a few posts earlier works for some hard drives and others will just boot without any fiddling


execute bootmii, wait for black screen. Let hang, then plug in uSB drive and watch disk drive flash the blue light and sneek boots up.

works for me EVERY TIME. it works on and off with other methods and until I figured out the for sure solution. the HDD or usb drive gets corrupted when you try to boot up sneek with it connected prior.

Didn't work for me. Not even a blue light for me, the Wii is dead as a doornail when attempting to launch BootMii in HBC using the Sneek+DI armboot. Trying to load BootMii IOS in Preloader tells me I don't even have BootMii installed because of that armboot.
 
xfcrowman said:
Nollog said:
Does anyone here know of a way I can put my sneek games back into an iso?
You can also use WiiJmanager to take decrypted games for sneek and convert them into iso or ciso.

Doesn't look like you can.
It can't seem to find any sneek riped games, even the ones it rips itself.

QUOTE(pepxl @ May 28 2010, 03:41 PM)
repack the files with partition builder and load the partition.bin into wiiscrubber using a template ISO
Where is partition.bin in the sneek folders? Is it tmd.bin? fst.bin? I don't see any partition.bin.
Also, by "load partition.bin" do you mean partition1.img ?

I tried using fst.bin and ried to replace the game partition on pokemon since it was the smallest I had on my computer, but it just corrupted the iso.
 
If you have problems with di, try opening your sneek/diconfig.bin file with a hex editor.
I'll bet a pretty penny it will tell you it's corrupt.
I rolled back to r97 myself, no problems since.
 

Site & Scene News

Popular threads in this forum