Simply put, updating a Wii bricked a Wii

This can’t be good. And we’re not talking about 60″ projection TVs this time. wC, the proprietor of his or her very own wheelsee.net blog, and for a moment the proud owner of a Wii, lost her console to the 2.0 update via WiiConnect24. The picture above from wC gives a very good summary of what happened at the end of the entire ordeal, but here’s the bullet-point summary of what happened:

• wC connects to WiiConnect24, update to 2.0U prompted
• At the prompt, system firmware updates to 2.0U
• wC attempts to reconnect to WiiConnect24 again with new 2.0U
• Result? “Error Code: 110213 There is a problem with the WiiConnect24 service. Please try again later.“
• According to Ninty Customer Service: Error Code 110213 = “we ask that you call us at (800) 255-3700”
• wC calls up (800) 255-3700
• Guy at the other end of the line says that “I (wC) have a hardware error and will have to be sent a new consoleÂ…so IÂ’m done with my Wii for a couple days as I canÂ’t transfer the saves from Zelda anymoreÂ…the new Wii is on the way but will take 3-4 business daysÂ…”
• Speaking of which, it might be a bit longer than three to four business days… wC later checks Nintendo.com and they show the replacement unit as under “backorder”.

This bit of news has, as wC observed, “been dugg’d and kotaku’d and in some aspect joystiq’d”, and now he or she has been QJ’d, too, but the hard part is that “it just sucks that the NOA reps are saying itÂ’s not widespread but it definately sounds like it as s a lot of people are having the issueÂ…”

This is the first strangled cry of pain we’ve heard so far but once this goes up on post, we’re gonna hear from our readers, both who will claim this is not so and claim that this is true… Sigh. Speculation can abound whether this is the firmware, or the hardware, or just random bad luck. How’s your Wii, if we may be bold to ask?

This can’t be good. And we’re not talking about 60″ projection TVs this time. wC, the proprietor of his or her very own wheelsee.net blog, and for a moment the proud owner of a Wii, lost her console to the 2.0 update via WiiConnect24. The picture above from wC gives a very good summary of what happened at the end of the entire ordeal, but here’s the bullet-point summary of what happened:

• wC connects to WiiConnect24, update to 2.0U prompted
• At the prompt, system firmware updates to 2.0U
• wC attempts to reconnect to WiiConnect24 again with new 2.0U
• Result? “Error Code: 110213 There is a problem with the WiiConnect24 service. Please try again later.“
• According to Ninty Customer Service: Error Code 110213 = “we ask that you call us at (800) 255-3700”
• wC calls up (800) 255-3700
• Guy at the other end of the line says that “I (wC) have a hardware error and will have to be sent a new consoleÂ…so IÂ’m done with my Wii for a couple days as I canÂ’t transfer the saves from Zelda anymoreÂ…the new Wii is on the way but will take 3-4 business daysÂ…”
• Speaking of which, it might be a bit longer than three to four business days… wC later checks Nintendo.com and they show the replacement unit as under “backorder”.

This bit of news has, as wC observed, “been dugg’d and kotaku’d and in some aspect joystiq’d”, and now he or she has been QJ’d, too, but the hard part is that “it just sucks that the NOA reps are saying itÂ’s not widespread but it definately sounds like it as s a lot of people are having the issueÂ…”

This is the first strangled cry of pain we’ve heard so far but once this goes up on post, we’re gonna hear from our readers, both who will claim this is not so and claim that this is true… Sigh. Speculation can abound whether this is the firmware, or the hardware, or just random bad luck. How’s your Wii, if we may be bold to ask?