Using Luma3DS + Gateway on B9S

ultimatetemper · Jul 22, 2017

You needed the GW EmuNAND installed first.
If not, you're screwed (unless there's a way to copy EmuNAND with GodMode9 or something)

xxfliermiles · Jul 22, 2017

ultimatetemper said:
You needed the GW EmuNAND installed first.
If not, you're screwed (unless there's a way to copy EmuNAND with GodMode9 or something)

Gateway EMUNAND 11.2 is on a separate SD card...

Wen installing LUMA 3DS 11.5, I thought it wouLD instALL oN The SD CarD ONLY (AND Not Boot if tHe SD Card is taken out)

Darn, so tHere is No way for me to revert to 9.2 SYSNAND? Get 11.2 EMUNAND for GW... TheN Get LUMA 3DS 11.5?

ultimatetemper · Jul 22, 2017

I don't know about all of GodMode9's options, maybe there's an option to create an EmuNAND partition and then use the EmuNAND tool to transfer that emuNAND from one SD to another.

Temptress Cerise · Jul 22, 2017

xxfliermiles said:
Gateway EMUNAND 11.2 is on a separate SD card...

Wen installing LUMA 3DS 11.5, I thought it wouLD instALL oN The SD CarD ONLY (AND Not Boot if tHe SD Card is taken out)

Darn, so tHere is No way for me to revert to 9.2 SYSNAND? Get 11.2 EMUNAND for GW... TheN Get LUMA 3DS 11.5?

I think you are completely confused as to what 3DS.Guide achieves. The point of following 3DS.Guide to the end, without deviating from it, is to have an up-to-date SysNAND w/ Luma3DS. With that setup, there is no need to ever have to need or want to be on a low firmware like 9.2. EVER. Anything that required 9.2, such as menuhax do not work at all.

The point of this guide, is that if you somehow manage to keep an EmuNAND on 11.2 or lower, that you can still use it.

If your running an SD Card on GW EmuNAND and one for SysNAND. Then you need to get that, your SysNAND will always be on the same firmware, that's because the SysNAND is INTERNAL to the 3DS and does not have anything to do with SD Cards. The only thing that the SD Card would have is the boot.firm, and even then, Luma3DS can boot of the CTRNAND part of SysNAND and not even need an SD Card to even boot.

Now, if you want to get a GW EmuNAND setup, you can go ahead and backup the contents of your SD Card, and then use GodMode9 to make a GW EmuNAND, if you happen to have a GW EmuNAND .bin backup on 11.2 or lower, that you want to use, then you'd figure out how to do that in GodMode9, and restore it. Now, if you have no EmuNAND .bin backup, then you still have to make a GW EmuNAND in GodMode9, then use sysUpdater to downgrade to 11.2, you'd need to use 3DNUS to get the required files to downgrade. You'd have to use Luma3DS and boot your GW EmuNAND through that.

If nothing I said makes sense, then maybe someone else can guide you through it, but I won't. Sorry.

xxfliermiles · Jul 22, 2017

makes sense, just a quicc point to ASk however...

Kan u use GoDMoDe9 On A LUMA 3DS 1.5 to set up GW EMUNAND 11.2 (if u have an 11.2 EMUNAND BiN rDY)?

gamerboy1995 · Jul 23, 2017

OP, what is your opinion of the B9S gateway payload someone posted at https://gbatemp.net/threads/release-the-bootctr9-release-thread.435347/page-5#post-7457140 ?
The poster says

BTW, I've included a converted GW payload in case you or anyone else needs it. This obsoletes the old v2gw.bin trick. The converted payload doesn't need it. Just place it wherever you want it (I use a folder named /b9s/payloads) and have BootCTR9 launch it directly.

Would that work any better as a Gateway access point than using the method described in this tutorial, because it seems less roundabout?

gamerboy1995 · Jul 24, 2017

So I followed your guide and tried to set it up to load Gateway when I hold R. It looks like it works when I hold START to go to the chainloader menu and then choose "R_BootCTR9" from that list, but if I just hold the R button it gives me a black screen followed by a crash screen saying something like "Data Abort". What would cause that?
Also, NTR doesn't appear to work correctly in Luma mode, but does in Gateway mode? I honestly don't remember if it had that problem before or not...

