Difference between revisions of "SystemUpdater"
m (Change incorrect information regarding updater TADs) |
m (Proof.) |
||
| Line 30: | Line 30: | ||
[[File:TWLCartNonWatermark.jpg|thumb|150px|left|Confirmed image of the cartridge. The same cartridge is used for TWL prototypes and other development applications.]] | [[File:TWLCartNonWatermark.jpg|thumb|150px|left|Confirmed image of the cartridge. The same cartridge is used for TWL prototypes and other development applications.]] | ||
==Uniquely signed TADs== | ==Uniquely signed TADs== | ||
| − | The TAD files in NitroFS are not development signed<ref>[https://randommeaninglesscharacters.com/dsidev/twlsystemupdater.html Twl SystemUpdater (rmc)]</ref>. Rather than being signed with "maketad.exe" like most TADs, these are signed with " | + | The TAD files in NitroFS are not development signed<ref>[https://randommeaninglesscharacters.com/dsidev/twlsystemupdater.html Twl SystemUpdater (rmc)]</ref>. Rather than being signed with "maketad.exe" like most TADs, these are signed with "maketad.updater.exe" from TwlIPL which uses an unknown key. Because of this the TAD files cannot currently be decrypted back into SRLs. |
| + | |||
| + | The signing process for the updater TADs can be found in the gigaleaks at: '''TwlIPL/trunk/build/systemMenu_tools/SystemUpdater/data/Makefile''' | ||
| + | [[File:twlsystemupdater maketad.png|center|thumb|388x388px|Twl SystemUpdater uses "maketad.updater.exe" to sign its TAD files.]] | ||
==Available versions== | ==Available versions== | ||
Revision as of 03:34, 8 December 2023
 Picture of v1.4a, running on No$GBA | |
| Cart ID | NTRJ - 0SUA |
|---|---|
| Found versions | v1.3a, v1.4, v1.4a |
| ROM Build Date | 2010-04-15 (v1.4a) |
The SystemUpdater is a collection of TAD files that allow you to update an IS-TWL-DEBUGGER or DSi Panda. These were mainly used for development consoles, and they do not work on retail units.
Features
The features for this cartridge are very simple. The cartridge contains updates for all regions (including China and Korea since v1.4) and they will be installed when selected. When a region has been selected, all the data will be deleted from the NAND and update-signed TAD's will be installed. Unlike regular TWL carts and exploits that do not have NAND access, this one does. If done correctly, the tickets, TWLCFG0.dat, TWLCFG1.dat and the system menu, with the bundled DSi applications have been installed. TwlNmenu and NandFiler are optional.
The cartridge can also detect if you're on a Panda or Debugger. If 16MB of memory is found, it will be listed as TWL CONSOLE (Panda, IS-TWL-CAPTURE). If 32MB of memory is found, it will be listed as IS_TWL_DEBUGGER.
- SystemUpdater Images
The main menu, showing a selection of regions.
You can cancel the update by pressing B, freezing the menu, forcing you to restart.
The menu asking you if you want to continue.
The menu testing if it can write to the NAND. It copies TWLCFG#.dat files afterwards.
The updater failing to install, due to update-signed TAD files.
The updater completing the installation. You have to turn off the DSi yourself.
Uniquely signed TADs
The TAD files in NitroFS are not development signed[1]. Rather than being signed with "maketad.exe" like most TADs, these are signed with "maketad.updater.exe" from TwlIPL which uses an unknown key. Because of this the TAD files cannot currently be decrypted back into SRLs.
The signing process for the updater TADs can be found in the gigaleaks at: TwlIPL/trunk/build/systemMenu_tools/SystemUpdater/data/Makefile
Available versions
With the updater comes a HTML file for instructions and troubleshooting. On the bottom of the page is a changelog[2] listed.
References
Notes
- Holding SELECT and A at the same time when continuing an update skips the installation for TwlNmenu and NandFiler.
- Instead of the version number being (eg.) v1.4E, it says v1.4E_dev, notifying you it has been updated using a SystemUpdater cartridge.
- The development DSi firmware cannot import or export .bin files from the system settings like a retail unit. It can only delete applications, therefore, TwlNmenu must be used.
