Hacking System Menu questions/thoughts

  • Thread starter Thread starter OSW
  • Start date Start date
  • Views Views 168,134
  • Replies Replies 1,572
Matt93 said:
Alright, I have to install this. Can someone please PM me the link to WiiBlaster's cIOS download pack and also cIOS 16? I don't think he is online right now. I of course know the risks, complications, etc... I've been following this the whole way.

Also, could someone could give me all of the original IOS'es as well? I need them because i doubt my Wii is a genuine 3.2U.


I can't believe the discoveries that have been happening in the past few days. Backups natively running from the Disk channel without a modchip? That was once unthinkable, and now we have it within a few days from the idea that started this! I may not ever have to use a loader again. All of my backups are NTSC. This is definitely the best thread I have followed since I've been a member at GBAtemp. Thank you for all who have contributed to this project!


Multi_cIOS installer, that's all you need and the cIOS30 cause this doesn't allow you to screw your Wii...!!!
biggrin.gif
 
ether2802 said:
Matt93 said:
Alright, I have to install this. Can someone please PM me the link to WiiBlaster's cIOS download pack and also cIOS 16? I don't think he is online right now. I of course know the risks, complications, etc... I've been following this the whole way.

Also, could someone could give me all of the original IOS'es as well? I need them because i doubt my Wii is a genuine 3.2U.


I can't believe the discoveries that have been happening in the past few days. Backups natively running from the Disk channel without a modchip? That was once unthinkable, and now we have it within a few days from the idea that started this! I may not ever have to use a loader again. All of my backups are NTSC. This is definitely the best thread I have followed since I've been a member at GBAtemp. Thank you for all who have contributed to this project!


Multi_cIOS installer, that's all you need and the cIOS30 cause this doesn't allow you to screw your Wii...!!!
biggrin.gif
Does this include all the IOS's?
 
is the installer only, you can make it install cIOS33 - 36 - 37 - 55 in any place between 249 and 9, except for IOS30, so you get to choose wich ones you want them DIP7'd and wich ones don't, one at a time...!!!
smile.gif
 
digitydogs said:
glancing at the listings above id say no it misses a few

All of the IOS are patched with dip7. They just look different in the listing becasue some were done differently. Some are original IOS patched with dip7 while others are copies of cIOS36dip7 patched to the lower 9-22 i think IOS.
 
ether2802 said:
and I'm still wondering why da' f**ck Starfall doesn't region free the discs
hate2.gif

this may have been answered already, but it's late and I have to get up for work in a few hours so I don't feel like going back through the posts. Has anyone checked to see that the rest of starfall features are working? Most notably, the rescue-menu.

Edit: i don't \have a GC controller to try....
 
An interesting process with interesting results, specifically the ability to run autoboot software discs without a chip. Too bad it takes messing around with the system menu IOS without a means to recover if shit goes sideways... something I'm certainly not up for doing. Maybe when BootMii and according recovery methods come along.

And while certainly less dangerous than messing about with IOS30, the prospect of replacing the rest of the system's IOS base with modified (DIP'd) versions just to load backups from the disc channel also isn't very appealing. Then again, I've just plain never understood the fascination with disc channel loading, but I guess some people really must love those animated disc banners and legit entries in the daily activity log.


Regardless, a good read. Cheers to the folks who tried it. And sincere hope for the success of others who will attempt it.
smile.gif
 
The list of IOSes from WiiBrew:

IOS History
From WiiBrew
Jump to: navigation, search
This page is intended to track changes in IOS ( the operating system that runs on Starlet) such as: added features, bug fixes, etc.

It will also cover what different minor versions are known to exist.




Major Minor(s) Version Number(s) Notes
IOS4 0.3 v3 only has minimal drivers; possibly used during manufacturing and/or updating
IOS9 2.4 v516, v520 Has only one LED pattern: blinking. first "normal" IOS version
IOS11 0.10 v10, v256 Internal timestamp says Nov 14 2006 16:26:01
IOS12 0.6 v6, v11
IOS13 0.10 v10, v15
IOS14 1.1 v262
IOS15 1.1, 1.4 v260 contains NAND BOOT PROGRAM (NUS gives a 401 error on download attempt)
IOS16 only used for Wii Backup Disc
IOS17 2.0 v512, v517
IOS20 0.12 v12, v256 Feb 22 2007 04:25:59
IOS21 2.2, 2.5 v514, v515, v516, v517, v522 contains NAND BOOT PROGRAM. most debugging messages are removed.
IOS22 3.4 v777
IOS28 5.8 v1288
IOS30 4.15, 4.16 v1037, v1039, v1040 starting with IOS30, firmware is divided into 15 modules. Added USB Keyboard support.
IOS31 4.15, 4.16 v1037, v1039, v1040
IOS33 4.16 v1040
IOS34 4.15 v1039
IOS35 4.16 v1040
IOS36 4.18 v1042
IOS37 8.22 v2070 first to fix the signature-checking function bug (NUS gives a 401 error on download attempt)
IOS38 14.19 Introduced with Animal Crossing: City Folk. Not yet analyzed but may have something to do with WiiSpeak. (Not on NUS)
IOS50 distributed along with and used by System Menu 3.4
IOS51 used by new Shop Channel. released at same time as fixes to remaining fakesigning bugs
IOS53 comes with Need for Speed Undercover
IOS55 comes with Need for Speed Undercover. Seems to have changes in the DI Module. Loading the game with geckoos produces error #002. It can be an update for the new wireless USB Driving Wheel from Logitech, supported only by Need for Speed: Undercover.
IOS254 v2 distributed along with System Menu 3.4, copy of IOS9

