Hacking Wii U Hacking & Homebrew Discussion

  • Thread starter Thread starter filfat
  • Start date Start date
  • Views Views 5,074,432
  • Replies Replies 21,104
  • Likes Likes 29
well if anything it will at least bring 5.4 compatibility which is a good thing, shame everyone applied that spoof which will mean updating to 5.4 from 5.3.2 will be a challenge......but for the most part it doesn't really matter unless you really really wanted that MM manual
Why would you want to update from FW5.3.2 to 5.4.0 anyway?. Everything good going for this exploit is being run on 5.3.2 also with the spoofer you have the best of both worlds.
 
You're not missing much being on 5.4 vs 5.3.2 lmao they're literally the same for all intensive purposes, just need a different userspace exploit since they patched the old one, kexploit works fine too.
There we go, need I say anymore :P the only problem I can see is if this spoofer has problems in the near future with updating again? Nintendo could easily patch the next update to cause an issue with the spoofer and probably your wholeWiiU
 
Last edited by Reecey,
Is there a confirmed, un-released kernel exploit for 5.5? The temptation to upgrade to 5.5 is pretty heavy. The only reason I'm holding back anymore is if an IOSU exploit is being worked on for 5.3.2 that may have been patched in 5.5. If anything, an upgrade to 5.4 may be in line for me to play SMM. I'm not messing with that spoof, I've seen nothing but drawback and issues from it and I'd rather not waste my time.
 
Is there a confirmed, un-released kernel exploit for 5.5? The temptation to upgrade to 5.5 is pretty heavy. The only reason I'm holding back anymore is if an IOSU exploit is being worked on for 5.3.2 that may have been patched in 5.5. If anything, an upgrade to 5.4 may be in line for me to play SMM. I'm not messing with that spoof, I've seen nothing but drawback and issues from it and I'd rather not waste my time.
Yes, but it is very unlikely it'll be released before a full IOSU exploit, unless they somehow figure it out and patch it which is even more unlikely.
 
Why would you want to update from FW5.3.2 to 5.4.0 anyway?. Everything good going for this exploit is being run on 5.3.2 also with the spoofer you have the best of both worlds.
You're not missing much being on 5.4 vs 5.3.2 lmao they're literally the same for all intensive purposes, just need a different userspace exploit since they patched the old one, kexploit works fine too.
i did say
but for the most part it doesn't really matter unless you really really wanted that MM manual

.....some people really wanted that manual which doesnt work with 4.3.2 :P
 
It was just a matter of time before this exploit was published. The Stagefright issue was widely publicized and tons of PoCs were published as well:
http://googleprojectzero.blogspot.pt/2015/09/stagefrightened.html
https://blog.zimperium.com/stagefright-vulnerability-details-stagefright-detector-tool-released/

Anyway, yes, our 5.4.0/5.5.0 userland exploit is based on one of the Stagefright bugs, so, what yellows8 mentioned is accurate.
so can one say that there is no reason to keep the 5.4/5.5 userland exploit under wraps and release it (with Kexploit for 5.4 that is)? (yup, you guessed it, i was one of those that ended up with 5.4 thanks to dynamic IP, and opendns being on an outdated IP...)
 
i didnt say you were wrong, just pointing out that i was aware there was very little reason to be on 5.4 over 5.3.2, the only reason i can think of is people wanting to read the mario maker manual
I know, I wasn't serious I was just playing along with you.
 
  • Like
Reactions: gamesquest1
so can one say that there is no reason to keep the 5.4/5.5 userland exploit under wraps and release it (with Kexploit for 5.4 that is)? (yup, you guessed it, i was one of those that ended up with 5.4 thanks to dynamic IP, and opendns being on an outdated IP...)
I mean, if you want, but there's no guarantee it'll work, as I've said many times it has buffer alignment issues for what it jumps to when running ROP
 
so can one say that there is no reason to keep the 5.4/5.5 userland exploit under wraps and release it (with Kexploit for 5.4 that is)? (yup, you guessed it, i was one of those that ended up with 5.4 thanks to dynamic IP, and opendns being on an outdated IP...)
the kernel exploit for 5.4 was the same one as 5.3.2 it was just the entry point patched, so with this entrypoint 5.4 should be good with no additional releases required (assuming this can be worked out for wiiu usage)
 
Last edited by gamesquest1,
I mean, if you want, but there's no guarantee it'll work, as I've said many times it has buffer alignment issues for what it jumps to when running ROP
2 questions, improper buffer alignment result in freeze or unwanted crash of browser ? and is the said buffer alignment console specific and unguessable without crashing the system in the process ?
 
2 questions, improper buffer alignment result in freeze or unwanted crash of browser ? and is the said buffer alignment console specific and unguessable without crashing the system in the process ?
1) It'll just freeze, won't run any code you want. 2) Yes, it seems to be console specific, mine's worked 100% once I figured it out though, minus a few weird browser quirks.
 
  • Like
Reactions: Margen67
so can one say that there is no reason to keep the 5.4/5.5 userland exploit under wraps and release it (with Kexploit for 5.4 that is)? (yup, you guessed it, i was one of those that ended up with 5.4 thanks to dynamic IP, and opendns being on an outdated IP...)

I see no reason to not release this now. The nature of the exploit makes it really unstable so that will be a nuisance for 5.4.0/5.5.0 users.
Nonetheless, it may be possible to improve it by taking advantage of other Stagefright bugs, especially now that PoCs are available everywhere.
 
I mean, if you want, but there's no guarantee it'll work, as I've said many times it has buffer alignment issues for what it jumps to when running ROP

Doesn't this already happen in 5.3.2 from what I've read? People have to keep running the exploit multiple times before it'll finally install?
 
1) It'll just freeze, won't run any code you want. 2) Yes, it seems to be console specific, mine's worked 100% once I figured it out though, minus a few weird browser quirks.
was the test console sample big enough to determine that it was strictly console specific ? it might have a console specific location from a pool of 10-20 locations ? (just spewing my thoughts, but i guess that was already tested prior.)
 

Site & Scene News

Popular threads in this forum