There's at least two Infectus guides on this site, did you even bother to check them out or attempt to follow them?
i have a bricked Wii here. Unfortunately I have no NAND Backup and no Keys. I connect the NAND Chip with the Infectus 2 and used the Infectus NAND Flasher 1.03 to make a NAND dump. With WiiNand I have extracted the Keys to keys.bin.
Then I used Betwiin to make another NAND Backup with the keys.bin.
Everything worked fine.
Now I want to flash the new NAND with the Xavbox NAND Programmer, but if I compare the data after the flash, it es different. The Programmer also show the wrong Chip Ident. It shows Hynix HY27UF084G2M, but the Chip on the Wii board is a Hynix HY27UF084G2B.
Is there anything I forgot to do?
Can anybody tell me, for what the two switches on the little Infectus board are? (the one with the usb port). The description ist "ON" on the one side and 1,2 on the other side.
This is usually due to a bad connection or crossed connection (short) to your NAND.Now I want to flash the new NAND with the Xavbox NAND Programmer, but if I compare the data after the flash, it es different.
Is this happening with Xavbox or the Infectus flasher or both? What version of Xavbox are you using and where did you download it from? Are you sure you have the most recent drivers?The Programmer also show the wrong Chip Ident. It shows Hynix HY27UF084G2M, but the Chip on the Wii board is a Hynix HY27UF084G2B.
He is probably correct about the chip part number.
The applications have the chip name hardcoded. When you ID a chip, it doesnt return the full name, just an ID.
However, the different between G2M and G2B is just which generation it is (according to the datasheets) and likely give the same ID. So thats not a problem and can safely be ignored.
This is probably just typical infectus ground bounce.
I made a NAND dump with the Infectus NAND Flasher 1.03 from the bricked console. And with WiiNAND I extracted the Keys from this dump.
I tried to follow this guide http://www.wiihacks.com/bricked-wii-...-tutorial.html, but the wii does not have a vulnerable boot1.
You cant extract the keys from a dump created with Infectus, only from dumps made with bootmii.
This is because bootmii adds the keys onto the end of the nand dump. The keys are NOT stored in the NAND, they are within the hollywood CPU and you need to run code on the Wii to get them.
If your boot1 isnt vulnerable and you do not have the nand backup or keys from BOOTMII, you cant fix it.
This has been said a million times, in a million threads.
But why WiiNAND shows me the keys when I opened the NAND dump which I made with the Infectus NAND flasher?
I'm not sure how Wiinand would've given you any sort of keys in the first place
As Bad_Ad said, the keys aren't attached to the NAND.
You probably had keys.bin in the same folder from another wii?
Doesnt really matter, as what you are trying to do cannot be done.
Why do you think we tell people you cant fix the wii without a backup or vulnerable boot1 if this worked?