Hacking [Tutorial] Setting up Reinand CFW from scratch

[Arecaidian Fox]

Use FBI to reinstall Reinands ROP and you'll be able to launch Emunand via profile exploit again.

So...CN>QR Code>Pasta>CN>QR Code>FBI>Install ROP?

 

[usernametaken]

So...CN>QR Code>Pasta>CN>QR Code>FBI>Install ROP?

Yes, whenever you want to install something with FBI from the Hombrew menu, you'll need to have Sysnand signatures patched with a cfw like Pasta.

 

[Arecaidian Fox]

Yes, whenever you want to install something with FBI from the Hombrew menu, you'll need to have Sysnand signatures patched with a cfw like Pasta.

Right, so any time I want to install, say, a .CIA file to my emuNAND I have to be on sysNAND and run it through the Ninjhax exploit with FBI, right?

 

[usernametaken]

Right, so any time I want to install, say, a .CIA file to my emuNAND I have to be on sysNAND and run it through the Ninjhax exploit with FBI, right?

No, in Emunand you'll use Devmenu or BigBlueMenu (BBM is included in the 9.5 pack on the pastebin) to install your cias.

 

[Arecaidian Fox]

No, in Emunand you'll use Devmenu or BigBlueMenu (BBM is included in the 9.5 pack on the pastebin) to install your cias.

Dumb question then, but how would I install BBM or DevMenu on emuNAND? I want to make sure I have actual instructions instead of guesswork on my part.

 

[usernametaken]

Dumb question then, but how would I install BBM or DevMenu on emuNAND? I want to make sure I have actual instructions instead of guesswork on my part.

You created your Emunand, when you create the Emunand your nands are linked. Anything you install on the Sysnand will be on the Emunand. So when you installed Devmenu, it was 'installed' on your Emunand as well.

If you were to unlink your Nands, the Sysnand would be wiped & it would create a new ID for itself. The Emunand would persist with the old ID along with everything you installed on Sysnand.

Since you'll have Devmenu in Emunand, you can use that Title manager to install other Cias; including other title managers like BigBlueMenu.

 

[Arecaidian Fox]

You created your Emunand, when you create the Emunand your nands are linked. Anything you install on the Sysnand will be on the Emunand. So when you installed Devmenu, it was 'installed' on your Emunand as well.

If you were to unlink your Nands, the Sysnand would be wiped & it would create a new ID for itself. The Emunand would persist with the old ID along with everything you installed on Sysnand.

Since you'll have Devmenu in Emunand, you can use that Title manager to install other Cias; including other title managers like BigBlueMenu.

I'm looking at my emuNAND now and I don't see DevMenu.

 

[usernametaken]

I'm looking at my emuNAND now and I don't see DevMenu.

If you have Devmenu on your Sysnand > Reformat Emunand
If you don't have Devmenu at all Install to Sysnand > Reformat Emunand

 

[Arecaidian Fox]

If you have Devmenu on your Sysnand > Reformat Emunand
If you don't have Devmenu at all Install to Sysnand > Reformat Emunand

I unlinked the two NANDs, so I don't have DevMenu installed on sysNAND. What will happen if I reformat my emuNAND? Will I need to reinstall exploits? Actually, couldn't I just install BBM/DevMenu via Ninjhax on emuNAND?

 

[usernametaken]

I unlinked the two NANDs, so I don't have DevMenu installed on sysNAND. What will happen if I reformat my emuNAND? Will I need to reinstall exploits? Actually, couldn't I just install BBM/DevMenu via Ninjhax on emuNAND?

Your emunand will have the downgraded settings (Which will be removed if you update the firmware to 9.5.0-23).
You'll need to reinstall the ROP to Sysnand if you unlink the nands afterwards.
Fairly sure Ninjhax 1.1 won't launch from emunand due to firmlaunch, you're welcome to try though.

 

[Arecaidian Fox]

Your emunand will have the downgraded settings (Which will be removed if you update the firmware to 9.5.0-23).
You'll need to reinstall the ROP to Sysnand if you unlink the nands afterwards.
Fairly sure Ninjhax 1.1 won't launch from emunand due to firmlaunch, you're welcome to try though.

I already have the ROP installed to sysNAND and it's unlinked from the emuNAND, and I haven't updated either one yet. But it looks FBI has insufficient privileges to run without Pasta on reiNAND, and Pasta causes a system error/crash when it loads on emuNAND. So now I essentially have to reinstall DevMenu on sysNAND, then reformat my enuNAND and unlink them again, right?

 

[usernametaken]

I already have the ROP installed to sysNAND and it's unlinked from the emuNAND, and I haven't updated either one yet. But it looks FBI has insufficient privileges to run without Pasta on reiNAND, and Pasta causes a system error/crash when it loads on emuNAND. So now I essentially have to reinstall DevMenu on sysNAND, then reformat my enuNAND and unlink them again, right?

That's what I said in the last two posts, yes. :|

 

[Arecaidian Fox]

That's what I said in the last two posts, yes. :|

Sorry, wanted to make sure. What tool would you suggest for reformatting my emuNAND?

 

[usernametaken]

Sorry, wanted to make sure. What tool would you suggest for reformatting my emuNAND?

I'd use Gateways Menu to reformat the Emunand.

Pastas menu has a format emunand option as well. Should work exactly the same, you're welcome to use whichever you prefer.
Confirm you have Devmenu on your Emunand before unlinking the nands.

 

[Arecaidian Fox]

Okay, I did post on here wrongly before, but I may as well recycle the post. I can't for the life of me get DevMenu to show up at ALL in emuNAND. Just to be clear, the EXACT process for installing it and getting it into emulated NAND is to boot Cubic Ninja, run Ninjhax exploit v1.1b, Hold [L] and run Pasta and select "Give me some Pasta", then boot back into Cubic Ninja and run FBI through Ninjhax, then install DevMenu.cia to the system's mSD card, go back to the Home Menu, confirm DevMenu is installed by unwrapping it, boot back into CN, rerun Pasta, then go back into CN once more and have Pasta format the emuNAND. Is this correct?

 

[usernametaken]

Okay, I did post on here wrongly before, but I may as well recycle the post. I can't for the life of me get DevMenu to show up at ALL in emuNAND. Just to be clear, the EXACT process for installing it and getting it into emulated NAND is to boot Cubic Ninja, run Ninjhax exploit v1.1b, Hold [L] and run Pasta and select "Give me some Pasta", then boot back into Cubic Ninja and run FBI through Ninjhax, then install DevMenu.cia to the system's mSD card, go back to the Home Menu, confirm DevMenu is installed by unwrapping it, boot back into CN, rerun Pasta, then go back into CN once more and have Pasta format the emuNAND. Is this correct?

If that didn't work for you, try making the emunand then installing devmenu.
I'd just take the extra step and use Gateways menu for the Reformat of the Emunand.

 

[joex11]

usernametaken sensei, would you know if there is any other method to upgrade an old 3ds (2.2u) to 4.x to 9.2 that isn't game cartdrige update?

 

[usernametaken]

usernametaken sensei, would you know if there is any other method to upgrade an old 3ds (2.2u) to 4.x to 9.2 that isn't game cartdrige update?

I don't have an O3DS & haven't looked too much into them.
As far as i'm aware, your only option is a cartridge update to 4.5 (Fairly sure you want to stay on 4.5 for the profile exploit)

 

[joex11]

I don't have an O3DS & haven't looked too much into them.
As far as i'm aware, your only option is a cartridge update to 4.5 (Fairly sure you want to stay on 4.5 for the profile exploit)

Oh yeah, forgot about the ds profile exploit. But reinand only has rop to launch n3ds right? so that would only work to use gateway

 

[Arecaidian Fox]

Well, DevMenu isn't even showing up on sysNAND now. Or on emuNAND. I'm just going to wipe everything and try it from scratch again. Maybe 5th time's the charm =/