Homebrew Channel/Help< Homebrew Channel
Please place all support questions here, in the correct area.
NOTE: If you think you've found a bug, please refer to the Bugs page instead. If you don't see your question here, check to see if it's been moved there.
Q: What is the Homebrew Channel all about?
A: It's a channel that lets you run Wii Homebrew in .elf or .dol format. Currently, you can load them from an SD card, a USB Gecko or via local network (WiFi or wired). Each application may have a customised icon of certain size, and various metadata which is displayed when selected, such as name, short description, long description, version, release date, and coder, stored in an XML file.
Installing the channel
Q: After installing the Homebrew Channel using the twilight princess hack, will the Homebrew channel still function if I delete the twilight princess hack and reinstall my original save file?
A: Yes. Once the Homebrew Channel is installed, the twilight hack save is no longer required.
Q: Do you need any special software version to run HBC? Will it work with all versions? How do I find out which version I have?
A: No; most Wii owners should be able to install the HBC. If you receive a message during installation saying you are missing required system components, try renting or borrowing a recent Nintendo-authored game such as Super Mario Galaxy or Mario Kart; these games contain full updates and should install anything you need.
Q: Would the installer install properly if it were booted through the Homebrew Channel? ie Add it as a Channel and then boot it
A: Yes. It is also possible to transfer it to the Wii using the Wiiload method.
Q: What type of file format should I put into the SD?
A: Apps need to be called boot.elf or boot.dol (wii .dol only). Icons should be called icon.png, and information should be in meta.xml.
A: You need to create a folder in the root of the SD card called apps. Then you need to create a folder inside of that for each DOL or ELF file. Put the File in there, and rename it to either boot.elf or boot.dol(depending on the file type). You can then add an icon for each app in the same folder, with it named icon.png, and a description file name meta.xml.
Using the channel
Q: Is there a way to prevent the Homebrew Channel - and the time spent using it - from being logged on the Wii message board?
A: No, nor is there any real need to.
Q: Is it possible to sort the applications running in the Homebrew Channel?
As of beta8, the Homebrew Channel sorts your applications alphabetically by their name (i.e. the content of the <name> Element in the application's meta.xml).
Q: Is there anything I can do to allow the Homebrew Channel to automatically update, assuming that I may be behind a http proxy? Or would a slow internet connection affect the update checker?
A: The self-update feature is still experimental; sometimes it does not work and we do not know why. Proxy support is something we'll need to explicitly add.
Issues with specific apps
Q: Is there any chance at all that Nintendo can/will brick a Wii that has the Homebrew Channel?
A: Possible, but unlikely. It's far more likely that a future Nintendo update could *accidentally* conflict with the HBC. Keep checking on WiiBrew before installing updates and you'll likely be safe.
Q: Does this void my warranty even though it is just software and not a hardware mod?
A: Technically? Perhaps. Realistically? No
Q: Why didn't my Homebrew Channel detect the update? Connect 24 is on... And the World Icon on the Channel is white
A: You could be behind a http proxy, the channel does not currently account for that. Also, the check is only done when you start the channel, we have not yet bothered reverse engineering connect 24.
Q: If I can not update through the Homebrew Channel's auto update, can I install Homebrew Channel beta8 over beta7 via the twilight hack?
A: Sure, btw other ways of booting the installer also works. (like from the HBC itself ;) )
Q: Will the source code be released?
A: When both it and the audience is ready for that.
Q: Nintendo has just relased an update for the Wii System Software. In the relase notes, Nintendo says that modded savefiles and so on will be removed by this update. I've installed the HBC. What will I do? Is it sure to install this update?
A: Although we recommend you not update, the Homebrew Channel is unaffected by the update.
Q: I have downloaded the TP Hack and the homebrew channel and renamed it boot.elf and put it at the root of my sd card like it says. I turn on the wii delete the zelda file, copy the TP hack to the wii and go to the disc channel, let it load, start it, do the vision test, load the TP hack file and talk to the man, but then this comes up and it freezes. I already reformated the sd card and everything but i dont know whats wrong?
here is the error message:
FAT_ReadFile (boot.elf) failed with error -1 No elf image at adress 90100000 Dol image detected? loading binary files
A: Your SD card is probably formatted to FAT32. Reformat to FAT16 and try again
Q: I keep getting the error message exception 10300. What does this mean, and how an i fix it?
A: Where are you seeing this error? What are you doing that causes this error to appear? (I don't believe we have code that reports errors as "exception xxxx". Bushing 10:19, 23 June 2008 (CEST)
Q: I succesfully installed the HB channel and the provided apps package too, but I cannot setup the modern style into the ScummVM. The Wii ScummVM has only the classic style built-in, so I tried to copy the "modern" style from my PC to the SD card. The Wii ScummVM now does list the new style, but even if I choose it, the interface does not change. What am I doing wrong?
Q: Is there a Japanese translation for the Homebrew Channel planned?
A: Not yet, because we do not yet have Japanese-characterset support for our text rendering code. A good first step would be for us to make Japanese text work in meta.xml. Can you provide some examples of meta.xml with Japanese text, along with a screenshot of how it should work? Bushing 11:27, 23 June 2008 (CEST)
Q: After installing the homebrew channel using the twilight hack, the homebrew channel works, other channels work, but none of my Wii game discs work. After clicking "start" on the game channel, the screen goes black and returns to the channel list. Deleting the Homebrew channel did not fix the issue, but formatting the Wii System Memory did fix it. Is this a bug?
A: Is your NAND full? Bushing 11:27, 23 June 2008 (CEST)
A: We have some plans for functionality along these lines -- stay tuned.
Q: While this has probably been thought before, I'm not sure the reasoning why it isn't done. Would it be possible to COPY the actual channel from one machine onto another. If it's machine locked out, why not edit the file. Also, publishing a disc like action replay or gameshark might be able to force a channel!
A: Taken separately:
- Q. Would it be possible to COPY the actual channel from one machine onto another.
- A. no
- Q. If it's machine locked out, why not edit the file.
- A. Because it doesn't work that way.
- Q. Also, publishing a disc like action replay or gameshark might be able to force a channel!
- A. Huh? Bushing 11:27, 23 June 2008 (CEST)
Q: I keep getting an exception 0300 when booting using the Twilight Hack
Twilight Hack: twilight-hack-v0.1-beta1 The Homebrew Channel: the_homebrew_channel-beta_8 Disc: RVL-RZDP-0A-0 JPN Savegame: /private/wii/title/rzdp/data.bin MD5 of boot.elf on SD: [K:\] boot.elf 5134a30e1bdb7d8ed1a8add9302df307 SD Cards: 1GB Sandisk or 2GB Kingston FAT or FAT32, doesn't matter Error Log: USB Gecko serial interface not detected Loading FAT: OEM Name: MSDOS 5.0, 36 reserved sectors, FAT32 fat size = f1c00 FAT starts at sector 0x11d / starts at sector 0x1039 Reading boot.dol start cluster = 0003 boot.dol not found (-1), reading boot.elf: start cluster = 0003 Found boot.elf! done, filesize is 1597440 Valid ELF image detected. Exception 0300 occurred! R0-R7 R8-R15 R16-R23 R24-R31 66522432 00000002 00000000 90004ddc 9000ff40 9ea88d24 90004ef0 900052d0 80000000 90010000 90004cdc 900052c8 9ea88d24 90010000 90004d2c 900052c0 b4724344 28000022 90004d08 00000000 f0100cac 00000000 90004d54 00000001 9ea88d24 00000000 90004d64 90100000 00000020 00000000 90004d78 9028d1f8 CR/XER LR/CTR SRR0/SRR1 DAR/DSISR 48002024 90002dc8 900008cc b4724344 00000000 9028d1f8 00003032 04000000
A: Your boot.elf is corrupt. The correct MD5 sum is 80dd6b7c096dcba88b7996a4cd8a5935.