I poked around a bit and was able to find a couple Develop nnrtld + nnSdkEn + glslc pairs (sdk rel 6.4.0 and 6.4.2) that seem to be close in size to those in the corrupt debug titles though, I couldn't find any exact matches, so I think they were using an internal build of the sdk (or Nintendo silently updated smth). But it probably doesn't matter, I can't imagine they'd change anything significant between silent/micro revisions.It's the more common thing thats corrupt. But in some titles, another thing is corrupt too. For example, in 01004b9000490003_000012c30000_Program.nca the "sdk" file is corrupt in addition to the "subsdk0" file.
I haven't thoroughly examined all the files of all the titles. I have just gone through as far as focusing on the subsdk0's as those are what happens to be corrupt with the debug versions. I can probably compile a better list of whats corrupt and what isn't if needed.
I'll take anything that gives a chance at making it boot. The dev version is clearly different, and offers more features. For one, it looks to have IMGUI options like Sloop. Probably not the same exact interface, but something. There is even a --ask argument that I suspect may allow the inclusion of more than 1 ROM with each game, and a menu selection among them. Rather than 1 game per title.
EDIT:
Corrupt files:
The things shown in orange in the OP do not have corrupt files, but instead something else that makes them not boot.
- 01004b9000490000_000017234000_Program.nca: subsdk0
- 01004b9000490001_0000070ac000_Program.nca: subsdk0
- 01004b9000490003_000012c30000_Program.nca: sdk
- 01004b9000490003_000012c30000_Program.nca: subsdk0
- 01004b9000490003_000008470000_Program.nca: subsdk0
- 01004b9000490004_00000356c000_Program.nca: subsdk0
- 01004b9000490005_000005cf0000_Program.nca: subsdk0
- 01004b9000490006_000013fec000_Program.nca: The nca itself seems bad.
- 01004b9000490006_000004930000_Program.nca: subsdk0
- 01004b9000490014_0000153a0000_Program.nca: subsdk0
EDIT2:
The corruption of the subsdk0's in the following two pairs are the same, fyi. As in, they are the same exact data.
for 0015 that can make sense, as its the same game probably recompiled with a fix. But for 0003 and 0004... not so much. They are different games, with different testing goals (Touch controls vs. normal controls).
&
- 01004b9000490003_000008470000_Program.nca: subsdk0
- 01004b9000490004_00000356c000_Program.nca: subsdk0
For 0002, there appears to be a string sanitization/localization error in the control.nacp. At a glance it would seem like corrupt data, but my experience finds it consistent with not converting the string format between Unicode/UTF-8 and such. But such a issue could certainly be the cause for a failure to work.
- 01004b9000490015_000006d44000_Program.nca: subsdk0
- 01004b9000490015_0000094b8000_Program.nca: subsdk0
Im not sure what the issue is with the first 0013 not booting, or what the issue is with the first 0006 nca not reading correctly.
Got anywhere I can send them over?
Also I checked the original dev unit dump and it does seem the scanner dumped everything correctly... so I guess subsdk0 being corrupt everywhere is just an unfortunate coincidence..?
Maybe that control is in Japanese?
Also I can extract the non-corrupt 006 fine, if that's what you mean?