U need to generate that file to dump the xorpads its a py script for pc drop the rom onto the py script then place that file on the root of the 3dss sd card
you need to install Python v2.7 first.
Look inside the "scripts" folder. Drag and drop your rom onto "ncchinfo_gen.py" and a ncchinfo.bin will be generated. Copy that file to the SD card.
Last edited by piratesephiroth,
I should've been clearer. It's for my NAND region swap, not a game dump.
Xorpad Generator > CTRNAND
(there's that EmuNAND option there, I dunno why though... I always used the same xorpad for both)
Last edited by piratesephiroth,
D
Deleted-236924
Guest
The 3DS freezes when it's starting. Usually while it's displaying those numbers.
BootCtr doesn't give me that problem.
Do you mean when your 3ds initially boots, before the bottom screen turns yellow,pink,etc.? Then that would be a menuhax problem. Also, use the latest version or CtrBootManager, since I updated, I have a 100% boot rate in CtrBootManager, altough it fails sometimes in menuhax boot (Freezes on yellow screen).
If you want that now, check my source code on Github and compile it yourself. Or wait for a release by me
.Guess that already has been answered. Decrypt9 decrypts those just fine, the problem is in GW. Nothing much that can be done about that. And f.... annoying for GW users. You also don't have any way of displaying manuals from (formerly) seed encrypted games (try it if you don't believe it)
Um... EmuNAND option for XORpads? Not in my build of of Decrypt9
. If you mean EmuNAND Options -> Partition Dump -> CTRNAND, that dumps the decrypted partition, not a XORpad. And yes, of course the XORpad is the same for EmuNAND and SysNAND!
Finally, a proper release again. And possibly the last one this year. Here's what's new:
Scrolling and screenshots for debug output work only after the processing is finished, not while Decrypt9 processes the current operation. The improved title detection means that H&S can now be injected on basically any 3DS, except for a few isolated cases were GW has royally messed up the SysNAND.
For the updatesave read here and the previous pages, too. Also check out my new EmuNAND9Tool - testers here know that part of that was initially in unreleased Decrypt9WIP.
- Vastly improved title detection routines for H&S injection
- Different unlock sequences for SysNAND / EmuNAND writing for additional safety
- Hidden batch screenshot feature included (left/right + X)
- Show total SD size and EmuNAND type in main menu
- Allow dumping/injecting the updatesave file
- Added scrolling and screenshot (X button) feature for debug output
- Added code for theming Decrypt9
- Added various improvements and additional safety clamps
- Improved the code structure
Scrolling and screenshots for debug output work only after the processing is finished, not while Decrypt9 processes the current operation. The improved title detection means that H&S can now be injected on basically any 3DS, except for a few isolated cases were GW has royally messed up the SysNAND.
For the updatesave read here and the previous pages, too. Also check out my new EmuNAND9Tool - testers here know that part of that was initially in unreleased Decrypt9WIP.
I'll have to get around to updating the UI version at some point now i guess.
Thanks for the new release. Also, is there a way to power off without having to restart?In previous releases SELECT was used for that, but now is used to Unmount SD (Awesome feature BTW).
DPad Left + Start = PowerOff
(I always add this to the main.c before I compile so I remember the key-code)
Code:
DrawStringF(menublock_x0, menublock_y1 + 20, top_screen, "SELECT : Unmount SD");
DrawStringF(menublock_x0, menublock_y1 + 30, top_screen, "START : Reboot");
DrawStringF(menublock_x0, menublock_y1 + 40, top_screen, "DPad_Left+START : Shutdown");
Last edited by Datalogger,
Already fixed that, take a look at my Github. By the way, the screenshot feature proves useful again!
@everyone: Are there any features that you would like to see in Decrypt9? Or, possibly, something that needs fixing or should work differently? This is what I have planned at the moment:
- Injecting into any sysapp instead of just H&S (unsure) - this is actually not difficult to do, but bears a lot of bricking potential for noobs. Also, it might be questionable if users would actually use this. There are useless system apps other than H&S, but those might be somehow ingrained more deeply in the system. Also, do we need to replace more than one sysapp to inject to? I also thought about using this for simple mods of, f.e. the settings app or the like.
- Provide a simple file name selection for dump & inject features - allowing the user to decide the filename for the file to dump or inject. Might make things a lot more complicated for the users. If not this, I'd need at least a way of fixing the current name scheming / behaviour. Think about ticket.db for SysNAND and ticket_emu.db for EmuNAND. When injecting to the EmuNAND, which of the two should be chosen? On the other hand, you want different names, so that you can dump both (SysNAND / EmuNAND) at once. Ideas for that are welcome.
- Vastly improve the SD decryptor feature - the way this works now, you have to copy the files to decrypt to a certain folder, and also keep the correct folder strcuture. This is a feat not even easily accomplished with CTRXplorer. The way it should work is, let the user select what to decrypt, then copy that automagically to the work folder and decrypt it from there. Same for the SD xorpad generator.
- Add a NDS .tad decryptor feature (or NDS SD decryptor) (unsure) - as requested by @zoogie . Problem here is: the DSiBrew article doesn't provide enough information to actually decrypt it, and I don't have data to test on (the test data must be tested on the same 3DS they cam from). If at least test data was available, decryption could be tested with a handful of different configurations until the correct one is found (unsure if that is doable, too).
- Finally add an actually useful readme - self explaining I guess. And help for that would be greatly appreciated.
Last edited by d0k3,
wd it be possible to add mset support similar to your other tool emuNAND9 tool....wd be appreciated.....and loads dead easily ......course if its possible.......but great tool and thank you for it.....Already fixed that, take a look at my Github. By the way, the screenshot proves useful again!
@everyone: Are there any features that you would like to see in Decrypt9? Or, possibly, something that needs fixing or should work differently? This is what I have planned at the moment:
Feedback on my ideas and maybe other ideas are appreciated!
- Injecting into any sysapp instead of just H&S (unsure) - this is actually not difficult to do, but bears a lot of bricking potential for noobs. Also, it might be questionable if users would actually use this. There are useless system apps other than H&S, but those might be somehow ingrained more deeply in the system. Also, do we need to replace more than one sysapp to inject to? I also thought about using this for simple mods of, f.e. the settings app or the like.
- Provide a simple file name selection for dump & inject features - allowing the user to decide the filename for the file to dump or inject. Might make things a lot more complicated for the users. If not this, I'd need at least a way of fixing the current name scheming / behaviour. Think about ticket.db for SysNAND and ticket_emu.db for EmuNAND. When injecting to the EmuNAND, which of the two should be chosen? On the other hand, you want different names, so that you can dump both (SysNAND / EmuNAND) at once. Ideas for that are welcome.
- Vastly improve the SD decryptor feature - the way this works now, you have to copy the files to decrypt to a certain folder, and also keep the correct folder strcuture. This is a feat not even easily accomplished with CTRXplorer. The way it should work is, let the user select what to decrypt, then copy that automagically to the work folder and decrypt it from there. Same for the SD xorpad generator.
- Add a NDS .tad decryptor feature (or NDS SD decryptor) (unsure) - as requested by @zoogie . Problem here is: the DSiBrew article doesn't provide enough information to actually decrypt it, and I don't have data to test on (the test data must be tested on the same 3DS they cam from). If at least test data was available, decryption could be tested with a handful of different configurations until the correct one is found (unsure if that is doable, too).
- Finally add an actually useful readme - self explaining I guess. And help for that would be greatly appreciated.
That is already in there... for a long time
. Just download from the opening post.Similar threads
-
Xdqwerty
what are you looking at? -
K3Nv2
- S salazarcosplay