Hacking RELEASE: v4.2 Safe Firmware Updater

[zektor]

I updated throw this guide ,safe update v4.2, and i did the thing you mention, but if thats the case how do i boot up via boot2? orelse am i screwed?

I was not aware (and apparently neither were you) that your Wii was region borked. If you don't know how to boot into boot2, chances are you didn't make a nand backup either. The program detects the region your Wii firmware is CURRENTLY on and applies that update. The official Nintendo update works in precisely the SAME manner. There has been literally dozens (if not hundreds) of threads warning of the dangers of region hacking your Wii...as well as the extreme danger of updating a region hacked Wii....via installers or official.

If you didn't know your Wii was region hacked and falsely sold to you as a true USA console, I feel for you. You actually could have discovered this at point of sale by simply looking at your serial number. If your Wii is bricked because of it, it was not my installer. It was Nintendo's firmware update that blocked out the region hacking.

 

[bowser]

What's the exact difference between a region hacked and native USA console? I want to know the technical details. I have a NTSC-J Wii region hacked to NTSC-U. So I guess I shouldn't update to 4.2U.

 

[Groomery]

I updated throw this guide ,safe update v4.2, and i did the thing you mention, but if thats the case how do i boot up via boot2? orelse am i screwed?

I was not aware (and apparently neither were you) that your Wii was region borked. If you don't know how to boot into boot2, chances are you didn't make a nand backup either. The program detects the region your Wii firmware is CURRENTLY on and applies that update. The official Nintendo update works in precisely the SAME manner. There has been literally dozens (if not hundreds) of threads warning of the dangers of region hacking your Wii...as well as the extreme danger of updating a region hacked Wii....via installers or official.

If you didn't know your Wii was region hacked and falsely sold to you as a true USA console, I feel for you. You actually could have discovered this at point of sale by simply looking at your serial number. If your Wii is bricked because of it, it was not my installer. It was Nintendo's firmware update that blocked out the region hacking.

Thats true it had happens the same result with Nintendos official update,and i didnt realize it was korean, and the seller doesnt told me but i want to test and do a boot 2, shall i set up my sd memory on a speciall way or how does it work?

 

[Jacobeian]

what happen if a patched IOS70 is already installed (before updating the system menu) ? Did it get overriden by your update or does the fact version number are the sames ensure it won't be re-updated ?
Since it's probably overwritten, it could be a good idea to first check if IOS70 is already installed before downloading it again ? This can be done in a few lines of code... I think it's always safer to first DOP IOS70 if you want it, before updating the system menu...

It will get overwritten, and to be safer, it always updates everything (in case you're an idiot and previously installed a stubbed IOS in one of the positions or something).

The idea here is to only apply Nintendo updates without any patches whatsoever. If you want to use patches, you are able to add them yourself afterwards. The app is designed for everybody to use, and those of us that hate piracy do not want any trucha patches in our system except those in the custom IOSes.

Well, since there is only one and no stub version of IOS70 and since it's always safer to install the IOS before the system menu, I would have thought checking if IOS70 was already installed before downloading it would have been nice (just as the Nintendo Updater is doing by the way), to avoid any potential risks when patching the system menu IOS after its installation.

I will give a look to the source and modify it like that for me, then if it works, I could post it here

 

[Cline2]

I used Firmware Updater v4.2 (before this one came out) to install all then HBC was upside down so I used DOP-Mod to imstall IOS60 then HBC is back to normal will it be fine??? Let me know Thanks

 

[zektor]

Thats true it had happens the same result with Nintendos official update,and i didnt realize it was korean, and the seller doesnt told me but i want to test and do a boot 2, shall i set up my sd memory on a speciall way or how does it work?

I would get in touch with that seller if possible and demand a refund! It would have been fine if he had just LEFT it as a Korean console. The update would not have harmed a thing.

When you install the hackmii installer it gave you an option to install bootmii to boot2 or IOS. It *must* have been installed to boot2 to restore a brick. When you installed, it would have created the necessary bootmii folder with three files inside on your SD card. To boot into bootmii, you would then simply have that SD card inside of your system and turn it on.

But again, since you are asking me how it works and have not mentioned anything about backing up your nand, I have the feeling you did not do these things. If not, the only thing you can do at this point is to wait to see if somebody can fix this issue (doubtful) or maybe contact Nintendo, tell them you did the official update and you are getting the error. Chances are they will tell you that your console has been fitted with an unauthorized device, but maybe if you tell them your story on how the store you purchased it from lied to you....maybe they will help. I don't know honestly. I never messed around with region hacked consoles. There is just no need for it.

 

[KiiNG]

What's the exact difference between a region hacked and native USA console? I want to know the technical details. I have a NTSC-J Wii region hacked to NTSC-U. So I guess I shouldn't update to 4.2U.

As far as I'm aware, the issue is specific for Korean Wii consoles. Hardware wise, I know they have a different power supply module, but beyond that, I haven't a clue. I can't relate as I have a NTSC-U Wii running.. yep, NTSC-U firmware, but I've read a few threads about people with NTSC-J Wii consoles updating without any issues. Then again.. there's really no point in updating right now, and by the time you really need to all the details will be ironed out cleanly.

 

[Groomery]

Thats true it had happens the same result with Nintendos official update,and i didnt realize it was korean, and the seller doesnt told me but i want to test and do a boot 2, shall i set up my sd memory on a speciall way or how does it work?

I would get in touch with that seller if possible and demand a refund! It would have been fine if he had just LEFT it as a Korean console. The update would not have harmed a thing.

When you install the hackmii installer it gave you an option to install bootmii to boot2 or IOS. It *must* have been installed to boot2 to restore a brick. When you installed, it would have created the necessary bootmii folder with three files inside on your SD card. To boot into bootmii, you would then simply have that SD card inside of your system and turn it on.

But again, since you are asking me how it works and have not mentioned anything about backing up your nand, I have the feeling you did not do these things. If not, the only thing you can do at this point is to wait to see if somebody can fix this issue (doubtful) or maybe contact Nintendo, tell them you did the official update and you are getting the error. Chances are they will tell you that your console has been fitted with an unauthorized device, but maybe if you tell them your story on how the store you purchased it from lied to you....maybe they will help. I don't know honestly. I never messed around with region hacked consoles. There is just no need for it.

Thanks for the answers, but i also chipped my console with a wiikey2, and i brought it from Renchi and i live in Sweden, so i dont think its going to work, thanks anyway!

 

[bowser]

I used Firmware Updater v4.2 (before this one came out) to install all then HBC was upside down so I used DOP-Mod to imstall IOS60 then HBC is back to normal will it be fine??? Let me know Thanks

It will be fine. No worries.

 

[phantagom]

What's the exact difference between a region hacked and native USA console? I want to know the technical details. I have a NTSC-J Wii region hacked to NTSC-U. So I guess I shouldn't update to 4.2U.

As far as I'm aware, the issue is specific for Korean Wii consoles. Hardware wise, I know they have a different power supply module, but beyond that, I haven't a clue. I can't relate as I have a NTSC-U Wii running.. yep, NTSC-U firmware, but I've read a few threads about people with NTSC-J Wii consoles updating without any issues. Then again.. there's really no point in updating right now, and by the time you really need to all the details will be ironed out cleanly.

Look here http://gbatemp.net/index.php?showtopic=182...p;#entry2311570

I am trying to find out the issue with the korean Wii's according to bushing a Korean Wii has a key stored in it's sEEPROM, I think a non kor sys menu 4.2 does a check for this key, if it finds, then brick...

 

[zektor]

Thanks for the answers, but i also chipped my console with a wiikey2, and i brought it from Renchi and i live in Sweden, so i dont think its going to work, thanks anyway!

You are chipped? Isn't there a way to boot an autoboot wad manager disc with chipped wii consoles? I don't know....I have never had a chip. Maybe someone can add some input?

Reason I ask is because if he can somehow get to wad manager, I believe if he downloads both the USA and Korean system menus he can fix this. In wad manager perhaps you can uninstall the USA menu using the wad, then install the Korean system menu wad. That might just work to get you back to normal.

 

[zektor]

I used Firmware Updater v4.2 (before this one came out) to install all then HBC was upside down so I used DOP-Mod to imstall IOS60 then HBC is back to normal will it be fine??? Let me know Thanks

It will be fine. No worries.

That will, but you are probably (most likely) going to have issues installing hackmii in the future (ie: when an updated HBC/bootmii is released). Just to check, try running the current hackmii installer and see if you can get in. If it tells you that "no vulnerable IOS found", then you will obviously have a problem. If it does, I would recommend to use this updater to unpatch all of those unneccessary IOS patches the Waninkoko updater did for you

 

[zektor]

What's the exact difference between a region hacked and native USA console? I want to know the technical details. I have a NTSC-J Wii region hacked to NTSC-U. So I guess I shouldn't update to 4.2U.

As far as I'm aware, the issue is specific for Korean Wii consoles. Hardware wise, I know they have a different power supply module, but beyond that, I haven't a clue. I can't relate as I have a NTSC-U Wii running.. yep, NTSC-U firmware, but I've read a few threads about people with NTSC-J Wii consoles updating without any issues. Then again.. there's really no point in updating right now, and by the time you really need to all the details will be ironed out cleanly.

For now I am just recommending that anyone with a region hacked console NOT update. The goal here is not to brick consoles

I have only heard of Korean consoles doing this myself as well, but better safe than sorry. If you do have say a NTSC-J console hacked to NTSC-U and boot2 bootmii installed with nand backup...and want to try....I would like to know how you made out on the update.

 

[drarab2]

im just wondering i accedently updated my to 4.2U will Dop_IOS still work

 

[Rodrigo210881]

I´m a brazilian wii consumer and I have a hacked region Wii firmware. My Wii is korean and my firmware is american.
I update my Wii by official way and get the famous error 003. I have one question: I have a drivekey, with autoboot game disabled. If i enabled and can launch Lego Indiana ou SSBB i can use indian pwns or smash attack to load homebrews? To load cIOS Downgrader for example, or Wad Manager, or Hackmii installer?

Please, do not repair in my English, hardly speak Portuguese, English imagines

 

[Cmurda187]

Thanks Zector and Dr. Clipper for the hardwork and effort you guys put into this updater. I grabbed a copy of this for later use as I am not willing to update to 4.2 until it is needed for something. But when the time comes this is the one I will use. From what I have read I haven't seen a bad report.

 

[FenrirWolf]

I´m a brazilian wii consumer and I have a hacked region Wii firmware. My Wii is korean and my firmware is american.
I update my Wii by official way and get the famous error 003. I have one question: I have a drivekey, with autoboot game disabled. If i enabled and can launch Lego Indiana ou SSBB i can use indian pwns or smash attack to load homebrews? To load cIOS Downgrader for example, or Wad Manager, or Hackmii installer?

Please, do not repair in my English, hardly speak Portuguese, English imagines

Pode tentar se você tem um jeito ativar a função autoboot no modchip. Mas não sei se o error 003 te permite accessar a recovery menu.

My portuguese is sucking too. lolz

 

[Cline2]

I used Firmware Updater v4.2 (before this one came out) to install all then HBC was upside down so I used DOP-Mod to imstall IOS60 then HBC is back to normal will it be fine??? Let me know Thanks

It will be fine. No worries.

That will, but you are probably (most likely) going to have issues installing hackmii in the future (ie: when an updated HBC/bootmii is released). Just to check, try running the current hackmii installer and see if you can get in. If it tells you that "no vulnerable IOS found", then you will obviously have a problem. If it does, I would recommend to use this updater to unpatch all of those unneccessary IOS patches the Waninkoko updater did for you

Yes I tested the hackmii 0.5 it runs fine it said it can be installed on HBC DVDx Bootmii no problem at all!!! Great!!! So my wii is fine !!! Thank God!!! Thank you for the answer!!!

 

[Rodrigo210881]

Interessante. Não entendi a parte do recovery menu. Pretendo, com um outro wii, habilitar a opção do autoboot game. A partir daí tentar usar algum homebrew e tentar recuperar meu Wii!!!

Interesting. I didn´t understood the recovery menu comments. I want, from another wii, to enable the autoboot game option that´s available in drivekey and run, using indiana pwns or smash attack, any homebrew. Perhaps thru this procedure I´ll be able to recovery my Wii.

 

[bnm81002]

Also, make sure you have HBC 1.05 installed before the update as well. Remember, v4.2 system menu deletes the old HBC. Not a big deal if you forget however, as you can always use bannerbomb when done and get the HBC v1.05 installed, but why worry about it later?

now that HBC 1.0.6 is out, would it affect the 4.2 installer in any way? also, does 1.0.6 have a different ID like 1.0.5 does? thanks