Page 2 of 2 FirstFirst 12
Results 11 to 17 of 17

Thread: Black screen, bootmii and homebrew starts

  1. #11
    Junior Member
    Join Date
    Aug 2009
    Posts
    4
    Thanks
    0
    Thanked 0 Times in 0 Posts

    bluetooth

    The problem is fixed, as I expected it was the bluetooth module that was broken. So if you ever get a black screen when starting your wii and your wiimotes won't sync, you still can access bootmii and HBC, but nothing else, then try to replace the bluetooth module.

  2. #12
    Junior Member
    Join Date
    Aug 2009
    Posts
    5
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Unhappy WII Start issue

    I have a issue with mu WII, when I start my WII it display the following menu:

    Systemmenu
    Homebrew Channel
    Installed File
    Load/Install File
    Systemmenu Hacks
    Settings

    I try Systemmenu and get the following ‘error autobooting systemmenu! Could not get TMD size!’.

    when i click on my Homebrew Channel, it still working.

    Thanks in advance for any help you can give me

  3. #13
    Junior Member
    Join Date
    Aug 2009
    Posts
    5
    Thanks
    0
    Thanked 0 Times in 0 Posts
    thanks to all for the support. It's working

  4. #14
    Junior Member
    Join Date
    Jan 2009
    Posts
    18
    Thanks
    5
    Thanked 2 Times in 2 Posts

    Thumbs up

    Quote Originally Posted by Tealc99 View Post
    Right. This file cboot2.zip is cboot2 and should allow you to boot a wad manager application to reinstate your system menu.

    This replaces the normal bootmii folder so make sure you have a backup of your existing one.

    You might like to get your system back at 3.2 or 4.0 depending on how far you think your downgrade got before it failed. I have a limited supply of system menus in my mediafire, click my sig.
    Hi Tealc,

    Kin awesome!! Got the menu back so can have a butchers at it!!

    Thanks again!
    Twicks

  5. #15
    Junior Member
    Join Date
    Oct 2009
    Posts
    5
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Unhappy

    Quote Originally Posted by Tealc View Post
    Right. This file cboot2.zip is cboot2 and should allow you to boot a wad manager application to reinstate your system menu.

    This replaces the normal bootmii folder so make sure you have a backup of your existing one.

    You might like to get your system back at 3.2 or 4.0 depending on how far you think your downgrade got before it failed. I have a limited supply of system menus in my mediafire, click my sig.
    Umm, my wii is bricked as well cause of me experimenting with softmii and umm, i tried your way, but my wii remotes won't sync and the gamecube controller isn't supported, is there anything else I can do before I have to take it to the 'amateur repairman'

  6. #16
    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
    You can replace the booting file with one of your choice, a GC enabled wad manager perhaps. Wad.Manager.1.5.Folder.wiiNinja.Mod3.rar

    If you can use cboot2 you can pretty much launch any application, as long as it's been modified to be GC compatible, to rescue your Wii.
    Not really doing much Wii stuff these days.

  7. #17
    Junior Member
    Join Date
    Oct 2009
    Posts
    5
    Thanks
    0
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by Tealc View Post
    You can replace the booting file with one of your choice, a GC enabled wad manager perhaps. Wad.Manager.1.5.Folder.wiiNinja.Mod3.rar

    If you can use cboot2 you can pretty much launch any application, as long as it's been modified to be GC compatible, to rescue your Wii.
    well I have a 4.0E (european wii i have) which told me to install cIOS60 first (which I did) I then tried to install System Menu 4.0E PAL .wad and it completed successfully, but my wii still loads to a black screen?

    if it helps i tried running Anyregion changer (the one that downgrades wii to 3.3) and it came up with an error on SYSCONF - unexpected error SYSCONF-Init Value -106
    Last edited by Lonestar1234; 10-03-2009 at 12:38 AM.

Page 2 of 2 FirstFirst 12

Tags for this Thread

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
  •