Xbox 360 Homebrew Library

Temporary exploit: This Xbox release specifies RGH/JTAG. Temporary exploit support is not confirmed.

HDD example

Hdd1:\apps\swanstation\

USB example

Usb0:\apps\swanstation\

Launch

swanstation.xex

1. Create the shown swanstation app folder on your HDD or USB device. This store ZIP has swanstation.xex at its root; extract its contents directly into that app folder.
2. Put your own PlayStation BIOS beside swanstation.xex and your owned disc images in games\. Keep all companion files and notices.
3. Launch swanstation.xex through your existing homebrew launcher, or add the parent apps folder to Aurora’s Content paths and scan it.

Per-game memory cards live in saves\. Wait a few seconds after saving before quitting.

swanstation-0.1.1.0.zip
2,199,302 bytes · SHA-256
4a6844861dd4318fe42d65754feef4d3f822d98fa1acee4b6627626c5a224957

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: ABadAvatar is explicitly supported. Run its matching runtime workflow after each reboot. BadUpdate and Peer Pressure are not separately certified by this app.

HDD example

Hdd1:\apps\balatro360\

USB example

Usb0:\apps\balatro360\

Launch

default.xex

1. Extract the manual ZIP on your PC. Copy its apps folder to the root of the console’s HDD, shown as Hdd1 over FTP. If apps already exists, copy only its balatro360 subfolder into it.
2. The final executable belongs at Hdd1:\apps\balatro360\default.xex. Put the required personal game data beside that XEX as described above. For a USB installation, copy the balatro360 subfolder into the shown USB app directory.
3. Launch default.xex through your existing homebrew launcher, or add the parent apps folder to Aurora’s Content paths and scan it.

Preserve the save folder. Hold Back + Start for one second to quit.

Balatro360-Xbox360-1.0.0.0.zip
2,331,470 bytes · SHA-256
c63dc4ccce4c848ac8c6b975a8326686c0f32e8334897660a783dc0196535c18

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: The publisher specifies RGH/JTAG; no temporary-exploit compatibility claim is made.

HDD example

Hdd1:\apps\dusklight\

USB example

Usb0:\apps\dusklight\

Launch

dusklight.xex

1. Create the shown dusklight app folder on your HDD or USB device. This store ZIP has dusklight.xex at its root; extract its contents directly into that app folder.
2. Keep the res folder intact. Put your own supported disc image beside dusklight.xex with the exact name dusklight.iso.
3. Launch dusklight.xex through your existing homebrew launcher, or add the parent apps folder to Aurora’s Content paths and scan it.

Keep Unlock Framerate off. Preserve TwilitRealm / Dusklight saves, settings and shader caches. Shader compilation and pop-in remain known limitations.

dusklight-0.1.0.0.zip
21,359,103 bytes · SHA-256
59b69f3e447c83165ff034d407316a1834aa6967408e935a8e51daa080993c19

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: This release specifies RGH/JTAG. BadUpdate, ABadAvatar and Peer Pressure support is not claimed by the publisher.

HDD example

Hdd1:\apps\starship\

USB example

Usb0:\apps\starship\

Launch

starship.xex

1. Extract the manual ZIP on your PC. Copy its apps folder to the root of the console’s HDD, shown as Hdd1 over FTP. If apps already exists, copy only its starship subfolder into it.
2. The final executable belongs at Hdd1:\apps\starship\starship.xex. Put the required personal game data beside that XEX as described above. For a USB installation, copy the starship subfolder into the shown USB app directory.
3. Launch starship.xex through your existing homebrew launcher, or add the parent apps folder to Aurora’s Content paths and scan it.

Leave frame interpolation at the default 30 FPS; scene-loading stalls are a known limitation.

Starship-Xbox360-0.2.0.0.zip
6,787,372 bytes · SHA-256
cfd6f0343d167869843f46d31165212249675e2ab9a28fa81e21b66947c56222

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: A specific temporary exploit/payload is not certified by the author. Do not infer compatibility from another app’s requirements.

HDD example

Hdd1:\apps\ctr360\

USB example

Usb0:\apps\ctr360\

Launch

default.xex

1. Extract the manual ZIP on your PC. Copy its apps folder to the root of the console’s HDD, shown as Hdd1 over FTP. If apps already exists, copy only its ctr360 subfolder into it.
2. The final executable belongs at Hdd1:\apps\ctr360\default.xex. Put the required personal game data beside that XEX as described above. For a USB installation, copy the ctr360 subfolder into the shown USB app directory.
3. Launch default.xex through your existing homebrew launcher, or add the parent apps folder to Aurora’s Content paths and scan it.

Preserve memcards\ and ctr360.ini. A Windows converter is included in the official manual package as an optional helper; it is not required for the console conversion path and was not run.

CTR360-Xbox360-1.0.3.0.zip
12,571,568 bytes · SHA-256
96fc653f711a9c94950eeb397de824c61fceb7be1c82ece71910cb5509c2ac99

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: The bundled release README specifies RGH/JTAG. A temporary exploit/payload combination is not confirmed by the publisher.

