<![CDATA[Sick Gaming - Jailbreak]]>

<![CDATA[Sick Gaming - Jailbreak]]> https://sickgaming.net/ Sun, 18 Oct 2026 08:51:46 +0000 MyBB <![CDATA[PS5 PUP Format Reverse Engineered - Breakdown, Tools and 5.50 Analysis]]> https://sickgaming.net/thread-113455.html Tue, 29 Sep 2026 20:04:20 -0200 SickProdigy]]> https://sickgaming.net/thread-113455.html PS5 PUP Format Reverse Engineered - Full Breakdown, Tools & 5.50 Analysis

Introduction

If you have spent any time in the PS5 scene, you have probably come across .PUP files - Sony's firmware update packages. You may have seen them referenced when discussing firmware versions or noticed decrypted versions shared for research purposes. Outside of a few scattered wiki entries and tool source code, very little has been written about what is inside these files, how the format works, and what the components are.

This thread documents the PS5 5.50 Update PUP, including the file format, known component types, inner SELF header structures, and open-source Python tools for extracting and analysing PUP contents.

The psdevwiki PS5 PUP page has also been updated with this information.

What Is a PUP?

PUP stands for PlayStation Update. It is the container Sony uses to deliver firmware updates to the PS5.

Update PUP - Contains only the components that changed since the previous firmware version. It is smaller and installs faster. This is the type normally downloaded from Sony's update page.
Recovery PUP - Contains the complete firmware and is used when the system will not boot normally. It performs a full reinstall.

The PS5 accepts a PUP at or above the currently installed firmware version. Installing an older version requires applicable exploits.

The SLB2 Container Format

PUP Header

0x00 - Magic (4 bytes): Always 53 4C 42 32 ("SLB2")
0x04 - Version (4 bytes): Format version
0x08 - Mode (4 bytes): No description provided
0x0C - Entry Count (4 bytes): Number of components stored in this PUP
0x10 - Header Size (8 bytes): No description provided
0x18 - Data Size (8 bytes): Total PUP file size
0x20 - Padding (16 bytes): No description provided
0x30 - Entry Table (Entry Count x 0x30): One 48-byte record per component

Entry Structure

Each record in the entry table is 48 bytes (0x30).

0x00 - Entry ID (8 bytes): 64-bit type identifier. See Known Entry IDs below.
0x08 - Compressed Size (8 bytes): Size of the data as stored in the PUP
0x10 - Uncompressed Size (8 bytes): Size after decompression; equals Compressed Size if not compressed
0x18 - Data Offset (8 bytes): Byte offset from the start of the PUP to the component data
0x20 - Flags (4 bytes): Bit 0 = compressed, Bit 1 = signed, Bit 2 = encrypted
0x24 - Padding (12 bytes): No description provided

Every PS5 PUP uses an outer container identified by the magic bytes 53 4C 42 32 at offset 0x00 - the ASCII string "SLB2". The existing psdevwiki page documented the magic bytes and a file table at 0x30. Parsing an actual 5.50 Update PUP made it possible to document the full header layout above.

What Is Inside a 5.50 Update PUP

The 5.50 Update PUP contains 95 entries across 14 distinct component types. Many entry IDs appear multiple times in the same PUP. This represents primary and backup copies for redundancy and, in some cases, different builds for different hardware revisions.

For example, the 5.50 Update PUP contains 11 copies of the GPU microcode entry that are byte-for-byte identical and 5 copies of eap_kernel at differing sizes representing different hardware variants.

Files extracted by pup_extract.py are named with the extension .arm64 or .bin. The .arm64 extension is assigned by the extractor's file-type detection heuristic and indicates that the blob passed an ARM64 opcode-density check. This is not a guarantee that the data is plaintext ARM64 code. Encrypted data can pass the same heuristic because of its byte distribution. The .bin extension is assigned to raw binaries, zero-padded blobs, and anything that did not match a known type.

Known Entry IDs

0x0000000000000100 - eap_kernel: Aeolia Application Processor kernel. The OS running on the PS5 security co-processor's ARM cores. Size: ~330-466 MB per copy, 5 copies. Extension: .arm64
0x0000000000000200 - emc_ipl: Aeolia Embedded Controller Initial Program Loader. Contains an embedded x86-64 SELF executable. Size: ~14 MB. Extension: .arm64
0x0000000000000300 - tee: Trusted Execution Environment. Size: ~9 KB (arm64), 8 bytes (bin). Extension: .arm64 / .bin
0x0000000000000400 - bios: System BIOS. Multiple hardware-variant copies. Size: ~365-482 MB per copy, 5 copies. Extension: .arm64
0x0000000000000600 - smf_ipl: System Management Firmware IPL. Size: ~238 KB. Extension: .arm64
0x0000000000001000 - kernel: Main PS5 kernel. Size: ~4 KB (arm64), ~2.2 MB (bin). Extension: .arm64 / .bin
0x0000000000001100 - bootloader0: First-stage bootloader. Size: ~4 KB (arm64), ~45 KB (bin). Extension: .arm64 / .bin
0x0000000000001300 - psp_bl: Security processor bootloader. Size: ~4.8 KB. Extension: .bin
0x0000000000001400 - psp_kernel: Security processor kernel. Size: ~449 KB (arm64), ~5 KB (bin). Extension: .arm64 / .bin
0x0000000000002000 - update_package: Small update blobs. 22 entries in 5.50. Size: 2-8 KB each. Extension: .arm64 / .bin
0x0000000000004000 - version_info: Per-component version tags. 32 entries in 5.50. Size: 1-4 bytes most; one ~4 MB. Extension: .arm64 / .bin
0x0000000000005000 - swu_manifest: Software update manifest. Two instances in 5.50. Size: ~20 KB and ~808 MB. Extension: .arm64
0x0000000000020000 - gpu_ucode: GPU microcode. 11 byte-for-byte identical copies in 5.50. Size: ~594 KB each. Extension: .arm64
0x0000000000030000 - sio_firmware: System I/O controller firmware. Size: ~2.3 MB. Extension: .arm64

The Encryption Situation

This is important to understand. A decrypted PUP (.PUP.dec) has had the outer SLB2 container encryption removed. This gives you readable headers: you can parse the entry table, see component names and sizes, and extract each blob to a separate file.

However, each individual firmware component uses the PS5 SELF format (ET_SCE_EXEC, type 0xFE00) with its own per-segment AES encryption. The SELF container headers are plaintext. ELF structure, segment layouts, load addresses, and entry points are readable, but the actual code and data in each segment are encrypted with keys specific to that binary and stored in Aeolia's secure storage on the hardware.

In practice:

Outer SLB2 - Decrypted. Components can be extracted and identified.
Inner SELF headers - Readable in plaintext. ELF structure, segment counts, and entry points are visible.
Inner SELF segment data - Still AES-encrypted. Per-binary keys from the hardware are required for decryption.

The entropy on every component's segment data is approximately 7.95-7.997 bits per byte, which is indistinguishable from random data and is what would be expected from AES encryption.

Inner SELF Headers

emc_ipl and smf_ipl - Identical SELF

Both emc_ipl and smf_ipl contain the same x86-64 SELF executable. The full 0x4000 bytes of header data are byte-for-byte identical between the two files. The ELF is at different offsets within each outer blob: 0x8D318 in emc_ipl and 0x1C6C8 in smf_ipl. The encrypted wrapper before the SELF differs in size, but the payload inside is the same binary.

Format: PS5 SELF (ET_SCE_EXEC, 0xFE00)
Architecture: x86-64
Entry VA: 0x0000000000400080
Segments: 6
Sections: 0 (stripped)

Segment layout:

Segment 0: Type PT_LOAD; VA 0x400000; File Size 0x9AAFC; Mem Size 0x9AAFC; Flags --X (execute only)
Segment 1: Type PT_LOAD; VA 0x49C000; File Size 0x92E08; Mem Size 0x92E08; Flags R-- (read only)
Segment 2: Type PT_LOAD; VA 0x530000; File Size 0x9E6D54; Mem Size 0xA9EF30; Flags RW-
Segment 3: Type SCE_RELRO; VA 0x52EDA8; File Size 0x60; Mem Size 0x60; Flags R--
Segment 4: Type PT_TLS; VA 0x530000; File Size 0x10; Mem Size 0x46; Flags R--
Segment 5: Type GNU_STACK; VA 0x529FB4; File Size 0x4DF4; Mem Size 0x4DF4; Flags R--

Points of note:

Segment 0 is execute-only with no read permission. This is an intentional hardening measure; the code cannot read its own pages.
Segment 2 has MemSz 0xA9EF30 versus FileSz 0x9E6D54. The difference of 0xB81DC bytes, approximately 736 KB, is uninitialised BSS that is zeroed at load time rather than stored in the file.
The TLS segment is 16 bytes on disk and expands to 70 bytes in memory.
The ELF has zero section headers. Symbol and debug information has been fully stripped.

Encrypted Segment Info Table

The bytes immediately before the ELF header in emc_ipl contain a structured table describing encrypted segments. Three entries were recoverable from the plaintext region.

Entry 10: File Offset 0x110006; Encrypted Size 0x6A0; Decrypted Size 0x4E0
Entry 12: File Offset 0x310006; Encrypted Size 0x9B680; Decrypted Size 0x4A0
Entry 14: File Offset 0x510006; Encrypted Size 0x12E930; Decrypted Size 0x4F40

The offsets all end in 0x0006, suggesting a consistent alignment or header prefix on each encrypted block.

The compression ratios are extreme. Entry 12 has an encrypted size of approximately 630 KB and decrypts to only about 1.2 KB. Entry 14 is approximately 1.2 MB and decrypts to about 20 KB. These figures suggest deliberate padding to obscure the true size of the decrypted contents, which is a known anti-analysis technique.

psp_kernel and sio_firmware

No ELF was found in either psp_kernel or sio_firmware. Both begin with opaque encrypted data and contain no recognisable container signatures: no SLB2, SELF, BLS, or SEAD. These components either use a format specific to their respective processors or are fully opaque encrypted blobs with no plaintext structural metadata.

