Hacking Any good reason to NOT update WiiU to 5.5.2 (haxchi user)

[suzsuzuki]

I have haxchi installed, so any good reason to NOT update WiiU to 5.5.2?

(NOT or DON'T? I'm not a native english speaker)

 

[shanefromoz]

I would like to know this also please

 

[DontShootUp]

"Not" is correct

Unfortunately I don't have an answer to the question though.

 

[OrGoN3]

If you're that worried, make a nand backup (https://gbatemp.net/threads/nand-dumper-create-full-dumps-of-the-nand.465680/), backup all of those files to a computer/cloud/whatever, and then update. You can always revert back. Your Haxchi isn't going to disappear.

 

[MattKimura]

This is very debatable but me personally, I'm staying on 5.5.1 since 5.5.2 adds nothing new at all. I'd say wait til you actually have problems in 5.5.1 before updating. So far everything works just the same as before this update came out. Online play works just fine.

You could update, but then you also don't have to at all. At least stay on 5.5.1 for about a month or two before deciding on updating. I don't feel prohibited at all on 5.5.1 so I'm perfectly fine to enjoy my content as usual. I'm not even spoofed and things work fine, but I am using CBHC though.

 

[The Real Jdbye]

I have haxchi installed, so any good reason to NOT update WiiU to 5.5.2?

(NOT or DON'T? I'm not a native english speaker)

I would like to know this also please

Easy.
If anything ever goes wrong with your Haxchi install, for example if an update goes wrong or you reinstall it to change the config and you mess up the config, then you'll have no way to reinstall it. No way to get back into homebrew. You'll be screwed.
Not having any primary entrypoint and relying completely on a secondary entrypoint that might stop working at some point is worrying to me.

 

[Madridi]

Easy.
If anything ever goes wrong with your Haxchi install, for example if an update goes wrong or you reinstall it to change the config and you mess up the config, then you'll have no way to reinstall it. No way to get back into homebrew. You'll be screwed.
Not having any primary entrypoint and relying completely on a secondary entrypoint that might stop working at some point is worrying to me.

Exactly this.

If anything happens to haxchi (removed by mistake, corruption, etc..) you are left without another exploit to fix it. This alone outweighs the benefits of updating since update does nothing that you can't do on 5.5.1

 

[InsaneNutter]

You gain nothing by updating and loose the only primary exploit you have as @The Real Jdbye mentioned, so why would you knowingly update?

 

[Deleted User]

Don't update to 5.5.2 if you have CBHC installed, it has chance to break (still works but it will not bootup on startup)

 

[C0mm4nd_]

Don't update to 5.5.2 if you have CBHC installed, it has chance to break (still works but it will not bootup on startup)

well, the app is still there, so you can just launch it and launch CBHC installer

 

[fille]

i updated to 5.5.2 with cbh,no problems here,homebrew works-games on usb works.

 

[kublai]

In theory if you are on 5.5.1 than your FW is still exploitable still if they find another hole in the browser?

 

[godreborn]

I'm staying on 5.5.1 for the reasons mentioned. I was so paranoid that my console may have updated without me knowing it that I tested browserhax. everything worked as it should. I'm using cbhc btw, so I couldn't check by going into the system settings unless I uninstalled it.

 

[biggan1]

If it ain't broken definitely wait, see if any new entry points arises. People shouldn't hurry so much updating their modded console.. You need to be sensible with your actions once you installed any Homebrew, many people are way to unhesitant in doing stuff that can brick with no knowledge to updating when not needed at all.

I feel sad for those whom got their console autoupdated, but they should've blocked DNS in the first place.

Personally mine wasn't even plugged in when the update dropped and I will stay on 5.5.1 atleast for now, I will see and let the time pass. If new entry point is found I might update, if not I'll stay on my current firmware.

You never know if you need to format your Wii for some reason and boom no entry point. I know it can be restored with nand backups. But many don't even have that nor know how to use it.. Hence I'm staying on 5.5.1, it's just easier and safer for the avarage user to NOT UPDATE at the moment if you don't have any problem now, since the update juśt blocks browserhax and adds no functional to the console.

 

[retrofan_k]

