Using Luma3DS + Gateway on B9S

simalexander3009 · Feb 20, 2018

I followed the guide to install gateway exactly but I can't boot into gateway. I am on firmware 9.2.0-20U. I am pressing DPAD-DOWN on bootup but it doesn't boot into gateway. It just boots into Luma I don't even get the dragon logo at all. I am on Luma 9.0 and I have the latest version of bootstrap installed. I was using Gateway as my EmuNand before I installed Luma so I know it was working with my 3DS. If someone can help me fix this problem that would be really great.

EDIT: I got it to work.

Maximilious · Feb 20, 2018

Kazuma77 said:
That's why I include the option to synchronize tickets in InScripted. No gift wrap issues as long as you synchronize before switching. Themes are shared, but ironically, folders are not. So you could easily make a folder named "EmuNAND" or just "E" and know which is which. I find the convenience of being able to play the same games on both worth the hassle of having to synchronize after installing new games. But to each their own.

Nice, I didn't know that. I find myself in sysNAND a lot more that GW mode anymore, and install everything to sysNAND anyway. I'm just used to having them separate after years of keeping them that way haha.

RussellClarke · Mar 12, 2018

Guys... I've just found this thread and read the big red text in the OP

.. I just updated my Luma, boot9 and upgraded to 11.6 and everything was great. I then tested my gateway launcher and now i have stock FW with no luma. I probably know the answer to this but is there anyway I can get CFW back? Or do i need to just buy another 3ds?

Mylink5 · May 27, 2018

Hello!
So I used this guide a while back to set up my o3DSXL.Now I am thinking of ditching GW and have only luma so I can update. How would I go about doing that? Thanks

ken28 · May 27, 2018

Just ditch gw and use Luma.

Maximilious · May 27, 2018

Mylink5 said:
Hello!
So I used this guide a while back to set up my o3DSXL.Now I am thinking of ditching GW and have only luma so I can update. How would I go about doing that? Thanks

If you properly unlinked your NAND's as you should have done when setting up emuNAND anyway, then you can update your sysNAND while in Luma and keep your emuNAND on 11.2. One flaw of this guide is they don't detail how to unlink your NAND during setup, which if you have a lot of games installed to sysNAND/Luma would take a lot of time to set up again.

Mylink5 · May 27, 2018

Maximilious said:
If you properly unlinked your NAND's as you should have done when setting up emuNAND anyway, then you can update your sysNAND while in Luma and keep your emuNAND on 11.2. One flaw of this guide is they don't detail how to unlink your NAND during setup, which if you have a lot of games installed to sysNAND/Luma would take a lot of time to set up again.

I am sure I had emunand when I was using only GW but after the guide when booting to GW it says GW fastboot:Sysnand and on system settings the fw says Ver. 11.0.0.
How can I remove the GW stuff from my console and only have Luma?

Maximilious · May 27, 2018

Mylink5 said:
I am sure I had emunand when I was using only GW but after the guide when booting to GW it says GW fastboot:Sysnand and on system settings the fw says Ver. 11.0.0.
How can I remove the GW stuff from my console and only have Luma?

I'm not sure at all, but if it were me I'd grab a sysNAND backup and probably just start over on the official 3ds.guide (after B9S since you already have it). Perform a system reset, clear SD card and only have items you need on it for Luma and anything else excluding GW stuff. I'm not very versed in Luma/B9S as I only set it up once and have a "set it and forget it" mentality with that kind of stuff.

Mylink5 · May 27, 2018

Maximilious said:
I'm not sure at all, but if it were me I'd grab a sysNAND backup and probably just start over on the official 3ds.guide (after B9S since you already have it). Perform a system reset, clear SD card and only have items you need on it for Luma and anything else excluding GW stuff. I'm not very versed in Luma/B9S as I only set it up once and have a "set it and forget it" mentality with that kind of stuff.

