Using Luma3DS + Gateway on B9S

Kazuma77 · Jul 27, 2017

Temptress Cerise said:
@Hayleia is the one that made it, probably could provide you with the source code behind v2gw.bin.

As for having steps to convert, I'll pass on adding those. That's just silly. If people want to throw that file around, that's fine, I don't care, it won't be part of this guide though, and if someone wants to make that guide, they are more than welcome to do that.

Don't you see? It doesn't matter if you get me the source. I'd still have to have EVERY BYTE OF COPYRIGHTED SOURCE CODE EVER WRITTEN to compare it against to prove v2gw.bin doesn't contain any. I'm good, but not that good

. Just like I would have to explore every inch of the universe to definitively be able to prove whether a god existed or not, and that still wouldn't do it since it's possible that he/she/it isn't in a stationary location, exists in a parallel plane, etc (not trying to trample on anyone's beliefs, btw, just giving an example). You cannot prove a negative. This is a universal truth. By your standard of proof, v2gw.bin is equally unsafe, since you cannot prove it is free of copyright code either. We can either consider both unsafe by the irrational standard of proving a negative, or consider both safe by the rational standard of proving a positive.

I'll remind you, GW supports multiple entry points. Does it make sense for them to put keys and firmware that all these other entry points are going to need into an A9LH-only launcher? And again, its 6,984 bytes. By comparison, v2gw.bin is 9,076. GW's payload is officially the smallest A9LH payload in existence. There just isn't space for anything more than a basic loader. Especially considering that it took a third party 2092 more bytes just to code a bare-bones chainloader to launch it. I think I have logically proven to a 99% degree of certainty that the loader is free of any of Nintendo's code. If that's not good enough for you, so be it.

