Hacking ...and now my Wii U has been wrecked. (Update to an earlier situation, and a warning)

[KhX-3]

EDIT: (Thanks to everyone helping, the problem that I thought was a lost cause, HAS BEEN FIXED. Hoorah! Everything is back to normal and it's a happy day for me. If you find yourself ever having this problem, GBATEMP IS AWESOME. )

Hey. You may remember me. I'm the guy that posted this about a week ago: http://gbatemp.net/threads/having-a...kmii-installer-on-the-vwii-of-a-wii-u.357405/

The guy that had a problem, installed HBC, replaced IOS58 of the vWii with the Wii's IOS58, not realizing that would ruin the ability to run HBC or mod or hack my vWii in any more capacity. It froze that IOS, can't repair it, can't softmod, can't do anything.

Eventually with no way of fixing the problem (that I know of), at the end of that thread, I just decided to take my loss, lick my wounds and just go about my business as normal with the rest of the Wii U. ...or so I thought.

Now even this has come back to kick me in the balls again, and has even destroyed my capabilities of my newly bought Wii U, essentially taking the system, the games I bought, the pro controller, all of these things, totaling over $350 for everything combined. I thought the story would just end there, but apparently no.

Nintendo forced a new firmware update just a small bit ago. Took a look around to see what this would handle, and saw there should have been no problems. So, because I had to in order essentially boot any games or use the eShop at all, or do anything anyway, I had to update.

"Error 162-0002". Uh. What? I try it about 8 more times. Download gets 30%, then fails. I thought "There HAS to be something I can do about this."

A few searches on the internet later and I realize that this situation has gone from bad, to worse, to unbelievably, ridiculously, cartoonishly bad.

So that ONE mistake I made of updating ONE little IOS a week or so ago, on the vWii section of the Wii U, is what's now causing a crash, blocking the update, blocking the eShop and any disc based game I want to play on this system. There's no fix for this. The Wii U was bought used, Nintendo wouldn't handle this without a warranty ANYWAY, and another person online that tried to contact Nintendo was told that his console was modded, therefore they will not help him, will not replace the system, and will not refund any money to this person. he adamantly denies that that his console was modded.

I can't make that claim. Might as well take responsibility for myself, eh? I was here a week ago and already explained how I failed at modding this, for not momentarily realizing the difference between a vWii IOS and a Wii IOS. So I'm royally screwed here, more so than I thought, with no chance in sight of a fix.

I would love to fix this IOS, restore it properly, but without a vWii that can be modded and an HBC installation that just hangs on the scam warning screen no matter how many times I try, I'm stuck with a fried IOS58, an Error Code 162-0002, the complete inability to update it, update the firmware, use the eShop, play any games, do anything, really. Dammit.

$350 complete and utterly down the toilet just like that, and a non working console simply for a 15 second error in judgement on my part regarding an IOS.

Gonna be honest, i'm pissed. Defeated, crushed, sad, and honestly pretty angry. At myself as well as this entire situation. So why am I posting here? Just to let people and give a warning just how one little thing that even someone who THINKS they know what they're doing can pretty much blow everything in an instant.

Don't end up like me. If you have any intent on modding the vWii on a Wii U, here's what to do to avoid wrecking everything, so that I MAY at LEAST be able to help someone else out:

1. Don't update, change, do ANYTHING to the vWii IOS. Not a thing. Don't touch it. Don't look at it funny. Leave it how it is, unless you are absolutely certain you know everything about IOS's and the minute differences between the Virtual Wii and the real Wii.

2. If you do any of this, be ready for any future update to semi or maybe even FULLY brick your WiiU if it detects ANYTHING like this. I didn't count on this happening. Other people should, it seems. It's VERY possible with this. You're taking a much bigger risk with this than you are with a regular Wii that's for damn sure.

3. Don't try to deal with Nintendo over this. They won't really care what you do, what you say, they'll just declare it out of their hands, and will not help. They seem to be really callous about this. Modding is even more of a dirty word to them than even I assumed it was, and I already knew they didn't much care for it.

Don't take it lightly. With the Wii U, either know what you're doing or end up having one momentarily mistake cost you $350. I hacked, re-hacked, and did more things to my original Wii than most people would. 10 minutes modding a vWii can ruin everything for you if you're not immediately careful.

I'm not sure what I can do now other than just be upset about it. But if i've caused one person out there to at least be cautious or avoid ending up like me, then maybe I'll have helped someone else out, who is thinking of doing this. I'm not saying NOT to do it. But just be careful. If you think you're careful enough, be MORE careful.

That's all for me, i guess. sigh. Good luck, everyone. Be safe. AND DON'T FUCK WITH vWII IOS58 FOR THE LOVE OF GOD. I'm gonna go cry over in a dark corner, now, for being the proud owner of a $350 brick set. -_-

 

[Ray Lewis]

1.). Read the sticky threads
2.) Read them again
3.). Ask before doing anything
4.). It is well known; don't add Wii ios to VWii
5.). If you had hardware based backups of emmc/VWII band (believe somebody said infectus works), you might have
recovered. If you wanted to help, look up my thread/links for emmc reading/writing. Try to read then write back the emmc. Maybe if/when hacked, you could flash "firmware" to fix issues via hardware flashing.
6.). I tried to read it all...try disc update.
7.). Other options I won't give as they are illegal/shady.

