Hacking HackMii Installer v0.2 RELEASED!

[kedest]

ah... i just had a DUH DUH moment... i dont have enough space on the SD card to make a backup, so it freezes

there should be a message at least ttat tells you... maybe in beta 3 XD

also, kedest, whats boot delay do?

You can set bootmii to autoboot to hbc or wii menu. In the first release, it waited 5 seconds before doing that (so can you use the bootmii menu itself)
Now you can change it to a specified number of seconds

 

[oxMUDxo]

I installed BootMii 0.2 and the New HomeBrew Channel over the old ones WITH NO PROBLEMS!!!
I just wanted to know how to set the autoboot..?

This is my boot me config file..

# BootMii config file

# Video mode, possible settings:
# NTSC, PAL50, PAL60, PROGRESSIVE
VIDEO=NTSC

# Autoboot, possible settings:
# SYSMENU, HBC
#AUTOBOOT=SYSMENU

Do I change something in there?

THANKS, WiiMan123
BootMii 0.2 seems farter..

 

[keyra]

mine looks like that
# BootMii config file

# Video mode, possible settings:
# NTSC, PAL50, PAL60, PROGRESSIVE
VIDEO=PROGRESSIVE

# Autoboot, possible settings:
# SYSMENU, HBC
#AUTOBOOT=SYSMENU

# Autoboot delay, in seconds:
# Default is 5
#BOOTDELAY=5


Posts merged

removed # in front of autoboot and bootdelay and ... voila ! it launches sysmenu

 

[oxMUDxo]

Humm, I missing the last 3 lines..

# Autoboot delay, in seconds:
# Default is 5
#BOOTDELAY=5

Guess I'll add them to see if that is it?

 

[Skater4599]

Quick question on the new autoboot delay feature, if you set it to 0 so it loads instantly into system menu, is the only way to get back into bootmii to change the delay on the sd card again or can you do somthing like preloader did and hold reset for it to pop up?

Also, i havnt installed bootmii yet but is it worth installing as both boot2 and as an ios? is there any real benefits to this as my wii can install as boot2 w/o probs

 

[cojiro]

Quick question on the new autoboot delay feature, if you set it to 0 so it loads instantly into system menu, is the only way to get back into bootmii to change the delay on the sd card again or can you do somthing like preloader did and hold reset for it to pop up?

Also, i havnt installed bootmii yet but is it worth installing as both boot2 and as an ios? is there any real benefits to this as my wii can install as boot2 w/o probs

if possible, as boot2 is better, it allows for you to recover from bricks. you can install both, but there is no need for as ios if you have it as boot2

 

[sm32]

so i'm having issues installing bootmii and i was hoping someone here could help me out. i'm on a 3.3u system and have usb loader and a bunch of other things working. i was trying to do an install to boot2 and it said it shouldn't have any issues. here's the complete log installer file:

Spoiler

HackMii v0.2 installer starting up
PVR = 00087200
183 titles are installed
Found IOS 222: revision: 0x1*
Found IOS 250: revision: 0xffff*
Found IOS 53: revision: 0x1011.
Found IOS 249: revision: 0xa*
Found IOS 37: revision: 0x816.
Found IOS 36: revision: 0x412.
Found IOS 28: revision: 0x508.
Found IOS 22: revision: 0x304.
Found IOS 14: revision: 0x101.
Found IOS 35: revision: 0x410.
Found IOS 33: revision: 0x410.
Found IOS 34: revision: 0x40f.
Found IOS 31: revision: 0xa10.
Found IOS 30: revision: 0xa10.
Found IOS 20: revision: 0xc.
Found IOS 17: revision: 0x200.
Found IOS 15: revision: 0x104.
Found IOS 13: revision: 0xa.
Found IOS 12: revision: 0x6.
Found IOS 11: revision: 0xa.
Found IOS 21: revision: 0x205.
Found IOS 2: revision: 0x161.
Found IOS 9: revision: 0x204.
Found IOS 4: revision: 0x3.
WARNING: ECC failure at page 138
WARNING: ECC failure at page 139
WARNING: ECC failure at page 140
WARNING: ECC failure at page 141
WARNING: ECC failure at page 142
WARNING: ECC failure at page 143
WARNING: ECC failure at page 144
WARNING: ECC failure at page 145
WARNING: ECC failure at page 146
WARNING: ECC failure at page 147
WARNING: ECC failure at page 148
WARNING: ECC failure at page 149
WARNING: ECC failure at page 150
WARNING: ECC failure at page 151
WARNING: ECC failure at page 152
WARNING: ECC failure at page 153
WARNING: ECC failure at page 154
WARNING: ECC failure at page 155
WARNING: ECC failure at page 156
WARNING: ECC failure at page 157
WARNING: ECC failure at page 158
WARNING: ECC failure at page 159
WARNING: ECC failure at page 160
WARNING: ECC failure at page 161
WARNING: ECC failure at page 162
WARNING: ECC failure at page 163
WARNING: ECC failure at page 164
WARNING: ECC failure at page 165
WARNING: ECC failure at page 166
WARNING: ECC failure at page 167
WARNING: ECC failure at page 168
WARNING: ECC failure at page 169
WARNING: ECC failure at page 170
WARNING: ECC failure at page 171
WARNING: ECC failure at page 172
WARNING: ECC failure at page 173
WARNING: ECC failure at page 174
WARNING: ECC failure at page 175
WARNING: ECC failure at page 176
WARNING: ECC failure at page 177
WARNING: ECC failure at page 178
WARNING: ECC failure at page 179
WARNING: ECC failure at page 180
WARNING: ECC failure at page 181
WARNING: ECC failure at page 182
WARNING: ECC failure at page 183
WARNING: ECC failure at page 184
WARNING: ECC failure at page 185
WARNING: ECC failure at page 186
WARNING: ECC failure at page 187
WARNING: ECC failure at page 188
WARNING: ECC failure at page 189
WARNING: ECC failure at page 190
WARNING: ECC failure at page 191
WARNING: ECC failure at page 192
WARNING: ECC failure at page 193
WARNING: ECC failure at page 194
WARNING: ECC failure at page 195
WARNING: ECC failure at page 196
WARNING: ECC failure at page 197
WARNING: ECC failure at page 198
WARNING: ECC failure at page 199
WARNING: ECC failure at page 200
WARNING: ECC failure at page 201
WARNING: ECC failure at page 202
WARNING: ECC failure at page 203
WARNING: ECC failure at page 204
WARNING: ECC failure at page 205
WARNING: ECC failure at page 206
WARNING: ECC failure at page 207
WARNING: ECC failure at page 208
WARNING: ECC failure at page 209
WARNING: ECC failure at page 210
WARNING: ECC failure at page 211
WARNING: ECC failure at page 212
WARNING: ECC failure at page 213
WARNING: ECC failure at page 214
WARNING: ECC failure at page 215
WARNING: ECC failure at page 216
WARNING: ECC failure at page 217
WARNING: ECC failure at page 218
WARNING: ECC failure at page 219
WARNING: ECC failure at page 220
WARNING: ECC failure at page 221
WARNING: ECC failure at page 222
WARNING: ECC failure at page 223
WARNING: ECC failure at page 224
WARNING: ECC failure at page 225
WARNING: ECC failure at page 226
WARNING: ECC failure at page 227
WARNING: ECC failure at page 228
WARNING: ECC failure at page 229
WARNING: ECC failure at page 230
WARNING: ECC failure at page 231
WARNING: ECC failure at page 232
WARNING: ECC failure at page 233
WARNING: ECC failure at page 234
WARNING: ECC failure at page 235
WARNING: ECC failure at page 236
WARNING: ECC failure at page 237
WARNING: ECC failure at page 238
WARNING: ECC failure at page 239
WARNING: ECC failure at page 240
WARNING: ECC failure at page 241
WARNING: ECC failure at page 242
WARNING: ECC failure at page 243
WARNING: ECC failure at page 244
WARNING: ECC failure at page 245
WARNING: ECC failure at page 246
WARNING: ECC failure at page 247
WARNING: ECC failure at page 248
WARNING: ECC failure at page 249
WARNING: ECC failure at page 250
WARNING: ECC failure at page 251
WARNING: ECC failure at page 252
WARNING: ECC failure at page 253
WARNING: ECC failure at page 254
WARNING: ECC failure at page 255
WARNING: ECC failure at page 320
WARNING: ECC failure at page 321
WARNING: ECC failure at page 322
WARNING: ECC failure at page 323
WARNING: ECC failure at page 324
WARNING: ECC failure at page 325
WARNING: ECC failure at page 326
WARNING: ECC failure at page 327
WARNING: ECC failure at page 328
WARNING: ECC failure at page 329
WARNING: ECC failure at page 330
WARNING: ECC failure at page 331
WARNING: ECC failure at page 332
WARNING: ECC failure at page 333
WARNING: ECC failure at page 334
WARNING: ECC failure at page 335
WARNING: ECC failure at page 336
WARNING: ECC failure at page 337
WARNING: ECC failure at page 338
WARNING: ECC failure at page 339
WARNING: ECC failure at page 340
WARNING: ECC failure at page 341
WARNING: ECC failure at page 342
WARNING: ECC failure at page 343
WARNING: ECC failure at page 344
WARNING: ECC failure at page 345
WARNING: ECC failure at page 346
WARNING: ECC failure at page 347
WARNING: ECC failure at page 348
WARNING: ECC failure at page 349
WARNING: ECC failure at page 350
WARNING: ECC failure at page 351
WARNING: ECC failure at page 352
WARNING: ECC failure at page 353
WARNING: ECC failure at page 354
WARNING: ECC failure at page 355
WARNING: ECC failure at page 356
WARNING: ECC failure at page 357
WARNING: ECC failure at page 358
WARNING: ECC failure at page 359
WARNING: ECC failure at page 360
WARNING: ECC failure at page 361
WARNING: ECC failure at page 362
WARNING: ECC failure at page 363
WARNING: ECC failure at page 364
WARNING: ECC failure at page 365
WARNING: ECC failure at page 366
WARNING: ECC failure at page 367
WARNING: ECC failure at page 368
WARNING: ECC failure at page 369
WARNING: ECC failure at page 370
WARNING: ECC failure at page 371
WARNING: ECC failure at page 372
WARNING: ECC failure at page 373
WARNING: ECC failure at page 374
WARNING: ECC failure at page 375
WARNING: ECC failure at page 376
WARNING: ECC failure at page 377
WARNING: ECC failure at page 378
WARNING: ECC failure at page 379
WARNING: ECC failure at page 380
WARNING: ECC failure at page 381
WARNING: ECC failure at page 382
WARNING: ECC failure at page 383
WARNING: ECC failure at page 394
WARNING: ECC failure at page 395
WARNING: ECC failure at page 396
WARNING: ECC failure at page 397
WARNING: ECC failure at page 398
WARNING: ECC failure at page 399
WARNING: ECC failure at page 400
WARNING: ECC failure at page 401
WARNING: ECC failure at page 402
WARNING: ECC failure at page 403
WARNING: ECC failure at page 404
WARNING: ECC failure at page 405
WARNING: ECC failure at page 406
WARNING: ECC failure at page 407
WARNING: ECC failure at page 408
WARNING: ECC failure at page 409
WARNING: ECC failure at page 410
WARNING: ECC failure at page 411
WARNING: ECC failure at page 412
WARNING: ECC failure at page 413
WARNING: ECC failure at page 414
WARNING: ECC failure at page 415
WARNING: ECC failure at page 416
WARNING: ECC failure at page 417
WARNING: ECC failure at page 418
WARNING: ECC failure at page 419
WARNING: ECC failure at page 420
WARNING: ECC failure at page 421
WARNING: ECC failure at page 422
WARNING: ECC failure at page 423
WARNING: ECC failure at page 424
WARNING: ECC failure at page 425
WARNING: ECC failure at page 426
WARNING: ECC failure at page 427
WARNING: ECC failure at page 428
WARNING: ECC failure at page 429
WARNING: ECC failure at page 430
WARNING: ECC failure at page 431
WARNING: ECC failure at page 432
WARNING: ECC failure at page 433
WARNING: ECC failure at page 434
WARNING: ECC failure at page 435
WARNING: ECC failure at page 436
WARNING: ECC failure at page 437
WARNING: ECC failure at page 438
WARNING: ECC failure at page 439
WARNING: ECC failure at page 440
WARNING: ECC failure at page 441
WARNING: ECC failure at page 442
WARNING: ECC failure at page 443
WARNING: ECC failure at page 444
WARNING: ECC failure at page 445
WARNING: ECC failure at page 446
WARNING: ECC failure at page 447
parsing last generation bootmap
found valid boot2 blockmap at block 1 (pos 0x627c0), submap 0, generation 2
found valid boot2 blockmap at block 5 (pos 0xe67c0), submap 0, generation 3
parse_blocks: found 2 valid blockmaps
found 2 valid blockmaps
using generation 3
boot2 blocks: 00 01 02 04 05 06
boot2bin @5,0 (blocks=0,1 - bootmii=0)
bootmii@-1,-1
boot2 blocks: 06 05 04 02 01 00
boot2bin @5,1 (blocks=6,5 - bootmii=0)
boot2 block layout: 2 2 1 1 1 0 0
Assembling boot2 in RAM
copyright size = 34
copyright text = 'Copyright 2008,2009 Team Twiizers.'
tmd ends at 0x802884ac, data starts at 0x802884e0
bootmii version = '0.9'
Ok for boot2 install
The test results are in:

 Using IOS versions: Installer: 36, HBC: 53, DVDX: 36

The Homebrew Channel: Can be installed
DVDX: Can be installed
BootMii: Can be installed
A BootMii install requires a SD card.

Runtime files will be written, these are required to
properly boot BootMii.

Mounting SD card...
Creating directory '/bootmii'...
Writing '/bootmii/armboot.bin'...
Writing '/bootmii/ppcboot.elf'...
Writing config file...
Skipped, file already exists

Done.

Erasing NAND block 3
Writing NAND block 3
Verifying NAND block 3 to block 0 of BootMii
Erasing NAND block 4
error erasing page 256: -13
Erasing NAND block 3
Erasing NAND block 4
error erasing page 256: -13
A BootMii install requires a SD card.

Runtime files will be written, these are required to
properly boot BootMii.

Mounting SD card...
Creating directory '/bootmii'...
Writing '/bootmii/armboot.bin'...
Writing '/bootmii/ppcboot.elf'...
Writing config file...

Done.

A BootMii install requires a SD card.

Runtime files will be written, these are required to
properly boot BootMii.

Mounting SD card...
Creating directory '/bootmii'...
Writing '/bootmii/armboot.bin'...
Writing '/bootmii/ppcboot.elf'...
Writing config file...
Skipped, file already exists

Done.

Erasing NAND block 3
Writing NAND block 3
Verifying NAND block 3 to block 0 of BootMii
Erasing NAND block 4
error erasing page 256: -13
Erasing NAND block 3
Erasing NAND block 4
error erasing page 256: -13
A BootMii install requires a SD card.

