Xerxes

Joined 25 November 2014
m
Line 98: Line 98:
<pre>http://ccs.cdn.shop.wii.com/ccs/download/00010001<ID prefix>/tmd</pre>
<pre>http://ccs.cdn.shop.wii.com/ccs/download/00010001<ID prefix>/tmd</pre>


The <ID prefix> bit needs to be replaced with the first four characters of the ID you're trying to confirm in hex ([http://ccs.cdn.shop.wii.com/ccs/download/000100014A414C54/tmd here] is a working link for prefix JALT as an example). If the prefix exists, a download will begin for an extensionless file named "tmd"; otherwise, a 404 will be reached. This file can then be opened with a hex editor, and the full ID can be seen (with a small gap between the prefix and publisher code) around halfway through the file in cleartext.
The <ID prefix> bit needs to be replaced with the first four characters of the ID being confirmed in hex ([http://ccs.cdn.shop.wii.com/ccs/download/000100014A414C54/tmd here] is a working link for prefix JALT as an example). If the prefix exists, a download will begin for an extensionless file named "tmd"; otherwise, a 404 will be reached. This file can then be opened with a hex editor, and the full ID can be seen (with a small gap between the prefix and publisher code) around halfway through the file in cleartext.


The major problem with this method is that it can only be used for ID confirmation and not addition, since the prefix must be known ahead of time. There's been efforts to scrape the entire update server for all TMDs and therefore never run into this problem, but the work is still pending.
The major problem with this method is that it can only be used for ID confirmation and not addition, since the prefix must be known ahead of time. There's been efforts to scrape the entire update server for all TMDs and therefore never run into this problem, but the work is still pending.
6,906

edits