Homebrew mocha cfw options

[pidibi36421]

thank you for your answers and your patience



bye

EDIT

if "Don’t relaunch OS" is "off" it's does not cancel the action of haxchi exploit ?

 

[Ryccardo]

if "Don’t relaunch OS" is "off" it's does not cancel the action of haxchi exploit ?

Haxchi, when used to launch an homebrew (including the HBL), does not have any patching effects anyway

If you started Haxchi minicfw first, yes, you would want (and propably need) to disable it (by leaving that option off); but there's no reason or advantage to launch 2 CFWs in a row!

 

[pidibi36421]

"haxchi exploit" only serves to launch something; it is "this something" who patch/crack the wii u

 

[Ryccardo]

"haxchi exploit" only serves to launch something; it is "this something" who patch/crack the wii u

Exactly, and since you only want to use Mocha as CFW, "this something" is Mocha, so it doesn't have to bother with a non-existing already running CFW

 

[pidibi36421]

in fact I was a little scared because i have read that if the console was to restart, "haxchi exploit" and "modcha cfw" effects will disappear.

in fact, i must understand that "Do not relaunch OS" "off" does not restart the console?

 

[Ryccardo]

in fact I was a little scared because i have read that if the console was to restart, "haxchi exploit" and "modcha cfw" will disappear.

in fact, i must understand that "Do not relaunch OS" "off" does not restart the console?

If off, it does indeed soft reset the console, which is not a problem (just takes more time)

The effects of any already running CFW disappear when the system is reloaded; it does not mean that Haxchi/the DS game is deleted from the console, or that Mocha is removed from the SD

 

[pidibi36421]

i do not understand

launching modcha:
-reset the console ---> ok
-do not remove effect of haxchi hack, because, it is just a "launcher" and has no effect ---> ok
-keeps modcha effects ---> how ?

for the non deletition, i knew it, but thks

 

[Ryccardo]

-keeps modcha effects ---> how ?

Mocha stays active until your console is turned off or restarted (for any reason), if you do one of those things (and need Mocha again) you simply need to start Mocha again

 

[pidibi36421]

i understand:
wii u reset = mocha effects disappear
wii u power off = mocha effects disappear

i do not understand:
wii u power on > "haxchi exploit" > "home brew launcher" > "mocha cfw" launched with option "Don’t relaunch OS" is "off" > the wii u do an automatic reset > mocha launch -_-''''

how, since the console has reseted?

 

[Ryccardo]

i understand:
wii u reset = mocha effects disappear
wii u power off = mocha effects disappear

i do not understand:
wii u power on > "haxchi exploit" > "home brew launcher" > "modcha cfw" launched with option "Don’t relaunch OS" is "off" > the wii u reset > modcha launch -_-''''

how, since the console has reseted?

1- When the console (re)starts normally, the bootroms finds fw.img in the SLC nand chip, verifies, loads, and runs it, then fw.img starts loading the rest of the operating system

2- When a CFW that relaunches OS starts, it loads a copy of fw.img, applies patches to it, then it runs it (which is possible because it doesn't go through the bootrom's checks (simplified))

3- When a CFW that doesn't relaunch OS starts, it applies patches to the copy of fw.img already running (the copy that was loaded in 1-)

 

[pidibi36421]

1- the console checks the existence/hash/signature of the original fw.img located into the nand, if ok, she loads it in ram

2- the console restarts, makes a copy "somewhere" of the original fw.img located into the nand, applies patches to it, then loads it in ram
-> this works because it's not a "complete real" reset ?

3- the cfw patches the original fw.img loaded in ram (1-)

am i right ?

 

[Ryccardo]

1- the console checks the existence/hash/signature of the original fw.img located into the nand, if ok, she loads it in ram

2- the console restarts, makes a copy "somewhere" of the original fw.img located into the nand, applies patches to it, then loads it in ram
-> this works because it's not a "complete real" reset ?

3- the cfw patches the original fw.img loaded in ram (1-)

am i right ?

Pretty much, there are some details I did not explain (like how it convinces the system to change to the patched fw.img that does not pass checks) but the general concept is that one

 

[pidibi36421]

I think I now have all the information needed to understand a minimum how the hack works.

thanks ^^
good night.