Kazuma77 · Jul 25, 2017

Temptress Cerise said:
I think you are completely confused as to what 3DS.Guide achieves. The point of following 3DS.Guide to the end, without deviating from it, is to have an up-to-date SysNAND w/ Luma3DS. With that setup, there is no need to ever have to need or want to be on a low firmware like 9.2. EVER. Anything that required 9.2, such as menuhax do not work at all.

The point of this guide, is that if you somehow manage to keep an EmuNAND on 11.2 or lower, that you can still use it.

If your running an SD Card on GW EmuNAND and one for SysNAND. Then you need to get that, your SysNAND will always be on the same firmware, that's because the SysNAND is INTERNAL to the 3DS and does not have anything to do with SD Cards. The only thing that the SD Card would have is the boot.firm, and even then, Luma3DS can boot of the CTRNAND part of SysNAND and not even need an SD Card to even boot.

Now, if you want to get a GW EmuNAND setup, you can go ahead and backup the contents of your SD Card, and then use GodMode9 to make a GW EmuNAND, if you happen to have a GW EmuNAND .bin backup on 11.2 or lower, that you want to use, then you'd figure out how to do that in GodMode9, and restore it. Now, if you have no EmuNAND .bin backup, then you still have to make a GW EmuNAND in GodMode9, then use sysUpdater to downgrade to 11.2, you'd need to use 3DNUS to get the required files to downgrade. You'd have to use Luma3DS and boot your GW EmuNAND through that.

If nothing I said makes sense, then maybe someone else can guide you through it, but I won't. Sorry.

Actually, 9.2 works fine. I'm loading it, with Menuhax installed, from a second EmuNAND created using Multi EmuNAND Creation Tool (I had problems with the current version, though, so I uploaded an older copy here). I'm even having that further chain into BootCTR so I can choose between Gridlauncher and the new menu (I'm actually quite impressed with it's backwards compatibility, especially with it primarily being written for Rosa). ctrQuake, Spectre3DS, and ctrHexenII are all running fine in my B9S setup (Rosa crashes on them all). You just have to load this 9.2 EmuNAND via Puma or Cakes on on O3DS. On an N3DS, only Puma seems work (and you have to provide a fully decrypted 9.0 firmware file on the N3DS as well, but GM9 can do said decryption easily). And of course, you have to use BootCTR9 to run Puma, since Luma doesn't support firmtool-converted payloads (though it might be better to leave it unconverted, because it still needs a .bin copy for reboot patches to work).

