- Joined
- Sep 21, 2008
- Messages
- 850
- Trophies
- 0
- Location
- Somewhere in USA
- Website
- ironmaskshideout.blogspot.com
- XP
- 184
- Country
Well.. my opinion changed a little after yesterday's event. For obvious reasons. But I was still thinking that if you updated or used CIOSCorp on any other system menu version, you could still be screwed. Basically my setup has been CIOSCorp/Starfall/Preloader when ever I have installed a new system menu.wad I always go straight back into homebrew to "rearm" myself just for precautions.
I am going to do some more testing today with trying to figure out what it actually was that saved my ass from the terrible black screen of death. The thing that was weird was, when I got the black screen after returning to homebrew after installing the "newsystemmenu.wad" by IceFire...Using ARM's (thanks) Wad Manager-HBC return edition brought me safetly back in the my HBC. From there I went straight to preloader install screen, yet my install screen showed nothing but black screen. I was thinking, that maybe I had it on 480p resolution because sometimes that throws me a blackscreen using homebrew. (I wasn't, I checked after I recovered it was reg 480i setting) So the preloader install went screen black, never seeing the install screen. I waited...waited..waited... Ooops! was my response. I though to myself. I finally did it this time...
To continue this experience, I jumped back to the thread after knowing my Wii was "bricked" (so, I thought) a black screen was what I had. I turned my Wii off. Turned it back on. Black screen. Off, On. Black screen. Off, on while holding reset in. Nothing. (I only tried this out of hopefulness) By this time, I was in #wadder on efnet with IceFire.... My second attempt of response was to pull out my modified version of a gamecube controlled that I hadn't finished yet! So, I went to pull the plastic direction pad to file the middle down so I could try all 4 directions. LO and Behold! Trying to get the piece out I broke the GC controller main circuit board...Flail! (I was scrambling...yet still found it amusing!) I didn't want to embarrass myself and tell IceFire what I did, just yet... If I had only finished my JiizmoBlaster!
So...now I pondering I looked over at my other bucket o' controllers and ran my fingers through my long blackbeard and grabbed my generic unmodified,Purple Advanced GC Controller w/ fingerprint logo on it (if that helps). (Used at GameStop)... I inserted my Autoboot WAD manager disc patched to ios249 (I had patched it the 1st night of cioscorp testing when I originally chose to patch my system menu to 249 as well with Wiiblaster)...
I stuck the disc in while turning the Wii on and held Y on the GC controller in port 1.... No go. Tried one more time.... no go. I turned the Wii off... unplugged the GC controller and put it in the 4th port and held all directions on GC controller.... 3.2U showed up in bottom left corner of screen and then Wad Manager booted up... you obviously know what happened next....
Today, I am going to try and figure out how that exactly saved me...
I did reinstall preloader again, after reinstalling my native untouched systemmenu3.2(ntsc).wad and returning to HBC. After preloader installed I went to my system hacks settings and the ones enabled were still showing enabled and the ones disabled were showing disabled (GC region hacks that we have for preloader)
That tells me the hacks.ini was still alive in the NAND when I installed the corrupted system menu.wad
I am going to uninstall preloader and starfall and try my GC controller by itself with no hacks enabled just with CIOScorp alone and then work my way back.... I'd like to see exactly what saved my Wii...
Thanks for the support guys. And back to what I was really getting at... the reason my opinions of CIOScorp changed is because of the obvious ordeal. I still would not call this a safeway to park your Wii at.... especially if you plan to do future updates... We still don't know exactly what Ninty will throw at us...but I will say this... We always end up climbing out of the pile of rubbish when the smoke clears with new ideas! So this is only another mountain to climb in our journey to the ultimate Wii hack!
Sorry the message was so long... just wanted to share an interesting experience with how this whole thread has effected me. And I am sure it will help others learn.. because I really thought the all direction 4th port recovery feature was a myth..and it would never work on a non-chipped Wii.....well I just proved that theory wrong.
I am going to do some more testing today with trying to figure out what it actually was that saved my ass from the terrible black screen of death. The thing that was weird was, when I got the black screen after returning to homebrew after installing the "newsystemmenu.wad" by IceFire...Using ARM's (thanks) Wad Manager-HBC return edition brought me safetly back in the my HBC. From there I went straight to preloader install screen, yet my install screen showed nothing but black screen. I was thinking, that maybe I had it on 480p resolution because sometimes that throws me a blackscreen using homebrew. (I wasn't, I checked after I recovered it was reg 480i setting) So the preloader install went screen black, never seeing the install screen. I waited...waited..waited... Ooops! was my response. I though to myself. I finally did it this time...
To continue this experience, I jumped back to the thread after knowing my Wii was "bricked" (so, I thought) a black screen was what I had. I turned my Wii off. Turned it back on. Black screen. Off, On. Black screen. Off, on while holding reset in. Nothing. (I only tried this out of hopefulness) By this time, I was in #wadder on efnet with IceFire.... My second attempt of response was to pull out my modified version of a gamecube controlled that I hadn't finished yet! So, I went to pull the plastic direction pad to file the middle down so I could try all 4 directions. LO and Behold! Trying to get the piece out I broke the GC controller main circuit board...Flail! (I was scrambling...yet still found it amusing!) I didn't want to embarrass myself and tell IceFire what I did, just yet... If I had only finished my JiizmoBlaster!
I stuck the disc in while turning the Wii on and held Y on the GC controller in port 1.... No go. Tried one more time.... no go. I turned the Wii off... unplugged the GC controller and put it in the 4th port and held all directions on GC controller.... 3.2U showed up in bottom left corner of screen and then Wad Manager booted up... you obviously know what happened next....
Today, I am going to try and figure out how that exactly saved me...
I did reinstall preloader again, after reinstalling my native untouched systemmenu3.2(ntsc).wad and returning to HBC. After preloader installed I went to my system hacks settings and the ones enabled were still showing enabled and the ones disabled were showing disabled (GC region hacks that we have for preloader)
That tells me the hacks.ini was still alive in the NAND when I installed the corrupted system menu.wad
I am going to uninstall preloader and starfall and try my GC controller by itself with no hacks enabled just with CIOScorp alone and then work my way back.... I'd like to see exactly what saved my Wii...
Thanks for the support guys. And back to what I was really getting at... the reason my opinions of CIOScorp changed is because of the obvious ordeal. I still would not call this a safeway to park your Wii at.... especially if you plan to do future updates... We still don't know exactly what Ninty will throw at us...but I will say this... We always end up climbing out of the pile of rubbish when the smoke clears with new ideas! So this is only another mountain to climb in our journey to the ultimate Wii hack!
Sorry the message was so long... just wanted to share an interesting experience with how this whole thread has effected me. And I am sure it will help others learn.. because I really thought the all direction 4th port recovery feature was a myth..and it would never work on a non-chipped Wii.....well I just proved that theory wrong.