This fits with what you said as it does not require modifying the boot sequence. That modified Priiloader would then loadsa patched system menu similarly to how USB Loader GX loads games so return to main menu redirects to USB Loader GX (patching the app that is returned to is also known to be working, otherwise USB Loader GX would've bricked my vWii 100x over), except in this case we'd have it return to Priiloader. Or, this could also be skipped and the user could just run the WAD manually on the vWii menu same way shown in that video. To the best of my knowledge, we have a theoretical workaround for this: Load vWii with a WAD forwarder on Wii U menu to special Priiloader channel instead of launching regularly (we know this can be done, otherwise WAD forwarders wouldn't exist). Without the signing private keys or a PPC bootrom exploit, no one is modifying the vWii SM or the boot sequence.
On the WiiU, both the PPC and ARM processors have secure bootroms that perform signature checks on the binaries they are running. A cute thing to look at, but not useful in the slightest. It does not have any of the interesting features of priiloader such as system menu hacks or autoboot, and it certainly does not load before the vWii system menu.
This WAD is just a channel that loads the priiloader. I'd think you guys may wanna check this out: Not sure if this is at all what the issue is though. Thank You for your answers, I suppose to have Fakemote work in other apps, its possible to just modify the app (snes9x for example) to support Fakemote IOS? It's a long way around the problem, but it is a way :Pīelieve that could be worked around in a similar way to how USB Loader GX allows return to wii menu to go back to USB Loader GX instead (works on vWii). That's pretty definitive then :P We're not going to be able to brute force it that's for sure. thats how asymmetric encryption works, private key can encrypt, public key decrypts. Im not going to say its impossible, because its technically possible, but it would require to brute force the private key that is used to encrypt the ancast images which will (currently) take a lifetime to get. Since we have the keys could we possibly build Priiloader as an ancast image so it would be accepted, or are there other problems with building Priiloader as an ancast image?
#PRIILOADER USB LOADER GX FORWARDER INSTALL#
to install it, it would need to be installed as a separate title that isn't system menu because installing in system menu would brick vWii (since priiloader is not an ancast image). we'd need the decrypt it first before booting it. the biggest one is that system menu's application is an ancast and encrypted. I think he meant every time you return to the Wii Menu i.e. I can live with the losing of patches if the System restarts since we would be booting the channel from WiiU, the only time you would need to restart vWii would be to boot back to WiiU (well no the only time but mostly) I also suspect he either hijacked a title or made a new one, but i wanted to be sure.
#PRIILOADER USB LOADER GX FORWARDER PATCH#
would require some work, since the title would need to have AHB enabled, patch the running IOS to have nand access and ES_DiVerify accessible, and change IOS (or force authentication) when booting system menu.Īs soon as priiloader closes (aka boot something else) it looses all power over the system, the patches would still be applied, but are lost once system menu is restarted. is there any source of that? in theory you could make it boot a different title (it being priiloader or w/e) and work from there i suppose.
So it doesn't seem like encryption is one of them. I don't know if there's some other issue with doing it but we do have the keys. Used to decrypt the Cafe OS kernel at load time. Used to decrypt vWii System Menu and new NANDloader binaries at load time. Actually not Just the vWii keys, both the vWii and Wii U keys. Well as for the keys The vWii keys were made public, quite a while ago actually.
Oh Originally I thought it could be possible to apply temporary patches after boot, I don't know why but I thought that it could somehow work. that screenshot was generated by replacing homebrew channel's binaries with priiloader, but in theory it can be made its own channel. is the public decryption key that the cpu uses to decrypt it public? cause without it nothing can touch system menu. : what advantage would you have from having a priiloader channel? it can't patch system menu since it can't load it (its encrypted).
0 kommentar(er)
