GOD Game Not Showing on Xbox 360: Path and Title ID Fixes
When a GOD game is not showing on your Xbox 360, the game files are usually fine — they are simply not where the dashboard looks, or the header file has been separated from its data folder. The fix is almost always about location and structure: the exact Content path, the correct Title ID folder, and keeping the package’s two parts together.
This page covers both situations: the stock dashboard, which only looks in one specific place, and custom dashboards such as Aurora, which scan wherever you tell them to. If instead your console finds the game but calls it corrupted, go to our corrupted content fix — that is a different problem with different causes.
How a GOD package is structured (and why it goes missing)
A conversion produces two things that belong together: a header file (the package header, named for the package) and a folder with the same name plus .data, containing numbered part files such as Data0000, Data0001 and so on. The header is what dashboards list and launch; the .data folder is where the game actually lives. Copy one without the other, rename one of them, or split them across folders, and the dashboard sees nothing usable — the single most common reason a converted game “doesn’t show up.”
The stock dashboard path — there is only one
For a game to appear in the stock dashboard’s library, it must sit in this exact location on the internal drive or a configured USB storage device:
Content\0000000000000000\<TitleID>\00070000\Inside 00070000 go the header file and its .data folder, side by side. Every level of that path matters:
| Path level | What it must be | Common mistake |
|---|---|---|
| Content | The literal folder name at the root of the storage device | Placing the game in a self-named Games folder and expecting the stock dash to find it |
| 0000000000000000 | The shared / zero profile folder used for GOD content | Using a profile ID folder instead |
| <TitleID> | The game’s own eight-character Title ID, as a folder name | A typo, the Media ID, or the title ID of a different (or regional) release |
| 00070000 | The content-type folder for Games On Demand titles | Using another content-type folder, or skipping this level entirely |
Title ID mismatch: the invisible typo
The folder name must be the game’s Title ID exactly. Iso2God reads the Title ID from the game’s XEX during conversion — the GUI shows it in the metadata it extracts, and iso2god-rs can report it before you convert (its --dry-run mode exists for exactly this kind of check; see our iso2god-rs guide). A folder named with a transposed pair of characters, a Media ID instead of a Title ID, or the Title ID of a different regional release will all leave the dashboard blind to a perfectly good package. If a game refuses to appear, compare the folder name character by character against the Title ID the converter reported, and rename rather than reconvert — the package itself does not need rebuilding.
Check the transfer actually completed
- Confirm both items are present in
00070000: the header file and the matching.datafolder, with identical base names. - Open the .data folder and confirm the part files are all there and sensibly sized. A transfer interrupted by a USB dropout can leave a header with missing parts — which may show as corrupted rather than missing, as explained in our corrupted content guide.
- Re-copy the package from your PC if anything looks short, using a wired connection or a known-good USB device where you can.
- On the console, restart the dashboard (or reboot) after copying, then check the game library again.
Aurora and custom dashboards: scan paths and refresh
In a custom dashboard such as Aurora or Freestyle Dash, a GOD package can live anywhere on the drive — it does not need the Content path. What it needs is to be inside a location the dashboard actually scans:
- Open the dashboard’s content / scan settings and confirm the folder (or its parent) is listed as a scan path, with a scan depth deep enough to reach the package.
- Trigger a manual scan or content refresh after copying new games, rather than assuming the library updates itself instantly.
- Confirm the header file and .data folder travelled together to the new location, exactly as in the stock-dash checks above.
- Remember the exception: downloadable content still belongs under the Content structure even when the game itself lives elsewhere (next section).
DLC and title updates live somewhere else
A frequent source of confusion: the game shows, but its DLC does not (or the reverse report — someone “fixed” a missing game by moving folders and broke their DLC). Games scanned by Aurora can sit anywhere, but DLC must sit under the Content folder structure, in the game’s Title ID folder, to be found. Keep the two ideas separate: game package placement is flexible on a custom dashboard and strict on the stock dashboard; DLC placement is strict in both cases.
One honest limitation
Placement fixes assume the console can run Iso2God output at all. GOD packages produced by Iso2God carry an unlocked licence and are made for modded consoles — JTAG, RGH, or a BadUpdate-class exploit — or for emulation in Xenia. A completely stock retail console will not list or launch them no matter how correct the path is; that refusal is by design on Microsoft’s side, not a fault in your copy. If you are testing on a stock machine, test on the modded console or in Xenia instead.
Frequently asked questions
Where exactly do GOD games go on Xbox 360?
For the stock dashboard: Content\0000000000000000\<TitleID>\00070000\ on the internal drive or a configured USB device, with the header file and its .data folder together inside 00070000. In Aurora or Freestyle Dash, the package can live anywhere covered by a scan path.
My game folder uses the right path but the game still does not show. Why?
Check the Title ID folder name character by character, and confirm the header file was not separated from its .data folder during the copy. Those two account for most remaining cases. Then reboot the console and check again.
Do I need to reconvert if the Title ID folder was wrong?
No. The package itself is unchanged by its folder name. Rename the folder to the correct Title ID — the one Iso2God or iso2god-rs reported for that game — and rescan or reboot.
The game shows in Aurora but the DLC does not. What is wrong?
DLC must be under the Content structure in the game’s Title ID folder, even when the game itself is stored elsewhere for Aurora to scan. Move the DLC there and refresh. More fixes live on the Troubleshooting hub, and the converters themselves are on our download page.
If you transferred by FTP, check the destination twice
FTP uploads add one more place for a game to hide: the wrong destination folder. The GUI has long offered FTP upload to the console, and the fork lets you choose the destination path — which means a package can upload successfully to a folder that is neither the Content path nor one of Aurora’s scan paths, and then appear to have vanished. If a game is missing after an FTP transfer, list the destination on the console with a file manager before reconverting anything: confirm the header file and .data folder actually arrived, note exactly where they landed, and then either move them into Content\0000000000000000\<TitleID>\00070000\ or add that location as a scan path in your dashboard. Also confirm the storage device itself is the one the dashboard is set up to read — a package copied perfectly to a second USB device that was never configured as storage will not be listed either. These are five-minute checks, and they rescue far more “missing” games than reconversion ever will.