Fixed!Let's hope nintendo has provided an easy way to reflash the nand in case of problems. Maybe they learned something from the many bricked wii's because of Waninkoko that they got 4 repair.
Long time ago I thought I read something correctly on Wii, this was like two years ago, and bricked it using his little tool. Thought I read it correctly and was only updating an IOS. might have removed one (must have). No bootmii, no priiloader, no nand backup; end of Wii;-( Oh well, nothing a good old Walmart special could not fix. Greatest price in the world at Walmart;-)
That might have been it;-). Thanks for sharing that.it was one of his updater programs that was bricking consoles.
Not sure for what system menu it was for but anyway it grabbed the latest ios file needed for the system menu from the nintendo servers.
Well it worked fine until nintendo released the next update in which case made the previous system menu ios file a stub and wankys updater still grabbed the same ios file which was now a stub.
sh*t happens...
Funny how it's always the people who do understand the process that point the blame at waninkoko, and the people who don't that jump in to defend him. His code was bad, it bricked Wiis, it bricked PS3s. It's not a case of pointing blame at some scapegoat, he wrote bad software which caused bricks. That is fact.Exactly, that's the price to pay for hacking your system. There is always a risk, most people just don't understand the process and look for the first person to blame.
I agree that it was bad coding (specifically the lack of safety checks), but he didn't say "Hey, try this, it is 100% safe". I'm not defending his coding, but people accept the risks involved (even if they don't understand them) when they run an app.Funny how it's always the people who do understand the process that point the blame at waninkoko, and the people who don't that jump in to defend him. His code was bad, it bricked Wiis, it bricked PS3s. It's not a case of pointing blame at some scapegoat, he wrote bad software which caused bricks. That is fact.
I agree that it was bad coding (specifically the lack of safety checks), but he didn't say "Hey, try this, it is 100% safe". I'm not defending his coding, but people accept the risks involved (even if they don't understand them) when they run an app.
Actually, wanky's Safe Updaters were designed to grab the latest IOS version. It was never hard coded to a specific IOS version....wankys updater still grabbed the same ios file which was now a stub.
He didn't do any good that other people could not have done. Hermes (a construction worker) made a cIOS also, and he never caused anyone to get a bricked wii. And just look at d2x right now, it has overcome a lot of issues that wanky said could never be fixed, and now that d2x started going on a roll wanky asked if he could help with it so he could get his name back in on it.It's true Waninkoko made some mistakes that caused bricking but he also did a lot of good things for the Wii scene.
NEVER underestimate the power of human error;-) No matter how well something is made, human beings will find a way to make a brick. Just history here, not even really opinion.Not being a thieving pirate, I'd be exactly as happy as I was with the HBC. He did nothing but kludge together other people's work fairly similar to Geohot, with a little help from those who did know what they were doing and released for the glory the moment it "worked" at all. His work was inherently unsafe by (lack of) design. It was irresponsible and many paid a high price - often a deserved one for the desired ends, but anyway. One thing nobody can claim of TT/f0's work. Unaware of even one legitimate "HBC bricked my Wii" claim after all this time. These things don't "just happen". They happen if you don't take the time and care to test, reiterate and employ enough checks.
Obviously some people are able to talk there; it is a public IRC channel. This remark of yours makes no sense (getting used to that from you...)Sounds like some are able to talk on #wiiudev;-)
It sounds to me like you are contradicting Stalkid64X's point that Team Twiizer's stuff has never bricked a (public) Wii: if so, you're even dimmer than I thought. What he said is fact, I have not once read of any legitimate claim that anything made by TT has caused a brick. (I think one person maybe reported that he lost power during the BootMii/boot2 installation, but that has absolutely NOTHING to do with the code).NEVER underestimate the power of human error;-) No matter how well something is made, human beings will find a way to make a brick. Just history here, not even really opinion.