Yes, you need BootCTR9 if you are on v2 A9LH.
Someone was kind enough to make a tutorial on it: http://gbatemp.net/threads/using-gateway-on-a9lh-v2.431222/
You can change it up to suit your needs, but that's the basic gist of it.
Someone was kind enough to make a tutorial on it: http://gbatemp.net/threads/using-gateway-on-a9lh-v2.431222/
You can change it up to suit your needs, but that's the basic gist of it.
But if I wasn't on V2 but instead on V1, can I just chainload using luma? I'm fairly certain I installed a9lh 2 days before the release of V2.
On v1, then yeah, you can go ahead and chainload of Luma3DS, no need to bother with BootCTR9. There is also no need to update to v2 either, until payloads start requiring it.
What's the lowest gw version that works with the a9lh.bin? Will 3.4.1 work and will it work with the n3ds?
Nope. 3.4.1 does not support N3DS.
Guessing you are trying to use a DSTwo+
There's a tutorial on getting it to work, but o3DS/2DS only.
Link: http://gbatemp.net/threads/tutorial...e-work-with-latest-emunand-on-old-3ds.429035/
Sorry but you are pretty much out of luck.
Yeah, I'm considering getting a DSTwo+ since its heaps cheaper than a gateway
It bricks if you use >3.4.1 but since it 3.4.1 doesn't work on n3ds, I wont be getting it. Considering getting the sky3ds+ though
I just use mine for exploit games. Very, very handy for that. But eh, wouldn't really recommend it. But hey, go for it, if you want.
You've got the sky3ds+ or the older sky3ds? Tbh, I'm just seeking for a way to convert my old gw.sav files
Sky3DS+ the latest revision of it. I know, because I've updated it's firmware, and it's the drag-and-drop version, which the previous versions weren't like this.
I got mine for free. I setup A9LH on my friend's 3DS, and he was so thankful that he gave it to me. But he did tell me how much he did pay, which was around 90 US Dollars. Which is a lot. I can see why some people like it, if they want to use .3ds roms and want a drag-and-drop solution. But I don't know if I could justify that price tag for it. But to each their own.
Update to my previous post: https://gbatemp.net/threads/release...vate-beta-program.429241/page-30#post-6450450
This is what I did; use at your own risk.
- took my GW EmuNAND card out and put it aside, used a 2nd SD card
- upgraded SysNAND from 4.1.0-8U to 9.2.0-20U as per Plialect's guide,
- followed Plialect's guide for the most part (didn't upgrade RedNAND - left it at 9.2.0) until at 2.1.0
- dumped otp.bin anyway
- mostly followed 'older' Part 5 here: https://github.com/Plailect/Guide/w...hax)/69d8cada9361ff8240955abf7e74eb7fdb30fb07 so I ended up with v1 of A9LH (older guide still asked for otp.bin, not sure if it actually got used)
- restored the 9.2.0 emuNAND_original.bin to SysNAND
(TO DO: restore emunand formatted to RedNAND, boot into RedNAND, update to 11.0.0U for use with Luma)
(TO DO 2: create a 2nd RedNAND, change region to Europe, update to 11.0.0E)
- copied GW's arm9loaderhax.bin over to the GW EmuNAND SDCard, left my 3.7.1 launcher.dat as-is,
- inserted in o3DS, turned on, and boom: see the dragon, boots in my 11.0.0 EmuNAND, press select to play a .3ds game.
- FBI.3ds game icon looks kinda weird...
Observations:
- need 2 SD cards, one for use with GW and .3ds games, one for Luma3DS and .cia games
- SysNAND is and remains at 9.2.0, you work with an EmuNAND/RedNAND in either case
- I don't think GW's arm9loaderhax protects your firmware, so be very careful
- you can always switch to some bootmanager later, as Luma supports EmuNAND as well
This is what I did; use at your own risk.
- took my GW EmuNAND card out and put it aside, used a 2nd SD card
- upgraded SysNAND from 4.1.0-8U to 9.2.0-20U as per Plialect's guide,
- followed Plialect's guide for the most part (didn't upgrade RedNAND - left it at 9.2.0) until at 2.1.0
- dumped otp.bin anyway
- mostly followed 'older' Part 5 here: https://github.com/Plailect/Guide/w...hax)/69d8cada9361ff8240955abf7e74eb7fdb30fb07 so I ended up with v1 of A9LH (older guide still asked for otp.bin, not sure if it actually got used)
- restored the 9.2.0 emuNAND_original.bin to SysNAND
(TO DO: restore emunand formatted to RedNAND, boot into RedNAND, update to 11.0.0U for use with Luma)
(TO DO 2: create a 2nd RedNAND, change region to Europe, update to 11.0.0E)
- copied GW's arm9loaderhax.bin over to the GW EmuNAND SDCard, left my 3.7.1 launcher.dat as-is,
- inserted in o3DS, turned on, and boom: see the dragon, boots in my 11.0.0 EmuNAND, press select to play a .3ds game.
- FBI.3ds game icon looks kinda weird...
Observations:
- need 2 SD cards, one for use with GW and .3ds games, one for Luma3DS and .cia games
- SysNAND is and remains at 9.2.0, you work with an EmuNAND/RedNAND in either case
- I don't think GW's arm9loaderhax protects your firmware, so be very careful
- you can always switch to some bootmanager later, as Luma supports EmuNAND as well
I think "a9lh v2" broke Gateway's payload. you'd need to go to v1 somehow, or wait for them to update arm9loaderhax.bin
What ihaveamac said is correct. You either downgrade to v1 A9LH. Wait for GW to update their A9LH.bin.
However, you do have another workaround that doesn't involve downgrading, and that's using a BootCTR9.
Someone was kind enough to make a tutorial, look over it.
Link: http://gbatemp.net/threads/using-gateway-on-a9lh-v2.431222/
Your second option, is to use a v2 A9LH fork that's compatible with GW. However, this requires compiling it yourself.
Link: https://gbatemp.net/threads/safea9lhinstaller.419577/page-29#post-6432075
Good luck~
<3
using the bin from gateway in my o3ds a9lh v1 in sysnand 11.0, shows up the gateway menu but gives me a black screen when i enter in gateway mode
still must have the sysnand in 9.2, even with a9lh to gateway work???
still must have the sysnand in 9.2, even with a9lh to gateway work???
Similar threads