PS5 Security Architecture - Background

The PS5's main game CPU is an AMD Zen 2 x86-64 chip, but it operates under the control of a separate security co-processor called Aeolia. Aeolia is a Sony-designed SoC containing ARM Cortex-A53 cores running a dedicated operating system independently of the main CPU.

Aeolia is responsible for:

Enforcing hypervisor memory protections on the main CPU through AMD SVM nested page tables
Authenticating SELF executables before they are allowed to run
Managing hardware security keys
Handling the secure boot chain

The eap_kernel entries in the PUP are the operating system running on those A53 cores. emc_ipl is the Aeolia embedded controller firmware. The bios entries boot the main x86-64 system. All of these are encrypted with Aeolia's on-chip keys.

The firmware installation phases listed in the update log - emc_salina_c0.bls, titania.bls, and eap_kbl.bin - are early boot-stage components written to flash before the main system starts. The .bls files are Aeolia bootloader stages. Titania is the internal codename for the PS5's Aeolia chip revision.

Update Index Order

This is the firmware flashing sequence observed during a PS5 firmware update and documented from installation logs. Numbers in parentheses are the internal phase indices.

Code:
[INFO] writing system firmware phase 1  (18)   usb_pdc_salina_c0.bls
[INFO] writing system firmware phase 2  (16)   emc_salina_c0.bls
[INFO] writing system firmware phase 3  (11)   titania.bls
[INFO] writing system firmware phase 4  (14)   eap_kbl.bin
[INFO] writing system firmware phase 5  (4)    mbr.bin
[INFO] writing system firmware phase 6  (259)  oberon_sec_ldr_c0.bin
[INFO] writing system firmware phase 7  (5)    kernel.bin
--- reboots here ---
[INFO] writing system firmware phase 8  (513)  wlanbt.bin
[INFO] writing system firmware phase 9  (515)  ssd0.system_b
[INFO] writing system firmware phase 10 (516)  ssd0.system_ex_b
[INFO] writing system firmware phase 11 (519)  ssd0.preinst
--- mounts system: nmount /dev/ssd0.system_b to /update/mnt/system ---
[INFO] writing system firmware phase 12 (2000) bluray.bin

Phases 8, 9, 10, and 12 cannot be decrypted with current public tools.

The Tools

Two Python scripts can be downloaded below. Both require Python 3.8 or above. The capstone library is an optional dependency for the analyser. Install it with:

Code:
pip install capstone

pup_extract.py

Parses the SLB2 header, lists all entries with their IDs, names, sizes, offsets, and detected file types, then extracts every component to an extracted/ subfolder. It also outputs a full entries.csv manifest and pup_header_hex.txt for manual inspection.

Place the script in the same folder as your PS5UPDATE1.PUP.dec file and run:

Code:
python pup_extract.py

Output:

Code:
extracted/          All components, named by index and type
entries.csv         Full manifest with offsets, sizes, SHA-256 partial hashes, and detected file types
pup_header_hex.txt  First 8 KB of the PUP header as a hex dump

The script has three fallback strategies for non-standard header layouts:

Tries multiple known header offset variants.
Brute-force scans for known entry IDs if parsing fails.
Falls back to fixed 16 MB chunk dumps so nothing is lost.

analyse_extracted.py

Scans the extracted/ folder produced by pup_extract.py, scores each file for ARM64 code density, checks known reference offsets, and attempts to identify firmware structure. It is designed for hardware-decrypted firmware dumps.

Run it from the same folder:

Code:
python analyse_extracted.py

The script outputs analysis_report.txt with per-file findings.

What This Adds to Community Knowledge

Before this research, the psdevwiki PS5 PUP page documented only the SLB2 magic bytes and a firmware installation log. This thread adds:

The full header structure with all field offsets and sizes
The complete entry record format with all six fields documented
Fourteen known Entry IDs with names, descriptions, and sizes observed in 5.50
An explanation of why duplicate entries exist and what they represent
Documentation of the two-layer encryption model: outer SLB2 and inner SELF
Inner SELF ELF headers and segment layouts
Notes on emc_ipl and smf_ipl containing identical embedded x86-64 SELF binaries
The encrypted segment information table structure documented from emc_ipl
Notes on psp_kernel and sio_firmware using unknown or fully opaque container formats
Two open-source Python tools for extraction and analysis

If you have additional entry IDs, sizes from other firmware versions, or corrections to anything here, post them below.

Downloads: Mega + Mirror

]]> PS5 PUP Format Reverse Engineered - Full Breakdown, Tools & 5.50 Analysis

What Is a PUP?

PUP stands for PlayStation Update. It is the container Sony uses to deliver firmware updates to the PS5.

Update PUP - Contains only the components that changed since the previous firmware version. It is smaller and installs faster. This is the type normally downloaded from Sony's update page.
Recovery PUP - Contains the complete firmware and is used when the system will not boot normally. It performs a full reinstall.

The PS5 accepts a PUP at or above the currently installed firmware version. Installing an older version requires applicable exploits.

The SLB2 Container Format

PUP Header

0x00 - Magic (4 bytes): Always 53 4C 42 32 ("SLB2")
0x04 - Version (4 bytes): Format version
0x08 - Mode (4 bytes): No description provided
0x0C - Entry Count (4 bytes): Number of components stored in this PUP
0x10 - Header Size (8 bytes): No description provided
0x18 - Data Size (8 bytes): Total PUP file size
0x20 - Padding (16 bytes): No description provided
0x30 - Entry Table (Entry Count x 0x30): One 48-byte record per component

Entry Structure

Each record in the entry table is 48 bytes (0x30).

0x00 - Entry ID (8 bytes): 64-bit type identifier. See Known Entry IDs below.
0x08 - Compressed Size (8 bytes): Size of the data as stored in the PUP
0x10 - Uncompressed Size (8 bytes): Size after decompression; equals Compressed Size if not compressed
0x18 - Data Offset (8 bytes): Byte offset from the start of the PUP to the component data
0x20 - Flags (4 bytes): Bit 0 = compressed, Bit 1 = signed, Bit 2 = encrypted
0x24 - Padding (12 bytes): No description provided

0x0000000000000100 - eap_kernel: Aeolia Application Processor kernel. The OS running on the PS5 security co-processor's ARM cores. Size: ~330-466 MB per copy, 5 copies. Extension: .arm64
0x0000000000000200 - emc_ipl: Aeolia Embedded Controller Initial Program Loader. Contains an embedded x86-64 SELF executable. Size: ~14 MB. Extension: .arm64
0x0000000000000300 - tee: Trusted Execution Environment. Size: ~9 KB (arm64), 8 bytes (bin). Extension: .arm64 / .bin
0x0000000000000400 - bios: System BIOS. Multiple hardware-variant copies. Size: ~365-482 MB per copy, 5 copies. Extension: .arm64
0x0000000000000600 - smf_ipl: System Management Firmware IPL. Size: ~238 KB. Extension: .arm64
0x0000000000001000 - kernel: Main PS5 kernel. Size: ~4 KB (arm64), ~2.2 MB (bin). Extension: .arm64 / .bin
0x0000000000001100 - bootloader0: First-stage bootloader. Size: ~4 KB (arm64), ~45 KB (bin). Extension: .arm64 / .bin
0x0000000000001300 - psp_bl: Security processor bootloader. Size: ~4.8 KB. Extension: .bin
0x0000000000001400 - psp_kernel: Security processor kernel. Size: ~449 KB (arm64), ~5 KB (bin). Extension: .arm64 / .bin
0x0000000000002000 - update_package: Small update blobs. 22 entries in 5.50. Size: 2-8 KB each. Extension: .arm64 / .bin
0x0000000000004000 - version_info: Per-component version tags. 32 entries in 5.50. Size: 1-4 bytes most; one ~4 MB. Extension: .arm64 / .bin
0x0000000000005000 - swu_manifest: Software update manifest. Two instances in 5.50. Size: ~20 KB and ~808 MB. Extension: .arm64
0x0000000000020000 - gpu_ucode: GPU microcode. 11 byte-for-byte identical copies in 5.50. Size: ~594 KB each. Extension: .arm64
0x0000000000030000 - sio_firmware: System I/O controller firmware. Size: ~2.3 MB. Extension: .arm64

Outer SLB2 - Decrypted. Components can be extracted and identified.
Inner SELF headers - Readable in plaintext. ELF structure, segment counts, and entry points are visible.
Inner SELF segment data - Still AES-encrypted. Per-binary keys from the hardware are required for decryption.

The entropy on every component's segment data is approximately 7.95-7.997 bits per byte, which is indistinguishable from random data and is what would be expected from AES encryption.

Format: PS5 SELF (ET_SCE_EXEC, 0xFE00)
Architecture: x86-64
Entry VA: 0x0000000000400080
Segments: 6
Sections: 0 (stripped)

Segment layout:

Segment 0: Type PT_LOAD; VA 0x400000; File Size 0x9AAFC; Mem Size 0x9AAFC; Flags --X (execute only)
Segment 1: Type PT_LOAD; VA 0x49C000; File Size 0x92E08; Mem Size 0x92E08; Flags R-- (read only)
Segment 2: Type PT_LOAD; VA 0x530000; File Size 0x9E6D54; Mem Size 0xA9EF30; Flags RW-
Segment 3: Type SCE_RELRO; VA 0x52EDA8; File Size 0x60; Mem Size 0x60; Flags R--
Segment 4: Type PT_TLS; VA 0x530000; File Size 0x10; Mem Size 0x46; Flags R--
Segment 5: Type GNU_STACK; VA 0x529FB4; File Size 0x4DF4; Mem Size 0x4DF4; Flags R--

Points of note:

Segment 0 is execute-only with no read permission. This is an intentional hardening measure; the code cannot read its own pages.
Segment 2 has MemSz 0xA9EF30 versus FileSz 0x9E6D54. The difference of 0xB81DC bytes, approximately 736 KB, is uninitialised BSS that is zeroed at load time rather than stored in the file.
The TLS segment is 16 bytes on disk and expands to 70 bytes in memory.
The ELF has zero section headers. Symbol and debug information has been fully stripped.