If it ain't broken definitely wait, see if any new entry points arises. People shouldn't hurry so much updating their modded console.. You need to be sensible with your actions once you installed any Homebrew, many people are way to unhesitant in doing stuff that can brick with no knowledge to updating when not needed at all.

I feel sad for those whom got their console autoupdated, but they should've blocked DNS in the first place.

Personally mine wasn't even plugged in when the update dropped and I will stay on 5.5.1 atleast for now, I will see and let the time pass. If new entry point is found I might update, if not I'll stay on my feet.

You never know if you need to format your Wii for some reason and boom no entry point. I know it can be restored with nand backups. But many don't even have that nor know how to use it.. Hence I'm staying on 5.5.1, it's just easier and safer for the avarage user to NOT UPDATE at the moment if you don't have any problem now, since the update juśt blocks browserhax and adds no functional to the console.

It's good to see this mindset here, as practically everyone, even some long term members here I have seen update, as soon as a new fw is pushed (especially on the 3DS) out without properly weighing up the pros and cons first.

 

[LaPingas]

I'm staying on 5.5.1 for the reasons mentioned. I was so paranoid that my console may have updated without me knowing it that I tested browserhax. everything worked as it should. I'm using cbhc btw, so I couldn't check by going into the system settings unless I uninstalled it.

You can launch mocha from cbhc menu and then go to settings to see the real sys ver

 

[Rinnux]

If it ain't broken definitely wait, see if any new entry points arises. People shouldn't hurry so much updating their modded console.. You need to be sensible with your actions once you installed any Homebrew, many people are way to unhesitant in doing stuff that can brick with no knowledge to updating when not needed at all.

I feel sad for those whom got their console autoupdated, but they should've blocked DNS in the first place.

Personally mine wasn't even plugged in when the update dropped and I will stay on 5.5.1 atleast for now, I will see and let the time pass. If new entry point is found I might update, if not I'll stay on my current firmware.

You never know if you need to format your Wii for some reason and boom no entry point. I know it can be restored with nand backups. But many don't even have that nor know how to use it.. Hence I'm staying on 5.5.1, it's just easier and safer for the avarage user to NOT UPDATE at the moment if you don't have any problem now, since the update juśt blocks browserhax and adds no functional to the console.

A friend of mine just got his Wii u a couple days ago. I walked him through the steps of blocking updates with the DNS settings and his Wii still auto updated. Sometimes the DNS block doesn't work.

 

[the_randomizer]

There's no compelling reason to go to 5.5.2, no functionality is added, nothing is fixed or improved, why would anyone want to update to an exploit-breaking firmware?

 

[biggan1]

A friend of mine just got his Wii u a couple days ago. I walked him through the steps of blocking updates with the DNS settings and his Wii still auto updated. Sometimes the DNS block doesn't work.

Hm strange, I feel bad for him. I'm not using any online services for the moment. Although I would probably be pretty safe. Nevertheless I got all games on my hard drive already.

Not updating to 5.5.2 not yet anyways. The future will tell, people should be more hesitant and wait and see when we know it's an anti exploit patch.

 

[Psionic Roshambo]

Using just DNS will not block everything.

You need to go into your router settings and if possible block these addresses.

*.cdn.shop.wii.com
*.cdn.wup.shop.nintendo.net
*.deploy.akamaitechnologies.com
*.deploy.static.akamaitechnologies.com
*.wup.shop.nintendo.net
184.50.229.137
184.50.229.158
96.17.161.145

23.65.181.75
http://nus.cdn.shop.wii.com/ccs/download/
c.shop.nintendowifi.net
cbvc.cdn.nintendo.net
cbvc.nintendo.net
nus.c.shop.nintendowifi.net
nus.cdn.c.shop.nintendowifi.net
nus.cdn.shop.wii.com
nus.cdn.wup.shop.nintendo.net
nus.wup.shop.nintendo.net

The reason DNS will not block everything is those IP addresses (the just numbers octets) do not require any DNS for connectivity. DNS is short for Domain Name Server, it basically translates www.yourname.com into 255.255.255.255 (an invalid IP there, well it's valid but not used...) if you have 123.123.123.123 you don't need to go through DNS at all.

I hope this clears up some confusion about how Wii-U's can update in spite of having some weird DNS settings.

list shamelessly copied from https://wiiuhax.com/tutorial-how-to-block-wii-u-firmware-updates/