Using Gateway on A9LH V2

Cosmic_Link Jun 16, 2016.

  1. Cosmic_Link
    OP

    Cosmic_Link Advanced Member

    Newcomer
    6
    Jun 9, 2010
    lol You're right about things being on the root, it looks incredibly untidy. Sheer laziness is what has caused me to put everything on the root. XD That coupled with the fact that everything else is just thrown into root anyway, so it's not going to look any better whether I have everything in root or folders. lol Things like launcher.dat, gateway save files, and others. It looks pretty cluttered already. >.<
     
  2. Emenaria

    Emenaria GBAtemp Regular

    Member
    5
    Nov 6, 2015
    Japan
  3. Temptress Cerise

    Temptress Cerise Miss Magic~ <3

    Member
    9
    May 1, 2016
    United States
    Ah, yes, those darn Gateway saves. I usually only just use my GW for Pokemon .3ds rom hacks, and cheats. :P Or for play testing, before converting fully to .CIA. So mine is pretty tidy in that regard. ^_^

    sd-root.

    To be honest, that just updates//replaces A9LH v2, with liomajor's Three Stage 2. For some people, they like that. However, I am not too much of a fan of that method. Don't get me wrong, I used it back when it was the only method and we didn't have a compatible a9lh.bin on v1 A9LH. But now, I just use the A9LH.bin GW has provided. Also, with BootCTR9, people don't have to bother running SafeA9LHInstaller and worrying about making sure they have all the correct files to flash.

    I don't know, I feel BootCTR9 is a much more friendlier way of getting GW to work on v2 A9LH. But that's just my opinion.

    Edit: The "USE AT YOUR OWN RISK" also doesn't scream noob friendly. :P
     
    Last edited by Temptress Cerise, Jun 19, 2016
  4. retrofan_k

    retrofan_k GBAtemp Addict

    Member
    10
    May 31, 2013
    Belarus
    Caves
    Personally, i'd stick with V1 or if you are on currently on V2, use BootCTR to get GW to work and the whole purpose of CFW is to ideally do away with flash carts and if CFW in the future enables multi-rom drag n drop/cheats, GW will be a thing of the past.

    The risks involved using modified stages with "Use at your own risk" is not something to take lightly when V2 does not bring anything exciting or useful to the table at present. Anyone without a "hard mod" or little experience should not play with fire.
     
    Last edited by retrofan_k, Jun 19, 2016
  5. ken28

    ken28 GBAtemp Maniac

    Member
    7
    Oct 21, 2010
    Germany
    hoe do use it with bootanim9 without losing luma?
     
  6. gohan127

    gohan127 Member

    Newcomer
    1
    Jun 10, 2016
    United States
    hey draven, i had the same problem, what helped for me was to boot holding select--> tell luma not to force boot from sysnand. everytime GWtried to boot luma would somehow interfere and cause black screens. hope it helps. ..
     
  7. Kazuma77

    Kazuma77 GBAtemp Maniac

    Member
    6
    May 11, 2008
    United States
    No need to waste 3 hotkeys on Luma. Just put it on A. All Luma hotkeys seem to work with A held. I guess that breaks your pattern of placing tools on the right side buttons though. I prefer them on the d-pad myself.

    Actually, d0k3 has a modified Safe A9LH Installer v1.5.2 here that works. Also, "payload_stage[x]" files are not console-specific. Not even delebile's. If I posted them, they would work for everyone. The reason I haven't done that is because they seem to break BootCTR9 (at least the Github release, but I'll check the dev build since you provided a link to the pre-compiled one). It's only the installer that gets built that is console-specific, but if you're using Safe A9LH Installer, all you need are the compiled stage payloads, which are not.

    Why people add another chain loader to their boot sequence just to hold onto Luma's chain loader is beyond me. BootCTR9's configuration file isn't that much of a hassle to setup. If you ask me, liomajor's time would be better spent fixing Arm9Select. It's almost identical to Luma's chain loader, but not CFW-dependent. Then you could stick to just having one chain loader.
     
    Last edited by Kazuma77, Jun 19, 2016
  8. noctis90210

    noctis90210 GBAtemp Advanced Fan

    Member
    6
    Dec 24, 2013
    @retrofan_k @Cosmic_Link
    just found out easy steps without messing too much about boot_config.ini

    the only content of my boot_config.ini is this:

    Code:
    [DEFAULT]
    path = /luma/Luma3DS.bin
    delay = 0
    offset = 0
    payload = -1
    
    no more no less, but i can still boot into d9, e9, hg9, gm9, gw, lumaconfig...

    what i did was:
    i pathchanged the luma a9lh payload to /luma/Luma3DS.bin
    and the luma will work as before (like without the bootctr9)


    the logic of the less clutter boot_config.ini is this:

    Code:
                            |---d9 (luma payload folder)
                            |---e9 (luma payload folder)
                            |---gw (luma payload folder)
    bootctr----luma---------|---gm9 (luma payload folder)
                            |---lumaconfig
                            |---hg9 (luma payload folder)
                            |---etc payload (luma payload folder)
    
    
    (bootctr only handles luma and Luma handes most of the payload)
    (payload still on luma/payload folder but boot_config.ini is clutter less)
    

    and the logic of the cluttery boot__config.ini that being talked about since this thread is opened is this:

    Code:
                  |---d9 (random file directory)
                  |---luma (random file directory)
                  |---gw (random file directory)
    bootctr-------|---e9 (random file directory)
                  |---gm9 (random file directory)
                  |---lumaconfig
                  |---hg9 (random file directory)
                  |---etc payload (random file directory)
    
    (bootctr handles all the payload)
    (payload directory is the users choice, but the boot_config.ini is cluttery)
    
     
    Last edited by noctis90210, Jun 19, 2016
    Cosmic_Link and retrofan_k like this.
  9. Cosmic_Link
    OP

    Cosmic_Link Advanced Member

    Newcomer
    6
    Jun 9, 2010
    Yeah, I know there's no need. I would have just kept Luma on L and Select. The reason for L and Select is for still being able to access Luma settings holding select should the need arise. The reason for me putting the other hotkeys as they were was to match plailect's guide and removes any confusion. There is method to the madness. XD There was no real reason for Luma being hotkey to R though. Just for the sake of it I guess. :P Don't forget, that particular confit was for my own preference and not necessarily for everybody! ^_^

    @noctis90210 Thanks for this. I will have a look at cleaning up my own boot_config.ini later on. However, I don't imagine it will benefit me much since the idea for me was to boot into Gateway by default as I am most likely to use my Gateway card and only have Luma on there for other things that I can't do in Gateway mode.

     
    Last edited by Cosmic_Link, Jun 19, 2016
    noctis90210 likes this.
  10. gartlan

    gartlan Member

    Newcomer
    5
    Nov 5, 2002
  11. Kazuma77

    Kazuma77 GBAtemp Maniac

    Member
    6
    May 11, 2008
    United States
    I guess that simplifies things if your only reason for using BootCTR9 is compatibility (and you're extremely lazy). I could understand such laziness if I hadn't already provided a complete configuration for everyone. What's wrong with this is that it has everything except Luma needlessly going through an extra chain loader. Extremely inefficient to say the least. Not to mention inflexible. If Corbenik overtakes Luma as the top CFW, then your method's useless. It's also useless for anyone that wants to run GW as the default. Basically, it only works if all you want BootCTR9 for is the compatibility. Besides, once you have one hotkey setup, it's pretty much just copy, paste, change key name, change .bin name. For me, adding extra entries is no more time-consuming than doing the rename thing for Luma.

    Does he give a reason for not recommending v8? That's kind-of my discovery, btw. I put it into my configuration files as the main CBM9 menu long before he said anything. My CBM9 configuration is using v8 for the main menu and the original for the submenus (I did that because I noticed GW was having issues with some forks, and haven't had time to test the unofficial version with the various CFWs and GW yet). Since GW is still actually being launched from cpajuste's original version, in theory, my CBM9 configuration should work with A9LH v2 without issues, just like my BootCTR9 one does.
     
  12. WiiHoney

    WiiHoney GBAtemp Regular

    Member
    2
    Mar 22, 2010
    United States
    How would i update my GW emuNAND after following the OP's directions?

    If i updated GW emuNAND by accident, do i need to install A9LH v2 all over again?
     
  13. Temptress Cerise

    Temptress Cerise Miss Magic~ <3

    Member
    9
    May 1, 2016
    United States
    If you followed Plailect's A9LH Guide to the very end, without skipping anything. Then you should no longer have an EmuNAND at all.

    As such you are on a SysNAND only setup. To update your setup, you would use Luma3DS to Update your SysNAND, as GW does not do any FIRM Protection on A9LH.

    Edit: If you happen to update SysNAND while in GW Mode, with A9LH, two things will either happen. On o3DS, you will lose A9LH and be on the latest OFW//Stock version, or maybe brick. On N3DS, you will brick. At least that's what I recall from previous info.
     
    Last edited by Temptress Cerise, Jun 20, 2016
  14. WiiHoney

    WiiHoney GBAtemp Regular

    Member
    2
    Mar 22, 2010
    United States
    @Temptress Cerise I actually had to install GW emuNAND to my SD card. Following Plailect's guide made me loose all the MII's and the MII plaza accomplishments . so right now i have GW3D 11.0.0-33U and EmuS 11.0.0-33U, Without GW emuNAND i have no access to GW RED card.

    Now i dont have any option to update GW emuNAND. If i update i lose A9LH or worst is brick. If i dont update i wont be able to play latest games that required online play.

    If i update my Luma3DS sysNAND (holding R while booting) i still cant access MII plaza
     
  15. Temptress Cerise

    Temptress Cerise Miss Magic~ <3

    Member
    9
    May 1, 2016
    United States
    If you are booting into EmuNAND while using GW, then there really shouldn't be any problems updating via GW, as this is the method that GW actually recommends with their own locked down GW-A9LH. I would assume on Standard A9LH, with GW's a9lh.bin, the same would apply.

    You could use Luma3DS to boot your EmuNAND, and update via that, making sure you are in EmuNAND. But I honestly don't think this be necessary.

    Again, if you update EmuNAND via GW Mode or Luma3DS, FIRM Protection shouldn't really matter. Since A9LH lives on the FIRM partition of SysNAND, not the one of EmuNAND.
     
    WiiHoney likes this.
  16. WiiHoney

    WiiHoney GBAtemp Regular

    Member
    2
    Mar 22, 2010
    United States
    I got it now, Thank you again @Temptress Cerise .

    Update GW emuNAND the normal way through System Setting in GW mode
    Update Luma3DS sysNAND through Luma3D updater cia
     
  17. Temptress Cerise

    Temptress Cerise Miss Magic~ <3

    Member
    9
    May 1, 2016
    United States
    The Luma3DS Updater .CIA will only update your Luma3DS payload, you'll still need to update via System Settings with Luma3DS to update your SysNAND.
     
    WiiHoney likes this.
  18. retrofan_k

    retrofan_k GBAtemp Addict

    Member
    10
    May 31, 2013
    Belarus
    Caves
    Yes, that is the correct way to update. Just double check when in sysnand it says "Sys" before the version number, as one can easily forget that they are in GW sysnand if using using GW on a regular basis.
     
    WiiHoney likes this.
  19. Temptress Cerise

    Temptress Cerise Miss Magic~ <3

    Member
    9
    May 1, 2016
    United States
    To add to this, just make sure you are using Launcher.dat 4.0b, as it'll nag you if you try to boot into SysNAND, and as such would be a clear indicator that, you shouldn't update. The nag will not appear if using EmuNAND, and it'll just boot right into your GW EmuNAND.
     
  20. retrofan_k

    retrofan_k GBAtemp Addict

    Member
    10
    May 31, 2013
    Belarus
    Caves
    I'm using 3.7.1 without the nag, so didn't mention that. Reason being, is I'm not comfortable with possible hidden code that might be in the 4.0b launcher.dat. Still don't trust GW and their shady practices.
     
Quick Reply
Draft saved Draft deleted
Loading...