Retrieved from "http://wiibrew.org/wiki/IOS_History"

1) I shouldn't have to worry about IOS 4, if I am correct, as ether's Multi installer only works from 9 to 249.
2) I assume (read: KNOW) that I shouldn't overwrite IOS30 (not that the installer would let me).
3) Anyone tried to update while doing this? It seems like the only thing untested.
4) Read through the thread (AND SEARCHED!
tongue.gif
), but couldn't find if downgraded Wiis (3.3 U -> 3.2 U) would be OK.
5) Just to be sure, IOS254 and IOS55 should be fine to overwrite, if I am correct.
6) What's the outlook on Trucha-signed Rock Band? That's what I'm concerned about.

Thank you, GBATemp!
-SFenton
 
telefunkin said:
ether2802 said:
and I'm still wondering why da' f**ck Starfall doesn't region free the discs
hate2.gif

this may have been answered already, but it's late and I have to get up for work in a few hours so I don't feel like going back through the posts. Has anyone checked to see that the rest of starfall features are working? Most notably, the rescue-menu.

Edit: i don't \have a GC controller to try....

All of starfall options except region free are working as far as i know. I use Recovery mode to boot games direct in fact.
 
I'm gonna test this now I'll report back when I'm done.

Edit- Ok add me to the list of permanently softmodded wii. I put the IOS wads on my SD card went to Wad manager installed from IOS 9 and went all the way down to IOS 55 rebooted and all was well tried a few backups they worked. I'm on 3.2U and now I'm going to re install Starfall.
 
thawkins1 said:
I'm gonna test this now I'll report back when I'm done.

Edit- Ok add me to the list of permanently softmodded wii. I put the IOS wads on my SD card went to Wad manager installed from IOS 9 and went all the way down to IOS 55 rebooted and all was well tried a few backups they worked. I'm on 3.2U and now I'm going to re install Starfall.

i didnt even have to reinstall starfall
 
OK guys, something really really cool here I have for you courtesy of Pelican Gamecube Wireless Controller.

Be patient with me here as I'll be kinka long winded explaining, but the end result is fantastic!

In my earlier ramblings I mentioned how I was going to make a gamecube controller into an autoboot dongle. Well the results turned out way better than I imagined.

I decided to use the Pelican Wireless because it has regular phillips screws and lets me have my auto boot switch moveable.

1. So I disassembled and put a dime on top of the Y button's rubber pressure pad and made it secure down with a big fat rubber band. So now the Y key is permanent pressed down.

2. I put the wireless receiver into gamecube port 1.

3. I turn on wireless controller and the sync lights indicate sync on both the receiver/transmitter.

At this point i expect that when i turn on the Wii it will boot into recvery mode and boot the game backup I have in the drive. This proves correct.

4. I do a return to Wii Menu command to exit the game expecting the Wii to just reboot the game, because the Y key is still active on the GC controller. This proves correct as the game just exits and recovery mode starts over and game reloads.

At this point I decide I have to turn off the GC controller now to get out of autoboot mode.

5. I turn off the GC controller. LED goes off, and light on wireless receiver starts blinking as expected. Now i exit the game with the Home button to exit to system menu expecting it to now go to system menu. BUT NO!!! It reboots to recovery mode again and boots the game. So the light goes off in my head. The receiver is keeping it's state to that it was in when communications were lost to it, so now it's still putting out the signal Y is held down.

At this point I'm thinking this is Kinda cool, but I don't want to have to unplug the unit from the GC port every time to disable autoboot. So I decide I'll just turn off the Wii to reset it.

6. I turn off the Wii. Monitor goes blank. No Video Signal. I Turn the Wii back on for it to boot to system menu, BUT NO! The wireless receiver is still stuck in Y pressed mode even after the wii was turned off.

***** Now this is where the really cool part comes in *****

I decide now that well, I'll just have to unplug the unit and do a different approach with a wired controller instead of this wireless one. And BANG, the miracle happens.

7. I reach to unplug the wireless receiver from the first gamecube port and I notice which i had never had to use before with it, a small pushbutton switch beside the flashing sync light. It's a small connect button easily found and pressed with a light finger tough. And I say to myself, I bet this button will also reset the state of the receiver. I press it and then do a reset on the Wii and Bingo! it boots to System Menu

