Original Xbox ISO to GOD: Converting OG Xbox Games for the 360
Original Xbox ISO to GOD conversion works in both modern tools — the Windows GUI and iso2god-rs read XGD1 images, parse the game’s XBE executable, and write a Games On Demand package with content type 0x5000 instead of the Xbox 360’s 0x7000. This guide covers what changes when the source is an original Xbox (OG Xbox) disc, what stays identical, and the Redump-image support the Windows fork adds.
What is different about an OG Xbox source
Three things change with a 2001-era disc, and everything else in the workflow is familiar:
| Aspect | Original Xbox | Xbox 360 |
|---|---|---|
| Disc format | XGD1 | XGD2 or XGD3 |
| Executable parsed for metadata | XBE (default.xbe) | XEX (default.xex) |
| GOD content type in the header | 0x5000 (Xbox Original) | 0x7000 (GamesOnDemand) |
| Title lookup list in the GUI | gamelist_xbox.csv | gamelist_xbox360.csv |
The output container is the same SVOD design either way — a header file plus a .data folder of parts, protected by the same hash tree — which is why one converter family handles both generations. What Is the GOD Format? explains that container, including where the 0x5000 and 0x7000 values live in the header.
Workflow in the Windows GUI
Download the GUI from the download page and use the standard flow from How to Use Iso2God: Add ISO, then read the metadata panel. For an OG image, xextool’s role is played against the XBE — the panel fills Name and Title ID from the original Xbox executable and its entry in the game list. Confirm the Title ID is populated and the name is the right game before converting; OG-era metadata is exactly where wrong or generic entries appear, and the name you approve here is what dashboards will display. Choose padding with the same judgement as for 360 titles — Partial remains the prudent default — and Convert. The fork carries OG-specific care worth knowing about: Redump-image support (it accepts OG images in the Redump preservation format) and thumbnail fixes for original Xbox titles, both listed among its quality-of-life additions over the 2010 original.
Workflow in iso2god-rs
The command-line tool treats an OG image as a first-class input: iso2god game.iso ./out detects the XGD1 image, parses its XBE for Title ID and title, checks its built-in title database, and writes the 0x5000 package. A --dry-run first is especially worthwhile here — read the Title ID and title it reports for these older discs before writing anything — and --game-title exists for the cases where the reported name needs correcting. Hashes and per-platform installs are in the iso2god-rs guide; binaries are on the download page.
Getting OG packages onto the console
A note on expectations for newcomers to the earlier console: original Xbox games vary more in their on-disc layout than the later, more uniform 360 catalogue, so an occasional title needing a second attempt — a different padding choice, a corrected title, an image rewritten by extract-xiso first — is a normal part of this library’s conversion work, not a sign that your disc or your tools are faulty.
Transfer is unchanged: header file and .data folder together, into the Content path for stock-dashboard visibility or anywhere scannable for Aurora and Freestyle Dash, following the transfer guide, or by FTP with the GUI’s uploader. The console requirement is also unchanged and worth repeating for this audience: these unlocked GOD packages need a modded console (JTAG/RGH/BadUpdate-class) — a stock retail 360 does not run them, for OG titles any more than for 360 titles. How an original Xbox game then runs on the 360 is the console’s own backwards-compatibility machinery; the converter’s job ends at producing a correct 0x5000 GOD package.
Names, thumbnails and the game lists
Original Xbox metadata deserves one extra minute of attention, because these discs predate the tidy standardisation later generations take for granted. The GUI resolves a game’s display name through its original-Xbox game list (gamelist_xbox.csv), and the fork’s corrections to those names are part of why its metadata panel usually shows the title you expect. Where the name comes back generic, truncated or simply wrong, edit it before converting: that text is written into the GOD header as UTF-16BE display title, and it is what every dashboard, scan result and library listing will call the game from then on. The same applies to the thumbnail extracted for the package. A missing thumbnail is cosmetic and never blocks a conversion, but fixing name and picture at conversion time is far easier than living with a library entry labelled by a filename. In iso2god-rs the equivalent lever is –game-title, applied when the –dry-run readout shows a name worth correcting.
Common mistakes with OG conversions
- Judging the package by 360 rules. An OG package carrying content type 0x5000 is correct, not mis-converted — expecting 0x7000 sends people reconverting healthy packages.
- Skipping the metadata check. OG-era XBE data and game-list coverage are patchier than 360 XEX data; the –dry-run or panel check is where a wrong Title ID gets caught cheaply.
- Assuming every OG image variant loads identically. Preservation-format (Redump) images are exactly the case the fork calls out with dedicated support — if one tool balks at an image variant, route the image through extract-xiso or the fork before doubting the disc.
- Forgetting the console requirement. A perfect 0x5000 package still needs a modded 360 to run. Conversion success and console compatibility are two separate checks.
The surrounding OG Xbox toolchain
OG work sometimes needs the image itself adjusted before or instead of GOD conversion, and the maintained tool there is extract-xiso from XboxDev — it creates, extracts and rewrites XISO images, including rewriting Redump images, and it is the xemu ecosystem’s standard utility. It is linked from the download page as extract-xiso. Older guides use the name ‘exiso’ for similar jobs; treat that as the legacy name for the same task family and prefer the maintained extract-xiso. Keep the division of labour straight: extract-xiso works on the ISO image, Iso2God and iso2god-rs convert the image into a GOD package.
Frequently asked questions
How can I tell an OG conversion worked?
The package structure is your evidence: a header file plus a complete .data folder, and — if you inspect it — content type 0x5000 in the header rather than 0x7000. On the console, the game appears in the dashboard scan with the name you approved at conversion time.
Does padding removal apply to OG Xbox games too?
Yes — OG images are padded to their mastered layout just as 360 images are, and the same None / Partial / Full judgement applies in the GUI, with Partial as the default. The reasoning and the counter-examples are in Padding Explained.
My OG ISO came as a Redump image. Which tool do I use?
Either modern route can serve you: the Windows fork explicitly lists Redump-image support for OG Xbox titles, and extract-xiso can rewrite a Redump image into a standard XISO first if your workflow needs one. Start with the fork for a direct conversion, and keep extract-xiso for image surgery.
Are OG and 360 GODs interchangeable on the console?
They are the same container family with different content types, and dashboards scan both through the same Content and scan-anywhere rules. They are not interchangeable as files — a package keeps the content type of the game it was converted from. More tutorials are in the Tutorials hub.