|
Can i unbrick my wii and if so how?
|
|
|
dtalley11
Junior Member
|
20. July 2009 @ 11:41 |
Link to this message
|
After hearing that my wii having system menu v 3.4 wasn't good, i wanted to downgrade my system menu. I downloaded a kit to do this and did the for steps:
<b>Use wad manager to:</b>
Install IOS38-64-v3609.wad
Install IOS16-64-v257-prod.wad
<b>use CUSTOM WM to:</b>
Install cios_fix.wad
Then use Custom IOS Downgrader to downgrade and download firmware
It was a good kit it worked good but the wad manager sometimes faled or the wad didn't copy right, noticing that these steps also allowed me to install unsigned wad it looked cool, but i couldn't download the system menu firmware cause i have dial-up... so i herd of this cool program...wuff and that my links crossbow training hade firmware v 3.0u YAY i did it i WUFFed the firmware and junk off the disk then installed the wad...it worked i hade system menu 3.0u but i didn't want to stop there, system menu 2.Xu (i cant remember exactly) was on one of my disks I wuffed it and installed that wad too. Only problem is that the wad wasn?t complete, it was corrupt and gave up, i didn't know this because I was making a sandwich, but i got back and pressed home on my wiimote and it was black i knew i hade killed it. I didn't have bootmii or anything on it... so after that lengthy story does anyone know a way to unbrick my wii, or reflash it or something?
|
|
Advertisement
|
|
|
|
AfterDawn Addict
|
20. July 2009 @ 13:34 |
Link to this message
|
It still amazes me that some do all this stuff without having any protection installed (Bootmii) in case of a brick.
Why in the world would you even want to go to 3.0 or 2.X?
In any case you could try installing a Modchip then use savemii or savemiifree to boot an autoboot disc to update the firmware of the system.
savemii is a piece of hardware that goes into a GameCube memory card slot to boot the system. You will need to buy this hardware.
savemiifree uses a Gamecube Controller to act as the savemii hardware and is free as long as you have a Gamecube controller to use.
Do a little research and get informed.
This message has been edited since posting. Last time this message was edited on 20. July 2009 @ 13:38
|
|
dtalley11
Junior Member
|
21. July 2009 @ 07:53 |
Link to this message
|
I tried SaveMii Frii, and nothing happened, just the same black screen after i turned my wii on, I do, on the other hand still have the bootmii files on my pc, i don't know if it is still on the wii's boot2 or ios, soz when i go home later i will try that out but I don't think it will work.
BTW, i was gonna goto v 1.0, to see if you can play other region games. I did on the other hand, always use Untitled Stats firmware.
This message has been edited since posting. Last time this message was edited on 21. July 2009 @ 07:57
|
AfterDawn Addict
|
21. July 2009 @ 12:26 |
Link to this message
|
Originally posted by dtalley11:
I tried SaveMii Frii, and nothing happened, just the same black screen after i turned my wii on, I do, on the other hand still have the bootmii files on my pc, i don't know if it is still on the wii's boot2 or ios, soz when i go home later i will try that out but I don't think it will work.
BTW, i was gonna goto v 1.0, to see if you can play other region games. I did on the other hand, always use Untitled Stats firmware.
You can boot most out of region games on any firmware (as long as they are region compatible). You do not have to be on 1.0 to do it.
If you installed Bootmii as Boot2 and took off the Bootmii folder from the SD card so Bootmii would not auto load then placing that Bootmii folder back to your SD card should Boot Bootmii.
From there you can restore a NAND backup if you happened to make a backup after installing Boot2.
If you didn't make a NAND backup then you should at least be able to boot the Homebrew Channel and then use a program like AnyRegionChanger to install 3.2 firmware to the system which should unbrick it.
Also for savemiifree did you take the Gamecube controller apart so you could press all 4 D-Pad directions at once? I also think you need the controller connected to Port 4 (it could be Port 1 but I am almost positive you need it in Port 4).
This message has been edited since posting. Last time this message was edited on 21. July 2009 @ 12:29
|
|
AMatthews
Senior Member
|
21. July 2009 @ 16:03 |
Link to this message
|
|
I just wanted to share how much I hate seeing cios fix.
I hate seeing cios fix...
|
|
dtalley11
Junior Member
|
21. July 2009 @ 17:54 |
Link to this message
|
1. i found my save mii files all that all there was is:armboot.bin, bootmii.ini and ppcboot.elf i took a look in the bootmii.ini, here it is:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# 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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
looks simple
anyways it must not be in boot2 and I don't think it is ios... bummer
BTW, my wii has the componit cabbles and did work on my tv with progressive, but now that its bricked the black screen is in 480I...not 480P
2. Yes i took my gamecube controller apart pulled of the plastic d-pad and held the 4 bumps on the rubber thing makin shur it was on the for spots on the pc bord...nothin'. am i supost to see a Version number or somthin couse im not jus a black screen like always... Bummer x 2...
edit: yes i tryed it on port 4... and all the rest.
3. The cIOS fix worked... i didn't know exactly what it all did but I could install unsigned wads.. I thought it was cool..untill i bricked my wii with it.
yet another edit: the system menu i was downgraiding to was 2.2 or w/e was the last 2.x one... if that helps
also i waas wondering if i decompress the system menu wad and put the componits on the right spot of my sd card...will my wii check the sd card for the system menu bionary (i can also do this with boot2 or iosX)
This message has been edited since posting. Last time this message was edited on 22. July 2009 @ 06:56
|
|
AMatthews
Senior Member
|
22. July 2009 @ 07:50 |
Link to this message
|
Are you sure you don't have bootmii? Those are the files that the bootmii installer puts on your SD card if you install it as Boot2.
If you haven't already tried it, make a folder on your SD card called bootmii and in that folder put the armboot.bin, bootmii.ini and ppcboot.elf that you found.
|
|
dtalley11
Junior Member
|
22. July 2009 @ 08:42 |
Link to this message
|
Quote:
AMatthews (Senior Member) 22. July 2009 @ 07:50
Are you sure you don't have bootmii? Those are the files that the bootmii installer puts on your SD card if you install it as Boot2.
If you haven't already tried it, make a folder on your SD card called bootmii and in that folder put the armboot.bin, bootmii.ini and ppcboot.elf that you found.
I have already tryed this but i will do it again... make a Bootmii forlder and put the files in it.........nothing a black screen. I know at one time bootmii was installed as boot2 and ios but i was being a dillweed and uninstalled it thinking it was gitting in the way of gecko os..it wasn't gecko os wasn't compadible with sys menu 3.4u and wouldent read my chanal list... i know i should of reinstalled it on 3.0u when i got it working...but i forgot to...that is hy it isn't on my wii...just remains on the blue sd card
Quote:
dtalley11 (Newbie) 21. July 2009 @ 17:54
...yet another edit: the system menu i was downgraiding to was 2.2 or w/e was the last 2.x one... if that helps
also i waas wondering if i decompress the system menu wad and put the componits on the right spot of my sd card...will my wii check the sd card for the system menu bionary (i can also do this with boot2 or iosX)
Is there a point in time the wii checkes anything other then the NAND befor it looks for system menu?
Edit: Quote:
In any case you could try installing a Modchip then use savemii or savemiifree to boot an autoboot disc to update the firmware of the system.
If this helps at all i installed DVDx
This message has been edited since posting. Last time this message was edited on 22. July 2009 @ 08:49
|
|
AMatthews
Senior Member
|
22. July 2009 @ 09:28 |
Link to this message
|
Is there a point in time the wii checkes anything other then the NAND befor it looks for system menu?
The Wii checks boot0, boot1, boot2, then the system menu.
There isn't really a way to change anything if you can't access anything.
If this helps at all i installed DVDx
DVDx won't help.
From what you have said, it's a little hard to tell exactly what happened with your system. I understand that you were definitely on 3.0 at one point (which isn't a bad firmware to be on as far as autobooting is concerned) but then you tried to go to 2.something.
I also agree with trying the Savemii or Savemiifrii.
If you're on 3.0 then it should show 3.0 when you do it. At this point all you have to do is put in any game with an update above 3.0
Mario Kart or Brawl have 3.1 etc. There's a lot to choose from. This is the best case scenario.
I'd say the hard part would be if you are below 3.0
Your System Menu must still be semi alive for autbooting something to work.
Since below 3.0 doesn't show which version you are on I'm not sure that you can tell whether the system menu is still semi alive or if it's gone since it doesn't tell you anything.
If it's still alive you could get a modchip which would allow you to autoboot a disc that you have prepared. But if it's dead then you kind of got a modchip for nothing.
Finally the reason you need a modchip for autobooting is similar to the function that it performs when you put a burned game in the drive. Without a modchip, the Wii is like what is the garbage? But with it it will play the game. Without a modchip even though you are trying to help your Wii, it sees the burned game and treats it just as it always did... "what is this garbage?"
This message has been edited since posting. Last time this message was edited on 22. July 2009 @ 09:33
|
|
dtalley11
Junior Member
|
22. July 2009 @ 12:42 |
Link to this message
|
to start out lets see if i can be more clear...
-i used WUFE to extract firmware off games
-i forund that Links crossbow hade firmware 3.0u (RVL-WiiSystemmenu-v225.wad.out.wad) on it
-i hade 3.4u
-i used wad maniger to install RVL-WiiSystemmenu-v225.wad.out.wad
-it worked
-then i found out that my wii play hade RVL-WiiSystemmenu-v193.wad i tryed to install it didn't finish
-i restarted the wii thinking it worked, but got a black screen
-now i get a black screen when i turn on the wii
Also the wii does spin up the disk (if one is in the reader)
-it must of failed installing one of the earlier contents (or ticket,benner...)
-When i use bootmiifrii i still get a black screen...showing nothing
here is the questions:
-does wad maniger deleat the old contient when trying to install a replacement wad?
-if wad maniger fails does it delete what it did?
-do i REALY have to install a modchip...i'd rather it get fixed by nintindo..if i don't what game has a system menu <2.2?
-if i take it to nintendo what are the chances they just go heck with
-it and send me a new consal befor they find the homebrew/softmod?
-is there a way to reflash my wii?
-and a obvious one...is my main system menu bionary there?
hopefully that helps
BTW: I have wad manager 2.3...
also, the wii doesn't use any of the ios yet?
This message has been edited since posting. Last time this message was edited on 22. July 2009 @ 12:54
|
|
dtalley11
Junior Member
|
22. July 2009 @ 13:25 |
Link to this message
|
Quote:
-do i REALY have to install a modchip...i'd rather it get fixed by nintindo..if i don't what game has a system menu <2.2?
Sarry about that, i was thinking if you have system menu 3.0 got higher and if you have 2.2 go lower...i was to busy...
|
|
AMatthews
Senior Member
|
22. July 2009 @ 14:21 |
Link to this message
|
Well that pretty interesting. 193 is the 2.2 system update but Wii Play came out in February of 07 and the 2.2 update came out in April of 07.
Are you sure it is Wii Play that you got the update from? And you're sure it was an NTSC disc?
I guess it's pretty much besides the point now. Are you certain that you did savemiifrii correctly?
You have to put a disassembled gamecube controller into the 4th port (that's the one closest to the memory card slots) and press all four button on the pad at the same time when you are turning the Wii on. It won't work if the gamecube pad is not disassembled because you won't be able to press the four buttons at the same time. Also try it a few times. People have had issues with getting it to work on the first time.
The disc spinning doesn't say much since even if you deleted your system menu it would still spin.
WadManager doesn't delete the old content if you try to install something else. Say you install a wad of a channel, if you try to install that same wad again it will just install again.
You don't have to get a modchip and I would be wary of getting one if I wasn't sure if my system menu was there or not. Just to re clarify, if your system menu is completely gone no updating with any disc is going to work.
Will Nintendo just give you a different console? Probably not but it's still up to chance. There have been reports of them searching for signs of hacks and and some people have actually had to pay more because of it. And yet others were let of the hook a lot easier (or at least according to them)
The methods of reflashing your Wii require you to have something (a nand backup) to be flashed on there. You could almost think of bootmii as flashing your Wii's nand when you use it to restore the nand. The Infectus mod chip is also capable of restoring but you still need the backup.
Not sure what you mean about main system bionary
And the latest version of Wad Manager is 1.4 so you likely mean something else when you say you have 2.3
The Wii does not use an IOS until it's time for the System Menu.
And which IOS is used for the System Menu varies depending on which firmware you are on.
It uses IOS60 if your are on 4.0 or 4.1
50 for 3.4
30 for everything between 3.0 and 3.3
It uses IOS 20 for 2.2 and 11 for 2.0 and 2.1
|
|
AMatthews
Senior Member
|
22. July 2009 @ 14:29 |
Link to this message
|
This is also part of why upgrading and downgrading can be dangerous. Though I'm still not exactly sure why this happened to your Wii.
But just an example for you and someone who might wander into this thread.
Notice how at this site it lists all the IOSes http://wiibrew.org/wiki/IOS_History
And next to certain ones it says Mothballed?
This means that Nintendo is no longer using that IOS on its latest firmware.
So if you update to say firmware 4.0, all the IOSes that say Mothballed next to them are now pretty much nothing. They don't contain the data that the original IOS contained.
Notice how next to IOS50 it says Mothballed. And that IOS50 is the IOS that System Menu 3.4 runs off of.
If you downgraded back to 3.2, you would still have the trash IOS50 on your system.
Then if you upgraded to 3.4 again, you would receive a brick from an official update because the trash IOS50 wouldn't be replaced (since it's a higher version)
For the future, don't downgrade.
|
|
dtalley11
Junior Member
|
22. July 2009 @ 15:08 |
Link to this message
|
Quote:
Well that pretty interesting. 193 is the 2.2 system update but Wii Play came out in February of 07 and the 2.2 update came out in April of 07.
Are you sure it is Wii Play that you got the update from? And you're sure it was an NTSC disc?
it my have ben redsteel or emergancy mayham i dowbt it is any of the other games
Quote:
I guess it's pretty much besides the point now. Are you certain that you did savemiifrii correctly?
i am tired of disassimbling my gamecube controller!
Quote:
Will Nintendo just give you a different console? Probably not but it's still up to chance. There have been reports of them searching for signs of hacks and and some people have actually had to pay more because of it. And yet others were let of the hook a lot easier (or at least according to them)
I am not gonna pay more then $125... for i could shop on ebay for a wii with a hardware error and replace Motherbords...
Quote:
And the latest version of Wad Manager is 1.4 so you likely mean something else when you say you have 2.3
1.3
Quote:
Not sure what you mean about main system bionary
I got a email from savemii sales..here it is:
ops must have deleted it...=(
Binary is what i ment... the thing that boot2 is looking for
Quote:
This is also part of why upgrading and downgrading can be dangerous. Though I'm still not exactly sure why this happened to your Wii.
But just an example for you and someone who might wander into this thread.
Notice how at this site it lists all the IOSes http://wiibrew.org/wiki/IOS_History
And next to certain ones it says Mothballed?
This means that Nintendo is no longer using that IOS on its latest firmware.
So if you update to say firmware 4.0, all the IOSes that say Mothballed next to them are now pretty much nothing. They don't contain the data that the original IOS contained.
Notice how next to IOS50 it says Mothballed. And that IOS50 is the IOS that System Menu 3.4 runs off of.
If you downgraded back to 3.2, you would still have the trash IOS50 on your system.
Then if you upgraded to 3.4 again, you would receive a brick from an official update because the trash IOS50 wouldn't be replaced (since it's a higher version)
For the future, don't downgrade.
Well i don't think you have to tell me that again... it will be eather at 3.2u or 3.0u lol and definatly have BOOTMII as BOOT2!!!!!!!! (the bootmii installer came with bannerbomb, meaning if nintindo sends me that wii with firmware 4.1u on it ill use bannerbomb for bootmii first, but i don't know if i can make a NAND dump, for my sd card is 256mb...its blue)
and about not knowing what i did... i don't know if you want me to give you more detales about somthing or is it that part between WAD MANIGER FAILD INSTALL IT WRITE (a error somware between the ticket and 3rd content) or I ONLY SEE A BLACK SCREEN WHEN I TURN IT ON!!!!=(
(i am not gitting mad..just seeing if it helps)
thanks for everyones help soo far....
Last.. what was wrong about the cIOS fix... and what is cIOS?
This message has been edited since posting. Last time this message was edited on 22. July 2009 @ 15:15
|
|
AMatthews
Senior Member
|
22. July 2009 @ 15:22 |
Link to this message
|
Boot2 doesn't look for anything. If you ordered a savemii you'll find out whether your system menu is intact or not pretty soon.
As for it either being on 3.0 or 3.2 I would advise against downgrading if it's above that when you get it. And the current firmwares aren't bad. I'm on 4.1 and am quite content.
And yeah you should really have bootmii as boot2 when you get it fixed.
And whether WadManager didn't install it all the way (or whatever) was what I was trying to figure out. But from what you said I can't think of any reason why you now have a black screen. I don't mess with installing wads of the system menu but I don't see why you have a black screen from what you did.
Well I'm sorry that this stuff happened. I hope whatever you decide to do doesn't cost too much money.
cIOS is a modified IOS. Your Wii has a bunch of IOSes. The cIOSes install to the IOS slots in the 200s (your Wii has 256 IOS slots)
This particular cIOS that we are talking about is what allows you to run backups of games as well as use the USB Loader and other things.
Oh and the reason I don't like seeing cIOS fix is because it is old. I think it's a modified version of cIOS36rev5 or something around there. We are now on cIOS38rev13 (I don't think Waninkoko even has cIOSes before rev8 out his site anymore). The Wii scene has changed a lot and sometimes people get into trouble when they work with outdated things.
This message has been edited since posting. Last time this message was edited on 22. July 2009 @ 15:23
|
|
dtalley11
Junior Member
|
22. July 2009 @ 17:07 |
Link to this message
|
Quote:
Boot2 doesn't look for anything. If you ordered a savemii you'll find out whether your system menu is intact or not pretty soon.
A. if boot2 doesn't start the system menu what does? a ini file, some rom thing?
B. I don't think i will be ording savemii for like $40, since nintindo repairs are $70
C. I also hade a problem when i first got my wii (back when they where hard to find) if i put my gamecube memory card in slot 1 it would say 'unreconised device in slot 1' if i get it repaired by nintendo will they fix that two? (by it would say.. i mean whin i look at it in the wii menu or try to save to it in gamecube mode)
Quote:
And whether WadManager didn't install it all the way (or whatever) was what I was trying to figure out. But from what you said I can't think of any reason why you now have a black screen. I don't mess with installing wads of the system menu but I don't see why you have a black screen from what you did.
I will try this again soz u r not still scratching your head.
in the prosses of installing a systemmenu wad, wad manager didn't finnish... it was obvious because installing a ~20 mb wad would of tookin longer than that...but knowing how long it takes (from installing other 20mb wads) i went and did somthing..i forget what is was because its ben like 5 days now. But i got back and i should of ben still installing a wad...well assuming it worked (but thinking it was strange) i hit the home butten to restart my wii and it just whent black..so i turned it off and back on black... it may have somthing to do with you ios thing thow also...so i will tell you ALL of the system menu's my wii has hade:
i bought it with 3.2u or 3.0u or somthing old in late summer 2008. it was a show one but for sume reson game traiders was selling it. i was having a hard time even buying one so..why not just git it used and save $10. i eventualy took it to my ants and nintindo hade a update for it..not thinking i would use it for homebrew i updated. forund out i hade a nice bonis, came with internet chanal, nintindo chanal everyone votes and check Mii out..free and photo chanal 1.0a or somthin. soon i found out how to share my dial-up over wifi...i got it connected and...another update, gosh..took forever so i was at 3.4 then. recently (in 2009) i finaly found out of bannerbomb! modded it and basicly now i am here (with alot more hombrew/fixis).
then i downgraided to 3.0u and then 2.2u..mayby this coused a ios problem and that may be why i am getting black screen. but i still think it was wad maniger..i know what it does with a bad wad because i tryed injecting vurtual consal wads with roms (Zelda lttp tryed injecting ff5 buy finding 00000005.app spliting it into 3 parts with a hex editer part 2 being the rom and re making it with ff5 rom in it and commpressing the wad this is the tutorial http://wii.ds-scene.net/?s=viewtopic&id=508 ...it didn't work) so when i tryed putting ff5 as 00000005.app and used wadpacker put ip on my wii gave me a error and put me back to wad selection page where a working wad inport would leve mee at the resolts of the inport and tell me to press home to restart or somthing.
Just try and read through this because it took me forever to type...even without revising it..sarry
|
|
AMatthews
Senior Member
|
22. July 2009 @ 17:28 |
Link to this message
|
A. if boot2 doesn't start the system menu what does? a ini file, some rom thing?
From hackmii.com:
Let?s revisit the boot sequence of the Wii. The very first piece of code that runs is boot0, which is part of the mask artwork of the Hollywood chipset and thus entirely untouchable. It loads boot1 from the beginning of NAND and verifies it against a hash stored in non-writable memory. This ensures that boot1 is also untouchable (you?ll brick your Wii if you try). Here?s where it gets interesting: boot1 is supposed to load boot2 from a special reserved section of the NAND Flash memory. Boot2, which is a sort of mini-IOS, then kicks off the loading of the system menu (and ends up loading its required IOS beforehand). However, the boot2 verification uses the same exact infrastructure as the one used in the rest of the Wii, and it is also vulnerable to the fakesigning bug. Since boot1 is untouchable once the Wii leaves the factory, every current Wii in existence (as far as we know) is and forever will be vulnerable to this bug, which lets us install a fakesigned boot2 of our choice.
B. I don't think i will be ording savemii for like $40, since nintindo repairs are $70
Yeah I guess it doesn't make sense to do that
C. I also hade a problem when i first got my wii (back when they where hard to find) if i put my gamecube memory card in slot 1 it would say 'unreconised device in slot 1' if i get it repaired by nintendo will they fix that two? (by it would say.. i mean whin i look at it in the wii menu or try to save to it in gamecube mode)
I'm not sure about this. You should ask them
And I did read all of the rest of what you wrote but I still don't see anything that should have bricked your Wii. I do agree that something strange happened when you started installing the wad, and then you came back and it was finished before you got back. Still if it was an IOS problem it should have happened before what you did with the wad a 2.2.
If you tried injecting Final Fantasy V into A Link to the Past, if something bad were to happen it should have happened then and not later on. I would also like to add that for SNES games you are better of just using the SNES9X emulator than injecting wads. And what you having right now is definitely more serious than a banner brick that wad files caused simply from being installed.
And regardless of what caused it, you have to move forward. Get it fixed and I'm sure you'll stay far away from whatever caused the problem (at least without having bootmii)
|
|
dtalley11
Junior Member
|
22. July 2009 @ 18:33 |
Link to this message
|
Quote:
If you tried injecting Final Fantasy V into A Link to the Past, if something bad were to happen it should have happened then and not later on. I would also like to add that for SNES games you are better of just using the SNES9X emulator than injecting wads. And what you having right now is definitely more serious than a banner brick that wad files caused simply from being installed.
a little off topic but id like to do this with n64 games too, but wii 64 only runs at half speed...
Quote:
And I did read all of the rest of what you wrote but I still don't see anything that should have bricked your Wii. I do agree that something strange happened when you started installing the wad, and then you came back and it was finished before you got back. Still if it was an IOS problem it should have happened before what you did with the wad a 2.2.
I don't think wad maniger finnished , when it has a problem it tells you and takes you back to wad selection...its ben a little whilebut i thank thats where it was.
Quote:
And regardless of what caused it, you have to move forward. Get it fixed and I'm sure you'll stay far away from whatever caused the problem (at least without having bootmii)
I would hope so!... althow if nintindo doesn't find the softmod, they give you a new 1yr worenty once they fix/send you a new wii!
i will still have bootmii as boot2
Quote:
The Wii does not use an IOS until it's time for the System Menu.
And which IOS is used for the System Menu varies depending on which firmware you are on.
It uses IOS60 if your are on 4.0 or 4.1
50 for 3.4
30 for everything between 3.0 and 3.3
It uses IOS 20 for 2.2 and 11 for 2.0 and 2.1
what about 1.0, IOS9?
This message has been edited since posting. Last time this message was edited on 22. July 2009 @ 18:36
|
|
AMatthews
Senior Member
|
22. July 2009 @ 19:01 |
Link to this message
|
a little off topic but id like to do this with n64 games too, but wii 64 only runs at half speed...
Progress is being made on Wii64. http://emulatemii.com/wordpress/
I don't know if you've seen the April 1st video http://emulatemii.com/wordpress/?p=89
I don't think wad maniger finnished , when it has a problem it tells you and takes you back to wad selection...its ben a little whilebut i thank thats where it was.
I see. For WadManager I can only go off of what people have told me multiple times because I've never had any problems with it. So thanks for that.
I would hope so!... althow if nintindo doesn't find the softmod, they give you a new 1yr worenty once they fix/send you a new wii!
I didn't know this either. That actually sounds like a good deal.
what about 1.0, IOS9?
I think you are right about this one.
|
|
dtalley11
Junior Member
|
22. July 2009 @ 19:36 |
Link to this message
|
Now i am REALY getting off topic but what does this do? cMIOS_rev3
will it realy make gc apps work, like with the gamecube controller?
Also i do agree with what you said about the sytem menu 4.1 working with hombrew..one thing i have lernd (and i think is cool) alot of times...you buy stuff and the cummunity keeps up with it better then the develiper/publisher... but i noticed wii homebrew alwas is changing... since the relece of firmware 4.1u... alot of stuff in hombrew exploits/fixis is changing to match up with it! i may not change from 4.1 if i end up with it.
This message has been edited since posting. Last time this message was edited on 22. July 2009 @ 19:43
|
|
AMatthews
Senior Member
|
22. July 2009 @ 19:48 |
Link to this message
|
cMIOS lets you play Gamecube backups.
And yeah the scene really has come a long way. Seems like people are always working over time.
The 14th revision of cIOS is supposed to be released by Waninkoko this weekend. It supposedly has nand emulation features. I seem to remember reading that he said that he was emulating someone's nand and could see their Miis and their system menu etc. So I guess it's to be expected that copies of people's nands will be on the internet before long.
I'm sure Nintendo will have something to say pretty soon but as of right now 4.1 is pretty golden.
|
|
dtalley11
Junior Member
|
23. July 2009 @ 07:35 |
Link to this message
|
OH NO!!! i just got this off the faq part of the bootmii website:
Quote:
( http://www.bootmii.org/faq/ ) What does "The installed boot1 version prevents a boot2 install (-2) mean? Are you going to fix it?
No, it can't be fixed. Installing as boot2 is the most useful way to install BootMii, but it requires that we exploit a particularly silly bug in a part of the system that can not be changed under any circumstances. Nintendo finally fixed this bug in new Wiis that were released sometime in 2008. We have looked for a suitable replacement for this exploit, but have not found one, and it does not seem likely that anyone ever will.
This doesn't sound good!, if nintendo fixis my wii, will they put the boot1 patch on it? Can they put the boot1 patch on it? i hope they don't put the boot1 patch on it!!!
If they can't find somthing in boot1 alowing them to patch boot2...nvmd i guess im not downgraiding!!!!
bootmii as ios only will fix simple things like banner bricks and Semi-Brick, it woulden't fix what i got! THERE GONNA HAVE TO DO SOMTHING BECAUSE IF I CAN DO IT ANYONE CAN DO IT!
This message has been edited since posting. Last time this message was edited on 23. July 2009 @ 07:41
|
|
BigYeti
Newbie
|
20. November 2009 @ 14:27 |
Link to this message
|
It's been awhile since I updated my wii. I decided to update and did everything perfectly. I tried to get super mario wii to work, so I tried to install cios53. Affter trying it and seeing that it didn't work, I went back to the same program and put uninstall, thinking that it only removes the patch. In short, I accidently deleated cios53 and now my wii won't boot up. I get nothing. I turn on the wii and all I get is a black screen. I did the NAND backup, but stupid me didn't know what the backup was for, so I deleated it. I was reading what larrylje posted "If you didn't make a NAND backup then you should at least be able to boot the Homebrew Channel and then use a program like AnyRegionChanger to install 3.2 firmware to the system which should unbrick it". I have 4.1U firmware. I really need step by step help on how to boot up the homebrew channel and install a new firmware while the wii is bricked. I don't have a modchip and I don't wish to spend money on one. Please help. I always updated my wii. This is the first time I bricked it.
|
|
BigYeti
Newbie
|
20. November 2009 @ 15:03 |
Link to this message
|
I had a thought also,but don't know if it works, or if anyone even tried it. The BootMii can only be installed on the SD through the wii to my understanding. Is it possible to do a NAND backup on another wii console and transfer the BootMii recovery data to my own wii?
|
|
Advertisement
|
|
|
|
Drakonian
Suspended permanently
|
20. November 2009 @ 15:08 |
Link to this message
|
it still amazes me how many people fail in this thread. BACKUP YOUR NAND its not hard and if you delete it your wii deserves to be bricked in all honesty. There are only two methods out there if you have a wii black menu brick. Either get a mod chip costing around 40 bucks now to fix the wii, use savemii or savefrii, or send it back to nintendo for a 70 dollar replacement. Stop asking how do i fix my wii and do the research for once. People in this thread have already listed the options now its up to you to figure it out otherwise dont mod systems without knowledge cause you are only bricking things.
|
