Hacking NUS Downloader - v1.2 Beta

[bootsector]

thanks for the clarification!

 

[WB3000]

One of the best tools just got extremely better. Probably nothing could top the XML database and patching titles.

I would like to recommend either removing stub IOSes from the database.xml, or at least warn about them. At the time of writing, these are the known stubs: IOS4, IOS10, IOS11 v256, IOS16, IOS20 v256, IOS30 v2816, IOS50 v5120, IOS51 v4864, IOS254. (The ones without versions mean all of their revisions on NUS are stubs.)

Also, I couldn't help but notice BC and MIOS revisions were missing from the default database.xml. The versions for BC (1-100) are 2, 4, and 5. The versions for MIOS (1-101) are 4, 5, 8, and 9.

Thanks! I've updated the versions in the database on my end. I'm thinking that something like a tag with a description of what makes the title dangerous will be a good solution for not only stub IOS modules but also other dangerous titles (System Menu, etc.).

QUOTE(sirakain @ Jul 8 2009, 05:07 AM) And what is the "Amount of DLC" in the Trucha section ?

In section 'Fake (Trucha) Ticket Signing', the time limit is at 2147483647 sec, or 7F FF FF FF in hex. Shouldn't it be FF FF FF FF ? (or 4294967295 sec )

Also noticed you could check/uncheck the boxes while downloading.
you should disable the possibility to check the 'Trucha' Box when downloading a content that doesn't have a ticket.
and I'm confirming that when you successfully download a WW/VC, the button can't be clicked again.

DLC amounts are mostly useless with the titles that you can fully access with NUSD. Most of the time it is set to whatever the title version is. I figured I'd not remove the function to change it, unless there's a big reason not too.

What are you referring to as the limit? If a title is set to have a 7F FF FF FF time limit, it will be shown in the program as such. If you put the maxed out value in and it still goes to 7F ... , then there's a problem.

As far as checking boxes goes, I'll probably end up fixing that, although in some cases there's no harm done if, say, immediately after pressing start you decided that you wanted the WAD. Thanks for bringing up the fact that signing for the ticket should be disabled.

I'm not exactly sure what is causing the button to stay enabled, the last part of the downloading code enables everything no matter what. Do you have the ignore ticket checkbox ticked?

 

[supagusti]

you know, if you reconstruct another tik file ..... ive done it before it its really hard

You can't just make up some ticket and magically be able to decrypt NUS content. Constructing a ticket is only useful if you've got decrypted content that you want to install on the wii.

How - in a "normal" puchase process - is the CETK file downloaded to the wii?

 

[Dialexio]

Well the URL I'm using is wierd. I don't want to post it, because it's DLC for a game, instead of "tmd.xxxx" it's "00000000".


And when I don't put a version number in it says there's 1253 pieces of content. It doesn't actually download it, though it says it will.

The lowest version I could get to work was 151 pieces of content or so.

I guess I can just directly download the files.
Just change the URL from "00000000" to "tmd", download the file, and load the TMD in NUS Downloader. That ought to work. Remember NUS Downloader will not generate the ticket needed to play the game. That's why games should be purchased. (I'm not calling you a pirate.)

QUOTE(Dialexio @ Jul 8 2009, 09:31 AM) One of the best tools just got extremely better. Probably nothing could top the XML database and patching titles.

I would like to recommend either removing stub IOSes from the database.xml, or at least warn about them. At the time of writing, these are the known stubs: IOS4, IOS10, IOS11 v256, IOS16, IOS20 v256, IOS30 v2816, IOS50 v5120, IOS51 v4864, IOS254. (The ones without versions mean all of their revisions on NUS are stubs.)

Also, I couldn't help but notice BC and MIOS revisions were missing from the default database.xml. The versions for BC (1-100) are 2, 4, and 5. The versions for MIOS (1-101) are 4, 5, 8, and 9.

Keep up the great work!

Could you explain briefly what are stub IOSes? And why it can brick?

A "stub" IOS cannot be used at all. Nintendo uses these stubs to overwrite things that they don't like people using, such as IOS16 and PatchMii (which installed into IOS254).

As Nintendo uses a new IOS for the System Menu and Wii Shop Channel, they turn the old one into a stub. Let's say 4.2 uses IOS208 (obviously, it won't). In that update, they will also turn IOS60 into a stub, since nothing will use it any more. If somebody on 4.0 or 4.1 installs the non-functioning stub version, they will get bricked unless they have BootMii as boot2.

Also, in my list of stub IOSes, I inadvertently left out IOS40 v3072. (I added it to my post.) IOS40 v2320 is used by System Menu 3.3K.

 

[s3phir0th115]

While we go along with this whole stub thing, perhaps a system can be implemented to tell you what IOS number and version of the IOS a particular system menu depends on. I can imagine most stub related bricks come from not using the right version of an IOS for your system menu. For example, System Menu 3.2 needs IOS30 v1040. A brick in this case would most likely be caused by getting IOS30 v2816, the IOS30 stub, instead of v1040 that it need.

Just my thoughts. It would certainly save people a lot of trouble if that was shown. Perhaps you could put something like a dependencies box or something. If you did System Menu 3.2 would look like, "Dependencies: IOS30 v1040"

 

[WB3000]

I'm currently writing in support for icons in the database menuitems, green will be ticket and not dangerous, yellow is no ticket but safe, red is a dangerous title.

Currently, you can see the IOS depended upon from loading a TMD again. That information can and will be added to the download log as well.

Does 3.2 really require the exact specific version of the IOS? A TMD only specifies the IOS number, not version, so that would need to be hard coded somehow...

