Hacking Wii U Update 4.0.2

[Deletedmember331810]

Do you get a 162-0002 error when updating? If so, would you like me to help you fix it?

Edit:

PM me. I answered you in the other thread to PM me but you obviously must not want this fixed... I saw two others in there as well with the same problem and they must like having busted consoles too, lol.

Seriously though, PM me and I will walk you through it!

 

[KhX-3]

It's not practically screwed, it is screwed.

Actually, I am happy to report that because of a thread about a semi-bricked vWii and a solution by dantheman, and because of Cyan's help in actually pointing this out, and providing a possible solution, everything is fixed, and i'm not screwed, anymore.

Yes, vWii IOS58 got overwritten by the regular Wii IOS58 and I got locked out of Homebrew. But I was able to get back into it by combining Homebrew Loader 1.0 to load up DIRECTLY via SmashStack (bypassing Hackmii) with a program to re-install the vWii IOS's.

At first, they wouldn't install the ticket, but by loading up IOS236, I got the vWii IOS58 re-installer to work, and from there, fixed up the IOS that I damaged by stupidly replacing it the first time.

Once I did that, and then went back and proceeded to update the firmware, Error Code: 162-0002, was a thing of the past. Now that IOS58 was repaired (apparently it must check it, even if it doesn't change it, that is my guess), the update worked, I got the eShop back, and my vWii is even fully hackable once more.

Good times.

 

[the_randomizer]

Actually, I am happy to report that because of a thread about a semi-bricked vWii and a solution by dantheman, and because of Cyan's help in actually pointing this out, and providing a possible solution, everything is fixed, and i'm not screwed, anymore.

Yes, vWii IOS58 got overwritten by the regular Wii IOS58 and I got locked out of Homebrew. But I was able to get back into it by combining Homebrew Loader 1.0 to load up DIRECTLY via SmashStack (bypassing Hackmii) with a program to re-install the vWii IOS's.

At first, they wouldn't install the ticket, but by loading up IOS236, I got the vWii IOS58 re-installer to work, and from there, fixed up the IOS that I damaged by stupidly replacing it the first time.

Once I did that, and then went back and proceeded to update the firmware, Error Code: 162-0002, was a thing of the past. Now that IOS58 was repaired (apparently it must check it, even if it doesn't change it, that is my guess), the update worked, I got the eShop back, and my vWii is even fully hackable once more.

Good times.

The issue was fully reversed? That's awesome!

 

[mysticwaterfall]

Good to hear. Nice cautionary tale for everybody.