- Dec 05, 2019 Download: PS Vita Firmware 3.65 Update (US) / PS Vita Firmware 3.65 Update (EU) / PS Vita Firmware 3.65 Update (JP) From Sony's Official Site comes the PS Vita 3.65 changelog, as follows: PlayStation Vita system software version 3.65 was released on April 18. Version 3.65 adds or updates the following features. New for 3.65.
- Oct 11, 2016 Seperti yang telah saya tulis di artikel sebelumnya Bermain Game Bajakan di PS Vita, untuk dapat memainkan homebrew PS Vita memakai Henkaku, kita harus memiliki PS Vita dengan Firmware 3.60.Jika firmware kita belum 3.60, disarankan untuk melakukan Update Manual PS Vita Firmware 3.60 karena update otomatis akan langsung membuat Firmware.
- 3Installation
- 4Installation descriptive
- 5Firmware .PUP structure
- 6Files in tree example
- 7Content of different versions
Aug 08, 2014 How to Update using PUP File. Download “PSVUPDAT.PUP” file via the aforementioned links. Take an empty PS Vita-compatible memory card (aka PS Vita card) and copy “PSVUPDAT.PUP” to its root directory. Turn off the console and insert your PS Vita card. Next, reboot the console and wait for update to pop up. Apr 10, 2018 Those interested can check it out below, and as usual it's advisable NOT to update for most sceners who didn't get a PS Vita or PlayStation TV to use it only for vanilla mainstream retail games and applications. Download: PS Vita Firmware 3.68 Update (US) / PS Vita Firmware 3.68 Update (EU) / PS Vita Firmware 3.68 Update (JP).
Description[edit]
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).
Regioning[edit]
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).
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).
- Japan, jp (00 > 0x83)
- USA, us (01 > 0x84)
- Europe, eu (04 > 0x85)
- Korea, kr (05 > 0x86)
- United Kingdom, uk (03 > 0x87)
- Mexico, mx (11 > 0x88)
- Australia/New Zealand, au (02 > 0x89)
- South Asia, sa (Asia except China, Japan, Korea and Taiwan) (06 > 0x8A)
- Taiwan, tw (07 > 0x8B)
- Russia, ru (08 > 0x8C)
- China, cn (09 > 0x8D)
- Hong Kong, hk (10 > 0x8D)
- Brasil, br (11 > 0x8F)
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:
Installation[edit]
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 update location for Kiosk is the same as Retail/CEX.
- The update location for disc media (CD, DVD, BD-ROM) is /PS3_UPDATE/PS3UPDAT.PUP
- The update data for Reference Tool (Tool/DECR) is %SCE_PS3_ROOT%targetupdaterref-toolPS3UPDAT.PUP.NNN.0xx
- The update data for Debugging Station (Debug/DEX) is %SCE_PS3_ROOT%targetupdaterdebugging_stationPS3UPDAT.PUP.NNN.0xx.forDEX.release.yyyymmdd
- For updating with a single firmware PUP, both the Reference Tool (Tool/DECR) and Debugging Station (Debug/DEX) use the same folder structure as Retail/CEX : /PS3/UPDATE/PS3UPDAT.PUP
- For updating with a multiple firmware PUP (2.50 or later), the Reference Tool (Tool/DECR) can use the folder structure : /PS3/UPDATE/SEARCH with a maximum of 2 sublevels deeper (e.g. PS3/UPDATE/SEARCH/ReferenceTool/250/PS3UPDAT.PUP.242.001). A maximum of 20 PUP files (including /PS3/UPDATE/PS3UPDAT.PUP if applicable) will be shown in the firmware list.
- The update location for Arcade is '/dev_hdd0/game/SCEEXE000/ARCDIR/PS3UPDAT.PUP'
- The update location in Factory Service Mode (used for downgrader and remarry) is /PS3UPDAT.PUP
- The update location for QA Debug setting : System Update Debug=ON is /dev_hdd0/updater/01/PS3UPDAT.PUP, /dev_hdd0/updater/02/PS3UPDAT.PUP, etc... (or up to 20 updates together with any name and no file extension required in /dev_hdd0/updater/01/)
Problem solving / tips[edit]
- Don’t use any USB Mass Storage Device with enhanced functions as: encryption, fingerprintreader, U3, pincode etc. (sometimes marketed under names as SCSI Enclosure Services (SES) thus needing drivers and only working under Windows)
- Don’t use USB Mass Storage Devices with a long initialisation time (e.g. some MP3 players)
- Don’t use multipartitioned USB Mass Storage Devices, only use 1 single primary FAT32 partition.
- Make sure they are formatted according to specifications with FAT32 (e.g. HP USB Format Tool – or TOKIWA / Ridgecrop FAT32 formatter)
- If the stick is formatted FAT32 and still not working, consider other stick or use this tool: http://www.pendrivelinux.com/restoring-your-usb-key-partition/
- Most USB Mass Storage Devices that’ll work effortless with PenDrive Linux, will also work with the PS3 (for downgrading, upgrading, storage of your Game dumps and any normal filestorage under the XMB). Those USB Mass Storage Devices are most likely also the ones giving you the least problems under more exotic platforms like PSX/PSone, PS2/PStwo, Xbox/X360, Gamecube/Wii/WiiU etc.
- Make sure no disc is inside the drive otherwise it will try to install that one instead of the one on USB Mass Storage Device!
- Make sure the media is not readonly (e.g. SDcard or USB Stick with readonly tab) if using firmwares when doing one of the following:
- Factory Service Mode reinstallation
- Remarry BDdrive
- RSOD Fix
- or any process that needs to write a log file, in short, write access
Installation descriptive[edit]
- Select via XMB, Settings -> System Update
- Select Update via Storage Media
- Select OK
- Select right arrow or left joystick right
- Select right arrow or left joystick right
- msg_updater_10 - msg_updater_60 tested to work. they appear one after another in the same manner as the EULA.
- Could list each feature as a seperate msg_updater_X
- Select start to install
Orientation[edit]
Firmware .PUP structure[edit]
The HMAC key used to verify the packages has been released. Look around for 'pup-hmac'
Header[edit]
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 |
File Table[edit]
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 |
Filename IDs[edit]
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) |
Hash Table[edit]
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 |
Files in tree example[edit]
Here are two examples of the files stored in a PUP.
3.55[edit]
For a comparison between Retail and Debug firmware : 3.55 firmware
3.60 - 4.00[edit]
Content of different versions[edit]
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).
File Structure[edit]
HMAC Key
Ps Vita Update 3.65 Download
Header
File Entry
Hash Entry
Footer
Entry Id
PUPEntryID entries
Contents[edit]
Ps Vita 3.60 Update File
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 |
|
Retrieved from ‘http://www.psdevwiki.com/ps3/index.php?title=Playstation_Update_Package_(PUP)&oldid=54806’