Hacking Hykem's 5.5 iosu Exploit

[LoganK93]

Fot those who will interest on this. Found on Smea's twitter:
https://github.com/yellows8/wiiu_browserhax_fright

Seems like yellows8 did not stop working.

This has been out all day. It's good news for those on 5.4.0, but us losers on 5.5.0 have to wait even longer until we can join the party.

 

[Megalegacy98]

This has been out all day. It's good news for those on 5.4.0, but us losers on 5.5.0 have to wait even longer until we can join the party.

Why do we have to wait? (Sorry if I sound stupid)

 

[MichMaster]

Fot those who will interest on this. Found on Smea's twitter:
https://github.com/yellows8/wiiu_browserhax_fright

Seems like yellows8 did not stop working.

There is a thread already...

 

[TheZander]

I'm just saying the lack of information is similar. They spent a good amount of posts hyping everyone up, kept making these vague release mentions, and then suddenly a delay followed by complete radio silence. Did it get patched? C&D'd? Paid off by Ninty? THe same way people immediately started speculating when Zelda got delayed.

From my perspective he really hasn't hyped anyone up intentionally. No sunglasses and boombox, he makes seldom post just trying to calm the waters. We've had a browser and kernel exploit for almost a year now in which people were chomping at the bit to get their hands on. Yet there has been minimum stuff developed. Can you tell me the first thing you are going to do once the IOSU exploit is released?

 

[Dark_AleX]

Didn't check here all day. Sorry guys

 

[Famicon]

So where is the exploit for 5.5.0 that will allow me to use TCPGecko with my Wii U?

 

[Megalegacy98]

So where is the exploit for 5.5.0 that will allow me to use TCPGecko with my Wii U?

Did you even read?

It's not here yet. Please be patient.

 

[Famicon]

Did you even read?

It's not here yet. Please be patient.

Ok ok

 

[jimbo13]

It's good news for those on 5.4.0, but us losers on 5.5.0 have to wait even longer until we can join the party.

Hykem said: ↑
The following statements are facts:
- I have successfully compromised the Wii U's IOSU;
- The exploit being used works from 2.0.0 up to 5.5.0, but it obviously needs to be ported for each firmware;
- The exploit doesn't need PPC kernel access, so the new kernel exploit won't have to be released. (Yes, the IOSU can manipulate all the PPC kernel memory.)

The safe assumption whatever is released for 5.4 will also be available for 5.5 at the same time or shortly there after so stop stirring up all the xmas adopters stuck with 5.5 systems.

 

[Megalegacy98]

Hykem said: ↑
The following statements are facts:
- I have successfully compromised the Wii U's IOSU;
- The exploit being used works from 2.0.0 up to 5.5.0, but it obviously needs to be ported for each firmware;
- The exploit doesn't need PPC kernel access, so the new kernel exploit won't have to be released. (Yes, the IOSU can manipulate all the PPC kernel memory.)

The safe assumption whatever is released for 5.4 will also be available for 5.5 at the same time or shortly there after so stop stirring up all the xmas adopters stuck with 5.5 systems.

He's talking about the browserhax for Wii U yellows8 released.

 

[LoganK93]

Hykem said: ↑
The following statements are facts:
- I have successfully compromised the Wii U's IOSU;
- The exploit being used works from 2.0.0 up to 5.5.0, but it obviously needs to be ported for each firmware;
- The exploit doesn't need PPC kernel access, so the new kernel exploit won't have to be released. (Yes, the IOSU can manipulate all the PPC kernel memory.)

The safe assumption whatever is released for 5.4 will also be available for 5.5 at the same time or shortly there after so stop stirring up all the xmas adopters stuck with 5.5 systems.

You'll notice of course that I was referring to something other than the IOSU exploit, and used the word WAIT, as in, we will eventually have one that works on that firmware but as of now we have to "wait even longer". I was referring to the fact that 5.5.0 is now the new 5.4.0 until something actually gets released that works on this firmware. And while I can wait patiently, many people cannot as evidenced by this thread, and it now stings a little more seeing those of us lucky enough to be on 5.4.0 getting to use their new toys.

Edit: Thanks Megalegacy98, you got it!

 

[Megalegacy98]

You'll notice of course that I was referring to something other than the IOSU exploit, and used the word WAIT, as in, we will eventually have one that works on that firmware but as of now we have to "wait even longer". I was referring to the fact that 5.5.0 is now the new 5.4.0 until something actually gets released that works on this firmware. And while I can wait patiently, many people cannot as evidenced by this thread, and it now stings a little more seeing those of us lucky enough to be on 5.4.0 getting to use their new toys.

Edit: Thanks Megalegacy98, you got it!

No prob, but

Why do we have to wait? (Sorry if I sound stupid)

 

[shaneod]

Because it takes time for developers to code. They can't just magic up some code instantly that works perfectly.
It takes weeks to months in order for one to be made, and you won't be thanked enough for it.

The already working kernel exploit isn't being posted for reasons explained countless times throughout this thread.

 

[LoganK93]

No prob, but

Well, simply because Hykem's isn't finished/he was abducted by aliens, and that the other Kernel exploit is being withheld so that it can function on as many firmwares as possible. The 5.4.0 users were lucky in that the K-exploit for 5.3.2 just happens to be the same one as 5.4.0, so when the browser exploit was patched in 5.5.1 and they released it, they automatically had kernel access too. 5.5.0 got the Web exploit the same as 5.4.0, BUT the kernel exploit for 5.5.0 is different. So we now have an entry point that essentially leads to nothing, until the Kernel exploit gets patched. In other words the devs just want to be sure it can work on as many "new" firmwares as possible so that we do not have things like in the 3ds scene where people were scrounging around for a hackable system on a firmware that became more and more obsolete.

Edit: The quote was weird but I don't post often and don't feel it's worth it to fix.

 

[Megalegacy98]

Because it takes time for developers to code. They can't just magic up some code instantly that works perfectly.
It takes weeks to months in order for one to be made, and you won't be thanked enough for it.

The already working kernel exploit isn't being posted for reasons explained countless times throughout this thread.

I'm talking about the browserhax exploit. All of the developers says it supports 5.5.0, and @LoganK93 says we have to wait.

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

Well, simply because Hykem's isn't finished/he was abducted by aliens, and that the other Kernel exploit is being withheld so that it can function on as many firmwares as possible. The 5.4.0 users were lucky in that the K-exploit for 5.3.2 just happens to be the same one as 5.4.0, so when the browser exploit was patched in 5.5.1 and they released it, they automatically had kernel access too. 5.5.0 got the Web exploit the same as 5.4.0, BUT the kernel exploit for 5.5.0 is different. So we now have an entry point that essentially leads to nothing, until the Kernel exploit gets patched. In other words the devs just want to be sure it can work on as many "new" firmwares as possible so that we do not have things like in the 3ds scene where people were scrounging around for a hackable system on a firmware that became more and more obsolete.

Edit: The quote was weird but I don't post often and don't feel it's worth it to fix.

Ohhhhhhhhhhhhhhhhh. I see now. So the browser exploit leads to nothing in 5.5.0... thanks for clarification.

 

[LoganK93]

I'm talking about the browserhax exploit. All of the developers says it supports 5.5.0, and @LoganK93 says we have to wait.

I attempted to explain above. TLDR; we have an entrypoint that essentially leads to nothing on 5.5.0, because while the browserhax exploit works for both, the only public kernel exploit only works on 5.3.2-5.4.0 right now.

Edit: Never mind he got it while I was typing.

 

[Megalegacy98]

I attempted to explain above. TLDR; we have an entrypoint that essentially leads to nothing on 5.5.0, because while the browserhax exploit works for both, the only public kernel exploit only works on 5.3.2-5.4.0 right now.

Reload your page.

 

[jimbo13]

You'll notice of course that I was referring to something other than the IOSU exploit.

You'll notice of course this thread is about Hykem's IOSU exploit so don't bold and snark at me while your off topic. The thread for Yellow8s hack is here.

 

[LoganK93]

You'll notice of course this thread is about Hykem's IOSU exploit so don't bold and snark at me while your off topic. The thread for Yellow8s hack is here.

I was just replying to the first person to go offtopic sweetheart. But thanks.

 

[kingraa777]

Dark Alex ?!? Heard that name before ........... Surely not