Runtime files will be written, these are required to
properly boot BootMii.

Mounting SD card...
Creating directory '/bootmii'...
Writing '/bootmii/armboot.bin'...
Writing '/bootmii/ppcboot.elf'...
Writing config file...
Skipped, file already exists

Done.

Erasing NAND block 3
Writing NAND block 3
Verifying NAND block 3 to block 0 of BootMii
Erasing NAND block 4
error erasing page 256: -13
Erasing NAND block 3
Erasing NAND block 4
error erasing page 256: -13
A BootMii install requires a SD card.

Runtime files will be written, these are required to
properly boot BootMii.

Mounting SD card...
Creating directory '/bootmii'...
Writing '/bootmii/armboot.bin'...
Writing '/bootmii/ppcboot.elf'...
Writing config file...
Skipped, file already exists

Done.

Erasing NAND block 3
Writing NAND block 3
Verifying NAND block 3 to block 0 of BootMii
Erasing NAND block 4
error erasing page 256: -13
Erasing NAND block 3
Erasing NAND block 4
error erasing page 256: -13

In the end on the screen it displays FAILED (-1020000013). Not really sure what to make of any of it.

Thanks for your help!

 

[LowKeyEnergy]

hey guys , i installed hbc 1.0.3 using hackmii installer 0.2 so that i could use my 8gb SDHC card in wad manager 1.3 .

hbc 1.0.3 was installed successfully , but i still get error code (ret -1) when trying to retrive the device contents from wad manager . has anyone else had trouble loading wads from sdhc AFTER updating their hbc to 1.0.3 ?

several apps such as nes and snes emulators work fine and their forwarders work . mplayer_ce 0.5 works , but the forwarder stop working on sdhc cards , so sdhc is not totally broken . mostly just the wad loader .

system specs :
system menu 4.0
cios10
downgraded ios 12
cioscorp
preloader

i forget what other details might be relevant

any help is very much appreciated , though i suppose that goes without saying

 

[supagusti]

I installed BootMii 0.2 and the New HomeBrew Channel over the old ones WITH NO PROBLEMS!!!
I just wanted to know how to set the autoboot..?

This is my boot me config file..

