Homebrew Possible to run Pasta CFW and Gateway on same N3DS?

[Urbanshadow]

Your solution/concept to boot both Pasta CFW and Gateway is good. Now with BrowserHax&ThemeHax allows N3DS to run HBL without OOT/CN, plus PASTA CFW is now made to boot through HBL without the need of CN. Yes, you now can run PASTA CFW on N3DS only with just HBL through BrowserHax/ThemeHax (the first entry point is HBL, not CFW or CN/OOT cartridge). What left is use that Pasta CFW to install CN or OOT cia on to SYSNAND to be used to boot Gateway.

For those who doesn't own a Gateway card, you can do a two steps configuration similar to this making a pretty solid build. In the first step you do the tutorial to setup emunand through the CN GW launcher (this one). In the second step goes like this:
1. Format sysnand to unlink emunand
2. Reinstall themehax on sysnand (if you dont intent to use sysnand anymore go to 5)
3. Reinstall cia installer and CN on sysnand
4. Install ninjhax2 in CN sysnand
5. Move rxtools.3dsx on sd root
6. Modify themehax payload with an hex editor to boot rxtools.3dsx directly
7. Install ninjhax2 in CN emunand

With this you can start hbl offline from emunand through CN. You can run hbl the first time in sysnand through browserhax to launch Pasta. You can run hbl from pasta through CN. You can use pasta menu for nand backup things instead of GW launcher. You can install cias to sysnand with pasta. You can sysupdate sysnand with pasta, but themehax payload must be regenerated and modified again. You can install cias to emunand through rxtools. You can sysupdate emunand through rxtools. You can in fact run rxMode on sysnand (for playing virtual console games). On top of emunand you can run NTR cfw as cia if you have N3DS. Pro tip: if themehax is triggerless, you boot into emunand without doing anything in about 6-8 seconds.

 

[KidIce]

Well. When I quoted you, I was aware of the age of the OP and your response. I saw newer response suggested downgraded MSET and ThemeHax. I advise against downgraded MSET due to some people just forget and "Format System Memory" with downgraded MSET which causes brick on N3DS. I meant to say to other people (not directed at you) when quoting you: "this is the better/safer concept to launch both Gateway and Pasta CFW without anything but 9.0-9.2 N3DS with new 'tools'. Avoid MSET downgrade as much as you can!"

Your solution/concept to boot both Pasta CFW and Gateway is good. Now with BrowserHax&ThemeHax allows N3DS to run HBL without OOT/CN, plus PASTA CFW is now made to boot through HBL without the need of CN. Yes, you now can run PASTA CFW on N3DS only with just HBL through BrowserHax/ThemeHax (the first entry point is HBL, not CFW or CN/OOT cartridge). What left is use that Pasta CFW to install CN or OOT cia on to SYSNAND to be used to boot Gateway.

Then why install both CN and OOT? This is where my confusion lies. I mean, as you say, use [preferred]hax for HBL/Pasta, then installed CN OR OOT for GW... Or am I missing something? That's why it seemed to me you were saying you could run those CIA's w/o patching the system first. Do you use the CN install to return to Pasta from GW mode?

I may sound argumentative, but if there's something I don't know, I'm actually curious as to what it is. I think I'm fairly well read on the subject at hand and I was really after anything I may have missed... Something you possibly knew that I don't (i.e. running a manager installed title w/o CFW).

I agree wholeheartedly w/ not using MSET on >4.5 systems, the risks and side effects are just too great IMO if one has to downgrade to do so.

 

[tivu100]

Then why install both CN and OOT? This is where my confusion lies. I mean, as you say, use [preferred]hax for HBL/Pasta, then installed CN OR OOT for GW... Or am I missing something? That's why it seemed to me you were saying you could run those CIA's w/o patching the system first. Do you use the CN install to return to Pasta from GW mode?

I may sound argumentative, but if there's something I don't know, I'm actually curious as to what it is. I think I'm fairly well read on the subject at hand and I was really after anything I may have missed... Something you possibly knew that I don't (i.e. running a manager installed title w/o CFW).

I agree wholeheartedly w/ not using MSET on >4.5 systems, the risks and side effects are just too great IMO if one has to downgrade to do so.

a. Let's say one has CN cartridge: to boot into PASTA CFW: turn on system -> boot into CN -> launch Pasta CFW by using the exploit on save game. b. New way to boot Pasta CFW with Themehax: turn on system (holding L or whatever way you set up themehax) -> on HBL boot Pasta CFW. * To launch Gatay Menu Launcher will take another step that launch the CIA installed in PASTA mode (the inconvenience by this extra stepcan be offset by eliminating the risk of bricking by accident with downgraded MSET)

We pretty much do same number of steps to boot Pasta CFW with themehax, yet we don't need CN cartridge or CIA. Never said we can run unsigned CIA without any sort of CFW/hax mode. Just that's now the only requirement is N3DS with 9.0-9.2 firmware.

In the Pasta CFW mode: I installed both CN and OOT cia for: a. CN to be able boot to HBL again so I can restore browser to its original function. CN takes up little disk space and doesn't have update snag like Ironhax, better boot rate than both browserhax and themehax (perhaps someone doesn't need to use browser so can use CN for Gateway Menu Launcher so no need for point b.). b. OOT to boot Gateway menu launcher (can use CN for this and use ironhax/themehax/browserhax for HBL if it's to saveSD disk space).

To return from GW SYSNAND mode to Pasta CFW: either boot CN/ enter and exit system settings holding L to trigger themehax, to launch HBL -> choose to boot PASTA CFW.

 

[Sonansune]

coldboot pasta, mset ds profile gw.
nice and easy