-
Notifications
You must be signed in to change notification settings - Fork 2
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
extraction is not achieved #7
Comments
|
Hello how are you ?? I only managed to unlock the def. The command that appeared above -p=/def,/manifest.sii indicates that it does not work. and it doesn't work when /manifest.sii is left blank where the arrow indicates cuts the command completely and in what is an example in the sound folder it worked on 1 bus and on the other it didn't work. here is an example in a single image https://drive.google.com/file/d/1vhIGMbg13fdNi1DNmubZCmLXhKU6g2GL/view?usp=sharing The link I attached is the mod (bus) that does not work |
TIL that commas have a special meaning in PowerShell. I've never used it so I didn't know about that. Wrap the parameter in single quotes:
The extractor can't find I'm a bit out of my depth here because I don't actually know how the sound system works, but searching for definition files containing "sound" in their name yields the following:
Starting with the first, we find the following paths:
And in those files, we find this path, which can be extracted:
Along with the accompanying And so on, and so forth. You get the idea. |
The first field you highlighted is the salt. The second field is the offset of the entry table. Nothing about this is new in any way, and nothing is being "reinforced" or "blocked" here. |
Hello. I tried to do the extraction but it asks me to use --raw when using it, it still doesn't allow me to use -p, -a,
... I don't know if giving up this hashfs thing for someone who is basic in computing is too complicated. You have to know a lot about cybersecurity to specify the issue of hashes and especially with hexadecimal code.
The text was updated successfully, but these errors were encountered: