Comments on: amoxiflash

By: nmaupu

nmaupu — Mon, 18 Jan 2010 20:04:21 +0000

Hi,

I had exactly the same problem as Bushing and Bonx (Bytes inserted).

I added a bounce-ground wire as bushing said. Not better …
So I added a very long (4 ou 5 times the sizes of all wires) WE (Q pin) wire and I confirm that works !

By: bushing

bushing — Mon, 04 Jan 2010 18:36:32 +0000

Yes, you can use the Infectus chip as described in this article, but it’s not much fun to solder up.

By: bluefire66

bluefire66 — Sun, 27 Dec 2009 15:43:21 +0000

Actually, I found a old nand backup and keys (from bootmii) for one of the wiis.

Can i flash this to the nand without bootmii, because mt wii cannot even get to it….

By: bluefire66

bluefire66 — Sun, 27 Dec 2009 15:19:50 +0000

@bushing:
Im sitting here with 2 bricked wiis and no nand backups…. i think they are a low level bricks because they do not show any picture on the screen. (the tv says “no signal”, but the wii makes the disk noise and the green LED lights up)

If i buy an infectus chip, would i have any luck unbricking them?

thanks

By: bushing

bushing — Sun, 06 Dec 2009 13:31:36 +0000

Yes, but you have to be careful. You can back up the corrupted NAND image, extract boot1 and boot2 (first 8 * 64 * 2112 bytes of NAND dump) from the corrupted NAND image, and replace the older boot2 in your old NAND dump with boot2v4. Then you can reflash with amoxiflash to downgrade.

(You must replace the older boot2 with the new boot2v4, because boot1 will not allow you to downgrade boot2.)

By: geekatcmu

geekatcmu — Wed, 02 Dec 2009 15:06:36 +0000

Assuming you have a NAND backup (from bootmii), could this technique be used to recover from a Korean Wii bricked by the 4.2 update?

By: winston154

winston154 — Sat, 05 Jul 2008 22:05:19 +0000

hopefully last question, I now have the program running, but I am getting an error:

[root@localhost amoxiflash]# ./amoxiflash dump test.dat
amoxiflash version 0.4, (c) 2008 bushing
infectus Device Found @ Address 005
infectus Vendor ID 0x010c4
infectus Product ID 0x082e3
Infectus version (?) = 81
Infectus Loader version = 128.1
PLD ID: SPI Programmer
ID = 200
ID = 200
ID = 200
Unknown flash ID 0200
If this is correct, please notify the author.

I do not have the push button or extra gnd wire hooked up yet, not worried about having a corrupted file from the infectus, just want to make sure I can get this to work. I have not updated it with the latest programming firmware from infectus, version 0.0.3.9. I also have the blue and amber LED light on the programmer, power is on on the system.

By: winston154

winston154 — Fri, 04 Jul 2008 13:07:28 +0000

It was operator error. Somehow the makefile was corrupted so I downloaded a new file and all is well.
now to try it out!!!! Thanks Bushing

By: winston154

winston154 — Fri, 04 Jul 2008 12:00:30 +0000

I am not getting that far, I downloaded the six files and I thought all I had to do is run the “make” command and it would compile it, but it doesn’t, I get: “Makefile:2: *** missing separator. Stop.”
I have looked for a step by step instructions for this on how to flash the Infectus chip but unable to find one, this is probably operator error also.

By: bushing

bushing — Thu, 03 Jul 2008 00:50:19 +0000

@winston154: Are you getting any error messages?