We’ve developed a BootMii Compatibility Checker that we need as many people as possible to run on their Wii. This little utility will check your boot1 against a list of known versions and tell us if you have one that we haven’t seen. We’ve recently seen a few boot1 versions floating around that break BootMii so with your help we’re compiling a list of safe boot1’s to use in our installer so that you get a better quality BootMii.
Current stats: 428 reports of “normal” (compatible) boot1 (2cdd…), 22 reports of “variant 1″ (4a7c…) and 40 reports of what I was calling the “Korean boot1″ (f01e…). The latter will not be compatible with BootMii, and it looks like it’s not just Korean Wiis (or, as noted in the comments below, they could be region-changed Korean Wiis). Console IDs greater than 0x6000000 appear to be using the new “Korean” boot1, and the rest are using either the normal one or the variant.
What are you waiting for? Download and run Checker and do your part for BootMii.
Update: Checker will not work on Wiis running v3.4 of the System Menu, or version 3.3 with the October 23 IOS update, or if you have an updated IOS picked as default for libogc for whatever reason. Don’t worry, BootMii will run just fine on v3.4 when it’s released. DO NOT downgrade or do anything else just to get this to work. If it doesn’t work, it’s okay, we don’t need people doing dangerous things just to add a few extra data points.
Update: Marcan asked me to remind you that by running Checker you’re consenting to Checker sending your data about your Wii to us. Checker tells you about this when you run it, but apparently my WiFi sucks and takes longer to init than most people’s so you may not have time to read it all before it sends the info (we should have added an explicit delay there).
Update: Just to clarify Checker does not install anything on your Wii, it just collects your ConsoleID (this is used in exported save games), boot1 hash, boot2 version, region, video mode and the IOS version it’s running under and sends it back to us over Wifi. It does not peek at anything you may have installed on your Wii so you can put those tinfoil hats away now.
Update: We are in contact with the guy whose Wii has boot2 v4. Thanks everyone for helping to locate him (it was kind of scary at times) and also to the GBATemp mods for putting him in touch with us.
53 responses so far ↓
1 http://maikelsteneker.blogspot.com/ // Feb 16, 2009 at 7:21 am
I doubt this will help you (my Wii was bought on launch), but I just ran it. I can’t wait for the first real release
2 r1cola // Feb 16, 2009 at 7:24 am
Neato. So just rename to boot.elf or….?
Also, how bout an intro for youself? Dont rec the handle
3 http://maikelsteneker.blogspot.com/ // Feb 16, 2009 at 7:49 am
@ r1cola: just rename bootmii_check.elf to boot.elf and place it in any folder inside the apps folder on your SD card. Of course, you can also send it to the homebrew channel via WiFi.
4 sanderevers // Feb 16, 2009 at 8:09 am
I hope you guys release Bootmii before Nintendo comes with Wii firmware 4.0…
5 djdynamite123 // Feb 16, 2009 at 8:41 am
Hope this info helps you, iv’e done my bit hehe
Hope we get more updates regarding BootMii
6 linkinworm-c98 // Feb 16, 2009 at 9:26 am
wow, you really are trying to make this brickproof
i wonder how many guides people make to use this? lol(gbatemp pun)
7 Ghost5 // Feb 16, 2009 at 9:38 am
I’ve sent my info.
The process was pretty fast, I was expecting longer…
8 Fennec // Feb 16, 2009 at 10:17 am
Someone should post on wiibrew about this.
I’ll run the bootmii checker now.
9 Blue-K // Feb 16, 2009 at 10:55 am
I’ve also runned the Bootmii Checker (although I have a Wii that I bough at the launch day, so probably no new boot1…). But I think every little helps
.
10 Matando // Feb 16, 2009 at 11:07 am
Info Sent, You’re welcome and good luck
11 tech3475 // Feb 16, 2009 at 11:24 am
hope this helps you guys .
keep up the good work.
12 HCK // Feb 16, 2009 at 11:43 am
Submitted
I Hope this really helps you!
13 r1cola // Feb 16, 2009 at 11:46 am
@maikel thanks. How-to on the wifi load?
14 adr990 // Feb 16, 2009 at 11:58 am
Cool…
I will run it later.
Good to see this
Just awesome! ^_^
15 Apicio // Feb 16, 2009 at 12:03 pm
May we use it (both BootMii and BootMii Checker) even with Preloader installed?
16 tompccs // Feb 16, 2009 at 12:13 pm
I think a lot of people would feel more comfortable running this (myself included) if we could see the source. It’s not that I don’t trust you, just that the idea of sending data around over which I have little control concerns me. Sorry for being such an a**hole about this.
17 bdr9 // Feb 16, 2009 at 1:59 pm
Is it OK to convert it to a .dol for usage in HBC beta 9 and up?
18 Arm the Homeless // Feb 16, 2009 at 2:31 pm
You don’t need to convert it.
HBC beta9 and up work with ELFs.
Just not improperly made ELFs.
19 maddoc // Feb 16, 2009 at 2:32 pm
f01e could still be korean Wii’s but region changed!
Remember they got a modified Any Region Changer.
Anyway I submitted my boot1 (variant1).
20 Remadon // Feb 16, 2009 at 2:43 pm
Sent.
21 HCK // Feb 16, 2009 at 2:51 pm
@bdr9
That ELF is not malformed, you can run it on the latest HBC without problems.
22 WB3000 // Feb 16, 2009 at 3:20 pm
Worked flawlessly. I’m spreading the word at Nintendo-Scene, so you can add a few more results to your check.
Now that I think about it, I recall the hash starting with 4… I might have the variant 1? I would run the check again to make sure, but I don’t want to pollute the results.
23 adr990 // Feb 16, 2009 at 3:21 pm
tompccs
I was about to ask the source too…
But yeah…
I don’t care if they close the W@Ds…
(I’m not in VC/WW Pirating..)
We get cool tools anyways…
Also, done sending..
And a couple of my friends)
(On other forums I ask to let them run that Checker too
24 badkarma12 // Feb 16, 2009 at 3:42 pm
Only me and 3 other people have the variant so far?
25 Ezmegaz // Feb 16, 2009 at 4:06 pm
Sent, but can we see that our wii is compatible whit bootmii?
Any reply, or other elf that confirm whitout wisk, that our wii can run bootmii? Sorry for my bad english =)
26 vitaminj // Feb 16, 2009 at 4:26 pm
I was hoping to run this, but it complains that it can’t read /dev/flash, but I still have 3.2E. It says it’s running under IOS35 v12.16.
I did run the Wii Shop / IOS51 installer, and then used the shop to download an update to the Nintendo Channel – would that have sneaked in a patched IOS without telling me? Title Lister says HATP is using IOS35.
Is there a utility I can run to list and check the presence of signing bugs and/or patches in all IOSes? Or am I barking up the wrong tree?
Thanks for all the hard work!
27 ChuckBartowski // Feb 16, 2009 at 4:56 pm
aw man i wish it worked on 3.4. So why wont it work with 3.4
28 Ibrahim Awwal // Feb 16, 2009 at 5:32 pm
Hi, I had a similar situation as vitaminj. I’m on 3.3U (with I think the 10/23 update) and it says it can’t read /dev/flash because of 3.4. I also ran the Wii Shop upgrader so that might be the culprit. HBC reports that it’s running IOS36 v12.18. Anyway, hope this means bootmii is making good progress, and good luck!
29 caitsith2 // Feb 16, 2009 at 7:35 pm
If you have ever dumped your flash at any point, the first 0x20000 bytes of that flash (128KiB) is boot1, and that is what sha1 is calculated over. (This only applies if you did the non-ecc flash dump.)
30 GhostSonic // Feb 16, 2009 at 7:53 pm
You guys scared me with the red text, it came up after I logged on and I thought you were talking about me. Also it would be nice to see what version we had.
31 Remadon // Feb 16, 2009 at 7:53 pm
Oh wow, A Never-Before-Seen Boot2 Huh? Sounds interesting…
32 Summersett // Feb 16, 2009 at 8:17 pm
I did the Wii Shop Upgrade with IOS51 Installation, so I could still stay on 3.2U, and it still allowed me to submit my information. Throw that theory out.
33 ften // Feb 16, 2009 at 9:20 pm
Odd I got a f01e boot1 hash… I got my Wii at a US Target in June of last year. Never region changed it. Intresting, Intresting.
34 WiiLee // Feb 16, 2009 at 11:10 pm
I ran the installer so I did my part but if you have any testing positions available I would take a job, my Wii specs are:
SystemMenu 3.2U
CiosCorp
cMIOS rev3
Preloader 2.8
and I have experience downgrading
I am willing to take risks with my Wii and i have many recovery options in the case of a brick, so far i have never bricked
35 Hells_Guardian // Feb 17, 2009 at 11:12 am
I do believe I am the person you are looking for. I loaded the tool on a wii that belongs to a friend of mine. he got it less then a month ago and I guess you folks found something interesting. You can contact me via email at MKBechtold(at)Gmail.com
I’m sure a member of the team knows what i mean with the above address. I hope I can help. If not I will swap wiis for a bit with the individual. I have an older version that I’m sure you’ve seen the same of time and time again.
look forward to hearing from you if I’m the one you are looking for. OSW over at GBATemp had mentioned that my ip matched so I hope to help you.
36 noir // Feb 17, 2009 at 1:03 pm
I seem to have “Korean boot1.” I’m guessing this came from when Nintendo fixed my brick at the end of last year. When I got my Wii back, it came with System Menu 3.2 and all of the same old tricks still worked on it. What’s the point of changing boot1 if everything is still left vulnerable?
37 RobotMenace // Feb 17, 2009 at 1:11 pm
When I ran the checker I didn’t take any notice of the hash. I known it won’t squew your statistics as you’re collecting console ids as well, but I’d like to check it won’t get on anyones nerves if I do. ty
38 noir // Feb 17, 2009 at 1:51 pm
Do you guys know approximately when console IDs passed 0×60000000? Does the console ID change if Nintendo flashes to a new boot1?
39 dimok // Feb 17, 2009 at 3:37 pm
I got a european Wii and got f01e hash too
.
Will BootMii just not work on Wiis with this boot1 hash at the first release or will it never work on these Wiis?
40 HenshinMijin // Feb 17, 2009 at 5:02 pm
Nooo!! I failed you!
I wanted sooo badly to be able to help you guys out in any way I could. But I can’t even run the BootMii Checker on my Wii!
Is there ANYTHING else I could do?
fo shizzle
~K Dizzle™
41 FRanatic // Feb 18, 2009 at 12:20 am
Well, I did my part.
Now going back to waiting patiently for BootMii to get released…
I really am curious what this platform will brings us.
42 caitsith2 // Feb 18, 2009 at 5:07 am
Unfortunately, short of creating a SHA1 collision with an earlier boot1, the f01e version will never be compatible with bootmii.
(A sha1 is calculated over the first 0x18000 bytes of the flash, and boot1 in reality, only takes up 0x4320 bytes of that space. All the rest of that space is All 0x00, which means if one could force a sha1 collision in that zone, then boot1 could be overwritten. This is not likely to happen any time soon though.)
43 metroid maniac // Feb 18, 2009 at 1:34 pm
so all this does is gather the information and send it to you?
44 dimok // Feb 18, 2009 at 2:23 pm
Thanks for your answer caitsith2.
Too bad to hear that. Oh well i guess i gotta be carefull with my Wii.
45 WiiLee // Feb 18, 2009 at 7:20 pm
@dimok
we have high hopes but it does not look bright for the f01e, but you never know things change
I have a 2cdd
@metroid maniac
yes
46 qiantpune // Feb 18, 2009 at 10:01 pm
I just sent mine in. I sent it twice just to help you get BootMii done a little bit sooner.
47 locoss // Feb 19, 2009 at 2:08 am
I would love to help, but my menu is running a ver 3.4 so I cannot run it. But if I ever downgrade my wii I will do it
Just want to put a comment to say you guys are GREAT! You kick buts
I love to read your progress and enjoy your talk on the congress, especialy your slides crazy effects 
Keep it up! Greetings from Venezuela
48 alpha tauri // Feb 19, 2009 at 2:57 pm
It has been done on my 3.2U Console and apparently it ran smooth. I must add that I can’t wait to have bootMii installed on my console. Best regards from Brazil.
49 metroid maniac // Feb 20, 2009 at 6:48 am
does it work on variant 1?
50 mystrythng // Feb 20, 2009 at 2:54 pm
When I run it, it generates the hash fine, but gives me a network error -112 when it attempts to send it… I know the wireless is working on it (woo running stuff on the HBC off the computer), so dunno what its problem is. Is all you’re looking for the hash? Because I could just type that out manually…
51 Daverball // Feb 20, 2009 at 6:33 pm
yes it does, the korean one doesn’t work because it has the signing bug fixed, variant 1 is actually an even earlier version of boot1 than the one that most people have. Bushing made a comment on the next article about all the different boot1 versions.
52 Nemno // Feb 21, 2009 at 4:10 am
Send the info..
After a about 8 tries… most of the time i got net_init() failed: [-116]
I did got net_init failed at ftpii but that seems to be fixed with the new version 0.0.18, there the do a retry after the net_init() failed… and the retry does get a connection immediately.
I launch from HBC, a connection there doesn’t mean that the the net_init() works !?
No connection in HBC does not mean that the net_init (in ftpii) doesn’t connect :p
I assume the net_init() code is the same ios call in ftpii as it is in bootmii_check.
many thanks for hbc, and good luck/skill with bootmii,
Nemno
53 chuckthetekkie // Mar 3, 2009 at 10:59 pm
I tried to run boot checker but it crashes
You must log in to post a comment.