Homebrew What's the difference between mocha and sys2patcher?

[Psygnosis]

Hi all.
I want to understand technically what's the difference between mocha cfw (loaded to sysnand) and sys2patcher.
Cause I don't understand why I had to run both to install something to sysnand through.
So: what mocha ad sys2patcher do?

I have another question. Can I install hbl on sysnand though mocha without have haxchi?

Thank you sorry for the strange question I like to understand what hb and hack do.

 

[AmandaRose]

You don't need to run both to install to sysnand you only need one of them. I only have mocha and have installed over 250 games that way including homebrew launcher. Mocha is an advanced version of simple signature check patcher) with more features.

 

[Psygnosis]

sorry for necroposting I don't like to create endless thread for the same question.
I have some free time to play with wiiu.
So:
1. I can start hbl through browser hack -> start mocha ->install hbl in sys via wupinstaller?
2. Is there a way to check that mocha is running in sys?
3. when I press on mocha homebrew no option are showed it just reboot in sys (or hbl I don't remember now) is that normal?

Thank you

 

[NeroAngelo]

sorry for necroposting I don't like to create endless thread for the same question.
I have some free time to play with wiiu.
So:
1. I can start hbl through browser hack -> start mocha ->install hbl in sys via wupinstaller?
2. Is there a way to check that mocha is running in sys?
3. when I press on mocha homebrew no option are showed it just reboot in sys (or hbl I don't remember now) is that normal?

Thank you

You'll notice the loading logo change, once Mocha is run once, it will stay active until you restart the WiiU

 

[Deleted User]

[Kinda] Quote from my redNAND-free guide:
"Mocha CFW works as CFW, giving you 'iosuhax speed boost' which will greatly increase SDCard performance [and Wii U's NAND speed], Sigpatcher2 only gives you sigpatching and isn't an CFW. Sigpatcher is slow when it comes to loading roms off SDCard or any sort of homebrew."

 

[Cyan]

signpatcher IS a custom firmware in the same sense than other system patchers : it patches the firmware to replace/edit some original functions.
it has less features than mocha, but for the end user who only wish to install or play a wiiu game requiring signature+region patch, it's enough.

Like you said, Mocha has additional SDCard performance, but it's NOT related to games, it's only for homebrew taking advantage of mocha's file system patch, like RetroArch ROM listing from SD card.

So, technically, both are good for playing games only, and you need to run only one, not multiple patchers, to get signature patched.
Use Mocha if you want homebrew SD access speed increase (retroArch or any other heavy SD file access homebrew which are taking advantage of IOSUHax speed improvement).
use signature patcher return to sys, if you want to play games (it's patching the system faster as it edit less functions in the firmware)
use signature patcher return to hbl, if you want to install game (it returns to HBL so it's faster to launch WUP installer next)
use Mocha if you don't care about patch time, or don't want to bother with multiple patcher based on what you want to do next.

 

[Psygnosis]

You'll notice the loading logo change, once Mocha is run once, it will stay active until you restart the WiiU

Well I don't see any logo change. It's always the wiiu logo. Maybe there is something that are not working =(

Edit:
So if I have mocha running and hbl installed on sysnand I could launch hbl from menu until I restart the console right?

 

[Cyan]

Browser hax is the one responsible for still being able to run HBL until you restart the console.
browser hax = allow homebrew launching
simple sigpatcher = signature + region patch
mocha = keep "browser hax" feature + signature + region patch (and other patches) + repatch all on system reload
CBHC or haxchi : "browser hax" + the other patches too + repatch all on system reload


if you run browser hax, and then Mocha, and don't disable the "reload OS" option, all the patches will stay in memory until you shutdown the console.
if you disable "reload OS" or use simple signature patcher instead of Mocha, you'll lose the patches if you go to the console's settings and you'll have to run browser hax once again to get signature+region patches back.

if you install the homebrew launcher as channel, you'll have to be in a "patched mode" to run it.
just try to run it, if it's working then it's good. if you have an error, it means you need to patch your console first (run mocha, or any other firmware patcher first) which will stay in memory as long as you don't reset the firmware (reboot, or go to settings if you don't use a "reload OS" compatible patcher)


I'm not sure, but you might have to run Miimaker if you want to run the homebrew launcher a second time.
When running HBL for the first time in browser hax mode, it's replacing miimaker with HBL code. to run HBL again you don't have to run browser hax again as you just need to run miimaker (now that it's replaced with HBL).
I don't know if the HBL channel work the same way and is just a "patcher to replace Miimaker with HBL" or if it's a real channel with its own executable code.

But if you install HBL channel and use Mocha or signature patcher, then the HBL channel is REALLY not needed!
this is because to run Mocha or signature patcher, you need to run browser hax first to run HBL to run mocha, which set HBL inside miimaker. so you already has HBL as channel (in miimaker!).

The standalone HBL channel is useful only if you have haxchi or CBHC, and you don't have to use internet's browser exploit to run homebrew at all.

sysmenu -> browser exploit -> homebrew compatible console -> HBL set in Miimaker channel and autorun the first time; next time you want HBL just run miimaker
or
sysmenu -> haxchi or chbc -> homebrew compatible console -> HBL as channel (set hbl code in miimaker channel or not?); next time you want HBL run HBL channel or miimaker? (that I would like confirmation)

 

[Deleted User]

If you run browserhax once, then everytime you will want to run it, you can use Mii Maker.

 

[NeroAngelo]

Browser hax is the one responsible for still being able to run HBL until you restart the console.
browser hax = allow homebrew launching
simple sigpatcher = signature + region patch
mocha = keep "browser hax" feature + signature + region patch (and other patches) + repatch all on system reload
CBHC or haxchi : "browser hax" + the other patches too + repatch all on system reload


if you run browser hax, and then Mocha, and don't disable the "reload OS" option, all the patches will stay in memory until you shutdown the console.
if you disable "reload OS" or use simple signature patcher instead of Mocha, you'll lose the patches if you go to the console's settings and you'll have to run browser hax once again to get signature+region patches back.

if you install the homebrew launcher as channel, you'll have to be in a "patched mode" to run it.
just try to run it, if it's working then it's good. if you have an error, it means you need to patch your console first (run mocha, or any other firmware patcher first) which will stay in memory as long as you don't reset the firmware (reboot, or go to settings if you don't use a "reload OS" compatible patcher)


I'm not sure, but you might have to run Miimaker if you want to run the homebrew launcher a second time.
When running HBL for the first time in browser hax mode, it's replacing miimaker with HBL code. to run HBL again you don't have to run browser hax again as you just need to run miimaker (now that it's replaced with HBL).
I don't know if the HBL channel work the same way and is just a "patcher to replace Miimaker with HBL" or if it's a real channel with its own executable code.

But if you install HBL channel and use Mocha or signature patcher, then the HBL channel is REALLY not needed!
this is because to run Mocha or signature patcher, you need to run browser hax first to run HBL to run mocha, which set HBL inside miimaker. so you already has HBL as channel (in miimaker!).

The standalone HBL channel is useful only if you have haxchi or CBHC, and you don't have to use internet's browser exploit to run homebrew at all.

sysmenu -> browser exploit -> homebrew compatible console -> HBL set in Miimaker channel and autorun the first time; next time you want HBL just run miimaker
or
sysmenu -> haxchi or chbc -> homebrew compatible console -> HBL as channel (set hbl code in miimaker channel or not?); next time you want HBL run HBL channel or miimaker? (that I would like confirmation)

to boot HBL when using Haxchi, i just set it to autoboot it OR i set it to a button combo

 

[Cyan]

yes, but I would like to know if you can run Miimaker to run HBL a second time when NOT using browser hax.

haxchi -> hbl channel -> exit hbl
then to run HBL, can you run HBL channel again or will it freeze? I've read few time that you have to run miimaker the second time, I would like confirmation that running HBL channel multiple times work or not.

I guess it should work, as it's like if you run the elf multiple time from haxchi+config file. it's just running the elf/rpx ?

 

[NeroAngelo]

yes, but I would like to know if you can run Miimaker to run HBL a second time when NOT using browser hax.

haxchi -> hbl channel -> exit hbl
then to run HBL, can you run HBL channel again or will it freeze? I've read few time that you have to run miimaker the second time, I would like confirmation that running HBL channel multiple times work or not.

Oh sorry, that's what i meant, what's the point of wanting to run it from miimaker again when using haxchi? you can just boot haxchi again and either set it to auto boot to HBL or boot to it using a button combo

 

[Cyan]

well, I understand that you can set it to a shortcut inside haxchi.
That's still not what I'm wondering.

let's say the user is using CBHC instead of haxchi then.
I'm talking about the HBL channel. no shortcut.

cbhc -> sysmenu -> HBL channel -> exit HBL
now what? can you run HBL channel again or will it freeze?

I guess only running browser hax twice is freezing, it's unrelated to HBL right?
Second question : is running the HBL channel version also set HBL to Miimaker?

 

[Deleted User]

well, I understand that you can set it to a shortcut inside haxchi.
That's still not what I'm wondering.

let's say the user is using CBHC instead of haxchi then.
I'm talking about the HBL channel. no shortcut.

cbhc -> sysmenu -> HBL channel -> exit HBL
now what? can you run HBL channel again or will it freeze?

I guess only running browser hax twice is freezing, it's unrelated to HBL right?
Second question : is running the HBL channel version also set HBL to Miimaker?

You can run it 4-6 times before it will freeze.
To that second question: I don't think so. Will check that in a minute.

 

[Cyan]

thank you, I'll update the HBL release thread with these answers


edit:
I updated HBL first post.

- I added loadiine.ovh and wiiubru.com/x as possible remote launching website for the browser hax mode.
- I added information on subsequent launches when using browserhax, user has to run miimaker channel instead of a second browser hax exploit.
- I added HBL+haxchi method
- I added Haxchi and CBHC to possible CFW for channel installation (I guess if they can run it, they can install it too, right?)
- I deprecated the fw.img method
- I said you can run the HBL channel version multiple times instead of launching miimaker. (in prevision of your test and report)
- I said channel version is not useful if using haxchi, as it can be run from config.txt +SD card instead.

if anything is wrong or need precision, let me know.