Results 1 to 6 of 6

Thread: Banner brick 4.2 (PAL) - is drivekey the solution?

  1. #1
    Junior Member
    Join Date
    Feb 2010
    Location
    at home
    Posts
    4
    Thanks
    2
    Thanked 0 Times in 0 Posts

    Banner brick 4.2 (PAL) - is drivekey the solution?

    Hi,

    I have banner bricked my wii (FW 4.2, PAL) using a bad wad.

    I get to the health warning but after I press A I get a black screen.
    A strange thing is that if I push and hold reset just after pressing A at the health screen it takes about 5 seconds then I get to the wii logos that
    appears at the top left of the screen and moves towards the bottom right of the screen. After that it is back to the black screen. And if I press reset when I see the logos it disappears for a couple of seconds and then reappears. I can do this over and over but when i stop pushing reset I always get the black screen. I donīt think this is relevant but I find it kind of strange and i am just wondering if anyone else has noticed this.

    I have bootmii as ios and no preloader. So I believe my only chance of unbricking is to buy a modchip (must be a drivekey since I am useless at soldering) and use it to boot a DVD from recovery mode. If there is another option please let me know. I have not reached the recovery mode since I need a screwdriver to open my GC controller and modify it. But I donīt see a reason I shouldnīt be able to reach the recovery mode, or?

    But my real question is what I will be able to do from the recovery menu after installing the drivekey? What can I do with/without autoboot enabled on the drivekey, donīt think I can order it set to autoboot.

    1. Boot legit games?
    2. boot backup games?
    3. boot recovery disc (boot wad manager or boatmii)? this would be the best scenario so I can just remove the bad wad.
    4.boot "Nintendo offical recovery disc"? not sure what this is but to my understanding this could give me the opportunity to delete everything on my wii including the bad wad.

    I think option 3 and 4 should work on my system but I am far from certain. I appreciate all comments.

    If it is any help I think i have ios 36 or 38. But when I used neogamma it said ios249. I have seen posts that suggests that option 3 needs a trucha bug and that some ios "opens" the trucha bug even on later version of the nintendo FW. But I have no idea if 36/38/249 supports this.

    This became quite a long story, if you read this far please make a comment. I donīt wanna spend money on a drivekey if there is no chance of it unbricking my wii. If there is a chance I will give it a try and report back on this forum of my progress.

    /Zyk2B

  2. #2
    Banned
    Join Date
    Jan 2010
    Location
    Somewhere........
    Posts
    243
    Thanks
    13
    Thanked 57 Times in 51 Posts
    First of all try wii maintance mode.Hold + and - and at helt screen push A few times.Try this for couple of times.If u boot up,post and i will tell u what to do.If that fails next thing will fix your wii but is a bit harder to do it


    Hope it helps

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


  4. #3
    Junior Member
    Join Date
    Feb 2010
    Location
    at home
    Posts
    4
    Thanks
    2
    Thanked 0 Times in 0 Posts
    Hi, thanks for the quick reply. I have tried this without succes. Thanks anyway

  5. #4
    Senior Member
    DA KINE WiiHacker
    mauifrog's Avatar
    Join Date
    May 2009
    Posts
    9,180
    Thanks
    307
    Thanked 9,571 Times in 2,972 Posts
    Blog Entries
    15
    You installed a theme wad, yes?

    You need a modchip preconfigured to autoboot.

    If you installed ios70 with trucha patch, you will be able to boot recovery disks, like an autoboot HBC loader, or loadmii. Then you would be able to run the required apps. If you did not install a patched ios70, you will not be able to boot any custom disks.

    You will be able to boot many game iso, but all. If you installed Indiana PWNS, you can autoboot Lego Indiana Jones and use that exploit to load your apps. But it would need to be installed on the wii to work.

    Smash stack wtih SSBB will not work, so don't try.

    If all of the above is FAIL, you may be able to force your way into data management, if data management still functions. The process involes installing many many large savegame files, channels, perhaps DLC, filling the nand. This would force the wii to send you to data management to free up space.

    If you bricked your wii by installing a custome theme wad, you can fix it when a 4.3 update is released. You would disable your update block on the chip, and update from the disk. Unfortunatly you'll probably have to wait a year or so for that to work.

    So when you buy your chip, make sure it is preconfigured to autoboot, region free is enabled, and the update block is disabled. You will not be able to configure to chip on the bricked wii.
    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. #5
    Junior Member
    Join Date
    Feb 2010
    Location
    at home
    Posts
    4
    Thanks
    2
    Thanked 0 Times in 0 Posts
    Yes, I am pretty sure it was a bad theme wad.

    I doubt i have ios70 and definitely no lego indiana jones either . So it looks like I have two options. Try and fill up the NAND to reach data management and wipe the wii from there or wait for a game that does the automatic update to 4.3. And both of these options require a drivekey set to autoboot. Good, at least now I know my options. My next question then is, can I configure the drivekey in my friends wii or must it be done another way by the supplier. If I get the drivekey installed with autoboot I will at least be able to play some games and then we will see if I have the patience to fill the nand or just sit back and wait and hope that 4.3 fixes my problem.

    Thanks a lot for the extremely quick and informative answer.

  8. #6
    Junior Member
    Join Date
    Feb 2010
    Location
    at home
    Posts
    4
    Thanks
    2
    Thanked 0 Times in 0 Posts
    I need to correct myself regarding the wad. It was a bad channel forwarder which i guess means that the 4.3 update wonīt solv the problem since it doesnīt delete any channels?? So I guess my only chance then is to get the chip and start filling up my nand. I think I have seen some threads on the topic on this site so I will review them.

    Thanks for all the help

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
  •