Hacking Change Bootlogo/healthscreen on 4.2

[WiiShizzza]

I wanna try a custom bootlogo on 4.2....
- extracting the 0000008a.app from the SM.wad and changing health.ash, then repacking the wad, works.
...but to minimize the risk I don't wanna patch and install a changed SM.wad, I wanna dumb the needed app file from nand...
here comes my problem. Which file I should dump from wii nands "shared1" ?

...i tried to extract several app files which I got with the FSToolbox, but U8Tool 10.1 gives me errors on some.
The files I can extract with u8tool doesn't include the health.ash. I don't know if the problem is cos I'm running u8tool under win7?

Anyone any hint ?

 

[XFlak]

isn't this similar to mymenuify? Maybe try looking at its source code???

 

[WiiShizzza]

hmm... mymenuify... i don't want to use such tools... but maybe I can find something in the source...
if I remember correct, on FW 3.4 the file to dump was the 0000042.app on FW 4.0 it was the 0000072.app... or do I mix something up right now...

//EDIT:

DANG

That was my 1000s post

 

[damysteryman]

0000008a.app is not shared.

It is found in isfs:/title/00000001/00000002/content/0000008a.app.

dump it, then extract it with a U8 extractor.

After extracting, the health.ash will be found in:
0000008a_app_OUT\layout\common\health.ash.

You need ash0.exe (should be on wiibrew) to convert it from an ash to an arc, then extract it, and mod it all you want.

After modding it, just repack it to an arc file (no need to re-ash it).

Then repack everything, and write the modified 0000008a.app to NAND. (have bootmii backup ready though, just in case)

 

[WiiShizzza]

you're right about the path, da_letter_a, I was a bit confused...
And also you're right with the steps. These are the same I always did on older FWs, except I repacked the whole wad.

I'm not sure if writing the 0000008a.app to NAND would bring the success... maybe I'm just too scared to try^^

... ATM I'm dumping my nand, then I'll compare the 0000008a.app that I get with NUSD with the one I dumped.

I normally use yaz0 to compress the repacked arc. that'll save around 5MB

//EDIT:
I was able to create 16:9 bootscreens way back in time on 3.4.

Ohh... just to mention the "theme" was made before benzin was born... goood ol' dayz

 

[damysteryman]

you can rewrite it with fstoolbox, or repack the wad, just like old times. Both work.

And yeah, yaz0 compression is a good idea.

Quick trivial question: I wonder why the system menu supports yaz0 decompression in the first place?

All this talk about theming makes me want to port my 3.2 theme that I never released.

 

[WiiShizzza]

I knew the answer some time. But I totally lost it... I'm getting old.^^ and not beeing active since a year doesn't bring the knowledge back...
yaz0 is a relict from the gamecube times...

Yeah, I also got plenty of unreleased bootscreens on my old HDD. But as they are wads, i never released them and i guess i never will.

mymenuify is the only way how to release themes or bootscreens...

 

[WiiShizzza]

Heres what I did, and that ended with a black scree. luckily I got bootmii in boot2:

-I extracted the modded health.ash out of my old 0000042.app and copied it over the health.ash inside the 4.2 000008a.app_OUT folder.
-then I repacked the 000008a.app_OUT folder to a 000008a.app (checked again with parseu8 if the structure was right)
-after that i overwrote the 000008a.app in nand (/title/00000001/00000002/content/0000008a.app.)

After restart, I was lucky I had bootmii installed...

it didn't look like the 3.2-health.ash was different then the 4.2-health.ash...
You think I should take some time and build up the health.ash from scratch?

//EDIT:
Well, problem solved

I got it working. I was able to rebuild a working 000008a.apa and installed it with FSToolbox.
Now I got a modded healthscreen on 4.2