Hacking The status of Gateway and A9LH

dsync

Active Member
Newcomer
Joined
May 2, 2012
Messages
29
Trophies
0
XP
127
Country
Malaysia
I've just completed A9LH installation following Plailect's guide and Luma is booting perfectly. I wanted to have Luma and Gateway share sysNAND but I'm getting a black screen when I try to boot into Gateway.

I've formatted my SD with Emunand9's no emuNAND option, I have launcher.dat (tried 3.7.1 and 4.0a) on the root of the SD and Gateway's a9lh payload in luma/payloads renamed to l_gw.bin so I can hold L to boot into Gateway. As I understand it Plailect's guide uses a screen init version of a9lh which Gateway requires. What am I missing?

edit: Got it working. just changed the hotkey, seems L isn't supported.

Yes I had the same setup as you (followed Plailect's guide from Part 3-5) and setup Luma 3DS. I can confirmed that the arm9loaderhax.bin released by Gateway 4.0Beta is working on my N3DS SysNAND 11.x.x. What I did was simply renaming the .bin file to a hotkey that Luma3DS recognized (x_gw.bin) and copy the launcher.dat to the root of my microSD card.

Before getting to this, I saw other guides with long setup instructions that detailed on how to dual boot Luma3DS and Gateway. Correct me if I'm wrong, but perhaps we no longer have to follow those guides if we're using the arm9loaderhax.bin released by Gateway?
 
  • Like
Reactions: polarbernd

Temptress Cerise

Miss Magic~ <3
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
Seems like gateway doesn't work with the new AuroraWright's arm9loaderhax
Did you use the screen-init or no-screen-init build? It should work fine with the screen-init build, as GW's a9lh.bin payload needs screen-init, and Luma3DS' chainloader doesn't seem to pass this on correctly on no-screen-init builds. At least from previous tests I've done, but those were with the older branches of A9LH, and not the updated ones.

I am still running the old A9LH, I'll probably update tomorrow, but I don't use Luma3DS anymore and prefer BootCTR9 for managing my a9lh.bin payloads.

Edit: Though I'll probably still test Luma3DS to see what's up.


Second Edit: Seems Aurora Wright's v2 does break GW's a9lh.bin files, I'll look into upgrading to v2 when it's actually needed.
 
Last edited by Temptress Cerise,

dsync

Active Member
Newcomer
Joined
May 2, 2012
Messages
29
Trophies
0
XP
127
Country
Malaysia
I think mine is with the screen-init build since I followed plailect's guide. Just setup all up yesterday and is kicking right now :)
 

wiiuser2

Well-Known Member
Member
Joined
Sep 12, 2009
Messages
186
Trophies
0
XP
211
Country
Netherlands
EDIT 2: It's fixed now. The original "screen init" files are now included as intended. I would advise anyone who's downloaded my Boot Manager Mega Configs before to re-download.

Made another update to my Boot Manager Mega Configs. This time to update Decrypt9, EmuNAND9, and GodMode9. Complete version coming to the iso site in a few minutes..

Thanks a lot for the quick follow up. In the mean time I found out that when starting Luma via CBM9, that the old DS flashcards are not working anymore.
I reverted back to BootAnim9 -->Luma. Gateway is working fine as Luma payload and Luma support DS flashcards in Emunand as well. Also when finishing a DS game, the system restarts into BootAnim9 but it detects that and immediately continues to booting Luma. The result is that when exiting a DS game you end up back in the Luma homescreen automatically. For me this is the almost pefect setup.
The threeStage A9LH also allows me booting Gateway directly when pressing a key, default it starts BootAnim9.
P.S. I did modify the BootAnim9 0.6.1 source to replace the Gateway nag by my payloads button setup definition as a menu (just text) in the bottom screen and ony show the random video in the topscreen. Basically gives me the basic CBM9 functionality but with video as well ;-)
 

Kazuma77

Well-Known Member
Member
Joined
May 11, 2008
Messages
1,035
Trophies
1
XP
905
Country
United States
Seems like gateway doesn't work with the new AuroraWright's arm9loaderhax
Did you use the screen-init or no-screen-init build? It should work fine with the screen-init build, as GW's a9lh.bin payload needs screen-init, and Luma3DS' chainloader doesn't seem to pass this on correctly on no-screen-init builds. At least from previous tests I've done, but those were with the older branches of A9LH, and not the updated ones.

I am still running the old A9LH, I'll probably update tomorrow, but I don't use Luma3DS anymore and prefer BootCTR9 for managing my a9lh.bin payloads.

Edit: Though I'll probably still test Luma3DS to see what's up.
Gw payload dosen"t work with the new A9LH installer so i reinstall the old versión

That's not the only problem. CBM9 (the main branch from cpajuste) gives a black screen as well (and that was with the screen init payloads). In other words, it breaks my "everything else" menus. Actually, newer "screen init" files for the old A9LH broke it too. I had to go back to the payloads from mid-March.

