Priiloader v.5 causes garbled text during install/uninstall

[GoogleCodeExporter]

using the lastest priiloader from the download page( I am using the xml with it 
as well before anyone asks and i also have the latest ios58 installed)

When trying to install or uninstall priiloader the whole screen turns to 
garbled text and the wii freezes and has to be shut off from the power button 
on the consoles.It even does this when just letting priiloader sit at its main 
screen where it gives the instructions on how to use the app.

The first time it happened it bricked the wii.
I reinstalled the system menu via wad manager and then tried the priiloader 
install again.Same thing happened this time except when i turned the wii back 
on after it froze it was not bricked.I turned the wii off again and then back 
on while holding the reset button.This time the priiloader install worked.

I thought it might be my sd card so i reformatted it and tried it again and 
still had all the same issues.

I then used the same sd card on a different wii and uninstalled priiloader from 
it and then reinstalled it again without a single issue.

Something else is causing this maybe something on the wii itself.
If there is anymore testing i can do to help try to figure the cause of this i 
would be glad to help.After today i will not have access to the wii that had 
problems with the priiloader install as my friend will be picking it up but i 
still have access to at least 2 other wiis at all times to try anything out on.

I'm not the only one with this issue check out the following thread and you 
will see its happened to at least 1 other person.

http://gbatemp.net/t251061-priiloader-messed-up-wii-please-help

Original issue reported on code.google.com by icpma...@gmail.com on 1 Sep 2010 at 2:45

[GoogleCodeExporter]

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.

Original comment by dac...@gmail.com on 1 Sep 2010 at 5:13

[GoogleCodeExporter]

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.

Original comment by icpma...@gmail.com on 1 Sep 2010 at 10:09

[GoogleCodeExporter]

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

is this a US or EU wii?

Original comment by dac...@gmail.com on 1 Sep 2010 at 2:37

[GoogleCodeExporter]

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.

Original comment by icpma...@gmail.com on 1 Sep 2010 at 8:57

[GoogleCodeExporter]

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.

Original comment by icpma...@gmail.com on 1 Sep 2010 at 10:13

[GoogleCodeExporter]

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

Original comment by serial.k...@netvisao.pt on 1 Sep 2010 at 10:48

[GoogleCodeExporter]

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.

Original comment by icpma...@gmail.com on 2 Sep 2010 at 12:07

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

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.

Original comment by dac...@gmail.com on 2 Sep 2010 at 5:49

[GoogleCodeExporter]

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.

Original comment by icpma...@gmail.com on 2 Sep 2010 at 10:01

[GoogleCodeExporter]

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...

Original comment by dac...@gmail.com on 2 Sep 2010 at 2:23

[GoogleCodeExporter]

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 ?

Original comment by icpma...@gmail.com on 2 Sep 2010 at 7:57

[GoogleCodeExporter]

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... :/ )

Original comment by dac...@gmail.com on 2 Sep 2010 at 8:18

[GoogleCodeExporter]

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.

Original comment by mauif...@gmail.com on 2 Sep 2010 at 8:23

[GoogleCodeExporter]

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 
:) )

Original comment by dac...@gmail.com on 2 Sep 2010 at 8:27

[GoogleCodeExporter]

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.

Original comment by serial.k...@netvisao.pt on 2 Sep 2010 at 8:43

[GoogleCodeExporter]

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.

Original comment by mauif...@gmail.com on 2 Sep 2010 at 8:46

[GoogleCodeExporter]

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.

Original comment by icpma...@gmail.com on 2 Sep 2010 at 9:15

[GoogleCodeExporter]

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

Original comment by serial.k...@netvisao.pt on 2 Sep 2010 at 9:37

[GoogleCodeExporter]

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).

Original comment by aksuenag...@gmail.com on 2 Sep 2010 at 10:06

[GoogleCodeExporter]

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.

Original comment by icpma...@gmail.com on 2 Sep 2010 at 10:46

