Wasn't arguing that. OK. Go back to sleep. Wake up on the right side of the bed. Drink tea.did hykem give a date? no. he gave an expectation.
waiting won't kill anyone.
Wasn't arguing that. OK. Go back to sleep. Wake up on the right side of the bed. Drink tea.did hykem give a date? no. he gave an expectation.
waiting won't kill anyone.
nah. i've still got another 4 hours or soWasn't arguing that. OK. Go back to sleep. Wake up on the right side of the bed. Drink tea.
It's ok. we're all tired of waiting for ANYTHING and some of us handle it better than others. Let's just chill and play games.nah. i've still got another 4 hours or so
i feel like last year's gateway announcement/hype ruined the "waiting" mentality for some people. i just get a bit bothered when people who do legitimate work get assaulted for not following the strict schedule of everyone waiting to freely benefit from their efforts.
so, apologies if i came off as snappy.
I hate to break it to you, but be prepared for déjà vu!i feel like last year's gateway announcement/hype ruined the "waiting" mentality for some people. i just get a bit bothered when people who do legitimate work get assaulted for not following the strict schedule of everyone waiting to freely benefit from their efforts.
Gateway has a new announcement.i feel like last year's gateway announcement/hype ruined the "waiting" mentality for some people.
5.4 & 5.5 users?I really have to wonder why the IOSU hype is
All these doubts about Hykem. Wow. You guys do know that he posts lots of information of his findings about Wii U stuff in WiiUBrew, right?
Welp, back to Xenoblade Chronicles X.
Every time Hykem posts about this with more unnecessary delays I get more convenced its all a hoax. He is now saying the IOSU hack is done. But wont release it until a seperate better hack is developed, makes very little sense to me.
Hykem said:With that said, if this turns out to be nothing, I'll release the exploit right away.
Wait so does that mean Hykem is done with the IOSU exploit? Like porting it to 5.5.0 and 5.4.0?Actually, in the same quote from Hykem:
He's basically investigating what this new possible hack can do, and if it doesn't do anything he'll release the current IOSU. But if it leads to a permanent IOSU exploit, then the delay is appropriate.
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.
So basically my understanding, plain and simples, is he wants to investigate this new lead because he believes itll lead to less people being dumb and potentially bricking their console.
So the exploit he had ready could let someone dumb fuck up their console.
Exploit he's researching would limit the risk of said fuck up.
BOOM.
But people will somehow find a way to fuck up no matter what he does because people are stupid. I bet there will be a lot of bitching if 5.6 patches everything and they update before doing research on said update or something to that nature. I'm calling it right now.So basically my understanding, plain and simples, is he wants to investigate this new lead because he believes itll lead to less people being dumb and potentially bricking their console.
So the exploit he had ready could let someone dumb fuck up their console.
Exploit he's researching would limit the risk of said fuck up.
BOOM.
Nice!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.
Not too many days ago (I don't remember which thread) someone was talking about a possible permanent HBC. Everyone said no because we had boot1/2 access on the Wii and it wouldn't be a while before we got there with the Wii U.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.
One of them is me.Well, I can feel a lot of good things coming very soon! It's really awesome.