Hacking Official [Source Release] ReiNand CFW

  • Thread starter Thread starter Reisyukaku
  • Start date Start date
  • Views Views 988,107
  • Replies Replies 6,480
  • Likes Likes 115
Freeshop takedown.
The only argument Nintendo could stand on was the fact "Freeshop" used the official Nintendo 3DS bootlogo... but Freeshop's source never contained it; rather, it's makerom which actually has the logos and puts the selected one in the ncch/cia

Nintendo should even have known this, since "ctr_makerom32" was invented by Nintendo and the open source homebrew "makerom" is intended to be compatible with Nintendo's!!

Yet for some reasons they didn't report the makerom repo, nor any other homebrew using the Nintendo 3DS logo.
Seems like the reasons they hate Freeshop aren't due to the logo, amirite?

If you think logically for the purpose of "Free" Shop, yeah
 
Honestly, given the current discussion and all I would say that there is an inherent risk in using anything copyrighted. It probably would be wisest to remove the need for it. However the key here is that there is probably a decent safe leeway on this. So what makes the most sense, IMO, is to go ahead and remove it, but not to rush at it and to just do it at your leisure, just a bit here and there until it's ready and then remove it before any actual strikes or anything like that. After all, it's also possible they could actually sue or something rather than just issue a DMCA takedown. You really never know in these things. I imagine that's terribly unlikely if not borderline simply not going to happen, but if you can take steps to avoid it, why not? It just shouldn't be anything to be scared about and rush to do ASAP dropping everything else is all.

EDIT: BTW, if ctrnand means what I think it does, maybe given ReiNand's focus on a minimal nature might actually mean it would be a really good candidate for possibly going the ctrnand route? It seems like lately there isn't anything even being worked on for this that I could find anyway.
 
Last edited by Nazosan,
Freeshop takedown.
The only argument Nintendo could stand on was the fact "Freeshop" used the official Nintendo 3DS bootlogo... but Freeshop's source never contained it; rather, it's makerom which actually has the logos and puts the selected one in the ncch/cia

Nintendo should even have known this, since "ctr_makerom32" was invented by Nintendo and the open source homebrew "makerom" is intended to be compatible with Nintendo's!!

Yet for some reasons they didn't report the makerom repo, nor any other homebrew using the Nintendo 3DS logo.
Seems like the reasons they hate Freeshop aren't due to the logo, amirite?
It obviously wasn't because of the logo, but that's all they could get them on. Being that freeShop doesn't break any actual laws, they could only tackle it for the one bit of copyright code that it did break.
But really this shouldn't be brought up here because this isn't about reiNAND
 
Honestly, given the current discussion and all I would say that there is an inherent risk in using anything copyrighted. It probably would be wisest to remove the need for it. However the key here is that there is probably a decent safe leeway on this. So what makes the most sense, IMO, is to go ahead and remove it, but not to rush at it and to just do it at your leisure, just a bit here and there until it's ready and then remove it before any actual strikes or anything like that. After all, it's also possible they could actually sue or something rather than just issue a DMCA takedown. You really never know in these things. I imagine that's terribly unlikely if not borderline simply not going to happen, but if you can take steps to avoid it, why not? It just shouldn't be anything to be scared about and rush to do ASAP dropping everything else is all.

Thankfully nowadays we have the aeskeydb which everyone can get with a quick google search. Should be pretty easy to integrate it into ReiNand and be able to ditch the pre-decrypted firmware.
However, this brings up another issue...

EDIT: BTW, if ctrnand means what I think it does, maybe given ReiNand's focus on a minimal nature might actually mean it would be a really good candidate for possibly going the ctrnand route? It seems like lately there isn't anything even being worked on for this that I could find anyway.

... which is code complexity. When the readme says "minimal nature" it doesn't mean "minimal amount of files required in runtime" or "fastest execution time". It (probably) means "simplest code possible while retaining basic features plus those that are sane enough to keep".

CTRNAND decryption would add a lot of complexity, ranging from adding a new drive to FatFS, adding the required decryption code, having to differentiate between N3DS and O3DS (they use different keyslots, partition locations and their FIRM title ids are different, etc). This adds a whole bunch of problems that can only be solved with more code. And as everyone who has studied CS knows, more code means higher chance of bugs.

