Hacking (v)Wii homebrew channel open sourced

[r4dius]

Thanks man worked like a charm ,
Btw is it safe to delete the old version using the wii channel manager ?

 

[Ryccardo]

Thanks man worked like a charm ,
Btw is it safe to delete the old version using the wii channel manager ?

Yeah, why shouldn't it be?

But it may be hard to find, without using an (homebrew) title manager that displays titleIDs (like AnyTitle Deleter Mod)

 

[r4dius]

Yeah, why shouldn't it be?

But it may be hard to find, without using an (homebrew) title manager that displays titleIDs (like AnyTitle Deleter Mod)

Ahah just not sure of this with all the things that can brick it ^^, yeah it was not ordered like on the menu but I got it deleted now thanks

 

[DestinySky]

Installed Open Homebrew Channel v1.1.4-1 on a fresh emunand built with ModMii on a real Wii, got error below after launch, while OHBC trying to load files (can see HBC menu with the circle for about 2 secs).

 

[Zonta85]

I don't know how to code, is like speaking Arabian for me.
So I'm asking if is possible to have a compiled version of this with the old title id to replace the Homebrew channel and fixing the Widescreen issue.

 

[MushGuy]

@FIX94 Will this channel have support for the Gamecube Controller Adapter in the future? That would be very useful for Wii U users who have this but not the Wii Remote.

 

[DestinySky]

Installed Open Homebrew Channel v1.1.4-1 on a fresh emunand built with ModMii on a real Wii, got error below after launch, while OHBC trying to load files (can see HBC menu with the circle for about 2 secs).

As you are so helpful to me, may I ask if you can have a look on my other problem here too @Cyan

 

[Cyan]

that's an old thread. you still have that problem?

fresh emunand built with ModMii on a real Wii

Well, first you say you used a fresh emuNAND?
then you say "on a real Wii"

do you use that fresh built NAND as "real NAND" (written back to NAND with NAND flasher or bootmii? or rebuilding and converting it with your own consoles keys ?)

or are you trying that emuNAND with neek?
I don't know if OHBC work on neek, but I guess it would need the same "ticket trick" than the original HBC on neek.

Second, that screen doesn't help me at all, as I would need to have compiled that version myself and kept the elf file for debugging purpose.
to debug with that screenshot, you need to contact the person who compiled it and released it, in hope he kept the elf file if you have only the dol.

if it's neek, did you try original HBC instead of OHBC?

 

[DestinySky]

that's an old thread. you still have that problem?


Well, first you say you used a fresh emuNAND?
then you say "on a real Wii"

do you use that fresh built NAND as "real NAND" (written back to NAND with NAND flasher or bootmii? or rebuilding and converting it with your own consoles keys ?)

or are you trying that emuNAND with neek?
I don't know if OHBC work on neek, but I guess it would need the same "ticket trick" than the original HBC on neek.

Second, that screen doesn't help me at all, as I would need to have compiled that version myself and kept the elf file for debugging purpose.
to debug with that screenshot, you need to contact the person who compiled it and released it, in hope he kept the elf file if you have only the dol.

if it's neek, did you try original HBC instead of OHBC?

Yes, real Wii as in not vWii, and I'm using neek2o+di emunand built with modwii with my own wii serial number.
The one I'm trying to run is this: https://github.com/FIX94/hbc/releases
What is this ticket trick, maybe I can try it out?

I just find that it is strange no one have this problem on neek2o emunand except me.

 

[Cyan]

installing the channel using a wad manager usually corrupt/patch the ticket (maybe depending on the used wad manager?), or maybe it's the WAD dumper which does that. Nobody tried install a wad created using BlueDumpMod without patching enabled?

HBC check if the ticket is good or altered and stop working if it is, but usually with an error message, not a crash.
the trick was to install HBC with hackmii installer on your NAND. dump HBC to wad, and dump your original ticket file from NAND. install WAD to emuNAND (with showmiiwad for example) and overwrite bad ticket with good one manually to emuNAND folder.
OHBC is only available as wad, without installer, so they probably removed that ticket check.


the github you linked don't have the elf file for debugging purpose.
I don't know if the crash is from the channel booter, or from OHBC either.

is the original HBC working on your neek2o?
I didn't follow OHBC usage, other users reported installing it to neek? which wad installer did they use?

 

[niuus]

I didn't follow OHBC usage, other users reported installing it to neek? which wad installer did they use?

Not an emunand user, but i always use YAWMM, since it is the most recent.

 

[DestinySky]

installing the channel using a wad manager usually corrupt/patch the ticket (maybe depending on the used wad manager?), or maybe it's the WAD dumper which does that. Nobody tried install a wad created using BlueDumpMod without patching enabled?

