ok, i ended up doubling up the wires on the gnd and v points, and my old chip programed without any issues! can't same the same for me new chip tho, keep getting update failed on the same blocks, might it be something with the chip considering my other chip (same kind) works without any issues.
The new nand chip has a different block map than the original and therefore you are getting the error when it tries to write data to a bad block. The best thing to do is figure out where the bad blocks are on the new chip by dumping the data and then use Punes ohneswanzenegger tool to generate a new nand with the same block map.
This is an excellent guide!
I have a WII with LEH104071265 serial, it's a very old WII. This is semi-bricked, opera error... I try to fix it with SaveMii, but I can't it.
I don't have nanad backup, and I don't have donor nand, so I need your "Boot Patcher" as I know.
"If you don't have a donor you can use my Boot Patcher program to generate the boot blocks."
Where can I download this Boot Patcher?
if ur very old Wii has been semi-brick long long time ago, would it be fixed by updating with a 4.3e game, today ? tried ?
It's a good idea, but as I remember, this WII is not booting any disc... only an error message on screen. I try to boot any game with savemii, but it didn't succeed.
Originally Posted by billyhome
Which game have the 4.3E update?
if the console boots directly to an OPERA error, it's fully bricked. running a game is no longer an option.
Wheelie Breakers 5D's shall be 4.3e, i guess. (correct me, if wrong.)
I have some Problems to identify my NAND with xavbox.
Now, i use On-Board wiring.
If i start my without Data0 - GND short, the NAND is identify in xavbox.
I start my Wii with Data0 - GND short, i get the Error Fabricant inconnu / Type inconnu !
After 36 retries i turn off my pc and go to bed.
What can i do?
What make i false?
First of all, thanks for the nice guide. Fairly easy to follow and good instructions =)
EDIT: FYI, solved this issue myself after 8 long hours, but through others might find my solution helpful =) Look for the solution below...
Some notes on my Wii. Its a older model (white) with boot1c and boot2v4 (stock), and I've got the bootmii backup from when I first modded the Wii.
I removed the NAND from the mobo, and connected it to a tsop adaptor, all wiring checked and working.
Xavbox programmer can perform the read/write test of blocks 4080-4095 without any problems, but when trying to to a full nand update and compare write I get update fail errors after the first 2048 blocks (namely starting at block 2048).
I noted from all the guide comments that some users have succesfully writen all data to the nand by just skipping the first block that caused the error. In my case however, it seems that several blocks cant be updated. From block 2048 it seems that every 8'th block or so cant be updated. Could this be a ground bounce problem, or some problem related to the usb voltage dropping (haven't measured this yet)? Does anyone known if the Infectus2 requires a USB 2.0 connection (current output of >500mA)?
** SOLUTION **
By spending several hours I found that the nand had about 3/4 bad blocks from blocks 2048-4095. So I used my keys from the previous nand backup and the boot blocks posted on page 1 by Bad_Ad84 to generate a new nand.bin file using ohneschwezenegger.
In ohneschwezenegger I inputted the bad block numbers, and flashed the newly generated nand.bin to the Wii using my Infectus programmer setup.
This did the trick and my Wii now booted as if it were a brand new Wii =)
** END SOLUTION **
** Other noted that I would like to have answered though **
Also, several people stated that they cant see any devices to update when using the libusb32 filter wizard. If the infectus xavbox programmer driver is listed under libusb32 something in the device manager, the filter should already be installed correct? And this can't be related to my issue above?
It doesn't matter whether you flash the nand with the original bootmii backup (nand.bin), or the infectus clean (with WiiNAND) right? The only difference is that the keys are appended to the end of the nand.bin which are outside the 4095 block range anyway correct?
In regards to donor nands. You state that the boot1 of the donor nand has to match the one from my bricked wii's. I have another (black wii) nand backup with has boot1d, which is not the same as my bricked wii's (boot1c). But shouldn't it be posible to append the boot1c and boot2v4 (stock) from the bootblocks.rar file that bad_ad84 posted on page 1? Ofc i have the keys for both Wii's, so i should be able to perform the betwiin donor swap.
Also, I'm using Windows7 32-bit if that is of any importance =)
I have a fullbrick wii ... bootmii as ios and no nand backup.
With the infectus chip i get a complettly nand.bin.
There is now way to get the keys.bin?
Are the keys.bin hidden anywhere in the nand backup?
Where are the fuc***** keys.bin - sorry :)
What can i do?
Is there any tiny way to fix the brick?
I hear from .. Superblocs ....
What is a Superbloc?
thank you very much!
Comedian: No the keys are located within the Hollywood chip, and is not accessable from the nand chip. To obtain them you need a working Wii were you extracted a backup through BootMii e.g. after installing HBC.
So short answer, without the keys no way to fix bricked Wii by NAND flashing as this guide purposes.