HDD example

Hdd1:\apps\hbstore\

USB example

Usb0:\apps\hbstore\

Launch

homebrew_app_store.xex

1. Extract the manual ZIP on your PC. Copy its apps folder to the root of your console’s HDD, shown as Hdd1 over FTP. If apps already exists, copy the hbstore subfolder into it.
2. The final path is Hdd1:\apps\hbstore\homebrew_app_store.xex. Keep cacert.pem beside that XEX. App installations require the writable HDD even if the store itself is placed on USB.
3. Start homebrew_app_store.xex from your dashboard. Installed apps each get their own folder in Hdd1:\apps\.

Homebrew-App-Store-Xbox360-0.1.0.0.zip
1,891,078 bytes · SHA-256
43eaec792e733b5cacb85e299af93ac9bac00891e5abd816da65e9db0f929d33

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: Use only after a compatible runtime payload. A temporary exploit session ends on reboot; do not install DashLaunch into NAND to make this dashboard persistent. Peer Pressure has separate plugin limitations.

HDD example

Hdd1:\Aurora\

USB example

Usb0:\Aurora\

Launch

Aurora.xex

1. Extract the full official package into a new Aurora folder on your HDD or USB drive. Keep your existing installation until the new one has been checked.
2. Launch Aurora.xex with your existing unsigned-code loader. Configure Content → Manage Paths for your Homebrew folders and choose a scan depth that reaches the XEX.
3. Back up your database and settings before migrating. Enable network modules only if the runtime supports them.

Aurora 0.7b.2 - Release Package.rar
22,647,806 bytes · SHA-256
0c7c765c3a5b938cfc64c71beda276a17d109b88df2a88e3f91eb1e74b7e46a0

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: Publisher does not certify BadUpdate, ABadAvatar or Peer Pressure. Aurora plugin compatibility depends on your active runtime. The corrected v1.1 installer is not yet verified on-console by the author.

HDD example

Hdd1:\Aurora\User\Scripts\Utility\AuroraAZInstaller\

USB example

Usb0:\Aurora\User\Scripts\Utility\AuroraAZInstaller\

Launch

Aurora script: Install Aurora A-Z

1. Extract AuroraAZInstaller into your actual Aurora\User\Scripts\Utility\ directory. Keep Main.lua, AuroraAZ.xex and icon.png together.
2. In Aurora open Scripts, refresh with X, run Install Aurora A-Z and select Install. The installer backs up an existing NetDbgDll.xex.
3. Reboot manually, restoring the temporary runtime first if applicable. Hold R3 to browse letters; R3 + L3 changes Browse / Filter mode.

AuroraAZ-v1.1-Installer.zip
1,623,449 bytes · SHA-256
725b6918c693e8bcf3f6f217f638a8fe4d1ed6b86bf0c7bdefbd8a7689fb6b27

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: Skin selection does not provide an exploit or make a temporary homebrew session persistent.

HDD example

Hdd1:\Aurora\Skins\Catppuccin-Latte-Blue.xzp

USB example

Usb0:\Aurora\Skins\Catppuccin-Latte-Blue.xzp

Launch

Aurora → B → Skin → Change

1. Copy the XZP file into the Skins directory of your actual Aurora installation. Do not unpack the XZP.
2. In Aurora press B → Skin → Change and select the new skin.
3. Press Back → Restart. Keep the previous XZP until the replacement loads correctly.

Catppuccin-Latte-Blue.xzp
8,259,338 bytes · SHA-256
473ef6e2cf880aba2e41be89ccbabc2f12875ab017eafaf5bd2a653c23579196

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: Skin selection does not provide an exploit or make a temporary homebrew session persistent.

HDD example

Hdd1:\Aurora\Skins\Catppuccin-Frappe-Blue.xzp

USB example

Usb0:\Aurora\Skins\Catppuccin-Frappe-Blue.xzp

Launch

Aurora → B → Skin → Change

1. Copy the XZP file into the Skins directory of your actual Aurora installation. Do not unpack the XZP.
2. In Aurora press B → Skin → Change and select the new skin.
3. Press Back → Restart. Keep the previous XZP until the replacement loads correctly.

Catppuccin-Frappe-Blue.xzp
8,253,241 bytes · SHA-256
6649ac7add90fcc26a790845585b0b3b747211368f56e921e2792c1e426ddbf1

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: Skin selection does not provide an exploit or make a temporary homebrew session persistent.

HDD example

Hdd1:\Aurora\Skins\Catppuccin-Macchiato-Blue.xzp

USB example

Usb0:\Aurora\Skins\Catppuccin-Macchiato-Blue.xzp

Launch

Aurora → B → Skin → Change

1. Copy the XZP file into the Skins directory of your actual Aurora installation. Do not unpack the XZP.
2. In Aurora press B → Skin → Change and select the new skin.
3. Press Back → Restart. Keep the previous XZP until the replacement loads correctly.

Catppuccin-Macchiato-Blue.xzp
8,253,392 bytes · SHA-256
49c2f5e541358c6ef45657ff6ce287fc87f5e0e7bda14aad2a408c0db6a47632

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: Skin selection does not provide an exploit or make a temporary homebrew session persistent.

HDD example

Hdd1:\Aurora\Skins\Catppuccin-Mocha-Blue.xzp

USB example

Usb0:\Aurora\Skins\Catppuccin-Mocha-Blue.xzp

Launch

Aurora → B → Skin → Change

1. Copy the XZP file into the Skins directory of your actual Aurora installation. Do not unpack the XZP.
2. In Aurora press B → Skin → Change and select the new skin.
3. Press Back → Restart. Keep the previous XZP until the replacement loads correctly.

Catppuccin-Mocha-Blue.xzp
8,255,172 bytes · SHA-256
c96c549c3e5a70bd3c4c1e024b46f5d1f2adaec2f4067a3020a46ae752359400

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: Publisher specifies RGH/JTAG; temporary exploit and Peer Pressure support are unverified.

HDD example

Hdd1:\Emulators\Harissa64\

USB example

Usb0:\Emulators\Harissa64\

Launch

default.xex

1. Extract the ZIP on your PC, then copy its whole Harissa64 folder into Hdd1:\Emulators\ or the shown USB Emulators folder. The XEX should be directly inside Harissa64, without a second nested Harissa64 folder.
2. Put your own games in Harissa64\roms\. Add the parent Emulators folder to Aurora’s scan paths, or browse to Harissa64 and launch default.xex.
3. For games in another location, open Files, browse to the desired folder, then press Y to use that current folder as the game folder.

Harissa64-2.0.8.zip
39,116,506 bytes · SHA-256
d181ce07e2b30a78e200cb4a1bea5906f0db38f54508ff109cbbd312aca3f8fc

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: The publisher specifies RGH/JTAG; temporary exploit support is not confirmed.

HDD example

Hdd1:\Emulators\HarissaDC\

USB example

Usb0:\Emulators\HarissaDC\

Launch

default.xex

1. Extract the ZIP on your PC, then copy its whole HarissaDC folder into Hdd1:\Emulators\ or the shown USB Emulators folder. The XEX should be directly inside HarissaDC, without a second nested HarissaDC folder.
2. Add your own games under HarissaDC\games\, keeping multi-track GDI / BIN sets together.
3. Launch default.xex through your existing homebrew launcher. Keep game settings and saves when upgrading.

Development build: graphical glitches and slow cutscenes are known. CHD loading may be slower.

HarissaDC-0.1.0-dev.zip
21,495,409 bytes · SHA-256
b49d608656832e2dad835f5d56ce4ee22c06b20538f7250269d4c7fd3a00bfb7

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: The author does not certify a temporary exploit/payload combination. Use an established compatible unsigned-code runtime.

HDD example

Hdd1:\Homebrew\Anarch360\

USB example

Usb0:\Homebrew\Anarch360\

Launch

anarch360.xex

1. Create a new Homebrew\Anarch360 folder on the HDD or FAT32 USB drive.
2. Copy anarch360.xex into it. Launch it from your existing unsigned-code file manager or add the folder to Aurora’s scan paths.

anarch360.xex
3,252,224 bytes · SHA-256
0652e4aaac97cbecf57ae8bbb1b87d812a80fd0595396d655b73f5c8fc01e23e

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: This skin does not enable unsigned code or persist a temporary exploit. A working Aurora setup is required; no specific temporary exploit or Peer Pressure certification is made.

HDD example

Hdd1:\Aurora\Skins\AuroraFlow.Global.xzp

USB example

Usb0:\Aurora\Skins\AuroraFlow.Global.xzp

Launch

Aurora → B → Skin → Change

1. Copy AuroraFlow.Global.xzp into the Skins folder of your actual Aurora installation. Keep your existing XZP until the new skin is checked.
2. Copy Modern.by.MaZ3.Global.cfljson into Aurora\Media\Layouts\. Keep skin and layout language variants matched.
3. Press B → Skin and select AuroraFlow (Global). Disable Animation and select the matching Modern by MaZ3 layout. Restart Aurora.

Keep the skin and layout language variants matched and disable Animation. The publisher’s skin metadata contains trailing legacy text; the original release is preserved unchanged. Keep a working skin available; physical-console behavior was not tested.

AuroraFlow.Global.xzp
31,007,960 bytes · SHA-256
bdc72ccda62de7ebdaa05bccf08311ec7ce65e4ca3021f60e945af8510abeaf3

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: This skin does not enable unsigned code or persist a temporary exploit. A working Aurora setup is required; no specific temporary exploit or Peer Pressure certification is made.

HDD example

Hdd1:\Aurora\Skins\AuroraFlow.EN.xzp

USB example

Usb0:\Aurora\Skins\AuroraFlow.EN.xzp

Launch

Aurora → B → Skin → Change

1. Copy AuroraFlow.EN.xzp into the Skins folder of your actual Aurora installation. Keep your existing XZP until the new skin is checked.
2. Copy Modern.by.MaZ3.cfljson into Aurora\Media\Layouts\. Keep skin and layout language variants matched.
3. Press B → Skin and select AuroraFlow (EN). Disable Animation and select the matching Modern by MaZ3 layout. Restart Aurora.

