Hacking SaveMiiFrii question ....

[EmperorOfCanada]

Yes. Also for starfall it has to be from GC slot one right?

 

[AdamBrunt]

Wiicrazy: Have you got the "Remove rescue-menu diagnostic disc check" hack installed on your starfall ?

 

[WiiCrazy]

2xYes
Starfall recovery mode patch should be installed and when using you must plug the gc controller in port 1 (for savemiifrii it's port 4)

 

[WiiCrazy]

Wiicrazy: Have you got the "Remove rescue-menu diagnostic disc check" hack installed on your starfall ?

It's not related... that patch ensures the autoboot everytime from recovery mode and it's only effective when launching the disc from recovery menu...
so it's not relevant to getting into the recovery mode...

by the way for the original question : yes I installed that patch too

 

[AdamBrunt]

Well, just tried the y button and the controller in the first slot - no joy. Hopefully, that just means I didn't install the bottom 2 hacks.

right, stupid question time ...... the reset button and the buttons on the RHS sit on top of 'membrane' type thing which has black circles on the bottom presumably for the contact points. Shouldn't the d-pad also have one of these ? cos at the moment it doesn't ? Unless it flew off somewhere whilst I opening the controller.

 

[WiiCrazy]

Well I wrote above previously you should use that membrane... probably it's somewhere around...

Don't use bare hands to make the contacts

 

[AdamBrunt]

I did tell you it was a stupid question

Just found it lying next to my DVD player

 

[AdamBrunt]

Wahoo !!!!

3.2(EUR) in the bottom right hand corrner

I didn't think it was going to do it at first.

Next step ... insert the autoboot wadmanager DVD

And also (hopefully) remembering how the controller goes back together

 

[EmperorOfCanada]

Gooooo AB!

*cheers you on*

 

[AdamBrunt]

Next question ... presumably starfall will be installed ? If I *wanted* to use the autoboot 3.2 system ISO, would starfall still be installed then ?

 

[AdamBrunt]

autoboot wadmanager just goes to a black screen ??

 

[WiiCrazy]

Well sorry for you, it seems we are in the same boat... I told thousand times that some system files corrupted bricks prevent booting but noone listened to... here now we have second concrete example... but don't worry, your wii is still able to run unsigned code, put in the freeloader disc in the recovery menu and see for yourself... there is a huge ground there for exploit

 

[AdamBrunt]

so - is this the end of the road for my Wii ?

 

[WiiCrazy]

so - is this the end of the road for my Wii ?

Well just try a few autoboot discs more... the first should be an autoboot zelda... and it's not the end... I am certainly sure that a neat hack to recover those wiis will come along...

An advice, whatever you do, don't upgrade your wii to 3.3... Your wii in current status is fixable in the future but the chances may not be same for 3.3 system version

 

[EmperorOfCanada]

What caused the brick in the first place?

*edit*
I know, bad wad. But is there anything more to the story?

 

[AdamBrunt]

Well just try a few autoboot discs more... the first should be an autoboot zelda... and it's not the end... I am certainly sure that a

Ok - I'll try and find one of those. I have an original Zelda but presumably that isn't going to work.

What other autoboots are there ?? the wadmanager does nothing, the bushing (??) 3.2 system doesn't seem to do anything (the 3.2EUR stays on the screen) ....

QUOTE(WiiCrazy @ Nov 28 2008, 10:59 PM) An advice, whatever you do, don't upgrade your wii to 3.3... Your wii in current status is fixable in the future but the chances may not be same for 3.3 system version

No chance of that surely if the Wii doesn't work

 

[AdamBrunt]

What caused the brick in the first place?

*edit*
I know, bad wad. But is there anything more to the story?

Not as far as I know.

The Wii was working fine. I ran HBC and installed the bad WAD of the SD card. It claimed to have installed fine and exited back to the menu screen whereupon the Wii hung. Rebooted and from then on I got the "system files corrupted" message

 

[WiiCrazy]

Well just try a few autoboot discs more... the first should be an autoboot zelda... and it's not the end... I am certainly sure that a

Ok - I'll try and find one of those. I have an original Zelda but presumably that isn't going to work.

What other autoboots are there ?? the wadmanager does nothing, the bushing (??) 3.2 system doesn't seem to do anything (the 3.2EUR stays on the screen) ....

QUOTE(WiiCrazy @ Nov 28 2008, 10:59 PM) An advice, whatever you do, don't upgrade your wii to 3.3... Your wii in current status is fixable in the future but the chances may not be same for 3.3 system version

No chance of that surely if the Wii doesn't work

Well 3.2 semi-brick fix has nothing to do with your problem since you have the update contents of that disc already... But... if the update process works in these bricked wiis then there is a chance to install a patched boot2...(too dangerous to try

)

Still patching the menu from apploader has a great potential in fixing these bricked wiis

 

[AdamBrunt]

so, short term I presume I need a new Wii

 

[AdamBrunt]

Oh my goodness there is a God !!!!

My wii is no longer bricked.

I assume you tried this WiiCrazy but I went to the Hackmii site, found this ISO apploader template, unzipped it, regionpatched it and ran it through Wii Bootme to make it autoboot. Put in the Wii at the "3.2(EUR)" screen and it boots direct to the HBC. From there using WAD manager to uninstall the shitty MPlayer channel was easy.

As I say, WiiCrazy, I assume you have tried this already .....

Anyway - you will not believe how happy I am that my wii is fixed

Many many thanks guys for the help - especially after my "dumb ass" moment with the membrane earlier