IIRC it does some magic with the files to validate the ticket.
What I'm sure about that it validates the ticket OFFLINE.
What I'm sure about that it validates the ticket OFFLINE.
The title instalation with single byte modification, or they have to create two different title ID for each game (digital and disk) to fix that?what can be patched?
we can't generate signatures without the private key or we could install homebrew directly to the WiiU menu.
Woah this is getting interesting.alright now, here is something crazy for you:
I just dumped some .tik files from discs I had over network using iosuhax and... the tiks already start with "01" and are "xor'd" as well, meaning dumped tiks like that cant be installed directly without any errors, so the question now is, are those files in .wuds somehow unclean or does the wiiu at some level automatically even from disc adjust those values so the wiiu can actually use them? that explains though why they have to be changed in the first place I guess to be installable.
I've dumped my eshop tiks as well and they contain my console id (4 bytes at 0x1D8) so you can most likely only install them directly on your own console unless you run a ciosu with signature checks disabled, else you probably risk a brick.Woah this is getting interesting.
One question though. Can the same method be used for already installed titles, as in, eshop purchasses?
NWPlayer is dumping hers, so we know it can be done.I've dumped my eshop tiks as well and they contain my console id (4 bytes at 0x1D8) so you can most likely only install them directly on your own console unless you run a ciosu with signature checks disabled, else you probably risk a brick.
Another question regarding this. Would it be possible to compare a dumped ticket from one of those that already exist, possibly to find a pattern, or a potential similarity between them? That could possibly lead to some sort of dummy ticket that could be used for the same game without a wud, maybe?I've dumped my eshop tiks as well and they contain my console id (4 bytes at 0x1D8) so you can most likely only install them directly on your own console unless you run a ciosu with signature checks disabled, else you probably risk a brick.
No. The thing why this works most likely has to do with the tik not requiring a specific console, nintendo used the exact same sign mechanism for both eshop titles and disc titles so, disc titles cant have a console id requirement, which is why you can install it globally on every wiiu if you have an installer. The 3ds had similar things and the wii too by the way. So changing anything in a tik right now such as, removing that id, or changing it to another region id would make it invalid because its signature would not match up anymore.Another question regarding this. Would it be possible to compare a dumped ticket from one of those that already exist, possibly to find a pattern, or a potential similarity between them? That could possibly lead to some sort of dummy ticket that could be used for the same game without a wud, maybe?
Oh I see. Well then now I know, hahaNo. The thing why this works most likely has to do with the tik not requiring a specific console, nintendo used the exact same sign mechanism for both eshop titles and disc titles so, disc titles cant have a console id requirement, which is why you can install it globally on every wiiu if you have an installer. The 3ds had similar things and the wii too by the way. So changing anything in a tik right now such as, removing that id, or changing it to another region id would make it invalid because its signature would not match up anymore.
edit: I can even proof this to you, somebody just was friendly enough to dump a game tik I also had from his console and if I compare both tiks they indeed differ a lot because of the signatures:
You can see on the counts alone that there would be no way to brute force that to another console.
alright now, here is something crazy for you:
I just dumped some .tik files from discs I had over network using iosuhax and... the tiks already start with "01" and are "xor'd" as well, meaning dumped tiks like that cant be installed directly without any errors, so the question now is, are those files in .wuds somehow unclean or does the wiiu at some level automatically even from disc adjust those values so the wiiu can actually use them? that explains though why they have to be changed in the first place I guess to be installable.
That's interesting. So basically no pirated DLC without CFW, and yet for some reason they didn't think to do the same thing for games. How bizarreNo. The thing why this works most likely has to do with the tik not requiring a specific console, nintendo used the exact same sign mechanism for both eshop titles and disc titles so, disc titles cant have a console id requirement, which is why you can install it globally on every wiiu if you have an installer. The 3ds had similar things and the wii too by the way. So changing anything in a tik right now such as, removing that id, or changing it to another region id would make it invalid because its signature would not match up anymore.
edit: I can even proof this to you, somebody just was friendly enough to dump a game tik I also had from his console and if I compare both tiks they indeed differ a lot because of the signatures:
You can see on the counts alone that there would be no way to brute force that to another console.
Games come as discs, while DLC does not. Really not that bizarre. Discs need to be universally signed to work on every console. DLCs need not.That's interesting. So basically no pirated DLC without CFW, and yet for some reason they didn't think to do the same thing for games. How bizarre