I always hate seeing these stories. However, I cannot think of a reason why you would even want to do what you've done. If serious, tough break. If post is a joke, "very funny."

 

[KhX-3]

4.). It is well known; don't add Wii ios to VWii

Yup. My own stupid fault. Absolutely cannot debate that. I just initially assumed it would be EXACTLY like softmodding a regular Wii. I was wrong on that. I assumed that like a fool before reading about any possible difference between vWii and Wii. I just up and tried it immediately. It was my downfall. Thought they were the same, found out the hard way they are not.

5.). If you had hardware based backups of emmc/VWII band (believe somebody said infectus works), you might have
recovered.

Pretty much. If I had taken precautions before jumping into the deep end of the pool and assuming the two were the same, I could have fixed it. Damn.

If serious, tough break.

Yeah. :/ Just thought that this might be of use to anyone else, to be sure not to be a fool like I was. Even though i'm sure about 80% of people here aside from the newbs are already smarter than me on this. That being said, I was dumb and deserve all of the "tough breaks", I get.

If post is a joke, "very funny."

I assure you it is not. Jumped right in, assuming vWii and Wii was the same system. Last time I ever read anything here was honestly back before the Wii U came out. So I had modded a Wii before with these instructions long ago. Heard that vWii was the same procedure. ...Proceeded to goof it all up. sigh.

 

[Foxi4]

There is a fair chance that eventually there will be a game with a disc-based update that will fix the issue or a new kind of exploit - don't give up, wait it out.

 

[Ray Lewis]

Foxi4 is wise. I feel badly, be careful next time.

 

[bowser]

Hey. You may remember me. I'm the guy that posted this about a week ago: http://gbatemp.net/threads/having-a...kmii-installer-on-the-vwii-of-a-wii-u.357405/

The guy that had a problem, installed HBC, replaced IOS58 of the vWii with the Wii's IOS58, not realizing that would ruin the ability to run HBC or mod or hack my vWii in any more capacity. It froze that IOS, can't repair it, can't softmod, can't do anything.

Eventually with no way of fixing the problem (that I know of), at the end of that thread, I just decided to take my loss, lick my wounds and just go about my business as normal with the rest of the Wii U. ...or so I thought.

Now even this has come back to kick me in the balls again, and has even destroyed my capabilities of my newly bought Wii U, essentially taking the system, the games I bought, the pro controller, all of these things, totaling over $350 for everything combined. I thought the story would just end there, but apparently no.

Nintendo forced a new firmware update just a small bit ago. Took a look around to see what this would handle, and saw there should have been no problems. So, because I had to in order essentially boot any games or use the eShop at all, or do anything anyway, I had to update.

"Error 162-0002". Uh. What? I try it about 8 more times. Download gets 30%, then fails. I thought "There HAS to be something I can do about this."

A few searches on the internet later and I realize that this situation has gone from bad, to worse, to unbelievably, ridiculously, cartoonishly bad.

