Hacking Priiloader 0.9 Released!

[DacoTaco]

is there by any chance anyone still around that knows how it works, all the technical details? cause this code is... eug

 

[Magnus87]

I will never tire of saying Thank You Daco!
It is incredible that the flame for continuing to develop for Wii is still alive within you. No matter how small the update or improvement you can make, it is really something valuable.

 

[XFlak]

is there by any chance anyone still around that knows how it works, all the technical details?

@Etheboss, @OverjoY, @obcd, any of you dudes still around by any chance?

--------------------- MERGED ---------------------------

is there by any chance anyone still around that knows how it works, all the technical details?

Also don't forget that I can't get even this v0.7 neek mod to load at the present time. So even if you replicate all the changes perfectly it may still not work... that being said, because I KNOW it was working once upon a time, the issue may be with something I did to break my personal setup (edit: like maybe updating neek itself? Discussed more below)

If anyone else is able to help test (I'm thinking of my favourite volunteer right now @alexander1970 lol) these are all things I was thinking to try:

1) do as Daco suggested and install priiloader v0.9, enable logging in priiloader, save, then make a nand backup, extract for use with neek and load it up as per usual. Try booting it via GX and traditional bootmii methods to see if it makes a difference (hold reset while booting neek to try and access neek priiloader). Pro testing tip: after making the nand backup, on your real nand move some system menu channels around and change priiloader's background color so that you can easily identify whether you're inside your real vs emulated nands. When done obv please share the logs and results here.

2) Download and see if you can get the Priiloader v0.7 neek mod to work. For this you probably want to boot UNEEK and save the installer to SD, and run it from inside uneek. Assuming it installs correctly, see if you can access it by holding reset when booting your emunand. Also try the priibooter app that comes with it.

3) similar to above, try manually injecting the neek mod of v0.7 priiloader.app. This is actually super easy because of modmii, just use ModMii's emulated nand modifier to inject it into your Emunand, and test again.

4) I wonder if perhaps this isn't working anymore because of updates to neek2o. I haven't checked yet, but I am curious to compare the release dates for the latest neek2o and the priiloader v0.7 neek mod. Assuming there's a big time difference here, maybe try an older version of neek2o to see if it's failing only because of being run on newer\incompatible versions of neek.

I feel like I had one more idea to try, I'll edit this post if I think of it. And if no one else is able to test before me, I will eventually get around to it, but it may take me a bit.

 

[Alexander1970]

@Etheboss, @OverjoY, @obcd, any of you dudes still around by any chance?

--------------------- MERGED ---------------------------


Also don't forget that I can't get even this v0.7 neek mod to load at the present time. So even if you replicate all the changes perfectly it may still not work... that being said, because I KNOW it was working once upon a time, the issue may be with something I've done.

If anyone else is able to help test (I'm thinking of my favourite volunteer right now @alexander1970 lol) these are all things I was thinking to try:

1) do as Daco suggested and install priiloader v0.9, enable logging in priiloader, save, then make a nand backup, extract for use with neek and load it up as per usual. Try booting it via GX and traditional bootmii methods to see if it makes a difference (hold reset while booting neek to try and access neek priiloader). Pro testing tip: after making the nand backup, move some channels on your real nand system menu and change priiloaders background color so that you can easily identify which is loaded. When done obv please share the logs and results here.

2) Download and see if you can get the Priiloader v0.7 neek mod to work. For this you probably want to boot UNEEK and save the installer to SD, and run it from inside uneek. Assuming it installs correctly, see if you can access it by holding reset when booting your emunand. Also try the priibooter app that comes it.

3) similar to above, try manually injecting the neek mod of v0.7 priiloader.app. This is actually super easy because of modmii, just use ModMii's emulated nand modifier to inject it into your Emunand, and test again.

4) I wonder if perhaps this isn't working anymore because of updates to neek2o. I haven't checked yet, but I am curious to compared the release dates for the latest neek2o and the priiloader v0.7 neek mod. Assuming there's a big time difference here, maybe try an older version of neek2o to see if it's failing only because of being run on newer\incompatible versions of neek.

I feel like I had one more idea to try, I'll edit this post if I think of it. And if no one else is able to test before me, I will eventually get around to it, but it may take be a bit.

No neek/sneek/meek/bleek....Määäh...

 

[XFlak]

No neek/sneek/meek/bleek....Määäh...

Lol! I honestly don't know if this meant u would test or if you ain't touching neek with a 10 foot pole

 

[Alexander1970]

Lol! I honestly don't know if this meant u would test or if you ain't touching neek with a 10 foot pole

That Thing with the Pole.

One Day,when I have really,really,really nothing to do........maybe then I will try this neek/sneek/meek/bleek Thing.

 

[XFlak]

No worries dude, u already do so much.

Any chance anyone else is able to volunteer to help test this out?

 

[tofttwaswas]

crasy on how there is still support for this console

 

[totakeke95]

Wiimmfi has released a new patch version and I was wondering if you going to update Priiloader to make it work with it.

 

[XFlak]

I'm pretty sure a new hacks_hash file with wiimmfi v3 is being worked on by the wiimmfi guys, just be a bit patient

 

[DacoTaco]

I'm pretty sure a new hacks_hash file with wiimmfi v3 is being worked on by the wiimmfi guys, just be a bit patient

it is in the makes (or so i was told) and should be updated on github (on the release branch) as soon as they make the pull request.

a new version won't be necessary afaik and you would only need to replace the hacks file on the sd and save it

