Results 1 to 7 of 7

Thread: WBFS manager and disk update

  1. #1

    WBFS manager and disk update

    Hi all,

    well, i bought a pre-soft-modded wii from a store, and the only two information the guy knew was that it was using ios249 (dunno the revision, or how to know whats installed inside) and that i was under system menu 4.2. (its a black NTSC-U wii bundled with wii sports, wii resort and wii motion plus).

    It came with neogamma, and i already installed USB Loader GX via wad manager, and im actually using CFG Loader that i use from SD card with a fowarder channel (the fowarder i also used wad manager to install). All of them latest version till today.

    I read the posts and guides to do those tricks, and i use WBFS manager to place my backup isos at my hdd.

    And in the meantime some questions popped in my head:

    I usually copy pre-scrubbed isos to the hdd, if i cant get any pre-scrubbed, wbfs manager usually crop the iso to install it.

    1) Does the scrubbing process remove any disk update in the game?
    2) Do WBFS manager while scrubbing remove any disk updates?
    3) When i asked to the guy who sold me the wii bout disk updates he told me "only god knows", do i need to fear disk update bricks while using scrubbed isos?
    4) Could i brick my wii using those methods of copy/load isos to/from hdd?
    5) How do i know if i have bootmii under boot2 in case of any badass brick?

    PS: I looked into so many guides, and i think i saw this information somewhere, but i dont really remember if its something floating on my mind or if theres some reason into it. Sorry if its a "search the guides" sorta post. I just dont remember and couldnt find any info on that right now looking through the guides again.

  2. #2
    You can install priiloader to block disc and online updates. You can check if you already have this installed. Turn off the wii. Hold the reset button(dont let go) and press power. If priiloader is installed a menu should come up.

  3. #3
    Member WhiteShad0wX's Avatar
    Join Date
    Jun 2010
    Location
    I'm right here
    Posts
    1,615
    1+2. a scrubbed has the update removed (wbfs manager does it automatically)
    3. you can't install an update from an iso on a hard drive
    4. far as I know, you won't brick doing that
    5. with a black wii, since it's newer, you can't install bootmii as boot2 on it (when you turn on the wii, if the drive light flashes twice, boot2 is installed, if once, it's not installed)

    edit: you can do what mrkazador said to check on priiloader, if you don't have it, you'd better install it right away!
    See the Thanks button over there?
    <================================= Click it

  4. #4
    I was looking for some guide regarding the install of priiloader. I will now try to install priiloader in order to secure some bricks, but im not planning on cIOSCORP or anything dandy, i just want to play the thing. Nothing fancy. So i guess the priiloader could help in any game related brick, am i right?

    I did a SysCheck and certified that im running on 4.2 and some other info bout the system. Here it goes:

    [SPOILER]sysCheck GX v1.0.0 by Erik Spyder

    sysCheck GX is running under IOS36 (rev 65535).

    Console ID: 133584839.
    Region: NTSC-U.
    Hollywood v0x21.
    Boot2 v4.
    System Menu v481 (4.2U).
    BC v6.
    MIOS v10.


    Found 107 titles.
    Found 38 IOS and 8 IOS Stubs on this console.


    IOS 3 (rev 65280): Stub
    IOS 4 (rev 65280): Stub
    IOS 9 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS 10 (rev 768): Stub
    IOS 11 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS 12 (rev 269)
    IOS 13 (rev 273)
    IOS 14 (rev 520)
    IOS 15 (rev 1031)
    IOS 16 (rev 512): Stub
    IOS 17 (rev 65535): Trucha Bug
    IOS 20 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS 21 (rev 65535): Trucha Bug
    IOS 22 (rev 1037)
    IOS 28 (rev 65535): Trucha Bug
    IOS 30 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS 31 (rev 3349)
    IOS 33 (rev 65535): Trucha Bug
    IOS 34 (rev 3348)
    IOS 35 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS 36 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS 37 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS 38 (rev 65535): Trucha Bug
    IOS 40 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS 41 (rev 65535): Trucha Bug
    IOS 43 (rev 65535): Trucha Bug
    IOS 45 (rev 65535): Trucha Bug
    IOS 46 (rev 65535): Trucha Bug
    IOS 48 (rev 65535): Trucha Bug
    IOS 50 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS 51 (rev 4864): Stub
    IOS 52 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS 53 (rev 65535): Trucha Bug
    IOS 55 (rev 65535): Trucha Bug
    IOS 56 (rev 65535): Trucha Bug
    IOS 57 (rev 65535): Trucha Bug
    IOS 58 (rev 65535): Trucha Bug, USB 2.0
    IOS 60 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS 61 (rev 5405)
    IOS 70 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS 80 (rev 65535): Trucha Bug, ES_Identify, NAND Access
    IOS222 (rev 65280): Stub
    IOS223 (rev 65280): Stub
    IOS249 (rev 17): Trucha Bug, ES_Identify, NAND Access, USB 2.0
    IOS250 (rev 65280): Stub
    IOS254 (rev 31338)

    Report generated on 2010-11-15.[/SPOILER]


    I downloaded the priiloader, but without a guide to install it, and i found this on the disclaimer:


    [SPOILER]==============================
    Compiling / Binding Preloader
    ==============================

    In order to compile & use this installer with your application you must first place a "certs.bin"
    in the data directory along with "preloader.app". The "preloader.app" file is your
    compiled binary of the preloader source that has been bound with nand booting code.
    You can obtain this from any systems menu or channel. This code must be placed at the end of your
    compiled binary and potentially padded.
    you will also need to add the correct loading address in the dol header, in text section 1.
    this can be done manually or with dolboot.exe or (the much improved) opendolboot (found in priiloader source folder)

    FAILURE TO DO THIS PROPERLY WILL RESULT IN A BRICK SO BOOTMII INSTALLED TO BOOT2 IS A MUST!
    I ACCEPT NO LIABILITY FOR INCORRECT USE!![/SPOILER]

    I know im not compiling anything, but i dont know if i should install the .dol that came in the .rar without any reagard. I downloaded priiloader v04, should i just install it like any other thing at the HBC?

    I couldnt find any guide/tutorial directly to install it, can someone point me to one?
    Last edited by manteiga; 11-14-2010 at 07:34 PM.

  5. #5
    Looks like you have cIOSCORP installed but I'm no expert... You should wait for someone who knows before you install anything so you don't mess up your wii.

  6. #6
    nightstah
    Guest
    That's DarkFAIL or cIOSFAIL, all right. You might want to find Ithian's removal thread on this nasty piece of software and switch to a backup loader.

  7. #7
    Quote Originally Posted by nightstah View Post
    That's DarkFAIL or cIOSFAIL, all right. You might want to find Ithian's removal thread on this nasty piece of software and switch to a backup loader.
    My wii is actually running fine and i only use loaders to run games. Dunno what should i do ... its everything working fine, i just wanna install some brick protection.

    Other than that wii works fine.

    EDIT:

    I just did some reading and found Ithian thoughts and guide.

    He says:

    Quote Originally Posted by Ithian View Post
    [2a] Should I Remove cIOSCORP?

    Who this Guide is for: This is a guide for people who weren't sure what cIOSCORP is before they installed it, for those who want to avoid potential complications in the future, and for those who bought a system with cIOSCORP pre-installed who want to get rid of it. If you were directed to this page by someone it was probably for good reason.

    Who this Guide isn't for: If you are comfortable using cIOSCORP, know and understand what effect it has on your console, and are able to troubleshoot your way out of any issues that may arise in the future (like a brick), then this guide is not for you.
    I am a guy that got a wii with pre-installed cIOSCORP, cause of the 65535rev at my ios files. But i dont really know what are my 'potential complications in the future'. I really would get rid of it, but before i mess with something i just started to understand a week ago, i wanna know if for the uses i want, do i have to worry bout those complications.

    I already know that cIOSCORP messes with some ios overwriting them, and im pretty used with the disclaimer bout messing up with ios. So, if i had a choice i wouldnt mess with it and would use another softmod option.

    I just wanna play some games via usb hdd loader, install some harmless wads like loader fowarders, game covers and crap like that. My wii doesnt even has internet access.

    Maybe install some DLC/wiiware/VC, and i said maybe.

    Im not supporting cIOSCORP, i just dont wanna mess with something i dont understand.

    1) If hdd loaders cant install updates, and i dont plan to update system menu do i need to worry about cIOSCORP in my system?
    2) Is there any other source of harm besides system updates regarding cIOSCORP?
    Last edited by manteiga; 11-14-2010 at 08:49 PM.

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •