Requirements:
WiiScrubber v1.40;
nfs2iso2nfs v0.5.4; it may require the Wii common Key. You can use wiiscrubber's key.bin renamed to wii_common_key.bin.
A clean rip of your Wii game;
The extracted contents of a Wii VC title for the Wii U (except the .nfs files);
-the 2 below require java to be installed-
jnustool (requires Wii U common key so you'll have to search online - hint: it begins with D7B0. Open the "config" file in notepad and paste the key inside, replacing [COMMONKEY]);
NUSpacker (must be @ihaveamac's version, requires Wii U common key as well)

Current limitations:
It's possible to use the gamepad to emulate ONLY the Classic Controller.
Wii Remote emulation is possible but there's no gyroscope or infrared commands (at least for now).
(Input emulation patches by @FIX94)

The game must be already compatible with the Classic Controller but that isn't a guarantee that it's going to work.
Here's a compatibility list: http://wiki.gbatemp.net/wiki/WiiU_VC_Wii_inject_compatibility_list

Integrity checks are still in place so only clean disc rips work.
The game iso must be pristine: untrimmed, unscrubbed and the partitions signed.
No homebrew, no mods, no wimmfi patched games until sigpatches are implemented.
Patched isos work now! Original idea by @Tock46!

Homebrew works now, even a special version of Nintendont by @FIX94

Trimmed isos still don't work, at least not isos trimmed by WiiScrubber.



HOW TO DO IT


0. Downloading a Wii VC Title
This may be illegal and I'm just telling you so you don't ever do it by mistake OK?
You can use the command line to download games' contents directly if you know the title id and title key.
I heard you can get them on a certain titlekeys site...

Once you have that, this is the command

java -jar JNUSTool.jar TITLEID TITLEKEY

Note: You should get a game that contains the latest revision of fw.img (r590), that's the only version supported by @FIX94's patches.
Here's some info you can use to verify that you have a good file:
Size: 1785497 bytes.
CRC32: E2F27E9B
MD5: 3CAF52A9A440EEE4F125A3AD22E305C8
SHA: A5A75EBF3164874830A1D5992495DE510AB3F74E

Now here's a list of some titles that contain the preferred fw.img (verified mostly by @fejich and @markehmus)
DONKEY KONG JUNGLE BEAT [VBXE01]
Kirby's Epic Yarn [VARE01]
Lost in Shadow [VA8E01]
Mario Strikers Charged [VBFE01]
Mario Super Sluggers [VBHE01]
Pandora's Tower [VAPE01]
PIKMIN 2 [VBTE01]
PIKMIN [VBUE01]
Resident Evil 4 Wii Edition [VBDE01]
Resident Evil The Umbrella Chronicles [VBWE01]
Rhythm Heaven Fever [VAKE01]
Sin and Punishment Star Successor [VALE01]
Super Mario Galaxy [VBKJ01]
Super Paper Mario [VBBE01]
The Legend of Zelda Skyward Sword [VANE01]
Trauma Team [VA6E01]
Wario Land Shake It [VBGE01]
WARIO WARE SMOOTH MOVES [VBVE01]





-----------------------------------------------

1. WiiScrubber
First setup WiiScrubber. Remember it needs the Wii common keys so run MakeKeyBin.exe first and do as it says.
Run it and open you iso. Right-click the UPDATE partition and select "Delete partition". Confirm.

Now click on the + box to expand the DATA partition, then expand partition.bin.
Right click tmd.bin, select "Extract" and save it.
Do the same with ticket.bin.

Rename the extracted ticket.bin to rvlt.tik
Rename the extracted tmd.bin to rvlt.tmd

Copy/move both files to the "code" folder of the Wii VC title.

Your iso is now ready and you can close WiiScrubber.


2. nfs2iso2nfs
Move your iso to the "content" folder of the Wii VC. Rename the file to "game.iso".
The content folder should contain only game.iso and the "assets" folder. Delete any nfs files that are still present.

Copy nfs2iso2nfs.exe to the content folder and run it. If everything is in place, it will begin the conversion process.
It should take around 15 minutes. Its console window will close when it's finished.
Once it ends you can delete your iso file and nfs2iso2nfs.exe (and wii_common_key.bin if it exists).
The content folder should contain only the nfs files and the "assets" folder.

Optional: You can enable Classic Controller emulation for playing using only the gamepad.
Open meta.xml (it's in the meta folder) in notepad.
Look for the line

<drc_use type="unsignedInt" length="4">1</drc_use>

replace it with

<drc_use type="unsignedInt" length="4">65537</drc_use>

and save the file.
Note that this will only work if the game supports the Classic Controller.
If it doesn't either it won't boot or you won't be able to do anything and only the gamepad's power button will work.
Here's a list of such games: https://wiki.gbatemp.net/wiki/List_of_Wii_games_compatible_with_Classic_Controller


3.NUSpacker
The final part, building the installation files.
NUSpacker requires the Wii U common key. You should find it online and then open the file "encryptKeyWith" with
notepad and paste the key inside (hint: it begins with D7B0)

It's also a command line tool so you'll have to write down the commands, or simply create a new text file,
write the command inside, save it and change the extension from .txt to .bat

I recommend copying the Wii VC folder (that contains the other 3 folders, code, content and meta) to nuspacker's folder.
That will make everything easier.

The command works like this (replace with the names of your own folders)
If you folders have spaces in their names, enclose them in quotation marks, like "Just Dance".

java -jar nuspacker.jar -in GAME_FOLDER -out INSTALATION_FILES_FOLDER

Wiait until it finishes the process.
Now just copy the folder with the installation data to the "install" folder SD card, run a CFW and install it with WUP Installer GX2!

PS: If you make a nonfunctional game, remember to uninstall it before trying again.
If you install a fiunctional game over a broken installation, it will still appear as broken.

 

[piratesephiroth]

Does your update only work with the crc32 e2f27e9b fw.img that Fix94 worked with, or do some/all of your patches work with the other fw.img versions?

I'm not sure. I have 3 games here and all have that same fw.img so that must be a very common version.
But the patches search for patterns. Hopefully they will match the corresponding places on other revisions.

 

[markehmus]

I'm not sure. I have 3 games here and all have that same fw.img so that must be a very common version.
But the patches search for patterns. Hopefully they will match the corresponding places on other revisions.

https://gbatemp.net/threads/wii-on-wii-u-virtual-console-injecting-games.483007/page-41#post-7570180
i have a few listed so far

 

[ploggy]

So, today @pedro702 did a couple more tests for me and we got the gamepad data read out using the same fw.img as I already used the other day (the crc32 e2f27e9b one).

First you need this simple patch:
offset 0x1478A from 0x6818 to 0x2000
Set drc_use to that value needed for the gamepad classic controller emu to work, you can still use homebrew as you normally would in vwii mode, using a real wiimote with that patch.

Then there is this patch that moves down the gamepad data area low enough so wii apps can actually read it out with memprot and ahbprot still enabled:
offset 0x119A0 from 0x138BA004 to 0x13210000

And lastly, just to give a quick thing using the gamepad in wii homebrew I threw this demo together.
https://mega.nz/#!hlZlxCyQ!igqT2_jUXQnIHVwE2MCA9UVhLRUxBRT4HIfgn5_77AY
It just prints out all the buttons/sticks on screen, source is included.

While it is not much at least it shows that yes, you CAN use the gamepad outside those official wii games.

COOL! I just patched a the fw.img.
Gamepad and Wiimote now work in harmony and I tried your Gamepad tester app both work as expected Thank you.
The Gamepad still doesn't work with existing Wii Homebrew apps though? Would they have to be recompiled or something?

Thanks again.

 

[DarthDub]

COOL! I just patched a the fw.img.
Gamepad and Wiimote now work in harmony and I tried your Gamepad tester app both work as expected Thank you.
The Gamepad still doesn't work with existing Wii Homebrew apps though? Would they have to be recompiled or something?

Thanks again.

We are so close!

 

[ploggy]

We are so close!

Soooo Close.

 

[FIX94]

Would they have to be recompiled or something?

its a completely different interface that has nothing to do with wiimotes or bluetooth in general anymore, so it would have to be modified to accept that new interface.

 

[ploggy]

its a completely different interface that has nothing to do with wiimotes or bluetooth in general anymore, so it would have to be modified to accept that new interface.

Is that something you'd be able to do?

 

[Drak0rex]

Maybe it's already been asked, I don't feel like reading 45 pages, but could homebrew such as retro emulators and nintendont be injected into virtual console games to allow the gamepad to be used on them as well?

 

[FIX94]

Is that something you'd be able to do?

Well I started writing up plans for nintendont major version 5 (and man I have some cool plans), during that I'll need some new library, and since I wrote such a type of library before (libwupc) I'll just write up a new one in that style for the gamepad that can then be added to existing emus and stuff.

 

[piratesephiroth]

COOL! I just patched a the fw.img.
Gamepad and Wiimote now work in harmony and I tried your Gamepad tester app both work as expected Thank you.
The Gamepad still doesn't work with existing Wii Homebrew apps though? Would they have to be recompiled or something?

Thanks again.

I didn't quite understand that first patch. Does it make it possible to sync Wii Remotes alongside Classic Controller emulation?

 

[cucholix]

COOL! I just patched a the fw.img.
Gamepad and Wiimote now work in harmony and I tried your Gamepad tester app both work as expected Thank you.
The Gamepad still doesn't work with existing Wii Homebrew apps though? Would they have to be recompiled or something?

Thanks again.

This would be useful for Wii VC games that doesn't recognize gamepad as CC at the start, like Resident Evil 4? Does the Wiimote sync as player 1 too, as the gamepad?

 

[ploggy]

Dude you are a star.. This is a dream Iv'e had for a long time and now its finally happening Sunshine on Gamepad = awesome
THANK YOU!

If you need anything tested I'm always around

Also where can I download older version of Nintendont.?

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

I didn't quite understand that first patch. Does it make it possible to sync Wii Remotes alongside Classic Controller emulation?

Yes you can have both enabled at the same time. Just set Gamepad support as default and wiimote will work also

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

This would be useful for Wii VC games that doesn't recognize gamepad as CC at the start, like Resident Evil 4? Does the Wiimote sync as player 1 too, as the gamepad?

I haven't tested in depth but they are both recognised.

 

[FIX94]

To go into more detail about that patch:
The OHCI code either emulates incoming calls with that fake classic controller OR it is in a sort of "passthrough" when the gamepad was disabled in the meta to allow normal bluetooth input; what that patch does it make that code THINK that its disabled in the meta even though it isnt, so all the gamepad read threads still start up, this means you can use that "passthrough" mode for actual bluetooth input and also read out the gamepad memory normally used for classic controller emulation at the same time with a homebrew app.

 

[cucholix]

I wonder if fw.img are exchangeable among different bases...

Edit: Ok, was messing with the Wiimote+gamepad patch and it worked on Xeno base, not quite sure as only tried one variant but fw.img seems to work independently from the base, means that Rythm Heaven Fever fw.img patched can work on Xeno base.

I tried on one of those conflictive games (Guilty Gear XX) that check Wiimote + extension before boot the game code, it turns out that it recognize the Wiimote just fine asigning to P1, but the gamepad buttons are disabled, another weird thing is that forcing Wiimote de-sync by taking off the batteries (for example) freeze the game, it could be just a specific behavoir for this game though, not enough test to extrapolate to other games. Thanks to @ploggy for guide me in the patching process

 

[leseratte]

To go into more detail about that patch:
The OHCI code either emulates incoming calls with that fake classic controller OR it is in a sort of "passthrough" when the gamepad was disabled in the meta to allow normal bluetooth input; what that patch does it make that code THINK that its disabled in the meta even though it isnt, so all the gamepad read threads still start up, this means you can use that "passthrough" mode for actual bluetooth input and also read out the gamepad memory normally used for classic controller emulation at the same time with a homebrew app.

So if I understand that correctly, your patch basically lets player 1 have two controllers, the actual CC connected to Wiimote 1 and the emulated one on the Gamepad?
Or does the Wiimote actually sync as player 2? What if I only have one Wiimote, will that be "blocked" by the Gamepad or will it work for player 2?

 

[fejich]

@piratesephiroth
I added the "-wiimote" parameter, the software suggested: Wii Remote emulation enabled ....

With ftpiiu_everywhere overwrite the original file, but I went into the game GamePad does not work
I tested the game is: New Super Mario Bros. Wii

I tried three games of fw.img, all with the same result

1. New Super Mario Bros. Wii
2. Super Mario Galaxy 2
3. Xenoblade Chronicles

 

[leseratte]

NSMB and SMG2 use version 569.
Xenoblade uses version 570.

AFAIK, the "wiimote" patch is for version 590.

Try Rhythm Heaven. Or Pikmin. Or Mario Strikers Charged Football. Any game with fw.img version 590.

 

[pedro702]

So if I understand that correctly, your patch basically lets player 1 have two controllers, the actual CC connected to Wiimote 1 and the emulated one on the Gamepad?
Or does the Wiimote actually sync as player 2? What if I only have one Wiimote, will that be "blocked" by the Gamepad or will it work for player 2?

yeah both wiimote and gamepad will controll player 1 while a secon wiimote will control player 2 and so on.

@piratesephiroth
I added the "-wiimote" parameter, the software suggested: Wii Remote emulation enabled ....

With ftpiiu_everywhere overwrite the original file, but I went into the game GamePad does not work
I tested the game is: New Super Mario Bros. Wii

I tried three games of fw.img, all with the same result

1. New Super Mario Bros. Wii
2. Super Mario Galaxy 2
3. Xenoblade Chronicles

some games do not work with wiimote or even CC emulation , nintendo code is not 100% compatible incase you didint knew not even for CC.And yeah nsmb is not compatible with gamepad emulation sadly.

 

[leseratte]

yeah both wiimote and gamepad will controll player 1 while a secon wiimote will control player 2 and so on.

Do you think it'd be possible to change that so that the actual wiimote 1 is recognized as wiimote 2 by the vWii? Because with the current patch, you'll still need a wiimote for every player even if one of them plays with the gamepad.

 

[Columbo2811]

Do you think it'd be possible to change that so that the actual wiimote 1 is recognized as wiimote 2 by the vWii? Because with the current patch, you'll still need a wiimote for every player even if one of them plays with the gamepad.

Can't you press home button and go into controller settings and map wiimote 1 to player 2?