Page 4 of 17 FirstFirst ... 2345614 ... LastLast
Results 31 to 40 of 167

Thread: No Vulnerable IOS found, fix tested on 2 consoles so far

  1. #31
    New Member
    Join Date
    Sep 2009
    Posts
    105
    Thanks
    0
    Thanked 36 Times in 20 Posts
    Quote Originally Posted by kungpow12345 View Post
    When I downloaded my WADs, I was using NUSDownloader so I didn't have an option to do the sig hash check when I installed them using WAD Manager.

    So what I'm gathering, I'm assuming I need to reinstall IOS36-64-3351 from this tutorial with version 1042? Will that fix the black screen with hbc? I know others have reinstalled it and that seemed to fix it for them but they were using the beta9 installer. I'm assuming this is with preloader and the 4.2U Hacks engaged?

    The tutorial from gbatemp mentioned reinstalling a few other IOSes including 249 so I'm not sure which path to take right now. I would much rather get the backups back if all possible.
    DO NOT INSTALL LOWER VERSIONS.....sorry for the caps, I have had 3 ppl report bricks by doing so......as far as I know, you want to download the latest version using NUS. Can anyone confirm this is truly the case?

  2. #32
    Junior Member
    Join Date
    Oct 2009
    Posts
    11
    Thanks
    2
    Thanked 1 Time in 1 Post
    I still wish I knew why those other IOSes errored out. I did exactly what your tutorial said but seeing the HBC load with a black screen is definitely puzzling for me. If I remember correctly, when it's showing a black screen that's because it doesn't have the correct IOS to "draw" something on screen right? The same reason why the Backup Channel isn't working with the current IOS249? (I think at this point it's still Nintendo's stub)

  3. #33
    New Member
    Join Date
    Sep 2009
    Posts
    105
    Thanks
    0
    Thanked 36 Times in 20 Posts
    I had that happen to me before, I was sure it had something to do with the fact I had cioscorp at some point, I did an official update to the console to 4.2u. In my case I was lucky, it deleted all my stuff, I reinstall HBC and it worked. Then I followed various tuts for uninstallinig 222,223,249 and one other I cant remember, and reinstalling them.
    I would get the black screen for everything, hbc, wadmanager, the only thing that worked for me was preloader, I was on system 4.1 when this happened. I updated to 4.2 it was fixed, I broke it again(duh) updated again, an left well enough alone.


    I dont know if this info will help you, some ppl are reporting bricks using the official update, I didn't brick luckily. I know there is a 4.2 safe updater out there....

  4. #34
    New Member
    Join Date
    Sep 2009
    Posts
    105
    Thanks
    0
    Thanked 36 Times in 20 Posts
    I had that happen to me before, I was sure it had something to do with the fact I had cioscorp at some point, I did an official update to the console to 4.2u. In my case I was lucky, it deleted all my stuff, I reinstall HBC and it worked. Then I followed various tuts for uninstallinig 222,223,249 and one other I cant remember, and reinstalling them.
    I would get the black screen for everything, hbc, wadmanager, the only thing that worked for me was preloader, I was on system 4.1 when this happened. I updated to 4.2 it was fixed, I broke it again(duh) updated again, an left well enough alone.


    I dont know if this info will help you, some ppl are reporting bricks using the official update, I didn't brick luckily. I know there is a 4.2 safe updater out there....

  5. #35
    Junior Member
    Join Date
    Oct 2009
    Posts
    11
    Thanks
    2
    Thanked 1 Time in 1 Post
    I'm probably going to sound like a total noob here but cios corp from my reading is a WAD Manager but you can patch IOSes with it too. I know for 249, it downloads ios30(?) and then patches itself to be IOS249. ...is there anyway to find out if you still have any cIOSes still on your system or not? perhaps through dop-ios? Maybe if I got rid of them, it'd act right.

    So currently on your 4.2U what did you managed to get working after all that you did below? (Ie. HBC, DVDX, Backups, etc?)

    Quote Originally Posted by pccfatman View Post
    I had that happen to me before, I was sure it had something to do with the fact I had cioscorp at some point, I did an official update to the console to 4.2u. In my case I was lucky, it deleted all my stuff, I reinstall HBC and it worked. Then I followed various tuts for uninstallinig 222,223,249 and one other I cant remember, and reinstalling them.
    I would get the black screen for everything, hbc, wadmanager, the only thing that worked for me was preloader, I was on system 4.1 when this happened. I updated to 4.2 it was fixed, I broke it again(duh) updated again, an left well enough alone.


    I dont know if this info will help you, some ppl are reporting bricks using the official update, I didn't brick luckily. I know there is a 4.2 safe updater out there....

  6. #36
    New Member
    Join Date
    Sep 2009
    Posts
    105
    Thanks
    0
    Thanked 36 Times in 20 Posts
    Well, I'm not sure about finding out what cIOS files are on your Wii, I have read in alot of places that removing any IOS under 200 will brick your Wii so I would suggest not doing so.....cioscorp is BAD.....especially for novices. As far as I can tell it gets you into more trouble than its worth.

    I got everything to work that I had on 4.1 except preloader and bootmii as boot2

    HBC, Dvdx and bootmii as IOS, Backups through Neogamma, GC through GC Backup launcher, USB through Configurable USB Loader, usb loader gx and various others, mplayer
    Homebrew browser just errors out for me lately, not sure why, happens on both Wii's one on 4.2 and one still on 4.1 LU65 and LU37.

    Ummm Wii64 works great.....the only major difference is bootmii and preloader that I can see.....and Until I can get those, my hacking on that particular will will stop as it no longer has and type of brick protection without them

  7. #37
    Junior Member
    Join Date
    Oct 2009
    Posts
    11
    Thanks
    2
    Thanked 1 Time in 1 Post
    Well I know I never used cioscorp the program but I have used cIOS files to enable mplayer ce (DVD version) and the Backup channel to work but now thanks to the 4.2U update, it's now a stub.

    Do you happen to know if the IOS that HBC or any other program uses to install itself matters wither or not you get a black screen? Or do they use a specific one or two in order to work? Also would you advise installing the cios files or regular ios files you mentioned before? (222,223,249)

    Quote Originally Posted by pccfatman View Post
    Well, I'm not sure about finding out what cIOS files are on your Wii, I have read in alot of places that removing any IOS under 200 will brick your Wii so I would suggest not doing so.....cioscorp is BAD.....especially for novices. As far as I can tell it gets you into more trouble than its worth.

    I got everything to work that I had on 4.1 except preloader and bootmii as boot2

    HBC, Dvdx and bootmii as IOS, Backups through Neogamma, GC through GC Backup launcher, USB through Configurable USB Loader, usb loader gx and various others, mplayer
    Homebrew browser just errors out for me lately, not sure why, happens on both Wii's one on 4.2 and one still on 4.1 LU65 and LU37.

    Ummm Wii64 works great.....the only major difference is bootmii and preloader that I can see.....and Until I can get those, my hacking on that particular will will stop as it no longer has and type of brick protection without them

  8. #38
    New Member
    Join Date
    Sep 2009
    Posts
    105
    Thanks
    0
    Thanked 36 Times in 20 Posts
    You are getting into areas beyond my knowledge, i don't yet fully understand all of the IOS files and what each is used for......So far I know that until v4.2 249 was the IOS that most wads were installed from and most games used to boot, with some exceptions of 222/223 that were patched, like 223-mload for guitar hero 5 and such(i think that was it), as of system 4.2 N has made IOS249 a stub to block homebrew and switched the sysmenu from IOS60 to IOS70. It is my understanding you have you uninstall IOS249 and reinstall it to remove N's stub and put cios rev14 back on it. I dont have instructions on how to do it as I have decided to leave well enough alone on my console till I have more solid info.....I have alot of reading to do b4 I mess with anything else Stupid N, what were they thinking....stop homebrew, really........stop it for what, 2 hours, lolz

  9. #39
    Junior Member
    Join Date
    Oct 2009
    Posts
    11
    Thanks
    2
    Thanked 1 Time in 1 Post
    I guess my course of action now is to try to reinstall HBC, then reinstall cios 249, unless anyone else has any other suggestions?

  10. #40
    Junior Member
    Join Date
    Sep 2009
    Posts
    11
    Thanks
    0
    Thanked 3 Times in 2 Posts

    Smile

    well after alot of reading, testing and breakthroughs, i have 4.2 running the exact same way i had 4.1 running. I've also succesfully got my virgin wii 4.2 working aswell with everything except bootmi unfortuantly.


    on my previously softmodded console. i updated via waninkoko's updater.

    then installed cioscorp 3.4. then to make it work i had to us fstoolbox to patch the system menu's tmd to use ios60 instead of ios70. the ios60 is of course the patched one from cioscorp so all my backups boot via disc channel now.

    pre loader then installed the usual way and using system menu hacks for 4.2 available on wiibrew. and because i upgraded via waninkoko uprgrader boot2 was untouched so i still have a fully functional bootmii.

    if this info is helpful pm me , or if you need any help

Page 4 of 17 FirstFirst ... 2345614 ... 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
  •