Hacking Wii U Hacking & Homebrew Discussion

  • Thread starter Thread starter filfat
  • Start date Start date
  • Views Views 5,122,201
  • Replies Replies 21,104
  • Likes Likes 29
I always heard hackers say nothing is unhackable only varying degrees of difficulty.

Indeed, but if it has no software vulnerabilities, then we have to attack the platform that it runs on. Unfortunately, the key is placed inside the CPU die, so its a hard bit to reach hardware-wise, since those things have billions of transistors.... Its not unhackable though - even if it shows up that no "simpler" side-channel attacks work, one could always hack it using a focused ion beam and tonnes of time. Nothing is unhackable, but things might be what is termed "computationally infeasible" to break.
 
  • Like
Reactions: TotalInsanity4
Nothing is "unhackable" but the term unhackable simply states that, if it is so, something is not worth the time compared to the value it'll bring.
This means that you could try and hack something for (just a big example now) over 20 years and you'll eventually find something or you'll then have a working reverse engineered architecture to access and change something. But what now? 20 years have passed, no one is probably going to use it anymore and/or most people just have newer consoles already and don't even bother anymore.
 
  • Like
Reactions: TotalInsanity4
nobody has asked the main question yet
who the hell gets 2months vacation a year that doesnt work for the goverment? lol

this will end up on the new xfiles
 
  • Like
Reactions: Don Jon
Or he took his bonus time instead of getting the over time as payment. The timing is odd, since most companies wouldn't allow that right after christmas, but it's not our place to judge. We should be happy he got the free time.
 
  • Like
Reactions: josh87402
Hey guys! I've had a hard time repacking my folders into SARC (turns out UWizard packs them incorrectly, they keep crashing when I open WiiUExplorer)-

I resorted to using a tool from @NWPlayer123, and that's SARCTools. However, I can't get SARCPack.py to load.

I have Python installed. I keep dropping the folder on it, but SARCPack.py just keeps crashing. I have yaz0enc (it's required) in the same folder, but I still fail to pack my folder in SARC.

Any advice would help me tremendously.
 
  • Like
Reactions: LawnMeower
Hey guys! I've had a hard time repacking my folders into SARC (turns out UWizard packs them incorrectly, they keep crashing when I open WiiUExplorer)-

I resorted to using a tool from @NWPlayer123, and that's SARCTools. However, I can't get SARCPack.py to load.

I have Python installed. I keep dropping the folder on it, but SARCPack.py just keeps crashing. I have yaz0enc (it's required) in the same folder, but I still fail to pack my folder in SARC.

Any advice would help me tremendously.
Depends on what you're using, the whole thing is a little iffy, back then I've only tested with python 2, 3'll probably break
 
  • Like
Reactions: lonemoonHD
Im going to bring up something Hykem said a bit ago. I have been receiving a lot of hate for saying its "probably" coming before February. This is what Hykem has said.



So, I’ve got good news and bad news.
The bad news is that I’m going to postpone the release again. I said this week would be a more realistic release date, but I never confirmed it would happen then. Still, it’s not a huge delay and it’s definitely not to wait for a new firmware update.
Like I stated before, I have the entire month of January free just to work on this and the exploit will be released and maintained before February (yes, I’m sure of that).
Now the good news, which should explain the additional delay. I need some time to pursue something I found in the MCP module. If I’m correct about this, we should be able to get a boot-time exploit. The reason for that is that the MCP module is responsible for launching “master” titles (like the PPC kernel, for example) and I found a bug that, if it turns out to be exploitable, should allow to hijack execution while MCP is still preparing to launch stuff. This means, early IOSU access and a direct boot into an exploitable environment. Not to mention that MCP is the IOSU user module with most privileges (next to BSP that is) and having access to it alone is more than enough to own the IOSU kernel at any given time.
I believe it’s important to look into this because if it works, no one will have to worry about possibly bricking consoles by installing custom titles (homebrew channel, for example) and then attempting to launch them before triggering the exploit again after a fresh boot.

With that said, if this turns out to be nothing, I’ll release the exploit right away.
 
Im going to bring up something Hykem said a bit ago. I have been receiving a lot of hate for saying its "probably" coming before February. This is what Hykem has said.



So, I’ve got good news and bad news.
The bad news is that I’m going to postpone the release again. I said this week would be a more realistic release date, but I never confirmed it would happen then. Still, it’s not a huge delay and it’s definitely not to wait for a new firmware update.
Like I stated before, I have the entire month of January free just to work on this and the exploit will be released and maintained before February (yes, I’m sure of that).
Now the good news, which should explain the additional delay. I need some time to pursue something I found in the MCP module. If I’m correct about this, we should be able to get a boot-time exploit. The reason for that is that the MCP module is responsible for launching “master” titles (like the PPC kernel, for example) and I found a bug that, if it turns out to be exploitable, should allow to hijack execution while MCP is still preparing to launch stuff. This means, early IOSU access and a direct boot into an exploitable environment. Not to mention that MCP is the IOSU user module with most privileges (next to BSP that is) and having access to it alone is more than enough to own the IOSU kernel at any given time.
I believe it’s important to look into this because if it works, no one will have to worry about possibly bricking consoles by installing custom titles (homebrew channel, for example) and then attempting to launch them before triggering the exploit again after a fresh boot.

With that said, if this turns out to be nothing, I’ll release the exploit right away.
Where did you find this?
 

Site & Scene News

Popular threads in this forum