You don't have one IOS on your system. When the HBC says IOS61, it means that the HBC is running off of IOS61. The IOS you use in wad manager needs to be any IOS that has the trucha bug in it otherwise it won't install. Generally for this purpose and for loading Wii backups you would install a cIOS on your system which would install to IOS249 and then you would use that in wad manager.
Being on 4.1, if you have not done anything to get the trucha bug back or install a cIOS, you do not have the trucha bug on any IOS, so you will need to use the Trucha Bug Restorer to downgrade IOS15, use IOS15 to install IOS36 with the trucha bug and ES_Identify, and then restore IOS15, then run the cIOS rev14 installer and have that use IOS36 to install with a network installation instead of a wad installation if you have wifi on your Wii.
From that point you can then use wad manager using IOS249 to install wads. Before you do though you should make absolutely certain that the wad you are trying to install is legit. A badly formed wad can banner brick you and there are malicious wad's out there that will do this to you. If this does happen to you, you would need to use preloader or boot2 bootmii to run the HBC/wad manager to uninstall the bad wad.
Also you should not be messing around with any sort of IOS or system menu wad's at all. Other than that, keep any other vc/wiiware wad's you install so you can uninstall them if you need to. Deleting them through the system menu will not get rid of the ticket they leave on your system.
For more detailed explanations of what you need to use and how to use them, read through my guide in my sig/stickies.
nabster92, as always, love your explanation.
one question: what is this 'ticket' you keep mentioning? thanks
You know how if you legitimately buy a VC/Wiiware game from the shop channel, even if you delete it through data management, you can still go back to the shop channel and redownload it again without having to buy it again? This is possible because deleting it through data management still leaves this "ticket" for the installed game on your system. So if the shop channel see's you still have this ticket, it will still allow you to download the game again. The only way to remove this ticket would be to use AnyTitleDeleter for a legit title and have that delete the ticket for that game (provided you can get the title id or the version of anytitledeleter shows the name of it or something) and if it's a wad of a game you can use the wad with wad manager to uninstall it and it will also remove the ticket along with the game.
The Viztard said:
Oh uhh sorry. I meant safe as in if there was a chance at all that it would brick your wii? It does the occasional freezing thing so I have to reboot the Wii. Or is it that only certain apps have high chances of bricking your wii while others don't?
If you have bootmii installed to boot2 and have used it to make a NAND backup of your Wii, even if you do brick using something, you should still be able to load bootmii and restore that backup and revert it back to that fixed state it was in when you made the backup.
Just using apps like that shouldn't cause a brick though. Only things that would affect like the system menu IOS's or the system menu itself or something should be able to brick you. (Or installing bad wad's which would install a channel on your Wii with a banner that can't be displayed by the system menu causing a brick.) That should be fixed by just uninstalling the wad that did it though, not fully restoring the NAND backup.
QUOTE(wertyqa @ Sep 4 2009, 02:46 PM) My question is about Wiis that have modchip installed.
I´m running 3.4E with Wasabi V1 and this time RB:Beatles gives black screen. After couple of hours searching thru various threads I have come to a conclution that I can update my Wii freely from any disk to any menu since modchip allows me to play these backups anyways.
Is this correct?
And if so, is there any precautions that I should take before I do this update?
I do have HBC installed and I think I have bootmii too? All I have to get for the RB:Beatles to work is IOS56... right?
Modchip users should not do disc updates from anything. Those have the most likely chance to brick you. Though moreso if you downgraded from 4.0 to 3.2 or something. You should be able to update properly to 4.1 by using Waninkoko's 4.0 updater and then his 4.1 updater. That SHOULD install any IOS's you need at this point and have you on an up to date system menu, but if you want to be sure after that you can use dop-IOSv7 to scroll through the list of all the official IOS's and see if any of yours aren't up to date to the most recent ones and install them if they aren't (don't need to apply the sig hash check to them all except for IOS60, and you can ignore any stub IOS's). Also you will need a cIOS installed to be able to use dop-IOS so if you don't have one of Waninkoko's cIOS revisions installed, you should do so asap.
QUOTE(Kramzy @ Sep 4 2009, 02:52 PM)