346
edits
Changes
Jump to navigation
Jump to search
Line 31:
Line 31: + + +
“How it works” section
==Usage==
==Usage==
The DS game that Haxchi is installed over will be replaced by a new channel, the Haxchi Channel. Launching this channel loads up the Haxchi CFW, although certain buttons can be configured to perform certain actions instead of loading the CFW. For example, many people configure A to load the [[Homebrew Launcher]] to skip the need to run an inconsistent Browserhax exploit, though this quickly gets superseded by a dedicated channel for HBL installed by [[WUP Installer]].
The DS game that Haxchi is installed over will be replaced by a new channel, the Haxchi Channel. Launching this channel loads up the Haxchi CFW, although certain buttons can be configured to perform certain actions instead of loading the CFW. For example, many people configure A to load the [[Homebrew Launcher]] to skip the need to run an inconsistent Browserhax exploit, though this quickly gets superseded by a dedicated channel for HBL installed by [[WUP Installer]].
==How it works==
Haxchi first gains root access using [[Uhshax]]. It then takes advantage of the contenthax bug, which allows every part of a title except the actual code to be modified without invalidating it. In the case of Virtual Console games, this code is the emulator, not the game’s code, which means the game itself can be modified. Haxchi replaces the game’s code with a sequence of bytes that sets up ROP, and therefore can pass code execution to itself. Haxchi also replaces the title and banner of the game, since these are not checked either, to look like a different title.