Priiloader Installed, System Menu fail

Discussion in 'Wii - Hacking' started by TRIGRHAPPY, Nov 28, 2009.

Nov 28, 2009
  1. TRIGRHAPPY
    OP

    Newcomer TRIGRHAPPY Member

    Joined:
    Nov 28, 2009
    Messages:
    10
    Country:
    United States
    I started with a 4.0 Virgin Wii two days ago. I read all the how-tos, even the irrelevant ones that just provided a history of certain things. I installed Preloader .29, Bootmii, HBC, cIOS249 and I used dop-ios to patch any relevant IOSs I may need patched. I backed up my nand with Bootmii and stored it on my computer's hard drive for safe keeping.

    It's been working fine.

    Tonight I decided to update to 4.2 (with the safe one). That worked fine, I retained my HBC and all that good stuff....but it of course does away with Preloader. The install itself went flawlessly. Now I wanted to re-install Priiloader for safety reasons. I had been using Preloader .29 since that's what the tutorial specified, but since 4.2 did away with it anyway, I decided to use the opportunity to install Priiloader (rev 15 if I recall) instead. I placed the updated hacks.ini in the SD root directory, put Priiloader in my apps folder, ran priiloader install via HBC and installed. Then I restarted the Wii....

    To my surprise, it ran Bootmii (instead of the main priiloader screen)
    No biggie I figured, so I restarted again (while holding reset).
    It started up Priiloader. The autoboot was on bootmii, so I switched it to System Menu, and switched return to priiloader.

    Now when I start it up (without holding reset of course) it does nothing. It just goes to a black screen with "4.2(USA)" at the bottom right. I checked that priiloader was using the right IOS for 4.2, which it was. I then booted into HBC and ran DOP-IOS and reinstalled+patched IOS70. Then I restarted...

    Still no dice. Same black screen with 4.2(USA).

    Like I said, I still have Bootmii......and a backed up NAND......access to HBC (with dop-ios and any other useful homebrew).

    Just wondering if there is any easy fix so I don't lose all my work from since I backed up my nand.... I'd sure appreciate it!
     
  2. TRIGRHAPPY
    OP

    Newcomer TRIGRHAPPY Member

    Joined:
    Nov 28, 2009
    Messages:
    10
    Country:
    United States
    QUICK UPDATE:

    I believe this is a bug with Priiloader .1 v15. Don't take my word as gospel though, since I've had a Wii for all of 3 days now.

    The issue is that in Priiloader, some of the "System Menu Hacks" were enabled by default. One of these hacks is "FORCED STANDARD RECOVERY MODE".

    If this is enabled, it will not boot to the system menu (only the black screen with 4.2(USA) )
    If this is disabled, it boots perfectly.

    So now I have zero issues at all. Credit for the fix goes to icpmattj

    My humble advice to the creators of Priiloader would be to ensure this option is disabled by default.

    Also, I believe the least I owe to everyone is an honest "Thank You" to everyone on these forums for creating the VERY detailed guides which have kept me from bricking my Wii. It is extremely obvious that all guides here are created with safety in mind, which I greatly appreciate! Also, thank you to the software developers who have made many of the programs that I'm sure we all enjoy.

    Lastly...... If someone bricks their Wii (me included), nobody is to blame but themselves. I'm new to Wiis but I've been modding consoles for many years........the very act of deciding to "mod" your console places all responsibility after that on you. I've bricked a few consoles (the first Xbox I ever tried to mod still sits in my closet....bricked). Big gob of solder across a small (but important) corner of the mobo. Contrary to what the guides and How-To's may say.....the first step to modding a console is accepting responsibility for bricking it!
     

Share This Page