Hacking Wii U Hacking & Homebrew Discussion

  • Thread starter Thread starter filfat
  • Start date Start date
  • Views Views 5,124,633
  • Replies Replies 21,104
  • Likes Likes 29
I have tried hosting with python -m SimpleHTTPServer on my computer and raspberry pi (because the command line uses 2.7.x on both and I don't know how to change it) and I can't access the page on Chrome, Safari, or Midori no matter where I host the server and where I go to the webpage. I thin k it has something to do with my firewall because python says something like hosting server at 0.0.0.0 port 8000 like most sites say it should. Any tips?

Im 100% sure that it does work. In fact, before i posted my reply to you before, i hosted an html file using that method and was able to access it just fine. It is normal for it to say its hosted at 0.0.0.0 but you should still be accessing it using your local ip address. Another thing i would say you could try is including the port number, by default 8000, although in general that isn't necessary as it is assumed that port 8000 is being used, but it's probably a good practice. Also be sure that the exploit html file is in the same directory as the script/command you are running. Unless youve played with firewall settings, port 8000 is generally open

If you haven't already, add python to your PATH Environment. Then you can navigate to the directory which contains the exploit and run your command. I have a strange feeling that you aren't running the server in thedirectory containing the html file
 
Just have to create an account to ask this, should I update a 5.2/5.3 Wii U to 5.3.2? The stickies say no, but some posts in this thread are kinda maybe half implying otherwise and I reckon we all suffer from the lack of multiplayer so you guys understand that pain.

I guess my question is did 5.3.1 fix the kernel exploit? if it didn't it's safe to assume that we can update to 5.3.2 right?
 
Just have to create an account to ask this, should I update a 5.2/5.3 Wii U to 5.3.2? The stickies say no, but some posts in this thread are kinda maybe half implying otherwise and I reckon we all suffer from the lack of multiplayer so you guys understand that pain.

I guess my question is did 5.3.1 fix the kernel exploit? if it didn't it's safe to assume that we can update to 5.3.2 right?



5.2.0 is okay, and is pushing it, but anything past that will make it quite difficult for future hacks that'll be released. Super Smash Bros updates to 5.2.0, be sure to delete all internet settings if you go this route.
 
  • Like
Reactions: TeamScriptKiddies
5.2.0 is okay, and is pushing it, but anything past that will make it quite difficult for future hacks that'll be released. Super Smash Bros updates to 5.2.0, be sure to delete all internet settings if you go this route.

Does it mean that 5.3.0 is the FW version that fixed the kernel exploit and not 5.3.1? as in the sticky should be

Q: I want to update to the latest version but I don't want to miss out, am I safe in doing so?
A: NO. Do not update past 5.2.0 if you can help it.

instead of

Q: I want to update to the latest version but I don't want to miss out, am I safe in doing so?
A: NO. Do not update past 5.3.0 if you can help it.

?
 
Does it mean that 5.3.0 is the FW version that fixed the kernel exploit and not 5.3.1? as in the sticky should be

Q: I want to update to the latest version but I don't want to miss out, am I safe in doing so?
A: NO. Do not update past 5.2.0 if you can help it.

instead of

Q: I want to update to the latest version but I don't want to miss out, am I safe in doing so?
A: NO. Do not update past 5.3.0 if you can help it.

?


Yes, 5.3.0 and above fix the exploit, so if you have to update, stay on 5.2.0, preferably 5.1.0, but even then, it's pushing it.
 
Actually 5.3.0 doesn't fix the exploit, and 5.3.1/5.3.2 is unknown, however it's still advised to stay on as low a firmware as possible if you're gonna go that route(though if you wanna update for Smash or w/e then that should be fine, but anything past 5.2.0 is pushing it)
 
Actually 5.3.0 doesn't fix the exploit, and 5.3.1/5.3.2 is unknown, however it's still advised to stay on as low a firmware as possible if you're gonna go that route(though if you wanna update for Smash or w/e then that should be fine, but anything past 5.2.0 is pushing it)

OH, NOW I see why people are advocating staying on 5.2.0 instead of 5.3.0, it's because 5.2.0 comes with the Smash disc and it's impossible to update to 5.3.0 from a lower FW currently because no game has it on disc.

definitely not updating to 5.3.2 then. "unknown" at this point a month after the release probably means "yes".
 
  • Like
Reactions: NWPlayer123
Im 100% sure that it does work. In fact, before i posted my reply to you before, i hosted an html file using that method and was able to access it just fine. It is normal for it to say its hosted at 0.0.0.0 but you should still be accessing it using your local ip address. Another thing i would say you could try is including the port number, by default 8000, although in general that isn't necessary as it is assumed that port 8000 is being used, but it's probably a good practice. Also be sure that the exploit html file is in the same directory as the script/command you are running. Unless youve played with firewall settings, port 8000 is generally open

If you haven't already, add python to your PATH Environment. Then you can navigate to the directory which contains the exploit and run your command. I have a strange feeling that you aren't running the server in thedirectory containing the html file


I'm running it in the right directory and going to (my pi/computers ip):8000.
 
I'm running it in the right directory and going to (my pi/computers ip):8000.

So are you also including the name of your exploit .html file? ie: 192.168.0.101:8000/test500.html
If so then it sound like you are doing everything rightnow and its probably definitely a firewall setting or something. Although im not quite sure why you would have port 8000 closed unless you specifically changed that setting yourself, in which case i think you would be aware of it. If you still cant get it figured out after you check all possible settings etc. you could try opening
a new thread so this one doesn't get too cluttered.
 
So are you also including the name of your exploit .html file? ie: 192.168.0.101:8000/test500.html
If so then it sound like you are doing everything rightnow and its probably definitely a firewall setting or something. Although im not quite sure why you would have port 8000 closed unless you specifically changed that setting yourself, in which case i think you would be aware of it. If you still cant get it figured out after you check all possible settings etc. you could try opening
a new thread so this one doesn't get too cluttered.

On the contrary, I believe the firewall stops it unless you permit it. The first time running it, Windows Firewall popped up a dialog box asking to allow or deny the access.
 
On the contrary, I believe the firewall stops it unless you permit it. The first time running it, Windows Firewall popped up a dialog box asking to allow or deny the access.


Turns out I made a foolish and slightly embarrassing error in my responses, I was confusing port 8000 with port 80. In my original response to his question I provided a very simple script which utilized port 80, which I always use in situations like this because port 80 is the default port for the web and therefore gives me no fuss when accessing stuff I'm hosting locally and know is secure and safe. This is nice when accessing via a web browser as well because you need not include the port# in the address bar. (Which is why I also mistakenly said that it is assumed that port 8000 is being used by default) Once it was pointed out to me that it was much simpler to use: 'python -m BaseHTTPServer' at the command line instead of the small script I provided, I began to confuse the two ports because the command line option is defaulting to port 8000(the most common for third party web services) and my script was intentionally using 80. My apologies for the confusion :ohnoes: It is also worth mentioning that I just accessed port 8000 on my wifes laptop which is more or less a stock Dell with Norton Securtity Suite as the software firewall and I'm positive she has NEVER messed with any settings and I was able to access it just fine so maybe some block it by default and some have it open by default.
 
  • Like
Reactions: Fpsrussia117
Did some of you update their system with super smash bro ? I mean it's got 5.2.0 update on disk but I do not know if I should play it (and install the update) ... I' ve got the game for one month now, still not open ...
 

Site & Scene News

Popular threads in this forum