for god's sake.... don't touch pimp my wii.. ever nor darkcorp... and don';t listen to that due above.. NEVER (practically never) do an official nintendo update! this problem is very easily fixed!
use xflaks modmii.. its soo simple.. reinstalls your IOS's to the correct versions... asks you questions (yes or no).. how can you mess up?
when asked... choose 4.2 or 4.1 firmware... not 4.3..
it generates a CUSTOM guide for you... read the guide... try to understand the semantics of each step and its process, and why it is important...
after you have a patched 36 installed to slot 236... USE MMM (multimod manager) to reinstall all your wads generated by modmii.... UNINSTALL the wad that originally started your problem (could be bannerbrick)... get stuff working...
make a bootmii NAND backup... put it on your computer..
use xflaks modmii.. its soo simple.. reinstalls your IOS's to the correct versions... asks you questions (yes or no).. how can you mess up?
when asked... choose 4.2 or 4.1 firmware... not 4.3..
it generates a CUSTOM guide for you... read the guide... try to understand the semantics of each step and its process, and why it is important...
after you have a patched 36 installed to slot 236... USE MMM (multimod manager) to reinstall all your wads generated by modmii.... UNINSTALL the wad that originally started your problem (could be bannerbrick)... get stuff working...
make a bootmii NAND backup... put it on your computer..
tj_cool said:
LOL... dude... did you really just ask that? what culture are you from? I only ask because I don't know anyone that would not get that joke!
rAiN mAn 2o0o said:
Please do explain why the "due" above is wrong, which I would assume is directed towards me?? What is wrong with Nintendo updates these days? Granted when 4.3 first came out, it removed HBC, however HBC has since then been updated and is now no longer removed when 4.3 is installed. Any thing else that used to no work in 4.3 has since then either been updated to work, or replaced by something much better.
I do agree that it can be easily fixed; however, when there is the option to update and get the latest code, why not just do the update this way? When games start requiring 4.3, they will already be there and won't have to do any more updating in order to play that game. Granted by that time we will be beyond 4.3, but, while other suckers are complaining that they have to update to 4.3 to play Zelda, they, and all the other people already on 4.3 will be enjoying the game and will be able to give out spoilers to those still waiting for updates to happen.
Once again, if this were my Wii, I would still go ahead and perform the update, and if anything does go screwy, just revert to 4.2 with the nand backup you made before the update, or if you need to, reload HBC using BootMii and the special HackMii made for BootMii.
QUOTE said:
I agree that according to the case PMW might be the appropriate tool but I totally disagree your comment about the fact that the use of PMW ends in disaster :
I have been using PWM several times without problems,
I have followed some threads about PMW use I and I don't remember that someone complained about PMW and comments demonstrated that it has been used by a big number of users.
This tools which is very well maintained provides now a quick way to hack 4.3 WII (with obviously the help of INDIANA or YU-GI-OH), this explained in several tutorials and I doubt that the websites that give these tutorial are suggesting the worst method !
So again I agree that when some IOS are corrupted it might be the right tool but I really advise PMW to hack and update a WII.
Olivier
caster62003 said:
meant "dude".. Didn't mean it derogatory. 4.3 does not support bannerbomb (which is really handy)... and adds no functionality.... no longer supports regionfree VC and wiiware...and I say pick 4.2 over 4.1 because of slightly more control with priiloader hacks.
and as far as Official nintendo updates go... Were you here the day 4.2 launched? did you see the forums...? Nintendo ended up bricking almost as many systems as they patched (some weren't even modded and still got bricked). when you have a softmodded wii, it is always good to know what certain files are and what they are used for and what version number they are. updating through homebrew apps like Multimod manager, dop-mii, moddmii, and or installing them with wad files.
There are some cases where doing an OFFICIAL NINTENDO update can be the EASIEST route... but is it the smartest? Do you know Exactly everything that has been changed? are logs kept? see my point?
mike333 said:
i read/ran modmii, and had a pretty lengthy pm session with xflak about this problem. he was very helpful, but it was deemed that way too much had happened within this disaster.
and the whole problem/blame does lay with me for NOT making a nand backup when everything was running perfectly.
as for me possibly being a kid:
i only wish that i was still a kid trying to get out of bricking a wii. unfortunately at 37 i do not have that luxury.
this whole calamity was/is nowhere near what the title would suggest.
i was trying to make a funny about a rather non-issue.
i was slighty miffed about the whole thing. more from the perspective that i was not able to resolve it without returning the wii.
my pride is a little hurt, however i just went a got a tumbler of johnny walker red, some angustora bitters and relaxed afterwards. it's all good.
i would like to thank everyone for their comments and suggestions, even the useless ones.
it's great to have a place to come to that i can get some help.
- Joined
- Oct 15, 2008
- Messages
- 404
- Trophies
- 0
- Age
- 54
- Location
- Glasgow, Scotland, UK
- Website
- Visit site
- XP
- 137
- Country
jaynecobb said:i tried many different things that were suggested, and nothing worked.
i went from redoing modmii to trying to download official ios's from nintendo to pimp my wii, but to no avail.
my wife said she installed a couple things and now she thinks that she installed to ios(s) 36, 56, 57, 236, and 249.
no matter what i tried nothing would solve the problem. i am really pissed that i didn't take the time to make a nand backup when i set everything up to begin with.
halo:reach was just calling a little too loudly. gotta love those banned 360's.
i finally just sucked it up and took the wii back to gamestop and returned it for credit on my halo:reach (yes i buy still), sony move, and kinect preorders.
i guess i will just have to live with taking my original wii up and down the stairs when i want to game after the wife has finished her workouts.
thanks again for all the advice!
Oh ffs....can you believe this guy?
YOU COULD HAVE FIXED THIS, BUT INSTEAD USED YOUR LAZYNESS AS AN EXCUSE TO TRADE IN A WII CONSOLE FOR A 360 GAME!?" You know the other shit didn't really matter.
Enjoy having just one wii when you used to have two!
I hope your wife visits this site and reads this.
Similar threads
- No one is chatting at the moment.
-
-
-
-
-
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
32GBs is the baseline for 4K video editing these days and lots of recommendations for 64GBs but for games 16,GBs is honestly plenty for a long time. -
-
-
-
-
-
-
-
-
-
@
Psionic Roshambo:
Some sort of police thing going on near me lol "Get out of the car with your hands up and walk backwards towards us" over a loud speaker thing
-
-
like a 250 dollar kit back when DDR4 was Intel only
