|
Is there any way to fix my fully bricked Wii?
|
|
|
hookem102
Suspended permanently
|
4. August 2009 @ 10:58 |
Link to this message
|
Hi, my Wii was on system menu 3.2u with preloader installed. Then I upgraded my Wii to 4.1u officially. When I couldn't get some of my homebrew to work, I tried to downgrade my Wii to 3.2 again. except I accidentally installed the IOS16-64-v257-prod.wad instead of the IOS30-64-v1040.wad, and then I installed the systemMenu-v289.wad. And when I went back to the system menu I just got a black screen, and every time I turn it on now I just get that black screen.
For some reason I can't get to the preloader by holding reset.
Is there any way to fix it, or am I stuck with chunk of plastic?
Thank you for taking the time to read this post!
|
|
Advertisement
|
|
|
|
AfterDawn Addict
|
4. August 2009 @ 11:05 |
Link to this message
|
Did you have Bootmii installed as Boot2?
If not then you will probably have to try using Savemii or Savemiifree to fix this issue.
Preloader will be deleted when doing a Menu version change. So you lost Preloader when going from 3.2 to 4.1 firmware. If you installed Preloader after you updated to 4.1 then it would have been deleted again when downgrading to 3.2 firmware.
|
|
hookem102
Suspended permanently
|
4. August 2009 @ 11:12 |
Link to this message
|
Originally posted by larrylje:
Did you have Bootmii installed as Boot2?
If not then you will probably have to try using Savemii or Savemiifree to fix this issue.
Preloader will be deleted when doing a Menu version change. So you lost Preloader when going from 3.2 to 4.1 firmware. If you installed Preloader after you updated to 4.1 then it would have been deleted again when downgrading to 3.2 firmware.
Yes I think I have bootmii installed as boot2, because I have a bootmii folder on my sd card that has a armboot.bin a bootmii.ini and a ppcboot.elf files.
|
AfterDawn Addict
|
4. August 2009 @ 11:46 |
Link to this message
|
You probably have it installed as an IOS if the Bootmii folder is on your SD card and it dosent auto-boot when turning on your Wii system.
Does Bootmii start when you turn on the system? Did you edit the config file of Bootmii to make it auto-boot to the Wii system menu?
|
|
hookem102
Suspended permanently
|
4. August 2009 @ 11:48 |
Link to this message
|
Originally posted by larrylje:
You probably have it installed as an IOS if the Bootmii folder is on your SD card and it dosent auto-boot when turning on your Wii system.
Does Bootmii start when you turn on the system? Did you edit the config file of Bootmii to make it auto-boot to the Wii system menu?
No, bootmii doesn't start when I turn on my system.
And I never edited the config file.
|
AfterDawn Addict
|
4. August 2009 @ 11:58 |
Link to this message
|
Then your going to have to try savemii or savemiifrii.
More then likely your going to need a Modchip to boot auto-update disc.
If you don't know what that is then use Google.
This message has been edited since posting. Last time this message was edited on 4. August 2009 @ 12:00
|
|
hookem102
Suspended permanently
|
4. August 2009 @ 12:01 |
Link to this message
|
Originally posted by larrylje:
Then your going to have to try savemii or savemiifrii.
More then likely your going to need a Modchip to boot auto-update disc.
If you don't know what that is then use Google.
Yeah, I know what your talking about.
Thanks for the response!
|
|
hookem102
Suspended permanently
|
4. August 2009 @ 12:18 |
Link to this message
|
I just had a thought. Can't I edit the bootmii.ini file so it autoboots to the Homebrew Channel?
|
AfterDawn Addict
|
4. August 2009 @ 13:06 |
Link to this message
|
Not all systems can install Bootmii to Boot2. If it can't be installed in Boot2 it will install as an IOS.
If it is installed in Boot2 then it should auto-start when you turn on your system.
If it is installed as an IOS then you launch it from the Homebrew Channel.
So more then likely you have it installed as an IOS which pretty much doesn't protect you from a brick.
|
|
hookem102
Suspended permanently
|
4. August 2009 @ 23:09 |
Link to this message
|
Originally posted by larrylje:
Then your going to have to try savemii or savemiifrii.
More then likely your going to need a Modchip to boot auto-update disc.
If you don't know what that is then use Google.
So I've been trying to use savemiifrii. the GC controller won't work on the bricked wii but it will work on a non-bricked wii.
Is this a common problem?
|
AfterDawn Addict
|
5. August 2009 @ 00:22 |
Link to this message
|
|
You need to take the controler apart so you can press down on all 4 D-Pad buttons at the same time.
|
|
hookem102
Suspended permanently
|
5. August 2009 @ 09:46 |
Link to this message
|
Originally posted by larrylje:
You need to take the controler apart so you can press down on all 4 D-Pad buttons at the same time.
My controller is taken apart and modded so all four directions can be pressed at once.
It works on my Wii that doesn't need to be fixed, but it will not work on the bricked Wii.
|
|
AMatthews
Senior Member
|
5. August 2009 @ 14:36 |
Link to this message
|
The most concerning thing is that you tried to downgrade from 4.1 to 3.2. Honestly downgrading should just be left alone.
Take a look at this site http://wiibrew.org/wiki/IOS_History
Notice how next to certain IOSes it says Mothballed?
Notice how next to IOS30 it says Mothballed?
Mothballed basically means that a garbage IOS has replaced the original functioning IOS.
When you upgraded from 3.2 to 4.1 your IOS30 was mothballed (v2816). The reason you needed to install IOS30 before installing systemMenu-v289.wad was so that you overwrite the mothballed IOS30 with a properly functioning one from before when Nintendo mothballed it.
IOS30 is the IOS that System Menu 3.2 runs off of. A mothballed IOS30 is basically the same thing as deleting it. Deleting IOS30 on 3.2 is the same as deleting IOS60 on 4.0 or 4.1
Edit: Hmm, does installing bootmii as an IOS put the bootmii folder on the SD card? I was under the impression that it was the boot2 install that did that. Although I think I seem to remember that there is an option to prepare the card. It's probably this that puts those files on there independently of which install you do.
This message has been edited since posting. Last time this message was edited on 5. August 2009 @ 14:44
|
|
dacore84
Junior Member
|
29. August 2009 @ 13:17 |
Link to this message
|
Originally posted by larrylje:
You probably have it installed as an IOS if the Bootmii folder is on your SD card and it dosent auto-boot when turning on your Wii system.
Does Bootmii start when you turn on the system? Did you edit the config file of Bootmii to make it auto-boot to the Wii system menu?
Could you please explain that again? Is bootmii probably installed as an ios if you got the bootmii folder on the SD-card with the 3 files (armboot.bin, bootmii.ini, ppcboot.elf)?
I hopefully made a boot2 installation and got that folder with those files put on my SD-card. My Wii also start with bootmii automatically when the SD-card is plugged in.
But you say it can be installed as an ios anyway?
|
|
dacore84
Junior Member
|
30. August 2009 @ 04:34 |
Link to this message
|
Originally posted by AMatthews:
The most concerning thing is that you tried to downgrade from 4.1 to 3.2. Honestly downgrading should just be left alone.
Take a look at this site http://wiibrew.org/wiki/IOS_History
Notice how next to certain IOSes it says Mothballed?
Notice how next to IOS30 it says Mothballed?
Mothballed basically means that a garbage IOS has replaced the original functioning IOS.
When you upgraded from 3.2 to 4.1 your IOS30 was mothballed (v2816). The reason you needed to install IOS30 before installing systemMenu-v289.wad was so that you overwrite the mothballed IOS30 with a properly functioning one from before when Nintendo mothballed it.
IOS30 is the IOS that System Menu 3.2 runs off of. A mothballed IOS30 is basically the same thing as deleting it. Deleting IOS30 on 3.2 is the same as deleting IOS60 on 4.0 or 4.1
Edit: Hmm, does installing bootmii as an IOS put the bootmii folder on the SD card? I was under the impression that it was the boot2 install that did that. Although I think I seem to remember that there is an option to prepare the card. It's probably this that puts those files on there independently of which install you do.
Sry to bump like this but I would also like to get this confirmed? My post above this one also asks the same thing. Any way to check if it´s ios installed instead of boot2? Bootmii autostarts with the SD-card placed in the SD-card slot. Is it 100% sure it´s insalled as boot2 then?
This message has been edited since posting. Last time this message was edited on 30. August 2009 @ 04:35
|
|
Advertisement
|
|
|
AfterDawn Addict
|
30. August 2009 @ 12:34 |
Link to this message
|
Originally posted by dacore84:
Sry to bump like this but I would also like to get this confirmed? My post above this one also asks the same thing. Any way to check if it´s ios installed instead of boot2? Bootmii autostarts with the SD-card placed in the SD-card slot. Is it 100% sure it´s insalled as boot2 then?
If Bootmii starts automatically when turning on the system then it is installed to Boot2. Bootmii installed as an IOS has to be ran from the Homebrew Channel.
|
