Hacking Wii U Hacking & Homebrew Discussion

  • Thread starter Thread starter filfat
  • Start date Start date
  • Views Views 5,108,664
  • Replies Replies 21,104
  • Likes Likes 29
Im not updating this wii u anytime soon, i want the OS as vulnerable as possible :). Im going to be playing around with thw current webkit exploit and once the kernel is released ill be utilizing that :). Newer games can wait for now <3
 
Is the IOS exploit related to the guys developing the ODE device? Or is it being worked on by people independent of the ODE
 
Is the IOS exploit related to the guys developing the ODE device? Or is it being worked on by people independent of the ODE

The one Hykem has indirectly mentioned is independent AFAIK. Anybody related to the ODE has been silent for a while, not sure what's up with that.
 
The one Hykem has indirectly mentioned is independent AFAIK. Anybody related to the ODE has been silent for a while, not sure what's up with that.



They are waiting for you guys to slip your stuff into their hands to sell it to the ODE guys. That is why the ODE is still not here. They sold what they had, then leaked it to appear not the ones who sold it and since what they sold didn't give much for the ODE to work. It backfired. So keep your stuff tight and in a small group.
 
I tried to build the RPC system, because I wanted to make sure I installed devkitPPC properly, and encountered this:
Code:
./build.sh: line 39: powerpc-eabi-gcc: command not found
 
./build.sh: line 40: powerpc-eabi-ld: command not found
The test(version number) file still built. Did I do something wrong?
 
Never mind. Re-added it to my path within the build folder. Now I get this:
Code:
powerpc-eabi-ld: warning: cannot find entry symbol _start; defaulting to 01800000
Ugh.
 
Apparently my mac is incapable of remembering something I add to the path after I close the shell. I added a line of code that adds the folder to my path at the beginning of build.sh. It might be a good idea to add that line of code to your script in the main repo. It could be as simple as having a third argument in the script point to the bin directory n devkitPPC.
 
This entire thread is confusing me. People are saying they are glad they didn't update their 4.x Wii U but the exploit should work on 5.x? NWPlayer123 said it was safe to update fully (i'm on 5.2.0 from smash)?
 

Site & Scene News

Popular threads in this forum