hbc -"channel cant be used" & wad manager question

Discussion in 'Wii - Hacking' started by q9wert, Apr 8, 2010.

  1. q9wert
    OP

    q9wert Member

    Newcomer
    17
    0
    Apr 8, 2010
    hi
    i recently upgraded my wii from 3.4e to 4.0 using wankinko's upgrader because priiloader doesnt work under 3.4. i installed the hbc ages ago, using the twilight hack, and everything worked fine. but now, after the update (and numerous edits of ios/cios - all guided ofc) i get a message that says "This channel cant be used", when i open the hbc through the wii menu. it works fine, when i open it through bootmii though.
    this only seems to happen to other people, when they install wads that are from another region, according to google.
    do i have to reinstall the hbc using the banner bomb exploit?

    another question i have is, how can i get the wadmanager running? (nothing illegal here, i just want to use it for gecko os and cfg usb loader). i always get an 1029 error...

    ty in advance
     
  2. Krestent

    Krestent What to post?

    Member
    3,953
    33
    Mar 31, 2009
    United States
    You probably have an outdated HBC anyway. Just reinstall it.
     
  3. q9wert
    OP

    q9wert Member

    Newcomer
    17
    0
    Apr 8, 2010
    reinstalled it (after previously uninstalling it) through hackmii, doesnt change anything...

    but i solved the other problem. wads work for me now if i use ios 222 instead of 249.

    btw, i tried to forward my gecko. i got the same error. installing cfg usbloader as wad works perfectly though.

    also, i have some files in the root of my sd, which i didnt create myself: a folder called 00000001 (no idea where that came from), a boot.dol (priiloader?) and a key.bin (might be part of my nand backup, not sure). any ideas? might one of those cause the problem?


    EDIT: y, boot.dol is needed by priiloader. priiloader also has a hack for "cannot load channel". seems perfect, doesnt help though;(
     
  4. leondmsmith

    leondmsmith GBAtemp Regular

    Member
    256
    0
    Mar 20, 2009
  5. q9wert
    OP

    q9wert Member

    Newcomer
    17
    0
    Apr 8, 2010
    is this my only option? i dont really trust 4.2... i read that it makes things more complicated than they need to be.

    are there any solid disadvantages or advantages (beside the fact that hbc might be accessible through the system menu ofc) compared to 4.0? would i have a good chance of solving my problem, or is it just that upgrading is my only real option?
     
  6. q9wert
    OP

    q9wert Member

    Newcomer
    17
    0
    Apr 8, 2010
    bump
     
  7. TRushInfo

    TRushInfo Banned

    Banned
    978
    0
    Jun 13, 2009
    United States
    you read wrong. youll be just fine just do it. use the sticky guide update and rehack and stop bumping.
     
  8. q9wert
    OP

    q9wert Member

    Newcomer
    17
    0
    Apr 8, 2010
    should i do a simple or a complete update?
     
  9. House Spider

    House Spider In the GBAtemp attic.

    Banned
    1,282
    0
    Apr 25, 2009
    Dundalk
    I'd do a complete update.
     
  10. FenrirWolf

    FenrirWolf GBAtemp Psycho!

    Member
    4,347
    329
    Nov 19, 2008
    United States
    Sandy, UT
    4.2 is harmless. Waninkoko's 4.0 updater has a much greater chance of bricking you than 4.2 ever did. It's a good thing you installed or had previously installed a good IOS60 or you'd be toast.
     
  11. pimmeke

    pimmeke Member

    Newcomer
    10
    0
    Sep 14, 2009
    Belgium
    i've sort of the same problem.HBC won't start up from bootmii.from system menu and priiloader no problem but from bootmii only system menu starts up.luckily i can access it too from priiloader so i'm still kind of safe.wii is 4.0E.i updated iosses with pimp my wii 1.4.installed cios rev 19.anyone knows what the problem is?also red steel 2 won't start up.
     
  12. q9wert
    OP

    q9wert Member

    Newcomer
    17
    0
    Apr 8, 2010
    the update to 4.2 solved the problem for me, if thats any help to u.

    but id try to reinstall bootmii first.