Hacking Wii U Hacking & Homebrew Discussion

  • Thread starter Thread starter filfat
  • Start date Start date
  • Views Views 5,129,772
  • Replies Replies 21,104
  • Likes Likes 29
Or a game or something. I was connected in Settings a little bit ago snooping. If you exit the app, you'll have to rerun the exploit. Least I have.
Then the correct process would be:
  1. open the browser from the Wii U menu
  2. run the osdriver exploit
  3. open the browser again from the Wii U menu
  4. run TCPGecko
  5. open an app from the Wii U menu
  6. connect
Is that correct?
 
So do game-specific updates affect the Wii U firmware version in any way? I need to be sure to not mess anything up severely. :P
Not really, the only instance I can think of where a firmware version is /actually/ relevant to a game is Smash because of amiibo/NFC since nn_nfp wasn't added until 5.2.0.
this exploit load backups? it will?
No, go away and come back in like 8 months and then maybe.
 
Any ideas on how to update games using the kernel exploit ? :/
Everything you download from the eShop is signed, so you can't just bypass the eShop and install whatever you want manually, unless there is a signature patcher, AKA CFW...
But I think it will be possible to spoof the firmware or to use an emuNAND once an IOUS (AKA IOSU) exploit has been achieved.
For now, you can backup the NAND via hardware to switch between versions, and maybe even copy the signed update from the updated NAND to the downgraded one.
 
Everything you download from the eShop is signed, so you can't just bypass the eShop and install whatever you want manually, unless there is a signature patcher, AKA CFW...
But I think it will be possible to spoof the firmware or to use an emuNAND once an IOUS (AKA IOSU) exploit has been achieved.
For now, you can backup the NAND via hardware to switch between versions, and maybe even copy the signed update from the updated NAND to the downgraded one.
Right now you can't copy stuff from one NAND to another because there's no way to decrypt them right now
 
Then the correct process would be:
  1. open the browser from the Wii U menu
  2. run the osdriver exploit
  3. open the browser again from the Wii U menu
  4. run TCPGecko
  5. open an app from the Wii U menu
  6. connect
Is that correct?
1, 2, 3 are correct.

4. run <ip or website>/pyGecko (i use wj44's site using pyGecko4, manually type it in)

5. Run internet browser from home menu or click return to wii menu and load something.

6. Run TCP Gecko dotNet or pyGecko in IDLE

That's what I've been doing anyhow. Don't be confused with pyGecko in step 6, it's the python program you run in IDLE on your computer, written for the "pyGecko" you run in the web browser. but you do not need to use it if you load TCP Gecko dotNet on your pc instead.
 
  • Like
Reactions: nastys
you all said there was no need to stay on 5.3.2 anymore :cry:
No!
"We all" said that if you really have to update because of your own reasons you can (because it will work eventually!) but staying on the lowest firmware possible is always the best idea if it's about getting homebrew run! ;)
 
So correct me if I'm wrong but it's essentially the same exploit as this one? as this one also runs in userspace? (I think that's the correct term).
It's not the same exploit but yes the exploit runs with "userland" permissions to get the kernel permission! :)

--------------------- MERGED ---------------------------

Also @nuwohunk maybe it was unintended, but I'm pretty sure what @NWPlayer123 said was a hint! ;)
Think about it! Who uses a magic wand? :D
After you've got the answer to that question you only have to look through this thread a little bit and you've got the answer to yours! :rolleyes:
 
  • Like
Reactions: Vanth88
It's not the same exploit but yes the exploit runs with "userland" permissions to get the kernel permission! :)
Thanks for the reply. Well that's good news then. I'm still a tad bummed that my Wii U auto-updated (I've since disabled standby). I was really excited to hear about the memory editor and I really wanted to try that out. Oh well here's hoping something get's released.
 
People are always eager to update by the time the 5.5.0 exloit is even released there will be a 5.6.0 firmware and the same kind people that couldnt wait on 5.3.2 will be the same complaining for 5.6.0 support becuase they will keep updating, and it will be a vicious cycle until the wiiu abandoned by nintendo.
 
Thanks for the reply. Well that's good news then. I'm still a tad bummed that my Wii U auto-updated (I've since disabled standby). I was really excited to hear about the memory editor and I really wanted to try that out. Oh well here's hoping something get's released.
Disabling standby alone won't help much (as you've seen) you have to block specific URLs in your router so you can't connect to Nintendo's update servers! ;)
 

Site & Scene News

Popular threads in this forum