Aurora Disc to GOD: Converting Games on the Console Itself
Aurora Disc to GOD is the on-console route: the Aurora dashboard for modded Xbox 360 consoles includes a Disc-to-GOD script that converts a game on the console itself, without a PC conversion in between. That makes Aurora the natural counterpart to Iso2God — same destination format, completely different place of work.
Aurora is the current default custom dashboard for modded Xbox 360 consoles in ConsoleMods’ documentation, and the successor-line dashboard to Freestyle Dash (FSD). If you have set up a JTAG or RGH console recently, Aurora is very likely what boots on it. This guide describes what it does with GOD packages, what its disc-to-GOD route is good for, and where a PC conversion with Iso2God is still the better tool. One honesty note up front: we do not print an Aurora version number on this page, because we could not verify an exact latest version from a primary source in this session, and an invented one would help nobody.
The PC side of this workflow — converting, then uploading the finished package to Aurora over FTP — is covered step by step in the Iso2God FTP upload to Aurora guide. The converters themselves are on the download page.
What Aurora is, in one pass
- A custom dashboard for modded Xbox 360 consoles (JTAG, RGH, and BadUpdate-class setups), in the line that follows Freestyle Dash.
- A game scanner and library. Aurora scans GOD packages and extracted games stored anywhere on the console’s storage, not only in the stock Content folder.
- An FTP server. The console can receive files over the network, which is how PC-converted GOD packages are uploaded to it.
- A metadata fetcher. Aurora pulls cover art and title updates (TUs) through XboxUnity.
- A conversion host. Its Disc-to-GOD script converts a game on the console, described below.
That combination is why Aurora sits at the centre of most modern modded-console setups. The dashboard is not just a launcher; it is the library manager, the network endpoint, and — through the script — one of the conversion tools.
The on-console Disc-to-GOD script
The Disc-to-GOD script runs on the console and converts a game disc’s content into a GOD package in place. Its appeal is obvious: the game is already at the console, so there is no ISO to move to a PC, no conversion queue on another machine, and no package to transfer back. For a single game you already own on disc and want on the hard drive, that is the shortest path.
Its limits follow from the same fact. The console is doing the work, so the console’s speed, storage, and your patience set the pace, and you get none of the PC tools’ controls: no per-game padding decision of the kind the Iso2God GUI offers, no queue of many images processed while you do something else, and no command-line repeatability. Treat the script as a convenience for games at the console, not as a replacement for a library-scale PC workflow.
Scanning: GOD packages can live anywhere
One of Aurora’s most useful behaviours is where it looks. On the stock dashboard, a GOD package is only visible if it sits in the Content structure — Content\0000000000000000\<TitleID>\00070000\ on internal or USB storage. In Aurora, a GOD package can live anywhere on disk and be picked up by a scan of that path. That frees you from the stock folder discipline for games launched through Aurora, and it makes external and secondary drives much easier to organise.
Two qualifications keep that freedom honest. First, downloadable content still belongs under Content even when the game itself lives elsewhere. Second, “anywhere” still means “anywhere Aurora is configured to scan” — if a newly copied package does not appear, checking and re-running the scan for that path is the first fix, before suspecting the package.
Covers and title updates through XboxUnity
Aurora fetches cover art and title updates via XboxUnity, which is what turns a scanned folder of packages into a browsable library with artwork, and what keeps games updated without manual file hunting. If covers are missing after a scan, the usual cause is connectivity or the fetch step, not the GOD package itself — a package that launches is a working package whether or not its cover downloaded.
On-console conversion versus Iso2God on PC, compared briefly
| Question | Aurora Disc-to-GOD (on console) | Iso2God (on PC) |
|---|---|---|
| Where the work happens | On the modded console itself. | On a Windows PC (GUI), or Windows/Linux/macOS with the iso2god-rs command-line tool. |
| Best for | A disc you have at the console and want installed with the least moving around. | Building or rebuilding a library from ISO images, several games at a time. |
| Padding control | No equivalent of the GUI’s None / Partial / Full decision is the point of this route. | Full control: None, Partial, or Full per game — which matters for documented exceptions. |
| Transfer step | None; the package is created on the target storage. | Copy over USB, or upload by FTP to Aurora, Freestyle Dash, or another FTP target. |
| Repeatability | Manual, per game, at the console. | Queues in the GUI; scriptable, repeatable runs with iso2god-rs. |
The padding row is the one with real consequences. Documented cases such as Tetris – The Grand Master Ace (use Partial) and Wolfenstein: The New Order Disc 1 (keep padding) need a deliberate setting, and that decision lives on the PC side. See the best padding settings per game before converting a game with a known exception, whichever route you take afterwards.
A sensible combined workflow
- Convert the bulk of a library on PC with Iso2God or iso2god-rs, choosing padding per game.
- Upload finished packages to Aurora by FTP — the dedicated walkthrough is the FTP upload guide.
- Scan the destination path in Aurora so the new packages appear in the library.
- Fetch covers and title updates through XboxUnity once the games are listed.
- Use the on-console Disc-to-GOD script opportunistically for a single disc that is already at the console, rather than round-tripping it through the PC.
Who this is for — and who it is not
Everything on this page assumes a modded console. Aurora itself only runs on a modified Xbox 360, and GOD packages produced by Iso2God carry an unlocked licence that a stock retail console refuses. There is no Aurora route for an unmodified console, and any page suggesting otherwise is misleading you. On a PC, the equivalent playback route for GOD packages is an emulator, covered in the Xenia GOD format guide.
Frequently asked questions
What is Aurora on Xbox 360?
Aurora is a custom dashboard for modded Xbox 360 consoles, the current default in ConsoleMods’ documentation and the successor-line to Freestyle Dash. It scans and launches games, serves FTP, fetches covers and title updates via XboxUnity, and hosts a Disc-to-GOD script.
Can Aurora convert a game disc to GOD?
Yes. Aurora includes an on-console Disc-to-GOD script that converts a game on the console itself, with no PC conversion step and no transfer afterwards.
Where do GOD packages have to be for Aurora to see them?
Anywhere on the console’s storage that Aurora is set to scan. Unlike the stock dashboard, Aurora is not limited to the Content\0000000000000000\<TitleID>\00070000\ path — though DLC still belongs under Content.
Should I convert on the console or on a PC?
On the console for a single disc that is already there; on a PC for a library, for repeatability, and for any game where the padding setting matters. The two routes produce the same kind of package and combine well.
More console-side and conversion guides are collected on the Tutorials hub.