Entry 10: File Offset 0x110006; Encrypted Size 0x6A0; Decrypted Size 0x4E0
Entry 12: File Offset 0x310006; Encrypted Size 0x9B680; Decrypted Size 0x4A0
Entry 14: File Offset 0x510006; Encrypted Size 0x12E930; Decrypted Size 0x4F40

Enforcing hypervisor memory protections on the main CPU through AMD SVM nested page tables
Authenticating SELF executables before they are allowed to run
Managing hardware security keys
Handling the secure boot chain

Update Index Order

This is the firmware flashing sequence observed during a PS5 firmware update and documented from installation logs. Numbers in parentheses are the internal phase indices.

Code:
[INFO] writing system firmware phase 1  (18)   usb_pdc_salina_c0.bls
[INFO] writing system firmware phase 2  (16)   emc_salina_c0.bls
[INFO] writing system firmware phase 3  (11)   titania.bls
[INFO] writing system firmware phase 4  (14)   eap_kbl.bin
[INFO] writing system firmware phase 5  (4)    mbr.bin
[INFO] writing system firmware phase 6  (259)  oberon_sec_ldr_c0.bin
[INFO] writing system firmware phase 7  (5)    kernel.bin
--- reboots here ---
[INFO] writing system firmware phase 8  (513)  wlanbt.bin
[INFO] writing system firmware phase 9  (515)  ssd0.system_b
[INFO] writing system firmware phase 10 (516)  ssd0.system_ex_b
[INFO] writing system firmware phase 11 (519)  ssd0.preinst
--- mounts system: nmount /dev/ssd0.system_b to /update/mnt/system ---
[INFO] writing system firmware phase 12 (2000) bluray.bin

Phases 8, 9, 10, and 12 cannot be decrypted with current public tools.

The Tools

Two Python scripts can be downloaded below. Both require Python 3.8 or above. The capstone library is an optional dependency for the analyser. Install it with:

Code:
pip install capstone

Code:
python pup_extract.py

Output:

Code:
extracted/          All components, named by index and type
entries.csv         Full manifest with offsets, sizes, SHA-256 partial hashes, and detected file types
pup_header_hex.txt  First 8 KB of the PUP header as a hex dump

The script has three fallback strategies for non-standard header layouts:

Tries multiple known header offset variants.
Brute-force scans for known entry IDs if parsing fails.
Falls back to fixed 16 MB chunk dumps so nothing is lost.

Code:
python analyse_extracted.py

The script outputs analysis_report.txt with per-file findings.

What This Adds to Community Knowledge

Before this research, the psdevwiki PS5 PUP page documented only the SLB2 magic bytes and a firmware installation log. This thread adds:

The full header structure with all field offsets and sizes
The complete entry record format with all six fields documented
Fourteen known Entry IDs with names, descriptions, and sizes observed in 5.50
An explanation of why duplicate entries exist and what they represent
Documentation of the two-layer encryption model: outer SLB2 and inner SELF
Inner SELF ELF headers and segment layouts
Notes on emc_ipl and smf_ipl containing identical embedded x86-64 SELF binaries
The encrypted segment information table structure documented from emc_ipl
Notes on psp_kernel and sio_firmware using unknown or fully opaque container formats
Two open-source Python tools for extraction and analysis

If you have additional entry IDs, sizes from other firmware versions, or corrections to anything here, post them below.

Downloads: Mega + Mirror

]]> <![CDATA[Porkfolio v1.0.6 PS5 Utility (Game Library, Backporks, FTP, Cheats, Saves, +more)]]> https://sickgaming.net/thread-113453.html Tue, 29 Sep 2026 19:42:59 -0200 SickProdigy]]> https://sickgaming.net/thread-113453.html Porkfolio
All-in-One PS5 Utility for managing your PS5 game library, local backups, backporks, FTP transfers, media, cheats, avatars, save files, system streaming, jailbreak payloads, and more.

Please expect bugs and be ready to report them. I could not give the app the stress testing it needs due to low storage space

Requirements

Windows
PS5 with FTP enabled — requires a jailbreak with an FTP server payload running
USB capture card — only required for the System View streaming feature

First-Time Setup

Settings → FTP Connection — Enter your PS5's IP address and port (default 2121, or check what your FTP payload uses). You can list multiple ports to try in order.
Settings → Game Source Folders — Point to one or more local directories where your game backup folders live (e.g. G:\PS5\Games).
Settings → Backpork Folders — Register any firmware-labeled folders (e.g. 5.xx, 6.xx) containing backpork patches.
Settings → Remote Game Paths — Enter the path on your PS5 where games are installed (e.g. /mnt/sandbox/pfsmnt/).
Settings → Media — Set a local save folder for screenshots/clips and optionally add a Discord webhook URL.
Dashboard → Connect — Connect to your PS5.
Dashboard → Scan PS5 — Discovers all installed games and kicks off metadata fetching.

Features

Dashboard
The landing page with stats and quick actions.

Stat cards: Total Games, Installed, Backed Up, Backup Files
FTP Quick Connect: One-click connect button with connection status indicator
Pinnable widget cards: Pin PSNotify, Payload, xAvatar, or other tools to the dashboard
Recent activity feed

Games
Scans your PS5's configured game path and builds a full library from PPSA#####-app / CUSA#####-app folders. Metadata pulled from ProsperoPatches.com.

Filter by installed / backed up / not backed up / firmware label
Sort by title, game ID, size, or date
Search by title or game ID
Per-game detail modal with tabs: Info, Updates, DLC, Regions, Manage
Info — title, publisher, content ID, region, version, icon, banner
Updates — all available patches with firmware requirements and changelogs
DLC — full DLC list from ProsperoPatches.com
Regions — alternate regional releases
Manage — upload/download this game, link local backups, set FTP path, hash verification

Backups
Tracks local game backup folders detected in your configured source directories.

Auto-detects any folder named PPSA#####* or CUSA#####* on scan
Recursive size calculation per backup
Filterable by region, searchable by title or ID
Per-backup badges: local size, backpork count, available updates, DLC count, install status
Hash the backup file or entire folder tree with one click

Backporks
Manages firmware-specific game patches for your installed games.

Register one or more firmware root folders — Porkfolio auto-detects all firmware subfolders inside (e.g. 4.xx, 5.xx, 6.xx)
Per-firmware game lists filtered by what you have locally
Pork to PS5 — uploads the correct game subfolder to the PS5's configured remote path via FTP
Available as a post-install step in the Install modal (applies the backpork on top of a fresh game install)

Transfer Manager
All FTP operations run through a unified job queue with real-time progress.