Its been merged : https://raw.githubusercontent.com/DacoTaco/priiloader/release/priiloader/hacks_hash.ini

 

[XFlak]

I heard the following in the rc24 group in discord, and was wondering if anyone knows if the priiloader hacks will need get adjusted again?

@everyone OK, some bad news - listen up

About the new Wiimmfi patcher - there is a bug that the Wiimmfi team found that is being fixed in all the patchers - the new patch broke worldwide matchmaking in some games.

For those games, another repatch is required. It is not quite ready yet, but we will tell you when it is.

We are very, very, sorry about this.

As I understand it this doesn't impact most games and I'm not sure if it even would affect the priiloader hack at all.

On another note,i just learned something about neek2o, if priiloader is present in the emunand, neek2o will detect it and will load the system menu instead. Since neek2o is able to apply all necessary patches it was thought that there is no reason to use priiloader... can we think of any good reasons now? Like autobooting or new system menu hacks (like the new wiimmfi patch for example)

So yeah, if there's a solid reason to have priiloader access in neek2o, overjoy may do us a favour and gift wrap it for us (so to speak). Otherwise anyone wanting to access priiloader on their emunand will need to use the original neek and not neek2o (edit: or an older version of neek2o)

 

[DacoTaco]

I heard the following in the rc24 group in discord, and was wondering if anyone knows if the priiloader hacks will need get adjusted again?

yes it does : https://github.com/DacoTaco/priiloader/pull/276

 

[XFlak]

@Etheboss, @OverjoY, @obcd, any of you dudes still around by any chance?

--------------------- MERGED ---------------------------


Also don't forget that I can't get even this v0.7 neek mod to load at the present time. So even if you replicate all the changes perfectly it may still not work... that being said, because I KNOW it was working once upon a time, the issue may be with something I did to break my personal setup (edit: like maybe updating neek itself? Discussed more below)

If anyone else is able to help test (I'm thinking of my favourite volunteer right now @alexander1970 lol) these are all things I was thinking to try:

1) do as Daco suggested and install priiloader v0.9, enable logging in priiloader, save, then make a nand backup, extract for use with neek and load it up as per usual. Try booting it via GX and traditional bootmii methods to see if it makes a difference (hold reset while booting neek to try and access neek priiloader). Pro testing tip: after making the nand backup, on your real nand move some system menu channels around and change priiloader's background color so that you can easily identify whether you're inside your real vs emulated nands. When done obv please share the logs and results here.

2) Download and see if you can get the Priiloader v0.7 neek mod to work. For this you probably want to boot UNEEK and save the installer to SD, and run it from inside uneek. Assuming it installs correctly, see if you can access it by holding reset when booting your emunand. Also try the priibooter app that comes with it.

3) similar to above, try manually injecting the neek mod of v0.7 priiloader.app. This is actually super easy because of modmii, just use ModMii's emulated nand modifier to inject it into your Emunand, and test again.

4) I wonder if perhaps this isn't working anymore because of updates to neek2o. I haven't checked yet, but I am curious to compare the release dates for the latest neek2o and the priiloader v0.7 neek mod. Assuming there's a big time difference here, maybe try an older version of neek2o to see if it's failing only because of being run on newer\incompatible versions of neek.

I feel like I had one more idea to try, I'll edit this post if I think of it. And if no one else is able to test before me, I will eventually get around to it, but it may take me a bit.

So I tested with an old version of neek2o (rev 64) and Priiloader v0.9 loads perfectly. Also, I recently spoke with someone close to the project and confirmed that newer versions of neek2o bypass Priiloader if detected on the EmuNAND. So the latest versions of neek2o today still bypass EmuPriiloader... well at least for now... *fingers crossed*

so at this point in time, if you want Priiloader access on your EmuNAND, you'll have to use an older version of neek2o, or the original version of neek

 

[john1578]

Thanks for your hard work!

 

[DacoTaco]

FYI : Priiloader 0.9.1 is released with the fixes that have been done since 0.9 + new hacks file (including the wiimmfi fixes, which btw doesnt need this release...)

 

[XFlak]

Thanks! There was just 1 thing I didn't get from the changelog: fixed loading dol/elf arguments from nand if there are none

First, how does one load arguments from nand? And if if there are no arguments, how can they be fixed?

Thanks for this release!

 

[DacoTaco]

Thanks! There was just 1 thing I didn't get from the changelog: fixed loading dol/elf arguments from nand if there are none

First, how does one load arguments from nand? And if if there are no arguments, how can they be fixed?

Thanks for this release!

when installing a binary from priiloader it also saves the arguments to nand. when loading it from nand it also loads the arguments back in.
however, the arguments file contains information besides arguments ( like where it booted from, if it needs ahbprot disabled or not etc ). that stuff did not get loaded properly when there were no additional parameters

 

[XFlak]

But where does it grab arguments from? Sd:/meta.xml? Last time I installed a binary priiloader could only see them on the device root, so that's why I'm assuming sd:/meta.xml, but if now priiloader can navigate other directories then I imagine it would be the meta.xml saved to the same directory as the binary. Are one of these assumptions correct?

 

[DacoTaco]

it loads them just like the homebrew channel does (same file, same location).
aka sd:/apps/[appname]/meta.xml. it loads that for application name, if ahbprot is needed & arguments. it saves the information to nand when installing the binary.

Priiloader was able to do this back in 0.8 btw (0.6 added loading from /apps/ as well and 0.8 added arguments)