1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

GUIDE: HOW TO INSTALL PRIILOADER ON FWs 4.1 & 4.2 + AUTO-BOOT TO YOUR FAVE USB LOADER

Discussion in 'Nintendo Wii / Wii U' started by pryme_H, Jan 12, 2010.

  1. pryme_H

    pryme_H Regular member

    Joined:
    Mar 13, 2006
    Messages:
    1,715
    Likes Received:
    0
    Trophy Points:
    46
    [​IMG]
    Priiloader is a modified version of the officially discontinued Preloader. For most people that are unable to install BootMii as boot2, you need a way to launch HBC to get to Bootmii. This makes Priiloader a must-have.

    VERY IMPORTANT PRE-REQUISITES:

    1. It is recommended to create a NAND backup if you can.

    2. If you are on firmware 4.0 or 4.1 and want to play Wiiware or Virtual Console off the SD card, you need to install patched IOS60 first. Consequently, for firmware 4.2, install patched IOS70, first and foremost. In simple terms, patched IOS70 and IOS60 are official Nintendo IOSes that are patched with the ES_identify. By doing this, you can negate a partial brick. However, both are not required for the proper installation of Priiloader.

    ADVANTAGES OF PRIILOADER:

    1. Brick protection that are non-IOS or NAND corruption related

    2. Install an auto-boot plug-in that can place itself before the System Menu

    3. Link to Bootmii IOS

    4. Installation of System Menu hacks

    REQUIREMENTS:

    1. System Menus 4.1 & 4.2

    2. SD card formatted to FAT is more desirable. However, an SDHC formatted to FAT32 will also work.

    3. Soft-modded Wii with at least the Homebrew Channel installed

    DOWNLOAD LINKS:

    Priiloader Hacks

    Priiloader 0.3b (latest release)

    Changelog:
    * Change and fixed IOS Stub detection. All known IOS' are detected like they should. thank you Attila
    * Changed Autoboot setting so it would start system menu when having just updated/installed Priiloader
    * Fixed Hacks.ini bug when it was made in linux (or any ini that doesn't have windows' \r\n newlines and uses \n instead)
    * Fixed Bootstate handling. we should now handle all known bootstates correctly("invalid" bootstate 255 included). all unknown bootstates load priiloader instead
    * Fixed Bug with USB drives that could crash System menu
    * Fixed the Wii Blue Light on wiimail issue (when standby, forgot to merge the light init code from phpgeek)
    * Fixed Background issues when changing colour and not saving settings
    * Fixed various video related bugs ( out of screen text, text on top of the other, ... )
    * Fixed some ES_Identify Bugs (in a hacky way) when not using system menu IOS for system menu
    * Reload Hacks completly when LoadHacks() is called and hacks were already loaded once
    * Added the checksum function from priiloader to the installer. if the checksum fails it asks the user what to do. it checks when:

    * Copying (installation of priiloader) the System menu app
    * Restoring (uninstall of priiloader) the System menu app
    * after Writing the Priiloader app (the checking installation part)

    * Added basic HBC Stub Loading. if priiloader (or a dol loaded by priiloader) crashes you can press reset to load HBC
    * Added possibility to boot System Menu if no wiimote is detected. after 15 seconds priiloader booted press reset to boot system menu
    * Added a check when loading/installing binaries to see if the SD/USB is still present or not


    INSTALLATION GUIDE:

    1.Download the Priiloader installer that's contained in the ZIP
    archive. Create a new folder (name it whatever you like) in the
    apps folder on your SD card. Put the boot.dol file in
    that folder.

    2. Next, download the hacks.ini file corresponding to your firmware. You will need to
    rename the file to hacks.ini. Place the file on the root of
    your SD card.

    3. Load Priiloader via the Homebrew Channel. You will be
    presented with the disclaimer. Press (+) on the Wiimote to
    install Priiloader.

    [​IMG]

    It'll bring you back to the Homebrew Channel once installation finishes.

    [​IMG]

    To validate that Priiloader has installed successfully, press and hold the Reset button on the Wii. Priiloader should load.

    At this time, you can now enable some System Menu hacks. Always save your settings after enabling/disabling System Menu hacks.

    Descriptions of each hack are explained here.

    [​IMG]


    ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

    HOW TO INSTALL A FILE TO AUTO-BOOT

    1. First off, what you need to do is to acquire whatever DOL file you want for auto-booting e.g. USB Loader Gx, USB Loader, CFG, uLoader et al. You DO NOT need to rename the DOL file. However, for easy identification you can affix the appropriate name. For example, boot.dol file for USB Loader Gx can be renamed to USB Loader Gx.dol.

    2. Next, put the DOL file on the root of the SD card.

    3. Now, run Priiloader again by holding the Reset button.

    4. With the Wiimote scroll down to Load/Install option.
    Press A. You should see the DOL file in there. Make sure it is selected, then press A once more. The file should install in a few seconds. Press B to return to Main Menu.

    5. Finally, go to Settings. Change Autoboot to File. Subsequently, change Return to: to Priiloader or System Menu. The choice is yours. Make sure you save these settings. Restart the Wii to ensure the applied changes took effect.
    Last edited: Feb 18, 2010
  2. AfterDawn

    AfterDawn Advertisement

  3. larrylje

    larrylje Active member

    Joined:
    Jan 4, 2005
    Messages:
    12,506
    Likes Received:
    0
    Trophy Points:
    96
    Nice guide.

    Will defiantly help the community.
  4. pryme_H

    pryme_H Regular member

    Joined:
    Mar 13, 2006
    Messages:
    1,715
    Likes Received:
    0
    Trophy Points:
    46
    Thanks larry for the kudos. It sure means a lot coming from you.
  5. keypox

    keypox Regular member

    Joined:
    Apr 25, 2007
    Messages:
    112
    Likes Received:
    0
    Trophy Points:
    26
    thanks followed this and your 4.2 softmod guide. Both worked great.

    Now what should i preload?
  6. matrixebi

    matrixebi Member

    Joined:
    Dec 24, 2009
    Messages:
    75
    Likes Received:
    0
    Trophy Points:
    16
    Thank you for the guide but just had a few questions.

    I softmodded my new wii 4.2U and had to install Bootmii as IOS and did a NAND backup so hence the reason why I want to install Priiloader because I can apparently restore my NAND with Priiloader if anything goes wrong with with booting my wii.

    Now to the questions:
    "patched IOS70 and IOS60 are official Nintendo IOSes that are patched with the ES_identify

    1) How do I patch IOS70 and IOS60?

    2) if something was to happen to my wii, how do I load Priiloader and do the NAND restore?

    Thank you
  7. pryme_H

    pryme_H Regular member

    Joined:
    Mar 13, 2006
    Messages:
    1,715
    Likes Received:
    0
    Trophy Points:
    46
    I've provided the download links to both patched IOS70 and IOS60. So, go back to the beginning of the guide. With you being in firmware 4.2, you only need IOS70. Install it via WAD Manager. To answer your second question, you pressed and hold the Reset button on the Wii. This will load Priiloader. From there, you can load Bootmii IOS and restore your system.
  8. pryme_H

    pryme_H Regular member

    Joined:
    Mar 13, 2006
    Messages:
    1,715
    Likes Received:
    0
    Trophy Points:
    46
    What do you mean by this exactly?
  9. larrylje

    larrylje Active member

    Joined:
    Jan 4, 2005
    Messages:
    12,506
    Likes Received:
    0
    Trophy Points:
    96
    If your coming from my softmod guide to do pryme_H guide you shouldn't even need to patch IOS60 or IOS70. If you followed the softmod guide properly it would already be patched.

    Also as pryme_H said IOS60 and IOS70 needs to be patched so VC/WiiWare games can play from SD Card. This is not a requirement to install Priiloader.

    If you do install Priiloader and for some reason don't have IOS60 or IOS70 patched then you can patch them. This however will give you a "FILES ARE CORRUPT ERROR". To fix this issue you will need to load Priiloader and then use HBC to reinstall Priiloader again.

    It is Important to remember what pryme_H said 4.0 and 4.1 only needs IOS60 Patched and 4.2 only needs IOS70 patched.
    Last edited: Jan 21, 2010
  10. matrixebi

    matrixebi Member

    Joined:
    Dec 24, 2009
    Messages:
    75
    Likes Received:
    0
    Trophy Points:
    16
    Ok, thanks, I have the IOS70 patched already from Larry's guide but when you say I can load "Bootmii IOS and restore your system" is that the 'Recover' option in your picture above saying to use the GC controller and it will get me into BootMii?
  11. pryme_H

    pryme_H Regular member

    Joined:
    Mar 13, 2006
    Messages:
    1,715
    Likes Received:
    0
    Trophy Points:
    46
    Yes. If you haven't already noticed there is an option Bootmii IOS. If you select this it'll take you to RestoreMii. To perform a restore you will need a GC controller.
  12. matrixebi

    matrixebi Member

    Joined:
    Dec 24, 2009
    Messages:
    75
    Likes Received:
    0
    Trophy Points:
    16
    Ok, I'll try to install it. I don't see Bootmii IOS in your pic above so I guess I have to "enable" the Recover options then do a reboot again holding the reset button to get back to Priiloader then I should see Bootmii IOS on the main screen or maybe I'll see it after setting the Recover options to enable then press right on the GC controller.
    Thank you
  13. pryme_H

    pryme_H Regular member

    Joined:
    Mar 13, 2006
    Messages:
    1,715
    Likes Received:
    0
    Trophy Points:
    46
    The screenshot for Bootmii IOS on Priiloader's main screen is not on this guide. You will see it once you get Priiloader installed. It'll basically look something like this...
    [​IMG]
  14. matrixebi

    matrixebi Member

    Joined:
    Dec 24, 2009
    Messages:
    75
    Likes Received:
    0
    Trophy Points:
    16
    Ah, ok thanks.

    So what are the 'Recovery Mode' options for? Don't see then listed in the "Descriptions of each hack are explained here. "

    Thank you
  15. Enix82

    Enix82 Member

    Joined:
    Oct 28, 2007
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    11
    Great guide. I guess revision .30 has a new one added, "Block Online Updates." I cannot find any info about this one; however, I can only assume it's good to use just like the "Block Disc Updates." I hope.
  16. tunno1

    tunno1 Member

    Joined:
    Jan 22, 2010
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    11
    i cannot seem to get into the "system menu hacks" option.
    when im on the main screen (the white one in the pic a few comments ago,
    i click "system menu hacks", it goes white for a couple of seconds, then goes straight back to the same screen.

    have i missed something on my SD card?
  17. pryme_H

    pryme_H Regular member

    Joined:
    Mar 13, 2006
    Messages:
    1,715
    Likes Received:
    0
    Trophy Points:
    46
    If you followed the guide down to the letter the only other possible cause of this would be an incompatible SD card.

    Are you sure you placed the hacks.ini file on the root of the SD card?
  18. Enix82

    Enix82 Member

    Joined:
    Oct 28, 2007
    Messages:
    12
    Likes Received:
    0
    Trophy Points:
    11
    i cannot seem to get into the "system menu hacks" option.
    when im on the main screen (the white one in the pic a few comments ago,
    i click "system menu hacks", it goes white for a couple of seconds, then goes straight back to the same screen.

    have i missed something on my SD card?


    I bet you renamed the hacks incorrectly. On your desktop, don't add .ini to the end. It will actually be hacks.ini.ini if you do. Just change the name to hacks and save it because it is already an .ini extension.
  19. tunno1

    tunno1 Member

    Joined:
    Jan 22, 2010
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    11

    yes i did :)
    woops
    thank you VERY much!
  20. tunno1

    tunno1 Member

    Joined:
    Jan 22, 2010
    Messages:
    10
    Likes Received:
    0
    Trophy Points:
    11

    i just tried this and it worked.
    thank you very much!
  21. pryme_H

    pryme_H Regular member

    Joined:
    Mar 13, 2006
    Messages:
    1,715
    Likes Received:
    0
    Trophy Points:
    46
    If your computer is set to hide known file extensions, then this could happen.

Share This Page