So that ONE mistake I made of updating ONE little IOS a week or so ago, on the vWii section of the Wii U, is what's now causing a crash, blocking the update, blocking the eShop and any disc based game I want to play on this system. There's no fix for this. The Wii U was bought used, Nintendo wouldn't handle this without a warranty ANYWAY, and another person online that tried to contact Nintendo was told that his console was modded, therefore they will not help him, will not replace the system, and will not refund any money to this person. he adamantly denies that that his console was modded.

I can't make that claim. Might as well take responsibility for myself, eh? I was here a week ago and already explained how I failed at modding this, for not momentarily realizing the difference between a vWii IOS and a Wii IOS. So I'm royally screwed here, more so than I thought, with no chance in sight of a fix.

I would love to fix this IOS, restore it properly, but without a vWii that can be modded and an HBC installation that just hangs on the scam warning screen no matter how many times I try, I'm stuck with a fried IOS58, an Error Code 162-0002, the complete inability to update it, update the firmware, use the eShop, play any games, do anything, really. Dammit.

$350 complete and utterly down the toilet just like that, and a non working console simply for a 15 second error in judgement on my part regarding an IOS.

Gonna be honest, i'm pissed. Defeated, crushed, sad, and honestly pretty angry. At myself as well as this entire situation. So why am I posting here? Just to let people and give a warning just how one little thing that even someone who THINKS they know what they're doing can pretty much blow everything in an instant.

Don't end up like me. If you have any intent on modding the vWii on a Wii U, here's what to do to avoid wrecking everything, so that I MAY at LEAST be able to help someone else out:

1. Don't update, change, do ANYTHING to the vWii IOS. Not a thing. Don't touch it. Don't look at it funny. Leave it how it is, unless you are absolutely certain you know everything about IOS's and the minute differences between the Virtual Wii and the real Wii.

2. If you do any of this, be ready for any future update to semi or maybe even FULLY brick your WiiU if it detects ANYTHING like this. I didn't count on this happening. Other people should, it seems. It's VERY possible with this. You're taking a much bigger risk with this than you are with a regular Wii that's for damn sure.

3. Don't try to deal with Nintendo over this. They won't really care what you do, what you say, they'll just declare it out of their hands, and will not help. They seem to be really callous about this. Modding is even more of a dirty word to them than even I assumed it was, and I already knew they didn't much care for it.

Don't take it lightly. With the Wii U, either know what you're doing or end up having one momentarily mistake cost you $350. I hacked, re-hacked, and did more things to my original Wii than most people would. 10 minutes modding a vWii can ruin everything for you if you're not immediately careful.

I'm not sure what I can do now other than just be upset about it. But if i've caused one person out there to at least be cautious or avoid ending up like me, then maybe I'll have helped someone else out, who is thinking of doing this. I'm not saying NOT to do it. But just be careful. If you think you're careful enough, be MORE careful.

That's all for me, i guess. sigh. Good luck, everyone. Be safe. AND DON'T FUCK WITH vWII IOS58 FOR THE LOVE OF GOD. I'm gonna go cry over in a dark corner, now, for being the proud owner of a $350 brick set. -_-

I don't get why you're not able to play your Wii U games. My Wii U is connected to the internet and after the 4.0.2 update came out, my Nintendo Land disc started nagging me to update. Strangely Pikmin 3 didn't do this. Since I didn't want to update, I deleted all of my network connections in the Wii U settings and tried to start the game again. It again asked to update and I clicked ok or Update or whatever. Then it gave me a message saying no network connections were found and if I would like to start the game without updating. Hope it works for you.

 

[the_randomizer]

Things that happen on vWii mode should only vWii mode. Wii U mode is completely separate from vWii so I'm very confused.

 

[lisreal2401]

Why don't you load a wad manager with SmashStack and just reinstall the stuff?

 

[KhX-3]

Why don't you load a wad manager with SmashStack and just reinstall the stuff?

Because as I said in my other thread, and the beginning of this one, I no longer have ANY modding capabilities. Whatsoever. I basically screwed over any chance of this working even going back as far as step one.

