Comments on: bricks wanted?

By: erikie

erikie — Tue, 12 Jan 2010 10:50:13 +0000

I found a board with a Hollywood that has date code 0807 and has boot1b in it. I managed to get bootmii into the nand it works, only problem I have is that it is not doing any more than that. cboot2 fails to load IOS and system menu is not coming on. Although ios30 is present on the system with sysmenu 3.1. Could this be a cpu failure?

By: bushing

bushing — Wed, 06 Jan 2010 05:17:11 +0000

Erkie: the main thing there is that your board was made in week 30-33 of 2008 — so we know that the transition to boot1c (the first fixed one) happened in 2008, I don’t think the exact PCB rev is as important.

I’d be more interested in finding someone with a PCB (or more specifically, a Hollywood chip) that was made in 2008 but had boot1b.

By: erikie

erikie — Tue, 05 Jan 2010 18:24:10 +0000

Looked at the mobo again now I am at home. Here are some date codes from the chips:
Hollywood: 0830
Broadway: 0830
Mainboard: 08338 (Rev 01)
This one already had boot1c in nand memory.

By: erikie

erikie — Tue, 05 Jan 2010 14:19:27 +0000

I got this information from underneath the revision type of the mainboard next to the SD slot. As it is a v01 board. I will take a picture of the board and post it later. Are you still interested in images of boards? As I have all 3 versions at home.

By: bushing

bushing — Mon, 04 Jan 2010 18:58:01 +0000

If this happens to anyone else, please take a NAND dump of the bricked state and just send me that dump.

By: bushing

bushing — Mon, 04 Jan 2010 18:40:33 +0000

“PRN M07 1″? Where do you see that? The date code for the main PCB is on the bottom of the board, under where the SD slot is located.

You can see the date code on the Broadway and Hollywood chips — it’s the first 4 digits of the last line with numbers on each chip package. No, it’s not possible that they replaced the CPU or changed keys, I think you misread the date code on the PCB.

By: 59672

59672 — Sun, 03 Jan 2010 05:15:54 +0000

I recently got a brick from updating. I couldn’t run any other software but bootmii. I restored my wii but im going to see if i can get it to brick again by updating. fyi i got my wii on launch.

By: erikie

erikie — Wed, 30 Dec 2009 21:24:53 +0000

Maybe not the place to comment, but I think I have a bricked mainboard that was produced in 07 week 1 (mainboard says: PRN M07 1) it is a version 01 board. Strange thing is this comes out of a half year old wii which was bricked by someone. It contains boot1c.
As this board is quite old, could they replaced the cpu with a new key or did they change the key. That is my question
it contains Hollywood AA and Broadway B cpu

By: marcan

marcan — Wed, 23 Dec 2009 11:05:40 +0000

BootMii should not cause any increased chance of bricks. People without BootMii are getting bricked. The chances of brickage are slim; they’re relevant in the grand scheme of things for Nintendo, but individually they’re pretty slight.

By: halsafar

halsafar — Fri, 18 Dec 2009 04:35:20 +0000

So, not to sound like a hound. But I have been using bootmii installed in boot2 since the day of the first beta release. It has been the pride and joy of my Wii, always amazes people.

I have been reading all of the comments on this site about the 4.2 update and I am confused about one thing.

Did bootmii cause this? Or do you not know for sure? Are people without boot mii getting bricked, if so I would conclude bootmii has nothing to do with it.

I have fw3.4U loaded right now with HBC1.06, bootmii/boot2 (newest) installed. I just bought New Super Mario Bro’s out of excitement and then remembered how out of date my Wii is. Should I update or will I be mailing you my Wii soon (heh)? I did a NAND dump with the keys already just in case.