[GoogleCodeExporter]

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

Original comment by icpma...@gmail.com on 2 Sep 2010 at 10:52

[GoogleCodeExporter]

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 )

Original comment by dac...@gmail.com on 3 Sep 2010 at 5:22

[GoogleCodeExporter]

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?

Original comment by icpma...@gmail.com on 3 Sep 2010 at 10:04

[GoogleCodeExporter]

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!

Original comment by dac...@gmail.com on 4 Sep 2010 at 8:15

Attachments:

• tests.zip

[GoogleCodeExporter]

Will try these out later today and hopefully post the results later tonight

Original comment by icpma...@gmail.com on 4 Sep 2010 at 1:38

[GoogleCodeExporter]

I was able to get to this sooner then i thought.

Only tested this on one wii.
If you absolutely need it tested on the other i can just let me know.

Here are my results.

4.3U wii updated through Nintendo via wifi
ios 36 has been patched using the latest MMM to do it.

Test #1 using boot1.dol from tests.zip

Installed a clean system menu wad via wad manager 1.7 
*system menu wad was downloaded from NUSD*

Priiloader installer says ios58 rev 6175 at the top.

When pressing + to install priiloader i get the following message.

ES_Identify failed error -1017(-ox3f9)ios58 not patched with ES_diverfy?
Using ios36(Holding B then pressing + or - )will probably solve this.
NOTE:you need a patched ios36
Do you with to continue the installation(or attempt to install?)
A=YES B=NO HOME/START=EXIT

I pushed the B button to exit priiloader installer and then restarted it again.
This time i held down B while pressing + to install priiloader.

THE INSTALL PROCESS WORKED PERFECTLY.NEVER HAD GARBLED TEXT.

I then tried uninstalling priiloader.The same thing as above happened when just 
pressing the - to uninstall so i had to restart the installer and hold B button 
down while pressing - and the uninstall worked fine.

TEST #2
 using boot2.dol from tests.zip

Same IOS 58 and 36 as used in test #1

I also reinstalled the system menu wad again before doing test #2

Not going to type everything out again but the results were IDENTICAL AS TEST #1

SIDE NOTE: WHEN I USED THE OFFICIAL .5 RELEASE INSTALLER I NEVER GOT THE MESSAGE
ABOUT IOS58 NOT BEING PATCHED AND IT INSTALLED FINE WITHOUT HAVING TO HOLD DOWN 
THE B BUTTON.IT DID HOWEVER PRODUCE THE GARBLED TEXT PROBLEM BUT IF I WAS QUICK 
ENOUGH TO PRESS + TO INSTALL IT SOMETIMES IT MADE IT THROUGH AND INSTALLED 
PRIILOADER AND OTHER TIMES IT CAUSED A BRICK.

If there is anything else i can do just let me know.I have access to  two wiis 
anytime and both have bootmii as boot2 so there issues with me trying anything.

Original comment by icpma...@gmail.com on 4 Sep 2010 at 2:56

[GoogleCodeExporter]

grmz, one issue fixed and another resolved...

so neither tests result in a garbled text but the nand permissions was failed 
to patch >_> (hence the option to reload to 36...)

i wonder why its failing to patch while working on mine... >_<;

Original comment by dac...@gmail.com on 4 Sep 2010 at 4:52

[GoogleCodeExporter]

Neither test had garbled text.

I know there is two different versions of ios58.

Was yours the same as mine?

If you need anything else tested just post it here as i check it daily now.

Original comment by icpma...@gmail.com on 4 Sep 2010 at 7:41

[GoogleCodeExporter]

just a question, how did you load the dol? if you loaded it from SD; did you 
use the Priiloader 0.5 meta.xml ? cause its very important that the installer 
has access to the memory...

Original comment by dac...@gmail.com on 4 Sep 2010 at 7:54

[GoogleCodeExporter]

Very good question and no i didnt use the meta.xml

I just copied each test dol to its own folder and ran it from a sd card.

