Using Gateway on A9LH V2

Cosmic_Link Jun 16, 2016.

  1. dodol

    dodol GBAtemp Regular

    Member
    3
    Sep 24, 2007
    United States
    how to remove bootctr ascii text and just use splash screen ?
    I set boot_splash to 1 and ascii text still shown.
     
  2. Kazuma77

    Kazuma77 GBAtemp Maniac

    Member
    6
    May 11, 2008
    United States
    Just put Luma on A. Leave L, R, and select unmapped. Then you'll have no problems. All A does is tell it to boot with the default settings (persistence override). You can use any of Luma's hotkeys in conjunction with A (select, L, R, they all work). This is why I said mapping it to those other buttons was a bad idea. Too confusing for people.

    It's not like GBA, DS carts, and DSiWare would magically start working with an EmuNAND. They have never worked with Gateway AT ALL (not even the ambassador titles) and probably never will. Also, it's only the Github version of BootCTR9 that works. For whatever reason, the dev version you linked gives a black screen with v2. I still need to try using delebile's payloads with the dev version of BootCTR9 though. I've confirmed that the stage payloads for delebile's version are indeed not console-specific and can be shared. Not that it matters. I'm not going to upload payloads that break boot managers.
     
    Last edited by Kazuma77, Jun 23, 2016
  3. Temptress Cerise

    Temptress Cerise Miss Magic~ <3

    Member
    9
    May 1, 2016
    United States
    I've never cared for GBA, DS or DSiWare as GW User. Not even on my main custom firmware do I care about GBA//DSiWare stuff. I use my DSTwo on whatever 3DS I happen to want to use it on, while using Corbenik, but even then I have AGB//TWL patches disabled.

    Also, my "it works", was towards what Hayleia released. As this is the first time I actually have a V2 A9LH console. And I wasn't about to upgrade all my previous consoles to V2 A9LH just to test if they break what or who. Though, when I linked it to retrofan_k, it was just to show him, that it Key_X, did work on the root for me, but that the difference was that I was using the latest dev build. I guess I should have also mentioned I was on v1 A9LH, as that probably was another difference.
     
  4. Kazuma77

    Kazuma77 GBAtemp Maniac

    Member
    6
    May 11, 2008
    United States
    OK, that makes sense. I have a DSTwo myself. TempGBA FTW. I only install the GBA ambassador titles to test reboot patches with. I haven't messed with injected titles. As for DSiWare, I do enjoy "Zelda: Four Swords Anniversary Edition" -- it's the primary reason I've been dual booting since PBT came out. Though Alphabounce is a nice Breakout/Arkanoid clone. And of course, there's Dragon's Lair, and Brain Age Express: Sudoku (I thought I would actually play that, I cleared them all in the original Brain Age, but my puzzle game of choice tends to be Stretchmo now -- and to think, I only discovered it because Nintendo shoved a free trial in my face, not the smartest move on their part as easy as DLC tickets are to get). And the guitar tuner app is useful. I've got a big set of DSiWare titles downloaded, both as .nds and .cia. I've been meaning to check them out in an emulator or something to get an idea of what's good. I get the feeling I'm missing out on a lot of good stuff just because I don't know it exists. I kind-of skipped the DSi and went straight from the DS Lite to the 3DS XL.

    The new mini boot manager does looks interesting. Oh yeah, the path is in plain text. I can modify it to "/a9lh/payloads/Gateway.bin" easily. So, this isn't just useful for Luma. It can be used as a workaround for Arm9Select and CBM9 as well.

    There's an even easier method. And it doesn't put everything through an extra chain loader, just GW. After all, you're only using BootCTR9 to get GW to run. No need to run everything through it. Try this one:

    Code:
    [BOOTCTR9]
    screenEnabled = 1
    screenLog = 0
    fileLog = 0
    key_delay = 0
    screenBrightness = 0x40
    
    [DEFAULT]
    path = /a9lh/payloads/Gateway.bin
    screenEnabled = 1
    delay = 200
    offset = 0
    payload = -1
    
    Change the path as needed, of course. This is my current fix for Arm9Select (the new mini chain loader crashes too much with it for some reason). Anyway, just hotkey BootCTR9 as if it was GW. Now you're not running everything through an extra chain loader needlessly. You don't even have to patch Luma. I'm not getting how someone can care about clutter in an .ini file (where it doesn't matter) yet have zero concerns about cluttering the boot process, but to each their own.

    Thanks for this. I've taken the liberty of changing "/luma/payloads/gateway.bin" to "/a9lh/payloads/Gateway.bin" in the copies I'm using. Makes it more universal. Besides, I don't like the thought of putting something in the "luma/payloads" folder that isn't actually being hotkeyed. I've done some thorough testing of this with Arm9Select, CBM9, and of course Luma, the intended target. The boot rate is close enough to 100% with CBM9 and Luma, but it's absolutely dreadful with Arm9Select for some reason. Oh well, for now I'll just use this with CBM9 and Luma, and have Arm9Select use BootCTR9 for it's GW hotkey (with an .ini file that defaults to GW and has no hotkeys defined). However, if you can figure out what's causing it to fail in A9S, that would be great.
     
    Last edited by Kazuma77, Jun 24, 2016
  5. Hayleia

    Hayleia GBAtemp Maniac

    Member
    7
    Feb 26, 2015
    France
    Yeah of course, change the path to whatever suits you.
    I primarily made this for people who use Luma as main and Gateway as secondary, so that's why I hardcoded the /luma/payloads/ folder. Other people probably have a boot manager anyway, and the boot manager is supposed to be able to run Gateway...

    And no idea why a9select would fail with v2gw. But I'm not sure I'm getting what your setup was since you mention CBM9, a9select and BootCtr9 :P
    Your root a9lh.bin is a9select with Luma as default, CBM9 as secondary, and Gateway as wanted secondary (but fails due to a9select not supporting it and v2gw failing for some reason), is that it?
    If that's so, you should be able to replace a9select with a9lhay in your setup since it's supposed to support Gateway directly (without v2gw). Though I'm not really able to test stuff at the moment since my only working setup is my 2DS (my O3DSXL's SD went into read-only for some reason, my N3DSXL is disassembled, and my 2DS doesn't use a9lhay and I'm prioritize the reassembly of my N3DSXL more than testing stuff on my 2DS).
     
  6. Kazuma77

    Kazuma77 GBAtemp Maniac

    Member
    6
    May 11, 2008
    United States
    Well, I'm not necessarily using them all at once ;)

    Actually, my own setup uses BootCTR9, so it doesn't need the fix. It has Luma as default, but has Gateway, Cakes, and ReiNAND all as hotkeyed alternatives. It also uses CBM9 as a sort of "extras" menu for less used apps and CFWs (Uncart, Salt, Salt Lite, etc.). And that's not exactly a normal setup either -- I use multiple .cfg files via CBM9's memory patching feature to create fake sub-menus (for example, select "Apps" and it reloads CBM9 with another configuration file showing a list of apps, the last entry being a "Return to Main" option that again re-launches CBM9 with the default configuration file).

    However, I took it upon myself to create an AIO drag-and-drop archive that gives people a choice of the 4 most popular boot managers (pre-configured to run just about every CFW and app, and in the case of the copy that goes to the iso site, with all firmware and key files said CFWs and apps need included, so that people having trouble getting them to work can just copy and paste). Actually, I started out just uploading my BootCTR9 config for people that wanted to make GW the default. Then I decided to add a CBM9 setup, because most long-time Menuhax users seem to be more used to CBM and might prefer it. At some point I decided I might as well include Arm9Select because it's easy enough to setup, and a Luma configuration so that people don't feel compelled to switch from what they're used to just for the ready-to-use CFWs.

    So, basically, since I'm providing these fully configured boot managers, and the only one that loads GW from A9LH v2 is BootCTR9, I thought I'd see if this would work with the other two boot managers. One worked great, the other, not so much. Oh well, there's probably far more people using CBM9 anyway.

    It's no big deal if you can't check it out. I can just have A9S hotkey BootCTR9 for now (with an .ini file set to boot straight into Gateway). I certainly understand the priority of reassembling an N3DS XL. I had one apart recently myself. A word of advice. Be VERY CAREFUL with those damn clamps for the screen ribbon cables. They have a nasty tendency to become unhinged. And once it's off, it's not going back. You're looking at a motherboard replacement at that point. I just said screw it and bent the pins onto the cable with a flat-head screwdriver. I don't advise it. Text screens look perfectly fine, but the Home Menu looks messed up. It will work for grabbing EUR eShop updates, but I'll probably never be able to play games on my Australian N3DS XL again. The cost of a motherboard is $70. I can't justify that. Especially since, given the recent nose dive the UK's currency just took, I could probably import a brand new PAL unit for that price now ;)

    I've looked into A9LHay before, but I don't have any kids I need to keep out of GodMode9, so I don't need it's primary reason for existing -- being able to assign button combos to payloads. Maybe I should look into it again if it supports GW on A9LH v2. Still, I'd rather avoid the "how would I reassign CFW X to this button" questions for it. The folder naming scheme it uses to determine the button combo isn't exactly straightforward. I'd have to look up the naming scheme every time someone had a question.
     
    Last edited by Kazuma77, Jun 25, 2016
  7. ken28

    ken28 GBAtemp Maniac

    Member
    7
    Oct 21, 2010
    Germany
    so noone can tell how to use gw3ds 19lh and bootanim9?
     
  8. xdarkmario

    xdarkmario Philosopher

    Member
    7
    Dec 30, 2010
    United States
    Mushroom Kingdom
    *Frantically googles A9LH V2*
     
  9. Kazuma77

    Kazuma77 GBAtemp Maniac

    Member
    6
    May 11, 2008
    United States
    @Hayleia, I've recently tested it with Corbenik's chain loader. It works well for that, also. I've included your GWv2 launcher in my AIO configs on the iso site, and their stripped down counterparts here. Your launcher makes it much easier to recommend A9LH v2 to people. Thanks again.
     
    Hayleia likes this.
  10. Bonovox40

    Bonovox40 GBAtemp Advanced Fan

    Member
    5
    Apr 2, 2003
    United States
    So if I'm a GW card user, running a N3DS on v10.x emunand, with NO cfw installed (besides the mset hack).... can I follow this guide or do I need to start with that one guys a9lh install guide? (Obviously don't want to use GW al9h where its permanent)

    My only motivation for this is to have a way to boot directly into emunand. Hate having to go through system profile/DS profile, and hope it doesn't freeze up. (Happens like 20% of the time)
     
  11. Temptress Cerise

    Temptress Cerise Miss Magic~ <3

    Member
    9
    May 1, 2016
    United States
    You need to have completed Plailect's A9LH Guide before being able to use mine.
     
  12. Bonovox40

    Bonovox40 GBAtemp Advanced Fan

    Member
    5
    Apr 2, 2003
    United States
    I'm newb to messing w any a9lh setups. What does your version do different/addition to Plailects? And his guide is fine for N3ds and keeping the use of GW card/emunand right? (I like having both 3ds and CIA roms usable) :-)
     
  13. Temptress Cerise

    Temptress Cerise Miss Magic~ <3

    Member
    9
    May 1, 2016
    United States
    My guide is just so you can actually use GW with Luma3DS, without using BootCTR9. Even if you want to use this guide on this thread. You need A9LH. Doesn't matter which guide, this one or mine, you decide to use. You'll need to use either or, to get GW working on v2 A9LH. Plailect's A9LH Guide doesn't cover getting how to get GW's a9lh.bin working.

    As for keeping your EmuNAND, that's up to you. With A9LH you don't need to keep an EmuNAND anymore, you just keep your SysNAND updated, but you can't update SysNAND in GW Mode, otherwise you'll lose A9LH or brick.
     
  14. Bonovox40

    Bonovox40 GBAtemp Advanced Fan

    Member
    5
    Apr 2, 2003
    United States
    OK. Thanks for all the good info. Do any of these methods result in my current emunand being wiped or CIA/saves being lost/corrupted?
    And I only ever update in emunand. Sys fw is still 9.0x.
     
  15. Kazuma77

    Kazuma77 GBAtemp Maniac

    Member
    6
    May 11, 2008
    United States
    The only thing that gets lost with Plaillect's guide is anything installed to SysNAND, because it has you restore your EmuNAND to SysNAND (without overwriting the firm partitions, so you keep A9LH). There's no need to keep SysNAND on 9.x with A9LH (A9LH runs first, so SysNAND firmware version no longer matters) so Plaillect just has you overwrite it with your EmuNAND, because most people have presumably installed everything except GBA and DSiWare there. Which puts everything that is on your EmuNAND on your SysNAND (including updates). He then has you delete EmuNAND, but you don't have to. If you're feeling a bit more cautious, you can restore sysNAND_original.bin to EmuNAND instead. That gives you a chance to look it over, make sure you're not missing anything. I keep 9.2 around as an EmuNAND, just in case Nintendo breaks homebrew apps in a future update. If you decide you don't need it, you can always delete it later, after all.

    I have a more open-ended guide on a certain iso site's "3DS Tips and Tutorials" section that doesn't have you delete EmuNAND immediately, instead giving you the option to swap both, or leave both where they are. That ensures that you still have everything, either way, in case you forgot to back a save up from a GBA game, DSiWare title, or legit CIA. My version also hotkeys the apps and CFWs used with BootCTR, and includes a couple of GW shortcuts for those that own GW, like using the TinyFormat ROM instead of installing the CIA. Mine also sets up Gateway for you already, with a hotkey (the B button). Mine also walks you through configuring Cakes, along with Luma. In the event something doesn't work right, you have a second CFW to troubleshoot with (actually, mine more or less gives you all CFWs and apps). I also provide a link at the end of my guide to my "AIO A9LH Configurations" which lets you choose between 3 dedicated boot managers and 2 CFWs as your chain loader, and set pretty much any CFW as the default (unless you pick one of those two CFWs for your chain loader, in which case, they will be the default), with the ability to select all the other CFWs.

    I would argue that my revision gives more options, and it gives you GW already setup. However, it's only for setting up A9LH. It assumes you already have Menuhax setup (though it refers people to other guides that can help with that, including Plaillect's). Also, following Plaillect's guide, then grabbing my "AIO A9LH Configurations" afterward pretty much gives you the same results. So, choose whichever you find easier to follow. You can still get my complete setups with Gateway pre-configured either way. Temptress Cerise and I are both using the same work-around. I may have implemented it slightly differently, but the result is the same. GW will work in A9LH v2 when using Luma as your chain loader. The difference is, I didn't stop with Luma. I implemented the same fix in CBM9 and Corbenik. Though I've also added a work-around for Arm9Select. Any chain loader you pick should run GW without issue.
     
    Last edited by Kazuma77, Jul 3, 2016
  16. gha_razor

    gha_razor Member

    Newcomer
    2
    Aug 14, 2012
    Indonesia
    can somebedy help me, I am using exact same boot_config as the guide in page 1
    but why I can't access Luma using BootCtr9
    I can access all other like Gateway, Decrypt9, Emunand9, Hourglass, etc
    but when holding L or R to access Luma it gives me black screen
    I can access it normally without BootCtr9 though
    already tried version 0.4.1, 0.4, & 0.3 with same result
    haven't tried the 0.1 & 0.2 though but I think it will be the same
    so how can I fix this?

    this is the log file
    arm9bootloader.log
    is there something wrong in this log?
     
    Last edited by gha_razor, Jul 4, 2016
  17. Bimmel

    Bimmel ~ Game Soundtrack Collector ~

    Member
    10
    Jan 28, 2014
    Gambia, The
    If this is being used, my DSTWO does not work anymore on Luma3DS. Can anyone help me with this?
     
  18. Hayleia

    Hayleia GBAtemp Maniac

    Member
    7
    Feb 26, 2015
    France
  19. Bimmel

    Bimmel ~ Game Soundtrack Collector ~

    Member
    10
    Jan 28, 2014
    Gambia, The
    My setup is like this:

    Warning: Spoilers inside!
    What does this pathchanger do exactly?
     
  20. Hayleia

    Hayleia GBAtemp Maniac

    Member
    7
    Feb 26, 2015
    France
    The pathchanger tells Luma where it is so it can apply patches to itself when the 3DS needs to reboot in special modes like the DS mode.
     
Quick Reply
Draft saved Draft deleted
Loading...