Yep, that's the one I'm using and I'm decrypting Japanese version of SMT4 (2GB).
It's been going for an hour now and it's only not at half...
Xor it with the rom first. Then use ctrtool to extract romfs.Kingston MicroSDHC 16GB, Class 10. In a SD adapter. It's definitely not the card besides now it's going well.
Okay, got myself the xorpad files, how do I go about opening them now exactly? ctrtool? Do I need to specify parameters or is just -x enough?
Has anyone messed with the genesis 3d classics vc to see if it's an emulator?
Somebody please give me a step by step tutorial since I can't comprehend this.
I used ctrKeyGen to generate ncchinfo.info which I then used to generate xorpad files on my 3DS with Gateway.
Then what do I do with those files? People keep throwing around terms "just xor it" as if I already know what it means.
I have no bloody idea what does it mean and I've been fighting with these tools for past few hours trying to figure it out and I just can't wrap my head around this XOR thing.
So please someone give me step by step intructions what do I do after getting the xorpad files.
Thanks, that helped me immensely, turns out I was doing everything properly just didn't realize the .xor output from 3DSExplorer was my decrypted file just with changed extension.
Is there any way at all to re-encrypt roms right now?
You mentioned earlier that an "easier" way of encrypting with 0 key will come soon, which made me wonder if a harder way exists now.
http://gbatemp.net/threads/release-romfs-generator.371770/#post-5107673Just got an email stating issue 19 (romfs generation) was closed!
https://github.com/3DSGuy/Project_CTR/issues/19
Anyone want to compile the new source? ( I would but I'm currently on mobile)
My "solution" was to build as CARD2 instead of CARD1Okay, I've managed to recompile a ROM, but I get the same "An error has occurred" as was posted a bit back. Now, I don't want to hear "My program can do that but I haven't released it because it's not ready yet" because that just sounds like an empty promise and I can't give two sh*ts about that tbh. Now, can someone either explain how I can fix this error, or provide a way of replacing files in a ROM without having to recompile it as I am sick of people saying "read the previous posts" or "we can do it but you can't".
An alternative solution is to replace the "Writable Address" offset at 0x200 with the one from the original dump.My "solution" was to build as CARD2 instead of CARD1
thanks for the heads upAn alternative solution is to replace the "Writable Address" offset at 0x200 with the one from the original dump.
Should also say that if the compiled version uses more bytes, you should edit this to be hex(total size/512) instead of the original version'sthanks for the heads up