before i go and react, you should know im banned on gbafail and therefor can't 
read the topic at all (up yours gbafail. you can go to hell if you dont want my 
knowledge)

now, about the issue...
having the wii settings (video,shutdown mode etc etc) would be nice
the system menu version, and if the wii is region changed would also be nice.

Wii is 4.2U system menu and it has not been region changed.
Video is the standard SD video in the wii settings.
It set to full shutdown via wii settings (red light)
Wii connect 24 and standby are both turned off.

If there is anything else i can try let me know.
I have another wii im going to update priiloader on later today and im going to
see if the same thing happens to it.

"standard" isn't as standard as you think :P

is this a US or EU wii?

this is a US wii

I will only have this wii for a short time longer so if theres anything you 
needed tested let me know as soon as possible.

Just tried this on my other wii as well that has been updated to 4.3 through 
nintendo and the same thing is happening with it.Although on the 2nd attempt it 
worked fine but trying to just load the priiloader app and letting it sit makes 
it go to the garbled screen.

I have this same issue too. The instructions appeared and 2 seconds later the 
text turns garbled, i needed to restart the wii on power button. I can 
installed the Priiloader but i must be very fast befor the 2 seconds.

My Wii never bricked whit this issue.

May Wii:
4.1E

I've had the issue on two out of three wiis i have tried it on.

wii #1 4.2U - had priiloader latest beta then i upgraded to the latest release 
without any issues.I have uninstalled and reinstalled again priiloader over and 
over on this wii and not had a single issue at all.

wii #2 4.2U - never had priiloader on it until trying the latest release.first 
try was a brick and then after two more tries it finally installed but still 
turned to the garbled text.

wii #3 4.3U - Had previous beta release and updated to latest release.Worked 
fine the first time but everytime i load priiloader app after that it gets the 
garbled text.

On the wiis that are messing up it happens just by loading the priiloader app 
through HBC and letting it sit on its main screen.After a few seconds it turns 
to garbled text.

I also tried reformatting my sd card and that did not change anything and i 
also tried a different brand and size sd card and that did not change anything.

There has got to be some setting in the wii somewhere that's causing this issue.

I have access to wii #1 and #3 anytime so i can test out anything that you 
think might help.

[deleted comment]

priiloader app = the installer i guess?

also, compare the wii settings, look for differences

and next time you have the text, press reset first and wait a minute , and if 
HBC comes up REINSTALL SYSTEM MENU JUST TO BE SURE and tell me if that worked.

The Priiloader app I'm talking about is the installer.

I will compare settings and post them here.
* I know for sure the wiis that had problems did not have any internet or wii 
connect 24 settings setup at all and the wii that works perfect does.I will 
play around with it someone and see what happens,but it might be this weekend 
until i get a good chance to do everything.

I will also try the reset once it comes up garbled but i believe i tried it 
before and it did nothing.It seems if i hurry up and press the + or _ to 
install/uninstall that it sometimes beats the garbled text but not always or in 
the middle of the install while its telling me if moved system menu ext.. it 
goes to the garbled text.

im pretty sure the reset should work if you wait min or so. if it doesn't 
something is really really REALLY fucked :-/
but i wonder why alot of wii's are fine...

You wanting me to do the reset after an install fails? or after just letting 
the priiloader installer sit there until it messes up.

Also when the priiloader installer boots up and it says "please wait init"

What exactly is it initializing ?

can't tell what its initializing :-P
not untill i release my source
its nothing that should cause this depending on what ios is installed in 
slot58...


also, i mean that when the garbled text does come up just press reset once and 
wait half a minute (should be enough if HBC would boot... :/ )

I can confirm 1 bricked wii from this issue, from a person following my guide 
on wiihacks. Same thing happened to him, garbled screen, reboot to bricked wii.

ye, thats why i wanna see if pressing reset and waiting for HBC will do.

also, comments about bricked wii's are not wanted. im seriously thinking about 
the issue and if you just wanna nag about a bricked wii then gtfo (also, the 
installer is run on the users own risk. any damage done isn't my fault directly 
:) )

I try press reset once after garbled text, and wait 1/2 minutes. Appears one 
more garble text line. After that freeze and nothing happened.

