Dragona Akehi
Retired
JonathanEx said:
Essentially yes. The problem isn't that they're writing boot2 (though that is a risky thing to do anyway) it's that the code they used for this purpose was absolute crap on stickleback bass.
-
Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.
GAF Wii Homebrew thread: Homebrew, emulators, USB disc installs! Easy tutorial!
- Thread starter radioheadrule83
- Start date
Essentially yes. The problem isn't that they're writing boot2 (though that is a risky thing to do anyway) it's that the code they used for this purpose was absolute crap on stickleback bass.
JonathanEx
Member
Alright, cheers for the clarification. So this update could have been done properly, but Nintendo didn't.
And then when it gets to the homebrew checks, they were extremely crude and easily can be gotten around.
And then when it gets to the homebrew checks, they were extremely crude and easily can be gotten around.
Dragona Akehi
Retired
JonathanEx said:
Yes, it's really like Team Twiizers are the professionals, and the NCL team are the "hacks".
ZombieSupaStar
Member
HK-47 said:
mine didnt *shrugs*
never had a 360 or ps3 brick during an update either, just lucky i guess.
Marty Chinn
Member
ZombieSupaStar said:
This would be all over CNN if Nintendo released an update that bricked everybody's system. That's not te point. The point is they released an update that has a certain probability of possibly bricking your system when you update. It won't hapen to everyone, thus why you succeeded, but it can happen to anyone at any given time during the update.
360s and PS3s tend to try to limit the risk on how they are updating when updating their OS/firmware. Nintendo was just sloppy and did it half assed. There's a big difference between this which is an update Nintendo should have never released. Sony and Microsoft try to avoid releasing dangerous releases like this to the public. Try to understand the difference here.
ZombieSupaStar
Member
Marty Chinn said:
yeah I tend to trust Microsoft the most when it comes to software issues on consoles.....and I cant believe I just said that either... :lol
SlipperySlope
Banned
I have an RMA set up for my system already. The disk drive is constant DRE's.
I haven't sent it in for repair yet though. I'm considering upgrading to 4.2, and if it bricks, I can get both problems fixed at the same time.
What new does 4.2 bring?
I haven't sent it in for repair yet though. I'm considering upgrading to 4.2, and if it bricks, I can get both problems fixed at the same time.
What new does 4.2 bring?
Well I'm glad I read this now..figures, I was leaning towards just going back to the official firmware on my own Wii. I've played all the stuff I've got on my Wii right now anyway plus I want to be able to play Super Mario Wii when it gets out soon, Muramasa plus I STILL haven't gotten to play the new Punch Out. Feel like I'm the only one who hasn't gotten to play that yet too 
Guess I'll have to wait for a safe update before I try to go back to the ofw.
Guess I'll have to wait for a safe update before I try to go back to the ofw.So, just to recap.
I have a hacked Wii with the latest HBC, DVDX and BootMii set to IOS. If I wanted to take the chance and update to 4.2 (not that I would, until I had assurances that the danger of bricking was minimal), I'd have to remove all of those apps to do it "safely", and then reinstall them later, right? Or am I OK right now?
My Wii's NAND and everything else is safely backed up, btw.
I have a hacked Wii with the latest HBC, DVDX and BootMii set to IOS. If I wanted to take the chance and update to 4.2 (not that I would, until I had assurances that the danger of bricking was minimal), I'd have to remove all of those apps to do it "safely", and then reinstall them later, right? Or am I OK right now?
My Wii's NAND and everything else is safely backed up, btw.
I just realized that Nintendo didn't potentially brick 50 million consoles. Nintendo's saving grace for once is that most users don't connect their Wii's to the internet.
Nintendo pre-assumes that you're a pirate, before they even look at your system. If they find indisputable proof that you're NOT a pirate, then they'll repair it for free. It should be that anyone can send it in to be repaired for free (all warranties should be extended for bricks, since Nintendo iscertainly potentially the cause), but if they happen to find the slightest proof that you're a pirate, it voids the offer. It's effectively the same thing, but different.
And if it's bricked by Nintendo's tampering with the boot2, but you installed HBC purely to play imports, then you're screwed, regardless of the state of the warranty.Mejilan said:
Nintendo pre-assumes that you're a pirate, before they even look at your system. If they find indisputable proof that you're NOT a pirate, then they'll repair it for free. It should be that anyone can send it in to be repaired for free (all warranties should be extended for bricks, since Nintendo is
There is NO REASON for you to update to 4.2. All 4.2 does is remove your hacks, and risk destroying your system. Nintendo closed their store to anyone who doesn't agree to the update (ha ha, they won't be allowed to pay money for ROMs anymore, that'll show those pirates who's boss), but if you have homebrew, you can regain access the store, through methods mentioned earlier in the thread.Dambrosi said:
No.Dambrosi said:
First thing's first... DO NOT UPDATE. Whether you use homebrew or not, the official update procedure is nothing more than playing Russian Roulette with your Wii as the stake. You get no benefit. There are no games that will require the upgrade in future.
You likely DON'T have the latest HBC, DVDX and BootMii. They were all updated within the last 24 hours.
If you theoretically did want to update (even though the only reason to do this is if you are a masochist or fatally curious), then what you want to do is first upgrade HBC and BootMii. Then do the update (but seriously, don't) and then put BootMii back on as it will have been overwritten by the update. You will also need to install the new DVDX at this time, and wait fro your apps to support it.
tl;dr version: Don't update unless you enjoy pain.
BocoDragon
or, How I Learned to Stop Worrying and Realize This Assgrab is Delicious
How do I update BootMii and DVDx again? The HBC is obvious.. start it up and it checks for an update... but BootMii... Can I update through the app itself or do I have to download it on PC and put it on the card?Clipper said:
http://gwht.wikidot.com/bootmiiBocoDragon said:
http://gwht.wikidot.com/homebrew-channel
Look at the "Upgrading" sections, and they are all the same app, so you can use HBC to do the lot.
ShockingAlberto
Member
So if I'm to understand their customer service comments correctly, bricking modified Wii's is now policy rather than an unintentional but acceptable coincidence?
It's not a policy. They are just saying that it isn't their problem. The same thing as if you put your console near an edge and it dropped to the floor and broke. I don't blame them on that part. Punishing the legitimate users is something unacceptable, but they are now compensating for that too.ShockingAlberto said:
EatChildren
Currently polling second in Australia's federal election (first in the Gold Coast), this feral may one day be your Bogan King.
benita316 said:
I have no idea what specifically did it, but I'll tell you what I did; I erased the Wii partition on my USB and created a new one. I reinstalled Hermes cIOS with the latest version as found in the official tutorial. I had already installed Hermes cIOS and I haven't asked Extraction to use it, but I did it anyway.
Then it worked. Well, it got past all the menus. I haven't actually played it yet, but earlier the game would freeze every time during the introduction clips when the game boots. Now it gets to the menu and seems to be fine.
I'll give it some playtime later.
iamaustrian
Member
well, the update does fix the horrible "The Conduit" online glitch.
http://www.gamealmighty.com/nintendo-patches-the-conduits-spawn-glitch
http://www.gamealmighty.com/nintendo-patches-the-conduits-spawn-glitch
It's not that they're saying "we are going to brick your Wii", it's that they're saying "if your Wii happens to get bricked and you've been hacking it we're not fixing it free."ShockingAlberto said:
the update isn't meant to brick anything, it's meant to remove the homebrew stuff.
In other words, if your system is bricked and it hasn't been modified, they're like "okay this is obviously our fault we'll fix that right up." If they see it has been modified, they're like, "okay you been screwin around and hacking this thing so we ain't gonna be responsible for that."
Which I find perfectly reasonable.
It's not reasonable at all. If you took your car in to the dealer for a recall and they massively screwed something up, would you be ok with them then refusing to fix their screw-up because they don't approve of your aftermarket hubcaps?Htown said:
If they want to take that line they should do it like Microsoft (Windows) and simply not give you the patch if they don't like you, not give you a potentially fatal patch and then say "not our problem" when something goes wrong that has nothing whatsoever to do with the stuff they don't like.
Oh, OK. Then how do I access the Shopping Channel? I have several of the previous owner's VC games left to download, though thankfully I already got the best ones (Lylat Wars FTW!), and I heard there was a trick to regaining access without updating. Can anyone link me?Clipper said:
Oh, I do. I updated them this morning, before I heard about all this update=brick nonsense.:lolClipper said:
Relax, I'm not a masochist. I'll just wait it out.Clipper said:
If the hubcaps have some potential to screw up the car in a similar way to the problem and the manufacturer/dealer made it clear that non-sanctioned parts are potentially bad for the car, then yes. I'd have no problem with them doing that.Remfin said:
Installing Homebrew comes at a risk. E.g., if you are stupid enough to follow a tutorial that tells you to put cIOSCORP on your Wii, then you are at a high chance of bricking your Wii. Even installing BootMii is dangerous if your power goes out at an inopportune moment. When you started using the Wii online, you agreed that you would not use software that wasn't sanctioned by Nintendo. Hence, they are perfectly within their rights to refuse warranty privileges to you if you violate that agreement.
http://gwht.wikidot.com/wii-shopDambrosi said:
http://www.gwht.wikidot.com/upgrade-faqcrispyben said:
Edit: Oh, I missed how old your Gecko OS is too. Upgrade it too.
If Nintendo sees that your Wii has been modded, they have no idea whether it was for homebrew or piracy and I think it's reasonable for Nintendo to refuse to fix a console that they think may have been pirating their games.Remfin said:
Modding a Wii is clearing going to be against the terms of service/warranty/whatever, that's the risk you take if you do it.
GrotesqueBeauty
Banned
Scaremongering? It's always great to see someone express their gratitude so gracefully when other people are trying to watch their back.meppi said:
Starwolf_UK
Member
If I were to draw a real-world analogy to the matter I would use this:
http://news.bbc.co.uk/1/hi/health/8281673.stm
If we describe homebrew or piracy not functioning as an adverse reaction I guess we can draw the analogy that a Wii which bricks is a fatal reaction to the update. If we then say Wiis that were bricked had an underlying health problem (I know it is slippery slope...which might make it a poor analogy). I don't know about a great deal about ECC and if it is required but my guess is just the ECC not updating is not able to cause a brick on its own because the system might not require it to boot for some reason. But it not updating will cause a brick if the Wii needed to use the ECC it to boot.
The difference lies in the fact the local health authority quarantined the vaccination as soon as they heard the story and the maker will be running tests on the batch to see if they are any faults. Nintendo on the other hand have done nothing and clearly done insufficient testing.
Then there is the fact Cervarix has a clear purpose while updating boot2 does also have a purpose but considering the updates target (uniformed individuals) it ends up a rather baffling one. I was under the impression more casual users (who are most likely to go gung-ho into this update) wouldn't be using bootmii or backing up their NAND in the first place so losing the ability to do so wouldn't affect them.
I would love it if someone could find a better analogy but I hope this means there is more understanding between both sides of the debate and the points made. I have to say I'm pleased I've seen none of the "I've not had a brick. Clearly the people that have are pirating liars. My Nintendo would never do anything wrong." which seems to plague the debate on Nintendo fan sites.
http://news.bbc.co.uk/1/hi/health/8281673.stm
If we describe homebrew or piracy not functioning as an adverse reaction I guess we can draw the analogy that a Wii which bricks is a fatal reaction to the update. If we then say Wiis that were bricked had an underlying health problem (I know it is slippery slope...which might make it a poor analogy). I don't know about a great deal about ECC and if it is required but my guess is just the ECC not updating is not able to cause a brick on its own because the system might not require it to boot for some reason. But it not updating will cause a brick if the Wii needed to use the ECC it to boot.
The difference lies in the fact the local health authority quarantined the vaccination as soon as they heard the story and the maker will be running tests on the batch to see if they are any faults. Nintendo on the other hand have done nothing and clearly done insufficient testing.
Then there is the fact Cervarix has a clear purpose while updating boot2 does also have a purpose but considering the updates target (uniformed individuals) it ends up a rather baffling one. I was under the impression more casual users (who are most likely to go gung-ho into this update) wouldn't be using bootmii or backing up their NAND in the first place so losing the ability to do so wouldn't affect them.
I would love it if someone could find a better analogy but I hope this means there is more understanding between both sides of the debate and the points made. I have to say I'm pleased I've seen none of the "I've not had a brick. Clearly the people that have are pirating liars. My Nintendo would never do anything wrong." which seems to plague the debate on Nintendo fan sites.