Hacking Wii U Hacking & Homebrew Discussion

  • Thread starter Thread starter filfat
  • Start date Start date
  • Views Views 5,080,018
  • Replies Replies 21,104
  • Likes Likes 29
So, are there still any reasons to stay under 5.3.2 ? I was staying at 4.1.0 but loadiine v3 is quite limited. Even if older firmware are assumed to be more stable, it doesnt make sense if we can only play a very limited amount of games.
 
So, are there still any reasons to stay under 5.3.2 ? I was staying at 4.1.0 but loadiine v3 is quite limited. Even if older firmware are assumed to be more stable, it doesnt make sense if we can only play a very limited amount of games.
Just get yourself at 5.3.2, it's more convenient for most of what is already available.
 
yes it has fake all over it but they dont want to hear that
Though this has already been mentioned multiple times, here's the reasons:

- Installing unsigned titles is possible with IOSU, but there's some problems to go along with this.

- If you run an installed, unsigned title after a reboot, without first launching the IOSU exploit, you can irreversibly brick your Wii U, unless you have a NAND backup from before the brick and a means of flashing it through hardware.

- With a boot-hax method of taking over IOSU, this risk is greatly minimized, as users can no longer start the system into a non-exploited state unintentionally.


AKA there's a very valid reason for not releasing it yet. Just chill and sit back. If it's fake, we'll know soon enough. I HIGHLY doubt it's fake though, considering the ridiculous amount of information Hykem posted on WiiU Brew about the IOSU. Finding all that information would necessitate either breaking a firm NDA, or having an IOSU exploit. I'm going to make an educated guess and say it's the latter.
 
- If you run an installed, unsigned title after a reboot, without first launching the IOSU exploit, you can irreversibly brick your Wii U, unless you have a NAND backup from before the brick and a means of flashing it through hardware.
I'm curious about this, what would make launching an unsigned title cause a brick? Why wouldn't it simply refuse to start? Like on the 3DS, unsigned installed titles can be seen on the home menu, but not started at all without disabling sig checks.
 
  • Like
Reactions: MattKimura
I'm curious about this, what would make launching an unsigned title cause a brick? Why wouldn't it simply refuse to start? Like on the 3DS, unsigned installed titles can be seen on the home menu, but not started at all without disabling sig checks.
He said "it can", in best case scenario when a title check is failed it will crash, or refuse to run the title.
But the devs mentioned there is a possibility of it causing a brick, that's just the worse case scenario, no one probably has tried yet.
 
i dont know why there are some who think this IOSU thingie is all faked etc. ( Sorry i am noobish myself ) BUT,

i believe this hykem guy, he appears every now and then and tells us his progress and stuff,

it is getting more and more exciting, and February is not far.
 
  • Like
Reactions: TotalInsanity4
Oh well, i don't care much about IOSU, when it really comes > OH IT'S MR. IOSU
If not, we can play almost everything, who cares for online gaming when Nintendo
can simply ban you?

hykem can take all his sweet time he needs, until then, i'll play and ignore the hypetrain.
 
  • Like
Reactions: I pwned U!
Most people are new here they dont know the work hyken has done in the past so they are noone believers, hyen has proven himself before and he has added alot of stuff to wiiubrew about iosu that shows he has alot of acess to it to get all that info he posts regulary, people chill out and wait, like that old saying, Good Things happens to those who wait.
 
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.

you should call the exploit Zelda's Wii U 5.5.0 iosu haha lmao.
...
...
i need my zelda for wii u rn :sad::cry:
 
Do you think that with the presence of loadiine and hykems work soon to be released , that we will ever see what failoverflow ever acheived ? meaning do you think they will ever let out what they had ? and would it be a better solution than what hykem is about to release? or would it assist and enhance in anyway ?
 
Do you think that with the presence of loadiine and hykems work soon to be released , that we will ever see what failoverflow ever acheived ? meaning do you think they will ever let out what they had ? and would it be a better solution than what hykem is about to release? or would it assist and enhance in anyway ?
ISOU Exploit+permanent, il doubt theres much more to achieve from an enduser point of view.
 
  • Like
Reactions: TotalInsanity4
Look, in a worse case scenario this possible exploit hykem has found doesnt lead to anything and we have the release sometime in January as soon as its confirmed its not possible.... Or best case scenario hykem new found exploit for earlier control of the system in the boot sequence turns out to be good and we get a more permanent iosu solution in February sometime.
 
Do you think that with the presence of loadiine and hykems work soon to be released , that we will ever see what failoverflow ever acheived ? meaning do you think they will ever let out what they had ? and would it be a better solution than what hykem is about to release? or would it assist and enhance in anyway ?

fail0verflow's stuff was for a very old software version (2.0.0 or 2.1.0), so it's unlikely that it would be very useful. Once we complete the IOSU exploit, I suppose there would be no barrier to them releasing what they had, but no one gains much from it either.
 
ah , didnt think on software revisions , good point , but as they didnt release their work i guess it wouldnt have been patched. Did they actually acheive anything more than whats due ?
 
ah , didnt think on software revisions , good point , but as they didnt release their work i guess it wouldnt have been patched. Did they actually acheive anything more than whats due ?
Just because they didn't release it doesn't mean it wasn't found and patched by Nintendo in a FW update since then.
 

Site & Scene News

Popular threads in this forum