Hacking Bricked 4.0(u) Wii

  • Thread starter Thread starter SageonX
  • Start date Start date
  • Views Views 2,524
  • Replies Replies 15

SageonX

Member
Newcomer
Joined
May 23, 2009
Messages
8
Reaction score
0
Trophies
1
XP
11
Country
United States
Hello all

As you can already tell from my thread topic, my Wii is bricked and would like to request some help. After scouring the internet and dozens of topic forums, I have found similar problems relating to mine, but not all are entirely in my situation (or so I believe).

Posting here had been my last resort so here it goes!

After following Davi92's Downgrade for System Menu 4.0, I was able to get as far as step 7. I installed all of the IOSes; excluding IOS35. I did not install the latest shop channel, etc. because I thought that was not necessary. I also tried to downgrade to verion 3.2(u) of the IOS and a little after, I made a mistake of not installing IOS60 (I misread the direction of holding down (+) and then (-)).

I'm pretty screwed now, having attempted to us the SaveMiiFrii and not receiving the screen everyone else gets (the FW appearing etc.)

I do not have a mod chip installed, it's all soft modded.

Here are my specs for my Wii:

Updated: 4.0u
-No Previous HBC Installed
-No soft modded etc

Soft Modded with the BannerBomb Exploit. Installed HBC Successfully (thanks to Comex and everyone else who helped with it's development).

Now, when I boot up my wii, I get a black screen (no opera message that asks for troubleshooting).

Any suggestions on what I should do?
 
if you dont have preloader, bootmii, or a mod chip i think youre in trouble

you should always install preloader before upgrading IOS files
 
so basically you almost downgraded to 3.2 but did not install an ios correctly and THAT bricked your wii? you're not very clear on what actually went wrong?
If you install system menu 3.2 then you need ios 30 the thread says, not 30
and if you want to stay at 4.0 then it's ios60
 
I have a very similar probleme; but i had previously installed preloader.
I have tried many times now to load the preloader but with no success.
The screen stays black and the wiimotes won't connect.
I don't know if this really helped anyone to help us.
But thanks for trying
 
to have more chance with bootmii (boot 2) try to buy an OLD wii
wink.gif


Good luck
 
manias said:
so basically you almost downgraded to 3.2 but did not install an ios correctly and THAT bricked your wii? you're not very clear on what actually went wrong?
If you install system menu 3.2 then you need ios 30 the thread says, not 30
and if you want to stay at 4.0 then it's ios60

I did place in IOS30, just not 35.

Yes, it is a retarded guide--not very clear on instructions = unnoob-proof

No, I did not install preloaded (i think).

I had bootmii, but it disappeared from my HBC o_o




Question: Is there a way to factory reset (hard reset) the wii at all?
 
SageonX said:
manias said:
so basically you almost downgraded to 3.2 but did not install an ios correctly and THAT bricked your wii? you're not very clear on what actually went wrong?
If you install system menu 3.2 then you need ios 30 the thread says, not 30
and if you want to stay at 4.0 then it's ios60

I did place in IOS30, just not 35.

Yes, it is a retarded guide--not very clear on instructions = unnoob-proof

No, I did not install preloaded (i think).

I had bootmii, but it disappeared from my HBC o_o




Question: Is there a way to factory reset (hard reset) the wii at all?
Dude i dont mean to sound rude but unless u have bootmii installed and usable ure screwed and no way to fix it.
 
I’d send the Wii too Nintendo. Since they will know what you were doing your Wii will be out of warranty. But I’m sure they will just charge you the flat repair fee for non warranty Wii's. I think it’s about $179. This option is cheaper than a new Wii.
 
Eh.. It's fully bricked. Thought I'm not gonna give up--even if it does seem hopeless to begin with.

It's a software issue.. I'm guessing. Anyway, thanks for all the replies!
 
SageonX said:
Eh.. It's fully bricked. Thought I'm not gonna give up--even if it does seem hopeless to begin with.

It's a software issue.. I'm guessing. Anyway, thanks for all the replies!

Dude, don't fucking guess. It is definite that it is a software issue, people here told you already.

I hate guesstimates.
 
I wonder if everyone is this friendly
wtf.gif


Either way, it shouldn't pose a problem to you--since you only offered a very tedious input.
 

Site & Scene News

Popular threads in this forum