Hacking [Release] rxTools - Roxas75 3DS Toolkit [fw 2.0 - 9.2]

  • Thread starter Thread starter Roxas75
  • Start date Start date
  • Views Views 3,355,901
  • Replies Replies 19,240
  • Likes Likes 151
Status
Not open for further replies.
Basically, running a DS cart requires twl_firm (it puts your 3ds info DS mode). Same for agb_firm for GBA suff. Virtual console stuff is basically a rom wrapped up with an emulator (so it runs like any other app).

Understanding this will help you understand why doing any of this from emunand is no trivial thing. You are basically rebooting as a different system when you launch DS or GBA. When you exit, you reboot NATIVE_FIRM. Now think how to maintain control over the system to hijack the reboots to redirect to emunand...
 
Basically, running a DS cart requires twl_firm (it puts your 3ds info DS mode). Same for agb_firm for GBA suff. Virtual console stuff is basically a rom wrapped up with an emulator (so it runs like any other app).

Understanding this will help you understand why doing any of this from emunand is no trivial thing. You are basically rebooting as a different system when you launch DS or GBA. When you exit, you reboot NATIVE_FIRM. Now think how to maintain control over the system to hijack the reboots to redirect to emunand...

Yeah, from what I understand with the current hacks and exploits there is no way for the cfw itself to handle forcing it to reboot back to emunand, and it seems like it is a royal pain in the ass to get it to load an exploited version of twl_firm or agb_firm at all.
 
I really don't know!

I like to compile my own versions :) + latest github changes is from a few hours ago, while lavanoid is still 05-12-2015 (15-12-05 in US date)
In the US we use Month-Day-Year. Just to let you know.

Basically, running a DS cart requires twl_firm (it puts your 3ds info DS mode). Same for agb_firm for GBA suff. Virtual console stuff is basically a rom wrapped up with an emulator (so it runs like any other app).

Understanding this will help you understand why doing any of this from emunand is no trivial thing. You are basically rebooting as a different system when you launch DS or GBA. When you exit, you reboot NATIVE_FIRM. Now think how to maintain control over the system to hijack the reboots to redirect to emunand...
One could use ThemeHax/MenuHax to load rxTools.3DSx when the system reboots into sysNand like I do.
 
Last edited by ccfman2004,
Makes sense, thanks.
In the US we use Month-Day-Year. Just to let you know.

One could use ThemeHax/MenuHax to load rxTools.3DSx when the system reboots into sysNand like I do.
either way, TWL/AGB are being launched from SYSNAND, not the SD. This is why A) you have to install them in BOTH SYSNAND and emunand (if you are unlinked), and B) why I roll my eyes every time someone says they want to be able to launch them from emunand. Even on versions where that seems to work, it's simply NOT what is happening.
 
Last edited by urherenow,
either way, TWL/AGB are being launched from SYSNAND, not the SD. This is why A) you have to install them in BOTH SYSNAND and emunand (if you are unlinked), and B) why I roll my eyes every time someone says they want to be able to launch them from emunand. Even on versions where that seems to work, it's simply NOT what is happening.
If TWL/AGB are being launched from sysNand then why are they included in the python script that people on O3DS have to download? I always thought that when you play a GBA or DS games while on emuNand it used files from emuNand since it thinks that emuNand is really sysNand. I know that when you exit a DS or GBA game the system reboots but I always thought that TWL and AGB were launched from emuNand. Maybe that's why people keep asking since no one has said that when you play a DS or GBA game, the 3DS uses TWL and AGB from sysNand. Or at least I didn't see it in a post here.
 
If TWL/AGB are being launched from sysNand then why are they included in the python script that people on O3DS have to download? I always thought that when you play a GBA or DS games while on emuNand it used files from emuNand since it thinks that emuNand is really sysNand. I know that when you exit a DS or GBA game the system reboots but I always thought that TWL and AGB were launched from emuNand. Maybe that's why people keep asking since no one has said that when you play a DS or GBA game, the 3DS uses TWL and AGB from sysNand. Or at least I didn't see it in a post here.

I wonder if what rxTools is supposed to be doing is patching the twl/agb firms in the emunand to redirect to the sysnand, and at the moment said patching is whats broken on the N3DS?
 
I wonder if what rxTools is supposed to be doing is patching the twl/agb firms in the emunand to redirect to the sysnand, and at the moment said patching is whats broken on the N3DS?
I believe that on the N3DS, TWL and AGB firms are not included in the firm files that rxTools uses where as they are on the O3DS.
 
I believe that on the N3DS, TWL and AGB firms are not included in the firm files that rxTools uses where as they are on the O3DS.
They are most certainly included in the emunand itself though as they are part of the 3ds system firmware files.

edit:

By that I mean they are included in the files that are installed to the "nand" portion of the sd card.
 
They are most certainly included in the emunand itself though as they are part of the 3ds system firmware files.

edit:

By that I mean they are included in the files that are installed to the "nand" portion of the sd card.
I'm referring to the decrypted files that rxTools uses. I wonder why we need them on the O3DS and not on N3DS.
 
I'm referring to the decrypted files that rxTools uses. I wonder why we need them on the O3DS and not on N3DS.
Probably because its loading a patched version as part of firmlaunch then. Whether the O3DS is actually using them instead of the ones in the nand, or whether the patch is just to redirect it to the system nand instead of the emulated one, i do not know.
 
Yes they are included for O3DS. Only native_firm is used on n3ds. Nothing is loaded as part of anything. Only 1 firm can be launched at a time. That's what the problem is. For it to truly work from emunand, all 3 firms would have to be RE'd to hack in a redirect to SD for rebooting native->twl, twl->native, native->AGB, AGB->native.
 
Yes they are included for O3DS. Only native_firm is used on n3ds. Nothing is loaded as part of anything. Only 1 firm can be launched at a time. That's what the problem is. For it to truly work from emunand, all 3 firms would have to be RE'd to hack in a redirect to SD for rebooting native->twl, twl->native, native->AGB, AGB->native.
So then what exactly is rxTools patching or doing to TWL/AGB firms on an O3DS?
 
So then what exactly is rxTools patching or doing to TWL/AGB firms on an O3DS?
Look at the source; it's in there (and frankly, I'm too uneducated to figure it out, but I'm learning...). The compiled patches are in rxtools/sys/patches on your SD and the resulting patched (or just decrypted?) AGB and twl firms are in /data after you've done the "data installation suite".
 
Last edited by urherenow,
I lost my profile exploit when I changed my username in the Sysnand. Is it possible for me to install it again without CN or another flashcart?? I am on 4.2

I am happily using the web browser exploit but was just wondering...
 
I lost my profile exploit when I changed my username in the Sysnand. Is it possible for me to install it again without CN or another flashcart?? I am on 4.2

I am happily using the web browser exploit but was just wondering...
FBI can for some things... try it out!
 
  • Like
Reactions: solitaire4eva
  • Like
Reactions: solitaire4eva
Status
Not open for further replies.

Site & Scene News

Popular threads in this forum