I am not trying to nag, just confirming the issue. Take a breath, you do 
excellent work and it is appreciated more than you'll ever know.

Did some testing.

Pressing reset after garbled text does absolutely nothing.

I did however find the cause of the issue i think.

The wii that i have that works perfect has the internet configured through the 
wii settings menu.

The wii that i have that has the problems does not have the internet configured 
through the wii settings menu.

I played around with both and when i deleted the internet settings from the 
working wii then the priiloader installer would crash everytime.

The opposite worked the same

Everytime i added the internet settings back into the wii the priiloader 
install worked fine everytime.

I tried this multiple times on BOTH wiis and it crashed every time there was no 
internet settings configured into the settings menu and worked every time the 
settings where there.


PLEASE SOMEONE ELSE CONFIRM THIS.

what type settings you added. I try to add wired connecting and priiloader 
install fail again. 

I update Priiloader from v.4 to v.5 today trough hbc 1.0.8 and in the end of 
install the text become all garbled too. After a few minutes without anything 
happened, turned off the wii pressing power button (reset didn´t work). 
Apparently everything is ok, the wii is normal and Priiloader was updated :)
What I notice is the apps that use ios58 crash or freeze when launched from hbc:
fceugx 3.2.2 
snes9xgx 4.2.4 
wiimc channel installer 1.4
wiimc 1.0.7
priiloader intaller v.5

My wii is 4.1U, ios58 v6175 (downloaded with Nusd and installed using wad 
manager 1.7 and ios249 rev19) without internet configured (can´t test with 
internet - sorry).

I used wireless internet connection on both wiis.

Like i said earlier every time i added it the installer worked fine.

When internet settings were removed the installer crashed.

Also forgot to mention

When i had no internet configured and the installer always crashed.

Sometimes it crashed within a few seconds other times it was a good 20-30 
seconds of just letting it sit on the main installer screen with the 
instructions until it crashed.

Sometimes it crashed during install process
Sometimes it crashed during uninstall process
Sometimes it crashed while exiting the installer

thats...interresting yet very irritating as it has no direct relation to the 
issue afaik :/

(now to find some1 with bootmii as boot2 on irc to let me try and run a few 
installers :P )

I have bootmii as boot2 on both wiis.

I have no time though to come on irc but if you wanted to email me the 
installers or something i would be fine with that.


If you do email them to me do you want me to run them with no internet 
configured i assume?

here is a zip with a few test installers.
please test these on the wii that doesn't have internet settings (so the bug 
happens)
try and do the following tests:
- Install (from a fresh system menu install trough wad or dopmii)
- Uninstall
- Update
also, for anyone who else who wishes to run the test : DO NO RUN THIS INSTALLER 
WITHOUT ANY WAY OF RECOVERY LIKE BOOTMII AS BOOT2 OR AN INFECTUS CHIP!! IF YOU 
GET A BRICK WITHOUT ANY RECOVERY ITS NOT MY FAULT!

god damnit, the ios patching addresses are fine too.
what the hell is happening :-/

[deleted comment]

i am now able to reproduce the issue but its fucking with me...hard
ive given the code to wintermute in hope he can figure it out cause its WAY 
above my head :-/

ive also deleted 0.5 from the google code page & my server (so the download 
link from wiibrew is dead).

Since your now able to reproduce the problem i take it you no longer need me to 
test the boot.dol you gave me on irc right?

For now im not even going to bother with it unless you still want me to.

If you do just post here saying so.

Just to clarify for those following this thread... If you successfully 
installed v0.5, are you still at risk for a brick from this issue later or is 
this only an issue with the install/uninstall app? Also, if we attempt to 
uninstall from priiloader, should we use another method to ensure we don't 
brick? Thanks...

if you got 0.5 installed then you are fine.
its just the installer itself that is being an ass.

jayshomecamera, if you want to uninstall priiloader just reinstall your system 
menu with dop-mii

just a heads up
http://bugs.hackmii.com/index.php?do=details&task_id=376&project=6

its a VERY specific thing
things needed for it to crash
- AHBPROT set trough wiiload or meta.xml
- IOS58 in use by HBC
- all internet settings in system menu are cleared

lukegb & i have been running a few tests for dhewg but they didn't look good >_<

