Some people can't take a hint.
Do you really think that a new DVD drive will cure totally corrupted software? It is known that loose bluetooth modules can cause black screens but did you throw your Wii across the room as well as installing an update at the same time?
It should be absolutely obvious by now that you have broken your Wii, you downgraded your Wii software and then decided it would be a great idea to install an update from a game disc. You committed one of the cardinal sins in the soft modding world and what's more, for no real reason. If you'd asked you could have found out how to patch your Wii so you could have played any game. An expensive mistake.
By all means go and buy a DVD drive and a new bluetooth module, or alternatively donate that cash to charity and go and buy a new Wii, which is what you'll have to do anyway.
Think we're both in a similar boat with our consoles. Mine bricked after I uninstalled a bad ISO60 WAD file (error on install then uninstalled via WAD mgr). After I rebooted, the video will not come on so I too am stuck with a bad brick \NAND corrupt situation. Unless your Wii fell off the desk\stand (etc), its most likely a waste of time to open up the console to 'check' components unless you want to try to install a chip to 'see' if life comes back to your system.
On a side note, I have 2 local shops that install mod chips and guarentee or refund so I really have nothing to loose to take my 'paper weight' in to see what can happen. I fully suspect that I may have to invest in a new system however this time may do a hard mod, and still watch what I install\uninstall. If this fixes, I'm thinking will be good news for the community to hear.
To fix this sort of corruption you basically need to replace the NAND with a working NAND, something that is very tricky without bootmii installed. I suppose Nintendo can do it but they designed the hardware and until some bright spark replicates what they do then you are pretty much stuck.
You could always send your Wii to Nintendo, they might not notice you've soft modded it and only charge you a nominal fee.
There seems to be a lot of reported bricks these days with people updating using The conduit, Wii Sports Resort and other newer games. I wonder if this is due to some software Nintendo have put into their updates that targets 3.2 downgraded systems.
For the mod chips, do they read the NAND then proceed do their thing, or do they boot with their own flavour of firmware and bypass the NAND altogether? Is there is a chip that has its on 'BIOS' and ignors the NAND out there?
A modchip will NOT allow you to recover from a low level brick. They are only designed to play backups.
So others that think its gonna be smart to update after they downgraded let this be your warning. There are like 5 threads here that are saying "well i downgraded to 3.2 because everybody else is but i wanted to play me new game so i updated because im to lazy to search". tisk tisk tisk
Thanks again for your replies and sharing of knowledge! I understand 'what' mod chips do, I was wondering 'how' or at what level of booting up they do the function. Whether it bypasses the security chip or the if they have their own code injected at boot up (pre or post NAND handover to the OS).
Anyways, I've taken the brick to the shop to see if they can repair with a chip or not. Its free for diags if it fails, then its the solid piece of mind that it truly is an unrecoverable brick. I assume this is the outcome, however it is worth the gas there and back to find out.
Although my brick was arrived at differently than the OP, not all bricks are caused from being too lazy, mis-informed or under informed. Sometimes its just bad luck. Modding anythihng beyond its designed function has risks, making a brick is the biggest of which. Even if all measures are followed, understood and kept up. I was on 3.4u. Never changed, downgraded\updated from there. Mine was caused by a failed IOS60 install, crapped out part way through. I uninstalled and the system rebooted itself = brick. I never would have considered going to 4.0\4.1, disk or system updating or anything else.
Hopefully, this is a warning that not just n00bs can be bricked too.
Mod chips aren't that deeply rooted into the operating system of the Wii. I'm no expert on this as I just installed mine and forgot about it but I believe they intercept the signal from the security chip and bypass it, fooling the Wii into thinking that it is a genuine disc.
The banner brick fix which is one that the mod chip is used for (not the types you guys have) needs the chip to load the auto recovery disc. Banner bricks are generally caused by installing a bad wad and only damages a certain part of the operating system. This is the type of brick where the savemii and savemiifrii trick seems to work, mind you I'd try it regardless of the type of brick.
There are a few golden rules that I've picked up in my time helping out on Wiihacks:-
- Never delete any IOS or cIOS -- Overwriting is fine -- (Unless you are following the make your Wii a virgin tutorial.)
- Only install wads from a trusted source and then only when you really need to.
- Never update from Nintendo servers or Game Discs (retail or backup) This includes in and out of region.
- Install bootmii as boot2 and create a backup NAND just in case.
For sure. I think I got buggered on uninstalling the wad, vs trying to reinstall or download and try new. Am at a bit of a loss though as to why it just rebooted on its own without me permitting it (wasn't happily pushing buttons continually). I was actually just trying to load another IOS60HK wad I had on the SD card then it went.
The NAND backup did fail the one time I tried to do it, so didn't revisit back then as I didn't want to corrupt it (go figure!).
Maybe will get lucky with the repair, will advise and inform what (if anything) was done.
I tried the savemiifrii, sadly wouldn't work. I did though notice input did very briefly flicker when I hit the GC d-pad from port 4 (tried all ports, just in case too though), although never launched the recovery screen. Who knows, maybe will be lucky and 'just' have a bad video connector... as unlikely as that is though. Maybe they have 'THE Ultimate fixer' device ;)
Bootmii has saved a few IOS60 deleters. If you can load bootmii then you can load wad manager and install a fresh system menu. NAND isn't needed for that.
The reason your Wii rebooted is that it had no operating system to work with once you deleted IOS60.