Homebrew NXDumpTool error

  • Thread starter Thread starter Ebojo
  • Start date Start date
  • Views Views 40,458
  • Replies Replies 28

Ebojo

Member
Newcomer
Joined
Jul 26, 2019
Messages
13
Reaction score
2
Trophies
0
Age
38
XP
141
Country
United States
I am able to dumb base application NSP without any issues for all games. However, I am getting an error when trying to dump any bundled NSP.

"Error: invalid magic word for Program NCA section #0 PFS0 partition! Wrong KAEK? (0x490BF3E0)"

Any help would be greatly appreciated.
 
I am not sure if this would have anything to do with it, but before installing Atmosphere, I never had an sd card in my switch, so any game updates would have been saved directly do the internal memory. Could that possibly cause an issue like this?
 
If you read the notes for NXdumptool it states you need prod.keys even to dump installed titles
DEEDF6CE-98E9-4E24-8173-82C4201DCC33.jpeg
 
  • Like
Reactions: DarkMatterCore
dudes dont talk shit if you know nothing. How would he be able to dump the base game but not its update if he would not have the Keys...
The same happened to me right now. Dumped all Keys und dumped all of my games and updates flawlesly. But as i tried dumping the Update file of pokemon Lets Go it gave me the same error...
All other games, updates and DLCs worked before...
 
same her, cannot dump a bundled update, unsure where to get that on the web...
it IS asking for prog.ketys at "sdmc/:...." so unsure what PARTITION that might be ( i have 2 on the sd card, using atmosphere and its emuMMC)
 
In that case, I may have to add an exception for Pokemon Let's Go updates. They may use a different Program NCA layout than the common one.

It's important to report this kind of stuff in the official nxdumptool thread or in its GitHub repository. Otherwise, it's impossible for me to know if anything goes wrong - I can't test everything on my own, sadly.

@Ebojo @Razor1993 @xakamd If the error can still be reproduced in v1.1.7 (latest one atm) and any of you guys is willing to help me by running some test builds, please get in touch with me. I'd be more than glad to help.
 
Last edited by DarkMatterCore,
  • Like
Reactions: Razor1993 and satel
In that case, I may have to add an exception for Pokemon Let's Go updates. They may use a different Program NCA layout than the common one.

It's important to report this kind of stuff in the official nxdumptool thread or in its GitHub repository. Otherwise, it's impossible for me to know if anything goes wrong - I can't test everything on my own, sadly.

@Ebojo @Razor1993 @xakamd If the error can still be reproduced in v1.1.7 (latest one atm) and any of you guys is willing to help me by running some test builds, please get in touch with me. I'd be more than glad to help.

yes i have the same error in 1.1.7 trying to dump Luigi mansion 3 update,feel free to send me newer builds to test. thanks
 
  • Like
Reactions: DarkMatterCore
yes i have the same error in 1.1.7 trying to dump Luigi mansion 3 update,feel free to send me newer builds to test. thanks

Alright, thanks for reporting the issue. I'll send you a test build as soon as I get back home.

In the time being, can you please try running the latest version of Lockpick_RCM (grab it from GitHub) and dumping the update again? Just to be completely sure.
 
  • Like
Reactions: satel
Alright, thanks for reporting the issue. I'll send you a test build as soon as I get back home.

In the time being, can you please try running the latest version of Lockpick_RCM (grab it from GitHub) and dumping the update again? Just to be completely sure.

i just did to dump the prod.keys & still the same error
 
  • Like
Reactions: DarkMatterCore
thanks but still same error,unable to find fs index from key

Oh, I thought you were talking about the "Wrong KAEK" error the other users from this thread mentioned. You're experimenting a whole different error altogether. Please PM me, I'll further instruct you on how to help me debug it.
 
@Ebojo @Razor1993 @xakamd @satel Are you guys using an emuMMC? If so, is your emuMMC FW version different than your sysMMC FW version?
Hi, cool that you are Bugfixing this.
Yeah I am using EmuMMC with the latest firmware and Kosmos Atmosphere.
SysMMC and EmuMMC had the same latest version(9.0 or something).
Dumped all Keys with the uptodate version of Lockpick etc. like I have said everything else worked. Only on 2 TitleUpdates It gave me that error message.
 
Hi, cool that you are Bugfixing this.
Yeah I am using EmuMMC with the latest firmware and Kosmos Atmosphere.
SysMMC and EmuMMC had the same latest version(9.0 or something).
Dumped all Keys with the uptodate version of Lockpick etc. like I have said everything else worked. Only on 2 TitleUpdates It gave me that error message.

Please try to dump any of those updates using the build I previously shared in this thread, and send me the "program_nca_header.bin" file from your SD card root afterwards. That should help me further debug this issue.

Just to be clear, you have to trigger the error on purpose using that build. That's how you'll get the file.
 
Last edited by DarkMatterCore,
  • Like
Reactions: satel
The bug reported by @satel has been fixed.

@Ebojo @Razor1993 @xakamd Here's another test build: https://mega.nz/#!cZ4S2SaJ!hDan4qsjOECZymKmf4dDz8yzCIkCvSdPsOo83z-MKm4. Please try this one instead. Just trigger the dump error on purpose and look for the "program_nca_header.bin" file in your SD card root.

Still the same Error if I try dumping Lets Go Pikachu Update:
https://i.ibb.co/kQmvbZr/2019111219291400-4-E3-C1-F870-D1997912-EA61-E1657-E1-AE11.jpg

and here proof that I dumped the Key files: https://i.ibb.co/TgKCw1t/2019111219294600-4-E3-C1-F870-D1997912-EA61-E1657-E1-AE11.jpg

and here is the header.bin file: https://mega.nz/#!mt1VnKaD!DgfKtXZGokzPX4RoOotj8loFo9aClaKtwLecm6shG4I
 
  • Like
Reactions: DarkMatterCore

Site & Scene News

Popular threads in this forum