Table of Contents
What Home Menu title-version should I use for menuhax installation?
The Home Menu title-version used for menuhax installation here is requested from the ninupdates site. This should not be used unless you’re going to install a different Home Menu title-version afterwards. Send the Home Menu title-version for the initial *hax payload network request. This is only used when the system-version was not overridden.
How do I send a *Hax payload network request from Home Menu?
Send the Home Menu title-version for the initial *hax payload network request. This is only used when the system-version was not overridden. This fixes issues with the installed Home Menu version not matching the system-version.
How to force menuhax *Hax payload to boot from SD?
Moved menuhax files stored in the SD root into “/menuhax/”, the old data is deleted/moved in some cases. Implemented cfg exec_type, see source. This can be used to force- {enable/disable} menuhax *hax payload booting at next Home Menu boot (this overrides PADCHECK).
What’s new in the menuhax app?
Various app UI changes. Moved HTTPC init/exit code in the app, into the actual menuhax install function. Changed the app name from “themehax_installer” to “menuhax_manager”, and switched “themehax” to “menuhax” in most places. Added proper ropbin handling: *hax 2.5 payloads are now supported.
What’s new in menuhax_manager?
Theme-data-related functionality (including additional menuhax extdata file deletion) is now only enabled if the cfg allows it, due to a theme-data exploit being installed. The delay value used before jumping to the *hax payload can now be configured with menuhax_manager.
What happened to menuhax’s blank theme?
The additional theme-data used when menuhax is installed (themehax/shufflehax), is now initialized with a blank theme .lz, instead of leaving it at all-zeros. This was implemented because this is required with shufflehax.