Modded PS5 Runs Original Xbox While 360 And PC Wait

By Indie Kings | October 4, 2026

Updated October 4, 2026: Jailbroken PS5 consoles can now run original Xbox games through XPSemu Alpha 1 with documented frame rate results. Xbox 360 support through BrinoBlitz and PC game support through a Wine based Proton project remain announced but unreleased with no public builds.

Image: Original Xbox console. Credit: Wikimedia Commons, public domain, Evan-Amos.

Per VideoCardz by WhyCry, jailbroken PS5 consoles have gained an original Xbox emulator called XPSemu alongside two separate announced projects for Xbox 360 and PC games. The report was published Oct 3, 2026 at 09:23 GMT and frames the moment as a maturity ladder with one shipped Alpha and two early announcements. This article keeps those tiers separate throughout. Shipped means tested with numbers. Announced means described with no public build.

The photograph above shows a 2001 original Xbox console, the machine being emulated, not a PS5 running it. That distinction matters because the story is about one console family imitating another through software. The Xbox system shown here used an x86 style CPU and a PC derived GPU. The PS5 recreates that behavior in software through XPSemu. No PS5 hardware is pictured here.

VideoCardz presents this wave as a follow on to recent PS5SX2 work that brought native PS2 emulation to jailbroken PS5 consoles. That PS2 precedent matters because XPSemu credits PS5SX2 for references on JIT memory, CPU layout and DualSense handling. The lineage is stated plainly in the source. PS5SX2 showed PS2 games could run as PS5 apps. XPSemu extends the idea to original Xbox games.

XPSemu Ships Alpha

XPSemu is a PS5 port of the open source xemu project for the original Xbox. It is for original Xbox games, not Xbox 360 games. That platform boundary is explicit in the VideoCardz report. Readers should not confuse XPSemu with Microsoft Xbox 360 emulation. The two efforts use different names and different code paths.

XPSemu runs as a PS5 app on a jailbroken console. It does not run inside Linux as a workaround. It is described as native PS5 homebrew software. That design choice keeps the project comparable to PS5SX2. Both aim to run older console software directly under the PS5 environment.

The CPU approach uses QEMU TCG JIT to handle the emulated Xbox CPU. JIT means just in time recompilation from Xbox CPU instructions into code the PS5 CPU can run. The report credits PS5SX2 references for help with JIT memory and CPU layout. That credit places XPSemu in a small shared knowledge base of PS5 homebrew developers.

The graphics approach uses the xemu Vulkan backend on the open source RADV driver for PS5. Vulkan is the rendering interface carried over from xemu. RADV is the open source Vulkan driver used here to reach PS5 graphics hardware. The combination is stated in the source as the technical basis for display output.

Alpha 1 boots games with an Xbox style user interface. That UI choice makes the software feel familiar to people who used original Xbox hardware. It is a presentation layer around game booting. It does not change the underlying emulation accuracy by itself.

Alpha 1 includes per game settings, patches, performance monitoring and internal resolution scaling from 1x to 4x. Per game settings allow tuning on a title by title basis. Patches allow frame rate or behavior changes where supported. Performance monitoring shows measured results during play. Resolution scaling raises internal render resolution above the original baseline.

The reported game results are limited to four named titles. Halo 2 is reported at 30 FPS stock and 36 to 50 FPS in gameplay with a 60 FPS patch. Crash Bandicoot The Wrath of Cortex is described as smooth. Forza Motorsport is reported at 15 to 21 FPS during racing. Fable The Lost Chapters is reported at 22 to 30 FPS in many areas and 10 to 20 FPS in heavier scenes.

Those numbers come from developer reports relayed by VideoCardz. They are not independent lab tests. They are not guarantees for other discs or other console units. They describe what was observed in the tested cases. This article treats them as developer reports, not as universal compatibility claims.

XPSemu stands apart because it has a public repo plus documented results. The presence of code and numbers lets readers check claims. The Wine announcement has neither a compatibility list nor performance figures. That gap defines the maturity ladder used in this article.

The second table below collects the XPSemu numbers in one place. Each row names one game and the reported result. Each row is labeled as a developer report. No other game should be read into this table.

Halo 2 is the strongest data point in the set because it pairs a stock figure with a patched figure. The stock result is 30 FPS. The patched gameplay range is 36 to 50 FPS with a 60 FPS patch applied. The patch raises the ceiling but does not lock every scene to full speed.

Crash Bandicoot The Wrath of Cortex is described only as smooth. No frame rate band is attached to that word in the source. Smooth here means playable in developer testing. It should not be converted into a specific number by readers.

Forza Motorsport sits lower at 15 to 21 FPS during racing. That range indicates a playable but clearly limited result. Racing games show frame drops more sharply than slower genres. The reported band keeps expectations grounded.

Fable The Lost Chapters shows the widest spread in the table. Many areas run 22 to 30 FPS. Heavier scenes fall to 10 to 20 FPS. The split shows how scene complexity changes load. One average number would hide that behavior.

The maturity ladder table below places XPSemu against the other named projects. XPSemu is listed as shipped Alpha. BrinoBlitz 360 is listed as announced. PP Proton is listed as announced. PS5SX2 is listed as context from prior coverage.

The table is the core of the article. It answers the central question in one glance. What runs today. What is only described. What came before. Readers who skip the prose still get the correct ranking from the table alone.

CPU Bound Not GPU Bound

The emulated Xbox CPU thread takes 85 to 97 percent of assigned PS5 CPU time. That figure is attributed to developer reporting relayed by VideoCardz. It describes sustained load on one assigned thread. It does not describe total PS5 system load.

The GPU is described as mostly idle during these tests. Idle here means the graphics side has headroom while the CPU side strains. That imbalance is common in emulation of older x86 systems. The hard work sits in translating CPU instructions correctly and quickly.

Resolution scaling from 3x to 4x costs little in many games. That detail supports the CPU bound reading. Raising pixel load barely moves total performance when the CPU is the limit. The GPU absorbs the extra pixels without becoming the new limit.

This pattern explains why a newer console can still show modest frame rates in old games. Raw PS5 power does not map one to one onto emulated Xbox speed. Translation overhead dominates. The 85 to 97 percent thread figure quantifies that overhead in one number.

The 1x to 4x scaling range is a feature of Alpha 1. It lets users trade sharpness against stability on a per game basis. In CPU bound titles the higher settings cost little. In other titles the cost may differ. The source limits the free scaling claim to many games, not all games.

Performance monitoring in Alpha 1 helps users see this balance directly. Frame data shows whether a slowdown tracks CPU load or render load. Per game settings then store the working choice. Patches add another lever where a 60 FPS patch exists.

Halo 2 illustrates the CPU story in practice. Stock speed holds 30 FPS. A 60 FPS patch lifts gameplay to 36 to 50 FPS. The gain is real but capped. The remaining cap points back to CPU translation limits rather than pixel limits.

Forza Motorsport and Fable show the same ceiling from the other side. Forza holds 15 to 21 FPS while racing. Fable drops to 10 to 20 FPS in heavier scenes. Both results fit a CPU limit that scene complexity makes worse. Extra GPU headroom does not rescue those scenes.

Future speed gains would need to come from CPU side efficiency. That could mean better JIT throughput or better thread use. It is unlikely to come from GPU tweaks alone while the GPU idles. The source does not promise a timeline for such gains.

This section stays narrow by design. Only the CPU thread figure and the scaling note are established. Broader claims about PS5 CPU topology or future optimization paths would need separate sourcing. Anything beyond the reported band is omitted here.

360 Announced Not Shipped

BrinoBlitz is described as an early Xbox 360 emulator on PS5. It is a separate project from XPSemu. The name distinction matters. XPSemu covers original Xbox. BrinoBlitz targets Xbox 360.

The reported plan is release after remaining bugs are fixed. That phrasing signals active work but not completion. Bugs pending means the software is not judged ready by its own author. No date is attached to that milestone in the source.

There is no public build for BrinoBlitz. There is no compatibility list for BrinoBlitz. Those two absences define its standing. Without a build, users cannot test it. Without a list, no game can be called supported.

BrinoBlitz sits at an earlier stage than XPSemu. XPSemu has Alpha 1 plus numbers for four games. BrinoBlitz has an announcement with no testable artifact. The ladder puts shipped above announced for that reason.

Readers should not treat 360 support as available on jailbroken PS5 consoles today. Availability means a build exists with documented behavior. BrinoBlitz does not meet that bar in the source. It meets the bar for a project to watch.

The Xbox 360 is a different emulation target from the original Xbox. It uses a different CPU architecture and a different software stack. Success with original Xbox does not imply near term success with 360. Each platform needs its own compatibility work.

VideoCardz does not attach game names to BrinoBlitz. No frame rates are reported for it. No resolution scaling claim is made for it. No CPU load figure is given for it. Silence on those points is itself information about maturity.

This article names BrinoBlitz in prose without linking to any page or file. No download location is given. No repo is linked. No video is linked. The project is identified so readers can follow future coverage, not so readers can fetch code today.

Any claim that a specific 360 game runs on PS5 through BrinoBlitz would be unverified on this source. Unlisted games stay outside this article. If other titles are mentioned elsewhere, they should be marked [NEEDS VERIFICATION] until developer data appears.

Proton Announced No Repo

PP PS5 Proton is described as a Wine port project for jailbroken PS5 consoles. The goal is to run Windows games and Windows apps without loading Linux first. That direct path is the novelty claimed in the report. It skips the separate operating system step used in older methods.

The project names associated in the source are Mihawk plus 0xManuel. Those names identify the announced effort. They do not by themselves establish availability. Attribution is not the same as a release.

The project has been demonstrated. Demonstration means shown working in some form. It does not mean released. The source reports a demo without a public build or repo. Readers cannot download or inspect it from the facts given.

Compatibility and performance for the Proton project are unknown. No game list is provided. No frame figures are provided. No settings or scaling details are provided. The absence of data is stated plainly so expectations stay flat.

XPSemu has a public repo plus documented results. The Wine announcement has neither a list nor figures. That contrast is drawn explicitly in the source facts. One project can be checked. The other can only be noted.

The phrase without Linux first deserves care. It describes a shorter boot path to Windows software. It does not describe Windows itself running on PS5. It does not describe Sony support for Windows apps. It describes an unofficial compatibility layer goal.

Wine here means a compatibility approach for Windows programs, not an emulator in the console sense. The report frames it as a Wine port plus Proton style packaging for PS5. Details beyond that framing are not established. This article does not fill the gaps with general Wine knowledge.

PC game readers should keep this project in the announced tier. Announced means worth tracking across future reports. It does not mean ready for testing. No install steps exist in this article because no install artifact is established.

This article names Mihawk and 0xManuel in prose without hyperlinking. No repo is linked. No post is linked. No video is linked. The names aid future source matching when a build or repo appears.

The 13.6 Jailbreak Context

The pace of PS5 homebrew accelerated after PS5 13.6 jailbreaks covering nearly all consoles on the market. That breadth explains why several projects surfaced close together. More testable consoles means more developers and more reports. The 13.6 firmware version is the reference point given in the source.

Nearly all consoles does not mean every console forever. It describes market coverage at the time of reporting. Firmware revisions change the picture. Readers should treat the phrase as a snapshot, not a permanent guarantee.

Sony released a new firmware described as performance optimization. The description comes from the release framing noted by VideoCardz. The technical content of that update is not detailed in the facts used here. Performance language alone does not confirm or deny exploit changes.

Jailbreak hopefuls should avoid updating until the new firmware is examined. That caution is relayed from the source. It is not a guide to staying on an old version. It is not a step by step firmware instruction. It is a wait and see warning tied to one update.

This article gives no jailbreak steps. It gives no firmware install guidance beyond relaying that avoid update caution. It links to no firmware files. It links to no exploit pages. Those limits are intentional and permanent for this post.

VideoCardz notes that jailbreaking is not only piracy. The cited uses include homebrew, open source software and alternative operating systems that Sony disallows. That framing places XPSemu and Wine work in a homebrew context. Emulation of owned games and open source tools are the examples in view.

The report adds that these environments cannot boot directly but automation eases use. That detail describes everyday friction. Users still need a boot path per session. Scripts or helpers reduce repetition without removing the underlying limit.

Sony as a platform holder sets the rules for allowed software on PS5. Microsoft as the Xbox platform holder owns the Xbox side of the compatibility question. Both names appear here only to identify platform roles. No approval or partnership is implied by either name.

The PS5SX2 precedent belongs in this context section as well. Native PS2 emulation arrived first and shared practical references with XPSemu. JIT memory handling, CPU layout notes and DualSense references moved across projects. That sharing helps explain the current speed of releases.

Warranty And Brick Warning

Jailbreaking voids warranty and risks bricking and bans. Voided warranty means Sony can refuse repair service tied to the modified console. Bricking means the console can be rendered unusable by a failed modification. Bans can restrict access to online services tied to the account or hardware.

Unofficial tools only are described in this article. XPSemu, BrinoBlitz and the Proton effort are not Sony products. They are not Microsoft products. They carry no platform support. Problems fall on the user with no vendor fix path.

This article gives no jailbreak steps. It gives no exploit chain. It gives no payload hosting notes. It gives no settings sequence for modifying a console. Anyone seeking those details will not find them here.

This article gives no firmware guidance beyond relaying the avoid update caution from the source. It does not recommend a target version. It does not explain how to block updates. It does not explain how to check versions. Firmware work is out of scope.

This article provides no downloads. It provides no repos. It provides no ROMs. It provides no ISOs. It provides no purchase links. It provides no download mirrors. Those categories are excluded in full.

No purchase, download, repo, firmware or ROM links appear anywhere in this post. The only external link is the VideoCardz source citation in Bottom Line. That single link exists for attribution. It is not a software source.

Readers who own Xbox discs should not read this article as legal advice. Ownership, backup rights and circumvention rules vary by country. The homebrew uses noted by VideoCardz do not settle those questions. Local law controls.

The safest reading of this coverage is observational. Developers are testing what jailbroken PS5 hardware can do. Some results are measured. Much remains unknown. Waiting for stable builds and clearer documentation is the cautious path.

What Is Not Established

Compatibility beyond the four listed games is not established. Halo 2, Crash Bandicoot The Wrath of Cortex, Forza Motorsport and Fable The Lost Chapters are the only named data points. Any other title mentioned in connection with XPSemu should be marked [NEEDS VERIFICATION]. That tag signals missing developer data.

BrinoBlitz compatibility is not established. No list exists in the source. No frame rates exist in the source. No settings exist in the source. The project standing is announced with bugs pending. Nothing more can be claimed on these facts.

Proton compatibility and performance are unknown. No Windows game is named as working. No app is named as working. No speed figure is given. Demonstrated without a build means observed by the reporter chain, not testable by readers.

General PS5 homebrew install behavior beyond the automation note is not established here. The source says environments cannot boot directly but automation eases use. Boot sequences, persistence and update survival are not detailed [NEEDS VERIFICATION]. This article does not generalize from that single note.

The content of the new Sony firmware beyond a performance optimization description is not established in the facts used here. Whether it changes exploit status awaits examination [NEEDS VERIFICATION]. This article relays the caution to avoid updating until examined. It does not assert what the firmware contains.

Prices, download counts, release dates and version numbers beyond Alpha 1 and firmware 13.6 are not established. This article states dates and versions explicitly where the source gives them. It invents no others. Gaps stay visible rather than filled.

The table pattern from earlier sections is the right lens for gaps. Shipped Alpha means code plus numbers. Announced means words without a build. Context means background that explains pace. Anything that does not fit those rows stays out.

FAQ

Does XPSemu play original Xbox or Xbox 360 games?
XPSemu plays original Xbox games, not Xbox 360 games, per VideoCardz by WhyCry.

What frame rates were reported for XPSemu Alpha 1?
Halo 2 at 30 stock and 36 to 50 with a 60 patch, Forza at 15 to 21, Fable at 22 to 30 and 10 to 20 in heavier scenes, plus Crash described as smooth.

Is BrinoBlitz Xbox 360 emulation available now?
No, BrinoBlitz has no public build and no compatibility list with release after remaining bugs are fixed.

Is the PS5 Wine Proton project available now?
No, it is demonstrated with no public build or repo and unknown compatibility and performance.

Why does resolution scaling cost so little in many games?
Because the load sits on the emulated CPU thread at 85 to 97 percent while the GPU stays mostly idle.

Should PS5 owners update to the newest Sony firmware?
Jailbreak hopefuls should avoid updating until the release is examined, as relayed from the VideoCardz report.

Bottom Line

XPSemu Alpha 1 is the only shipped item in this story with code and numbers. BrinoBlitz for Xbox 360 and the PP Proton Wine project for Windows games are announced without public builds. That ranking should guide every expectation until new developer data appears.

The CPU thread figure is the technical takeaway to remember. When one emulated thread takes 85 to 97 percent of assigned PS5 CPU time while the GPU idles, scaling pixels comes nearly free. Future gains depend on CPU side efficiency, not on prettier pixels.

The 13.6 jailbreak coverage explains the timing without promising permanence. Nearly all consoles on the market describes a window, not a right. Sony has already shipped a new firmware framed as performance optimization. Caution before updating is the only firmware point relayed here.

Sources: VideoCardz by WhyCry, Modded PS5 now runs original Xbox games, Xbox 360 and PC support are also in development, published Oct 3, 2026 09:23 GMT, full report. XPSemu, xemu, BrinoBlitz, Sony and Microsoft are named without links per house policy. No repos, posts, videos, firmware files, ROMs or ISOs are linked in this article.