Hacking Is this Wii savable? (Syscheck added)

  • Thread starter Thread starter BvanBart
  • Start date Start date
  • Views Views 15,283
  • Replies Replies 142
Well, then you need some guy who can install it with a chip, that's the only way I know.
 
I don't know if it's even possible, but couldn't you somehow trick the wii into using one of the other copies of boot2 by making it believe that the one it's using now is corrupt? It's just a random thought. You would need to be sure that the other copies are valid ones.
 
I don't know if it's even possible, but couldn't you somehow trick the wii into using one of the other copies of boot2 by making it believe that the one it's using now is corrupt? It's just a random thought. You would need to be sure that the other copies are valid ones.
No, because all those apps are grabbing the boot2 version info from the eeprom. His boot2 is not corrupt, it's perfectly fine. It's the info in the eeprom thats fucked up.
 
Can you load retail games if you boot NeoGamma or Gecko OS? If not, can you post the error codes NeoGamma gives you?

Plan B for you could be to just install channels for the stuff you want to have and accept that HBC and disc channel don't work.
 
0__o

Eh... i have some NeoGamma installs... but they do not have the feature to post error codes. Could you link me to a version that does?
HBC is not that important. Playing Metriod etc would be nice though.

EDIT

@ DeadlyFoez

I live in the netherlands :P
 
What you need for your wii to be fully fixed is for someone to make an app for you that will fix the boot2 version written in the eeprom without doing any checks. Have it write v2 and then you can use dop-mii to do a real update to v4. After that all your issues should be fixed.
 
There's nothing wrong with boot2 or the seeprom. Syscheck and DOP-Mii are saying it's version 0 because they can't figure out the real version (DOP-Mii even states this in plain english). If the version in the seeprom was higher than the actual version, the wii wouldn't boot. If the seeprom version were lower than the actual version, boot2 would update the seeprom when it ran.

This is most likely your problem:
HackMii v0.8 installer starting up
PVR = 00087103
running under IOS 58 rev 0x182055 titles are installed
Found IOS 0: revision: 0x0*
It's a DOP-Mii brick.
 
What technically occurs that causes this brick and how is it fixed? I vaguely remember hearing about this type of brick before.

If the seeprom version were lower than the actual version, boot2 would update the seeprom when it ran.
^^Now that I know is not true because as I said in an earlier post...
....there has been many wii's that I have repaired that do have boot2v2 or boot2v3 installed, but I flash on boot2v4 with bootmii already in it and both bootmii and dopmii will tell me that it is boot2v2 or boot2v3 that is installed because they both only look at what is written in the eeprom. Kinda crappy way of checking it.
And to get a little more detailed into it, updating boot2 is always the very last thing I do to a wii before sending it back out the door. I ALWAYS flash boot2v4 just because I don't feel like dicking around and trying to figure out which version is really installed when v4 will work just fine on every wii no matter what is written in the eeprom. Once I getting the SM working back on the wii, I remove my SD card and boot the wii like normal.

So can fully say that your statement is untrue unless there is something about bootmii's boot2 code that prevents the real boot2 from writing to the eeprom.
 
Am I wrong to say that bootmii will go and launch the normal boot2 code if the sd card and files are not found? I was pretty sure that was the way it ran.

I'll trust what you say since you would be one to know for sure, but next time I get another wii in for repair and I will remove bootmii from boot2 and see if the info in eeprom gets updated.... but I could have been sure that I've done things in that scenario before... expecially with the 200+ wii's that I've repaired.
 
Bootmii still interferes with a few things, for example if you press the power button while playing a gamecube game (without an SD card inserted) the wii will reboot to the system menu instead of turning off.

The SEEPROM will never get updated if you manually flash a higher version of boot2 and don't update from the sysmenu. Otherwise the only thing that touches boot2 is IOS and it sets an update tag for the new boot2 to see when it runs.
 
There's nothing wrong with boot2 or the seeprom. Syscheck and DOP-Mii are saying it's version 0 because they can't figure out the real version (DOP-Mii even states this in plain english). If the version in the seeprom was higher than the actual version, the wii wouldn't boot. If the seeprom version were lower than the actual version, boot2 would update the seeprom when it ran.

This is most likely your problem:
HackMii v0.8 installer starting up
PVR = 00087103
running under IOS 58 rev 0x182055 titles are installed
Found IOS 0: revision: 0x0*
It's a DOP-Mii brick.

So it's this issue:
http://code.google.com/p/dop-iosmod/issues/detail?id=33
?

And how is it fixed exactly? Just run the latest DOP-Mii?
 
Hello :P. I can assure you it;s NOT a Dop-mii brick. I haven't used Dopmii on this Wii yet. (I only started it and it said it can do nothing for me.) So that's not right.

So i need a program that can write to Boot2 without checking what's in it now :O? Were would i be able to find that?
I will see if i can find another Syscheck version as is stated on the Google site.
 

Site & Scene News

Popular threads in this forum