Hmm, I'd have to check if I lost my sysNand backup when my drive failed (if that's the case is there anything I can do?). So when I find my backup, is there a specific section for it in the guide ? How do i use the backup ? Thanks for your time and sorry for the many questions. Studying drove me away from the scene.

Maximilious · May 27, 2018

Mylink5 said:
Hmm, I'd have to check if I lost my sysNand backup when my drive failed (if that's the case is there anything I can do?). So when I find my backup, is there a specific section for it in the guide ? How do i use the backup ? Thanks for your time and sorry for the many questions. Studying drove me away from the scene.

It's fine, since you have B9S you can boot into GodMode and take a new sysNAND backup, and also options to restore sysNAND too. You'll keep that on your SD card root in case you need to restore to it (or place your backup there if you find it). You'll definitely want to do some more research before moving forward though, or just make a new thread describing how you want to remove GW stuff and just go with Luma. I'm sure someone else has made one in your exact situation and previous thread may have info (even though search is really bad here).

Personally, I keep my offline games for my GW emuNAND card and install Online-Only in my updated sysNAND so I don't lose out on my investment in my GW card, but it's up to you if you want to remove it completely.

Mylink5 · May 27, 2018

Maximilious said:
It's fine, since you have B9S you can boot into GodMode and take a new sysNAND backup, and also options to restore sysNAND too. You'll keep that on your SD card root in case you need to restore to it (or place your backup there if you find it). You'll definitely want to do some more research before moving forward though, or just make a new thread describing how you want to remove GW stuff and just go with Luma. I'm sure someone else has made one in your exact situation and previous thread may have info (even though search is really bad here).

Personally, I keep my offline games for my GW emuNAND card and install Online-Only in my updated sysNAND so I don't lose out on my investment in my GW card, but it's up to you if you want to remove it completely.

The thing is, that I am not sure if my GW boots from emunand, so if that is the case, I wouldnt be able to update, right? Because, in the past when I for sure had emunand,it said so in the system settings, but now it only says VER and when booting GW it says "GW FASTBOOT: Sysnand". So, not sure if I am able to update.

Maximilious · May 27, 2018

Mylink5 said:
The thing is, that I am not sure if my GW boots from emunand, so if that is the case, I wouldnt be able to update, right? Because, in the past when I for sure had emunand,it said so in the system settings, but now it only says VER and when booting GW it says "GW FASTBOOT: Sysnand". So, not sure if I am able to update.

Correct, you're running from sysNAND so as this guide states you will lose B9S if you update. If I recall, all you should have to do is replace your GW.bin in the Luma plugin folder with the normal Luma.bin, but I'm not 100% certain. Really, all you should really need to to is follow this guide in reverse to remove the changes it makes. Let me look it over real quick to see what is changed in regards to SD files.

Edit: Yeah, looks like all you really need to do is replace your boot.ini file with the original one to go back to using just Luma, since all this guide is doing is placing GW's A9LH.bin and a Luma payload file, and then changing the boot chain to point to the GW Payload in the Payload folder.

Edit2: Again, I'd just do some quick research on the forum to see if anyone else has rolled this guide back, but I think that's all you need to do. There's also the "dev built CTR9" which I'm not sure what that does, but if you follow 3ds.guide again and get the original files I think you should be alright.

Temptress Cerise · May 27, 2018

Maximilious said:
Correct, you're running from sysNAND so as this guide states you will lose B9S if you update. If I recall, all you should have to do is replace your GW.bin in the Luma plugin folder with the normal Luma.bin, but I'm not 100% certain. Really, all you should really need to to is follow this guide in reverse to remove the changes it makes. Let me look it over real quick to see what is changed in regards to SD files.

Edit: Yeah, looks like all you really need to do is replace your boot.ini file with the original one to go back to using just Luma, since all this guide is doing is placing GW's A9LH.bin and a Luma payload file, and then changing the boot chain to point to the GW Payload in the Payload folder.

Edit2: Again, I'd just do some quick research on the forum to see if anyone else has rolled this guide back, but I think that's all you need to do. There's also the "dev built CTR9" which I'm not sure what that does, but if you follow 3ds.guide again and get the original files I think you should be alright.

If this guide was actually followed, then they would be booting into Luma3DS with nothing pressed. So if he’s automatically booting into Gateway, then he made his own changes or followed something else.

Mylink5 · May 27, 2018

Maximilious said:
Correct, you're running from sysNAND so as this guide states you will lose B9S if you update. If I recall, all you should have to do is replace your GW.bin in the Luma plugin folder with the normal Luma.bin, but I'm not 100% certain. Really, all you should really need to to is follow this guide in reverse to remove the changes it makes. Let me look it over real quick to see what is changed in regards to SD files.

Edit: Yeah, looks like all you really need to do is replace your boot.ini file with the original one to go back to using just Luma, since all this guide is doing is placing GW's A9LH.bin and a Luma payload file, and then changing the boot chain to point to the GW Payload in the Payload folder.

Edit2: Again, I'd just do some quick research on the forum to see if anyone else has rolled this guide back, but I think that's all you need to do. There's also the "dev built CTR9" which I'm not sure what that does, but if you follow 3ds.guide again and get the original files I think you should be alright.

Oh, so it's as simple as changing one file? Thanks!

Temptress Cerise said:
If this guide was actually followed, then they would be booting into Luma3DS with nothing pressed. So if he’s automatically booting into Gateway, then he made his own changes or followed something else.

I actually boot into Luma...

Temptress Cerise · May 27, 2018

Mylink5 said:
Oh, so it's as simple as changing one file? Thanks!

I actually boot into Luma...

Then delete the GW files. I’m not sure what is so difficult to undo. This guide was written to give you the option to boot into GW, it was not meant to make GW your default, unless you purposely deviated from the instructions and did that on your own.

Mylink5 · May 27, 2018

Temptress Cerise said:
Then delete the GW files. I’m not sure what is so difficult to undo. This guide was written to give you the option to boot into GW, it was not meant to make GW your default, unless you purposely deviated from the instructions and did that on your own.

I followed the guide to the word so I should be fine. It is just that I did this a long time ago and I didn't remember if what I did made permanent changes. Thanks!!

mikey420 · Jun 28, 2018

Does anyone have a .ini file that works? For some reason when I launch the bootctr.firm file it gives me an error saying Pani failed to load something something.... The firm file launches fine through luma chain loader but doesn't load anything.

Maximilious · Jun 29, 2018

mikey420 said:
Does anyone have a .ini file that works? For some reason when I launch the bootctr.firm file it gives me an error saying Pani failed to load something something.... The firm file launches fine through luma chain loader but doesn't load anything.

Did you configure the .ini file like the OP says? You can also make a new notepad document, paste the following in and rename the extension from .txt to .ini:

[BOOTCTR9]
key_delay = 1000

[DEFAULT]
path = /luma/payloads/v2gw.bin

Arnold101 · Aug 1, 2018

if i update to the 11.8 i lost gateway again? this hack can be fixed for the new firmware?

Temptress Cerise · Aug 1, 2018

Arnold101 said:
if i update to the 11.8 i lost gateway again? this hack can be fixed for the new firmware?

Do you have an EmuNAND setup?

Attachments

Active Member

Whistles a familiar tune

Member

Well-Known Member

Well-Known Member

Whistles a familiar tune

Well-Known Member

Whistles a familiar tune

Well-Known Member

Whistles a familiar tune

Well-Known Member

Whistles a familiar tune

Miss Magic~ <3

Well-Known Member

Miss Magic~ <3

Well-Known Member

Well-Known Member

Whistles a familiar tune

Well-Known Member

Miss Magic~ <3

Similar threads

Popular threads in this forum