EDIT: Even worse, it refused to go back to the old version. I had to do a NAND restore. Now I'm going to have to find a different way back.
 
Last edited by Kazuma77,

retrofan_k

Well-Known Member
Member
Joined
May 31, 2013
Messages
2,077
Trophies
2
Location
Caves
XP
2,462
Country
Belarus
Did you use the screen-init or no-screen-init build? It should work fine with the screen-init build, as GW's a9lh.bin payload needs screen-init, and Luma3DS' chainloader doesn't seem to pass this on correctly on no-screen-init builds. At least from previous tests I've done, but those were with the older branches of A9LH, and not the updated ones.

I am still running the old A9LH, I'll probably update tomorrow, but I don't use Luma3DS anymore and prefer BootCTR9 for managing my a9lh.bin payloads.

Edit: Though I'll probably still test Luma3DS to see what's up.

There is no reason to update.

I'm quoting "Liomajor" from another thread:

Either use delebile's v2 with his own installer including firm0 from firmware 8.1, or send a mail to gateway if they could fix their arm9loaderhax.bin to work with aurora's v2.

Aurora's 2.0.1 is only a bugfix > "Disable caches/mpu before changing MPU settings". Using v2 is not better than v1, its completly fine to stay on v1.
 

Kazuma77

Well-Known Member
Member
Joined
May 11, 2008
Messages
1,035
Trophies
1
XP
905
Country
United States
There is no reason to update.

I'm quoting "Liomajor" from another thread:

Either use delebile's v2 with his own installer including firm0 from firmware 8.1, or send a mail to gateway if they could fix their arm9loaderhax.bin to work with aurora's v2.

Aurora's 2.0.1 is only a bugfix > "Disable caches/mpu before changing MPU settings". Using v2 is not better than v1, its completly fine to stay on v1.

That wouldn't be a problem... but I wrote an A9LH guide that uses V2's new features. If I can't make downgrading work, it has to go back to the old method.
 

Temptress Cerise

Miss Magic~ <3
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
You're as bad as Gateway. Which card? 3DS or uSD?
If you can't figure this out on your own, are you sure you should be messing with these files?

Here is that disclaimer that can be found on that openly public Private Beta Program page:
"DISCLAIMER: Files on this page should be treated with extreme care and only used by advanced users who have access to a way to restore their 3DS NAND. Users should have a valid/known good copy of their NAND before proceeding! Use at your own risk!"

Also, don't go blaming anyone here or Gateway for that matter if you brick.

There is no reason to update.

I'm quoting "Liomajor" from another thread:

Either use delebile's v2 with his own installer including firm0 from firmware 8.1, or send a mail to gateway if they could fix their arm9loaderhax.bin to work with aurora's v2.

Aurora's 2.0.1 is only a bugfix > "Disable caches/mpu before changing MPU settings". Using v2 is not better than v1, its completly fine to stay on v1.
That wouldn't be a problem... but I wrote an A9LH guide that uses V2's new features. If I can't make downgrading work, it has to go back to the old method.

Thanks guys, I guess I won't update into v2 actually is needed by new a9lh.bin payloads then, right? ^_^
 
  • Like
Reactions: ldeveraux

retrofan_k

Well-Known Member
Member
Joined
May 31, 2013
Messages
2,077
Trophies
2
Location
Caves
XP
2,462
Country
Belarus
Thanks guys, I guess I won't update into v2 actually is needed by new a9lh.bin payloads then, right? ^_^

Yeah, from what I see and read so far, the extra bytes are useful with V2 in the long run for newer payloads but it's best to stay as we are on V1 until it's necessary to keep up with newer developments.
 

Temptress Cerise

Miss Magic~ <3
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
Yeah, from what I see and read so far, the extra bytes are useful with V2 in the long run for newer payloads but it's best to stay as we are on V1 until it's necessary to keep up with newer developments.
Alright~ If anything, I'll update the payloads on two of my systems, as those two don't use GW. (However, since I can also be lazy, I'll probably push it off as well lol) ^_^
 

Temptress Cerise

Miss Magic~ <3
Member
Joined
May 1, 2016
Messages
2,242
Trophies
1
XP
2,336
Country
United States
She's not kidding. You're going to brick. Have fun with that.
Fixed that for you. Since I am a girl. ^_^

Less of the attitude please.

Anyways, I don't think anyone here is going to go out of their way to help someone brick their system.

That's why we keep either telling people not to use GW's A9LH installer and why we suggest people use Standard A9LH if they can't wait.

If you don't mind the idea of being locked down to GW and want GW-A9LH, then wait for them to polish it and actually make a better installer.
 
Last edited by Temptress Cerise,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Veho @ Veho: New Myoo.