Aug 14, 2016 Both download links of the.PUP are the same.Whoops, apparently there is a DUS.psv instead of DEU.psv in the links. The 3.60 actually is downloadable from pal regions, i just got mine from the italian site. Configure the latest PS3 System Software Update 4.84 and get the benefit of improved features. Download update data using a PC and save on storage media. or a USB Mass Storage device. Copy the update data to the PS3™ system's hard disk drive and perform the update. Save as file name “PS3UPDAT.PUP”. Update procedure. Nov 15, 2013 Go to Sony’s PS4 firmware download page and download the file to your PC or Mac. Click the Download link to get the PS4UPDATE.PUP file. On the USB thumb drive, be sure to create the following folder structure: PS4 Update PS4UPDATE.PUP. To do this, just create a PS4 folder. Go into this folder and then create an Update folder.
An update to the system software for PlayStation®Vita systems and PlayStation®TV systems was released on October 16, 2019. Use this update to install system software version 3.73.
The PlayStation®TV system is sold as PlayStation®Vita TV system in some countries and regions. Systems with either name are referred to as “PlayStation®TV” or 'PS TV' on this page.
Always update your system to the latest version of the system software. By updating, you can enjoy additional features, improved usability, and enhanced security.
PUP (Playstation Update Package) files are packages which contain the files used to update a PSP or PS3 system. There are 2 different types: patches (PS3PATCH.PUP) and full updates (PS3UPDAT.PUP). Based on the model, there are 4 different release types: Retail/CEX, Shop/SEX, Debug/DEX and Tool/DECR. Within the Retail/CEX there are 2 file versions: 1 is a PUP with a normal file length which also gets released online. The other PUP file version is the same, except it is zero-filled after the normal PUP content to a fixed filelength of 256MB, which gets released on Gamedisks (if gamecreators build their project to a premaster and give it to Sony for signing, they just use a placeholder of a 256MB PS3UPDAT.PUP which contains no firmwaredata at all - it is completely zerofilled. Sony decides the firmware that gets on the disk and for which firmware the 'Gold' code is signed and mastered).
There is no regioning in the .PUP files, they are the same for all different regions (if you were looking for regioninfo, see here).
The PS3 however gets the ps3-updatelist.txt from different servers, depending on the region of that model (last 2 numbers in the CECHxxXX SKU name).
for completeness see Target ID: Reference Tool/DECR : 0x81, Debug/DEX : 0x82, and Arcade : 0xA0
Retail basic structure of the update URL:
Shop update check URL: http://fshop01.ps3.update.playstation.net/update/ps3/list/shop/ps3-updatelist.txt
Content:
Shop basic structure of the update URL:
To install firmware via USB Mass Storage Devices (e.g. USB-stick, Memory Stick, SD-card, Compact Flash with at least 256MB free), place the PS3UPDAT.PUP file in the following folder structure: /PS3/UPDATE/PS3UPDAT.PUP
The HMAC key used to verify the packages has been released. Look around for 'pup-hmac'
Offset | Length | Type | Information |
---|---|---|---|
0x0 | 0x8 | unsigned long | Magic |
0x8 | 0x8 | unsigned long | Package Version |
0x10 | 0x8 | unsigned long | Image Version |
0x18 | 0x8 | unsigned long | File Count |
0x20 | 0x8 | unsigned long | Header Length |
0x28 | 0x8 | unsigned long | File Length |
0x30 | 0x20 * File Count | File Table | File Table |
0x30 + (0x20 * File Count) | 0x20 * File Count | Hash Table | Hash Table |
0x30 + (0x40 * File Count) | 0x14 | bytes | Header Hash |
0x44 + (0x40 * File Count) | 0xC | bytes | Unknown |
The file table consists of a number of file entries determined by File Count, with the format below:
Offset | Length | Type | Information |
---|---|---|---|
0x0 | 0x8 | unsigned long | Entry ID |
0x8 | 0x8 | unsigned long | Data Offset |
0x10 | 0x8 | unsigned long | Data Length |
0x18 | 0x8 | unsigned long | Unknown |
File Entry ID | Filename |
---|---|
0x100 | version.txt (aka: ps3version.txt) |
0x101 | license.xml (aka: resource.txt? ) |
0x102 | promo_flags.txt (only on Shop ) (aka: shop.txt?) |
0x103 | update_flags.txt |
0x104 | patch_build.txt |
0x200 | ps3swu.self |
0x201 | vsh.tar / font_resource.tar |
0x202 | dots.txt |
0x203 | patch_data.pkg |
0x300 | update_files.tar |
0x501 | spkg_hdr.tar (added since FW 3.56) |
0x601 | ps3swu2.self (added since FW 3.56) |
The hash table contains a hash entry for every file inside the PUP.
The hash entry format is:
Offset | Length | Type | Information |
---|---|---|---|
0x0 | 0x8 | unsigned long | File Entry ID |
0x8 | 0x14 | bytes | HMAC-SHA1 hash |
0x1C | 0x4 | unsigned int | Unknown |
Here are two examples of the files stored in a PUP.
For a comparison between Retail and Debug firmware : 3.55 firmware
The following information is a copy/paste from the output of KaKaRoTo's pup.c tool. This is an old build, which does not support 3.56/3.60 and higher added entryid's x501 & 0x601 (which because of that are named Unknown entry id).
HMAC Key
Header
File Entry
Hash Entry
Footer
Entry Id
PUPEntryID entries
Entry Id | Filename |
---|---|
0x100 | version.txt |
0x101 | license.xml |
0x102 | promo_flags.txt |
0x103 | update_flags.txt |
0x104 | patch_build.txt |
0x200 | ps3swu.self |
0x201 | vsh.tar |
0x202 | dots.txt |
0x203 | patch_data.pkg |
0x300 | update_files.tar |
0x501 | spkg_hdr.tar |
0x601 | ps3swu2.self |
|