Of corse I'm new to this and I just wanted to now how I could use codes on bought wiiware games or other bought games if possible. Thanks guys! ;)
I've never used GeckoOS with any Wii channels, but I imagine that you would basically do the same thing, which is place the GCT file for the channel in the 'codes' folder on the root of your SD card, and then select "Launch Channel" on GeckoOS 1.9.3.1. I can't see why that wouldn't load the channels with the codes that you want applied. Get codes from here...
http://www.geckocodes.org/ (http://www.geckocodes.org/)
Also, what System Menu are you currently on? You may need to patch IOS36, depending on the version of it that you have.
I have menu 4.1 but I'm pretty sure I already have IOS 36 patched. I can load channels on gecko 1.9.3.1 but how would I get the codes on gecko, because the code manager doesn't allow any of the wii ware/vc game ID's! It says "this is not a valid ID only game name will be stored" is there another way to add codes to gecko, please help! ;)
Ok I actualy fixed my own problem, thanks for your help anyways! ;)
All you need to do is download the GCT file from the code database and and if you want to use it on code manager download the txt file and open it on code manager the export to GCT. The only problem is you have to enter the ID every time you change the codes in the manager because it doesn't technicly store the ID... but it works.
I'd like to know this, as well, really; I downloaded the Trucha Bug Restorer and read its readme but I'm afraid I'm at a loss. I mean, I don't -think- I'm stupid, but given the trouble I had installing Gecko in the first place and now this, I'm starting to wonder. I just wanna show Mega Man 9 who's boss.....
Read my above post, if it's a bit hard to understand here is another post showing the set up of getting codes if your really new:http://wiird.l0nk.org/forum/index.php/topic,5585.msg49294.html#msg49294 (http://wiird.l0nk.org/forum/index.php/topic,5585.msg49294.html#msg49294) you should skip to step five.
I already have Gecko and the Homebrew Channel installed; it's reinstalling the Trucha Bug so I can use channel cheats for WiiWare and Virtual Console games that I'm scratching my head over.
I don't think you have to do anything with trucha bug, I didn't. Make sure you have IOS 36 patched in order for gecko to work with channels, do you have gecko or gecko os, this only works with gecko. Once done so, whenever you use gecko the menu will have a load channels option.
I'm using Gecko 1.9.3.1 but there is no "Load Channel" option at all. Patching IOS36 is what I need to do and it was my understanding that the Trucha Bug Restorer did that.
Your right, wow, I forgot that, lol.
Well if you have wii menu 4.2 load TBR with IOS 249 or 250 then select the IOS that it loaded with for the IOS slot and set all four patches to yes then click on install, that should do it, if it doesn't please let me know.
In order to get the Rebooter function of GeckoOS to work, you need to either patch the ES_Identify bug into IOS36, or downgrade your IOS36 to version 1042. You can find that version on games such as Super Smash Brothers Brawl and Mario Kart Wii. Use the Wii Update File Extractor (http://www.wiibrew.org/wiki/WUFE) to extract that version of IOS36 onto your SD card, and use a WAD Manager to install it onto your console.
However, it is probably safer to just patch the version of IOS36 that you have. Some newer Wii consoles cannot use IOS36 v1042. Newer Wii consoles also cannot use a System Menu lower than 3.4, or something like that. Therefore, it's probably not a good idea to get into a habit of things like that. Use something like the Trucha Bug Restorer (http://www.wiibrew.org/wiki/Trucha_Bug_Restorer), or possibly DOP-Mii (http://www.wiibrew.org/wiki/DOP-Mii), to patch ES_Identify into IOS36.
I have the Trucha Bug Restorer and am willing to install it, but I can't make heads or tails of the stuff in the readme and I don't want to risk bricking my Wii (I can't afford a repair or replacement until October). If the steps to install/use TBR can be condensed into a few sentences written so that a non-programmer/hacker can understand them, I'd appreciate it. I hate to ask someone to "dumb down" something for me, but I'd rather look like an idiot for asking a question than be an idiot for bricking my Wii.
Do you have BootMii installed as boot2? If not, run the HackMii installer and see if you have the ability to install it to boot2. Use the link here to download it, and run it through Bannerbomb or the Homebrew Channel (if installed)...
http://www.bootmii.org/download/ (http://www.bootmii.org/download/)
If you can install to boot2, make a NAND backup, and save that and the keys that BootMii will generate for you. If you can only install as an IOS, do the same thing. Keep in mind, however, that in the event that you were to brick your Wii with only BootMii as an IOS installed, you would be unable to fix it through software. However, with the NAND backup and your console keys, you could have someone restore your console with an Infectus modchip.
BootMii as boot2 will protect you from basically any type of brick, as long as boot1 and boot2 remain untouched. If you break the System Menu or something to that effect, BootMii as boot2 is a software solution to fixing it. Also keep in mind that if something goes wrong with the boot2 install, you would again need an Infectus modchip to install BootMii to boot2. As far as I know, the console keys would not be required. I have never heard of a boot2 install of BootMii going wrong, though.
I have never run the Trucha Bug Restorer, so I am not familiar with it. However, I know that you need to use the NUS Downloader (http://www.wiibrew.org/wiki/NUS_Downloader) to download some required IOS files for the program. NUS Downloader is used right on your computer, and not the Wii.
That all seems kind of dangerous, and I don't know anyone that can use modchips or anything. I'm sorry if I've wasted your time, but I simply cannot take the risk. Until/unless the process becomes as brick-free as Ocarina and the "stock" Gecko, I'll just resign myself to getting my keester handed to me on Mega Man 9.
Assuming that the boot2 install goes correctly (again, I've never heard of anyone who has broken their boot2 since it has been released), no mod chip will ever be required for you. Just pointing out the situation in the event that you can only install BootMii as an IOS, and not as boot2.
Also, I'm not aware of IOS36 using anything important, like the System Menu or things like that. If something were to go wrong with IOS36, it is very likely that you will be able to recover from it, as long as you continue to have a way of booting homebrew programs.
Okay; you changed my mind. I -think- I used boot2 to install my Homebrew Channel, but I can't be 100% sure. I think I remember something called "boot2.elf" that involved renaming but again I'm not sure. Is that the same thing you're talking about?
Dop-mii is what I did, It's all comming back now. Once you have boot2 installed you'll be all set to use dop-mii and if your wii somehow happens to brick, hold power and reset at the same time to un-brick it. Trust me, I once bricked my wii (from preloader not dop-mii) and used this trick, and was I every so happy to see my wii on again! You install boot-mii well using hackmii installer, once done so you will be able to use boot-mii by pressing HOME at the homebrew channel. There will be a "Boot-Mii" option, click on that to start it up, you should probably do a NAND backup. Use the buttons power to scroll (kinda weird...) and reset to select (or you can use the d-pad on a gamecube controller).
Okay; I think I'm starting to understand how this stuff really works, though (understandably, I hope) I'd like to take a day or two familiarize myself with this a little more so that I'm -sure- I know what I'm doing. When a NAND backup is created, boes it create it on the SD card or the Wii system memory?
Just to clarify, you will only see the BootMii option in the Homebrew Channel if you have installed BootMii as an IOS. If you installed it as boot2, you will not see that option in the Homebrew Channel. BootMii as boot2 can be started by simply inserting the SD card before you turn on the Wii, assuming that the correct files are on the SD card.
Run the HackMii Installer, and post the "installer.log" file that the HackMii Installer generates on your SD card. This file should be generated by the time that you can bypass the "Scam Warning" on the installer, so therefore, you do not need to install anything at this time. This will help me to see whether or not you can install BootMii as boot2, or if BootMii as an IOS is the only option for you. You can download the HackMii Installer from the following site...
http://www.bootmii.org/download/ (http://www.bootmii.org/download/)
When you do a NAND backup, it would be created on your SD card, along with your console keys. The NAND backup is not saved on the Wii console. You should save those in a safe place (SD card/computer/etc.). You should create a NAND backup even if you can only install BootMii as an IOS. Also, when the NAND backup is completed, allow BootMii to verify the backup.
EDIT: I should also point out that the NAND backup will be over 500 megabytes. Therefore, you would need to make sure that your SD card has enough free space to save it.
After all this, yes, you can probably use a program like DOP-Mii to patch the ES_Identify bug into IOS36.
There is no "BootMii" option on my Homebrew Channel, so I must've installed it as boot2.
Here's the installer.log text, but it said right there in the screen that HackMii can only be instaleld as an IOS because the current boot1 installation prevents boot2, or something.
HackMii v0.6 installer starting up
PVR = 00087200
running under IOS 36 rev 0xd17
94 titles are installed
Found IOS 250: revision: 0xff00.
Found IOS 249: revision: 0xff00.
Found IOS 223: revision: 0xff00.
Found IOS 222: revision: 0xff00.
Found IOS 57: revision: 0x161d.
Found IOS 70: revision: 0x1a1f.
Found IOS 56: revision: 0x151d.
Found IOS 61: revision: 0x151d.
Found IOS 55: revision: 0x151e.
Found IOS 53: revision: 0x151e.
Found IOS 38: revision: 0xf1b.
Found IOS 16: revision: 0x200.
Found IOS 60: revision: 0x1900.
Found IOS 254: revision: 0x104.
Found IOS 50: revision: 0x1400.
Found IOS 51: revision: 0x1300.
Found IOS 37: revision: 0xf1d.
Found IOS 10: revision: 0x300.
Found IOS 36: revision: 0xd17.
Found IOS 35: revision: 0xd15.
Found IOS 34: revision: 0xd14.
Found IOS 33: revision: 0xc13.
Found IOS 31: revision: 0xd15.
Found IOS 30: revision: 0xb00.
Found IOS 28: revision: 0x60e.
Found IOS 22: revision: 0x40d.
Found IOS 20: revision: 0x100.
Found IOS 17: revision: 0x307.
Found IOS 15: revision: 0x20b.
Found IOS 14: revision: 0x208.
Found IOS 13: revision: 0x111.
Found IOS 12: revision: 0x10d.
Found IOS 11: revision: 0x100.
Found IOS 21: revision: 0x30e.
Found IOS 2: revision: 0x1e1.
Found IOS 9: revision: 0x30a.
Found IOS 4: revision: 0xff00.
IOS versions: Installer: 34, HBC: 61, DVDX: 36
launching IOS for the installer...starting preparationsCalling boot2_run(1, 34)
Waiting for boot2 to load ...
boot2 loaded, waiting for IOS
IOS loaded: IOS34 v13.20
IPC started (524)
parsing last generation bootmap
found valid boot2 blockmap at block 1 (pos 0x627c0), submap 0, generation 4
found valid boot2 blockmap at block 5 (pos 0xe67c0), submap 0, generation 5
parse_blocks: found 2 valid blockmaps
found 2 valid blockmaps
using generation 5
boot2 blocks: 00 01 02 03 04 05 06
boot2bin @5,0 (blocks=0,1 - bootmii=0)
bootmii@-1,-1
boot2 blocks: 06 05 04 03 02 01 00
boot2bin @5,1 (blocks=6,5 - bootmii=0)
boot2 block layout: 2 2 1 1 1 0 0
Assembling boot2 in RAM
copyright size = 34
copyright text = 'Copyright 2008,2009 Team Twiizers.'
tmd ends at 0x80295dac, data starts at 0x80295de0
bootmii version = '1.1'
prepare_bootmii: bootmii_check_boot1 failed: -2
preparations done![33;1mThe test results are in:
[37;1m Using IOS versions: Installer: 34, HBC: 61, DVDX: 36
The Homebrew Channel: [32;1mCan be installed[37;1m
DVDX: [32;1mCan be installed[37;1m
BootMii: [35;1mCan only be installed as an IOS
[37;1m The installed boot1 version prevents a boot2 install (-2)
Thanks for posting the log.
Unfortunately, you cannot install BootMii as boot2, as your boot1 version prevents an install to boot2. You can only install BootMii as an IOS. On the Homebrew Channel, you can get to the "Launch BootMii" option by either pressing "HOME" on the Wii Remote, or by pressing the Start button on a GameCube controller, and probably other ways as well. I would still recommend installing BootMii as an IOS, making a NAND backup, and saving that along with your keys. For some brick protection, you may consider something like Priiloader (http://www.wiibrew.org/wiki/Priiloader), although this is not as good as BootMii as boot2. Priiloader will not save you from things like a corrupted System Menu/corrupted System Menu IOS/etc. I have never used Priiloader, so I can't recommend it one way or another.
It looks like you are on 4.2 (based on IOS70 (http://www.wiibrew.org/wiki/IOS70) showing on that log), so I'm not going to offer instructions on how to downgrade IOS36, as that likely won't work for you. You will need to patch the ES_Identify bug into IOS36.
You will need to use a program like DOP-Mii (http://www.wiibrew.org/wiki/DOP-Mii) to patch ES_Identify to your IOS36.
Does your Wii have a reliable internet connection? If so, I believe that the patching of IOS36 can be done right through DOP-Mii. If not, then you will need another program, called NUS Downloader (http://www.wiibrew.org/wiki/NUS_Downloader), to download some required files.
Yeah; I've got a very reliable wireless network in my home. I play Tatsunoko vs. Capcom with a friend in Illinois with zero lag, no freezing and very short load times; same goes for Beatles Rock Band. And I am running on 4.2; I would just update whenever a game required it. However, I still got the HBC and Ocarina (and later Gecko) operational with zero issues.
If all I'm using this for is cheats on the VC/WiiWare games and not trying to hack or pirate games (which I don't do anyway; nasty practice), what are the chances, in percentages if you can tell me, of the Wii getting bricked? I like to know the odds.
EDIT: Okay, I installed BootMii as an IOS. I hit the "Home" button on he Wii Remote at the HBC and clicked "Launch BootMii". After figuring out that I needed to use a GameCube controller to work the new menu, I am now creating a NAND backup. What do I do after this?
I might try and run some of DOP-Mii on SNEEK later on, so I can get a better idea of how it works. SNEEK can't detect SD cards though, so I don't know how much that might help.
Assuming that you only apply patches to IOS36 (http://www.wiibrew.org/wiki/IOS36), you should be pretty safe from a brick. The 4.2 System Menu uses IOS70, and IOS36 is only used by Nintendo games like Mario Kart Wii and Super Smash Brothers Brawl. The worst thing that would probably happen is that games like those wouldn't be able to boot, but that would be fixable.
On the BootMii (http://www.wiibrew.org/wiki/BootMii) menu, you can also use the "Power" and "Reset" buttons on the Wii console (http://www.wiibrew.org/wiki/BootMii#Controls) to navigate through the menu. A GameCube controller is not required. Anyway, once you have created and verified a NAND backup, there should be two new files on your SD card, named "nand.bin" and "keys.bin." Just save those files in a safe place, and possibly make multiple backups on your computer if you want.
Gotcha; now do I just run DOP-Mii through the HBC like I did Hack-Mii?
Yes, that is how you would run it. However, I'm going to try and get an idea of how to use it before giving any advice. It's up to you if you want to try and figure it out yourself.
Hopefully I will have a chance to try it soon.
Yeah; I'm gonna go ahead and wait on you, since, of the two of us, you know what you're doing. I've got this thread bookmarked and you take as much time as you need to figure it out. I can be patient.
I wanted to use DOP-Mii to patch the IOS36 on my emulated SD card NAND for SNEEK, but unfortunately for me, it kept crashing. However, I think I got a pretty good idea on how it works.
Fortunately, DOP-Mii seems pretty straightforward and easy to use...
1. When you start DOP-Mii, the first thing you will see is a page that has credits and states that DOP-Mii is free software. Press 'A' on the Wii Remote to continue to the next screen.
2. On the next page, you will see an option which states "Install IOS36 (v3351) w/FakeSign." Scroll down to highlight it, and press 'A' to select that option. After you press 'A', you may see the following...
Are you sure you want to continue? [A] Yes (B) No [Home] Return to Loader
If you do, just press 'A' again to continue from there.
3. On the next page, you will get the following options for loading "IOS15 v257" into memory...
Download from NUS
Cancel
Load WAD from SD Card
Load WAD from USB Storage
If you plan on downloading from the internet, make sure you have an internet connection set up on the Wii, and select "Download from NUS." If you want to do it offline, you need the following files...
IOS15-64-v257.wad
IOS15-64-v523.wad
IOS36-64-v3351.wad
You can download those on your computer by using NUS Downloader (http://www.wiibrew.org/wiki/NUS_Downloader). You would need to place those files in a folder named "WAD" on the root of whatever device you are using (SD card or USB device). However, I would recommend just using an internet connection if you have a reliable one, and if you don't, to just use an SD card. If you use an internet connection, I doubt that NUS Downloader would be required.
4. That was as far as I got, but I believe that you just downgrade IOS15 from that point, and at some point, it will ask you to apply the ES_Identify patch into IOS36. If it does, allow it to do so.
IOS15 (http://www.wiibrew.org/wiki/IOS15) and IOS36 (http://www.wiibrew.org/wiki/IOS36) are not really used by anything important, like the Wii System Menu (http://www.wiibrew.org/wiki/System_Menu). These IOS files should be pretty safe to modify, and that's all that the "Install IOS36 (v3351) w/FakeSign" option seems to do.
Sweet - it worked. Basically I just answered "Yes" to everything DOP-Mii wanted to do and it worked like a charm. "Load Channel" showed right up in Gecko and it reads the codes off of the SD cards flawlessly. (I'm finally getting vengeance on Mega Man 9.)
And for reference if anyone asks, the Code Manager I have (dunno if everybody uses the same one) seems to have issues with the 4-digit ID codes for the WiiWare/Virtual Console games; they'll still save and still work, but you have to pretty much enter the Game ID manually and save it to the SD card manually (it does it automatically for the regular Wii discs). You'll get an error about the Game ID and an option to continue anyway; do so and save the file. A little more cumbersome, but the same results, so I'm not complaining. Thank you for all of your help, 111.
ok i did the iso36 download from nus thing and it says ''error ES Addtitlestart (-1035) title with a higher verion intalled. has ur iso15 been installed higher than 257?'' any help woud b appreciated ???
I'm also having issues with this...
I tried using Dop Mii to install IOS36, DopMii couldn't find any IOS it could use to install it (needs fake signing bug aparrently) so I asked here and looked on the internet and found this Trucha Bug Restorer and tried to do that but i ended up with this error
Quoteerror ES_Addtitlestart returned -1035, maybe you need an updated downgrader