Hacking Wii u updated

[depaul]

Congratulation to the team, hopefully we won't bother them too much

The last IOSU was a failure because of false hopes we had. Remember how we were told all that remains is some "obfuscation so that Nintendo will have hard time patching the exploit". But no hard feelings toward anyone hopefully hykem is alright with his real life.

 

[AboodXD]

I feel sad for Hykem, he's the one who found the bug, so no iosuhax without Hykem either way...
RIP Hykem...

 

[Reecey]

You should set up both DNS address with both hacks, just to be safe & sure and make sure you set these up for every connection, wherever you are! Set up the first box with Tubehax:- 107.211.140.065 and set up the second box with chncdcksn hax: 104.236.072.203 You get the best of both worlds, it will never fail if Tubehax fails and you will always have a connection if Tubehax fails because I find Tubehax is very unreliable at the moment. I think you will find the OP was at fault here I don't think there is any need to panic and say Tubehax has faulted.

 

[EmulateLife]

People need to change their settings in system settings to where it doesn't update when the Wii U is off in addition to tubehax/dns, otherwise Nintendo might come out with an update that completely blocks all piracy and you might find yourself on it one day. If you don't think it can happen the PS3 has not been able to hack a firmware above 3.55 and it's been years.

The other alternative is taking your Wii U completely offline and doing the offline exploit through connectify which makes your computer a local hotspot and choosing no internet sharing so it's local only. This is what I do.

 

[FaTaL_ErRoR]

Oh wow guys.
What you are calling "IOSU" has had barely any changes between 5.3.2 and 5.5.1.
The kernel had changes, the webkit had changes, and the one actual change in what you are calling IOSU was the removal of tvii. (and that was also combo with kernel level changes and that was done by going from 5.3.2 to 5.4)
The webkit exploit is probably the only reason for the change to 5.5.1.
And ABOOD is by far not a person to take advice from.
5.5.0 and 5.5.1 only changed the version of webkit. If you see how version changes work you will understand that core changes move the first number version. secondary IE kernel changes move the second number and app updates from factory installed apps change the last number.
It all has to do with software license. The primary software has remained unchanged since version 5.
Now information from someone like Wulfystyles can be taken to the bank.
So if that who said update to 5.5.1 then it should be good. As that is the webkit and kernel exploit they are using to exploit the embedded os.
I mean seriously though ABOOD. There was a change in webkit from 5.5.0 to 5.5.1 that was it. And the revision it updated to for some odd reason didn't fix the accidentally released current websploit. (In all honesty every other webkit of that version that update patched it. Which was why they released it)
That is probably why Nintendo has given up fighting with these guys. For some reason even though the code should have been handled by this patch it didn't fix it. Which means there is something else wrong and they have yet to find a solve for it. For them hopefully the lesson learned would be to not use any open source for any part of future consoles. Open source webkit has a huge issue. And that is it's own public reporting. Users registered as developers over there are given access to past and present issues. And in the hands of those that want to open can be excellent tools.
You can't sell hardware and expect people to not hack it. It's not like a web loadable game. Users have direct access to the heart of the product.
Then you lock it up to attempt to stop hackers, yet you install one of the most vulnerable web engines on the market?... Just makes no sense.

 

[AboodXD]

Oh wow guys.
What you are calling "IOSU" has had barely any changes between 5.3.2 and 5.5.1.
The kernel had changes, the webkit had changes, and the one actual change in what you are calling IOSU was the removal of tvii. (and that was also combo with kernel level changes and that was done by going from 5.3.2 to 5.4)
The webkit exploit is probably the only reason for the change to 5.5.1.
And ABOOD is by far not a person to take advice from.
5.5.0 and 5.5.1 only changed the version of webkit. If you see how version changes work you will understand that core changes move the first number version. secondary IE kernel changes move the second number and app updates from factory installed apps change the last number.
It all has to do with software license. The primary software has remained unchanged since version 5.
Now information from someone like Wulfystyles can be taken to the bank.
So if that who said update to 5.5.1 then it should be good. As that is the webkit and kernel exploit they are using to exploit the embedded os.
I mean seriously though ABOOD. There was a change in webkit from 5.5.0 to 5.5.1 that was it. And the revision it updated to for some odd reason didn't fix the accidentally released current websploit. (In all honesty every other webkit of that version that update patched it. Which was why they released it)
That is probably why Nintendo has given up fighting with these guys. For some reason even though the code should have been handled by this patch it didn't fix it. Which means there is something else wrong and they have yet to find a solve for it. For them hopefully the lesson learned would be to not use any open source for any part of future consoles. Open source webkit has a huge issue. And that is it's own public reporting. Users registered as developers over there are given access to past and present issues. And in the hands of those that want to open can be excellent tools.
You can't sell hardware and expect people to not hack it. It's not like a web loadable game. Users have direct access to the heart of the product.
Then you lock it up to attempt to stop hackers, yet you install one of the most vulnerable web engines on the market?... Just makes no sense.

