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

The exfat partion can not decrypt #129

Open
CHNWangXi opened this issue Aug 29, 2024 · 6 comments
Open

The exfat partion can not decrypt #129

CHNWangXi opened this issue Aug 29, 2024 · 6 comments

Comments

@CHNWangXi
Copy link

rt

@impeeza
Copy link

impeeza commented Aug 29, 2024

¿?

@CHNWangXi
Copy link
Author

¿?

Now the USER partition is in exfat format, which is not supported by nxnandmanager.

@impeeza
Copy link

impeeza commented Sep 6, 2024

Seriously? I can swear the USER and SYSTEM partitions have FAT32 format because the bootloader have not implemented ExFAT, only HOS have the (bugged) driver for ExFAT.

are you telling me The ninjas now are formatting the USER partition as ExFAT?

@CHNWangXi
Copy link
Author

Previously, I wanted to export the archived data of an Atmosphere system. However, I found that the system partition can be decrypted while the user partition cannot. Then I checked the partition format and discovered that it was actually in exfat format. I changed it to fat32 format, but still couldn't read it. Later, I debugged the code and found that it was a problem with the value of magic_off. After I modified the value of magic_off, it could be read, but I don't know the specific reason.

@CHNWangXi
Copy link
Author

屏幕截图 2024-09-19 090400
屏幕截图 2024-09-19 090348

@CHNRoyWang
Copy link

I think I have found the reason. My machine is mounted to a Windows computer through hacdiskmount. Then, after formatting, a new system is created. Then I created a virtual system based on this system. Since the formatting is operated on Windows, the information of each partition contains Windows partition information, such as the MSDOS-like mark. Therefore, it is different from the partition table information native to the Switch, resulting in the inability of nxnandmanager to recognize it and thus unable to parse it.

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

3 participants