Hacking New Homebrew Channel black screen

[Dipole]

Hi everyone,
I just updated the Homebrew Channel on my Wii and it will now only give me a black screen if I try to use it.
The old version worked fine v1.01, but everytime I started it while connected to the web it asked me to update. So I did.
The new version is 1.03.
I read somewhere that this is due to a problem with iso51 but not sure.
I also read that version 1.03 can access the usb port to load homebrew and wonder if that is the issue.

I was going to reinstall the Homebrew Ch using the normal Twilight Princess Hack ,
but wonder if I could reinstall it using the USB loader forwarder Ch that is still working.
I removed the Homebrew Ch with the Wii data manager and I think that the older version will work if I can re-install it.
I have the Gamma Backup loader installed and another Backup loader plus USB loader forwarder,
Wii Version 3.2u firmware.

This is the logfile created on the SD card
--------------------------------------------------
HackMii v0.2 installer starting up
PVR = 00087200
85 titles are installed
Found IOS 250: revision: 0xffff*
Found IOS 0: revision: 0x0*
Found IOS 249: revision: 0xa*
Found IOS 16: revision: 0x101.
Found IOS 51: revision: 0x1300*
Found IOS 10: revision: 0x300.
Found IOS 37: revision: 0x816.
Found IOS 36: revision: 0x412.
Found IOS 35: revision: 0x410.
Found IOS 34: revision: 0x40f.
Found IOS 33: revision: 0x410.
Found IOS 31: revision: 0x410.
Found IOS 30: revision: 0x40f.
Found IOS 28: revision: 0x50c.
Found IOS 22: revision: 0x309.
Found IOS 20: revision: 0xc.
Found IOS 17: revision: 0x200.
Found IOS 15: revision: 0x101.
Found IOS 14: revision: 0x106.
Found IOS 13: revision: 0xa.
Found IOS 12: revision: 0x6.
Found IOS 11: revision: 0xa.
Found IOS 21: revision: 0x202.
Found IOS 2: revision: 0x121.
Found IOS 9: revision: 0x208.
Found IOS 4: revision: 0xff00.
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 256
WARNING: ECC failure at page 257
WARNING: ECC failure at page 258
WARNING: ECC failure at page 259
WARNING: ECC failure at page 260
WARNING: ECC failure at page 261
WARNING: ECC failure at page 262
WARNING: ECC failure at page 263
WARNING: ECC failure at page 264
WARNING: ECC failure at page 265
WARNING: ECC failure at page 266
WARNING: ECC failure at page 267
WARNING: ECC failure at page 268
WARNING: ECC failure at page 269
WARNING: ECC failure at page 270
WARNING: ECC failure at page 271
WARNING: ECC failure at page 272
WARNING: ECC failure at page 273
WARNING: ECC failure at page 274
WARNING: ECC failure at page 275
WARNING: ECC failure at page 276
WARNING: ECC failure at page 277
WARNING: ECC failure at page 278
WARNING: ECC failure at page 279
WARNING: ECC failure at page 280
WARNING: ECC failure at page 281
WARNING: ECC failure at page 282
WARNING: ECC failure at page 283
WARNING: ECC failure at page 284
WARNING: ECC failure at page 285
WARNING: ECC failure at page 286
WARNING: ECC failure at page 287
WARNING: ECC failure at page 288
WARNING: ECC failure at page 289
WARNING: ECC failure at page 290
WARNING: ECC failure at page 291
WARNING: ECC failure at page 292
WARNING: ECC failure at page 293
WARNING: ECC failure at page 294
WARNING: ECC failure at page 295
WARNING: ECC failure at page 296
WARNING: ECC failure at page 297
WARNING: ECC failure at page 298
WARNING: ECC failure at page 299
WARNING: ECC failure at page 300
WARNING: ECC failure at page 301
WARNING: ECC failure at page 302
WARNING: ECC failure at page 303
WARNING: ECC failure at page 304
WARNING: ECC failure at page 305
WARNING: ECC failure at page 306
WARNING: ECC failure at page 307
WARNING: ECC failure at page 308
WARNING: ECC failure at page 309
WARNING: ECC failure at page 310
WARNING: ECC failure at page 311
WARNING: ECC failure at page 312
WARNING: ECC failure at page 313
WARNING: ECC failure at page 314
WARNING: ECC failure at page 315
WARNING: ECC failure at page 316
WARNING: ECC failure at page 317
WARNING: ECC failure at page 318
WARNING: ECC failure at page 319
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 03 04 05 06
boot2bin @5,0 (blocks=0,1 - bootmii=0)
bootmii@-1,-1
boot2 blocks: 06 05 04 03 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'
prepare_bootmii: bootmii_check_boot1 failed: -2
The test results are in:

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

The Homebrew Channel: Can be installed
DVDX: Can be installed
BootMii: Can only be installed as an IOS
The installed boot1 version prevents a boot2 install (-2)
Removing title 0x0001000844564458...
Deleting 1 ticket

--------------------------------------------------------------------------