*coughs*

However, in firmware 5.5.1 a new check was added to the system call handler that verifies if the calling thread's stack pointer is valid. In order to sucessfully make use of this exploit chain in firmware 5.5.1 one must be sure to build a small enough ROP chain that allows calling a system call before the thread's stack pointer goes past the stack top address.

See?

And the revision it updated to for some odd reason didn't fix the accidentally released current websploit.

It wasn't meant to patch the current one, it was meant to patch Marionumber1's webkit exploit, and yes it did patch it. (It was released, but nobody used it due to its success rate, I think I still have it somewhere)
yellows8 had his own webkit exploit (It's the one that we're currently using), he thought it was patched in 5.5.1, so he released it, then smealum posted a tweet about that it wasn't patched.

Do your research dude. :/

 

[Wekker]

I probalby will buy a wii u in the future, anyone know how to disable every possible way of internet? Kill the wifi chip?

 

[EmulateLife]

I probalby will buy a wii u in the future, anyone know how to disable every possible way of internet? Kill the wifi chip?

No need just download this and follow the directions https://drive.google.com/file/d/0BzJAGHWBJ_5sNmphWWVPSTlNMGM/view (credit to FlimFlam69 and others before him that made it)

It's a completely offline method using your computer as a local only hotspot, works really well too.

 

[AboodXD]

-snip-

 

[Wekker]

No need just download this and follow the directions https://drive.google.com/file/d/0BzJAGHWBJ_5sNmphWWVPSTlNMGM/view (credit to FlimFlam69 and others before him that made it)

It's a completely offline method using your computer as a local only hotspot, works really well too.

but is still has autoupdate option, so when i go to friends place with it, it will udpate when it get turned on...

 

[AboodXD]

-snip-

 

[EmulateLife]

but is still has autoupdate option, so when i go to friends place with it, it will udpate when it get turned on...

The auto update option can be turned off by you anytime if you go to your friends and don't turn it off and connect to the internet and it updates that's completely your own fault. I'm not even sure why I need to explain this to you.

 

[Wekker]

The auto update option can be turned off by you anytime if you go to your friends and don't turn it off and connect to the internet and it updates that's completely your own fault.

So if i never turn it on, or have it turned off. Wii u will never update automatically right? The reason i ask this is because i got some info somewhere on gbatemp about people has there wii auto updated

 

[EmulateLife]

Just go into system settings then power setttings then standby functions and make sure it's disabled. People that don't know this or do this get their wii u auto updated.

 

[AboodXD]

I just want to make things clear, as @NoSoul81 said, if you have the standby feature turned on, the Wii U will update if your console is turned off.
But what if your console is on? It will never auto update, because before it installs the update, it asks you to click OK. (It downloads the update automatically, but it won't install unless you click OK)
If the message with the "OK" button appears and you don't want your Wii U to update (sadly, there's no "Cancel" button... It would have been nice. ), you should never click OK but instead, unplug your AC adapter every time that message appears.
You can also remove the downloaded (not installed) update by using a homebrew app that I've forgotten its name. [/B][/B]

 

[EmulateLife]

Exactly it's not like it's going to update in 2 seconds without you knowing it. Wekker if you're that worried about it updating maybe you shouldn't take it to your friends and put it online in the first place, but even if you did unless you stay the night and leave it to connected to the internet and don't turn off standby functions it won't update anyway without you knowing it or saying ok.

 

[FaTaL_ErRoR]

*coughs*

See?

It wasn't meant to patch the current one, it was meant to patch Marionumber1's webkit exploit, and yes it did patch it. (It was released, but nobody used it due to its success rate, I think I still have it somewhere)
yellows8 had his own webkit exploit (It's the one that we're currently using), he thought it was patched in 5.5.1, so he released it, then smealum posted a tweet about that it wasn't patched.

Do your research dude. :/

