Hacking Fully Bricked Wii

[Midna]

I have a brilliant problem on my hands here. My old launch Wii has bricked, directly following me doing nothing at all to it except playing Lost Winds.

When I got up today, the power LED was orange, but pressing it did not turn on the console.
Upon yanking the power and booting it up, I am greeted with a black screen.
A couple more tries at starting the console give me "the system files are corrupt" in garbled text
Starting the console with a SD card prepared for Bootmii (I have boot2) gives a black screen and a blinking disk light
Priiloader works, if I don't have the bootmii card in when I start it.
From Priiloader I've been able to load any homebrew and various channels.
However, reinstalling the system menu wad, running syscheck (All versions and DOP-Mii), and running hackmii all freeze.
I have my old NAND backup, but I only have the nand.bin and not the keys.bin. Stupid me.

So, uh, any tips? What exactly can I do out of priiloader that would be of help.

 

[XFlak]

u don't need the keys.bin to restore the nand.bin backup. In fact, with the exception of the very first revisions of bootmii, all nand.bin backups have the keys.bin appended to the end of it. So essentially you can extracts your keys.bin from your nand.bin.

Are you able to access bootmii at all (ie. via the HBC or priiloader)? Have you tried running syschecks' syscheck (not dop-mii's)?

 

[Centrix]

If you didn't need the keys.bin than why have bootmii give them to you when you back up the NAND?

 

[Midna]

Alright, looks like I spoke too soon. I tried running hackmii for a third time, and this time it worked. Reinstalled bootmii, and now bootmii starts up.
However, Bootmii is claiming that my backup is from a different Wii. There's no god damn way I backed up the wrong Wii. Is there any other reason i might be receiving that message?

 

[Centrix]

hm...maybe you did back up the wrong wii and you just forgot, I've done that once or twice before!

 

[AbdallahTerro]

I have few ideas that need experts blessings:
Since bootmii-boot2 is present you can try different workarounds:
1. from your previous semi-brick post you told us about error messages related to wii settings/Mii channel...
so one option is to delete your settings by deleting "Shared2" folder using WiiXplorer rev234 or fstoolbox
2. A second option is to restore your wii back to factory - many games can take you straight to wii settings bypassing the system menu
3. Restore your Nand if everything fails

 

[Coto]

I think either tuieidj or giantpune will give you the correct answer for that.

Can you do a NAND backup right now?
How many bad blocks has your NAND now?

Write down and post here everything Bootmii shows on screen while doing the NAND backup process..

 

[Midna]

I think either tuieidj or giantpune will give you the correct answer for that.

Can you do a NAND backup right now?
How many bad blocks has your NAND now?

Write down and post here everything Bootmii shows on screen while doing the NAND backup process..

This Wii has always had shitloads of bad blocks, right from the start.
Thanks for reminding me though. I KNOW that nand backup is from this Wii. I remember getting the usual tons of bad blocks. My other Wii doesn't get those.
So why is Bootmii asking for the konami code?

 

[Coto]

Well then, stop. A huge amount of bad blocks means physically damaged /wearing out NAND. Konami code is mandatory in newest hackmii versions, and requires a GC controller plugged in, in order to restore NAND.

You could try replacing NAND chip, or wait. Don't do anything completely rash as you'll waste a day 1 Wii (bootmii at boot2 capable)

 

[Midna]

Well then, stop. A huge amount of bad blocks means physically damaged /wearing out NAND. Konami code is mandatory in newest hackmii versions, and requires a GC controller plugged in, in order to restore NAND.

You could try replacing NAND chip, or wait. Don't do anything completely rash as you'll waste a day 1 Wii (bootmii at boot2 capable)

>A huge amount of bad blocks means physically damaged /wearing out NAND
It's always been this way though. I attributed it to launch run factory defects.

 

[JoostinOnline]

Can you ballpark the number of bad blocks? If it's over 80, then you've got a problem.

Edit: The Konami code is only necessary if you are using Bootmii as IOS.

 

[Coto]

The only way to "fix it" is by using a hardware flasher, swap the NAND chip and solder a new one. Rewrite the latest NAND backup you did (even with bad blocks labeled in the fs), re-do a NAND backup, extract keys, build a new NAND with ohneschwanzenegger using your Wii's keys, then profit.

 

[Midna]

Yeah it's not that high, and it hasn't gotten worse over time. Just much higher than my other Wii. Pretty damn sure this is the right nand backup. Just, is there any other possible reason why bootmii would be complaining like it is?

 

[JoostinOnline]

I'd still like a ballpark.

 

[Midna]

Perhaps 20? Maybe a bit more? I'm not at all sure.
And Joostin, it's asking for the Konami code because it says that my nand backup doesn't match my Wii. I'm wondering if there is any situation in which it could be giving this message in error

 

[Anon10W1z]

garbled text means you set the priiloader SM ios to something that can't boot SM.

 

[JoostinOnline]

Perhaps 20? Maybe a bit more? I'm not at all sure.
And Joostin, it's asking for the Konami code because it says that my nand backup doesn't match my Wii. I'm wondering if there is any situation in which it could be giving this message in error

I'm sorry, I missed that part. Check your bootmii version. I'm guessing you made the backup with v1.0 or earlier, although you may not have it now. They fixed that bug in v1.1.

 

[DeadlyFoez]

Well then, stop. A huge amount of bad blocks means physically damaged /wearing out NAND. Konami code is mandatory in newest hackmii versions, and requires a GC controller plugged in, in order to restore NAND.

You could try replacing NAND chip, or wait. Don't do anything completely rash as you'll waste a day 1 Wii (bootmii at boot2 capable)

The only way to "fix it" is by using a hardware flasher, swap the NAND chip and solder a new one. Rewrite the latest NAND backup you did (even with bad blocks labeled in the fs), re-do a NAND backup, extract keys, build a new NAND with ohneschwanzenegger using your Wii's keys, then profit.

Almost everything you said is misinformation. I think the only word that was not wrong is the word "the".

 

[Coto]

Well then, stop. A huge amount of bad blocks means physically damaged /wearing out NAND. Konami code is mandatory in newest hackmii versions, and requires a GC controller plugged in, in order to restore NAND.

You could try replacing NAND chip, or wait. Don't do anything completely rash as you'll waste a day 1 Wii (bootmii at boot2 capable)

The only way to "fix it" is by using a hardware flasher, swap the NAND chip and solder a new one. Rewrite the latest NAND backup you did (even with bad blocks labeled in the fs), re-do a NAND backup, extract keys, build a new NAND with ohneschwanzenegger using your Wii's keys, then profit.

Almost everything you said is misinformation. I think the only word that was not wrong is the word "the".

I love how people like you won't say something useful at all (sometimes, because you can be quite helpful sometimes either). I've coded on chips read/write retries, DEMUX, etc and all that stuff, so that's why I always ask how is the current chip condition as it could be the main cause of weird problems accessing data (or failing at reading vital OS files)

Expect perfection and end up alone, dear temper. I'm trying my best trying to help, and not "misunderstand" others, as they will be probably more right than I. Sharing experience will lead to something good in the end, with a good attitude.

 

[DeadlyFoez]

ok. Sorry. Joostin already explained about the konami code, and the OP doesn't need a hardware flasher for this situation since his nand is not getting more bad blocks so his nand chip does not need to be replaced.

I was in a rush, I had dinner cooking and the bitch wife wasn't doing her job with it.