Keep the skin and layout language variants matched and disable Animation. The publisher’s skin metadata contains trailing legacy text; the original release is preserved unchanged. Keep a working skin available; physical-console behavior was not tested.

AuroraFlow.EN.xzp
31,210,299 bytes · SHA-256
868fc3c8374c5217da4247077e51e8693cb81f146bf4d50339c9b17eac41bb83

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: This skin does not enable unsigned code or persist a temporary exploit. A working Aurora setup is required; no specific temporary exploit or Peer Pressure certification is made.

HDD example

Hdd1:\Aurora\Skins\Def-NXESp-Av-Xblogov5.xzp

USB example

Usb0:\Aurora\Skins\Def-NXESp-Av-Xblogov5.xzp

Launch

Aurora → B → Skin → Change

1. Copy the original XZP to the Skins folder of your actual Aurora install via USB or FTP.
2. Press B → Skins and choose NXE Splash + Avatar + Xblogo. Restart Aurora.
3. Keep a working skin and file-manager recovery route before changing themes.

The author reports avatar prop animation is faster than normal. For personal use only; author grants no commercial or derivative-use license.

Def-NXESp-Av-Xblogov5.xzp
5,605,497 bytes · SHA-256
b7fcd1cfbb9f4ebd96b717e6afc03716c18291d5d23185f3a94b2f5a35be7b53

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: Original source describes an RGH setup. Temporary exploit and Peer Pressure compatibility are not confirmed; the skin itself cannot enable homebrew.

HDD example

Hdd1:\Aurora\Skins\XboxOneExperience.xzp

USB example

Usb0:\Aurora\Skins\XboxOneExperience.xzp

Launch

Aurora → B → Skin → Change

1. Confirm you are using the source-pinned Aurora0.6b installation and retain the working skin.
2. Copy XboxOneExperience.xzp into that installation’s Skins folder. Do not unpack it or overwrite Default.xzp.
3. Select Xbox ONE Experience in Aurora’s B → Skin menu, then restart Aurora.

The repository ships a ready XZP directly; only that file was downloaded, not a repository/source archive. Original packaged metadata identifies author CEOISS, revision1, creationdate2017-06-05 and auroraver0.6.

XboxOneExperience.xzp
6,420,180 bytes · SHA-256
bca1ecf133245b6e6a61d83633f3ef3a85c9878bf467308ec95c8fdf56fbc4c7

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: The author targets RGH/JTAG; BadUpdate, ABadAvatar and Peer Pressure are not separately certified. Release 0.8.10 still lists Xbox 360 timing/gameplay testing as outstanding.

HDD example

Hdd1:\Emulators\FCEUX360\

USB example

Usb0:\Emulators\FCEUX360\

Launch

fceux.xex

1. The release ZIP has fceux.xex and media at its root. Extract its contents directly into the shown FCEUX360 folder, keeping media/ui.xzp and media/xarialuni.ttf beside the executable’s directory.
2. Put your own .nes / .zip files in roms\ and launch fceux.xex from Aurora, FSD or XeXMenu.
3. Keep fceui.ini, scripts, ROMs, BIOS, screenshots, saves and states when upgrading. Battery saves use sav\; screenshots use snaps\.

START + BACK opens the in-game menu; LT rewinds, RT fast-forwards and right-stick click captures a screenshot. Use the full ZIP for a new installation; the standalone XEX asset alone omits required media.

fce360-enhanced.v0.8.10.zip
11,968,834 bytes · SHA-256
52870b7d2320814f2cb0e1f5f97b2b8c533b73b752ab7a314740de2fe8f91711

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: No specific temporary-exploit combination is certified in the frontend documentation. The optional hidmouse.xex DashLaunch plugin is a separate setup and must not be assumed compatible with Peer Pressure or another runtime without plugin support.

HDD example

Hdd1:\Emulators\Salvia\

USB example

Usb0:\Salvia\

Launch

default.xex

1. The Xbox 360 ZIP has default.xex, core XEX files, salvia.cfg and supporting directories at its root. Extract all contents directly into a dedicated Salvia folder, such as Usb0:\Salvia\ or the shown HDD path. Launch default.xex; individual core XEX files stay alongside it.
2. Keep Roms next to the XEX files or at the USB root. Put personal games into their system subfolders, such as nes, snes, Genesis, gb, gba, n64, psx and fbneo. Supply only BIOS files needed by the cores you use.
3. Change the library parent directory in Options → Emulation → Roms Main Directory, or roms_path in salvia.cfg. The frontend uses Hdd:\ for internal-HDD game paths and usb:\ to detect the USB port automatically.

SELECT + START exits emulation and SELECT + Y toggles the options menu by default. Saves/states are under data\saves and data\states. N64 support improved in 1.1.0; game compatibility remains core-specific. Mouse support is optional, not a requirement for controller use.

