Separate names with a comma.
Discussion in '3DS - Homebrew Development and Emulators' started by d0k3, Aug 6, 2017.
I would prefer the memory version, wouldn't use flash cycles.
That actually seems like a useful feature, especially for apps like SafeB9SInstaller. No reason to keep it around if I am only going to use it once.
I'd prefer that, too, but the problem is finding a good memory location. I will definitely look into.
Sadly there's no real, standardized way to go from the regular firmware to an arbitrary payload (after all, that's what an exploit is for). There haven been some efforts in the form of arm9hook but that died off due to lack of interest.
Your best bet is to write to a *very* specific memory location in FCRAM and hope that a modified b9s would catch it on next boot... still doesn't fix the problem and it's messy at best, hacky at worst. There should've been a way to run binaries on baremetal on both CPUs since the early CFWs (svc 0x7B fixed the problem for the MPCore but since it was official nintendo code there's no guarantee it'd remain there).
How does Nintendo tell the console to reboot into DSi and GBA titles?
Quick question, but is it normal for GM9 to not use the top screen when starting it via GM9link?
Using the .3dsx version.
Nope, that's very strange. Does it happen everytime?
Just tried again. Yep, third time in a row now.
I added that im using the .3dsx version.
Now this is funny. I made a screenshot and it shows the top side of the screen. So its there, but I just cant see it.
Warning: Spoilers inside!
The launcher (Home or any other app with the right permissions) just asks for a title to be run and the caveat that a different kernel may be required, the currently running kernel and the called one do all the real work
The newly run kernel can receive parameters (mainly TitleID of the requested app and memory layout) by checking fixed positions in RAM
If you were really bored, you could (at least on paper) package a .firm homebrew (one that runs if flashed directly as kernel, or any?) as a fifth/sixth/etc kernel, then also create a forwarder that requests being run with that kernel...
Does not sound like a bad idea, just would take a lot of work.
This is happening to me too.
It's odd why so many people use the .3dsx version. Nintendo is able to see an invalid title Id sure, but the 3ds has to reboot into godmode9, and never actually runs the application, if not for a split second.
I dont care about what nintendo sees and whatnot, but thats how I organize my stuff. For almost everything hombrew related I want to use I use the hombrew launcher. Its how I first did it and I kinda like it that way. Except for things like FBI or NTR
Nicely done. Been reading code source and i'm surprised, how does the 3DS run GM9 on a hardware reboot? (i'm a noob )
@d0k3 What firmtool version did you use to compile this boot9strap fork? I'm having a hard time compiling it due to an unknown command --b9s=2
To my understanding, when loading the godmode9 app, it creates a file on the sd card, that when the 3ds reboots prioritizes over boot.firm. then godmode9 deletes that file.
Almost - it's the B9S mod that deletes the one-time payload
I'm already looking into this. Will be fixed soon.
Duh. There have been some changes that I was not aware of, I guess. Will look into that later, too.
I also tried starting GodMode9.firm straight from NTRBootHax and get the blank top screen issue. Decrypt9.firm works fine straight from NTRBootHax though.
@d0k3 would it be possible to create a version that runs .cias apon boot?