Job types: upload folder, upload file, download file, download folder, pork (install game)
Concurrent transfers: 1–15 simultaneous FTP connections (configurable)
Per-job progress: file counter, transfer speed, bytes transferred, percent complete
Pause All / Resume All / Cancel individual jobs / Clear completed
Nav badge shows active + queued job count across all pages
PS5 toast notifications at job start, 25/50/75% milestones, retry warnings, and completion
Automatic retry: Files that fail are retried up to 3 times before being skipped
Extra FTP connections created automatically for concurrent downloads (doesn't block the primary connection)

Hash Verification
Verify the integrity of your local backups against a community database.

SHA-256 hash any local backup — single file or entire folder tree with streaming progress
Results stored in the local database
Compared against a bundled community game_hashes.json database
Badge system: ✓ Verified (community match), ⧭ Hashed (local only), ⚠ Hash Fail (mismatch)
Bulk hash all games at once with progress tracking
Export your own hashes to contribute back to the community

Media
Browse, download, and share screenshots and video clips stored on your PS5.

Scans PS5 media directories via FTP (/user/av_contents/photo/ and /user/av_contents/video/)
Filterable by type (screenshots / video clips), searchable by game ID or filename
Sort by date captured, size, or game
Inline screenshot previews and video clip thumbnails (extracted via ffmpeg)
Batch clip thumbnail fetcher — download and extract thumbnails for all clips at once
Download to a configured local save path (skips re-download if file already exists; handles OneDrive locking gracefully)
Open folder button to jump to the local media directory in Explorer
Discord Integration: Screenshots attached directly as image embeds; video clips uploaded to catbox.moe and posted as embed link
Per-step PS5 notifications (download/upload/done/error — each independently toggleable)

System View
Live-stream your PS5's display through a USB capture card connected to your PC.

Connects via getUserMedia() to any capture card visible to the OS
Selectable video device, audio device, and stream resolution/FPS
GIF export (captures frames and encodes to animated GIF)
Video clip export (WebM recording)
Mute/unmute audio independently of the video feed
Popout to a separate floating window
Fullscreen mode
Configurable hotkeys (mute, record GIF, record video, toggle fullscreen, popout)
Auto-load on launch — boots straight into System View and starts the stream automatically
No-signal splash screen when no capture device is detected

Cheats
Browse and install PS5 cheat databases from HEN-Cheats-Collection.

Fetches cheat index from GitHub with progress tracking
Search by game title or ID
Shows file count per game with game icons from ProsperoPatches.com
Download all cheats or by individual game
Install cheat files directly to the PS5 via FTP (/data/etaHEN/cheats/)
Local caching of downloaded cheat files
Unmatched section highlights cheat files for games not yet in the app's database

xAvatar
Convert images to the PS5's proprietary .xavatar format and upload them.

Drag-and-drop, file browse, or clipboard paste to load any image
DXT5 compression to multiple required sizes (440px, 260px, 128px, 64px)
Generates proper PS5 avatar JSON metadata
Preview the result before saving or uploading
Save to file — download the .xavatar to your PC
Send to PS5 — uploads directly to /data/AVATARS/ via FTP
Extract PNG — reverse-convert an existing .xavatar back to PNG
Avatar library browser shows all .xavatar files currently on your PS5

Local Save Manager
Decrypt, resign, and manage PS5 save files on your PC.

Connect to PS5 save manager payload
Download encrypted saves from PS5
Decrypt saves locally
Resign saves with a different Account ID
Re-encrypt and upload back to PS5
Create new empty PFS save files
Extract save file icons
Dump saves from USB storage

GarlicSaves
Integration with the Garlic-worker save management system.

Auto-download garlic-worker ELF from GitHub
Send worker payload via TCP (port 9021)
Upload config.ini to PS5 /data/garlic/
Save backup and restore functionality
Step-by-step progress tracking

Voidshell
Requires the voidshell payload to be running!

Browse /mnt/usb0, /data, and other PS5 paths
File and folder operations: copy, delete, rename
Real-time storage statistics
Search and filtering
Thumbnail previews
Favorites system
Configurable TCP port (default 7007)

PS Notify
Send notifications directly to your PS5's notification system over UDP.

Manual send with message + sub-message fields
Test button to verify connectivity
Full notification history log (per session) with success/failure state
Automatically used throughout the app for transfer events, conversion milestones, media operations, and errors
Configurable PS5 IP, port (default 6969), and timeout

Database Explorer
Built-in database explorer and query runner.

Browse raw games, backups, and hashes tables
Execute arbitrary SQL queries with result display
Export full database as a SQL dump
Export any table as CSV
Clear database or clear hashes only

Jailbreak Tools
Payload Manager

Multiple GitHub payload sources (user-configurable, enable/disable toggle)
Auto-check for updates from GitHub releases
SHA-256 hash verification for payload files
Local and remote payload management
One-click send-to-PS5 via FTP
Configurable local storage and remote paths

Autoloader Snapshots

Take snapshots of the current autoloader state with custom labels
Restore any saved snapshot
Export snapshots as .porkchop files (JSON bundle with base64-encoded payloads)
Import snapshots from .porkchop files or ZIP archives
Drag-and-drop payload reordering in the sequence editor
Configurable delay presets between payloads (250ms–5s)

Game Conversion (Windows only)
Convert game backups between formats for installation.

Raw Dumps (PFS) — direct FTP folder upload, no conversion needed
FFPKG — convert via UFS2Tool.exe (requires Windows + Admin)
ExFAT — create mountable exFAT image via PowerShell (requires Windows + Admin)
Conversion job queue with progress tracking
Optional auto-upload to PS5 after conversion
Optional delete source after successful upload
PS5 notifications at each conversion stage

Multi-Language (i18n)

Language switcher in Settings
JSON-based translation files in build/lang/
Ships with English and French
Export base language file for community translation contributions
All navigation, page headers, and settings labels support i18n

Settings Overview

FTP Connection — PS5 IP, port list, username, password, auto-connect on launch
Game Source Folders — Multiple local backup directory paths
Remote Game Paths — PS5 game installation paths for scanning
Conversion — Output mode (PFS/FFPKG/ExFAT), tool paths, output/temp dirs, auto-upload, auto-delete
Payload — Local payload folder, remote PS5 path
Cheats — Remote cheats path on PS5
Media — Local save path, Discord webhook URL, per-step PS5 notification toggles
PS Notify — PS5 IP, port, timeout
System View — Hotkey bindings (mute, record GIF, record video, fullscreen, popout), auto-launch
Appearance — Accent color (hex), time format (12h/24h), language
Voidshell —

Known Limitations

Game Conversion — FFPKG and ExFAT modes require Windows and Administrator privileges. Raw PFS dump mode works on all platforms.
Community Hash DB — The bundled game_hashes.json grows with community contributions via the hash export feature. Initial coverage is sparse.
System View — Requires a USB capture card physically connected between your PS5 and PC. Resolution and latency depend on the capture card's capabilities.
Zeroed WebM clips — Some PS5 video recordings may have valid container headers but zeroed content — this is a known issue with zftpd. Use etaHEN or a different FTP plugin to fetch your video clips.
Voidshell & Save Manager — Require their respective payloads running on the PS5 to function.

Download:

Enjoy!

Please note: This app is closed source. This thread is the only intended spot for releases and ongoing bug reports. Please do not share this application directly — link back to this thread instead. Thank you.]]> Porkfolio
All-in-One PS5 Utility for managing your PS5 game library, local backups, backporks, FTP transfers, media, cheats, avatars, save files, system streaming, jailbreak payloads, and more.

Please expect bugs and be ready to report them. I could not give the app the stress testing it needs due to low storage space

Requirements

Windows
PS5 with FTP enabled — requires a jailbreak with an FTP server payload running
USB capture card — only required for the System View streaming feature

First-Time Setup

Settings → FTP Connection — Enter your PS5's IP address and port (default 2121, or check what your FTP payload uses). You can list multiple ports to try in order.
Settings → Game Source Folders — Point to one or more local directories where your game backup folders live (e.g. G:\PS5\Games).
Settings → Backpork Folders — Register any firmware-labeled folders (e.g. 5.xx, 6.xx) containing backpork patches.
Settings → Remote Game Paths — Enter the path on your PS5 where games are installed (e.g. /mnt/sandbox/pfsmnt/).
Settings → Media — Set a local save folder for screenshots/clips and optionally add a Discord webhook URL.
Dashboard → Connect — Connect to your PS5.
Dashboard → Scan PS5 — Discovers all installed games and kicks off metadata fetching.

Features

Dashboard
The landing page with stats and quick actions.

Stat cards: Total Games, Installed, Backed Up, Backup Files
FTP Quick Connect: One-click connect button with connection status indicator
Pinnable widget cards: Pin PSNotify, Payload, xAvatar, or other tools to the dashboard
Recent activity feed

Games
Scans your PS5's configured game path and builds a full library from PPSA#####-app / CUSA#####-app folders. Metadata pulled from ProsperoPatches.com.

Filter by installed / backed up / not backed up / firmware label
Sort by title, game ID, size, or date
Search by title or game ID
Per-game detail modal with tabs: Info, Updates, DLC, Regions, Manage
Info — title, publisher, content ID, region, version, icon, banner
Updates — all available patches with firmware requirements and changelogs
DLC — full DLC list from ProsperoPatches.com
Regions — alternate regional releases
Manage — upload/download this game, link local backups, set FTP path, hash verification

Backups
Tracks local game backup folders detected in your configured source directories.

Auto-detects any folder named PPSA#####* or CUSA#####* on scan
Recursive size calculation per backup
Filterable by region, searchable by title or ID
Per-backup badges: local size, backpork count, available updates, DLC count, install status
Hash the backup file or entire folder tree with one click

Backporks
Manages firmware-specific game patches for your installed games.

Register one or more firmware root folders — Porkfolio auto-detects all firmware subfolders inside (e.g. 4.xx, 5.xx, 6.xx)
Per-firmware game lists filtered by what you have locally
Pork to PS5 — uploads the correct game subfolder to the PS5's configured remote path via FTP
Available as a post-install step in the Install modal (applies the backpork on top of a fresh game install)

Transfer Manager
All FTP operations run through a unified job queue with real-time progress.

