Hey guys.
Well as the title says is my 4.0E got wii bricked. Savemii/Savemiifrii doesn't work but it boots into Bootmii just fine.
I figured I could just take another wii's NAND and insert it into the bricked Wii but I can't seem to get a key.bin file
after backing up my bricked wii's NAND with the current version of BootMii.
Wii version 4.0E - bricked through patchmii, the Mii channel failed to install.
Bootmii v0.8 - Gives you a nand.bin but not a key.bin
Homebrewchannel - Should be latest, didn't ask for an update launching it for the first time. Dosn't boot through BootMii.
I saw that earlier versions of BootMii doesn't create a seperate file for the wii keys (key.bin & NAND.bin) but the
key is still in the NAND file.....so I cannot use betwiin due to the lack of knowledge of how I can extract the key's from a NAND with a hex editor.
I also tried using Comex's Nand Formatter to fix this issue, I did was told in the readme (download respective .wad files with your region) but it doesn't seem to run all the wad files, It just stops after Region select and systemmenu, "Done".
I realized that you can put the wad files in different orders which also resault with a black screen.
Everytime the installer installed an IOS it just stops, and bootmii still say that the Wii version is 4.0E
when I installed 3.1E.
The files are the following:
Wii Systemmenu - v258 ( 3.1E )
IOS 17 - 64 - v512
IOS 30 - 64 - v1040 (I read somewhere that this file is curropted if you download it via NUSD? )
IOS 31 - 64 - 1037
Eula - NUS - v2
Regionselect - NUS - v2 & v1
After another couple of hours of trying out different combinations (installing the PAL wads and NTSC wads) I just gave up, google doesn't seem to be able to answer my question once again.
So I finally found this forum which seems to be quite promising! Instantly I found a "guide" to fix your fully bricked Wii and got the the part where I could use cboot2 to launch Wad manager.
However didn't the application seem to launch at all, I have no idea what's wrong and I tried both versions onthis site. None of them worked....and you are suppossed to run them via your SD card viewer on BootMii right?
After anopther failure I felt like doing some research on bootmii and saw that I had to run the installer on another wii to prepare the SD card to autoboot into wad manager after 10 seconds......which I need a little help with, since I don't have a clue what to do here, nor do I want to cause my other Wii to ger bricked too.
(I have bootmii on both machines btw)
What should I do?
________________________________________________________________________________
I do have 2 Wii's to work with, the working wii has a wiikey v1 installed on it and have the latest bootmii installed on it, the bricked wii doesn't have a chip only bootmii v0.8
Bootmii v0.8
Stub v0.8
Mini v0.8
Console ID : (Censor)
SysMenu : 4.0E boot1b boot2v3
Nand FS usage :62.9%
Well as the title says is my 4.0E got wii bricked. Savemii/Savemiifrii doesn't work but it boots into Bootmii just fine.
I figured I could just take another wii's NAND and insert it into the bricked Wii but I can't seem to get a key.bin file
after backing up my bricked wii's NAND with the current version of BootMii.
Wii version 4.0E - bricked through patchmii, the Mii channel failed to install.
Bootmii v0.8 - Gives you a nand.bin but not a key.bin
Homebrewchannel - Should be latest, didn't ask for an update launching it for the first time. Dosn't boot through BootMii.
I saw that earlier versions of BootMii doesn't create a seperate file for the wii keys (key.bin & NAND.bin) but the
key is still in the NAND file.....so I cannot use betwiin due to the lack of knowledge of how I can extract the key's from a NAND with a hex editor.
I also tried using Comex's Nand Formatter to fix this issue, I did was told in the readme (download respective .wad files with your region) but it doesn't seem to run all the wad files, It just stops after Region select and systemmenu, "Done".
I realized that you can put the wad files in different orders which also resault with a black screen.
Everytime the installer installed an IOS it just stops, and bootmii still say that the Wii version is 4.0E
when I installed 3.1E.
The files are the following:
Wii Systemmenu - v258 ( 3.1E )
IOS 17 - 64 - v512
IOS 30 - 64 - v1040 (I read somewhere that this file is curropted if you download it via NUSD? )
IOS 31 - 64 - 1037
Eula - NUS - v2
Regionselect - NUS - v2 & v1
After another couple of hours of trying out different combinations (installing the PAL wads and NTSC wads) I just gave up, google doesn't seem to be able to answer my question once again.
So I finally found this forum which seems to be quite promising! Instantly I found a "guide" to fix your fully bricked Wii and got the the part where I could use cboot2 to launch Wad manager.
However didn't the application seem to launch at all, I have no idea what's wrong and I tried both versions onthis site. None of them worked....and you are suppossed to run them via your SD card viewer on BootMii right?
After anopther failure I felt like doing some research on bootmii and saw that I had to run the installer on another wii to prepare the SD card to autoboot into wad manager after 10 seconds......which I need a little help with, since I don't have a clue what to do here, nor do I want to cause my other Wii to ger bricked too.
(I have bootmii on both machines btw)
What should I do?
________________________________________________________________________________
I do have 2 Wii's to work with, the working wii has a wiikey v1 installed on it and have the latest bootmii installed on it, the bricked wii doesn't have a chip only bootmii v0.8
Bootmii v0.8
Stub v0.8
Mini v0.8
Console ID : (Censor)
SysMenu : 4.0E boot1b boot2v3
Nand FS usage :62.9%
