Hacking HELP! WiiU with errors on vWii, can't update the system

rockmann

Well-Known Member
OP
Newcomer
Joined
Mar 31, 2017
Messages
45
Trophies
0
Age
73
XP
45
Country
Argentina
I'm creating a new thread as the one I posted seems to be very old:

Hey guys!

I got a used 5.3.2 WiiU from ebay +1 year ago. I did not know anything about vWii (I wasn't interested on running Wii games), so I did not touch it. This week I wanted to finally upgrade to get BOTW and I got the 162-3006. Long story short, I tried everything about the wifi, so it looked like the vWii IOSes were played with. I got a Brawl to do Smash Stack to install HBC, but Hackmii does not pass the Scam screen (tried +5 SDs on fat16, 32, also different controllers with and without motion plus, it just shows the "press 1 to continue" and crash there). Loadmii just don't load any .dol neither (it just won't do anything when I press A), so I'm lost on how to run SysCheck as I can find an .elf of it.

I was losing all hope about, but I was able to run YAWMM as it comes with an .elf, and found that the following +ios80 IOSes are installed:

202, 222, 223, 224, 245, 246, 247, 248, 249, 250, 251, 252.

What do you recommend? Is there a way to use one of this IOS to install the original vWii ones? (Obviously I don't have a backup as I never touched the vWii before)

Thanks in advance.

UPDATE:If I understand correctly, if I update the ios58 to version 6432 -that I supposse is the culprit to crash the hackmii- I should be able to install the HBC and then run a syscheck and fix the rest?

UPDATE 2: I found a ios58 6432 wad but I get an ret= -1017 error if I try to use it. Must be a bad .wad.

Also, I forgot to mention that the system version is spoofed to 5.5.1, does this affect it? If a get ahold of a a game with a newer firm (I heard Star Fox Zero has 5.5.1) it will upgrade and fix the vWii or it will keep showing the 162-3006 error?

thanks a lot
 
D

Deleted User

Guest
He probably overwritted IOS which is used by System. [Common thing eh?]
If you want ios58 wad, use NUSDownloader. It can grab vWii IOS'es.

Nope, you're unable to update unless you're going to fix your vWii.
 

rockmann

Well-Known Member
OP
Newcomer
Joined
Mar 31, 2017
Messages
45
Trophies
0
Age
73
XP
45
Country
Argentina
He probably overwritted IOS which is used by System. [Common thing eh?]
If you want ios58 wad, use NUSDownloader. It can grab vWii IOS'es.

Nope, you're unable to update unless you're going to fix your vWii.

Yes, very common unfortunately. :(

Thanks! I did not know that NUSDownloader was able to do that (all the other posts I read so far indicated that downloading from it is not possible). Trying it right now.

EDIT: Sorry, it only shows up to 6176, do you know how make it to show the vWii 6432?
I already tried updating the database.
 
Last edited by rockmann,
D

Deleted User

Guest
Yes, very common unfortunately. :(

Thanks! I did not know that NUSDownloader was able to do that (all the other posts I read so far indicated that downloading from it is not possible). Trying it right now.

EDIT: Sorry, it only shows up to 6176, do you know how make it to show the vWii 6432?
I already tried updating the database.
It's a list from NUS itself so i don't think you can do that.
Anyways, can you run syscheck?
 

Cyan

GBATemp's lurking knight
Former Staff
Joined
Oct 27, 2002
Messages
23,749
Trophies
4
Age
45
Location
Engine room, learning
XP
15,646
Country
France
Also, I forgot to mention that the system version is spoofed to 5.5.1, does this affect it?
It's not a problem. either for WiiU or vWii, the spoof doesn't affect anything.

For your issue:
Don't get vWii IOS from NUS. They are not good signed.

The error you get when installing is not related to wrong signature but to a protection against IOS installation (or because of "no NAND access" due to wrong IOS loaded in memory?).
You'll need cIOS 236 to install IOS58 (easy), or a vWii cIOS (more steps, but still easy).

So, first, what you can do is either :
- fix vWii from vWii side (could be hard long to check everything, based on what the user did previously). it's not always possible to fix. (full vWii brick)
or
- fix the vWii from WiiU side (could be the only method, but there's no automated tools and you'll have to edit SLCCMPT NAND manually, could be bad too)


So, first, let's work vWii side :
I made a Question/answer form to determine what can be done.
https://gbatemp.net/threads/vwii-brick-idiot-needs-help.420561/#post-6202225

but based on your information, I know this:
• You tried to install HBC (which means you don't have it? if you still have it, do not delete it even if it's not working)
• you have a SSBB disc.
• You have 202, 222, 223, 224, 245, 246, 247, 248, 249, 250, 251, 252.
So you miss IOS236, but you still have 249 and it's very good, as long as it's a "vWii version". this is were it's becoming bad : slot 202-222-223-224 are old cIOS released for the Wii.
It means that the user probably followed a Wii guide to hack his vWii, which probably also installed the Wii version of ALL the other cIOS.

If all cIOS are Wii version, there's nothing you can do to fix your console from the vWii side.

But it's only a supposition, maybe the user mixed installation? Very unlikely, but let's check it !

• maybe the user used a youtube tutorial which provides illegal files, they usually comes in full package with both IOS <80 and IOS > slot 80. there's a (bad)chance he also replaced ALL his vWii IOS with Wii version, even the one under slot 80.
I think he didn't do that, because vWii wouldn't run at all if he replaced slot70 with Wii version.

• it will be long and fastidious to fix his console, if he replaced a lot of system files to Wii version u_u
only IOS58 would have been easy to fix.
Let's hope he installed only Wii cIOS, not Wii IOS, but then IOS58 would work and HBC install too.


What you should do now:

Run (using SSBB exploit, and the elf version) YAWMM mod (please, use THIS version, old ones might not have all required patches for vWii)
Once loaded, select reload to slot 249.

If it works, it should be fine. it means you have vWii version.
if not, try another slot up to 252.
report if any slot is loading fine.

Note: You might not be able to install IOS58 even if it works !
remember that you need two things to do it :
- proper IOS58 good signed, not from NUSD
- IOS patch allowing IOS installation, which might (or might not?) be inside the YAWMM version I linked.

so do not try to install IOS58 please.
just tell us if reloading to these slot is working or not inside YAWMM.


I have very little faith in fixing it from vWii side :(
I never fixed a vWii from WiiU side, it's only a theory now that WiiU has vWii NAND access. it involved replacing files one by one manually.

edit:
Ohh, one important thing :
1. do not try random things which involve editing your system file (install/delete/edit) without asking our advice first. You could make things worse, like "HBC doesn't boot, so let's delete it to reinstall it !" is a VERY bad idea.
2. always report and answer our questions (I tried helping someone, it was very frustrating when he never replied and did other things and never report, etc.)
 
Last edited by Cyan,

rockmann

Well-Known Member
OP
Newcomer
Joined
Mar 31, 2017
Messages
45
Trophies
0
Age
73
XP
45
Country
Argentina
@Cyan Ok. So far I have little faith too, it looks like is hermes and waninkoko stuff. I downloaded the YAWMM you linked and will try it, I will report soon.

And no, it does not have HBC, the original owner deleted it (I suppose? Maybe he never was able to install it?)

Thanks a lot for your thoroughly reply.
 

rockmann

Well-Known Member
OP
Newcomer
Joined
Mar 31, 2017
Messages
45
Trophies
0
Age
73
XP
45
Country
Argentina
@Cyan I tried 249, 250, 251 and 252.

249 and 250 disconnected the wiimote when selected and a "Select NAND-Emulation device: < disabled >" message appeared. The wiimote would not connect again afterwards and had to turn off the Wiiu unplugin the power socket each time.

251 and 252 disconnected the wiimote when selected and a "Select the WAD location: < SD Card >" message appeared. The wiimote would not connect again afterwards and had to turn off the Wiiu unplugin the power socket each time.


Note: I noticed something weird, my system is in spanish, and when SSBB is loaded, the warnings are in spanish but after the first loading it is in english.
 

Cyan

GBATemp's lurking knight
Former Staff
Joined
Oct 27, 2002
Messages
23,749
Trophies
4
Age
45
Location
Engine room, learning
XP
15,646
Country
France
the fact the wiimote disconnect means the IOS is incorrect (it's the hardware driver, so the wiimote can't communicate with the console anymore).
without a vWii cIOS, I think you can't fix it in vWii mode :(
maybe I'm missing a method, and someone else would have an idea, but I think you'll have to try to fix it using the WiiU Mode.
I'll bother @JoostinOnline, just to confirm I didn't forget something. (not sure the notification worked, I edited my post to add it)


I never tried, and you might be my guinea pig, if you don't mind :P
At worse, your vWii will still not work.
At best, it would launch and you could install HBC ! from HBC it will be easier to fix and install or replace IOS/cIOSes.


My idea is to replace the IOS 58 files directly on NAND (without using a WAD) by accessing it from WiiU homebrew.
either WUP server or fptiiu everywhere.
FTP is maybe easier to browse and edit the NAND content, as WUP server require typing command line and path manually one by one.

the issue is that when installing an IOS, it does not just copy the file to a specific folder, it's also editing a file with hash data of the installed file. the console use this hash list to determine which file is installed.
so you will probably have to edit it manually, and it's a binary file. it will require an hex editor program, unless someone released a GUI editor? I'll have to check wiibrew website.
We can try without editing it first, and see if the console kept the old hash in cache. (making backup of every replaced file first of course)
 
Last edited by Cyan,
D

Deleted User

Guest
FTP is maybe easier to browse and edit the NAND content, as WUP server require typing command line and path manually one by one.
iosuhax isn't available below 5.5.1 so i highly doubt he will be able to even do something with it.
 

Cyan

GBATemp's lurking knight
Former Staff
Joined
Oct 27, 2002
Messages
23,749
Trophies
4
Age
45
Location
Engine room, learning
XP
15,646
Country
France
ohhh, damn, I forgot he is spoofed .
well, WUP server was available, so no ftpiiu but wup server only. but I don't remember if we had access to vWii side with wup server on a console below 5.5.1 :(
I think it didn't work. (my memory is blurry about vWii access using wup). I'll have to check which exploit I still have from Dimok's work on 5.3.2


Another solution would be hardware dump/edit/restore.
We can now edit SLC from a dumped NAND.
but that will require a hardware modification with a teensy, not sure you'd want to go that way just to restore vWii.
 
Last edited by Cyan,

rockmann

Well-Known Member
OP
Newcomer
Joined
Mar 31, 2017
Messages
45
Trophies
0
Age
73
XP
45
Country
Argentina
I never tried, and you might be my guinea pig, if you don't mind :P
At worse, your vWii will still not work.
At best, it would launch and you could install HBC ! from HBC it will be easier to fix and install or replace IOS/cIOSes.


My idea is to replace the IOS 58 files directly on NAND (without using a WAD) by accessing it from WiiU homebrew.
either WUP server or fptiiu everywhere.
FTP is maybe easier to browse and edit the NAND content, as WUP server require typing command line and path manually one by one.

Yes, I'm spoofed so it is really a 5.3.2, no FTP. But I'm up to it, I don't mind to try and be the guinea pig, maybe we can find a fix that other people can use! (and stop the ebay ripoff sellers :angry:)

If there's a way to play BOTW at least, I will do anything. This is my son's console (he's nine), and he had saved up money to buy it -main reason why I wanted to update, he had used it to play Mario Maker and SSB so far-.
I was so disappointed that I tried to install it with wupinstaller to see if it runs, and it loads, but you can only play it until the second shrine and then it crashes. I read it was because I don't have 5.5.1, but maybe there's also a way to update the system manually to have the 5.5.1 files so it don't crash? If it can be spoofed, I suppose yes, but it sounds dangerous.

I will be waiting further instructions :yay:
 

Cyan

GBATemp's lurking knight
Former Staff
Joined
Oct 27, 2002
Messages
23,749
Trophies
4
Age
45
Location
Engine room, learning
XP
15,646
Country
France
Manual update is very dangerous and will brick wiiu mode.
do not attempt that.

I don't know if we will be able to fix vWii using software only.
I will have to remember what dimok was working on, and when he decided to move to 5.5.1 definitely.
he did a lot of work on 5.3.2 too, but I don't remember if vWii was only in 5.5.1
the thing is that all the hacks would be working with all WiiU version, it's just that the devs stopped developping for all of them. The needed addresses to patch started to be searched only on 5.5.1 and old version support were dropped, even if it would have been possible.

I don't think a developer would want to look into old firmwares again (it would be hard without an old system to debug it), all your hope will be in what was still possible before 5.3.2 support was fully dropped.

edit:
humm, it seems it was Fix94 who got vWii access first (around october 2016), and it's in a form of CFW (fw.img) that you need to compile and boot using cfw booter if it's working on 5.3.2.
I have no idea what could happen if you try to boot a 5.5.1 firmware with 5.3.2 system files.

Sorry, I might not be the person who will be able to help you here.
it's too many unknown area and it's dangerous to just make supposition. at best, it will not do anything.

I still think the easiest way would be to dump your NAND and edit it on computer, but you'll need OTP.bin file which contains your console's keys. I think this also require IOSU hack, so you're out of luck.

Maybe your only choice is to buy a new console.
 
Last edited by Cyan,

rockmann

Well-Known Member
OP
Newcomer
Joined
Mar 31, 2017
Messages
45
Trophies
0
Age
73
XP
45
Country
Argentina
Thanks for your time. It is a pity as I have seen a couple of guys on the same situation, and I'm sure there's a lot of wiius circulating with the same kind of brick. It is easy to hide it, so I would expect that a good % of consoles on auctions/thrift stores will have this problem and the buyers wouldn't know better.

humm, it seems it was Fix94 who got vWii access first (around october 2016), and it's in a form of CFW (fw.img) that you need to compile and boot using cfw booter if it's working on 5.3.2.
I have no idea what could happen if you try to boot a 5.5.1 firmware with 5.3.2 system files.

Maybe I can send an email to Fix94 explaining and pointing to this thread?

A new wiiu for me in the meantime is prohibitive, here in argentina they are super expensive (that's why I fall on a cheap ebay one when I visited USA last year)

EDIT: Looking at Fix94 repository, the last wuphax says "wuphax v1.1! now no longer requires wupclient or iosuhax, only a elf!". Does it means that the vWii can be accessed without iosuhax, meaning no 5.5.1 is required?

https://github.com/FIX94/wuphax
 
Last edited by rockmann,
D

Deleted User

Guest
Dumping vWii's NAND would be useless without otp...
Hm, wasn't redNAND created for 5.3.2 also? You could use it then SDIO NAND Manager and extract otp.bin from there then proceed to dump vWii's NAND and fix everything from your PC then redump and you would be done.

--------------------- MERGED ---------------------------

EDIT: Looking at Fix94 repository, the last wuphax says "wuphax v1.1! now no longer requires wupclient or iosuhax, only a elf!". Does it means that the vWii can be accessed without iosuhax, meaning no 5.5.1 is required?
wuphax exploits Mii Channel to launch BootMii installer which runs on IOSv58 as far as i know.
 

rockmann

Well-Known Member
OP
Newcomer
Joined
Mar 31, 2017
Messages
45
Trophies
0
Age
73
XP
45
Country
Argentina
Hm, wasn't redNAND created for 5.3.2 also? You could use it then SDIO NAND Manager and extract otp.bin from there then proceed to dump vWii's NAND and fix everything from your PC then redump and you would be done.

If someone can confirm this, can be huge. Your guide does not mention it, but any other one says it need to be on 5.5.x

wuphax exploits Mii Channel to launch BootMii installer which runs on IOSv58 as far as i know.

So basically is the same as using smash stack, right?
 

rockmann

Well-Known Member
OP
Newcomer
Joined
Mar 31, 2017
Messages
45
Trophies
0
Age
73
XP
45
Country
Argentina
Ok, I got the .elf of syscheckhde and when I try to run it on smash stack I get this:


20170331_223352.jpg
 
Last edited by rockmann,

Cyan

GBATemp's lurking knight
Former Staff
Joined
Oct 27, 2002
Messages
23,749
Trophies
4
Age
45
Location
Engine room, learning
XP
15,646
Country
France
Wuphax replaces a Wii game disc.
you boot boothax (instead of game) which loads hackmii's boot.elf from SD.

the "1.1" changelog refers to the fact that what was required to do manually before, is now automated by a homebrew.
former version requires :
1. generate a fw.bin with IOSU Hack and vWii access
2. browser hax or any method to run homebrew
3. firmware booter -> reboot using the custom/modified firmware's fw.img to get SLC vWii access
4. use WUP Server to dump vWii Mii channel dol
5. use WUP Server to replace Mii channel dol on SLC with hackmii booter


6. boot into vWii, launch miimaker, install HBC, exit vWii

7. browser hax or any method to run homebrew
8. firmware booter -> reboot using the custom/modified firmware's fw.img to get SLC vWii access
9. use WUP server to replace hackmii booter with original backup'd Miimaker dol



WUPHax 1.1 replaces all the red steps with an automated homebrew launched from HBL. It patches the firmware directly in memory instead of requiring an external firmware file to be loaded, then it automatically replace the miimaker file (install or restore).


The step "1" which is an old CFW method consist in patching the firmware on the computer and load that patched file with a firmware booter.
I still think this might be a solution for old 5.3.2 bricked consoles.
If you can get the 5.3.2 firmware from NUS (if nintendo didn't remove it) then you could patch it with the same features : IOSU hack and SLC.

the issue is that all devs updated their consoles to 5.5.x and won't be able to help find the required addresses and values to patch to get IOSU hack on these firmware.
 
Last edited by Cyan,

C0mm4nd_

Aspirant Wii U homebrew dev :P
Member
Joined
Oct 9, 2016
Messages
697
Trophies
0
Website
127.0.0.1
XP
540
Country
Italy
uhshax (iosu exploit for 5.5.1) shouldn't work on 5.5.1
btw maybe mqhax (another iosu exploit) could work on 5.3.2...
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: