Hacking Official [Source Release] ReiNand CFW

[SirNapkin1334]

Rei-Six can't load firms that old. 1.0.0 has some different patches that I don't have implemented. But generally on Rei-Six emunand is booted by holding R at launch or by having a file on your SD called "loademunand" in the /Rei folder with no file extension.

Do you know any way I could load it?

 

[CrimsonMaple]

Do you know any way I could load it?

Nope.

 

[gnmmarechal]

Finally got around to writing some code again. I added firm loading from NAND! So here is a release! https://github.com/CrimsonMaple/Rei-Six/releases/tag/1.2

Emunand users please don't hate me. I removed the FIRM Binaries. You can still use Emunand though! The previous ones will not work since I got rid of the memekey period. (Press F to pay respects).
There are instructions to get new firm binaries in the README! Be sure to check that out if you use EmuNand!

Time to update my 2DS it seems

 

[KuroGentei]

I added firm loading from NAND! So here is a release! https://github.com/CrimsonMaple/Rei-Six/releases/tag/1.2

Can now rei-six install in bootfirm (sysnand) FIRM0 and FIRM1?

 

[CrimsonMaple]

Can now rei-six install in bootfirm (sysnand) FIRM0 and FIRM1?

Technically it can be installed to firm1 or firm0, but godmode9 won't do it.

 

[nitrozz]

Up and running

 

[CrispyCola]

Can’t get this to boot RedNAND, it always boots SysNAND and I have all the firmware files in /rei. Help would be appreciated [emoji4]


Sent from my iPhone using Tapatalk

 

[CrimsonMaple]

Can’t get this to boot RedNAND, it always boots SysNAND and I have all the firmware files in /rei. Help would be appreciated [emoji4]


Sent from my iPhone using Tapatalk

Hold R on startup or if you want it to auto boot emunand add the file "/rei/loademunand" to your SD. No file extension.

 

[CrispyCola]

Hold R on startup or if you want it to auto boot emunand add the file "/rei/loademunand" to your SD. No file extension.

I added the loademunand and now my 3DS shuts off immediately on power up
Edit: nevermind I fixed it


Sent from my iPhone using Tapatalk

 

[CrimsonMaple]

I added the loademunand and now my 3DS shuts off immediately on power up


Sent from my iPhone using Tapatalk

You are using the old firmware files. You need to make new ones using Decrypt9wip. I have instructions on the readme.

 

[Nazosan]

Well, you say it supports booting from NAND, but it seems like it still requires a memory card for the files? Or do the files have to be in a specific location in the NAND? It seems like most things go to the /rw folder (eg I put a "rei" folder under /rw with the same files as my memory card) but perhaps this doesn't? If not, I wonder if it should -- or at least if it should support it even if it uses multiple paths or something. This is mostly just intended to be an emergency backup sort of thing if my memory card fails or something, so I may never need it, but I do want to have it working just in case that situation ever does arise.

 

[CrimsonMaple]

Well, you say it supports booting from NAND, but it seems like it still requires a memory card for the files? Or do the files have to be in a specific location in the NAND? It seems like most things go to the /rw folder (eg I put a "rei" folder under /rw with the same files as my memory card) but perhaps this doesn't? If not, I wonder if it should -- or at least if it should support it even if it uses multiple paths or something. This is mostly just intended to be an emergency backup sort of thing if my memory card fails or something, so I may never need it, but I do want to have it working just in case that situation ever does arise.

Technically it does still use files on the SD but the firmware will still boot without them. It just won't have as many patches. (Like region free for example.) But no, you cannot put the /Rei folder on nand and expect it to boot with those patches. But you can put the boot.firm file there and expect it to boot.

 

[nitrozz]

Technically it does still use files on the SD but the firmware will still boot without them. It just won't have as many patches. (Like region free for example.) But no, you cannot put the /Rei folder on nand and expect it to boot with those patches. But you can put the boot.firm file there and expect it to boot.

How to know if patch are loaded ? There is some log file?

 

[CrimsonMaple]

How to know if patch are loaded ? There is some log file?

If you see the ".:rei" string in system settings then they are all loaded. If not then loader.cxi isn't in "SD:/rei". If you haven't deleted anything in /rei then you are fine.

 

[The Catboy]

Can now rei-six install in bootfirm (sysnand) FIRM0 and FIRM1?

Rei-six can be installed to the FIRM1 and boot from the FIRM1 using FB3DS.
You can also copy the .firm file to the CTRNAND and launch it that way as well.

 

[Nekoxid]