Doing a CTRNAND-only install (where all files are placed on it instead of SD) wouldn't be completely insane, but doing *both* SD and CTRNAND at the same time is a bit more tricky. It's definitely not impossible, dare I say it's not even hard. But it breaks with the whole "simplicity" paradigm.
 
Last edited by Wolfvak,
(N3dsxl) I am running emunand 11.2 with menuhax and I use Reinand to boot into emunand. My sysnand is 9.2.

I was looking to update to 11.4 on my emunand, so I got the latest version of reinand (5.1) and booted my console. Every time I boot into reinand 5.1 i just get a black screen, no splash screen either. So I grabbed 5.0 reinand and put it on, everything booted fine with that version. Did something change with 11.4 to where I have to update on 5.0 then throw on 5.1 to get it to work?
 
(N3dsxl) I am running emunand 11.2 with menuhax and I use Reinand to boot into emunand. My sysnand is 9.2.

I was looking to update to 11.4 on my emunand, so I got the latest version of reinand (5.1) and booted my console. Every time I boot into reinand 5.1 i just get a black screen, no splash screen either. So I grabbed 5.0 reinand and put it on, everything booted fine with that version. Did something change with 11.4 to where I have to update on 5.0 then throw on 5.1 to get it to work?
I really need to add a notification to github...... I swear to god. Just grab the firmware.bin in /data from github and put it in /rei and you will be good to go.
 
I really need to add a notification to github...... I swear to god. Just grab the firmware.bin in /data from github and put it in /rei and you will be good to go.
Ok, so I used the new firmware.bin file for both 5.1 and 5.0. 5.1 just goes to black screen. 5.0 gets stuck on the splash screen and doesn't load into emunand
 
Ok, so I used the new firmware.bin file for both 5.1 and 5.0. 5.1 just goes to black screen. 5.0 gets stuck on the splash screen and doesn't load into emunand
Works fine for me. Use the one in the Dropbox link page back or so. It will only work on 5.1 since 5.0 has some issues with keys not being properly loaded.
 
Hey guys. I have the same problem with others: System Update then after the ReiNAND screen shows up, it's all black.
Pleeeeeeeeeeeease help me. I kind of need step by step guides because it'll be my first time to fix anything software-related.
Thanks in advance for the help~
 
Hey guys. I have the same problem with others: System Update then after the ReiNAND screen shows up, it's all black.
Pleeeeeeeeeeeease help me. I kind of need step by step guides because it'll be my first time to fix anything software-related.
Thanks in advance for the help~
If you are on v5.1 (which it sounds like you arent. So update.) Then download the firmware.bin from the Dropbox link a page or two back and put it in the /rei folder.
 
Last edited by CrimsonMaple,
Hey guys. I have the same problem with others: System Update then after the ReiNAND screen shows up, it's all black.
Pleeeeeeeeeeeease help me. I kind of need step by step guides because it'll be my first time to fix anything software-related.
Thanks in advance for the help~
You need to download the latest firmware.bin from the repo. It's listed under the "data" link
If you are on v5.1 then download the firmware.bin from the Dropbox link a page or two back and put it in the /rei folder.
It really would make more sense to replace the firmware.bin in the 5.1 with the firmware.bin from the repo. Would solve a lot of problems.
 
Last edited by The Catboy,
So, with the direction that ReiNAND is going in, should I keep using Luma3DS or just switch to ReiNAND? Because the latter seems more nostalgic for some reason.
 
If you are on v5.1 (which it sounds like you arent. So update.) Then download the firmware.bin from the Dropbox link a page or two back and put it in the /rei folder.
Oooooookay. This will be hard for me since I got my 3DS recently (second-hand from a friend) and I still don't know how to navigate around it.
Do I connect the 3DS to the computer or just connect the SD Card to the computer? (I am assuming that I can pull out a certain SD Card from my 3DS if I opened it because when I play Fire Emblem Fates, it says saving on SD Card).
I'm so sorry for being such a hard one to teach.
 
If I had two 3DS I would have used both, but I only have one, so I get only one option.
Also, "per que no las dos?"
Lol, what? You can run as many CFWs as you want. I am running 5 different CFWs right now on the same sysNAND.
CFWs on the 3DS does two things, applies patches to the OFW and reads information from the NAND. So you can run Luma3DS with reiNAND without a problem.
 

Site & Scene News

Popular threads in this forum