Hacking Wii U System Update 5.3.1E/U

  • Thread starter Thread starter Teh H4rRy
  • Start date Start date
  • Views Views 13,702
  • Replies Replies 45
  • Likes Likes 1

Teh H4rRy

Well-Known Member
Member
Joined
Jun 12, 2009
Messages
145
Reaction score
3
Trophies
1
XP
151
Country
Version 5.3.1 U, available via an Internet connection, includes the following improvements:
Mario Kart 8 highlight reel upload fix:
  • Resolved an issue that resulted in some users receiving error code 104-1852 while uploading a Mario Kart 8 highlight reel to YouTube
Improvements to system stability and usability:
  • Further improvements to overall system stability and other minor adjustments have been made to enhance the user experience
Source

I just updated (5.3.1E) and tested my vWii, USB loading, Nintendont and Homebrew all seem to be in order. I haven't tested in depth but it doesn't break anything obvious that I can see.
 
  • Like
Reactions: SSG Vegeta
Keep in mind that there is no concrete evidence on what this does to exploits for certain, other than patching one of the holes, so if people care about a full blown exploit, it's best not to update. If you only care about vWii, go ahead and update.
 
I LOL whenever I see "Further improvements to overall system stability and other minor adjustments have been made to enhance the user experience." AKA "we fixed all your exploits you haven't found yet, suckers!"


Pretty much, it's their own euphemism of saying "we patched your haxxors trololololol" XD
 
Im
I don't know about stability, but it was damn slow back in 2012. Glad they fixed that (for the most part).

I'm still using 4.03 and that slow response times in the menus, etc, was fixed ages ago around 2.xx something if i remember
 
DO NOT UPDATE UNTIL FURTHER NOTICE.
5.3.0: Mozilla/5.0 (Nintendo WiiU) AppleWebKit/536.28 (KHTML, like Gecko) NX/3.0.3.12.14 NintendoBrowser/4.1.0.9584.US
5.3.1: Mozilla/5.0 (Nintendo WiiU) AppleWebKit/536.28 (KHTML, like Gecko) NX/3.0.3.12.15 NintendoBrowser/4.1.1.9601.US

They have updated NX yet again, and pushed an entirely new version of Nintendo Browser (I'm just calling it that from now on) 4.1.0 > 4.1.1 and updated NX.
 
[quo
DO NOT UPDATE UNTIL FURTHER NOTICE.
5.3.0: Mozilla/5.0 (Nintendo WiiU) AppleWebKit/536.28 (KHTML, like Gecko) NX/3.0.3.12.14 NintendoBrowser/4.1.0.9584.US
5.3.1: Mozilla/5.0 (Nintendo WiiU) AppleWebKit/536.28 (KHTML, like Gecko) NX/3.0.3.12.15 NintendoBrowser/4.1.1.9601.US

They have updated NX yet again, and pushed an entirely new version of Nintendo Browser (I'm just calling it that from now on) 4.1.0 > 4.1.1 and updated NX.


Oh, well, okay then. So, uh, what if they release a patch for SSB?
 
[quo


Oh, well, okay then. So, uh, what if they release a patch for SSB?

If anything it's a hardware problem, meaning you'd have to send it in, or it's a software problem, and they'll just push 5.3.2 to fix it. It's not just smash.
This has happened with:
https://www.reddit.com/r/smashbros/comments/2o2ems/error_1600103_its_not_smash/
EDIT: It's also not on the latest system version either, it's been happening since it's release.
 
  • Like
Reactions: Adr990
If anything it's a hardware problem, meaning you'd have to send it in, or it's a software problem, and they'll just push 5.3.2 to fix it. It's not just smash.
This has happened with:
https://www.reddit.com/r/smashbros/comments/2o2ems/error_1600103_its_not_smash/

EDIT: It's also not on the latest system version either, it's been happening since it's release.


Ah, but if you had to send it in or update via a patch for the game, one is pretty much screwed as Nintendo would just update it to 5.3.x. I don't like this at all. I haven't had that error before, and I sure as hell hope I don't get it. Otherwise, I pay 100 dollars for repair and get back a force-updated console from Nintendo. Ugh... How do I know I'm not one of the "lucky" ones with this problem? Oh and it's a 8 GB model from 2012, so, now I'm actually afraid to turn it on or play SSB. Maybe I should just sell all my games to avoid this. Hell, maybe I should just sell the Wii U as I might have a defect. Ah crap.
 
Ah, but if you had to send it in or update via a patch for the game, one is pretty much screwed as Nintendo would just update it to 5.3.x. I don't like this at all. I haven't had that error before, and I sure as hell hope I don't get it. Otherwise, I pay 100 dollars for repair and get back a force-updated console from Nintendo. Ugh... How do I know I'm not one of the "lucky" ones with this problem? Oh and it's a 8 GB model from 2012, so, now I'm actually afraid to turn it on or play SSB. Maybe I should just sell all my games to avoid this. Hell, maybe I should just sell the Wii U as I might have a defect. Ah crap.
Never heard of this before, yet dont use the wiiu for anything except ZombiU and Vwii softmod for GC isos as im still on 4.03. What is actually triggering this error? Semi brick or full brick?
 
Never heard of this before, yet dont use the wiiu for anything except ZombiU and Vwii softmod for GC isos as im still on 4.03. What is actually triggering this error? Semi brick or full brick?


No one really knows aside from possibly a few units with defective NAND chips causing memory corruption with a Wii U game. 5.2.0 is the cutoff for the exploit.
 
so highest safe firmware is still 5.2.0?

Almost certainly 5.3.0, but unsure about 5.3.1 since the number of bugs we have is going down steadily. It may end up like the 3DS where we only have access to a certain range of firmwares, unless we do it ourselves and find a new bug to exploit that nobody has found before. Of course that'd require a lot more manpower/more skilled people at finding exploits to do so.
EDIT: So it's time to call in anyone and everyone you know who can research exploits, tell them to download the latest version from Nintendo Browser (http://www.nintendo.co.jp/support/oss/index.html#oss_wiiu) and start looking.
 
If i get that error I would be so pissed. They would update my firmware from 5.2.0 to latest and still not fix the error because I installed hbc:dry:
 
If i get that error I would be so pissed. They would update my firmware from 5.2.0 to latest and still not fix the error because I installed hbc:dry:


Again, it only affects a very small no. of Wii U consoles, just like how some Wii consoles couldn't read dual-layer discs, same kind of situation. Stay on 5.2.0 to be safe, that's what I'm doing. Another theory is people are closing the game down when it auto-saves. If people do get the error, do NOT go into Data Management.
 
As someone who played For Glory, Crazy Orders, Wind Waker HD, New Super Mario Bros U, Hyrule Warriors, Mario Kart 8, Black Ops 2. I have not encountered this error nor has my friend. Probably happening to certain WiiU's.

My WiiU: 8GB, bought May 2013
My friends: 32GB, bought on launch.
 

Site & Scene News

Popular threads in this forum