Job types: upload folder, upload file, download file, download folder, pork (install game)
Concurrent transfers: 1–15 simultaneous FTP connections (configurable)
Per-job progress: file counter, transfer speed, bytes transferred, percent complete
Pause All / Resume All / Cancel individual jobs / Clear completed
Nav badge shows active + queued job count across all pages
PS5 toast notifications at job start, 25/50/75% milestones, retry warnings, and completion
Automatic retry: Files that fail are retried up to 3 times before being skipped
Extra FTP connections created automatically for concurrent downloads (doesn't block the primary connection)

Hash Verification
Verify the integrity of your local backups against a community database.

SHA-256 hash any local backup — single file or entire folder tree with streaming progress
Results stored in the local database
Compared against a bundled community game_hashes.json database
Badge system: ✓ Verified (community match), ⧭ Hashed (local only), ⚠ Hash Fail (mismatch)
Bulk hash all games at once with progress tracking
Export your own hashes to contribute back to the community

Media
Browse, download, and share screenshots and video clips stored on your PS5.

Scans PS5 media directories via FTP (/user/av_contents/photo/ and /user/av_contents/video/)
Filterable by type (screenshots / video clips), searchable by game ID or filename
Sort by date captured, size, or game
Inline screenshot previews and video clip thumbnails (extracted via ffmpeg)
Batch clip thumbnail fetcher — download and extract thumbnails for all clips at once
Download to a configured local save path (skips re-download if file already exists; handles OneDrive locking gracefully)
Open folder button to jump to the local media directory in Explorer
Discord Integration: Screenshots attached directly as image embeds; video clips uploaded to catbox.moe and posted as embed link
Per-step PS5 notifications (download/upload/done/error — each independently toggleable)

System View
Live-stream your PS5's display through a USB capture card connected to your PC.

Connects via getUserMedia() to any capture card visible to the OS
Selectable video device, audio device, and stream resolution/FPS
GIF export (captures frames and encodes to animated GIF)
Video clip export (WebM recording)
Mute/unmute audio independently of the video feed
Popout to a separate floating window
Fullscreen mode
Configurable hotkeys (mute, record GIF, record video, toggle fullscreen, popout)
Auto-load on launch — boots straight into System View and starts the stream automatically
No-signal splash screen when no capture device is detected

Cheats
Browse and install PS5 cheat databases from HEN-Cheats-Collection.

Fetches cheat index from GitHub with progress tracking
Search by game title or ID
Shows file count per game with game icons from ProsperoPatches.com
Download all cheats or by individual game
Install cheat files directly to the PS5 via FTP (/data/etaHEN/cheats/)
Local caching of downloaded cheat files
Unmatched section highlights cheat files for games not yet in the app's database

xAvatar
Convert images to the PS5's proprietary .xavatar format and upload them.

Drag-and-drop, file browse, or clipboard paste to load any image
DXT5 compression to multiple required sizes (440px, 260px, 128px, 64px)
Generates proper PS5 avatar JSON metadata
Preview the result before saving or uploading
Save to file — download the .xavatar to your PC
Send to PS5 — uploads directly to /data/AVATARS/ via FTP
Extract PNG — reverse-convert an existing .xavatar back to PNG
Avatar library browser shows all .xavatar files currently on your PS5

Local Save Manager
Decrypt, resign, and manage PS5 save files on your PC.

Connect to PS5 save manager payload
Download encrypted saves from PS5
Decrypt saves locally
Resign saves with a different Account ID
Re-encrypt and upload back to PS5
Create new empty PFS save files
Extract save file icons
Dump saves from USB storage

GarlicSaves
Integration with the Garlic-worker save management system.

Auto-download garlic-worker ELF from GitHub
Send worker payload via TCP (port 9021)
Upload config.ini to PS5 /data/garlic/
Save backup and restore functionality
Step-by-step progress tracking

Voidshell
Requires the voidshell payload to be running!

Browse /mnt/usb0, /data, and other PS5 paths
File and folder operations: copy, delete, rename
Real-time storage statistics
Search and filtering
Thumbnail previews
Favorites system
Configurable TCP port (default 7007)

PS Notify
Send notifications directly to your PS5's notification system over UDP.

Manual send with message + sub-message fields
Test button to verify connectivity
Full notification history log (per session) with success/failure state
Automatically used throughout the app for transfer events, conversion milestones, media operations, and errors
Configurable PS5 IP, port (default 6969), and timeout

Database Explorer
Built-in database explorer and query runner.

Browse raw games, backups, and hashes tables
Execute arbitrary SQL queries with result display
Export full database as a SQL dump
Export any table as CSV
Clear database or clear hashes only

Jailbreak Tools
Payload Manager

Multiple GitHub payload sources (user-configurable, enable/disable toggle)
Auto-check for updates from GitHub releases
SHA-256 hash verification for payload files
Local and remote payload management
One-click send-to-PS5 via FTP
Configurable local storage and remote paths

Autoloader Snapshots

Take snapshots of the current autoloader state with custom labels
Restore any saved snapshot
Export snapshots as .porkchop files (JSON bundle with base64-encoded payloads)
Import snapshots from .porkchop files or ZIP archives
Drag-and-drop payload reordering in the sequence editor
Configurable delay presets between payloads (250ms–5s)

Game Conversion (Windows only)
Convert game backups between formats for installation.

Raw Dumps (PFS) — direct FTP folder upload, no conversion needed
FFPKG — convert via UFS2Tool.exe (requires Windows + Admin)
ExFAT — create mountable exFAT image via PowerShell (requires Windows + Admin)
Conversion job queue with progress tracking
Optional auto-upload to PS5 after conversion
Optional delete source after successful upload
PS5 notifications at each conversion stage

Multi-Language (i18n)

Language switcher in Settings
JSON-based translation files in build/lang/
Ships with English and French
Export base language file for community translation contributions
All navigation, page headers, and settings labels support i18n

Settings Overview

FTP Connection — PS5 IP, port list, username, password, auto-connect on launch
Game Source Folders — Multiple local backup directory paths
Remote Game Paths — PS5 game installation paths for scanning
Conversion — Output mode (PFS/FFPKG/ExFAT), tool paths, output/temp dirs, auto-upload, auto-delete
Payload — Local payload folder, remote PS5 path
Cheats — Remote cheats path on PS5
Media — Local save path, Discord webhook URL, per-step PS5 notification toggles
PS Notify — PS5 IP, port, timeout
System View — Hotkey bindings (mute, record GIF, record video, fullscreen, popout), auto-launch
Appearance — Accent color (hex), time format (12h/24h), language
Voidshell —

Known Limitations

Game Conversion — FFPKG and ExFAT modes require Windows and Administrator privileges. Raw PFS dump mode works on all platforms.
Community Hash DB — The bundled game_hashes.json grows with community contributions via the hash export feature. Initial coverage is sparse.
System View — Requires a USB capture card physically connected between your PS5 and PC. Resolution and latency depend on the capture card's capabilities.
Zeroed WebM clips — Some PS5 video recordings may have valid container headers but zeroed content — this is a known issue with zftpd. Use etaHEN or a different FTP plugin to fetch your video clips.
Voidshell & Save Manager — Require their respective payloads running on the PS5 to function.

Download:

Enjoy!

Please note: This app is closed source. This thread is the only intended spot for releases and ongoing bug reports. Please do not share this application directly — link back to this thread instead. Thank you.]]> <![CDATA[How to jailbreak PS5 FW 7.00 through 13.60 with Relapse]]> https://sickgaming.net/thread-113452.html Tue, 29 Sep 2026 19:35:28 -0200 SickProdigy]]> https://sickgaming.net/thread-113452.html How to jailbreak PS5 FW 7.00 through 13.60 with Relapse

1.
[*]In your PS5 network settings, set Primary DNS to 45.56.67.85 Settings > Network > Setup Internet Connection > Advanced Settings

[Image: 1790671084061-png.20289]

2. Open Setting -> Guide & Tips, Health and Safety, and Other Information -> Under Guide and Tips -> click on User's Guide
[Image: 1790671095600-png.20291]

3. Scroll bottom of the page and type this
tiny.cc/jx9b101 then click go

[Image: 1790671102519-png.20292]

After a successful run, the ELF loader listens on port 9021. After elfldr starts on port 9021, you can press R2 to send kstuff.elf, shadowmountplus.elf, then etaHEN.elf

A success should look something like this
[Image: 1790671109561-png.20293]

Enjoy!]]> How to jailbreak PS5 FW 7.00 through 13.60 with Relapse

1.
[*]In your PS5 network settings, set Primary DNS to 45.56.67.85 Settings > Network > Setup Internet Connection > Advanced Settings

[Image: 1790671084061-png.20289]

2. Open Setting -> Guide & Tips, Health and Safety, and Other Information -> Under Guide and Tips -> click on User's Guide
[Image: 1790671095600-png.20291]

3. Scroll bottom of the page and type this
tiny.cc/jx9b101 then click go

[Image: 1790671102519-png.20292]

Enjoy!]]> <![CDATA[PlayStation 4: 1.76 System Update & Recovery (Download)]]> https://sickgaming.net/thread-113858.html Mon, 04 Apr 2016 08:27:41 -0200 xSicKxBot]]> https://sickgaming.net/thread-113858.html PlayStation 4: 1.76 System Update & Recovery Download

Description

PlayStation 4 System Update / Firmware Version 1.76
Released: 2nd September 2014

Download:

System Update:

System Recovery:

System Update or System Recovery?

The system update is all that you require to update a PS4 and is generally what you will want to download in most cases. The System Recovery will only be required if you upgrade the hard drive inside the PS4. This will allow the PS4's operating system to be re-installed on the new hard drive.

How to use:

Download the System Update from the link above
Extract the PS4UPDATE.PUP with WinRAR or another program capable of extracting zip files
On a FAT32 formatted USB memory stick create a folder called PS4, then inside this folder create a folder called UPDATE
Copy the extracted PS4UPDATE.PUP to the USB memory stick in the PS4 > UPDATE folder
Connect the USB memory stick to the PS4, then on the PS4 go to Settings > System Software Update
Follow the screens to complete the update

Features added in the PlayStation 4 1.76 System / Firmware update:

Minor changes and was the last update until version 2.0.

Note: This is the firmware your PS4 must be on to take advantage of the BadIRET exploit.

Use at your own risk.]]> PlayStation 4: 1.76 System Update & Recovery Download

Description

PlayStation 4 System Update / Firmware Version 1.76
Released: 2nd September 2014

Download:

System Update:

System Recovery:

Download the System Update from the link above
Extract the PS4UPDATE.PUP with WinRAR or another program capable of extracting zip files
On a FAT32 formatted USB memory stick create a folder called PS4, then inside this folder create a folder called UPDATE
Copy the extracted PS4UPDATE.PUP to the USB memory stick in the PS4 > UPDATE folder
Connect the USB memory stick to the PS4, then on the PS4 go to Settings > System Software Update
Follow the screens to complete the update

Features added in the PlayStation 4 1.76 System / Firmware update:

Minor changes and was the last update until version 2.0.

Note: This is the firmware your PS4 must be on to take advantage of the BadIRET exploit.

Use at your own risk.]]> <![CDATA[Custom PS3 Firmware Downloads Links + 3.55 & 3.41 OFW!]]> https://sickgaming.net/thread-82855.html Mon, 23 Feb 2015 16:53:19 -0200 xSicKx]]> https://sickgaming.net/thread-82855.html Custom PS3 Firmware Downloads Links + 3.55 & 3.41 OFW!

Here are working download links for the most popular PS3 custom firmwares. Enjoy!

3.55 & 3.41 Custom Firmwares

Geohot 3.55 Custom Firmware Download -

PS3UPDAT.PUP
Kmeaw 3.55 Custom Firmware Download -

PS3UPDAT.PUP
Rebug 3.55 Custom Firmware Download -

Rebug
Rebug 3.41 Custom Firmware Download -

Codename: Rebug
CFW 3.55 OtherOS Special (Thanks to Chips 98) -

PS3UPDAT.pup

___________________________________________________________________________

4.XX Custom Firmwares
(You must be on firmware 3.55 or earlier to install these.)

Rogero 4.21 Custom Firmware -

Rogero4.21

ErmaC 4.30 Custom Firmware -

ErmaC 4.30 CFW 1.4.rar

[align=left]Rogero 4.40 Custom Firmware (Thanks to Wolf) -

Rogero_CEX-4.40_v1.03.PUP
___________________________________________________________________________

Official Firmwares

Official Firmware 3.55 Download

PS3UPDAT.PUP
Official Firmware 3.41 Download:

PS3UPDAT.PUP

___________________________________________________________________________

If any of the links are broken, let me know and I will update them. Thanks.]]> Custom PS3 Firmware Downloads Links + 3.55 & 3.41 OFW!

Here are working download links for the most popular PS3 custom firmwares. Enjoy!

3.55 & 3.41 Custom Firmwares

Geohot 3.55 Custom Firmware Download -

PS3UPDAT.PUP
Kmeaw 3.55 Custom Firmware Download -

PS3UPDAT.PUP
Rebug 3.55 Custom Firmware Download -

Rebug
Rebug 3.41 Custom Firmware Download -

Codename: Rebug
CFW 3.55 OtherOS Special (Thanks to Chips 98) -

PS3UPDAT.pup

___________________________________________________________________________

4.XX Custom Firmwares
(You must be on firmware 3.55 or earlier to install these.)

