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

Thread: New Mario Bros. killed my Wii

  1. #1
    Junior Member
    Join Date
    Dec 2009
    Posts
    1
    Thanks
    0
    Thanked 0 Times in 0 Posts

    removed

    removed removed removed
    Last edited by jaeryee; 01-06-2010 at 01:16 PM.

  2. #2
    Junior Member Jasons34's Avatar
    Join Date
    May 2009
    Posts
    1,295
    Thanks
    20
    Thanked 455 Times in 350 Posts
    Blog Entries
    1
    There are a few things in your post that put up a red flag. For one, you say you have a NTSC-U console. Why would you be going off a guide thats for pal systems? 2. If you went and downgraded to 3.2U, why would you let NSMB upgrade you again? That made your downgrade pointless. Also, was the game the same region as your firmware AFTER you downgraded? If the game region was different than your firmware region, then you bricked your console.
    If I have helped you in any way, please thank me by pressing the little thanks button.

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


  4. #3
    Senior Member
    DA KINE WiiHacker
    mauifrog's Avatar
    Join Date
    May 2009
    Posts
    9,187
    Thanks
    307
    Thanked 9,584 Times in 2,974 Posts
    Blog Entries
    15
    Quote Originally Posted by jaeryee View Post
    Big help needed

    bit of background first
    1. Drivekey modded Wii
    2. updated to 4.2U
    3. Downgraded to 3.2U using below link instruction
    Downgrader wii 4.2E en 3.2E

    After downgraded to 3.2U, I inserted New Super Mario Bros. burned DVD.
    Wii request System Update from New Super Mario Bros. DVD - updated.
    Wii reset.
    "No Signal" appears on my TV screen.

    Power button has green light.

    how can I fix this problem.
    Unless you have boot2 bootmii, your wii is not fixable, unless you replace the mainboard and reprogram the nand.

    Your brick is a direct result of downgrading to 3.2. This left stubbed system ios50 and ios60. A disk update to 3.4, 4.0, or 4.1 was a guaranteed brick.
    Ipsa scientia potestas est.


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

  5. #4
    Senior Member
    DA KINE WiiHacker
    mauifrog's Avatar
    Join Date
    May 2009
    Posts
    9,187
    Thanks
    307
    Thanked 9,584 Times in 2,974 Posts
    Blog Entries
    15
    Quote Originally Posted by jaeryee View Post
    how do I get boot2 bootmii.
    I want to fix my Wii.
    Please help.....
    You can't get it, it needs to already be installed. You would have installed it with the HBC. If you have it you would see two flashes from the blue led drive light at boot with disk removed.
    Ipsa scientia potestas est.


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

  6. #5
    Retired WiiHacks Staff Tealc's Avatar
    Join Date
    May 2009
    Location
    Sunny Wales, UK
    Posts
    7,152
    Thanks
    502
    Thanked 4,104 Times in 2,453 Posts
    Blog Entries
    1
    Launch into HBC through bootmii and use Wad manager to install IOS60 v6174

    Download this cboot2_wadmanager_1.5_mod.zip

    Drop contents to a formatted SD card.

    Download this IOS60patched.rar

    Drop the wad file to SD:\wad

    Put SD card in Wii
    Power on.
    When Wad manager loads use IOS249 to install IOS60patched.wad
    Rejoice.

    You may need to use a Gamecube controller to control Wad manager.
    Not really doing much Wii stuff these days.

  7. #6
    Junior Member Jasons34's Avatar
    Join Date
    May 2009
    Posts
    1,295
    Thanks
    20
    Thanked 455 Times in 350 Posts
    Blog Entries
    1
    I didnt even take notice that he was on 4.2 already when he did the nintendo update. Arent I correct when I say that you cant downgrade a 4.2 firmware?
    If I have helped you in any way, please thank me by pressing the little thanks button.

  8. #7
    Junior Member Jasons34's Avatar
    Join Date
    May 2009
    Posts
    1,295
    Thanks
    20
    Thanked 455 Times in 350 Posts
    Blog Entries
    1
    Did you install bootmii as boot2 or ios? If you installed as boot 2, when you power on the wii, the drive will flash quickly 2 times.
    If I have helped you in any way, please thank me by pressing the little thanks button.

  9. #8
    Senior Member
    DA KINE WiiHacker
    mauifrog's Avatar
    Join Date
    May 2009
    Posts
    9,187
    Thanks
    307
    Thanked 9,584 Times in 2,974 Posts
    Blog Entries
    15
    Quote Originally Posted by Jasons34 View Post
    I didnt even take notice that he was on 4.2 already when he did the nintendo update. Arent I correct when I say that you cant downgrade a 4.2 firmware?
    Downgrading is not recommended because there is little point. It is a relic of a technique used when system menu 3.4 was a thorn in ones side as there where no system menu hacks for it, and still are not. Downgrading is possible but it is not worth the risks.

    2 bad things can happen.
    1- Ios30 and system menu 3.2 do not fully support new wii's, lu64 and newer. Downgrading these can, as far as I know result in a bricked wii.

    2- the biggest problem is the stubbed system ios files left behind. If they are not replaced with functional ios, and an update from disk is preformed, the stubbed ios will not be replaced by the update, because they have a higher version #. This is exactly what happened in this thread. Ios60 was stubbed, because the wii was on 4.2, then downgraded to 3.2, leaving stubbed ios50 and ios60. And a dead wii after NSMB updated to 4.1.

    Hopefully he does have boot2 bootmii.
    Ipsa scientia potestas est.


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

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


  11. #9
    Junior Member Jasons34's Avatar
    Join Date
    May 2009
    Posts
    1,295
    Thanks
    20
    Thanked 455 Times in 350 Posts
    Blog Entries
    1
    You need to understand that 4.2 uses completly different ios files as 3.2 does. Its fine to update from 3.2 to 4.2 but when you downgrade from 4.2 to 3.2 and then upgrade again, that will brick. Not to mention that you arent even sure what firmware you had to begin with. Easy way to figure this out is......... What country do you live in and did you buy the wii from your country? If you live in the US and bought it new in the US, then you have a US firmware (U). If you live in europe and bought it new in europe, then you have a pal firmware (E). Then you have to see what region the game is that you used to upgrade your firmware. Its either NTSC-U or PAL.
    If I have helped you in any way, please thank me by pressing the little thanks button.

  12. #10
    Retired WiiHacks Staff Tealc's Avatar
    Join Date
    May 2009
    Location
    Sunny Wales, UK
    Posts
    7,152
    Thanks
    502
    Thanked 4,104 Times in 2,453 Posts
    Blog Entries
    1
    Jason - You can downgrade 4.2 firmware, it's just like downgrading any other System Menu, simply install System IOS and System Menu for your chosen revision, making sure that future upgrade paths are free of stub IOS. This is where the OP failed and so many others. Updating firmware always installs stubs to IOS50 and IOS60 which are not flushed when a disc update comes along. The other fail is when people choose 3.2 and their Wii cannot run 3.2 (LU64).
    I would not even consider downgrading without having boot2 installed.


    The OP clearly has his/her own agenda and will not listen to anything the experts on Wiihacks have to say....

    Mauifrog has suggested you check for bootmii flashes a couple of times.

    I recommended you use cboot2 to launch wad manager to fix your problem

    Jason also suggested you check for double flashes.

    So what's it to be OP?

    Did you want help or are you just wanting to waste our time? I can always remove this thread and your posting privileges if you like.
    Not really doing much Wii stuff these days.

  13. 1 User Says Thank You Tealc 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
  •