Hacking Wii U Hacking & Homebrew Discussion

  • Thread starter Thread starter filfat
  • Start date Start date
  • Views Views 5,122,208
  • Replies Replies 21,104
  • Likes Likes 29
ok so if i stay on lower firmware and do the vwii ssb exploit i wont have any trouble updating to 5.3.2 when i need to , because i would love to play some gamecube games on my wiiu for now ?
 
ok so if i stay on lower firmware and do the vwii ssb exploit i wont have any trouble updating to 5.3.2 when i need to , because i would love to play some gamecube games on my wiiu for now ?

Yeah, you'll be fine. Just do NOT patch any vIOSs, that has the potential of bricking the update feature
 
exactly what he said lol ^^^^^ basically run the wii mode smash exploit (any exploit like normall except letter bomb) and then only install d2x thats given in the guide on this website
 
  • Like
Reactions: JVC2
ok thanks both of you , will try it later on ,wonder if my third party wii u pro controller would work

Not to get your hopes down, but it probably won't. Still, you won't know until you try! :P

Edit: If we're talking about vWii homebrew, that is. Third party WUP controllers have a surprising compatibility when it comes to Wii U software
 
Not to get your hopes down, but it probably won't. Still, you won't know until you try! :P

Edit: If we're talking about vWii homebrew, that is. Third party WUP controllers have a surprising compatibility when it comes to Wii U software


ok well i have a wii classic controller for wii and i have a playstation 2 usb adapter , so one of them has to work lol
 
Sooo I shouldn't have updated to 5.3.2 this morning? Mother &%$#*+! Meh it's cool though, I wanted to get the MK8 title update and dlc.

No, you're fine, 5.3.2 has been confirmed safe. However, there's always the (accurately-based) mentality that the lower the firmware you can stay on, the better off you'll be. If you have a reason/desire to update to 5.3.2 (such as DLC, eShop exclusive content, Club Nintendo code redemptions, etc.) then by all means there's nothing stopping you from doing so, but if not, and you are specifically waiting for homebrew, its recommended that you don't update unless you have to. Just remember that no one is forcing you to do anything, not even devs, the most any of us can do is recommend what to do.

Hope that clears some confusion up :)
 
  • Like
Reactions: digipimp75
said it was fine to update yea. but nobody made it clear that the webkit exploit doesnt work on that firmware (to my knowledge)!!!
The old webkit exploit does not work for 5.1.0+,but that doesnt mean a new one will appear,so thats why unless you are going for code,then you dont need to worry that much.
A new webkit exploit could still be ported to new FW.
 
  • Like
Reactions: jammybudga777
sweeeeet. i have been considering updateing as it would be nice to have the other features added in 5.++........ but ill hold out just a little while
 
The old webkit exploit does not work for 5.1.0+,but that doesnt mean a new one will appear,so thats why unless you are going for code,then you dont need to worry that much.
A new webkit exploit could still be ported to new FW.


So those on 5.2.0 are shit outta luck. Great.
 
So those on 5.2.0 are shit outta luck. Great.

Shhhhhhhhh it's ok friend, don't cry

No, don't worry, those of us on 5.3.0 and up are fine, there are still literally hundreds (if not closer to thousands) of potentially exploitable bugs in the version of WebKit that Nintendo is using, and we have a handful of dedicated testers working to uncover them. So yeah, we will not be excluded, and it sounds like they have at least one, if not a few in development right now, so worst case it will just take a little extra longer, that's all :)
 
I thought 5.3.2 was confirmed safe?

its safe since the kernel exploit works,but people that stay on 5.1.0 or less have the webkit exploit,while new FW doesnt,so we have to wait for one to appear,and Kelton2 just was mentioning his web browser exploit that looks very exploitable.
In all terms,we are ok since the kernel hasnt been fixed in 5.3.2.
 

Site & Scene News

Popular threads in this forum