12-12-2011, 03:35 PM
Even in worst case scenario, I think you can still save your console.
Before we assume the worst, I just want to confirm the details. I don't want to suggest a bad solution.
1. Your console boots to a black screen when no SD card is inserted on bootup; you are not even reaching the health screen. You are using Bootmii and/or Priiloader because your system menu is refusing to boot.
2. Your Wii remotes that you are sure were synced to the console beforehand are not connecting in any program or application that supports the use of Wii remotes.
Note that to sync a Wii remote, you must be in the system menu. If the system menu is refusing to boot for any reason, than you cannot sync new Wii remotes. (I'm speaking by my own experiences; I'm have no research to support this - let me know if this doesn't hold true for you).
If these items hold true, then there is both some good news and some bad news for your situation.
Bad News: Your Wii cannot be repaired with software tools; the issue is a hardware problem. In order to get your Wii remotes connected to your console again, it will be necessary to replace the bluetooth module. This does mean you will have to open up your console.
Good News: I believe the procedure is only a moderately difficult fix - I think you can do it yourself. I bet the procedure will be more time-consuming than it is challenging. You can use this as an opportunity to have some fun with hardware.
Even though your Wii remotes won't work, if you can access Bootmii, you can still use your console to play Gamecube games, and access Homebrew applications assuming you have a Gamecube controller.
I believe a bluetooth module costs about $30. I believe a bricked Wii console also runs at about $30 (these are both just rough estimes). I also believe one of the Senior Members at Wiihacks has a supply of bricked Wiis and is attempting to fix them - I think it's Krafter but I'm not sure. If you ask him, he may be willing to sell you one. I think purchasing another console that is already ruined would give you an opportunity to practice disassembling a console and to breathe easy about it (because if you do mess it up, you have nothing to lose if it's already ruined). You may even feel better about handling hardware; this could be a valuable learning experience if you are interested.
I believe the most challenging areas in this procedure will be removing the rubber stoppers, and soldering (I can't remember whether the bluetooth module is soldered in place - hopefully it isn't...). There are forty tiny screws that you will have to remove to completely open the console, but if you have the proper sized screwdriver this shouldn't be a problem.
Alternately, you can probably send your console in and have someone else do this for you. You will probably be charged for both the part and the service.
I'd like to get a Senior member's opinion on this before passing judgment. I have never taken apart a Wii myself; I have only watched a tutorial. Someone else may very well disagree with me.
If you think that a broken bluetooth module is the cause at this point, then the best next course of action would be to start a thread in the bricked issues forums where (hopefully) a Senior member will be in present. From there, another member can verify the problem, and direct you to a member and place where you can purchase another console or bluetooth module.
If you start another thread and privcy isn't an issue, if you PM me the link or post it here, I'd be glad to follow you and help you get set up with the other member. If you do post it here, I think other members may also be able benefit from the information. Once in the other forum, hopefully another staff member can recommend a seller. You may also want to check the market area yourself - you may find something useful there.
To any moderator/ staff members who are viewing this, please don't close this thread! I still am hoping someone will come along with infromation about how to make the latest version of UNEEK work - I still haven't managed to make it work myself. If anyone wants me to move or delete this post since it is steering away from SNEEK/ UNEEK, I'd be glad to. I'm hoping to continue this troubleshooting discussion in a more appropriate thread.
Sorry Hay1tsme. It looks like you have one of the very few consoles with this problem - I rarely have heard of this happening. Hopefully we'll have this figured out soon.
12-12-2011, 03:54 PM
Well, I'm an idiot
All i had to do was sync from the Wii menu, and it worked! Thank you so much for that.
I feel so bad at the time you had to waist because of my stupidity.
Thanks again for the fix
12-13-2011, 03:34 PM
No problem about the time: I needed a break from reality anyway. This very same detail caused me some confusion as well. At least we figured this out now and not after deciding to place an order.
Just curious about the savedata...did you back it up? Even if your console is bricked and or the Wii remotes refuse to connect, you can use a Gamecube Controller to access a savegame manager - there are a few applications for the Homebrew Channel made for backing up and restoring savedata. A few of them do support the use of a Gamecube Controller. This way you can back up all of your data before performing a NAND backup, because doing this will wipe everything: channels, savedata, and the registry. Alternately, you can make a NAND backup, and then I believe you can extract it on a computer.
Now that your console is settled, have you gotten SNEEK and UNEEK working? Do you have a working version of UNEEK and would you mind letting me know what version you are using? I am yet to see a successful boot via UNEEK.
12-14-2011, 01:32 PM
i don't have SNEEK working, so I just said f*** it and got rid of it, but if a working version is found for 4.3u, i'd be glad to know of it.
12-17-2011, 07:35 AM
So you're on 4.3u? You may be able to work around that. I think you can change the system menu version of your NAND dump by using Showmiiwads - it allows you to install WAD files to a virtual NAND. I don't see why it wouldn't change a system menu.
Alternately, many WAD managers support NAND emulation. You could install a system menu on a virtual NAND via a WAD manager. At the moment, I don't have much experience with NAND emulation via a WAD manager, and I'm not 100% sure it's safe. Chances are it is safe, but I never like to assume - I prefer to speak from experience. I tried installing a channel at one point, and I just remember the program crashing; no harm was done though.
Also, if you're interested, you can change your system menu on your actual console to 4.2. Just make sure you install a working version of IOS70 (non-stub version) prior to installing the menu or a full brick will be the result. In this case of changing your real system menu, I'd suggest looking at one of the guides in the recommended section. Changes system menus on newer consoles makes me very nervous.
Again: WARNING: Dangerous procedure.
Last edited by vtwombat; 12-17-2011 at 07:50 AM.
Tags for this Thread