Salvia-360.zip
140,795,200 bytes · SHA-256
3e82efe38d35aa71567faf998c7e8db75adb471964b2df8915f067327303b47c

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: BadUpdate, ABadAvatar and Peer Pressure are not separately certified by this app’s documentation.

HDD example

Hdd1:\Apps\Simple360Player\

USB example

Usb0:\Apps\Simple360Player\

Launch

default.xex

1. Extract the ZIP on your PC and copy the whole Simple360Player folder into Apps on the console’s HDD or USB drive.
2. Launch default.xex from Aurora, FSD or XeXMenu and browse your own videos. Matching external .srt subtitles stay beside the video file.
3. Keep settings.ini when upgrading. The app writes settings and a log only beside its executable.

Press X during playback for aspect ratio and Y for audio/subtitle/options controls. 1080p H.264 is too demanding according to the author. Surround passthrough was not physically tested by this site.

Simple360Player-0.2.zip
6,398,773 bytes · SHA-256
eadb457719b5b6c92420e1e0c8bfa0986d00dcb2727f107b8421fff72f01e226

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: BadUpdate is explicitly supported. Re-establish its temporary unsigned-code session after reboot. ABadAvatar and Peer Pressure are not separately certified in the app documentation.

HDD example

Hdd1:\Apps\Multiplex360\

USB example

Usb0:\Apps\Multiplex360\

Launch

default.xex

1. Extract the release ZIP and copy its complete Multiplex360 folder to HDD or USB; start default.xex through your existing homebrew dashboard.
2. On first launch the console displays a code. Enter it at plex.tv/link on your phone or PC and select your Plex profile.
3. Keep auth.ini and settings when upgrading. From version 0.4 the app asks before installing its own updates and preserves the previous executable as default.old.

The author states it works with DashLaunch liveblock enabled and needs neither Xbox Live nor a stealth server. It writes only inside its own folder. Sign out through Settings or remove auth.ini yourself.

Multiplex360-0.4.zip
6,792,896 bytes · SHA-256
de565422ccf2789a3c9ec8305c57e6ca21981e6c7e1a8b57d413a9a56861bcc8

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: BadUpdate, ABadAvatar and Peer Pressure are not separately certified by the author. Do not infer support merely because another dashboard launches in that runtime.

HDD example

Hdd1:\Apps\Silverdash360\

USB example

Usb0:\Apps\Silverdash360\

Launch

default.xex

1. Extract Silverdash360-0.1.2-console.zip. It contains the complete Silverdash360 folder and required runtime files.
2. Extract the 0.1.3 update into that Silverdash360 folder on your PC, applying the new files there. Preserve both original archives and a copy of your existing installation.
3. Copy the prepared Silverdash360 folder into Apps on HDD or USB, then start default.xex. Review the first-run FTP settings; the first library scan may take time.
4. Keep the Data folder beside default.xex when upgrading: it holds settings, library data and cached artwork.

Silverdash360-0.1.2-console.zip
64,510,979 bytes · SHA-256
6478589dd4963294eca15961b5ecca8347d0442b4fbc5c136d20643194c5a1f1

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: The publisher does not certify BadUpdate, ABadAvatar or Peer Pressure; use a compatible established unsigned-code setup.

HDD example

Hdd1:\Homebrew\QuadCarnage\

USB example

Usb0:\Homebrew\QuadCarnage\

Launch

default.xex

1. Extract the ZIP on your PC. Copy its QuadCarnage folder to the shown HDD or USB Homebrew directory.
2. Keep Media, game data and all companion files beside default.xex. Launch the XEX through your existing homebrew file manager or add the directory to Aurora scan paths.

No physical-console execution was performed.

Quad Carnage for 360.zip
87,175,153 bytes · SHA-256
3df04b186612f6b10cf9ae6201c0e01f46c4753b45dcded3abff843842756b9c

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: A particular temporary exploit or runtime payload is not certified by this game’s author.

HDD example

Hdd1:\Homebrew\WowJay\

USB example

Usb0:\Homebrew\WowJay\

Launch

default.xex

1. Extract the full 7z archive directly into the shown WowJay directory: default.xex is at the archive root.
2. Keep the complete Media directory and data alongside default.xex. Launch default.xex through your existing homebrew launcher.

No physical-console execution was performed.

WOWJAY360.7z
37,455,015 bytes · SHA-256
d8d9fbfe8394c43e2c23f89ed6e5663257d4f83f2a17f8163acda6979da9eafb

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: The publisher does not certify a particular temporary exploit or payload combination.

HDD example

Hdd1:\Homebrew\NestBound\

USB example

Usb0:\Homebrew\NestBound\

Launch

NestBoud 360.xex

1. Extract the ZIP on your PC. Copy the contents of its NestBoud 360 folder to the shown NestBound directory.
2. Keep Media and all companion data intact. Launch NestBoud 360.xex; do not rename managed module XEX files inside Media.

No physical-console execution was performed.

NestBoud 360.zip
52,807,754 bytes · SHA-256
6580ec0cc55f3e44adbb1695d07cf2e83aaa9007f8d9b6e7763377459721bc62

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: BadUpdate, ABadAvatar and Peer Pressure are not separately certified by this release.

