Spkg hdr.tar: Difference between revisions

From PS3 Developer wiki
Jump to navigation Jump to search
mNo edit summary
No edit summary
 
(8 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Signed Firmware Package headers ==
= Signed Package headers TAR =
added since firmware 3.56


contains TAR'ed collection of all signed PKG headers
Added since firmware 3.56. Contains the TAR'ed collection of all SPKG headers.


For decrypt them we need to use spkg keyset (for 3.56+ firmwares)
== Decryption ==


=== History ===
To decrypt it you need to use spkg keyset.
The very first(early) 4.xx cfw were only installable over 3.55 because they were not having new spkg.
 
spkg is suppose to be created newly.the most easiest way for now is that you get metadata of your new pkg and decryp,then encrypt with spkg keys.the reason for cfw not installable over any ofw is that we dont have spkg private keys.ps3 verifies it on both, xmb and recovery mode.even if xmb makes it good, it will fail when installation screens pops up.more info on what and how to decrypt metainfo, refer here:
== History ==
http://www.psdevwiki.com/ps3/SELF_File_Format_and_Decryption
 
The very first (early) 4.xx CFWs were only installable over 3.55 because they were not having new spkg.
 
spkg is supposed to be created newly.
 
The easiest way for now is that you get Certification of your new spkg and decrypt it, then encrypt with spkg keys.
 
The reason why CFW is not installable over any OFW is that we dont have spkg private keys.
 
PS3 verifies it on both xmb and recovery mode. Even if xmb makes it good, it will fail when installation screens pops up.
 
For more info on CF encryption, refer [[Certified File|here]].
 
== Example ==


=== 3.56 CEX/Retail spkg_hdr.tar content ===
=== 3.56 CEX/Retail spkg_hdr.tar content ===
<pre>
  BDIT_FIRMWARE_PACKAGE.pkg.spkg_hdr.1
  BDIT_FIRMWARE_PACKAGE.pkg.spkg_hdr.1
  BDPT_FIRMWARE_PACKAGE_301R.pkg.spkg_hdr.1
  BDPT_FIRMWARE_PACKAGE_301R.pkg.spkg_hdr.1
Line 54: Line 68:
  SYS_CON_FIRMWARE_S1_00010002083E0832.pkg.spkg_hdr.1
  SYS_CON_FIRMWARE_S1_00010002083E0832.pkg.spkg_hdr.1
  UPL.xml.pkg.spkg_hdr.1
  UPL.xml.pkg.spkg_hdr.1
</pre>
= SPKG header =
It is a [[Certified File]] header.
== Location ==
spkg_hdr.tar -> *.pkg.spkg_hdr.1
== Structure ==
To document.
== Example ==


==== example ====
{| class="wikitable"
{| class="wikitable"
|-
|-
Line 63: Line 91:


00000000  53 43 45 00 00 00 00 02 00 00 00 03 00 00 00 00  SCE.............
00000000  53 43 45 00 00 00 00 02 00 00 00 03 00 00 00 00  SCE.............
00000010  00 00 00 00 00 00 02 80 00 00 00 00 00 1E 01 10  .......€........
00000010  00 00 00 00 00 00 02 80 00 00 00 00 00 1E 01 10  .......€........</pre>
00000020 - 0000027F  Signed Header data</pre>
|-
|}
|}


==== structure ====
== Tools ==
{|class="wikitable"
|-
! Address !! Length !! Value !! Description
|-
| 0x0 || 0x4 || 0x53434500 / ASCII:SCE. || Magic Header
|-
| 0x4 || 0x4 || 0x2 || Version
|-
| 0x8 || 0x2 || 0x0 || SDK type?
|-
| 0x8 || 0x4 || 0x3 || SCE header type; pkg
|-
| 0xC || 0x4 || 0x0 || Meta offset
|-
| 0x10 || 0x8 || 0x280 || Size of sce_shdr + sizeof meta_shdr
|-
| 0x18 || 0x8 || 0x1E0110 || content_size_real
|-
|}


== Tools ==
*[[http://www.mirrorcreator.com/files/1KDUUGFL/spkg_tool.tar.gz_links|spkg (linux/win)]]
*[[http://www.mirrorcreator.com/files/1KDUUGFL/spkg_tool.tar.gz_links|spkg (linux/win)]]




related: [[PKG files]]
{{Custom Firmware}}
 
<noinclude>[[Category:Main]]</noinclude>
 
{{Firmware}}<noinclude>[[Category:Main]]</noinclude>

Latest revision as of 17:07, 28 December 2019

Signed Package headers TAR[edit | edit source]

Added since firmware 3.56. Contains the TAR'ed collection of all SPKG headers.

Decryption[edit | edit source]

To decrypt it you need to use spkg keyset.

History[edit | edit source]

The very first (early) 4.xx CFWs were only installable over 3.55 because they were not having new spkg.

spkg is supposed to be created newly.

The easiest way for now is that you get Certification of your new spkg and decrypt it, then encrypt with spkg keys.

The reason why CFW is not installable over any OFW is that we dont have spkg private keys.

PS3 verifies it on both xmb and recovery mode. Even if xmb makes it good, it will fail when installation screens pops up.

For more info on CF encryption, refer here.

Example[edit | edit source]

3.56 CEX/Retail spkg_hdr.tar content[edit | edit source]

 BDIT_FIRMWARE_PACKAGE.pkg.spkg_hdr.1
 BDPT_FIRMWARE_PACKAGE_301R.pkg.spkg_hdr.1
 BDPT_FIRMWARE_PACKAGE_302R.pkg.spkg_hdr.1
 BDPT_FIRMWARE_PACKAGE_303R.pkg.spkg_hdr.1
 BDPT_FIRMWARE_PACKAGE_304R.pkg.spkg_hdr.1
 BDPT_FIRMWARE_PACKAGE_306R.pkg.spkg_hdr.1
 BDPT_FIRMWARE_PACKAGE_308R.pkg.spkg_hdr.1
 BLUETOOTH_FIRMWARE.pkg.spkg_hdr.1
 CORE_OS_PACKAGE.pkg.spkg_hdr.1
 dev_flash_000.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_001.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_002.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_003.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_004.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_005.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_006.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_007.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_008.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_009.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_010.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_011.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_012.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_013.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_014.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_015.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_016.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_017.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_018.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_019.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_020.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash_021.tar.aa.2011_01_25_032219.spkg_hdr.1
 dev_flash3_022.tar.aa.2011_01_25_032219.spkg_hdr.1
 MULTI_CARD_FIRMWARE.pkg.spkg_hdr.1
 SYS_CON_FIRMWARE_01000006.pkg.spkg_hdr.1
 SYS_CON_FIRMWARE_01010303.pkg.spkg_hdr.1
 SYS_CON_FIRMWARE_01020302.pkg.spkg_hdr.1
 SYS_CON_FIRMWARE_01030302.pkg.spkg_hdr.1
 SYS_CON_FIRMWARE_01040402.pkg.spkg_hdr.1
 SYS_CON_FIRMWARE_01050002.pkg.spkg_hdr.1
 SYS_CON_FIRMWARE_01050101.pkg.spkg_hdr.1
 SYS_CON_FIRMWARE_S1_00010002083E0832.pkg.spkg_hdr.1
 UPL.xml.pkg.spkg_hdr.1

SPKG header[edit | edit source]

It is a Certified File header.

Location[edit | edit source]

spkg_hdr.tar -> *.pkg.spkg_hdr.1

Structure[edit | edit source]

To document.

Example[edit | edit source]

BDIT_FIRMWARE_PACKAGE.pkg.spkg_hdr.1
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  53 43 45 00 00 00 00 02 00 00 00 03 00 00 00 00  SCE.............
00000010  00 00 00 00 00 00 02 80 00 00 00 00 00 1E 01 10  .......€........

Tools[edit | edit source]