HBC check if the ticket is good or altered and stop working if it is, but usually with an error message, not a crash.
the trick was to install HBC with hackmii installer on your NAND. dump HBC to wad, and dump your original ticket file from NAND. install WAD to emuNAND (with showmiiwad for example) and overwrite bad ticket with good one manually to emuNAND folder.
OHBC is only available as wad, without installer, so they probably removed that ticket check.


the github you linked don't have the elf file for debugging purpose.
I don't know if the crash is from the channel booter, or from OHBC either.

is the original HBC working on your neek2o?
I didn't follow OHBC usage, other users reported installing it to neek? which wad installer did they use?

Yes, that's is actually the first thing I did (install hbc on sysnand, dump the wad from nand dump then install it to neek2o emunand usinf showmiiwad) once I realized I cant install HBC 1.1.2 the normal way. It crashed, so I install the OHBC 1.1.4-1 using showmiiwad, it too crashes. One thing to mention, Wiiflow Lite also don't work in neek2o while old Wiiflow from fix84 works.

Meanwhile, on sysnand, everything works, HBC 1.1.2 , OHBC 1.1.4-1 works, Wiiflow Lite works.

 

[Cyan]

loaders on neek are not a good idea, as the "devices" are seen differently.
the "SD" is now seed as "real NAND"
SD is unavailable
USB is unchanged

if the loader tries to load config files from SD, while you didn't enable "sd access for homebrew" when compiling sneek, then your homebrew have only access to "real NAND" (actually located on SD) and USB.
I don't know how wiiflow/lite are working, it's just a general information which might, or might not be related to the crash.

no idea for OHBC.
you should be able to install HBC though.


If you made a "NAND dump to emuNAND" with HBC already installed, HBC should work as it already contains the proper ticket.
If you made a "clean emuNAND" from modmii, you'll have to dump HBC to wad. install that wad to emuNAND (showmiiwad). extract the ticket from your NAND to copy it to emuNAND.
OR maybe dump HBC as wad using proper signed ticket. try to dump to wad using BlueDumpMod with all option to "fake sign" disabled. maybe it'll be enough to make it work.

But, this is only one way to do it.
I couldn't find the thread, but I thought there were a way to fix the ticket by editing it in hexeditor. Maybe my memory is failing.

 

[DestinySky]

Alright thanks a lot for your feedback.

All these while I thought that Wi emunand is the same as 3DS or switch emunand, as in everything is the same as sysnand just that filesystem be redirected to another device (another partition on sd etc), thus everything that works on sysnand should work on emunand as it makes no different to all homebrew.
But it seems that it's not the case for wii.

The reason I use emunand is to try to save the wii sysnand from wear and tear.

I think I shall end my quest trying to make HBC or OHBC and wiiflow to work on emunand.
I can use postloader as an alternative for HBC/OHBC, and neek2o native wbfs loader on the disc channel instead of wiiflow lite (no fancy boxart etc).

Thanks again for finally closing this chapter of my gaming life.

 

[Cyan]

emuNAND on wii is not a "full binary copy of the encrypted partition" like 3DS or Switch as there's no full firmware always loaded in the background or hardware hack to do the emmc redirection.
it's active file and folders redirection done by current loaded apps "on the fly", it's not meant to be a daily environment usage, but more a "check if something would break" without bricking real NAND (like theming the sysmenu).
it can also be used as a way to play specfic game backup that wouldn't work on USBLoaders or cIOS method due to piracy detection functions in such games.

on Wii, the emuNAND is more about "using the Wii as if it wasn't hacked", which is why some games work only with neek (not hacked = no piracy detected), so you don't install or launch homebrew from it. you could, on specific condition, but it's really not a good idea. real NAND should be used as first choice when possible.

 

[niuus]

The reason I use emunand is to try to save the wii sysnand from wear and tear

Your Wii's NAND will probably outlive you, even if you play Virtual Console titles copied to your SD a lot and play large N64 games with the emulators.

 

[DestinySky]

Your Wii's NAND will probably outlive you, even if you play Virtual Console titles copied to your SD a lot and play large N64 games with the emulators.

I do encounter Wiis that have many (>100) bad blocks.
Also emunand prevent bricks by unnecessary action by it's user (my niece etc).

 

[universales]

I think the wad is out of date @FIX94 .
Could you update it from the official repository?
Thanks

 

[TeleTubby666]

I would second that question

I don't know how to code, is like speaking Arabian for me.
So I'm asking if is possible to have a compiled version of this with the old title id to replace the Homebrew channel and fixing the Widescreen issue.

 

[geoGolem]

ya, it looks like it is 9 commits behind the official failoverflow repo... not sure if it matters, but ill just stick with existing HBC but will switch to OBHC if it gets rebased with HBC latest...