
Umm D9 doesn't unpack anything. that is done on pc alone.Question:
How to use Decrypt9 to unpack things?
NCCH padgen can't generate RomFS XORPAD which is required for unpacking .3DS.
NCCH Decrypter outputs only a single .3DS file which makes me unable to do anything further.
Decrypt9 cannot generate RomFS XORPAD but the old method's tool can (which requires SysNAND 4.X and very very easy to freeze)Umm D9 doesn't unpack anything. that is done on pc alone.
And to unpack games you have 2 options, directly decrypt the .3ds (or .cia) and then unpack it with ctrtool etc on pc. OR generate xorpads and do it that way on pc (which is the long way).

Yes it can. It can generate all xorpads if you give it a complete ncchinfo.bin.Decrypt9 cannot generate RomFS XORPAD but the old method's tool can (which requires SysNAND 4.X and very very easy to freeze)
Then the last hope is decrypted single .3DS file but how do I use it?
I tried using CTRTool to extract the RomFS and mounted it with OSFMount but it didn't work.
Finally I got it worked.Yes it can. It can generate all xorpads if you give it a complete ncchinfo.bin.
And you don't mount the romfs with ofsmount, that won't get you anywhere. You have to extract (unpack) the romfs etc with ctrtool. Which I'm not going to get into here as there's already plenty of info here on the forums about doing all that already.
ctrtool.exe -p --romfs=romfs.bin *.3ds
ctrtool.exe -t romfs --romfsdir=* RomFS.bin
With that old XORpad method, you simply would have had to use the ncchinfo_gen.py to generate the ncchinfo.bin. That's basically how it always has been done.Finally I got it worked.
(1) NCCH Decrypter -> output a single decrypted .3DS
(2) Make a .bat with thisand execute itCode:ctrtool.exe -p --romfs=romfs.bin *.3ds ctrtool.exe -t romfs --romfsdir=* RomFS.bin

Firm corruption (in one of the two, not both!) is completely normal with a9lh and is part of the exploit. That is also the reason why the NAND validator said it succeeded and did not fail.The nand backup tester said me that my firm1 is corrupted (I have a9hl) What wrong it is? Because my new3ds work fine.
Enviado desde mi DROID4 mediante Tapatalk
What would happen if both got corrupted?in one of the two, not both!
The validation would fail. Decrypt9 would also not let you restore that image anymore (unless you use 'forced').What would happen if both got corrupted?
The boot failure rate on N3DS with Brahma is an enigma we have not yet figured out. At times you get 10 succesful boots in sequence, thinking everything is fine now, and then you get 5 failures after each other.@d0k3 BTW I like that "blue screen" because it decreases the boot failure rate on my New3DS (Menuhax 2.2 -> CTRBootManager -> HBL -> D9)
Unfortunately it has been removed from current version![]()
Isn't shutdown start+left on dpad?@d0k3
It's possible to add a shutdown script in the WIP version too, not only the UI?
I don't like force the power off by holding the power button, and reboot for then a proper power off take time...

Same as Custom Firmware's splash screen.@d0k3
Real or just part of the April fools? If real how is this done?
- You can now display a logo on the bottom screen - just put d9logo.bin into your SD root or into /Decrypt9
Not possible in ARM9. Or I'd have to mess with I2C, which would mean danger.Would it be possible to not have Decrypt9 turn the bottom-screen's back-light on, sort of like how you can turn the bottom screen off when using the RetroArch emulators?
In fact, the full April fools changelog was real. To get that logo, just do (with imagemagick installed):@d0k3
Real or just part of the April fools? If real how is this done?
- You can now display a logo on the bottom screen - just put d9logo.bin into your SD root or into /Decrypt9
convert yourlogo.png -rotate 90 d9logo.bgr
ren d9logo.bgr d9logo.bin
Not possible in ARM9. Or I'd have to mess with I2C, which would mean danger.
Or I'd have to mess with I2C, which would mean danger.
which would mean danger.
mmm whatcha smeadanger.