IOS58 specific bug? if it is, this is a very step back...

So does this mean it is a HBC bug, and can cause problems for anyone using 
AHBPROT (HBC no-IOS-reload)?
Is there any other method of loading the boot.dol with IOS58 and AHBPROT (I 
suppose there is no point testing anyhow, as it is not Priiloader)?
Hope to see a fix soon.

yes we (lukegb and i) fear it is infact a HBC bug.

cause just my bug report says, even a small program like the one i posted 
(which just inits video and goes into a loop) crashes after a while.

and it might not be 58 specific; but lukegb was first using IOS31 and he didn't 
have the crash...

daco you may release the version 0.5 without AHBPROT (using IOS36 as always), 
while the bug is fixed, because it does work fine. just a suggestion :)

ive been thinking of that, but i wont for now.

if ppl really want they can just download the 0.5 from any other site, and 
remove the <no_ios_reload\> tag so that it'll loose the AHBPROT rights and give 
the option to use 36 instead

[deleted comment]

I saw this part "IOS58 in use by HBC" and was wondering if someone loaded the 
installer using wiixplorer would they get the same failed installer. If I had 
Bootmii in Boot2 I would test but I have no way to recover if I brick so I will 
leave it alone.

About the GBAturd stuff are you looking for another site?

I know I'm coming into this topic late, but I had the same problem when I went 
to install 0.5 the day it was released. It eventually bricked my Wii when I 
tried to hit +/A to install before the garbled text hit, because it froze right 
after. Fortunately I have BootMii in Boot2 so no harm was done. I also have my 
Wireless Disabled as others have mentioned.

I eventually got it installed by holding B or whatever button forces the CIOS 
to do the installation (I don't remember now). 

I downloaded the new ios58(6176) tried the installer.
As before works with internet set.
Deleted settings, garbled screen. (it does actually install, but then gives 
garbled screen and you have to power off. Powering on again priiloader is there.

So no change with new version.

ha, thx for that

i wanted to try it myself right now but seems like i dont need to :P

http://www.dacotaco.com/about-the-priiloader-0-5-removal

that should tell everything there is to this bug.
its waiting for an update now

@daco65: I gess you should report the HBC bug as "severe" in HBC bugtracker, as 
priiloader is the only anti-brick solution that recent wii can use (when 
bootmii can not be installed as boot2).
Mabe this will speedup the resolution of this bug (and if it is exactly what 
you are thinking about, it should be really simple to solve).

thx

there can be no more of a speedup as there already is

they know about it
they know the source
they know the circumstances it happens in
they know how to fix it (i think. as my blog post says we suggest its the async 
network init but we aren't sure)

also, i looked at how to change the bug's stats after reporting but i can't :)

It seems that when you run the HBC through BootMii (-IOS in my case) the 
AHBPROT works fine, no problems on cIOS 236, Dop-Mii or Priiloader (ONLY 
through BootMii).

as i just said on teh official issue report of hbc, dhewg asked me to try the 
same; however it still happend for me

[deleted comment]

I tried it 3 times each (cIOS 236, Dop-Mii & Priiloader 0.5 install) already, 
and it all seemed to work fine when launched via BootMii and crashed when not, 
can't figure out why it doesn't work for some people, i sure hope the do fix it 
fast.

Had garbled text when installing with 4.3e. Downgraded to 4.1 and installed 
first time with no problems

im not so sure where you got 0.5 or how ignorant the site is that provided you 
with a 0.5 download; but consider yourself lucky...

well i full bricked a wii when installing priiloader 0.5, i had a black wii 
4.2USwith HBC 1.0.8 IOS58 v6176, the first time i tried priiloader freezed with 
garbled text i just restarted the wii ad everything was ok so decided to try 
again... the 2nd time it freezed in checking the TMD.. and the wii wouldnt 
start anymore, black screen... 

corrupted system menu TMD

same thing as i said above : 

"im not so sure where you got 0.5 or how ignorant the site is that provided you 
with a 0.5 download; but consider yourself lucky..."

cause seriously, why haven't ALL sites deleted 0.5 yet eventho i wrote a bloody 
blog post about it?

both the reason why 0.5 crashed, and why the text was garbled is now fixed :)