D
Deleted User
Guest
OP
Hey guys...
So last night i coulnd´t sleep well. Because i just thought about the question what last protection the WiiU still might have, that we have not yet overcome.
And then i looked at that newly released tool "Dumpling" and then it stroke me like a lightning! It`s an .ELF-file!
So why is this important? Simple. 99% of WiiU-homebrew (currently) is run as a WiiU-RPX file. And RPX is a WiiU-OS-fileformat.
And so i thought and thought and finally found out that RPX-files are encrypted by WiiU`s OS (by standard) as well!
But: ELF-files are not encrypted, since they are simple created homebrew-files without official WiiU-SDK. .ELF-files are files directly produced from a linker on your PC/laptop or notebook.
Thanks to "Mocha CFWs" recently released USB-patch which allows to run data directly from USB with full speed, it came to me how we crack that last protection.
Simple. We start Mocha & then run our .ELF-files directly from there. Boom! No WiiU-OS. No encryptions. Full USB-speed!
So again here´s what we should consider doing next:
1) Create a linux-loader WITHOUT making use of RPX-files or trying to circumvent the WiiU`S OS! We simply have to create an .ELF-linux loader IN a CFW to boot it from there (best solution is Mocha since it has full USB support)! We can e.g. use Wii-creator-tools.
2) Each homebrew we create has to be in .ELF format (or .dol but i dunno if we can run that yet, we`d have to program a .dol-loader first lol)
3) For example: If we want RETROARCH @ full speed we have to compile it as an .ELF-file guys! No RPX! You can´t use the "WiiU Homebrew development-kit" since that implements all encryptions again. So taht is the FIRST thing you can do to try this instruction-guide here. Re-compile "Retroarch" and use the .elf-format. Do NOT use WiiU-converting-tools! Then your software- assuming you run it from Mocha CFW´s unlocked USB will run at MAX possible speed!
4) A lot of software has to be converted from .dol to run as an .ELF-file. But without programming a .dol-launcher we might not be able to use .DOL-format (exception Nintendon`t but that has to be newly compiled as an .elf file as well since currently it´s RPX as well!)
5) In the future we might want to use the WiiU´S GX2-shaders. And this will one day be possible. BUT: We have to have suitable drivers for that. Which we currently don`t have. Which is why we have to use the official tools to compile our software. And THIS is where encryption of WiiU-created files start!
So now- i want to trigger a SERIOUS warning for everybody following my instructions here. IT´s DANGEROUS. You do this on your OWN risk. You can compile .elf-files & execute them on this machine on your OWN RISK!
Nobody knows what happens to a WiiU-console if you do run a homebrew-file without encryption for long periods of time! It´s your own risk. The WiiU might overheat. The processor can fail and/or the VRM can fail especially if your environment is HOT. So i stronly advise you to make sure, your environment is NOT hot and that you consider cooling the box well! Use air-condition if necesary!
Personally i think Nintendo has considered this and the WiiU won´t fail in this process. But who knows? There is allways a tiny risk. If the WiiU gets damaged it won´t be because of a brick. Since you just run Homebrew .elf from Mocha CFW`S USB-drive. But overheating is no simple issue and sometimes leads to severe hardware-damage.
So now that you know how it´s done...please be careful. If you have questions about it, then i`ll be here to hear you.
One last thing. I made guesses as to how much cpu-bandwidth the WiiU`s processor is using to implement the software-AES-encryption of WiiU´s OS.
And my guess is: 18 Gbytes/second (which is about roughly 90% of free cpu-ressources) are being used to implement that heavy encryption. So theoretically things like "Retroarch" should run like ~10x faster after it´s being recompiled into an .elf-file and not using GX2! Since instead of 2 Gbyte/Second you will now gain a boost of 900% more bandwidth, that should equal a 9x improvement.
The WiiU`s espresso-chip can do a bandwidth of about 20 Gbytes/second. Which equals roughly 70 Tbytes/hour of bandwidth. This is about ~10x faster than what the Wii´s old cpu did. But: when you enable heavy encryption, a lot of that bandwidth is lost, and that´s why i said, 18 Gbytes/second is lost, and only 2 Gbyte/second can be used for stuff you wan to execute.
Please be aware that this bandwidth is used for everything though & is only possible in theory and will in real life applications depend on what you use and what you want to calculcate/do. That means (theoretically) if you use one USB-port, you do lose about ~3% of cpu-ressources (roughly 600 Mbyte/Second of WiiU´s cpu-bandwidth) for communication. In this case, only 97% of cpu-bandwidth is free to do calculations.
So nothing is for free. The more USB-devices you might use or hog, the more bandwidth is lost! E.g. you use 2 devices, that equals 6% bandwidth-loss (that´s the case when you e.g. copy from one USB to another). And then there´s allways the possibility to want to use mouse/keyboard via USB simultanously as well, which will consume additional 1% for each too.
So now that i gave you a solution for PERFECT homebrew on WiiU...GOOD luck everybody! may the revolution begin. And you can show your results here if you want. You can make a video on Youtube to show if your compiling worked!
Happy compiling!
Btw: Did you guys here about "3DS-sourcecode leaked" allready? Oh boy. Nintendo´s on a run with their "security" it seems.
So last night i coulnd´t sleep well. Because i just thought about the question what last protection the WiiU still might have, that we have not yet overcome.
And then i looked at that newly released tool "Dumpling" and then it stroke me like a lightning! It`s an .ELF-file!
So why is this important? Simple. 99% of WiiU-homebrew (currently) is run as a WiiU-RPX file. And RPX is a WiiU-OS-fileformat.
And so i thought and thought and finally found out that RPX-files are encrypted by WiiU`s OS (by standard) as well!
But: ELF-files are not encrypted, since they are simple created homebrew-files without official WiiU-SDK. .ELF-files are files directly produced from a linker on your PC/laptop or notebook.
Thanks to "Mocha CFWs" recently released USB-patch which allows to run data directly from USB with full speed, it came to me how we crack that last protection.
Simple. We start Mocha & then run our .ELF-files directly from there. Boom! No WiiU-OS. No encryptions. Full USB-speed!
So again here´s what we should consider doing next:
1) Create a linux-loader WITHOUT making use of RPX-files or trying to circumvent the WiiU`S OS! We simply have to create an .ELF-linux loader IN a CFW to boot it from there (best solution is Mocha since it has full USB support)! We can e.g. use Wii-creator-tools.
2) Each homebrew we create has to be in .ELF format (or .dol but i dunno if we can run that yet, we`d have to program a .dol-loader first lol)
3) For example: If we want RETROARCH @ full speed we have to compile it as an .ELF-file guys! No RPX! You can´t use the "WiiU Homebrew development-kit" since that implements all encryptions again. So taht is the FIRST thing you can do to try this instruction-guide here. Re-compile "Retroarch" and use the .elf-format. Do NOT use WiiU-converting-tools! Then your software- assuming you run it from Mocha CFW´s unlocked USB will run at MAX possible speed!
4) A lot of software has to be converted from .dol to run as an .ELF-file. But without programming a .dol-launcher we might not be able to use .DOL-format (exception Nintendon`t but that has to be newly compiled as an .elf file as well since currently it´s RPX as well!)
5) In the future we might want to use the WiiU´S GX2-shaders. And this will one day be possible. BUT: We have to have suitable drivers for that. Which we currently don`t have. Which is why we have to use the official tools to compile our software. And THIS is where encryption of WiiU-created files start!
So now- i want to trigger a SERIOUS warning for everybody following my instructions here. IT´s DANGEROUS. You do this on your OWN risk. You can compile .elf-files & execute them on this machine on your OWN RISK!
Nobody knows what happens to a WiiU-console if you do run a homebrew-file without encryption for long periods of time! It´s your own risk. The WiiU might overheat. The processor can fail and/or the VRM can fail especially if your environment is HOT. So i stronly advise you to make sure, your environment is NOT hot and that you consider cooling the box well! Use air-condition if necesary!
Personally i think Nintendo has considered this and the WiiU won´t fail in this process. But who knows? There is allways a tiny risk. If the WiiU gets damaged it won´t be because of a brick. Since you just run Homebrew .elf from Mocha CFW`S USB-drive. But overheating is no simple issue and sometimes leads to severe hardware-damage.
So now that you know how it´s done...please be careful. If you have questions about it, then i`ll be here to hear you.
One last thing. I made guesses as to how much cpu-bandwidth the WiiU`s processor is using to implement the software-AES-encryption of WiiU´s OS.
And my guess is: 18 Gbytes/second (which is about roughly 90% of free cpu-ressources) are being used to implement that heavy encryption. So theoretically things like "Retroarch" should run like ~10x faster after it´s being recompiled into an .elf-file and not using GX2! Since instead of 2 Gbyte/Second you will now gain a boost of 900% more bandwidth, that should equal a 9x improvement.
The WiiU`s espresso-chip can do a bandwidth of about 20 Gbytes/second. Which equals roughly 70 Tbytes/hour of bandwidth. This is about ~10x faster than what the Wii´s old cpu did. But: when you enable heavy encryption, a lot of that bandwidth is lost, and that´s why i said, 18 Gbytes/second is lost, and only 2 Gbyte/second can be used for stuff you wan to execute.
Please be aware that this bandwidth is used for everything though & is only possible in theory and will in real life applications depend on what you use and what you want to calculcate/do. That means (theoretically) if you use one USB-port, you do lose about ~3% of cpu-ressources (roughly 600 Mbyte/Second of WiiU´s cpu-bandwidth) for communication. In this case, only 97% of cpu-bandwidth is free to do calculations.
So nothing is for free. The more USB-devices you might use or hog, the more bandwidth is lost! E.g. you use 2 devices, that equals 6% bandwidth-loss (that´s the case when you e.g. copy from one USB to another). And then there´s allways the possibility to want to use mouse/keyboard via USB simultanously as well, which will consume additional 1% for each too.
So now that i gave you a solution for PERFECT homebrew on WiiU...GOOD luck everybody! may the revolution begin. And you can show your results here if you want. You can make a video on Youtube to show if your compiling worked!
Happy compiling!
Btw: Did you guys here about "3DS-sourcecode leaked" allready? Oh boy. Nintendo´s on a run with their "security" it seems.