Will try again with the meta.xml from the .5 installer and post back with 
results.

Original comment by icpma...@gmail.com on 4 Sep 2010 at 9:27

[GoogleCodeExporter]

When i added the meta.xml back to the folder with the test dols i get the same 
results as the .5 installer did

garbled text on just letting it sit there,installing or uninstalling it.

happened on both test dols

First test dol installed fine the very first time with no garbled text but then 
i went back into the installer to uninstaller and when i did this i got the 
garbled text again.

Original comment by icpma...@gmail.com on 4 Sep 2010 at 9:35

[GoogleCodeExporter]

ok, good (actually not good but ok)

the question remains why when patching ios it happens and when not patching ios 
it doesn't... hmm

Original comment by dac...@gmail.com on 5 Sep 2010 at 6:36

• Changed state: Accepted

[GoogleCodeExporter]

these are a few tests in 1 zip
these tests output some gecko output to the screen and added some 
information/disabled some code.
the zip contains 2 dol's. one is compressed and the other isn't (its so we can 
test if its the compression that makes it fail which is doubtfull but an 
option). please try the compressed on first and if it fails try the bigger, 
uncompressed, boot2.dol

if the garbled text (which is probably a dsi exepection i think) comes up after 
a while then you should have enough time to read the following i hope :/

what i'd like are the address of the patches , the result of the nand test and 
how many patches it applies (this should be 3)

if this test does work flawlessly ill upload a debug information free installer 
for testing :)

Original comment by dac...@gmail.com on 5 Sep 2010 at 9:14

Attachments:

• tests.zip

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Tested the original 0.5 with wireless enabled - fine.
Removed Priiloader.
Tested the original 0.5 with wireless disabled - crash.
Tested both boot.dol and boot2.dol from tests.zip - both crash with output:

start looking for the function(s)...
Found ES_Identify check @ 0x939F0E70, patching...
Found NAND Permission check @ 0x93A11304, patching...
Found Hash check2 @ 0x93A75624, patching...
testing permissions...and bingo was his name-O

Press (+/A) to .........
Enjoy! DacoTaco, _Dax_ & BadUncle

3 patches applied

The crash happens soon after. Don't need to press any buttons to cause the 
crash. It happens on its own. (Tried it a couple of times - On one test I had 
to press a button before it crashed.)

I enabled the wireless and tested all again. Works fine with wireless enabled.
IOS 58 v6175

Original comment by mevans@westnet.com.au on 5 Sep 2010 at 10:28

[GoogleCodeExporter]

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

Original comment by dac...@gmail.com on 5 Sep 2010 at 10:48

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

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).

Original comment by dac...@gmail.com on 5 Sep 2010 at 6:35

[GoogleCodeExporter]

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.

Original comment by icpma...@gmail.com on 6 Sep 2010 at 3:03

[GoogleCodeExporter]

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...

Original comment by jayshome...@gmail.com on 6 Sep 2010 at 4:12

[GoogleCodeExporter]

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

Original comment by dac...@gmail.com on 6 Sep 2010 at 5:00

[GoogleCodeExporter]

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

Original comment by Kevin.Raptor@gmail.com on 6 Sep 2010 at 9:16

[GoogleCodeExporter]

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 >_<

Original comment by dac...@gmail.com on 6 Sep 2010 at 8:38

[GoogleCodeExporter]

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

Original comment by Kevin.Raptor@gmail.com on 6 Sep 2010 at 8:57

[GoogleCodeExporter]

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.

Original comment by mevans@westnet.com.au on 7 Sep 2010 at 12:02

[GoogleCodeExporter]

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...

Original comment by dac...@gmail.com on 7 Sep 2010 at 5:08

[GoogleCodeExporter]

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 :)

Original comment by Kevin.Raptor@gmail.com on 7 Sep 2010 at 12:40

[GoogleCodeExporter]

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

Original comment by dac...@gmail.com on 7 Sep 2010 at 2:30