Homebrew WIP 4NXCI Open-Source *.XCI to *.NSP Converter

[OperationNT]

It seems that it fails when the XCI contains an NCA file which exceeds 4 GB (Dragon Quest Builder worked, BotW failed, Disgaea 5 failed). When it fails, I get an error "Failed to read file!" after the big NCA patching step.

But in the end, I didn't manage to install the NSP I got: with DevMenu, it stops at the end and TinFoil says it cannot find an entrypoint at the begining.

 

[datahoarder]

It seems that it fails when the XCI contains an NCA file which exceeds 4 GB (Dragon Quest Builder worked, BotW failed, Disgaea 5 failed). When it fails, I get an error "Failed to read file!" after the big NCA patching step.

But in the end, I didn't manage to install the NSP I got: with DevMenu, it stops at the end and TinFoil says it cannot find an entrypoint at the begining.

I think the ticket isn't being generated correctly, but also did you try changing the dev flag for the ticket as I suggested a few posts ago?

 

[D4rkelton]

Seems to only work on games with smaller filesizes. The Binding of Isaac (1.5 GB) was converted sucessfully, while bigger games stopped after creating an NCA. Also is it normal that the games shrink to like 1/3 of their filesizes? TBOI ended up with 580 MB.

 

[hippy dave]

Was really happy to see this tool earlier today, thanks to the author! Hopefully you'll figure out why it doesn't work for some games.
Worked perfectly with the first game I tried tho, Flashback. There's a snipli link called flashback if anyone's interested.

 

[XC-3730C]

Was really happy to see this tool earlier today, thanks to the author! Hopefully you'll figure out why it doesn't work for some games.
Worked perfectly with the first game I tried tho, Flashback. There's a snipli link called flashback if anyone's interested.

I'm interested. Flashback and Wild Guns is what I wanna convert to NSP

Sent from my SM-G955U using Tapatalk

 

[Vorde]

Seems to only work on games with smaller filesizes. The Binding of Isaac (1.5 GB) was converted sucessfully, while bigger games stopped after creating an NCA. Also is it normal that the games shrink to like 1/3 of their filesizes? TBOI ended up with 580 MB.

I believe that the XCI files are an exact 1:1 image of the dumped ROM, so any padding added to the game to fill up the whole chip would likely be on there. When converted to an NSP, it's likely removing said padding. This is speculation though, while I don't know enough about it to know 100% Also I'm hoping it works with larger games, as I'm needing to get this done for Odyssey

 

[hippy dave]

Also I built it for MacOS if anyone wants it, still needs keys.dat

e: newer version here.

 

[ScarletDreamz]

All saves and data associated with games are stored on your switch and sent to nintendo when playing online, using eShop, etc.
An emuNAND would be a different storage this data is written to and if you never connect online with that one, no data should tell nintendo that you use a softmod to do whatever you like.

You do know that an emunand, its an exact copy of your NAND? if by some reason you got banned on emunand, you will get banned on your nand. most likely.

 

[Deleted User]

You do know that an emunand, its an exact copy of your NAND? if by some reason you got banned on emunand, you will get banned on your nand. most likely.

Yes, but If, say something goes wrong you can isolate your emunand to being offline only, thus saving any potential ban.

Then with your "clean" sysnand, you can go online, as your emunand was offline and error reporting was impossible.

 

[diablodb]

Y try to convert Octopath Traveler and only decryt no convert to nsp.Help

 

[Nazosan]

Because homebrew is prone to corrupting the SD card when using exFAT due to its lack of file jounaling support. That's why RetroNX heavily recommends against it and lakka basically doesn't support it.