Research? I dont need to to know that is for webkit.
And the next version of webkit should have effectively patched the other websploit as well.
Just looking at webkit version tells you that. Pretty sure thats why it was released. Lack of testing after patch rolled is why it was released. But going off of webkit version updates his should have been patched along with MN1's.
Meaning the exploit is still functioning because its not a webkit problem as it should have handled it. But something nintendos os is doing with webkit that isnt handling it.
Your understanding of webkit is rather low if you think something is being specifically written to patch mn1's exploit. The holes mn1 has used are known holes in old versions of webkit. He just makes them work for wii u. (And did a fantastic job)
They get patched by moving to a later version of webkit that has patched the old holes. Honestly I think someone at nintendo enjoys the cat and mouse game. Because to this day they arent on the latest webkit version. Which probably wouldnt help them at this point since the version they upgraded to should have patched yellow8's exploit as well.
If there was anything else added with the 5.5 update it was done when it moved to 5.5.0 as the only difference os wise from 5.5.0 and 5.5.1 was the version of webkit.
Check the version of webkit currently then check the previous version.
Then log in to webkit site and look to see what security patches were done. Neither websploit should work in the current webkit version the wii u is using.

 

[TotalInsanity4]

Research? I dont need to to know that is for webkit.
And the next version of webkit should have effectively patched the other websploit as well.
Just looking at webkit version tells you that. Pretty sure thats why it was released. Lack of testing after patch rolled is why it was released. But going off of webkit version updates his should have been patched along with MN1's.
Meaning the exploit is still functioning because its not a webkit problem as it should have handled it. But something nintendos os is doing with webkit that isnt handling it.
Your understanding of webkit is rather low if you think something is being specifically written to patch mn1's exploit. The holes mn1 has used are known holes in old versions of webkit. He just makes them work for wii u. (And did a fantastic job)
They get patched by moving to a later version of webkit that has patched the old holes. Honestly I think someone at nintendo enjoys the cat and mouse game. Because to this day they arent on the latest webkit version. Which probably wouldnt help them at this point since the version they upgraded to should have patched yellow8's exploit as well.
If there was anything else added with the 5.5 update it was done when it moved to 5.5.0 as the only difference os wise from 5.5.0 and 5.5.1 was the version of webkit.
Check the version of webkit currently then check the previous version.
Then log in to webkit site and look to see what security patches were done. Neither websploit should work in the current webkit version the wii u is using.

Hey how's GraceU coming

 

[stl25]

ISOUHAX is like the elusive Bigfoot, Nessie, chupacabra, aliens or unicorn. Take your pick. Lots of alleged sightings but no concrete proof of existence. Also these mythical beasts (ISOUHAX included) make for good storytelling though. I'm thinking alien confirmation may break before ISOUHAX though. Just chiming in because I saw some ISOUHAX fodder in an earlier post in this thread.

 

[AboodXD]

Research? I dont need to to know that is for webkit.
And the next version of webkit should have effectively patched the other websploit as well.
Just looking at webkit version tells you that. Pretty sure thats why it was released. Lack of testing after patch rolled is why it was released. But going off of webkit version updates his should have been patched along with MN1's.
Meaning the exploit is still functioning because its not a webkit problem as it should have handled it. But something nintendos os is doing with webkit that isnt handling it.
Your understanding of webkit is rather low if you think something is being specifically written to patch mn1's exploit. The holes mn1 has used are known holes in old versions of webkit. He just makes them work for wii u. (And did a fantastic job)
They get patched by moving to a later version of webkit that has patched the old holes. Honestly I think someone at nintendo enjoys the cat and mouse game. Because to this day they arent on the latest webkit version. Which probably wouldnt help them at this point since the version they upgraded to should have patched yellow8's exploit as well.
If there was anything else added with the 5.5 update it was done when it moved to 5.5.0 as the only difference os wise from 5.5.0 and 5.5.1 was the version of webkit.
Check the version of webkit currently then check the previous version.
Then log in to webkit site and look to see what security patches were done. Neither websploit should work in the current webkit version the wii u is using.

1. Don't try to act like a nerd, if you think I'm stupid and don't know how stuff goes.
2. What you said isn't 100% about the latest firmware, as in my post that you quoted, I showed a proof that there were other changes made in 5.5.1, I even posted an exact quote from WiiUBrew.

I won't be replying to your messages anymore, because I don't care a bit about what you say, what you think, and what you claim.

Have a nice day.