# BootMii config file

# Video mode, possible settings:
# NTSC, PAL50, PAL60, PROGRESSIVE
VIDEO=NTSC

# Autoboot, possible settings:
# SYSMENU, HBC
#AUTOBOOT=SYSMENU

Do I change something in there?

THANKS, WiiMan123
BootMii 0.2 seems farter..

Without knowing anything about bootmii iwould say you have to remove the "#" in the line "#AUTOBOOT=SYSMENU".

CODE# Autoboot, possible settings:
# SYSMENU, HBC
AUTOBOOT=SYSMENU

Normaly the # character comments out the following line...

 

[fst312]

hey guys , i installed hbc 1.0.3 using hackmii installer 0.2 so that i could use my 8gb SDHC card in wad manager 1.3 .

hbc 1.0.3 was installed successfully , but i still get error code (ret -1) when trying to retrive the device contents from wad manager . has anyone else had trouble loading wads from sdhc AFTER updating their hbc to 1.0.3 ?

several apps such as nes and snes emulators work fine and their forwarders work . mplayer_ce 0.5 works , but the forwarder stop working on sdhc cards , so sdhc is not totally broken . mostly just the wad loader .

system specs :
system menu 4.0
cios10
downgraded ios 12
cioscorp
preloader

i forget what other details might be relevant

any help is very much appreciated , though i suppose that goes without saying

if your sd card is an 8GB kingston class 4 your not going to be able to use it on anything but HBC for now inever was able to use mine till HBC 1.0.3 came out.other apps didn't work with it i think that is why hackmii.com has an twilight hack source code right now so coders could use it so the sd cards that work on HBC will work on their apps such as mplayer ce and emulators.well these are apps that don't work for me.and i haven't used a forwarder yet.i usually use hbc for apps.

 

[keyra]

hmmz, as i said before looks like the new dvdx combined with ftpii permits to grab the nand file from ftp



the thing is, since it's .img would it be possible to change to .bin and make it working

 

[LowKeyEnergy]

if your sd card is an 8GB kingston class 4 your not going to be able to use it on anything but HBC for now inever was able to use mine till HBC 1.0.3 came out.other apps didn't work with it i think that is why hackmii.com has an twilight hack source code right now so coders could use it so the sd cards that work on HBC will work on their apps such as mplayer ce and emulators.well these are apps that don't work for me.and i haven't used a forwarder yet.i usually use hbc for apps.

thanks for the response .

its not kingston . it's sandisk , and it's working for everything except wadmanager now . all my forwarders are good , just had to find new ones compiled with proper sdhc support libs .


can anyone else shed some light on this problem ?

 

[Arm the Homeless]

hmmz, as i said before looks like the new dvdx combined with ftpii permits to grab the nand file from ftp



the thing is, since it's .img would it be possible to change to .bin and make it working

It won't work like that.

Oh, and the reason why it wants to open the files with different things is because to my knowledge, Linux opens things based on their contents and Windows opens things based on their file extension.

 

[cacique77]

I fixed my problem, it was some random IOS corruption due to other patch from non-verified sources that I tried. I can say that it works succesfully on LU64 console running menu system 4.0.

how did you fixed?? I have the same problem

 

[cacique77]

Any one?? knows..... How did he fixed it..
thanks

 

[LowKeyEnergy]

Any one?? knows..... How did he fixed it..
thanks

if he had a corrupt file then he fixed it by replacing it with a good file .

 

[emachine]

just a noob question. do i need a separate SD card to backup the NAND of the wii or i can use the same SD card that was used to install the bootmii?

 

[onneeye]

Thanks guys for the tips. I was able to install bootmii in boot2 sector and works great. I found out the to back up the nand you need a secound sd card.


When bootmi backup the nand it show a bad black it said factory bad block marker at block 2025.

What does it mean?

 

[FenrirWolf]

It means that the block was bad before it left Nintendo. It's normal to have anywhere from 0-80 of them, so don't worry if they show up.

 

[SublimeAndEtc]

just a noob question. do i need a separate SD card to backup the NAND of the wii or i can use the same SD card that was used to install the bootmii?

You can use the same one. If you're using BootMii v0.2, just make sure you have over 528MB free. If you're using BootMii v0.1, you'll have to temporarily move the contents of your SD to your computer, then let it backup your NAND, because v0.1 requires that you format. After either case, just copy the nand.bin to your computer for safe keeping.