HDD example

Hdd1:\Homebrew\Slither360\

USB example

Usb0:\Homebrew\Slither360\

Launch

default.xex

1. Extract the complete RAR on your computer.
2. Copy the contents of Slither360-v0.10.2-dev.1-PUBLIC into the shown app folder, retaining assets/atlas.rgba and the license files.
3. Launch default.xex with your homebrew dashboard or file manager.

Development build: multiplayer disabled; back up saves before upgrading. Optional LIVE Vision support is for local testing. Independent project; developer discloses AI-assisted code. The bundled checksum list matches default.xex, assets/atlas.rgba and five other files; LEIA-ME.txt has a stale listed hash. The original RAR remains unchanged and its actual SHA-256 is recorded. No physical-console execution was performed.

Slither360-v0.10.2-dev.1-PUBLIC.rar
1,826,917 bytes · SHA-256
a28c7ce96e817a4cd270fb461348c6806edbcea8283ac039655ac2e315fe4dbc

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: The author does not certify specific temporary exploits or payloads.

HDD example

Hdd1:\Homebrew\PortalClone\

USB example

Usb0:\Homebrew\PortalClone\

Launch

default.xex

1. Extract only the Xbox archive PortalCloneXbox.rar on your PC.
2. Copy the complete PortalClone directory into a game/homebrew folder scanned by Aurora, or open its XEX from a file manager.
3. Launch PortalClone\default.xex with all Media files retained.
4. Launch PortalClone\default.xex with all Media files retained.

Tech demo: no test chambers or actual puzzles. Controls: sticks move/look; RT/LT place blue/orange portals, A jumps, left-stick click sprints. No physical-console execution was performed.

PortalCloneXbox.rar
55,805,775 bytes · SHA-256
2dbc6172f0802f8adab9e2ce53bde3d5397785caf4fca0dfac5e5d45574630cd

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: No specific BadUpdate, ABadAvatar or Peer Pressure combination is certified by this release. The author says version 0.38 launch, UI navigation and gameplay still require hardware testing.

HDD example

Hdd1:\Emulators\Snes360\

USB example

Usb0:\Emulators\Snes360\

Launch

Snes360.xex

1. The complete ZIP has Snes360.xex and media at its root. Extract all contents directly into the shown Snes360 folder.
2. Add your own ROMs to Roms or configure settings.xml, then launch Snes360.xex from Aurora, FSD or XeXMenu.
3. Preserve settings.xml, favorites.txt, saves and states when installing another version. Press both thumbsticks for the in-game menu.

Beta build. Achievement integration is removed. Supplied screenshots show an earlier interface version; they are publisher references, not hardware tests by this site.

snes360-enhanced.v0.38.zip
11,740,360 bytes · SHA-256
a305a177bc16d481333ed98fbfc217d0cbbc0f9775a0c54554d194ceba6176d6

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: The publisher targets JTAG/RGH; no BadUpdate, ABadAvatar or Peer Pressure certification is provided.

HDD example

Hdd1:\Emulators\Amiga360Refresh\

USB example

Usb0:\Emulators\Amiga360Refresh\

Launch

A360RF26.xex

1. The 7z contains the runtime directly at its root. Extract all directories and A360RF26.xex together into the shown folder; keep media and the supplied Software helpers intact.
2. Supply your owned Kickstart and media in the exact folders above, then launch A360RF26.xex.
3. Preserve Config, SAVE, personal media and hardfiles between versions. If a Workbench hardfile misses its first boot, use Reset Amiga in the app before retrying.

The optional 115 MB Tools CD is not needed for the basic emulator and was not downloaded. The author reports hardware testing of this branch; this site did not run the build. Floppy formats include ADF, ADZ, DMS, FDI, compatible IPF, ZIP and M3U.

A360RF26-Xbox.7z
14,235,921 bytes · SHA-256
146a2e42894f57944fbc9dfebb861a6a96992c993e3dbdf32b4ba91d436ed592

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: The author does not certify a particular temporary exploit/payload combination or Peer Pressure. Do not infer it from another emulator.

HDD example

Hdd1:\Emulators\AceDriverCollection\

USB example

Usb0:\Emulators\AceDriverCollection\

Launch

default.xex

1. Extract the ZIP on your computer. Copy its whole AceDriverCollection folder into Emulators on your HDD or USB; avoid nesting another AceDriverCollection folder inside it.
2. Place your own four required ROM/driver ZIPs in the included roms folder. Keep them zipped.
3. Launch default.xex from an existing homebrew dashboard or file manager.

Version 1.0.1 fixes rebinding and a camera-switch acceleration issue. System Link/online play remains unfinished; force feedback is partial, and the documented difficulty control adds time rather than changing AI behavior.

AceDriverCollection.zip
5,158,650 bytes · SHA-256
5a2936b833b7544f804f7cf9a93c9ad31a3116841058023f18c1a6eb670e9d7f

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: Explicit temporary-session support. Re-run your exploit/runtime after reboot. Keep launch.xex loaded: using its unload/load controls can crash the console. Peer Pressure does not support this DashLaunch-plugin workflow.

