Open GoogleCodeExporter opened 9 years ago
if you want to take the risk of running possible unstable code then please try
it with the beta i posted
http://code.google.com/p/priiloader/issues/detail?id=86#c13
there
Original comment by dac...@gmail.com
on 10 Oct 2010 at 10:00
Actually, I found a temporary solution. All you have to do is turn off Standby
for Wiiconnect24. You can still have WiiConnect24 on, but you just have to turn
off the Standby function. If this is done, then the Wii will stop outputting a
random color screen and shutdown like normal. Also, the Wii will instantly shut
off if you do this (instead of taking about 5 seconds like it used to).
Another thing I now remember was that before Priiloader was installed, the Wii
would output a black screen (not a random color) if you turned off your Wii
from the Homebrew Channel, so I don't really think this is only a problem with
Priiloader, but all homebrew in general. I'm thinking this has to do with the
way Wii homebrew is coded, and possibly DevKitPro.
Original comment by tflou...@gmail.com
on 10 Oct 2010 at 10:46
ye, and my beta doesn't shutdown like most applications :P (it actually shuts
down the video interface manually before shutting down)
Original comment by dac...@gmail.com
on 11 Oct 2010 at 5:20
have you tried the beta yet?
i really want to know the result >_<
Original comment by dac...@gmail.com
on 16 Oct 2010 at 9:35
I would try it out, but I don't (and can't) have Bootmii as boot2. If I did, I
would have tried this right away. I'm worried my Wii will brick if I install
unstable code.
If I was to do this and my Wii would brick, would I still be able to boot into
the recovery menu (to boot Super Smash Bros Brawl)? Also, I have an LU64 Wii
along with Darkcorp (Only for booting SSBB from the recovery menu if I need to)
and patched cIOS 222, 223, and 249.
Original comment by tflou...@gmail.com
on 17 Oct 2010 at 2:29
UPDATE: I thought I would give it a go, but I'm getting a little problem. Once
I open up the program, two white dots (they look like up arrows) are on the top
of my screen. After 4 seconds, I get taken back to the Homebrew Channel. This
is the same issue as DrewCU. It's also weird because we both have our video
settings set to 480p with 16:9 widescreen, but I don't have a Drivekey. I know
it's the program because I just tried it on 3 SD cards and none of them worked
out. I also changed my video settings and WiiConnect24 settings to see if that
is the issue, but I still get 2 white dots/arrows.
What is going on?
Original comment by tflou...@gmail.com
on 17 Oct 2010 at 3:02
ok, so the video issue happens more then i thought :P
check if it still installed or not(hold reset to boot priiloader). if it
didn't; i guess youll have to wait untill i fix that issue :')
Original comment by dac...@gmail.com
on 17 Oct 2010 at 8:35
It didn't install. I didn't even get the option to. Whenever I open it directly
from the Homebrew Channel, 2 white dots appear. No option to install, or any
indication to do anything. It just locks up for 4 seconds and then it returns
to the Homebrew Channel. I wonder if it's because I never installed 0.5 (it got
taken down before I had the chance.) I won't mind running 0.5 on my Wii (I have
internet on it) Can you send me it, or should I just wait?
Original comment by tflou...@gmail.com
on 17 Oct 2010 at 11:52
[deleted comment]
@tflouras : ...do you have cioscorp or darkcorp installed...?
Original comment by dac...@gmail.com
on 17 Oct 2010 at 12:36
@daco65 Yes, I have darkcorp. I only use it to boot Super Smash Bros. Brawl
through the recovery menu.
Original comment by tflou...@gmail.com
on 17 Oct 2010 at 1:18
hm, well
post a system log from dopmii & your wii settings in the new issue i created.
http://code.google.com/p/priiloader/issues/detail?id=141
Original comment by dac...@gmail.com
on 17 Oct 2010 at 2:09
sadly, i have no suggestion. its weird it still happens as priiloader shuts
down the video interface completely by hand :/
Original comment by dac...@gmail.com
on 17 Oct 2010 at 7:15
Well, there is something that did change. It isn't using a random color
anymore. It only outputs black. Still, it is an issue that maybe someone else
has a solution too. I'd suggest asking the creators of the Homebrew Channel
because they actually released an update (v1.0.1) that fixed what they call
"video after shutdown". You should ask them what they did to fix that bug or
look in the source (if they will provide one). It's probably fairly easy to fix.
Here's a link to the changelog (from wiibrew.org)
http://wiibrew.org/wiki/Homebrew_Channel#Changelog
Original comment by tflou...@gmail.com
on 17 Oct 2010 at 8:53
a shutdown from HBC does not give the issue? :/
Original comment by dac...@gmail.com
on 18 Oct 2010 at 4:55
That wasn't what I was trying to say. I'm saying that they fixed the issue in
1.0.1. However, it doesn't work because when you shut off the Wii, it goes
though the IOS priiloader uses (the first one, I think) and for some odd reason
turns the video on.
When I just had Homebrew Channel, it did do the same thing, but it got fixed.
Also, I'm guessing when you shut down the video interface, it probably wasn't
at the very end. Therefore, when it goes through the IOS, it doesn't find that
command and skips to turning off the Wii. Remember, this only happens when
WiiConnect24 is on. If I turn it off (or just the standby), it works and does
not output a black screen.
Original comment by tflou...@gmail.com
on 18 Oct 2010 at 11:35
cause without standby the wii fully shuts down. however, priiloader kills the
interface even before it shuts down the dvd drive (check that, if im correct
the dvd should still be spinning when you get those weird random colours )
i just wonder why on your wii its still outputting SOME video output while on
others it gives no output :/
Original comment by dac...@gmail.com
on 18 Oct 2010 at 2:39
Guess what? I just checked that and the DVD drive DOES stop. The only thing
that is different when WiiConnect24 is on is USB ports are powered and the
video output problem occurs. However, I have an idea. Can you edit the beta you
gave me so when it turns off, the Wii drive blinks a certain amount of times (5
would work well). This way, we can see if it's just not running the shutdown
code or another part of the code.
Also, I'm not sure that it matters, but I have an LU64 Wii (from March 2009).
Could that make things different?
Original comment by tflou...@gmail.com
on 18 Oct 2010 at 6:50
no it shouldn't make a difference . specially not since mine is from the same
time. sep/oct 2009.
also, if the weird colours appear AFTER the dvd drive is killed then its
stm/ios doign something weird :/
Original comment by dac...@gmail.com
on 18 Oct 2010 at 7:07
Well, I do have Darkcorp installed, so I guess that would make a difference.
Also, can you make a special version that makes the Wii drive blink at
shutdown? It would help us figure out if the code is working.
Original comment by tflou...@gmail.com
on 18 Oct 2010 at 7:18
I don't mean to bump this issue after 2 weeks, but I just uninstalled
priiloader and it appears that the random color screen issue disappeared. I
wonder if it's the IOS the system menu runs on? Would it be safe to reinstall
IOS80 and see if that fixes it?
Original comment by tflou...@gmail.com
on 31 Oct 2010 at 2:27
well that just proves something is pooped in the shutdown but i dont know what
ill check it out once my installer is working again >_>
Original comment by dac...@gmail.com
on 31 Oct 2010 at 2:49
No random color here but I see a black screen when wii is on standby mode :S.
I have last version of Priiloader 0.7, I though that was a cIOS problem but I
cleaned my wii but the problem still there :S
Original comment by pmagnu...@gmail.com
on 20 Jun 2011 at 7:04
I have a half green screen when i shut down mine however i am not too concerned
as long as its only cosmetic...
Original comment by deanmill...@comcast.net
on 28 Sep 2012 at 5:43
what are your settings(in priiloader and system menu) ? and is it always like
that? no matter from what app you shut down?
Original comment by dac...@gmail.com
on 28 Sep 2012 at 8:12
Original issue reported on code.google.com by
tflou...@gmail.com
on 25 Sep 2010 at 9:13