Hacking Wii U will not update

  • Thread starter Thread starter austint54
  • Start date Start date
  • Views Views 21,183
  • Replies Replies 111
Those are cases, where people installed wrong IOSes and thats why it was necessary for them to be deleted.
However, there are also people reporting this issue, who have never softmodded their WiiU, so there cant be wrong Wii IOSes installed in their vWii.
In those cases their routers are probably to blame, because they are corrupting the download file. Like I said, trying another router or visiting a friend with your WiiU might help in some cases.
 
You guys are acting like there is only one way the error can appear. I currently have the error and have tried everything possible with regard to the connection.

In my case I am going to try to check the IOS & HBC angle. It's highly likely there is more than one cause with the same root problem.

<snip>

I'm going to go the IOS HBC route and give my feedback as well.
 
<snip>

I'm going to go the IOS HBC route and give my feedback as well.
<snip> I also believe that HE believes deleting a few vIOS's will fix the problem. That doesn't make any sense though. Everything is done from the Wii U side. An IOS can't stop you from updating anyway. So long as an IOS isn't running (and only one runs at a time), it has no effect.

If you want to delete a vIOS, at the very least make a NAND backup.
 
I don't believe anything. I am just passing the information on from others who had the same problem and ended up fixing it successfully using this method. <snip>
 
<snip> I also believe that HE believes deleting a few vIOS's will fix the problem. That doesn't make any sense though. Everything is done from the Wii U side. An IOS can't stop you from updating anyway. So long as an IOS isn't running (and only one runs at a time), it has no effect.

If you want to delete a vIOS, at the very least make a NAND backup.

<snip> You have no idea what counter measures Nintendo may have employed to stop vWii hacking. That's one way that modding an IOS for the vWii could cause the Wii U not to update.

I've tried two connections and same issue. When I try to update via the Wii U system update i get 105-3102 and when I try to update through Super Mario 3D World I get error 162-0002.

I also have tried wired and wireless connections. The IOS/HBC seems more likely as I go through possible solutions. I'll let you guys know what I find.
 
<snip>

But whatever. You have no idea what counter measures Nintendo may have employed to stop vWii hacking. That's one way that modding an IOS for the vWii could cause the Wii U not to update.
Actually I do have some idea. You might not know who I am, but I'm not exactly new to this community.

Do what you want, but PLEASE make a NAND backup.
 
  • Like
Reactions: Deletedmember331810
<snip> But whatever. You have no idea what counter measures Nintendo may have employed to stop vWii hacking. That's one way that modding an IOS for the vWii could cause the Wii U not to update.

I've tried two connections and same issue. When I try to update via the Wii U system update i get 105-3102 and when I try to update through Super Mario 3D World I get error 162-0002.

I also have tried wired and wireless connections. The IOS/HBC seems more likely as I go through possible solutions. I'll let you guys know what I find.

I appreciate your support and I hope that method works for you, just be very careful and follow what the guy says in the threads (and dump your NAND, please, you won't regret it! Everyone should have one already anyway!)

<snip>

I hope everything works out for you guys and you get your Wii U's sorted, I truly mean that!
 
  • Like
Reactions: JoostinOnline
<snip>

Actually I do have some idea. You might not know who I am, but I'm not exactly new to this community.

Do what you want, but PLEASE make a NAND backup.


Again no you have idea because you aren't doing anything on the Wii U side of things.


But what ever...
 
I can absolutely confirm that, in my case, restoring IOS36 to the original without the ES_IDENTIFY patch has allowed my Wii U to be updated.

I used MMM & Pimp My Wii (Multi Mod Manager) to review my IOS installs. I uninstalled cIOS 249,250,251,236 and re-installed the original IOS36 wad I previously dumped from Bluedump when I softmodded my vWii. I also removed HBC.

Mind you I had tried patching along the way. Here's what I tried as a list (starting from last night, and after a trip to Bestbuy for a USB lan adapter).
  1. Change my DNS to Google DNS with my wireless connection - Failed to update
  2. #1 Above and set my own IP manually with my wireless connection - Failed to update
  3. Change DNS with my wired connection - Failed to update
  4. #3 plus manual IP - Failed to update
  5. Do # 1-4 on another internet connection. - Failed to update
  6. Uninstall HBC - Failed to update
  7. (Reinstall HBC so I could...) Uninstall cIOS 249,250,251,236 - Failed to update
  8. Uninstall HBC with the cIOS 249,250,251,236 all already removed - Failed to update
  9. Checked every IOS via Pimp My Wii test and found out that IOS36 was ES_ID patched, installed the original WADs for IOS36 from when I Bluedump-ed them during my original vWii softmod.. UPDATE WORKED!
Hooray. # 6-9 were done on my original connection through a wired option...
My suspicion has to do with IOS36 and the ES_ID patch for now. Would love someone to verify that. Hope this helps someone else!




Btw all that was so I can play Super Mario 3D World. :)

Also It fixed both errors 105-3102 & 162-0002
 
Yes, I knew it! Thanks for reporting back, man!!!

I am glad you got it working and you can play your game! The new Mario World is RAW!!!

I am glad my research was not in vain and it was able to help others!
 
  • Like
Reactions: raulpica and f7_key
Yes, I knew it! Thanks for reporting back, man!!!


I had actually found that same German link last night and wound up trying that as the last resort versus the connection issues. But I thank you for linking it as well and providing some clue that it might be IOS related.

I just hope this can help others.
 
  • Like
Reactions: Deletedmember331810
I had actually found that same German link last night and wound up trying that as the last resort versus the connection issues. But I thank you for linking it as well and providing some clue that it might be IOS related.

I just hope this can help others.
I still don't understand how it could possibly matter though. :unsure:
 
That is very interesting. I wouldn't be surprised if BrickMyWii f*cked something up though.


How would that be? I had never used it at all before. You got to get over yourself man. It worked and I took a very scientific approach of changing one thing at a time and testing to determine what may be the issue.

I'm tempted to cancel the update, install teh patched ios36 again and see if I can recreate the problem.
 
How would that be? I had never used it at all before. You got to get over yourself man. It worked and I took a very scientific approach of changing one thing at a time and testing to determine what may be the issue.

I'm tempted to cancel the update, install teh patched ios36 again and see if I can recreate the problem.

I almost guarantee you can repeat it!

No snottiness, please. Your Wii U is fixed and that is the important thing.

Hopefully the reason why will be figured out soon now that people have multiple options to look over as to what could be causing the issue(s.)
 
Anyways off to enjoy Mario. Again, hope this helps someone. But as always read and research before you plunge into IOS editing.
 
<snip>

Anyway, I'll have to look into this. Could you at least tell me what you used to patch IOS36, and if it was definitely based on the vIOS? If I can duplicate it, I might find a way to patch a vIOS without such problems.
 
I can absolutely confirm that, in my case, restoring IOS36 to the original without the ES_IDENTIFY patch has allowed my Wii U to be updated.

I used MMM & Pimp My Wii (Multi Mod Manager) to review my IOS installs. I uninstalled cIOS 249,250,251,236 and re-installed the original IOS36 wad I previously dumped from Bluedump when I softmodded my vWii. I also removed HBC.

Mind you I had tried patching along the way. Here's what I tried as a list (starting from last night, and after a trip to Bestbuy for a USB lan adapter).
  1. Change my DNS to Google DNS with my wireless connection - Failed to update
  2. #1 Above and set my own IP manually with my wireless connection - Failed to update
  3. Change DNS with my wired connection - Failed to update
  4. #3 plus manual IP - Failed to update
  5. Do # 1-4 on another internet connection. - Failed to update
  6. Uninstall HBC - Failed to update
  7. (Reinstall HBC so I could...) Uninstall cIOS 249,250,251,236 - Failed to update
  8. Uninstall HBC with the cIOS 249,250,251,236 all already removed - Failed to update
  9. Checked every IOS via Pimp My Wii test and found out that IOS36 was ES_ID patched, installed the original WADs for IOS36 from when I Bluedump-ed them during my original vWii softmod.. UPDATE WORKED!
Hooray. # 6-9 were done on my original connection through a wired option...

My suspicion has to do with IOS36 and the ES_ID patch for now. Would love someone to verify that. Hope this helps someone else!

Glad to hear you got past this stupid error. You were one of the lucky ones, I got 2 Wii Us in my possession (1 hacked vWii-2 not hacked vWii) that are unable to update through my ISP/Router, tried your attempt and still not updating at my home. I know I can take them to another location and simply update them but I would like to find out why I can't update from my own damn house.
 
Please let Joostin know so he can look into it. This is very important!

Joostin's personality is raw and uncensored and as sarcastic as they come. He does not mean anything personal by it. I hope you can understand this... I am not choosing sides and we appreciate you putting the work into testing this for us!
 

Site & Scene News

Popular threads in this forum