Hacking SEEPROM

[JoostinOnline]

If they've already bricked their Wii, this won't help them.

 

[Maxternal]

Oh well,

(and forgive the silly question, youtube is blocked for me here at work.)

 

[neotank19]

This now begs the question, Is a korean wii without its korean key still a korean wii?

 

[DeadlyFoez]

This now begs the question, Is a korean wii without its korean key still a korean wii?

Well, is it still in a korean wii case with a korean serial number? If so then yes. In the case of my former-korean wii, it is in a NA case with a NA serial number and no longer has the korean key so it is in fact a NA wii now.

 

[Maxternal]

Just a thought, I understand CREATING a Korean key is interesting and all from a theoretical, proof-of-concept standpoint but having THAT in this app is what would REALLY make it dangerous, right?

Wouldn't it be better to just post a version that would only be able to DELETE the Korean key? (Even just commenting it out in the code to leave it there as a reference.)
Am I right to assume that deleting the Korean key is pretty much safe for anyone to do?

 

[JoostinOnline]

Just a thought, I understand CREATING a Korean key is interesting and all from a theoretical, proof-of-concept standpoint but having THAT in this app is what would REALLY make it dangerous, right?

Wouldn't it be better to just post a version that would only be able to DELETE the Korean key? (Even just commenting it out in the code to leave it there as a reference.)
Am I right to assume that deleting the Korean key is pretty much safe for anyone to do?

Adding/removing involve the exact same amount of risk. If you look at the source, you will see it's just overwriting the key. And why are you asking Foez? Lol.

 

[tueidj]

If people are able to induce the 003 error without becoming fully bricked (ie. have bootmii installed as boot2) maybe somebody will come up with a better way to fix 003 bricks that doesn't require a wode and a bunch of ISO editing.

 

[Maxternal]

Adding/removing involve the exact same amount of risk. If you look at the source, you will see it's just overwriting the key. And why are you asking Foez? Lol.

Okay ... I just thought in terms of deleting the key prevents/removes an error while creating it potentially causes an error.
but I guess it tampers with unsafe stuff either way.

And I didn't think about exactly who I was asking but I guess my worry was directed at both of you since you both posted a compiled version.

 

[JoostinOnline]

If people are able to induce the 003 error without becoming fully bricked (ie. have bootmii installed as boot2) maybe somebody will come up with a better way to fix 003 bricks that doesn't require a wode and a bunch of ISO editing.

I don't see how, considering you will still need a way to launch homebrew

PS: Did I do all the licensing stuff correctly in KoreanKii?

 

[leo.uff]

It only works if HBC is using ios 58?

 

[JoostinOnline]

It only works if HBC is using ios 58?

No, IOS58 has nothing to do with it. However, you do need to use HBC v1.0.7 or above (preferably v1.1.0 to avoid the no-network bug) so it can disable AHBPROT.

 

[SifJar]

If people are able to induce the 003 error without becoming fully bricked (ie. have bootmii installed as boot2) maybe somebody will come up with a better way to fix 003 bricks that doesn't require a wode and a bunch of ISO editing.

I don't see how, considering you will still need a way to launch homebrew

He specifically stated having BootMii/boot2, which would allow launching homebrew. (If the person doesn't have HBC, they can use the MINI version of HackMii Installer and install HBC, then use it to launch homebrew).

EDIT: Of course, BootMii/boot2 apparently can't be installed on a Korean Wii as seemingly they all have the fixed boot1. So I guess it's a completely hypothetical statement.

 

[JoostinOnline]

If he meant a fix for people with bootmii as boot2, that wouldn't really be necessary as bootmii is a fix itself.

 

[mauifrog]

Great, so now I can put the Korean key back onto my Korean wii, which giantpune was kind enough to remove for me some time ago. But I think I will just leave it the way it is. Very cool stuff, nice work.

 

[Maxternal]

So ... wait ... how was [member='Giantprune'] able to remove the key "some time ago" without this tool? Has he known this little, juicy detail for a while now then?

 

[mauifrog]

So ... wait ... how was [member='Giantprune'] able to remove the key "some time ago" without this tool? Has he known this little, juicy detail for a while now then?

That is what is says in post #1. This has been able to be done for a very long time, but no one released the code. For ethical reasons I believe. Not encouraging people to mass region change wiis. Also I was told that if the process fails, your screwed, even if you have boot2 bootmii. Not sure, but that is my understanding.

ok, what i did to your wii is delete the korean key. so as it is right now, it will forever be immune to any 003 or similar bricks, and aside from the model number on the outside of the case, it is the same as a usa wii. so if you dont care anymore about fixing the 003 brick, i can leave it as it is. the downside of this is that it will no longer play any games encrypted with the korean key, retail or otherwise.

the reasons i dont want people knowing how easy it is to do this is (1) it is dangerous, and (2) it would encourage them to keep buying korean wiis and region changing them and selling them to rip off people. and by dangerous, i mean that if you mess up during the writing process, there is no fixing it. no bootmii or infectious will fix it. it will be D-E-D dead.

 

[tueidj]

The only way it would screw up is if you wrote over the wrong part of the SEEPROM. One of my wiis had "iminurseeprompretendinimkorean" stored at the korean key offset for a long time with no ill effects.

 

[mauifrog]

The only way it would screw up is if you wrote over the wrong part of the SEEPROM. One of my wiis had "iminurseeprompretendinimkorean" stored at the korean key offset for a long time with no ill effects.

Just a thought, but do other values in the korean key cause a 003 brick, or only the korean key?

 

[damysteryman]

As far as I know, it is only the Korean Key.

http://wiibrew.org/wiki/Error_003

Technical cause
System Menu 4.2E/U/J and higher call a new ES Ioctlv(0x45) which got added in IOS70. On older(check!) IOSs this Ioctlv always returns -1017.

IOS tries to encrypt a certain byte pattern with the Korean key and then compares it with hard coded values, if the result matches it returns 0 which will then trigger the error in the System Menu.

 

[mauifrog]

As far as I know, it is only the Korean Key.

http://wiibrew.org/wiki/Error_003

Technical cause
System Menu 4.2E/U/J and higher call a new ES Ioctlv(0x45) which got added in IOS70. On older(check!) IOSs this Ioctlv always returns -1017.

IOS tries to encrypt a certain byte pattern with the Korean key and then compares it with hard coded values, if the result matches it returns 0 which will then trigger the error in the System Menu.

I am no lawyer, but I would think that would be illegal in many countries. At least it should be. Perhaps a class action law suit is needed.