Using 3 chainloaders is MUCH MORE silly than running a converter IMHO. It's just a couple of quick extra steps. Copy and double-click. Conversion means you can run the GW payload directly from BootCTR9, and only use 2 chainloaders if you want to keep using Luma's. It's much cleaner. Besides, your solution is too limited. It only works with Luma's chainloader. Some people might like something that works with BootCTR9 and CBM9 (especially since they don't break other CFWs like Cakes). I could make you a v2gw.bin that uses "a9lh" instead of "luma", so it works with everything, and doesn't put payloads that won't run in the GUI, but why would I encourage this?

I think you just want to stick to v2gw.bin because it's become a tradition/ritual for you or something. That's your choice. Since you seem to want to shoot down my every attempt to simplify the process, then I will make my own release. I'll go one further than writing a tutorial though. I'm releasing an "AIO B9S Pack Lite" here for those who can't find the iso site. No tutorial needed. Assuming you have the Launcher.dat on your card already, just drag, drop, and you're done. A full choice of chainloaders will be there as usual -- BootCTR9, CBM9, and Luma. I may not think highly of Luma's chainloader atm, but I still believe in having a choice.

gamerboy1995 said:
I use Luma with Emunand because I already unlinked my NANDs a long time ago and don't want to go through the hassle of setting up a new linked Emunand and installing dozens of games again.
Supposedly 3Down has a lower risk of bricking than SysUpdater, but I would also have to reinstall my tickets and all my games...

1. SysUpdater 0.4.2 has never bricked for me, so, I'm not sure how anything could be lower than 0%. Besides, I think when it bricked, it was an issue with updating the firm partitions on retail. B9s isn't retail. It doesn't care. If you're worried, make sure you're using Luma since it write protects them. Also, I don't think EmuNAND even uses it's firm partitions.

I've been using SysUpdater all week, trying partial upgrades to 11.5, reverting to partial 11.4 when the select menu didn't work, etc. I even realized yesterday that I forgot to backup my backups made by the B9S installer. I restored my 11.4 SysNAND backup, re-ran the Safe B9S Installer, ran my script to copy ticket.db over from EmuNAND to SysNAND, booted into SysNAND, and updated SysNAND to 11.5 using SysUpdater (didn't want to log into Nintendo again, might look suspicious). If that didn't brick it, I don't know what will. I think having A9LH or B9S and a CFW with firm protection (anything up to date) makes it impossible.

2. It's EmuNAND. You couldn't brick your console if you were still on Menuhax. But with B9S and firm protection, even a SysNAND brick isn't a system brick, because you can still load GM9 or Decrypt9 and restore. Just have a backup.

3. If 3Down deletes your tickets, that's enough of a reason not to use it right there. SysUpdater does not. Though I suppose you could backup your ticket.db with GM9 then restore it, assuming it doesn't format.

Re-linking might not be as complicated as all that, either. You could backup your EmuNAND, safe restore to SysNAND (keeping B9S) using GM9 or Decrypt9, then just update SysNAND. As opposed to the traditional way of doing it by copying SysNAND to EmuNAND. Granted, you might still have to reinstall any DSiWare or GBA titles, but those are relatively small compared to your retail 3DS games, right? Just a guess at something that might help.

gnmmarechal · Jul 27, 2017

Kazuma77 said:
Don't you see? It doesn't matter if you get me the source. I'd still have to have EVERY BYTE OF COPYRIGHTED SOURCE CODE EVER WRITTEN to compare it against to prove v2gw.bin doesn't contain any. I'm good, but not that good . Just like I would have to explore every inch of the universe to definitively be able to prove whether a god existed or not, and that still wouldn't do it since it's possible that he/she/it isn't in a stationary location, exists in a parallel plane, etc (not trying to trample on anyone's beliefs, btw, just giving an example). You cannot prove a negative. This is a universal truth. By your standard of proof, v2gw.bin is equally unsafe, since you cannot prove it is free of copyright code either. We can either consider both unsafe by the irrational standard of proving a negative, or consider both safe by the rational standard of proving a positive.

I'll remind you, GW supports multiple entry points. Does it make sense for them to put keys and firmware that all these other entry points are going to need into an A9LH-only launcher? And again, its 6,984 bytes. By comparison, v2gw.bin is 9,076. GW's payload is officially the smallest A9LH payload in existence. There just isn't space for anything more than a basic loader. Especially considering that it took a third party 2092 more bytes just to code a bare-bones chainloader to launch it. I think I have logically proven to a 99% degree of certainty that the loader is free of any of Nintendo's code. If that's not good enough for you, so be it.

Using 3 chainloaders is MUCH MORE silly than running a converter IMHO. It's just a couple of quick extra steps. Copy and double-click. Conversion means you can run the GW payload directly from BootCTR9, and only use 2 chainloaders if you want to keep using Luma's. It's much cleaner. Besides, your solution is too limited. It only works with Luma's chainloader. Some people might like something that works with BootCTR9 and CBM9 (especially since they don't break other CFWs like Cakes). I could make you a v2gw.bin that uses "a9lh" instead of "luma", so it works with everything, and doesn't put payloads that won't run in the GUI, but why would I encourage this?

I think you just want to stick to v2gw.bin because it's become a tradition/ritual for you or something. That's your choice. Since you seem to want to shoot down my every attempt to simplify the process, then I will make my own release. I'll go one further than writing a tutorial though. I'm releasing an "AIO B9S Pack Lite" here for those who can't find the iso site. No tutorial needed. Assuming you have the Launcher.dat on your card already, just drag, drop, and you're done. A full choice of chainloaders will be there as usual -- BootCTR9, CBM9, and Luma. I may not think highly of Luma's chainloader atm, but I still believe in having a choice.

1. SysUpdater 0.4.2 has never bricked for me, so, I'm not sure how anything could be lower than 0%. Besides, I think when it bricked, it was an issue with updating the firm partitions on retail. B9s isn't retail. It doesn't care. If you're worried, make sure you're using Luma since it write protects them. Also, I don't think EmuNAND even uses it's firm partitions.

I've been using SysUpdater all week, trying partial upgrades to 11.5, reverting to partial 11.4 when the select menu didn't work, etc. I even realized yesterday that I forgot to backup my backups made by the B9S installer. I restored my 11.4 SysNAND backup, re-ran the Safe B9S Installer, ran my script to copy ticket.db over from EmuNAND to SysNAND, booted into SysNAND, and updated SysNAND to 11.5 using SysUpdater (didn't want to log into Nintendo again, might look suspicious). If that didn't brick it, I don't know what will. I think having A9LH or B9S and a CFW with firm protection (anything up to date) makes it impossible.

2. It's EmuNAND. You couldn't brick your console if you were still on Menuhax. But with B9S and firm protection, even a SysNAND brick isn't a system brick, because you can still load GM9 or Decrypt9 and restore. Just have a backup.

3. If 3Down deletes your tickets, that's enough of a reason not to use it right there. SysUpdater does not. Though I suppose you could backup your ticket.db with GM9 then restore it, assuming it doesn't format.

Re-linking might not be as complicated as all that, either. You could backup your EmuNAND, safe restore to SysNAND (keeping B9S) using GM9 or Decrypt9, then just update SysNAND. As opposed to the traditional way of doing it by copying SysNAND to EmuNAND. Granted, you might still have to reinstall any DSiWare or GBA titles, but those are relatively small compared to your retail 3DS games, right? Just a guess at something that might help.

I can't help but laugh at this post.

Sent from my cave of despair where I don't stalk Seriel

gamerboy1995 · Jul 28, 2017

Kazuma77 said:
D

1. SysUpdater 0.4.2 has never bricked for me, so, I'm not sure how anything could be lower than 0%. Besides, I think when it bricked, it was an issue with updating the firm partitions on retail. B9s isn't retail. It doesn't care. If you're worried, make sure you're using Luma since it write protects them. Also, I don't think EmuNAND even uses it's firm partitions.

I've been using SysUpdater all week, trying partial upgrades to 11.5, reverting to partial 11.4 when the select menu didn't work, etc. I even realized yesterday that I forgot to backup my backups made by the B9S installer. I restored my 11.4 SysNAND backup, re-ran the Safe B9S Installer, ran my script to copy ticket.db over from EmuNAND to SysNAND, booted into SysNAND, and updated SysNAND to 11.5 using SysUpdater (didn't want to log into Nintendo again, might look suspicious). If that didn't brick it, I don't know what will. I think having A9LH or B9S and a CFW with firm protection (anything up to date) makes it impossible.

2. It's EmuNAND. You couldn't brick your console if you were still on Menuhax. But with B9S and firm protection, even a SysNAND brick isn't a system brick, because you can still load GM9 or Decrypt9 and restore. Just have a backup.

3. If 3Down deletes your tickets, that's enough of a reason not to use it right there. SysUpdater does not. Though I suppose you could backup your ticket.db with GM9 then restore it, assuming it doesn't format.

Re-linking might not be as complicated as all that, either. You could backup your EmuNAND, safe restore to SysNAND (keeping B9S) using GM9 or Decrypt9, then just update SysNAND. As opposed to the traditional way of doing it by copying SysNAND to EmuNAND. Granted, you might still have to reinstall any DSiWare or GBA titles, but those are relatively small compared to your retail 3DS games, right? Just a guess at something that might help.

Thanks I'll went ahead with updating to 11.2 Emunand using sysUpdater, since I have a backup anyways, and it looks like it works.
I wonder if that concept would work the same with having two separate EmuNands, since the CFWs let you have as many as 4? Then I could have my SysNand still on 9.0 and working, one EmuNand on 11.2 for Gateway, and one on 11.5 for Luma. I know it seems silly, but I like the feeling of knowing my SysNand is safe from any possibility of accidental mess-ups.

Kazuma77 · Jul 28, 2017

gamerboy1995 said:
Thanks I'll went ahead with updating to 11.2 Emunand using sysUpdater, since I have a backup anyways, and it looks like it works.
I wonder if that concept would work the same with having two separate EmuNands, since the CFWs let you have as many as 4? Then I could have my SysNand still on 9.0 and working, one EmuNand on 11.2 for Gateway, and one on 11.5 for Luma. I know it seems silly, but I like the feeling of knowing my SysNand is safe from any possibility of accidental mess-ups.

It's your system. The only person your configuration has to please is you. And yes, that will work. Inject an EmuNAND backup into slot 2 with Multi EmuNAND Creatior then just update it with Luma. Gateway always has to have the first EmuNAND. But Luma, Puma, Skeith, and Cakes can launch pretty much any of them (actually, according to Skeith's config menu, it supports up to 10). There's probably not a way to create a GM9 script to sync tickets, because I don't see a command to switch EmuNANDs, but, it's really not that complicated to do manually. It's not like ticket.db is nested deep in multiple folders. Aside from that, it would pretty much be just like mine, but in reverse, with SysNAND being the low version instead of the high version.

Actually, your concerns aren't completely unfounded. I have accidentally run Cakes unconfigured before (thumb slipped, hit B then A while in the configuration menu, so it backed out and ran it without any patches). I've even messed up and entered the GW SysNAND boot sequence on my hard-modded unit after updating it (good thing it was that one). Then again, not many people run Cakes anymore, and this is only a potential problem during initial configuration. If you're used to running GW from EmuNAND, you haven't made the deadly mistake of committing the SysNAND combo to muscle memory. And Corbenik/Skeith is virtually impossible to boot by accident. So, overall, updating SysNAND is still pretty safe. But it's not like things can't go wrong. And it's not like DSiWare and GBA injects need 11.x. So, again, if you're happy with it, that's all that matters.

gamerboy1995 · Jul 28, 2017

Kazuma77 said:
It's your system. The only person your configuration has to please is you. And yes, that will work. Inject an EmuNAND backup into slot 2 with Multi EmuNAND Creatior then just update it with Luma. Gateway always has to have the first EmuNAND. But Luma, Puma, Skeith, and Cakes can launch pretty much any of them (actually, according to Skeith's config menu, it supports up to 10). There's probably not a way to create a GM9 script to sync tickets, because I don't see a command to switch EmuNANDs, but, it's really not that complicated to do manually. It's not like ticket.db is nested deep in multiple folders. Aside from that, it would pretty much be just like mine, but in reverse, with SysNAND being the low version instead of the high version.

Actually, your concerns aren't completely unfounded. I have accidentally run Cakes unconfigured before (thumb slipped, hit B then A while in the configuration menu, so it backed out and ran it without any patches). I've even messed up and entered the GW SysNAND boot sequence on my hard-modded unit after updating it (good thing it was that one). Then again, not many people run Cakes anymore, and this is only a potential problem during initial configuration. If you're used to running GW from EmuNAND, you haven't made the deadly mistake of committing the SysNAND combo to muscle memory. And Corbenik/Skeith is virtually impossible to boot by accident. So, overall, updating SysNAND is still pretty safe. But it's not like things can't go wrong. And it's not like DSiWare and GBA injects need 11.x. So, again, if you're happy with it, that's all that matters.

Well, I was going to try to do it my way, until I found out I'd need to cut/paste all the files from my 128 GB SD card that was almost full onto my PC before adding the second EmuNAND and then paste them all back, so I just went ahead and did what you suggested earlier - restored a backup of my EmuNAND to SysNAND and now I've got SysNAND 11.5U for Luma and 11.2U for Gateway.
Would be nice if I could give them different themes from each other to make it easier to tell at a glance which I'm on, but that doesn't seem to be possible.

Shame it doesn't seem to fix the fact I keep crashing when trying to play Ever Oasis, either... That's a topic for another thread, though.

Kazuma77 · Jul 28, 2017

gamerboy1995 said:
Well, I was going to try to do it my way, until I found out I'd need to cut/paste all the files from my 128 GB SD card that was almost full onto my PC before adding the second EmuNAND and then paste them all back, so I just went ahead and did what you suggested earlier - restored a backup of my EmuNAND to SysNAND and now I've got SysNAND 11.5U for Luma and 11.2U for Gateway.
Would be nice if I could give them different themes from each other to make it easier to tell at a glance which I'm on, but that doesn't seem to be possible.

Shame it doesn't seem to fix the fact I keep crashing when trying to play Ever Oasis, either... That's a topic for another thread, though.

Themes get shared with linked NANDs, but folders do not. You could make one named "EmuNAND" or just "E" to tag your EmuNAND as such. Oh yeah, those scripts I keep mentioning. I'll post them now. Maybe you'll find them useful.

jamz · Jul 29, 2017

hello

i'm trying to follow this tutorial https://gbatemp.net/threads/importing-gateway-saves-to-cia-games.425743/ to transfer a .3ds save file to .cia. but i'm stuck at step 6

Press home and close it. Press select to open Gateway's rom menu and choose the game you're about to work on, but don't go into the game

cause my sysnand is in 11.5 and i am afraid going in gateway mode will leave me with an unhacked console since emunand don't support firmware above 11.2.

my question is it safe to press select and load gateway?

sorry for asking something so noob, but until yesterday i was a gateway user so al this CF is new to me.

Kazuma77 · Jul 29, 2017

jamz said:
hello

i'm trying to follow this tutorial https://gbatemp.net/threads/importing-gateway-saves-to-cia-games.425743/ to transfer a .3ds save file to .cia. but i'm stuck at step 6 cause my sysnand is in 11.5 and i am afraid going in gateway mode will leave me with an unhacked console since emunand don't support firmware above 11.2.

my question is it safe to press select and load gateway?

sorry for asking something so noob, but until yesterday i was a gateway user so al this CF is new to me.

I can tell you first hand, if you boot GW to a SysNAND above 11.2 you will end up on retail if you have an O3DS. I've done it with a hard-modded unit just to confirm. It ended up on retail. An N3DS would probably brick, having an invalid secret sector. Then again, I don't know if B9S replaces the secret sector or not. Mine would brick though, because it used to be running A9LH, and that did.

I'd heavily advise creating an EmuNAND if you are running your system without one. You can use a backup of your SysNAND, you'll just need to downgrade it with SysUpdater or that 3Down someone else mentioned. You can easily download a full 11.2 set with 3DNUS (and I've heard that certain iso and chaos sites have it too). And 11.4 for that matter if you want to try the partial upgrade trick in the other thread (make a backup in case it doesn't work though)

And if you or anyone else would rather download a pre-made configuration than follow the lengthy list of steps in this guide, I've uploaded 3 here. No offense to the guide's creator, but, sometimes it's just easier having a pre-made example to refer to. It does reduce the number of chainloaders used, because I converted the GW loader to a .firm file, so it doesn't need v2gw.bin. A bit cleaner and more direct. Though to be fair, unless you're Lt. Commander Data, you're unlikely to notice a difference in boot time.

gnmmarechal said:
I can't help but laugh at this post.

Sent from my cave of despair where I don't stalk Seriel

That almost reads like an apology. There's nothing wrong with having a sense of humor. I was trying to make a point, but there was some intended comedy in there. It's good to know someone got it.

alucard_xs · Jul 30, 2017

HI dudes,

So I'm now on CFW B9S + Luma3DS on my new 2DS XL, but can I still use my Gateway card ?

gamerboy1995 · Jul 30, 2017

alucard_xs said:
HI dudes,

So I'm now on CFW B9S + Luma3DS on my new 2DS XL, but can I still use my Gateway card ?

only if you have an Emunand (or Sysnand, but not recommended) on 11.2 or below

kazerei · Jul 30, 2017

thanks for the guide, all works flawlessly, bit now i have a quick question right now I only have games installed on sysnand and in the emunand only the ones on the gateway card, and also I have on both the same NNID, is this ok? or Its not safe and should unlink the nnid on the emunand and use another?

k7ra · Aug 4, 2017

No questions

henrytlh · Aug 6, 2017

Can I have SYSNAND Luma on 11.5 and Gateway Emunand on 11.2? Currently running SYSNAND a9lh 11.3+Gateway EMUNAND 11.2. I've read using payload will remove the a9lh(I hold the up button before boot to go directly into Gateway Emunand if I need it). Are there any chance of bricking besides updating in Gateway SYSNAND mode? What is the best setup if I want to update to latest B9S and continue using Gateway?

p/s my concern is I do not want to brick my N3DS and also accidentally removing the B9S

k7ra · Aug 6, 2017

henrytlh said:
Can I have SYSNAND Luma on 11.5 and Gateway Emunand on 11.2? Currently running SYSNAND a9lh 11.3+Gateway EMUNAND 11.2. I've read using payload will remove the a9lh(I hold the up button before boot to go directly into Gateway Emunand if I need it). Are there any chance of bricking besides updating in Gateway SYSNAND mode? What is the best setup if I want to update to latest B9S and continue using Gateway?

p/s my concern is I do not want to brick my N3DS and also accidentally removing the B9S

Ofc you can have SYSNAND Luma on 11.5 and Gateway Emunand on 11.2.
The best setup if you want to update to latest B9S and continue using Gateway is update to latest B9S and continue using Gateway...
I installed last B9S and continue using Gateway, so dunno why you cant then...

Install last B9S like all do and follow this thread instructions.
So far you can have Sysnand on any version of Luma and emunand for GW if you want.
But I use emunand for GW and Luma same time, no problems so far.
If I wanna cheat and play 3ds games boot GW, on default online play I boot Luma

PeadyJ · Aug 7, 2017

Hi Guys, i've been away from 3DS hacking for ages and just wanting to clarify some stuff.
I am running normal sysnand 9.2 with gateway emunand 11.2 and menuhacks (No gateway Al94h)

I'm guessing i follow this guide https://3ds.guide/ and not copy my emunand to sysnand.

then after this is done, i do this guide? My question is, how do i then choose to boot into CFW sysnand on 11.5 or my Gateway emunand on 11.2? I'm scared because it says don't boot into GW mode (i think thats Gateway Emunand?) if you have sysnand 11.5 which i will from Luma CFW?

It says it will boot directly into gateway emunand which is what i want. But no idea then how to boot into luma (as i want to play ever oasis on firmware 11.5)

Please help, i'm scared and i don't want to brick my 3DS but i really want to play ever oasis.

Kazuma77 · Aug 7, 2017

PeadyJ said:
Hi Guys, i've been away from 3DS hacking for ages and just wanting to clarify some stuff.
I am running normal sysnand 9.2 with gateway emunand 11.2 and menuhacks (No gateway Al94h)

I'm guessing i follow this guide https://3ds.guide/ and not copy my emunand to sysnand.

then after this is done, i do this guide? My question is, how do i then choose to boot into CFW sysnand on 11.5 or my Gateway emunand on 11.2? I'm scared because it says don't boot into GW mode (i think thats Gateway Emunand?) if you have sysnand 11.5 which i will from Luma CFW?

It says it will boot directly into gateway emunand which is what i want. But no idea then how to boot into luma (as i want to play ever oasis on firmware 11.5)

Please help, i'm scared and i don't want to brick my 3DS but i really want to play ever oasis.

Right, you follow the guide, but you probably DO want to copy EmuNAND to SysNAND as it suggests, and update SysNAND, but don't delete EmuNAND. That way your NANDs are linked. Gateway looks for EmuNAND by default, so as long as you have one and don't go into the menu and enter the combination to boot to SysNAND, and confirm the choice (and it does ask you to confirm), you'll be fine. If it doesn't find an EmuNAND it will ask you to press a combo to boot SysNAND, so, just don't do it if you see that. The guide only sets up Luma and Godmode9 though, not Gateway or anything else. So, you can either follow this tutorial, or I have some pre-made configurations here you can check out that have Gateway already setup for you. I've also included some Godmode9 scripts for syncing tickets between SysNAND and EmuNAND. So, all you have to do if you install new games in Luma on SysNAND is reboot into GM9, run the "Synchronize Tickets (Sys to Emu)" script from the scripts menu, then reboot into GW mode and your new games are there. This is why I suggest linking. Though it's your choice.

And if you did want to keep your 9.2 (I'd back it up just in case either way), you could setup a second EmuNAND using 3DS Multi EmuNAND Creator. This will wipe the card though, so you would need to back it up. I like having something I can auto-boot into Menuhax and have launch straight into the homebrew menu. Keep in mind, Luma probably won't boot it. It always crashes with mine. That's why I include a copy of Puma. You can set that to automatically boot EmuNAND 2 and have a quick HB menu on hotkey. Or you could just setup a 9.2 EmuNAND on a second card. Either is optional. You can always just use Soundhax or Ninjhax (from an installed CIA of Cubic Ninja) from the 11.2 EmuNAND if you want to run the homebrew that Rosalina crashes with. I'm just used to keeping 9.2 around so I don't have to wait for a new *hax exploit every update. Though if Rosalina runs all the homebrew titles you're interested in, that's a non-issue. It crashes on some of the ones I run though.

I should also mention that there's a guide to partially update your EmuNAND to 11.4 while keeping it GW-compatible here if you're interested. Though it's easier to use the latest 3DNUS release, grab the full 11.4 set, copy it to the "updates" folder on your SD card, then delete the 3 titles it tells you not to update, than to download all those titles manually. If it's an O3DS, you also want to remove "000400300000CC02.cia" and "0004013000008002.cia" from the "updates" folder. The only catch is, neither Ninjhax nor Soundhax will work on 11.4 on an O3DS (though Ninjhax is working with 11.4 and 11.5 on the N3DS). So, if you want to still be able to run ctrQuake, Spectre3DS, ctrHexenII, eDuke3D, ctrWolfen, and/or 3DScraft (which all either crash, exit, or have corrupted graphics in Rosalina) on an O3DS, setting up the aforementioned second EmuNAND on 9.2 might not be optional. I have plenty of space on my card, so I don't mind doing that. But it depends on if any of the above even interest you I guess. And Rosalina will probably get them working eventually.

Hayabusa 7 · Aug 8, 2017

Hello everyone. Just have a quick question. Managed to run my gateway red card successfully. However, the GW blue card only works in emunand. In sysnand with the blue card, I am greeted with a black screen.
I assume I can use it on emunand safely? Running luma on 11.2 both nands. Reason being I only have a 4gb SD card and a 32gb Micro sd card for GW so hence why I can't really use luma that much.
Thank you in advance for your help

.

CHRoNiCWiLL · Aug 12, 2017

Kyrara · Aug 16, 2017

is there a way to Boot directly into Gateway without pushing a button?
I dont have found something that it Autoboot the Payload.

Kazuma77 · Aug 16, 2017

Kyrara said:
is there a way to Boot directly into Gateway without pushing a button?
I dont have found something that it Autoboot the Payload.

Sure, just use my BootCTR9 or CBM9 configuration found here. The default configuration files run Luma by default. However, there's a "boot_config_gw.ini" for BootCTR9 and an "a9lh_gw.cfg" for CBM9. Just take the "_gw" part off to make them your active configuration file, and GW will launch by default. Even the backwards method presented here doesn't have to use Luma's chainloader. It just needs Gateway.bin in Luma's payloads folder for some unexplained reason. I mean, why would you want something on the GUI that won't even run? They should have used an out-of-the-way location like "a9lh/payloads" instead.

Keep in mind that some of the payloads used are now outdated, like Luma and GM9. I'm working on an update. Still, it provides a good example of how to set it up.

Attachments

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Attachments

Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

Member

Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum