Hacking WiiKey Update 1.9g Success Reports

[klyick]

Awesome. So we seem to have people with both factory WiiKey rom going straight to 1.9g as well as people playing it safe and upgrading to 1.9b first.
I think its safe to say that the updater simply replaces the ROM, and doesn't patch it.

I've also seem numerous upgrade paths with the Wii firmware version, so it looks like at least recent firmware versions are safe. My guess is that the problems seen are related to connection problems, faulty/clone WiiKeys, and bad media/burns.

Anyone agree?

-Klyick

 

[WarmWoollySheep]

No problems at all.

I had never updated my Wiikey, I had the default firmware. Update from default to 1.9g went fine.

Everyone who has a problem posts about it, but everyone who succeeds probably just plays mario.

 

[sepinho]

I had previously updated my European launchday Wii to 1.9b without any problem whatsoever.

On updating to 1.9g, the Wii refused to read both the Firmware and the Setup discs on the first attempt; worked like a charm after resetting the console though. Odd, isn't it? I used Verbatim DVD-R @ 4x for both discs btw.

 

[ledav007]

Japanese Wii, firmware 3.1J
Genuine Wiikey 1.9b
Burning on Mac using LiquidCD

Burnt the 1.9G without padding on Verbatim -R at 4x

Updated the Wiikey with no problem at all

Reset

Applied SMG Japan (original) update

Game runs fine

Reset

Tested with a backup of SMG Japan, runs fine

I also think that most problems are due to BAD media.

 

[robi]

NTSC/U Wii with D2B drive, 3.1U firmware

official Wiikey updated to 1.9b, then 1.9g (burned on ImgBurn on Verbatim DVD+RW)

SMG works great.

 

[Jimmy de Grasso]

Genuine Wiikey w/ 1.9b firmware previosly.
NTSC-U Wii w/ DMS Chipset, 3.1U firmware.
Burnt with ImgBurn on a cheap DVD-RW, without filechop.
Success!


PS: Only a strange thing, at the first time I played SMG, the blue light on wii's driver was on. I turned off the console then I played the game again then the light turned off.

 

[adgloride]

Lauch pal wii
Genuine Wiikey w/ 1.9b previously
wiiconnect 24 turned off
Burned with ImgBurn

Success no problems, started updating right away.

 

[modojojo]

Launch Wii NTSC, USA
Wii key original first gen
burnt 1.9g update w/img burn on dvd no padding this Is the first wii key update for my system.
firmware update did 2 pass throughs 100%
poped In SMG, It did It's own system update and everything works flawlessly.

 

[nilsk123]

pal wii ( launch day )
wiikey , never updated. ( launch day, so no clone)
didn't work, check connections error. Tried everything still didn't work.
put in a new wiikey
updated directly to 1.9G
worked
Launched mario, worked perrrrrrrfectly.

I had duplicate channels allready from metroid, so no negative side effects from mario update

 

[cardyology]

ok....

before

PAL - UK Wii - bought 8th Dec 2006 (w00t!)

Was on f/w 3.0e - Wiikey v1.2 (never upgraded to 1.9b)

I have previously allowed the update off the NTSC metroid release to update my wii but I made sure I had the latest "E" firmware first.
Metty 3 works fine but I have dupe channels. (no big deal imho)

So....

After (last night)
I did this in this order.
-update wii over wi-fi to UK 3.1E f/w

-d/l'ed & burned the Wiikey 1.9g HOTFIX update .iso & the 1.3 setup disc .iso.

-ran the 1.9g update disc in my wii - all went smooth. Let it TEST then confirm, then FLASH then confirm

(remember I am going straight from 1.2 to 1.9g skipping the 1.9B update - this is not a problem!)

-Then ran the 1.3 setup disc just to activate region free again.

-re tested with Metroid 3 - WORKING

Extracted & burned S.M.Galaxy - it asked me to update - I said YES

-Allowed it to update FULLY - this is fine if you already have 3.1E (& no turning off @15% - if you ask me, doing this is just asking for your wii to go broken. I'd rather have dupe channels then rag the power out the back of the console halfway through a firmware update.)

-Wii will auto reboot when "update" is complete.

-S.M.Galaxy appeard in the game channel.

-Works fine - What a game!!!

The end.


EDIT!!! - Sorry, just to add to this - when i burned SMG i didnt patch it. NO regionfrii - NO Brickblocker.
Its not nessecarry.

 

[Redsquirrel]

i have done several of these - some going straight from default wiikey to 1.9g, some from 1.2 to 1.9g and some from 1.9b to 1.9g - all worked fine!

 

[Jannibal]

I have an launchday Wii PAL version.
I have a Chiip which I just converted to a Wiikey and I use Wiikey 1.9g which is made for my chiip.
My Wii finds SMG and updates fine (I got the dupe channels). After that I try to run the game. It obviously finds the game since I get the SMG spalshscreen in Disc-channel. But when I start the game it says the following:
Error #0001 Unauthorized device detected

Have anyone seen this error before ? And what can I do to solve it ?

EDIT: I just remembered that I haven't soldered in the extra GND or the resistor on my chiip. And also, I just used Westek's auto-programmer and haven't tried any Wiikey-update DVD or anything of that sort. Prolly need to go and solder the resistor and the second ground before updating the thing again.

 

[rhyguy]

thats what 1.9g shoudls top i think, try updating again

 

[Jannibal]

I got it to work...
I added the extra resistor and the extra ground (I don't know if that was really necessary, but I just followed the book). And then I updated my "new" wiikey with the setup-disc from wiikey.cn and the new hotfix after that and then it worked swimmingly.

 

[traeskapa]

You guys that got it to work, did you filechop the update, or did you burn it as it was?
I tried to burn it with IMGBURN in 2x, and it just kept burning for an hour :/
And I'm low on DVD-R discs, so I don't want to waste any more of them.

 

[manias]

You guys that got it to work, did you filechop the update, or did you burn it as it was?
I tried to burn it with IMGBURN in 2x, and it just kept burning for an hour :/
And I'm low on DVD-R discs, so I don't want to waste any more of them.

I didn't have to filechop, others do.. depends on your burner

 

[WarmWoollySheep]

Burned it with Nero, didn't do anything special. I double-clicked it and then pressed the burn button.

 

[traeskapa]

You guys that got it to work, did you filechop the update, or did you burn it as it was?
I tried to burn it with IMGBURN in 2x, and it just kept burning for an hour :/
And I'm low on DVD-R discs, so I don't want to waste any more of them.

I didn't have to filechop, others do.. depends on your burner

Okay, I got some random HP-burner.
I'll try again without it, I think.
Could filechopping the file cause errors with the update?