I can't load a WAD manager, because it was the IOS58 that was damaged to the point of removing HBC from working, AND Smashstack no longer works, because it needs an exploitable IOS to patch. I no longer have one of those, it was overwritten, meaning my vWii is completely unhackable past any point where I COULD load a Wad manager.

Any attempts at expoiting, running HBC, or even re-installing it with Smashstack or ANY modding method just causes it to hang on the "scam warning" screen. This is because, as I read elsewhere after this, IOS58 or some vulnurable IOS needs to be exploited. If the hackme installer cannot exploit an IOS, it will sit there and do nothing.

I thought I made that very clear. It needs IOS58 to even mod the vWii. IOS58 was damaged and thus I have been locked out of any step of this. So I don't understand how you're asking me to do something to fix the problem that the problem has prevented me from doing in the first place.

IOS58 is shot and with that, any chance to load any homebrew. And only homebrew could fix this. Aside from dumping the NAND and restoring the NAND by loading it back in. And that option is also gone. Becuase again... unhackable, now.

 

[Arras]

Because as I said in my other thread, and the beginning of this one, I no longer have ANY modding capabilities. Whatsoever. I basically screwed over any chance of this working even going back as far as step one.

I can't load a WAD manager, because it was the IOS58 that was damaged to the point of removing HBC from working, AND Smashstack no longer works, because it needs an exploitable IOS to patch. I no longer have one of those, it was overwritten, meaning my vWii is completely unhackable past any point where I COULD load a Wad manager.

Any attempts at expoiting, running HBC, or even re-installing it with Smashstack or ANY modding method just causes it to hang on the "scam warning" screen. This is because, as I read elsewhere after this, IOS58 or some vulnurable IOS needs to be exploited. If the hackme installer cannot exploit an IOS, it will sit there and do nothing.

I thought I made that very clear. It needs IOS58 to even mod the vWii. IOS58 was damaged and thus I have been locked out of any step of this. So I don't understand how you're asking me to do something to fix the problem that the problem has prevented me from doing in the first place.

IOS58 is shot and with that, any chance to load any homebrew. And only homebrew could fix this. Aside from dumping the NAND and restoring the NAND by loading it back in. And that option is also gone. Becuase again... unhackable, now.

Of course the HBC relies on 58 and is unusable, but can't Smash Stack run other stuff if you replace the proper files? I haven't messed with my Wii in quite some time, but usually there's just a boot.elf file for these exploits that you can replace by something else. If you can get a WAD manager or a different homebrew launcher to load that way, it might be savable (although I don't know whether WAD managers will work on a vanilla vWii with screwed IOS58).

 

[Cyan]

you don't have 249 or 250 anymore ?
I didn't find where you said they were unusable in this thread or the other one.
If you have them, you can still save your vWii.


Someone else had a IOS58 problem, damysteryman helped him, providing a modified wad manager installed as channels to enable AHB access and reinstall the official vWii IOS58.
Though, it ended in an upside-down HBC because either the wad manager was patching the file internally instead of installing it clean or he installed a patched version of IOS58, but once you have a working upside-down HBC, you can run other homebrew again to fix this issue.

You should read carefully this thread, this user fully deleted IOS58 so it's doing the same thing as you : can't load it.
http://gbatemp.net/threads/vwii-semi-bricked.353595/
You might find the solution there.

edit: don't try random things, your case might be different, ask first.

 

[KhX-3]

you don't have 249 or 250 anymore ?
I didn't find where you said they were unusable in this thread or the other one.
.

Yeah, I thought that was odd at first, too.

I mean, I did nothing to 249 or 250. It SHOULD be exploiting those.

That, I am baffled by. There's no reason it shouldn't find those. Yet, doesn't.

I mean if I could verbally ARGUE with the vWii and ask it "Hey man, where's 249 and 250? What about those?" that would be awesome. ehe. ...but reality doesn't work that way I guess. >_> sigh. ..it is curious though. This, I don't get.

 

[Cyan]

I'm not sure I understand what you said.
you said it doesn't find them. what is "it" ?
Which homebrew did you try which tells you it doesn't find these IOS?

You need to explicitly tell the homebrew to use them, otherwise it will try to load IOS58 and use AHB access.
Well, it also depends on the version of the homebrew you are using. That's why using very specific files could be helpful to your situation

 

