Results 1 to 6 of 6

Thread: I think I have a fully bricked Wii

  1. #1
    New Member
    Join Date
    Apr 2009
    Posts
    11
    Thanks
    2
    Thanked 0 Times in 0 Posts

    I think I have a fully bricked Wii

    Ok, so I am going to explain everything in detail so as to give an idea of how I got into this current situation.

    I had bought a Wii on kijiji for $10.00 knowing full well it was broken; originally I had thought that the Wii was physically broken. As it turns out the Wii was physically fine but had corrupted system files. After much searching and trying to figure things out we were able to use the Gamecube controller (taken apart) to launch into the black screen with the version 4.3U at the bottom right corner.

    After nothing was launching from that screen we were running out of options, so my fiancé had obtained some advice on here from a very experienced member in the Wii community on how to fix it if we had a way of playing the netflix backup. We have a fully functional Wii that has a D2CKey so I installed the disc drive from my working wii into the wii that was not working. Followed the instructions for the netflix isntallation and voila everything was great.

    Then we went through and followed the instructions after formatting. Installed bootmii, made a backup of the NAND, installed Home Brew channel etc... I should also note that this was one of the wii systems that would not enable installing bootmii to boot2 (I think that is how it goes). Everything seemed to be working fine and then all of a sudden I started getting errors when I would transfer a game from my wii to the SD card under data management option (so I could play from the SD card and save space on the wii channels). There errors didn't come from the transfer, it came from when i tryed to exit the SD card menu and go back to the wii menu; I would get a black screen with the same old "System files are corrupt". So I turned the wii off (had to hold the button down to turn it off) and restarted it and everything seemed fine, I did this a few times and then had enough for one night. Well about an hour later my fiancé went to launch the backup channel I believe it was and she got that "system files are corrupt message". This time the wii was no longer outputting any tv video or audio signal what-so-ever, it was like the wii did not exist. Whenever I turn it on I get no signal and I have to turn the power off by holding it for 2 or 3 seconds. I have done lots of reading on this but am still confused to if there is something I did terribly wrong (which i am assuming is the case) or if this is fixable without the NAND flashing option.

    I have read the guide on NAND flashing and am comfortable with doing the NAND flash as I am very comfortable with soldering and small components; I just wanted that to be a last resort. Not to mention if something does go horribly wrong this is kind of like a hobby wii that I am learning from.

    I may be missing important information, if there is some vital info I have not posted here that would help make understanding what I did easier please just ask.

    I appreciate any help that I can get, thank you.

    EDIT - I should also note that the wiimote turns the console on, it just won't connect to the console, the disc drive is operational as when I put a game in it spins.
    Last edited by gravitysdepth; 01-21-2013 at 04:47 PM. Reason: Forgot some details

  2. #2
    Senior Member
    DA KINE WiiHacker
    mauifrog's Avatar
    Join Date
    May 2009
    Posts
    9,180
    Thanks
    307
    Thanked 9,572 Times in 2,972 Posts
    Blog Entries
    15
    Are priiloader or savemiifrii working? Or not? When you did the softmod guide, did you keep system menu 4.3 or downgrade to 4.1? I would leave it unpluged for a night, if your lucky it will come back on. I don't see anything that you did to cause this, just bad luck.

    Also download this
    http://www.mediafire.com/?9778sgmybexww1o
    Have a look at that nand backup you made with nandbincheck.
    From the shell do
    Code:
    nandbincheck nand.bin -all -vvv
    Post the output here, it may give some clue. Or not.
    Last edited by mauifrog; 01-21-2013 at 07:38 PM.
    Ipsa scientia potestas est.


    Warning: Piracy is NOT supported. Word your questions carefully.

  3. #3
    Senior Member
    WiiHacks Staff
    Forum Administrator
    Only Site Donators Can PM Staff
    nightstah's Avatar
    Join Date
    Nov 2009
    Location
    Repatriated to WH
    Posts
    18,495
    Thanks
    1,859
    Thanked 4,331 Times in 3,632 Posts
    Blog Entries
    5
    Moved to the bricked section. OP: maui's most def the man for this in terms of advice

  4. #4
    New Member
    Join Date
    Apr 2009
    Posts
    11
    Thanks
    2
    Thanked 0 Times in 0 Posts
    Thanks for the help mauifrog, here is what I got... Doesn't seem good.
    Also, I did try savemiifrii, priiloader no luck.

    C:\Users\Darryl\Desktop\NAN>nandbincheck nand.bin -all -vvv
    ** nandBinCheck : Wii nand info tool **
    from giantpune
    built: Jan 29 2011 03:36:05
    checking boot1 & 2...
    Boot1 C (fixed)
    found 2 copies of boot2
    "blocks 1 & 2: Used for booting; Content Sha1 matches TMD; TMD officially signed
    ; Ticket officially signed; Version 4"
    "blocks 7 & 6: Backup copy; Content Sha1 matches TMD; TMD officially signed; Tic
    ket officially signed; Version 4"
    checking uid.sys...
    UIDmap::Check() system menu entry is messed up: 5087022971491600136 13a74d00
    checking content.map...
    NandBin::ItemFromPath ->item not found "/shared1/content.map"
    "No content map found in the nand"

  5. #5
    Senior Member
    DA KINE WiiHacker
    mauifrog's Avatar
    Join Date
    May 2009
    Posts
    9,180
    Thanks
    307
    Thanked 9,572 Times in 2,972 Posts
    Blog Entries
    15
    That does not look good at all. Here is what I would do. Make a backup copy of that nand.bin.
    Download giantpune's Nand Tools.zip
    Use ohneschwanzenegger format you nand.bin
    Use ohneschwanzenegger to install 4.3u system on the nand.bin
    Check the new nand.bin with nandbincheck as before for errors

    Now if the wii ever decides to turn back on, the first thing you should do is load bootmii ios and restore this new nand.bin. Use your gc controller and the KONAMI Code (UP,UP,DOWN,DOWN,LEFT,RIGHT,LEFT,RIGHT,B,A).

    If the wii never turns back on, flash that new nand with a nand programer.
    Ipsa scientia potestas est.


    Warning: Piracy is NOT supported. Word your questions carefully.

  6. 1 User Says Thank You mauifrog For This Useful Post


  7. #6
    New Member
    Join Date
    Apr 2009
    Posts
    11
    Thanks
    2
    Thanked 0 Times in 0 Posts
    Ok, so it looks much better after formatting the nand.bin file and putting the 4.3U system on it. This is what I get now. I am thinking I will have to manually flash it as it has been about a week or so now and it is still in the same mode where the TV doesn't see it and I have to hold the power button to turn it off. Thanks for all your help mauifrog.


    C:\Users\Darryl\Desktop\WII\NAN>nandbincheck nand.bin -all -vvv
    ** nandBinCheck : Wii nand info tool **
    from giantpune
    built: Jan 29 2011 03:36:05
    checking boot1 & 2...
    Boot1 C (fixed)
    found 2 copies of boot2
    "blocks 1 & 2: Used for booting; Content Sha1 matches TMD; TMD officially signed
    ; Ticket officially signed; Version 4"
    "blocks 7 & 6: Backup copy; Content Sha1 matches TMD; TMD officially signed; Tic
    ket officially signed; Version 4"
    checking uid.sys...
    checking content.map...
    checking "/shared1/00000000.app" ...
    checking "/shared1/00000001.app" ...
    checking "/shared1/00000002.app" ...
    checking "/shared1/00000003.app" ...
    checking "/shared1/00000004.app" ...
    checking "/shared1/00000005.app" ...
    checking "/shared1/00000006.app" ...
    checking "/shared1/00000007.app" ...
    checking "/shared1/00000008.app" ...
    checking "/shared1/00000009.app" ...
    checking "/shared1/0000000a.app" ...
    checking "/shared1/0000000b.app" ...
    checking "/shared1/0000000c.app" ...
    checking "/shared1/0000000d.app" ...
    checking "/shared1/0000000e.app" ...
    checking "/shared1/0000000f.app" ...
    checking "/shared1/00000010.app" ...
    checking "/shared1/00000011.app" ...
    checking "/shared1/00000012.app" ...
    checking "/shared1/00000013.app" ...
    checking "/shared1/00000014.app" ...
    checking "/shared1/00000015.app" ...
    checking "/shared1/00000016.app" ...
    checking "/shared1/00000017.app" ...
    checking "/shared1/00000018.app" ...
    checking "/shared1/00000019.app" ...
    checking "/shared1/0000001a.app" ...
    checking "/shared1/0000001b.app" ...
    checking "/shared1/0000001c.app" ...
    checking "/shared1/0000001d.app" ...
    checking "/shared1/0000001e.app" ...
    checking "/shared1/0000001f.app" ...
    checking "/shared1/00000020.app" ...
    checking "/shared1/00000021.app" ...
    checking "/shared1/00000022.app" ...
    checking "/shared1/00000023.app" ...
    checking "/shared1/00000024.app" ...
    checking "/shared1/00000025.app" ...
    checking "/shared1/00000026.app" ...
    checking "/shared1/00000027.app" ...
    checking "/shared1/00000028.app" ...
    checking "/shared1/00000029.app" ...
    checking "/shared1/0000002a.app" ...
    checking "/shared1/0000002b.app" ...
    checking "/shared1/0000002c.app" ...
    checking "/shared1/0000002d.app" ...
    checking "/shared1/0000002e.app" ...
    checking "/shared1/0000002f.app" ...
    checking "/shared1/00000030.app" ...
    checking "/shared1/00000031.app" ...
    checking "/shared1/00000032.app" ...
    checking "/shared1/00000033.app" ...
    checking "/shared1/00000034.app" ...
    checking "/shared1/00000035.app" ...
    checking "/shared1/00000036.app" ...
    checking "/shared1/00000037.app" ...
    checking "/shared1/00000038.app" ...
    checking "/shared1/00000039.app" ...
    checking "/shared1/0000003a.app" ...
    checking "/shared1/0000003b.app" ...
    checking "/shared1/0000003c.app" ...
    checking "/shared1/0000003d.app" ...
    checking "/shared1/0000003e.app" ...
    checking "/shared1/0000003f.app" ...
    checking "/shared1/00000040.app" ...
    checking "/shared1/00000041.app" ...
    checking "/shared1/00000042.app" ...
    checking "/shared1/00000043.app" ...
    checking "/shared1/00000044.app" ...
    checking "/shared1/00000045.app" ...
    checking "/shared1/00000046.app" ...
    checking "/shared1/00000047.app" ...
    checking "/shared1/00000048.app" ...
    checking "/shared1/00000049.app" ...
    checking "/shared1/0000004a.app" ...
    checking "/shared1/0000004b.app" ...
    checking "/shared1/0000004c.app" ...
    checking "/shared1/0000004d.app" ...
    checking "/shared1/0000004e.app" ...
    checking "/shared1/0000004f.app" ...
    checking "/shared1/00000050.app" ...
    checking "/shared1/00000051.app" ...
    checking "/shared1/00000052.app" ...
    checking "/shared1/00000053.app" ...
    found 58 titles installed
    Checking 00000001-00000009 ...
    Checking 00000001-0000000c ...
    Checking 00000001-0000000d ...
    Checking 00000001-0000000e ...
    Checking 00000001-0000000f ...
    Checking 00000001-00000011 ...
    Checking 00000001-00000015 ...
    Checking 00000001-00000016 ...
    Checking 00000001-0000001c ...
    Checking 00000001-0000001f ...
    Checking 00000001-00000021 ...
    Checking 00000001-00000022 ...
    Checking 00000001-00000023 ...
    Checking 00000001-00000024 ...
    Checking 00000001-00000025 ...
    Checking 00000001-00000026 ...
    Checking 00000001-00000029 ...
    Checking 00000001-0000002b ...
    Checking 00000001-0000002d ...
    Checking 00000001-0000002e ...
    Checking 00000001-00000030 ...
    Checking 00000001-00000035 ...
    Checking 00000001-00000037 ...
    Checking 00000001-00000038 ...
    Checking 00000001-00000039 ...
    Checking 00000001-0000003a ...
    Checking 00000001-0000003d ...
    Checking 00000001-00000050 ...
    found 28 bootable IOS
    Checking 00000001-00000002 ...
    Checking 00000001-00000004 ...
    Checking 00000001-0000000a ...
    Checking 00000001-0000000b ...
    Checking 00000001-00000010 ...
    Checking 00000001-00000014 ...
    Checking 00000001-0000001e ...
    Checking 00000001-00000028 ...
    Checking 00000001-00000032 ...
    Checking 00000001-00000033 ...
    Checking 00000001-00000034 ...
    Checking 00000001-0000003c ...
    Checking 00000001-00000046 ...
    Checking 00000001-000000de ...
    Checking 00000001-000000df ...
    Checking 00000001-000000f9 ...
    Checking 00000001-000000fa ...
    Checking 00000001-000000fe ...
    Checking 00000001-00000100 ...
    Checking 00000001-00000101 ...
    Checking 00010002-48414141 (HAAA) ...
    Checking 00010002-48414241 (HABA) ...
    Checking 00010002-48414341 (HACA) ...
    Checking 00010002-48414641 (HAFA) ...
    Checking 00010002-48414645 (HAFE) ...
    Checking 00010002-48414741 (HAGA) ...
    Checking 00010002-48414745 (HAGE) ...
    Checking 00010002-48415941 (HAYA) ...
    Checking 00010008-48414b45 (HAKE) ...
    Checking 00010008-48414c45 (HALE) ...
    Checking for 003 error ...
    Checking setting.txt stuff...
    Comparing uid.sys against the filesystem...
    checking for lost clusters...
    found 0 lost clusters
    UNK ( 0xffff ) 0 ()
    free 636e
    verifying ecc...
    2 out of 460928 pages had incorrect ecc.
    they were spread through 2 clusters in 2 blocks:
    (2, 6)
    0 of those clusters are non-special (they belong to the fs)
    verifying hmac...
    verifying hmac for 315 files
    0 files had bad HMAC data
    checking HMAC for superclusters...
    0 superClusters had bad HMAC data

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
  •