You really should update your guide though. The v2gw.bin file you're using was never needed. All you had to do was convert the GW A9LH payload to a .firm using firmtool (the "-e 0" example in the readme works fine). As someone else has already pointed out, I did upload a copy here in case anyone needs it. Feel free to use it. Just point BootCTR9 directly to it and it loads just fine. Besides, you would need to hex edit v2gw.bin if you were wanting to use something other than Luma for your chainloader. As you might have noticed, I've always done that in my AIO A9LH packs, changing the "luma" to "a9lh" so it can work with anything. Also, this allows you keep payloads that won't work from showing up in GUI mode. There's no such thing as too foolproof (I'd recommend putting "Gateway.firm" in something like "b9s/payloads" myself).

Speaking of my old AIO packs, I'm working on one for B9S now. Keep an eye out for it. I'm including a GM9 script that installs Luma to CTRNAND for you (wait till Plaillect gets a load of it, he can change that part of his guide to "run this script"

). I'll also be including an A9LH to B9S installer with a post-install clean-up script that deletes every file in it (including itself, but it leaves the backups in the "boot9strap" folder). I may do a couple of scripts to sync tickets for those using linked NANDs as well. Install new content on SysNAND, run script, reboot to EmuNAND, and it's ready to use with GW's cheat engine.

gamerboy1995 said:
So I followed your guide and tried to set it up to load Gateway when I hold R. It looks like it works when I hold START to go to the chainloader menu and then choose "R_BootCTR9" from that list, but if I just hold the R button it gives me a black screen followed by a crash screen saying something like "Data Abort". What would cause that?
Also, NTR doesn't appear to work correctly in Luma mode, but does in Gateway mode? I honestly don't remember if it had that problem before or not...

Simple. "R" is a reserved key, just like "A" and "select" -- you have to hold L with it to use it as a hotkey. When used by itself, it tries to boot EmuNAND using SysNAND's NATIVE_FIRM. Actually, if you have the second option checked in settings, it will try to boot SysNAND with EmuNAND's firm. There used to be another setting that defined which used firmware.bin. The right combo actually allowed you to have it boot SysNAND with a firmware.bin file. That was great back when you needed to use one to run NTR. But I'm not sure what you'd use it for now.

Onepunchbruh · Jul 25, 2017

Hey i'm on B9S 11.2E firmware. How do I use gateway on it?

Ace-D · Jul 25, 2017

Hello. I have Bootstrap9 with luma 8.1 on 3ds firmware 11.5. the thing is I wanted to follow this to get back my Gateway saves but obviously cant with that firmware. I also formatted the emunand card after migrating so i cant do anything (that involves something too complicated like downgrading, 3ds which I softbricked before). Im new here so before posting anything would you direct me to the right direction? All I want are my GW saves to import them with SDF or JKSM to my current cias. All this time searching Ive found no PC nor 3ds utility to decrypt those saves. If anything, are there posts or people that can export those saves with their GW for me? Thnks

gamerboy1995 · Jul 25, 2017

Ace-D said:
Hello. I have Bootstrap9 with luma 8.1 on 3ds firmware 11.5. the thing is I wanted to follow this to get back my Gateway saves but obviously cant with that firmware. I also formatted the emunand card after migrating so i cant do anything (that involves something too complicated like downgrading, 3ds which I softbricked before). Im new here so before posting anything would you direct me to the right direction? All I want are my GW saves to import them with SDF or JKSM to my current cias. All this time searching Ive found no PC nor 3ds utility to decrypt those saves. If anything, are there posts or people that can export those saves with their GW for me? Thnks

The problem is that you should have exported the saves from Gateway before updating to 11.5. Unless you downgrade back to 11.2, or get someone else to export the saves for you, there's really nothing you can do.

Onepunchbruh · Jul 26, 2017

gamerboy1995 said:
The problem is that you should have exported the saves from Gateway before updating to 11.5. Unless you downgrade back to 11.2, or get someone else to export the saves for you, there's really nothing you can do.

Hey i'm on 11.2 b9s. Can you help me out? How should I use gateway on b9s?

Ace-D · Jul 26, 2017

Haider Raza said:
Hey i'm on 11.2 b9s. Can you help me out? How should I use gateway on b9s?

read the tutorial on page 1

Temptress Cerise · Jul 26, 2017

Kazuma77 said:
Actually, 9.2 works fine. I'm loading it, with Menuhax installed, from a second EmuNAND created using Multi EmuNAND Creation Tool (I had problems with the current version, though, so I uploaded an older copy here). I'm even having that further chain into BootCTR so I can choose between Gridlauncher and the new menu (I'm actually quite impressed with it's backwards compatibility, especially with it primarily being written for Rosa). ctrQuake, Spectre3DS, and ctrHexenII are all running fine in my B9S setup (Rosa crashes on them all). You just have to load this 9.2 EmuNAND via Puma or Cakes on on O3DS. On an N3DS, only Puma seems work (and you have to provide a fully decrypted 9.0 firmware file on the N3DS as well, but GM9 can do said decryption easily). And of course, you have to use BootCTR9 to run Puma, since Luma doesn't support firmtool-converted payloads (though it might be better to leave it unconverted, because it still needs a .bin copy for reboot patches to work).

You really should update your guide though. The v2gw.bin file you're using was never needed. All you had to do was convert the GW A9LH payload to a .firm using firmtool (the "-e 0" example in the readme works fine). As someone else has already pointed out, I did upload a copy here in case anyone needs it. Feel free to use it. Just point BootCTR9 directly to it and it loads just fine. Besides, you would need to hex edit v2gw.bin if you were wanting to use something other than Luma for your chainloader. As you might have noticed, I've always done that in my AIO A9LH packs, changing the "luma" to "a9lh" so it can work with anything. Also, this allows you keep payloads that won't work from showing up in GUI mode. There's no such thing as too foolproof (I'd recommend putting "Gateway.firm" in something like "b9s/payloads" myself).

Speaking of my old AIO packs, I'm working on one for B9S now. Keep an eye out for it. I'm including a GM9 script that installs Luma to CTRNAND for you (wait till Plaillect gets a load of it, he can change that part of his guide to "run this script" ). I'll also be including an A9LH to B9S installer with a post-install clean-up script that deletes every file in it (including itself, but it leaves the backups in the "boot9strap" folder). I may do a couple of scripts to sync tickets for those using linked NANDs as well. Install new content on SysNAND, run script, reboot to EmuNAND, and it's ready to use with GW's cheat engine.

Simple. "R" is a reserved key, just like "A" and "select" -- you have to hold L with it to use it as a hotkey. When used by itself, it tries to boot EmuNAND using SysNAND's NATIVE_FIRM. Actually, if you have the second option checked in settings, it will try to boot SysNAND with EmuNAND's firm. There used to be another setting that defined which used firmware.bin. The right combo actually allowed you to have it boot SysNAND with a firmware.bin file. That was great back when you needed to use one to run NTR. But I'm not sure what you'd use it for now.

gamerboy1995 said:
OP, what is your opinion of the B9S gateway payload someone posted at https://gbatemp.net/threads/release-the-bootctr9-release-thread.435347/page-5#post-7457140 ?
The poster says

Would that work any better as a Gateway access point than using the method described in this tutorial, because it seems less roundabout?

I'll add the file if anyone can actually confirm that it does not contain any copyright code, which GW is known to include and bundle into it's Launcher.dat, which is why it's banned from GBAtemp. The whole reason why the v2gw.bin was made in the first place, was because of this.

Kazuma77 · Jul 26, 2017

Temptress Cerise said:
I'll add the file if anyone can actually confirm that it does not contain any copyright code, which GW is known to include and bundle into it's Launcher.dat, which is why it's banned from GBAtemp. The whole reason why the v2gw.bin was made in the first place, was because of this.

You know damn well it's not possible to prove a negative. You might as well be asking me to prove there is no god. Can you prove that v2gw.bin contains no copyrighted code? Of course not (unless you have the source code, and ALL COPYRIGHTED CODE EVER WRITTEN to compare it against). If someone can show that it DOES contain copyright code, I'll be more than happy to delete it.

There's a fine line between caution and paranoia. Almost all CFWs have used firmware files at some point. Most still do. It's not like GW is unique in this respect. The file I uploaded is just a conversion of the "arm9loaderhax.bin" GW put out. Considering it's only 7K, I don't think there's any room for firmware in there. It's the "Launcher.dat" that contains the firmware, and pretty much everything else. This just runs it. Like PrBoom runs Doom. You'll still need the "Launcher.dat" (.wad file) from the official site, as always. But if you insist, have a converter then. Just copy GW's "arm9loaderhax.bin" into the folder and double click "convert.bat" to get "Gateway.firm" and use it directly with BootCTR9. Requires Python (2.7 or 3.x).

And IIRC, v2gw.bin was made because Luma's chainloader was incapable of launching GW's A9LH loader directly, not because of any legality issues. I used v2gw.bin in some of my AIO packs myself, because I was able to hex edit the location from "luma/payloads" to "a9lh/payloads" (and because BootCTR9 needed an extra file in the root at the time). Also, it ran without assistance in A9LH, so there was the same number of chainloaders either way. This thing's time has come and gone though. BootCTR9 no longer uses an extra file, and CBM9 can patch BootCTR9's .ini name (allowing for infinite mini-configs). This is just using an extra chain loader for no reason.

I'm really starting to wish Luma had never added a chainloader. I like that it does GUI and hotkeys in one, but the work-arounds for its incompatibilities have become too convoluted. You get better results with a combination of BootCTR9 and CBM9. Just like you get better results using a combination of Godmode9 and Luma3DS than rxTools.

TudorBlue · Jul 26, 2017

Cant get NTR to work, keeps failing

gamerboy1995 · Jul 26, 2017

TudorBlue said:
Cant get NTR to work, keeps failing

Does it fail in Luma mode or Gateway mode? And what version of the 3DS firmware are you on?
I'm using 10.6U Emunand and I've been having trouble getting NTR to work in Luma mode, even though it works perfectly in Gateway mode, and someone else suggested that I should try upgrading my EmuNand to 11.2 using a tool called 3Down. I haven't tried it yet, but I thought I would pass the information along to you.

Kazuma77 · Jul 27, 2017

gamerboy1995 said:
Does it fail in Luma mode or Gateway mode? And what version of the 3DS firmware are you on?
I'm using 10.6U Emunand and I've been having trouble getting NTR to work in Luma mode, even though it works perfectly in Gateway mode, and someone else suggested that I should try upgrading my EmuNand to 11.2 using a tool called 3Down. I haven't tried it yet, but I thought I would pass the information along to you.

Or you could use 3DNUS and SysUpdater it thatt doesn't work. BootNTR Selector 2.8 is working fine for me, though, so, I can't troubleshoot what I can't replicate.

Also, I can't see why you would use Luma with EmuNAND. I just keep my NANDs linked, and copy ticket.db to the other NAND when I install new things. This allows me to have 11.5 SysNAND with Luma, a partially upgraded 11.4 EmuNAND with GW, and the same content installed on both.

Temptress Cerise · Jul 27, 2017

Kazuma77 said:
You know damn well it's not possible to prove a negative. You might as well be asking me to prove there is no god. Can you prove that v2gw.bin contains no copyrighted code? Of course not (unless you have the source code, and ALL COPYRIGHTED CODE EVER WRITTEN to compare it against). If someone can show that it DOES contain copyright code, I'll be more than happy to delete it.

There's a fine line between caution and paranoia. Almost all CFWs have used firmware files at some point. Most still do. It's not like GW is unique in this respect. The file I uploaded is just a conversion of the "arm9loaderhax.bin" GW put out. Considering it's only 7K, I don't think there's any room for firmware in there. It's the "Launcher.dat" that contains the firmware, and pretty much everything else. This just runs it. Like PrBoom runs Doom. You'll still need the "Launcher.dat" (.wad file) from the official site, as always. But if you insist, have a converter then. Just copy GW's "arm9loaderhax.bin" into the folder and double click "convert.bat" to get "Gateway.firm" and use it directly with BootCTR9. Requires Python (2.7 or 3.x).

And IIRC, v2gw.bin was made because Luma's chainloader was incapable of launching GW's A9LH loader directly, not because of any legality issues. I used v2gw.bin in some of my AIO packs myself, because I was able to hex edit the location from "luma/payloads" to "a9lh/payloads" (and because BootCTR9 needed an extra file in the root at the time). Also, it ran without assistance in A9LH, so there was the same number of chainloaders either way. This thing's time has come and gone though. BootCTR9 no longer uses an extra file, and CBM9 can patch BootCTR9's .ini name (allowing for infinite mini-configs). This is just using an extra chain loader for no reason.

I'm really starting to wish Luma had never added a chainloader. I like that it does GUI and hotkeys in one, but the work-arounds for its incompatibilities have become too convoluted. You get better results with a combination of BootCTR9 and CBM9. Just like you get better results using a combination of Godmode9 and Luma3DS than rxTools.

@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.

gamerboy1995 · Jul 27, 2017

Kazuma77 said:
Or you could use 3DNUS and SysUpdater it thatt doesn't work. BootNTR Selector 2.8 is working fine for me, though, so, I can't troubleshoot what I can't replicate.

Also, I can't see why you would use Luma with EmuNAND. I just keep my NANDs linked, and copy ticket.db to the other NAND when I install new things. This allows me to have 11.5 SysNAND with Luma, a partially upgraded 11.4 EmuNAND with GW, and the same content installed on both.

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...

Attachments

Well-Known Member

Active Member

Well-Known Member

Miss Magic~ <3

Active Member

Well-Known Member

Well-Known Member

Well-Known Member

Alhumdulillah

Member

Well-Known Member

Alhumdulillah

Member

Miss Magic~ <3

Well-Known Member

Attachments

Well-Known Member

Well-Known Member

Well-Known Member

Miss Magic~ <3

Well-Known Member

Similar threads

Popular threads in this forum