Hacking Some info: Can this be an hardware problem?

  • Thread starter Thread starter actar
  • Start date Start date
  • Views Views 1,272
  • Replies Replies 7

actar

Well-Known Member
Member
Joined
Feb 3, 2011
Messages
371
Reaction score
76
Trophies
0
Location
Torino (Italy)
XP
214
Country
Italy
Hello to all.

I need some ideas for a problem that has had a user.

Before I tell you the little info you information that I have on his Wii
4.3E without GameCube port
Priiloader installed.

What he did:
Made the mod (but I don't know the site followed for the mod) and it played without problems.
After a few days, restarting wii: black screen

What ha can do:
The priiloader starts, but DO NOT connect the wiimote.
In priiloader main menu, after wait 15 seconds to boot the system menu with RESET, the screen returns to black

What has assured me:
that had NOT activated on priiloader the hacks "Lock System Menu with Black Screen"


THEN
priiloader start: it isn't a full brick
before the "problem" the system menu works good: no semi-brick for custom theme or wad channel

CAN BE
1-bluetooth module?
but if I don't say wrong.. if this module doesn't work, priiloader won't start... but I'm not sure.
Someone can confirm that (or not)

2-Other hardware problem?
Shit.. the Wii is new..

3-What else?



SORRY FOR THE LONG POST (and sorry for my bad english)
 
hmm, first thing that comes to mind is hes using the 'new' wii remote (RVL-CNT-01-TR?) and since priiloader was compiled with a libogc prior to 1.8.9 it isnt compatible with his remote.

Sounds a little suss that "After a few days, restarting wii: black screen" happens out of nowhere, anyone else in house that may be playing practical jokes with hacks.ini?

If priiloader loads i find it hard to believe it would be hardware anyway.
 
Definitely bad bt module, or some other hardware on the mainboard affecting the bt module. If you enable the force standard recovery menu hack, this will load rm same as savemiifrii which should be working without issue with the bad bt module.
 
The version used by the user is the official 0.7, but he install it with using an old remote.
And he apply some patch without problems.
And hacks.ini wasn't been modified.

Anyway trying to start SM from priiloader menu with RESET (after 15 seconds) doesn't work.

The problem is that without GC ports, is quite difficult to do anything. :(

But if you saying me that with a BT module broken, priiloader CAN start, I hope the problem is with that (easy to change and low cost).
 
Priiloader, savemiifrii, boot2 bootmii, hbc, hb app- all work without issue with a bad bt module.

System menu, system channels, wii games, wiiware, vc- do not work with a bad bt module.

I would try to replace the bt module, they are pretty cheap.

Possibly some evil homebrew kills bt module, seems to happen sometimes. The module can be fixed with the proper equipment to reprogram it when this happens.
 
  • Like
Reactions: actar
I had this problem in the past.
Wii just booted black screen, out of the bleu.
Did nothing to the system prior.

luckely I had bootmii@boot2, and was able to make a fresh nand with ohnswanzenneger, as I had no bootmii dump lying around.
It was'nt my BT module at all..
 
In the end the problem was solved.

It was just the bluetooth module broken, once replaced the Wii started to work properly.


Thanks guys (to me for the info, and from the user for the Wii). ;)
 

Site & Scene News