Nilum's Revirginize Guide

Discussion in 'Wii - Hacking' started by nilum, Sep 17, 2010.

Sep 17, 2010

Nilum's Revirginize Guide by nilum at 4:14 AM (8,186 Views / 0 Likes) 13 replies

  1. nilum
    OP

    Newcomer nilum Member

    Joined:
    Sep 4, 2009
    Messages:
    28
    Country:
    United States
    <b>Nilum’s Revirginize Guide</b>
    <a href="https://docs0.google.com/document/edit?id=10E8ijcsJ-6BlaCigMlaCDlQSYaqXrQWTxO4niowMa9k&hl=en#" target="_blank">Google Docs Version</a>

    <b><!--coloro:red--><span style="color:red"><!--/coloro-->This guide does not remove or overwrite uid.sys which keeps details for every title (including homebrew) that is run on the Wii. If you are sending it out to be repaired, be prepared for the repair to be denied. Note once it's denied once, your registered Wii's serial number will probably be blocked from any future repairs.<!--colorc--></span><!--/colorc--></b>

    I made this guide because there weren't any definitive steps to take on the web. I am sending my Wii in for repair, so I needed to make sure it was clean as there have been cases of Nintendo refusing to repair soft-modded Wii's. Just FYI it's $85 to get the artifacting problem fixed <img src="style_emoticons/<#EMO_DIR#>/frown.gif" style="vertical-align:middle" emoid=":(" border="0" alt="frown.gif" />.

    Hope this is helpful for some people. I wrote this guide as I was doing the steps. So the procedures did work for me using 4.2U. Also, mostly used IOS236[36].

    <b>I only suggest using this guide if you are planning on selling your Wii or shipping it out for repair. There is no reason to start over from scratch when hacking a Wii.</b>

    I suggest having a NAND backup with BootMii loaded to Boot2 before proceeding. The Homebrew Channel and BootMii are the last two items we remove, so if you brick before then, you will at least be able to restore and try again. Not necessarily the case if BootMii is loaded as an IOS and not to the Boot2.

    <b>The Tools You Need</b>
    DOPMii - <a href="http://bit.ly/b6CkPr" target="_blank">http://bit.ly/b6CkPr</a>
    AnyTitle Deleter MOD - <a href="http://bit.ly/c7asXh" target="_blank">http://bit.ly/c7asXh</a>
    WAD Manager - <a href="http://bit.ly/90UvWh" target="_blank">http://bit.ly/90UvWh</a>
    NANDClean - <a href="http://bit.ly/b6ojcG" target="_blank">http://bit.ly/b6ojcG</a>
    HackMii - <a href="http://bit.ly/JyBtY" target="_blank">http://bit.ly/JyBtY</a>
    <b>Extract and copy the folder containing the boot.dol to SDRoot\apps. Make sure to rename the .dol file to boot.dol if its not already.</b>

    NUSDownloader - <a href="http://bit.ly/5rzPur" target="_blank">http://bit.ly/5rzPur</a>
    <b>Extract it to a folder on your computer this is a Windows application - not homebrew made to run on the Wii - Downloading your system menu explained below.</b>

    <b>Remove Patches from IOS and Update IOS</b>
    Load DOPMii from the Homebrew Channel.
    Choose your preferred patched IOS (36, 222, 236, 249, etc).
    Choose: ‘Scan the Wii’s internals (SysCheck)’
    Press ‘A’ to continue. Note: this is not a scrollable list, so once SysCheck fills the screen it will pause and you need to press ‘A’ to continue.
    Take note of the IOS with patches, then press ‘A’ to continue. Keep doing this until it lists all IOS.
    Most IOS should say Disabled for all three fields (meaning they are unpatched). The only ones that should have any patches are the 200+ IOS (which are all cIOS) and possibly IOS36.
    If other IOS have patches then we need to get rid of these patches in the next step.
    Once SysCheck has completed the scan, you can choose to save the report. Instead, just exit by pressing ‘B.’ You will return to the main menu.

    Choose: ‘IOS, BC, MIOS’
    Take a moment and look at the interface.
    In the top left is the IOS/cIOS that is currently selected, along with its version(which can also be selected). These are IOS/cIOS that DOPMii detects or can install. DOPMii cannot install all IOS (especially not cIOS).
    In the top right is the current installed version of that particular IOS/cIOS selected or if it is not installed at all.
    In the middle row is information about the selected IOS and its uses. It also lists available patches for the IOS and if it can be downloaded via NUS.
    At the bottom are commands and ‘Current IOS’ which is the IOS you selected to use for DOPMii at the beginning.
    First, check if you have installed any Korean IOS: 40, 41, 43, 45, 46, 48.
    These are needed for Korean games. Some cIOS installers will install patched versions of these IOS, but these aren’t supposed to be on US/EU systems, so they should be removed. I believe JP systems do have the Korean IOS.
    So unless you have a JP or Korean system, press ‘-’ to unstall each of these IOS.
    <b>[NOTE: 4.3 Wii's of all regions have Korean IOS. If you use 4.3, these IOS should be on your Wii!]</b>
    Press ‘A’ when prompted for confirmation.
    Second, try to install any STUBs that you may have removed. Nintendo doesn’t remove any IOS, instead they just deprecate them to a STUB. If you use DOPMii (or any other IOS manager) to clean up your NAND, you have probably already removed some of these useless IOS, but they should be there.
    Press ‘A’ for both confirmations. Choose ‘NUS Downloader’ as the Installation method (for the following steps as well).
    Next, reinstall (overwrite) any of the patched IOS we saw in our SysCheck report.
    In some cases these will include STUBs that were patched for some unknown reason.
    <b>Remember to leave your patched IOS36 and patched cIOS (200+), until later on.
    <!--coloro:red--><span style="color:red"><!--/coloro-->ALSO: If you are running an older System Menu (4.2 and lower), do NOT update the IOS that corresponds to your system menu to the ‘STUB’ version. Example: If you have System Menu 4.2U and IOS70 v6687, upgrading to v6912 will brick your Wii.<!--colorc--></span><!--/colorc-->
    If you have an IOS that is for a later version of system menu (IE, you have 4.2U with IOS80(for 4.3U) installed), delete it with the exception of IOS58. </b>
    I think IOS58 this is also part of 4.3U - please correct me if I am wrong - this is needed by the Homebrew Channel. Unfortunately I don’t know if Uninstalling the Homebrew Channel with Hackmii removes this IOS, but it might. At the very least you will have one out of place IOS on your system.
    Proceed to update any other out of date IOS (keeping the aforementioned info in mind). Remember not to select any patches for these.
    Finally, if you know there are some cIOS that you don’t need, go ahead and remove them now. DO NOT DELETE IOS254... and make sure you have at least one patched IOS you can use for the rest of this guide.

    <b>Remove Pirated WiiWare/Virtual Console Titles and Homebrew</b>
    Load AnyTitle Deleter from the Homebrew Channel.
    Load with your preferred cIOS.
    Goto: Installed Channel Titles
    Use ‘-’ an ‘+’ to page through the list.
    Press ‘A’ after selecting a title, and confirm with ‘A’ to delete.
    Here you will see a list of games(WiiWare/VC). A few might show up as UNKNOWN, but if you search for the hex or alphanumeric value on google, you should be able to find out what the title is called.
    If you have installed wads for loaders or other homebrew like USB Loader GX and Neogamma, you might see them listed in here as UNKNOWN as well.
    <b><!--coloro:red--><span style="color:red"><!--/coloro-->The Homebrew Channel is also listed here. Make sure NOT to delete this yet! We will be using HackMii to do that.<!--colorc--></span><!--/colorc-->
    [Note: You might experience errors when deleting. For the most part I have found that AnyTitle Deleter still does its job regardless, but if it is bothering you try using TruchaBug Restorer to install patched IOS36 as IOS236. Then use IOS236 and see if that fixes your error. If not, I wouldn’t worry]</b>
    After you’ve removed all your pirated WiiWare/Virtual Console Games and Homebrew Titles<b> (Remember do not remove the Homebrew Channel yet)</b>, exit out.
    <b>[Note: You can also take the time to delete your save data here. I chose to, just go to ‘Disc Game Titles (and Saves)’. Also, check out ‘Games that use Channels (Channel+Save)’ and ‘Downloadable Game Content.’ Just delete them all if they are not legit.]
    </b>

    <b>Remove Priiloader/Preloader</b>
    To remove Priiloader/Preloader all you need to do is install your System Menu wad. This is different from IOS. Priiloader/Preloader itself is just a modified System Menu.

    Run NUS Downloader on your PC.
    Make sure the ‘Pack -> Wad’ menu is checked.
    Click Database > System > System Menu > [choose your system menu]
    <b>[Note: to find out what system menu you are using, at the Wii channel menu, click the Wii icon on the bottom left. Click Wii Settings. You will see your system menu version at the top-right portion of the display (i.e. 4.2U).]</b>
    Click ‘Start NUS Downloader!’ to begin downloading your System Menu as a wad.
    Move the wad to SDRoot\wad.

    Load Wad Manager from the Homebrew Channel.
    [WARNING FINAL FANTASY MUSIC (for 1.7 at least XD)- enjoy]
    Press ‘A’ to agree.
    Choose preferred patched IOS.
    For ‘Select NAND emulator device:’ choose ‘Disable.’
    For ‘Select source device’ choose ‘Wii SD Slot.’
    When the ‘Filebrowser’ appears, select the ‘WAD’ directory.
    Select your System menu wad (i.e. ‘System Menu-NUS-v481.wad’).
    For ‘Select action’ choose ‘Install WAD.’
    Press ‘A’ to continue. Press ‘B’ to go back and then ‘Home’ to exit.

    <b>Remove Residual Traces of Priiloader/Preloader</b>
    Load NANDClean from the Homebrew Channel.
    Press ‘A’ at all prompts.
    If it doesn’t find a file that is okay.
    When you get to the prompt asking you to delete the System Menu app, press ‘+’, and then press ‘-.’ Don’t worry we don’t need this anymore, as we’ve installed the unmodified version in the previous step.
    Press any key to quit.

    <b>Remove cIOS and/or unpatch IOS36</b>
    Return to DOPMii and remove any cIOS you have left. Any of the 200+ IOS works. Also, unpatch IOS36 by reinstalling it and when the options come up to patch, press ‘B’ to choose no. DO NOT DELETE IOS254. We’ll let HackMii handle that.
    Note: I’m not sure if you can uninstall an IOS even if you are currently running that IOS for DOPMii. What I suggest though is having IOS36 patched. Running DOPMii with IOS36, uninstall all your 200+ IOS, and then update IOS36 without the patches.

    <b>Run HackMii to Remove BootMii and the Homebrew Channel</b>
    HackMii does not need patched IOS to run thankfully. Just Homebrew Channel or one of the many exploits(Twilight Hack, Bannerbomb, Smash Stack, or Indiana PWNS(EU))
    Load HackMii Installer from the Homebrew Channel.
    It takes a few seconds to start. Press ‘1’ to proceed.
    It should detect IOS 58.
    Choose ‘Uninstall DVDX’ (if it’s selectable - if it’s not installed it won’t be an option)
    Choose ‘Boot Mii...’
    Choose ‘Uninstall BootMii as IOS’
    Confirm
    <b>[Note: for some reason this option doesn’t seem to go away - use SysCheck to make sure it’s gone - DopMii doesn’t need a patched IOS for the SysCheck.]</b>
    Run HackMii again! (that is if for some reason it crashes - did that for me - otherwise continue. Even if it crashes it should be gone)
    ...
    Choose ‘Boot Mii...’
    Confirm
    Uninstall ‘BootMii as Boot 2’
    Choose ‘Return to the main menu’ to go back
    Choose ‘Uninstall Homebrew Channel’
    Confirm
    Exit

    For some reason it goes to BootMii. Don’t be worried though, it is wiped off. Press ‘reset.’

    <b>Format Your Wii System Memory</b>
    At the Wii Channel Select Screen, click the Wii icon at the bootom left.
    Choose ‘Wii Settings.’
    Click the arrows over to thr right twice.
    Choose ‘Format Wii System Memory.’
    This removes the system messages that have logs of your usage - this also includes messages about homebrew. This also deletes saves, etc. If you have anything you want to save search for a way to back it up.

    <b>REMOVE YOUR SD CARD or FORMAT IT</b>
    That should be self explanatory. If you are sending your Wii out to be repaired, you don’t want to provide them with an SD card full of homebrew.

    <b>Congratulations your Wii is clean!</b>
     
  2. moosehunter

    Member moosehunter GBAtemp Regular

    Joined:
    Nov 26, 2008
    Messages:
    199
    Country:
    United States
    uid anybody?

    Edit: didn't see the Format Your Wii System Memory. Stopped skimming at Congratulations your Wii is clean!

    Edit2: Actually I don't know if formatting from the SM touches the UID
     
  3. nilum
    OP

    Newcomer nilum Member

    Joined:
    Sep 4, 2009
    Messages:
    28
    Country:
    United States
    User ID? What do you mean?
     
  4. Slimmmmmm

    Member Slimmmmmm GBAtemp MoNkEeE

    Joined:
    Nov 1, 2007
    Messages:
    1,687
    Location:
    the land of lol
    Country:
    United Kingdom
    No it wont "clean" the uid.sys afaik, plus some other files that log things. So this WILL NOT make your Wii "virgin" to Nintendo, only to someone that doesn't know where to look.
     
  5. XFlak

    Member XFlak Wiitired but still kicking

    Joined:
    Sep 12, 2009
    Messages:
    9,122
    Location:
    Ontario
    Country:
    Canada
  6. Slimmmmmm

    Member Slimmmmmm GBAtemp MoNkEeE

    Joined:
    Nov 1, 2007
    Messages:
    1,687
    Location:
    the land of lol
    Country:
    United Kingdom
    The main problem is even if you can remove everything and get rid of all traces of things you ran with some "wonder app", that "wonder app" itself being ran will leave traces.

    To remove traces of the "wonder app", you could always use some other "uber app", but again it would leaves traces.

    @ the op, nice effort on the guide thuogh. I don't mean to knock your efforts.
     
  7. nilum
    OP

    Newcomer nilum Member

    Joined:
    Sep 4, 2009
    Messages:
    28
    Country:
    United States
  8. Slimmmmmm

    Member Slimmmmmm GBAtemp MoNkEeE

    Joined:
    Nov 1, 2007
    Messages:
    1,687
    Location:
    the land of lol
    Country:
    United Kingdom
    I can easily overwrite the uid.sys file, BUT whatever I use to do this WILL leave a trace. I can overwrite that, but again that will leave a trace etc etc etc.

    Plus uid.sys is not the only thing that Nintendo can investigate to see what's been done on a wii.

    However, do you really think Nintendo has time to spend digging deep into the Wii files ? I don't think so, so your guide "should" be ok. Th eonly way to know is have someone use it and send a Wii to Nintendo.

    I've know people to return Wii's with many things left that Nintendo didn't bother to look for, so you never know.
     
  9. nilum
    OP

    Newcomer nilum Member

    Joined:
    Sep 4, 2009
    Messages:
    28
    Country:
    United States
    What I was thinking is that you could have the a title used for cleaning the sys.uid spoof another title.

    Also, doesn't it depend when data is written to the uid.sys. If it's written to before or right after the title is launched, launching the 'wonder app' and then having it clean the sys.uid, shouldn't leave any traces. And even if it's written to when the title is terminated, you could pull the power on it before terminating that title.

    Assuming we execute the code using bannerbomb (or other exploits) we could do this without having to go back in and delete other homebrew. Once it's done - it's done.

    Pseudocode:
    Run code via Bannerbomb or other exploit - Wii appends sys.uid
    Overwrite sys.uid
    Prompt user to pull power


    Then have user use wii with legit titles for a while to show some activity on the wii.
     
  10. nilum
    OP

    Newcomer nilum Member

    Joined:
    Sep 4, 2009
    Messages:
    28
    Country:
    United States
    Well, I might ship it out today. So I'll have the results soon.
     
  11. nilum
    OP

    Newcomer nilum Member

    Joined:
    Sep 4, 2009
    Messages:
    28
    Country:
    United States
    Portion of a reply I got from bushing (Team Twiizers):

    I've put off sending my Wii in, but I promise I will send it out soon.

    If NoA doesn't refuse to repair my Wii, we at least know that they aren't prying into the uid.sys.
     
  12. KiiNG

    Member KiiNG GBAtemp Regular

    Joined:
    Aug 20, 2009
    Messages:
    180
    Country:
    United States
    I've sent my original Wii off twice. Never got denied repair. My 2nd Wii had one of the retarded drive errors from SSBB which didn't get denied either. Each time had homebrew on it. The first time, HBC was still on the Wii. Since when did the third-party company actually repairing them, making pay-per-unit, care what's on it? Nintendo out-sources their repairs. Hell, I think all gaming consoles do.

    Sadly, its cheaper to go on Craigslist now if you got access to it. [​IMG] I was able to buy another Wii for $60 (boot2v2) a few weeks back.
     
  13. nilum
    OP

    Newcomer nilum Member

    Joined:
    Sep 4, 2009
    Messages:
    28
    Country:
    United States
    New modified version of AnyTitle Deleter by bushing is available for people to try.

    atd_bushing.zip
     
  14. nilum
    OP

    Newcomer nilum Member

    Joined:
    Sep 4, 2009
    Messages:
    28
    Country:
    United States
    Just wanted to add one more thing. I forgot I had written this guide.

    Nintendo did the repair no questions asked when I sent them my Wii, but if you have an older mod you might have IOS0 still on there. The version of Any Title Deleter bushing updated (previous posting) does detect IOS0.

    Hope this was helpful.

    Edit: When my Wii was repaired the latest version of the System Menu was loaded (4.3) and the internal hardware was changed to prevent boot2 from being used. I still soft chose to soft mod my Wii again even with the additional risk.
     

Share This Page