Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[3DS] Content header magic doesn't always start with 0x80 #3

Open
DaniElectra opened this issue Jan 21, 2023 · 1 comment
Open

[3DS] Content header magic doesn't always start with 0x80 #3

DaniElectra opened this issue Jan 21, 2023 · 1 comment

Comments

@DaniElectra
Copy link
Member

DaniElectra commented Jan 21, 2023

Most BOSS data (usually game data) starts with 0x80 as the CONTENT_HEADER_MAGIC. However, this isn't always the case.

There are some BOSS files (usually game config and news) that starts with 0x00, instead of 0x80. It is unknown how this value affects the BOSS data though

@DaniElectra
Copy link
Member Author

DaniElectra commented Feb 9, 2025

I have done more research on this and I think that value is a flag related with marking the content as arrived or not. If the flag is not set, the sysmodule checks if the BOSS content was downloaded by a privileged session (BOSSP:InitializeSessionPrivileged was previously used for the belonging title). If that is the case, it marks the "arrived" flag in the application entry in the BOSS savedata.

If the flag is set though, this check is skipped, and always marks the "arrived" flag.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant