The Pre-Sequel editor throws scarier-looking errors than the BL2 one — LZO decompression failures, EndOfStream exceptions, SHA1 complaints — but don't let the jargon fool you. They trace back to the same handful of causes as Borderlands 2, just with different wording. Find your exact message below and I'll tell you what it actually means. Just getting set up? Start from the Pre-Sequel hub.
- Use the latest bloz_saveedit_1.0.25 from the verified release — in its own folder, not mixed with the BL2 editor.
- Pick the correct platform in the Open dialog (PC for Steam/Epic; PS3 for a PS3 save, etc.).
- Back up the save first, and don't add items from DLC you don't own.
Which error is it?
| Error | Most likely cause |
|---|---|
| LZO decompression failure | Corrupted/incomplete save, or a build too old for the format |
| invalid SHA1 hash | Encrypted console save, or wrong platform picked |
| EndOfStreamException | Truncated / damaged save file |
| Lost progress after adding gear | Unrecognized / un-owned-DLC item made the game reject the save |
"LZO decompression failure"
You'll see this as LZO decompression failure (LookbehindOverrun) or (InputOverrun) — it's logged as issue #38. LZO is the compression the save uses; this error means the editor started unpacking the file and the data didn't line up. In practice that's a corrupted or incomplete save, or an editor build too old to decompress the current format.
Fix: make sure you're on 1.0.25 (not some old mirror build), and that the save downloaded or copied completely. If it's a console save, it likely isn't decrypted yet — see SHA1 below.
"invalid SHA1 hash" / "sha1 load failed"
Same beast as in Borderlands 2 (issue #34 here). The save is an encrypted console save and hasn't been decrypted, so its signature doesn't check out. The cure is identical to the BL2 flow: decrypt with your platform's tool, edit, then re-encrypt.
When you open a PS3 save, set the platform dropdown to PS3, not PC. Picking PC on a console save is a common way to trigger this. The full decrypt → edit → re-encrypt process is in the SHA1 guide — it works the same for TPS.
"EndOfStreamException"
The full text is attempted to read past the end of the stream (issue #42). The editor expected more save file than there actually was — meaning the file is truncated or damaged, usually from an interrupted copy, a bad transfer, or a crash while the game was saving.
There's no editor-side repair for a file that's missing data. Your route back is a backup or a .bak copy — recovering from those is covered in save location & backups.
"I added a gun and lost all my progress"
This is the one that genuinely hurts (issue #27), and it's why I bang on about backups. Add an item the game can't make sense of — gear from a DLC you don't own, or modded parts the vanilla game rejects — and on load the game can throw out the entire save, not just the bad item. People have lost full characters this way.
Back up the save folder before you touch anything, and only add items you can actually obtain in your version of the game. If you already lost the save, your backup (or a .bak) is the only way back.
The universal fix
Strip away the specific wording and every one of these comes down to the same four checks:
Latest build, own folder
bloz_saveedit 1.0.25 from GitHub, kept separate from the BL2 editor.
Right platform
PC for Steam/Epic; the matching console platform for a console save (and decrypt it first).
Intact file
A fully-copied, uncorrupted save — if it's truncated, go to a backup.
Only real items
Nothing from un-owned DLC or impossible modded parts, so the game doesn't reject the save.
Quick answers
Are these different from the BL2 errors?
My PS3 save gives invalid SHA1 hash.
Can I recover a save that throws EndOfStreamException?
Gibbed.BorderlandsOz issues #38 (LZO), #34 (SHA1), #42 (EndOfStream), #36, #27 (lost progress); the Pre-Sequel revision comment threads on PS3 SHA1; and DemonAsylum's TPS walkthrough. Checked June 2026.