Hacking wii 4.3J - brick?

darksent21 · Nov 27, 2019

Hello,

It seems that my wii is bricked?
Wii = Japanese with 4.3j
Modmii installed as IOS.
Priiloader installed.

Issue:
Whenever using USB GX Loader or just even in the dashboard, random crash occurs.
When this happen, the wii will be turn off by holding the power button or unplug cable.
Once turning it on again, it will only display black screen with a single blink of blue light.

When holding the reset button, priiloader wont load. (it's working before)
Never install any WAD nor changing the system menu.

Weird Part:
By doing the "hold reset button" multiple times. (100+ times).
It sometimes load the priiloader and I'm able to fix my wii.

Real Issue:
It keeps happening again once the USB Loader GX crash.

Can someone give me advice on how to avoid repeating the weird part? or why does the priiloader wont work once the USB Loader GX crashed?

XFlak · Nov 27, 2019

First of all, you have bootmii installed as ios, not modmii, modmii is a wii related program that runs on windows.

Second, this doesn't sound even remotely like a brick.

Third, to access priiloader you should have the wii powered off, then when the wii is booting up hold reset. It's odd if this doesn't work for u.

Lastly, please post a syscheck

darksent21 · Nov 30, 2019

I just restart my wii by holding reset for 89 times today before the priiloader menu pops out.

I use sysCheck but halfway through, it got stock with blue led blinking. This is the only details when I open the CSV:

sysCheck v1.6.2 by Erik Spyder

Region: NTSC-J
The system menu v512 is running under IOS58 (rev 6176)
Hollywood v0x11
Console ID: 103090520
Boot2 v4
Found 91 titles
Found 32 IOS on this console
Found 15 IOS Stubs on this console

darksent21 · Nov 30, 2019

I use sysCheck v2.1.0b18 instead:

sysCheck v2.1.0b18 by Double_A and R2-D2199
...runs on IOS58 (rev 6176).

Region: NTSC-J
System Menu 4.3J (v512)
Priiloader installed
Drive date: 2007.02.13
Homebrew Channel 1.0.0 running on IOS0
Hollywood v0x11
Console ID: 103090520
Boot2 v4
Found 91 titles.
Found 47 IOS on this console. 15 of them are stub.

IOS4 (rev 65280): Stub
IOS9 (rev 1034): No Patches
IOS10 (rev 768): Stub
IOS11 (rev 256): Stub
IOS12 (rev 526): No Patches
IOS13 (rev 1032): No Patches
IOS14 (rev 1032): No Patches
IOS15 (rev 1032): No Patches
IOS16 (rev 512): Stub
IOS17 (rev 1032): No Patches
IOS20 (rev 256): Stub
IOS21 (rev 1039): No Patches
IOS22 (rev 1294): No Patches
IOS28 (rev 1807): No Patches
IOS30 (rev 2816): Stub
IOS31 (rev 3608): No Patches
IOS33 (rev 3608): No Patches
IOS34 (rev 3608): No Patches
IOS35 (rev 3608): No Patches
IOS36 (rev 3608): No Patches
IOS37 (rev 5663): No Patches
IOS38 (rev 4124): No Patches
IOS40 (rev 3072): Stub
IOS41 (rev 3607): No Patches
IOS43 (rev 3607): No Patches
IOS45 (rev 3607): No Patches
IOS46 (rev 3607): No Patches
IOS48 (rev 4124): No Patches
IOS50 (rev 5120): Stub
IOS51 (rev 4864): Stub
IOS52 (rev 5888): Stub
IOS53 (rev 5663): No Patches
IOS55 (rev 5663): No Patches
IOS56 (rev 5662): No Patches
IOS57 (rev 5919): No Patches
IOS58 (rev 6176): USB 2.0
IOS59 (rev 9249): No Patches
IOS60 (rev 6400): Stub
IOS61 (rev 5662): No Patches
IOS62 (rev 6430): No Patches
IOS70 (rev 6912): Stub
IOS80 (rev 6944): No Patches
IOS222 (rev 65280): Stub
IOS223 (rev 65280): Stub
IOS249[56] (rev 65535, Info: d2x-v9beta(r47)): Trucha Bug, NAND Access, USB 2.0
IOS250 (rev 65280): Stub
IOS254 (rev 65281): BootMii
BC v6
MIOS v10

Report generated on 2019/11/30.

FancyNintendoGamer567 · Nov 30, 2019

What the fuck is that cIOS? v9 beta r47? That would probably explain why. Just get v8 final or v10 beta52 and it will probably work.

FrenezyFr · Nov 30, 2019

The HBC version is not correct. You will need to update Homebrew channel. Installing IOS236 would also be a good thing, as well as the d2x cios in version 8 or 10 beta 52. The easiest way would be to use Modmii and redo a complete hack

darksent21 · Dec 1, 2019

As for my HBC. I thhink the syscheck doesnt display the correct one as I already updated it to the latest version.
As for the IOS 236, I believe it isn't needed:

Cyan said:
No, it's not needed.

loading games from USB requires a patched IOS, but NOT the IOS36 (236 is the resulted IOS after patching IOS36).
IOS236 was used to grant NAND access (to install wads, edit system files, patch signature check, etc.)
It's not needed anymore as a clean IOS58 can do the same with updated homebrew now.

Playing games from USB requires an additional patch to redirect Disc access to USB or SD, and IOS236 is not doing it. only Hermes and Waninkoko/d2x are.

btw, as what you guys suggested, I updated my cIOS into v10 beta52.
As for now I'm staying away with USB Loader GX and use Wiiflow lite instead. If I don't encounter any error or Bricks in a week or two, I'll test USB Loader GX again.

jeannotte · Dec 1, 2019

darksent21 said:
As for my HBC. I thhink the syscheck doesnt display the correct one as I already updated it to the latest version.
As for the IOS 236, I believe it isn't needed:

btw, as what you guys suggested, I updated my cIOS into v10 beta52.
As for now I'm staying away with USB Loader GX and use Wiiflow lite instead. If I don't encounter any error or Bricks in a week or two, I'll test USB Loader GX again.

Hello,

Can you post a new syscheck report (more recent version), but this time follow this guide ==>https://gbatemp.net/threads/posting-a-system-check.300279/

thank you .

Cryoraptor · Dec 6, 2019

The fact that Wiiflow is working means something is wrong with your USB Loader GX installation or the cIOS it uses. Since it was working fine before I don't believe a progam/cIOS randomly kills itself overnight and you've probably installed another app or modification that's overwritten the cIOS USBGX is using and ruined it.

darksent21 · Dec 8, 2019

Cryoraptor said:
The fact that Wiiflow is working means something is wrong with your USB Loader GX installation or the cIOS it uses. Since it was working fine before I don't believe a progam/cIOS randomly kills itself overnight and you've probably installed another app or modification that's overwritten the cIOS USBGX is using and ruined it.

Its like a week now and no crash happened using the wiiflow. I'll now switching to USB Loader GX to test the updated CIOS.
Also, maybe my faulty flash drive is one of the culprit why I experiencing some crash. I'm now using a new one.

I hope that I won't encounter any issue with the loader now since activating the priiloader while booting is so tedious (only happened if the usb loader GX crashed, otherwise I boot the priiloader menu as it used too).

Cryoraptor · Dec 8, 2019

darksent21 said:
Its like a week now and no crash happened using the wiiflow. I'll now switching to USB Loader GX to test the updated CIOS.
Also, maybe my faulty flash drive is one of the culprit why I experiencing some crash. I'm now using a new one.

I hope that I won't encounter any issue with the loader now since activating the priiloader while booting is so tedious (only happened if the usb loader GX crashed, otherwise I boot the priiloader menu as it used too).

Your flash drive isn't faulty because it wouldn't work with Wiiflow otherwise. There's definitely something wrong with your USBGX or the cIOS it's using.

Try the updated cIOS and see if it works. If it doesn't work then delete your USBGX and reinstall it. If it still doesn't work then something has gone majorly wrong with your Wii.

However since you're using Wiiflow now, if USBGX still won't work then you can just keep using Wiiflow.

darksent21 · Dec 15, 2019

Hello,

Thanks for the info. While using USB Loader GX again, my wii got stuck again in a black screen while the priiloader isn't working again though this time, the loader didn't crash just when I turn it on it became like that.

I can't provide the updated syscheck info as of now as I'm still trying the hold reset button to boot into the priiloader. (56+ times as of now).

I also found some guy who has the same problem with me:
https://www.reddit.com/r/WiiHacks/comments/7avxyx/black_screen_on_boot_priiloader_not_working/

tried loading Priiloader by holding reset and powering on while holding, nothing. Powering on then holding reset, nothing. I tried with and without the USB HDD plugged in. I tried different cables (composite and component, and these cables do work with another Wii). I've tried different TVs as well if that makes a difference. I read that a failed bluetooth module can cause this, but my Wii can be powered on by the remote so that isn't the case for me.

I also post my issue to priiloader github as I'm not sure which is the culprit.
Sorry but I'm really sad that I can't play my wii normally while having this issue.

I can't trigger the issue but the closest is by doing the ff:

*using USB Loader GX*
*Shutting down the wii directly by unplugging it while in game*
* Random Crash (which doesn't happening after I update my cIOS)*

FrenezyFr · Dec 16, 2019

Have you reinstalled the System Menu since then? If yes, did you reinstall Priiloader right after? After installing Priiloader did you block online updates and game updates?

Cryoraptor · Dec 17, 2019

Honestly I'd just keep using WiiFlow at this stage instead of trying to fix USBGX, there's obviously a deeper issue that you could make worse by trying to fix. Did you uninstall USBGX and then reinstall it?

As for Priiloader, you've obviously messed with an IOS it uses. Have you recently installed any apps that install a cIOS?

The only other thing I can think of is that you've installed a new system menu and it's overwritten some cIOSes and IOSes that these apps use. If things continue to not work then all I can suggest is uninstall the apps, install a new System Menu to restore clean IOSes and stub cIOSes, and then reinstall the apps and the required cIOSes. If the problem still continues then it's most likely wear and tear and the Wii's hardware is degrading. As the Wii is getting old we are going to start seeing more and more cases where it's simply a hardware problem since a lot of Wiis are passing the 10 year mark now and their hardware is going to be less than intact from all those years of operation. I highly doubt that your case has anything to do with hardware though.

FrenezyFr · Dec 17, 2019

If I understood correctly the Wii does not start any more. A black screen with no more access to Priiloader. So Full brick. If this is the case the only hope is Bootmii in Boot 2. Reinstalling the System menu removes Priiloader and reinstalling the System Menu does not modify the IOS or cIOS. Menu 4.3 uses IOS 80 and 4.2 IOS 70. To reinstall clean IOS, either you have to do an official update, which will also remove
Priiloader, either you have to reinstall the IOS manually after having recovered them with NUSD and installed with a WadManager for example. So if I understood correctly and that a reinstallation of the Menu system was made (Manual or official with an update of the Wii) and that Priiloader was not reinstalled right after, it remains only as hope Bootmii in boot 2.

darksent21 · Dec 18, 2019

Thanks for the help guys. I really appreciate it. Though, to clear things up:

1.) I installed Bootmii as an IOS unfortunately
2.) I didn't touch anything on the system menu. I just installed the the needed IOS for 249 (v10 beta52) to load USB Loader GX
3.) "Wii does not start any more. A black screen with no more access to Priiloader" - yes that is correct. when I press and hold the reset button, the priiloader menu won't display. BUT... If I do it multiple times, like 50+ attempts, I can manage to pop up the Priiloader menu. And when it does, my wii will is functioning normally again. I can activate the priiloader menu anytime and play the game.

However, when the crash occurs, I will again get a black screen when booting my wii.

I created a thread on github DacoTaco for him to look if the culprit is the priiloader.
https://github.com/DacoTaco/priiloader/issues/219

PS. I only encounter this issue if I'm using USB Loader GX.
I don't encounter this if I'm using WiiFlow or just booting into System Menu.
Also, no, my bluetooth adapter is working since I can turn on my wii using the wiimote.

Alexander1970 · Dec 18, 2019

darksent21 said:
I created a thread on github DacoTaco for him to look if the culprit is the priiloader.
https://github.com/DacoTaco/priiloader/issues/219

I think @DacoTaco has an Solution:

PRIILOADER 0.9
(in "Progress"...)

darksent21 · Dec 18, 2019

alexander1970 said:
PRIILOADER 0.9
(in "Progress"...)

Yes hopefully.
Also for reference, my issue is VERY VERY similar to these guys

https://gbatemp.net/threads/avoid-bricking-again-usb-loader-gx-wad-priiloader.383458/ (first half of his problem)
https://gbatemp.net/threads/bricked-wii-priiloader-wont-load.251452/
https://gbatemp.net/threads/i-think-my-wii-is-bricked-and-priiloader-is-not-loading.309121/
https://www.reddit.com/r/WiiHacks/comments/7avxyx/black_screen_on_boot_priiloader_not_working/

Alexander1970 · Dec 18, 2019

darksent21 said:
Yes hopefully.
Also for reference, my issue is VERY VERY similar to these guys

https://gbatemp.net/threads/avoid-bricking-again-usb-loader-gx-wad-priiloader.383458/ (first half of his problem)
https://gbatemp.net/threads/bricked-wii-priiloader-wont-load.251452/
https://gbatemp.net/threads/i-think-my-wii-is-bricked-and-priiloader-is-not-loading.309121/
https://www.reddit.com/r/WiiHacks/comments/7avxyx/black_screen_on_boot_priiloader_not_working/

I think more with this like he mentioned.

...this has to do with the dol's high entrypoint and it overwriting priiloader.

Hacking wii 4.3J - brick?

Member

Wiitired but still kicking

Member

Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

XP not matters.

Member

XP not matters.

Similar threads

Popular threads in this forum