Hacking NO SIGNAL

  • Thread starter Thread starter spiderjjr45
  • Start date Start date
  • Views Views 4,225
  • Replies Replies 26
nitrostemp said:
not having any thing at the end of "autoboot="

OH THANK GOD!

Alright, my wii's up and fine. However, I have no connection to the internet on my wii right now. So how do I restore it to 4.1 and make everything better?
 
spiderjjr45 said:
My Bootmii ini looks like this:

# BootMii config file

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

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

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

Edit: The autoboot was at first SYSMENU, I just changed it to HBC, will this help?
Set the BOOTdelay to 5 or 10 in your .ini file
 
Something no one has seemed to mention - you can use BootMii to boot directly into the homebrew channel, which uses IOS 36 (which may still be present). If so, install IOS 60 (non-stub!) and then 4.1 system menu. It could well be an easy, quick fix.
 
toejam316 said:
Something no one has seemed to mention - you can use BootMii to boot directly into the homebrew channel, which uses IOS 36 (which may still be present). If so, install IOS 60 (non-stub!) and then 4.1 system menu. It could well be an easy, quick fix.

I just use normal Wad manager to install that, right?

Also, v6174 would be the non stub version of the IOS, right?


(I'm sorry for asking so many questions, I could usually do this easily, but the recent semi-brick has caused me to be quite paranoid.)
 
--- IOS60 ---

Version 6400 of this IOS a stub, meaning it has no functionality besides simply existing. You will not be able to run any code from a stub IOS. Do NOT install version 6400!! as System Menu 4.0 and 4.1 requires it to function. Version 6400 will DEFINITELY BRICK your wii of version 4.1 or below!!
 

Site & Scene News

Popular threads in this forum