Use another NAND after a brick

Step-by-step Wii tutorials: mod your Wii, install the Homebrew Channel, cIOS and a USB Loader, back up and unbrick your console.
User avatar
xav91
Habitué
Members
Posts: 258
Joined: Thu 25 Dec 2008 18:40
Wi-Fi: Oui
Firmware Wii: 4.3E
CFW Wii: hermes
Type de DS: DSi
Linker DS: supercard ds two
Location: 25 km au sud de Paris

Use another NAND after a brick

Post by xav91 »

Automatically translated from French.

Your WII just bricked, you've tried everything and nothing works; there's still one solution left (still very restrictive though)!
You previously installed BootMII in Boot2 (mandatory), this tuto will show you how to recover its keys (before the brick) and reinject them into a healthy (non-bricked) NAND copy.

First of all

Have BootMII installed
download the archive
This content is for members only. Log in or register for free to see it.
place the folder xyzzy in the folder apps of your SD card
install "python-2.6.2.msi" , "pycrypto-2.0.1.win32-py2.6.exe" and "numpy-1.3.0-win32-superpack-python2.6.exe"

The different steps:
  • recover the keys specific to your WII using Xyzzy
  • retrieve the Boot1 and Boot2 version of your NAND using BootMII
  • copy the keys from your NAND onto a healthy (non-bricked) NAND using Betwiin
recover your WII's keys

For this, we're going to use xyzzy-1.1, created by Bushing, which will give us all the keys specific to your WII (Common key, SD key, NAND key, ECC private key ...)
Launch the homebrew via the Homebrew Channel
Image unavailable (removed by its host)

Homebrew process: downloading and patching IOS11, installing the hacked IOS11, removing this hacked IOS11
Image unavailable (removed by its host)

displaying the keys and saving them to the SD card
Image unavailable (removed by its host)

Image unavailable (removed by its host)

the keys we're interested in are hmac-key and nand-key

Another method consists of editing nand.bin (NAND backup made with BootMII) using a hex editor (EditHexa provided in the archive, it's in French and free)
Image unavailable (removed by its host)

the hmac-key is located at address (offset) 21000144 (or depending on the editor $21000144 or 0x21000144) and is 20 bytes
Image unavailable (removed by its host)

and the nand-key is located at address 21000158 over 16 bytes
Image unavailable (removed by its host)

retrieve the Boot1 and Boot2 version of your NAND using BootMII

start on the BootMII menu and go to the last icon by pressing Power 3 times then Reset to confirm
Image unavailable (removed by its host)

then go to the Info icon by pressing Power 2 times then Reset to confirm
Image unavailable (removed by its host)

the information screen gives us:
  • the BootMII version
  • the console's identification number
  • the System Menu version (unknown in my case)
  • the boot1 version (1b)
  • the boot2 version (v3)
  • the space taken by the NAND (59.4%)
Image unavailable (removed by its host)

press Reset, and go back to the arrow icon to exit the submenu and return to the BootMII menu
Image unavailable (removed by its host)

copy the keys from your NAND onto a healthy NAND

Careful, there are still a few precautions to take:
  • The boot1 version of your WII's NAND must be identical to the one from which you're recovering the NAND copy
  • The boot2 version of the healthy NAND copy must be greater than or equal to the Boot2 version of the bricked WII.
  • If the healthy NAND copy has Bad blocks in the same place as system files, it won't work once mounted: you'll need to find another healthy NAND copy.
  • The new NAND, once mounted, will use the serial number of the WII the NAND copy comes from (Only WIIshop can be affected by this serial number change, especially regarding purchased channels)

  • copy the nand.bin (healthy backup) into the folder "betwiin/input" and rename it "flash.bin" (be careful to keep a backup of this file nand.bin, we'll need it later)
  • edit the file "flash.bin" with a hex editor and delete the last 1024 bytes (select the bytes from address 21000000 to the end then delete)
  • copy the keys nand-key and hmac-key, from the working WII's NAND, into the folder input
  • copy the keys nand-key and hmac-key, from the bricked WII's NAND, into the folder output
  • launch betwiin.py
Image unavailable (removed by its host)
  • reinject the last 1024 bytes (with a hex editor) into the file flash.bin which is located in the folder output
  • rename the file flash.bin coming from the folder output (with the last 1024 bytes reinjected) to nand.bin
all that's left is to reinject the nand.bin using BootMII :D
User avatar
Oops
God Member
Members
Posts: 7083
Joined: Thu 2 Apr 2009 00:35
Wi-Fi: Oui
CFW Wii: Wii vendu
Type de DS: 3DS
Linker DS: R4i GOLD 3DS (r4ids.cn)
CFW PS3: ode a venir
Type PSP: Fat
Firmware PSP: 6.60 pro-B10
lecteurxbox: LiteOn
Firmware lecteur Xbox360: LT+3.0 rgh2 coolrunn
Dashboard: 3.775
Location: 17 et 95

Re: Use another NAND after a brick

Post by Oops »

Automatically translated from French.

A great tuto. :o :accord: :accord: :accord:

Too bad too many people show up here with a brick, when it's too late, without having taken precautions :cry: ...
Hey!!?? that reminds me of something else unrelated to the wii but I can't remember what... :mrgreen: :98:
coy218
Nouvel arrivant
Members
Posts: 3
Joined: Sat 21 Nov 2009 14:17

Re: Use another NAND after a brick

Post by coy218 »

Automatically translated from French.

hi thanks for this tuto :D

Everything for Wii · Wii U · Switch