4.2 BlackScreen Brick, WiiRemote are not synced
I have a black screen brick. It was appeared unexpected.
Wii just worked and in one day stopped turn-on and WiiRemote are no longer synced.
What is installed:
4.2U, HBC 1.0.7, Priiloader 0.1 r15, no chip, boot2v4 (no BootMii), Confiurable USB Loader via IOS222/223, latest BootMii as IOS (NAND backup is available).
[-] wiiRemote are never sync (not on boot, not in Priiloader, not in HBC), SYNC button doesn't help
[+] WiFi works excellent from all the software
[-] System Menu 4.2 doesn't start (just a black screen, disc is spinning if inserted).
[+] Priiloader starts weel
[+] It is possible to boot BootMii as IOS from Priiloader
[-] It is NOT possible to boot HBC 1.0.7 from Priiloader directly (trap on start, It is caused by update HBC 1.0.6->1.0.7. (1.0.6 was loaded well). I think/hope Priiloader update 0.1->0.4b will help, but I want to do this after repair the console)
[+] It is possible to load HBC 1.0.7 in a way: Priiloader->BootMii->HBC 1.0.7
[-] it is NOT possible to get IOS statuses as all the software stuck near IOS2XX: IOS Check, signCheck, sysCheck, sysCheck с DOP-Mii...
What can\should I do? I've spent all the ideas I had....
Attachment 2999Attachment 3000Attachment 3001Attachment 3002Attachment 3003Attachment 3004
Detailed (long) description, what was installed from the beginning:
4.2U, HBC 1.0.6, Priiloader 0.1 r15, no chip, boot2v4 (no BootMii), Confiurable USB Loader via IOS222/223.
Wii stopped working 27 June 2010 (Note that 4.3 System Menu is out 21 June 2010).
So, from the beginning I thought that Wii was update somehow to 4.3 and bricked.
(Priiloader options "block disk updates" and "block online updates" were enabled).
So, I bought GC controller and boot savemiifree (all D-pad buttons down). Label "4.2(USA)" appears, so the Wii was not updated to 4.3 (or at least was not fully updated to 4.3).
Then I tried to boot Priiloader - success. System menu was not stated from Priiloader (just black screen, if disc is inserted - it spins, WiiRemote are not synced).
From Priiloader I was able to boot HBC 1.0.6. So, I tried to check the system by: IOS Check, signCheck, sysCheck, sysCheck с DOP-Mii...All of them are stuck on almost the same positions (near IOS222). I'll upload the print screens if required.
So, I can't provide you with detailed .csv file as all of the software above are writing the .csv file at the end of checking. (I am trying to contact software developers to improve soft a bit: write the .csv file on the fly, not after all th checking).
I tried to boot Configurable USB Loader:
using IOS222 - stuck on loading (show only main picture)
using IOS223 - stuck on loading (show only main picture)
using no IOS - started well, trying to mount HDD (no luck as no USB IOSes), WiiRemote doesn't sync.
On this forum I read thet it is possible issues with Bluetooth module. How can I check my bluetooth module?
In one moment I installed HBC 1.0.7 (each time when 1.0.6 started it suggest me update HBC to 1.0.7, one time I was tired and allow to install HBC 1.0.7)
HBC 1.0.7 was installed successfully, I've installed BootMii as IOS to make a NAND dump. At the moment HBC is working well if was loaded from BootMii (PriiLoader->BootMii->HBC 1.0.7),
but doesn't start in a way (Priiloader->HBC 1.0.7 (crash on start). Priiloader->HBC 1.0.6 (worked well before the update)).
Can someone suggest me what should I do the next? :confused: