electronics Aug 1, 2026 ◑ 3 views ◯ 6 min read

How to Install Custom Firmware on a Sony PSP for Homebrew and Backups

pspsony pspcustom firmwarecfwhomebrewretro gaminghandheldmoddingemulationark 4memory stick

The PSP remains one of the best handheld platforms for homebrew and retro emulation almost two decades after launch — a real MIPS CPU, a big screen for its era, and (unlike most modern consoles) a scene that's had years to mature its custom firmware. This guide covers identifying your PSP model and firmware version, choosing the right CFW path for it, installing a homebrew launcher, and loading your own game backups and emulators. It does not cover where to obtain copyrighted ROMs — only dump and load games you actually own.

A Quick Legal Note

Installing custom firmware and running homebrew software is legal — it's your hardware, and CFW itself does nothing but unlock functionality Sony didn't expose. Dumping UMDs or memory-stick games you own for personal backup is widely considered fair use in most jurisdictions, similar to ripping a DVD you own. Downloading ROMs of games you don't own is copyright infringement regardless of what CFW makes technically possible. This guide treats "load your ROMs" the same way it would treat "load your MP3s" — assuming you're the one who put them there from media you own.

Step 1: Identify Your Model and Firmware Version

The PSP line spans several hardware revisions, and the CFW installation path depends entirely on which one you have and what firmware it's currently running.

ModelNotes PSP-1000 (Phat)Original model, UMD drive, most exploit-friendly PSP-2000/3000 (Slim)Slimmer, brighter screen, still has UMD drive PSP Go (N1000)No UMD drive, digital-only, different CFW path (Adrenaline-based) PSP Street (E1000)Budget model, no WiFi on some units — affects exploit delivery method

Check your firmware version under Settings > System Settings > System Information. Write this number down — it determines everything in the next step.

Step 2: Choose Your CFW Path

The exploit landscape depends on your firmware version:

Firmware 6.60/6.61 (most common on used units): Install ARK-4 directly — its browser-based installer handles the whole permanent-CFW chain in one pass, no separate exploit tool needed first.
Firmware 6.20–6.39: Update to 6.60 first (Sony's official update, safe and expected), then follow the 6.60 path above.
Firmware 5.00 or below (older units, rare today): These predate ARK-4's supported range — check the Legacy Exploits page, though updating to 6.60 first is usually simpler unless you have a specific reason to stay low.
PSP Go: Uses Adrenaline, a different install chain built around the Go's internal flash rather than a memory stick — follow that page specifically rather than the Phat/Slim steps below.

ARK-4 is the current community-standard CFW — successor to the older PRO and ME firmware lines, with the widest device support and an active wiki. Worth knowing going in: as of this writing its lead maintainer has announced ARK-4 is feature-complete and being succeeded by a rewrite (ARK-5); ARK-4 still installs and runs fine today, but check the releases page before you start in case that's landed by the time you read this.

Step 3: Prepare Your Memory Stick

Use a genuine or well-reviewed third-party Memory Stick Pro Duo (or a Memory Stick Pro Duo adapter with a microSD card, which is far cheaper and easier to source in 2026 than original Sony sticks).
Format it in the PSP itself first (Settings > System Settings > Format Memory Stick) to guarantee the correct filesystem and folder structure before you start copying files.
Back up anything already on the card — the format step wipes it.

Step 4: Install the CFW

Two supported routes — pick whichever fits your setup:

Browser-based (no PC needed): connect your PSP to WiFi (Settings > Network Settings), open its built-in browser, and follow the Online Installer instructions on ARK-4's wiki — it walks the exploit chain and installs ARK-4 in one pass from the PSP itself.
PC-assisted: download the current release from the official ARK-4 GitHub releases page and follow the step-by-step Installation on PSP guide, which covers permanent CFW via cIPL (the currently recommended method) plus folder layout for your Memory Stick.

Either way: only get ARK-4 from the official PSP-Archive/ARK-4 GitHub repo linked above, not a third-party mirror — CFW installers are a common malware vector on file-sharing and blog download sites, and several older PRO-B10-era mirror sites still floating around are exactly that.

After installation, reboot — you should see a new Recovery Menu accessible by holding a shortcut button at boot (usually R trigger), which confirms CFW is installed.

Step 5: Install a Homebrew Launcher

ARK-4 includes its own homebrew menu, but many users also install a dedicated file manager like PSP Filer for easier navigation of the memory stick's folder structure. Homebrew apps and games go in /PSP/GAME/; they'll show up automatically in the XMB after a restart.

Step 6: Set Up Emulators

The PSP's homebrew scene has mature, actively-updated emulators for older systems — this is a huge part of what makes CFW worthwhile beyond just running your own backups:

NES/SNES: FCEU and SNES9x TYL ports run full-speed on PSP hardware.
Game Boy/GBA: gpSP is the standard choice, close to full compatibility.
Genesis/Master System: PicoDrive handles both well.
Arcade (limited): some MAME-derived ports exist but compatibility is spottier given the PSP's CPU ceiling.

Each emulator has its own BIOS requirements — some (like GBA) need a BIOS file you'd dump from hardware you own; others run BIOS-free. Check each emulator's documentation rather than assuming.

Step 7: Load Your Own Game Backups

If you have UMD games, dump them to ISO using a tool like UMDGen run through the CFW's UMD dumper homebrew, from a PSP with a working UMD drive. Copy the resulting ISO to /ISO/ on the memory stick, and launch it from the CFW's Game menu in "ISO Mode." For digital PSN purchases, PS Vita/PSP account tools can extract your own purchased PKGs — a separate process from UMD dumping.

Troubleshooting

Black screen after installing CFW: hold the R trigger at boot to force the Recovery Menu, then check the CFW version installed and re-flash if needed.
Homebrew won't show in XMB: confirm the folder structure — it needs to be exactly /PSP/GAME/[appname]/EBOOT.PBP, not nested deeper or shallower.
ISO won't boot: confirm you're in the correct CFW driver mode (ARK-4 lets you switch between compatibility modes per-game in its config menu) — some ISOs need a specific mode to run correctly.
Battery drains fast after modding: unrelated to CFW itself — check if you left WiFi on, since that's the most common cause on any PSP, modded or not.

Safety Notes

There's no hardware risk from CFW installation on this generation of PSP — worst case is a bad flash that Recovery Mode can fix by reflashing. Unlike some Nintendo consoles, there's no widely-known permanent "brick" exploit involved in this process when following current, non-abandoned installer tools. Always download CFW tools directly from their official GitHub repos, since PSP modding's popularity makes it a target for bundled malware on unofficial download sites.

Wrapping Up

A modded PSP is one of the most capable, pocketable retro emulation devices you can put together for the cost of a used console and a memory stick adapter — and unlike jailbreaking a modern device, the process is stable, well-documented, and unlikely to be patched out from under you since Sony stopped supporting the platform years ago. Between homebrew apps, emulation, and your own game backups, it's a genuinely different maker project from the electronics and fabrication work elsewhere on this site, but it scratches a similar itch: taking hardware apart (functionally, if not physically) and making it do more than it shipped with.