What is it?
it is a rebooter & system menu patcher that should be run from bannerbomb for people too pussie to install the homebrew channel or patch an IOS so they can use better tools.
Why is it?
there was a post from a dude wanting to copy protected saves without installing any cIOS or homebrew. so that got me wondering why nobody has made something like that yet. so here is my first attempt.
Where is it?
v1http://www.multiupload.com/FBLGGQEZV8
v2http://www.multiupload.com/NILEOJUKIF
what system menus does it work on?
it SHOULD work on every system menu that has a SD card menu. even if it does start from the old bannerbomb, the system menu will most likely freeze when you reboot it and try to copy a save. i have just taken the "remove copy protection" hacks from wiibrew. so any of the 4.X system menus there should be working.
is it safe?
yes. there is no code here that writes anything to the nand, SD card, usb drive, network or anywhere but the RAM.
does it have bugs?
yes. its only been tested on 1 wii so far... mine.
its got a some issues that im not sure if i can get rid of. maybe one day.
in an attempt not to use any DI_Verify() related stuff, ive also left out any IOS reload stuff. that makes sure that it will do what it does no matter if you have a patched IOS or not. it also is the cause of many possible issues since it is not a great idea.
the IOS is left in the state that it was in when you run bannerbomb to crash the system menu.
apparently if you have already gone to the "Data Management" in the settings before you do bannerbomb to run this, and then you try to go there after you have restarted the system menu, it will freeze. because of the fact that the IOS has already been doing other stuff before this program is run and then it loads the system menu again without resetting the IOS, it really is in an unstable state. and because of that, there can be random crashes once the system menu has bee restarted.
why can't I use this with the old bannerbomb?
as stated already, the IOS is left in the state it was when bannerbomb did its thing. so my best guess is that the following happens...
you start the system menu and go to the data management screen to use bannerbomb.
the system menu does the equivalent of
CODEfor( int i = 0; i < ALL_THESE_CHANNELS; i++ )
FILE* fp = fopen( someimportantfile, rb);
then you crash the system menu with bannerbomb. and since those files were never closed, the system menu cannot open them when it tries.
why does it tell me to eject the dvd and try again?
if there was a dvd in the drive, it will be identified as the dvd and not the system menu
how do i use it?
use system menu 4.0 or higher
put the boot.dol on the root of your sd card and the bannerbomb private foder.
remove any dvd from the wii's vagina
go to the sd card menu.
load the dol.
it should restart your system menu and you will be able to copy saves using the "Data Management" in the settings.
even if the "copy" button looks disabled, click it anyways.
if the system menu freezes at any time, just hold the power button till the light goes red, then turn on your wii and try again
I don't recommend back-to-back usage. Aside from there being no benefit, you add to the chance that this will crash from "stacking" it back to back. Instead, use this to restart the system menu. Then press reset or home->wii menu befor you try it again.
i would like some feedback.
does this work for you?
if it NEVER works, what system menu do you have?
does it reboot but you are still unable to copy saves?
does it work great?
do you have preloader installed?
changelog
v1. initial release
v2. changed from ISFS_ to ES_
changed entrypoint
suppress most debug output. people using this wont have a usb gecko anyways
lots of little changes under the hood
tested and verified working on my wii with 4.0u, 4.1u, and 4.2u with official and correct IOSes
ive just 50 tests in a row with no freezing or crashes (4.1u).
