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).
- Change my DNS to Google DNS with my wireless connection - Failed to update
- #1 Above and set my own IP manually with my wireless connection - Failed to update
- Change DNS with my wired connection - Failed to update
- #3 plus manual IP - Failed to update
- Do # 1-4 on another internet connection. - Failed to update
- Uninstall HBC - Failed to update
- (Reinstall HBC so I could...) Uninstall cIOS 249,250,251,236 - Failed to update
- Uninstall HBC with the cIOS 249,250,251,236 all already removed - Failed to update
- 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