399
edits
Changes
Jump to navigation
Jump to search
Line 259:
Line 259: + + Line 269:
Line 271: + +
→Partitions: more on partitions and save filesystem...
* The u64 at 0x40 is an offset because if you summarize the hashtable's length and the partition's length you'll get sometimes less then this value. so it isn't the length of the total partition but an offset.
* The u64 at 0x40 is an offset because if you summarize the hashtable's length and the partition's length you'll get sometimes less then this value. so it isn't the length of the total partition but an offset.
* Every partition is preceded by a 0x1000 block which has a 0x108 long block whose perpose is still unknown.
The first partition starts at 0x2000. First comes the hashtable (usually start @ 0x40 into the partition) and then the filesystem.
The first partition starts at 0x2000. First comes the hashtable (usually start @ 0x40 into the partition) and then the filesystem.
Savefiles are stored on the FLASH in a custom filesystem called SAVE. SAVE has a header which describes where the various bits of the filesystem live.
Savefiles are stored on the FLASH in a custom filesystem called SAVE. SAVE has a header which describes where the various bits of the filesystem live.
* The SAVE filesystem works with a backup. There are two SAVE blocks inside the partition concatenated. It seems that the second is always the updated one...
Finding the file system file base:
Finding the file system file base: