Hacking wii new nand, still black

[dude105tanki]

Basically, one day i powered on my wii to a black screen, still don't know what caused it, I've tried multiple solutions to try and fix it to no avail.

i have bootmii installed as boot2 as well as priiloader and I can access homebrew channel from that so I can confirm that the wii still works and it runs emulators.

i tried following the tutorial "Restoring a Softmodded Wii's NAND Back to Stock" off youtube but after the final restart it still comes up black

can anyone tell me what possible went wrong and/or how to fix?
i do have another wii but I cant install bootmii as boot2 so its suck just to have the wii with bootmii as ios

 

[KleinesSinchen]

Hopefully you still have BootMii@boot2. You could try if EmuNAND works. Reference thread:
https://gbatemp.net/threads/help-restoring-nand-for-bricked-wii-backups-arent-working.558562/

 

[dude105tanki]

i do have it installed as such, I'm not entirely sure its failing though, as in degreading over time, I've flashed multiple nands (to try to fix it) and always came right back to where I started, I should mention I don't have original nands or else I would have done it, I haven't tried reinstalling cios, think that'll do something? also I haven't tried system menus themes either, I thought ohneswanzenegger should fix all of those right?

i understand that I can emunand but id like to get it back to its original state if possible

 

[XFlak]

If ohneschwanzenegger isn't working then I think the issue is probably hardware related.

You could try posting a syscheck, but again I don't think software will resolve this issue for u

https://gbatemp.net/threads/posting-a-system-check.300279/

 

[JaapDaniels]

since it boots to priiloader, i'd say check if there's region patch active first (this kind o tend to kill soft launch, and block restoration for it will just reinstall or unmatching region or unmatching console system menu), then check if there's a theme installed wich means installing a clean system menu should fix that isue.
for hardware: check the wifi and the bluetooth module, these break startup too but not for homebrew in most cases.
for more options check: wii unbrick at wiibrew.org.

 

[dude105tanki]

If ohneschwanzenegger isn't working then I think the issue is probably hardware related.

You could try posting a syscheck, but again I don't think software will resolve this issue for u

the following is from the ohneschwanzenegger flash, so it should be brand new stuff, hasn't been though the setup but its still black, i should mention i failed to connect a wiimote in either homebrew or syscheck (have a GameCube controller) possible bluetooth module like you said? i could have sworn i used a wii mote in an emulator and it worked, ill get back to you on that one


SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline Double_A R2-D2199 and Nano
...runs on IOS58 (rev 6176).
Region: NTSC-U
System Menu 4.3U (v513)
Drive date: 02.13.2007
Homebrew Channel 1.1.2 running on IOS58
Hollywood v0x11
Console ID: 75585632
Console Type: Wii
Shop Channel Country: Anguila (8)
Boot2 v4
Found 59 titles.
Found 45 IOS on this console. 17 of them are stubs.
IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20 (rev 256): Stub
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 2816): Stub
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3348): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 6400): Stub
IOS61 (rev 5662): No Patches
IOS70 (rev 6912): Stub
IOS80 (rev 6944): No Patches
IOS222 (rev 65280): Stub
IOS223 (rev 65280): Stub
IOS249 (rev 65280): Stub
IOS250 (rev 65280): Stub
IOS254 (rev 65280): Stub
BC v6
MIOS v10
Report generated on 01/01/2010.



(also cant post a link from a quote because im a new user.....strange)

--------------------- MERGED ---------------------------

since it boots to priiloader, i'd say check if there's region patch active first (this kind o tend to kill soft launch, and block restoration for it will just reinstall or unmatching region or unmatching console system menu), then check if there's a theme installed wich means installing a clean system menu should fix that isue.
for hardware: check the wifi and the bluetooth module, these break startup too but not for homebrew in most cases.
for more options check:

ohneschwanzenegger was flashed so it should be clean, plus priiloader (before the flash) prevented any disk from trying to update with all those options turned on to block updates.

also can you mention which types of bricks your trying to referring to so i can more effective try solutions?

 

[JaapDaniels]