Danger tags have been implemented in the database as well. I'll update the beta once I get the icon usage straightened out.

 

[lll]

Does 3.2 really require the exact specific version of the IOS? A TMD only specifies the IOS number, not version, so that would need to be hard coded somehow...

I assume that most System Menus would freak out if given a stub IOS since they almost certainly use features that aren't present in IOS9.

 

[WB3000]

I assume that most System Menus would freak out if given a stub IOS since they almost certainly use features that aren't present in IOS9.

Stubs are a given that will fail, but perhaps say v1037 or v1039?

Anyways, I've recompiled another beta with many of the suggestions here implemented. The database has received a slight update as well.

NUSD v1.2 Beta 2: http://www.mediafire.com/?1jynydt1dhj

Thanks for all the suggestions!

 

[Bloodlust]

Earlier on there was a cboot2 softmod which uses ios16 and lu64.wad. If ios16 is a stub ios, then what is the purpose there?

 

[Dialexio]

System Menu 3.2 will accept any IOS30, so long as it's not a stub (obviously). That means 3.2 can operate on IOS30 v1037, though I'd think USB keyboard support might be wacked up. Heck, Waninkoko's Firmware Downgrader gives IOS30 v1039 for System Menus 3.0-3.2.

Everything seems good in beta2.

I would recommend making the contents of the tag appear in a prompt, though.

Earlier on there was a cboot2 softmod which uses ios16 and lu64.wad. If ios16 is a stub ios, then what is the purpose there?

Softmodding guides that use IOS16 rely on the leaked IOS16 v257. The version on NUS, however, is v512. v512 is a stub meant to prevent use of v257.

 

[Bloodlust]

System Menu 3.2 will accept any IOS30, so long as it's not a stub (obviously). That means 3.2 can operate on IOS30 v1037, though I'd think USB keyboard support might be wacked up. Heck, Waninkoko's Firmware Downgrader gives IOS30 v1039 for System Menus 3.0-3.2.

Everything seems good in beta2.

I would recommend making the contents of the tag appear in a prompt, though.

Earlier on there was a cboot2 softmod which uses ios16 and lu64.wad. If ios16 is a stub ios, then what is the purpose there?

Softmodding guides that use IOS16 rely on the leaked IOS16 v257. The version on NUS, however, is v512. v512 is a stub meant to prevent use of v257.

I take my hat off to you bro. You are the best! Thanks! No wonder IOS16 must be removed before installing the v257.

 

[s3phir0th115]

Thanks WB3000 for listening to others and me regarding feature additions. I checked in the latest beta you just uploaded and I like the safety warnings you added.

Regarding the whole System Menu IOS version thing, I'm fairly certain that all versions of a given IOS version work save the stubs of course. From what I understand little is changed in IOS revisions as they come out for compatibility reasons.

 

[sirakain]

Could someone mirror it ? Thanks !

 

[sirakain]

I HATE DOUBLE POST

 

[tomazzzi]

This is a damn great release.

Thanks for the work !

 

[WB3000]

Could someone mirror it ? Thanks !

http://sharebee.com/f56aef21

 

[Bloodlust]

I got a question, is the wad packer in NUS downloader reliable? It's because I just did a SHA-1 comparison of a v4.1J v448 system menu.wad from another source which is tested to work and the one packed with NUS downloader has a different SHA-1 value though the filesize for both are exact.

 

[carbonyle]

Yeah NUS Downloader is reliable for sure !
If you want some explications: http://wiibrew.org/wiki/NUS_Downloader

Size Differences

After the initial release, there were concerns rising about differences in file sizes between official WADs and NUSD ones. A first, obvious difference is in that official ones have a footer, and NUSD packed ones do not. This adds a few bytes onto the official ones which will not be present.

A second difference may be noticed in the Certificate Chain added to the WAD. While it may appear entirely different, it is simply ordered in a different way, and the Wii sees nothing different. V1.1 of NUSD will order the certs in the most common way, so that difference is covered.

The only real difference is in some tickets. NUS has a variation on the ticket for a title, as do the WADs that come in discs. While they are different, the only changed values are small (ticket_id and DLC purchases). The big things like Title Key remain intact. There has been no issues using these tickets, which is understandable as many are probably on your Wii right now.

 

[Bloodlust]

Yeah NUS Downloader is reliable for sure !
If you want some explications: http://wiibrew.org/wiki/NUS_Downloader

Size Differences

After the initial release, there were concerns rising about differences in file sizes between official WADs and NUSD ones. A first, obvious difference is in that official ones have a footer, and NUSD packed ones do not. This adds a few bytes onto the official ones which will not be present.

A second difference may be noticed in the Certificate Chain added to the WAD. While it may appear entirely different, it is simply ordered in a different way, and the Wii sees nothing different. V1.1 of NUSD will order the certs in the most common way, so that difference is covered.

The only real difference is in some tickets. NUS has a variation on the ticket for a title, as do the WADs that come in discs. While they are different, the only changed values are small (ticket_id and DLC purchases). The big things like Title Key remain intact. There has been no issues using these tickets, which is understandable as many are probably on your Wii right now.

Thanks for the info. However the above explanation only applies to 1.1. Without a doubt 1.2 should be the same (I hope).

 

[WB3000]

Thanks for the info. However the above explanation only applies to 1.1. Without a doubt 1.2 should be the same (I hope).

I haven't touched WAD packing code since the earlier releases.

If there's no more issues anyone can think of, I'll begin wrapping up this version. Thanks for all the suggestions.