Hacking easy way to patch wad with the right ticket?

[annubbis]

is there any easy way to do that?


PS: I have used the search engine and i found out that i had to install the wad, dump the wii memory and then, patch the .tmd with a wadpacker

 

[zidane_genome]

if your trying to install a VC game, just install the WAD from the download you got... there's not patching, dumping of the Wii memory, or anything like that... just install, reset the Wii, and play

 

[misticknight]

^but apparantly theres games with bad tickets, and games patched with good tickets.

 

[Arakon]

all games have bad tickets. they're all trucha signed.

 

[misticknight]

but what does patching with the WAD Packer do then cause i wanted to know and noone answered in my other topic.

 

[Arakon]

the patch option (-p) creates a fake ticket that works on any wii, because the original ticket only works on yours. so if you create a wad from your own downloaded VC game, you have to use that option for it to work for others.

 

[gamidi]

the patch option (-p) creates a fake ticket that works on any wii, because the original ticket only works on yours. so if you create a wad from your own downloaded VC game, you have to use that option for it to work for others.

Thats incorrect. The -p option just randoms the ticket gamecode so many channels with the same vc game can be created. What prevents the wii game from working on other wiis is the wii nand filesystem encryption but that is taken care by the wii fs dumper that decrypts everything. Kike wadpacker is what creates the incorrect tickets so if you have used this you cant download the actual game the ticket was refering to on the wii shop channel.

 

[Arakon]

eh, no. when the blaze packer came out, injection wads didn't exist yet, hence there was no need for different game IDs. I know for a fact that my release of PSII didn't work on other wiis until I used the -p option.

 

[blu9987]

the -p option does NOT randomize the ticket.
Through my own experimentation I found that the blaze packer -p command changes a line of hex at offset 0x01d1 in the .tik file......
Doesn't touch the 4 letter ticket at all...