Hacking haxchi update option

[pidibi36421]

hi!

my question does not concern the "haxchi cfw" (i use "mocha cfw")
my question is about the "haxchi exploit" only

/////

it says on the "hachi exploit":

-not install the "hachi exploit" with a nds game downloaded illegally (otherwise = brick)

-to update the "hachi exploit" reuse the nds game without redownloading it

/////

but after having:
-bought / downloaded the game nds "legally"
-installed the "hachi exploit"

the game is now in "hacked" state, right?

1- will not it cause a brick, if i try to update the "hachi exploit" with this game nds in its hacked state?

2- do I have to run the "mocha cfw" to update the "hachi exploit"? if i run the "modcha cfw" before updating the "haxchi exploit", is there a risk or not? ---> EDIT, i have my reponse, i must not execute a "cfw" when installing/updating "haxchi exploit"

3- if i update the "haxchi exploit" v4.444 (example) with the same version (v4.444), is there a risk of brick or not?

4- it says that if we want to reinstall "hachi exploit", we must remove the nds game and download it again; why since an update does not need to remove the nds game and download it again?

thks.

 

[Ryccardo]

but after having:
-bought / downloaded the game nds "legally"
-installed the "hachi exploit"

the game is now in "hacked" state, right?

A pirated eShop game (like every DS game) will not run without CFW, therefore if you set it as launcher (like the CBHC installer does) the console won't boot
A game with its executable modified will also fail verification, without CFW
However, it's possible to modify non-executable files, and the game will still run without CFW being launched (this principle has been called "contenthax", and is exactly what Haxchi/CBHC take advantage of)

There is no brick risk associated with overwriting or deleting the game used for Haxchi, because the DS game is not set as launcher

will not it cause a brick, if i try to update the "hachi exploit" with this game nds in its hacked state?

No, see above

3- if i update the "haxchi exploit" v4.444 (example) with the same version (v4.444), is there a risk of brick or not?

4- it says that if we want to reinstall "hachi exploit", we must remove the nds game and download it again; why since an update does not need to remove the nds game and download it again?

Reinstalling haxchi (the same version, to load a new config.txt - or even a different version) can be directly installed over the existing one; worst case scenario, you will have to delete it, redownload from eShop, and install again

 

[pidibi36421]

what i understand:

buy legit marios 64 nds on eshop, and install "haxchi exploit" on it (cfw not launched)

after:

-for "uninstall" "haxchi exploit"
-> delete the nds game or format wii u or remove nnid (cfw not launched)

-for "update" (with new version) or "reinstall" (same version for config.txt or other reason) "haxchi exploit"
-> keep the nds game "haxchi patched", run a second time the "haxchi installer" from "sdcard files" +
"homebrew launcher" (cfw not launched)

the legit mario 64 nds:
-have her legit signature/authorization somewhere in the nand of the wii u

the legit mario 64 nds "haxchi patched":
-have always her legit signature/authorization somewhere in the nand of the wii u
-"hachi exploit" modify the content of the game, but not her signature/authorization

a non legit nds game
-have not her signature/authorization in the nand of the wii u
-do not work directly

am i right?

 

[Cyan]

that's right
you understood it.


A title installed on WiiU has 3 folders attached to it :

/code/
/content/
/meta/

the /code/ contains the excutable, and all the files located in this folder is verified by the console at launch. If a file is not legit, or has been modified, the console refuse to launch it.
the /content/ contains additional files, could be anything (pictures, binary, the actual game files, not the executable). these file's integrity are not checked by the console.
the /meta/ contains information about the title (game's TitleID, the game's title in each different language, whether the gamepad is enabled or not, etc.), and the icons you see on your WiiU main menu, and the one you see when you launch the game.


NDS virtual console games are like this :
/code/ <-- contains the emulator's executable.
/content/ <-- contains the NDS ROM in zip format (rom.zip)
/meta/ <-- just simple config files, and pictures for wiiu menu. not verified by the console either.


Haxchi replace the rom.zip file with another one, which the console doesn't verify. the new NDS rom actually contains the code which crashes the NDS emulator by exploiting some if its vulnerabilities to crash the console to allow user level access code execution. (allow you to run homebrew). it's not patching the kernel access at this point.
the /code/ and the emulator are not edited and the console launches that channel without problem, it doesn't know the ROM has been modified and loads it like it would with any other rom.zip

you can reinstall haxchi over and over, it will only replace the rom.zip, the config.txt (not in the legit game, it's added by haxchi), and the pictures located in /meta/ so you can edit the pictures which appear on your console. "H" or "Haxchi" can be anything else you want.


if you install a pirated version of the NDS virtual console using WUP installer, then the /code/ contains an unsigned version of the executable, and requires CFW to be launched.



Like you noted on your first post, haxchi exploit is different than haxchi CFW.
the exploit only allows user level homebrew execution. it's similar to browser hax, but offline, and is primarily used to launch a homebrew. (usually, homebrew_launcher.elf)
it can launch any homebrew, even ones that do more patches like kernel access patches (mocha.elf, or internally coded haxchi cfw patcher), this one grants kernel access and persistent cfw with signature check patched out.
I think most people mix both haxchi exploit and cfw together because of it's integrated form. It's nice that you understood there are two different things

 

[pidibi36421]

A title installed on WiiU has 3 folders attached to it :

/code/
/content/
/meta/

in decrypted form, i already understood this, thks.

the /code/ contains the excutable, and all the files located in this folder is verified by the console at launch. If a file is not legit, or has been modified, the console refuse to launch it.
the /content/ contains additional files, could be anything (pictures, binary, the actual game files, not the executable). these file's integrity are not checked by the console.
the /meta/ contains information about the title (game's TitleID, the game's title in each different language, whether the gamepad is enabled or not, etc.), and the icons you see on your WiiU main menu, and the one you see when you launch the game.

i already understood this "partially",thks for important clarifications.

NDS virtual console games are like this :
/code/ <-- contains the emulator's executable.
/content/ <-- contains the NDS ROM in zip format (rom.zip)
/meta/ <-- just simple config files, and pictures for wiiu menu. not verified by the console either.

Haxchi replace the rom.zip file with another one, which the console doesn't verify. the new NDS rom actually contains the code which crashes the NDS emulator by exploiting some if its vulnerabilities to crash the console to allow user level access code execution. (allow you to run homebrew). it's not patching the kernel access at this point.
the /code/ and the emulator are not edited and the console launches that channel without problem, it doesn't know the ROM has been modified and loads it like it would with any other rom.zip

you can reinstall haxchi over and over, it will only replace the rom.zip, the config.txt (not in the legit game, it's added by haxchi), and the pictures located in /meta/ so you can edit the pictures which appear on your console. "H" or "Haxchi" can be anything else you want.

if you install a pirated version of the NDS virtual console, then the /code/ contains an unsigned version of the executable, and requires CFW to be launched.

interesting part.

i thought the emulator nds was already on the console, but no, he is missing.
in fact it is packaged in each nds game, like a little for psx games on psp.

only the not verified part (rom.zip) is hacked, so the wii u launch it without verification.

ok, now, having thought well, I have now understood

Like you noted on your first post, haxchi exploit is different than haxchi CFW.
the exploit only allows user level homebrew execution. it's similar to browser hax, but offline, and is primarily used to launch a homebrew. (usually, homebrew_launcher.elf)
it can launch any homebrew, even ones that do more patches like kernel access patches (mocha.elf, or internally coded haxchi cfw patcher), this one grants kernel access and persistent cfw with signature check patched out.

me, i ran the local version (HaxServer.jar).

i've understood that:
-kexploit is an exploit "userspace" temporary, requiring an pc or internet for access to loadiine.ovh (example) for work
-haxchi exploit is an exploit "IOSU" who resists to a reset of the wii u caused by a cfw, but not to a power off, and it can be restarted autonomously




thk you ^^