Not entirely useless, but most of it is. You can still backup your NAND, you just can't recover it. Could be useful in a semi-brick, or (alongside Priiloader) could solve a banner brick, if you are not certain what was the title that caused the brick. Maybe it isn't the best sollution, since it will make your nand data go all the way back to the day you made the backup. Unless you makeby Aobx - Homebrew General
I'm kind of skeptical about this. I mean, people send to Nintendo some Wiis with their NAND screwed up, and they replace the entire console. If you can have a perfect sollution for 5 bucks, why would people condemn some bricks as unsolvable? I'd like to know more information about this Wii BIOS Chipset.by Aobx - FixMii
That means a person has to deactivate hacks before reinstalling the system menu, or he/she will to reinstall Preloader again just to deactivate them? So that's the reason for NANDClean. Also, I've never heard about a Priiloader uninstaller, always thought you had to overwrite the system menu for this. Since we were talking about how far can Priiloader offer brick protection, and a mby Aobx - Homebrew General
Thanks for answering, jbc. I wonder if a system menu reinstallation could really "uninstall" everything, as the dev suggest. If the old system menu is renamed, wouldn't the reinstalled system menu just overwrite Priiloader and leave the old system menu alone? Not that the reinstallation wouldn't work, but is there a chance to have an old and inactive system menu taking up space in the Nby Aobx - Homebrew General
Reading in Bootmii.org, I was told Bootmii and Priiloader do their things in completely different ways. Bootmii patches itself in boot2 to work properly, right? But where do Priiloader patches itself? According to Wiibrew Wiki: "Priiloader places itself in boot sequence before the system menu", but I would bet it isn't in boot2, otherwise it wouldn't work in any console that had the fixby Aobx - Homebrew General
Wandering around some foruns, I came across this supposed solution for "most of the full brick Wii console(s)." Has anyone heard of this? Isn't this chipset just for the bluetooth module and nothing else? I mean, if you are missing a system IOS or sysconf is screwed up, would this chipset still make its miracle and set everything alright? If you've never seen it, check here:by Aobx - FixMii
Just thinking, you cannot modify the boot1 EEPROM, since it would be detected by the boot0 hash check and the system would halt. But why can't you modify boot0, since nothing checks it? Is boot0 stored in a kind of memory that isn't erasable? Anyway, wouldn't be the best way to create a vulnerability. Seems not easy to erase and rewrite in a EEPROM. Not the kind of thing everyonby Aobx - Homebrew General
Interesting. But as we talked before, nothing great comes from downgrading or upgrading boot2, since the vulnerabilities we'd like to find would be in the boot1. Nice having a confirmation though.by Aobx - Homebrew General
It's against the rules giving support for cIOS related to piracy here. Maybe only cIOS 202, since it isn't related to playing backup games. I don't think you are trying to get support for piracy from here, but restrain from talking freely about cIOS. About your question, some apps are getting dvd support through cIOS 202, like, for example, the media player WiiMC. Older apps stiby Aobx - Homebrew General
QuoteSifJarIts probably something to do with the fact that when the IOS is loaded by boot2 (last stage in boot process), its probably given System Menu privileges without needing to identify, whereas once it is reloaded, that is lost and must be regained via ES_DiVerify. However, this is a COMPLETE guess, it could be way off, but it sounds believable :P It's quite plausible though. Prettyby Aobx - Homebrew General
Pretty curious Preloader reloading the system menu IOS, since Priiloader doesn't need to do that to fully work. I guess the Preloader code wasn't honed enough? Or maybe there's a benifit in this. Anyway, I don't know if I've understood perfectly, but you say Preloader needs an IOS with ES_DiVerify even if it's the system menu IOS? In that case, why would the system Iby Aobx - Homebrew General
Thanks for giving another example, jbc. But I thought Preloader was set by default to use the system IOS, not reloading another one. Guess only Priiloader does this? Also, about Priiloader and the bricks, I read this in Wiibrew Wiki about what the app can do: "Save wii from banner & other kind of bricks that aren't ios/boot2/nand corruption related". Does that "ios corruption" means any Iby Aobx - Homebrew General
Thanks again, SifJar. Finally, I understand a reason to use IOS reload. The other patches really caught my attention, since I've never found an app that required one of those three. Even Bootmii doesn't mention anything about "IOS with boot2 access". I hope some developer will bother giving some explanations, sometime.by Aobx - Homebrew General
In fact, I ask these things by browsing tutorials and seeing the advices like "never downgrade", "Priiloader doesn't solve full brick", "Block IOS reload"... I don't have any specific app in mind. It's just a matter of curiosity. I would like to know why reload even reload an IOS. Don't you have everything you need in a single IOS, like trucha bug and ES_DiVerify? I thought "Iby Aobx - Homebrew General
Oh, it means another IOS. I thought it would be the same IOS. But why the option "block IOS reload" in some apps? What's the problem with an IOS reloading in the process?by Aobx - Homebrew General
Just make IOS 37 the way it was, then. Let's try offline installation. From the WiiBrew Wiki, there are these instructions: * Download IOS57 v5661 using NUSD. o The folder that NUSD outputs will be named 0000000100000039v5661, copy the contents of that folder into SD:/IOS/0000000100000039v5661/ * Unzip this archive directly to your SD or USB. * Launch the installby Aobx - Homebrew General
Interesting learning about IOSes. Reading the forum and the main page, I came across something called "IOS reload". Some applications reference this. What does it mean? If you load an IOS, why would you load it again?by Aobx - Homebrew General
Don't worry about not finding the exact explanation, SifJar. I could understand from the one you found. Thanks a lot. So, Priiloader just need IOS36 with trucha and ES_DiVerify enabled, but as requisites for its installation, not for it to function, right? In theory, could be another IOS with the same patches, too? I can't see why IOS36 specifically is the one for Priiloader.by Aobx - Homebrew General
I'm not sure, but I guess installing titles need ES_Identify patch. Also, I think the WiiMC installer looks for the highest patched IOS, since it doesn't make sense not using IOS36 for the job. I recommend installing a clean IOS37, and leaving IOS36 with the patches you already have. Then, just run the installer again. Following the same theory, you could also install a fully patchedby Aobx - Homebrew General
Since you're talking about tutorials, may I ask something about Priiloader? The official website points that you just need a trucha signed and ES_identify patched IOS36. However, I came across a tutorial telling to also trucha sign the system IOS for 4.0 ~ 4.2. It even recommended upgrading to at least system menu 4.0, if you want to installer Priiloader. Does any of this make sense? Why wouby Aobx - Homebrew General
Install IOS 202 by its official installer in WiiMC official page. The installer will automatically search for a trucha signed IOS and install IOS 202. No further knowledge required other than run the installer from homebrew channel. In case you don't have a trucha signed IOS, you can use Trucha Bug Restorer to trucha IOS36 or create a functional clone of it in another slot.by Aobx - Homebrew General
Thanks a lot, SifJar (and all the others who helped). My curiosity is satisfied for now! Very nice of you to share your knowledge with me.by Aobx - Homebrew General
When searching for the risks of upgrading to system menu 4.2, I came across this tutorial: That's where I saw the thing about boot2v4. I was curious to know why boot2v4 installed first by dop-mii would be better, since Nintendo would update with the same version of boot2, anyway. Thanks for clarifying that for me. So, that brick thing is random (can happen by no apparent reason) or itby Aobx - Homebrew General
Thanks again for all your answers. I'm getting it now. So, without the system IOS, ppc is screwed up and a fix attempt can only be made by starlet code only, like mini. Edit: Oh, I forgot to ask something related to the topic. Sorry if I'm asking too many questions. But I've come across a tutorial that says a official upgrade procedure to system menu 4.2 can be much less risky iby Aobx - Homebrew General
You mean updating to system menu 4.2? It only deletes the title that have the id HAXX, used by Homebrew Channel 1.0.4 and lower. If you update HBC to 1.0.5 or higher, it won't be deleted by the system menu upgrade.by Aobx - Homebrew General
Thanks a lot for the answers. I'm really learning here. I think I know the risks envolving downgrading now. Just one more question, please. I have Bootmii/boot2, and have learned it uses mini to do all its functions. However, when I boot HBC through Bootmii/boot2, my wiimote begins to function. Doesn't the bluetooth module have to do with IOSes? So, I suppose HBC through Bootmii isn&by Aobx - Homebrew General
First of all, I'd like to make clear that I'm not attempting downgrading, I'm just curious about the process and its risks. When system menu 4.2 first came off, when people were still having trouble with it because of their homebrews, there were some sollutions that pointed to downgrading back to system menu 4.1. Regardless of not being a good method for keeping your homebrews sby Aobx - Homebrew General