Page 1 of 2 12 LastLast
Results 1 to 10 of 12

Thread: Wii system files corrupt - but can be bypassed

  1. #1
    New Member
    Join Date
    Apr 2010
    Location
    Naples, FL USA
    Posts
    33
    Thanks
    6
    Thanked 2 Times in 2 Posts

    Us Wii system files corrupt - but can be bypassed

    First of all I'd like to point out I, to some extent, know what I'm doing well enough to not have done something terribly stupid (though who knows)

    I'm currently using 4.2U firmware on a LU73~ Wii. I've tried looking into things like bootmii etcetera to save from a possible brick but haven't been able to on such a newer serial of wii.

    I just today ran into the issue of a black screeen showing "Wii system files are corrupt" after exiting out of a game I was playing through neogamma (a legit copy of NSMB - by hitting home and Menu), but once removing the game, SD card, and USB hard drive the wii started up just fine.

    I've got several (I know I should keep track of this, but I didn't know better at the time) IOS patches, cIos (waninkoko's) installed, but these were all long ago.

    The only two things to my wii that could possibly be causing this are upgrading from Neogamma R8 to R9b47 and the fact I started messing with ocarina codes.

    I thought of the possibility of some saves being corrupted, so I deleted my NSMB and SSBB saves (only games I've used ocarina codes on).


    Does anyone know if this is a problem which would progress over time? Does anyone know any method I can safeguard from a future brick? Should I be worried about this?



    -- Bonus question -- If anyone is so kind as to help me, is there a way to make my LU73+ wii read burnt discs? (for playing GC backups through neogamma (through disc))?


    Thanks in advance!

  2. #2
    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,407
    Thanks
    1,825
    Thanked 4,288 Times in 3,603 Posts
    Blog Entries
    5
    Moved to the bricked section. You have Priiloader installed? Look here.

    Bonus question: replace your optical drive (or at least the attached PCB) with an older one, if yours is D3-2.

  3. 1 User Says Thank You nightstah For This Useful Post


  4. #3
    New Member
    Join Date
    Apr 2010
    Location
    Naples, FL USA
    Posts
    33
    Thanks
    6
    Thanked 2 Times in 2 Posts
    Alright, sorry for the confusion, I just didn't know if I should post under the bricked section when I still had somewhat full access.

    I don't have priiloader installed as of yet, I'm looking into that post though. Were you asking as an option to safeguard from further bricking/issues or were you asking to try to determine the nature of my corrupted system files?

  5. #4
    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
    Your not bricked. Your issue is most likely related to an issue with your loader, cios, or a combination. I will suggest that you follow the softmod guide linked below from start to finish, do every step. Then see if the issue is resolved upon completion.
    Ipsa scientia potestas est.


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

  6. #5
    New Member
    Join Date
    Apr 2010
    Location
    Naples, FL USA
    Posts
    33
    Thanks
    6
    Thanked 2 Times in 2 Posts
    Yeah, I know I'm not bricked, I was just wondering if this was more of a notice of an impending NAND or system failure that I could prevent, and was wondering how I would go about preventing it.

    As of now I still have full access to my system with the sporadic apparition of the black screen of doom.

    I know bootmii ( i think that's what it was) couldn't do much because it couldn't be installed on a certain part of my system (boot2?). Would priiloader be able to save me from a possible future brick on a LU73+?

  7. #6
    New Member
    Join Date
    Apr 2010
    Location
    Naples, FL USA
    Posts
    33
    Thanks
    6
    Thanked 2 Times in 2 Posts
    Possibly useful information : For some reason since this happened, my wii does not go on standby (yellow light mode) anymore when put on it, it's always either green/red. Played 2 hours of wario land shake it last night just fine.

  8. #7
    Junior Member
    Join Date
    Dec 2009
    Location
    England
    Posts
    1,304
    Thanks
    7
    Thanked 320 Times in 240 Posts
    Blog Entries
    2
    Yellow light just means Wiiconnect24 is turned on.

  9. #8
    New Member
    Join Date
    Apr 2010
    Location
    Naples, FL USA
    Posts
    33
    Thanks
    6
    Thanked 2 Times in 2 Posts
    Oh, I did turn that off recently, I was just used to it. I always thought it was some form of sleep mode, though essentially that's what wiiconnect24 is. Thanks for the information though!

  10. #9
    New Member
    Join Date
    Apr 2010
    Location
    Naples, FL USA
    Posts
    33
    Thanks
    6
    Thanked 2 Times in 2 Posts
    Alright, so far the problem is still around, I have a nand backup to a much earlier date. Would it be beneficial (e.g. Solve my corruption problem) were I to restore that nand backup? Also is there a chance of anything going wrong with that? And would I have to reinstall Waninkoko's/Hermes' cIOS?

    syscheckGX report as requested by junkmail on IRC.


    Code:
    sysCheck GX v1.0.0 by Erik Spyder
    
    sysCheck GX is running under IOS61 (rev 5405).
    
    Console ID: 86178011.
    Region: NTSC-U.
    Hollywood v0x21.
    Boot2 v4.
    System Menu v481 (4.2U).
    BC v6.
    MIOS v10. 
    
    
    Found 174 titles.
    Found 25 IOS and 12 IOS Stubs on this console.
    
    
    IOS  3 (rev 65280): Stub
    IOS  4 (rev 65280): Stub
    IOS  9 (rev   778)
    IOS 10 (rev   768): Stub
    IOS 11 (rev   256): Stub
    IOS 12 (rev   269)
    IOS 13 (rev   273)
    IOS 14 (rev   520)
    IOS 15 (rev   523)
    IOS 16 (rev   512): Stub
    IOS 17 (rev   775)
    IOS 20 (rev   256): Stub
    IOS 21 (rev   782)
    IOS 22 (rev  1037)
    IOS 28 (rev  1550)
    IOS 30 (rev  2816): Stub
    IOS 31 (rev  3349)
    IOS 33 (rev  3091)
    IOS 34 (rev  3348)
    IOS 35 (rev  3349)
    IOS 36 (rev  3351)
    IOS 37 (rev  3869)
    IOS 38 (rev  3867)
    IOS 50 (rev  5120): Stub
    IOS 51 (rev  4864): Stub
    IOS 53 (rev  5406)
    IOS 55 (rev  5149)
    IOS 56 (rev  5405)
    IOS 57 (rev  5661)
    IOS 60 (rev  6400): Stub
    IOS 61 (rev  5405)
    IOS 70 (rev  6687)
    IOS222 (rev 65280): Stub
    IOS223 (rev 65280): Stub
    IOS249 (rev    19): Trucha Bug, ES_Identify, NAND Access, USB 2.0
    IOS250 (rev 65535): Trucha Bug, ES_Identify, NAND Access, USB 2.0
    IOS254 (rev 65281)
    
    Report generated on 2010-11-17.
    Edit: Followed mauifrogs EXCELLENT guide, but still having some issues. Did everything on the guide step by step, except the 4.1 downgrade, everything worked till I exited out of CFG USB loader, took me to home, got the system files corrupt message again.
    Last edited by zeiddiez; 11-17-2010 at 03:04 PM.

  11. #10
    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
    Do you ever get this issue when booting the wii?
    You can try two things.
    1- you can try to reinstall your system ios and system menu or downgrade to 4.1- you would need to reinstall priiloader when your done, preferably before rebooting the wii.
    2- you can try a system format from the wii settings, you would loss all saves and channels.
    Ipsa scientia potestas est.


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

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


Page 1 of 2 12 LastLast

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
  •