I have a question (and I hope I'm asking this in the right place).

I have a N3DS with a 9.2.0-20E firmware, and a 11.6.0-39E emunand with the latest Reinand (v5.1).
Is it hard to switch to Rei-Six from Reinand? (I want to keep the 9.2.0 fw in case something goes wrong with my emunand.)

 

[CrimsonMaple]

I have a question (and I hope I'm asking this in the right place).

I have a N3DS with a 9.2.0-20E firmware, and a 11.6.0-39E emunand with the latest Reinand (v5.1).
Is it hard to switch to Rei-Six from Reinand? (I want to keep the 9.2.0 fw in case something goes wrong with my emunand.)

Nope. There is an extra step for emunand users though. You will have to get your own firmware binary files. But I made instructions for that on the Readme as well as add the file 'loademunand' with no file extension to the /Rei folder. But you just install b9s and can use Rei-Six. But it is recommended that you just abandon emunand. Emunand isn't required and just takes up space. Keeping a 9.2 firm is also quite irrelevant since you can hack the latest firmware using a DS flashcart. SysNands older than 11.4 can't boot on Rei-Six anyways.

 

[Nekoxid]

Nope. There is an extra step for emunand users though. You will have to get your own firmware binary files. But I made instructions for that on the Readme as well as add the file 'loademunand' with no file extension to the /Rei folder. But you just install b9s and can use Rei-Six. But it is recommended that you just abandon emunand. Emunand isn't required and just takes up space. Keeping a 9.2 firm is also quite irrelevant since you can hack the latest firmware using a DS flashcart. SysNands older than 11.4 can't boot on Rei-Six anyways.

Ah okay. So I guess I need to update my Sysnand too then.
Thanks for the reply.

 

[Hunter]

Ah okay. So I guess I need to update my Sysnand too then.
Thanks for the reply.

you can use godmode9 to backup your emunand, then restore it over your sysnand, so you dont lose anything

*if you are using b9s* so upgrade that first if not

 

[Kazuma77]

If you see the ".:rei" string in system settings then they are all loaded. If not then loader.cxi isn't in "SD:/rei". If you haven't deleted anything in /rei then you are fine.

So, will it run without "loader.cxi" now? The previous version would crash without it. Which threw a wrench into my "stealth mode" feature that launched ReiNAND without it to have a relatively legit looking system (in case they decided to check systems for CFW at a Pokemon tournament or something). So, I had to comment the line that moved it out. If it works without it again, that's good news for people who want such a feature.

Also, only one of the .rnp files got included in the "patches.dat" that is in the release. It's a bug with the Windows versions of the compilers, I think. I get around it by having a batch file do the compiling, and having it delete the generated "patches.dat" file and use "copy/b" to create one that includes all of the .rnp files. It should be 115 bytes, not 18. Unless "loader.cxi" handles those other 3 patches now.

It would be easy to write a GM9 script to extract the firms (we're talking less than 30 lines). But is this only for EmuNAND? Or will it use the extracted files for both, if present? If it's only using them for EmuNAND, would it not be better to have the script extract the firms from said EmuNAND, so that the EmuNAND is being run with it's own Native FIRM instead of the 11.4 one? That just seems like it would provide better compatibility. Well, let me know which would be better. I'll post a standalone version here, then I'll probably add it to my "Settings" app (seems like the most appropriate place for it in my AIO, but I'm open to suggestions).

Nope. There is an extra step for emunand users though. You will have to get your own firmware binary files. But I made instructions for that on the Readme as well as add the file 'loademunand' with no file extension to the /Rei folder. But you just install b9s and can use Rei-Six. But it is recommended that you just abandon emunand. Emunand isn't required and just takes up space. Keeping a 9.2 firm is also quite irrelevant since you can hack the latest firmware using a DS flashcart. SysNands older than 11.4 can't boot on Rei-Six anyways.

You're forgetting about Gateway for ROM loading, for those of us who still use it (if you have a large ROM collection like me, multi-booting into GW is much less of a hassle than converting everything, and even if it never gets another update, GW will still run most ROMs just fine). Unless they finally put out an update while I wasn't looking. It's not like the Dragon Quest series is multiplayer anyway. So that stuff can go on my second card.

And I like keeping 9.2 around for old exploits. But that's my second one with me being a GW owner. Meaning I can't use ReiNAND for it anyway. But Puma and Luma Legacy work for that (and Cakes on the O3DS, but it only supports 9.2 SysNAND on the N3DS for whatever reason). I like having Ninjhax 1.1b still available just in case. And I like being able to chainload into Menuhax. Not that having one of my alternate CFWs boot an EmuNAND that more or less goes straight into the HB menu is a necessity, but it's a nice convenience if you have a big card and space to burn. But yeah, it's pretty much just a power user thing. Not something most people will miss.