So to sum up....

I put temporary contact pushbutton switch across the power switch contacts on the wireless remote and mounted the guts into small utility box. All I have to do is Hold down the Pushbutton until the SYNC light goes solid. At that point Y key press is sent to receiver. I release the Pushbutton and Wii is now in Recovery/Autoboot mode until I press the Connect button on the wireless receiver, which is noting more than a small black 1.5 inch by 2 inch module sitting on top of the wii plugged into GC port 1.

There is no way possible that this could have worked out any better. 1 Button push to put unit into autoboot till reset button on autoboot dongle is pressed. And when I bought this controller at Wal-Mart about a year ago it was 14.95 I think. I just can't believe how remarkably convenient the receiver's state memory and connect button combination worked out. Cool thing is too that if I never activate it's apparently also 100% transparent. Also because wireless also drains batteries it's cool that I only have the battery powered controller on for about 2 seconds, just long enough to establish the connection between controller and receiver. So battery should never be an issue.

I can't say how other controllers would work out for this application, but I got lucky and the one I have is perfect! I think the big issue will be if other receiver modules keep their state when the controller/transmitter is turned off.

As Final Note this is what it allows me to do. And I just did a timing test to confirm.

From my Wii being in a powered off state. I press my JiizBlaster button for about 1.25 to 1.5 seconds to activate it.
I insert backup into Wii drive and the Wii turns itself on and boots directly into game in a matter of about 10-20 seconds (depending on the game) until the Strap Warning screen appears. I'm now in game autoboot mode until iItouch the reset button on the GC Port Dongle!
smile.gif


EDIT: As an afterthought I just realized that of course it also acts as a simple pushbutton activatate starfall recovery mode system with autoboot wadmanager or twilight princess in drive instead of game backup.
 
Slimmmmmm said:
JizBlaster sounds like you just shot your load
tongue.gif


Did you ?

Nearly, I was not expecting such good results. Nor it to be so damn easy. And it's JiizBlaster. Or maybe I should rename because that is kinda seedy sounding.

I didn't even consider trying this autobooter till WiiBlaster and company busted open the whole Disc Channel/IOS shebang.
I originally was thinking of Recovery Mode as a last resort to recover from a banner brick, then the more I thougt about it the more I saw it as nothing but another system boot loader. Regardless whether or not it was designed to be used that way, it's not bad for it as far as I can see, it's simply a computer booting a disc. And it's not doing anything to the nand or important OS files in any way as far as I think. So why not just exploit it. Recovery mode's ability to boot autoboot homebrew, games, whatever is quite a good interceptor of the OS before System Menu. I simply chose to exploit it to make a convenient Game Autobooter/Recovery Mode hardware hack.
 
Well....that's definately some good stuff to hear!
smile.gif

I have a broke up GC controller I still need to solder back together... I may use that for now until I come across one of those Logitech's (should we buy some stock in Logitech!?)
laugh.gif


Anyways... I gotta get my ass to work so I can afford the electricity to power all these toys!


I still think this is awesomely weird... What the hell were we waiting for?!
blink.gif


***Kids what you've just seen in this thread is not a joke ! These acts were done by professional Nintendo StuntMen.... PLEASE DO NOT TRY THIS AT HOME! Your parents will ground you for a month!

*Nintendo and the Wii Stuntmen are not responsible for your Wii bricking.
 
I Dont think anybody was really waiting, we were just distracted playing all the new games that came out for christmas and happy to be making our own WADs and stuff like that. Then you remember the boring week or so where nothing of any real interest at all happened. Once we had all our pretty Wii-Dumper Dump Truck Channels and Pretty FTPii channels and almost all backups running it didn't take long to get bored. So you had on your hands a buncha hackers/coders/testers and whatever who hadn't made any changes to their Wii in about a week. It was like an orgasmic rush of new challenge when OSW and WiiPower thought this up and Blaster pushed it forward. And then of course IronMask puts on his blindfold and runs out into traffic! The rest is history.
 
Ok - Tested on Pal with preloader and workin fine - Anyone who is using this setup on PAL should have it installed in my view - it all works like it should.

Im going to try autobooting some dols now to see what the outcome is.
 
QUOTE said:
could you also make a savemiifrii dongle by putting solder on the d pad buttons?
i can get generic gc pads for $5 near my house if so i might have to make one.


5 BUCKS!! Lucky you! I'd like to get a GC controller but there isn't any for sell here(where I live) so i got to buy one online... I got a question about autobooting discs; If I use the 00 HEX trick on an ISO, wii it autoboot?

EDIT: As I said before, I got Starfall on a 3.2U Wii and everything works fine! :

EDIT2: Nobody answered my other question either: If your installation fells and you brick your Wii, what kind of brick is it?
 

Site & Scene News

Popular threads in this forum