Hacking Error 003

  • Thread starter Thread starter damysteryman
  • Start date Start date
  • Views Views 17,896
  • Replies Replies 36
This has nothing to do with support or sanctioning. They destroy peoples property willfully. Not by accident but fully intentional. That's not ok and it's not "a risk we all take" it's royal douchery.
I really hope they won't get away with this.
 
can anyone with that 003 error try to get into the rescue menu? (savemii or press all 4 digital directions at once on a GC controller in the 4th port)
I'm pretty certain that it will still work and you should be able to fix it from there!
 
Only if you have the trucha bug in your system menus IOS. Otherwise I don't see how. Maybe if you are on 4.2E, once Smashstack for the PAL-version of Smash Brothers is out.
 
yes i was able to access the Rescue Menu .But none of the UUDV2 or any other disc works i think we need a disc that uses IOS70 rather than IOS60 or IOS 35.

I have also attached the infectus and made a nand dump . however i have been unsuccessfull to unbrick it since the nand.bin has no keys in it
and the amoxiflash takes like 2-3 hrs to dump and write 512mb any help on how to speed it up.
 
If you have your keys.bin and if you asked someone with a wii which is similiar to yours (date of purchase LUXX etc...) You could use betwiin and change keys in the NAND.bin with yours and then flash your wii with it.
 
hey DA_letter_a, since you can make the 003 error appear can you try to delete the IOS4x to see if that is how it detects korean wii, it will be very helpful as we still don't know for sure how its detect korean region modded wii.
 
I wonder. People are saying that it's possible to boot using Indiana Pwns or SSBB. (WiiCrazy link above)
This games should have a modified save game already on your Wii in order to work.
Also, it's said that an AutoBoot would be able to fix it.
Ok, I've tried the AutoBoot option using a drivekey already modified to autoboot. The problem is, it's not really working because UUDv2 (or any autoboot disk for that matter) works..
Is there really a way to fix it?

I've more than a hand full of customers with #003 error (all of them are Korean wiis modded to US).
 
Wateva said:
I wonder. People are saying that it's possible to boot using Indiana Pwns or SSBB. (WiiCrazy link above)
This games should have a modified save game already on your Wii in order to work.
Also, it's said that an AutoBoot would be able to fix it.
Ok, I've tried the AutoBoot option using a drivekey already modified to autoboot. The problem is, it's not really working because UUDv2 (or any autoboot disk for that matter) works..
Is there really a way to fix it?

I've more than a hand full of customers with #003 error (all of them are Korean wiis modded to US).

im asking the same question?
 
I have a bricked Wii bought in China that got the Error 003 after updating it to 4.2.

I can access the rescue menu from the GC controller, but how do I get to unbrick my Wii from there?
 
Wiiwu said:
hey DA_letter_a, since you can make the 003 error appear can you try to delete the IOS4x to see if that is how it detects korean wii, it will be very helpful as we still don't know for sure how its detect korean region modded wii.

I think it reads the korean key in the eeprom, then you will know its a korean wii that region changed
 
opac said:
I have a bricked Wii bought in China that got the Error 003 after updating it to 4.2.

I can access the rescue menu from the GC controller, but how do I get to unbrick my Wii from there?


How can you access the rescue menu from the GC controller? Can you give me detailed instructions? Did you have to unmount it?
 

Site & Scene News

Popular threads in this forum