Advice: Is my NAND screwed up, and can I fix it?

Discussion in 'Wii - Hacking' started by IggyNignokt, May 7, 2011.

  1. IggyNignokt
    OP

    Newcomer IggyNignokt Member

    Joined:
    Oct 19, 2010
    Messages:
    25
    Country:
    United States
    Hey everyone,

    I have an original Wii from release day 11/19/06. It had worked well for me, and I upgraded it to 4.3U normally. A few months after that, I started getting intermittent errors that my Mii channel data was corrupt. It would go away if I reset the Wii, but would come back a few days or weeks later. My concern about having to wipe my Wii and lose all my Miis, games with online play save data, etc. led me to look into hacking my Wii so I could back up the NAND. I got Homebrew and BootMii going via SmashHack, and backed up my NAND immediately.

    Things had been working swimmingly until about the last 2 months. All of a sudden, my Wii has become VERY unreliable. There are times it won’t go past getting turned on by the Wiimote (black screen, Wiimotes sync to turn it on and then lose sync), times it will get to the Warning screen but won’t get to the System Menu, times it can get to BootMii (if I choose) but crashes after selecting to load the Homebrew Channel, often crashes trying to load or exit the “Wii Settings” menu, and games loaded from USB Loader GX v1r927 (used in March, then reverted back to in late April), USB Loader GX v2.0 (used in early April), Configurable USB Loader v1.5 (used in late April), or the original discs (throughout) all randomly lock up.

    So basically my Wii has become incredibly unreliable. Restoring from a NAND backup via BootMii tends to fix things for a few days, but now I never know if my Wii will work when I go to turn it on. I suspect it is due to the NAND, so are there any tools I can use to verify the NAND on the Wii or repair it? My fear is I will have to wipe the Wii completely and not restore from a backup (as perhaps my NAND backups are corrupt too), or even worse there’s nothing to be done and my Wii is toast.

    Thanks for any info!
     


  2. LinkFan16

    Member LinkFan16 I link them all

    Joined:
    Mar 15, 2009
    Messages:
    378
    Country:
    Germany
    To save your Miis and your savedata without having to do a full nand backup, you can use SaveGame Manager GX. As for your other problems, I think there surely is a solution to this, but that is better explained by someone who has a bit more knowledge than me.

    EDIT: Typo fixed
     
  3. neotank19

    Member neotank19 GBAtemp Regular

    Joined:
    Apr 1, 2010
    Messages:
    222
    Country:
    United States
    First I would backup all gamesaves and miis as stated abouce with savegame manager gx. Then I would do a complete remod with modmii. If your problems are still there after that or if you modded with modmii before you can try another program called "ohneswanzenegger" you can use this to create a fresh nand filesystem on your computer then flash it to your wii with bootmii.
     
  4. obcd

    Member obcd GBAtemp Advanced Maniac

    Joined:
    Apr 5, 2011
    Messages:
    1,594
    Country:
    Belgium
    A nand chip is known to have bad blocks. They are marked as being bad and no longer used as storage area.
    The number of write/erase cycles of a flash chip are limited. Unless your nand chip storage area is almost fully used,
    bad blocks shouldn't be a problem. If you take a backup with bootmii, it will tell you the number of blocks that are marked as being bad.

    You could try to use Sneek/ Uneek. It only uses the boot2 area of your nand chip, and doesn't care about the rest of your nand contents.
    If that runs without issues, your problem is your nand. If it gives you issues as well, there is something else wrong with your wii.
     
  5. IggyNignokt
    OP

    Newcomer IggyNignokt Member

    Joined:
    Oct 19, 2010
    Messages:
    25
    Country:
    United States
    Well, I’ve downloaded and built all of GiantPune’s latest tools on Mac OS X. My last NAND backup is as follows, courtesy of NANDBinCheck from the CLI:

    <div class='codetop'>CODE</div><div class='codemain' style='height:200px;white-space:Pre;overflow:auto'>checking boot1 & 2...
    Boot1 B (vulnerable)
    found 3 copies of boot2
    "blocks 1 & 2: Marked as bad blocks; Content Sha1 matches TMD; TMD officially signed; Ticket officially signed; Version 4"
    "blocks 3 & 4: Used for booting; Content Sha1 matches TMD; TMD is fakesigned; Ticket officially signed; BootMii 1.3"
    "blocks 7 & 6: Backup copy; Content Sha1 matches TMD; TMD officially signed; Ticket 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" ...
    checking "/shared1/00000054.app" ...
    checking "/shared1/00000055.app" ...
    checking "/shared1/00000056.app" ...
    checking "/shared1/00000057.app" ...
    checking "/shared1/00000058.app" ...
    checking "/shared1/00000059.app" ...
    checking "/shared1/0000005a.app" ...
    checking "/shared1/0000005b.app" ...
    checking "/shared1/0000005c.app" ...
    checking "/shared1/0000005d.app" ...
    checking "/shared1/0000005e.app" ...
    checking "/shared1/0000005f.app" ...
    checking "/shared1/00000060.app" ...
    checking "/shared1/00000061.app" ...
    checking "/shared1/00000062.app" ...
    checking "/shared1/00000063.app" ...
    checking "/shared1/00000064.app" ...
    checking "/shared1/00000065.app" ...
    checking "/shared1/00000066.app" ...
    checking "/shared1/00000067.app" ...
    checking "/shared1/00000068.app" ...
    checking "/shared1/00000069.app" ...
    checking "/shared1/0000006a.app" ...
    checking "/shared1/0000006b.app" ...
    checking "/shared1/0000006c.app" ...
    checking "/shared1/0000006d.app" ...
    checking "/shared1/0000006e.app" ...
    checking "/shared1/0000006f.app" ...
    checking "/shared1/00000070.app" ...
    checking "/shared1/00000071.app" ...
    checking "/shared1/00000072.app" ...
    checking "/shared1/00000073.app" ...
    checking "/shared1/00000074.app" ...
    checking "/shared1/00000075.app" ...
    checking "/shared1/00000076.app" ...
    checking "/shared1/00000077.app" ...
    checking "/shared1/00000078.app" ...
    checking "/shared1/00000079.app" ...
    checking "/shared1/0000007a.app" ...
    checking "/shared1/0000007b.app" ...
    checking "/shared1/0000007c.app" ...
    checking "/shared1/0000007d.app" ...
    checking "/shared1/0000007e.app" ...
    checking "/shared1/0000007f.app" ...
    checking "/shared1/00000080.app" ...
    checking "/shared1/00000081.app" ...
    checking "/shared1/00000082.app" ...
    checking "/shared1/00000083.app" ...
    checking "/shared1/00000084.app" ...
    checking "/shared1/00000085.app" ...
    checking "/shared1/00000086.app" ...
    checking "/shared1/00000087.app" ...
    checking "/shared1/00000088.app" ...
    checking "/shared1/00000089.app" ...
    checking "/shared1/0000008a.app" ...
    checking "/shared1/0000008b.app" ...
    checking "/shared1/0000008c.app" ...
    checking "/shared1/0000008d.app" ...
    checking "/shared1/0000008e.app" ...
    checking "/shared1/0000008f.app" ...
    checking "/shared1/00000090.app" ...
    checking "/shared1/00000091.app" ...
    checking "/shared1/00000092.app" ...
    checking "/shared1/00000093.app" ...
    checking "/shared1/00000094.app" ...
    checking "/shared1/00000095.app" ...
    checking "/shared1/00000096.app" ...
    checking "/shared1/00000097.app" ...
    checking "/shared1/00000098.app" ...
    checking "/shared1/00000099.app" ...
    found 74 titles installed
    Checking 00000001-00000009 ...
    Checking 00000001-0000000c ...
    Checking 00000001-0000000d ...
    Checking 00000001-0000000e ...
    Checking 00000001-0000000f ...
    Checking 00000001-00000010 ...
    tmd fakesigned
    Checking 00000001-00000011 ...
    Checking 00000001-00000015 ...
    Checking 00000001-00000016 ...
    Checking 00000001-0000001c ...
    Checking 00000001-0000001e ...
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: 4781d270a35b6470f9978ec6d20f31c2b9772a57
    ticket RSA signature isn't even close ( 4 )
    tmd fakesigned
    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-00000032 ...
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: 27ec49fa7489ceb559caa99657de1691b127334c
    ticket RSA signature isn't even close ( 4 )
    tmd fakesigned
    Checking 00000001-00000035 ...
    Checking 00000001-00000037 ...
    Checking 00000001-00000038 ...
    Checking 00000001-00000039 ...
    Checking 00000001-0000003a ...
    Checking 00000001-0000003c ...
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: cdf37839a84b7f51d3bf7bbb1d01e30de7e58aa6
    ticket RSA signature isn't even close ( 4 )
    tmd fakesigned
    Checking 00000001-0000003d ...
    Checking 00000001-00000046 ...
    Checking 00000001-00000050 ...
    tmd fakesigned
    Checking 00000001-000000ca ...
    ticket fakesigned
    tmd fakesigned
    Checking 00000001-000000de ...
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: c4f6206aae907977fc4740aaf7d63f78ef7f5df4
    ticket RSA signature isn't even close ( 4 )
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: 48900638a513496d917b6f0aa6c898a57424b816
    tmd RSA signature isn't even close ( 4 )
    Checking 00000001-000000df ...
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: 3873973e59211f1456f9cb64cad8fe196a57d2e0
    ticket RSA signature isn't even close ( 4 )
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: def57806d64d06cf878b846383937d636018280f
    tmd RSA signature isn't even close ( 4 )
    Checking 00000001-000000e0 ...
    ticket fakesigned
    tmd fakesigned
    Checking 00000001-000000ec ...
    ticket fakesigned
    tmd fakesigned
    Checking 00000001-000000f9 ...
    ticket fakesigned
    tmd fakesigned
    Checking 00000001-000000fa ...
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: 90e6739edef63708884faa915ee9328a4eec9fe4
    ticket RSA signature isn't even close ( 4 )
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: 4e824e7216013dac3988044343bb5eb6e88a2622
    tmd RSA signature isn't even close ( 4 )
    Checking 00000001-000000fe ...
    ticket fakesigned
    tmd fakesigned
    found 41 bootable IOS
    Checking 00000001-00000002 ...
    Checking 00000001-00000004 ...
    Checking 00000001-0000000a ...
    Checking 00000001-0000000b ...
    Checking 00000001-00000014 ...
    Checking 00000001-00000033 ...
    Checking 00000001-00000100 ...
    Checking 00000001-00000101 ...
    Checking 00010001-48414445 (HADE) ...
    NandBin::ItemFromPath ->item not found "/title/00010001/48414445/content/00000023.app"
    error reading one of the private contents "/title/00010001/48414445/content/00000023.app"
    Checking 00010001-48414a45 (HAJE) ...
    Checking 00010001-48415045 (HAPE) ...
    Checking 00010001-48415445 (HATE) ...
    NandBin::ItemFromPath ->item not found "/title/00010001/48415445/content/00000012.app"
    error reading one of the private contents "/title/00010001/48415445/content/00000012.app"
    Checking 00010001-4a414645 (JAFE) ...
    Checking 00010001-4d414245 (MABE) ...
    Checking 00010001-50414145 (PAAE) ...
    Checking 00010001-55435846 (UCXF) ...
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: 8af88ca78892382ae25444162b1e78a5c504ec4a
    ticket RSA signature isn't even close ( 4 )
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: 465522dae3772e4b3a811608f6314ed5547655df
    tmd RSA signature isn't even close ( 4 )
    Checking 00010001-554c4e52 (ULNR) ...
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: 9ef470a28c60c020a2f6b7084b974d15ceed09ae
    ticket RSA signature isn't even close ( 4 )
    tmd fakesigned
    NandBin::ItemFromPath ->item not found "/title/00010001/554c4e52/content/00000000.app"
    error reading one of the private contents "/title/00010001/554c4e52/content/00000000.app"
    Checking 00010001-554e454f (UNEO) ...
    Decrypted signature hash: 0000000000000000000000000000000000000000
    SHA1 hash: d0605fe7377ce240c843555fb6b0dcb5e9d80e1c
    ticket RSA signature isn't even close ( 4 )
    tmd fakesigned
    NandBin::ItemFromPath ->item not found "/title/00010001/554e454f/content/00000000.app"
    error reading one of the private contents "/title/00010001/554e454f/content/00000000.app"
    Checking 00010001-57444d45 (WDME) ...
    Checking 00010001-af1bf516 (....) ...
    ticket fakesigned
    tmd fakesigned
    Checking 00010002-48414141 (HAAA) ...
    Checking 00010002-48414241 (HABA) ...
    Checking 00010002-48414341 (HACA) ...
    Checking 00010002-48414641 (HAFA) ...
    incorrect uid/gid for data folder-- expected: "0000100a"/"3031" got: "0000100a"/"0002"
    Checking 00010002-48414645 (HAFE) ...
    Checking 00010002-48414741 (HAGA) ...
    incorrect uid/gid for data folder-- expected: "0000100c"/"3031" got: "0000100c"/"0002"
    Checking 00010002-48414745 (HAGE) ...
    Checking 00010002-48415941 (HAYA) ...
    Checking 00010004-52464e45 (RFNE) ...
    NandBin::ItemFromPath ->item not found "/title/00010004/52464e45/content/00000001.app"
    error reading one of the private contents "/title/00010004/52464e45/content/00000001.app"
    Checking 00010004-52465045 (RFPE) ...
    Checking 00010004-524d4345 (RMCE) ...
    Checking 00010008-48414b45 (HAKE) ...
    Checking 00010008-48414c45 (HALE) ...
    Checking for 003 error ...
    Checking setting.txt stuff...
    Comparing uid.sys against the filesystem...
    00010001-48415745 (HAWE) has been deleted
    00010000-00494e53 (.INS) has been deleted
    00010005-73584145 (sXAE) has been deleted
    00010005-73594f45 (sYOE) has been deleted
    00010005-73584545 (sXEE) has been deleted
    TMD for 00000001-00000000 is fakesigned
    00000001-00000000 has been deleted
    00010000-53584950 (SXIP) has been deleted
    ticket for 00010005-735a4145 (sZAE) is fakesigned
    00010005-735a4145 (sZAE) has been deleted
    ticket for 00010005-735a4245 (sZBE) is fakesigned
    00010005-735a4245 (sZBE) has been deleted
    ticket for 00010005-735a4345 (sZCE) is fakesigned
    00010005-735a4345 (sZCE) has been deleted
    ticket for 00010005-735a4445 (sZDE) is fakesigned
    00010005-735a4445 (sZDE) has been deleted
    ticket for 00010005-735a4545 (sZEE) is fakesigned
    00010005-735a4545 (sZEE) has been deleted
    00010000-52333645 (R36E) has been deleted
    ticket for 00010005-735a4a45 (sZJE) is fakesigned
    00010005-735a4a45 (sZJE) has been deleted
    TMD for 00010000-524b4d45 (RKME) is fakesigned
    ticket for 00010005-735a4b45 (sZKE) is fakesigned
    00010005-735a4b45 (sZKE) has been deleted
    ticket for 00010005-73443245 (sD2E) is fakesigned
    00010005-73443245 (sD2E) has been deleted
    ticket for 00010005-735a4645 (sZFE) is fakesigned
    00010005-735a4645 (sZFE) has been deleted
    ticket for 00010005-72394a45 (r9JE) is fakesigned
    00010005-72394a45 (r9JE) has been deleted
    checking for lost clusters...
    found 0 lost clusters
    UNK ( 0xffff ) 20 (568e, 568f, 56f9, 56fa, 56fb, 56fc, 56fd, 56fe, 56ff, 6258, 6259, 625a, 625b, 625c, 625d, 625e, 625f, 6be9, 6bea, 6beb, 6bec, 6bed, 6bee, 6bef, 7938, 7939, 793a, 793b, 793c, 793d, 793e, 793f)
    free 2769
    verifying ecc...
    2 out of 1451456 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 867 files
    0 files had bad HMAC data
    checking HMAC for superclusters...
    0 superClusters had bad HMAC data
    </div>

    I don’t think it’s a good thing that the first System Menu on boot2 is marked as “bad blocks”, but they also aren’t flagged red in the CLI (or even blue), so at least GiantPune didn’t think it was brick-worthy. Otherwise the only errors are some things that are fake signed, some incorrect permissions, and some missing files, but nothing else flagged red.

    Neotank19, I used another of GiantPune’s apps, nandExtract, to verify it can read and extract save games and Miis from my current NAND backup. obcd, my NAND is about 70% used and it’s never been more filled than it is now. There are a few bad blocks reported when I last used BootMii to back it up (perhaps 3). It is going on 5 years old, though. I restored my last NAND again, and things are working for now. We’ll see how long it lasts....

    I’ll take your advice and switch over to UNEEK if I have any more trouble with my Wii, as that way I’m trying to starting over from a virginized NAND in a virtual fashion and still have my real NAND to fall back on if things don’t work out.
     
  6. techboy

    Member techboy GBAtemp Advanced Maniac

    Joined:
    Mar 15, 2009
    Messages:
    1,720
    Location:
    Pennsylvania
    Country:
    United States
    The fakesigned stuff is normal. Patched or custom IOSes, modified/custom channels, HBC, and warez will appear that way. The SM will have hash mismatches if priiloader or startpatch is installed, or if you modified it in other ways (e.g. installing a theme).

    Not sure about the permissions and missing files though...someone with more NAND FS expertise would likely be able to explain these.
     
  7. giantpune

    Member giantpune GBAtemp Addict

    Joined:
    Apr 10, 2009
    Messages:
    2,860
    Country:
    United States
    this statement doesnt really make sense. the system menu is not installed ON any boot2. and those blocks are not really bad. that is just a trick used by the hackmii installer uses to be able to write bootmii to some unused blocks and then get the wii to use the newly written boot2 when booting the wii.


    it would be more helpful to wait until you wii is broken again and then dump the nand and check the broken nand. if you are checking you old nand and then installing it, it really doesnt tell you much about what has gone wrong. next time your wii "breaks", dump the nand with bootmii and run nandBinChecker with the args " -all -v -v" and see if it says anything useful.
     
  8. IggyNignokt
    OP

    Newcomer IggyNignokt Member

    Joined:
    Oct 19, 2010
    Messages:
    25
    Country:
    United States
    My misunderstanding, I thought that the Boot2 blocks mentioned with “Version 4” implied it was what the Wii used to finish the normal bootloader and get to the System Menu (with “Version 4” referring to System Menu 4.3). I didn’t know how BootMii worked regarding marking the first few sectors as “bad blocks” on purpose to get the hacked boot2 loaded.

    Anyway, I tried to see if using ModMii and UNEEK would work to save my Wii. After setting up a new NAND image and bringing over my setting.txt, Miis, savegames, and Friend List, I’m still stuck with random freezes in the Wii System Settings Menu, random black screens before the initial warning screen and after (usually after), and random lock-ups of games played off of their original disc or off of a backup saved to the USB drive.

    End result, I’m growing more suspicious that my Wii is just getting too old to function properly. Which is a shame, as I still have a working NES from over 20 years ago! I’ll try some other options in the next few days, including SNEEK (to rule out a USB or HD issue), and using a totally virgin NAND (both restored to the Wii and one created by ModMii for SNEEK or UNEEK), but I’m losing hope it can be rescued.
     
  9. DeadlyFoez

    Member DeadlyFoez Banned

    Joined:
    Apr 12, 2009
    Messages:
    5,224
    Country:
    United States
    Wii Connect 24 could be the culprit if you had it enabled. But it sounds like either your wii needs a full reflow, the ram is bad, or you got some bad IOS issues.

    Are you still wasting your time with USB Loader GX? That could be your problem because it's been known to cause bricks like you have described. Try using wiiflow or CFG loader instead after doing a nand restore from a GOOD working nand image.

    If that still doesn't fix it, you could try Ohneschanzenegger by Pune to create a fresh nand image for your wii. If that still doesn't work then you could send your wii to me and I'll take a good stab at it. I wouldn't charge as much as I normally charge for a brick repair, and if I can't fix it to satisfaction then I would not charge anything. Basically, if I can't fix it then you only lost on shipping costs and I'll give you your money back. But if I can't fix it then all hope is lost with the wii because I can do reflows and replace the ram. If I can't fix it then I'd even buy it from you if you would like so I can have some spare parts and you can get a little cash back to get another wii. As everyone on here would tell you, I am an honest person when it comes to my service work and I have NEVER screwed anyone over........EVER!!!

    Funny enough, there was even one wii that I repaired and some drunk driving asshole hit a telephone pole outside my house and cause a power surge that burned up that wii and a few of my electronics. I took it upon myself to purchase a new wii for that customer so he could have a working one. Even though it wasn't my fault, seeing it from the customers end it was my fault so I needed to fix it.

    Either way, try what I suggested and get back to us in this thread. I'd rather help you out free of cost to you before you would ever have to pay me for a repair.
     
  10. IggyNignokt
    OP

    Newcomer IggyNignokt Member

    Joined:
    Oct 19, 2010
    Messages:
    25
    Country:
    United States
    I haven’t been able to turn Wii Connect 24 off, as even with a fresh NAND it crashes every time I try to go into the System Settings to disable it.

    I’ve not used USB Loader GX in about 3 weeks, though the issues did start with it. I’ve since restored to a NAND from prior to using USB Loader GX 2. I’ve tried jumping back to several known-good NANDs from my own Wii taken from over the past 8 months or so, and all lead to these problems within a day or two of use (if not right from the start). I’ve more recently used CFG Loader and am now on UNEEK + DI and JoyFlow. All still have crashing issues.

    I’ll see if starting completely over from a virgin NAND will work next.
     
  11. mauifrog

    Member mauifrog DA KINE WiiHacker

    Joined:
    Jan 21, 2010
    Messages:
    1,585
    Country:
    United States
    If I where you I would simply backup my miis and savegames and use Ohneschanzenegger, just as others have said. Just make you life simple and make a new nand.
     
  12. tueidj

    Member tueidj I R Expert

    Joined:
    Jan 8, 2009
    Messages:
    2,569
    Country:
    You are aware your good buddy giantpune helped write USB Loader GX, right?
     
  13. DeadlyFoez

    Member DeadlyFoez Banned

    Joined:
    Apr 12, 2009
    Messages:
    5,224
    Country:
    United States
    "OH NOES!! Pune helped dev it?!?! It's all HIS fault. Get out your torches and pitchforks. We're going on a dev hunt."

    Cool. Whoopdy doo. It doesn't change the fact that lots of other noobie dev's had their filthy hands on the source, and it also doesn't change the fact that it has bricked lots of wii's. So you making that statement is just you trying to start trouble again.

    If you have nothing useful to add then go and crawl back under your rock. I'm trying to help someone, not be a trouble starter.
     
  14. tueidj

    Member tueidj I R Expert

    Joined:
    Jan 8, 2009
    Messages:
    2,569
    Country:
    Perhaps a good way to not be a trouble starter would be to not criticize something, especially when you don't have any evidence.
     
  15. shortz1994

    Member shortz1994 GBAtemp Maniac

    Joined:
    Jan 21, 2011
    Messages:
    1,341
    Country:
    United States
    i'm following this post,an so far to me it seems gx is a risk, so i will be removing that one from my wii. i had all three of the good ones, (so i thought).i have cfg, flow an gx. please don't ask why. just want to make sure i can play my games.
     
  16. tueidj

    Member tueidj I R Expert

    Joined:
    Jan 8, 2009
    Messages:
    2,569
    Country:
    i heard an read you like men and teh buttsex.
     
  17. DeadlyFoez

    Member DeadlyFoez Banned

    Joined:
    Apr 12, 2009
    Messages:
    5,224
    Country:
    United States


    Yes, there has been a huge amount of threads about random bricks on this forum and wiihacks and I'm sure many other places too, and the common denominator has always been GX. Those random bricks of that nature don't happen with other loaders, only with GX.

     
  18. tueidj

    Member tueidj I R Expert

    Joined:
    Jan 8, 2009
    Messages:
    2,569
    Country:
    Well, look at it this way: you've got disposable wiis and an infectus. If GX is so unstable why don't you make it brick a wii, dump the NAND, run it through nandbincheck and find out exactly what the problem is? Then you can dump on it all you like
     
  19. DeadlyFoez

    Member DeadlyFoez Banned

    Joined:
    Apr 12, 2009
    Messages:
    5,224
    Country:
    United States
    Sounds like an idea, but I don't care to waste my time trying to figure out which game or combination of cIOS's or whatever the formula might be especially when almost nobody uses GX anymore. It's easier to just tell people to avoid GX.

    And please, you can talk to me without being insulting.
     
  20. IggyNignokt
    OP

    Newcomer IggyNignokt Member

    Joined:
    Oct 19, 2010
    Messages:
    25
    Country:
    United States
    Ladies and gentlemen, no need for all the flames! I do thank you for all the suggestions, though.

    Let’s remember that the whole reason I started looking at the Homebrew scene was because I was getting random errors that my Miis were corrupt back before any hacking. I was able to save them, and used USB Loader GX in various revisions for about a year without issue. Going to USBLGX 2.0 seems to have coincided roughly with when all the issues became worse, but that could have been coincidental.

    At this point, I have a UNEEK + DI setup going, which has given me some flexibility in quickly changing emulated NANDs. After going to a fresh NAND with only the minimal of my Wii’s info copied over (setting.txt, Miis, Friend List, and a few save game files), things seem to be running better.

    There are still a few issues, namely lockups at the Wii Settings screen (especially when trying to go to the second or third page of options, though I have been able to turn off WiiConnect 24) and with JoyFlow and DI both choking on a couple of my games. The main offender is Mario Kart Wii, which I just cannot get to load! This is from the USBLGX .wbfs converted to DiscEx, .wbfs to ISO to DiscEx, or a redump via DI to ISO to DiscEx. Loading via DI gives a “disc not read” error, while JoyFlow crashes upon selecting it. This is with or without my original savefiles in place. If I reboot to my internal NAND the original disc plays just fine there.

    So for now, it seems I’ve saved my Wii from the garbage heap. I’ll update this thread if things change in the future.

    Thanks again for all the help!
     

Share This Page