Hacking Wii U Hacking & Homebrew Discussion

  • Thread starter Thread starter filfat
  • Start date Start date
  • Views Views 5,119,061
  • Replies Replies 21,104
  • Likes Likes 29
Hi. Say I didnt want to exploit the wii u, but I already have the vwii mode hacked, will I lose my vwii if I update the wii u? Like I said earlier I dont want to do any wii u exploiting right now.

Thanks :)
No, you won't! :)
Updates only affect the Wii U system files.
If there was a vWii update someone would have noticed! ;)
Edit:
It's pretty unlikely Nintendo is going to update the vWii ever, but there's never 100% safety! :P
 
First homebrew mod that needs to be done if possible is to shutdown all forced updates on wiiu permanently seriously i hate not having a choice also im afraid when i connect my wiiu to the internet to test homebrew it will update itself also :S.
 
@Marionumber1 @NWPlayer123
Do we always have to copy the newly generated playload files when we try to execute a new project?
If that's the case I think we found one of the issues! :D
Maybe the makefile shouldn't copy them into the "www-folder", but into the folder where the project's binaries are! ;)

I recompiled it today, put the new payloads into the folder and the HelloWorld code runs successfully again! ^^
 
I just noticed that my Wii U auto-updated but I had filters setup in my router. WTF, until yesterday I was still 5.3.2. :unsure:
Code:
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.wii.net
*.cdn.c.shop.nintendowifi.net
*.c.shop.nintendowifi.net
*.c.shop.nintendowifi.net
*.c.app.nintendowifi.net
*.e.akamai.net
nus.cdn.c.shop.nintendowifi.net
nus.c.shop.nintendowifi.net
cp3s-auth.c.shop.nintendowifi.net
ecs.c.shop.nintendowifi.net
cp3s.cdn.nintendowifi.net
cas.c.shop.nintendowifi.net
eou.cdn.nintendowifi.net
pls.c.shop.nintendowifi.net
npul.c.app.nintendowifi.net
ecs.c.shop.nintendowifi.net
a248.e.akamai.net
nppl.c.app.nintendowifi.net
conntest.nintendowifi.net
*.conntest.nintendowifi.net
 
@Adr990 Here you go; It's only the helloworld though, I didn't test the others...
@JaceCearK1 What do you mean with:
Everytime you compile a project, there are copied certain files into the "www folder", they're called "payloadxyz.html".
It looks like you always have to copy the newly generated ones into the folder where your code is to execute it properly. :)
 
I just noticed that my Wii U auto-updated but I had filters setup in my router. WTF, until yesterday I was still 5.3.2. :unsure:
You are using the quick boot/silent update feature?
Quickboot should be turned off, or the console will try to download/install updates while in standby.

I read on openDNS thread that another user's router only block http, not https.
Maybe your router didn't block the SSL check to see if eshop is reachable, and started downloading updates. (but updates are not on ssl, so I don't know)
or nintendo can update the URLs in realtime (dns, or urls retrieved from any successful connection).

maybe akamai is also providing updates.
 
You are using the quick boot/silent update feature?
Quickboot should be turned off, or the console will try to download/install updates while in standby.

I read on openDNS thread that another user's router only block http, not https.
Maybe your router didn't block the SSL check to see if eshop is reachable, and started downloading updates. (but updates are not on ssl, so I don't know)
Yes, I had quick start and automatic software downloads on. My router should support everything since it came out in August 2014 so it's pretty new:
http://avm.de/produkte/fritzbox/fritzbox-7490/

Oh shit, it seems like I didn't assign the blacklist to the Wii U. Man, that sucks now. I thought it would be applied to everything but I guess not.
 
Last edited by BullyWiiPlaza,
Oops, you were tagged because you was mentioned in the quote.
Obviously, I was talking about deformyer's HelloWorld.rar.
But you should use the ones that are compiled with your source anyways since they belong to each othe. ;)
Remember: They are in the "www" folder after compilation! ;)
It works for the HelloWorld example at least, but not in the osscreenexamples sadly! :(
 
But you should use the ones that are compiled with your source anyways since they belong to each othe. ;)
Remember: They are in the "www" folder after compilation! ;)
It works for the HelloWorld example at least, but not in the osscreenexamples sadly! :(
But if you compile the payloads with the same source code... should be fine, right? :P

Still nothing on 5.3.2E
Then it might be an issue that a remote host is used... Too bad.
 

Site & Scene News

Popular threads in this forum