Rogero 4.21 Custom Firmware -

Rogero4.21

ErmaC 4.30 Custom Firmware -

ErmaC 4.30 CFW 1.4.rar

[align=left]Rogero 4.40 Custom Firmware (Thanks to Wolf) -

Rogero_CEX-4.40_v1.03.PUP
___________________________________________________________________________

Official Firmwares

Official Firmware 3.55 Download

PS3UPDAT.PUP
Official Firmware 3.41 Download:

PS3UPDAT.PUP

___________________________________________________________________________

If any of the links are broken, let me know and I will update them. Thanks.]]> <![CDATA[Downgrading with E3 Flasher, How to install + info]]> https://sickgaming.net/thread-82854.html Mon, 23 Feb 2015 16:42:44 -0200 xSicKx]]> https://sickgaming.net/thread-82854.html

Information on an E3Flasher:

E3 flasher is a special device to help you program NAND and NOR flash data . It is simplest to help you get all function with one key operation without any PC software.
E3 flasher is also easy upgradable from TF card and PC USB. it has 16M Nor flash memory on board, so you can save data on E3 flasher or TF card in few min, no need connect to PC anymore.
E3 flasher has a special design for PS3, to allow user install and operation easier, and even get more function like dual boot.
Now we only provide E3 flasher Limited version , it is a special suit for PS3 NOR FLASH user, The quantity for all the world is only 3000pcs .

Here is a list to show flash version on difference console :

Here is a list to show flash version on difference console :

CECHA/COK-001 up to including CECHE/COK-002W : NAND FLASH
CECHG/SEM-001 : NAND FLASH
CECHH/DIA-001 up to including CECHK/DIA-002 : NOR FLASH
CECHL/VER-001 (1-878-196-31) : NOR FLASH
CECHL/VER-001 : NOR FLASH
CECHL/VER-001 and PS3 Slim 2... : NOR FLASH
And all SLIM console is NOR FLASH

To check model compatibility, refer to these two images:

PS3 Phat

[Image: Screen-Shot-2011-10-27-at-1.04.11-PM1-538x367.png]

[Image: Screen-Shot-2011-10-27-at-1.04.11-PM1-538x367.png]

PS3 Slim

[Image: Screen-Shot-2011-10-27-at-1.04.36-PM1-538x357.png]

How to install (Video Tutorial):
]]>

Information on an E3Flasher:

E3 flasher is a special device to help you program NAND and NOR flash data . It is simplest to help you get all function with one key operation without any PC software.
E3 flasher is also easy upgradable from TF card and PC USB. it has 16M Nor flash memory on board, so you can save data on E3 flasher or TF card in few min, no need connect to PC anymore.
E3 flasher has a special design for PS3, to allow user install and operation easier, and even get more function like dual boot.
Now we only provide E3 flasher Limited version , it is a special suit for PS3 NOR FLASH user, The quantity for all the world is only 3000pcs .

Here is a list to show flash version on difference console :

Here is a list to show flash version on difference console :

CECHA/COK-001 up to including CECHE/COK-002W : NAND FLASH
CECHG/SEM-001 : NAND FLASH
CECHH/DIA-001 up to including CECHK/DIA-002 : NOR FLASH
CECHL/VER-001 (1-878-196-31) : NOR FLASH
CECHL/VER-001 : NOR FLASH
CECHL/VER-001 and PS3 Slim 2... : NOR FLASH
And all SLIM console is NOR FLASH

To check model compatibility, refer to these two images:

PS3 Phat

[Image: Screen-Shot-2011-10-27-at-1.04.11-PM1-538x367.png]

PS3 Slim

How to install (Video Tutorial):
]]> <![CDATA[Requirements to Jailbreak your PS3! Read this first!]]> https://sickgaming.net/thread-82853.html Mon, 23 Feb 2015 16:38:06 -0200 xSicKx]]> https://sickgaming.net/thread-82853.html

First off, check your firmware version.
This can be done by navigating in the
XMB to settings>system settings>system information.

The latest firmware as of now (April 8, 2013) is 4.66.
In order for your Ps3 to be jailbroken, you MUST be on OFW (Official FirmWare) 3.55 or lower (3.50, 3.41, etc.)

Super-slims cannot be jailbroken, and the system has to have once been on version 3.55. As for slims, the only noted unjailbrokable ones are the CECH-3001A.

If you are not on version 3.55 or lower, there's still hope. You may seek into downgrading your system. This is done by purchasing an E3 Flasher, which will downgrade upon using.

Some CECH250x models come out of the box on 3.61.

To find out the compatability for your model, check this list:
[Image: cpV1U.png]

If you have doubts, check the minvercheck here.

Once you have downgraded and on version 3.55, you can now begin the jailbreaking process!

Tutorial on how to do this (by me) can be found: http://adf.ly/13wo6a

Hope this helps on any confusion on whether you can do this or not.]]> <![CDATA[How to Jailbreak Your PS3 + Spoof for online play! Modded Lobbies and all!]]> https://sickgaming.net/thread-82852.html Mon, 23 Feb 2015 16:29:13 -0200 xSicKx]]> https://sickgaming.net/thread-82852.html Getting Started

One common question I find on here time and again is “Can I jailbreak my PS3?” The answer is simple. You MUST be on version 3.55, and you should have 2 PS3 consoles, just to make this easier on yourself (This isn't needed, but it helps so you can play regularly on one, and mod things on the other. It's completely up to you).

Some PS3 slim models will not be able to be downgraded, so please refer to the Next Steps part, and check the compatibility there. To check your current version, on the XMB(Main screen) navigate to Settings>System Settings>System Info. The “System Version” is where your current version will be. Consoles that have not at one time been on 3.55 cannot be jailbroken either. So, if you bought a PS3 from Walmart and it came out of the box on 3.60, your out of luck.

There is also a tool called MinVerChk, which searches for the firmware your system had installed when it left the factory. I recommend those on 25xx to run this package, as it will tell you what minimum firmware can be installed.
If it says 3.55 and lower, your system can be jailbroken.
If it says 3.55 and higher, your system cannot be jailbroken.

You may also check the requirements here.

Downgrading Step
If you are on 3.55 or lower, you are in luck, and are able to jailbreak! If you are on 3.56 - 4.60, you will need to downgrade with an E3Flasher or another hardware flasher of your choice, which the tutorial for the E3Flasher can be found below. Info on the E3Flasher can be found here. If you're having troubles, verify your downgrade.bin is up to date as well as your flasher software.

If your SKU model is NOR, you use an E3 Flasher. If it is NAND, use Progskeet.

Models CECHA. CECHB, CECHC, CECHE, and CECHG are NAND.
Models CECHH, CECHJ, CECHL, CECHM, CECHP, CECHQ, and all Slims are NOR.

Downgrading videos:

Progskeet Downgrade

CFW Choice Step:
Now that you have read the E3Flasher tutorial, and have downgraded your PS3, you can now proceed to the next step of actually jailbreaking. Jailbreaking can be accomplished by downloading any of the 3.55 CFW files, found: http://www.sickkilledu.com/thread-82855.html

The recommended CFW file is Kmeaw 3.55, as it is one of the more popular ones. You're not limited to it, as you can chose any CFW (Geohot for example).

The USB Step:
In order to jailbreak, download the Kmeaw 3.55 download, and plug in your USB flash drive. In your flash drive, right-click and format your flash drive to FAT32. Once that is done, go into your USB, and create a new folder. Name this folder “PS3” without the quotations. Inside the PS3 folder, create a folder called “Update” without the quotations. In this folder, you should place the PS3UPDAT.PUP, which is found in the download for the Kmeaw 3.55 download.
Your setup should be like this:
|PS3
|UPDATE
|PS3UPDAT.PUP

You can now safely eject your USB, and plug it into your PS3.

The Jailbreaking Step
Once your USB is plugged into your PS3, on the XMB, head over to System>System Update. In here, it will ask you to update OTA(Over the Air) or to update via storage media. Click on Update via storage media, and it shall say Kmeaw 3.55-jb, and click OK. Agree to the bullcrap (this is seriously bullcrap, go ahead and read it, it actually is amusing.) Let the update install (it shouldn’t take more than 5 minutes. After your PS3 has restarted, you should be back on the XMB, and you should see under the “Game” tab *Install Package Files and */App_Home/PS3_GAME/. This means you have successfully jailbroken your PS3!

ProTip: It is much easier after downgrading to install the OFW of 3.55 before installing the CFW, as it makes it faster and easier, which again can be found in Cash's download thread.

Should Look Like this:
[Image: 2011012014.48.351.jpg]

ODE Option
If you are unable to jailbreak, there is another solution to playing games or run homebrew on your system. That is the ODE, which can be used by soldering parts onto the motherboard.

Code:
Phat:
CECHA (PATA)
CECHB (PATA)
CECHC (PATA)
CECHE (PATA)
CECHG (PATA)
CECHH (PATA)
CECHK (PATA)
CECHL (SATA)

Slim:
CECH 2XXX (SATA)
CECH 21XX (SATA)
CECH 25XX (SATA)
CECH 3XXX (SATA)

Super Slim:
CECH 4XXX (SATA)

There's 3 major types of ODE:
Cobra ODE: http://www.cobra-ode.com/
3K3Y: http://www.3k3y.com/
E3 ODE: http://www.e3-tech.net/e3 ode pro.html

Spoofing
Spoofing allows you to trick your PS3 into thinking it is on the lastest version, and allows you to data transfer to your retail, resulting in PSN access. There are various ways to spoof to the latest version, including a REX toolbox, or just installing via storage media with your 4.50 CFW version. Downloads can be found in the download tab for both.

You may also ask, "which spoofing version is right for me? I've heard of CEX, DEX and REBUG, but which do I choose?" The answer is simple. CEX is the basic CFW version, which allows you to access basically anything. You're able to host modded lobbies, as well as download some pirated games. DEX on the other hand is Developer Firmware. This means it's usually only used when you are planning on making a game, or want to access other developing features such as enabling or disabling lvl2 patches. REBUG combines both of those, which makes it easier to switch from CEX to DEX with the click of a button rather than having to reinstall the firmware to switch. REBUG also comes with some fun features, such as unlocking trophies to trick your friends into thinking you're some trophy god or something like that.

An example of a spoofed PS3 version: (Rebug)
[Image: 2.jpg]

Spoofing - What's the difference?:
At some point in this thread, you've probably wondered: CFW is great and all, but which is for me? There's a simple way to answer this. First off, if you're asking yourself this in the first place, you should go with a simple firmware type, such as CEX. CEX is the basic any custom firmware can get, all it has is install package files, and root access, which is all you need.
DEX on the other hand is much more complicated. The only reason DEX is more popular than CEX is because CEX didn't have the ability to RTM on until recently with the release of CCAPI 2.00. Now that that's released, there really isn't a need to be on DEX, unless if your modding client is for DEX firmware only.
REX or REBUG is both of those put together, along with a few more debug options, like built in MAC and Console ID spoofing with REBUG Toolbox. I personally like the look of REBUG because it has more of a custom feeling to it, rather than the plain old XMB.
Stay away from SEX firmware. All it is is a kiosk firmware that shops use to install demos. There is literally nothing cool about it.

Getting Online:
CEX:
Getting online on CEX is pretty straightforward. If you have the new 4.55 Rogero installed, you should be good to just go ahead and sign in.
If you're on Rogero 4.55 or 4.50, there is something called ZOFMOD (link below) which will spoof you to 4.60. I suggest using PS Ninja to wipe your game history after you install it or with any homebrew.

DEX:
DEX is a little bit more complicated. Best way to explain this is by a video.

CEX To DEX Tutorial:

Things you will need:
Ps3 on 3.55 firmware
A USB device with at least 1GB free
jaicrab’s preloader
FactoryServiceMode tool
eEID_RKDumper
CEX2DEX tool

1. Install the FactoryServiceMode pkg on your PS3 and use it to boot your PS3 into Factory Service Mode. When done, confirm your console is in service mode by turning it on and seeing if the red box is there in the lower right hand corner. Power down your PS3.

2. Take all the files from Preloader.zip and extract them onto the root of your USB stick. Rename "Lv2diag.self.flash" to "Lv2diag.self".

3. Eject your USB from your PC and place it in the rightmost USB port of your PS3 (your PS3 needs to be turned off). Once it is securely in place, turn on the console. Nothing is going to come up on the screen, and eventually the PS3 power LED will start blinking. DO NOT TURN OFF THE CONSOLE, it is dumping your NAND/NOR. Wait for it to power down itself.

4. Once your console turns itself off, remove the USB from your PS3 and plug it back into your PC. There will now be a file on it named "Backuprflash.bin" (Note: You may have to enable displaying of system files in order for it to be shown). This is your dump of your NOR/NAND - if your console is NOR, the filesize should be 16mb. If your console is NAND, it will be 256mb.

5. On your USB, rename "Lv2diag.self" back to "Lv2diag.self.flash" and then rename "Lv2diag.self.exit" to "Lv2diag.self". Place the USB in the rightmost USB port of your PS3 (turned off), then turn it on. It should turn itself off after a few seconds. When it turns off, remove your USB and boot the PS3. It should now be out of factory service mode.

6. Install the eEID_RKDumper on your PS3. Run it, and it should cause your console to blackscreen. It will reboot after a few seconds, just give it it's time and don't interrupt it (it is dumping your root key). Once it reboots, proceed to the next step.

7. Use a filemanager or FTP server to retrieve your root key dump from your PS3 - it is located at dev_hdd0/tmp/eid_root_key. It should be 256kb. Get it onto your USB, it should be in the same directory as your Backuprflash.bin. Rename it to "dump" (no file extension).

9. Start up CEX2DEX again on your PC. For the NOR/NAND flash dump, select your Backuprflash.bin. For the METLDR dump, select your rootkey (file named "dump"). Click on CEX -> DEX, and when it prompts you save the new file as "rflash.bin" and put it onto the root of your USB stick. Your NOR/NAND dump is now fully converted to DEX, all that is left is to flash it back onto your PS3. The filesize for rflash.bin should be 16mb for NOR consoles and 256mb for NAND consoles.

10. On your PS3, use FactoryServiceMode Tool to boot into Factory Service Mode again. On your USB, rename "Lv2diag.self" to "Lv2diag.self.exit" and rename "Lv2diag.flash.self" to "Lv2diag.self". Delete the advance.cfg file from the USB, and put this one onto the root of it: advance.cfg

11. Make sure your PS3 is fully powered off, then plug your USB into the rightmost USB port. Turn on the PS3, and it will begin writing to your NAND/NOR. DO NOT TURN OFF THE PS3!!! If you do, it is a guaranteed brick. Just leave it alone until the PS3 turns itself off, it may take 15 minutes or more. Don't worry if it's taking too long, mine took about 40 minutes to write completely. Once your PS3 has powered itself off continue to the next step.

12. On your USB, rename "Lv2diag.self" back to "Lv2diag.self.flash" and then rename "Lv2diag.self.exit" to "Lv2diag.self". Place the USB in the rightmost USB port of your PS3 (turned off), then turn it on. It should turn itself off after a few seconds. When it turns off, remove your USB and boot the PS3. It should now be out of factory service mode. Congratulations, you are now ready to install DEX firmware. I would recommend downloading and installing this debug firmware, from there you can go to 4.20 debug or whatever other version you want.

Important Notes:
-Once you convert to DEX, your console can no longer access the Playstation Network. Your IDPS becomes invalid.
-You cannot data transfer from a DEX console to a CEX console.
-If you choose to install a debug update of version 3.56 or higher, Peek & Poke will be disabled. This will make certain homebrew applications no longer work.
-Most PKGs and homebrew applications will have to be resigned as debug files before they can be installed/run on DEX firmwares above 3.55.

Game Modding
With a now jailbroken system, you can now add whatever peripherals to any game (well sort of). Jailbroken systems are commonly associated with game modders, as in those people you see with aimbots annoying the piss out of you.

But, how do they do it you say? The answer is simple. With the more recent games (such as Call of Duty: Ghosts) those "aimbotters" use a console application called ConsoleControllAPI, which allows a connection from your PC to your PS3 via an ethernet cable to poke commands into a game. These commands are called offsets and look like for example: 0x01F134DC (offset to change in-game name).

Before I get more into detail than I should, here is a tutorial on how to host these lobbies, as well as a video tutorial. These lobbies can also be accomplished with an RTM tool, which can be found in their respective game modding forums here on Se7ensins.

Backups
What are they? Backups are an ability jailbroken systems have to backup or install a game disk so you may play it without the game disk. How you do this is by using Rogero's Backup Manager or Multiman in the downloads. Please note this version is not comparable with rebut, so it's only for a system on 3.55. Only for CFW.

Here is a tutorial on how to create and play backups on Multiman.

An example of backups via Multiman:
[Image: MultiMAN-1.09.03-Multifunctional-Filemanager.jpg]

[Image: MultiMAN-1.09.03-Multifunctional-Filemanager.jpg]

To update a backup, just find your region code, and search the game you would like to update along with your region code. Your region code should be BLES/BLUSxxxxx. When you find the update, it should be in package form. Then just copy to your USB, plug it in to your system, then go to install package files and then install the package you just downloaded. You're now good to go.

How to update/install new CFW

You just install the package via storage media to update.

How to downgrade CFW

QA flagging your console is the fastest and easiest way to downgrade your CFW version. Note you MUST have a working Blu-Ray drive to QA flag.
Dehashing: uses "ros0" and "ros1", which takes your system back to it's original state. Use Rogero 999 Downgrader, then QA flag your console on 3.55CFW.

Regarding Banning
The only way to unban yourself is to obtain another legal console ID, which you can change in Rebug Toolbox or through another client. Keep in mind trading or selling console ID's is against 7s TOS. You will also need the PSID patch which is found in the downloads.

How to prevent banning:

Code:
Mostly Common Sense

    Never Mod new Games unless you are offline or you are certain that you will not get banned
    Never use mods online
    Only use mod for your own fun not to use it against people (who can then report you)
    Never use Homebrew for long periods or whilst connected to SEN
    Never use your main SEN Account on you're PS3
    Do NOT use pre-releases with your CFW and avoid playing online with them.
    Try not to use the Modded comment.
    Try and avoid staying online on your CFW. (Less Chance of a ban when you're not)
    Never Use the Sign in Automatically Option.
    Don't go crazy whilst RTEing.

How to prevent bricking:

Code:
   Only change files that you know
    Always Read a tutorial throughout and read as you do it.
    Never Turn you're PS3 off if you think you done something wrong (just find the original files)
    Always back up the files you are modding
    Never delete files from the system that you dont know

Emulators

Emulators can range from the SNES system to running PS2 games on an 80GB system or newer.

SNES Example:

With that said, the downloads are in the downloads folder for the emulator and the ROMS for it.

To run this, you need to download the manager for it, first the base then the real thing. I added both links in the 'downloads' tab below.

Any questions? Please comment below. Let me know how it works for you!]]> Getting Started

One common question I find on here time and again is “Can I jailbreak my PS3?” The answer is simple. You MUST be on version 3.55, and you should have 2 PS3 consoles, just to make this easier on yourself (This isn't needed, but it helps so you can play regularly on one, and mod things on the other. It's completely up to you).

Some PS3 slim models will not be able to be downgraded, so please refer to the Next Steps part, and check the compatibility there. To check your current version, on the XMB(Main screen) navigate to Settings>System Settings>System Info. The “System Version” is where your current version will be. Consoles that have not at one time been on 3.55 cannot be jailbroken either. So, if you bought a PS3 from Walmart and it came out of the box on 3.60, your out of luck.

There is also a tool called MinVerChk, which searches for the firmware your system had installed when it left the factory. I recommend those on 25xx to run this package, as it will tell you what minimum firmware can be installed.
If it says 3.55 and lower, your system can be jailbroken.
If it says 3.55 and higher, your system cannot be jailbroken.

You may also check the requirements here.

