Tyveil's forum posts
Bump =pZeroTae
Why keep bumping this? It's been stickied for like a week.
[QUOTE="55centv2"]What is it that im hearing about certain updates breaking your wii? I think that might happen to me? Is this true? Can some1 explain?MoldOnHold
Yes, there is an update out that permanently froze a very small number of Wiis, but that should've subsided by now. If it does happen to you, don't freak; Nintendo acknowledges the problem and will happily take in your Wii and repair it
EDIT - at no cost to you
Wrong. They send you a new Wii free of charge and you send your existing Wii back in that box. So you don't have to go any time without a Wii. Anyways the update does not "brick" your Wii as so many claim (including the Gamespot article).. all it does is makes it so you cannot go online (for updates or VC anymore).. playing games and everything else still works fine, so I wouldn't call that a brick. This update no longer goes out anymore, theres a newer one, so there is no chance this will happen to anyone else.
Before you send your Wii back try reformatting the system. I have heard from one person that they reformatted and there system was all good again.
I would guess that could work for the "Bricking issue".
Note that all your save data will be deleted.
hotplayer220
Seeing as how at this poing there is no way to move data from one Wii to another it is worth trying a system format.
I'm noticing problems with the sensor now. The pointer randomly disappears. I wonder if anyone else is having this issue.
Another tip that could probably use adding here. Some SD card saves will not transfer from the SD card to another system. Nintendo is aware of the problem and working on it. This could happen to a lot of people considering how many have already gotten faulty replacements.
http://www.gamespot.com/events/wiilaunch/forums/show_msgs.php?topic_id=25169498
[QUOTE="pzco"]Sometimes when I'm going back to the main menu, the system stays at a black screen for a looong time, usually like 2-3 minutes, and I get pissed off and restart...it does eventually go away on its own though. What's causing it?j03yAsunderI would like to know about this as well. Also on another note when I was playing Metroid Prime 2 on the Wii I shut it off and then turned it back on to check to see if I had messages and the pwer wouldn't turn on! I tried w/ the remote... Nothing, then manually and still it didn't turn on. I unplugged it and plugged it back then it worked. Whats up w/ that? One more thing how come some e-mails don't show up? For example SOME e-mails w/ picture attachments. They just completely dissappeared! And I was testing to see if newer ones would come up first and they did! The other e-mails were nowhere to be seen. What happened to them? Thanx for this thread its answered alot of problems I was having and now my mind is more at ease.
I had the constant black screen for awile. I turned my Wii from being vertical to horizontal and I haven't had the problem anymore.
Alright, I removed it until we get the finals ironed out. Just give me time!
redsox639109
You didn't need to remove it, just restate it:
Q: WiiConnect24 Error 110213
A: Internal Error with the Wii console, no fix. Call Nintendo to confirm the error and they will send you a replacement.
"Specifically" the first post doesn't say that answer for just that number: it says potentially WiiConnect errors in general. We all understand that particular error code is most likely died to the firmware issues they had; it's the tons of other iterations of the errors that are caused by issues on the user's side that are the concern: the last thing people need is to be thinking they need to ship their console back when it's just a router problem on their end. What you do and don't know about networking is immaterial.Spelunker
The only problem I see is the first post needs to take out the "(may be a wide range of errors)" because any way you look at it if you're getting Error 110213 your Wii is bad. No way around it. Anyways I wouldn't suggest just shipping in your console. Of course you should call first.
Log in to comment