If the twilight princess hack is the only way to re-install I will use that method.
I also thought I could use BannerBomb, but I think that would re-install the updated version of the Homebrew Ch I believe, unless it can be used to install any version.
Any help would be very welcome Thank you..

 

[micric100]

theres a couple of topics like this, search gbatemp

 

[Dipole]

Well I removed the Homebrew Channel with the Wii data manager.
I used the TP hack to re-install Homebrew Beta 9, then loaded the update for Homebrew 1.01 and everything works fine again.
I'm not going to update to 1.02 or 1.03.
Maybe I'll update to a newer version once the problem is identified.

I think my idea of using the USB loader forwarder may have worked to re-install the HB ch by putting the boot.dol into the USBloader folder.
The other option would be to use the Bannerbomb with a suitable version of the HB ch to re-install.
I used the TP hack after going out and buying the TP game, as I had originally used the TP hack to install the HB ch and thought it would be the safer option.

Thanks to all out there in the Wii hacking world, too many to give credit to but thanks anyway....

A personal thank you to Rulnip who helped to get my Wii back to its former self...

 

[TroyTheZombie]

You need ios61 for the new homebrew channel.

they expect you to be at 4.0. Either update or install that ios separately.

My advice? install a cios(rev8 or above), use wanikoko's updater, and run ios60 updater.

there really is no need to be at a lower system menu anymore, 4.0 is just as functional and hackable.

 

[Jacobeian]

You need ios61 for the new homebrew channel.

they expect you to be at 4.0. Either update or install that ios separately.

My advice? install a cios(rev8 or above), use wanikoko's updater, and run ios60 updater.

there really is no need to be at a lower system menu anymore, 4.0 is just as functional and hackable.


that's not true
HBC use the last IOS version it can detect, in that case IOS51

see that line :
QUOTEUsing IOS versions: Installer: 36, HBC: 51, DVDX: 36

according to the Installer log, your IOS51 has a fake signature (hence the * sign), that could mean it has some issue
No problem with HBC 1.03 on clean Wii
I' d avise as Troy anyway, update to 4.0 with his method (no need to install cIOS, you already have it apparently) and reinstall the HBC using Bannerbomb, it will use the clean IOS61 this time

btw, what is this IOS0 thing ?

 

[Dipole]

I will consider the update in the future.
Thanks for your advice Troy.. and Jacobeian for your feedback that helps me understand the log a little better.
I am surprised that if ios61 is required that the update does not check for it to be installed and report back before allowing the update. Plus it nags you to install the update whenever we go online and run the HB Ch. Just seems a little odd that if it is required to have ios61 that it doesn't warn so.
Don't think I'm not grateful to all the guys out there for their great work.
I have a post Oct 2008 wii that can't have the bootmii installed to the Boot as you can see from the log file and that makes me less confident to do more updates as things are working so well right now with HB and USB loaders etc. I don't want to risk bricking what is so far a great Homebrew system.

Jacobeian
I have no idea about the :-
Found IOS 0: revision: 0x0*

Maybe someone else has some clues..

 

[FenrirWolf]

Updating won't brick you, so don't worry about that.

 

[Jacobeian]

I will consider the update in the future.
Thanks for your advice Troy..
I am surprised that if ios61 is required that the update does not check for it to be installed and report back before allowing the update. Plus it nags you to install the update whenever we go online and run the HB Ch. Just seems a little odd that if it is required to have ios61 that it doesn't warn so.
Don't think I'm not grateful to all the guys out there for their great work.
I have a post Oct 2008 wii that can't have the bootmii installed to the Boot as you can see from the log file and that makes me less confident to do more updates as things are working so well right now with HB and USB loaders etc. I don't want to risk bricking what is so far a great Homebrew system.

ios61 is NOT required, that's a myth
read my post above

 

[TroyTheZombie]

ah, i see. so it can work on a lower ios, just needs to not be fake signed.

anyway, updating will NOT BRICK YOU. it won't mess with usb loader, backup launchers, or anything.

 

[Jacobeian]

Jacobeian
I have no idea about the :-
Found IOS 0: revision: 0x0*

Maybe someone else has some clues..

http://wiibrew.org/wiki/Talk:Title_database
QUOTEI don't know where you're getting the name IOS0, but that TITLE.TMD is the fakesigned super user TMD used by Waninkoko's FS Dumper. It gets installed when the program runs the ES_Identify() command with that TMD. The Title ID itself is essentially fake.

basically it's Waninkoko's experiments leaving trace on your Wii

 

[ToneEQ]

I had the same problem with HBC 1.02 and 1.03, I had to reinstall 1.01 as all I would get is the black screen. I got fed up of being asked to update HBC everytime I used it so I looked for a solution.

I used Wii System Channels Updater to install patched versions of IOS60 and IOS61 and the then updated to HBC 1.03, worked a charm on 3.2E firmware.

 

[ocdetective]

I notice you dont have IOS 38, 53 and 55 too. Some of the newer games need these to run - a fresh install of these (if you google you can find a download for all 3) would also be sufficient to allow HBC 1.0.3 to subsequently run. My 3.2U currently runs HBC 1.0.3 on IOS55