[Arras]

you don't have 249 or 250 anymore ?
I didn't find where you said they were unusable in this thread or the other one.
If you have them, you can still save your vWii.


Someone else had a IOS58 problem, damysteryman helped him, providing a modified wad manager installed as channels to enable AHB access and reinstall the official vWii IOS58.
Though, it ended in an upside-down HBC because either the wad manager was patching the file internally instead of installing it clean or he installed a patched version of IOS58, but once you have a working upside-down HBC, you can run other homebrew again to fix this issue.

You should read carefully this thread, this user fully deleted IOS58 so it's doing the same thing as you : can't load it.
http://gbatemp.net/threads/vwii-semi-bricked.353595/
You might find the solution there.

edit: don't try random things, your case might be different, ask first.

I don't know about 249 or 250, but according to the other thread he has 236 at least.

 

[Cyan]

that's fine too.
236 can be used to install the channel.

 

[KhX-3]

I'm not sure I understand what you said.
you said it doesn't find them. what is "it" ?
Which homebrew did you try which tells you it doesn't find these IOS?

You need to explicitly tell the homebrew to use them, otherwise it will try to load IOS58 and use AHB access.
Well, it also depends on the version of the homebrew you are using. That's why using very specific files could be helpful to your situation

"them" meaning 249 and 250.

And yeah, Smashstack just crashes. Hangs there. Does nothing. It was only after looking up on google a thread about it, and why it hangs on the scam warning did I find out why it does that. I can tell the homebrew to use them? I just get a complete freeze on the scam warning. My tracks stop there.

 

[Cyan]

No, you don't understand.
The Smashstack is an exploit to load a homebrew : ANY homebrew. not only the hackmii installer!

Smash bros > Hackmii installer > scam screen : you can't go any further
Smash bros > ANOTHER homebrew > Working

instead of using the boot.elf from the hackmii installer, use another boot.elf and smashstack will load it.


If you read the other thread , you will see it's used like that :

Smash bros > Homebrew Launcher 1.0 > WiiMod lite 1.1's Wad manager > reload to IOS249 (or 236) > Install the IOS-58-Channel
exit to system menu
Load the IOS-58-channel to install the new/clean IOS58


Yes, it's a lot of steps that you need to follow in correct orders, but it's a solution to your problem.

 

[KhX-3]

No, you don't understand.
The Smashstack is an exploit to load a homebrew : ANY homebrew. not only the hackmii installer!

Smash bros > Hackmii installer > scam screen : you can't go any further
Smash bros > ANOTHER homebrew > Working

huh. I did at one point try loading one thing like this, but it just told me that it couldn't run. (I never mentioned this previously after the one time I tried it, it ended up being another dead end to me). I renamed the file I was replacing the same as the Hackmii file and put it there in it's place. It just told me it wasn't a valid file to load.

HOWEVER... when you present the idea that I should try and load something that is meant to exploit through another IOS, I could try that. (The method in that other thread. I'll give that one a shot.) I'll do that and see what happens. I have a feeling it'll tell me it's not a valid file, but if it doesn't, it may work. fingers crossed I suppose.

 

[Cyan]

You can't rename the boot.dol to boot.elf, you need a real boot.elf that's why it didn't work.

just be sure that you use the correct versions and files for everything (homebrew, channel, IOS) when you follow the other thread. ask help here, and maybe damysteryman could help too.
I didn't follow the other thread when the user had his problem, but it's possible to fix.

 

[Arras]

huh. I did at one point try loading one thing like this, but it just told me that it couldn't run. (I never mentioned this previously after the one time I tried it, it ended up being another dead end to me). I renamed the file I was replacing the same as the Hackmii file and put it there in it's place. It just told me it wasn't a valid file to load.

HOWEVER... when you present the idea that I should try and load something that is meant to exploit through another IOS, I could try that. (The method in that other thread. I'll give that one a shot.) I'll do that and see what happens. I have a feeling it'll tell me it's not a valid file, but if it doesn't, it may work. fingers crossed I suppose.

Remember that you have to use a .elf file. I THINK plainly renaming a .dol is not enough, although I'm not sure about that. IIRC there is a way to convert them though...