Well just running it from luma chainloader works and it being flashed to my r4 works also. The only usage I was trying to get out of this is speed running ntrboothax, so I was trying to get rid of the swapping SD card step. And its pretty cool to be able to shack some ones 3ds with nothing but a flashcart.
There's no need to do all of that just to eliminate the swap step. You could just put the configuration files in a folder, then copy the folder to "0:/" and delete the folder for the last two lines. However, a same card installer can pretty much coexist with the configuration's files, with the exception of the need to overwrite "boot.firm" so the installer's payload can run. What I do is have a "boot.firm.bak" as part of the configuration, and have the installer copy it back right before it deletes all the temporary files (which I try to keep in the same folder as much as possible to reduce the number of "rm" lines).
I have a great example of a same card installer in my InScripted AIO (iso site, "CFW Discussion" section). I called it "One & Done" because it did the whole process with one script (now, one SSR, but the scripts are still included under the "source" folder so you can see what they do, and build your own variants if desired). Though it's not just for NTRBootHax. I included additional files to support Soundhax and other *hax methods so that people on 9.0 to 11.3 can use it without buying a flash cart. I've even included a launcher for MSET. So you may want to remove those if yours is just for NTRBootHax. Though it's not like the scripts waste much time deleting those extra files. They're pretty fast. Feel free to check it out and customize it for your own uses. No need to reinvent the wheel. I also have a "Shove & Shift" swap card. But it's definitely not for speed runs. I'm going for flexibility and customization, so I nearly fill the RAM drive. Though it's open to customization too. It's not even using SSRs like "One & Done" is (there's just too many scripts to compile them all and make it a CBM9-based hand-holder, and I'd expect anyone that's looking to create a swap card to know what they're doing).
Not entirely correct. The limitation comes from the size of VRAM (6MB, of which 3MB is already in use). Also, the data will be taken over to M:/vram.mem regardless of how you're running GM9.
You guessed right, that's an issue in firmtool. We already found it, and it's in the progress of being fixed. Fix coming today, I guess.
Alright, well, I hadn't actually tried it, because I have yet to come up with anything that could use it (especially with the 3 MB limitation). I suppose I could make a DSP firm "extractor" that works 100% of the time
but I'm not releasing my AIO here anyway, since it would no longer be an AIO with all that stuff removed.
That's great news that it was found (especially so quickly). I figured it was better to let someone they would actually listen to report it. They'd probably have just told me it "wasn't their problem" again (after the obligatory ad hominem attack, of course).
About Lazarus3DS since it relies on GM9, I successfully unbricked an N3DS on it, installed B9S, after some real hassles (renaming, finding specific files that the prep script didn't account for). The problem though is after all that, my console gets an 002-0121 message. If that's intentional, an online services ban, I think there should be a disclaimer because I did not read any such thing here:
https://github.com/AnalogMan151/Lazarus3DS
If there's a solution, I'd like to know.
Well, it uses files from a donor console. So, it would be my guess that if said donor gets banned, so do you. If they came from a public source, the seed probably got used long ago. I doubt there's anything d0k3 could add to GM9 to prevent this. Don't quote me on this, but I think you should be able to unban it via the usual tricks. Still, you might want to double check with
@AnalogMan since it's his project. Though I would hold off on performing an unban at this time. Based on the complaints I'm seeing pop up on various sites, it looks like a second wave is in progress.