Editing SLB2

Jump to navigation Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.

Latest revision Your text
Line 1: Line 1:
== Structure ==
== SLB2 structure ==


[[File:PS4 SLB PUP container format - SKFU.png|thumb|PS4 SLB PUP container format - SKFU]]
[[File:PS4 SLB PUP container format - SKFU.png|thumb|PS4 SLB PUP container format - SKFU]]
Line 6: Line 6:
/* SLB2 structure is little endian */
/* SLB2 structure is little endian */
   
   
struct SceSlb2Entry {
struct slb2_entry {
uint32_t fileStartSector;
uint32_t block_offset;
uint32_t fileSizeInByte;
uint32_t file_size;
uint32_t reserved[2]; // padding for alignment
uint32_t alignment[2];
char    fileName[32];
char    file_name[32];
} __attribute__((packed));
} __attribute__((packed));
   
   
struct SceSlb2Header {
struct slb2_header {
uint32_t magic; // "SLB2"
uint32_t magic;
uint32_t version; // ex: 1
uint32_t version;
uint32_t flags; // ex: 0
uint32_t flags;
uint32_t entryNum;
uint32_t file_count;
uint32_t sizeInSector;
uint32_t block_count;
uint32_t reserved[3]; // padding for alignment
uint32_t unk[3];
struct SceSlb2Entry entryList[0];
struct slb2_entry entry_list[0];
} __attribute__((packed));
} __attribute__((packed));
</source>
</source>
Line 39: Line 39:
* [https://github.com/yifanlu/slb2tools slb2tools] (yifan lu)
* [https://github.com/yifanlu/slb2tools slb2tools] (yifan lu)


== Usage ==


SLB2 files are parsed by many executables:
* PS4 [[Southbridge]] EMC IPL to extract C0028001 (EMC IPL) and C0020001 (EMC IPL information) from sflash0s0x32b (inactive partition).
== Other notes ==
It looks like newer (confirmed for OFW 7.55 and above) SLB2 files have some data between 0x200 and 0x270 which doesn't affect any unpacking tool but affects the unpacking on the PS4. The file gets recognised as corrupted if that data isn't there. This data is present in the `recovery` images but not in the `update` images.
-Other note
Newer updates seems to have  New data exactly before the start of the PS4UPDATE.PUP file
It has the same effect as the  one between 0x200 and 0x270
{{Software}}
{{Software}}
<noinclude>[[Category:Main]]</noinclude>
<noinclude>[[Category:Main]]</noinclude>
Please note that all contributions to PS4 Developer wiki are considered to be released under the GNU Free Documentation License 1.2 (see PS4 Developer wiki:Copyrights for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission!

To protect the wiki against automated edit spam, we kindly ask you to solve the following hCaptcha:

Cancel Editing help (opens in new window)