FAT32 lacks journalization -- in fact, since it's just a very basic extension of FAT16 which in turn is an extension of FAT12 it actually predates journalization -- and is even less robust than exFAT. exFAT is a more modern OS designed with removable media in mind so is actually more tolerant overall. FAT32 also has more limitations on file structures and etc, though that probably won't come into play here. It's still not journalized, but it's the best you're ever going to get on the Switch as I don't think they'll ever do anything like NTFS (which is really horrible for removable media.) Actually, this may all be on purpose. Journalization has advantages in general but is actually often a bad idea for things like this for quite a number of reasons (data alignment, more frequent writes stressing the cells more, more overhead for the OS and reduced performance overall where bandwidth is limited as it is here, and so on.)

The ONLY reason you'd want splitting is if you don't have the exFAT "update" (really just enabling a built-in support via license.) I don't know if there is an easier way to modify your system to enable exFAT than the guide I originally read but it definitely requires a few hoops to jump through. Most people will just tell you "go ahead and update," but some people want to hold out on older firmwares in the hopes that someday a MenuHax or similar sort of thing will happen (though it may be that the thing that you'd most likely use for a software implementation is probably still about as many hoops to jump through as RCM is anyway.) So basically that is the only reason at all anyone could have to want to not do exFAT. (But even then, like I said, there is a non-update method of getting that license activated, it just isn't easy.)

Actually, other than the splitting XCI actually is more disadvantageous than anything else. It's only supported in one thing at this time and would always require you to go through a special loader instead of just simply selecting a game from your home screen. Presumably someday Nintendo will get around to implementing some basic organization like the folders and icon resizing and etc the 3DS does too, but XCIs will always have to be managed by the loader (and in my experience with the 3DS at least it seems like the coders doing loader for that sort of thing apparently couldn't care less if they make it painful for the user. At least it's not as bad as Sky3DS's method though I guess.) Not to mention the fact that was already brought up before that XCI only works in one commercial implementation of questionable ethics (yeah, I know, "honor among thieves" and all, but IMO they have crossed several lines that are just not good for the scene at all) whereas NSP works not only in that but in everything else too (including just a very basic sigpatched stock OS without even a CFW once the NSP is actually installed.)

give me the name of xcis that don't convert to nsp
btw failure of converting multi rev cards is a known issue
ps: enc_header_key is not important, just remove it from your keyset file

I'm trying to convert PriPara (プリパラ.)

 

[sj33]

^The main reason for people sticking with FAT32 right now is file corruption caused by exFAT when using homebrew. It is most notable when using RetroNX or Lakka, neither of which are going to officially support exFAT anytime soon.

 

[peteruk]

Is the developer of this app a member here ? It would be nice if we could feedback the issues surrounding files over 4GB spitting out NCA's instead of fully repacked NSP files

 

[M7L7NK7]

Is the developer of this app a member here ? It would be nice if we could feedback the issues surrounding files over 4GB spitting out NCA's instead of fully repacked NSP files

They posted a few pages back asking what games aren't working

 

[peteruk]

They posted a few pages back asking what games aren't working

ah right, I didn't realise that was the dev - thanks for that

pretty sure I replied to them

it's a useful app for games which didn't get a digital release OR keys are currently unknown for, fingers crossed they're able to bring a fix for us

 

[Dean_]

I found out some games which are relatively larger (>4GB maybe?) cannot be converted using the provided binary (x86). But those can be converted using linux binary (posted on issues @ github). Maybe x86-related problem..

 

[tiliarou]

I found out some games which are relatively larger (>4GB maybe?) cannot be converted using the provided binary (x86). But those can be converted using linux binary (posted on issues @ github). Maybe x86-related problem..

Interesting findings. Did you post on the github as well in the issue mentioning large files ?

 

[peteruk]

Interesting findings. Did you post on the github as well in the issue mentioning large files ?

Looks like someone else already has

 

[Wierd_w]

Sounds like an "out of memory" problem on 32bit hardware. (CPU cannot address more than 4gb of total address space, and so cannot handle that much data in memory all at once.)

Sounds like the author needs to either 1) read in smaller chunks, and process those sequentially or 2) Make 64bit a requirement, and state how much RAM you will need.

 

[The-4n]

new build is out
solves large file size problem