100
edits
Changes
no edit summary
:::The ExeFS contains only the ARM11 code and the banner. To know the offset of the ARM11 code you would need to scan the ExeFS for the file ".code".
:::The ExeFS contains only the ARM11 code and the banner. To know the offset of the ARM11 code you would need to scan the ExeFS for the file ".code".
:::As for the homebrew file format, I think it's a little too early for that. Whatever happens, happens. --[[User:Neimod|Neimod]] 23:12, 6 September 2011 (CEST)
:::As for the homebrew file format, I think it's a little too early for that. Whatever happens, happens. --[[User:Neimod|Neimod]] 23:12, 6 September 2011 (CEST)
::::Thanks, but please can you give me the parameters for your tool to decrypt the ExeFS and save it? The usage for that is a bit ununderstandable.--[[User:Lazymarek9614|Lazymarek9614]] 20:01, 7 September 2011 (CEST)
Hi Neimod, love your work! my question is: The extended header suppose to start right after the NCCH header so why there is twice the space? (extended header size is usually 1024 and plain region offset is usually 5*512 = 2560 -> 2048 after the end of the ncch) thanks. --[[User:Elisherer|Elisherer]] 11:46, 6 September 2011 (CEST)
Hi Neimod, love your work! my question is: The extended header suppose to start right after the NCCH header so why there is twice the space? (extended header size is usually 1024 and plain region offset is usually 5*512 = 2560 -> 2048 after the end of the ncch) thanks. --[[User:Elisherer|Elisherer]] 11:46, 6 September 2011 (CEST)