Hacking How to fix this weird VWII brick?

[Xero874]

bump

 

[Xero874]

should I just give up and sell the wii-u?

 

[Xero874]

bump

 

[Bug_Checker_]

I guess if you are impatient, you should sell. A 5.1.2 firmware might piques someone's interest. Although, before a 5.5.1 kernel exploit it would have been worth more.

You have so many problems and to test out everything is probably gonna be a dead end anyway.

But the only thing going for you is a had/have SD card access to be able to write the SysCheck log out.

On the bad side:
Your system has no HBC.
You don't know when you lost the ability to write to NAND but you had to have it to install Wii IOS on your vWii. If you did not install the Wii IOS, then your friend did. So ANY IOS you backup are tainted and cannot be used.
To attempt to fix this you would have to be methodical.
You would have to try normal starts and maintenance mode starts. You have to try alternate disk exploits(unless you got lucky with Lego Star Wars).
You would have to try renaming files to "boot.dol" and booting the "boot.dol" from the root of the SD card(straight from game - no launchers).
You would most likely have to manually check every wad's for fakesigned and correct vWii versions.
You would have to try loading Riivolution then Lego Star Wars then boot.dol.
(on the plus side Riivolution needs a good IOS37 so it could fix that IOS.)

You would NEED to be able to backup your NAND( xyzzy,FSToolbox). If you can read your NAND and write to SD card you might have a chance to read and write the other way.

Finally, in a perfect world, you would be able to restore ALL the incorrect IOS, cIOS and SysMenu. This would allow you to update.
If that option were not available to you, you MIGHT be able to delete all the bad IOS and then the SysMenu(absolutely last).
This ^ would most likely FUBAR your vWii that only a hardmod would solve.
But, I believe that it would allow the Wii U to update and reinstall the correct SysMenu but leaving all the broken(missing) IOS alone.(So the vWii may still boot the SysMenu but it is anyone guess how useful this would be.)

Here are the important takeaways:
Do NOT delete the cIOS.(it maybe the only thing with some added access since HBC is gone)
Do NOT delete IOS80.(it is what SysMenu needs)
Do NOT delete SysMenu until the very last step.(if you chose to delete everything and do not care about vWii)

Your goal should be to install cIOS with known good vWii wad bases.
See if you get write access to NAND(my guess is you will see a LOT of "-1017"s when you try to install IOS)
-1017 is an error code added which needed to be patched out before IOS could be installed correctly.
You need to fix ALL errors or delete ALL problems(this means checking every IOS if you miss one it will be enough to end your chances of updating once you delete SysMenu)