Did the update touch anything on the vWii side? Or would it have affected anything on the vWii side?
I'm having issues with vWii now. The Wii U app intended to forward from HBL to the vWii homebrew channel fails and reboots into Wii U menu (granted, this is my first time ever using it, so maybe that's not the update's fault). Also, WiiFlow now freezes on the startup screen and the console has to be unplugged in order to power it off.
I ran syscheck, it says no stubs and the cIOSes are all as they should be, so I'm not sure what the issue is? Unless...
Okay this just occurred to me, I'm sleep-deprived and ignorant of much of the ways these homebrew apps work. Last time I used WiiFlow, I had a different hdd plugged in and set it to use the hdd. Just now, when it froze on me, I had the Wii U hdd plugged in instead. Could that have caused the problem? And if so, what's the fix for it? Just plug the other hdd back in next time before I start WiiFlow?
I'm having issues with vWii now. The Wii U app intended to forward from HBL to the vWii homebrew channel fails and reboots into Wii U menu (granted, this is my first time ever using it, so maybe that's not the update's fault). Also, WiiFlow now freezes on the startup screen and the console has to be unplugged in order to power it off.
I ran syscheck, it says no stubs and the cIOSes are all as they should be, so I'm not sure what the issue is? Unless...
Okay this just occurred to me, I'm sleep-deprived and ignorant of much of the ways these homebrew apps work. Last time I used WiiFlow, I had a different hdd plugged in and set it to use the hdd. Just now, when it froze on me, I had the Wii U hdd plugged in instead. Could that have caused the problem? And if so, what's the fix for it? Just plug the other hdd back in next time before I start WiiFlow?