Hacking Now, why can't we install system updates using WUP Installer?

  • Thread starter Thread starter AboodXD
  • Start date Start date
  • Views Views 1,673
  • Replies Replies 15
  • Likes Likes 1

AboodXD

I hack NSMB games, and other shiz.
Member
Joined
Oct 11, 2014
Messages
2,880
Reaction score
1,880
Trophies
1
Location
Not under a rock.
XP
3,048
Country
United Arab Emirates
This is really confusing?

Did somebody think about this?

Edit: If this has already been answered somewhere, don't go "faceplam"ing yourself just because I missed the answer.
 
Last edited by AboodXD,
  • Like
Reactions: Quantumcat
I also wanted to know the same thing, but didn't want to look stupid by asking. Thanks :-)

Why is it different to the 3DS? (Since you can use sysupdater and NASA above 9.2 to install legit games, game updates, and system update files)
 
I also wanted to know the same thing, but didn't want to look stupid by asking. Thanks :-)

Why is it different to the 3DS? (Since you can use sysupdater and NASA above 9.2 to install legit games, game updates, and system update files)
I haven't personally tried it... but you might be able to using the WUPInstaller version I released that has checks disabled.
 
I also wanted to know the same thing, but didn't want to look stupid by asking. Thanks :-)

Why is it different to the 3DS? (Since you can use sysupdater and NASA above 9.2 to install legit games, game updates, and system update files)
You would very likely receive a brick if you install system update package using nasa/fbi/devmenu.
 
no only if native firms needs to be updated and the hax you are in is blocking that
nasa/fbi/devmenu update native firm title but do not update firm0/firm1 partitions. So if don't use sysupdater (which calls additional api to update those partitions) and your native firm has conflicts with new titles, you'll end up having a brick.
This area is unexplored on wii u. We don't have guarantee that simple system title installing will end up good.
 
nasa/fbi/devmenu update native firm title but do not update firm0/firm1 partitions. So if don't use sysupdater (which calls additional api to update those partitions) and your native firm has conflicts with new titles, you'll end up having a brick.
This area is unexplored on wii u. We don't have guarantee that simple system title installing will end up good.
ok cool, someone needs to test! it will be interesting
 
I also wanted to know the same thing, but didn't want to look stupid by asking. Thanks :-)

Why is it different to the 3DS? (Since you can use sysupdater and NASA above 9.2 to install legit games, game updates, and system update files)
The Wii U is much more picky with updates and partial updates are more likely to brick. That's probably not the only reason though. Since there's no easy way to download full update packages and there's nothing stopping people from installing single titles for some reason or other, they blocked most system titles from installing so that they wouldn't be blamed for any bricks. If you already have kernel access there's no reason to update, you can just spoof and use nnu-patcher. Even if that changes there's no way to update to the newest firmware to get access to eShop and online etc. while keeping kernel access. It would just brick. So there's no reason anyone would need to update other system titles right now, but if that changes they will probably release a version with a modified whitelist that allows those things.
 

Site & Scene News

Popular threads in this forum