Quote:
Originally Posted by bcas9472
Sure wish you installed bootmii prior to bricking, you would be saved.
|
yes well, i'm aware of this fact. I also wish i had starfall or preloader or SOMETHING on it. We never actually got that far. Bannerbomb installed, a couple of test reboots, then a few channels to prove functionality. Eventually, full downgrade to 3.2 and install of softmii was the plan.
I'm still not entirely sure what caused the brick. The mod itself was solid, noted because of the reboots. The failure didn't come till after wads were installed. This made me think it was banner brick or duplicate channel semi brick, but it sure as hell didn't look like either
i'm reading that an infectus 2 and bootmii should be able to get the unit to boot up again....since this is an older wii, boot1 is still affected by the signing bug, which allows boot2 to be resigned. I'm assuming that my boot2 on this system is screwed since i never get to the health screen. From what i've read, if i install the bootmii code on the infectus 2, it should be able to inject the working boot2 from the bootmii code into place after boot1, allowing the unit to load an auto launching disc, such as the universal brick fix.
I'm still left with the problem of rebuilding/reflashing boot2, which some have fixed by removing the nand from a working wii with bootmii installed and soldering it in place in the dead wii. Infectus then works it's magic, and you can pull out the keys needed to do a possible rebuild on the original nand
the problem with all of this for me is that i don't have, nor do i want to try to obtain, an infectus chip. i REALLY don't want to try to do this one on my own either....having 1 dead wii is bad enough, but accidentally killing a second while getting the first working iss totally unacceptable.
So, anyone have any actual helpful advice?