Hacking FAQ: What CFW is best for me?

[chaoskagami]

so which cfw would be better because i got my 3ds modded by someone, so I don't really know the differences and what "a9lh" means?

Thank you for replying truly appreciate it.

You probably want Luma. It's easy to use and literally impossible to screw up.

 

[The Catboy]

so which cfw would be better because i got my 3ds modded by someone, so I don't really know the differences and what "a9lh" means?

Thank you for replying truly appreciate it.

The point of this thread really isn't for me to tell you which CFW is better, but to help as a study guide for you to determine which one works better best for you. I personally tested out all the CFW's before determining which one I enjoyed the most and settled on that one.

Hi"Crystal the Glaceon", may I pick your brain on what i should use for a cfw?
Currently I'm running Reinand and I like it, however I want to do "cro Editing" on Pk3ds like type modifications for making a custom ROM, however i read and experienced that CRO editing is only supported on Luma3ds. If so How can I change my cfw to luma from Reinand?

Thanks for creating this thread makes it easier for noob like me.

As far as I know, I believe all CFW's currently support that. But since I've never used that feature, I can't completely say. Anyone who know more, please chime in.

 

[chaoskagami]

The point of this thread really isn't for me to tell you which CFW is better, but to help as a study guide for you to determine which one works better best for you. I personally tested out all the CFW's before determining which one I enjoyed the most and settled on that one.

As far as I know, I believe all CFW's currently support that. But since I've never used that feature, I can't completely say. Anyone who know more, please chime in.

It requires a loader replacement, but the gist of the RO signature patch is that CROs are like dlls or shared objects. Pokemon makes use of them, and the signature patch on RO is a separate thing from the normal signature patch.

 

[The Catboy]

It requires a loader replacement, but the gist of the RO signature patch is that CROs are like dlls or shared objects. Pokemon makes use of them, and the signature patch on RO is a separate thing from the normal signature patch.

Ohh~~ that shinny/large Pokemon thing people were doing? I didn't know there was term for it. I learned something new today.

 

[chaoskagami]

Ohh~~ that shinny/large Pokemon thing people were doing? I didn't know there was term for it. I learned something new today.

You can't edit the starters on Pokemon without a RO patch, for example. But yeah. ;P

 

[The Catboy]

You can't edit the starters on Pokemon without a RO patch, for example. But yeah. ;P

I think CakesFW might be the only one to not have it (I can't find any logs on it.)

 

[chaoskagami]

I think CakesFW might be the only one to not have it (I can't find any logs on it.)

Cakes doesn't have it out-of-box, not without a loader module cake. @Wolfvak had one on github and so did I before developing corbenik.

 

[The Catboy]

Cakes doesn't have it out-of-box, not without a loader module cake. @Wolfvak had one on github and so did I before developing corbenik.

I learned a new, again!

 

[Izaya-Orihara]

The point of this thread really isn't for me to tell you which CFW is better, but to help as a study guide for you to determine which one works better best for you. I personally tested out all the CFW's before determining which one I enjoyed the most and settled on that one.

As far as I know, I believe all CFW's currently support that. But since I've never used that feature, I can't completely say. Anyone who know more, please chime in.

thanks for your quick reply.

--------------------- MERGED ---------------------------

You probably want Luma. It's easy to use and literally impossible to screw up.

Thanks for letting me know, otherwise I would've been posting and searching multiple posts. I truly appreciate how you said I can't screw it up makes it that much easier for a noob like me to attempt switching over myself. Otherwise I would have to pay a guy $60 think it would be safer so I wouldn't get my 3ds bricked.

Thank you so much.

 

[Wolfvak]

Cakes doesn't have it out-of-box, not without a loader module cake. @Wolfvak had one on github and so did I before developing corbenik.

Alright, I think I arrived a bit late to the party but whatever. This has been going on for a while now (over two months) and it got a bit stale, but after reading this post I decided to take a look at it and rework certain parts.

I dare to say that some parts of the latest commit were inspired by corbenik's fork, like the removal of IFile.

Anyways, here it is: https://github.com/Wolfvak/3ds_injector/releases/latest. @Crystal the Glaceon, might wanna link this in the OP or something.

 

[chaoskagami]

Alright, I think I arrived a bit late to the party but whatever. This has been going on for a while now (over two months) and it got a bit stale, but after reading this post I decided to take a look at it and rework certain parts.

I dare to say that some parts of the latest commit were inspired by corbenik's fork, like the removal of IFile.

Anyways, here it is: https://github.com/Wolfvak/3ds_injector/releases/latest. @Crystal the Glaceon, might wanna link this in the OP or something.

I was really surprised at the fact that removing IFile regained about two mediaunits at near zero cost, honestly.

Looks like you're actually missing the RO patch, btw (and this originates from Luma)

Spoiler: ro patch

case 0x0004013000003702LL: // RO
{
static const u8 sigCheckPattern[] = {
0x30, 0x40, 0x2D, 0xE9, 0x02
};
static const u8 sha256ChecksPattern1[] = {
0x30, 0x40, 0x2D, 0xE9, 0x24
};
static const u8 sha256ChecksPattern2[] = {
0xF8, 0x4F, 0x2D, 0xE9, 0x01
};

static const u8 stub[] = {
0x00, 0x00, 0xA0, 0xE3, 0x1E, 0xFF, 0x2F, 0xE1 // mov r0, #0; bx lr
};

//Disable CRR0 signature (RSA2048 with SHA256) check
patchMemory(code, size,
sigCheckPattern,
sizeof(sigCheckPattern), 0,
stub,
sizeof(stub), 1
);

//Disable CRO0/CRR0 SHA256 hash checks (section hashes, and hash table)
patchMemory(code, size,
sha256ChecksPattern1,
sizeof(sha256ChecksPattern1), 0,
stub,
sizeof(stub), 1
);

patchMemory(code, size,
sha256ChecksPattern2,
sizeof(sha256ChecksPattern2), 0,
stub,
sizeof(stub), 1
);

break;
}

 

[Izaya-Orihara]

Alright, I think I arrived a bit late to the party but whatever. This has been going on for a while now (over two months) and it got a bit stale, but after reading this post I decided to take a look at it and rework certain parts.

I dare to say that some parts of the latest commit were inspired by corbenik's fork, like the removal of IFile.

Anyways, here it is: https://github.com/Wolfvak/3ds_injector/releases/latest. @Crystal the Glaceon, might wanna link this in the OP or something.

Sorry i am a noob, I don't understand what your getting at? Are u suggesting i use another cfw besides luma3ds for "cro editing" on pk3ds

 

[Wolfvak]

I was really surprised at the fact that removing IFile regained about two mediaunits at near zero cost, honestly.

Looks like you're actually missing the RO patch, btw (and this originates from Luma)

Spoiler: ro patch

case 0x0004013000003702LL: // RO
{
static const u8 sigCheckPattern[] = {
0x30, 0x40, 0x2D, 0xE9, 0x02
};
static const u8 sha256ChecksPattern1[] = {
0x30, 0x40, 0x2D, 0xE9, 0x24
};
static const u8 sha256ChecksPattern2[] = {
0xF8, 0x4F, 0x2D, 0xE9, 0x01
};

static const u8 stub[] = {
0x00, 0x00, 0xA0, 0xE3, 0x1E, 0xFF, 0x2F, 0xE1 // mov r0, #0; bx lr
};

//Disable CRR0 signature (RSA2048 with SHA256) check
patchMemory(code, size,
sigCheckPattern,
sizeof(sigCheckPattern), 0,
stub,
sizeof(stub), 1
);

//Disable CRO0/CRR0 SHA256 hash checks (section hashes, and hash table)
patchMemory(code, size,
sha256ChecksPattern1,
sizeof(sha256ChecksPattern1), 0,
stub,
sizeof(stub), 1
);

patchMemory(code, size,
sha256ChecksPattern2,
sizeof(sha256ChecksPattern2), 0,
stub,
sizeof(stub), 1
);

break;
}

This is a two month old project, guess I haven't kept up lol. Gonna add these.

 

[chaoskagami]

Sorry i am a noob, I don't understand what your getting at? Are u suggesting i use another cfw besides luma3ds for "cro editing" on pk3ds

Nah. @Wolfvak is just making a suggestion to put in the OP for this as far as I can tell. This might be something to document, because it isn't just luma that supports this.

 

[The Catboy]

Sorry i am a noob, I don't understand what your getting at? Are u suggesting i use another cfw besides luma3ds for "cro editing" on pk3ds

I personally suggest testing out different CFW's if you are interested. Otherwise if one works best for you, to not sweat it.

Alright, I think I arrived a bit late to the party but whatever. This has been going on for a while now (over two months) and it got a bit stale, but after reading this post I decided to take a look at it and rework certain parts.

I dare to say that some parts of the latest commit were inspired by corbenik's fork, like the removal of IFile.

Anyways, here it is: https://github.com/Wolfvak/3ds_injector/releases/latest. @Crystal the Glaceon, might wanna link this in the OP or something.

Being that I have a vague idea what this is, what is it? And do you mind if I quote you in the OP? I am 90% sure I will screw up explaining it.

 

[chaoskagami]

Being that I have a vague idea what this is, what is it? And do you mind if I quote you in the OP? I am 90% sure I will screw up explaining it.

It's an implementation of Yifan Lu's loader for Cakes. This implies the usual bits like region free, blocking updates, killing ASLR and the Cubic Ninja/OOTHax fix, etc.

 

[The Catboy]

It's an implementation of Yifan Lu's loader for Cakes. This implies the usual bits like region free, blocking updates, killing ASLR and the Cubic Ninja/OOTHax fix, etc.

I actually explain that! You mind if I quote you anyways because I know my post will just end up being made from this (or @Wolfvak's statement.)
I am also going to have to test this feature before including it. It's nothing personal, I just like to get a feel of the project before I ramble on about it.

 

[Wolfvak]

I actually explain that! You mind if I quote you anyways because I know my post will just end up being made from this (or @Wolfvak's statement.)
I am also going to have to test this feature before including it. It's nothing personal, I just like to get a feel of the project before I ramble on about it.

Go ahead. Just make sure to wait until I commit the RO sigpatches (and they're included in the release, of course)

 

[The Catboy]

Go ahead. Just make sure to wait until I commit the RO sigpatches (and they're included in the release, of course)

Can do! Take your time!

 

[chaoskagami]

I actually explain that! You mind if I quote you anyways because I know my post will just end up being made from this (or @Wolfvak's statement.)
I am also going to have to test this feature before including it. It's nothing personal, I just like to get a feel of the project before I ramble on about it.

Go ahead. Just make sure to wait until I commit the RO sigpatches (and they're included in the release, of course)

To answer, I don't care if you quote me either. Go ahead.