That is correct. cIOSCORP v3.4 won't prevent it as such, but if it's installed prior to 4.2 update, yu can use it to fix error 003.
cIOSCORP v3.5+/DARKCORP can prevent it for 4.2, but if a new update comes out (for example a 4.3 update or something), and a CORP'd Korean Wii updates to it, it will still get it, but like v3.4, it can be used to fix it with future updates.
My Korean Wii has DARKCORP and indiana pwns savefile on it just for this purpose despite having a D3-2 drive, and it's running 4.2E now.
However...
A while back, da_letter_a told me about this post in mauifrog's error 003 fixing thread over at Wiihacks:
http://www.wiihacks.com/bricked-wii-issues...html#post297147
posted by WiiHacks member "RedArrow" (I wonder if: Wiihacks' "RedArrow" = GBATemp's "RedArrow2").
It appears that a modshop in Australia has the ability to fix error 003. I am assuming they would have an official "error 003 fixing disc" to go along with their Waikiki adapter.
I wonder if anyone over in Australia is capable of acquiring this disc(s) from this modshop and dumping it maybe?
If everyone got their hands on that, then we could all fix error 003.
And does anybody know if there's any way for homebrew apps to wite to the serial EEPROM?
Anything already in libogc capable of doing this?
All we would need to do is overwrite the Korean key in a console's EEPROM with a null key bfore running any updates, and then that console will never get error 003.
@thchang:
People buy them because they are so damn cheap due to how cheap Korean Won (Korean currency) is.