the following is from the ohneschwanzenegger flash, so it should be brand new stuff, hasn't been though the setup but its still black, i should mention i failed to connect a wiimote in either homebrew or syscheck (have a GameCube controller) possible bluetooth module like you said? i could have sworn i used a wii mote in an emulator and it worked, ill get back to you on that one


SysCheck HDE v2.4.0 HacksDen Edition by JoostinOnline Double_A R2-D2199 and Nano
...runs on IOS58 (rev 6176).
Region: NTSC-U
System Menu 4.3U (v513)
Drive date: 02.13.2007
Homebrew Channel 1.1.2 running on IOS58
Hollywood v0x11
Console ID: 75585632
Console Type: Wii
Shop Channel Country: Anguila (8)
Boot2 v4
Found 59 titles.
Found 45 IOS on this console. 17 of them are stubs.
IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20 (rev 256): Stub
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 2816): Stub
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3348): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS60 (rev 6400): Stub
IOS61 (rev 5662): No Patches
IOS70 (rev 6912): Stub
IOS80 (rev 6944): No Patches
IOS222 (rev 65280): Stub
IOS223 (rev 65280): Stub
IOS249 (rev 65280): Stub
IOS250 (rev 65280): Stub
IOS254 (rev 65280): Stub
BC v6
MIOS v10
Report generated on 01/01/2010.



(also cant post a link from a quote because im a new user.....strange)

--------------------- MERGED ---------------------------



ohneschwanzenegger was flashed so it should be clean, plus priiloader (before the flash) prevented any disk from trying to update with all those options turned on to block updates.

also can you mention which types of bricks your trying to referring to so i can more effective try solutions?

clean could still mean unmatching region

 

[dude105tanki]

clean could still mean unmatching region

Well In the syscheck it says both 4.3U and ntsc-u
Am I missing something? Or even though the syscheck is reporting it it may not be?

 

[XFlak]

Unless the console was originally Korean and the Korean key is still present in the seeprom you should be fine from a software perspective after using ohneschwanzenegger

 

[dude105tanki]

Unless the console was originally Korean and the Korean key is still present in the seeprom you should be fine from a software perspective after using ohneschwanzenegger

Ya the more I think about it the more and more I think it’s the Bluetooth, kinda sucks, but if that’s it then that’ll be the fix for it, and it’s a USA one, says so of the sticker with the serial number, and as far as I know the keys that bootmii gives are valid and the ones that shipped with the console.

I’ll order a replacement soon and see if that fixes it,
Just out of curiosity, how do people know it’s the Bluetooth and not the WiFi? Also thanks for the insight, all of you, answered more questions in like 3 days instead of the 3 months i began working on it again

 

[JaapDaniels]

since the wiimote is using bluetoothe, do those still work on your emulators wireless?
if so, that's should mean bluetooth still works.
if you can start cleanrip or usb-loader gx you could check the dvd drive there. wich would mean there is still wifi, nand, CPU, GPU and RAM, counting you get into homebrew wich uses graphics, wich use ram and calculations...
the syscheck gives a clean nand, and it seems to accept read and write jobs...
wifi seems the only problem possible.
syscheck looks clean as far as i can see, so my bet would be the wifi...
although i would still check second hand wii price before repairing this one (at least around here they're pretty cheap)...

 

[dude105tanki]

since the wiimote is using bluetoothe, do those still work on your emulators wireless?
if so, that's should mean bluetooth still works.
if you can start cleanrip or usb-loader gx you could check the dvd drive there. wich would mean there is still wifi, nand, CPU, GPU and RAM, counting you get into homebrew wich uses graphics, wich use ram and calculations...
the syscheck gives a clean nand, and it seems to accept read and write jobs...
wifi seems the only problem possible.
syscheck looks clean as far as i can see, so my bet would be the wifi...
although i would still check second hand wii price before repairing this one (at least around here they're pretty cheap)...

Well at a glance repairing it would probably be cheaper than replacing (havnt accounted for shipping), also I can’t 100% remember if I was playing with a Wii more with emulators, I’ll check to see if theyll work though various apps of homebrew and get back to it