HDD example

Hdd1:\Apps\DashLaunchTemporary\

USB example

Usb0:\Apps\DashLaunchTemporary\

Launch

DashLaunch_for_BadUpdate.xex

1. Copy the standalone original XEX into the shown applications folder; launch it only after your runtime has loaded launch.xex.
2. Edit the desired launch.ini settings in the GUI and explicitly save to the intended existing HDD/USB launch.ini. Keep a backup.
3. Return to your existing homebrew launcher. This tool is a beta editor and does not make a temporary exploit persistent.

The fork disables installer/uninstaller/patch-update buttons and removes most NAND-writing code, but FTP can still modify flash. Do not write to flash through FTP. The author gives no safety guarantee and still lists unverified NAND paths and unfinished fan controls. No downloaded build was run here.

DashLaunch_for_BadUpdate.xex
1,699,840 bytes · SHA-256
1280828f7e33c21aa3d05ab2cbc0541e0cfa5eae0b91dcf33723ec744bcd1c9f

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: The author does not certify BadUpdate, ABadAvatar or Peer Pressure for this alpha runtime.

HDD example

Hdd1:\Apps\Triangle\

USB example

Usb0:\Apps\Triangle\

Launch

Triangle.xex

1. This is a local convenience ZIP assembled solely from the author’s ready runtime files at the pinned commit. Extract it on your PC; copy the contents of its Triangle-runtime-03cb4bc8e0e1 folder into the shown Triangle app directory.
2. Keep every original media/certs file and sources.json beside Triangle.xex, including the original secondary media/Triangle.xex.
3. Launch Triangle.xex using your existing homebrew dashboard, then review/add a trusted compatible source in Settings. The browser itself does not supply the content of third-party repositories.

Alpha snapshot, not an upstream ZIP release. The source repository contains ready binaries/resources rather than client source code. All 50 runtime originals were downloaded individually, their Git blob IDs checked, and their bytes retained unchanged in this bundle and staging manifest.

Triangle-runtime-03cb4bc8e0e1.zip
17,172,614 bytes · SHA-256
4544d5ed997ec5e3059857acd6df141a8a074895f4bd0c6875821a0f0160de2f

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: A working Aurora homebrew session is required. The skin does not supply an exploit, and its author does not certify a particular temporary payload or Peer Pressure combination.

HDD example

Hdd1:\Apps\Aurora\Skins\LiquidGlass.xzp

USB example

Usb0:\Aurora\Skins\LiquidGlass.xzp

Launch

Aurora → Settings → Appearance → Skin → Liquid Glass

1. Extract the official release ZIP on your PC. It contains an Aurora directory with both the skin and matching layout.
2. Copy LiquidGlass.xzp into the Skins folder of your actual Aurora installation, and Liquid Glass.cfljson into Aurora\Media\Layouts\. Preserve any existing versions before changing them.
3. Select Liquid Glass in Aurora’s skin settings. Then press B → View → Theme and choose the matching Liquid Glass CoverFlow layout. Restart Aurora if requested.

Enable game backgrounds for the intended appearance. The author notes that Greek Details text is truncated and the glass effect uses transparency rather than true blur.

LiquidGlass-Aurora-Skin-v1.0.0.zip
2,368,113 bytes · SHA-256
04b3e9328342ef6f462969fd4c694a65ba3e00ecb0eedcf2c0c28a27bc9cbec8

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: A working Aurora homebrew session is required. The skin does not supply an exploit, and its author does not certify a particular temporary payload or Peer Pressure combination.

HDD example

Hdd1:\Apps\Aurora\Skins\PolarGlass.xzp

USB example

Usb0:\Aurora\Skins\PolarGlass.xzp

Launch

Aurora → Settings → Appearance → Skin → Polar Glass

1. Extract the official release ZIP on your PC. It contains an Aurora directory with both the skin and matching layout.
2. Copy PolarGlass.xzp into the Skins folder of your actual Aurora installation, and Polar Glass.cfljson into Aurora\Media\Layouts\. Preserve any existing versions before changing them.
3. Select Polar Glass in Aurora’s skin settings. Then press B → View → Theme and choose the matching Polar Glass CoverFlow layout. Restart Aurora if requested.

Use the bundled matching layout to avoid cover overlap. Keep a known working skin available.

PolarGlass-Aurora-Skin-v1.0.0.zip
1,514,092 bytes · SHA-256
2081dbb5378a5000e9b5186fb79ecf8ba2021e0d720c92731776cd497529bbbc

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: BadUpdate followed by XeUnshackle is explicitly documented. Re-establish that runtime after reboot. Other temporary payloads and Peer Pressure are not separately certified by this release.

HDD example

Hdd1:\Homebrew\SilentHill\

USB example

Usb0:\Homebrew\SilentHill\

Launch

default.xex

1. Extract the ZIP on your PC. Copy its Silent Hill folder to a dedicated homebrew location, or copy that folder’s contents into the shown SilentHill path; avoid nesting it twice.
2. Put your own USA .bin under silenthill\ beside the optional silenthill.cfg. The final executable sits one directory above the disc image.
3. Launch default.xex from Aurora, FreeStyle or xbGuard after the documented runtime. Preserve silenthill\save\0.MCD when updating.

Alpha build: busy scenes can slow down and visual/combat/save behavior has known issues. Earlier test saves can have lost inventory items; memory cards are not interchangeable with the PC port. Keep your current saves and build. No physical-console execution was performed by this site.

SilentHill_Xbox360.zip
4,535,839 bytes · SHA-256
f9d0fccc547a0860c6541e8946f3213b2b5a7e906eb22928c4ea6936e27536e1

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: This collection requires an existing working Aurora setup. It does not provide an exploit or certify a temporary runtime / Peer Pressure combination.

HDD example

Hdd1:\Apps\Aurora\Skins\

USB example

Usb0:\Aurora\Skins\

Launch

Aurora → B / View → Skin

1. Download the original ZIP from the creator’s linked Google Drive file page, then extract it on your PC.
2. Copy the XZP files from inside the collection folder directly into the Skins folder of your actual Aurora install. Keep the original ZIP and existing skins; do not nest the collection folder under Skins.
3. In Aurora’s View / Skin menu, choose the desired skin and restart Aurora. Keep a known working skin available.

Includes four skins: Matrix and Trinity startup variants, each with and without background music. The creator states V1/V2 are retired and recommends V4; no older local version is removed.

Matrix Skins Aurora V4.zip
27,446,593 bytes · SHA-256
05b079ebd41aacddca8f5dfd9cdd96fa60352680285b027f3a29d2396806a880

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: The publisher does not separately certify BadUpdate, ABadAvatar or Peer Pressure; use a compatible established unsigned-code setup.

HDD example

Hdd1:\Homebrew\SonicEXE\

USB example

Usb0:\Homebrew\SonicEXE\

Launch

default.xex

1. Extract FinalUpdate.rar on your PC into a dedicated SonicEXE folder. Copy the complete extracted contents to the shown HDD or USB Homebrew directory.
2. Keep Media and every companion file beside default.xex, including the managed XEX modules under Media\Managed. Launch default.xex through your existing homebrew file manager or add the directory to Aurora scan paths.
3. Keep your current build and saves when upgrading. The included Changelog.txt describes the v1.0.0 save-system rework and v1.0.1–v1.0.2 fixes.

Horror fangame. Final Update is the exact Xbox 360 upload 19049130; Windows builds and older console releases are separate downloads. Archive integrity and executable formats were checked as data; no physical-console execution was performed.

FinalUpdate.rar
99,590,619 bytes · SHA-256
427ad55f5d64950135a969f0413d517c859d3b354e2d2032cb444d9bbf4c593d

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: BadUpdate, XeUnshackle and Peer Pressure compatibility are not separately stated by the publisher. Re-establish any temporary unsigned-code runtime used by your own setup after reboot.

HDD example

Hdd1:\Homebrew\SallyExe\

USB example

Usb0:\Homebrew\SallyExe\

Launch

default.xex

1. Extract Demo1.rar on your PC into a dedicated SallyExe folder. This archive has no enclosing game folder: default.xex and Media are already at its root.
2. Copy the complete extracted folder to the shown HDD or USB path. Keep Media and its Managed files beside default.xex; allow at least 819 MB for the complete extracted package.
3. Launch default.xex through your Xbox 360 homebrew dashboard after establishing your unsigned-code runtime. Keep this demo in its own versioned folder when preserving an older build.

Demo 1 (v0.1.0), marked in development by the author. The complete publisher archive is retained, including its box art and debug symbol files. Download integrity and file layout were inspected; the game was not executed or tested on a physical console.

Demo1.rar
126,278,336 bytes · SHA-256
97b95de2304ab6c720cde266d60fd0f2dca578b18a833da70fbee283e52a877f

File structure and SHA-256 checked. No console execution test performed.

Temporary exploit: This collection requires an existing working Aurora setup. It does not provide an exploit or certify a temporary runtime / Peer Pressure combination.

HDD example

Hdd1:\Apps\Aurora\Skins\

USB example

Usb0:\Aurora\Skins\

Launch

Aurora → B / View → Skin

1. Download the original ZIP from the creator’s linked Google Drive file page, then extract it on your PC.
2. Copy the XZP files from inside the collection folder directly into the Skins folder of your actual Aurora install. Preserve the original ZIP and existing skins; do not nest the collection folder under Skins.
3. In Aurora’s View / Skin menu, choose the desired skin and restart Aurora. Keep a known working skin available.

The original collection and every contained variant are retained together. Individual skin names may include their own revision suffixes; these are not separate game builds.

Silent Hill Skins Aurora Xbox360.zip
154,625,941 bytes · SHA-256
d764fcd76d4f3b582de6ec8d7cbc34667fdcb6f94b38011fe5912ab9330c2cf8

File structure and SHA-256 checked. No console execution test performed.