So do you have an updated batch/pack or is 0.2 that i have the latest?... AND IT WORKS!!!
Decrypt9 now includes two new features (four, actually, because everything is available for SysNAND & EmuNAND), one for dumping the H&S app, the other for injecting it. You need to compile from source, there's no binary release yet. And I suggest you use my last batch script to generate the inject .app (yup, .tmd / .xorpads not required!), because the .app to inject needs to be the exact same size as the original H&S app (that requirement will most likely be removed later), and I'm not sure if @Syphurith's script makes sure of that.
I will most likely refine some of how this works now. And, btw, we can easily inject to other system apps, too, but I'm unsure if that would be a good idea.
Now, although the Decrypt9 way might be the more noob friendly in the long run, we still need @Syphurith's script - because only with Syphuriths method, the .app to inject can be bigger than the original H&S app (that would never work in Decrypt9). If @Shadowtrance makes that GUI, it best includes both ways (with / without D9).
Advantages of the Decrypt9 method:
@Syphurith, could you add the Decrypt9 method to your nodeJS script (as an alternative)? It is the same as the other one, just with an already decrypted hs.app, no .tmd and no xorpads.
- Faster, needs only 3 steps (dump hs.app via D9, create inject app on PC, inject hs.app via D9).
- You only need to handle the .app file, no .tmd or .xorpads.
- Less room for error, much more noob friendly.
- Also, safer. Injecting files into FAT images using tools like OSFmount might lead to fragmentation, which in turn might lead to unexpected results. With Decrypt9 that will never happen, as it will leave everything untouched but the actual files space.
And how do we handle the n3ds version having 2 files? Just ignore the 2nd one like i did when i did it manually earlier i guess?
Last edited by Shadowtrance,