Downgrading Step
If you are on 3.55 or lower, you are in luck, and are able to jailbreak! If you are on 3.56 - 4.60, you will need to downgrade with an E3Flasher or another hardware flasher of your choice, which the tutorial for the E3Flasher can be found below. Info on the E3Flasher can be found here. If you're having troubles, verify your downgrade.bin is up to date as well as your flasher software.

If your SKU model is NOR, you use an E3 Flasher. If it is NAND, use Progskeet.

Models CECHA. CECHB, CECHC, CECHE, and CECHG are NAND.
Models CECHH, CECHJ, CECHL, CECHM, CECHP, CECHQ, and all Slims are NOR.

Downgrading videos:

Progskeet Downgrade

CFW Choice Step:
Now that you have read the E3Flasher tutorial, and have downgraded your PS3, you can now proceed to the next step of actually jailbreaking. Jailbreaking can be accomplished by downloading any of the 3.55 CFW files, found: http://www.sickkilledu.com/thread-82855.html

The recommended CFW file is Kmeaw 3.55, as it is one of the more popular ones. You're not limited to it, as you can chose any CFW (Geohot for example).

The USB Step:
In order to jailbreak, download the Kmeaw 3.55 download, and plug in your USB flash drive. In your flash drive, right-click and format your flash drive to FAT32. Once that is done, go into your USB, and create a new folder. Name this folder “PS3” without the quotations. Inside the PS3 folder, create a folder called “Update” without the quotations. In this folder, you should place the PS3UPDAT.PUP, which is found in the download for the Kmeaw 3.55 download.
Your setup should be like this:
|PS3
|UPDATE
|PS3UPDAT.PUP

You can now safely eject your USB, and plug it into your PS3.

The Jailbreaking Step
Once your USB is plugged into your PS3, on the XMB, head over to System>System Update. In here, it will ask you to update OTA(Over the Air) or to update via storage media. Click on Update via storage media, and it shall say Kmeaw 3.55-jb, and click OK. Agree to the bullcrap (this is seriously bullcrap, go ahead and read it, it actually is amusing.) Let the update install (it shouldn’t take more than 5 minutes. After your PS3 has restarted, you should be back on the XMB, and you should see under the “Game” tab *Install Package Files and */App_Home/PS3_GAME/. This means you have successfully jailbroken your PS3!

ProTip: It is much easier after downgrading to install the OFW of 3.55 before installing the CFW, as it makes it faster and easier, which again can be found in Cash's download thread.

Should Look Like this:
[Image: 2011012014.48.351.jpg]

ODE Option
If you are unable to jailbreak, there is another solution to playing games or run homebrew on your system. That is the ODE, which can be used by soldering parts onto the motherboard.

Code:
Phat:
CECHA (PATA)
CECHB (PATA)
CECHC (PATA)
CECHE (PATA)
CECHG (PATA)
CECHH (PATA)
CECHK (PATA)
CECHL (SATA)

Slim:
CECH 2XXX (SATA)
CECH 21XX (SATA)
CECH 25XX (SATA)
CECH 3XXX (SATA)

Super Slim:
CECH 4XXX (SATA)

QA flagging your console is the fastest and easiest way to downgrade your CFW version. Note you MUST have a working Blu-Ray drive to QA flag.
Dehashing: uses "ros0" and "ros1", which takes your system back to it's original state. Use Rogero 999 Downgrader, then QA flag your console on 3.55CFW.

Code:
Mostly Common Sense

    Never Mod new Games unless you are offline or you are certain that you will not get banned
    Never use mods online
    Only use mod for your own fun not to use it against people (who can then report you)
    Never use Homebrew for long periods or whilst connected to SEN
    Never use your main SEN Account on you're PS3
    Do NOT use pre-releases with your CFW and avoid playing online with them.
    Try not to use the Modded comment.
    Try and avoid staying online on your CFW. (Less Chance of a ban when you're not)
    Never Use the Sign in Automatically Option.
    Don't go crazy whilst RTEing.

How to prevent bricking:

Code:
   Only change files that you know
    Always Read a tutorial throughout and read as you do it.
    Never Turn you're PS3 off if you think you done something wrong (just find the original files)
    Always back up the files you are modding
    Never delete files from the system that you dont know

Any questions? Please comment below. Let me know how it works for you!]]> <![CDATA[FAQ for PS3 Jailbreak: What you need to know.]]> https://sickgaming.net/thread-82851.html Mon, 23 Feb 2015 16:17:40 -0200 xSicKx]]> https://sickgaming.net/thread-82851.html

Code:
Q: What can a jailbroken Playstation 3 system do?
 A: When a PS3 is jailbroken, it allows the use of installing package files, which can range from Emulators or programs that allow you to install free games from a black market marketplace. You can also mod games (such as Call of Duty), download free movies (with the removal of Cinavia, which disallowed the downloading of movies onto the system after 3.10), and run FTP clients, and much more!
Q: Can I jailbreak 4.50, 4.55, 4.60?
A: No. You must downgrade first, and in order to downgrade you must have had a console on 3.55 at one time. Super slims cannot be jailbroken.
Q: Can I downgrade a super slim?
A: NO! For all models that can be downgraded, please refer to the list of slim models that can be downgraded. Note all phat models can be downgraded.
Q: How do I check my model?
A: Your model is next to your serial number on the back of your system and always starts with CECHxxx (replace X's with your number).
Q: I have the E3 Installed an downgraded, what's the next step to get online?
A: To get online you use a spoof, which in retrospect, makes your system think it's on the current version, but isn't.

List of slim models that can be downgraded:
[Image: cpV1U.png]

Now that is cleared up, we can get started.

How to Jailbreak your PS3: http://adf.ly/13wo6a]]>

Code:
Q: What can a jailbroken Playstation 3 system do?
 A: When a PS3 is jailbroken, it allows the use of installing package files, which can range from Emulators or programs that allow you to install free games from a black market marketplace. You can also mod games (such as Call of Duty), download free movies (with the removal of Cinavia, which disallowed the downloading of movies onto the system after 3.10), and run FTP clients, and much more!
Q: Can I jailbreak 4.50, 4.55, 4.60?
A: No. You must downgrade first, and in order to downgrade you must have had a console on 3.55 at one time. Super slims cannot be jailbroken.
Q: Can I downgrade a super slim?
A: NO! For all models that can be downgraded, please refer to the list of slim models that can be downgraded. Note all phat models can be downgraded.
Q: How do I check my model?
A: Your model is next to your serial number on the back of your system and always starts with CECHxxx (replace X's with your number).
Q: I have the E3 Installed an downgraded, what's the next step to get online?
A: To get online you use a spoof, which in retrospect, makes your system think it's on the current version, but isn't.

List of slim models that can be downgraded:
[Image: cpV1U.png]

Now that is cleared up, we can get started.

How to Jailbreak your PS3: http://adf.ly/13wo6a]]> <![CDATA[How to find out if you PS3 is "Jailbreakable" 1st Step]]> https://sickgaming.net/thread-57669.html Mon, 17 Mar 2014 20:34:06 -0200 xSicKx]]> https://sickgaming.net/thread-57669.html How to Find Out if your PS3 is Jailbreakable!

The Latest Firmware You Can Downgrade From Is 4.53

DO THIS CHECK FIRST DO NOT SKIP THIS STEP

Locate the manufacturing date code found on the base of your ps3.
it will look like this

[Image: R3O8ZC2.jpg]

Where you see the “xx” part below you will see numbers on your ps3.
so the image above shows CECH-4003A but it will be in the below table as CECH-40XX the last 2 numbers do not affect whether it can be downgraded or not so we don’t need to list that part.

Now use DEFAULTDNB's PPC+ MD5 & DATE CHECK TOOL (DCT)v2.4.8.7

[spoiler=Phat/Fat Type PS3's]
CECHAxx (OK To Downgrade) NAND = Progskeet / TEENSY++ 2.0 / InFeCtuS

CECHBxx(OK To Downgrade) NAND = Progskeet / TEENSY++ 2.0 / InFeCtuS

CECHCxx(OK To Downgrade) NAND = Progskeet / TEENSY++ 2.0 / InFeCtuS

CECHExx (OK To Downgrade) NAND = Progskeet / TEENSY++ 2.0 / InFeCtuS

CECHGxx (OK To Downgrade) NAND = Progskeet / TEENSY++ 2.0 / InFeCtuS

CECHHxx(OK To Downgrade) NOR = Teensy++ 2.0 / Progskeet / E3 Flasher

CECHJxx (OK To Downgrade) NOR = Teensy++ 2.0 / Progskeet / E3 Flasher

CECHKxx (OK To Downgrade) NOR = Teensy++ 2.0 / Progskeet / E3 Flasher

CECHLxx (OK To Downgrade) NOR = Teensy++ 2.0 / Progskeet / E3 Flasher

CECHMxx(OK To Downgrade) NOR = Teensy++ 2.0 / Progskeet / E3 Flasher

CECHPxx (OK To Downgrade) NOR = Teensy++ 2.0 / Progskeet / E3 Flasher

CECHQxx (OK To Downgrade) NOR = Teensy++ 2.0 / Progskeet / E3 Flasher

DECHAxx (OK To Downgrade) [/spoiler]

[spoiler=Slime Type PS3's]
CECH-20xx(OK To Downgrade) NOR = Teensy++ 2.0 / Progskeet / E3 Flasher

CECH-21xx (OK To Downgrade) NOR = Teensy++ 2.0 / Progskeet / E3 Flasher

CECH-25xxA or B (with date code [0C] [0D] [1A] are known to be ok) NOR = Teensy++ 2.0 / Progskeet / E3 Flasher
ALL THE REST(DOUBLE CHECK THIS with MinVerChk from HERE AS SOME CANNOT BE DOWNGRADED)
[/spoiler]]]> How to Find Out if your PS3 is Jailbreakable!

The Latest Firmware You Can Downgrade From Is 4.53

DO THIS CHECK FIRST DO NOT SKIP THIS STEP

Locate the manufacturing date code found on the base of your ps3.
it will look like this

[Image: R3O8ZC2.jpg]